The document discusses working with BSC nodes in ENM and provides the following key points:
- BSC node configuration is done through managed objects (MOs) below the BscM object which have non-standard behavior for create, update, and delete operations.
- There are limitations when making changes to BscM MOs including only allowing 100 operations per command and only one user making changes at a time.
- Commands on BscM MOs can partially succeed, with some attributes or objects succeeding and others failing. It is important to review any failed operations carefully.
1 of 2
Download to read offline
More Related Content
Enm cli
1. 3/25/2020 ENM CLI
https://mtelenm.mtel.me/#help/app/cliapp/topic/tutorials_cm/WorkingWithBsc 1/2
Working with BSC nodes
Background
In ENM the BSC node is modelled using many different types of Managed Objects (MO)s.
MOs below BscM in the topology tree (BscM MOs) have a non-standard behavior for configuration management create,
update and delete operations. All other BSC MOs have standard behavior.
For changes to BscM MOs, the BSC node converts the operations on the MOs into MML commands internally. Some
operations will result in multiple MML commands, or multiple operations can result in one MML command. For details of
the mapping of MOs and attributes to MML command, see the BSC node documentation (MOM and MML mapping -
1/001 21-CXA 113 13/1).
There may be dependencies between operations on different attributes. These are described in the model.
BscM MOs Limitations and Deviations
The maximum supported number of operations per command is 100. CM CLI prevent more from being executed as
results will be unpredictable.
A BSC node can only support one user at a time making changes to the BscM MOs. If the node is busy processing one
request, subsequent requests will fail with a "ComNoResources" error. Retry the request later when the node is no
longer busy processing other write operations.
Some changes on BscM MOs can take a long time, therefore the CM CLI command can take a long time to complete,
no response will be provided until the complete command is finished.
It is possible for commands on one Managed Object to partially execute as follows. Therefore, it is important to review
operations that result in a failure very carefully.
For a Create MO operation which has partially executed, the MO will be created, but all of the attributes may not
have been set correctly.
For a Set operation with multiple attributes, some of the attributes may succeed and some may fail.
The partially successful operation is marked as a FAILURE and the reason for the failure is described. It is
possible to see which attributes were successfully set as all attributes (modified or not) are displayed.
The limitations and deviations described are applicable for CM CLI write operations on live configuration only.
Examples
Maximum number of supported operations per command exceeded
cmedit set BSC028 Gerancell.(state==HALTED) fnOffset=1 --force
Response
FAILED FDN : MeContext=BSC028,ManagedElement=BSC028,BscFunction=1,BscM=1,GeranCellM=1,GeranCell=
8101
Error 3006 : Execution prohibited - only 100 MO changes for command on a BSC Node that includes
Objects with BscM as parent
FAILED FDN : MeContext=BSC028,ManagedElement=BSC028,BscFunction=1,BscM=1,GeranCellM=1,GeranCell=
8102
2. 3/25/2020 ENM CLI
https://mtelenm.mtel.me/#help/app/cliapp/topic/tutorials_cm/WorkingWithBsc 2/2
Error 3006 : Execution prohibited - only 100 MO changes for command on a BSC Node that includes
Objects with BscM as parent
...
FAILED FDN : MeContext=BSC028,ManagedElement=BSC028,BscFunction=1,BscM=1,GeranCellM=1,GeranCell=
8131
Error 3006 : Execution prohibited - only 100 MO changes for command on a BSC Node that includes
Objects with BscM as parent
FAILED FDN : MeContext=BSC028,ManagedElement=BSC028,BscFunction=1,BscM=1,GeranCellM=1,GeranCell=
8132
Error 3006 : Execution prohibited - only 100 MO changes for command on a BSC Node that includes
Objects with BscM as parent
SUCCESS FDN : MeContext=BSC028,ManagedElement=BSC028,BscFunction=1,BscM=1,GeranCellM=1,GeranCell
=8001
SUCCESS FDN : MeContext=BSC028,ManagedElement=BSC028,BscFunction=1,BscM=1,GeranCellM=1,GeranCell
=8002
...
SUCCESS FDN : MeContext=BSC028,ManagedElement=BSC028,BscFunction=1,BscM=1,GeranCellM=1,GeranCell
=8099
SUCCESS FDN : MeContext=BSC028,ManagedElement=BSC028,BscFunction=1,BscM=1,GeranCellM=1,GeranCell
=8100
Error 5008 : The command executed on 100 out of 132 objects
Set multiple attributes for multiple MOs with partially MO success
cmedit set MeContext=BSC028,ManagedElement=BSC028,BscFunction=1,BscM=1,GeranCellM=1,GeranCell
=011C112;
MeContext=BSC028,ManagedElement=BSC028,BscFunction=1,BscM=1,GeranCellM=1,GeranCell
=028170C ncc=4,bcc=4
Response
SUCCESS FDN : MeContext=BSC028,ManagedElement=BSC028,BscFunction=1,BscM=1,GeranCellM=1,GeranCell
=011C112
FAILED FDN : MeContext=BSC028,ManagedElement=BSC028,BscFunction=1,BscM=1,GeranCellM=1,GeranCell=
028170C
Error 9999 : MML execution failed. Failed MML: RLDEC:CELL=028170C,BSIC=44; Result: NOT ACCEPTED,
FAULT CODE 4, CELL STATE NOT HALTED.
Error 5008 : The command executed on 1 out of 2 objects
Set multiple attributes for single MO with partially attributes success
cmedit set MeContext=BSC028,ManagedElement=BSC028,BscFunction=1,BscM=1,GeranCellM=1,GeranCell
=CE01,Mobility=1 ahostate=ACTIVE,nshState=INACTIVE
Response
PARTIALLY SUCCESSFUL FDN : MeContext=BSC028,ManagedElement=BSC028,BscFunction=1,BscM=1,GeranCell
M=1,GeranCell=CE01,Mobility=1
SUCCESS ATTRIBUTE(S) : [ahoState]
FAILED ATTRIBUTE(S) : [nshState]
Error 3007 : Partial attribute failure message - MML execution failed. Failed MML: RLHSE:CELL=CE
01; Result: NOT ACCEPTED, FAULT CODE 434, AUTOMATIC HANDOVER OPTIMIZATION IS ACTIVE.