WLC 5508 reboot cause switch port link flap error disable

Hi All
today my customer call me saied after reboot WLC , the switch port was err-disable , the cause is link flap
after we reboot 3 times , the switch port link flap err-disable every time
does anyone to meet the same problem??
we don't know why the WLC rebboot will cause it , it just normal action on device
the WLC version is 7.4.100.0
link switch with access port , no port channel , no portfast
Asa Hung 2013/05/30

Hello Asa,
As per your query i can suggest you the following solution-
Complete these steps to reset the WLC to factory default settings using the CLI:
Enter reset system at the command prompt.
At the prompt that asks whether you need to save changes to the configuration, enter Y or N. The unit reboots.
When you are prompted for a username, enter recover-config to restore the factory default configuration.
The WLC reboots and displays the Welcome to the Cisco WLAN Solution Wizard Configuration Tool message.
Use the configuration wizard to enter configuration settings.
Note: Once the WLC is reset to defaults, you need a serial connection to the WLC in order to use the configuration wizard.
Hope this will help you.

Similar Messages

2960X 15.0(2)EX5 Stack Bug? Master Switch Ports link in Orange, no spanning Tree

Is anyone aware of a bug in version 15.0(2)EX5 for 2960X Switches that would cause a switch in the master role to stop linking in new ports in green (and passing traffic). I have 2 2960X-48FPD-L Switches in a stack and whichever switch I designate master will only link new connections in orange and not pass traffic. All ports linked in show up/up and can be seen in a show cdp neighbor but won't pass any other traffic.
If I unplug the Stacking cables both switches become masters and ports linked in green on the previous member switch stay green, but after it switches to master any new connections plugged in only link in orange.
If I switch priorities and reboot the problem switches to the new master switch and the problem goes away on the member switch.
Also, a switch in the master role does not show any spanning tree instances for ports in the orange link state.
Has anyone seen this issue and do you know of a solution?
Jim

A quick update for those with this same problem.
1. 15.2(3)E turned out to be very unstable causing my switch stack to randomly lockup/reboot one of the switches about once a week.
2. I downgraded back to 15.0(2)EX5 but found a workaround. It turns out the switch stack with the 15.0 versions does not like the switchport voice vlan command on any of the interfaces on the master switch. I simply removed the voice vlan configuration on the interfaces and all the switch ports linked in just fine. I would prefer to run the phones on a voice vlan, but it still works without, just the PC's and phones are on the same vlan.
Jim

WLC 5508 rebooted but still showing high uptime

Hi all,
I had to reboot our production WLC 5508 last night to apply a new adder license, which increased our AP count by 25.
We run a DMZ mobility controller alongside the primary controller, which handles our mobile/guest WLANs using a Mobility Anchor. Normally we would reboot both of these due to issues with the anchor after the primary is rebooted.
So last night I rebooted the primary after installing the new adder license. Once it came back up, I checked the license count and it had increased as per the new license. After that I rebooted the mobility controller, and waited to ensure that this came back up.
Almost straight away, all the AP's had re-associated with the primary (all 96 of them), and clients were starting to show up. I checked the same on the mobility controller (although this does not manage any AP's) and I could see mobility clients associating with this also.
The problem came this morning, when none of the mobility clients that were connected to the mobiltiy WLANs were able to get to the Internet, or any kind of outside connection. This is the typical issue we see when our core switch gets rebooted, or the primary on its own, without rebooting the secondary.
So to troubleshoot this morning the first thing I suddenly noticed was the uptime on the primary controller. It showed 298 days!!
Anyone seen this behaviour before? The WLC DID reboot - I watched it go down and POST again. Why would the uptime counter not reset?
We're on firmware 7.2.111.3 - which I realise is pretty old, but due to CIsco screwing us over with a limited upgrade path, we are not able to upgrade it yet (AP hardware not supported on any of the newer code above this version).
Any help appreciated!

