0% found this document useful (0 votes)
910 views8 pages

External Link Failure: Operating Instructions

Junaid
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
910 views8 pages

External Link Failure: Operating Instructions

Junaid
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 8

External Link Failure

Operating Instructions

92/1543-LZA 701 6014/1 Uen L


Copyright

© Ericsson AB 2016-2018. All rights reserved. No part of this document may


be reproduced in any form without the written permission of the copyright
owner.

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.

92/1543-LZA 701 6014/1 Uen L | 2018-02-12


Contents

Contents

1 Select Remedy Action for External Link Failure 1

2 Remedy Action for ENodeBFunction 2

3 Remedy Action for Ssh and Tls: No common cipher


available, link cannot be established. 4

92/1543-LZA 701 6014/1 Uen L | 2018-02-12


External Link Failure

92/1543-LZA 701 6014/1 Uen L | 2018-02-12


Select Remedy Action for External Link Failure

1 Select Remedy Action for External Link


Failure

External Link Failure is a primary alarm.

Table 1 Alarm Summary


Managed Object Additional Text Link to Recovery
Actions
ENodeBFunction Remedy action is Remedy actions
independent of
additional text.
Ssh No common cipher Remedy actions
available, link cannot be
established
Tls No common cipher Remedy actions
available, link cannot be
established

92/1543-LZA 701 6014/1 Uen L | 2018-02-12 1


External Link Failure

2 Remedy Action for ENodeBFunction

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.

Direct communication is disabled between the neighboring eNodeBs.


Communication between the eNodeBs is routed through the MME.

Prerequisites

At least one TermPointToEnb MO has been in UNLOCKED administrative


state and DISABLED operational state after four unsuccessful X2 link resetup
attempts.

Steps

If there are more than one failed X2 links, resolve them one by one. Repeat
the following steps for each failed link:

1. Select a failed link to analyze.

2. Check that the corresponding TermPointToEnb MO of the remote


eNodeB is not in the LOCKED administrative state.
If the TermPointToEnb MO is in the LOCKED administrative state, do the
following:

3. Unlock the TermPointToEnb MO.


If there are no more failed links to correct, do the following:

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:

2 92/1543-LZA 701 6014/1 Uen L | 2018-02-12


Remedy Action for ENodeBFunction

6. Consult the next level of maintenance support.

92/1543-LZA 701 6014/1 Uen L | 2018-02-12 3


External Link Failure

3 Remedy Action for Ssh and Tls: No


common cipher available, link cannot be
established.

The External Link Failure alarm can be raised if there is a cipher


mismatch (the client and server does not have a common cipher) and a link
cannot be set up.

To resolve the mismatch between the ciphers do the following:

Prerequisites

Access to the NMS.

Steps

1. Enter the NMS.

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.

4 92/1543-LZA 701 6014/1 Uen L | 2018-02-12

You might also like