Table of Contents
Cisco Prime Cable Provisioning 5.1.1 Release Notes
Contents
Introduction
Prime Cable Provisioning 5.1.1 Enhancements
MIB Management Enhancements
MIB Migration
Migrating User-Defined MIBs
Prime Cable Provisioning 5.1.1 Bugs
Resolved Bugs
Open Bugs
Using the Bug Search Tool
Related Documentation
Accessibility Features in Prime Cable Provisioning 5.1.1
Obtaining Documentation and Submitting a Service Request
Contents
These release notes contain the following sections:
Introduction
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:
-
DOCSIS high-speed data
-
DPoE devices
-
PacketCable voice service, both Secure and Basic workflows
-
Non-secure CableHome
-
OpenCable Set-top box
For detailed information about Prime Cable Provisioning features, see the
Cisco Prime Cable Provisioning 5.1 User Guide
.
Prime Cable Provisioning 5.1.1 Enhancements
Prime Cable Provisioning 5.1.1 consists of the following enhancements:
MIB Management Enhancements
Following are the list of updates in Prime Cable Provisioning 5.1.1 for the MIB management:
1.
MIB enhancements provide more management options for the MIB files used by the RDU server and the RDU server will load the MIB files available in the RDU database. In earlier releases, the MIB files were loaded from the file system (BPR_HOME/rdu/mibs directory).
2. In the Administrative Web UI, under Configuration > Defaults > System Defaults menu option, for the MIB List field, a new button (Select MIB Files) is added to configure the MIB files from the displayed list that are available in the database instead of entering the file names manually in text box.
3. In the Administrative Web UI, under Configuration > Files page, for MIB file type, a new quick view button is added to view the MIB file details (File Name, Module Name, Parent Modules, Referenced-by Modules).
4. A new option -mib is added in runCfgUtil tool to validate and list the dependencies of MIBs. By default it will validate all the files available in BPR_HOME/rdu/mibs directory. If a filename/directory name is provided as argument, then it will validate and list the dependencies for that file/files available in that directory.
5. The validations that are added in the API for the MIB management are explained in the following table:
Table 1 MIB Management API Validations
|
|
|
|
|
AddFile
|
Adding an invalid MIB file, <arris_cm.mib>.
|
Failed to add MIB file <arris_cm.mib>. Not a valid MIB file: <arris_cm.mib>.
|
Adding a MIB file <arris_cm.mib> without adding the parent MIB <ARRIS-MIB>.
|
Failed to add MIB file <arris_cm.mib>. Cannot find the dependent MIB file <ARRIS-MIB> in database.
|
Adding a new MIB file with a name that already exists in the database, <SNMPv2-SMI>.
|
Failed to add MIB file <SNMPv2-SMI>. File already exist in the database.
|
Adding a MIB file which is already available in database <URI-TC-MIB>. Adding the same MIB file with a different name <Renamed_URI-TC-MIB>.
|
Failed to add MIB file <Renamed_URI-TC-MIB.MIB> module <URI-TC-MIB> already exist in database with file name <uri-tc-mib>.
|
|
DeleteFile
|
Delete a MIB file <ARRIS-MIB> which is a parent for some other MIBs.
|
Failed to delete MIB file <arris-mib>. MIB file(s) <arris_cm.mib, arris_mta_pp.mib> are dependent on MIB file <arris-mib>.
|
Delete a MIB file which is loaded. (configured in System Defaults MIB LIST).
|
Failed to delete MIB file <arris-mib>. The MIB file is currently in use. Requires System Default configuration to be updated under administrator's guidance.
|
|
ReplaceFile
|
Replace a MIB file <ARRIS-MIB> with invalid content (raw text file).
|
Replace operation failed for MIB file <arris-mib>. Not a valid MIB file: <ARRIS-MIB>.
|
Replace a MIB file <ARRIS-MIB> with another valid MIB file <arris_cm.mib>.
|
Replace operation failed for MIB file <arris-mib.MIB>. MIB module <ARRIS-CM-DEVICE-MIB> conflicts with existing MIB module <ARRIS-MIB>.
|
Replace a MIB file <arris_mta_pp.mib> without adding the new parent MIB <ARRIS-ROUTER-DEVICE-MIB>.
|
Unable to replace the MIB <arris_mta_pp.mib>. Cannot find the dependent MIB module <ARRIS-ROUTER-DEVICE-MIB> in database.
|
Replace a MIB file <ARRIS-MIB> by removing few OIDs which are being used by its children.
|
Replace operation failed for MIB file <arris-mib.MIB>. MIB file <arris-mib.MIB> is not compatible with child MIB(s).
|
Note The runCfgUtil script will continue to use the MIBs from the file system (BPR_HOME/rdu/mibs) and not from the RDU Database.
MIB Migration
In the Prime Cable Provisioning 5.1.1 migration, all the custom MIB files will be migrated to the database along with the default MIB files. If the user has configured the MIB file names in rdu.properties, the MIB files will be migrated to the database during the migration. If not, the migration script will get the MIB file names from the System Default configuration and migrate those files to the database.
Migrating User-Defined MIBs
The Prime Cable Provisioning database migration procedure requires that you migrate the components in the sequence recommended in below-mentioned sections.
Note For steps 1-4, see Cisco Prime Cable Provisioning 5.1 Quick Start Guide.
Step 1
Backup the RDU database.
Step 2 Recover the backed up RDU database.
Step 3 Verify the database integrity.
Step 4 Backup the property files.
Step 5 Migrate the RDU database along with the customer specific MIB files. Follow the steps provided in Cisco Prime Cable Provisioning 5.1 Quick Start Guide along with -mibdir option explained below:
– If you have added any custom MIB files in your current installation(4.2.x, 5.x), you will need to first back them up from $BPR_HOME/rdu/mibs/ and then copy them manually to the Prime Cable Provisioning 5.1.1 server.
Note The backed up MIB files should be copied to a location in Prime Cable Provisioning 5.1.1 server other than default $BPR_HOME/rdu/mibs, to avoid overwriting default 5.1.1 MIB files.
– Run the migrateDb.sh tool on the backed up database and backed up custom MIB directory if present. The migrateDb.sh script resides in the $BPR_HOME/migration directory. The migrateDb.sh script supports a new MIB migrating option as shown below:
-mibdir An optional parameter with custom MIB directory path. -mibdir option should be followed with a directory path which exists in file system and contains custom MIB files to be loaded.
For example:
# $BPR_HOME/migration/migrateDb.sh -dbdir /var/backup/rdu-backup-20120829-031028 -mibdir /tmp/mibs -dbdir Specifies the location of the database backup that is to be migrated; in this case, /var/backup. -mibdir Specifies the location of the custom mibs backup that is to be migrated; in this case, /tmp/mibs.
Note The MIB migration happens along with the database migration and it cannot be performed separately.
Prime Cable Provisioning 5.1.1 Bugs
For more information on a specific bug or to search all bugs in a particular Prime Cable Provisioning release, see Using the Bug Search Tool.
This section contains:
Resolved Bugs
Table 2
lists bugs that are resolved in Prime Cable Provisioning 5.1.1.
Table 2 Resolved Bugs in Prime Cable Provisioning 5.1.1
|
|
|
CSCui93957
|
runCfgUtil requires root permissions.
|
CSCun93785
|
Property to ignore generating instructions for DSS_ID.
|
CSCun75161
|
Adaptive way to generate DHCP instructions based on the PG capability.
|
CSCun93802
|
IP Preference Decision Matrix Changes when Device sending Null.
|
CSCua80377
|
Permission issue with shell scripts in BAC 5.0.
|
Open Bugs
Table 3
lists the open bugs in Prime Cable Provisioning 5.1.1. To view more details and possible workaround information for a particular bug, see Using the Bug Search Tool.
Table 3 Open Bugs in Prime Cable Provisioning 5.1.1
|
|
|
CSCuo78157
|
Device Config Gen Fails - IPv6 BASIC.1
|
CSCub63596
|
WS-I Compliance checking is needed.
|
CSCub67891
|
Access denied exception is not thrown when using getAllMatchingFiles.
|
CSCue80652
|
Keytool error is displayed when double quote is used for certificate value.
|
CSCue66152
|
RDU shows high CPU utilization from SSL client when trying to reconnect.
|
CSCue88789
|
NPE stack trace is seen in RDU log when certificate expires or when the keystore value is empty.
|
CSCuc32208
|
Fine-grain privilege level check is not done for RDU Events.
|
CSCtz25409
|
The generated template or Groovy file needs manual editing to make it work.
|
CSCud81568
|
Invalid Property error is displayed when RDU is misconfigured.
|
CSCub87431
|
User with child domain access is able to create user with RootDomain.
|
CSCue70770
|
PWS does not connect to RDUs added in both secure and nonsecure mode.
|
CSCud40680
|
Async Support of get operation is required for pollOperation.
|
CSCth16251
|
CNR extensions expect relay agent information in DHCPINFORM messages.
|
CSCti60751
|
Many PCs behind one modem cause the DPE to drop RDU connection.
|
CSCtj25387
|
Illegal argument exception is thrown in DPE logs for EMIC configurations.
|
CSCtj30159
|
RunRecoveryException is thrown while restoring the database using relative path.
|
CSCtl44226
|
Stack Trace is present in RDU/DPE log after rebooting server.
|
CSCtq15061
|
MTA FQDN auto generate does not require domain for some API calls.
|
CSCtq90931
|
Usage (-help option) is not available for some of the scripts in DPE.
|
CSCtr85371
|
Deletion of env folder from temp directory is required for installation.
|
CSCtr93324
|
Upgrade/Add Components fails if the current directory has no write permission.
|
CSCui73397
|
With IE browser, it is not possible to view the last CRS Request record in the queue.
|
CSCui93423
|
Mixed Mode is not supported for PacketCable when IPv6 interface is enabled.
|
CSCuh16164
|
IPv6-PacketCable 2.0 is not disabled in Admin UI when it is disabled in DPE.
|
CSCuh19526
|
HA email notification does not contain details of the issue in setup.
|
CSCuj14349
|
GetRDUDetails API is not working in RDU HA setup.
|
CSCui71019
|
GetRDUDefaults is showing CRS information even without priv_property_read and priv_crs_read.
|
CSCuj09659
|
DPE tries to connect to RDU in local loop when DNS is misconfigured.
|
CSCue27542
|
Configuration is generated twice for each device when default CoS is modified.
|
CSCuj04407
|
RDU runs out of memory while executing the search for device, file name or node.
|
CSCuj36832
|
Issue occurs when changing the security domain in Modify File page.
|
CSCuj43822
|
Remove api folder when DPE/CNR-EP components are installed separately.
|
Using the Bug Search Tool
Use the Bug Search tool to search for a specific bug or to search for all bugs in a release.
Step 1 Go to
http://tools.cisco.com/bugsearch
.
Step 2 At the Log In screen, enter your registered Cisco.com username and password; then, click
Log In
. The Bug Search page opens.
Note If you do not have a Cisco.com username and password, you can register for them at http://tools.cisco.com/RPF/register/register.do.
Step 3 To search for a specific bug, enter the bug ID in the Search For field and press
Enter
.
Step 4 To search for bugs in the current release:
a. In the Search For field, enter
Prime Cable Provisioning 5.1
, and press
Enter
(Leave the other fields empty).
b. When the search results are displayed, use the filter tools to find the types of bugs you are looking for. You can search for bugs by modified date, status, severity, and so forth.
Tip To export the results to a spreadsheet, click Export Results to Excel.
Accessibility Features in Prime Cable Provisioning 5.1.1
For a list of accessibility features in Prime Cable Provisioning, see the
Voluntary Product Accessibility Template (VPAT)
on the Cisco website, or contact
accessibility@cisco.com
.
All product documents are accessible except for images, graphics, and some charts. If you would like to receive the product documentation in audio format, braille, or large print, contact
accessibility@cisco.com
.
Obtaining Documentation and Submitting a Service Request
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 an RSS feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service. Cisco currently supports RSS Version 2.0.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL:
www.cisco.com/go/trademarks
. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
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.
© 2014 Cisco Systems, Inc. All rights reserved.
Feedback