tmnxDot1agCfmMepFcltyInstance
TIMETRA-IEEE8021-CFM-MIB ·
.1.3.6.1.4.1.6527.3.1.2.52.9.3
Object
scalar SNMPv2-TCDisplayString
The value of tmnxDot1agCfmMepFcltyInstance indicates the specific
facility instance that a facility MEP has affected via a raised or
cleared event.
This value is used in combination with its tmnxDot1agCfmMepFcltyType.
The possible facility types and instance forms are described in the
following table:
Facility Type | Facility Instance
---------------------------------------------
port | slot/mda/port
lag | lag-id
networkInterface | interface name
qinqPortTunnelSap | sap-id
qinqLagTunnelSap | sap-id
The combined value will appear as in the following examples:
port 7/2/2
lag 1
networkInterface test
qinqPortTunnelSap 2/2/2:100.*
qinqLagTunnelSap lag-1:100.*
When a facility fault occurs on a QinQ port or lag, the sap executing
the CFM functional test, the sap will be included as part of the
event log message. However, QinQ facility tunnel MEPs on the sap are
only the detection point for the defect / clear condition. The QinQ
facility tunnel is port or lag based and a representative outer tag.
Context
- MIB
- TIMETRA-IEEE8021-CFM-MIB
- OID
.1.3.6.1.4.1.6527.3.1.2.52.9.3- Type
- scalar
- Access
- notifyonly
- Status
- current
- Parent
- tmnxDot1agCfmNotificationObjs
- Groups
- 1
Net-SNMP examples
How SNMP and these commands workScalars have one instance, identified by the .0 suffix.
Read the scalar instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'TIMETRA-IEEE8021-CFM-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'TIMETRA-IEEE8021-CFM-MIB::tmnxDot1agCfmMepFcltyInstance.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'TIMETRA-IEEE8021-CFM-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'TIMETRA-IEEE8021-CFM-MIB::tmnxDot1agCfmMepFcltyInstance'
Syntax
- Source
- SNMPv2-TCDisplayString
- Base type
OctetString- Display format
255a
Type Description
Represents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as
US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special
meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the
same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is
illegal. (Note that this also means that a string may
end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255
characters in length.
Values & Constraints
Type Constraints
range: 0..255
Conformance
Member of