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

Descargar
Página de 38
 
3
Release Notes for Cisco ONS 15454 SDH Release 4.1.8
OL-7624-01
  Changes to the Release Notes
Changes to the Release Notes
This section documents supplemental changes that have been added to the Release Notes for Cisco ONS 
15454 SDH Release 4.1.8 
since the production of the Cisco ONS 15454 SDH System Software CD for 
Release 4.1.8.
No changes have been added to the release notes for Release 4.1.8.
Caveats
Review the notes listed below before deploying the ONS 15454 SDH. Caveats with DDTS tracking 
numbers are known system limitations that are scheduled to be addressed in a subsequent release. 
Caveats without DDTS tracking numbers are provided to point out procedural or situational 
considerations when deploying the product.
Hardware
DDTS # CSCec33248
Pulling the active XCVXL card might result in a traffic outage lasting for greater than 2 seconds. It is 
possible to see this approximately 1 out of every 7 active XCVXL card pulls. Excessive traffic outage 
from this issue will not occur after a software-induced XCVXL side switch. In this case, you can expect 
a traffic hit of less than 60 ms, and traffic will resume normally.
CWDM and DWDM GBIC Compatibility with G1000-4 Cards and G1K-4 Cards
G1000-4 cards support CWDM and DWDM GBICs. G1K-4 cards with the CLEI code of 
WM5IRWPCAA (manufactured after August 2003) support CWDM and DWDM GBICs. G1K-4 cards 
manufactured prior to August 2003 do not support CWDM or DWDM GBICs.
Note
Operating temperature of the DWDM GBICs is -5 degrees C to 40 degrees C.
DDTS # CSCdw92634 
SDH DS3-i and E3 electrical cards only support a VC4 J1 trace string setting for all VC4s together. You 
cannot set the J1 byte for individual VC4s. This issue is a limitation of hardware.
Note
VC3 J1 strings can be set individually, but the optical cards cannot monitor the VC3 J1 string.
DDTS # CSCdy00622
Very rarely, an Equipment Failure Alarm can occur on an externally timed TCC+ or TCC-I card after a 
reset. If this occurs, BITS will be displayed as good for one TCC, but bad for the other. If the issue occurs 
on the standby TCC, a second reset could clear the problem. If the issue occurs on the active TCC, the 
card must be replaced. This issue is closed, as it does not occur with TCC2, and is otherwise very rare.