Skyline EPM Platform
About
The Skyline EPM Platform connector allows the aggregation of KPIs from different collector elements deployed for different types of infrastructures.
This is an Experience and Performance Management connector, and as such it is designed to handle large amounts of data from the deployed infrastructures.
Skyline EPM Platform is the frontend connector of the EPM Solution. A deployed EPM Solution contains one Skyline EPM Platform frontend element and can have one or multiple backend elements (using Skyline EPM Platform DOCSIS). The Skyline EPM Platform frontend element is responsible for the top-level data aggregation from different backend elements. Each backend element is responsible for the aggregation of the data from the collectors.
Different topologies are presented in the Skyline EPM Platform. These topologies are diagrams shown in Visual Overview, which describe the connections between the entities of the different infrastructures. The current implementation integrates the following topologies: DOCSIS Network, DOCSIS Service, Network, and Quick. Each topology represents a connected entity from top to bottom. The following chains are present:
DOCSIS Network
- Network
- Market
- Hub
- CCAP Core
- DS Line Cards - US Line Cards
- DS Ports - US Ports
- Node Segment
- CM
DOCSIS Service
- DOCSIS Network
- DOCSIS Market
- DOCSIS Hub
- CCAP Core
- Service Group [Fiber Node]
- DS Service Group - US Service Group
- CM
DOCSIS Passives
- Node
- Amplifier
- Tap
- CM
GPON Service
- GPON Network
- GPON Market
- GPON Hub
- OLT
- Slot
- Port
- ONT
DOCSIS Quick
- Allows you to quickly access the DOCSIS topology level by selecting the desired filter.
GPON Quick
- Allows you to quickly access the GPON topology level by selecting the desired filter (including Split Route, Split Distribution, Split FAT).
Configuration
- Allows you to place Visual Overview layouts on a separate chain.
Version Info
| Range | Key Features | Based on | System Impact |
|---|---|---|---|
| 1.0.0.x | Initial version. | - | - |
| 1.0.1.x | Integration of PNM KPIs. | - | - |
| 1.0.2.x | Decoupling and enhancements. | - | - |
| 1.0.3.x | Remote view tables retrieve information from multiple source elements. | - | - |
| 1.0.4.x | - Partial table option enabled on several tables to improve loading time of the filter box for the EPM topology. - Parameter added that lets the user change the name of the automation script that notifies the CCAPs/CM collector pairs of new data to be ingested. |
- | - |
| 1.0.5.x | New exceptions added for the correction of the default value for average percentage US and DS utilization. | - | - |
| 1.0.6.x | Quick topology for GPON now contains Split Route, Split Distribution, and Split FAT. Generic Split level was removed. | - | - |
| 1.0.7.x | Remote views removed from DOCSIS CPE level (Cable Modem, QAM Channels). | - | - |
| 1.0.8.x | Remote views removed from GPON CPE level (ONT). | - | - |
| 1.0.9.x | Organization and grouping for KPIs through GPON Service, DOCSIS Network, and DOCSIS Service topologies. | - | - |
| 1.0.10.x | Tables ordered in the same way as on the overview page. | - | - |
| 1.0.11.x | Removed extra hyphens from thresholds page. | - | - |
| 1.0.12.x [SLC Main] | The GPON Network/Market/Hub Overview tables now includes new Rx Power states to provide more specific and accurate status information. | 1.0.11.4 | Table IDs changed. |
Product Info
| Range | Supported Firmware |
|---|---|
| 1.0.0.x | N/A |
| 1.0.1.x | N/A |
| 1.0.2.x | N/A |
| 1.0.3.x | N/A |
| 1.0.4.x | N/A |
| 1.0.5.x | N/A |
| 1.0.6.x | N/A |
| 1.0.7.x | N/A |
| 1.0.8.x | N/A |
| 1.0.9.x | N/A |
| 1.0.10.x | N/A |
| 1.0.11.x | N/A |
| 1.0.12.x | N/A |
System Info
| Range | DCF Integration | Cassandra Compliant | Linked Components | Exported Components |
|---|---|---|---|---|
| 1.0.0.x | No | Yes | - | - |
| 1.0.1.x | No | Yes | - | - |
| 1.0.2.x | No | Yes | - | - |
| 1.0.3.x | No | Yes | - | - |
| 1.0.4.x | No | Yes | - | - |
| 1.0.5.x | No | Yes | - | - |
| 1.0.6.x | No | Yes | - | - |
| 1.0.7.x | No | Yes | - | - |
| 1.0.8.x | No | Yes | - | - |
| 1.0.9.x | No | Yes | - | - |
| 1.0.10.x | No | Yes | - | - |
| 1.0.11.x | No | Yes | - | - |
| 1.0.12.x | No | Yes | Automation scripts: - EpmBeToOlt - EpmBeToOltPassives Generic KAFKA Consumer Connectors: - ZTE ZXA10 C600 GPON Platform - Huawei 5600-5800 GPON Platform - Nokia ISAM 7300 FX GPON Platform - Skyline EPM Platform GPON |
- |
Configuration
Connections
Virtual Connection
This connector uses a virtual connection and does not require any input during element creation.
Initialization
When you create a Skyline Platform EPM element, you need to configure the following data:
- Define the File Import Path on the Configuration page. This same directory must be configured on all the elements of the EPM Solution.
- Define the File Export Path on the Configuration page. This same directory must be configured on all the elements of the EPM Solution.
- If the File Import Path or File Export Path are in a remote location, fill in the Username and Password fields in the System Credentials section of the Configuration page.
- Add the DOCSIS backend elements to the Backend Registration table on the Frontend page.
- Add the GPON backend elements to the Backend Registration GPON table on the Frontend page.
- Add the Generic DOCSIS CM Collector elements in the DOCSIS Collector Registration table on the Frontend page.
- Add the PON OLT elements in the GPON Collector Registration table on the Frontend page.
Provisioning
The provisioning of the EPM Solution is sequential and involves the following components:
- Skyline Platform EPM: Responsible for the top-level data aggregation and for displaying the topologies.
- Skyline Platform EPM DOCSIS: In charge of the data aggregation from the collectors.
- Skyline Platform EPM GPON: In charge of the data aggregation from the OLTs.
- CCAP Platform: In charge of polling data from the different CMTSs.
- GPON Platform: In charge of polling data from the different OLTs.
- Generic DOCSIS CM Collector: Retrieves information from each individual available cable modem.
- Skyline Platform EPM DOCSIS WM: Creates compatible files regarding the passives available within the DOCSIS infrastructure.
- Skyline Platform EPM GPON WM: Creates compatible files regarding the passives available within the GPON infrastructure and the KAFKA OLT KPIs.
Thresholds Settings
In the threshold tables, you can define limits for each polled modulation. Two threshold tables are available: one for upstream and one for downstream.
The QAM thresholds tables are located under DOCSIS thresholds settings > upstream/downstream QAM channels.
These tables will serve as a multiple set function for all CCAP and CM collectors. Once the Apply button is clicked, the table settings will be applied to the active elements.
These are the available Key Performance Indicators (KPIs) for setting upstream thresholds:
- Maximum Timing Offset Level: Range from 0 to 10000 µs.
- Minimum Rx Power Level: Range from -12 to 12 dBmV.
- Maximum Rx Power Level: Range from -12 to 12 dBmV.
- Minimum SNR Level: Range from 10 to 60 dB.
- Post-FEC Maximum Uncorrectable Error Ratio Level: Range from 0 to 30000 ppm.
- Minimum Tx Power Level: Range from 25 to 55 dBmV.
- Maximum Tx Power Level: Range from 25 to 55 dBmV.
These are the available KPIs for setting downstream thresholds:
- Minimum Rx Power Level: Range from -16 to 20 dBmV.
- Maximum Rx Power Level: Range from -16 to 20 dBmV.
- Minimum SNR Level: Range from 0 to 100 dB.
- Post-FEC Maximum Uncorrectable Error Ratio Level: Range from 0 to 30000 ppm.
Under DOCSIS thresholds settings > upstream/downstream QAM channels, you will also find the PNM threshold parameters.
These are the available PNM parameters that can be modified:
- Velocity Factor (VF) for Coax Cable: Range from 0 to 1.
- Non-Main Tap Energy Ratio (NMTER) Threshold: Range from -50 to 0 dB.
- Post-Main Tap to Total Energy Ratio (PostMTTER) Threshold: Range from -50 to 0 dB.
- Pre-Main Tap to Total Energy Ratio (PreMTTER) Threshold: Range from -50 to 0 dB.
How to Use
The solution is based on the usage of CSV files and the DataMiner messaging system using information events.
The CCAP Platform and GPON Platform elements export the necessary files containing the resources that need to be assigned DataMiner IDs. These elements notify the Skyline Platform EPM frontend element, which in turn initiates the ID assignment process. The ID request notifications will be handled in a FIFO (First-In -First-Out) fashion to ensure the sequential processing of requests. The frontend element will import the CSV files in order to perform the necessary steps of the provisioning.
Once the ID assignment is completed, the frontend element will export a series of CSVs. For DOCSIS, the files will be imported by the Skyline Platform EPM DOCSIS backend, CCAP Platform, and Generic DOCSIS CM Collector elements. For GPON, the files will be imported by the Skyline Platform EPM GPON backend and OLT Platform elements. For this process to occur, the frontend element notifies the respective backend element to process these files. The backend element imports the resources with their assigned IDs and notifies the respective OLT Platform or CCAP Platform and Generic DOCSIS CM Collector elements of ID assignment completion (these elements will import the new files).
For DOCSIS, the backend elements are in charge of requesting the passives from the CMTS devices that they have assigned. For this, each backend element sends a request every 24 hours to their respective Skyline Platform EPM DOCSIS WM element. This second element receives the request, creates the required passive CSV files, and notifies the backend element. The backend element then notifies the frontend element that its passive files are available and requests the ID assignment. Once this process is finished, the frontend element informs the backend element, and it imports the passive resources with their assigned IDs.
The Provision button makes the element import and export all files and add any new entities. This will notify the backend, Platform, and Generic DOCSIS CM Collector elements that they need to perform the import.
The Reset button will remove existing data from tables and performs provisioning logic to remove any erroneous data.
In range 1.0.4.x, the Script Name parameter is added, which allows you to change the automation script to be executed. This parameter is available on the Configuration page.
In range 1.0.11.4, the Automatic CMTS Removal toggle button is added on the Configuration page and on the Visual page of the element. It allows you to enable or disable automatic CMTS removal on the frontend element and on all active backend elements in the system. Whenever you use the button, you will need to confirm this action in a pop-up window.
Notes
The messaging system integration requires the use of correlation rules and automation scripts that will pick up on the information events and send the corresponding message to a message listener to begin the logical flow.