cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1041
Views
0
Helpful
0
Replies

Mobility Express 8.4 in AP 1852i - "Make me Controller" not working

I got two units of 1852i running 8.4.100. Both are set to: 

AP Running Image : 8.4.100.0
Primary Boot Image : 8.4.100.0
Backup Boot Image : 8.3.112.0
AP Image type : MOBILITY EXPRESS IMAGE
AP Configuration : MOBILITY EXPRESS CAPABLE

I have configured AP-1 to be the WLC with one WLAN broadcasting an SSID. It is also acting as a DHCP server for the management vlan and a separate user vlan. AP-2 is acting just as a plain AP as expected. Config is saved. Reloading the whole system and it still works fine with AP-1 acting as WLC. Everything is working hunky-dory. 

However, when I go to AP-2 and click "Make me Controller", the WLC function doesn't swing over to AP-2 Nor can I ping the mgmt IP address. Strangely, the SSID is still being broadcasted. From the supposedly new WLC (AP-2), the console is on the startup wizard prompt:

"Would you like to terminate autoinstall? [yes]: "

The previous WLC (AP-1) console output is cycling with the following messages:

[*05/24/2017 12:23:01.4652]
[*05/24/2017 12:23:05.2340] Waiting for uplink IPv4 configuration
[*05/24/2017 12:23:10.2325] Waiting for uplink IPv4 configuration
[*05/24/2017 12:23:15.2409] Waiting for uplink IPv4 configuration
[*05/24/2017 12:23:16.2406] Resetting wired0 and srcr6, ifconfig down up
[*05/24/2017 12:23:16.2406]
[*05/24/2017 12:23:16.2506] chatter: tohost_srcr6 :: ToHost: device 'srcr6' went down
[*05/24/2017 12:23:18.2600] ADDRCONF(NETDEV_UP): wired0: link is not ready
[*05/24/2017 12:23:18.2600] chatter: tohost_srcr6 :: ToHost: device 'srcr6' came up
[*05/24/2017 12:23:18.4599] ADDRCONF(NETDEV_CHANGE): wired0: link becomes ready
[*05/24/2017 12:23:18.4699] wired0: 100 Mbps Full Duplex

I suppose AP-1 is set to boot itself as an AP mode but not getting the required info from the WLC or DHCP. Anyone knows if this is a bug? I have left AP-1 for some time but it never promotes itself as a WLC.

If I have to reload the whole system, AP-1 will assume the WLC role and AP-2 as a plain AP. Everything works normally again. Any thoughts? The woes in 8.3 drove me crazy but 8.4 seems to be taking the same road.  

xxx

0 Replies 0
Review Cisco Networking for a $25 gift card