10-06-2014 04:11 AM - edited 07-05-2021 01:39 AM
Hi Folks,
I've a WLC 5670 with AIR-CAP3602I and sometimes all connected AP's restarts and I can't figure out why this is happening.
can someone help on this?
find the attached logs for more details
best regards,
Alcides
Solved! Go to Solution.
01-21-2015 05:42 AM
Open a TAC case. My peer mentioned to me that two of his clients had the same issue and had the unit RMA'd.
-Scott
10-06-2014 04:55 AM
Hi Alcides,
What version of IOS-XE you run on this 5760 ?
Below may indicate wrong regulatory domain AP connected & 5760 rejecting the registration of them
*Oct 6 10:25:48.201: *%LWAPP-3-RD_ERR6: 1 wcm: APs (1cde.a7e8.c6e0) regulatory domain (-C) is not supported in country (ZA ), slot 80211a (1) supports -E *Oct 6 10:25:48.203: %LINK-3-UPDOWN: Interface Capwap39, changed state to up *Oct 6 10:25:48.247: *%LWAPP-3-VENDOR_PLD_VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload(155) with length=10 failed - AP 1c:de:a7:e8:ad:c0 *Oct 6 10:25:48.247: *%LWAPP-3-RD_ERR6: 1 wcm: APs (1cde.a7e8.adc0) regulatory domain (-C) is not supported in country (ZA ), slot 80211a (1) supports -E *Oct 6 10:25:48.250: %LINK-3-UPDOWN: Interface Capwap40, changed state to up *Oct 6 10:25:48.550: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap38, changed state to up *Oct 6 10:25:48.607: *%LWAPP-3-VENDOR_PLD_VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload(155) with length=10 failed - AP 1c:de:a7:e8:c7:00 *Oct 6 10:25:48.608: *%LWAPP-3-RD_ERR6: 1 wcm: APs (1cde.a7e8.c700) regulatory domain (-C) is not supported in country (ZA ), slot 80211a (1) supports -E
Check correct regulatory domain AP are in use. Refer this for detail
HTH
Rasika
**** Pls rate all useful responses ****
10-06-2014 05:16 AM
Hi Rasika,
This part of regulatory domain is about one new AP that we've bought that is on AIR-CAP3602I-C-K9. the issue that I'm facing is that I get my AP's restarting on regular basis. and I can't figure out the reason why.
best regards,
Alcides
10-06-2014 09:33 PM
Check the uptime of the individual APs. If they rebooted, then check the cabling.
10-07-2014 12:42 AM
Hi Leo,
I've 42 APs configured on my controller do I've to check each one? because all of them reboot time to time.
Best regards,
Alcides
10-07-2014 04:30 AM
Still doesn't answer the question about faulty cabling. Check every AP that bounces. If the AP reboots, then you need to determine why first. Cable will always be your "usual suspect".
11-03-2014 02:45 AM
Hi Leo,
I found that it happen because spanning-tree issue... I found this log on Switch Core 6509 when the AP's was unavailable
008694: Nov 3 11:34:51 GMT: %SPANTREE-2-LOOPGUARD_BLOCK: Loop guard blocking port Port-channel4 on VLAN0401.
008695: Nov 3 11:34:53 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet3/5, changed state to down
008696: Nov 3 11:34:53 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet3/13, changed state to down
008697: Nov 3 11:34:53 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel4, changed state to down
008698: Nov 3 11:34:53 GMT: %LINK-3-UPDOWN: Interface TenGigabitEthernet3/5, changed state to down
008699: Nov 3 11:34:53 GMT: %LINK-3-UPDOWN: Interface Port-channel4, changed state to down
008700: Nov 3 11:34:53 GMT: %LINK-3-UPDOWN: Interface TenGigabitEthernet3/13, changed state to down
How can I prevent this?
My Port-channel is configured like This
interface Port-channel4
description Link to WLC-01
switchport
switchport trunk native vlan 3
switchport trunk allowed vlan 4,400-402,993
switchport mode trunk
logging event link-status
spanning-tree portfast edge trunk
spanning-tree bpduguard disable
11-03-2014 06:07 PM
spanning-tree portfast edge trunk spanning-tree bpduguard disable
Please take these two lines OFF your configuration.
11-06-2014 01:08 AM
Hi Leo,
Thanks for your attention,
Even with that line off I can't get ride off the spanning-tree issue
008760: Nov 5 11:46:34 GMT: %SPANTREE-2-LOOPGUARD_BLOCK: Loop guard blocking port Port-channel4 on VLAN0401.
008761: Nov 5 11:46:35 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet3/5, changed state to down
008762: Nov 5 11:46:35 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet3/13, changed state to down
008763: Nov 5 11:46:35 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel4, changed state to down
008764: Nov 5 11:46:35 GMT: %LINK-3-UPDOWN: Interface TenGigabitEthernet3/5, changed state to down
008765: Nov 5 11:46:35 GMT: %LINK-3-UPDOWN: Interface Port-channel4, changed state to down
008766: Nov 5 11:46:35 GMT: %LINK-3-UPDOWN: Interface TenGigabitEthernet3/13, changed state to down
Best Regards,
Alcides
11-06-2014 03:49 AM
Post the configuration of the interfaces Ten 3/5, Ten 3/13 and PO4.
Also post the output to the command "sh run | i loopguard".
I want to see if you've got "spanning-tree guard loop" enabled or not. This is the command that's shutting down your ports.
11-06-2014 03:53 AM
interface Port-channel4
description Link to WLC-01
switchport
switchport trunk native vlan 3
switchport trunk allowed vlan 4,400-402,993
switchport mode trunk
logging event link-status
end
#sh run int ten3/5
Building configuration...
Current configuration : 221 bytes
!
interface TenGigabitEthernet3/5
switchport
switchport trunk native vlan 3
switchport trunk allowed vlan 4,400-402,993
switchport mode trunk
logging event link-status
udld port
channel-group 4 mode desirable
end
#sh run int ten3/13
Building configuration...
Current configuration : 222 bytes
!
interface TenGigabitEthernet3/13
switchport
switchport trunk native vlan 3
switchport trunk allowed vlan 4,400-402,993
switchport mode trunk
logging event link-status
udld port
channel-group 4 mode desirable
Port-channel4 is up, line protocol is up (connected)
Hardware is EtherChannel, address is e02f.6d6a.8530 (bia e02f.6d6a.8530)
Description: Link to ACFIN-WLC-01
MTU 1500 bytes, BW 20000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 10Gb/s, media type is unknown
input flow-control is on, output flow-control is off
Members in this channel: Te3/5 Te3/13
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 11800000 bits/sec, 2438 packets/sec
5 minute output rate 11312000 bits/sec, 1733 packets/sec
5033959678 packets input, 3102199783887 bytes, 0 no buffer
Received 52139517 broadcasts (37210897 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
3860530568 packets output, 3020432044356 bytes, 0 underruns
0 output errors, 0 collisions, 4 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 PAUSE output
0 output buffer failures, 0 output buffers swapped out
#sh int te3/5
TenGigabitEthernet3/5 is up, line protocol is up (connected)
Hardware is C6k 10000Mb 802.3, address is e02f.6d6a.8530 (bia e02f.6d6a.8530)
MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 10Gb/s, media type is 10Gbase-SR
input flow-control is on, output flow-control is off
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 8334000 bits/sec, 1629 packets/sec
5 minute output rate 5568000 bits/sec, 948 packets/sec
2525964025 packets input, 1570705218143 bytes, 0 no buffer
Received 19974119 broadcasts (14752425 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
1868319844 packets output, 1461956537250 bytes, 0 underruns
0 output errors, 0 collisions, 5 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 PAUSE output
0 output buffer failures, 0 output buffers swapped out
#sh int te3/13
TenGigabitEthernet3/13 is up, line protocol is up (connected)
Hardware is C6k 10000Mb 802.3, address is e02f.6d6a.8538 (bia e02f.6d6a.8538)
MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 10Gb/s, media type is 10Gbase-SR
input flow-control is on, output flow-control is off
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 4459000 bits/sec, 986 packets/sec
5 minute output rate 7070000 bits/sec, 925 packets/sec
2509404833 packets input, 1532247566534 bytes, 0 no buffer
Received 32283854 broadcasts (22573014 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
1993938916 packets output, 1559272067390 bytes, 0 underruns
0 output errors, 0 collisions, 5 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 PAUSE output
0 output buffer failures, 0 output buffers swapped out
11-06-2014 01:14 PM
Also post the output to the command "sh run | i loopguard".
11-06-2014 01:22 PM
#sh run | i loopguard
spanning-tree loopguard default
11-06-2014 02:08 PM
There you go. There's the culprit. Take the off the global command.
11-07-2014 05:43 AM
Hi Leo,
thanks for your attention but after removing that command the problem get worst
008940: Nov 7 10:46:00 GMT: %SPANTREE-2-BLOCK_BPDUGUARD: Received BPDU on port Port-channel4 with BPDU Guard enabled. Disabling port.
008941: Nov 7 10:46:00 GMT: %PM-4-ERR_DISABLE: bpduguard error detected on Po4, putting Te3/5 in err-disable state
008942: Nov 7 10:46:00 GMT: %PM-4-ERR_DISABLE: bpduguard error detected on Po4, putting Te3/13 in err-disable state
008943: Nov 7 10:46:00 GMT: %PM-4-ERR_DISABLE: bpduguard error detected on Po4, putting Po4 in err-disable state
008944: Nov 7 10:46:00 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet3/5, changed state to down
008945: Nov 7 10:46:00 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet3/13, changed state to down
008946: Nov 7 10:46:00 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel4, changed state to down
008947: Nov 7 10:46:00 GMT: %LINK-3-UPDOWN: Interface TenGigabitEthernet3/5, changed state to down
008948: Nov 7 10:46:00 GMT: %LINK-3-UPDOWN: Interface Port-channel4, changed state to down
008949: Nov 7 10:46:00 GMT: %LINK-3-UPDOWN: Interface TenGigabitEthernet3/13, changed state to down
Best regards,
Alcides
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: