I have 2 Aruba 650's, A and B.
I want A to be the master and it has the following setup:
VLAN1: 192.168.1.250. It is behind an internet router, 192.168.1.254. This router is also the default gateway for the controller.
I'm not 100% sure, but I think the VLAN1-ip is the 'main' IP of the controller. It is selected under 'Controller IP Details' under Network/Controller.
VLAN3: 10.11.12.13. This is a local LAN.
Loopback Interface is empty.
I want B to be the local and it has the following setup:
VLAN1: 192.168.2.250. It is behind an internet router, 192.168.2.254. This router is also the default gateway for the controller. This internet router is a different internet router than the internet router controller A is behind. This IP also seems to be the 'main' IP of this controller.
VLAN3: 10.11.12.14. This is the same local LAN that controller A is on.
Loopback Interface is empty.
I'm trying to setup the master-local connection through VLAN3, since that's a local LAN and it has no firewalls etc. It should be much simpler than trying to route everything through the internet.
Before I set controller B to Local, controller A and B are able to ping each other on their VLAN3 IP's. Then I set controller B to local and set 10.11.12.13 as the master. I enter the same IPSEC key as was entered on the master for 0.0.0.0 (1 key for every possible local). After this, the controllers can no longer ping each other, probably because it's trying to setup IPSEC. However, the IPSEC is not successful it seems.
The process log on the local keeps repeating this:
Aug 19 11:32:11 cfgm[2276]: <399815> <INFO> |cfgm| Cannot connect to the master 10.11.12.13 error Operation already in progress errno 149 socket id 19
Aug 19 11:32:11 cfgm[2276]: <307242> <INFO> |cfgm| Failed to connect to the Master (10.11.12.13),Configuration socket will try again: Operation already in progress
Aug 19 11:32:11 cfgm[2276]: <307103> <INFO> |cfgm| send_tcp_hb_master 103 Connection to the master failed, Will retry socket ID 19 state CONFIG_SOCKET_NOTCONNECTED
Aug 19 11:32:21 cfgm[2276]: <307025> <DBUG> |cfgm| local:Sending heartbeat message to MMS
Aug 19 11:32:21 cfgm[2276]: <399814> <DBUG> |cfgm| Sending the heartbeat message. Not Responding counter=10
Aug 19 11:32:21 cfgm[2276]: <307240> <DBUG> |cfgm| Connecting the Local CFGM socket, state 1
Aug 19 11:32:21 cfgm[2276]: <399815> <INFO> |cfgm| Cannot connect to the master 10.11.12.13 error Operation already in progress errno 149 socket id 19
Aug 19 11:32:21 cfgm[2276]: <307242> <INFO> |cfgm| Failed to connect to the Master (10.11.12.13),Configuration socket will try again: Operation already in progress
I guess the problem might be that Aruba wants me to use the 'main' IP's of the controllers to setup the relation instead of the VLAN3 IP? Is this true? Can't I just use the VLAN3 IP's? If I change the 'main' IP to local LAN IP, I no longer have internet access on the controller, it seems it can no longer talk to the default gateway anymore at that moment.
Does anyone have suggestions how I can make this work?
Edit: it seems that when I tell Aruba local to use 10.11.12.13 as a master IP, it tries to connect to 10.11.12.13 through its default gateway (who has no knowledge of the other controller), even though it could just use the 10.11.12.14-interface, which would work perfectly fine.
#AP103