Cisco Prime Cable Provisioning 5.3 Release Notes
Important Points to Know Before You Begin
Enhanced RDU Batch Processing Using Timeout Value
Dedicated Queue for Lease Query Batches
Prime Cable Provisioning 5.3 Bugs
Obtaining Documentation and Submitting a Service Request
Cisco Prime Cable Provisioning, referred to as Prime Cable Provisioning throughout this document, automates the tasks of provisioning and managing customer premises equipment (CPE) in a broadband service-provider network. The application provides a simple and easy way to deploy high-speed data, voice technology, and home networking devices.
Prime Cable Provisioning can be scaled to suit networks of virtually any size, even those deploying millions of devices. It also offers high availability, made possible by its distributed architecture with centralized management.
Prime Cable Provisioning incorporates support for many technologies to provide provisioning services for your network. These technologies include:
For detailed information about Prime Cable Provisioning features, see the Cisco Prime Cable Provisioning User Guide 5.3.
This release Cisco Prime Cable Provisioning 5.3, supports the following new features:
From 5.3 release, PCP additionally supports DPoE 2.0. This intensifies DPoE 1.0 specifications to provide requirements for additional service capabilities and corresponding provisioning and network management capabilities. This simplifies the provisioning of complex network-wide services.
PCP 5.3 introduces batch processing optimizations and allows the RDU to operate efficiently during specific negative scenarios using the below enhancements.
From 5.3 release, the timeout value configured by the API client is sent to the RDU for enhanced processing of the batches that stays on the batch processing queue for longer time period. The RDU validates the timeout value of read-only batches and executes only the batches that are not timed-out.
PCP 5.3 release introduces a dedicated batch processing queue to handle batches with Lease Query request. This feature allows the RDU to efficiently process all other client batches without disruption. The RDU is no more blocked from handling other batch requests during network glitches or when there is a communication issue between the RDU and DHCP servers.
Earlier, the DPE was registering with RDU in non-concurrent mode eventually suspending all the client batches from being executed. In PCP 5.3 release, the optimization of the DPE to RDU registration process, minimizes the event of non-concurrency. For instance, during a network outage, or glitch, or any other negative scenario, the DPEs would reconnect with the RDU seamlessly without entering into non-concurrent mode. This allows the RDU to continue processing all incoming batches without entering into non-concurrent mode.
For more information on a specific bug or to search all bugs in a particular Prime Cable Provisioning release, see Using the Bug Toolkit.
Table 1 Resolved bug list in Prime Cable Provisioning 5.3.
Table 2 Open Bug List in Prime Cable Provisioning 5.3.
This section explains how to use the Bug Toolkit to search for a specific bug or to search for all bugs in a release.
Step 1 Go to Cisco Software Bug Toolkit.
Step 2 At the Log In screen, enter your registered Cisco.com user name and password; then, click Log In. The Bug Toolkit page opens.
Note If you do not have a Cisco.com user name and password, you can register for them at http://tools.cisco.com/RPF/ register/register.do.
Step 3 To search for a specific bug, click the Search Bugs tab, enter the bug ID in the Search for Bug ID field, and click Go.
Step 4 To search for bugs in the current release, click the Search Bugs tab and specify the following criteria:
Note Do not enter Cisco Prime Cable Provisioning. Cisco Prime Cable Provisioning is the new product name for the former Cisco Broadband Access Center. At this time, the Bug Toolkit does not accept Cisco Prime Cable Provisioning as the product name.
– Severity—Choose the severity level.
– Status—Choose Terminated, Open, or Fixed.
Step 5 Click Search. The Bug Toolkit displays the list of bugs based on the specified search criteria.
Note For example, if a bug applies to both Cisco Prime Cable Provisioning 5.1 and Cisco Prime Cable Provisioning 5.2, the headline and Release-note enclosure contain the earlier Cisco PCP product terminology.
Step 6 To export the results to a spreadsheet:
1. In the Search Bugs tab, click Export All to Spreadsheet.
2. Specify the filename and location at which to save the spreadsheet.
3. Click Save. All bugs retrieved by the search are exported.
If you cannot export the spreadsheet, log into the Technical Support website at http://www.cisco.com/cisco/web/support/index.html or contact the Cisco Technical Assistance Center (TAC).
Note We sometimes update the printed and electronic documentation after original publication. Therefore, you should also review the documentation on Cisco.com for any updates.
See the Cisco Prime Cable Provisioning Documentation Overview for the list of Prime Cable Provisioning guides.
See the Cisco Prime Network Registrar 8.x Documentation Overview for the list of Cisco Prime Network Registrar guides.
See the Prime Cable Provisioning Compatibility Matrix for the compatibility of the current release with the previous releases.
See the Prime Cable Provisioning and Prime Network Registrar Compatibility Matrix for the compatibility of the current release with Prime Network Registrar.
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.