E******* LTE X2 alarm:

[balaprashanth90]

Hi Everyone! Hope all doing good. I'm working as a LTE field integrator. I most of the times find that "External link failure X2" alarm in the eNodeB? Could anyone tell me what's the reason for that? If its bcoz of adjacent node link, how will I find which is its adjacent node from the node using moshell?

[scumbie]

Hello Bala,

Yes it is because of an adjacent/external enodeB. Type st TermPointToENB in moshell to see which node is having the issue

-che-

[balaprashanth90]

Thanks a lot Man!!

[josogun2]

Hi Member,

Always use the thanks button instead of thank post.

[scorpion]

Can you post the screenshot of this alarm and MOSHELL script procedure to check this......will help others to understand it better.

What I can see between "balaprashanth90 & scumbie " is a discussion between two scientists... help us (Non E/// PPl) to understand this

[frenchy]

check the alarm details where you will find the Enode B ID of the neighbour site impacted
this alarm is raised when the neighbour site is down or locked or no yet on air (neighbour relations created on the source site)

[scorpion]

Can you post some screens hot, will be a great help...

[frenchy]

here you go

XXX_LTE> alt

140203-16:27:17 x.x.x.x 9.0z ERBS_NODE_MODEL_C_1_127 stopfile=/tmp/1480
Connecting to x.x.x.x:x (CorbaSecurity=OFF, corba_class=2, java=1.6.0_29, jacoms=R74G12, jacorb=R74D01)
Trying file=/var/opt/e*******/amos/moshell_logfiles/user/logs_moshell/tempfiles/20140203-162705_1429/ior1429
Resolving the alarm service in OMS...
Simple Alarm Client initialized...
Starting to retrieve active alarms
Nr of active alarms are: 2
====================================================================================================================
Date & Time (Local) S Specific Problem MO (Cause/AdditionalInfo)
====================================================================================================================
2013-11-28 04:57:27 w Large Number of Counters SubNetwork=OSS,MeContext=XXX_LTE,ManagedElement=1 (performance_degraded)
2014-02-03 15:41:17 m ExternalLinkFailure ENodeBFunction=1 (X2 link problem to one or several neighbouring eNodeBs. PLMN ID-eNB ID 1 : xxxx-84094)
>>> Total: 2 Alarms (0 Critical, 0 Major)

in this case, EnodeB ID 84094 is a site locked, waiting for emission authorization.
this site has been unlocked this morning and after a lock/unlock of the X2, the alarm is gone

[yb4in]

in amos do a st termp> this will say which X2 link is disabled