Cisco Cisco ONS 15454 M12 Multiservice Transport Platform (MSTP) Notas de publicación
25
Release Notes for Cisco ONS 15454 Release 4.1.8.2
OL-12393-01
Resolved Software Caveats for Release 4.1.8.2
CSCdz26071
The TL1 COPY-RFILE command, used for SW download, database backup, and database restore,
currently does not allow a user-selected port parameter to make connections to the host. The command
expects the default parameter of Port 21 and will only allow that number. This issue is resolved in
Release 5.0
currently does not allow a user-selected port parameter to make connections to the host. The command
expects the default parameter of Port 21 and will only allow that number. This issue is resolved in
Release 5.0
Resolved Software Caveats for Release 4.1.8.2
The following items are resolved in Release 4.1.8.2
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 is resolved now for all releases.
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 is resolved now for all releases.
CSCse60231
Networks containing mixed Releases of 3.x and 6.x nodes are not supported, such a mix might occur
briefly as nodes are upgraded. OSPF-HELLO alarms will be raised on DCCs when upgrading nodes to
Release 6.x or later if the network contains a node running any release prior to Release 4.0.
OSPF-HELLO alarms indicate that there is no management communication along the affected DCC. If
the DCC was used for management communication prior to the upgrade, some nodes might become
isolated. To avoid this issue ensure that all nodes in the network are first upgraded to Release 4.0 or later
before upgrading any node to Release 6.0 or later. This issue is resolved in following releases 6.2.2, 7.02,
7.22., 8.0, 4.182
briefly as nodes are upgraded. OSPF-HELLO alarms will be raised on DCCs when upgrading nodes to
Release 6.x or later if the network contains a node running any release prior to Release 4.0.
OSPF-HELLO alarms indicate that there is no management communication along the affected DCC. If
the DCC was used for management communication prior to the upgrade, some nodes might become
isolated. To avoid this issue ensure that all nodes in the network are first upgraded to Release 4.0 or later
before upgrading any node to Release 6.0 or later. This issue is resolved in following releases 6.2.2, 7.02,
7.22., 8.0, 4.182
CSCsd47710
LAN-connected NEs become unreachable for about 15 minutes every 99 days if it has been running
without a shelf controller reset for 99 days. The Ethernet port will fail without any alarms or warnings
for 15 minutes. If the NE is LAN-connected during this failure, it might be unreachable by management
hosts (CTC and Tl1). This occurs for all models of shelf controller, on the following platforms:
ONS 15454, ONS 15327, ONS 15600, ONS 15310-CL, and ONS 15310-MA. However the management
communication over the DCC will not be affected. Thus, if a node is managed over the DCC, it will not
experience problems. On the other hand, if the NE is a GNE, communication to ENEs behind the GNE
will be affected. This is caused because the NE has an internal clock that rolls over to zero every 99 days
(approximately) the last 15 minutes prior to rollover the Ethernet interface incorrectly calculates the age
of ARP entries and assumes the ARP entries have expire regardless of the true age and stops transmitting
IP packets This issue is resolved in Releases 4.182 5.08 6.22 7.02 8.0.
without a shelf controller reset for 99 days. The Ethernet port will fail without any alarms or warnings
for 15 minutes. If the NE is LAN-connected during this failure, it might be unreachable by management
hosts (CTC and Tl1). This occurs for all models of shelf controller, on the following platforms:
ONS 15454, ONS 15327, ONS 15600, ONS 15310-CL, and ONS 15310-MA. However the management
communication over the DCC will not be affected. Thus, if a node is managed over the DCC, it will not
experience problems. On the other hand, if the NE is a GNE, communication to ENEs behind the GNE
will be affected. This is caused because the NE has an internal clock that rolls over to zero every 99 days
(approximately) the last 15 minutes prior to rollover the Ethernet interface incorrectly calculates the age
of ARP entries and assumes the ARP entries have expire regardless of the true age and stops transmitting
IP packets This issue is resolved in Releases 4.182 5.08 6.22 7.02 8.0.