XYLANTRAP-3-MIB

All MIBs › XYLANTRAP-3-MIB

Category: Xylan OmniSwitch

Description: Defines Xylan OmniSwitch enterprise trap definitions for module 3 hardware and protocol event notifications.

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 XYLANTRAP-3-MIB?

XYLANTRAP-3-MIB is a Xylan-specific notification (trap) module that defines the enterprise SNMP trap catalog for a particular hardware/protocol module (module 3) on OmniSwitch equipment, rather than a table of polled data objects. Its content is entirely fault- and event-oriented: it enumerates the trap PDUs a switch emits for hardware faults, module state changes, and protocol-level events tied to that specific card or subsystem. Its monitoring value is therefore in event-driven fault detection rather than periodic polling -- an NMS trap receiver uses this MIB to decode incoming traps and immediately recognize conditions like module failure, link state changes, or protocol errors as they occur, rather than waiting for the next poll cycle. As an enterprise trap-definitions module it depends on the switch's core hardware/chassis MIB structures to supply the object identifiers referenced in trap varbinds. It is deployed alongside the broader Xylan OmniSwitch MIB set, loaded into trap-management/NMS software so that traps from OmniSwitch chassis module 3 render as human-readable events instead of raw numeric OIDs. Network engineers evaluating or troubleshooting this functionality can download the XYLANTRAP-3-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in XYLANTRAP-3-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 OmniSwitch LAN switch

Monitoring Examples

No sample object names were provided for this module; being a trap-definitions MIB, it does not expose polled runtime counters or tables -- instead, an admin would load it into an SNMP trap receiver so that unsolicited notifications from OmniSwitch module 3 hardware (e.g., a card failure or protocol fault) are decoded and alerted on in real time rather than requiring polling.

Imported Objects

From CHASSIS-MIB

chasControlSlot	OBJECT-TYPE
chasControlState	OBJECT-TYPE
chasModuleOperStatus	OBJECT-TYPE
chasModuleSlot	OBJECT-TYPE
chasModuleSubUnit	OBJECT-TYPE
chasModuleType	OBJECT-TYPE
chasPowerSupply1State	OBJECT-TYPE
chasPowerSupply2State	OBJECT-TYPE

From FDDI-SMT73-MIB

fddimibSMTCFState	OBJECT-TYPE
fddimibSMTIndex	OBJECT-TYPE

From RFC-1215

TRAP-TYPE

From XYLAN-ATM-MIB

atmxPortEnableILMI	OBJECT-TYPE
atmxPortPortIndex	OBJECT-TYPE
atmxPortSlotIndex	OBJECT-TYPE
atmxServiceAdmStatus	OBJECT-TYPE
atmxServiceNumber	OBJECT-TYPE
atmxServicePortIndex	OBJECT-TYPE
atmxServiceSlotIndex	OBJECT-TYPE
atmxVccAdmStatus	OBJECT-TYPE
atmxVccPortIndex	OBJECT-TYPE
atmxVccSlotIndex	OBJECT-TYPE
atmxVccVci	OBJECT-TYPE
atmxVccVpi	OBJECT-TYPE

From XYLAN-BASE-MIB

microSwitch	OBJECT-IDENTITY
omniswitch5	OBJECT-IDENTITY
omniswitch9	OBJECT-IDENTITY
pizzaSwitch	OBJECT-IDENTITY
xylan	OBJECT-IDENTITY
xylanSwitchDevice	OBJECT-IDENTITY

From XYLAN-FRAME-RELAY-MIB

frxVcControlDlci	OBJECT-TYPE
frxVcControlPortIndex	OBJECT-TYPE
frxVcControlSlotIndex	OBJECT-TYPE

From XYLAN-HEALTH-MIB

healthThreshDevTrapData	OBJECT-TYPE
healthThreshModTrapCount	OBJECT-TYPE
healthThreshModTrapData	OBJECT-TYPE

From XYLAN-IP-MIB

xylanIpAssocAddr	OBJECT-TYPE
xylanIpAssocDupIntf	OBJECT-TYPE
xylanIpAssocDupMac	OBJECT-TYPE
xylanIpAssocDupSlot	OBJECT-TYPE
xylanIpAssocIntf	OBJECT-TYPE
xylanIpAssocMac	OBJECT-TYPE
xylanIpAssocSlot	OBJECT-TYPE

From XYLAN-MGMTSTN-MIB

systemEventTrapNumber

OBJECT-TYPE

From XYLAN-PORT-MIB

