IEEE802171-CFM-MIB

TEXTUAL-CONVENTION

An integer which may be used as a new Index in a table. The special value of 0 indicates that no more new entries can be created in the relevant table. When a MIB is used for configuration, an object with this SYNTAX always contains a legal value (if non-zero) for an index that is not currently used in the relevant table. The Command Generator (Network Management Application) reads this variable and uses the (non-zero) value read when creating a new row with an SNMP SET. When the SET is performed, the Command Responder (agent) must determine whether the value is indeed still unused; Two Network Management Applications may attempt to create a row (configuration entry) simultaneously and use the same value. If it is currently unused, the SET succeeds and the Command Responder (agent) changes the value of this object, according to an implementation-specific algorithm. If the value is in use, however, the SET fails. The Network Management Application must then re-read this variable to obtain a new usable value. An OBJECT-TYPE definition using this SYNTAX MUST specify the relevant table for which the object is providing this functionality.

TEXTUAL-CONVENTION

Indicates the interval at which CCMs are sent by a MEP. The possible values are: intervalInvalid(0) No CCMs are sent (disabled). interval300Hz(1) CCMs are sent every 3 1/3 milliseconds (300Hz). interval10ms(2) CCMs are sent every 10 milliseconds. interval100ms(3) CCMs are sent every 100 milliseconds. interval1s(4) CCMs are sent every 1 second. interval10s(5) CCMs are sent every 10 seconds. interval1min(6) CCMs are sent every minute. interval10min(7) CCMs are sent every 10 minutes. Note: enumerations start at zero to match the 'CCM Interval field' protocol field.

TEXTUAL-CONVENTION

While making the MIP creation evaluation described in 802.1ag clause 22.2.3, the management entity can encounter errors in the configuration. These are possible errors that can be encountered: CFMleak(0) MA x is associated with a specific VID list, one or more of the VIDs in MA x can pass through the Bridge Port, no Down MEP is configured on any Bridge Port for MA x, and some other MA y, at a higher MD Level than MA x, and associated with at least one of the VID(s) also in MA x, does have a MEP configured on the Bridge Port. conflictingVids(1) MA x is associated with a specific VID list, an Up MEP is configured on MA x on the Bridge Port, and some other MA y, associated with at least one of the VID(s) also in MA x, also has an Up MEP configured on some Bridge Port. ExcessiveLevels(2) The number of different MD Levels at which MIPs are to be created on this port exceeds the Bridge's capabilities (see subclause 22.3). OverlappedLevels(3) A MEP is created for one VID at one MD Level, but a MEP is configured on another VID at that MD Level or higher, exceeding the Bridge's capabilities.

TEXTUAL-CONVENTION

Possible values returned in the egress action field

TEXTUAL-CONVENTION

Indicates the diferent states of the MEP Fault Notification Generator State Machine. fngReset(1) No defect has been present since the dot1agCfmMepFngResetTime timer expired, or since the state machine was last reset. fngDefect(2) A defect is present, but not for a long enough time to be reported (dot1agCfmMepFngAlarmTime). fngReportDefect(3) A momentary state during which the defect is reported by sending a dot1agCfmFaultAlarm notification, if that action is enabled. fngDefectReported(4) A defect is present, and some defect has been reported. fngDefectClearing(5) No defect is present, but the dot1agCfmMepFngResetTime timer has not yet expired.

TEXTUAL-CONVENTION

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(1) no defects since FNG_RESET defRDICCM(2) DefRDICCM defMACstatus(3) DefMACstatus defRemoteCCM(4) DefRemoteCCM defErrorCCM(5) DefErrorCCM defXconCCM(6) DefXconCCM

TEXTUAL-CONVENTION

Possible values returned in the ingress action field.

TEXTUAL-CONVENTION

An enumerated value from the Interface Status TLV from the last CCM received from the last MEP. It indicates the status of the Interface within which the MEP transmitting the CCM is configuredr, or the next lower Interface in the Interface Stack, if the MEP is not configured within an Interface. isNoInterfaceSatatusTLV(0) Indicates either that no CCM has been received or that no interface status TLV was present in the last CCM received. isUp(1) The interface is ready to pass packets. isDown(2) The interface cannot pass packets isTesting(3) The interface is in some test mode. isUnknown(4) The interface status cannot be determined for some reason. isDormant(5) The interface is not in a state to pass packets but is in a pending state, waiting for some external event. isNotPresent(6) Some component of the interface is missing isLowerLayerDown(7) The interface is down due to state of the lower layer interfaces NOTE: A 0 value is used for isNoInterfaceSatatusTLV, so that these code points can be kept consistent with new code points added to ifOperStatus in the IF-MIB.

