mesMaidMdName
LUM-MES-MIB ·
.1.3.6.1.4.1.8708.2.32.2.24.1.1.5
Object
The Maintenance Domain name. The type/format of this
object is determined by the value of the
dot1agCfmMdNameType object.
Each Maintenance Domain has unique name amongst all
those used or available to a service provider or
operator. It facilitates easy identification of
administrative responsibility for each Maintenance
Domain.
Clause 3.24 defines a Maintenance Domain name as the
identifier, unique over the domain for which CFM is to
protect against accidental concatenation of Service
Instances, of a particular Maintenance Domain.
This attribute can be written via SNMP.
Context
- MIB
- LUM-MES-MIB
- OID
.1.3.6.1.4.1.8708.2.32.2.24.1.1.5- Type
- column
- Access
- readwrite
- Status
- current
- Default
"DEFAULT"- Parent
- mesMaidEntry
- Groups
- 6
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 'LUM-MES-MIB' -M '/opt/observium/mibs/infinera:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'LUM-MES-MIB::mesMaidMdName'
More examples
Read one indexed instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'LUM-MES-MIB' -M '/opt/observium/mibs/infinera:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'LUM-MES-MIB::mesMaidMdName.<mesMaidIndex>'
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'LUM-MES-MIB' -M '/opt/observium/mibs/infinera:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'LUM-MES-MIB::mesMaidMdName'
Syntax
- Source
- Dot1agCfmMaintDomainName
- Base type
OctetString- Display format
43a
Type Description
Denotes a generic Maintenance Domain Name.
A Dot1agCfmMaintDomainName value is always interpreted within
the context of a Dot1agCfmMaintDomainNameType value. Every
usage of the Dot1agCfmMaintDomainName textual convention is
required to specify the Dot1agCfmMaintDomainNameType object
that provides the context. It is suggested that the
Dot1agCfmMaintDomainNameType object be logically registered
before the object(s) that use the Dot1agCfmMaintDomainName
textual convention, if they appear in the same logical row.
The value of a Dot1agCfmMaintDomainName object must always
be consistent with the value of the associated
Dot1agCfmMaintDomainNameType object. Attempts to set
an Dot1agCfmMaintDomainName object to a value inconsistent
with the associated Dot1agCfmMaintDomainNameType must fail
with an inconsistentValue error.
When this textual convention is used as the syntax of an
index object, there may be issues with the limit of 128
sub-identifiers specified in SMIv2, IETF STD 58. In this
case, the object definition MUST include a 'SIZE' clause
to limit the number of potential instance sub-identifiers;
otherwise the applicable constraints MUST be stated in
the appropriate conceptual row DESCRIPTION clauses, or
in the surrounding documentation if there is no single
DESCRIPTION clause that is appropriate.
A value of none(1) in the associated
Dot1agCfmMaintDomainNameType object means that no Maintenance
Domain name is present, and the contents of the
Dot1agCfmMaintDomainName object are meaningless.
See the DESCRIPTION of the Dot1agCfmMaintAssocNameType
TEXTUAL-CONVENTION for a discussion of the length limits on
the Maintenance Domain name and Maintenance Association name.
Values & Constraints
Type Constraints
range: 1..43