Release Notes

17
Release Notes for Cisco ONS 15454 SDH Release 4.1.3
OL-4984-01
Caveats
• Enable OSPF on the LAN
• Enable Firewall
• Craft Access Only
When any of these features are enabled, the proxy ARP service on the node is also disabled. The ONS
15454 SDH proxy ARP service assumes that all nodes are participating in the service.
This situation can also occur immediately after the aforementioned features are enabled. Other hosts on
the Ethernet segment (for example, the subnet router) may retain incorrect ARP settings for the ONS
15454 SDHs.
To avoid this issue, all nodes on the same Ethernet segment must have the same values for Enable OSPF
on the LAN, Enable Firewall, and Craft Access Only. If any of these values have changed recently, it
may be necessary to allow connected hosts (such as the subnet router) to expire their ARP entries.
You can avoid waiting for the ARP entries to expire on their own by removing the SDCC links from the
affected ONS 15454 SDH nodes. This will disconnect them for the purposes of the proxy ARP service
and the nodes should become directly accessible over the Ethernet. Network settings on the nodes can
then be provisioned as desired, after which the SDCC can be restored.
This issue will not be resolved.
DDTS # CSCdy11012
When the topology host is connected to multiple OSPF areas, but CTC is launched on a node that is
connected to fewer areas, the topology host appears in CTC, and all nodes appear in the network view,
but some nodes remain disconnected. This can occur when the CTC host does not have routing
information to connect to the disconnected nodes. (This can happen, for example, if automatic host
detection was used to connect the CTC workstation to the initial node.)
CTC will be able to contact the topology host to learn about all the nodes in all the OSPF areas, but will
be unable to contact any nodes that are not in the OSPF areas used by the launch node. Therefore, some
nodes will remain disconnected in the CTC network view.
To work around this issue, if no firewall enabled, then the network configuration of the CTC host can be
changed to allow CTC to see all nodes in the network. The launch node must be on its own subnet to
prevent network partitioning, and craft access must not be enabled. The CTC host must be provisioned
with an address on the same subnet as the initial node (but this address must not conflict with any other
node in the network), and with the default gateway of the initial node. CTC will now be able to contact
all nodes in the network.
If a firewall is enabled on any node in the network, then CTC will be unable to contact nodes outside of
the initial OSPF areas. This issue will not be resolved.
DDTS # CSCdy57891
An LOP-P alarm can be inadvertently cleared by an LOS that is raised and cleared. On STM-N cards,
when an LOP condition and an LOS condition are both present on the input, an LOS will be raised.
However, upon clearing the LOS with the LOP still present, the LOP alarm is not raised. An AIS-P
condition will be visible. This issue will be resolved in a future release.