- Print
- PDF
Overview
Skylight performance elements support Service Availability (SA) to determine the number of unavailable seconds and other counts for a specific service.
You can define Service Availability instances with one or more SA metrics (criteria) that will be used to determine unavailable seconds. Each criterion has its own threshold. The basic criteria for determining unavailable seconds, as defined in the MEF 10.2 Technical Specification, is the CFM packet loss.
The unit supports these SA metrics:
- CFM packet loss
- DMM one-way delay
- DMM one-way delay variation
- DMM two-way delay
- DMM two-way delay variation
- PAA packet loss
- PAA one-way delay
- PAA one-way delay variation
- PAA two-way delay
- PAA two-way delay variation
- SLM near end packet loss
- SLM far end packet loss
This specific article describes how to set up Service Availability on Skylight performance elements to monitor a point-to-point service using a CFM Packet Loss metric and a CFM DMM one-way delay metric.
Configuration Example
Skylight performance elements are configured in the same way, according to the following procedure:
Step #1: Add an MA/MEG
Set up a Maintenance Association or Maintenance Entity Group.
To add an MA/MEG
Access SOAM ▶ CFM ▶ MA/MEG.
Click Add.
Select an MD level that fits your network requirements, enter a Name for this MA/MEG, and enter the MEPID list associated with this MA/MEG (for example: 1, 2).
Note: The MA/MEG Name must be identical in each unit.Complete the other fields as required and then click Apply.
Step #2: Add an MEP
Set up a Maintenance Endpoint.
To add an MEP
Access SOAM ▶ CFM ▶ MEP ▶ Configuration.
Click Add.
Select the MA/MEG that was set up in the previous step, select the MEPID for each unit, and select Active.
Note: In this example, you will set MEPID to 1 for the NODE and to 2 for the NID.
- Complete the other fields as required and then click Apply to start the CCM.
Note: The local MEP starts sending CCM frames, but will display continuity errors. You must configure the other end-point for valid results to display.
Step #3: Add a CFM Packet Loss Instance
Set up the Connectivity Fault Management (CFM) Packet Loss instance.
To add a CFM Packet Loss Instance
Access SOAM ▶ CFM ▶ Packet loss ▶ Configuration.
Click Add.
Enter the PL Name. For example: CFM_PacketLoss.
Complete the remaining fields as needed and then click Apply.
Note: Take note of the PL Name since you will need to enter it when adding this CFM packet loss instance as an SA metric.
Step #4: Add a CFM DMM Instance
To add a CFM DMM Instance
Access SOAM ▶ CFM ▶ DMM ▶ Configuration.
Click Add.
Enter the DMM Name. For example: CFM_DMM_OWD.
Complete the remaining fields as needed and then click Apply.
Notes:
All units must be synchronized to a valid timing source (NTP, PTP or GPS) to perform accurate one-way measurements.
Take note of this name since you will need to enter it when adding this CFM DMM instance as an SA metric.
Step #5: Add an SA Instance
Set up the Service Availability (SA) instance.
To add an SA Instance
Access SOAM ▶ SA ▶ Configuration.
Click Add.
Complete the required fields and then click Apply.
Note: A newly added SA instance is out of service. You will need to put it in service after you add the SA metrics.
Step #6: Add SA Metrics
You must add one or more SA metrics for each SA instance. In this example, we will add the Packet Loss and the DMM delay metric that we set up above.
CAUTION: Once an SA metric has been set up using either a CFM DMM instance, CFM Packet Loss instance or PAA probe as the metric source, deleting the metric will also delete all SA metrics that are using it.
To add SA Metrics
Access SOAM ▶ SA ▶ Configuration.
Click the SA instance Name of the SA instance you want to edit.
Click Add.
Select the Metric type of CFM packet loss.
Enter a Name for this metric. For example: MetricPacketLoss.
Enter the Metric source name. For example: CFM_PacketLoss.
Note: Use the same Metric source name as used when defining the CFM packet loss instance.Set the Threshold for this metric and then click Apply.
Go back to SOAM ▶ SA ▶ Configuration.
Click the SA instance Name of the SA instance you want to edit.
At the bottom of the page, click Add to create a new SA metric.
In Metric type, select DMM one-way delay.
Enter a Name for this metric. For example: MetricDMM_OWD.
Enter the Metric source name. For example: CFMDMMOWD.
Note: Use the same Metric source name as used when defining the CFM DMM one-way delay instance.Set the Threshold for this metric and then click Apply.
Step #7: Put the SA Instance into Service
Once you have configured the SA Metrics, you need to put the SA instance into service.
To put the SA Instance into Service
Access SOAM ▶ SA ▶ Configuration.
Click SA instance name of the SA instance you created.
Select State of In service and then click Apply.
Repeat all steps above for the other unit.
Step #8: View the SA Counters
Once the SA instance and its metrics are configured on both units, you can view a summary of all Service Availability.
To view SA Counters
Access SOAM ▶ SA ▶ Counters.
Click an SA instance Name to view the detailed counters for this SA instance.
© 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