Cisco Cisco ONS 15454 SONET Multiservice Provisioning Platform (MSPP) Notas de publicación
3
Release Notes for Cisco ONS 15454 Release 7.0
OL-8935-01
Caveats
CSCuk48503
Under specific conditions the non-enhanced MXPD does not pass the Telcordia GR-253/G.825 Jitter
generation mask test on 10G TX Trunk port. The 2.5 G TX Client jitter generation is always within mask
and does not exhibit this issue. This occurs only when, in SONET mode, there is no FEC, no G.709, and
client interfaces are looped back, with non-synchronous clocking, and the jitter testbox TX connected to
Trunk RX port, while the jitter testbox RX is connected to the Trunk TX port. The jitter testbox TX clock
recovers from RX with an additional 5 ppm offset added. This issue will not be resolved.
generation mask test on 10G TX Trunk port. The 2.5 G TX Client jitter generation is always within mask
and does not exhibit this issue. This occurs only when, in SONET mode, there is no FEC, no G.709, and
client interfaces are looped back, with non-synchronous clocking, and the jitter testbox TX connected to
Trunk RX port, while the jitter testbox RX is connected to the Trunk TX port. The jitter testbox TX clock
recovers from RX with an additional 5 ppm offset added. This issue will not be resolved.
CSCuk44284
An optical connector and optical attenuators inserted into the SFP may force the fiber against the shelf
door when it is closed. Use the following types of optical connectors and optical attenuators when
connecting to the SFP:
door when it is closed. Use the following types of optical connectors and optical attenuators when
connecting to the SFP:
•
Optical connectors: The length of the connector (starting from the ferule tip) plus the fiber boot
must be 50 mm or shorter.
must be 50 mm or shorter.
•
Optical Attenuators: The following attenuator Cisco P/Ns are recommended:
–
39-0228-XX
–
39-0229-XX
–
39-0230-XX
Jitter Performance with XC10G
During testing with the XC10G, jitter generation above 0.10 UI p-p related to temperature gradient
testing has been observed. This effect is not expected to be seen under standard operating conditions.
Changes are being investigated to improve jitter performance in a future release. Tracking numbers
related to this issue include CSCdv50357, CSCdv63567, CSCdv68418, CSCdv68441, CSCdv68389,
CSCdv59621, and CSCdv73402.
testing has been observed. This effect is not expected to be seen under standard operating conditions.
Changes are being investigated to improve jitter performance in a future release. Tracking numbers
related to this issue include CSCdv50357, CSCdv63567, CSCdv68418, CSCdv68441, CSCdv68389,
CSCdv59621, and CSCdv73402.
CSCdz49928
When using KLM type fuses with specific types of fuse and alarm panels, the PWR-REDUN alarm may
not be displayed once the fuse is blown. A KLM fuse does not have a blown fuse indicator built into it.
As a result, the blown fuse detection circuitry on the FAP may continue to provide voltage on its output
despite a blown fuse.
not be displayed once the fuse is blown. A KLM fuse does not have a blown fuse indicator built into it.
As a result, the blown fuse detection circuitry on the FAP may continue to provide voltage on its output
despite a blown fuse.
Maintenance and Administration
Caution
VxWorks is intended for qualified Cisco personnel only. Customer use of VxWorks is not recommended,
nor is it supported by Cisco's Technical Assistance Center. Inappropriate use of VxWorks commands can
have a negative and service affecting impact on your network. Please consult the troubleshooting guide
for your release and platform for appropriate troubleshooting procedures. To exit without logging in,
enter a Control-D (hold down the Control and D keys at the same time) at the Username prompt. To exit
after logging in, type “logout” at the VxWorks shell prompt.
nor is it supported by Cisco's Technical Assistance Center. Inappropriate use of VxWorks commands can
have a negative and service affecting impact on your network. Please consult the troubleshooting guide
for your release and platform for appropriate troubleshooting procedures. To exit without logging in,
enter a Control-D (hold down the Control and D keys at the same time) at the Username prompt. To exit
after logging in, type “logout” at the VxWorks shell prompt.