Ethernet cfm domain – Brocade 6910 Ethernet Access Switch Configuration Guide (Supporting R2.2.0.0) User Manual
Page 580
524
Brocade 6910 Ethernet Access Switch Configuration Guide
53-1002651-02
25
CFM Commands
ethernet cfm domain
This command defines a CFM maintenance domain, sets the authorized maintenance level, and
enters CFM configuration mode. Use the no form to delete a CFM maintenance domain.
Syntax
ethernet cfm domain index index name domain-name level level-id [mip-creation type]
no ethernet cfm domain index index
index – Domain index. (Range: 1-65535)
domain-name – Domain name. (Range: 1-43 alphanumeric characters)
level-id – Authorized maintenance level for this domain. (Range: 0-7)
type – Specifies the CFM protocol’s creation method for maintenance intermediate points
(MIPs) in this domain:
default – 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.
explicit – 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.
none – No MIP can be created for any MA configured in this domain.
Default Setting
No maintenance domains are configured.
No MIPs are created for any MA in the specified domain.
Command Mode
Global Configuration
Command Usage
•
A domain can only be configured with one name.
•
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 using the
command or
command, 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 using the
command.
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 option in this command 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