Brocade Multi-Service IronWare Administration Guide (Supporting R05.6.00) - Manual (Page 171)

Multi-Service IronWare Administration Guide 153
53-1003028-02
Setting Maintenance Domain parameters
6
The mep-id parameter specifies the maintenance end point ID (mandatory) in the range 1-8191.
The up parameter sets the MEP direction away from the monitored VLAN.
The down parameter sets the MEP direction towards the monitored VLAN.
The vlan-id parameter specifies the VLAN end-points. It is configured only for MAs associated with
VPLS and not configured for MAs with a VLAN.
The port-id parameter specifies the target interface on which it is used.
The no form of the command removes the specified MEPs.
Configuring Remote MEPs
The remote-mep command is used to configure the remote MEP’s you are expecting. If a remote
MEP is not specified, the remote MEP database is built based on the CCM. If one remote MEP
never sends CCM, the failure can not be detected.
Brocade(config-cfm-md-VPLS-SP)# ma-name ma_1 vlan-id 30
Brocade(config-cfm-md-VPLS-SP-ma_1)# remote-mep 1 to 120
Brocade(config-cfm-md-VPLS-SP-ma_1)#
Syntax: [no] remote-mep mep-id [to mep-id]
The mep-id parameter specifies the maintenance end point ID (mandatory) in the range 1-8191.
The no form of the command removes the specified remote MEPs.
Setting the Remote Check Start-Delay
When configuring the remote MEPs range, you can set a wait time before the MEPs come up and
the CCM check operation is started. The default is set to 30 seconds.
Brocade(config)#cfm-enable
Brocade(config-cfm)#rmep-check start-delay 120
Brocade(config-cfm)#
Syntax: [no] rmep-check start-delay seconds
The seconds parameter is the wait time interval before the CCM check is started. The range is 10 –
600 seconds.
Specifying MIP creation policy
The mip-policy command, in Maintenance Association mode, specifies the conditions in which
MIPs are automatically created on ports.
NOTE
MIP functionality of 802.1ag over VPLS with sub-second timer will have all the configuration
restrictions of the VPLS CPU-protection.
A MIP can be created on a port and VLAN, only when explicit or default policy has been defined for
them. For a specific port and VLAN a MIP will be created at the lowest of the levels. Additionally, the
level created should be the next higher than the MEP level defined for these port and VLAN.