user manual
6
Release Notes for Cisco ONS 15600 Release 8.0
OL-10906-01
Caveats
Interoperability
CSCdx61916 and CSCeg20536
If, using CTC, you attempt to create a protected VT1.5 circuit that originates on one ONS 15454 that is
connected to the ONS 15600 via path protection to another ONS 15454 that is connected to the ONS
15600 via 1+1 or BLSR, the circuit creation request will be denied because of mixed protection domains.
CTC is currently incapable of routing VT circuits across the ONS 15600 when mixed protection schemes
are involved. VT traffic can be routed across the ONS 15600 when mixed protection schemes are
involved by performing the following:
Step 1 On the ONS 15600, create an STS level cross connect with the requisite path selectors.
Step 2 Use CTC to create a VT circuit from the source node to the trunk ports that interface to the 15600.
Step 3 Use CTC to create a VT circuit between the destination node and the trunk ports that interface with the
15600.
Note While this workaround provides the ability to route VT traffic across the ONS 15600 when mixed
protection domains exist, the traffic must be managed as three separate circuits instead of one single
end-to-end circuit.
This issue will be resolved in a future release.
CSCdy68110
When you attempt to configure VT circuits on a test configuration consisting of two ONS 15454 nodes
and one ONS 15600 node, when both ONS 15454s are connected to the ONS 15600 node using a dual
path protection connection configuration, and when the ONS 15600 node serves as an intermediate node
between the two ONS 15454 nodes, you may be unable to create a VT circuit from one ONS 15454 to
the ONS 15600 and then to the other ONS 15454. VT Tunnels are created, but the VT circuit is not
created. A mixed protection domain error message is raised when this occurs. To avoid this issue, create
the VT tunnels manually, so that the two tunnels do not create a topology where the working and protect
tunnels share the same I/O card. After the tunnels have been created, the VT circuit can be successfully
added. This issue will be resolved in future release.
CSCdx94969
Physical PM parameters can not be retrieved through the SNMP interface. MIBs released with the ONS
15600 do not have entries for the following physical PM parameters.
• LBC
• OPR
• OPT
The standard SONET Generic MIB does not have entries for these. To work around this issue, use CTC
to retrieve the values. SNMP support for these parameters may be considered for a future release.