In response to Sandeep, here's the sh sysinfo output:
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.2.111.3
Bootloader Version............................... 1.0.1
Field Recovery Image Version..................... 6.0.182.0
Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27
Build Type....................................... DATA + WPS
System Name...................................... UK***********
System Location.................................. Slough CoLo
System Contact................................... Greg Dent
System ObjectID.................................. 1.3.6.1.4.1.9.1.1069
IP Address....................................... 172.17.1.40
Last Reset....................................... Software reset
System Up Time................................... 0 days 3 hrs 42 mins 23 secs
System Timezone Location.........................
Configured Country............................... Multiple Countries:GB,RU,US
Operating Environment............................ Commercial (0 to 40 C)
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +44 C
External Temperature............................. +26 C
--More-- or (q)uit
Fan Status....................................... OK
State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 7
Number of Active Clients......................... 794
Burned-in MAC Address............................ **************
Power Supply 1................................... Present, OK
Power Supply 2................................... Present, OK
Maximum number of APs supported.................. 125
As you may notice, the uptime has now reset, but thats because I had to reboot it again this morning. I didnt grab the output before the second reboot. It seems whatever issue caused the uptime counter not to reset didnt occur this time.
Very odd.

WLC 5508 issue with 4 ports in portchannel

Hi,
We have one WLC 5508 and LAG is enabled on it but when we connect 4 cables to a distribution switch only 3 links are sending and receiving traffic and the 4th one is up with outgoing traffic from the distribution switch to WLC but nothing incoming.
Some APs went down and refuse to be registered back to the WLC. when we shut down the 4th port everything is back to normal.
the etherchannel config is identical and I can see all ports are active and not suspended :
interface GigabitEthernet2/2/1
description PortChannel-WLC1-Port1
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 60-67,2808,2922,2923,2932
switchport mode trunk
channel-group 99 mode on
interface GigabitEthernet2/2/2
description PortChannel-WLC1-Port2
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 60-67,2808,2922,2923,2932
switchport mode trunk
channel-group 99 mode on
interface GigabitEthernet2/2/3
description PortChannel-WLC1-Port3
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 60-67,2808,2922,2923,2932
switchport mode trunk
channel-group 99 mode on
interface GigabitEthernet2/2/4
description PortChannel-WLC1-Port4
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 60-67,2808,2922,2923,2932
switchport mode trunk
channel-group 99 mode on

sh etherchannel 99 sum
Flags: D - down        P - bundled in port-channel
        I - stand-alone s - suspended
        H - Hot-standby (LACP only)
        R - Layer3      S - Layer2
        U - in use      N - not in use, no aggregation
        f - failed to allocate aggregator
        M - not in use, no aggregation due to minimum links not met
        m - not in use, port not aggregated due to minimum links not met
        u - unsuitable for bundling
        d - default port
        w - waiting to be aggregated
Number of channel-groups in use: 38
Number of aggregators:           38
Group Port-channel Protocol    Ports
------+-------------+-----------+-----------------------------------------------
99     Po99(SU)         -        Gi2/2/1(P)     Gi2/2/2(P)     Gi2/2/3(D)
                                 Gi2/2/4(P)
Last applied Hash Distribution Algorithm: Fixed
Gi2/2/3 is down becasue we had to shut down the interface because when it is up many APs refuse to register.

WLC 5508 reboots itself after upgrading to 7.5.102.0

Hello all.
We have two WLC 5508 and we upgraded both to software release 7.5.102.0 two weeks ago. We also upgrade the FUS to version 1.7.
Since then both WLC reboot randomly once or twice a day with no obvious reason.
Is anyone else facing the same issue?
Many thanks.