TEXTUAL-CONVENTION

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 noDef(6) No defects are to be reported;

TEXTUAL-CONVENTION

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

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..47)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 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 Mainteanance Domain name and Maintenance Assication 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

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.

TEXTUAL-CONVENTION

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 Maintenenace 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 identifying the Maintenance Domain Level (MD Level). Higher numbers correspond to higher Maintenance Domains, those with the greatest physical reach, with the highest values for customers' CFM packets. Lower numbers correspond to lower Maintenance Domains, those with more limited physical reach, with the lowest values for single bridges or physical links. The value (-1) is reserved to indicate that no MA Level has been assigned.

TEXTUAL-CONVENTION

Maintenance association End Point Identifier (MEPID): A small integer, unique over a given Maintenance Association, identifying a specific MEP.

TEXTUAL-CONVENTION

Maintenance association End Point Identifier (MEPID): A small integer, unique over a given Maintenance Association, identifying a specific MEP. The special value 0 is allowed to indicate special cases, for example that no MEPID is configured in a given Maintenance Assosiation point. Whenever an object is defined with this SYNTAX, then the DESCRIPTION clause of such an object MUST specify what the special value of 0 means.

TEXTUAL-CONVENTION

Indicates if the Management Entity can create MHFs. The valid values are: defMHFnone(1) No MHFs can be created for this VID. defMHFdefault(2) MHFs can be created on this VID on any Bridge port through which this VID can pass. defMHFexplicit(3) MHFs can be created for this VID only on Bridge ports through which this VID can pass, and only if a MEP is created at some lower MA Level.

TEXTUAL-CONVENTION

Indicates the direction in which the Maintenance association (MEP or MIP) faces on the bridge port: down(1) Sends Continuity Check Messages away from the MAC Relay Entity. up(2) Sends Continuity Check Messages towards the MAC Relay Entity.

TEXTUAL-CONVENTION

An enumerated value from he Port Status TLV from the last CCM received from the last MEP. It indicates the ability of the Bridge Port on which the transmitting MEP resides to pass ordinary data, regardless of the status of the MAC (Table 21-10). psNoPortStateTLV(0) Indicates either that no CCM has been received or that no port status TLV was present in the last CCM received. psBlocked(1) Ordinary data cannot pass freely through the port on which the remote MEP resides. Value of enableRmepDefect is equal to false. psUp(2): Ordinary data can pass freely through the port on which the remote MEP resides. Value of enableRmepDefect is equal to true. NOTE: A 0 value is used for psNoPortStateTLV, so that additional code points can be added in a manner consistent with the Dot1agCfmInterfaceStatus textual convention.

TEXTUAL-CONVENTION

Possible values the Relay action field can take.

TEXTUAL-CONVENTION

Operational state of the remote MEP state machine. This state machine motitors the reception of valid CCMs from a remote MEP with a specific MEPID. It uses a timer that expires in 3.5 times the lengh of time indicated by the dot1agCfmMaCcmInterval object. rMepIdle(1) Momentary state during reset. rMepStart(2) The timer has not expired since the state machine was reset, and no valid CCM has yet been received. rMepFailed(3) The timer has expired, both since the state machine was reset, and since a valid CCM was received. rMepOk(4) The timer has not expired since a valid CCM was received.

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

There is one CFM Stack Managed object per bridge. It permits the retrieval of information about the maintenance Points configured on any given interface.

OBJECT-TYPE

The Stack table entry

OBJECT-TYPE

This object represents the Bridge Port or aggregated port on which MEPs or MHFs might be configured.

OBJECT-TYPE

Direction in which the MP faces on the Bridge Port

OBJECT-TYPE

If an MEP is configured, the MEPID, else 0

OBJECT-TYPE

MAC address of the MP.

OBJECT-IDENTITY

OBJECT-TYPE

The Default MD Level Managed Object controls MHF creation for VIDs that are not attached to a specific Maintenance Association Managed Object. The writable objects in this table need to be persistent upon reboot or restart of a device.

OBJECT-TYPE

The Default MD Level table entry.

OBJECT-TYPE

The index to the default MD Level table

OBJECT-TYPE

This is a VLAN ID monitored by MA.

