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

234 Multi-Service IronWare Administration Guide
53-1003028-02
Frame Loss Measurement
6
• As the measurement is performed in the LP, LMM functionality is not supported over LAG, if
member ports are from multiple slots. Loss will be measured only the ports on the same slot.
• If any ACLS are dropped on the same port or vport, the packets matching those ACLs will not be
counted or taken into account as the LMM ACLs will be listed below the layer 2 ACLs.
• Protocol packets or packets trapped to CPU are not counted.
• To measure frame loss on untagged endpoints in VPLS, cos 8 should be used which covers all
the priorities, as there is no priority carried in the untagged packet. This feature not supported
via SNMP as the priority range supported is 0 to 7.
• LMM initiator and responder should monitor on the same priority, otherwise the packet will be
discarded on the responder or initiator side which leads to inaccurate results.
• If cos 8 is configured on the source MEP, no other session with different priority is supported as
cos 8 already counts all the priorities. Cos 8 not supported via SNMP as it is additional and not
as per the standard MIB.
• If the start time is configured without the daily option, it will be shown in the running-config
until it is explicitly removed by the "stop now" command.
• LMM over VLL is not supported.
• For Layer 3 traffic, with VPLS the incoming priority in the data packet gets modified by DSCP
bits and gets changed in the egress side. As the ingress and egress priorities are different in
VPLS data traffic, only cos 8 should be used which monitors on all the priorities.
• For individual packet priority monitoring with VPLS L3 traffic, VLAN PCP and DSCP bits should
be the same in the ingress traffic.
Supported configurations
The following functionalities are common for both VPLS and VLAN endpoints.
Monitor LMM on demand
The LMM can be started immediately whenever required and can be stopped after some period of
time. The frame loss ratio will be calculated after every measurement interval configured and can
be viewed whenever required. This use case will be useful whenever the administrator wants to
measure immediately (on demand).
Monitor LMM for a fixed interval of time
The LMM can be configured to start at any fixed time (more than the current time) and can be
stopped after some period of time (more than the start time). The frame loss ratio will be
calculated after every measurement interval configured and can be viewed whenever required.
This use case will be useful whenever the administrator wants to measure at particular time
interval.
Monitor LMM after some relative time
The LMM can be configured to start after any relative time and can be stopped after some period
of time (more than the start time). The frame loss ratio will be calculated after every measurement
interval configured and can be viewed whenever required. This use case will be useful whenever
the administrator wants to trigger the measurement after some duration.