System®. Dell™, the DELL™ logo, and PowerConnect™ are trademarks of Dell Inc.
All rights reserved. Specifications in this manual are subject to change without notice.
Originated in the USA. All other trademarks are the property of their respective owners.
Open Source Code
Certain Aruba products include Open Source software code developed by third parties, including software code
subject to the GNU General Public License (GPL), GNU Lesser General Public License (LGPL), or other Open
Source Licenses. Includes software from Litech Systems Design. The IF-MAP client library copyright 2011 Infoblox,
Inc. All rights reserved. This product includes software developed by Lars Fenneberg, et al. The Open Source code
used can be found at this site:
http://www.arubanetworks.com/open_source
Legal Notice
The use of Aruba Networks, Inc. switching platforms and software, by all individuals or corporations, to terminate
other vendors’ VPN client devices constitutes complete acceptance of liability by that individual or corporation for
this action and indemnifies, in full, Aruba Networks, Inc. from any and all legal actions that might be taken against it
with respect to infringement of copyright on behalf of those vendors.
>In the command examples, italicized text within angle brackets represents items that you
should replace with information appropriate to your specific situation. For example:
# send <text message>
In this example, you would type “send” at the system prompt exactly as shown, followed by
the text of the message you wish to send. Do not type the angle brackets.
[Optional]
{Item A |
Item B}
Command examples enclosed in brackets are optional. Do not type the brackets.
In the command examples, items within curled braces and separated by a vertical bar
represent the available choices. Enter only one choice. Do not type the braces or bars.
The following informational icons are used throughout this guide:
Indicates helpful suggestions, pertinent information, and important things to remember.
Indicates a risk of damage to your hardware or loss of data.
Indicates a risk of personal injury or death.
What is New in this Release
The version of the document contains the following updates:
Table 2:
New Features in Dell Networking W-Series Instant 6.4.0.2-4.1
FeatureDescription
Sourcing Virtual Controller
traps from Virtual Controller IP
address and sysObjectID
enhancements
In the current release, if the Virtual Controller IP address is configured, the
traps are generated with Virtual Controller IP as the source IP address.
The sysObject ID of systemMIB returns results with iapvc when a query on
the Virtual Controller IP is performed.
Contacting Dell
Table 3:
Support
Main Websitedell.com
Contact Informationdell.com/contactdell
Support Websitedell.com/support
Documentation Website
Support Information
dell.com/support/manuals
21 | About this GuideDell Networking W-Series Instant 6.4.0.2-4.1 | MIBReference Guide
Chapter 2
MIBs Overview
This chapter provides information about Management Information Base (MIBs) supported in Dell Networking WSeries Instant 6.4.0.2-4.1 software release.
MIBs
A MIB is a virtual database that contains information used for network management. Each managed device contains
MIBs that define its properties. A separate MIB is provided for each defined property, such as the group of physical
ports assigned to a VLAN or the statistical data of packets transferred at a specific rate.
MIB objects, such as a MIB table or a specific object in a MIB table, are identified with Object identifiers (OIDs). The
OIDs are designated by text strings and integer sequences. For example,
private enterprise node
Figure 1 illustrates the high-level hierarchy of the Enterprise MIBs.
Figure 1 High-Level MIB Hierarchy
Dell
.
Dell
and 1.3.6.1.4.1.674 both represent the
The hardware MIBs are assigned under the Dell organization code, while all other MIBs are under the Aruba
organization code.
Table 4 indicates the numerical string that lists the nodes of the enterprise MIB hierarchy.
Table 4:
MIB Node Identification - Enterprise Nodes
Name
11OSI
31.3ORG
61.3.6DOD
11.3.6.1Internet
41.3.6.1.4Private
11.3.6.1.4.1Enterprise
6741.3.6.1.4.1.674Dell
The information provided by a MIB is a file that describes network elements with numerical strings. This information
is compiled into readable text by the SNMP manager. For information about reading MIB text files, see Reading MIB
Files on page 26.
SNMP
MIB objects can be accessed through the Simple Network Management Protocol (SNMP). To deliver information
between devices, every object referenced in an SNMP message must be listed in the MIB. A component of a device
that is not described in a MIB cannot be recognized by SNMP as there is no information for SNMP managers and
SNMP agents to exchange.
The significant elements of SNMP are Managers, Agents, and MIBs:
l SNMP Managers (software application) are used for communicating and managing the devices that support
SNMP Agents. SNMP Managers can also be used for sending configuration updates or controlling requests to
manage a network device.
l SNMP Agents (software application) provide information from the network devices to the SNMP Managers.
Network devices include workstations, routers, microwave radios, and other network components.
l MIBs are used for communication between the Managers and the Agents. The OIDs of the MIBs enable the
Managers and Agents to communicate specific data requests and data returns.
Instant MIBs support SNMPv1, SNMPv2, and SNMPv3. For information on configuring SNMP through the Instant
UI, see
Dell Networking W-Series Instant Access Point 6.4.0.2-4.1 User Guide
.
To retrieve information from a MIB, the following information is required:
The latest Instant MIB files are available for registered customers at download.dell-pcw.com.
For assistance to set up an account and access files, contact customer service. See Contacting Dell on page 21.
Reporting WLAN Health
SNMP MIBs are frequently used for running health checks on Dell Networking W-Series Instant devices, through a
MIB browser application.
To retrieve information from a MIB, the following information is required:
l SNMP version
l SNMP community name—
l The IP Address of the Virtual Controller and the slave W-IAPs
l The OID of the MIB value you want to monitor
MIB files can be placed in the appropriate disk location to assist the user in locating desired OID values for
monitoring. For most applications, the
point as shown in the following example:
.1.3.6.1.4.1.674.2.2.1.1.2.1
SNMP Operations on W-IAPs
Although the virtual controller address is configured on management station, the following MIBs are specific to a
particular W-IAP and therefore cannot be accessed from the Virtual Controller.
l ifTable
l ifXTable
l dot1qTpFdbTable
publicorprivate
root
of the MIB must be included in the OID—the OID begins with a decimal
To enable the management station to access the IF-MIB and Q-BRIDGE-MIB tables and W-IAPs to send traps, you
must configure the IP address of each W-IAP on the management station. The management station can
automatically configure the W-IAP details, by obtaining the IP address of each W-IAP from the AP MIB
(aiAccessPointTable), which lists all the slave W-IAPs in a swarm and is implemented on a virtual controller.
You do not have to set the SNMP community string and security parameters on each W-IAP as this configuration
is common to all W-IAPs and is inherited from virtual controller.
The following is an example of snmpget command to obtain information.
Figure 2 shows how information may be obtained through a graphical user interface (GUI). The user interface and the
available features vary by application.
Figure 2 Graphical User Interface
Reading MIB Files
This section describes how to interpret the basic components of a MIB file. To determine the OIDs, view the file
snmp.h. For more information, see SNMP File on page 29.
MIB files describe a specific component of a network device. The files are numerical strings that are converted to
ASCII text by the compiler of the SNMP manager. A word processor or text editor can be used to open the ASCII
file. The contents of an example Dell enterprise MIB file are as follows:
Opening Line
Following is the opening line, the beginning of the MIB file.
AI-AP-MIB DEFINITIONS ::= BEGIN
Imports
The
Imports
IMPORTS
TEXTUAL-CONVENTION
FROM SNMPv2-TC
MODULE-IDENTITY,
OBJECT-TYPE,
snmpModules,
Integer32,
Counter32,
Counter64,
IpAddress,
NOTIFICATION-TYPE
FROM SNMPv2-SMI
section lists the objects that are defined in external ASN.1 files and are used in the current MIB file.
DisplayString,
PhysAddress,
TimeInterval,
RowStatus,
StorageType,
TestAndIncr,
MacAddress,
TruthValue
FROM SNMPv2-TC
OBJECT-GROUP
FROM SNMPv2-CONF
aiEnterpriseMibModules
FROM ARUBA-MIB;
Inheritance
This section shows the vendor of the MIB and the inheritance, and provides an overall description.
A significant part of inheritance is the OID. The entire OID is not listed for each MIB object—instead, the parent of the
object is shown. The OID can be determined from the parent object as follows.
aiEnterpriseMibModules is the parent object —its OID is 1.3.6.1.4.1.14823.2.3.3.
aiStateGroup OBJECT IDENTIFIER ::= { aiMIB 2 }, the OID is 1.3.6.1.4.1.14823.2.3.3.1.2.
aiVirtualControllerKey OBJECT-TYPE, the OID is 1.3.6.1.4.1.14823.2.3.3.1.1.1.0.
All MIBs and their related OIDs are listed in the snmp file. For more information, see SNMP File on page 29.
Identity is the opening description of the MIB. The information includes contact information for the vendor and a
general description of the MIB.
aiMIB MODULE-IDENTITY
LAST-UPDATED "0804160206Z"
ORGANIZATION "Aruba Wireless Networks"
CONTACT-INFO
"Postal: 1322 Crossman Avenue
Sunnyvale, CA 94089
E-mail: dl-support@arubanetworks.com
Phone: +1 408 227 4500"
DESCRIPTION
"This MIB is for managing Dell Networking W-Series Instant WLAN"
REVISION "0804160206Z"
DESCRIPTION
"The initial revision."
::= { aiEnterpriseMibModules 1 }
MIB Modules
MIB objects can be placed in logical groups such as Group and Table. A group typically contains at least one global-
object or table. The table lists the MIB objects that contain the information exchanged.
The first object of a table is an Entry. The OIDs of the subsequent objects of this table are appended increments of
the Entry OID.
The keyword SEQUENCE lists the objects of the table that contain device information. Each subsequent object
(Informative MIB Object) inherits the OID of the Entry, and contains information sorted by the Syntax, Access,
Status, and Description keywords.
Group
aiStateGroup OBJECT IDENTIFIER ::= { aiMIB 2 }
Table
aiAccessPointTable OBJECT-TYPE
SYNTAX SEQUENCE OF AiAccessPointEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This contains all access points connected to the
virtual controller. This table is empty on AP where
virtual controller is not active"
::= { aiStateGroup 1 }
Entry
aiAccessPointEntry OBJECT-TYPE
SYNTAX AiAccessPointEntry
MAX-ACCESS not-accessible
STATUS current
Following is the closing line—the end of the MIBs file.
END
SNMP File
The snmp.h file lists the OIDs of all MIBs. Following are sections from snmp.h that show the complete OID of each
of the Controller Transport Service (CTS) MIB elements. The list starts from the ancestral parent
iso
.
The SNMP file with all Dell MIBs is listed in Standard SNMP MIBs on page 49.
All Instant MIBs inherit their OIDs from the Dell MIB node. The following rows list the MIBs that precede CTS,
starting from