OBJECT-TYPE

A value indicating if the Management entity can create MHFs (MIP Half Function) for this VID.

OBJECT-TYPE

The MD Level at which MHFs are to be created, or -1 if defMHFnone.

OBJECT-IDENTITY

OBJECT-TYPE

The CFM Configuration Error List table provides a list of Interfaces and VIDs that are incorrectly configured.

OBJECT-TYPE

The Config Error List Table entry

OBJECT-TYPE

The vlan ID of the vlan with errored interfaces.

OBJECT-TYPE

This object is the IfIndex of the interface.

OBJECT-TYPE

A vector of Boolean error conditions from 22.2.4, any of which may be true: 1) CFMleak; 2) ConflictingVids; 3) ExcessiveLevels; 4) OverlappedLevels.

OBJECT-IDENTITY

OBJECT-TYPE

This object contains an unused value for dot1agCfmMdIndex in the dot1agCfmMdTable, or a zero to indicate that none exist.

OBJECT-TYPE

The MaintenanceDomain table. Each row in the table represents a different maintenance domain. A Maintenace domain is described in 802.1ag (3.22) as the network or the part of the network for which faults in connectivity are to be managed. The boundary of a Maintenance Domain is defined by a set of DSAPs, each of which can become a point of connectivity to a service instance.

OBJECT-TYPE

The Maintenance Domain table entry. This entry is not lost upon reboot. It is backed up by stable storage.

OBJECT-TYPE

The index to the maintenance domain table. dot1agCfmMdTableNextIndex needs to be inspected to find an available index for row-creation. Referential integrity is required i.e. the index needs to be persistent upon a reboot or restart of a device. The index can never be reused for other maintenance domain. The index value should keep increasing up to the time that they wrap around. This is to facilitate access control based on OID.

OBJECT-TYPE

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

OBJECT-TYPE

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.

OBJECT-TYPE

The Maintenance Domain Level.

OBJECT-TYPE

Enumerated value indicating whether the management entity can create MHFs (MIP Half Function) for this Maintenance Domain.

OBJECT-TYPE

The transportDomain for the address to which Fault Alarms are to be transmitted. Typical values will be one of (not all inclusive) list: transportDomainUdpIpv4 (from TRANSPORT-ADDRESS-MIB) transportDomainUdpIpv6 (from TRANSPORT-ADDRESS-MIB) snmpIeee802Domain (from SNMP-IEEE802-TM-MIB) The value 'zeroDotZero' indicates 'Fault Alarms are not to be transmitted', in which case the related object of SYNTAX TransportAddress must have a zero-length OCTET STRING as a value.

OBJECT-TYPE

The transportAddress to which Fault Alarms are to be transmitted to. The type/format of this object is determined by the value of the dot1agCfmMdFaultAlarmDestDomain. If the dot1agCfmMdFaultAlarmDestDomain object has a value of 'zeroDotZero' (indicating 'Fault Alarms are not to be transmitted') then this object should have a value of a zero-length OCTET STRING.

OBJECT-TYPE

The status of the row. The writable columns in a row can not be changed if the row is active. All columns must have a valid value before a row can be activated.

OBJECT-IDENTITY

OBJECT-TYPE

Value to be used as the index of the MA table when the management entity wants to create a new row in the table.

OBJECT-TYPE

The Maintenance Association table. Each row in the table represents an MA. An MA is a set of MEPs, each configured with a single service instance. Creation of a Service Instance establishes a connectionless association among the selected DSAPs. Configuring a Maintenance association End Point (MEP) at each of the DSAPs creates a Maintenance Association (MA) to monitor that connectionless connectivity. The MA is identified by a Short MA Name that is unique within the Maintenance Domain and chosen to facilitate easy identification of the Service Instance. Together, the Maintenance Domain Name and the Short MA Name form the Maintenance Association Identifier (MAID) that is carried in CFM Messages to identify incorrect connectivity among Service Instances. A small integer, the Maintenance association End Point Identifier (MEPID), identifies each MEP among those configured on a single MA (802.1ag clauses 3.17 and 18.2). This table uses two indices, first index is the index of the Maintenance Domain table. The writable objects in this table need to be persistent upon reboot or restart of a device.

OBJECT-TYPE

The MA table entry.

OBJECT-TYPE

Index of the MA table dot1agCfmMaTableNextIndex needs to be inspected to find an available index for row-creation 1..4094 -> describes an MA entry associated with a VID 16777217..4294967295 -> describes an MA entry not associated with any VID

