On OSN 3500 NE with the SCC of version 220.127.116.11P01, an N2PQ1 board plays the role of an N1PQ1 board. When the NE is restarted, the SCC reports the WRG_BD_TYPE alarm for the N2PQ1 slot.
Perform a warm reset on the N2PQ1. At this time, the NE starts successfully.
If the board request to start working as the SSN2PQ1 at the beginning, the NE makes no response (and reports the WRG_BD_TYPE alarm). When the board request to start working as the SSN1PQ1, the NE makes a response, starts the board, and automatically clears the WRG_BD_TYPE alarm.
If the board request to start working as the SSN1PQ1 at the beginning, the NE makes a response and starts the board without any WRG_BD_TYPE alarm.
1. When the NE is restarted, the SSN2PQ1 starts faster than the SCC. The SSN2PQ1 cannot obtain a timely response from the NE when it request to start working as the SSN1PQ1. The NE buffers the request in a queue. The SSN2PQ1 then requests to start working as the SSN2PQ1 and SSN1PQ1alternatively.
2. After starting successfully, the NE handles the queued requests in sequence. When coming to the SSN1PQ1 start request, the NE issues a permission to the board. That is, the NE allows the SSN2PQ1 to start working as the SSN1PQ1. Assume that the SSN2PQ1 requests a working start as the SSN2PQ1 at the time. Therefore, the SSN2PQ1 successfully starts working as the SSN2PQ1. The NE, however, appends the SSN2PQ1 start request to the queue. The NE continues to handle the other queued start requests in sequence. When coming to the SSN2PQ1 start request, the SCC reports the WRG_BD_TYPE alarm.
The NE of R003 does not contain a board type in a board start permit. The NE of R006 contains a board type in a board start permit. In this way, the board can check the board type to ensure proper start.