Oi Brazil DSLAM Platform Manager
About
The Oi Brazil DSLAM Platform Manager allows the aggregation of KPIs and dynamic PING statistics from Oi Brazil DSLAM Collectors deployed as part of the Oi Brazil infrastructure.
CPE (Customer Premises Equipment) connectors are designed to poll large amounts of data from the deployed infrastructure. This is done using a frontend CPE Manager element and several backend CPE Manager elements at the same time. Both of these types of elements use the same CPE Manager connector.
The Oi Brazil system has one frontend element (FE) and several backend elements (BEs). The FE is responsible for the top-level data aggregation from the different BEs. Each BE is responsible for the aggregation of a section of the data from the collectors
Topologies describe the connections in the CPE diagram and chains display topology views. The Oi Brazil DSLAM Platform Manager implements five chains:
Location
- DSLAM
- City
- State
- Sub-Region
- Super-Region
Model
- DSLAM
- Model
Station
- DSLAM
- Station
Quick
- Allows you to select the filter DSLAM, City, State, Sub-Region, Super-Region, Model or Station.
Configuration
- Allows you to set up the different configuration options.
Installation and configuration
Creation
Virtual connection
This connector uses a virtual connection and does not require any input during element creation.
Configuration
For each backend element, the following data should be configured:
- Role (backend)
- File import path.
- List of registered collectors.
For each frontend element, the following data should be configured:
- Role (frontend)
- File import path.
- List of registered backend elements.
- List of all the collectors in the system.
Provisioning
The solution requires the pre-provisioning of configuration data. The necessary data will be contained in a .csv file and placed in a specific location (i.e., the Import File Path). The following steps need to be performed:
- Load the .csv file provided by the customer in the frontend element (FE). Based on the number of registered backend elements (BEs), the FE splits the loaded data and export a .csv for each BE. The division of the data is done in a such a way that the load is distributed between the different BEs, and each BE is in charge of a section of the data that does not overlap with another BE. Each BE is responsible for a subset of the available sub-regions.
- Load the .csv files generated by the FE in the BEs. Each BE distributes its assigned DSLAMs between its registered collectors and exports a .csv for each collector.
- Load the .csv files generated by the BEs in the collectors.
Usage
The CPE Manager's Data Display pages are not intended to be opened. Instead, the configuration should be performed through a Visio file or via multiple set.
When the manager element card is open in Cube, the CPE interface will be displayed, with different chains providing a different topology view.
When the filters (on the left side) are filled in, the topology diagram view is displayed.
When a KPI item is selected in this diagram view, a pop-up window with parameters opens.
KPIs
The following Key Point Indicators (KPIs) are calculated on the different levels.
| KPI | Description |
|---|---|
| PING Status OK | The number of DSLAMs with "OK" PING Status. |
| PING Status Unreachable | The number of DSLAMs with "Unreachable" PING Status |
| PING Result | The response time of the last PING query, if it succeeded. |
| PING Result Delta | The difference in the PING result time compared to the previous polling cycle. A negative value indicates a faster PING, a positive value a slower PING. |
| PING Average Time | The average response time of a number of succeeding PING queries. This value is updated after each polling cycle. |
| PING Minimum Time | The minimum response time of a number of succeeding PING queries. This value is updated after each polling cycle. |
| PING Maximum Time | The maximum response time of a number of succeeding PING queries. This value is updated after each polling cycle. |
| PING Average Success | The PING average success in %. This value is updated after each polling cycle. |
| PING Mask Enabled | The number of PING masked DSLAMs. |
| PING Mask Disabled | The number of PING unmasked DSLAMs. |
| Polling Status OK | The number of DSLAMs with "OK" Polling Status. |
| Polling Status Unreachable | The number of DSLAMs with "Unreachable" Polling Status. |
| Eth1 GigE Administration Status Up | The number of DSLAMs with "Up" Eth1 GigE Administration Status. |
| Eth1 GigE Administration Status Down | The number of DSLAMs with "Down" Eth1 GigE Administration Status. |
| Eth1 GigE Administration Status Other | The number of DSLAMs with "Other" Eth1 GigE Administration Status. |
| Eth1 GigE Operation Status Up | The number of DSLAMs with "Up" Eth1 GigE Operation Status. |
| Eth1 GigE Operation Status Down | The number of DSLAMs with "Down" Eth1 GigE Operation Status. |
| Eth1 GigE Operation Status Other | The number of DSLAMs with "Other" Eth1 GigE Operation Status. |
| Eth1 GigE In Rate | The DSLAM Eth1 GigE in bitrate in Mbps. |
| Eth1 GigE Out Rate | The DSLAM Eth1 GigE out bitrate in Mbps. |
| Eth2 GigE Administration Status Up | The number of DSLAMs with "Up" Eth2 GigE Administration Status. |
| Eth2 GigE Administration Status Down | The number of DSLAMs with "Down" Eth2 GigE Administration Status. |
| Eth2 GigE Administration Status Other | The number of DSLAMs with "Other" Eth2 GigE Administration Status. |
| Eth2 GigE Operation Status Up | The number of DSLAMs with "Up" Eth2 GigE Operation Status. |
| Eth2 GigE Operation Status Down | The number of DSLAMs with "Down" Eth2 GigE Operation Status. |
| Eth2 GigE Operation Status Other | The number of DSLAMs with "Other" Eth2 GigE Operation Status. |
| Eth2 GigE In Rate | The DSLAM Eth2 GigE in bitrate in Mbps. |
| Eth2 GigE Out Rate | The DSLAM Eth2 GigE out bitrate in Mbps. |
| Polling Mask Enabled | The number of polling masked DSLAMs. |
| Polling Mask Disabled | The number of polling unmasked DSLAMs. |
Revision History
DATE VERSION AUTHOR COMMENTS 20/08/2018 1.0.0.1 AIG, Skyline Initial version
Notes
As the data pages are not accessible, to provide an easier way to configure the settings, a custom Visio file can be used.