WCS/AP interface down messages

Unanswered Question
Nov 2nd, 2009
User Badges:

I just turned up my WCS so it can send me some alert email messages. I now constantly see some of my remote APs ( running in HREAP mode) having the following up/down messages. The down message are usually immediately followed by a up message in less than a minute.I never lost any network connectivity to the APs during these times and have not received complaints from any users ( at least no yet anyway ) What may be causing these messages and could they be a concern ? regards


AP 'ALAP2', interface '802.11a' is down on Controller '10.101.6.12'. (3 times)



AP 'ALAP2' associated with Controller '10.101.6.12' on Port number '29'.


AP 'ALAP2', interface '802.11a' is up on Controller '10.101.6.12'. (4 times)


AP 'ALAP2', interface '802.11b/g' is up on Controller '10.101.6.12'. (4 times)


E-mail will be suppressed up to 30 minutes for these changes.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
dmuralis Wed, 11/04/2009 - 05:39
User Badges:
  • Cisco Employee,

Hi,

Couple of things.


-When you get these notifications check the traplogs on your controller. Usually has more information and you can look for Heartbeat timeout/Lost heartbeat messages, where if the keepalives between the AP and the controller were missed for some reason, the AP would dissociate. You can also check the LWAPP uptime on the controller itself to verify if these messages are true.



If you just get Interface flap messages:


You will also see Interface flap messages when channel changes occur. Again on the traplogs you will see corresponding messages about channel change for that AP.


Interface flaps also seen sometimes when you have RLDP enabled.


kwanm63my Wed, 11/04/2009 - 06:52
User Badges:

Where do one look for the traplogs on the controller ? The only log file that I can find was under the management tab and for logs only 'message logs'. I don't believe RLDP is enabled.

kwanm63my Wed, 11/04/2009 - 07:27
User Badges:

I actually take that back and monitor the traplog the moment I saw the email.. but not sure if it's shedding any light for me..

The AP base radio mac address is 0:23:04:30:bc:d0 so I've included that section here.


Wed Nov 4 10:13:43 2009 AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:00:23:04:30:bc:d0 Cause=Admin Configured

8 Wed Nov 4 10:13:43 2009 AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:23:04:30:bc:d0 Cause=Admin Configured

9 Wed Nov 4 10:13:43 2009 AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:00:23:04:30:bc:d0 Cause=Admin Configured

10 Wed Nov 4 10:13:43 2009 AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:23:04:30:bc:d0 Cause=Admin Configured

11 Wed Nov 4 10:13:43 2009 AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:00:23:04:30:bc:d0 Cause=Admin Configured

12 Wed Nov 4 10:13:43 2009 AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:23:04:30:bc:d0 Cause=Admin Configured

13 Wed Nov 4 10:13:43 2009 AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:00:23:04:30:bc:d0 Cause=Admin Configured


etc

etc

some misc. Rogue AP messages and coverage hole here but the base mac is not the same so it probably came from another APs so I have not included..

etc

etc


15 Wed Nov 4 10:13:43 2009 AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:23:04:30:bc:d0 Cause=Admin Configured

16 Wed Nov 4 10:13:43 2009 AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:00:23:04:30:bc:d0 Cause=Admin Configured

17 Wed Nov 4 10:13:43 2009 AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:23:04:30:bc:d0 Cause=Admin Configured

18 Wed Nov 4 10:13:43 2009 AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:00:23:04:30:bc:d0 Cause=Admin Configured

19 Wed Nov 4 10:13:43 2009 AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:23:04:30:bc:d0 Cause=Admin Configured

20 Wed Nov 4 10:13:42 2009 AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:00:23:04:30:bc:d0 Cause=Admin Configured

21 Wed Nov 4 10:13:41 2009 AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:23:04:30:bc:d0 Cause=Admin Configured

22 Wed Nov 4 10:13:41 2009 AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:00:23:04:30:bc:d0 Cause=Admin Configured



dmuralis Wed, 11/04/2009 - 07:44
User Badges:
  • Cisco Employee,

On your controller itself if you look at "show traplog" from cli or from GUI- Management tab-> SNMP-> Trap logs, you will most likely see messages like :

Channel change on radio .... etc.


Are you seeing anything like that at all in the traps?

dmuralis Wed, 11/04/2009 - 07:47
User Badges:
  • Cisco Employee,

Once you determine you see no Channel change messages at all for the AP in question in the traps, check your Rogue location Detection Protocol and see if it is enabled.

kwanm63my Wed, 11/04/2009 - 07:56
User Badges:

I don't see any channel change message.

On my Rogue policies, it's disabled.

Under the "auto contain" options..


all 4 options are unchecked...

In fact, I believe these are all the defaults on the Rogue Policies page.



dmuralis Wed, 11/04/2009 - 07:59
User Badges:
  • Cisco Employee,

Is the LWAPP uptime corresponding to these flaps? Or does that remain normal?

kwanm63my Wed, 11/04/2009 - 08:23
User Badges:

The AP uptime never show that it dropped..

I'm not sure where to check the LWAPP uptime unless it's this. I do see a time statistics area under the general tab

and I do see a controller associated time and a controller association latency.

In there, I see that the associated time does seem to correspond to the last flap


Controller Associated Time 0 d, 01 h 03 m 57 s

Controller Association Latency 0 d, 00 h 01 m 23 s



kwanm63my Wed, 11/04/2009 - 09:42
User Badges:

I just had a another flap ( seen via email notification from the WCS ) and this time the 'time statistics' area is not really corresponding exactly..

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode