Configuring cfm maintenance associations, Figure 297 confi, Configuring cfm maintenance – Brocade 6910 Ethernet Access Switch Configuration Guide (Supporting R2.2.0.0) User Manual
Page 1059: Associations, Configuring, Cfm maintenance associations
Brocade 6910 Ethernet Access Switch Configuration Guide
1003
53-1002651-02
43
Connectivity Fault Management
FIGURE 297
Configuring Detailed Settings for Maintenance Domains
Configuring CFM Maintenance Associations
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.
CLI References
•
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 (see
“Configuring Maintenance End Points”
•
An MA must be defined before any associated DSAPs or remote MEPs can be assigned (see
“Configuring Remote Maintenance End Points”
•
Multiple domains at the same maintenance level cannot have an MA on the same VLAN (see
“Configuring CFM Maintenance Domains”
•
Before removing an MA, first remove the MEPs assigned to it (see
•
For a detailed description of the MIP types, refer to the Command Usage section under
“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.