XYLAN-OAM-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › XYLAN-OAM-MIB

Category: Xylan OmniSwitch

Description: Monitors Xylan OmniSwitch ATM OAM cell loopback and fault management flow parameters.

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 XYLAN-OAM-MIB?

XYLAN-OAM-MIB is a vendor-specific MIB from Xylan (later part of Alcatel's OmniSwitch line) that models ATM Operations, Administration and Maintenance (OAM) functionality, specifically loopback cell generation and fault-management flow parameters on ATM virtual circuits. It exposes configuration and status data for OAM loopback tests and fault-detection flows rather than general interface counters. Its primary monitoring value is verifying ATM connection continuity and fault state, effectively a software-level health check of virtual circuit reachability rather than physical hardware sensors like temperature or power. It depends conceptually on the ATM-MIB and ITU-T OAM cell-flow standards (I.610) that define standard ATM OAM behavior, though it is a proprietary extension. It would be deployed on Xylan/Alcatel OmniSwitch ATM switches used in legacy carrier or enterprise ATM backbone networks, and engineers maintaining such gear can download the XYLAN-OAM-MIB file to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in XYLAN-OAM-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

  • Xylan/Alcatel OmniSwitch ATM switch

Monitoring Examples

No object/table names were supplied for this module in the available data, and the source module description is empty, so specific object identifiers cannot be grounded here. In general terms, an administrator would use OAM loopback status objects to detect an ATM PVC/SVC that has stopped responding to end-to-end loopback cells, indicating a broken virtual circuit. Fault-management flow objects would be checked to see whether an alarm indication signal (AIS) or remote defect indication (RDI) condition has been raised on a monitored VC.

What Can Be Monitored

  • ATM OAM loopback cell status
  • virtual circuit fault-management flow state
  • loopback test configuration
  • remote defect/alarm indication state
Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC-1215

TRAP-TYPE

From XYLAN-BASE-MIB

xylanOamArchOBJECT-IDENTITY
OIDs

RFC description

Xylan (now Alcatel) vendor-specific MIB defining OAM (Operations, Administration, and Maintenance) objects for Xylan switching and networking equipment.

Start monitoring Xylan/Alcatel OmniSwitch ATM switch (ATM OAM loopback/fault-detection flow 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.

Download XYLAN-OAM-MIB