CISCO-OAM-MIB: View SNMP OID List / Download MIB

VENDOR: CISCO


 Home MIB: CISCO-OAM-MIB
Download as:   
SNMPv2-CONF, IF-MIB, SNMPv2-SMI, CISCO-SMI, RMON-MIB, SNMPv2-TC

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
 ciscoOamPingMIB 1.3.6.1.4.1.9.10.15
A MIB module for invoking OAM loopback Ping on ATM connections.
       ciscoOamPingMIBObjects 1.3.6.1.4.1.9.10.15.1
           oamLoopbackPingTable 1.3.6.1.4.1.9.10.15.1.1 no-access
A table of OAM loopback request entries. (This table is similar to the CISCO-PING-MIB.)
               oamLoopbackPingEntry 1.3.6.1.4.1.9.10.15.1.1.1 no-access
A OAM loopback request entry. A management station wishing to create an entry should first generate a pseudo-random serial number to be used as the index to this sparse table. The NMS should then create the associated instance of the row status and row owner objects. It must also, either in the same or in successive PDUs, create the associated instances specifying the VPI and VCI values. It should also modify the default values for the other configuration objects if the defaults are not appropriate. Once the appropriate instance of all the configuration objects have been created, either by an explicit SNMP set request or by default, the row status should be set to active to initiate the request. Note that this entire procedure may be initiated via a single set request which specifies a row status of createAndGo as well as specifies valid values for the non-defaulted configuration objects. Once the OAM sequence has been activated, it cannot be stopped -- it will run until the configured number of cells have been sent. Once the sequence completes, the management station should retrieve the values of the status objects of interest, and should then delete the entry. In order to prevent old entries from clogging the table, entries will be aged out, but an entry will never be deleted within 5 minutes of completing.
                   oamLoopbackPingSerialNumber 1.3.6.1.4.1.9.10.15.1.1.1.1 integer no-access
Object which identifies a unique entry in the oamLoopbackPingTable. A management station wishing to initiate a OAM-loopback operation should use a pseudo-random value for this object when creating or modifying an instance of an oamLoopbackPingEntry. The RowStatus semantics of the oamLoopbackPingEntryStatus object will prevent access conflicts.
                   oamLoopbackPingInterface 1.3.6.1.4.1.9.10.15.1.1.1.2 integer32 read-only
The interface of the connection on which OAM loopbacks are to be sent. Once an instance of this object is created, its value can not be changed. The value specified for this object must equate to a value of ifIndex in the ifTable.
                   oamLoopbackPingVpi 1.3.6.1.4.1.9.10.15.1.1.1.3 integer read-only
The VPI of the connection on which OAM loopbacks are to be sent. Once an instance of this object is created, its value can not be changed.
                   oamLoopbackPingVci 1.3.6.1.4.1.9.10.15.1.1.1.4 integer read-only
Either -1 or the VCI of the connection on which F5 OAM loopback cells are to be sent. If the value of this object is -1, then an F4 OAM loopback cells will be sent on the VPC indicated by oamLoopbackPingVpi. An instance of this object cannot be created until the associated instance of oamLoopbackPingVpi is created. Once an instance of this object is created, its value can not be changed.
                   oamLoopbackPingType 1.3.6.1.4.1.9.10.15.1.1.1.5 integer read-only
The type of OAM loopback to be performed. Enumeration: 'end2end': 2, 'segment': 1.
                   oamLoopbackPingLocation 1.3.6.1.4.1.9.10.15.1.1.1.6 octet string read-only
The value to be placed in the 'Loopback Location ID' field of the OAM loopback cell. If this value is less than 16 octets in length, then it will be appended with zero-valued octets to form the required 96-bit value. One possibility is to set this value to the IP-address of the node at which the OAM loopback is to occur. An instance of this object cannot be created until the associated instance of oamLoopbackPingVpi is created. Once an instance of this object is created, its value can not be changed.
                   oamLoopbackPingLocationFlag 1.3.6.1.4.1.9.10.15.1.1.1.7 integer read-only