OBJECT-TYPE

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

OBJECT-TYPE

The Short Maintenance Association name. The type/format of this object is determined by the value of the dot1agCfmMaNameType object.

OBJECT-TYPE

Indicates if the Management entity can create MHFs (MIP Half Function) for this MA.

OBJECT-TYPE

Interval between CCM transmissions to be used by all MEPs in the MA.

OBJECT-TYPE

The transportDomain for the address to which Fault Alarms are to be transmitted. Typical values will be one of (not all inclusive) list: transportDomainUdpIpv4 (from TRANSPORT-ADDRESS-MIB) transportDomainUdpIpv6 (from TRANSPORT-ADDRESS-MIB) snmpIeee802Domain (from SNMP-IEEE802-TM-MIB) The value 'zeroDotZero' indicates 'Fault Alarms are not to be transmitted', in which case the related object of SYNTAX transportAddress must have a zero-length OCTET STRING as a value.

OBJECT-TYPE

The transportAddress to which Fault Alarms are to be transmitted to. The type/format of this object is determined by the value of the dot1agCfmMaFaultAlarmDestDomain. If the dot1agCfmMaFaultAlarmDestDomain object has a value of 'zeroDotZero' (indicating 'Fault Alarms are not to be transmitted') then this object should have a value of a zero-length OCTET STRING.

OBJECT-TYPE

True indicate that the MA is associated with more that one VID. False indicates that the MA is associated with only one VID or no VID. This value should be false for MAs with an index greater than 16777216.

OBJECT-TYPE

The status of the row. The writable columns in a row can not be changed if the row is active. All columns must have a valid value before a row can be activated.

OBJECT-TYPE

If an MA is associated with multiple VIDs, then this table contains all the VIDs associated with the MA other than the primary VID. The writable objects in this table need to be persistent upon reboot or restart of a device.

OBJECT-TYPE

The Maintenance Association VLAN table entry.

OBJECT-TYPE

This is a VLAN ID of the vlan monitored by the MA. VID 0 means that the MA is not associated with any VLAN.

OBJECT-TYPE

The status of the row. The writable columns in a row can not be changed if the row is active. All columns must have a valid value before a row can be activated.

OBJECT-TYPE

List of MEPIDs (in any bridge) that belong to the same MA. Clause 12.14.6.1.3 specifies that a list of MEPIDs in all bridges in that MA, but since SNMP SMI does not allow to state in a MIB that an object in a table is an array, the information has to be stored in another table with two indices, being the first index, the index of the table that contains the list or array.

OBJECT-TYPE

The known MEPS table entry.

OBJECT-TYPE

MEPID

OBJECT-TYPE

The status of the row. Read SNMPv2-TC (RFC1903) for an explanation of the possible values this object can take.

OBJECT-IDENTITY

OBJECT-TYPE

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, goto 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 sucessfully 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.

OBJECT-TYPE

The MEP table entry

OBJECT-TYPE

Integer that is unique among all the MEPs in the same MA. Other definition is: a small integer, unique over a given Maintenance Association, identifying a specific Maintenance association End Point (3.19). MEP Identifier is also known as the MEPID.

OBJECT-TYPE

This object is the interface index of the interface eiter a bridge port, or an aggregated IEEE 802.1 link within a bridge port, to which the MEP is attached.

OBJECT-TYPE

The direction in which the MEP faces on the Bridge port.

OBJECT-TYPE

An integer indicating the Primary VID of the MEP, always one of the VIDs assigned to the MEP's MA. The value 0 indicates that either the Primary VID is that of the MEP's MA, or that the MEP's MA is associated with no VID.

OBJECT-TYPE

Administrative state of the MEP A Boolean indicating the administrative state of the MEP. True indicates that the MEP is to function normally, and false that it is to cease functioning.

OBJECT-TYPE

Current state of the MEP Fault Notification Generator State Machine.

OBJECT-TYPE

If set to true, the MEP will generate CCM messages.

OBJECT-TYPE

The priority value for CCMs and LTMs transmitted by the MEP. Default Value in the highest priority value allowed to pass through the bridge port for any of this MEPs VIDs. The management entity can obtain the default valuefor this variable from the priority regeneration table by extracting the highest priority value in this table on this MEPs bridge port. (1 is lowest, then 2, then 0, then 3-7).

OBJECT-TYPE

MAC address of the MEP.

