XYLANTRAP-13-MIB: View SNMP OID List / Download MIB

A tempAlarm indicates a temperature sensor has changed its state from underThreshold(4) to overThreshold(3).

A moduleChange trap occurs when a module is inserted or removed from the chassis.

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.

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.

A loginViolation trap occurs when a login attempt fails due to an incorrect login-id or password.

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.

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.

A portLinkTrap occurs whenever a phy, log, or virt port is enabled.

A portLinkTrap occurs whenever a phy, log, or virt port is disabled.

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.

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...

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)

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.

A portMove trap occurs when the specified port is moved from a group/vlan or has had its configuration changed.

A moduleResetReload trap occurs when the specified module has been reset or reloaded by the chassis mgr.

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

A vlanRouteTableFull trap occurs when either the IP or IPX route table is full. (discovered on insertion attempt)

A sapTableFull trap occurs when the IPX SAP table is found to be full on insertion.

A atmSSCOPstate trap occurs when the signalling state for the specified physical port changes.

A ilmiState trap occurs when the ILMI state for the specified physical port changes.

A atmConnection trap occurs when the specified ATM Vcc is created or deleted.

A atmService trap occurs when the specified ATM service is created or deleted>

Frame-Relay Dlci Just Created

Frame-Relay Dlci Just Deleted

Frame-Relay Dlci Just Changed to Active

Frame-Relay Dlci Just Changed to InActive

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.

A fddiCFStateChange trap occurs when the specified fddi physical port changes from wrap configuration state.

A duplicateIPaddress trap occurs whenever the switch detects a duplicate IP address.

A duplicateMACaddress trap occurs whenever the switch detects a duplicate MAC address of one of its own router ports.

A healthThresholdRising trap occurs when at least one of the user-specified thresholds is exceeded for the first time.

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.

A healthThresholdDevice trap occurs when at least one device-level threshold crossing is detected.

A healthThresholdModule trap occurs when at least one module-level threshold crossing is detected.

A xylanXIPXMAPPortStatusChange trap occurs when a change in status occurs in an XMAP-tracked virtual port.

A xylanXIPXMAPStateChange trap occurs when XMAP is turned on or off.

The last Authenticated VLAN authentication attempt.

A xylanXIPGMAPFailedUpdate trap occurs when GMAP is unable to update the forwarding database to reflect information in its internal database.

A clkBusLineStateChange trap occurs when 1 of the following occurs at the 8k or the 19m bus line: 1) bus line's status changes (active or inactive) 2) clock switching has occured The following are sent as part of the variable binding: Status code: inactive - 1 active - 2 Bus line: eightKhz - 1 nineteenMhz - 2

A bind-violation trap occurs whenever a binding rule which has been configured gets violated.

A phyPortPartition trap occurs when the device detects link state is active for a physical port, but line errors, or system behaviour, indicate that the cable/media is unuseable. The device will then force the disabling of the port in question and generate this trap. The device will retry using the port in question should a cable drop occur, which may indicate a user has attempted to fix the bad media.

This trap signifies that the switch subagent has detected that the event represented by eventIndex has occurred in the switch.

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 may cause mis-routing in a PNNI network if the port turns out to be an Inside port.

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 may cause mis-routing in a PNNI network.

An alarm indicating that a PNNI filter has denied access to a call attempt. The filter denying the access is identified in the variable.

An alarm indicating that no more Point-to-Multipoint calls may be established until ongoing PMP calls are released due to capacity restrictions of the local fabric.

An alarm indicating that no more calls may be established due to capacity restrictions of the DTL Table.

An alarm indicating that a neighbor on a particular port has ceased communication with this switching system.

An alarm indicating that a PNNI node (instance) within this switching system has been disabled and the reason. If the reason is due to remote action, the IP address causing the action is specified in the trap.

An alarm indicating that a particular port has transitioned from operational state within this switching system.

A healthThresholdPort trap occurs when at least one port-level threshold crossing is detected.

