MERU-CONFIG-ICR-MIB

Description: Manages Inter-Controller Roaming (ICR) settings on Meru Networks WLAN systems.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

MERU-CONFIG-ICR-MIB is a Meru Networks vendor MIB for configuring Inter-Controller Roaming (ICR), the mechanism that lets wireless clients roam seamlessly between access points managed by different Meru WLAN controllers. It exposes configuration data defining roaming relationships/peer settings between controllers rather than traffic or environmental data. It supports monitoring of the software/configuration status of the roaming feature, such as confirming ICR is correctly configured and active between controller pairs, which is important for diagnosing failed or delayed client roams across controller boundaries. It depends on the broader Meru controller-based WLAN architecture and is used alongside other Meru configuration MIBs rather than an IETF standard. It is typically deployed in multi-controller enterprise Meru WLAN deployments spanning large campuses or multi-building sites. Network engineers evaluating or troubleshooting this functionality can download the MERU-CONFIG-ICR-MIB file directly to load it into their MIB browser.

No specific object or table names were available in the source excerpt, but an administrator would typically use this MIB to confirm that inter-controller roaming is enabled and correctly paired between two Meru controllers, checking it after a report of clients dropping connectivity when moving between buildings served by different controllers.

Meru Networks MIB module for configuring Inter-Controller Roaming (ICR) features on Meru wireless LAN infrastructure controllers, supporting seamless roaming between access points.