tmnxOamLspTrCtlAssocChannel
TIMETRA-OAM-TEST-MIB ·
.1.3.6.1.4.1.6527.3.1.2.11.2.9.1.17
Object
The value of tmnxOamLspTrCtlAssocChannel specifies the launched echo
request's usage of the Associated Channel (ACH) mechanism, when
testing an MPLS-TP LSP.
When tmnxOamLspTrCtlTestSubMode is 'static(2)', the default value for
tmnxOamLspTrCtlAssocChannel is 'nonIp(2)'.
The supported object combinations for LSP trace route tests are listed
in the tmnxOamLspTrCtlTable DESCRIPTION clause.
Context
- MIB
- TIMETRA-OAM-TEST-MIB
- OID
.1.3.6.1.4.1.6527.3.1.2.11.2.9.1.17- Type
- column
- Access
- readwrite
- Status
- current
- Default
notApplicable- Parent
- tmnxOamLspTrCtlEntry
- Groups
- 1
Net-SNMP examples
How SNMP and these commands workWalk the column to discover its indexed instances, or supply every index to read one instance.
Walk the column
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'TIMETRA-OAM-TEST-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'TIMETRA-OAM-TEST-MIB::tmnxOamLspTrCtlAssocChannel'
More examples
Read one indexed instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'TIMETRA-OAM-TEST-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'TIMETRA-OAM-TEST-MIB::tmnxOamLspTrCtlAssocChannel.<tmnxOamTrCtlOwnerIndex>.<tmnxOamTrCtlTestIndex>'
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'TIMETRA-OAM-TEST-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'TIMETRA-OAM-TEST-MIB::tmnxOamLspTrCtlAssocChannel'
Syntax
- Source
- TmnxOamLspAssocChannel
- Base type
Enumeration
Type Description
A value of type TmnxOamLspAssocChannel specifies the launched echo
request's usage of the Associated Channel (ACH) mechanism, when
testing an MPLS-TP LSP.
Values:
notApplicable(1)
Used when the test is not testing an MPLS-TP LSP.
nonIp(2)
Use the Associated Channel mechanism described in RFC 6426,
Section 3.3.
none(3)
Do not use an Associated Channel, as described in RFC 6426,
Section 3.1.
ipv4(4)
Use the Associated Channel mechanism described in RFC 6426,
Section 3.2.
Values & Constraints
Type Values
1 | notApplicable |
2 | nonIp |
3 | none |
4 | ipv4 |
Conformance
Member of