Monitoring, Management & Location Tracking

 View Only
last person joined: one year ago 

Articles relating to existing and legacy HPE Aruba Networking products and solutions including AirWave, Meridian Apps, ALE, Central / HPE Aruba Networking Central, and UXI / HPE Aruba Networking User Experience Insight

What if SNMPv3 is setup correctly and the controller still does not respond? 

Jul 03, 2014 11:57 PM

Environment : When we have setup SNMPv3 between a controller to be monitored and Airwave, the communication doe snot initiate.

 

The first troubleshooting step would be to perform an snmp v3 walk like the example below.

Working example:
snmpwalk -v 3 -u netadmin_ro -a SHA -x AES -A netadmin_pass3 -X netadmin_pass3 -l authPriv 192.168.17.248 1.3.6.1.4.1.14823.2.2.1.4

WLSX-USER-MIB::wlsxTotalNumOfUsers.0 = Gauge32: 0
WLSX-USER-MIB::wlsxUserSessionTimeCount."campus_alcatel_cp".1 = Counter32: 0
WLSX-USER-MIB::wlsxUserSessionTimeCount."campus_alcatel_cp".5 = Counter32: 0
WLSX-USER-MIB::wlsxUserSessionTimeCount."campus_alcatel_cp".15 = Counter32: 2
WLSX-USER-MIB::wlsxUserSessionTimeCount."campus_alcatel_cp".30 = Counter32: 0
WLSX-USER-MIB::wlsxUserSessionTimeCount."campus_alcatel_cp".60 = Counter32: 0
WLSX-USER-MIB::wlsxUserSessionTimeCount."campus_alcatel_cp".120 = Counter32: 0
WLSX-USER-MIB::wlsxUserSessionTimeCount."campus_alcatel_cp".240 = Counter32: 0
WLSX-USER-MIB::wlsxNumOfUsers8021x.0 = Gauge32: 0
WLSX-USER-MIB::wlsxNumOfUsersVPN.0 = Gauge32: 1
WLSX-USER-MIB::wlsxNumOfUsersCP.0 = Gauge32: 0
WLSX-USER-MIB::wlsxNumOfUsersMAC.0 = Gauge32: 0
WLSX-USER-MIB::wlsxNumOfUsersStateful8021x.0 = Gauge32: 0


If manual snmpv3 walk does not return any information and times out from Airwave CLi. This article will help us find out as to why this is happening.

 

For the controller monitor page on Airwave, the STATUS of the device will show as DOWN and CONFIGURATION will show UNKNOWN or SNMP not working.

 

The cause of issue is essentially the controller configuration not getting updated with the SNMPv3 credentials.
Comparing the  running config files of 2 controllers you can see the following difference.

For the controller where SNMPv3 works.

!
snmp-server user "SNFv3SNMP" auth-prot sha ****** priv-prot aes ****** 
vpdn group pptp
!
 

 

For the controller where does not work.
!
no snmp-server
snmp-server user "SNFv3SNMP" auth-prot sha ****** priv-prot aes ****** 
vpdn group pptp
!
 
To make the SNMPv3 working we need to configure it from the controller CLI

Login to controller CLI

>config t
#snmp-server user <USERNAME> auth-prot sha <PASSWORD> priv-prot aes <PASSWORD>
#write memory

Once executed, the running config gets updated. We also need to poll the controller from its monitor page on Airwave to have the SNMPv3 communication initiated.

 

Statistics
0 Favorited
5 Views
0 Files
0 Shares
0 Downloads

Related Entries and Links

No Related Resource entered.