The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes several problem scenarios that you may encounter when using the solution. The problem scenarios and solutions are described under these sections:
To troubleshoot the cause of bad service to subscribers, consider these points:
To make sure that the problem is not with the Cisco SCE, perform these procedures:
Step 1 Verify that the Subscriber Manager-Cisco SCE subscriber data is synchronized.
In the Cisco SCE, use the show interface linecard 0 subscriber name < sub MAC > command to verify that the upvlinkId and downVlinkId values are the same as in the p3subs --show -s < sub MAC > Subscriber Manager CLU output and that the subscriber package ID is as expected.
This example shows the output of the Cisco SCE show interface command:
This example shows the output of the Subscriber Manager show command:
Step 2 Verify that the Subscriber Manager-Cisco SCE virtual links data is synchronized.
Compare the output of the Cisco SCE show interface linecard 0 virtual-links different-from-template command with the Subscriber Manager p3vlink --show-vlink-data --vlink-name < UpVlinkId/DownVlinkId Name > command to make sure that the PIR configuration is correct.
NoteThe Cisco SCE PIR value is in kilobits. You can calculate the VLM value by performing a multiplication with the relevant CMTS device factor as defined in the vlink.cfg configuration file. The CMTS device factor value appears in the output of the Subscriber Manager CLUp3vlink --show-device -d <device-name>.
The following example shows the output of the Cisco SCE show interface linecard command:
This example shows the output of the p3vlink --show-vlink-data Subscriber Manager command:
This example shows the output of the p3vlink --show-device Subscriber Manager command:
To enforce the correct policy on a specific subscriber:
a. Monitor all CMTS device interfaces by using the Subscriber Manager p3vlink --show-device -d NAME [ --detail ] command.
b. Verify that in the output of the CLU Sync state with Cisco SCE is Done.
If Sync state with Cisco SCE is Not Done:
– View the connection state between the Subscriber Manager and the Cisco SCE by using the Subscriber Manager CLU p3net --show -n SCE_NAME .
– Synchronize the Cisco SCE with the CMTS device configuration by using the Subscriber Manager CLU p3vlink --resync -n SCE_NAME .
Step 3 Verify that the VLM-CMTS data is synchronized.
Compare the virtual link names from the Subscriber Manager CLU p3subs --show -s < sub MAC > output with the CMTS configuration to verify that the subscriber is assigned to the correct CMTS and CMTS interface.
NoteThe virtual link name structure is <CTMS_NAME>_<INTERFACE_DESCRIPTION> and is obtained from the configuration file and the SNMP ifTable data.
Ensure that the PIR value is the same as the CMTS interface speed (as taken from the SNMP ifTable data) by comparing the virtual link PIR values from the Subscriber Manager CLU p3vlink --show-vlink-data --vlink-name < UpVlinkId/DownVlinkId Name > with the CMTS configuration.
To ensure that the PIR value is the same as the CMTS interface speed:
a. Use p3vlink --show-device -d < DEVICE_NAME > to verify that:
– The monitor period is not 0.
– The last query completed successfully. Check the user log for reasons for failure.
b. Use p3vlink --start-query -d < DEVICE_NAME > to force a start query on a specific CMTS device.
Step 1 Obtain the VLM name for a specific interface by using the p3subs --show -s < sub MAC > command, or build the interface name as <CTMS_NAME>_<INTERFACE_DESCRIPTION>.
Step 2 Retrieve the list of subscribers related to a specific interface and compare it with the CMTS data using the p3vlink --show-subs --vlink-name = < UpVlinkId/DownVlinkId Name > command:
The Cisco Insight can generate per interface consumption reports that can be used to monitor the solution. The VLM updates the reporter with the interface ID to name data and the Cisco SCE sends the raw data with the interface ID (virtual link).
A problem can stem from the VLM update or from the Cisco SCE RDRs.
Two possible solutions include:
Step 1 Verify the connectivity between the Subscriber Manager and the Collection Manager.
View the configured network elements and verify that the Collection Manager exists by using the Subscriber Manager CLU p3net --show-all --detail command.
View the Subscriber Manager-Collection Manager connection properties and state by using the p3net --show -n CM_NAME command, and then verify that the Cisco SCE list property value contains the Cisco SCE to which the CMTS is connected.
To fix the communication problems confirm that the Subscriber Manager configuration file contains the relevant Collection Manager information:
– Check that a Collection Manager Section exists and points to the Cisco SCE section.
– Validate the Collection Manager IP and port.
– Check that the Cisco SCE is related to the Collection Manager.
See the “Information About Communication Failures” section in the “Subscriber Manager Overview” chapter of Cisco Service Control Management Suite Subscriber Manager User Guide .
Step 2 Verify that the VLM and Collection Manager data is synchronized.
Verify that the synchronization state with Collection Manager is set to done using the CLU p3vlink --show-device -d < CMTS_NAME > command. To view a list of configured virtual links, use the Collection Manager CLU update_vlinks.sh --sce =< SCE_IP > --show command.
a. Force the VLM and the Collection Manager to synchronize by using the p3vlink --resync -n < CM_NAME > command.
b. For manual configuration, see Cisco Service Control Management Suite Collection Manager User Guide to add virtual links by using the update_vlinks.sh --sce =< SCE_IP > --file=vlinks.csv command.
This example shows the output of the p3net --show -n command:
This example shows the output of the p3vlink --show-device -d command:
This example shows the output of the update_vlinks.sh script:
If the virtual link assignment is incorrect or false subscriber login operations are not handled by the correct virtual link controller, virtual links can become congested. To resolve this issue, you must confirm that there are no subscribers associated with the virtual link and also verify that the distribution of subscribers to the virtual link is as expected.
To verify that the distribution of subscribers to the virtual link is as expected, see the “Verifying if the Distribution of Subscribers to the Virtual Link is Correct” section .
Step 1 Use the Cisco SCE show interface LineCard 0 subscriber property < upVlinkId|downVlinkId > equals 0 command to ensure that there are no subscribers associated with the default virtual link.
Subscribers in the Cisco SCE can have a virtual link ID set to 0 in several cases:
The following example shows the output of the show interface LineCard 0 subscriber property upVlinkId equals 0 command:
This example shows the output of the p3dhcpsniff --show-policy --policy=upVlinkId --detail command:
From Release 4.2.0, a CLU is added to perform p3vlink utility to check the subscriber's (Cable modem) service flow and vlink association details from the command line. This CLU can be used to check when the subscriber is left with partial vlink mapping and also to cross check the vlink association with actual channel mapping in CMTS.
New CLU will take subscriber id as input and query the CMTS to which the subscriber belongs, by using the giaddrIp property of the subscriber and will report command line about the MAC domain to which the subscriber's service flows are associated, Service flow details for both up/down stream with service flow id, Channel set idto which the service flows are associated, Vlink id of the upstream/downstream with mapping table entry.
The following CLI queries the subscriber vlink details:
>p3vlink --debug-snmp-bg -s <subscriber id>
The following example show the output of p3vlink --debug-snmp-bg -s command:
>p3vlink --debug-snmp-bg -s 010101010101
The messages that are written to the userlog are categorized based on their severity as:
These are the preconditions of the messages:
Table 6-1 lists the error messages that can be written to the userlog.
Table 6-2 lists the warning messages that can be written to the userlog.
Table 6-3 lists the information messages that can be written to the userlog.