All MIBs › AVAYA-WLAN-TC-MIB
Organization: Avaya, Inc
Last Updated: 2011-07-23
Category: SNMP Framework, Textual Conventions and Registries, Vendor: Avaya, Wireless and WLAN
Description: Defines textual conventions and common enumerated types shared across Avaya WLAN management MIB modules.
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.
What Is AVAYA-WLAN-TC-MIB?
AVAYA-WLAN-TC-MIB is a vendor-specific Avaya MIB module that defines no monitorable objects of its own but instead supplies the shared textual conventions (TCs) and enumerated types consumed by other Avaya WLAN management MIBs, e.g. AvWlanAPModel/AvWlanAPModelOrNone (AP hardware model identifiers like ap8120/ap8120-E/ap8120-O), AvWlanAPStatus (managed/unknown/standalone/rogue/knownForeign), AvWlanDomainRole (activeMdc/backupMdc/peerWc/standalone for Mobility Domain Controllers), AvWlanRadioChannel/AvWlanRadioPower for radio configuration, and AvWlanConfigSyncComponents (a BITS type enumerating configuration components synced across a mobility domain). Because it defines no OBJECT-TYPEs of its own, it is not something an operator polls directly, but it underpins the semantics of numeric/enumerated values returned by companion MIBs covering AP inventory, radio state, and WIDS/WIPS. It depends on SNMPv2-SMI, SNMPv2-TC, SNMP-FRAMEWORK-MIB, and the Avaya-specific SYNOPTICS-ROOT-MIB OID tree, and is deployed alongside Avaya wireless controllers such as the WC8180 and their associated AP81xx access points. Administrators who need to decode values from other Avaya WLAN MIBs typically keep the AVAYA-WLAN-TC-MIB reference on hand to interpret the enumerations correctly.
IPNetwork Monitor allows you to monitor SNMP objects defined in AVAYA-WLAN-TC-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- Avaya Wireless Controllers (WC8180) and AP8120-series access points
Monitoring Examples
An operator troubleshooting AP status in a companion Avaya WLAN MIB looks up a returned AvWlanAPStatus value against this MIB's enumeration (managed(1), unknown(2), standalone(3), rogue(4), knownForeign(5)) to determine whether an access point appearing in inventory is a legitimate managed AP or a rogue(4) device that should be investigated; a value that doesn't map to a known TC entry would indicate a mismatched or outdated MIB reference version.
What Can Be Monitored
- AP model/status enumerations (read via companion MIBs)
- Mobility Domain Controller role values
- radio channel/power/antenna enumerations
- configuration-sync component bitmask
- WIDS/WIPS operation mode enumerations
Imported Objects
From SNMP-FRAMEWORK-MIB
| SnmpAdminString |
From SNMPv2-SMI
| Integer32 | |
| MODULE-IDENTITY | |
| Unsigned32 |
From SNMPv2-TC
| TEXTUAL-CONVENTION |
From SYNOPTICS-ROOT-MIB
| avayaWlanMibs | OBJECT-IDENTITY |
OIDs
RFC description
Defines WLAN textual conventions and data types for Avaya wireless switch management and configuration.
Start monitoring Avaya WC8180 Wireless Controller / AP8120-series access points (legacy) 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.