The eNodeB fails to be activated, and an alarm is reported, indicating that the S1 interface is abnormal.
In this case, erform the following operations:
1.On the MML page, run the LST ENODEBFUNCTION command to check whether ENodeBID conflicts with other sites.
2.On the MML page, run the LST CPBEARER command to check the SCTP link associated with the bearer and run the DSP SCTPLNK command to check whether the link is normal.
3.If the preceding conditions are met, run the LST CNOPERATOR command to check whether the MNC and MCC are the same as those configured on the core network.
4. Check whether the device IP address used to configure the local port of the SCTP link conflicts with that of another site. If yes, an alarm is generated.
5. If the S1 interface status is still abnormal, check whether the MNC and MCC have been modified. If yes, restart the eNodeB to restore the S1 interface status.
