Cisco Cisco ONS 15454 SONET Multiservice Provisioning Platform (MSPP) Notas de publicación

Descargar
Página de 64
24
Release Notes for Cisco ONS 15454 Release 4.0.1
OL-4470-01
Resolved Software Caveats for Release 4.0.1
DDTS # CSCdy24967 and CSCdy21173
A G1000-4 card cannot auto-negotiate with a Catalyst 6500, CatOS Version 7.1.2, using the 
supervisor-1A module (8-port gig-e module). To avoid this issue, use previous version of CatOS, or use 
an IOS native image, or do not use flow control. This issue is resolved in Release 4.0.
Maintenance and Administration
DDTS # CSCdy52361
While provisioning an STS-x UCP circuit, the STS pulldown menu allows more STSs than are defined 
in CTC's circuit provisioning specification, or in Telcordia GR253. Do not use these extra STSs. If you 
do try to use one of these extra, invalid STSs, the node will reject it with an appropriate exception. This 
issue is resolved in Release 4.0.
DDTS # CSCdy65599
DS1 VT alarms report as occurring only on port 1 regardless of which port they actually occurred on. 
After testing, use CTC or TL1 to change the state from OOS-MT. This issue is resolved in Release 4.0.
DDTS # CSCdz05847 
After launching CTC from an ONS 15xxx running Release 3.3 or 3.4, you cannot launch CTC (on that 
computer) from an ONS 15454 running Release 3.1-3.2.x. Further, no error message is displayed 
indicating the issue. To recover from this situation, one of the following recovery procedures may be 
necessary. 
Delete the CTC cache (using the button in the browser applet window) before launching from the 
Release 3.1 or 3.2.x node. 
Continue to launch from the Release 3.3 or 3.4 node but access the Release 3.1 or 3.2.x node (if 
necessary) using a login group (defined in the Edit:Preferences dialog). 
This issue is resolved in Release 4.0.
Performance Monitoring Using Cisco Transport Manager
In Release 3.4, Cisco Transport Manager users that performed PM retrievals might have encountered any 
or all of the following issues:
G1000 statistics appearing unpredictably in the wrong fields
Missing PM data
Correct PMs falsely marked as invalid
Incorrect PMs not marked as invalid
These issues were most likely to occur with SONET path data.  SDH path data was unaffected. All of 
these issues have been resolved in Release 3.4.1 and Release 4.0.