- Print
- PDF
Provider Connectivity Assurance Gateway 24.09 Release Notes
These release notes cover the prerequisites, features, and limitations of the Cisco Provider Connectivity Assurance Gateway (formerly Skylight Gateway) 24.09 release. Read this document before using the gateway YANG interface.
For further information, questions, or clarifications regarding this release, contact the Provider Connectivity Assurance Technical Assistance Center (PCATAC) at skylight_tac@cisco.com.
Prerequisites
Package Name | Version |
---|---|
Provider Connectivity Assurance Gateway | 0.113.0 |
Skylight Sensor Orchestrate | 0.194.0 |
Skylight Essential installer | 15.111.55 Note: https://software.accedian.io/skylight/installer/release/24.09/skylight-installer-15.111.55.tar.gz |
Cisco Provider Connectivity Assurance Sensor Agents (formerly Skylight sensor: agents) | 24.09 |
Skylight orchestrator | 24.09 Note: Available on http://software.cisco.com/ |
Cisco Provider Connectivity Assurance Sensor Control (formerly Skylight sensor: control) | 24.09 Note: Available on Salesforce |
YANG Model | *@2024-09-nnn.yang Note: https://github.com/Accedian/skylight-yang/tree/main/skylight-gateway |
Features
Provider Connectivity Assurance Gateway version 24.09 has the following features:
Extended intent model
- Integration of the Service Activation Test (SAT) feature on SFP compute, supporting both RFC2544 and Y.1564 type throughput tests.
Metadata tags added
- For individual Session objects
- For Service object, applied to all sessions in the service
Topology metadata for Session objects
Support for geo-location tags on the service-endpoint objects
- Populates the source and destination lat/long settings for sessions between two endpoints
Threshold crossing alert policy configuration
- On Service object, applied to sessions tied to this Service
RESTCONF Notification support for
- service-endpoint state changes
- session state changes
- alerts from alert policies
Related Documentation
Document | Description |
---|---|
Setting up NSO with Provider Connectivity Assurance | How to set up and use Cisco NSO together with Provider Connectivity Assurance |
Service Model | Overview of the YANG service model used for endpoints, sessions, services, and alerts |
Service Endpoints | Details on the service-endpoint objects |
TWAMP and Metadata | Details on TWAMP sessions and Metadata |
Service Activation Testing (RFC2544 & Y.1564) | Details on Service Activation Tests (SAT) |
Session State and Threshold Crossing Notifications over RESTCONF | Details on RESTCONF notifications and alert policy configuration |
Notes
- If an Agent, Sensor SFP, or Sensor Control is removed manually while sessions are running, sessions will create an error in the Gateway. The Gateway will fail to delete sessions because the endpoint is not ready. To avoid this issue, remove the session from the YANG before deleting an agent.
- The error path returns the URI provided in the request; if the request targets a list node instead of a specific instance, the error path will show the list URI, not the instance.
- The YANG datastore model is the master “view” of the configuration, therefore, the resync will attempt to re-configure the orchestrator(s) if there is a discrepancy between the two configurations.
- If the resync fails to push a mismatched configuration to the Agent orchestrator, the instance is flagged as an error at the YANG level.
- Bulk services can be created on a single POST operation.
- Bulk sessions can be created on a single POST operation.
Limitations
Provider Connectivity Assurance Gateway version 0.113.0 has the following limitations:
Error limitation:
- Error-path is not included in the message from the ODL framework if constraint limits are reached.
Deployment limitations:
- Supported PCA actuators and devices: Agent actuate, Sensor Control, Sensor SFP
YANG limitations:
- Even though the YANG model supports 128 characters, the session name should be kept at 64 characters maximum, as there is a limitation in Agents.
- Session Auto-Start is not supported.
Notification limitation:
- Without retention time, because start time is not supported, the client must keep the connection open to receive notifications.
IPv6 limitation:
- Current version 24.09 is limited in terms of IPv6 support. Sensor Collector (formerly Roadrunner) needs to connect to the NGINX in IPv4.
CRUD limitations:
- Changing parameters from a Session/Endpoint/Service is not supported. In this version, you need to delete and recreate. (add/del in the list is supported with PUT/DELETE)
- PATCH operation is not supported.
- PUT operation is not supported to edit, it can only be used to create an instance.
Addressed Issues
None
© 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