Controller-less WLANs

Does Instant AP support SNMP GET functionality? How to configure and troubleshoot?

by on ‎07-04-2014 03:52 PM

This article will have a focus on configuring and troubleshooting SNMP GET functionality on the Aruba Instant™ Access Points running Aruba Instant™ 6.2.1.0-3.3.0.0 Software.

Aruba Instant™ 6.2.1.0-3.3.0.0 Software supports SNMP versions v1, v2c and v3 with support for GET functionality (GET, GET NEXT, GET BULK, and WALK)  and SNMP SET functionality is not yet supported on Aruba Instant™ 6.2.1.0-3.3.0.0 Software

Unlike the previous versions that support SNMP only on Virtual Controller, Aruba Instant™ 6.2.1.0-3.3.0.0 Software allows both VC and slaves to access the tables individually.

 

The configuration and verification steps mentioned in this article are tested on IAP 135 running 6.2.1.0-3.3.0.0.

 

Environment : This article applies to all the IAPs running a minimum OS version of 6.2.1.0-3.3.0.0.

 

Procedure for configuring SNMPv1, SNMPv2, and SNMPv3 community strings using Instant UI

To create community strings for SNMPv1 and SNMPv2 using Instant UI


1. Click System link at the top right corner of the Instant main window.The system window is displayed.
2. Click the Monitoring tab. The following figure shows the SNMP configuration parameters displayed in the Monitoring tab.

 

 

 

3. Click New in the Community Strings for SNMPV1 and SNMPV2 box.
4. Enter the string in the New Community String text box.
5. Click OK.
6. To delete a community string, select the string, and click Delete.

Creating community strings for SNMPv3 Using Instant UI

1. Click System link at the top right corner of the Instant main window. The system window is displayed.
2. Click the Monitoring tab. The SNMP configuration parameters displayed in the Monitoring tab.
3. Click New in the Users for SNMPV3 box.

A window for specifying SNMPv3 user information is displayed.

 

rtaImage (1).png

4. Enter the name of the user in the Name text box.
5. Select the type of authentication protocol from the Auth protocol drop-down list.
6. Enter the authentication password in the Password text box and retype the password in the Retype text box.
7. Select the type of privacy protocol from the Privacy protocol drop-down list.
8. Enter the privacy protocol password in the Password text box and retype the password in the Retype text box.
9. Click OK.
10. To edit the details for a particular user, select the user and click Edit.
11. To delete a particular user, select the user and click Delete.
 
Configuring SNMP Community Strings in the CLI


To configure an SNMP engine ID and host:
(Instant Access Point)(config)# snmp-server engine-id <engine-ID>
(Instant Access Point)(config)# host <ipaddr> version {1 <name> udp-port <port>}|{2c|3 <name> [inform] [udp-port <port>]}


To configure SNMPv1 and SNMPv2 community strings:

(Instant Access Point)(config)# snmp-server community <password>

To configure SNMPv3 community strings:

(Instant Access Point)(config)# snmp-server user <name> <auth-protocol> <password> <privacyprotocol> <password>

 

To view SNMP configuration:

(Instant Access Point)# show snmp-configuration

 

Engine ID:D8C7C8C44298
Community Strings
 -----------------
 Name
  ----
  test

 

 SNMPv3 Users
  ------------
   Name                 AuthenticationType    Encryption Type
    ----                    -------------------     --------------- 
  snmpv3 test                MD5                       DES

 

 SNMP Trap Hosts
  ---------------
  IP Address     Version     Name    Port    Inform
   ----------       -------      ----      ----    ------
   10.1.1.1           v2c        test      162     Yes      

 

Verify if the IP address of the managed device is reachable. With SNMP the underlying network must be functional. If the managed device doesn't 
   respond to a ping, then SNMP will certainly not work.

 

- Make sure you are using the correct community string. Community strings are like passwords to SNMP. If the wrong community string is used, the
   SNMP agent within the device will not process your request.

 

- Ensure ports (UDP port 161 for SNMP, UDP port 162 for recall traps) are open on firewalls.

 

- Use Wireshark or TCPDump traces for response and malformed packet issues; filter on IP address and port.
 

 

Packet capture of a SNMP Get Response packet
 
rtaImage (2).png
 

 

 

 

Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.