Cisco Cisco Prime Cable Provisioning 5.1 Release Notes

Use the Bug Search tool to search for a specific bug or to search for all bugs in a release.

Go to 

At the Log In screen, enter your registered Cisco.com username and password; then, click Log In. The 
Bug Search page opens.

If you do not have a Cisco.com username and password, you can register for them at 

.

To search for a specific bug, enter the bug ID in the Search For field and press Enter.

CNR extensions expect relay agent information in DHCPINFORM messages.

Many PCs behind one modem cause the DPE to drop RDU connection.

Illegal argument exception is thrown in DPE logs for EMIC configurations.

RunRecoveryException is thrown while restoring the database using relative path.

Stack Trace is present in RDU/DPE log after rebooting server.

MTA FQDN auto generate does not require domain for some API calls.

Usage (-help option) is not available for some of the scripts in DPE.

Deletion of env folder from temp directory is required for installation.

Upgrade/Add Components fails if the current directory has no write permission.

With IE browser, it is not possible to view the last CRS Request record in the queue.

Mixed Mode is not supported for PacketCable when IPv6 interface is enabled.

IPv6-PacketCable 2.0 is not disabled in Admin UI when it is disabled in DPE.

HA email notification does not contain details of the issue in setup.

GetRDUDetails API is not working in RDU HA setup.

GetRDUDefaults is showing CRS information even without priv_property_read and priv_crs_read.

DPE tries to connect to RDU in local loop when DNS is misconfigured.

Configuration is generated twice for each device when default CoS is modified.

RDU runs out of memory while executing the search for device, file name or node.

Issue occurs when changing the security domain in Modify File page.

Remove api folder when DPE/CNR-EP components are installed separately.