Using Service OAM
  • 25 Jan 2024
  • 22 Minutes to read
  • Contributors
  • PDF

Using Service OAM

  • PDF

Article summary

Service OAM (SOAM) is a layer-2 protocol used for Connectivity Fault Management (CFM) and Performance Monitoring (PM) in a Carrier Ethernet Network (CEN) and encompasses the fault management and performance management capabilities of the Skylight performance element GT.
The following sections describe IEEE 802.1ag Service OAM and show how to set up your Metro Ethernet Network to perform end-to-end monitoring.

An overview of Service OAM is given below.

Overview of Service OAM

1.bmp

The diagram below shows a typical setup scenario for Service OAM.

Typical Setup Scenario for Service OAM

2.bmp

MEP vs. MIP

A Maintenance End Point (MEP) is a provisioned OAM reference point that can initiate and terminate proactive OAM frames and can initiate and react to diagnostic OAM frames. A MEP is represented by a “triangle” symbol, as shown in the OAM diagram below. A Point-to-Point EVC has two MEPs, one at each end-point of the ME (i.e. each UNI-N).

Each MEP has a direction, down or up:

  • A Down MEP receives PDUs from the local interface and sends PDUs towards the local interface.
  • An Up MEP receives PDUs from the relay entity and sends PDUs towards the relay entity.

A Maintenance Intermediate Point (MIP) is a provisioned OAM reference point that is capable of reacting to diagnostic OAM frames initiated by MEPs and does not initiate proactive or diagnostic OAM frames. A MIP is represented by a “circle” symbol, as shown in the Overview of Service OAM, in Using Service OAM. The number of MIPs in a Point-to-Point EVC or Multipoint EVC depends on the specific deployment.

MIPs are used for Fault Management.

Setting Up CFM

The steps required to set up Connectivity Fault Management (CFM) are:

  • Set up Maintenance Domains (MD).
  • Set up Maintenance Associations (MA), also known as Maintenance Entity Groups (MEG).
  • Set up Maintenance association End Points (MEP).

Once these are set up, you can use Service OAM for performing the following fault management functions:

  • Link Trace Messages. "Setting Up Link Trace Messages".
  • Loopback Messages. "Setting Up Loopback Messages".

For viewing MEP information, see also Viewing MEP Status, Viewing the MEP Database, and Viewing MEP Statistics. You can also set up delay measurements, packet loss measurements and synthetic loss measurements.

If required, you can set up CFM defaults. "Setting Up CFM Default Values".

If required, you can configure the unit as a VSP reflector. "Setting Up VSP".

Viewing CFM Instances

To view CFM instances

  1. Access the page SOAM ▶CFM ▶Stack.
    A list of all CFM instances and their settings is displayed. For more information on specific parameters, refer to the following table.

CFM Stack (SOAM ▶CFM ▶Stack)

ParameterDescription
PortThe port on which MEPs or MIPs have been configured.
VIDThe VLAN ID to which the Maintenance Point is attached, or 0, if there is no VLAN ID.
LevelThe MD level (or MEG level) of the Maintenance Point.

Possible values: 0–7.

DirThe direction in which the MEP or MIPs faces on the port.
MD idxThe index of the Maintenance Domain with which the MEP or MIP is
associated.
MA idxThe index of MA (or MEG) with which the MEP or MIP is associated.
MEPIDThe MEPID of the MEP or MIP (MEPID of MIP is 0).
MAC AddressThe MAC address of the Maintenance Point.

Setting Up Maintenance Domains (MD)

There are eight pseudo MDs defined by default, one for each level, named Y.1731 level 0 to Y.1731 level 7. These MDs exist only to simplify the integration of MEGs for Y.1731 with the CFM MIB which requires MDs. Y.1731 uses MEG-IDs which are MAIDs without an MD name. User interfaces show the pseudo MD name, but this name is not included in Y.1731 CCM's MEGID. It is not possible to delete pseudo MDs.

To set up a Maintenance Domain

  1. Access the page SOAM ▶CFM ▶MD.
    A listing of all existing Maintenance Domains is displayed.

  2. Click the Add button to add a new Maintenance Domain or click the name of an existing Maintenance Domain to edit its settings.

  3. Complete the required fields, then click Apply.

For more information on specific parameters, refer to the following table.

Maintenance Domain (SOAM ▶CFM ▶MD)

ParameterDescription
IndexUnique index assigned to the Maintenance Domain.
Name FormatThe format of the Maintenance Domain name.
  • Character String: RFC-2579 display string, except that the character codes 0–31 (decimal) are not used.
The name format must be the same for the other end points.
Name

MD Name

Unique name for the Maintenance Domain.
LevelMaintenance level of the Maintenance Domain.

Possible values: 0–7

MHF CreationIndicates whether the management entity can create MHFs for VIDs on which no Up MEP is configured. Possible values are:
  • None: No MHFs can be created.
  • Default: Create MHFs if there is no lower active MD level, or if there is a MEP at the next lower active MD level on the component port.
  • Explicit: Create MHFs only if there is an MEP at the next lower active MD level on the component port.
Sender ID PermissionThe information (if any) to be included in the Sender ID TLV transmitted in CCMs, LBMs, LTMs and LTRs.

The available values are:

  • None: The Sender ID TLV is not to be sent.
  • Chassis: The Chassis ID Length, Chassis ID subtype, and Chassis ID fields of the Sender ID TLV are to be sent.
  • Manage: The Management Address Length and Management Address of the Sender ID TLV are to be sent.
  • Chassis and Manage: The Chassis ID Length, Chassis ID Subtype, Chassis ID, Management Address Length, and Management Address fields are all to be sent.
  • Bullet

Deleting a Maintenance Domain (MD)


CAUTION: Deleting an MD will also delete all instances (e.g. MA/MEG) that use this MD.

To delete a maintenance domain

  1. Access the page SOAM ▶CFM ▶MD.

  2. Click the name of the MD instance to delete.

  3. Click Delete.

Setting Up Maintenance Associations (Maintenance Entity Groups)

Before setting up a Maintenance Association or MA (also referred to as a MEG), you must first set up the MD to which you want the MA/MEG to belong. Maintenance Associations are discussed in IEEE 802.1ag. Maintenance Entity Groups are discussed in ITU-T Y.1731.

The remote MEP auto-discovery feature is intended to make it easier to configure MA/MEGs because it eliminates the process of manually building the comma-separated list of up to 255 associated MEPs (i.e. the MEPID list). With the remote MEP auto-discovery, Connectivity Check Messages (CCM) are processed as they are received by the MEP and the associated remote MEP is automatically added to the MEPID list. An R-CCM alarm is raised in the SOAM▶CFM ▶MEP ▶Status page when CCMs are no longer being received by a MEP; this MEP will be monitored until its MEPID is manually removed from the MEP IP list.


Note: For remote MEP auto-discovery to function as expected, all MEPs to be discovered must belong to the same MA. Furthermore, you must manually create at least one MEP per MA in order to receive the CCMs from the remote MEPs being discovered.

To set up a Maintenance Association or Maintenance Entity Group

  1. Access the page SOAM ▶CFM ▶MA/MEG.
    A listing of all Maintenance Associations / Maintenance Entity Groups is displayed.

  2. Click the Add button to add a new Maintenance Association or Maintenance Entity Group, or click the name of an existing Maintenance Association or Maintenance Entity Group to edit its settings.

  3. Complete the required fields, then click Apply.

For more information on specific parameters, refer to the following table.

Maintenance Association (SOAM ▶CFM ▶MA/MEG)

ParameterDescription
MA/MEG Index

Index

Unique index value assigned to the Maintenance Association or Maintenance Entity Group.
MD IndexUnique index value assigned to the Maintenance Domain for this Maintenance Association or Maintenance Entity Group.
MDMaintenance Domain for this Maintenance Association or Maintenance Entity Group.
Name FormatThe format of the Maintenance Association or Maintenance Entity Group name.

Possible values are:

  • String: RFC-2579 display string
  • ICC-Based: ITU Carrier Code format
MAID string format modeIndicates the string format mode of the Maintenance Association Identifier (MAID).

Note: This field will be visible only if the Maintenance Domain (MD) is set to Y.1731 and the Name Format is set to String.

Possible values are:

  • Normal: The MEG ID length will have a value equal to the MA/MEG name string length.
  • Legacy: The MEG ID length will have a default minimum length field of 13 character.
NameThe name of this Maintenance Association or Maintenance
MA/MEG NameEntity Group.
LevelMaintenance Level of the Maintenance Association or

Maintenance Entity Group.

Possible values: 0–7

CCM IntervalThe required time interval between Continuity Check

Messages (CCM). Expressed in milliseconds.

Default: 1,000 milliseconds

MHF CreationIndicates whether the management entity can create MHFs for VIDs on which no Up MEP has been configured.

