- 25 Jan 2024
- 22 Minutes to read
- Contributors
- Print
- PDF
Using Service OAM
- Updated on 25 Jan 2024
- 22 Minutes to read
- Contributors
- Print
- PDF
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
The diagram below shows a typical setup scenario for Service OAM.
Typical Setup Scenario for Service OAM
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
- 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)
Parameter | Description |
---|---|
Port | The port on which MEPs or MIPs have been configured. |
VID | The VLAN ID to which the Maintenance Point is attached, or 0, if there is no VLAN ID. |
Level | The MD level (or MEG level) of the Maintenance Point. Possible values: 0–7. |
Dir | The direction in which the MEP or MIPs faces on the port. |
MD idx | The index of the Maintenance Domain with which the MEP or MIP is |
associated. | |
MA idx | The index of MA (or MEG) with which the MEP or MIP is associated. |
MEPID | The MEPID of the MEP or MIP (MEPID of MIP is 0). |
MAC Address | The 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
Access the page SOAM ▶CFM ▶MD.
A listing of all existing Maintenance Domains is displayed.Click the Add button to add a new Maintenance Domain or click the name of an existing Maintenance Domain to edit its settings.
Complete the required fields, then click Apply.
For more information on specific parameters, refer to the following table.
Maintenance Domain (SOAM ▶CFM ▶MD)
Parameter | Description |
---|---|
Index | Unique index assigned to the Maintenance Domain. |
Name Format | The format of the Maintenance Domain name.
|
Name MD Name | Unique name for the Maintenance Domain. |
Level | Maintenance level of the Maintenance Domain. Possible values: 0–7 |
MHF Creation | Indicates whether the management entity can create MHFs for VIDs on which no Up MEP is configured. Possible values are:
|
Sender ID Permission | The information (if any) to be included in the Sender ID TLV transmitted in CCMs, LBMs, LTMs and LTRs. The available values are:
|
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
Access the page SOAM ▶CFM ▶MD.
Click the name of the MD instance to delete.
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
Access the page SOAM ▶CFM ▶MA/MEG.
A listing of all Maintenance Associations / Maintenance Entity Groups is displayed.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.
Complete the required fields, then click Apply.
For more information on specific parameters, refer to the following table.
Maintenance Association (SOAM ▶CFM ▶MA/MEG)
Parameter | Description |
---|---|
MA/MEG Index Index | Unique index value assigned to the Maintenance Association or Maintenance Entity Group. |
MD Index | Unique index value assigned to the Maintenance Domain for this Maintenance Association or Maintenance Entity Group. |
MD | Maintenance Domain for this Maintenance Association or Maintenance Entity Group. |
Name Format | The format of the Maintenance Association or Maintenance Entity Group name. Possible values are:
|
MAID string format mode | Indicates 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:
|
Name | The name of this Maintenance Association or Maintenance |
MA/MEG Name | Entity Group. |
Level | Maintenance Level of the Maintenance Association or Maintenance Entity Group. Possible values: 0–7 |
CCM Interval | The required time interval between Continuity Check Messages (CCM). Expressed in milliseconds. Default: 1,000 milliseconds |
MHF Creation | Indicates whether the management entity can create MHFs for VIDs on which no Up MEP has been configured. Possible values are:
|
Sender ID Permission | Determines what, if anything, is to be included in the Sender ID TLV transmitted in CCMs, LBMs, LTMs and LTRs. Possible values are:
|
Use VCE | Select this box to enable VCE for use. When enabled, another field is shown: VCE Name allowing you to select the VCE to use. |
VCE Name | Type the name of the VCE you wish to use. |
ComponentID | An unsigned integer identifying the VLAN bridge component in the system. |
VLAN Type | The VLAN type associated with this Maintenance Association or Maintenance Entity Group. Possible values are:
|
VLAN ID List | A 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-Discovery | Select 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 List | A 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.
Access the page SOAM ▶CFM ▶MA/MEG.
Click the name of the Maintenance Association or Maintenance Entity Group name to delete.
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
Access the page SOAM ▶CFM ▶MEP ▶Configuration.
A listing of all existing Maintenance association End Points is displayed.Click the Add button to add a new MEP or click the MEPID of an existing MEP to edit its settings.
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)
Parameter | Description |
---|---|
Index | The index value assigned to the Maintenance association End Point. |
MA/MEG Name | The name of the maintenance association (or MEG) to associate with the MEP. |
MEPID | Maintenance 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 port | A check box to enable use of a VCE port. Once selected, other options appear in the dialog. |
VCE Name | The name of the VCE that you wish to use. Appears only if VCE port check box has been selected. |
TP | A 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. |
Direction | A pull-down menu with a limited selection: Up or Down. Select the desired direction. |
Port | The port used by this MEP. Appears only if VCE port check box has not been selected. |
Direction | The direction in which the MEP faces on the Bridge port. Refer to IEEE802.1ag for more information.
|
MEP Name | The name of the Maintenance association End Point. |
Active | The administrative state of the MEP:
|
CCI Enable | Indicates whether or not the MEP generates CCM messages:
|
CCM Sequence Number | When 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 VLAN | The 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 Priority | Priority 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 Alarm | Lowest priority defect that is allowed to generate a CFM Fault Alarm. |
Fault Notification Alarm Time | The period of time, expressed in milliseconds, for which defects must be present before a Fault Alarm is issued. |
Fault Notification Reset Time | The 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.)
Parameter | Description |
---|---|
Interface Status TLV Enable | Check box to enable or disable the interface status TLV on a MEP.
|
CSF Enable | Check 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 Propagation | Check box to enable the use of this MEP's status in fault propagation. |
Client Interface | The 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.
Access the page SOAM ▶CFM ▶MEP.
Click the MEPID of the MEP to be deleted.
Click Delete.
Viewing MEP Status
To view maintenance association end point (MEP) status
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.(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.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
Parameter | Description |
---|---|
Index | Index assigned to the Maintenance association End Point. |
DB | Link to this MEP's database. |
Next LBM Sequence Number | Next 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 Number | Next 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 State | The possible values are:
|
Highest Defect Priority | The highest defect priority sent. The possible values are:
|
Defects (Alarm Conditions)
Parameter | Description |
---|---|
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-SLM | The Near-End Synthetic Loss Measurement indicates whether nearend synthetic loss messages are Active (A) or Inactive (I) for that MEP. |
F-SLM | The 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)
Parameter | Description |
---|---|
Loopback Request | Indicates whether the loopback request process are active for that MEP. |
Latest Start Time | Indicates the time at which the latest loopback request was initiated from that MEP. |
Latest End Time | Indicates the time at which the latest loopback request from that MEP was completed or was stopped. |
Nbr LBM Requested | Indicates the number of loopback messages requested. |
Nbr LBM Sent | Indicates the number of loopback messages transmitted. |
Nbr LBR Received | Indicates the number of loopback replies received. |
LBR with Bad MSDU | Indicates the number of loopback replies received whose content did not match the corresponding LBM. |
Nbr LBR Duplicated | Indicates the number of loopback replies received with a duplicate LBR sequence number. |
Packet Loss Ratio | Indicates the packet loss ratio evaluated during the latest request. |
Nbr Packets Lost | Indicates the number of loopback replies missing. |
Nbr Gaps | Indicates the number of gaps evaluated inside the LBR stream. |
Largest Gap Size | Indicates the number of missing frames for the largest gap. |
Nbr LBR Out of Order | Indicates 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
Access the page SOAM ▶CFM ▶MEP ▶Status.
Click the MEP database identifier for which you want to view a summary.
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])
Parameter | Description |
---|---|
MEP Index | Maintenance association End Point index of the local unit. |
MEPID | Maintenance association End Point identifier of the remote MEP whose information from the MEP Database is to be returned. |
State | The operational state of the remote MEP IFF state machines. Possible values are:
|
RDI | The state of the RDI bit in the last received CCM. Possible values are:
|
Mac Address | The MAC address of the remote MEP. |
Latest Failed-OK Time | The time at which the IFF Remote MEP state machine last entered either the failed or OK state. |
Port Status TLV | The 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:
|
Interface Status TLV | The 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:
|
Viewing MEP Statistics
To view MEP statistics
Access the page SOAM ▶CFM ▶MEP ▶Statistics.
A summary of statistics of all MEPs is displayed.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)
Parameter | Description |
---|---|
Index MEP Index | Index assigned to the Maintenance association End Point. |
MEPID | Maintenance 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. |
LBM | Indicates the number of loopback messages sent and received by this MEP. |
LBR | Indicates the number of loopback responses sent and received by this MEP. |
LTM | Indicates the number of linktrace messages sent and received by this MEP. |
LTR | Indicates the number of linktrace responses sent and received by this MEP. |
CSF | Indicates the number of client signal failure messages sent and received by this MEP. |
DMM | Indicates the number of delay measurement messages sent and received by this MEP per VLAN priority. |
DMR | Indicates the number of delay measurement responses sent and received by this MEP per VLAN priority. |
SLM | Indicates the number of synthetic loss messages sent and received by this MEP per VLAN priority. |
SLR | Indicates the number of synthetic loss responses sent and received by this MEP per VLAN priority. |
Unexpected LBR | Indicates the total number of LBRs received when no loopback request is active for that MEP. |
LBR Out of Order | Indicates the total number of valid, out-of-order loopback replies received. |
LBR with Bad MSDU | Indicates the total number of LBRs received whose Mac Service Data Unit did not match (except for the OpCode) that of the corresponding LBM. |
Unexpected LTR | Indicates the total number of LTRs received when no linktrace request is active for that MEP. |
LTR Dropped Bad MAC | Indicates the total number of link trace replies that were dropped because of an invalid MAC address. |
DMR priority mismatch | Indicates 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