Cisco Cisco Prime Central 1.0 Release Notes

For more information on a specific bug or to search all bugs in Prime Central 1.0, see 

.

This section contains the following information:

 lists open bugs in Prime Central 1.0. To view more details and possible workaround information 

for a particular bug, see 

.

Prime Optical GateWay/CORBA stops sending events, thereby impacting the Prime Central Common 
Inventory portlet, which relies on Prime Optical notifications for device inventory synchronization. If a 
device is added to Prime Optical while Prime Optical GateWay/CORBA stops sending events, the 
Prime Central device inventory might be out of sync. Common Inventory must wait for the next daily 
synchronization cycle to update its inventory.

This problem occurs when you use the Prime Optical GateWay/CORBA northbound interface to connect to 
a CORBA client or connect to Prime Central (in suite mode).

In Firefox 3.6, some Prime Central windows, menus, and dialog boxes (such as the About dialog box and 
the main menu bar) are partially obscured by the Alarm Browser portlet. This problem is related to a known 
Java applet and Firefox 3.6 issue as described in 

. To avoid this problem, minimize the 

Alarm Browser portlet before you open a new dialog box on the same page.

You cannot cross-launch Prime Optical from the Prime Central portal or from Prime Network Vision. The 
browser displays an “Unable to connect” error. This problem occurs when you cross-launch into 
Prime Optical, and Prime Optical is installed on a Solaris workstation.

Prime Central logs capture granular and verbose data unnecessarily, which obscures debugging information. 
This problem occurs in a Prime Central log file.