Possible values are:

  • None: No MHFs can be created.
  • Default: Create MHFs if there is no lower active MD level, or if there is a MEP at the next lower active MD level on the port.
  • Explicit: Create MHFs only if there is a MEP at the next lower active MD level on the port.
  • Defer: Use the Maintenance Domain parameter to determine MHF creation.
Sender ID PermissionDetermines what, if anything, is to be included in the Sender ID TLV transmitted in CCMs, LBMs, LTMs and LTRs.

Possible values are:

  • None: The Sender ID TLV is not to be sent.
  • Chassis: The Chassis ID Length, Chassis ID subtype, and Chassis ID fields of the Sender ID TLV are to be sent.
  • Manage: The Management Address Length and Management Address of the Sender ID TLV are to be sent.
  • Chassis & Manage: The Chassis ID Length, Chassis ID subtype, Chassis ID, Management Address Length, and Management Address fields are all to be sent.
  • Defer: Determined by the domain configuration or system configuration.
Use VCESelect this box to enable VCE for use. When enabled, another field is shown: VCE Name allowing you to select the VCE to use.
VCE NameType the name of the VCE you wish to use.
ComponentIDAn unsigned integer identifying the VLAN bridge component in the system.
VLAN TypeThe VLAN type associated with this Maintenance Association or Maintenance Entity Group.

Possible values are:

  • None: The association is not attached to a VLAN and the contents of the VLAN ID list is ignored.
  • C-VLAN: Customer VLAN (typically the inner tag).
  • S-VLAN: Service VLAN (typically the outer tag).
  • T-VLAN: Tunnel VLAN (either the inner or outer tag).
  • Bullet
VLAN ID ListA list of the VLANs associated with this Maintenance Association or Maintenance Entity Group.

If you leave the VLAN ID field empty, the association is not attached to a VLAN and the VLAN type is set to None implicitly.

Remote MEP Auto-DiscoverySelect this box to enable the Remote MEP Auto-Discovery feature for this Maintenance Association or Maintenance Entity Group. When enabled, remote MEPs are automatically added to the MA/MEG as soon as the remote MEP's CCM message is received.

Note: You must manually refresh the page to view any remote MEPs that have been discovered since the page was initially loaded. Access the page SOAM ▶CFM ▶MEP ▶ Statistics and examine the values in the "CCM Sent" and "CCM Received" columns if you believe a MEP has failed to be discovered.

MEPID ListA comma-separated list of all the MEPs that are associated with this Maintenance Association or Maintenance Entity Group.

Typically, when two MEP are added to a MA/MEG, it is usually because you are creating an E-Line type of service, based on a point-to-point EVC. In contrast, adding multiple MEP is for when you are creating an E-LAN type of service, based on a rooted-multipoint EVC.

To delete a Maintenance Association (Maintenance Entity Group)


CAUTION: Deleting a MA/MEG will also delete all instances (e.g. MEP) that use this MA/MEG.

  1. Access the page SOAM ▶CFM ▶MA/MEG.

  2. Click the name of the Maintenance Association or Maintenance Entity Group name to delete.

  3. Click Delete.

Setting Up Maintenance Association End Points

Before setting up a MEP, you must first set up its MA/MEG. Maintenance association End Points (MEP) are discussed in IEEE 802.1ag.

To set up a Maintenance association End Point

  1. Access the page SOAM ▶CFM ▶MEP ▶Configuration.
    A listing of all existing Maintenance association End Points is displayed.

  2. Click the Add button to add a new MEP or click the MEPID of an existing MEP to edit its settings.

  3. Complete the required fields, then click Apply to start the CCM.

For more information on specific parameters, refer to the following table.


Note: Although the local MEP will start sending CCM frames immediately, continuity errors will be raised. You must configure the other end point for valid results to be displayed.

Maintenance association End Point (SOAM ▶CFM ▶MEP ▶Configuration)

ParameterDescription
IndexThe index value assigned to the Maintenance association End Point.
MA/MEG NameThe name of the maintenance association (or MEG) to associate with the MEP.
MEPIDMaintenance association End Point Identifier (MEPID) for this Maintenance association.

This value is an integer, unique to each MA, that identifies a specific MEP in CCM frames.

