juniAtmPingTestOamSeg
Juniper-UNI-ATM-MIB ·
.1.3.6.1.4.1.4874.2.2.8.1.5.1.1
Object
node
This identifies an OAM Ping (multiple loopbacks) Test on a VPL, VPC,
VCL, or VCC termination point, using segment OAM cells.
The test type must have appended to it a code that uniquely identifies
an intermediate point responsible for looping back each cell. If this
is absent, the loopbacks are performed at the end of the segment or
connection.
E.g., the OID { juniAtmPingTestOamSeg 5 } identifies that the loopbacks
should be performed at the intermediate point labeled 5.
Context
- MIB
- Juniper-UNI-ATM-MIB
- OID
.1.3.6.1.4.1.4874.2.2.8.1.5.1.1- Type
- node
- Status
- current
- Parent
- juniAtmPingTestTypes
Net-SNMP examples
How SNMP and these commands workUse a bulk walk to inspect objects and instances beneath this OID.
Walk the subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'Juniper-UNI-ATM-MIB' -M '/opt/observium/mibs/junose:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'Juniper-UNI-ATM-MIB::juniAtmPingTestOamSeg'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'Juniper-UNI-ATM-MIB' -M '/opt/observium/mibs/junose:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'Juniper-UNI-ATM-MIB::juniAtmPingTestOamSeg'
Syntax
No syntax metadata recorded.
Values & Constraints
No enumerated values or constraints recorded.