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

154 Multi-Service IronWare Administration Guide
53-1003028-02
Y.1731 performance management
6
Brocade(config-cfm)#domain name VPLS-SP level 4
Brocade(config-cfm-md-VPLS-SP)#ma-name ma_1 vlan-id 30
Brocade(config-cfm-md-VPLS-SP-ma_1)#mip-policy explicit
Brocade(config-cfm-md-VPLS-SP-ma_1)#
Syntax: [no] mip-policy [explicit |default]
Use the explicit parameter to specify that explicit MIPs are configured only if a MEP exists on a
lower MD Level.
Use the default parameter to specify that MIPs will always be created.
The no form of the command restores the default Policy.
Y.1731 performance management
The Y.1731 feature provides the following performance monitoring capability for point-to-point links
as defined in ITU-T Rec Y.1731:
• Two-way Frame Delay Measurement (ETH-DM)
• Two-way Frame Delay Measurement Variation
NOTE
One-way ETH-DM is not supported in this release of the Multi-Service IronWare.
About Y.1731
Figure 8 shows an ETH-DM requester and responder.
FIGURE 8 ETH-DM requester and responder.
ETH-DM packets are transmitted, received and processed by LP CPU and are timestamped by the
hardware on transmit and receive path.
An ETH-DM packet contains 4 timestamps for measuring the round-trip delay.
Requester A, transmits ETH-DMM packets with TxTimeStampf (timestamp at the transmission time
of the packet).
Responder B, responds with an ETH-DMR packet using two timestamps to account for its
processing time: RxTimeStampf (Timestamp at the time of receiving the DMM packet) and
TxTimeStampb (timestamp at the time of transmitting the DMR packet).
Upon receiving an ETH-DMR packet, requester A stamps the packet with RxTimeb (timestamp at
the time the DMR packet is received).