The internal communication of an NE is abnormal and many boards report transiently BD_STATUS or COMMUN_FAIL alarms due to the conflicted subrack IDs.
Symptom
On network C built with the OptiX OSN 6800, many boards on an NE report a transient BD_STATUS or COMMUN_FAIL alarm. A query of the NE configuration shows that the logical board for slot 10 is sometimes displayed as TMX and sometimes displayed as XCS. Actually, the board housed in slot 10 is the TMX board.
Cause Analysis
Communication between the boards on an NE is abnormal when many boards on the NE report a transient BD_STATUS or COMMUN_FAIL alarm. The possible causes of the fault are as follows:
- The boards that report the alarms are faulty.
- The AUX board, which is the communication hub of the NE, is faulty.
- An external factor results in abnormal communication.
Procedure
- Considering that many boards of the NE report a transient BD_STATUS or COMMUN_FAIL alarm, suspect that internal communication of the NE may be abnormal.
- Rule out the possibility that the boards reporting the BD_STATUS or COMMUN_FAIL alarm are faulty since many boards of the NE report the same alarm.
- The logical board in slot 10 changes frequently. Thus, suspect that conflicting subrack IDs exist.
- Check the NE configurations at the site and find that two subracks of the NE use the same ID. Thus, determine that this problem is due to conflicting subrack IDs.
Reference Information
Conclusions and suggestions for this case are as follows:
After changing the settings of the DIP switches of a subrack in the engineering or maintenance phase, perform a power-off reset on the subrack so that the settings of the DIP switches take effect.
MORE BLOG:
No comments:
Post a Comment