MERU-SMI

Defines the enterprise OID structure and SMI root for Meru Networks MIB modules.

This is the Structure-of-Management-Information (SMI) module defining the Meru Networks enterprise OID tree under which all other Meru MIB modules (WLAN controller and access point MIBs) are registered, in the enterprise wireless networking technology area. It does not itself expose monitorable runtime data; instead it defines registration branches such as meru-reg, meru-wlan, and meru-modules, plus product-identity OIDs like mc500, mc1000, and mc1100 controller model families. As a pure naming/registration module it has no direct role in hardware or software status monitoring; that function is performed by other Meru MIBs (station config, VLAN config, etc.) registered beneath it. Every other Meru-specific MIB depends on the OID arcs this module defines, making it foundational to the vendor's entire MIB tree. It is present in any environment running Meru Networks WLAN controllers/access points, as the root MIB that must be loaded before other Meru MIBs. Every Meru controller, access point, and configuration object ultimately resolves to a MERU-SMI OID beneath the meru-reg arc, making this module the indispensable root for compiling any Meru device MIB.

This is a structural/registration MIB (an SMI module defining the OID tree) rather than one exposing runtime data objects, so there is no monitoring scenario to describe. mc500, mc1000, and mc1100 are product-identity OIDs used to identify controller hardware models in traps/objects defined elsewhere, not counters or status values themselves.

Meru Networks enterprise root SMI for Meru wireless LAN infrastructure and mobility management systems.