In a capacity expansion project, an extra subrack is configured in addition to the original OptiX OSN 6800 subrack. When the extra subrack is connected through a network cable, no physical slot of the subrack can be queried on the iManager T2000. Not all physical boards are listed when the cfg-get-phybd is executed. During creation of a physical board that is listed on the iManager T2000, the system displays an error message, indicating that creating the logical board fails due to illegal slot. In addition, several boards on the original subrack reports BD_STATUS and WRG_BD_TYPE alarms.
1. Check the subrack IDs.
The subrack IDs are configured properly.
2. Replace the network cable.
The problem persists.
3. Disconnect the network cable from the extended subrack, and then remove all boards. Insert the SCC back, and then insert all other boards when the SCC works normally.
All alarms are cleared and the problem is solved.
1. The ID of the original subrack conflicts with that of the extra subrack.2. The network cable connecting the subrack is faulty.
Subsequent analysis shows that the problem is caused by the incorrect construction sequence. For the NEs that do not suffer the problem, the relevant AUX DIP switches are configured before the NEs are powered on. For the NE that suffers the problem, the relevant AUX DIP switch is configured after the NE is powered on. The AUX DIP switch must be configured before the new subrack is powered on, so that the correct board information can be collected after power-on. Power-off reset is recommended for new NEs after the relevant AUX DIP switches are modified. To avoid similar problems, comply with the appropriate construction sequence.