Overview
This topic explains how to identify and resolve common issues encountered during NCS 2000 node upgrades in Cisco Optical Site Manager, including rack number conflicts, authentication misconfigurations, out-of-sync status, and incorrect device settings.
NCS 2000 node upgrade issues in Cisco Optical Site Manager are problems with configuration or integration. These issues prevent proper device onboarding, synchronization, or visualization in the Cisco Optical Site Manager UI.
-
These problems are typically caused by rack number conflicts, authentication misconfigurations, or incorrect device parameters.
-
These issues affect how the device is represented, synchronized, or managed in Cisco Optical Site Manager.
-
You can usually resolve these issues by correcting the configuration and re-adding the device.
Common upgrade and onboarding issues and their resolutions
Common issues during NCS 2000 upgrade and onboarding to Cisco Optical Site Manager are:
-
remote TXP rack overlap in the UI,
-
device synchronization status OUT-OF-SYNC, and
-
incorrect device name or device flavor configuration.
The table provides a summary of each issue, its cause, and the resolution.
| Issue |
Cause |
Resolution |
|---|---|---|
| Remote TXP nodes overlap in the UI |
The Rack Number of the remote TXP matches an existing rack number, causing the chassis to appear in an occupied rack. |
Delete the remote TXP device, correct the Rack Number in CTC, and add the device again. |
| Device Sync Status is OUT-OF-SYNC |
Admin Plane credentials are not included in the Authentication Group for the SVO controller. |
Edit the Authentication Group and add the required Admin Plane credentials. |
| Incorrect device name |
The device name is used as a key in the device YANG models and cannot be modified after the device is added. |
Delete the device and add it again with the correct device name. |
| Incorrect device flavor |
The selected device flavor does not match the actual node type, affecting device behavior in Cisco Optical Site Manager. |
Delete the device and add it again with the correct device flavor. |
You must delete and re-add the device after correcting configuration issues to ensure that the changes take effect.