Brocade Multi-Service IronWare Switching Configuration Guide (Supporting R05.6.00) - Manual (Page 340)

310 Multi-Service IronWare Switching Configuration Guide
53-1003036-02
802.1ag over PBB OAM
11
Forwarded Egress Egress Action Nexthop
----------------------------------------------------------------
Type Control-c to abort
1 000c.dbe2.8a00 10.1.1.1 IgrOK RLY_HIT
Not Forwarded
Destination 000c.dbe2.8a00 reached
Syntax: cfm loopback domain NAME ma MA-NAME scr-mep mep-id {target-mip
HH:HH:HH:HH:HH:HH | targetmep mep-id} [number number] [timeout timeout]
Brocade#cfm loopback domain CUST_1 ma ma_5 src-mep 1 target-mep 2
DOT1AG: Sending 10 Loopback to 000c.dbe2.8a00, timeout 10000 msec
Type Control-c to abort
Reply from 000c.dbe2.8a00: time=3ms
Reply from 000c.dbe2.8a00: time<1ms
Reply from 000c.dbe2.8a00: time<1ms
Reply from 000c.dbe2.8a00: time<1ms
Reply from 000c.dbe2.8a00: time=38ms
Reply from 000c.dbe2.8a00: time<1ms
Reply from 000c.dbe2.8a00: time<1ms
Reply from 000c.dbe2.8a00: time<1ms
Reply from 000c.dbe2.8a00: time<1ms
Reply from 000c.dbe2.8a00: time<1ms
A total of 10 loopback replies received.
Success rate is 100 percent (10/10), round-trip min/avg/max=0/4/38 ms.
If the linktrace and loopback to target-mep 2 fails, then linktrace can be done on the MIPs on
PEB-1 and PEB-2 to know the exact failure.
Deployment Scenario-2 (UP MEPs and MIPs on PEs)
If you have a deployment scenario where PEB-1 is not directly connected to BEB-1, but it is
connected to a PB network, then you can use MIPs configured over the intermediary nodes,
assuming the PB network is managed by the same administrator.
If the network is managed by a separate administrator, then you can have UP-MEPs configured on
the PE ports connected to CE devices. The intermediate devices will have MIPs configured.
FIGURE 55 Deployment scenario-2&3