CISCO-OAM-MIB
- Registered at
- 1.3.6.1.4.1.9.10.15
- Last updated
- 2006-02-17 00:00
- Organization
- Cisco Systems, Inc.
- Revisions
- 2006-02-17 00:00, 2003-06-27 00:00, 2003-04-04 00:00, 1996-05-01 00:00
- Namespace
- cisco
- Source file
CISCO-OAM-MIB- Digest
sha256:0aa8cb8c9bc49efd2518fcb6b168ad59f3d1585449e2b2cd6a420b78a5e02c89
Description
A MIB module for invoking OAM loopback Ping on ATM connections.
Contact
Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: cs-atm@cisco.com
Imports
| From | Symbols |
|---|---|
| CISCO-SMI | ciscoExperiment |
| IF-MIB | ifIndex |
| RMON-MIB | OwnerString |
| SNMPv2-CONF | MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP |
| SNMPv2-SMI | Counter32, Integer32, MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, Unsigned32, iso |
| SNMPv2-TC | DisplayString, RowStatus, TEXTUAL-CONVENTION, TimeStamp, TruthValue |
Imported by
Nothing in this corpus imports this module.
Load order
Every file a consumer needs in order to load this module, dependencies first.
CISCO-OAM-MIB CISCO-SMI IANAifType-MIB IF-MIB RMON-MIB SNMPv2-CONF SNMPv2-MIB SNMPv2-SMI SNMPv2-TC
Textual conventions
| Name | OID | Syntax | Access | Status |
|---|---|---|---|---|
| CiscoOAMPingDir TEXTUAL-CONVENTION Direction in which the OAM segment cells are sent: forward : send OAM loopback cells in the direction form the originator towards the destination of the connection. backward : send OAM loopback cells in the direction towards the originator of the connection. | current | |||
| CiscoOAMPingStatus TEXTUAL-CONVENTION Defines possible test status. success(1) - The test has completed. timeOut(2) - The test has been failed because the test does not receive loopback cell response from remote endpoint and it times out. resourceNotAvailable(3) - The resources required by the test is not available, such as other application is testing on the same endpoint. aborted(4) - The test is aborted due to the removal of connection endpoint or failed to proceed. inProgress(5) - The endpoint is still in progress of testing and waiting for the response. noResponseData(6) - If the test receives response from the remote end but without any data. failToStart(7) - The test fails to kickoff (internal messaging timeout). | current |
Objects
| Name | OID | Syntax | Access | Status |
|---|---|---|---|---|
| ciscoOamPingMIBObjects OBJECT-IDENTITY | 1.3.6.1.4.1.9.10.15.1 | |||
| oamLoopbackPingTable OBJECT-TYPE A table of OAM loopback request entries. (This table is similar to the CISCO-PING-MIB.) | 1.3.6.1.4.1.9.10.15.1.1 | not-accessible | current | |
| oamLoopbackPingEntry OBJECT-TYPE 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. | 1.3.6.1.4.1.9.10.15.1.1.1 | not-accessible | current | |
| oamLoopbackPingSerialNumber OBJECT-TYPE 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. | 1.3.6.1.4.1.9.10.15.1.1.1.1 | INTEGER (1..2147483647) | not-accessible | current |
| oamLoopbackPingInterface OBJECT-TYPE 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. | 1.3.6.1.4.1.9.10.15.1.1.1.2 | Integer32 (1..2147483647) | read-create | current |
| oamLoopbackPingVpi OBJECT-TYPE 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. | 1.3.6.1.4.1.9.10.15.1.1.1.3 | INTEGER (0..4095) | read-create | current |
| oamLoopbackPingVci OBJECT-TYPE 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. | 1.3.6.1.4.1.9.10.15.1.1.1.4 | INTEGER (-1..65535) | read-create | current |
| oamLoopbackPingType OBJECT-TYPE The type of OAM loopback to be performed. | 1.3.6.1.4.1.9.10.15.1.1.1.5 | INTEGER {segment(1), end2end(2)} | read-create | current |
| oamLoopbackPingLocation OBJECT-TYPE 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. | 1.3.6.1.4.1.9.10.15.1.1.1.6 | OCTET STRING (SIZE(0..16)) | read-create | current |
| oamLoopbackPingLocationFlag OBJECT-TYPE Specifies what kind of information is embedded into the oamLoopbackPingLocation string. This flag is ignored when oamLoopbackPingType is set to segment. | 1.3.6.1.4.1.9.10.15.1.1.1.7 | INTEGER {ipAddress(1), nsapPrefix(2), fixed16byteValue(3)} | read-create | current |
| oamLoopbackPingCount OBJECT-TYPE Specifies the number of OAM loopback cells to send to the target in this sequence. | 1.3.6.1.4.1.9.10.15.1.1.1.8 | INTEGER (0..2147483647) | read-create | current |
| oamLoopbackPingTimeout OBJECT-TYPE Specifies the amount of time to wait for a response to a transmitted OAM loopback cells before declaring the OAM loopback cells as 'dropped.' | 1.3.6.1.4.1.9.10.15.1.1.1.9 | INTEGER (0..3600000) | read-create | current |
| oamLoopbackPingDelay OBJECT-TYPE 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. | 1.3.6.1.4.1.9.10.15.1.1.1.10 | INTEGER (0..3600000) | read-create | current |
| oamLoopbackPingTrapOnCompletion OBJECT-TYPE 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. | 1.3.6.1.4.1.9.10.15.1.1.1.11 | TruthValue | read-create | current |
| oamLoopbackPingSentCells OBJECT-TYPE The number of OAM loopback cells that have been sent to the target in this sequence. | 1.3.6.1.4.1.9.10.15.1.1.1.12 | Counter32 | read-only | current |
| oamLoopbackPingReceivedCells OBJECT-TYPE The number of OAM loopback cells that have been received from the target in this sequence. | 1.3.6.1.4.1.9.10.15.1.1.1.13 | Counter32 | read-only | current |
| oamLoopbackPingMinRtt OBJECT-TYPE 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. | 1.3.6.1.4.1.9.10.15.1.1.1.14 | Integer32 (0..2147483647) | read-only | current |
| oamLoopbackPingAvgRtt OBJECT-TYPE 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. | 1.3.6.1.4.1.9.10.15.1.1.1.15 | Integer32 (0..2147483647) | read-only | current |
| oamLoopbackPingMaxRtt OBJECT-TYPE 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. | 1.3.6.1.4.1.9.10.15.1.1.1.16 | Integer32 (0..2147483647) | read-only | current |
| oamLoopbackPingCompleted OBJECT-TYPE Set to true when all the OAM loopback cells in this sequence have been either responded to or timed out. | 1.3.6.1.4.1.9.10.15.1.1.1.17 | TruthValue | read-only | current |
| oamLoopbackPingEntryOwner OBJECT-TYPE The entity that configured this entry. | 1.3.6.1.4.1.9.10.15.1.1.1.18 | OwnerString | read-create | current |
| oamLoopbackPingEntryStatus OBJECT-TYPE 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). | 1.3.6.1.4.1.9.10.15.1.1.1.19 | RowStatus | read-create | current |
| oamLoopbackPingDir OBJECT-TYPE This object set the traveling direction of the OAM segment loopback cells which are injected to the connection endpoint. | 1.3.6.1.4.1.9.10.15.1.1.1.20 | CiscoOAMPingDir | read-create | current |
| oamLoopbackPingOperStatus OBJECT-TYPE This object indicates the ping test status. | 1.3.6.1.4.1.9.10.15.1.1.1.21 | CiscoOAMPingStatus | read-only | current |
| oamLoopbackPingExecTime OBJECT-TYPE The value of sysUpTime when the MIB object is created which triggers the loppback ping test. | 1.3.6.1.4.1.9.10.15.1.1.1.22 | TimeStamp | read-only | current |
| oamLoopbackPingMinRttuSec OBJECT-TYPE 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. | 1.3.6.1.4.1.9.10.15.1.1.1.23 | Integer32 (0..2147483647) | read-only | current |
| oamLoopbackPingAvgRttuSec OBJECT-TYPE 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. | 1.3.6.1.4.1.9.10.15.1.1.1.24 | Integer32 (0..2147483647) | read-only | current |
| oamLoopbackPingMaxRttuSec OBJECT-TYPE 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. | 1.3.6.1.4.1.9.10.15.1.1.1.25 | Integer32 (0..2147483647) | read-only | current |
| oamLoopbackSegEndPointTable OBJECT-TYPE 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. | 1.3.6.1.4.1.9.10.15.1.2 | not-accessible | current | |
| oamLoopbackSegEndPointEntry OBJECT-TYPE An entry in the segment endpoint table. | 1.3.6.1.4.1.9.10.15.1.2.1 | not-accessible | current | |
| oamLoopSegVpi OBJECT-TYPE The VPI value of a VP or VC connection. | 1.3.6.1.4.1.9.10.15.1.2.1.1 | Unsigned32 (0..4095) | not-accessible | current |
| oamLoopSegVci OBJECT-TYPE The VCI value of VC connection. For a VPC connection, the VCI value is 0. | 1.3.6.1.4.1.9.10.15.1.2.1.2 | Unsigned32 (0..65535) | not-accessible | current |
| oamLoopSegRowStatus OBJECT-TYPE 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. | 1.3.6.1.4.1.9.10.15.1.2.1.3 | RowStatus | read-create | current |
| oamLoopbackPingMIBTrapPrefix OBJECT-IDENTITY | 1.3.6.1.4.1.9.10.15.2 | |||
| oamLoopbackPingMIBTraps OBJECT-IDENTITY | 1.3.6.1.4.1.9.10.15.2.0 | |||
| ciscoOamPingMIBConformance OBJECT-IDENTITY | 1.3.6.1.4.1.9.10.15.3 | |||
| ciscoOamPingMIBCompliances OBJECT-IDENTITY | 1.3.6.1.4.1.9.10.15.3.1 | |||
| ciscoOamPingMIBGroups OBJECT-IDENTITY | 1.3.6.1.4.1.9.10.15.3.2 |
Notifications
| Name | OID | Status |
|---|---|---|
| oamLoopbackPingCompletionTrap NOTIFICATION-TYPE 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. | 1.3.6.1.4.1.9.10.15.2.0.1 | current |
Conformance
| Name | OID | Status |
|---|---|---|
| ciscoOamPingMIBCompliance MODULE-COMPLIANCE The compliance statement for the Cisco OAM MIB. | 1.3.6.1.4.1.9.10.15.3.1.1 | deprecated |
| ciscoOamPingMIBCompliance2 MODULE-COMPLIANCE The compliance statement for the Cisco OAM MIB. | 1.3.6.1.4.1.9.10.15.3.1.2 | deprecated |
| ciscoOamPingMIBCompliance3 MODULE-COMPLIANCE The compliance statement for the Cisco OAM MIB. | 1.3.6.1.4.1.9.10.15.3.1.3 | current |
| ciscoOamPingMIBGroup OBJECT-GROUP A collection of objects providing the ability to invoke the sending of OAM loopback cells. | 1.3.6.1.4.1.9.10.15.3.2.1 | deprecated |
| ciscoOamPing2MIBGroup OBJECT-GROUP A collection of objects providing the ability to invoke the sending of OAM loopback cells. | 1.3.6.1.4.1.9.10.15.3.2.2 | deprecated |
| ciscoOamPingSegEndPointGroup OBJECT-GROUP A collection of objects providing the ability to provision ATM connection endpoints to be OAM segment loopback endpoint. | 1.3.6.1.4.1.9.10.15.3.2.3 | current |
| oamLoopbackNotificationsGroup NOTIFICATION-GROUP A collection of notifications for OAM loopback ping test. | 1.3.6.1.4.1.9.10.15.3.2.4 | current |
| ciscoOamPingMIBGroupRev3 OBJECT-GROUP A collection of objects providing the ability to invoke the sending of OAM loopback cells. | 1.3.6.1.4.1.9.10.15.3.2.5 | current |