OBJECT-TYPE

The transportDomain for the address to which Fault Alarms are to be transmitted. Typical values will be one of (not all inclusive) list: transportDomainUdpIpv4 (from TRANSPORT-ADDRESS-MIB) transportDomainUdpIpv6 (from TRANSPORT-ADDRESS-MIB) snmpIeee802Domain (from SNMP-IEEE802-TM-MIB) The value 'zeroDotZero' indicates 'Fault Alarms are not to be transmitted', in which case the related object of SYNTAX transportAddress must have a zero-length OCTET STRING as a value.

OBJECT-TYPE

The transportAddress to which Fault Alarms (12.14.7.7) are to be transmitted to. The type/format of this object is determined by the value of dot1agCfmMepFaultAlarmDestDomain. If the dot1agCfmMepFaultAlarmDestDomain object has a value of 'zeroDotZero' (indicating 'Fault Alarms are not specified') then this object should have a value of a zero-length OCTET STRING. If 'Fault Alarms are not specified', the address used is that from the Maintenance Association managed object (12.14.6.1.3:e).

OBJECT-TYPE

An integer value specifying the lowest priority defect that is allowed to generate fault alarm.

OBJECT-TYPE

The time that defects must be present before a Fault Alarm is issued (fngAlarmTime. 20.33.3) (default 2.5s).

OBJECT-TYPE

The time that defects must be absent before re-enabling a Fault Alarm (fngResetTime, 20.33.4) (default 10s).

OBJECT-TYPE

The highest priority defect that has been present since the MEPs Fault Notification Generator State Machine was last in the FNG_RESET state.

OBJECT-TYPE

A Boolean flag indicating that some other MEP in this MEP's MA is transmitting the RDI bit.

OBJECT-TYPE

A Boolean flag (someMACstatusDefect, 20.33.6) indicating that a Port Status TLV (21.5.4) or Interface Status TLV (21.5.5) is indicating an error condition (can trigger DefMACstatus).

OBJECT-TYPE

A Boolean flag indicating that CCMs are not being received from at least one of the configured remote MEPs.

OBJECT-TYPE

A Boolean flag indicating that a stream of erroneous CCMs is being received from some MEP in this MEP's MA.

OBJECT-TYPE

A Boolean flag indicating that a stream of CCMs is being received from a MEP that may be in some other MA.

OBJECT-TYPE

The last-received CCM that triggered an DefErrorCCM fault.

OBJECT-TYPE

The last-received CCM that triggered a DefXconCCM fault.

OBJECT-TYPE

The total number of out-of-sequence CCMs received from all remote MEPs.

OBJECT-TYPE

Total number of Continuity Check messages transmitted.

OBJECT-TYPE

Next sequence number/transaction identifier to be sent in a Loopback message. This sequence number can be zero because it wraps around.

OBJECT-TYPE

Total number of valid, in-order Loopback Replies received.

OBJECT-TYPE

The total number of valid, out-of-order Loopback Replies received.

OBJECT-TYPE

(optional) The total number of LBRs received whose mac_service_data_unit did not match (except for the OpCode) that of the corresponding LBM (20.2.3).

OBJECT-TYPE

Next transaction identifier/sequence number to be sent in a Linktrace message. This sequence number can be zero because it wraps around.

OBJECT-TYPE

The total number of unexpected LTRs received (20.39.1).

OBJECT-TYPE

Total number of Loopback Replies transmitted.

OBJECT-TYPE

A Boolean flag set to true by the bridge port to indicate that another LBM may be transmitted. Reset to false by the MEP Loopback Initiator State Machine.

OBJECT-TYPE

The Target MAC Address Field to be transmitted: A unicast destination MAC address. This address will be used if the value of the column dot1agCfmMepTransmitLbmDestIsMepId is 'false'.

OBJECT-TYPE

The Maintenance association End Point Identifier of another MEP in the same Maintenance Association to which the LBM is to be sent. This address will be used if the value of the column dot1agCfmMepTransmitLbmDestIsMepId is 'true'.

OBJECT-TYPE

True indicates that MepID of the target MEP is used for Loopback transmission. False indicates that unicast destination MAC address of the target MEP is used for Loopback transmission.

OBJECT-TYPE

The number of Loopback messages to be transmitted.

OBJECT-TYPE

An arbitrary amount of data to be included in the Data TLV, if the Data TLV is selected to be sent.

OBJECT-TYPE

