cfmMaFormat

DGS-1210-28XME-BX · .1.3.6.1.4.1.171.10.76.43.1.110.6.1.3

Object

The type (and thereby format) of the Maintenance Association
Name.

Context

MIB
DGS-1210-28XME-BX
OID
.1.3.6.1.4.1.171.10.76.43.1.110.6.1.3
Type
column
Access
readwrite
Status
current
Parent
cfmMaEntry

Walk 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 'DGS-1210-28XME-BX' -M '/opt/observium/mibs/d-link:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'DGS-1210-28XME-BX::cfmMaFormat'
More examples
Read one indexed instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'DGS-1210-28XME-BX' -M '/opt/observium/mibs/d-link:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'DGS-1210-28XME-BX::cfmMaFormat.<cfmMdIndex>.<cfmMaIndex>'
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'DGS-1210-28XME-BX' -M '/opt/observium/mibs/d-link:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'DGS-1210-28XME-BX::cfmMaFormat'

Syntax

Source
CfmMaintAssocNameType
Base type
Enumeration
Type Description
A value that represents a type (and thereby the format)
of a CfmMaintAssocName.  The value can be one of
the following:
          
ieeeReserved(0)   Reserved for definition by IEEE 802.1
                  recommend to not use zero unless
                  absolutely needed.
primaryVid(1)     Primary VLAN ID.
                  12 bits represented in a 2-octet integer:
                  - 4 least significant bits of the first
                    byte contains the 4 most significant 
                    bits of the 12 bits primary VID
                  - second byte contains the 8 least
                    significant bits of the primary VID
          
                         0 1 2 3 4 5 6 7 8
                         +-+-+-+-+-+-+-+-+
                         |0 0 0 0| (MSB) |
                         +-+-+-+-+-+-+-+-+
                         |  VID   LSB    |
                         +-+-+-+-+-+-+-+-+
          
charString(2)     RFC2579 DisplayString, except that the
                  character codes 0-31 (decimal) are not
                  used. (1..45) octets
unsignedInt16 (3) 2-octet integer/big endian
rfc2865VpnId(4)   RFC 2685 VPN ID
                  3 octet VPN authority Organizationally
                  Unique Identifier followed by 4 octet VPN
                  index identifying VPN according to the OUI:
          
                         0 1 2 3 4 5 6 7 8
                         +-+-+-+-+-+-+-+-+
                         | VPN OUI (MSB) |
                         +-+-+-+-+-+-+-+-+
                         |   VPN OUI     |
                         +-+-+-+-+-+-+-+-+
                         | VPN OUI (LSB) |
                         +-+-+-+-+-+-+-+-+
                         |VPN Index (MSB)|
                         +-+-+-+-+-+-+-+-+
                         |  VPN Index    |
                         +-+-+-+-+-+-+-+-+
                         |  VPN Index    |
                         +-+-+-+-+-+-+-+-+
                         |VPN Index (LSB)|
                         +-+-+-+-+-+-+-+-+
          
ieeeReserved(xx)  Reserved for definition by IEEE 802.1
                  xx values can be [5..31] and [64..255]
ituReserved(xx)   Reserved for definition by  ITU-T Y.1731
                  xx values range from [32..63]
          
To support future extensions, the CfmMaintAssocNameType
textual convention SHOULD NOT be sub-typed in object type
definitions.  It MAY be sub-typed in compliance statements in
order to require only a subset of these address types for a
compliant implementation.
          
Implementations must ensure that CfmMaintAssocNameType
objects and any dependent objects (e.g.,
CfmMaintAssocName objects) are consistent.  An
inconsistentValue error must be generated if an attempt to
change an CfmMaintAssocNameType object would, for
example, lead to an undefined CfmMaintAssocName value.
In particular,
CfmMaintAssocNameType/CfmMaintAssocName pairs
must be changed together if the nameType changes.
          
The Maintenance Domain name and Maintenance Association name,
when put together into the CCM PDU, MUST total 48 octets or
less.  If the CfmMaintDomainNameType object contains
none(1), then the CfmMaintAssocName object MUST be
45 octets or less in length.  Otherwise, the length of
the CfmMaintDomainName object plus the length of the
CfmMaintAssocName object, added together, MUST total
less than or equal to 44 octets.

Values & Constraints

Type Values
1primaryVid
2charString
3unsignedInt16
4rfc2865VpnId