A fddiLerFlagChange trap occurs when the LER flag on a port changes from CLEAR to SET.

A fddiLCTFailCntIncr trap occurs when the LCT flag on a port is incremented.

A statistic overflow trap occurs when a paticular entry of mpcStatisticsTable reach the threshold value, the paticular statistics is identified by statisticsNum of trap data which is the entry index of the mpcStatisticsTable. The current threshold valye is hard coded to 2024. The Trap PDU data format: struct { unsigned int mpcIndex; Index of MPC unsigned int statisticsNum; Entry Index of mpcStatisticsTable unsigned long statisticsThreshold; Trap Threshold Value of Entry unsigned long statisticsValue; Current Statistics Value of Entry } where statisticsNum, statisticsThreshold and statisticsValue entry attached with objecid mpcStatRxMpoaResolveReplyInsufECResources

A shortcut trap occurs when the shortcut path established, closed or failed to complete path. event type: 01 shortcut established 02 shortcut closed 03 failed to complete path The Trap PDU data format: struct { unsigned int event_type; unsigned int vcNumber; VCI number of destination unsigned int prototype; 1: IP, 11: IPX unsigned char destNet_addr[10]; IP or IPX address of destination unsigned char destAtm_addr[20]; ATM address of destination unsigned int mpcIndex; Index of MPC unsigned int mpsIndex; Index of MPS }

A ingress retry timeout trap occurs when the retry time exceed the MPC-p5 time. The Trap PDU data format: struct { unsigned int mpcIndex; Index of MPC unsigned int max_timeout_sec; Timeout value in second unsigned char destNet_addr[10]; IP or IPX address of destination unsigned char destAtm_addr[20]; ATM address of destination unsigned int prototype; 1: IP, 11: IPX unsigned int mpsIndex; Index of MPS }

This trap signifies that the specified connection is in VC-AIS state.

This trap signifies that the specified connection is in VC-RDI state.

This trap signifies that the specified connection is in VC-LOC state.

This trap signifies that the specified connection is unsuccessful Loopback state.

This trap signifies that the specified VP connection is in VP-AIS state.

This trap signifies that the specified VP connection is in VP-RDI state.

This trap signifies that the specified VP connection is in VP-LOC state.

This trap signifies that the specified VP connection is in Unsuccessful loopback state.

A LDP peer is identified by LDP Hello mechanism and peer entry is created.

A LDP peer is lost and peer entry is deleted.

A LDP session with the peer is established and a session entry is created.

A LDP session with the peer is lost and session entry is deleted.

An account event is generated to signal that a new accounting file is available on the switch.

This event is generated when the filling level exceeds the first threshold. This event is for information only, and signals that accounting data are accumulating on the switch.

This event is generated when the filling level goes below the first threshold. This event is for information only.

This alarm is generated when the filling level exceeds the second threshold. It signals that the switch changes over to the alternate collection device.

This event is generated when the filling level is lowering below the second threshold.

This event is generated when the filling level exceeds the third threshold. It signals that the switch is now in congestion.

This event is generated when the filling level is lowering below the third threshold.

This alarm is generated when the TCP connection establishment fails with both the primary and the secondary collection devices.

This alarm is generated when too many files are awaiting collection.

When a Lec status changes, a trap message will be send out to a network manager, the trap packet has the data format: struct { unsigned int lec_id; unsigned char elan_name[33]; unsigned char atm_addr[20]; unsigned int slot_number; unsigned int port_number; unsigned int service_number; unsigned int new_state; unsigned int pre_state; unsigned int reason_of_change; }

A fantrayEvent trap occurs when a problem condition is recognized on a chassis fan tray.

This trap is generated when there is any of the following AIS types of errors on Sonet PMC SONET_LINK_RX_AIS, SEC_LINE_AIS, SEC_PATH_AIS.

This trap is generated when there is any of the following RDI types of errors on Sonet SONET_LINK_RX_RDI, SEC_LINE_RDI, SEC_PATH_RDI.