oammMjTable

Object

table

This table controls which entities the DC-OAM Management component should join to
as master.  Each join is represented by a row
in this table.  The status of each join is represented
by a read-only object within each row.
          
DC-MPLS OAM Manager requires a single join of type
AMB_OAMM_MJ_I3 in order for it to go operStatusUp.
          
Additional joins must be programmed in order to support
specific DC-MPLS OAM manager function.
          
- A single join of type AMB_OAMM_MJ_FRI is required if
  DC-MPLS OAM Manager is to report faults status as
  determined by OAM function.
          
- One or more joins of type AMB_OAMM_MJ_BFDI must be
  programmed to enable DC-MPLS OAM Manager to intitiate BFD
  sessions.
          
- One or more joins of type AMB_OAMM_MJ_LPI must be
  programmed to enable DC-MPLS OAM Manager to intitiate LSP
  Ping transactions.
          
- One or more joins of type AMB_OAMM_MJ_PMI must be
  programmed to enable DC-MPLS OAM Manager to intitiate
  Performance Monitoring sessions.

Context

MIB: DC-OAMM-MIB
OID: .1.3.6.1.4.1.629.10.14.1.2
Type: table
Status: current
Parent: oammObjects
Children: 1

Net-SNMP examples

How SNMP and these commands work

Use a bulk walk to inspect objects and instances beneath this OID.

Walk the subtree

/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'DC-OAMM-MIB' -M '/opt/observium/mibs/mrv:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'DC-OAMM-MIB::oammMjTable'

More examples

Translate to a numeric OID

/usr/bin/snmptranslate -Pud -Ir -On -m 'DC-OAMM-MIB' -M '/opt/observium/mibs/mrv:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'DC-OAMM-MIB::oammMjTable'

Object

Context

Net-SNMP examples

Syntax

Values & Constraints