vportAdmStatus	OBJECT-TYPE
vportFuncType	OBJECT-TYPE
vportFuncTypeInstance	OBJECT-TYPE
vportIF	OBJECT-TYPE
vportSlot	OBJECT-TYPE

From XYLAN-VLAN-MIB

atVLANAdminStatus	OBJECT-TYPE
atVLANGroupId	OBJECT-TYPE
atVLANId	OBJECT-TYPE
vBrdgTpFdbAddress	OBJECT-TYPE
vDupMacIntf	OBJECT-TYPE
vDupMacMac	OBJECT-TYPE
vDupMacSlot	OBJECT-TYPE
vDupMacTime	OBJECT-TYPE
vLanAdmStatus	OBJECT-TYPE
vLanNumber	OBJECT-TYPE

OIDs

OID symbolic	OID numeric	Description
NTF tempAlarm3	1.3.6.1.4.1.800.3.1.1.3.0.1	A tempAlarm indicates a temperature sensor has changed its state from underThreshold(4) to overThreshold(3).
NTF moduleChange3	1.3.6.1.4.1.800.3.1.1.3.0.2	A moduleChange trap occurs when a module is inserted or removed from the chassis.
NTF powerEvent3	1.3.6.1.4.1.800.3.1.1.3.0.3	A powerEvent trap occurs when a power supply is inserted or removed from the chassis, or a problem condition is recognized on a power supply.
NTF controllerEvent3	1.3.6.1.4.1.800.3.1.1.3.0.4	A controlEvent trap occurs when a chassis controller (MPM) loses or gains the state of master(3). If this is due to chassis controller being inserted or removed from the slot, a moduleChange trap will also be sent.
NTF loginViolation3	1.3.6.1.4.1.800.3.1.1.3.0.5	A loginViolation trap occurs when a login attempt fails due to an incorrect login-id or password.
NTF macVlanViolation3	1.3.6.1.4.1.800.3.1.1.3.0.6	A macVlanViolation trap occurs when a frame is received from a port with a VLAN ID different from the VLAN where the frame previously has received.
NTF macDuplicatePort3	1.3.6.1.4.1.800.3.1.1.3.0.7	A macDuplicatePort trap occurs when a frame is received from a source port different from the port where the frame previously has received although they both ports belong to the same VLAN.
NTF portLinkUpEvent3	1.3.6.1.4.1.800.3.1.1.3.0.8	A portLinkTrap occurs whenever a phy, log, or virt port is enabled.
NTF portLinkDownEvent3	1.3.6.1.4.1.800.3.1.1.3.0.9	A portLinkTrap occurs whenever a phy, log, or virt port is disabled.
NTF portPartitioned3	1.3.6.1.4.1.800.3.1.1.3.0.10	A portPartioned trap occurs when the physical port has transitioned thru enable/disable states faster than 10 times in the past second...indicative of a flakey cable.
NTF portRecordMismatch3	1.3.6.1.4.1.800.3.1.1.3.0.11	A portRecordMismatch trap occurs when the specified port data is found to be diferent than the privious configuration. Typically this will be generated when a NIC of one type is swapped out for a DIFFERENT type. IE ethernet for fddi, atm for token-ring, etc...
NTF groupChange3	1.3.6.1.4.1.800.3.1.1.3.0.14	A groupChange trap occurs whenever a group is created or deleted from the system via the UI or SNMP. The group and status code are sent as part of the variable binding. The status codes are: 1 - disable 2 - enable 3 - delete 4 - create 5 - modify (see xylan-vport MIB)
NTF vlanChange3	1.3.6.1.4.1.800.3.1.1.3.0.15	A vlanChange trap occurs whenever a VLAN is created or deleted from the system via the UI or SNMP. The group, vlan and status code are sent as part of the variable binding. See groupChange for the status codes.
NTF portMove3	1.3.6.1.4.1.800.3.1.1.3.0.16	A portMove trap occurs when the specified port is moved from a group/vlan or has had its configuration changed.
NTF moduleResetReload3	1.3.6.1.4.1.800.3.1.1.3.0.17	A moduleResetReload trap occurs when the specified module has been reset or reloaded by the chassis mgr.
NTF systemEvent3	1.3.6.1.4.1.800.3.1.1.3.0.18	A systemEvent trap occurs when a potentially fatal system error occurrs. Such as: out of FLASH/ memory space. The event type is in the var bind. A Descriptive string MAY be present. The following trap numbers are defined (see xylan-trapc.mib): 10 Unspecified log event 11 Log file full 12 Log file erased 20 Unspecified memory event 21 Memory shortage 30 Unsepcified CPU event 31 Long term CPU overload 32 Short term CPU overload 40 Unspecified ffs event 41 Attempt to write to full ffs 42 System/user directed purge 43 Removed imgs/cfgs 44 Exec file removed 45 Config file removed 46 Exec file updated 47 Config file updated 50 Unspecified chassis event 51 Module failed to init 52 Module failed to load 53 Module startup failed 54 Module failed 55 Driver failed
NTF vlanRouteTableFull3	1.3.6.1.4.1.800.3.1.1.3.0.19	A vlanRouteTableFull trap occurs when either the IP or IPX route table is full. (discovered on insertion attempt)
NTF sapTableFull3	1.3.6.1.4.1.800.3.1.1.3.0.20	A sapTableFull trap occurs when the IPX SAP table is found to be full on insertion.
NTF atmSSCOPstate3	1.3.6.1.4.1.800.3.1.1.3.0.21	A atmSSCOPstate trap occurs when the signalling state for the specified physical port changes.
NTF ilmiState3	1.3.6.1.4.1.800.3.1.1.3.0.22	A ilmiState trap occurs when the ILMI state for the specified physical port changes.
NTF atmConnection3	1.3.6.1.4.1.800.3.1.1.3.0.23	A atmConnection trap occurs when the specified ATM Vcc is created or deleted.
NTF atmService3	1.3.6.1.4.1.800.3.1.1.3.0.24	A atmService trap occurs when the specified ATM service is created or deleted>
NTF dlciNew3	1.3.6.1.4.1.800.3.1.1.3.0.27	Frame-Relay Dlci Just Created
NTF dlciDel3	1.3.6.1.4.1.800.3.1.1.3.0.28	Frame-Relay Dlci Just Deleted
NTF dlciUp3	1.3.6.1.4.1.800.3.1.1.3.0.29	Frame-Relay Dlci Just Changed to Active
NTF dlciDn3	1.3.6.1.4.1.800.3.1.1.3.0.30	Frame-Relay Dlci Just Changed to InActive
NTF portManualForwardingMode3	1.3.6.1.4.1.800.3.1.1.3.0.31	A portManualForwardingMode trap occurs when the specified port is placed into manual mode forwarding as its default setting whenever the port is assigned to a Group that is participating in the IBM spanning tree algorithm.
NTF fddiCFStateChange3	1.3.6.1.4.1.800.3.1.1.3.0.32	A fddiCFStateChange trap occurs when the specified fddi physical port changes from wrap configuration state.
NTF duplicateIPaddress3	1.3.6.1.4.1.800.3.1.1.3.0.35	A duplicateIPaddress trap occurs whenever the switch detects a duplicate IP address.
NTF duplicateMACaddress3	1.3.6.1.4.1.800.3.1.1.3.0.36	A duplicateMACaddress trap occurs whenever the switch detects a duplicate MAC address of one of its own router ports.
NTF healthThresholdRising3	1.3.6.1.4.1.800.3.1.1.3.0.37	A healthThresholdRising trap occurs when at least one of the user-specified thresholds is exceeded for the first time.
NTF healthThresholdFalling3	1.3.6.1.4.1.800.3.1.1.3.0.38	A healthThresholdFalling trap occurs when at least one of the user-specified thresholds was exceeded during the previous cycle and none of them are exceeded this cycle.
NTF healthThresholdDevice3	1.3.6.1.4.1.800.3.1.1.3.0.39	A healthThresholdDevice trap occurs when at least one device-level threshold crossing is detected.
NTF healthThresholdModule3	1.3.6.1.4.1.800.3.1.1.3.0.40	A healthThresholdModule trap occurs when at least one module-level threshold crossing is detected.
NTF pnniRouteConflictPort3	1.3.6.1.4.1.800.3.1.1.3.0.50	This trap occurs when PNNI detects that a static route on the pnnixIfPortId port has been created and this port has been configured as a PNNI port. This is something that may cause misrouting in a PNNI network if the port turns out to be an Inside port.
NTF pnniRouteConflictSamePG3	1.3.6.1.4.1.800.3.1.1.3.0.51	This trap occurs when PNNI detects that a static route on the pnnixIfPortId port has been created and this route matches (a prefix of) the Peer Group ID. This is something that may cause misrouting in a PNNI network.

RFC description

Provides enterprise-specific trap definitions for Xylan Pizza Switch and Micro Switch network equipment.

Start monitoring Xylan OmniSwitch LAN switch (module-3 hardware/protocol trap-notification definitions, no polled data) 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 XYLANTRAP-3-MIB

What Is XYLANTRAP-3-MIB?

Supported Devices

Monitoring Examples

This MIB depends on

Related MIBs

RFC description