PASO 4.-Seguimiento y control de los subprocesos de la Gestión de los Recursos Humanos
3. CAPÍTULO II
3.3.2.14 Capacitaciones y Evaluación del desempeño
1. Log in to the NetAct Start Page as the user who has the permission to disable integration.
Note: For more information, refer to Managing integration users.
2. Select Monitoring → Monitor.
Expected outcome
The NetAct Monitor application window appears.
3. In the NetAct Monitor, right-click the LTE iOMS object.
4. Select Maintenance → Set under Maintenance.
5. Select Delete All Alarms from Database → Delete Alarms For Object And Its Subnetwork.
6. When prompted, select Yes, and then wait until the process is completed.
7. From the NetAct Start Page, select Configuration → CM Operations Manager.
Expected outcome
The CM Operations Manager application opens.
8. To open the Workflow Engine dialog box, perform either of the following:
•
From the Tools menu, select Workflow Engine....•
In the Plans tab, select the plan name, and then from the Tools menu, select WorkflowExpected outcome
The Workflow Engine dialog box appears.
9. In the MO(s) area, you can perform either of the following:
•
Drag and drop the network elements from CM Editor.•
Copy and paste the network elements from CM Editor.•
Select working sets from the Working Set field.Note: CM Editor and Workflow Engine must be open to drag and drop, or copy and
paste, the network elements from CM Editor. To locate the managed objects:
1. In the NetAct Start Page, select Configuration → CM Editor.
2. From the left pane, select Actual Configuration → PLMN-PLMN → <managed
object>.
10. From the Operation List drop-down list, select NE data deletion from Configurator. 11. In the Start column, click Start to begin the operation.
12. In the Name field, enter a name for the operation. This step is optional.
13. In the Description field, enter a description for the operation. This step is optional. 14. In the Scope area, select the managed objects for which the operation needs to be done. 15. Click Start.
16. When prompted, select Yes, and then wait until the process is completed. Expected outcome
The NE data deletion from Configuration: Finished dialog box appears displaying the results of the operation.
17. In NetAct Monitor, select Tools → Managed Objects → Object Explorer.
18. Expand the PLMN-PLMN object.
19. Right-click the LTE iOMS object, and then select Element Management → Element Manager →
OMS EM.
Expected outcome
Integrating Flexi Multiradio BTS LTE to NetAct Disabling integration
Note: If the message JAVA VIRTUAL MACHINE VERSION IS NOT SUPPORTED
appears, then you may ignore it by pressing I on the keyboard.
20. Double-click Parameter Tool.
Note: If the Parameter Tool is not visible in the Application Launcher, follow the
procedure under the LTE iOMS Parameter Tool entry in the Preparation checklist for LTE iOMS table to make the Parameter Tool visible.
Expected outcome
The Parameter Tool window appears.
21. Select fsClusterId=ClusterRoot → fsFragmentId=NWI3 → fsFragmentId=mediator.
If there are multiple items under fsFragmentId=mediator, then select the item that has an Active Value of true for fsnwi3configurationActive.
22. On the right-hand pane, remove value designated for fsnwi3registrationServiceIOR.
To remove the value from the Active Value column of fsnwi3registrationServiceIOR, double- click the figure, clear the IOR entry, and then click OK.
Expected outcome
The Active Value of fsnwi3registrationServiceIOR is updated to IOR.
23. Close the Parameter Tool window and the Application Launcher window.
24. Using SSH, log in to LTE iOMS as Nemuadmin user.
25. Using the su - command, switch to root user and restart NWI3Adapter by entering the following
command:
fshascli -rn /NWI3Adapter
Expected outcome
The NWI3Adapter restarts and the changes are saved.
Expected outcome
The NetAct Monitor application window appears.
27. In the NetAct Monitor, right-click the LTE iOMS object.
28. When prompted, select Delete → Yes, and then wait until the process is completed.
Note: For more information, refer to Deleting managed object.
Integrating Flexi Multiradio BTS LTE to NetAct
8 Troubleshooting integration problems
8.1 Integration data upload fails
Problem
The integration process is not successful.
Possible causes
•
NWI3 Access is not created in NEAC.Troubleshooting integration problems
•
Username or password of NWI3 Access is not configured correctly in NEAC.•
The NWI3 service of NetAct is not active.•
NWI3Adapter of LTE iOMS was locked.1. Create or recreate NWI3 access.
a) If NWI3 Access for LTE iOMS has not yet been created, then create it. For more information, refer to Creating service users required for Flexi Multiradio BTS LTE Integration.
b) If NWI3 Access has already been created but the problem still happens, then recreate the NWI3 Access.
1. Log in to the NetAct Start Page as omc user.
2. Select Security → Network Element Access Control.
3. Check if NWI3 Access has the proper credential. If the credential is not correct, then
proceed to the next step.
4. Select NWI3 Access and then click Delete.
5. To recreate NWI3 Access for LTE iOMS, refer to Creating service users required for Flexi
Multiradio BTS LTE Integration.
c) Check the password of NWI3 Access.
1. Log in to the NetAct Start Page as omc user.
2. Select Security → Network Element Access Control.
3. Check if NWI3 Access credential for Network Element is correct. If the username is not
correct, then remove NWI3 Access for LTE iOMS, and then create a new NWI3 Access for LTE iOMS.
4. If the password is not correct, then select NWI3 Access for LTE iOMS. 5. Click Modify, and then enter the correct password. 6.
Launch Integration Data Upload. d) Start the NWI3 service.
Note: These steps are intended only for the system administrator with root privileges.
1. Log in to the NetAct NWI3 node as root user.
2. To start the NWI3 service, enter the following command:
smanager.pl start service nwi3
Expected outcome
NWI3 service starts successfully.
An output like the one below appears:
Service nwi3 started on node <node where the service is located>
3. Launch Integration Data Upload.
e) Check the status of NWI3Adapter.
1. Log in to the LTE iOMS NE with a valid account.
2. To check the NWI3Adapter status, enter the following command:
fshascli -s /NWI3Adapter
Expected outcome
An output like the one below appears:
Figure 20: Example of output
3. If NWI3Adapter is locked, unlock it by entering the following command:
fshascli -u /NWI3Adapter
Expected outcome
NWI3Adapter is unlocked.
You may also refer to Unlock LTE iOMS NWI3 Adapter.
4. To restart NWI3Adapter, enter the following command:
fshascli -rn /NWI3Adapter
Expected outcome
Integrating Flexi Multiradio BTS LTE to NetAct Troubleshooting integration problems
5. Launch Integration Data Upload again.
2. Update Parameter Tool attributes and restart NWI3 Adapter.
a) Using an SSH client, log in to the node where NWI3 service is running. b) Get the IOR information by entering the following command:
cat /var/opt/oss/global/nwi3/RegistrationService.<NetAct node where NWI3 service is running>.ior
For example, cat /var/opt/oss/global/nwi3/
RegistrationService.clab123node01.netact.nsn-rdnet.net.ior
Expected outcome
An output like the one below appears:
IOR:010000002400000049444c3a4e5749332f526567697374726174696f6e53657276 6963655f56313a312e300001000000000000008c000000010102000d00000031302e34 342e3234362e3134000006c03900000014010f004e5550000000190000000001000000 526f6f74504f41006e77336e33632e31006e77336e33632e315f526567536572766963 655f3000000002000000000000000800000001ec8900004f4154010000001800000001 ec89000100010001000000010001050901010000000000
Take note of the IOR information.
c) Get the password of the nwi3system user by entering the following command:
/opt/nokia/oss/bin/syscredacc.sh -user nwi3system -type APPSERV - instance APPSERV
Expected outcome
The password of the nwi3system user is displayed.
d) Close the SSH session. e) Open the Application Launcher.
Note:
The IP address of LTE iOMS must be determined prior to launching the tool. If the Application Launcher is not yet installed, then install it locally. For more information, refer to Installing Application Launcher in Node Manager Server.
f) Run the Parameter Tool.
Note: If the Parameter Tool is not visible in the Application Launcher, follow the
procedure under the LTE iOMS Parameter Tool entry in the Preparation checklist for
g) Check the value of fsnwi3ActiveN3CF. Navigate to fsFragmentID = NWI3 → fsFragmentID = security. Take note of the fsnwi3ActiveN3CF value.
h) Navigate to fsFragmentID=NWI3 → fsFragmentID=mediator → fsnwi3N3CFId=X.
Note: X must be equal to the value of fsnwi3ActiveN3CF determined in the previous
step.
i) Modify the following attributes:
Parameter Tool attribute
fsnwi3initialRegistrationUsername
fsnwi3initialRegistrationPassword
fsnwi3registrationServiceIOR
fsnwi3takeIntoUseNext
Table 24: Values for Parameter Tool attributes
j) Close Parameter Tool and Application Launcher. k) Log in to LTE iOMS using an SSH client.
New Value
nwi3system
The password derived from Step 3
The IOR value derived from Step 2
true
l) Restart NWI3Adapter by entering the following command:
fshascli -r /NWI3Adapter
Expected outcome
NWI3Adapter restarts successfully.
m) To check the status of LTE iOMS services, enter the following command:
# zstatus -d
Expected outcome
An output like the one below appears: Monitoring cluster
CLA-0 R_GOMS6_1.113.1.0.release_oms.corr4 RecoveryGroups(@OMS, disabled):
RecoveryUnits(@/, disabled): Processes(@/, disabled): Monitoring cluster FINISHED
Integrating Flexi Multiradio BTS LTE to NetAct Troubleshooting integration problems
n) Execute Integration Data Upload again. For more information, refer to Executing integration
data upload.
3. Unlock LTE iOMS NWI3 Adapter.
a) Log in to LTE iOMS using an SSH client.
b) Unlock NWI3Adapter by entering the following command:
fshascli -u /NWI3Adapter
Expected outcome
NWI3Adapter is successfully unlocked.
c) Launch Integration Data Upload again.
8.2 Alarm upload fails
Problem
HTTPS operation failure in CM upload.
Possible causes
•
The required certificates are not installed.Solution
Make sure the required licenses are installed. For more information, refer to Configuring certifications
on network element.
8.3 Element management launch fails
Problem
•
The element manager can not be launched.Possible Causes
•
Node manager is not installed or configured properly.•
Element manager is not configured properly.Solution
1. Check Node Manager installation and configuration. For more information, contact your NetAct
administrator.
2. Check if the related service user is created. For more information, refer to Creating service users
required for Flexi Multiradio BTS LTE Integration.
3. Check if the element manager is configured properly. For more information, refer to Prerequisites
for Element Management
8.4 No fault management data received
Problem
•
There is no alarm displayed in NetAct Monitor.Possible causes
•
User permission is incorrect.•
Firewall is not properly set up. For more information, refer to Setting up firewall rules.•
Integration data upload failed.For more fault management troubleshooting information, refer to the Troubleshooting section of the NetAct Operating Documentation and navigate to Troubleshooting NetAct → Fault Management. Solution
1. Check connectivity and required NetAct components.
a) Check if the NWI3 mediation is running.
•
For instructions on starting the service, refer to Starting the NWI3 service in AdministeringNWI3.
•
For more information, refer to Checking the status of NWI3 mediation in AdministeringNWI3.
b) Check the IP connectivity between Flexi LTE BTS and NetAct. For more information, refer to
Checking connection from NetAct to Flexi Multiradio BTS LTE.
c) Check the deployed adaptation packages. For more information, refer to Checking the
adaptation packages in Adaptation Manager.
2. Check required permissions.
Verify if the appropriate user permission is granted. For more information, refer to Creating service
users required for Flexi Multiradio BTS LTE Integration.
Integrating Flexi Multiradio BTS LTE to NetAct Troubleshooting integration problems
Verify if the Fault Management process is running. For more information, refer to Administering
Fault Management.
8.5 State management operation
8.5.1 State management operation fails
The basic feature of the State Management functionality is the ability to change the Administrative State of network elements, such as LNCELs. The Administrative State on an object describes the permission for, or prohibition against, using the resource imposed through management services. This function is triggered using a dedicated state management option in the NetAct Monitor.
Problem
•
Failed appears as the status of State Management.Possible Causes
•
PLMN hierarchy is incorrect.•
The required licenses are missing.•
The Enable Graceful Cell Shutdown parameter is disabled1. Check connectivity and required NetAct components.
a) Check if the NWI3 mediation is running.
•
For instructions on starting the service, refer to Starting the NWI3 service in AdministeringNWI3.
•
For more information, refer to Checking the status of NWI3 mediation in AdministeringNWI3.
b) Check the IP connectivity between Flexi LTE BTS and NetAct. For more information, refer to
Checking connection from NetAct to Flexi Multiradio BTS LTE.
c) Check the deployed adaptation packages. For more information, refer to Checking the
adaptation packages in Adaptation Manager.
2. Check root object of NE.
Make sure the network element is under PLMN-PLMN hierarchy in NetAct Monitor. For more information, refer to Checking and creating the root object in NetAct.
3. Check required licenses.
Make sure the required licenses are installed. For more information, refer to Checking NetAct
licenses required for LTE software.
In the CM Editor, set the value of the LNBTS parameter Enable Graceful Cell Shutdown
(enableGrflShdn) to Enabled. For more information, refer to Changing the administrative state of
managed objects under NetAct Administration.
8.5.2 Error message "Existing operation is still running, please try again later."
appears
Every State Management operation is locked according to the network element being processed. Simultaneous execution of State Management operations is not possible on the same network
element. The preceding operation must be completed before another state management operation can proceed.
Problem
Unable to proceed with the state management operation even if no other operation is currently running.
Possible Cause
Forced or premature termination of the previous state management operation.
Solution
Note: Note down the BTS instance number of the unresponsive network element.
1. From the NetAct Start Page, open the CM Operations Manager application. 2. In CM Operations Manager, click the Operation History tab.
3. Check the status of the provision operation of the affected network element.
If the status is Started, wait for the provision operation to be completed before executing another State Management operation on the network element.
If the status is either Finished, Failed, or Interrupted, or if the provision operation of the affected network element is not found, then do the following:
a) Using an SSH client, log in to the NetAct node running the WAS service as omc user. b) Navigate to /var/opt/nokia/oss/global/adaptations/statemgmt by entering the
following command:
cd /var/opt/nokia/oss/global/adaptations/statemgmt c) Locate the LCK files related to the unresponsive network element object. d) Remove the LCK file by entering the following command:
rm MRBTS-<instance_number>.LCK For example:
Integrating Flexi Multiradio BTS LTE to NetAct Troubleshooting integration problems
rm MRBTS-1728.LCK
4. Retry the failed state management operation.