Wireless Access

Upcoming community maintenance Oct. 27th through Oct. 29th
For more info click here
Reply
Highlighted
MVP

Since upgrade to 8.5.0.9 Airwave not seeing clients

Hi,


I have since upgraded by AOS 8 environment to 8.5.0.9 - since this Airwave no longer displays and shows connected clients even though I can see them on the MM and the MDs.  The controllers are showing as up in Airwave so I am not sure why it isn't able to see or display the clients.  Has anyone else experienced this and know how to fix?


I also get trap alerts, but there is no downtime to any of the sites or devices, all the time since the upgrade, hundreds of these a day,  an example is this:

 

wlsxNVrrpStateChange wlsxTrapVrrpID.0: 10, wlsxTrapVrrpMasterIp.0:
0.0.0.0, wlsxTrapVrrpOperState.0: initialize(1), wlsxTrapTime: 7/22/2020
11:36:08 UTC-2
linkUp ifIndex.16388: 16388, ifDescr.16388: 802.1Q VLAN,
ifAdminStatus.16388: up(1), ifOperStatus.16388: up(1), ifName.16388: vlan
wlsxNVrrpStateChange wlsxTrapVrrpID.0: 10, wlsxTrapVrrpMasterIp.0:
0.0.0.0, wlsxTrapVrrpOperState.0: backup(2), wlsxTrapTime: 7/22/2020
11:36:10 UTC-2
linkDown ifIndex.16388: 16388, ifDescr.16388: 802.1Q VLAN,
ifAdminStatus.16388: up(1), ifOperStatus.16388: down(2), ifName.16388:
vlan
wlsxNVrrpStateChange wlsxTrapVrrpID.0: 10, wlsxTrapVrrpMasterIp.0:
0.0.0.0, wlsxTrapVrrpOperState.0: initialize(1), wlsxTrapTime: 7/22/2020
11:36:10 UTC-2
linkUp ifIndex.16388: 16388, ifDescr.16388: 802.1Q VLAN,
ifAdminStatus.16388: up(1), ifOperStatus.16388: up(1), ifName.16388: vlan
wlsxNVrrpStateChange wlsxTrapVrrpID.0: 10, wlsxTrapVrrpMasterIp.0:
0.0.0.0, wlsxTrapVrrpOperState.0: backup(2), wlsxTrapTime: 7/22/2020
11:36:11 UTC-2
linkDown ifIndex.16388: 16388, ifDescr.16388: 802.1Q VLAN,
ifAdminStatus.16388: up(1), ifOperStatus.16388: down(2), ifName.16388:
vlan
wlsxNVrrpStateChange wlsxTrapVrrpID.0: 10, wlsxTrapVrrpMasterIp.0:
0.0.0.0, wlsxTrapVrrpOperState.0: initialize(1), wlsxTrapTime: 7/22/2020

 

Highlighted
Guru Elite

Re: Since upgrade to 8.5.0.9 Airwave not seeing clients

You should re-enter the snmp read string on Airwave for the controller.  That is the main way Airwave determines if a device is up and how many clients it has on it.  If you have double-checked that, I would open a TAC case.


*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.5 User Guide
InstantOS 8.5 User Guide
Airheads Knowledgebase
Airheads Video Knowledge Base
Remote Access Point Solution Guide
ArubaOS Consolidated Release Notes
ArubaOS 8 ViA VPN Solution Guide
Highlighted
MVP

Re: Since upgrade to 8.5.0.9 Airwave not seeing clients

I have tried that but still the same.


Strange thing is I can see one of the clients connected however on the controller GUI and the MM I can see there is actually 8 clients.  

 

I have raised a support request just awaiting to hear back was hoping maybe someone knew something on here that could be a quick fix


Thanks

Highlighted

Re: Since upgrade to 8.5.0.9 Airwave not seeing clients

What is the Airwave version? Is prefer AMON enabled on Airwave? Could we make sure AMON profile is configured correctly on all the MDs.

 

Regards,
Vishnu
If my post helped you, don't forget to give kudos ;)
Highlighted
MVP

Re: Since upgrade to 8.5.0.9 Airwave not seeing clients

Prefer amon is not enabled.

Airwave version is 8.2.10

Mm version and MD versions 8.5.0.9

How do I tell if it is using the AMON version on the controller? The default-amp profile shows:

 

Mgmt Config profile "default-amp" (Predefined (changed))
--------------------------------------------------------
Parameter                           Value
---------                           -----
Stats                               Enabled
Stats_Ext                           Disabled
Generic_amon                        Enabled
Tag                                 Enabled
Sessions                            Enabled
Monitored Info - Add/Update         Disabled
Monitored Info - Deletion           Disabled
Monitored Info - Periodic Snapshot  Disabled
User_visibility                     Enabled
Wireless IDS Event Info             Disabled
Misc                                Enabled
Location                            Enabled
UCC Monitoring                      Disabled
AirGroup Info                       Disabled
Inline DHCP stats                   Enabled
Inline AP stats                     Enabled
Inline Auth stats                   Enabled
Inline DNS stats                    Enabled
WAN State Info                      Disabled       
Inline LLDP stats                   Disabled
AP stats                            Disabled​

 

Highlighted

Re: Since upgrade to 8.5.0.9 Airwave not seeing clients

Thank you for the details scott. Can we try enabling prefer AMON on Airwave and also map the default-amp amon profile on controller to Airwave IP? 

We can first check under Configuration --> System --> Airwave section on the Controller whether Airwave is defined(mostly this should create and map the AMON profile to Airwave IP). Also, make sure the default amp profile is mapped to Airwave IP on the controller.

Regards,
Vishnu
If my post helped you, don't forget to give kudos ;)
Highlighted
MVP

Re: Since upgrade to 8.5.0.9 Airwave not seeing clients

Yes it is configured on the controllers.


How do I tell what the IP is that the profile is mapped too?

 

Thanks

Highlighted
MVP

Re: Since upgrade to 8.5.0.9 Airwave not seeing clients

I have selected now prefer AMON in airwave settings however still the same issue after polling controllers

Highlighted
MVP

Re: Since upgrade to 8.5.0.9 Airwave not seeing clients

Ah found it under the show mgmt-servers and it confirms that it is mapped correctly to the IP of airwave server.

Strange thing is I am getting some clients updating and have been.  But it sitll says there are 4 clients on my controller whenever there is in fact 18.

Highlighted

Re: Since upgrade to 8.5.0.9 Airwave not seeing clients

Hmm so looks like the base settings needed seems to be right. More things TAC have to check enabling debug from CLI.

You could try restarting services on Airwave once if thats not done yet. However, since you already have a TAC ticket raised i will suggest let them find the cause on the same.

 

Regards,
Vishnu
If my post helped you, don't forget to give kudos ;)
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: