User's Manual

hwc_controlleravailmobility.fm
Availability, mobility, and controller functionality
Enabling SNMP
A31003-W1050-U100-2-7619,
March 2008
HiPath Wireless Controller, Access Points and Convergence Software V5 R1 , C20/C2400 User Guide 271
SNMP sends messages, called protocol data units (PDUs), to different parts of a
network. Devices on the network that are SNMP-compliant, called agents, store
data about themselves in Management Information Bases (MIBs) and return this
data to the SNMP requesters.
Note: In this current release (V5 R1), the SNMP protocol does not support the
Wireless 802.11n AP since some of the Wireless 802.11n AP properties are not
accurately reported.
7.6.1 MIB support
The HiPath Wireless Controller, Access Points and Convergence Software
system accepts SNMP Get commands and generates Trap messages. Support
is provided for the retrieval information from the router MIB-II (SNMP_GET) as
well as SNMP traps. The supported MIBs include:
• SNMPv2-MIB
• IF-MIB
• IEEE802dot11-MIB
• RFC1213-MIB
Note: The HiPath Wireless Controller is not fully compliant with MIB II. For
example, esa/IXP ports only provide interface statistics.
The Siemens Enterprise MIB includes:
• HIPATH-WIRELESS-HWC-MIB
• HIPATH-WIRELESS-PRODUCTS-MIB
• HIPATH-WIRELESS-SMI.my
• HIPATH-WIRELESS-DOT11-EXTNS-MIB
• HIPATH-WIRELESS-BRANCH-OFFICE-MIB
The MIB is provided for compilation into an external NMS. No support has been
provided for automatic device discovery by an external NMS.
The HiPath Wireless Controller is the only point of SNMP access for the entire
system. In effect, the HiPath Wireless Controller proxies sets, gets, and alarms
from the associated Wireless APs.