There is one CFM Stack table per bridge. It permits
the retrieval of information about the Maintenance Points
configured on any given interface.
**NOTE: this object is deprecated due to re-indexing of the
table.
There is one CFM Stack table per bridge. It permits
the retrieval of information about the Maintenance Points
configured on any given interface.
**NOTE: this object is deprecated due to re-indexing of the
table.
Parsed from file IEEE8021-CFM-MIB.my.txt
Company: None
Module: IEEE8021-CFM-MIB
A MEP can detect and report a number of defects, and multiple
defects can be present at the same time. These defects are:
bDefRDICCM(0) A remote MEP is reported the RDI bit in its
last CCM.
bDefMACstatus(1) Either some remote MEP is reporting its
Interface Status TLV as not isUp, or all remote
MEPs are reporting a Port Status TLV that
contains some value other than psUp.
bDefRemoteCCM(2) The MEP is not receiving valid CCMs from at
least one of the remote MEPs.
bDefErrorCCM(3) The MEP has received at least one invalid CCM
whose CCM Interval has not yet timed out.
bDefXconCCM(4) The MEP has received at least one CCM from
either another MAID or a lower MD Level whose
CCM Interval has not yet timed out.
A MEP can detect and report a number of defects, and multiple
defects can be present at the same time. These defects are:
bDefRDICCM(0) A remote MEP is reported the RDI bit in its
last CCM.
bDefMACstatus(1) Either some remote MEP is reporting its
Interface Status TLV as not isUp, or all remote
MEPs are reporting a Port Status TLV that
contains some value other than psUp.
bDefRemoteCCM(2) The MEP is not receiving valid CCMs from at
least one of the remote MEPs.
bDefErrorCCM(3) The MEP has received at least one invalid CCM
whose CCM Interval has not yet timed out.
bDefXconCCM(4) The MEP has received at least one CCM from
either another MAID or a lower MD Level whose
CCM Interval has not yet timed out.
Parsed from file IEEE8021-CFM-MIB.mib
Module: IEEE8021-CFM-MIB
dot1agCfmStackTable OBJECT-TYPE SYNTAX SEQUENCE OF Dot1agCfmStackEntry ACCESS not-accessible STATUS deprecated DESCRIPTION "There is one CFM Stack table per bridge. It permits the retrieval of information about the Maintenance Points configured on any given interface. **NOTE: this object is deprecated due to re-indexing of the table." REFERENCE "802.1ag clauses 12.14.2" ::= { dot1agCfmStack 1 }
Vendor: Cisco Systems
Module: IEEE8021-CFM-MIB (IEEE8021-CFM-MIB-V1SMI.my)
Type: TABLE
Access: not-accessible
Syntax: SEQUENCE OF
Automatically extracted from www.mibdepot.com
dot1agCfmStackTable OBJECT-TYPE SYNTAX SEQUENCE OF Dot1agCfmStackEntry ACCESS not-accessible STATUS deprecated DESCRIPTION "There is one CFM Stack table per bridge. It permits the retrieval of information about the Maintenance Points configured on any given interface. **NOTE: this object is deprecated due to re-indexing of the table." REFERENCE "802.1ag clauses 12.14.2" ::= { dot1agCfmStack 1 }
An OBJECT-TYPE definition using this SYNTAX MUST specify the relevant table for which the object is providing this functionality. " SYNTAX Unsigned32 (0..4294967295) Dot1agCfmMepDefects ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "A MEP can detect and report a number of defects, and multiple defects can be present at the same time. These defects are: bDefRDICCM(0) A remote MEP is reported the RDI bit in its last CCM. bDefMACstatus(1) Either some remote MEP is reporting its Interface Status TLV as not isUp, or all remote MEPs are reporting a Port Status TLV that contains some value other than psUp. bDefRemoteCCM(2) The MEP is not receiving valid CCMs from at least one of the remote MEPs. bDefErrorCCM(3) The MEP has received at least one invalid CCM whose CCM Interval has not yet timed out. bDefXconCCM(4) The MEP has received at least one CCM from either another MAID or a lower MD Level whose CCM Interval has not yet timed out. " REFERENCE "802.1ag clauses 12.14.7.1.3:o, 12.14.7.1.3:p, 12.14.7.1.3:q, 12.14.7.1.3:r, and 12.14.7.1.3:s." SYNTAX BITS { bDefRDICCM(0), bDefMACstatus(1), bDefRemoteCCM(2), bDefErrorCCM(3), bDefXconCCM(4) } Dot1agCfmConfigErrors ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "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. " REFERENCE "12.14.4.1.3:b and clauses 22.2.3 and 22.2.4" SYNTAX BITS { cfmLeak(0), conflictingVids(1), excessiveLevels(2), overlappedLevels(3) } Dot1agCfmPbbComponentIdentifier ::= TEXTUAL-CONVENTION DISPLAY-HINT "d" STATUS current DESCRIPTION "A Provider Backbone Bridge (PBB) can comprise a number of components, each of which can be managed in a manner essentially equivalent to an 802.1Q bridge. In order to access these components easily, an index is used in a number of tables. If any two tables are indexed by Dot1agCfmPbbComponentIdentifier, then entries in those tables indexed by the same value of Dot1agCfmPbbComponentIdentifier correspond to the same component. " REFERENCE "12.3 l)" SYNTAX Unsigned32 (1..4294967295) dot1agCfmStackTable OBJECT-TYPE SYNTAX SEQUENCE OF Dot1agCfmStackEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "There is one CFM Stack table per bridge. It permits the retrieval of information about the Maintenance Points configured on any given interface. **NOTE: this object is deprecated due to re-indexing of the table. " REFERENCE "802.1ag clauses 12.14.2" ::= { dot1agCfmStack 1 }
An OBJECT-TYPE definition using this SYNTAX MUST specify the relevant table for which the object is providing this functionality. " SYNTAX Unsigned32 (0..4294967295) Dot1agCfmMepDefects ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "A MEP can detect and report a number of defects, and multiple defects can be present at the same time. These defects are: bDefRDICCM(0) A remote MEP is reported the RDI bit in its last CCM. bDefMACstatus(1) Either some remote MEP is reporting its Interface Status TLV as not isUp, or all remote MEPs are reporting a Port Status TLV that contains some value other than psUp. bDefRemoteCCM(2) The MEP is not receiving valid CCMs from at least one of the remote MEPs. bDefErrorCCM(3) The MEP has received at least one invalid CCM whose CCM Interval has not yet timed out. bDefXconCCM(4) The MEP has received at least one CCM from either another MAID or a lower MD Level whose CCM Interval has not yet timed out. " REFERENCE "802.1ag clauses 12.14.7.1.3:o, 12.14.7.1.3:p, 12.14.7.1.3:q, 12.14.7.1.3:r, and 12.14.7.1.3:s." SYNTAX BITS { bDefRDICCM(0), bDefMACstatus(1), bDefRemoteCCM(2), bDefErrorCCM(3), bDefXconCCM(4) } Dot1agCfmConfigErrors ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "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. " REFERENCE "12.14.4.1.3:b and clauses 22.2.3 and 22.2.4" SYNTAX BITS { cfmLeak(0), conflictingVids(1), excessiveLevels(2), overlappedLevels(3) } Dot1agCfmPbbComponentIdentifier ::= TEXTUAL-CONVENTION DISPLAY-HINT "d" STATUS current DESCRIPTION "A Provider Backbone Bridge (PBB) can comprise a number of components, each of which can be managed in a manner essentially equivalent to an 802.1Q bridge. In order to access these components easily, an index is used in a number of tables. If any two tables are indexed by Dot1agCfmPbbComponentIdentifier, then entries in those tables indexed by the same value of Dot1agCfmPbbComponentIdentifier correspond to the same component. " REFERENCE "12.3 l)" SYNTAX Unsigned32 (1..4294967295) dot1agCfmStackTable OBJECT-TYPE SYNTAX SEQUENCE OF Dot1agCfmStackEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "There is one CFM Stack table per bridge. It permits the retrieval of information about the Maintenance Points configured on any given interface. **NOTE: this object is deprecated due to re-indexing of the table. " REFERENCE "802.1ag clauses 12.14.2" ::= { dot1agCfmStack 1 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.111.2.802.1.1.8.1.1.1.1 | dot1agCfmStackEntry | 8 | 8 | The Stack table entry |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.111.2.802.1.1.8.1.1.2 | ieee8021CfmStackTable | 1 | 10 | There is one CFM Stack table per bridge. It permits the retrieval of information about the Maintenance Points configured on any g… |