Radio interfaces down after restart 3850 (WLC)

hwildenberg · ‎07-27-2015

Hi all,

I have an 3850 WLC with 16 access-points. After restarting the 3850 WLC or an power down the radio interfaces of the access-points are down when the WLC is restarted again !

If you connect via https you can see that the network status of the radios are enabled but the radios are down. If the network status is disabled and applied to the WLC and after this again enabled the radios are "Up and running" again.

Information of the WLC:

WS-C3850-48P

03.07.01E RELEASE SOFTWARE (fc3)

AP: 2702I

Does someone have this experience and is this maybe software related ?

Kind regards, Huub

Leo Laohoo · ‎07-27-2015

Must be a bug. Try a more stable IOS, like 3.6.X.

Rasika Nayanajith · ‎07-27-2015

Yes, it is a bug of the software code you running. See below

https://tools.cisco.com/bugsearch/bug/CSCuu32303

Symptom:
AP radio interfaces are in "administratively down" state after controller reload.

Conditions:
1. Register AP with 3650 v.3.7.1SE.
2. Interface status before reload:
AP Name MAC Address Slot Admin State Oper State Channel Width TxPwr
-------------------------------------------------------------------------------------------------------------
APd072.dcba.5da0 544a.00bf.ed00 0 Enabled Up 11* 20 1(*)

AP Name MAC Address Slot Admin State Oper State Channel Width TxPwr
------------------------------------------------------------------------------------------------------------------
APd072.dcba.5da0 544a.00bf.ed00 1 Enabled Up (36,40)* 40 1(*)

3. Reload WLC

4. Interface status after reload:
AP Name MAC Address Slot Admin State Oper State Channel Width TxPwr
-------------------------------------------------------------------------------------------------------------
APd072.dcba.5da0 544a.00bf.ed00 0 Enabled Down 11* 20 1(*)

AP Name MAC Address Slot Admin State Oper State Channel Width TxPwr
------------------------------------------------------------------------------------------------------------------
APd072.dcba.5da0 544a.00bf.ed00 1 Enabled Down (36,40)* 40 1(*)

On AP:
APd072.dcba.5da0#sh ip int b
Interface IP-Address OK? Method Status Protocol
BVI1 192.168.2.175 YES DHCP up up
Dot11Radio0 unassigned NO unset administratively down down
Dot11Radio1 unassigned NO unset administratively down down

Workaround:
Disable and re-enable 24ghz/5ghz networks after WLC reboot:
ap dot11 24ghz shutdown
ap dot11 5ghz shutdown
no ap dot11 24ghz shutdown
no ap dot11 5ghz shutdown

OR

Use the below EEM Script on the Device so that the above commands gets executed automatically whenever the device reboots or crashes etc..

event manager applet SURBG
event syslog occurs 1 pattern "%LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up" period 1
action 1 cli command "enable"
action 11 cli command "configure terminal"
action 111 cli command "ap dot11 24ghz shutdown"
action 1111 cli command "ap dot11 5ghz shutdown"
action 11111 cli command "no ap dot11 24ghz shutdown"
action 111111 cli command "no ap dot11 5ghz shutdown"

This is what the script is doing -

The script is looking for event ?"%LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up? here am using VLAN 1 as the Wireless management interface , after reboot when the WLC comes up and when the wireless management vlan comes up right away the WLC will execute the script running the 4 commands

So, We have to replace the vlan ID with what we are using for wireless management interface

Last Modified:

Jul 24,2015

Status:

Fixed

Severity:

2 Severe

Product:

Cisco 5700 Series Wireless LAN Controllers

Support Cases:

25

Known Affected Releases:

(3)

10.3(110.0)

10.3(2.112)

10.4(0.17)

Known Fixed Releases:

(3)

10.3(122.111)

10.3(3.97)

10.3(3.98)

Download software for Cisco 5700 Series Wireless LAN Controllers

HTH

Rasika

*** Pls rate all useful responses ***

hwildenberg · ‎07-31-2015

Hi Rasika,

Thanks for your help. I did the radio interfaces manualy shut/no shut and it was working.

Now I implemented the EEM script. I will test it when possible cause it is operational at the customer.

Thanks....

Huub