eNODEB Location in ENM

OSS and NOC
, ,
1

Dear,

Can you tell me how can I locate coordinate of an eNodeB in the ENM, through the parameters: MCC, MNC, TAC, ECI, NB ID and Locall Cell ID? I have the parameters, I would like to find the host in ENM.

Thank you

2

Hi, with your parameters you can find specific node:
cmedit get * ENodeBFunction.eNBId==NBID
after that, get coordinates:
cmedit get NetworkElement=ENODEBNAME,GeographicLocation=1,GeometricPoint=1
elevation: null
geometricPointId: 1
latitude: 26.0345
longitude: 22.8765

2 Likes
3

It works perfectly. Thanks my friend!

1 Like
4

What is GeographicLocation does not exist ?
I’ve tried to create it but it won’t let me do it:
cmedit create NetworkElement=NodeName,GeographicLocation=1

Error 1022 : GeographicLocation is not valid for neType RadioNode and ossModelIdentity 4009-066-199

But other nodes with same ossModelIdentity do have its associated GeographicLocation object

5

In case the MO does not exist, you need to create it first and then define the coordinates:

cmedit create NetworkElement=eNODED_NAME,GeographicLocation=1 geographicLocationId=1 -ns=OSS_GEO -v=2.0.0

We create the following MO and define its coordinates.

cmedit create NetworkElement=eNODED_NAME,GeographicLocation=1, GeometricPoint=1 geometricPointId=1, latitude=41.66063,longitude=“-0.89737” -ns=OSS_GEO -v=2.0.1

In this example, for negative values, they are placed in quotes.

1 Like
6

Thanks so much for those commands, but I already tried to create that MO.
Response was “Error 1022 : GeographicLocation is not valid for neType RadioNode and ossModelIdentity 4009-066-199”

But other nodes with same ossModelIdentity do have its associated GeographicLocation object.
Anyway, I’ve forgotten about this problem. I thought this MO was mandatory for the node to work properly, but it isn’t :yum:

7

Hi, @JuanK, did you try to recreate this node from scratch?

8

didn’t use CLI commands to create this node. I just followed the instruccions in “Add Node”.
Anyway, I’ve forgotten about this problem. I thought this MO was mandatory for the node to work properly, but it isn’t :yum:
And by the way, none of the nodes on this network have its latitude and longitude with values different than 0.0 :rofl: It looks it does not matter at all.

9

I think this object is for user convenience and for external tools.