Connectivity Fault Management (CFM) is an OAM protocol that includes proactive connectivity monitoring using continuity check messages, fault verification through loop back messages, and fault isolation by examining end-to-end connections between provider edge devices or between customer edge devices.
CFM is implemented as a service level protocol based on service instances which encompass only that portion of the metropolitan area network supporting a specific customer. CFM can also provide controlled management access to a hierarchy of maintenance domains (such as the customer, service provider, and equipment operator).
This switch supports functions for defining the CFM structure, including domains, maintenance associations, and maintenance access points. It also supports fault detection through continuity check messages for all known maintenance points, and cross-check messages which are used to verify a static list of remote maintenance points located on other devices (in the same maintenance association) against those found through continuity check messages. Fault verification is supported using loop back messages, and fault isolation with link trace messages. Fault notification is also provided by SNMP alarms which are automatically generated by maintenance points when connectivity faults or configuration errors are detected in the local maintenance domain.
Use the Administration > CFM (Configure Global) page to configure global settings for CFM, such as enabling the CFM process on the switch, setting the start-up delay for cross-check operations, configuring parameters for the link trace cache, and enabling traps for events discovered by continuity check messages or cross-check messages.
Global Parameters
Enables CFM processing globally on the switch. (Default: Enabled)
To avoid generating an excessive number of traps, the complete CFM maintenance structure and process parameters should be configured prior to enabling CFM processing globally on the switch. Specifically, the maintenance domains, maintenance associations, and maintenance end-points (MEPs) should be configured on each participating bridge using the Configure MD page, Configure MA page, and the Configure MEP page.
When CFM is enabled, hardware resources are allocated for CFM processing.
Sets the maximum delay that a device waits for remote MEPs to come up before starting the cross-check operation. (Range: 1-65535 seconds; Default: 10 seconds)
This parameter sets the time to wait for a remote MEP to come up, and the switch starts cross-checking the list of statically configured remote MEPs in the local maintenance domain (Configure Remote MEP page) against the MEPs learned through continuity check messages (CCMs).
The cross-check start delay should be configured to a value greater than or equal to the continuity check message interval to avoid generating unnecessary traps.
LInk Trace Cache Settings
Enables caching of CFM data learned through link trace messages. (Default: Enabled)
A linktrace message is a multicast CFM frame initiated by a MEP, and forwarded from MIP to MIP, with each MIP generating a linktrace reply, up to the point at which the linktrace message reaches its destination or can no longer be forwarded.
Use this command attribute to enable the link trace cache to store the results of link trace operations initiated on this device. Use the CFM Transmit Link Trace page to transmit a linktrace message.
Linktrace responses are returned from each MIP along the path and from the target MEP. Information stored in the cache includes the maintenance domain name, MA name, MEPID, sequence number, and TTL value.
The hold time for CFM link trace cache entries. (Range: 1-65535 minutes; Default: 100 minutes)
Before setting the aging time for cache entries, the cache must first be enabled in the Linktrace Cache attribute field.
If the cache reaches the maximum number of specified entries, or the size is set to a value less than the current number of stored entries, no new entries are added. To add additional entries, the cache size must first be increased, or purged.
Continuity Check Errors
Sends a trap if this device receives a continuity check message (CCM) with the same maintenance end point identifier (MPID) as its own but with a different source MAC address, indicating that a CFM configuration error exists.
Sends a trap if this device receives a CCM with the same source MAC address and MPID as its own, indicating that a forwarding loop exists.
Sends a trap if this device loses connectivity with a remote maintenance end point (MEP), or connectivity has been restored to a remote MEP which has recovered from an error condition.
Sends a trap if a remote MEP is discovered and added to the local database, the port state of a previously discovered remote MEP changes, or a CCM is received from a remote MEP which as an expired entry in the archived database.
MEP Up traps are suppressed when cross-checking of MEPs is enabled because cross-check traps include more detailed status information.
Cross-check Errors
Sends a trap when all remote MEPs in an MA come up.
An MA Up trap is sent if cross-checking is enabled, and a CCM is received from all remote MEPs configured in the static list for this maintenance association
Sends a trap if the cross-check timer expires and no CCMs have been received from a remote MEP configured in the static list.
A MEP Missing trap is sent if cross-checking is enabled, and no CCM is received for a remote MEP configured in the static list.
Sends a trap if an unconfigured MEP comes up.
A MEP Unknown trap is sent if cross-checking is enabled, and a CCM is received from a remote MEP that is not configured in the static list.
CFM processes are enabled by default for all physical interfaces, both ports and trunks. You can use the Administration > CFM (Configure Interface) page to change these settings.
Command Usage
An interface must be enabled before a MEP can be created.
If a MEP has been configured on an interface, it must first be deleted before CFM can be disabled on that interface.
When CFM is disabled, hardware resources previously used for CFM processing on that interface are released, and all CFM frames entering that interface are forwarded as normal data traffic.
Use the Administration > CFM (Configure MD) pages to create and configure a Maintenance Domain (MD) which defines a portion of the network for which connectivity faults can be managed. Domain access points are set up on the boundary of a domain to provide end-to-end connectivity fault detection, analysis, and recovery. Domains can be configured in a hierarchy to provide management access to the same basic network resources for different user levels.
Command Usage
Configuring General Settings -
Where domains are nested, an upper-level hierarchical domain must have a higher maintenance level than the ones it encompasses. The higher to lower level domain types commonly include entities such as customer, service provider, and operator.
More than one domain can be configured at the same maintenance level, but a single domain can only be configured with one maintenance level.
If MEPs or MAs are configured for a domain, they must first be removed before you can remove the domain.
Maintenance domains are designed to provide a transparent method of verifying and resolving connectivity problems for end-to-end connections. By default, these connections run between the domain service access points (DSAPs) within each MA defined for a domain, and are manually configured.
In contrast, MIPs are interconnection points that make up all possible paths between the DSAPs within an MA. MIPs are automatically generated by the CFM protocol when the MIP Creation Type is set to "Default" or "Explicit," and the MIP creation state machine is invoked (as defined in IEEE 802.1ag). The default option allows MIPs to be created for all interconnection points within an MA, regardless of the domain's level in the maintenance hierarchy (e.g., customer, provider, or operator). While the explicit option only generates MIPs within an MA if its associated domain is not at the bottom of the maintenance hierarchy. This option is used to hide the structure of network at the lowest domain level.
The diagnostic functions provided by CFM can be used to detect connectivity failures between any pair of MEPs in an MA. Using MIPs allows these failures to be isolated to smaller segments of the network.
Allowing the CFM to generate MIPs exposes more of the network structure to users at higher domain levels, but can speed up the process of fault detection and recovery. This trade-off should be carefully considered when designing a CFM maintenance structure.
Also note that while MEPs are active agents which can initiate consistency check messages (CCMs), transmit loop back or link trace messages, and maintain the local CCM database, MIPs, on the other hand, are passive agents which can only validate received CFM messages, and respond to loop back and link trace messages.
The MIP creation method defined for an MA takes precedence over the method defined on the CFM Domain List.
Configuring Fault Notification -
A fault alarm can generate an SNMP notification. It is issued when the MEP fault notification generator state machine detects that the configured time period (MEP Fault Notify Alarm Time) has passed with one or more defects indicated, and fault alarms are enabled at or above the specified priority level (MEP Fault Notify Lowest Priority). The state machine transmits no further fault alarms until it is reset by the passage of a configured time period (MEP Fault Notify Reset Time) without a defect indication. The normal procedure upon receiving a fault alarm is to inspect the reporting MEP's managed objects using an appropriate SNMP software tool, diagnose the fault, correct it, re-examine the MEP's managed objects to see whether the MEP fault notification generator state machine has been reset, and repeat those steps until the fault is resolved.
Only the highest priority defect currently detected is reported in the fault alarm.
Refer the Management Guide for information on remote MEP priority levels and a description of MEP defects.
Parameters
Creating a Maintenance Domain -
Domain index. (Range: 1-65535)
Maintenance domain name. (Range: 1-43 alphanumeric characters)
Authorized maintenance level for this domain. (Range: 0-7)
Specifies the CFM protocol's creation method for maintenance intermediate points (MIPs) in this domain:
MIPs can be created for any maintenance association (MA) configured in this domain on any bridge port through which the MA's VID can pass.
MIPs can be created for any MA configured in this domain only on bridge ports through which the MA's VID can pass, and only if a maintenance end point (MEP) is created at some lower MA Level.
No MIP can be created for any MA configured in this domain.
Configuring Detailed Settings for a Maintenance Domain -
Domain index. (Range: 1-65535)
The time that data from a missing MEP is retained in the continuity check message (CCM) database before being purged. (Range: 1-65535 minutes; Default: 100 minutes)
A change to the hold time only applies to entries stored in the database after this attribute is changed.
The lowest priority defect that is allowed to generate a fault alarm. (Range: 1-6, Default: 2)
The time that one or more defects must be present before a fault alarm is issued. (Range: 3-10 seconds; Default: 3 seconds)
The time after a fault alarm has been issued, and no defect exists, before another fault alarm can be issued. (Range: 3-10 seconds; Default: 10 seconds)
Use the Administration > CFM (Configure MA) pages to create and configure the Maintenance Associations (MA) which define a unique CFM service instance. Each MA can be identified by its parent MD, the MD's maintenance level, the VLAN assigned to the MA, and the set of maintenance end points (MEPs) assigned to it.
Command Usage
Creating a Maintenance Association -
Use the Configure MA - Add screen to create an MA within the selected MD, map it to a customer service instance (S-VLAN), and set the manner in which MIPs are created for this service instance. Then use the MEP List to assign domain service access points (DSAPs) to this service instance.
An MA must be defined before any associated DSAPs or remote MEPs can be assigned.
Multiple domains at the same maintenance level cannot have an MA on the same VLAN.
Before removing an MA, first remove the MEPs assigned to it.
For a detailed description of the MIP types, refer to the preceeding section "Configuring CFM Maintenance Domains."
Configuring Detailed Settings for a Maintenance Association
CCMs are multicast periodically by a MEP in order to discover other MEPs in the same MA, and to assure connectivity to all other MEPs/MIPs in the MA.
Each CCM received is checked to verify that the MEP identifier field sent in the message does not match its own MEP ID, which would indicate a duplicate MEP or network loop. If these error types are not found, the CCM is stored in the MEP’s local database until aged out.
If a maintenance point fails to receive three consecutive CCMs from any other MEP in the same MA, a connectivity failure is registered.
If a maintenance point receives a CCM with an invalid MEPID or MA level or an MA level lower than its own, a failure is registered which indicates a configuration error or cross-connect error (i.e., overlapping MAs).
The interval at which CCMs are issued should be configured to detect connectivity problems in a timely manner, as dictated by the nature and size of the MA.
The maintenance of a MIP CCM database by a MIP presents some difficulty for bridges carrying a large number of Service Instances, and for whose MEPs are issuing CCMs at a high frequency. For this reason, slower CCM transmission rates may have to be used.
Parameters
Creating a Maintenance Association -
Domain index. (Range: 1-65535)
MA identifier. (Range: 1-2147483647)
MA name. (Range: 1-43 alphanumeric characters)
Each MA name must be unique within the CFM-managed network.
Service VLAN ID.
This is the VLAN through which all CFM functions are executed for this MA.
Specifies the CFM protocol's creation method for maintenance intermediate points (MIPs) in this MA:
MIPs can be created for this MA on any bridge port through which the MA's VID can pass.
MIPs can be created for this MA only on bridge ports through which the MA's VID can pass, and only if a maintenance end point (MEP) is created at some lower MA Level.
No MIP can be created for this MA.
Configuring Detailed Settings for a Maintenance Association
Domain index. (Range: 1-65535)
MA identifier. (Range: 1-2147483647)
Specifies the name format for the maintenance association as IEEE 802.1ag character based, or ITU-T SG13/SG15 Y.1731 defined ICC-based format.
IEEE 802.1ag defined character string format. This is an IETF RFC 2579 DisplayString.
ITU-T SG13/SG15 Y.1731 defined ICC based format.
The delay between sending CCMs. The setting for this parameter is expressed as levels 4 through 7, which in turn map to specific intervals of time. (Options: 4 - 1 second, 5 - 10 seconds, 6 - 1 minute, 7 - 10 minutes)
Enables transmission of CCMs. (Default: Disabled)
Enables cross-checking between a static list of MEPs assigned to other devices within the same maintenance association and the MEPs learned through CCMs.
Before starting the cross-check process, first configure the remote MEPs that exist on other devices inside the maintenance association using the Remote MEP List. These remote MEPs are used in the cross-check operation to verify that all endpoints in the specified MA are operational.
The cross-check start delay, which sets the maximum delay this device waits for a remote MEP to come up before starting the cross-check operation, is a domain-level parameter. To set this parameter, use the CFM MD Configuration screen.
Enables/disables suppression of the Alarm Indication Signal (AIS). (Default: Disabled)
Configures the period at which AIS is sent in an MA. (Range: 1 or 60 seconds; Default: 1 second)
Configure the AIS maintenance level in an MA. (Range: 0-7; Default is 0)
AIS Level must follow this rule: AIS Level >= Domain Level
Enables/disables suppression of the AIS. (Default: Disabled)
Use the Administration > CFM (Configure MEP - Add) page to configure Maintenance End Points (MEPs). MEPs, also called Domain Service Access Points (DSAPs), must be configured at the domain boundary to provide management access for each maintenance association.
Command Usage
CFM elements must be configured in the following order: (1) maintenance domain at the same level as the MEP to be configured, (2) maintenance association within the domain, and (3) finally the MEPs using the MEP List.
An interface may belong to more than one domain, or to different MAs in different domains.
To change the MEP’s MA or the direction it faces, first delete the MEP, and then create a new one.
Parameters
Domain index. (Range: 1-65535)
MA identifier. (Range: 1-2147483647)
Maintenance end point identifier. (Range: 1-8191)
Up indicates that the MEP faces inward toward the switch cross-connect matrix, and transmits CFM messages towards, and receives them from, the direction of the internal bridge relay mechanism. If the Up option is not selected, then the MEP is facing away from the switch, and transmits CFM messages towards, and receives them from, the direction of the physical medium.
Indicates a port or trunk.
Use the Administration > CFM (Configure Remote MEP - Add) page to specify remote maintenance end points (MEPs) set on other CFM-enabled devices within a common MA. Remote MEPs can be added to a static list in this manner to verify that each entry has been properly configured and is operational. When cross-checking is enabled, the list of statically configured remote MEPs is compared against the MEPs learned through continuity check messages (CCMs), and any discrepancies reported via SNMP traps.
Command Usage
All MEPs that exist on other devices inside a maintenance association should be statically configured to ensure full connectivity through the cross-check process.
Remote MEPs can only be configured if local domain service access points (DSAPs) have already been created at the same maintenance level and in the same MA. DSAPs are MEPs that exist on the edge of the domain, and act as primary service access points for end-to-end cross-check, loop-back, and link-trace functions.
The MEP cross-check start delay which sets the maximum delay that a device waits for remote MEPs to come up before starting the cross-check operation can be configured using the "ethernet cfm mep crosscheck start-delay" command.
SNMP traps for continuity check events discovered by cross-check operations can be configured on the CFM Configure Global page.
Parameters
Domain index. (Range: 1-65535)
MA identifier. (Range: 1-2147483647)
Identifier for a maintenance end point which exists on another CFM-enabled device within the same MA. (Range: 1-8191)
Use the Administration > CFM (Transmit Link Trace) page to transmit link trace messages (LTMs). These messages can isolate connectivity faults by tracing the path through a network to the designated target node (i.e., a remote maintenance end point).
Command Usage
LTMs can be targeted to MEPs, not MIPs. Before sending a link trace message, be sure you have configured the target MEP for the specified MA.
If MAC address of target MEP has not been learned by any local MEP, then the linktrace may fail. Use the Show Remote MEP page to verify that a MAC address has been learned for the target MEP.
LTMs are sent as multicast CFM frames, and forwarded from MIP to MIP, with each MIP generating a link trace reply, up to the point at which the LTM reaches its destination or can no longer be forwarded.
LTMs are used to isolate faults. However, this task can be difficult in an Ethernet environment, since each node is connected through multipoint links. Fault isolation is even more challenging since the MAC address of the target node can age out in several minutes. This can cause the traced path to vary over time, or connectivity lost if faults cause the target MEP to be isolated from other MEPs in an MA.
When using the command line or web interface, the source MEP used by to send a link trace message is chosen by the CFM protocol. However, when using SNMP, the source MEP can be specified by the user.
Parameters controlling the link trace cache, including operational state, entry hold time, and maximum size can be configured on the CFM Configure Global page.
Parameters
Domain index. (Range: 1-65535)
MA identifier. (Range: 1-2147483647)
The identifier of a source MEP that will send the link trace message. (Range: 1-8191)
The identifier of a remote MEP that is the target of a link trace message. (Range: 1-8191)
MAC address of a remote MEP that is the target of a link trace message. This address can be entered in either of the following formats: xx-xx-xx-xx-xx-xx or xxxxxxxxxxxx
The time to live of the link trace message. (Range: 0-255 hops)
Use the Administration > CFM (Transmit Loopback) page to transmit Loopback Messages (LBMs). These messages can be used to isolate or verify connectivity faults by submitting a request to a target node (i.e., a remote MEP or MIP) to echo the message back to the source.
Command Usage
Loopback messages can be used for fault verification and isolation after automatic detection of a fault or receipt of some other error report. Loopback messages can also used to confirm the successful restoration or initiation of connectivity. The receiving maintenance point should respond to the loop back message with a loopback reply.
The point from which the loopback message is transmitted (i.e., a local DSAP) and the target maintenance point must be within the same MA.
If the continuity check database does not have an entry for the specified maintenance point, an error message will be displayed.
When using the command line or web interface, the source MEP used by to send a loopback message is chosen by the CFM protocol. However, when using SNMP, the source MEP can be specified by the user.
Parameters
Domain index. (Range: 1-65535)
MA identifier. (Range: 1-2147483647)
The identifier of a source MEP that will send the loopback message. (Range: 1-8191)
The identifier of a remote MEP that is the target of a loopback message. (Range: 1-8191)
MAC address of a remote MEP that is the target of a loopback message. This address can be entered in either of the following formats: xx-xx-xx-xx-xx-xx or xxxxxxxxxxxx
The number of times the loopback message is sent. (Range: 1-1024)
The size of the loopback message. (Range: 64-1518 bytes; Default: 64 bytes)
Use the Administration > CFM (Transmit Delay Measure) page to send periodic delay-measure requests to a specified MEP within a maintenance association.
Command Usage
Delay measurement can be used to measure frame delay and frame delay variation between MEPs.
A local MEP must be configured for the same MA before you can use this function.
If a MEP is enabled to generate frames with delay measurement (DM) information, it periodically sends DM frames to its peer MEP in the same MA., and expects to receive DM frames back from it.
Frame delay measurement can be made only for two-way measurements, where the MEP transmits a frame with DM request information with the TxTimeStampf (Timestamp at the time of sending a frame with DM request information), and the receiving MEP responds with a frame with DM reply information with TxTimeStampf copied from the DM request information, RxTimeStampf (Timestamp at the time of receiving a frame with DM request information), and TxTimeStampb (Timestamp at the time of transmitting a frame with DM reply information):
Frame Delay = (RxTimeStampb-TxTimeStampf)-(TxTimeStampb-RxTimeStampf)
The MEP can also make two-way frame delay variation measurements based on its ability to calculate the difference between two subsequent two-way frame delay measurements.
Parameters
Domain index. (Range: 1-65535)
MA identifier. (Range: 1-2147483647)
The identifier of a source MEP that will send the delay-measure message. (Range: 1-8191)
The identifier of a remote MEP that is the target of a delay-measure message. (Range: 1-8191)
MAC address of a remote MEP that is the target of a delay-measure message. This address can be entered in either of the following formats: xx-xx-xx-xx-xx-xx or xxxxxxxxxxxx
The number of times to retry sending the message if no response is received before the specified timeout. (Range: 1-5; Default: 5)
The size of the delay-measure message. (Range: 64-1518 bytes; Default: 64 bytes)
The transmission delay between delay-measure messages. (Range: 1-5 seconds; Default: 1 second)
The timeout to wait for a response. (Range: 1-5 seconds; Default: 5 seconds)
Use the Administration > CFM > Show Information (Show Local MEP) page to show information for the MEPs configured on this device.
Maintenance end point identifier.
Maintenance domain name.
Authorized maintenance level for this domain.
Direction in which the MEP communicates CFM messages:
Down indicates that the MEP is facing away from the switch, and transmits CFM messages towards, and receives them from, the direction of the physical medium.
Up indicates that the MEP faces inward toward the switch cross-connect matrix, and transmits CFM messages towards, and receives them from, the direction of the internal bridge relay mechanism.
Service VLAN ID.
Physical interface of this entry (either a port or trunk).
Shows administrative status of CCMs.
MAC address of this MEP entry.
Use the Administration > CFM > Show Information (Show Local MEP Details) page to show detailed CFM information about a local MEP in the continuity check database.
Domain index. (Range: 1-65535)
MA identifier. (Range: 1-2147483647)
Maintenance end point identifier. (Range: 1-8191)
The maintenance domain for this entry.
Maintenance association to which this remote MEP belongs.
The format of the Maintenance Association name, including Character String or ICC Based.
Maintenance level of the local maintenance point.
The direction in which the MEP faces on the Bridge port (up or down).
The port to which this MEP is attached.
Shows if the MEP will generate CCM messages.
MAC address of the local maintenance point. (If a CCM for the specified remote MEP has never been received or the local MEP record times out, the address will be set to the initial value of all Fs.)
Shows the defect detected on the MEP.
Receive status of remote defect indication (RDI) messages on the MEP.
Shows if MEPs within the specified MA are enabled to send frames with AIS information following detection of defect conditions.
The interval at which AIS information is sent.
The maintenance level at which AIS information will be sent for the specified MEP.
Shows if the specified MEP is configured to suppress sending frames containing AIS information following the detection of defect conditions.
Shows if the specified MEP is currently suppressing sending frames containing AIS information following the detection of defect conditions.
Use the Administration > CFM > Show Information (Show Local MIP) page to show the MIPs on this device discovered by the CFM protocol. (For a description of MIPs, refer to the Command Usage section under "Configuring CFM Maintenance Domains.")
Maintenance domain name.
Authorized maintenance level for this domain.
Maintenance association name.
Service VLAN ID.
Physical interface of this entry (either a port or trunk).
Use the Administration > CFM > Show Information (Show Remote MEP) page to show MEPs located on other devices which have been discovered through continuity check messages, or statically configured in the MEP database and verified through cross-check messages.
Maintenance end point identifier.
Maintenance association name.
Authorized maintenance level for this domain.
Service VLAN ID.
Indicates whether or not this MEP is functioning normally.
MAC address of the remote maintenance point. (If a CCM for the specified remote MEP has never been received or the remote MEP record times out, the address will be set to the initial value of all Fs.)
Use the Administration > CFM > Show Information (Show Remote MEP Details) page to show detailed information for MEPs located on other devices which have been discovered through continuity check messages, or statically configured in the MEP database and verified through cross-check messages.
Domain index. (Range: 1-65535)
MA identifier. (Range: 1-2147483647)
Maintenance end point identifier. (Range: 1-8191)
Maintenance domain name.
Maintenance association name.
Authorized maintenance level for this domain.
MAC address of this MEP entry.
Service VLAN ID.
Port to which this remote MEP is attached.
Length of time to hold messages about this MEP in the CCM database.
Length of time the last CCM message about this MEP has been in the CCM database.
Percentage of transmitted frames lost.
The number of CCM packets received successfully and those with errors.
Port states include:
Up - The port is functioning normally.
Blocked - The port has been blocked by the Spanning Tree Protocol.
No port state - Either no CCM has been received, or nor port status TLV was received in the last CCM.
Interface states include:
No Status - Either no CCM has been received, or no interface status TLV was received in the last CCM.
Up - The interface is ready to pass packets.
Down - The interface cannot pass packets.
Testing - The interface is in some test mode.
Unknown - The interface status cannot be determined for some reason.
Dormant - The interface is not in a state to pass packets but is in a pending state, waiting for some external event.
Not Present - Some component of the interface is missing.
isLowerLayerDown - The interface is down due to state of the lower layer interfaces.
Shows if crosscheck function has been enabled.
Use the Administration > CFM > Show Information (Show Link Trace Cache) page to show information about link trace operations launched from this device.
The number hops taken to reach the target MEP.
Maintenance association name.
IP address or DNS alias of the target device’s CPU.
Shows whether or not this link trace message was forwarded. A message is not forwarded if received by the target MEP.
MAC address of the ingress port on the target device.
MAC address of the egress port on the target device.
Action taken on the ingress port:
IngOk - The target data frame passed through to the MAC Relay Entity.
IngDown - The bridge port's MAC_Operational parameter is false. This value could be returned, for example, by an operationally Down MEP that has another Down MEP at a higher MD level on the same bridge port that is causing the bridge port's MAC_Operational parameter to be false.
IngBlocked - The ingress port can be identified, but the target data frame was not forwarded when received on this port due to active topology management, i.e., the bridge port is not in the forwarding state.
IngVid - The ingress port is not in the member set of the LTM's VIDs, and ingress filtering is enabled, so the target data frame was filtered by ingress filtering.
Action taken on the egress port:
EgrOk - The targeted data frame was forwarded.
EgrDown - The Egress Port can be identified, but that bridge port's MAC_Operational parameter is false.
EgrBlocked - The egress port can be identified, but the data frame was not passed through the egress port due to active topology management, i.e., the bridge port is not in the forwarding state.
EgrVid - The Egress Port can be identified, but the bridge port is not in the LTM's VID member set, and was therefore filtered by egress filtering.
Reply action:
FDB - Target address found in forwarding database.
MPDB - Target address found in the maintenance point database.
HIT - Target located on this device.
Use the Administration > CFM > Show Information (Show Fault Notification Generator) page to display configuration settings for the fault notification generator.
Maintenance end point identifier.
Maintenance domain name.
Maintenance association name.
The highest defect that will generate a fault alarm. (This is disabled by default.)
The lowest defect that will generate a fault alarm.
The time a defect must exist before a fault alarm is issued.
The time after a fault alarm has been issued, and no defect exists, before another fault alarm can be issued.
Use the Administration > CFM > Show Information (Show Continuity Check Error) page to display the CFM continuity check errors logged on this device.
Maintenance level associated with this entry.
VLAN in which this error occurred.
Identifier of remote MEP.
Port at which the error was recorded.
MAC address of remote MEP.
Error types include:
LEAK - MA x is associated with a specific VID list, one or more of the VIDs in this MA can pass through the bridge port, no MEP is configured facing outward (down) on any bridge port for this MA, and some other MA y, at a higher maintenance level, and associated with at least one of the VID(s) also in MA x, does have a MEP configured on the bridge port.
This definition is based on the IEEE 802.1ag standard. Current software for this switch only supports a single VLAN per MA. However, since it may interact with other devices which support multiple VLAN assignments per MA, this error message may be reported.
VIDS - MA x is associated with a specific VID list, an MEP is configured facing inward (up) on this MA 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 facing inward (up) on some bridge port.
This definition is based on the IEEE 802.1ag standard. Current software for this switch only supports a single VLAN per MA. However, since it may interact with other devices which support multiple VLAN assignments per MA, this error message may be reported.
EXCESS_LEV - The number of different MD levels at which MIPs are to be created on this port exceeds the bridge's capabilities.
OVERLAP_LEV - A MEP is created for one VID at one maintenance level, but a MEP is configured on another VID at an equivalent or higher level, exceeding the bridge's capabilities.
The maintenance association for this entry.