| Dot1agCfmMaintDomainNameType |
|
| A value that represents a type (and thereby the format)
of a Dot1agCfmMaintDomainName. 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.
none(1) No format specified, usually because
there is not (yet) a Maintenance
Domain Name. In this case, a zero
length OCTET STRING for the Domain
Name field is acceptable.
dnsLikeName(2) Domain Name like string, globally unique
text string derived from a DNS name.
macAddrAndUint(3) MAC address + 2-octet (unsigned) integer.
charString(4) RFC2579 DisplayString, except that the
character codes 0-31 (decimal) are not
used.
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 Dot1agCfmMaintDomainNameType
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 Dot1agCfmMaintDomainNameType
objects and any dependent objects (e.g.,
Dot1agCfmMaintDomainName objects) are consistent. An
inconsistentValue error must be generated if an attempt to
change an Dot1agCfmMaintDomainNameType object would, for
example, lead to an undefined Dot1agCfmMaintDomainName value.
In particular,
Dot1agCfmMaintDomainNameType/Dot1agCfmMaintDomainName pairs
must be changed together if the nameType changes.
|
| TEXTUAL-CONVENTION |
|
|
|
| |
INTEGER |
none(1), dnsLikeName(2), macAddressAndUint(3), charString(4) |
|
| Dot1agCfmMaintDomainName |
|
| Denotes a generic Maintenance Domain Name.A Dot1agC
fmMaintDomainName 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.
|
| TEXTUAL-CONVENTION |
|
|
|
| |
OCTET STRING |
Size(1..43) |
|
| Dot1agCfmMaintAssocNameType |
|
| A value that represents a type (and thereby the format)
of a Dot1agCfmMaintAssocName. 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)|
+-+-+-+-+-+-+-+-+
iccString(32) ICC-based string. It consists of two subfields:
the ITU carrier code (ICC) followed by a unique MEG ID code (UMC).
The ITU Carrier Code consists of 1 6 left-justified characters,
alphabetic, or leading alphabetic with trailing numeric. The UMC
code immediately follows the ICC and shall consist of 7-12 characters,
with trailing NULLs, completing the 13-character MEG ID Value.
The UMC shall be a matter for the organization to which the ICC
has been assigned, provided that uniqueness is guaranteed.
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 [33..63]
To support future extensions, the Dot1agCfmMaintAssocNameType
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 Dot1agCfmMaintAssocNameType
objects and any dependent objects (e.g.,
Dot1agCfmMaintAssocName objects) are consistent. An
inconsistentValue error must be generated if an attempt to
change an Dot1agCfmMaintAssocNameType object would, for
example, lead to an undefined Dot1agCfmMaintAssocName value.
In particular,
Dot1agCfmMaintAssocNameType/Dot1agCfmMaintAssocName 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 Dot1agCfmMaintDomainNameType object contains
none(1), then the Dot1agCfmMaintAssocName object MUST be
45 octets or less in length. Otherwise, the length of
the Dot1agCfmMaintDomainName object plus the length of the
Dot1agCfmMaintAssocName object, added together, MUST total
less than or equal to 44 octets.
|
| TEXTUAL-CONVENTION |
|
|
|
| |
INTEGER |
primaryVid(1), charString(2), unsignedInt16(3), rfc2865VpnId(4), iccString(32) |
|
| Dot1agCfmMaintAssocName |
|
| Denotes a generic Maintenance Association Name. It is the
part of the Maintenance Association Identifier which is
unique within the Maintenance Domain Name and is appended
to the Maintenance Domain Name to form the Maintenance
Association Identifier (MAID).
A Dot1agCfmMaintAssocName value is always interpreted within
the context of a Dot1agCfmMaintAssocNameType value. Every
usage of the Dot1agCfmMaintAssocName textual convention is
required to specify the Dot1agCfmMaintAssocNameType object
that provides the context. It is suggested that the
Dot1agCfmMaintAssocNameType object be logically registered
before the object(s) that use the Dot1agCfmMaintAssocName
textual convention, if they appear in the same logical row.
The value of a Dot1agCfmMaintAssocName object must
always be consistent with the value of the associated
Dot1agCfmMaintAssocNameType object. Attempts to set
an Dot1agCfmMaintAssocName object to a value inconsistent
with the associated Dot1agCfmMaintAssocNameType 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.
|
| TEXTUAL-CONVENTION |
|
|
|
| |
OCTET STRING |
Size(1..45) |
|
| Dot1agCfmHighestDefectPri |
|
| An enumerated value, equal to the contents of the variable
highestDefect (20.33.9 and Table 20-1), indicating the
highest-priority defect that has been present since the MEP
Fault Notification Generator State Machine was last in the
FNG_RESET state, either:
none(0) no defects since FNG_RESET
defRDICCM(1) DefRDICCM
defMACstatus(2) DefMACstatus
defRemoteCCM(3) DefRemoteCCM
defErrorCCM(4) DefErrorCCM
defXconCCM(5) DefXconCCM
The value 0 is used for no defects so that additional higher
priority values can be added, if needed, at a later time, and
so that these values correspond with those in
Dot1agCfmLowestAlarmPri.
|
| TEXTUAL-CONVENTION |
|
|
|
| |
INTEGER |
none(0), defRDICCM(1), defMACstatus(2), defRemoteCCM(3), defErrorCCM(4), defXconCCM(5) |
|
| Dot1agCfmLowestAlarmPri |
|
| An integer value specifying the lowest priority defect
that is allowed to generate a Fault Alarm (20.9.5), either:
allDef(1) DefRDICCM, DefMACstatus, DefRemoteCCM,
DefErrorCCM, and DefXconCCM;
macRemErrXcon(2) Only DefMACstatus, DefRemoteCCM,
DefErrorCCM, and DefXconCCM (default);
remErrXcon(3) Only DefRemoteCCM, DefErrorCCM,
and DefXconCCM;
errXcon(4) Only DefErrorCCM and DefXconCCM;
xcon(5) Only DefXconCCM; or
noXcon(6) No defects DefXcon or lower are to be
reported;
|
| TEXTUAL-CONVENTION |
|
|
|
| |
INTEGER |
allDef(1), macRemErrXcon(2), remErrXcon(3), errXcon(4), xcon(5), noXcon(6) |
|
| Dot1agCfmIdPermission |
|
| Indicates what, if anything, is to be included in the Sender
ID TLV transmitted in CCMs, LBMs, LTMs, and LTRs. The valid
values are:
sendIdNone(1) The Sender ID TLV is not to be sent.
sendIdChassis(2) The Chassis ID Length, Chassis ID
Subtype, and Chassis ID fields of the
Sender ID TLV are to be sent.
sendIdManage(3) The Management Address Length and
Management Address of the Sender ID TLV
are to be sent.
sendIdChassisManage(4) The Chassis ID Length, Chassis ID
Subtype, Chassis ID, Management Address
Length and Management Address fields are
all to be sent.
sendIdDefer(5) The contents of the Sender ID TLV are
determined by the corresponding
Maintenance Domain variable
(dot1agCfmMaIdPermission).
|
| TEXTUAL-CONVENTION |
|
|
|
| |
INTEGER |
sendIdNone(1), sendIdChassis(2), sendIdManage(3), sendIdChassisManage(4), sendIdDefer(5) |
|
| Dot1agCfmMdEntry |
|
| SEQUENCE |
|
|
|
| |
dot1agCfmMdIndex |
Unsigned32 |
|
| |
dot1agCfmMdFormat |
Dot1agCfmMaintDomainNameType |
|
| |
dot1agCfmMdName |
Dot1agCfmMaintDomainName |
|
| |
dot1agCfmMdMdLevel |
Dot1agCfmMDLevel |
|
| |
dot1agCfmMdMhfCreation |
Dot1agCfmMhfCreation |
|
| |
dot1agCfmMdMhfIdPermission |
Dot1agCfmIdPermission |
|
| |
dot1agCfmMdMaTableNextIndex |
Dot1afCfmIndexIntegerNextFree |
|
| |
dot1agCfmMdRowStatus |
RowStatus |
|
| Dot1agCfmMaEntry |
|
| SEQUENCE |
|
|
|
| |
dot1agCfmMaIndex |
Unsigned32 |
|
| |
dot1agCfmMaPrimaryVlanId |
VlanIdOrNone |
|
| |
dot1agCfmMaFormat |
Dot1agCfmMaintAssocNameType |
|
| |
dot1agCfmMaName |
Dot1agCfmMaintAssocName |
|
| |
dot1agCfmMaMhfCreation |
Dot1agCfmMhfCreation |
|
| |
dot1agCfmMaCompIdPermission |
Dot1agCfmIdPermission |
|
| |
dot1agCfmMaCcmInterval |
Dot1agCfmCcmInterval |
|
| |
dot1agCfmMaRowStatus |
RowStatus |
|
| Dot1agCfmMaVlanListEntry |
|
| SEQUENCE |
|
|
|
| |
dot1agCfmMaVlanListIdentifier |
VlanId |
|
| |
dot1agCfmMaVlanListRowStatus |
RowStatus |
|
| Dot1agCfmMaMepListEntry |
|
| SEQUENCE |
|
|
|
| |
dot1agCfmMaMepListSessionId |
Dot1agCfmSessionId |
|
| |
dot1agCfmMaMepListRowStatus |
RowStatus |
|
| Dot1agCfmMepEntry |
|
| SEQUENCE |
|
|
|
| |
dot1agCfmSessionId |
Dot1agCfmSessionId |
|
| |
dot1agCfmMepIfIndex |
InterfaceIndexOrZero |
|
| |
dot1agCfmMepDirection |
Dot1agCfmMpDirection |
|
| |
dot1agCfmMepPrimaryVid |
Unsigned32 |
|
| |
dot1agCfmMepActive |
TruthValue |
|
| |
dot1agCfmMepFngState |
Dot1agCfmFngState |
|
| |
dot1agCfmMepCciEnabled |
TruthValue |
|
| |
dot1agCfmMepCcmLtmPriority |
Unsigned32 |
|
| |
dot1agCfmMepMacAddress |
MacAddress |
|
| |
dot1agCfmMepLowPrDef |
Dot1agCfmLowestAlarmPri |
|
| |
dot1agCfmMepHighestPrDefect |
Dot1agCfmHighestDefectPri |
|
| |
dot1agCfmMepDefects |
Dot1agCfmMepDefects |
|
| |
dot1agCfmMepCciSentCcms |
Counter32 |
|
| |
dot1agCfmMepId |
Unsigned32 |
|
| |
dot1agCfmMepPortName |
DisplayString |
|
| |
dot1agCfmMepLbrIn |
Counter32 |
|
| |
dot1agCfmMepLbrInOutOfOrder |
Counter32 |
|
| |
dot1agCfmMepLbrBadMsdu |
Counter32 |
|
| |
dot1agCfmMepLtmNextSeqNumber |
Unsigned32 |
|
| |
dot1agCfmMepUnexpLtrIn |
Counter32 |
|
| |
dot1agCfmMepLbrOut |
Counter32 |
|
| |
dot1agCfmMepRowStatus |
RowStatus |
|
| |
dot1agCfmMepCcCheckFlag |
TruthValue |
|
| |
dot1agCfmMepclientLevel |
Dot1agCfmClientLevel |
|
| |
dot1agCfmMepAISEnableFlag |
TruthValue |
|
| |
dot1agCfmMepLCKEnableFlag |
TruthValue |
|
| |
dot1agCfmMepNearLost |
Counter32 |
|
| |
dot1agCfmMepFarLost |
Counter32 |
|
| |
dot1agCfmMepDaly |
Counter32 |
|
| |
dot1agCfmMepDalyChg |
Counter32 |
|
| |
dot1agCfmMepDLMEnableFlag |
TruthValue |
|
| |
dot1agCfmMepLMMEnableFlag |
TruthValue |
|
| |
dot1agCfmMepDMMEnableFlag |
TruthValue |
|
| |
dot1agCfmMep1DMEnableFlag |
TruthValue |
|
| |
dot1agCfmMepProcDMMEnableFlag |
TruthValue |
|
| |
dot1agCfmMepProc1DMEnableFlag |
TruthValue |
|
| |
dot1agCfmMepLMMRMepId |
Unsigned32 |
|
| |
dot1agCfmMepLMMInterval |
Unsigned32 |
|
| |
dot1agCfmMepLMMRequireTime |
Unsigned32 |
|
| |
dot1agCfmMepDMMRMepId |
Unsigned32 |
|
| |
dot1agCfmMepDMMInterval |
Unsigned32 |
|
| |
dot1agCfmMepDMMRequireTime |
Unsigned32 |
|
| |
dot1agCfmMepDMMFrameSize |
Unsigned32 |
|
| |
dot1agCfmMep1DMRMepId |
Unsigned32 |
|
| |
dot1agCfmMep1DMInterval |
Unsigned32 |
|
| |
dot1agCfmMep1DMRequireTime |
Unsigned32 |
|
| |
dot1agCfmMep1DMFrameSize |
Unsigned32 |
|
| |
dot1agCfmMepProcDMMRMepId |
Unsigned32 |
|
| |
dot1agCfmMepProcDMMInterval |
Unsigned32 |
|
| |
dot1agCfmMepProcDMMFrameSize |
Unsigned32 |
|
| |
dot1agCfmMepProc1DMRMepId |
Unsigned32 |
|
| |
dot1agCfmMepProc1DMInterval |
Unsigned32 |
|
| |
dot1agCfmMepProc1DMFrameSize |
Unsigned32 |
|
| |
dot1agCfmMepAISInterval |
Unsigned32 |
|
| |
dot1agCfmMepLCKInterval |
Unsigned32 |
|
| |
dot1agCfmMepDLMCountOamFlag |
TruthValue |
|
| |
dot1agCfmMepLMMCountOamFlag |
TruthValue |
|
| Dot1agCfmLtrEntry |
|
| SEQUENCE |
|
|
|
| |
dot1agCfmLtrSeqNumber |
Unsigned32 |
|
| |
dot1agCfmLtrReceiveOrder |
Unsigned32 |
|
| |
dot1agCfmLtrTtl |
Unsigned32 |
|
| |
dot1agCfmLtrForwarded |
TruthValue |
|
| |
dot1agCfmLtrTerminalMep |
TruthValue |
|
| |
dot1agCfmLtrLastEgressIdentifier |
OCTET STRING |
|
| |
dot1agCfmLtrNextEgressIdentifier |
OCTET STRING |
|
| |
dot1agCfmLtrRelay |
Dot1agCfmRelayActionFieldValue |
|
| |
dot1agCfmLtrIngress |
Dot1agCfmIngressActionFieldValue |
|
| |
dot1agCfmLtrIngressMac |
MacAddress |
|
| |
dot1agCfmLtrEgress |
Dot1agCfmEgressActionFieldValue |
|
| |
dot1agCfmLtrEgressMac |
MacAddress |
|
| Dot1agCfmMepDbEntry |
|
| SEQUENCE |
|
|
|
| |
dot1agCfmMepDbRSessionId |
Dot1agCfmSessionId |
|
| |
dot1agCfmMepDbMacAddress |
MacAddress |
|
| |
dot1agCfmMepDbRdi |
TruthValue |
|
| |
dot1agCfmMepDbNearLost |
Counter32 |
|
| |
dot1agCfmMepDbFarLost |
Counter32 |
|
| |
dot1agCfmMepDbDaly |
Counter32 |
|
| |
dot1agCfmMepDbDalyChg |
Counter32 |
|
| |
dot1agCfmMepDbProcDaly |
Counter32 |
|
| |
dot1agCfmMepDbProcDalyChg |
Counter32 |
|
| dot1agCfmMdEntry |
1.3.6.1.4.1.3902.3.120.1.1.2.1 |
| The Maintenance Domain table entry. This entry is not lost
upon reboot. It is backed up by stable storage.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
Dot1agCfmMdEntry |
|
|
| dot1agCfmMaEntry |
1.3.6.1.4.1.3902.3.120.1.2.1.1 |
| The MA table entry. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
Dot1agCfmMaEntry |
|
|
| dot1agCfmMaIndex |
1.3.6.1.4.1.3902.3.120.1.2.1.1.1 |
| Index of the MA table dot1agCfmMdMaTableNextIndex needs to
be inspected to find an available index for row-creation.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
1..32 |
|
| dot1agCfmMaVlanListEntry |
1.3.6.1.4.1.3902.3.120.1.2.2.1 |
| The known Vlan table entry. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
Dot1agCfmMaVlanListEntry |
|
|
| dot1agCfmMaMepListEntry |
1.3.6.1.4.1.3902.3.120.1.2.3.1 |
| The known MEPS table entry. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
Dot1agCfmMaMepListEntry |
|
|
| dot1agCfmMepTable |
1.3.6.1.4.1.3902.3.120.1.3.1 |
| The Maintenance Association End Point (MEP) table.
Each row in the table represents a different MEP. A MEP is
an actively managed CFM entity, associated with a specific
DSAP of a Service Instance, which can generate and receive
CFM PDUs and track any responses. It is an end point of a
single Maintenance Association, and is an endpoint of a
separate Maintenance Entity for each of the other MEPs in
the same Maintenance Association (802.1ag clause 3.18).
This table uses three indices. The first two indices are the
indices of the Maintenance Domain and MA tables, the reason
being that a MEP is always related to an MA and Maintenance
Domain.
The Transmit Loopback table. Entries in this table are
created/removed at the same time than entries in the MEP
table are created/removed.
The MEP table also stores all the managed objects for sending
LBM and LTM.
*LBM Managed objects
LBM Managed objects in the MEP table
enables the management entity to initiate
transmission of Loopback messages. It will signal the MEP
that it should transmit some number of Loopback messages
and detect the detection (or lack thereof) of the
corresponding Loopback messages.
Steps to use entries in this table:
1) Wait for dot1agCfmMepTransmitLbmStatus value to be
'ready'. To do this do this sequence:
a. an SNMP GET for both SnmpSetSerialNo and
dot1agCfmMepTransmitLbmStatus objects (in same SNMP
PDU).
b. Check if value for dot1agCfmMepTransmitLbmStatus is
'ready'
- if not, wait x seconds, go to step a above.
- if yes, save the value of SnmpSetSerialNo and go
to step 2) below
2) Change dot1agCfmMepTransmitLbmStatus value from 'ready' to
'notReady' to ensure no other management entity will use
the service. In order to not disturb a possible other NMS
do this by sending an SNMP SET for both SnmpSetSerialNo
and dot1agCfmMepTransmitLbmStatus objects (in same SNMP
PDU, and make sure SNmpSetSerialNo is the first varBind).
For the SnmpSetSerialNo varBind, use the value that you
obtained in step 1)a.. This ensures that two cooperating
NMSes will not step on each others toes.
3) Setup the different data to be sent (number of messages,
optional TLVs,...).
4) Record the current values of dot1agCfmMepLbrIn,
dot1agCfmMepLbrInOutOfOrder, and dot1agCfmMepLbrBadMsdu.
6) Change dot1agCfmMepTransmitLbmStatus value from 'notReady'
to 'transmit' to initiate transmission of Loopback
messages.
7) Check the value of dot1agCfmMepTransmitLbmResultOK to
find out if the operation was successfully initiated or
not.
8) Monitor the value of dot1agCfmMepTransmitLbmMessages.
When it reaches 0, the last LBM has been transmitted.
Wait an additional 5 seconds to ensure that all LBRs have
been returned.
9) Compare dot1agCfmMepLbrIn, dot1agCfmMepLbrInOutOfOrder,
and dot1agCfmMepLbrBadMsdu to their old values from step
4, above, to get the results of the test.
10) Change the dot1agCfmMepTransmitLbmStatus value back to
'ready' to allow other management entities to use the
table.
*LTM Managed objects
The LTM Managed objects in the MEP table are used in a manner
similar to that described for LBM transmission, above. Upon
successfully initiating the transmission, the variables
dot1agCfmMepTransmitLtmSeqNumber and
dot1agCfmMepTransmitLtmEgressIdentifier return the information
required to recover the results of the LTM from the
dot1agCfmLtrTable.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
SEQUENCE OF |
|
|
| |
|
Dot1agCfmMepEntry |
|
| dot1agCfmMepEntry |
1.3.6.1.4.1.3902.3.120.1.3.1.1 |
| The MEP table entry |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
Dot1agCfmMepEntry |
|
|
| dot1agCfmMepDLMCountOamFlag |
1.3.6.1.4.1.3902.3.120.1.3.1.1.66 |
| Transmit and receive counters do not count the OAM frames
transmitted or received by the MEP at the MEP's MEG Level
normally. This flag set true provide rules of countting OAM
frames at the MEP's MEG Level as below:
A. For single-ended ETH-LM, both counters do not need to
count on-demand OAM frames for ETH-LB, ETH-LT, ETH-LM,
ETH-DM, and ETH-Test. Instead, proactive OAM frames for
ETH-CC and ETH-APS need to be counted. For dual-ended
ETH-LM, the counters do not need to count on-demand OAM
frames for ETH-LB, ETH-LT, ETH-LM, ETH-DM, and ETH-Test
and proactive OAM frames for ETH-CC. However, proactive
OAM frames for ETH-APS need to be counted.
B. As OAM frames for ETH-AIS and ETH-LCK are only sent in
the defect conditions where the result of loss measurements
is invalid, it is unnecessary to count these frames.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
TruthValue |
|
|
| dot1agCfmMepLMMCountOamFlag |
1.3.6.1.4.1.3902.3.120.1.3.1.1.67 |
| Transmit and receive counters do not count the OAM frames
transmitted or received by the MEP at the MEP's MEG Level
normally. This flag set true provide rules of countting OAM
frames at the MEP's MEG Level as below:
A. For single-ended ETH-LM, both counters do not need to
count on-demand OAM frames for ETH-LB, ETH-LT, ETH-LM,
ETH-DM, and ETH-Test. Instead, proactive OAM frames for
ETH-CC and ETH-APS need to be counted. For dual-ended
ETH-LM, the counters do not need to count on-demand OAM
frames for ETH-LB, ETH-LT, ETH-LM, ETH-DM, and ETH-Test
and proactive OAM frames for ETH-CC. However, proactive
OAM frames for ETH-APS need to be counted.
B. As OAM frames for ETH-AIS and ETH-LCK are only sent in
the defect conditions where the result of loss measurements
is invalid, it is unnecessary to count these frames.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
TruthValue |
|
|
| dot1agCfmLtrEntry |
1.3.6.1.4.1.3902.3.120.1.3.2.1 |
| The Linktrace Reply table entry. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
Dot1agCfmLtrEntry |
|
|
| dot1agCfmMepDbEntry |
1.3.6.1.4.1.3902.3.120.1.3.3.1 |
| The MEP Database table entry. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
Dot1agCfmMepDbEntry |
|
|
| dot1agCfmMipEntry |
1.3.6.1.4.1.3902.3.120.1.3.5.1 |
| The MIP table entry |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
Dot1agCfmMipEntry |
|
|
| dot1agCfmPwMipEntry |
1.3.6.1.4.1.3902.3.120.1.5.1.1 |
| The PW MIP table entry |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
Dot1agCfmPwMipEntry |
|
|
