ITOUCH-TRAP-MIB: View SNMP OID List / Download MIB

VENDOR: MRV COMMUNICATIONS


 Home MIB: ITOUCH-TRAP-MIB
Download as:   

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
     resourceLacks 1.3.6.1.2.1.1.20.9
Indication that the system incremented the corresponding value of resLacks. The variable is resType FROM ITOUCH-SYSTEM-MIB.
     repeaterRedundancy 1.3.6.1.2.1.1.20.12
A new path becomes active within a redundancy group. The variables are repeaterRedundancyGroupGroupIndex, repeaterRedundancyGroupOperPath FROM ITOUCH-REPEATER-MIB.
     accessViolated 1.3.6.1.2.1.1.20.14
Access violation by connected system with Ethernet address not allowed by repeaterPortAccessTable and repeaterPortAccessAction. The variable is repeaterPortIndex FROM ITOUCH-REPEATER-MIB.
     portIntegrityLoss 1.3.6.1.2.1.1.20.15
This port has lost link integrity. The variables are repeaterPortIndex, repeaterPortGroupIndex FROM ITOUCH-REPEATER-MIB.
     iTouchRmonAlarm 1.3.6.1.2.1.1.20.17
The SNMP trap that is generated when xRmonTrapType is set to iTouchFormat(2). These traps, like the RMON standardFormat(1) traps, occur when an alarm variable crosses its rising or falling threshold and generates an event configured to send SNMP traps. The format of the DisplayString embodied by the trap PDU is identical to that of mbLogDescription. The actual object identifier is not significant. The variable is mbLogDescription FROM ITOUCH-RMON-MIB.
     memoryCardSlotChange 1.3.6.1.2.1.1.20.18
Indication that the card has been added or removed. The deviceIndex from ITOUCH-BOOT-SERVER-MIB may be included as a variable in the trap.
     lb2ChassisCardSlotChange 1.3.6.1.2.1.1.20.19
Indication that the card has been added or removed. The variable is slotIndex FROM ITOUCH-CHASSIS-MIB.
     circuitDialTime 1.3.6.1.2.1.1.20.20
Indication that a dialed circuit has reached a threshhold for the maximum number of minutes that a dialed call may remain active. The variable is ifIndex FROM RFC1213-MIB.
     circuitPerDialTime 1.3.6.1.2.1.1.20.21
Indication that a dialed circuit has reached a threshhold for the maximum number of minutes that a circuit may be active with dialed calls within a given period. The variable is ifIndex FROM RFC1213-MIB.
     circuitPerDialAttempt 1.3.6.1.2.1.1.20.22
Indication that a dialed circuit has reached a threshhold for the maximum number of dial attempts that a circuit may make for a given period. The variable is ifIndex FROM RFC1213-MIB.
     fddiPcmStatusChange 1.3.6.1.2.1.1.20.23
A fddi port status has changed. The variable is fddimibPORTPCMState FROM FDDI-SMT73-MIB.
     fddiSMTCFStateFailure 1.3.6.1.2.1.1.20.26
A fddi station detects that the link is disabled or broken. The variable is fddimibSMTCFState FROM FDDI-SMT73-MIB.
     sysLoginAuthenticationFailed 1.3.6.1.2.1.1.20.28
Indicates when and where a user attempted and failed to access the system. The variables are sysLoginAuthFailureTrapType, sysLoginAuthTrapIdentity FROM ITOUCH-SYSTEM-MIB.
     sensorThresholdExceeded 1.3.6.1.2.1.1.20.29
Indication that the temperature or humidity exceeded a threshhold and the value of the currrent temperature or humidity. Either the basicTemperatureValue or basicHumidityValue is included as a variable in the trap to indicate which sensor exceeded its threshold. These variables are FROM ITOUCH-CHARACTER-MIB.
     contactClosureChange 1.3.6.1.2.1.1.20.30
Indication that the contact closure transitioned to open or closed.
     powerAlarmFuseA 1.3.6.1.2.1.1.20.31
Indicates that a fuse from bank A tripped its breaker, or that it went operational. However, it is unlikely that a trap would be issued when the fuse starts working.
     powerAlarmFuseB 1.3.6.1.2.1.1.20.32
Indicates that a fuse from bank B tripped its breaker, or that it went operational. However, it is unlikely that a trap would be issued when the fuse starts working.
     powerAlarmSupplyA 1.3.6.1.2.1.1.20.33
Indicates that power supply A lost or regained power. However, it is unlikely that a trap would be issued when the power comes on.
     powerAlarmSupplyB 1.3.6.1.2.1.1.20.34
Indicates that power supply B lost or regained power. However, it is unlikely that a trap would be issued when the power comes on.
     portInputSignalChanged 1.3.6.1.2.1.1.20.35
Indicates that an input signal on a port has transitioned to the state indicated in the variable rs232InSigState.
     portOutputSignalChanged 1.3.6.1.2.1.1.20.36
Indicates that an output signal on a port has transitioned to the state indicated in the variable rs232OutSigState.
 xTrap 1.3.6.1.4.1.33.48