Cisco Cisco ONS 15454 M12 Multiservice Transport Platform (MSTP) Notas de publicación
35
Release Notes for Cisco ONS 15454 Release 7.2.2
78-xxxxx-xx
Resolved Caveats for Release 7.2.x
CSCdu53509
When a TL1 session to a remote node (ENE) is established via a gateway node (GNE) and you have
changed the node name of the ENE via either TL1, CTC or SNMP, then you must wait for about 30
seconds to issue a TL1 command via the GNE. This delay is to permit the updates to propagate to all
nodes in the network. During this transition, neither the old node name nor the new node name can be
used in the TL1 session to access the ENE. This 30 second window may be reduced in a future release.
changed the node name of the ENE via either TL1, CTC or SNMP, then you must wait for about 30
seconds to issue a TL1 command via the GNE. This delay is to permit the updates to propagate to all
nodes in the network. During this transition, neither the old node name nor the new node name can be
used in the TL1 session to access the ENE. This 30 second window may be reduced in a future release.
Resolved Caveats for Release 7.2.x
This section documents caveats resolved in Release 7.2.x
Maintenance and Administration
CSCuk57066
ANS generating a "VOA Target Attenuation Error" on the PT ports of some WSS units in the Source and
Destination nodes of the OCHNC. This error can be generated by having the OPT-PRE units working
with 5dBm target power (16chs design) and the PT VOA not being able to reach the target attenuation
value required for the startup procedure. Setting the target power for the OPT-PREs to 2dBm it is
possible to clear the ANS errors and to have the OCHNC go to IS. This issue is resolved in Release 6.0,
7.04,7.22, 8.0
Destination nodes of the OCHNC. This error can be generated by having the OPT-PRE units working
with 5dBm target power (16chs design) and the PT VOA not being able to reach the target attenuation
value required for the startup procedure. Setting the target power for the OPT-PREs to 2dBm it is
possible to clear the ANS errors and to have the OCHNC go to IS. This issue is resolved in Release 6.0,
7.04,7.22, 8.0
CSCse53413
Creation of Low Order Server Trails (like VC12 or VT1.5) might reset the active TCC. No workaround
available. This issue is expected to be resolved in 7.22, 8.0.
available. This issue is expected to be resolved in 7.22, 8.0.
CSCsf14879
TCC of Node Controller reloads continuously when Multishelf MSTP NE with several DCC/GCC/OSC
is provisioned (approx. more than 10) involving cards plugged in subtended shelves. No work-around is
available. This issue is resolved in 7.22
is provisioned (approx. more than 10) involving cards plugged in subtended shelves. No work-around is
available. This issue is resolved in 7.22
CSCse36337
When a Server Trail is created on a 1+1 Protection Group, the Node's database gets deleted, and the Node
goes for continuous reboot. No work-around is available. This issue will be resolved in Release 7.22, 8.0.
goes for continuous reboot. No work-around is available. This issue will be resolved in Release 7.22, 8.0.
CSCsg43952
In CTC, Shelf view, select Provisioning -> General -> General and configure: - 10/20/2006 as Date - 16:05:00
as Time - "(GMT+01:00) Amsterdam, Berlin, Rome, Stockholm, Paris" as Time Zone - Use Daylight Saving
Time checked The Network Element is configured on the right time. Now change the Time Zone to
"(GMT+00:00) Dublin, Edinburgh, London, Lisbon": the Network Element time changes from 16:05 to 14:05
this t is wrong because in London it's 15:05. This issue is resolved in 7.22
as Time - "(GMT+01:00) Amsterdam, Berlin, Rome, Stockholm, Paris" as Time Zone - Use Daylight Saving
Time checked The Network Element is configured on the right time. Now change the Time Zone to
"(GMT+00:00) Dublin, Edinburgh, London, Lisbon": the Network Element time changes from 16:05 to 14:05
this t is wrong because in London it's 15:05. This issue is resolved in 7.22