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

VENDOR: XYLAN CORP.


 Home MIB: XYLANTRAP-M-MIB
Download as:   
SNMPv2-CONF, XYLAN-VLAN-MIB, FDDI-SMT73-MIB, XYLAN-PORT-MIB, SNMPv2-SMI, XYLAN-MGMTSTN-MIB, XYLAN-BASE-MIB, CHASSIS-MIB, XYLAN-ATM-MIB, XYLAN-IP-MIB, SNMPv2-TC, XYLAN-FRAME-RELAY-MIB, XYLAN-HEALTH-MIB

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 tempAlarmM 1.3.6.1.4.1.800.3.1.1.40.1
A tempAlarm indicates a temperature sensor has changed its state from underThreshold(4) to overThreshold(3).
 moduleChangeM 1.3.6.1.4.1.800.3.1.1.40.2
A moduleChange trap occurs when a module is inserted or removed from the chassis.
 powerEventM 1.3.6.1.4.1.800.3.1.1.40.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.
 controllerEventM 1.3.6.1.4.1.800.3.1.1.40.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.
 loginViolationM 1.3.6.1.4.1.800.3.1.1.40.5
A loginViolation trap occurs when a login attempt fails due to an incorrect login-id or password.
 macVlanViolationM 1.3.6.1.4.1.800.3.1.1.40.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.
 macDuplicatePortM 1.3.6.1.4.1.800.3.1.1.40.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.
 portLinkUpEventM 1.3.6.1.4.1.800.3.1.1.40.8
A portLinkTrap occurs whenever a phy, log, or virt port is enabled.
 portLinkDownEventM 1.3.6.1.4.1.800.3.1.1.40.9
A portLinkTrap occurs whenever a phy, log, or virt port is disabled.
 portPartitionedM 1.3.6.1.4.1.800.3.1.1.40.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.
 portRecordMismatchM 1.3.6.1.4.1.800.3.1.1.40.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...
 groupChangeM 1.3.6.1.4.1.800.3.1.1.40.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)
 vlanChangeM 1.3.6.1.4.1.800.3.1.1.40.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.
 portMoveM 1.3.6.1.4.1.800.3.1.1.40.16
A portMove trap occurs when the specified port is moved from a group/vlan or has had its configuration changed.
 moduleResetReloadM 1.3.6.1.4.1.800.3.1.1.40.17
A moduleResetReload trap occurs when the specified module has been reset or reloaded by the chassis mgr.
 systemEventM 1.3.6.1.4.1.800.3.1.1.40.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
 vlanRouteTableFullM 1.3.6.1.4.1.800.3.1.1.40.19
A vlanRouteTableFull trap occurs when either the IP or IPX route table is full. (discovered on insertion attempt)
 sapTableFullM 1.3.6.1.4.1.800.3.1.1.40.20
A sapTableFull trap occurs when the IPX SAP table is found to be full on insertion.
 atmSSCOPstateM 1.3.6.1.4.1.800.3.1.1.40.21
A atmSSCOPstate trap occurs when the signalling state for the specified physical port changes.
 ilmiStateM 1.3.6.1.4.1.800.3.1.1.40.22
A ilmiState trap occurs when the ILMI state for the specified physical port changes.
 atmConnectionM 1.3.6.1.4.1.800.3.1.1.40.23
A atmConnection trap occurs when the specified ATM Vcc is created or deleted.
 atmServiceM 1.3.6.1.4.1.800.3.1.1.40.24
A atmService trap occurs when the specified ATM service is created or deleted>
 dlciNewM 1.3.6.1.4.1.800.3.1.1.40.27
Frame-Relay Dlci Just Created
 dlciDelM 1.3.6.1.4.1.800.3.1.1.40.28
Frame-Relay Dlci Just Deleted
 dlciUpM 1.3.6.1.4.1.800.3.1.1.40.29
Frame-Relay Dlci Just Changed to Active
 dlciDnM 1.3.6.1.4.1.800.3.1.1.40.30
Frame-Relay Dlci Just Changed to InActive
 portManualForwardingModeM 1.3.6.1.4.1.800.3.1.1.40.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.
 fddiCFStateChangeM 1.3.6.1.4.1.800.3.1.1.40.32
A fddiCFStateChange trap occurs when the specified fddi physical port changes from wrap configuration state.
 duplicateIPaddressM 1.3.6.1.4.1.800.3.1.1.40.35
A duplicateIPaddress trap occurs whenever the switch detects a duplicate IP address.
 duplicateMACaddressM 1.3.6.1.4.1.800.3.1.1.40.36
A duplicateMACaddress trap occurs whenever the switch detects a duplicate MAC address of one of its own router ports.
 healthThresholdRisingM 1.3.6.1.4.1.800.3.1.1.40.37
A healthThresholdRising trap occurs when at least one of the user-specified thresholds is exceeded for the first time.
 healthThresholdFallingM 1.3.6.1.4.1.800.3.1.1.40.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.
 healthThresholdDeviceM 1.3.6.1.4.1.800.3.1.1.40.39
A healthThresholdDevice trap occurs when at least one device-level threshold crossing is detected.
 healthThresholdModuleM 1.3.6.1.4.1.800.3.1.1.40.40
A healthThresholdModule trap occurs when at least one module-level threshold crossing is detected.
 pnniRouteConflictPortM 1.3.6.1.4.1.800.3.1.1.40.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.
 pnniRouteConflictSamePGM 1.3.6.1.4.1.800.3.1.1.40.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.