Siemens HiPath AP2620 - Enabling SNMP; MIB Support

Availability, mobility, and controller functionality
A31003-W1040-U101-1-7619, July 2006 DRAFT
208 HiPath Wireless Controller, Access Points and Convergence Software V4.0, C10/C100/C1000 User Guide
hwc_controlleravailmobility.fm
Enabling SNMP
8.6 Enabling SNMP
The Controller, Access Points and Convergence Software system supports Simple Network
Management Protocol (SNMP), Version 1 and 2c. SNMP, a set of protocols for managing
complex networks, is used to retrieve HiPath Wireless Controller statistics and configuration
information.
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.
8.6.1 MIB support
The 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
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.
>
The HiPath Wireless Controller is not fully compliant with MIB II. For example, esa/
IXP ports only provide interface statistics.