Cisco Cisco Prime Central 1.3 Release Notes

Page of 8
5
Cisco Prime Central 1.3 Release Notes
OL-28575-02
  Prime Central 1.3 Bugs
Open Bugs
 lists open bugs in Prime Central 1.3. To view more details and possible workaround information 
for a particular bug, see 
.
Table 3
Open Bugs in Prime Central 1.3 
Bug ID
Description
CSCuf13450
When running in an Internet Explorer browser, Prime Central prompts for your username and password after 
you generate a report in the Alarm Report portlet.
To reproduce the problem:
1.
With Prime Central and Fault Management 1.3 already installed, create a new user in Prime Central that 
has access to both Prime Network and Fault Management.
2.
Log in to Prime Central as the new user.
3.
Select Assure > Prime Central Fault Management > Alarm Report.
4.
Generate a report, such as the Ack_Events_Details report.
5.
Click Home to return to the Prime Central home page.
You are prompted to enter your username and password.
Click Cancel to close the Windows Security dialog box. You do not need to enter your username and 
password here.
CSCum40730
After stopping and restarting an external Oracle database, you are able to log in to the Prime Central portal 
but portal content does not load.
To reproduce the problem:
1.
Install Prime Central and the integration layer along with an external Oracle database.
2.
Reboot the external Oracle database server.
3.
Stop and then restart the Oracle service.
4.
Start the listener and database without starting the Prime Central portal or integration layer.
5.
Open the portal login page and enter a valid username and password.
CSCum44785
The Prime Central portal hangs while vCenter and Unified Computing System (UCS) devices are being 
synchronized.
This problem was observed in a setup where Prime Network is integrated with Prime Central, managing 100 
UCS devices and two vCenter devices with 500 VMs configured. After initiating synchronization from Prime 
Central’s Common Inventory portlet, the portal hangs and is not accessible for 2 hours.
CSCum72551
Fault Management was observed to go down occasionally in a setup where Prime Central, the Prime Central 
integration layer, Fault Management, and an embedded Oracle database are installed on the same server 
managing 470 UCS devices.