Managing the Remote Cable MSO Links Solution
Introduction
This chapter describes the three monitoring mechanisms that you can use to monitor the traffic optimization on remote links solution:
Virtual Link Names
Each virtual link represents a single interface on the CMTS device and the virtual link name comprises the CMTS device name and the interface name. The virtual links are named according to the following naming convention:
<Device name>_<Interface name>
- <Device name>—This portion of the name is set when configuring the CMTS in the vlink.cfg configuration file.
- <Interface name>—This portion of the name identifies the specific CMTS interface including the direction and the interface index. This information is how the CMTS describes the interface internally and it is retrieved from the CMTS device by using SNMP.
–
The direction portion of the virtual link name indicates the virtual link direction. Values can be upstream or downstream.
–
The interface index indicates the specific interface on the CMTS of the virtual link.
This is a sample virtual link name for a CMTS device named Device-1:
Device-1_CMTS1/0-upstream 1
If a downstream virtual link contains two channels, then the virtual link names are displayed as:
<Device name>_<Interface name>-L<index of the primary channel>
Monitoring Using the p3vlink Utility
The p3vlink utility provides the ability to show virtual link configurations and metrics related to the virtual links. The command format is:
Table 5-1 and Table 5-2 lists the p3vlink operations and options, respectively.
p3vlink Utility Examples
To show the CMTS device general configuration, CMTS device list, and CMTS device information:
To show the general configuration of a specified CMTS device:
The output of this command includes these four information elements:
- Num of up interfaces—Summarizes the total number of upstream virtual links related to this CMTS device. Unknown indicates that the VLM was not able to communicate with the CMTS device.
- Num of down interfaces—Summarizes the total number of downstream virtual links related to this CMTS device. Unknown indicates that the VLM was not able to communicate with the CMTS device.
- Sync state with Cisco SCE:
–
Done—The Cisco SCE is fully synchronized with CMTS device information.
–
Not-done—The Cisco SCE is not synchronized with all CMTS device data. Use the p3vlink --resync -n < sce which manages the device > command to perform the synchronization operation.
–
Sync-in-process—When VLM detects configuration changes, the change needs to be sent to the Cisco SCE. During the update process, the VLM changes the sync state to Sync-in-process.
For successful updates, the Cisco SCE sync state is set to Done, else the value is set to Not-Done.
–
Done—The Collection Manager is fully synchronized with CMTS device information.
–
Not-done—The CM is not synchronized with all CMTS device data. Use the p3vlink --resync -n < sce which manages the device > command to perform the synchronization operation.
–
N/A—The Cisco SCE to which the CMTS device belongs, is not connected to any Collection Manager.
–
Sync-in-process – When VLM detects configuration changes, the change needs to be sent to the Collection Manager. During the update process, the VLM changes the sync state to Sync-in-process.
For successful updates, Cisco SCE sync state is set to Done, else the value is set to Not-Done.
–
Not started—Query operation for the device was not started since the last Cisco Subscriber Manager boot.
–
Completed—Last query was completed successfully.
–
Failure—Last query failed to complete.
–
Waiting for query—Query operation is in queue waiting for resources.
–
In-query—Device is in the process of a query operation.
–
Waiting for deletion—During the last query, if no giaddr was found, the system queues up the device for deletion. This is applicable only to dynamic devices.
To show all the virtual links for a specific network element (Cisco SCE):
To show the vlink data of a specific link:
Note
If more than one vlink has the same name, this command displays the information for all the vlinks.
To Show the maximum number of upstream and downstream vlinks, the number of existing, and free vlinks in a Cisco SCE device:
To show the upstream and downstream vlink mappings that the virtual link manager learnt from all configured CMTSs:
To show the subscribers using virtual links:
To view the subscribers with partial, no, and 0 vlink mappings for a given device:
To imort the subscribers from a given file to the SNMP BG primary queue:
Monitoring Virtual Links Using the Cisco SCE CLI
The Cisco SCE provides CLI commands to monitor the virtual links in the solution.
Table 5-3 lists the virtual links CLI commands.
virtual-links Command Examples
These examples show the output from the CLI virtual links commands:
Monitoring Virtual Links Using the Reporter
The Cisco SCA BB includes a Reporter tool that allows you to produce reports based on the traffic analysis performed by the Cisco SCE platform. The information is sent from the Cisco SCE platform and is stored in a database. The Reporter can query and retrieve information from the database and present the results in a comprehensive range of reports.
The Reporter includes the Virtual Links Monitoring group of report templates that allow you to view statistics of bandwidth or volume of traffic used by a virtual link. The reports are provided per service usage counter for the total volume used by the virtual link. The volume consumption can be displayed per service for the virtual link. The reports are provided per channel.
Each report can be filtered to focus on a virtual link ID, a virtual link name, a virtual link direction, or a combination of the virtual link identifiers.
The Virtual Links Monitoring group includes these report templates:
- VLink Bandwidth per Service—Shows the distribution of bandwidth among the different service usage counters defined in the system for all subscribers.
- VLink Aggregated Usage Volume per Service—Shows the total volume of traffic (upstream and downstream) for each service usage counter.
- VLink Bandwidth per Package—Shows the distribution of bandwidth among the different packages defined in the system for selected vlinks.
- VLink Hourly Usage Volume per Service—Shows the distribution of volume among the different service usage counters defined in the system, grouped by hour.
- VLink Daily Usage Volume per Service—Shows the distribution of volume among the different service usage counters defined in the system, grouped by day.
- Daily Peak BW for all VLinks—Shows the daily value of the maximum bandwidth (1-hour or 2-hour average) for all virtual links.
- Total Active Subscribers per VLink—Shows the number of active subscribers for a selected vlink.
- VLink Bandwidth per Channel—Shows the distribution of bandwidth among the different channels for selected vlinks.
- Top Subscribers per VLink—Shows a list of the top subscriber volume consumption in a specific hour or day for a selected vlink.
- Average Bandwidth per Subscribers per VLink—Shows the average bandwidth for a specific subscriber for a selected vlink.
- Accumulated Bandwidth Distribution per VLink—Shows the accumulated bandwidth distribution for a selected vlink.
Creating a New Report Instance Using Cisco Insight
For details on creating a new report instance using Cisco Insight, see the Cisco Insight Reporter User Guide.
Feedback