09-18-2014 06:27 AM - edited 07-05-2021 01:33 AM
Hello All
We are installing a secondary 5508 HA-SKU WLC under software version 8.0.100.
After configuring the primary 5508 (redundancy management ip, peer redundancy management ip, etc) we get the message "Please configure Redundancy Management VLAN before enabling redundancy" when we select SSO enabled. The redundancy management ips are in the same VLAN as the management ip and this is the default untagged VLAN. What have I missed?
John.
09-18-2014 08:36 AM
Check this link and correct your config:
http://networkguy.de/?p=558
REegards
10-22-2014 05:37 AM
This link is not for 8.0 software.
09-22-2014 02:37 AM
Hi John,
If you can please try to change the config to use tagged vlan for Management (Redundancy Management) and try again. Please keep me posted if this solves the problem.
Regards
Ralph
10-21-2014 10:49 PM
John...I'm, having a similiar problem - did you get around this?
10-22-2014 05:36 AM
You need to tag the management interface with a VLAN ID.
In 8.0 SSO is only supported on tagged management and redundancy management interface.
(It is still allowed in untagged mode if you upgrade from a SSO 7.x setup to 8.0).
Regards
Ralph
10-27-2014 10:07 AM
You nailed it Ralph - changed redundancy management interface to tagged and it works. Thanks for your help!
09-14-2015 09:49 AM
when you change the redundancy management interface to be tagged with management vlan ID, you should not able to ssh on the controller ?
09-14-2015 11:20 AM
The SSH capabilities are not affected by the adding of tag to the management interface.
09-16-2015 04:36 AM
i tried to tag the management interface with the management Vlan ID, but i found
the network connectivity down (ping is request time out).
i have Cisco WISM2 with version 8.0
09-17-2015 12:33 PM
Remember the Native Vlan on the 6500 side must be different from the Management id.
wism module x controller 1 native-vlan zzz
04-28-2015 12:49 AM
Hi Ralph,
We're running 8.0 in a WLC 8500 series but nor tagged nor untagged interface is working. This are the scenarios we have tested:
No scenario is working and in cases 1 and 2 we have lost the associated APs as they only recover in case 3.
In parallel, after enabling tagged interface in management, the "show ip arp" of the switch shows the IP through the HA interface and the ping is lost outwards WLC and inwards.
Any suggestion?
Regards.
04-28-2015 12:57 AM
Hi,
your Management interface should be tagged with a VLAN and the switchport connecting that interface should be running 802.1q trunk. Ensure that the native VLAN is not the VLAN your WLC management is on.
The RP port should ideally be a direct cable from 8510 to 8510. If you are using a VLAN ensure that it is not used for anything else. Run spanning-tree portfast and switchport mode access on the switch interface.
What kind of error do you get when building your SSO?
Regards
Ralph
01-06-2016 06:59 AM
While I understand that untagged mode is allowed if you upgrade from an SSO 7.X setup to 8.0; I would like to understand why this is so? Does the upgrade automatically enable tagging for management interface and if so, how does it know which vlan ID to tag it with?
How does one account for SSO 7.X setup with existing Native VLAN setting matching management interface on trunked interface if it cannot be the same after WLC is upgraded to 8.0?
Regards,
Matt
01-06-2016 07:33 AM
Hi Matt,
the upgrade doesn't change the configuration regarding management interface tagging.
Untagged will remain untagged. BUT; If you break the SSO in 8.x and try to enable it again you will get an error message because the SSO-Enable command will check your management interface.
You can keep your config if you expect it to run forever and never crash, but I'll recommend that you break the SSO and change the Management interface to be tagged.
Good Luck.
/Ralph
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide