When we needed to change the NE subrack(chassis), because it had some bent pins and the problem we encountered with the NE ID when using used (not new) NE subrack
OSN1800V.
Description
As we come to change the NE (OSN1800V), we followed serval steps.
- Initially we prepared for change by moving the passthrough traffic through other paths, so we minimize the cut impact, and then we installed an NE in the same rack and made the fiber & electrical connections ready for swap moment.
-The plan was to install An NE chassis and in the swap moment, we only need to move the UXCMS from NE1 to NE(2) and the whole configuration will move with the UXMS.
- Unexpectedly, in the moving time and once powered on the new chassis and move the UXCMS, the new NE appeared in the NCE (NE ECC Link Management) as the NE ID of the Chassis (the chassis was used before) not the NE ID in the UXCMS.
-The appeared NE ID was already used in the network and so it cant be repeated, and the NE couldn’t be created in the NCE.
The Solution
So we had to change the NE-ID as fast as possible.
Howeve,the NE is not created on the NCE, so we used Navigator to change the NE id as follow:-
1- Connect and Login with szhw the super admin user
2- Check the current NE-ID (:cm-get-neid;)
3- To set the NE-ID (:cm-set-neid:XXXX;)
The NE-ID in this command must be in the 8 digits Hexadecimal and you can get it using the navigator calculator, just enter the extended ID and the ID in decimal then get them in hexa here for example extended =9 and ID=501.
- To verify (:cfg-verify;).
After changing the NE-ID to the planned one, The NE appeared on the NCE normally.
-Knowledge
- The NE ID is used by ECC protocol as the unique identifier of an NE. Hence, you need to assign a unique NE ID to each NE when planning a network. If an NE ID conflicts with another NE ID, it causes an ECC route conflict and the NCE cannot manage NEs.
- You can use the NCE or Navigator to change NE IDs.
- When the NE uses the master / slave configuration, only the master NE uses the ID and the IP.
