Wireless Access

6.3.1.15 master redudency not working :(

Everytime we configure master redudency - connectiviy between both controller on same vlan/segment is gone...

Disabling the VRRP master redudency making to ICMP to be back and work as needed.

 

any advise?

 

Standby:

master-redundancy

  master-vrrp 100

  peer-ip-address 10.101.205.22 ipsec e5f06e6f176fec6396ec8c4f384fc904

!

vrrp 100

  priority 110

  ip address 10.101.205.20

  vlan 205

  preempt delay 0

  tracking master-up-time 30 add 20

  no shutdown

!

 

 

Master:

master-redundancy
  master-vrrp 100
  peer-ip-address 10.101.205.21 ipsec aec369f929c79374d424ef9b301a552b
!
vrrp 100
  priority 115
  ip address 10.101.205.20
  vlan 205
  preempt delay 0
  tracking master-up-time 30 add 20
  no shutdown
!

 

Please advise.

 

Both controller can ICMP/ping each other on VLAN205...until i set the master redudency setting. :(

What state is spanning-tree in when you enable VRRP? 


Thanks, 
Tim

Sapnning - tree is off on all interfaces/both controllers. y?

The funny thing is that when master-redudency is enabled both controllers cannot icmp each other from same vlan/segment...but i can ping them from another computer on same VLAN .... both of them...

when i disable the master redudency - both controllers again able to ping each other (both of them showing on each other ARP table)

 

enable spanning tree for the vlan only. try that

• On both controllers?
• Even due that on the backbone switches both controllers are connected two STP is enabled?
• Even due all othe vlans and even the vlan of the vrrp dont got any issue connecting from extranl pc on same vlan ? (until i enable the master redudency ?..and then the icmp/connecitivy between controllers on same vlan is lost)

 

 

i had an issue with VRRP where the backup wouldn't becoy the master unless I enabled spanning tree for the vlan. it was enabled globally but wouldn't work. its a bug in the code that is fixed in a newer release

Hi,

 

Check the status of the IPSec tunnel between master and standby. if possible share the output of "show ip route" and "show switches"

 

Please feel free for any further help on this.

Please check this post

http://community.arubanetworks.com/t5/Unified-Wired-Wireless-Access/VRRP-Pinging-and-syncronisation-issue/m-p/219593

in the past i got the same issue and it was because i was using nat inside the VRRP Master VLAN, the VRRP as you know use IPSEC , and ipsec does not support nat.

Regards

Thanks AirHeads.

Problem solved by carefuly recondigured everything.

(Thanks for the tip for not doing route-src-nat on any vlan you establishing the ipsec between the controllers in)

where is my kudo  lol

K+ you :) just because it's late.
BUT FYI: srcnat wasn't configured on any vlan ip interface at all... the fix was a simple reconfigure ,looking good into details.(like ip/interfaces/vlan/vrrp id's) Solve the issue.

Please check this post

http://community.arubanetworks.com/t5/Unified-Wired-Wireless-Access/VRRP-Pinging-and-syncronisation-issue/m-p/219593

in the past i got the same issue and it was because i was using nat inside the VRRP Master VLAN, the VRRP as you know use IPSEC , and ipsec does not support nat.

Regards