Priority. 3 bit value to be used in the VLAN tag, if present in the transmitted frame. The default value is CCM priority.

OBJECT-TYPE

Drop Enable bit value to be used in the VLAN tag, if present in the transmitted frame. For more information about VLAN Drop Enable, please check IEEE 802.1ad.

OBJECT-TYPE

Indicates the result of the operation: - true The Loopback Message(s) will be (or hasbeen) sent. - false The Loopback Message(s) will not be sent.

OBJECT-TYPE

The Loopback Transaction Identifier (dot1agCfmMepNextLbmTransId) of the first LBM (to be) sent. The value returned is undefined if dot1agCfmMepTransmitLbmResultOK is false.

OBJECT-TYPE

A Boolean flag set to true by the bridge port to indicate that another LTM may be transmitted. Reset to false by the MEP Linktrace Initiator State Machine.

OBJECT-TYPE

The flags field for LTMs transmitted by the MEP.

OBJECT-TYPE

The Target MAC Address Field to be transmitted: A unicast destination MAC address. This address will be used if the value of the column dot1agCfmMepTransmitLtmTargetIsMepId is 'false'.

OBJECT-TYPE

An indication of the Target MAC Address Field to be transmitted: The Maintenance association End Point Identifier of another MEP in the same Maintenance Association This address will be used if the value of the column dot1agCfmMepTransmitLtmTargetIsMepId is 'true'.

OBJECT-TYPE

True indicates that MepID of the target MEP is used for Linktrace transmission. False indicates that unicast destination MAC address of the target MEP is used for Loopback transmission.

OBJECT-TYPE

The LTM TTL field. Default value, if not specified, is 64. The TTL field indicates the number of hops remaining to the LTM. Decremented by 1 by each Linktrace Responder that handles the LTM. The decremented value is returned in the LTR. If 0 on input, the LTM is discarded. If 0 on output, the LTM is not transmitted to the next hop.

OBJECT-TYPE

Indicates the result of the operation: - true The Linktrace Message will be (or has been) sent. - false The Linktrace Message will not be sent

OBJECT-TYPE

The LTM Transaction Identifier (dot1agCfmMepLtmNextSeqNumber) of the LTM sent. The value returned is undefined if dot1agCfmMepTransmitLtmResult is false.

OBJECT-TYPE

Identifies the MEP Linktrace Initiator that is originating, or the Linktrace Responder that is forwarding, this LTM. The low-order six octets contain a 48-bit IEEE MAC address unique to the system in which the MEP Linktrace Initiator or Linktrace Responder resides. The high-order two octets contain a value sufficient to uniquely identify the MEP Linktrace Initiator or Linktrace Responder within that system. For most Bridges, the address of any MAC attached to the Bridge will suffice for the low-order six octets, and 0 for the high-order octets. In some situations, e.g. if multiple virtual Bridges utilizing emulated LANs are implemented in a single physical system, the high-order two octets can be used to differentiate among the transmitting entities. The value returned is undefined if dot1agCfmMepTransmitLtmResult is false.

OBJECT-TYPE

The status of the row. The writable columns in a row can not be changed if the row is active. All columns must have a valid value before a row can be activated.

OBJECT-TYPE

This table extends the MEP table and contains a list of Linktrace replies received by a specific MEP in response to a linktrace message. SNMP SMI does not allow to state in a MIB that an object in a table is an array. The solution is to take the index (or indices) of the first table and add one or more indices.

OBJECT-TYPE

The LinktraceReply table entry.

OBJECT-TYPE

Transaction identifier/Sequence number returned by a previous transmit linktrace message command, indicating which LTM's response is going to be returned.

OBJECT-TYPE

An index to distinguish among multiple LTRs with the same LTR Transaction Identifier field value. dot1agCfmLtrReceiveOrder are assigned sequentially from 1, in the order that the Linktrace Initiator received the LTRs.

OBJECT-TYPE

TTL field value for a returned LTR.

OBJECT-TYPE

Indicates if a LTM was forwarded by the repsonding MP, as returned ind the 'FwdYes' flag of the flags field.

OBJECT-TYPE

A boolean value stating whether the forwarded LTM reached a MEP enclosing its MA, as returned in the Terminal MEP flag of the Flags field.

OBJECT-TYPE

An octet field holding the Last Egress Identifier returned in the LTR. The Last Egress Identifier identifies the MEP Linktrace Initiator that originated, or the Linktrace Responder that forwarded, the LTM to which this LTR is the response. This is the same value as the Egress Identifier field of that LTM.