Ok, in that case it is very difficult to pin-point the cause for these sorts reboots. It may be due to a unknown bug. Go through below 7.5.102.0 release notes and see any unresolved caveats related to your issue
http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn75.html#wp1030058
Have you configure syslog on your WLC ? If so see what is the last syslog message sent by WLC before reloading, it may indicate something.
Do more observation & see whetehr controller reboot every time it hit 1k client limit. Try to narrow down the criteria to identify under what conditions this will trigger.
In my controller I do not have that many clients & cannot comment if it is related.
HTH
Rasika

Set-VMNetworkAdapterVlan throws Failed while applying switch port settings 'Ethernet Switch Port VLAN Settings' error

Hi,
I'm following this
guide I'm getting an error when running the below command:
Set-VMNetworkAdapterVlan -vmname PurpleVM1 -Isolated -PrimaryVlanId 2 –SecondaryVlanId 4
Generates the following error:
Set-VMNetworkAdapterVlan : The operation failed.
Failed while applying switch port settings 'Ethernet Switch Port VLAN Settings' on switch 'New Virtual Switch': One or
more arguments are invalid (0x80070057).
A parameter that is not valid was passed to the operation.
Does anyone know why this is happening?
ta

Hi TomG101,
It seems that there is a configuration conflict on the virtual switch port .
Also I tested the command on my lab , it works .
For troubleshooting please create a new virtual switch then try to configure again .
Any further information please feel free to let us know .
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

WLC 5508 and its 8 ports

I've three independants sites that I want to manage with the controller 5508, do I have to use three port of management?
could you explain me the use of managment interface because the wlc contains 8 and I'm using the first port "1".

Hi Sali,
This link should give you a good idea of how those ports work:
http://www.cisco.com/en/US/docs/wireless/controller/7.4/configuration/guides/consolidated/b_cg74_CONSOLIDATED_chapter_011010.html
Ultimately, you can only assign a single "port" number to your management interface with LAG disabled. With LAG enabled, it is similar to an etherchannel setup where you are bundling all the connected ports together.
Cheers,
Erwin
How helpful was I? Don't forget to rate me when you have the chance!

Cisco WLC 5508 and LACP

Hi Fellows,
I wanna know if 5508 Cisco WLC support LACP or not. Actually i work in a project where i must
connect WLC 5508 in Enterasys Switches with Link Aggregation.
Enterasys Switches support LACP 802.3ad but when i learn Cisco Books i see that WLC 5508
doesn't support LACP.
Can you help please ?
Sincerely
Joseph

Hi,
Please take a look into the config guide:
http://www.cisco.com/en/US/docs/wireless/controller/7.0/configuration/guide/c70mint.html#wp1277652.
You can read there:
Once the EtherChannel is configured as on at both ends of the link, it does not matter if the Catalyst switch is configured for either Link Aggregation Control Protocol (LACP) or Cisco proprietary Port Aggregation Protocol (PAgP) because no channel negotiation is done between the controller and the switch. Additionally, LACP and PAgP are not supported on the controller.
HTH,
Tiago
If this helps you and/or answers your question please mark the question as "answered" and/or rate it, so other users can easily find it.

Link flap problem?

Hello everyone,
Quick question about what causes a "link flap failure"
Here is the output
11-07-2005 18:48:38 Local7.Warning 172.16.208.184 1737: *Mar 13 05:47:09.196: %PM-4-ERR_DISABLE: link-flap error detected on Gi0/1, putting Gi0/1 in err-disable state
11-07-2005 18:49:10 Local7.Error 205.110.152.19 9281: 1w3d: %LINK-3-UPDOWN: Interface FastEthernet0/5, changed state to up
11-07-2005 18:50:53 Local7.Warning 172.16.208.184 1738: *Mar 13 05:49:23.765: %PM-4-ERR_RECOVER: Attempting to recover from link-flap err-disable state on Gi0/1
11-07-2005 18:50:55 Local7.Error 172.16.208.184 1739: *Mar 13 05:49:26.137: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up
I leave the errdisable recovery on and it brings the port back up once the timer goes.
What causes this link flap?
Thanx

Hello there 8)
From the previously mentioned switch:
Gi0/1 TRUNK TO ISF159 connected trunk a-full a-1000 1000BaseLX
CONTRA#sh run | begin Gig
interface GigabitEthernet0/1
description TRUNK TO AS
switchport mode trunk
This is from the connected switch:
Gi0/1 TRUNK TO CONTRACTO connected trunk a-full a-1000 1000BaseLX
AS#sh run | begin Gig
interface GigabitEthernet0/1
description TRUNK TO CONTRACTORS
switchport trunk encapsulation dot1q
switchport mode trunk
no ip address
Thanx for any help

Interfaces WLC 5508

Hi good afternoon,
I have an easy question, checking how WLC with AP associated making a tunneling in CAPWAP (standard RFC 4188) using a UDP dest port looks like its necessary L3.
Let me try to explain what i want:
I have a WLC 5508 with a Switch the trunk pass 4 vlans. So one of the is used for Management to associated APS with the WLC and i added full config but when i add a new interface:
Interface Address
VLAN Identifier
IP Address
Netmask
Gateway
Why its necessary put an IP in all vlans? If i try to use blank IP got an error, and with 0.0.0.0 i can't add SSID after this...
WLC not works fully at L2? For every interface is necessary add an IP.
Switch are L2 and no needs an IP.
Router = L3 needs an IP.
Can someone explain me this?
Thanks and regards

You are correct, the WLC is purely a L2 device, it does not route.
Don't think of the interface as an SVI, it's not.
The reason that every interface needs an IP address, has to do with roaming.
If you do an intercontroller roam, and both the WLC are using VLAN ID 10 on both. What happens to your client traffic if WLCA = 10.10.10.x/24 and WLCB = 10.10.110.0/24?
Your client would not be able to pass traffic, as it would not have the correct IP address. Now, if the client were to force a DHCP at every roam, you could get around this, but that would also delay the client in being able to pass traffic.
So with the IP and the VLAN ID, the WLC is able to know if the roam is a pure L2 roam, same VLAN same IP range, and move the MSCB entry from one WLC to the other. Or if it's supposed to be a L3 roam, where it needs to setup anchoring of the client traffic.
Make sense?
Steve

2960s Link-Flap issue.

I've recently had a few ports on 48 way 2960s go in to err mode.
Bit of digging and they have been disabled due to link flapping. I disconnected the devices to check cables etc and all checked out. I've since repatched in another stacked 2960s without issue.
The switch with the issue seems to have got progressively worse, what started with a couple of ports now has gone to gi1/0/33-40 are now disabled due to flapping.Even though none of the ports are now in use. I've restarted the switch just in case it was having a special moment but no luck.
show log displays
000062: Dec 17 19:30:19.490: %PM-4-ERR_DISABLE: link-flap error detected on Gi1/0/40, putting Gi1/0/40 in err-disable state
Switch attempts to recover after 300s with no luck. Just to confirm there is nothing patched in to the effected ports.
Any suggestions or is it it RMA time.

Hello Leo Laohoo,
Thank you for the quick reply,
I mentioned earlier in the thread that I've unpatched and tested the cables and have moved the devices in to another switch all working fine. Ports also have recover on too, and still are in error mode.
Below is test result on one port which shows fine.
Interface Speed Local pair Pair length        Remote pair Pair status
Gi1/0/33 auto Pair A     0    +/- 0 meters N/A         Normal
                Pair B     0    +/- 0 meters N/A         Normal
                Pair C     0    +/- 0 meters N/A         Normal
                Pair D     0    +/- 0 meters N/A         Normal
Regards
Rob

WLC 5508 Failure to upgrade code

Hi,
I'm trying to upgrade a WLC 5508 and I'm getting the following errors:
TFTP Code transfer starting.
TFTP receive complete... extracting components.
Failure while validating the signature!
TFTP Failure while storing in flash!
The image is good and for the right model. Does anyone have any ideas?

