AD | Application | AWS | Azure | Cloud | Database | Enterprise | Environmental | Event Log | File System | Infra | IoT | IT Service | Linux | Network/System | Performance | Protocol | SaaS | Security | Service Level | SNMP | Storage | VMware | VoIP | Web | Wireless

Crumbtrail

MonitorTools.com » Technical documentation » SNMP » MIB » Cisco » CISCO-OAM-MIB » Objects

CISCO-OAM-MIB.mib object view, vendor Cisco

Introduction

Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2024 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers). This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.

ActiveXperts Network Monitor 2024 can import MIB file CISCO-OAM-MIB and use it to monitor vendor specific OID's.

CISCO-OAM-MIB file content

Object view of CISCO-OAM-MIB:

Scalar Object
oamLoopbackPingEntry .1.3.6.1.4.1.9.10.15.1.1.1
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.
oamLoopbackSegEndPointEntry .1.3.6.1.4.1.9.10.15.1.2.1
An entry in the segment endpoint table.
Tabular Object
oamLoopbackPingSerialNumber .1.3.6.1.4.1.9.10.15.1.1.1.1
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
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
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
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
The type of OAM loopback to be performed.
oamLoopbackPingLocation .1.3.6.1.4.1.9.10.15.1.1.1.6
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
Specifies what kind of information is embedded into the oamLoopbackPingLocation string. This flag is ignored when oamLoopbackPingType is set to segment.
oamLoopbackPingCount .1.3.6.1.4.1.9.10.15.1.1.1.8
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
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
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
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
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
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
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
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
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
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
The entity that configured this entry.
oamLoopbackPingEntryStatus .1.3.6.1.4.1.9.10.15.1.1.1.19
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
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
This object indicates the ping test status.
oamLoopbackPingExecTime .1.3.6.1.4.1.9.10.15.1.1.1.22
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
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
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
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.
oamLoopSegVpi .1.3.6.1.4.1.9.10.15.1.2.1.1
The VPI value of a VP or VC connection.
oamLoopSegVci .1.3.6.1.4.1.9.10.15.1.2.1.2
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
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.
Table
oamLoopbackPingTable .1.3.6.1.4.1.9.10.15.1.1
A table of OAM loopback request entries. (This table is similar to the CISCO-PING-MIB.)
oamLoopbackSegEndPointTable .1.3.6.1.4.1.9.10.15.1.2
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.
Trap
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.
Object Identifier
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
oamLoopbackPingMIBTrapPrefix .1.3.6.1.4.1.9.10.15.2
oamLoopbackPingMIBTraps .1.3.6.1.4.1.9.10.15.2.0
ciscoOamPingMIBConformance .1.3.6.1.4.1.9.10.15.3
ciscoOamPingMIBCompliances .1.3.6.1.4.1.9.10.15.3.1
ciscoOamPingMIBGroups .1.3.6.1.4.1.9.10.15.3.2
Group
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.
oamLoopbackNotificationsGroup .1.3.6.1.4.1.9.10.15.3.2.4
A collection of notifications for OAM loopback ping test.
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.
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.