VCE portA check box to enable use of a VCE port. Once selected, other options appear in the dialog.
VCE NameThe name of the VCE that you wish to use. Appears only if VCE port check box has been selected.
TPA pull-down menu with a limited selection: tp-a or tp-z. Select the desired terminal point. Appears only if VCE port check box has been selected.
DirectionA pull-down menu with a limited selection: Up or Down. Select the desired direction.
PortThe port used by this MEP. Appears only if VCE port check box has not been selected.
DirectionThe direction in which the MEP faces on the Bridge port. Refer to IEEE802.1ag for more information.
  • Up: The MEP resides in a bridge that transmits CFM PDUs toward and receives them from, the direction of the Bridge Relay Entity. Up MEP points toward the Bridge Relay Entity.
  • Down: The MEP resides in a Bridge that receives CFM PDUs from, and transmits them toward, the direction of the LAN. Down MEP points away the Bridge Relay Entity.
MEP NameThe name of the Maintenance association End Point.
ActiveThe administrative state of the MEP:
  • Checked (Yes): The MEP is to function normally.
  • Unchecked (No): The MEP is to cease functioning.
Note: When deactivating a MEP, you must also deactivate all DMM, SLM and Frame Loss instances that use this MEP. Doing so will stop the unit from sending DMM and SLM frames and prevent the units from detecting unwanted alarms, such as CCM alarms.
CCI EnableIndicates whether or not the MEP generates CCM messages:
  • Checked (Enabled): The MEP generates CCM messages.
  • Description Unchecked (Disabled): The MEP does not generate CCM messages.
CCM Sequence NumberWhen enabled, a MEP transmits CCMs with a sequence number that increases by one for each CCM. When disabled, a MEP transmits CCMs with a sequence number set to zero.

Note: A peer MEP should have the sequence number enabled to allow a local MEP to perform CCM-based frame loss measurements.

Primary VID VLANThe Primary VLAN ID of the MEP. This is always one of the VLAN IDs assigned to the MEP's MA/MEG. The value 0 indicates that either the Primary VLAN ID is that of the MEP's MA/MEG, or that the MEP's MA/MEG is not associated with a VLAN ID.
CCM, LTM and CSF PriorityPriority parameter for CCMs, LTMs and CSFs transmitted by the MEP. The possible values are 0–7, with 7 being the highest value allowed to pass through the Bridge Port for any of this MEP's VLAN IDs.

Default value: 7 (highest priority)

Lowest Priority Defect AlarmLowest priority defect that is allowed to generate a CFM Fault Alarm.
Fault Notification Alarm TimeThe period of time, expressed in milliseconds, for which defects must be present before a Fault Alarm is issued.
Fault Notification Reset TimeThe period of time, expressed in milliseconds, for which defects must be absent before resetting a Fault Alarm.

EVC Client Interface (The EVC client is the client of a service.)

ParameterDescription
Interface Status TLV EnableCheck box to enable or disable the interface status TLV on a MEP.
  • For a down MEP, the client interface status is used for this TLV.
  • For an up MEP, the status is obtained from the port on which the MEP was created.
CSF EnableCheck box to enable this MEP to transmit Ethernet Client Signal Failure (ETH-CSF) to its peer MEP upon the detection of a failure or defect event in the Ethernet client signal. That port should also be set up to perform EVC fault propagation and that MEP must also be enabled for fault propagation for this parameter to take effect.

Note: A MA/MEG with more than two end points cannot be used and will raise an error.

Enable Fault PropagationCheck box to enable the use of this MEP's status in fault propagation.
Client InterfaceThe EVC client port to which the MEP status should be propagated.

Notes: This parameter is ignored if the port you select has not been set up to perform EVC fault propagation.

For a MEP on a VCE, the client interface is automatically chosen from the VCE configuration. During an add, the client interface will be hidden; during an edit, it will be shown, but will not be editable.

To delete a Maintenance association End Point


CAUTION: Deleting a MEP will also delete all instances (e.g. LTM, LBM) that use this MEP.

  1. Access the page SOAM ▶CFM ▶MEP.

  2. Click the MEPID of the MEP to be deleted.

  3. Click Delete.

Viewing MEP Status

To view maintenance association end point (MEP) status

  1. Access the page SOAM ▶CFM ▶MEP ▶Status.
    A listing of all MEPs is displayed, along with their status codes and details.
    The total number of MEPs found in the system is given in the lower-left corner of the page, as well as the index values of the items currently displayed on-screen (for example, [1–25] of 54). Use the page navigation links in the lower-right corner of the page to move between the pages of results.

  2. (Optional) To limit the view to only certain MEPs, enter a value on which to filter, then click Search. You can filter by the index value, MEPID, database, or by any of the provided status codes.


    Note: Enter an asterisk ( * ) as a wildcard to replace one or several characters.

  3. Click any MEPID to view detailed status of this MEP.