Hello Kayle
both of my controllers are brandnew according to their serial-#: and Leolaohoo's post.
Controller_1 : FCW1522L021
Controller_2 : FCW1522L022
Facts:
=====
1. Both are running code 7.0.98.218
2. Upgrade to 7.0.116.0 (AIR-CT5500-K9-7-0-116-0.aes) failed
Just to be sure, I also tried code AIR-CT5500-LDPE-K9-7-0-116-0.aes, which also failed on both
3. No firewall or antivirus is active on my workstation
4. Upgrade was tried via Service-Port as well as management-interface
5. Upgrade was tried via FTP as well as TFTP
6. Short after file-transfer has been finished I get the corresponding message and even short after that I receive the message "Failure while validating the signature"
7. Doing a "show logging", I get the message that the downloaded file seems to be corrupted (screenshot below), but checking the filesize gives me exactly the same size as on the CCO before downloading

Why would you NOT enable Loop Guard on switch ports?

Hello
Why would you NOT enable Loop Guard on switch ports?
It is disabled by default on all ports.
Since it prevents loops, in the absence of receiving BPDUs on non-designated ports, why would it not be enabled by default?

Ziffy wrote:
The Galaxy S4 supports Google Wallet, but yet you block it from being used. Why exactly? This is not right. I suggest you enable it before you start losing customers. Is there anybody out there that would like to start a petition? Perhaps look into whether or not this is actually legal? Seems like unfair practices to me. Thoughts?
Good luck with that. FCC already did and have left it alone... My theory is because... Google charges carriers to use allow devices to use it. At one point Sprint paid to go exclusive for wallet. FCC can't force you to buy your competitors product.

EEM on port error-disable due to UDLD

I would like to ask from the EEM community for some assistance in regards to crafting an EEM script for an ME-3800X. We have one or two appliances whereby the only uplink (TenGigabitEthernet0/1 and/or TenGigabitEthernet0/2) goes into error-disable and caused by UDLD. What I am looking for is a script to do the following:
1. If the ports TenGigabitEthernet0/1 and/or TenGigabitEthernet0/2 goes into error-disable caused by UDLD or link-flap then disable the port, wait for 5 seconds, enable the port;
2. Wait for 15 seconds and send an email.
I only want this EEM to work on the TenGigabitEthernet interfaces and I do not want the EEM script to do this on the access ports.
Error-disable recovery is a global option and there's no option to limit on a per-interface level.
Thank you in advance.

Thanks for responding, Joe.
We were not able to take down the error messages but I believe they error messages could be:
%UDLD-4-UDLD_PORT_DISABLED: UDLD disabled interface Te0/2, unidirectional link detected
%PM-4-ERR_DISABLE: udld error detected on Te0/2, putting Te0/2 in err-disable state
Could an EEM script be created when an error message or an event of "unidirectional link detected" occurs, do the following:
1. In privilege mode, issue the command "udld reset".
2. Wait for 30 seconds and then send an email.
Thanks for your assistance and support, Joe.

Error disabled ports

I have a 3550 switch that gets a error-disabled copper ports. There is no errors ont the port. What else would cause it to be disabled?

Although there is no error on the port , there should be an error message in the log that should tell you the reason why the port got error disabled like port security violation , loopback detection , etherchannel misconfig etc.
You can enable errordisable recovery for all different causes by setting a timer. What happens is once this timer expires , the port is brough out of error dsiabled state.
Here are some of the useful commands.
D-C3550-2A(config)#errdisable ?
detect Error disable detection
recovery Error disable recovery
D-C3550-2A(config)#errdisable recovery ?
cause Enable error disable recovery for application
interval Error disable recovery timer value
Hope this helps.
Salman Z.

WLC 5508 reboot cause switch port link flap error disable

Similar Messages

Maybe you are looking for