Specifies what kind of information is embedded into the oamLoopbackPingLocation string. This flag is ignored when oamLoopbackPingType is set to segment. Enumeration: 'nsapPrefix': 2, 'fixed16byteValue': 3, 'ipAddress': 1.
                   oamLoopbackPingCount 1.3.6.1.4.1.9.10.15.1.1.1.8 integer read-only
Specifies the number of OAM loopback cells to send to the target in this sequence.
                   oamLoopbackPingTimeout 1.3.6.1.4.1.9.10.15.1.1.1.9 integer read-only
Specifies the amount of time to wait for a response to a transmitted OAM loopback cells before declaring the OAM loopback cells as 'dropped.'
                   oamLoopbackPingDelay 1.3.6.1.4.1.9.10.15.1.1.1.10 integer read-only
Specifies the minimum amount of time to wait before sending the next OAM loopback cell in a sequence after receiving a response or declaring a timeout for a previous OAM cell. The actual delay may be greater due to internal task scheduling.
                   oamLoopbackPingTrapOnCompletion 1.3.6.1.4.1.9.10.15.1.1.1.11 truthvalue read-only
Specifies whether or not a oamLoopbackPingCompletion trap should be issued on completion of the sequence of OAM loopback cells. If such a trap is desired, it is the responsibility of the management entity to ensure that the SNMP administrative model is configured in such a way as to allow the trap to be delivered.
                   oamLoopbackPingSentCells 1.3.6.1.4.1.9.10.15.1.1.1.12 counter32 read-only
The number of OAM loopback cells that have been sent to the target in this sequence.
                   oamLoopbackPingReceivedCells 1.3.6.1.4.1.9.10.15.1.1.1.13 counter32 read-only
The number of OAM loopback cells that have been received from the target in this sequence.
                   oamLoopbackPingMinRtt 1.3.6.1.4.1.9.10.15.1.1.1.14 integer32 read-only
The minimum round trip time of all the OAM loopback cells that have been sent in this sequence. This object will not be created until the first OAM loopback response in a sequence is received.
                   oamLoopbackPingAvgRtt 1.3.6.1.4.1.9.10.15.1.1.1.15 integer32 read-only
The average round trip time of all the OAM loopback cells that have been sent in this sequence. This object will not be created until the first OAM loopback response in a sequence is received.
                   oamLoopbackPingMaxRtt 1.3.6.1.4.1.9.10.15.1.1.1.16 integer32 read-only
The maximum round trip time of all the OAM loopback cells that have been sent in this sequence. This object will not be created until the first OAM loopback response in a sequence is received.
                   oamLoopbackPingCompleted 1.3.6.1.4.1.9.10.15.1.1.1.17 truthvalue read-only
Set to true when all the OAM loopback cells in this sequence have been either responded to or timed out.
                   oamLoopbackPingEntryOwner 1.3.6.1.4.1.9.10.15.1.1.1.18 ownerstring read-only
The entity that configured this entry.
                   oamLoopbackPingEntryStatus 1.3.6.1.4.1.9.10.15.1.1.1.19 rowstatus read-only
The status of this table entry. Once the entry status is set to active, the associate entry cannot be modified until the sequence completes (oamLoopbackPingCompleted is true).
                   oamLoopbackPingDir 1.3.6.1.4.1.9.10.15.1.1.1.20 ciscooampingdir read-only
This object set the traveling direction of the OAM segment loopback cells which are injected to the connection endpoint.
                   oamLoopbackPingOperStatus 1.3.6.1.4.1.9.10.15.1.1.1.21 ciscooampingstatus read-only
This object indicates the ping test status.
                   oamLoopbackPingExecTime 1.3.6.1.4.1.9.10.15.1.1.1.22 timestamp read-only
The value of sysUpTime when the MIB object is created which triggers the loppback ping test.
                   oamLoopbackPingMinRttuSec 1.3.6.1.4.1.9.10.15.1.1.1.23 integer32 read-only
The minimum round trip time of all the OAM loopback cells that have been sent in this sequence. This object will not be created until the first OAM loopback response in a sequence is received. Notes: this object is the same as oamLoopbackPingMinRtt but the unit is in microseconds instead of milliseconds.
                   oamLoopbackPingAvgRttuSec 1.3.6.1.4.1.9.10.15.1.1.1.24 integer32 read-only