For more information on specific parameters, refer to the following table.

MEP Status (SOAM ▶CFM ▶MEP ▶Status

ParameterDescription
IndexIndex assigned to the Maintenance association End Point.
DBLink to this MEP's database.
Next LBM Sequence NumberNext sequence number/transaction identifier to be sent in a loopback message.

Note: The sequence number restarts at zero once the counter has reached its limit.

Next LTM Sequence NumberNext sequence number/transaction identifier to be sent in a link trace message.

Note: The sequence number restarts at zero once the counter has reached its limit.

Fault Notifications StateThe possible values are:
  • Reset
  • Defect
  • Report defect
  • Defect reported
  • Defect clearing
Highest Defect PriorityThe highest defect priority sent. The possible values are:
  • None
  • RDI CCM
  • MAC status
  • Remote CCM
  • Error CCM
  • Xcon CCM
  • AIS

Defects (Alarm Conditions)

ParameterDescription
RDI

CCM RDI

The latest CCM received by this MEP from a remote MEP containing the Remote Defect Indication (RDI) bit.

Possible values are Active (A) or Inactive (I).

MAC

MAC Status

The last CCM received by this MEP from a remote MEP indicates that the transmitting MEP's associated MAC is reporting an error status via the Port Status TLV or Interface Status TLV.

Possible values are Active (A) or Inactive (I)

R-CCM

Remote CCM

Indicates whether the MEP is not receiving CCMs from a MEP in its configured list.

Possible values are Active (A) or Inactive (I)

E-CCM

Errored CCM

Indicates whether the MEP is receiving invalid CCM messages.

Possible values are Active (A) or Inactive (I)

X-CCM

Cross-Connect CCM

Indicates whether the MEP is receiving CCM messages that could be coming from another MA.

Possible values are Active (A) or Inactive (I)

AIS

Received AIS

Indicates whether Y.1731 Alarm Indication Signal (AIS) PDUs are being received.

Possible values are Active (A) or Inactive (I)

EPL

Excessive Packet Loss

Indicates whether some packet loss measurement defect is Active (A) or Inactive (I) for that MEP.
EDM

Excessive Delay

Indicates whether some delay measurement defect is Active (A) or Inactive (I) for that MEP.
C-LOS

Received C-LOS

Indicates whether Y.1731 Client Signal Fail (CSF) Loss of Signal (LOS) PDUs are being received

Possible values are Active (A) or Inactive (I)

C-FDI

Received C-FDI

Indicates whether Y.1731 Client Signal Fail (CSF) Forward Defect Indication (FDI) PDUs are being received

Possible values are Active (A) or Inactive (I)

C-RDI

Received C-RDI

Indicates whether Y.1731 Client Signal Fail (CSF) Reverse Defect Indication (RDI) PDUs are being received

Possible values are Active (A) or Inactive (I)

N-SLMThe Near-End Synthetic Loss Measurement indicates whether nearend synthetic loss messages are Active (A) or Inactive (I) for that MEP.
F-SLMThe Far-End Synthetic Loss Measurement indicates whether far-end synthetic loss messages are Active (A) or Inactive (I) for that MEP.

Loopback (The status of the latest loopback request initiated from that MEP)

ParameterDescription
Loopback RequestIndicates whether the loopback request process are active for that MEP.
Latest Start TimeIndicates the time at which the latest loopback request was initiated from that MEP.
Latest End TimeIndicates the time at which the latest loopback request from that MEP was completed or was stopped.
Nbr LBM RequestedIndicates the number of loopback messages requested.
Nbr LBM SentIndicates the number of loopback messages transmitted.
Nbr LBR ReceivedIndicates the number of loopback replies received.
LBR with Bad MSDUIndicates the number of loopback replies received whose content did not match the corresponding LBM.
Nbr LBR DuplicatedIndicates the number of loopback replies received with a duplicate LBR sequence number.
Packet Loss RatioIndicates the packet loss ratio evaluated during the latest request.
Nbr Packets LostIndicates the number of loopback replies missing.
Nbr GapsIndicates the number of gaps evaluated inside the LBR stream.
Largest Gap SizeIndicates the number of missing frames for the largest gap.
Nbr LBR Out of OrderIndicates the number of LBRs received whose sequence number did not match the expected value.

Viewing the MEP Database

The MEP database gives you information about remote MEPs.

To view database information for MEPs

  1. Access the page SOAM ▶CFM ▶MEP ▶Status.

  2. Click the MEP database identifier for which you want to view a summary.

  3. Click any MEPID to view detailed database information.

For more information on specific parameters, refer to the following table.

MEP Database (SOAM ▶CFM ▶MEP ▶Status ▶[Database])

ParameterDescription
MEP IndexMaintenance association End Point index of the local unit.
MEPIDMaintenance association End Point identifier of the remote MEP whose information from the MEP Database is to be returned.
StateThe operational state of the remote MEP IFF state machines.

Possible values are:

  • Idle: If the local MEP is disabled, then all remote MEP IDs in that MA/MEG will remain idle.
  • Start: MEP monitoring has started, but no MEPs have been received.
  • Failed: MEP messages were not received, or received late.
  • OK: Valid MEP messages have been received.
RDIThe state of the RDI bit in the last received CCM. Possible values are:
  • True: The RDI bit was set.
  • False: The RDI bit was not set, no CCM message was received.
Mac AddressThe MAC address of the remote MEP.
Latest Failed-OK TimeThe time at which the IFF Remote MEP state machine last entered either the failed or OK state.
Port Status TLVThe value of the port status TLV received in the last CCM from the remote MEP (see section 21.5.4 Port Status TLV of 802.1ag for details).

Possible values are:

  • --- (none 0): No CCM was received or no port status TLV was received in the last CCM.
  • Blocked (1)
  • Up (2)
Interface Status TLVThe value of the interface status TLV received in the last CCM from the remote MEP (see section 21.5.5 Interface Status TLV of 802.1ag for details).

Possible values are:

  • --- (0): No CCM was received or no interface status TLV was received in the last CCM.
  • Up (1)
  • Down (2)
  • Testing (3)
  • Unknown (4)
  • Dormant (5)
  • Not Present (6)
  • Lower Layer Down (7)

Viewing MEP Statistics

To view MEP statistics

  1. Access the page SOAM ▶CFM ▶MEP ▶Statistics.
    A summary of statistics of all MEPs is displayed.

  2. Click any MEPID to view detailed statistics of this MEP.

For more information on specific parameters, refer to the following table.

MEP Statistics (SOAM ▶CFM ▶MEP ▶Statistics)

ParameterDescription
Index

MEP Index

Index assigned to the Maintenance association End Point.
MEPIDMaintenance association End Point Identifier.
CCM Sent

CCM

Indicates the number of connectivity check messages sent by this MEP.
CCM Received

CCM

Indicates the number of connectivity check messages received by this MEP.
RDI Sent

CCM with RDI

Indicates the number of connectivity check messages sent by this MEP with the RDI bit set.
RDI Received

CCM with RDI

Indicates the number of connectivity check messages received by this MEP with the RDI bit set.
CCM Seq Error

CCM Received

Sequence Errors

Indicates the total number of out-of-sequence CCMs received from all remote MEPs.
LBMIndicates the number of loopback messages sent and received by this MEP.
LBRIndicates the number of loopback responses sent and received by this MEP.
LTMIndicates the number of linktrace messages sent and received by this MEP.
LTRIndicates the number of linktrace responses sent and received by this MEP.
CSFIndicates the number of client signal failure messages sent and received by this MEP.
DMMIndicates the number of delay measurement messages sent and received by this MEP per VLAN priority.
DMRIndicates the number of delay measurement responses sent and received by this MEP per VLAN priority.
SLMIndicates the number of synthetic loss messages sent and received by this MEP per VLAN priority.
SLRIndicates the number of synthetic loss responses sent and received by this MEP per VLAN priority.
Unexpected LBRIndicates the total number of LBRs received when no loopback request is active for that MEP.
LBR Out of OrderIndicates the total number of valid, out-of-order loopback replies received.
LBR with Bad MSDUIndicates the total number of LBRs received whose Mac Service Data Unit did not match (except for the OpCode) that of the corresponding LBM.
Unexpected LTRIndicates the total number of LTRs received when no linktrace request is active for that MEP.
LTR Dropped Bad MACIndicates the total number of link trace replies that were dropped because of an invalid MAC address.
DMR priority mismatchIndicates the total number of DMRs received whose VLAN priority value did not match that of the corresponding DMM.

© 2024 Cisco and/or its affiliates. All rights reserved.
 
For more information about trademarks, please visit: Cisco trademarks
For more information about legal terms, please visit: Cisco legal terms

For legal information about Accedian Skylight products, please visit: Accedian legal terms and tradmarks



Was this article helpful?

Changing your password will log you out immediately. Use the new password to log back in.
First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.