External Link Failure: Operating Instructions
External Link Failure: Operating Instructions
Operating Instructions
Disclaimer
The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use of
this document.
Trademark List
All trademarks mentioned herein are the property of their respective owners.
These are shown in the document Trademark Information.
Contents
The External Link Failure alarm is raised when the X2 link to at least one
neighboring eNodeB is down after four resetup attempts. The time between
each resetup attempt is controlled by the x2RetryTimer. For more
information, see x2retryTimerStart .
The specific eNodeBs, to which the X2 links are down, are listed as Additional
Information in the alarm. Each listed eNodeB is named by the PLMN Id and
the eNodeB Id within that PLMN. The listed eNodeBs are sorted with the
oldest failed X2 link in the top of the list. The list can contain a maximum of
nine failed X2 links. If more than nine failed links have been detected, the
tenth Additional Information is PLMN ID-eNB ID list truncated.
Prerequisites
Steps
If there are more than one failed X2 links, resolve them one by one. Repeat
the following steps for each failed link:
4. Wait 3 minutes.
If the alarm remains, do the following:
5. Check the underlying transport network between the eNodeB and the
remote eNodeB for faults. If there are faults, correct them.
If the alarm remains for any of the links, do the following:
Prerequisites
Steps
2. Check the active cipher suites in the client and the server.
3. Ensure that the client and the server have at least one common and
activated cipher suite.