The average round trip time of all the OAM loopback cells that have been sent in this sequence. This object will not be created until the first OAM loopback response in a sequence is received. Notes: this object is the same as oamLoopbackPingAvgRtt but the unit is in microseconds instead of milliseconds.
                   oamLoopbackPingMaxRttuSec 1.3.6.1.4.1.9.10.15.1.1.1.25 integer32 read-only
The maximum round trip time of all the OAM loopback cells that have been sent in this sequence. This object will not be created until the first OAM loopback response in a sequence is received. Notes: this object is the same as oamLoopbackPingMaxRtt but the unit is in microseconds instead of milliseconds.
           oamLoopbackSegEndPointTable 1.3.6.1.4.1.9.10.15.1.2 no-access
This table contains a list of OAM loopback segment endpoints. When the endpoint is an OAM segment endpoint, it is able to send ATM segment loop back cells or loop back the cells to the originator which initiates the OAM loop back ping test. The provisioning of this table is required if the loopback ping test type (oamLoopbackPingType) in oamLoopbackPingTable is 'segment', and the endpoint under test or the remote ping endpoint is not OAM segment loopback endpoints.
               oamLoopbackSegEndPointEntry 1.3.6.1.4.1.9.10.15.1.2.1 no-access
An entry in the segment endpoint table.
                   oamLoopSegVpi 1.3.6.1.4.1.9.10.15.1.2.1.1 unsigned32 no-access
The VPI value of a VP or VC connection.
                   oamLoopSegVci 1.3.6.1.4.1.9.10.15.1.2.1.2 unsigned32 no-access
The VCI value of VC connection. For a VPC connection, the VCI value is 0.
                   oamLoopSegRowStatus 1.3.6.1.4.1.9.10.15.1.2.1.3 rowstatus read-only
To create, delete an OAM segment entry. Only the value 'active', 'createAndGo', and 'destroy' are supported. If the connection endpoint does not exist, the entry could not be created. If the associated ATM connection is de-routed or deleted, the connection endpoint is gone. The associated row entry will be removed automatically.
       oamLoopbackPingMIBTrapPrefix 1.3.6.1.4.1.9.10.15.2
           oamLoopbackPingMIBTraps 1.3.6.1.4.1.9.10.15.2.0
               oamLoopbackPingCompletionTrap 1.3.6.1.4.1.9.10.15.2.0.1
A oamLoopbackPingCompleted trap is sent at the completion of a sequence of OAM loopback cells if such a trap was requested when the sequence was initiated.
       ciscoOamPingMIBConformance 1.3.6.1.4.1.9.10.15.3
           ciscoOamPingMIBCompliances 1.3.6.1.4.1.9.10.15.3.1
               ciscoOamPingMIBCompliance 1.3.6.1.4.1.9.10.15.3.1.1
The compliance statement for the Cisco OAM MIB.
               ciscoOamPingMIBCompliance2 1.3.6.1.4.1.9.10.15.3.1.2
The compliance statement for the Cisco OAM MIB.
               ciscoOamPingMIBCompliance3 1.3.6.1.4.1.9.10.15.3.1.3
The compliance statement for the Cisco OAM MIB.
           ciscoOamPingMIBGroups 1.3.6.1.4.1.9.10.15.3.2
               ciscoOamPingMIBGroup 1.3.6.1.4.1.9.10.15.3.2.1
A collection of objects providing the ability to invoke the sending of OAM loopback cells.
               ciscoOamPing2MIBGroup 1.3.6.1.4.1.9.10.15.3.2.2
A collection of objects providing the ability to invoke the sending of OAM loopback cells.
               ciscoOamPingSegEndPointGroup 1.3.6.1.4.1.9.10.15.3.2.3
A collection of objects providing the ability to provision ATM connection endpoints to be OAM segment loopback endpoint.
               oamLoopbackNotificationsGroup 1.3.6.1.4.1.9.10.15.3.2.4
A collection of notifications for OAM loopback ping test.
               ciscoOamPingMIBGroupRev3 1.3.6.1.4.1.9.10.15.3.2.5
A collection of objects providing the ability to invoke the sending of OAM loopback cells.