Network Management

Reply
Highlighted
Contributor II

Re: Airwave won't pull in ap-105 previously deleted

Yes, these 3 lines are repeated many times but I don't see any correlation to the AP that is being classified a rogue.

Mon Mar  5 05:23:08 2012: node_id 4013.2892863, topic snmp_trap: Use of uninitialized value $client_mac in concatenation (.) or string at /usr/local/airwave/lib/perl/Mercury/Daemon/Monitoring/Client.pm line 548, <$__ANONIO__> line 8337915.
Mon Mar  5 05:23:18 2012: node_id 4013.2892899, topic snmp_trap: Use of uninitialized value in numeric eq (==) at /usr/local/airwave/lib/perl/Mercury/Daemon/Monitoring/Client.pm line 540, <$__ANONIO__> line 8337915.
Mon Mar  5 05:23:18 2012: node_id 4013.2892899, topic snmp_trap: Use of uninitialized value $client_mac in delete at /usr/local/airwave/lib/perl/Mercury/Daemon/Monitoring/Client.pm line 90, <$__ANONIO__> line 8337915.
Highlighted
Occasional Contributor I

Re: Airwave won't pull in ap-105 previously deleted

There are a number of these for the particular AP in question:

 

Mon Feb 27 08:42:52 2012: node_id 1266, topic interface_bandwidth: Failed reading bandwidth data for ap 'Rm18' (id: 1266)

 

None recently - last one was Feb 27.

 

 

Thu Feb 23 11:17:03 2012: node_id 359, topic thin_ap_status: RRDtool update of ap_is_up/440 (/var/airwave/rrd/ap_is_up/440) error: (rrdcached: illegal attempt to update using time 1330017410 when last update time is 1330017412 (minimum one second step)) Thu Feb 23 11:17:03 2012: node_id 359, topic thin_ap_status: RRDtool update of ap_sysuptime/440 (/var/airwave/rrd/ap_sysuptime/440) error: (rrdcached: illegal attempt to update using time 1330017410 when last update time is 1330017412 (minimum one second step))

 

About 10 of these in a group:

Sat Feb 25 11:13:54 2012: node_id 726, topic association_tables: Use of uninitialized value $model in index at /usr/local/airwave/lib/perl/Mercury/Utility/UserAgent.pm line 129, <$__ANONIO__> line 102857780.

 

And this one shows up again:

 

Wed Feb 29 02:39:43 2012: node_id 100, topic thin_ap_status: RRDtool update of ap_is_up/174 (/var/airwave/rrd/ap_is_up/174) error: (rrdcached: illegal attempt to update using time 1330504769 when last update time is 1330504780 (minimum one second step)) Wed Feb 29 02:39:43 2012: node_id 100, topic thin_ap_status: RRDtool update of ap_sysuptime/174 (/var/airwave/rrd/ap_sysuptime/174) error: (rrdcached: illegal attempt to update using time 1330504769 when last update time is 1330504780 (minimum one second step))

Highlighted
Aruba Employee

Re: Airwave won't pull in ap-105 previously deleted

Those errors are not related to thin AP discovery.

 

The last thing to check is whether the controller is properly reporting the AP over SNMP. I remember a controller bug a while ago where under certain rare cirumstances APs could stop showing up in the SNMP tables (which is how Airwave discovers them).

 

Please use this command on Airwave's CLI to walk the controller and see if the missing AP's name is present in the results (substitute CONTROLLER_IP with the controller's IP, and COMMUNITY with the controller's community string):

 

[root@your_amp mercury]# s2w CONTROLLER_IP COMMUNITY wlanAPName -OX

 Let me know if you are using SNMPv3 to monitor the controller and I will give that command.

Highlighted
Contributor II

Re: Airwave won't pull in ap-105 previously deleted

fyi - I have a TAC case open at this time.

Here is the output from you command:

[root@slu-amp mercury]#

 

 s2w [controller-ip] [snmp-string] DE-1010 -OX

DE-1010: Unknown Object Identifier (Sub-id not found: (top) -> DE-1010)
[root@slu-amp mercury]#

Highlighted
Aruba Employee

Re: Airwave won't pull in ap-105 previously deleted

Sorry, the 'wlanAPName' in the command should not be substituted with the name of the AP. 'wlanAPName' is the OID we want to walk.

Highlighted
Contributor II

Re: Airwave won't pull in ap-105 previously deleted

Sorry I misinterpreted.  That command returns all AP names but NOT the one in question - DE-1010 (which shows up on the local controller).

Highlighted
Occasional Contributor I

Re: Airwave won't pull in ap-105 previously deleted

We are not using SNMPv3.

 

The command returns a list of APs that does not include the missing AP. 

Aruba Employee

Re: Airwave won't pull in ap-105 previously deleted

Ok. One last thing to confirm: does the AP's LAN MAC end in EF or FF? I have tracked down the controller SNMP bug I referred to before and it seems to be triggered by specific MAC addresses. Unfortunately there is no available workaround. The bug has already been fixed and the fix will be included in a future release. What firmware version is your controller running?

View solution in original post

Highlighted
Contributor II

Re: Airwave won't pull in ap-105 previously deleted

Yes, for me.-  

d8:c7:c8:c1:bf:ff

Controllers are at 6.1.3.0

Airwave at 7.4.7

Highlighted
Occasional Contributor I

Re: Airwave won't pull in ap-105 previously deleted

Yes, it ends in FF.  Controller is running 6.1.2.6.

 

Thanks for all your help!