This document contains proprietary information, which is
protected by copyright. No part of this document may be
photocopied, reproduced, or translated into another language
without the prior written consent of Hewlett-Packard.
Publication Number
5998-3758
March 2013
Applicable Products
See Products covered on page 1-2
Trademark Credits
Windows NT®, Windows®, and MS Windows® are US
registered trademarks of Microsoft Corporation.
Disclaimer
HEWLETT-PACKARD COMPANY MAKES NO WARRANTY OF
ANY KIND WITH REGARD TO THIS MATERIAL, INCLUDING,
BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. Hewlett-Packard shall not be liable for errors
contained herein or for incidental or consequential damages in
connection with the furnishing, performance, or use of this
material.
The only warranties for HP products and services are set forth
in the express warranty statements accompanying such
products and services. Nothing herein should be construed as
constituting an additional warranty. HP shall not be liable for
technical or editorial errors or omissions contained herein.
Hewlett-Packard assumes no responsibility for the use or
reliability of its software on equipment that is not furnished by
Hewlett-Packard.
Hewlett-Packard Company
8000 Foothills Boulevard
Roseville, California 95747
www.hp.com/go/networking/
Contents
1 Introduction
About this guide ...........................................................................................................1-2
This guide provides an overview of the HP SNMP implementation and detailed information
on all supported MIB objects.
Products covered
This guide applies to the following MSM7xx Controller products:
ModelPart
MSM710 Access ControllerJ9328A
MSM710 Mobility ControllerJ9325A
MSM720 Access ControllerJ9693A
MSM720 Mobility ControllerJ9694A
MSM760 Access ControllerJ9421A
MSM760 Premium Mobility ControllerJ9420A
MSM765zl Premium Mobility ControllerJ9370A
This guide provides controlled-mode information for the following MSM3xx and MSM4xx
Access Points:
ModelWWAmericasUSAJapanIsrael
MSM430J9651AJ9650AJ9652AJ9653A
MSM460J9591AJ9590AJ9589AJ9618A
MSM466J9622AJ9621AJ9620AJ9619A
MSM466-RJ9716AJ9715AJ9717AJ9718A
MSM410J9427A/BJ9426A/BJ9529A/BJ9616A
MSM422J9359A/BJ9358A/BJ9530A/BJ9617A
MSM310J9379A/BJ9374A/BJ9524A/B
MSM310-R J9383A/BJ9380A/B
MSM317J9423AJ9422A
1-2
MSM320J9364A/BJ9360A/BJ9527A/B
MSM320-RJ9368A/BJ9365A/BJ9528A/B
MSM325J9373A/BJ9369A/B
MSM335J9357A/BJ9356A/B
“WW” identifies worldwide regions not otherwise explicitly named.
Note All references to the MSM320 also apply to the MSM325.
All references to the MSM466 also apply to the MSM466-R.
Important terms
The following terms are used in this guide.
TermDescription
Introduction
About this guide
AP
MSM AP
controller,
MSM Controller
local mesh
WDS
wireless links
VSC
Virtual AP
VAP
Conventions
Command syntax
These terms are used interchangeably to refer to any HP
MSM3xx or MSM4xx Access Point, or the MSM317 Access
Device.
Non-HP access points are identified as third-party APs. These
APs do not support controlled mode operation.
These terms are used interchangeably to refer to any
HP MSM7xx Controller, including both Access Controller and
Mobility Controller variants.
These terms are used interchangeably to refer to the local mesh
feature.
These terms are used interchangeably to refer to a
VSC (Virtual Service Community).
Command syntax is formatted in a monospaced font as follows:
ExampleDescription
use-access-list
ip_address
ssl-certificate=URL [%s]
(ONE | TWO)
Command name. Specify it as shown.
Items in italics are parameters for which you must
supply a value.
Items enclosed in square brackets are optional. You
can either include them or not. Do not include the
brackets. In this example you can either include the
“%s” or omit it.
Items separated by a vertical line indicate a choice.
Specify only one of the items. Do not include the
vertical line.
1-3
Introduction
HP Networking support
Management tool
This guide uses specific syntax when directing you to interact with the management tool user
interface. Key user-interface elements are identified as follows.
On APs:
Example directions in this guideWhat to do in the user interface
Select Wireless > Local Mesh.On the main menu select Wireless and then
select Local mesh on the sub-menu.
For Password, specify secret22.In the field Password enter the text secret22
exactly as shown.
On Controllers
Example directions in this guideWhat to do in the user interface
Select Controller >> Security > Firewall.In the Network Tree select the Controller element, then on the
main menu select Security, and then select Firewall on the
sub-menu. All elements to the left of the double angle brackets
>> are found in the Network Tree.
For Password specify secret22.In the Password field enter the text secret22 exactly as
Expand the Controller branch (select its + symbol), expand
the VSCs branch, select a [VSC-name], then select
Configuration on the main menu.
shown.
HP Networking support
For support information, visit www.hp.com/networking/support. Additionally, your HP-
authorized networking products reseller can provide you with assistance.
Before contacting support
To make the support process most efficient, before calling your networking dealer or HP
Support, you first should collect the following information:
Collect this informationWhere to find it
Product identification.On the rear of the product.
1-4
Software version.The management tool Login page.
Network topology map, including the
addresses assigned to all relevant devices.
Your network administrator.
Online documentation
You can download documentation from the HP Support Website at:
www.hp.com/support/manuals.
Search by product name or part number.
Introduction
Online documentation
1-5
Introduction
Configuring SNMP options
Configuring SNMP options
SNMP options are configured as follows:
By default, the SNMP agent is enabled (SNMP agent configuration in title bar is checked).
If you disable the agent, the device will not respond to SNMP requests. For example:
On an MSM AP, select Management > SNMP.
On an MSM Controller, select Controller >> Management > SNMP.
1-6
(The configuration page for an MSM720 is shown. The configuration pages on other
controllers and on APs are identical except for the Active interfaces table, which shows only
the interfaces available on each specific model.)
Introduction
Configuring SNMP options
The following sections use the term device to refer to any MSM Controller or MSM AP.
Attributes
System name
Specify a name to identify the controller. By default, this is set to the serial number of the
controller.
Location
Specify a descriptive name for the location where the controller is installed.
Contact
Contact information for the controller.
Port
Specify the UDP port and protocol the controller uses to respond to SNMP requests. Default
port is 161.
SNMP protocol
Select the SNMP versions that the controller will support. Default is Versio n 1 and Version
2c.
Notifications
Select the SNMP versions that the AP will support. Default is Vers ion 1 and Versi o n 2c.
Notifications
When this feature is enabled, the controller sends notifications to the hosts that appear in the
Notifications receivers list.
The controller supports the following MIB II notifications:
coldStart
linkUp
linkDown
authenticationFailure
In addition, the controller supports a number of custom notifications. Select Configure
Notifications. For a descriptions of these notifications, see the online help.
v1/v2 communities
Community name
Specify the password, also known as the read/write name, that controls read/write access to
the SNMP agent. A network management program must supply this name when attempting to
set or get SNMP information from the controller. By default, this is set to private.
Read-only name
This is the password that controls read-only access to the SNMP agent. A network
management program must supply this name when attempting to get SNMP information from
the controller. By default, this is set to public.
1-7
Introduction
Configuring SNMP options
v3 users
This table lists all defined SNMP v3 users. To add a new user, select Add New User. Up to
five users are supported. To edit a user, select its link in the Username column.
Username
The SNMP v3 username.
Security
Security protocol defined for the user. Authentication type and encryption type are separated
by a slash. For example, MD5/DES indicates MD5 authentication and DES encryption.
Access level
Type of access assigned to the user:
Notification receivers
This table lists all defined SNMP notification receivers. SNMP notifications are sent to all
receivers in this list. To add a new receiver, select Add New Receiver. Up to five receivers
are supported. To edit a receiver, select its link in the Host column.
Read-only: The user has read and notify access to all MIB objects.
Read-write: The user has read, write, and notify access to all MIB objects.
Host
The domain name or IP address of the SNMP notifications receiver to which the controller
will send notifications.
UDP port
The port on which the controller will send notifications.
Versi o n
The SNMP version (1, 2c, 3) for which this receiver is configured.
Community/Username
For SNMP v1 and v2c, the SNMP Community name of the receiver.
For SNMP v3, the SNMP v3 Username of the receiver.
Security
Use these settings to control access to the SNMP interface.
Allowed addresses: List of IP address from which access to the SNMP interface is
permitted. To add an entry, specify the IP address and appropriate Mask, and then
select Add.
When the list is empty, access is permitted from any IP address.
1-8
Active interfaces: Enable the checkboxes that correspond to the interfaces from which
to allow access to the SNMP agent. Use Ctrl-click to select multiple objects.
Introduction
Standard MIBs
Standard MIBs
Standard MIB II objects are supported as follows:
MIBMSM ControllersMSM APs
IEEE8021-PAE-MIB✓✓
RADIUS-AUTH-CLIENT-MIB✓-
RADIUS-ACC-CLIENT-MIB✓-
RADIUS-AUTH-SERVER-MIB✓-
IF-MIB✓✓
BRIDGE-MIB-✓
IP-MIB✓✓
TCP-MIB✓✓
UDP-MIB✓✓
SNMPV2-MIB✓✓
SNMP-FRAMEWORK-MIB ✓✓
SFLOW-MIB5✓✓
LLDP-EXT-DOT3-MIB✓✓
(controlled mode only)
LLDP-MIB✓✓
(controlled mode only)
The following restrictions apply to the support of standard MIBs:
GroupOIDSupport
IEEE8021-PAEdot1xPaePortInitializeRead-Only
dot1xAuthAdminControlledDirections
dot1xAuthAuthControlledPortControl
1-9
Introduction
Standard MIBs
GroupOIDSupport
IFifAdminStatus (up=1, down=2)Read-Write
ifLastChangeNot
ifInUnknownProtos
ifInNUcastPkts
ifOutNUcastPkts
ifInMulticastPkts (Always = 0)
ifInBroadcastPkts (Always = 0)
ifOutMulticastPkts (Always = 0)
ifOutBroadcastPkts (Always = 0)
ifHCInUcastPkts (Always = 0)
ifHCInMulticastPkts (Always = 0)
Supported
ifHCInBroadcastPkts (Always = 0)
ifHCOutUcastPkts (Always = 0)
ifHCOutMulticastPkts (Always = 0)
ifHCOutBroadcastPkts (Always = 0)
ifLinkUpDownTrapEnable (Always = 0)
ifPromiscuousModeRead only
ifAlias
ifStackStatusNot
ifTestId
supported
ifTestStatus
ifTes tType
ifTestResult
ifTestCode
ifTestOwner
ifTableLastChange
1-10
ifStackLastChange
ifRcvAddressStatus
ifRcvAddressType
Introduction
Enterprise MIBs
GroupOIDSupport
IPipForwardingRead-Only
ipDefaultTTL
ipAdEntReasmMaxSize
ipNetToMediaIfIndex
ipNetToMediaPhysAddress
ipNetToMediaNetAddress
ipNetToMediaType
NoteSome objects marked Not Supported do return a value, but the value is always zero.
Enterprise MIBs
NoteFor this release, Colubris-named Enterprise MIBs are still used. They apply to the HP MSM
products.
Enterprise MIBs report important status and statistical information that is specific to HP
MSM products. Several notifications are defined to report major events. For MIB download
and installation instructions, see Installing the MIBs on page 2-3.
2. Extract the contents of the zip file to a folder named c:\net-snmp. This results in the
following directory structure:
Create MIB-related environment variables as follows (example provided for Windows XP).
3.
4. Right-click My Computer and select Properties > Advanced > Environment
Varia b l es.
5. Under User variables, select New.
2-2
6. Specify the following and then select OK.
Variable Name: MIBDIRS
Variable Value: c:\net-snmp\usr\mibs
7. In the System variables box, select Path and then select Edit.
8. Append the following to the end of the existing path and select OK.
;c:\net-snmp\usr\bin;
MIB examples
Installing the MIBs
9. Select OK.
Installing the MIBs
The MIBs that you use must match the software version that is installed on your hardware.
Using older MIBs may result in some SNMP MIB objects not being found.
An MSM MIBs zip file is available at www.hp.com/networking/mibs. Look for the file
corresponding to your MSM software version.
NoteThe same MIB package applies to ALL products running the SAME firmware.
Use the following steps to install the MIBs.
1. Download the appropriate MIB file.
2. Extract the files from the MIBs zip file to the c:\net-snmp\usr\mibs folder, which already
has some standard MIBs in it. Verify that the MIBs were added to this folder.
SNMP examples
This section contains examples to shown you how to use the Net-snmp tool to “browse” the
MIBs and “walk”, “get,” or “set” values.
2-3
MIB examples
SNMP examples
Commands
Look in the c:\net-snmp\bin folder for the various executables that you can use. The
examples in this section use the following commands:
snmpwalk: Walks through the MIB tree from a specified OID (along the branch).
snmpget: Gets the value requested for a specified OID object
snmpset: Sets a value to a specified OID object (must be a Read-Write OID).
NoteChapter 3: MIB descriptions provides a read-write, read-only, or not-accessible designation
for each MIB object.
The following table shows you some options that you can specify with these commands.
Option or switchDescription
-v 2cIndicates that “snmp version 2c", should always be specified when
using the MIBs.
-cUsed to specify the community string on the HP product (by default,
this is set to public).
-m ALLIndicates that you want to use or refer to ALL the MIBs located at
$MIBDIRS.
-M pathAllows you to specify another location for your MIBs.
-OsCauses the SNMP response to only show the OID name and not the
whole path.
-OnCauses the SNMP response to show the OID numeric value, not the
descriptive name.
iInteger switch used to indicate whether the following value will be a
"1" or a "0".
oString switch used to indicate whether the following value will be a
string.
uNumeric switch used to indicate whether the following value will be
a numeric.
2-4
MIB examples
SNMP examples
Using snmpwalk
1. The snmpwalk command allows you to list all of the OID objects that are possible:
snmpwalk -v 2c -c public -m all -Os 192.168.1.1 iso
You can optionally collect the results into a file for easier review. You can save
this file and use it as a guide of the Colubris OID objects.
snmpwalk -v 2c -c public -m all -Os 192.168.1.1 iso > snmp.txt
You can also specify a lower starting point on the snmp tree instead of the top,
(iso):
snmpwalk -v 2c -c public -m all -Os 192.168.1.1 certificateExpiryDate
2. You can display the numeric equivalent for an object name:
snmpwalk -v 2c -c public -m all -On 192.168.1.1 certificateExpiryDate
3. Given the object's numeric value, you can retrieve the object's descriptive name:
snmpwalk -v 2c -c public -m all -Os 192.168.1.1 .1.3.6.1.4.1.8744.5.2.1.3.3.0
4. You can override the default MIBDIRS environment value by specifying another MIB
path:
snmpwalk -v 2c -c public -m all -M c:\net-snmp\usr\mibs-build-bbbb -Os 192.168.1.1 iso
Using snmpget
The snmpget command is similar to snmpwalk, except that it retrieves only the value of the
object specified, not the rest of the objects on that branch.
1. This command allows you to list the value for the sysDescr.0 OID object:
snmpget -v 2c -c public -m all -Os 192.168.1.1 sysDescr.0
2. You can optionally collect the results into a file for easier review, (i.e. object.txt):
snmpget -v 2c -c public -m all -Os 192.168.1.1 sysDescr.0 > object.txt
3. This command allows you to list the value for the certificateExpiryDate.0 OID object:
snmpget -v 2c -c public -m all -Os 192.168.1.1 certificateExpiryDate.0
4. To see the numeric equivalent for an object name:
snmpget -v 2c -c public -m all -On 192.168.1.1 certificateExpiryDate.0
5. Given the OID object's numeric value, you can retrieve the object's descriptive name:
snmpget -v 2c -c public -m all -Os 192.168.1.1 .1.3.6.1.4.1.8744.5.2.1.3.3.0
6. You can override the default MIBDIRS environment value by specifying another MIB
path:
snmpget -v 2c -c public -m all -M c:\net-snmp\usr\mibs -Os 192.168.1.1 sysDescr.0
2-5
MIB examples
SNMP examples
Using snmpset
You can also set notifications or assign values to certain R/W OIDs.
1. This command enables a Login notification when a user logs in:
NoteFor this release, Colubris-named Enterprise MIBs are still used. They apply to the HP MSM
products.
Colubris enterprise MIBs are used to report important status and statistics information
specific to Colubris products. Several traps are also defined to reports major events. The
following sections describe the functionality of the Enterprise MIB. In each table, we give the
name of the object, a description and the access rights: read, write, read/write, accessible for
notification or not accessible.
Colubris enterprise MIBs are used to report important status and statistics information
specific to Colubris products. Several traps are also defined to reports major events. The
following sections describe the functionality of the Enterprise MIB. In each table, we give the
name of the object, a description and the access rights: read, write, read/write, accessible for
notification or not accessible.
COLUBRIS-DEVICE-EVENT-MIB
This MIB is used to view the event logs generated by the remote devices connected to the APs
managed by a controller.
COLUBRIS-DEVICE-EVENT-MIB OIDs
coDevEvSuccessfulAssociationNotificationEnabled
.1.3.6.1.4.1.8744.5.26.1.1.1read-write
Specifies if coDeviceEventSuccessfulAssociation notifications are generated.
coDevEvAssociationFailureNotificationEnabled
.1.3.6.1.4.1.8744.5.26.1.1.2read-write
Specifies if coDeviceEventAssociationFailure notifications are generated.
coDevEvSuccessfulReAssociationNotificationEnabled
.1.3.6.1.4.1.8744.5.26.1.1.3read-write
Specifies if coDeviceEventSuccessfulReAssociation notifications are generated.
coDevEvReAssociationFailureNotificationEnabled
.1.3.6.1.4.1.8744.5.26.1.1.4read-write
Specifies if coDeviceEventReAssociationFailure notifications are generated.
Specifies if coDeviceEventSuccessfulDeAuthentication notifications are generated.
coDevEvDeAuthenticationFailureNotificationEnabled
.1.3.6.1.4.1.8744.5.26.1.1.10read-write
Specifies if coDeviceEventDeAuthenticationFailure notifications are generated.
coDeviceEventTable
.1.3.6.1.4.1.8744.5.26.1.2.1not-accessible
The list of devices available in the Event system.
coDeviceEventEntry
.1.3.6.1.4.1.8744.5.26.1.2.1.1not-accessible
An entry in the coDeviceEventTable. coDevDisIndex - Uniquely identify a device in the
MultiService Access Controller. coDevEvIndex - Uniquely identify a device in the Event
system.
coDevEvIndex
.1.3.6.1.4.1.8744.5.26.1.2.1.1.1not-accessible
Specifies the index associated with a device in the Event system.
coDevEvMacAddress
.1.3.6.1.4.1.8744.5.26.1.2.1.1.2read-only
MAC address of the device generating the events.
coDeviceEventDetailTable
.1.3.6.1.4.1.8744.5.26.1.2.2not-accessible
The Event for each devices.
coDeviceEventDetailEntry
.1.3.6.1.4.1.8744.5.26.1.2.2.1not-accessible
An entry in the coDeviceEventDetailTable. coDevDisIndex - Uniquely identifies a device
on the controller.
coDevEvIndex - Uniquely identifies a device in the Event system.
coDevEvLogIndex - Uniquely identifies a log for a specific device in the Event system.
3-4
coDevEvLogIndex
.1.3.6.1.4.1.8744.5.26.1.2.2.1.1not-accessible
Uniquely identifies a log for a specific device in the Event system.
Loading...
+ 134 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.