OBJECT-TYPE

An octet field holding the Next Egress Identifier returned in the LTR. The Next Egress Identifier Identifies the Linktrace Responder that transmitted this LTR, and can forward the LTM to the next hop. This is the same value as the Egress Identifier of the forwarded LTM, if any. If the FwdYes bit of the Flags field is false, the contents of this field are undefined, i.e. any value can be transmitted, and the field is ignored by the receiver.

OBJECT-TYPE

Value returned in the Relay Action field.

OBJECT-TYPE

This object specifies the format of the Chassis ID returned in the Sender ID TLV of the LTR, if any. This value is meaningless if the dot1agCfmLtrChassisId has a length of 0.

OBJECT-TYPE

The Chassis ID returned in the Sender ID TLV of the LTR, if any. The format of this object is determined by the value of the dot1agCfmLtrChassisIdSubtype object.

OBJECT-TYPE

Management Address subtype of the bridge transmitting the LTR, if returned in a Sender ID TLV. The value is meaningless if the dot1agCfmLtrManAddress has a length of 0.

OBJECT-TYPE

Management Address information of the bridge transmitting the LTR, if returned in the Sender ID TLV. Some limitation to the size of the TLVs carrying a Manaement Address is needed, as there is no bound on the lengths of AddressFamilyNumbers. 31 octets, the maximum length of LldpManAddress, is long enough for currently deployed systems. This MIB module assumes that SNMP (IETF STD 62) is used along with the Management Address to access the management database.

OBJECT-TYPE

The value returned in the Ingress Action Field of the LTM.

OBJECT-TYPE

MAC address returned in the ingress MAC address field.

OBJECT-TYPE

Format of the Ingress Port ID.

OBJECT-TYPE

Ingress Port ID. The format of this object is determined by the value of the dot1agCfmLtrIngressPortIdSubtype object.

OBJECT-TYPE

The value returned in the Egress Action Field of the LTM.

OBJECT-TYPE

MAC address returned in the egress MAC address field.

OBJECT-TYPE

Format of the egress Port ID.

OBJECT-TYPE

Egress Port ID. The format of this object is determined by the value of the dot1agCfmLtrEgressPortIdSubtype object.

OBJECT-TYPE

All Organization specific TLVs returned in the LTR, if any. Includes all octets including and following the TLV Length field of each TLV, concatenated together.

OBJECT-TYPE

The MEP Database. A database, maintained by every MEP, that maintains received information about other MEPs in the Maintenance Domain. SNMP SMI does not allow to stat in a MIB that an object in a table is an array. The solution is to take the index (or indices) of the first table and add one or more indices.

OBJECT-TYPE

The MEP Database table entry.

OBJECT-TYPE

Maintenance association End Point Identifier of a remote MEP whose information from the MEP Database is to be returned.

OBJECT-TYPE

The operational state of the remote MEP IFF State machines.

OBJECT-TYPE

The time (SysUpTime) at which the IFF Remote MEP state machine last entered either the RMEP_FAILED or RMEP_OK state.

OBJECT-TYPE

The MAC address of the remote MEP.

OBJECT-TYPE

State of the RDI bit in the last received CCM (true for RDI=1), or false if none has been received.

OBJECT-TYPE

An enumerated value of the Port status TLV received in the last CCM from the remote MEP or the default value psNoPortStateTLV indicating either no CCM has been received, or that nor port status TLV was received in the last CCM.

OBJECT-TYPE

An enumerated value of the Interface status TLV received in the last CCM from the remote MEP or the default value isNoInterfaceStatus TLV indicating either no CCM has been received, or that no interface status TLV was received in the last CCM.

OBJECT-TYPE

This object specifies the format of the Chassis ID received in the last CCM.

OBJECT-TYPE

The Chassis ID. The format of this object is determined by the value of the dot1agCfmLtrChassisIdSubtype object.

OBJECT-TYPE

Management Address subtype of the bridge transmitting the CCM.

OBJECT-TYPE

Management Address information of the bridge transmitting the CCM. Some limitation to the size of the TLVs carrying a Manaement Address is needed, as there is no bound on the lengths of AddressFamilyNumbers. 31 octets, the maximum length of LldpManAddress, is long enough for currently deployed systems. This MIB module assumes that SNMP (IETF STD 62) is used along with the Management Address to access the management database.

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY