Cisco NCS 2000 series Troubleshoot Manual

If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/c/en/us/support/index.html
for more information or call Cisco TAC (1 800 553-2447).
OCHNC-INC
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: OCHNC-CONN
The Optical Channel (OCH) Incomplete Cross-Connection condition is raised when an OCH cross connection
on a two-way circuit is deleted. For example, if you create an OCH circuit on a linear DWDM structure with
Nodes A, B and C—originating at Node A, traversing through Node B, and terminating at Node C—then
mistakenly delete a cross-connect (such as by TL1 command DLT-WLEN) on Nodes B or C, this condition
is raised on the source node (A). The condition is corrected by regenerating the cross-connect. The alarm also
follows these guidelines:
• Two-way circuit with Nodes A, B, and C (as described in the preceding example): Deleting a
cross-connection on Nodes B or C will raise OCHNC-INC on the Node A cross connection.
• Two-way circuit with Nodes A, B, and C: Deleting a cross connection on Node A will raise an
OCHNC-INC alarm on the Node C cross connection.
• One-way circuit with Nodes A, B and C: Deleting a cross connection on Nodes B or C will raise an
OCHNC-INC alarm on Node A cross connection.
• One-way circuit with Nodes A, B, and C: Deleting a cross connection on Node A will not raise an
OCHNC-INC alarm.
If you delete one of the cross-connects, you might not be able to recreate this same circuit with CTC because
the wavelength is already being used on the other component nodes for add, drop, or express.
Note
The OCHNC-INC alarm can also be raised if you restore one node’s database that is inconsistent with other
node databases, following the guidelines previously listed. (That is, an inconsistent database that does not
contain up-to-date circuit cross-connection information will cause the same problem as if you had deleted the
cross-connect.)
It is important to create a backup version of the database for each node of a topology during a known-stable
situation. You should give the saved files names that indicate their version and date or any other information
needed to verify their consistency. For procedures to back up or restore database files, refer to the Maintain
the Node document.
Caution
Cisco NCS 2000 series Troubleshooting Guide, Release 11.0
312
Alarm Troubleshooting
OCHNC-INC

Cisco NCS 2000 series Specifications

General

Brand	Cisco
Model	NCS 2000 series
Category	Network Hardware
Language	English