Deployment scenario-4 (isid meps on bebs) – Brocade Multi-Service IronWare Switching Configuration Guide (Supporting R05.6.00) User Manual
Page 343
Multi-Service IronWare Switching Configuration Guide
313
53-1003036-02
802.1ag over PBB OAM
11
3. Create a maintenance association within a specified domain of pbb-vpls 20 with priority 3.
Brocade(config-cfm-md-PROVIDER_1)#ma-name ma_8 pbb-vpls 20 priority 3
4. Set the time interval between successive Continuity Check Messages. The default is
10-seconds.
Brocade(config-cfm-md-PROVIDER_1-ma-ma_8)#ccm-interval 10-second
The above configuration will create SVID MIPs on BEBs. You can use linktrace to BEB MIPs from PE
MEPs to further isolate the fault location.
Deployment Scenario-4 (ISID MEPs on BEBs)
FIGURE 56
Deployment scenario-4&5
The Local VPLS configuration is similar to the previous scenario.
CFM configuration steps for BEB-1.
1. Enter the cfm-enable command to enable CFM
Brocade(config)#cfm-enable
2. Create a maintenance domain with a specified name PBB_1 and level 4.
Brocade(config-cfm)#domain-name PBB_1 level 3
3. Create a maintenance association within a specified domain of pbb-vpls 20 with priority 3.
Brocade(config-cfm-md-PROVIDER_1)#ma-name ma_8 pbb-vpls 20 priority 3
4. Set the time interval between successive Continuity Check Messages (CCM). The default is
10-seconds.
Brocade(config-cfm-md-PROVIDER_1-ma-ma_8)#ccm-interval 10-second
5. Configure a MEP on port 1/3 and vlan 10.
Brocade(config-cfm-md-PROVIDER_1-ma-ma_8)#mep 6 up ISID 200000 vlan 10 port ethe
1/3
To monitor the connectivity between BEB-1 and BEB-2, you can use the show cfm connectivity
commands as mentioned in the previous scenario. Also, you can use either loopback or linktrace
on BEB-1 or BEB-2.