Vous êtes sur la page 1sur 68

System Self Monitoring and Administration Tasks

System Self Monitoring and


Administration Tasks

Content
1 NetAct Self Monitoring 3
1.1 Overview 4
1.2 Data Flow 5
1.3 What is monitored? 7
1.4 Administering Self Monitoring 12
2 Administration Tasks 31
2.1 Revising the Status of the NetAct High Availability Services 32
2.2 Preventive Health Check 34
2.3 Log Monitor Tool 47
2.4 Preparing NetAct for Hardware Maintenance 50
2.5 Restoring a Host from Hardware Maintenance 51
2.6 Shutting down a Host 51
2.7 Live Migrating Virtual Machines Manually 51
2.8 Monitoring the Virtual Infrastructure 52
2.9 Recommended system shutdown and startup order 52
2.10 Shutting down NetAct 56
2.11 Starting up NetAct 58
2.12 Shutting down and starting up the hardware 60
3 Exercises 61
Exercise 1 63
Exercise 2 65
Exercise 3 67

OS90515EN15GLA0
Copyright ©2015 Nokia Solutions and Networks.
1
System Self Monitoring and Administration Tasks

OS90515EN15GLA0
Copyright ©2015 Nokia.Solutions and Networks.
2
System Self Monitoring and Administration Tasks

1 NetAct Self Monitoring

OS90515EN15GLA0
Copyright ©2015 Nokia Solutions and Networks.
3
System Self Monitoring and Administration Tasks

1.1 Overview
NetAct monitors its own performance and processes, both in hardware and software. System self-
monitoring processes and forwards performance management (PM) and fault management (FM)
data collected from the NetAct system to NetAct itself. The results of the self-monitoring process
can be seen in performance management reports for the PM data and as alarms for the FM data.
The solution is based on the O&M Agent software, which is installed on all NetAct virtual
machines and which starts to function immediately after installation. O&M Agent provides the
central functionality for the system self-monitoring: it raises alarms and cancels them when the
fault situation has been resolved. O&M Agent contains the Integration Framework and Core
components, and it also has configuration for active self-monitoring of FM and PM data.
.

WARNING
Network elements are not covered in scope of Self Monitoring

OS90515EN15GLA0
Copyright ©2015 Nokia.Solutions and Networks.
4
System Self Monitoring and Administration Tasks

1.2 Data Flow


NetAct hardware monitoring is carried out using HP SIM which monitors the hardware. HP SIM is
integrated into hardware at the time of NetAct installation.
NetAct software monitoring is done using O&M Agent that monitors specific NetAct objects.
1. Integration Framework monitors both NetAct software and certain aspects of hardware, for
example, the size of free space in file systems, and collects measurements.
2. HP SIM collects the alarms related to NetAct hardware, such as servers and switches, and
sends that data to Integration Framework (FM data Collection and PM Data Collection).
3. NetAct software-related alarms and measurements are collected directly by Integration
Framework.
4. The Core component of O&M Agent further processes FM and PM data and forwards it back
to NetAct itself as events and measurements using the NE3S/WS southbound interface.
5. FM and PM pipes transfer alarms and measurements to the NetAct database, from which the
FM and PM tools handling the data, Monitoring Desktop and Performance Manager
respectively, can access and show or process it. The FM and PM pipes also transfer the data
to NetAct’s northbound interfaces (optional), from where the self-monitoring data can be
forwarded to other network management systems for further processing.

OS90515EN15GLA0
Copyright ©2015 Nokia Solutions and Networks.
5
System Self Monitoring and Administration Tasks

NetAct Self Monitoring


Data Flow

HW HP SIM NB Interface

SW Performance
Database Manager
FM data PM data Monitoring
Collection Collection Desktop

O&M Adaptation
Agent

O&M Agent Core PM pipe FM pipe


Data Processing

NE3S/WS SB Interface Mediation

1 © Nokia Solutions and Networks 2014

Fig. 1

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .OS90515EN15GLA0
. . .
Copyright ©2015 Nokia.Solutions and Networks.
6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Self Monitoring and Administration Tasks

1.3 What is monitored?


1.3.1 Hardware
The monitored NetAct hardware is integrated during NetAct installation to HP SIM, which monitors
NetAct’s own hardware.
When the integration is complete, the HP SIM service starts to monitor NetAct hardware
resources, including for example, server hardware, DCN routers and switches, firewalls, and
storage devices. It also triggers alarms in NetAct Monitor when a pre-defined alarm severity
criteria is met.
In addition to displaying the alarms and their details in the HP SIM graphical user interface (GUI),
the HP SIM service sends notifications to O&M Agent, which in turn, forwards them to NetAct
Monitor. Critical and important hardware faults that require attention are interpreted by the HP
SIM service, which categorizes the alarms into three groups: server hardware faults, DCN
hardware faults, and storage hardware faults. Hence, in NetAct Monitor, only three types of
hardware alarms are visible as shown in the following table with the corresponding managed
objects:
.
Alarm ID Alarm Text Managed Object

10034 HP SIM Reported a Server Hardware Fault Hardware / Server


10035 HP SIM Reported a DCN Hardware Fault Hardware / DCN
1036 HP SIM Reported a Storage Hardware Fault Hardware / Storage

TIP
If there is a need to find out more about a particular hardware alarm, it is possible to
check the information from HP SIM.

OS90515EN15GLA0
Copyright ©2015 Nokia Solutions and Networks.
7
System Self Monitoring and Administration Tasks

1.3.1.1 Clearing hardware alarms


Hardware alarms need to be cleared first from HP SIM to automatically cancel the corresponding
alarm in NetAct Monitor. On the other hand, cancelling a hardware alarm in NetAct Monitor can
lead to synchronization problems as this operation does not cancel the corresponding alarm in
HP SIM.

1.3.1.2 Customizing alarms


The severity of each event or trap sent by the device is defined by the hardware vendors. It is
possible to modify the trap severity in the HP SIM GUI. However, this is not recommended as
changing the trap severity may cause an unwanted number of alarms to appear in NetAct Monitor
if, for example, the severity of some informational events is changed to major. On the other hand,
critical alarms may go unnoticed if severity is reduced.
It is also possible to disable certain events in HP SIM, such as the sign-in events. Unsuccessful
login attempts that arise when a user enters the wrong credentials create a critical security event.
As the severity set for the event is critical, a hardware alarm is triggered in NetAct Monitor.
Permission to disable such events should always be negotiated with the local security team as
this may violate the security policies set in your organization.

OS90515EN15GLA0
Copyright ©2015 Nokia.Solutions and Networks.
8
System Self Monitoring and Administration Tasks

NetAct Self Monitoring


Hardware Monitoring: Hardware Alarms

HW alarms need to be cleared first


from HP SIM to automatically
cancel the corresponding alarm in
NetAct Monitor

cancelling a HW alarm in NetAct Monitor can


lead to synchronization problems as this
operation does not cancel the
corresponding alarm in HP SIM.

If there is a need to find out more about a


particular hardware alarm, it is possible to
check the information from HP SIM

1 © Nokia Solutions and Networks 2014

Fig. 2

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . .
OS90515EN15GLA0 . . . . . . . . . . . . . . . . . . . . . . . . .
. . ©2015
Copyright . Nokia
. .Solutions
. . and.Networks.
. . . . . . . . . . . . . . . . . . . . . . . . . . .
9
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Self Monitoring and Administration Tasks

1.3.2 Software
During NetAct installation, a script checks for NetAct managed objects and O&M Agent starts to
monitor the objects that have been found. Topology upload is also supported.

1.3.3 Virtualization
Self Monitoring in NetAct 15 also includes support for virtualization related alarms.

OS90515EN15GLA0
Copyright ©2015 Nokia.Solutions and Networks.
10
System Self Monitoring and Administration Tasks

NetAct Self Monitoring


Software Monitoring

During NetAct installation, a script


checks for NetAct managed objects
and O&M Agent starts to monitor
the objects that have been found.

1 © Nokia Solutions and Networks 2014

Fig. 3

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . .
OS90515EN15GLA0 . . . . . . . . . . . . . . . . . . . . . . . . .
. . ©2015
Copyright . Nokia
. .Solutions
. . and.Networks.
. . . . . . . . . . . . . . . . . . . . . . . . . . .
11
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Self Monitoring and Administration Tasks

1.4 Administering Self Monitoring


1.4.1 Starting and stopping O&M Agent
1.4.1.1 Checking the Status of the O&M Agent
1. Log in to any NetAct virtual machine (VM), and switch to the root user.
2. To check whether the Core and the Integration Framework components of O&M Agent are
running, enter:
[root]# smanager.pl status service OMAgent
An output like the one below appears.

The number of VMs in this sample output may differ, depending on your configuration.
Note:
The Integration Framework component is configured to run in each VM so that O&M statistics can
be generated for every VM.

1.4.1.2 Starting O&M Agent


1. Log in to the VM where the Core component of O&M Agent is stopped, and switch to the
root user.
2. To start the Core component of O&M Agent, enter:
[root]# smanager.pl start service OMAgent

Service omagent started on node <vm where the service is located>

3. To start the Integration Framework component in each virtual machine, enter:


[root]# smanager.pl start service OMAgentAF-<vm name>
Note:
Ensure that the Integration Framework component in each VM is running so that O&M statistics
can be generated for every VM.

Service omagentaf-<vm name> started on node <vm where the service is located>

OS90515EN15GLA0
Copyright ©2015 Nokia.Solutions and Networks.
12
System Self Monitoring and Administration Tasks

1.4.1.3 Stopping O&M Agent

WARNING
Stopping the O&M Agent services is not at all recommended unless there is a
critical configuration change that requires restarting such services.
1. Log in to any NetAct virtual machine (VM), and switch to the root user.
2. To stop the Integration Framework component in each VM, enter:
[root]# smanager.pl stop service OMAgentAF-<vm name>

Service omagentaf-<vm name> stopped

3. Log in to the VM where the Core component of O&M Agent is running, and switch to the root
user.
4. To stop the Core component of O&M Agent, enter:
[root]# smanager.pl stop service OMAgent

Expected outcome

Service omagent stopped

WARNING
Please note that the start and stop order is important.

1.4.2 Configuration files


The configuration files for Self Monitoring are stored at /opt/cpf/oma/AF/cpf_config

OS90515EN15GLA0
Copyright ©2015 Nokia Solutions and Networks.
13
System Self Monitoring and Administration Tasks

1.4.3 Objects
1.4.3.1 Basic Resource Monitoring & Hardware Monitoring
The Self Monitoring Managed Objects are automatically created at the time of NetAct installation
and can be explored using the ‘Object Explorer’ tool in the NetAct Desktop.
The Basic Resource Monitoring (BRM) objects are grouped under the node NetAct Instance-
< name>. This is the parent node for all Self Monitoring objects. Under NetAct instance node
there is a single NE3SWS node and nodes for each of the VMs in the NetAct 15 cluster.
HP SIM objects are grouped under the node HW-1. All HP SIM alarms and measurements belong
to one of three HP SIM objects – DCN SIM, Server SIM and Storage SIM. There is only
one HW-1 node for a NetAct instance.

OS90515EN15GLA0
Copyright ©2015 Nokia.Solutions and Networks.
14
System Self Monitoring and Administration Tasks

Administering Self-Monitoring
Objects
NetAct instance

NE3SWS object

VM node objects

Specific objects are automatically


created in NetAct for Self
Monitoring
1 © Nokia Solutions and Networks 2014

Fig. 4

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . .
OS90515EN15GLA0 . . . . . . . . . . . . . . . . . . . . . . . . .
. . ©2015
Copyright . Nokia
. .Solutions
. . and.Networks.
. . . . . . . . . . . . . . . . . . . . . . . . . . .
15
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Self Monitoring and Administration Tasks

1.4.4 Log files


 Self Monitoring core
/opt/cpf/oma/esymacstarter/logEvents.log.0
This log contains PM and FM information as well as O&M activities. This file is located in the VM
that hosts the OMAgent service

 Adapter Framework
/opt/cpf/oma/AF/af.%g.log
These files contain the event logs on O&M Adapter Framework activities, including configuration
checks, object discovery and registration. The logs are located in the VMs that host the
OMAgentAF service

 HP SIM audit log file


/var/opt/mx/logs/mx.log
HP SIM Audit log file. The file is located in the VM that hosts the hpsim service.

 HP SIM server log file


/var/opt/mx/logs/mxdomainmgr.0.log
Server startup file. The file is located in VM that hosts the hpsim service

OS90515EN15GLA0
Copyright ©2015 Nokia.Solutions and Networks.
16
System Self Monitoring and Administration Tasks

1.4.5 HP Systems Insight Manager (SIM)


HP System Insight Manager (SIM) is used for monitoring server hardware, DCN routers and
switches, firewalls, and storage devices. HP SIM automatically discovers and identifies HP
servers that are used in the NetAct system. Other hardware used, such as the EMC VNX storage
system or HP switches can be manually integrated with HP SIM.
HP SIM agents collect performance management (PM) and fault management (FM) data from the
hardware in the managed system and forward it to the HP SIM manager for further processing.
Critical and important hardware faults that require attention are interpreted by the HP SIM service,
which categorizes the alarms into three groups:

 Server hardware faults

 DCN hardware faults

 Storage hardware

1.4.5.1 Launching the HP SIM GUI


To launch the HP SIM GUI, enter in a web browser:
https://<HP SIM package host name or virtual IP address>:50000/
The HP SIM login page opens.
Enter the application server hpadmin user’s username and password.
The HP SIM GUI opens.

Tip:
Instructions on how to use or administer the HP SIM GUI are available in the GUI’s online help.

OS90515EN15GLA0
Copyright ©2015 Nokia Solutions and Networks.
17
System Self Monitoring and Administration Tasks

Administering Self-Monitoring
HP Systems Insight Manager

1 © Nokia Solutions and Networks 2014

Fig. 5

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .OS90515EN15GLA0
. . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .Copyright
. .©2015
. Nokia.Solutions
. . . .and Networks.
18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Self Monitoring and Administration Tasks

Administering Self-Monitoring
HP Systems Insight Manager: All systems view

1 © Nokia Solutions and Networks 2014

Fig. 6

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . .
OS90515EN15GLA0 . . . . . . . . . . . . . . . . . . . . . . . . .
. . ©2015
Copyright . Nokia
. .Solutions
. . and.Networks.
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Self Monitoring and Administration Tasks

Administering Self-Monitoring
HP Systems Insight Manager: All Storage Systems view

1 © Nokia Solutions and Networks 2014

Fig. 7

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .OS90515EN15GLA0
. . .
Copyright ©2015 Nokia.Solutions and Networks.
20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Self Monitoring and Administration Tasks

Administering Self-Monitoring
HP Systems Insight Manager: Enclosure Details view

1 © Nokia Solutions and Networks 2014

Fig. 8

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . .
OS90515EN15GLA0 . . . . . . . . . . . . . . . . . . . . . . . . .
. . ©2015
Copyright . Nokia
. .Solutions
. . and.Networks.
. . . . . . . . . . . . . . . . . . . . . . . . . . .
21
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Self Monitoring and Administration Tasks

1.4.5.2 Checking HP SIM Status


1. Log in to any NetAct virtual machine (VM), and switch to the root user.
2. To check the HP SIM status, enter:
[root]# /opt/cpf/bin/smanager.pl status service hpsim
3. Log in to the VM where the HP SIM service is running.
4. To check the HP SIM status, enter:
[root]# /opt/mx/bin/mxstatus -v

1.4.5.3 Starting HP SIM


1. Log in to any NetAct virtual machine (VM), and switch to the root user.
To start the HP SIM service, enter:
[root]# /opt/cpf/bin/smanager.pl start service <hp sim service name>
For example:
[root]# /opt/cpf/bin/smanager.pl start service HPSimHA

1.4.5.4 Stopping the HP SIM service


1. Log into an application server and switch to the root user.
To stop the HP SIM service, enter:
[root]# /opt/cpf/bin/smanager.pl stop service <hp sim service name>
For example:
[root]# /opt/cpf/bin/smanager.pl stop service HPSimHA

OS90515EN15GLA0
Copyright ©2015 Nokia.Solutions and Networks.
22
System Self Monitoring and Administration Tasks

1.4.6 Self Monitoring related Objects


ID Super Class ID Presentation Path
Server Equipment Server NSNNetwork NetActHW
Server

FTPService LogicalDevice File Transfer Protocol NSNNetworkNetAct


Service LogicalServerFTPService

HighAvailability LogicalDevice High Availability Service NSNNetworkNetAct


LogicalServerHighAvailability

DatabaseService LogicalDevice Database Service NSNNetworkNetActLogicalServer


 DatabaseService

Storage Equipment Storage NSNNetworkNetActHW


Storage

NSNNetwork Network NSN Network NSNNetwork

BackupRestore LogicalDevice Backup system NSNNetworkNetAct


LogicalServerBackupRestore

HW PhysicalDevice Hardware NSNNetworkNetActHW

BRM LogicalResource Basic Resource Monitoring NSNNetworkNetActBRM

LoadBalancer LogicalDevice Load Balancing service NSNNetworkNetAct


LogicalServerLoadBalancer

DirectoryService LogicalDevice Directory Service NSNNetworkNetAct


LogicalServerDirectoryService

Scheduling LogicalDevice Scheduler NSNNetworkNetAct


LogicalServerScheduling

NetAct NSNManagementS NetAct NSNNetworkNetAct


ystem

OperatingSystem LogicalDevice Operating System NSNNetworkNetAct


LogicalServerOperatingSystem

J2EEServer LogicalDevice J2EEServer NSNNetworkNetAct


LogicalServerJ2EEServer

FileSystem LogicalDevice File System NSNNetworkNetAct


LogicalServerFileSystem

LogicalServer LogicalDevice Logical Server NSNNetworkNetAct


LogicalServer

DCN Equipment Data Communication NSNNetworkNetActHW DCN


Network

CertificateStorage LogicalDevice CertificateStorage NSNNetworkNetAct


LogicalServerCertificateStorage

OS90515EN15GLA0
Copyright ©2015 Nokia Solutions and Networks.
23
System Self Monitoring and Administration Tasks

Administering Self-Monitoring
Self- Monitoring related Objects

1. Select Objects tab

2. Select Adaptation for


Self Monitoring

3. Select Release

4. The list of objects


is displayed

1 © Nokia Solutions and Networks 2014

Fig. 9

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .OS90515EN15GLA0
. . .
Copyright ©2015 Nokia.Solutions and Networks.
24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Self Monitoring and Administration Tasks

1.4.7 Self Monitoring related Alarms


The following table details all alarms related to Self Monitoring

Alarm number Alarm text


10015 NO SPACE FOR BACKUPS

10006 READING OF THE DISK SHARINGSERVICE DOES NOT SUCCEED

10002 DIRECTORY SERVER DB CACHE HIT RATIO TOO LOW

10028 DEPLOYMENT MANAGER CAN NOT BE CONTACTED

86022 SELF MONITORING INTERNAL PROBLEM

10023 WAS NODE AGENT IS NOT WORKING

10010 DATABASE IS DOWN

10036 HP SIM REPORTED A STORAGE HARDWARE FAULT

10011 LISTENER IS DOWN

10035 HP SIM REPORTED A DCN HARDWARE FAULT

10 O&M AGENT HEARTBEAT PROBLEM

10026 NODES ARE NOT SYNCHRONIZED

10001 DIRECTORY SERVER REPLICATION IS NOT WORKING

10038 CERTIFICATE IS ABOUT TO EXPIRE

10017 FTP SERVICE IS NOT WORKING

10004 MEMORY IS LOW

10014 BACKUP ACTION FAILED

10000 DIRECTORY SERVER IS DOWN

10022 WAS DEPLOYMENT MANAGER IS NOT WORKING

10016 SCHEDULING IS NOT WORKING

10037 HA NODE IS NOT WORKING

10024 WAS APPLICATION SERVER IS NOT WORKING

9047 ALARMS FROM THE SELF MONITORING SYSTEM NOT ARRIVING

10003 DIRECTORY SERVER ENTRY CACHE HIT RATIO TOO LOW

10007 WRITING FOR THE DISK SHARING SERVICE DOES NOT SUCCEED

10005 HA SERVICE IS NOT WORKING

10012 DATABASE TABLESPACE IS GETTING FULL

OS90515EN15GLA0
Copyright ©2015 Nokia Solutions and Networks.
25
System Self Monitoring and Administration Tasks

Alarm number Alarm text


10034 HP SIM REPORTED A SERVER HARDWARE FAULT

10018 LOAD BALANCER SERVICE IS NOT WORKING

10013 DATABASE IS NOT OPEN

10027 USED MEMORY IS TOO CLOSE TO MAX HEAP SIZE

10021 AVAILABLE DISK CAPACITY IS LOW

9450 CONNECTION FAILURE TO AN SNMP HOST

9251 MAINTENANCE MODE ACTIVATED

86601 JMS COMPONENT NOT WORKING

9255 ALARM DATABASE UPLOAD FAILURE

30903 NE3S SNMP PM POLLING FAILED

9228 ALARM DATABASE UPLOAD IN PROGRESS

30902 CONNECTION FAILURE - ERROR CONNECTING TO FTP SERVER IN


GET

30900 ONE OR MORE TRAP(S) LOST

9069 ALARM BRIDGE CLIENT FAILURE IN OSS WS

9252 ELEMENT AND SUBTREE IN MAINTENANCE MODE

9047 ALARMS FROM NETWORK ELEMENTS INTEGRATED TO AGENT NOT


ARRIVING

30901 ERROR RECEIVED FROM SNMP ENABLED DEVICE IN GET

9256 ACK DATABASE UPLOAD FAILURE

86606 MULTIPLE AGENTS HAVE SAME MAINHOST

86609 AC IS OVERLOADED

9451 SNMP AGENT NOT RESPONDING

9229 ACK UPLOAD IN PROGRESS

86600 PIPE N IS SLOW OR NOT WORKING N=0,1,2,.......

OS90515EN15GLA0
Copyright ©2015 Nokia.Solutions and Networks.
26
System Self Monitoring and Administration Tasks

Administering Self-Monitoring
Self-Monitoring related Alarms

1. Select Alarms tab

2. Select Adaptation for


Self Monitoring
3. Select Release

4. The list of Alarms


Click on ID for more is displayed
details

1 © Nokia Solutions and Networks 2014

Fig. 10

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . .
OS90515EN15GLA0 . . . . . . . . . . . . . . . . . . . . . . . . .
. . ©2015
Copyright . Nokia
. .Solutions
. . and.Networks.
. . . . . . . . . . . . . . . . . . . . . . . . . . .
27
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Self Monitoring and Administration Tasks

1.4.8 Self Monitoring related Measurements and Counters


1.4.8.1 Measurements
Self monitoring supports the following measurements:

Managed
ID Measurement name Presentation
Objects
NETWORK NETWORK NETWORK NET

FS File System File System FS

AGGREGAT AGGREGATE AGGREGATE BRM

CPU Central Processing Unit Central Processing Unit CPU

1.4.8.2 Counters
ID Presentation Time Object
Aggregation Aggregation
bytesTransmitted bytesTransmitted SUM SUM

packetsTransmitted packetsTransmitted SUM SUM

packetsReceived packetsReceived SUM SUM

bytesReceived bytesReceived SUM SUM

fsUsed fsUsed AVG AVG

sysUptime sysUptime SUM SUM

sysAvailability sysAvailability SUM SUM

memUsed memUsed AVG AVG

memFree memFree AVG AVG

swapUsed swapUsed AVG AVG

swapFree swapFree AVG AVG

cpuAverageLoad cpuAverageLoad AVG AVG

cpuPeakLoad cpuPeakLoad MAX MAX

cpuPercentageOverValue cpuPercentageOverValue AVG AVG

cpuLoad CPU Load AVG AVG

cpuUsed CPU Used AVG AVG

OS90515EN15GLA0
Copyright ©2015 Nokia.Solutions and Networks.
28
System Self Monitoring and Administration Tasks

Administering Self-Monitoring
Self-Monitoring related Measurements

1. Select
Measurements tab

2. Select PM Adaptation
3. Select Release for Self Monitoring

Click on ID for more 4. The list of


details measurements
is displayed

1 © Nokia Solutions and Networks 2014

Fig. 11

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . .
OS90515EN15GLA0 . . . . . . . . . . . . . . . . . . . . . . . . .
. . ©2015
Copyright . Nokia
. .Solutions
. . and.Networks.
. . . . . . . . . . . . . . . . . . . . . . . . . . .
29
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Self Monitoring and Administration Tasks

Administering Self-Monitoring
Self-Monitoring related Counters

1. Select the Counters tab

2. Select PM Adaptation
for Self Monitoring
3. Select Release

4. The List of counters


Click on ID for is displayed.
details

1 © Nokia Solutions and Networks 2014

Fig. 12

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .OS90515EN15GLA0
. . .
Copyright ©2015 Nokia.Solutions and Networks.
30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Self Monitoring and Administration Tasks

2 Administration Tasks

OS90515EN15GLA0
Copyright ©2015 Nokia Solutions and Networks.
31
System Self Monitoring and Administration Tasks

2.1 Revising the Status of the NetAct High Availability


Services
The smanager.pl command informs the administrators, at a glance, of the status of a service in
NetAct.
To execute the command, do the following:
1. Log in to any virtual machine (VM) that is not the vCenter VM, and then switch to the root
user.
2. View the status of all services by entering: smanager.pl status
3. View the status of a specific service by entering smanager.pl <name_of_service>

Refer to the table below for a possible status of a service and what the status means.

Status Description

Starting The service is currently starting

Started The service is running and being monitored


by the Service Monitoring application
Stopping The service is stopping

Stopped The service was stopped by an smanager


command or was manually stopped
Recovering The service has failed to recover, and the
Service Monitoring application is trying to start the
service
Failed The service has stopped, and recovery efforts
has failed
Maintenance The service is not monitored by the Service
Monitoring application
No connection The smanager application cannot establish a
connection with the service
Frozen
The service is under maintenance mode

Config Error
The specified service control script does not exist.

Locked The service is disabled

The outcome displays a list of the active service names and virtual machines.

OS90515EN15GLA0
Copyright ©2015 Nokia.Solutions and Networks.
32
System Self Monitoring and Administration Tasks

OS90515EN15GLA0
Copyright ©2015 Nokia Solutions and Networks.
33
System Self Monitoring and Administration Tasks

2.2 Preventive Health Check


Preventive Health Check (PHC) is a command-line tool that is used to check the current state of
the NetAct system through the summary report it generates and the logs that it collects. The tool
can give the system administrator helpful insights about the system, especially when
troubleshooting so that it is best to execute it in the following scenarios:
• after every NetAct deployment
• when there are failures within NetAct
• when there is a need to monitor the NetAct system at regular intervals
The tool is modular and covers test cases for both RHEL and NetAct. The RHEL module test
cases perform the operating system and hardware-related tests. NetAct test cases are grouped
into the following sub-modules:
• Configuration management
• Fault management
• High availability
• NetAct system information
• Performance management
• WebSphere Application Server
System Administrator can run the tool from one VM using the mhcf user, which is automatically
created with the installation, and as a result, get the status of all the VMs. Every tool execution
creates a new folder that contains the summary of all the findings. The reports generated are
available in .html, .log, and .xml file formats. All logs collected are saved in a .tar file.
With the test the following information is obtained:
• Summary report on the state of the system.
• Collect symptoms to resolve the problems.
• Check the health of the system after NetAct deployment (after fresh installation or
upgrade).
• Verify all nodes using central remote execution utility.
• Generate consolidated summary report and collect logs from all the nodes on the node
where the tool is invoked.

OS90515EN15GLA0
Copyright ©2015 Nokia.Solutions and Networks.
34
System Self Monitoring and Administration Tasks

2.2.1 Preventive Health Check Contents


Preventive Health Check is part of NetAct 15 media. After installation, it is available on all cluster
nodes and can be invoked from any node using the mhcf user.
Note:
During installation, mhcf user belonging to mhcf group is created.
After installation, NSN-mhcf subdirectory is created in /opt/oss/ directory. For example,
/opt/oss/NSN-mhcf.
The Directory folders figure below shows the contents of the Preventive Health Check installation
directory.

Preventive Health Check installation directory consists of the following:


Data
Contains configuration files required to execute the Preventive Health Check as a complete test
suite. It also contains subfolders with configuration files specific to respective modules or sub-
modules. Each folder and its subfolder contain test scripts (Perl) required to execute the test
cases
lib
Contains Perl and Shell libraries used in Preventive Health Check.
logs
Contains the log folder generated when the Preventive Health Check is invoked. A log folder with
current timestamp is created when the Preventive Health Check is executed. This serves as the
output directory containing the summary reports and the logs collected.
tmp
Contains temporary data files that are created at runtime and deleted after the tool execution.

OS90515EN15GLA0
Copyright ©2015 Nokia Solutions and Networks.
35
System Self Monitoring and Administration Tasks

tools
Contains scripts such as Shell, SQL, and Perl that are used as tools in test scripts.
xslt
Contains files that transforms the generic XML into HTML format.
asws_root_privileges.pl
Script enables the mhcf user to run the programs with the security privileges of root user.
mhcf.pl
Script that executes Preventive Health Check.

2.2.2 Running Preventive Health Check


Preventive Health Check is installed on all cluster nodes. Therefore, you can run the health check
from any node.
To run Preventive Health Check:
1. Log in as mhcf user to the node where you want to run the health check.
2. Change the directory to /opt/oss/NSN-mhcf:
3. Start Preventive Health Check by executing:
./mhcf.pl –c <configuration file> -loglevel <value>
where:
• mhcf.pl- tool executable
• <configuration file> - configuration file for the complete testsuite
• <value> - value of the log level

OS90515EN15GLA0
Copyright ©2015 Nokia.Solutions and Networks.
36
System Self Monitoring and Administration Tasks

Note:
If Password Policy is enforced in the system; contact your system administrator to check the
latest password for mhcf user.
Password expiry duration is as per password policy, that is 180 days by default. If mhcf
password is expired on any node, the test cases executed on that node fails as Preventive Health
Check tool cannot make SSH connection to that node. In such cases the following error message
is displayed on the screen and in the output files. For example,

You must manually change the password on all nodes of the system. The user security hardening
measures mentioned in the Administering NetAct System Security document is also applicable
for mhcf user

Expected outcome
The command output is either passed or failed. A log folder is created in /opt/oss/NSN-
mhcf/logs directory.

Note:
The log folders older than 5 days in the /opt/oss/NSN-mhcf/logs directory are
cleaned up on execution of the tool. If the tool is not executed for more than 6 days, then the log
folders which are older than 5 days are not cleaned.

Minimum logs or basic symptoms for quick analysis of the problem are collected on every
execution of the tool with loglevel = 4 regardless of a test case pass or fail. If test case
fails, Preventive Health Check can be executed with loglevel = 2 and
filter=module name or testSet=testset name.

OS90515EN15GLA0
Copyright ©2015 Nokia Solutions and Networks.
37
System Self Monitoring and Administration Tasks

2.2.3 Health Check Parameters


1. To view the list of supported commands of the Preventive Health Check, execute:
./mhcf.pl –h

2. To run specific configuration file that contains the test case, execute:
./mhcf.pl -c /opt/oss/NSN-mhcf/product/netact8/cfg_netact8.xml

3. To run specific test set, execute:


./mhcf.pl -c /opt/oss/NSN-mhcf/product/netact8/cfg_netact8.xml-t
/opt/oss/NSN-mhcf/product/netact8/subcfg_netAct8.xml

Note:
subcfg_netAct8.xml is a sample test set configuration, which you can refer to create
customized test set configuration for different requirements.

4. To run test case based on filterTags=cm specified in the test case, execute:
./mhcf.pl -c /opt/oss/NSN-mhcf/product/netact8/cfg_netact8.xml
-f cm -loglevel 4

Note:
filterTags can be cm, rhel, nas_common, fm, ha, was, pm. You can
provide multiple filterTags as follows:
./mhcf.pl -c /opt/oss/NSN-mhcf/product/netact8/cfg_netact8.xml
–f cm,rhel,nas_common,fm,ha,was,pm -loglevel 4

5. To list all the available test cases, execute:


./mhcf.pl -c /opt/oss/NSN-mhcf/product/netact8/cfg_netact8.xml–
list

6. To run the health check in interactive mode, execute:


./mhcf.pl -c /opt/oss/NSN-mhcf/product/netact8/cfg_netact8.xml-i
-loglevel 4

7. To run specific test case assigned to specific role, such as db, execute:
./mhcf.pl -c /opt/oss/NSN-mhcf/product/netact8/cfg_netact8.xml
-r db -loglevel 4

Note:
Role can be dmgr, fm_pipe and was. Multiple role values can be provided in the same
command as follows:
./mhcf.pl -c /opt/oss/NSN-mhcf/product/netact8/cfg_netact8.xml-r
db,dmgr,fm_pipe,was - loglevel 4

OS90515EN15GLA0
Copyright ©2015 Nokia.Solutions and Networks.
38
System Self Monitoring and Administration Tasks

8. To suppress the output, execute:


./mhcf.pl -c /opt/oss/NSN-mhcf/product/netact8/cfg_netact8.xml-q
-loglevel 4

9. To run specific test case based on the test case number, execute:
./mhcf.pl -c /opt/oss/NSN-mhcf/product/netact8/cfg_netact8.xml-
single 1.2 -loglevel 4

where 1.2 is the test case number.

Note:
To view test case number, execute the command with -list option
10. To collect logs, execute:
./mhcf.pl -c /opt/oss/NSN-mhcf/product/netact8/cfg_netact8.xml-
loglevel 4

2.2.4 Log Directory Structure


The log directory contains the summary report and logs of Preventive Health Check.
The summary report lists the test cases executed on each cluster node and provides a summary
of the test results. The summary contains the description of each test and result of the test
execution. If any test case fails, the reason for the failure and suggested action are described.
Preventive Health Check logs collected are stored in .tar file. Summary report is available in
the following formats:
log - Summary report in text format is same as the console output . Open the file to view the
report on a console.
html - Summary report in .html format enables to view the report in a browser.
xml - Summary report in .xml format is ASWS compatible for integration to care tools.

Contents of logs directory is shown below.

Example of a summary report:

OS90515EN15GLA0
Copyright ©2015 Nokia Solutions and Networks.
39
System Self Monitoring and Administration Tasks

OS90515EN15GLA0
Copyright ©2015 Nokia.Solutions and Networks.
40
System Self Monitoring and Administration Tasks

2.2.5 Test cases


Preventive Health Check can be executed by using the following test cases:
• RHEL test cases check the operating system and hardware.
• NetAct test case check configuration management, fault management, high availability, NetAct
system information, performance management, and, WebSphere application server.

2.2.5.1 RHEL Module


The following table lists the RHEL test cases

Test case Test case description

HW check Checks the hardware specification such as processor


architecture, processor type and speed, processor count,
RAM size, and hard disk drive size

RHEL message Log Check Checks for error messages (in messages.log file) in the
/var/log directory. Test fails if errors are found

RHEL secure Log Check Checks for error messages (in secure log file) in the
/var/log directory. Test fails if errors are found

Node Performance Check – Checks that the load on the CPU (application and operating
System Load Check system) is less than 80%. Test fails if it exceeds 80%. You
can check the current CPU load in the log file

Duplicate IP Check Checks that the system IP is used in another machine in the
network and reports the MAC address of the same. Test fails
if the test case finds same IP

NTP Synch Check Checks that the system time is in synchronization with NTP
Server. Test fails if the test case finds any system not in
synchronization with NTP server

OS90515EN15GLA0
Copyright ©2015 Nokia Solutions and Networks.
41
System Self Monitoring and Administration Tasks

2.2.5.2 NetAct Module


NetAct module is categorized into:
 Configuration management
 Fault management
 High Availability
 NetAct system information
 Performance management
 • WebSphere application server

Note:
Check the filterTag in the test case for the module name. The filterTag can be cm,
rhel, nas_common, fm, ha, was, pm. You can execute the modules separately by
providing the module name as filter in the command.

Configuration Management
Test case title Test case Description

CM Import File Count Checks that the number of files in CM Import


folders is less than 10000 threshold. Test fails if
number of files exceeds the threshold. Check
south import directory to view the current number
of files.

OS90515EN15GLA0
Copyright ©2015 Nokia.Solutions and Networks.
42
System Self Monitoring and Administration Tasks

Fault Management

Test case title Test case Description


Checks that the average alarm insertion time is less
than the threshold of 120 seconds for each alarm in the
database. Test fails if insertion time is greater than the
FM Alarm Threshold
threshold.
Checks that:
• the FX alarm table buffer hit ratio is greater than 98
DB Buffer checks and FM alarm • the active alarm count is less than 100000 threshold.
checks Test fails if one of the condition is not met

Checks that the GEP instance of servicemix is running.


GEP Status
Test fails if GEP instance of servicemix is not running.

Checks that the trap delivery is working. This is done by


checking if mediation is listening to the traps and traps
are auto forwarded.
Test fails if any of these checks fail because the OFaS
FM Trap Delivery Check files are not written to the import directory

Logs the Used Memory, Committed Memory, and Max


Memory.
If Preventive Health Check is unable to retrieve these
GEP Process Memory Check
data, the test fails.
Checks that the number of files in FM Import folders is
FM Import File Count less than 10000 threshold. Test fails if file count
exceeds the threshold and the current number of files is
recorded in the south FM import directory

NetAct System Information


Test case title Test case Description

NetAct Base Info Lists system information such as RHEL version, Java
version, Oracle version, ClusterID, ClusterName, and
Domain name.
Test fails if it is not able to fetch the required information

DB Size Check Checks that the DB usage is below 80% threshold. Test
fails if usage exceeds threshold

Default System users Check Checks that the number of default system users is equal
to 6.
Test fails if it is not equal to 6

OS90515EN15GLA0
Copyright ©2015 Nokia Solutions and Networks.
43
System Self Monitoring and Administration Tasks

High Availability
Test case title Test case Description

NFS service check Checks that nfs is running. Test fails if it is not running

Net FS service check Checks that netfs-<node name> is running. Test fails if it is
not running
OMAgent AF service check Checks that OMAgentAF-<node name> is running. Test fails
if it is not running
Dirsrv service check Checks that dirsrv is running. Test fails if it is not running

tomcat_vcentplg service check Checks that netfs-<node name> is running. Test fails if it is
not running
db service check Checks that db is running. Test fails if it is not running.

Pulse-jbi service check Checks that pulse-jbi is running. Test fails if it is not
running

Pulse-j2ee service check Checks that pulse-j2ee is running. Test fails if it is not
running.

OM Agent service check Checks that OMAgent is running. Test fails if it is not running

hpsim service check Checks that hpsim is running. Test fails if it is not running

pingServer service check Checks that pingServer-<node name> is running. Test


fails if it is not running
tnameserver service check Checks that tnameserver-<node name> is running. Test
fails if it is not running
Nbi3gc service check Checks that nbi3gc is running. Test fails if it is not running

Rac3gp service check Checks that rac3gp is running. Test fails if it is not running

ftp service check Checks that ftp-<node name> is running. Test fails if it is
not running
Nwi3 service check Checks that nwi3 is running. Test fails if it is not running

Nwi3-http service check Checks that nwi3-http is running. Test fails if it is not
running

jacorb service check Checks that jacorb is running. Test fails if it is not running

osi service check Checks that osi is running. Test fails if it is not running.

Q3user service check Checks that q3user is running. Test fails if it is not
running

socks service check Checks that socks is running. Test fails if it is not
running

fmascii service check Checks that fmascii is running. Test fails if it is not
running

OS90515EN15GLA0
Copyright ©2015 Nokia.Solutions and Networks.
44
System Self Monitoring and Administration Tasks

High Availability (Cont.)


Test case title Test case Description

nbisnmp service check Checks that nbisnmp is running. Test fails if it is not
running

Nbi3gcpm service check Checks that nbi3gcpm is running. Test fails if it is not
running

Common_mediations service Checks that common_mediations-<node name> is running.


Test fails if it is not running
check

httpd service check Checks that httpd is running. Test fails if it is not running

FM_pipe service check Checks that fm_pipe-<node name> is running. Test fails if it is
not running
dmgr service check Checks that dmgr is running. Test fails if it is not running.

was service check Checks that was-<node name> is running. Test fails if it is not
running.
ihs service check Checks that ihs-<node name> is running. Test fails if it is not
running.

Performance Management
Test case title Test case Description

Check that the number of files in:


• SMI folder is less than the threshold of 20000.
PM files in import folder • error folder is equal to 0.
The test case fails if any of these checks fails. The current
number of files in each check is recorded in the log file

Checks that the number of files in North PM export directory is


PM files in export folder less than 10000 threshold. Test fails if it exceeds the threshold.
The current number of files in this directory is recorded in the log
file.

OS90515EN15GLA0
Copyright ©2015 Nokia Solutions and Networks.
45
System Self Monitoring and Administration Tasks

WebSphere Application Server


Test Case Title Test Case Description

Websphere status : nodeagent Checks that the Node Agent process is running. Test fails if
the process is not running
Websphere status : cluster Checks that the JMSCluster and SOLCluster processes are
running. Test fails if the either of these process is not running
Websphere status : listener Checks that the Websphere listener process is running. Test
fails if the process is not running
Websphere status : Checks that the WAS JDBC is connected to the database.
Test fails if the WAS JDBC is not connected
jdbc_connection

Temporary directory disk Checks that the free space is 1048576 bytes in the /tmp
directory of the node where was services are running. Test
space Check
fails if free disk space is less than the threshold
NTP Sync Check Checks that the nodes are synchronized with NTP server.
Test fails if it is not synchronized
Jetty Webserver Test Checks that the Jetty webserver is running. Test fails if it is
not running
WAS Heap Dump Checks Checks that there are any heap dumps in NetAct
applications, WAS phd, and WAS javacore. Test fails if heap
dump exists

OS90515EN15GLA0
Copyright ©2015 Nokia.Solutions and Networks.
46
System Self Monitoring and Administration Tasks

2.3 Log Monitor Tool


As there are many virtual machines representing a single NetAct cluster, it is difficult to check logs
on each of these virtual machines and troubleshoot the problems in NetAct system.
Log Monitor tool provides a real-time view of logs of all virtual machines. It is installed on the
virtual machine where Self Monitoring is running.
Log Monitor tool is not enabled by default after installation. You can enable or disable Log Monitor
tool at runtime, and also verify the status of Log Monitor tool.
When log monitor is enabled, logs are mounted from all virtual machines, and log monitor creates
the following directories:

Mount Location on Self Monitoring Virtual


Logs Location on Server
Machine

Application /var/opt/oss/log /var/opt/oss/logc/<nodeName>/osslogdir


Logs

WebSphere /opt/WebSphere/AppServer/profiles/ /var/opt/oss/logc/<nodeName>/dmgr


Logs dmgr/logs

/opt/WebSphere/AppServer/profiles/ /var/opt/oss/logc/<nodeName>/applicationserver
<nodename>/logs

/opt/IBMHttpServer/logs /var/opt/oss/logc/<nodeName>/httpserver

Deployment /oss/global/var/mediation/south/met /var/opt/oss/logc/<nodeName>deployment


Logs a/import

NetAct PM /var/opt/nokia/oss/local/common/log /var/opt/oss/logc/<nodename>/onepm_commonlog


logs

/var/opt/nokia/oss/local/common/var /var/opt/oss/logc/<nodeName>onepm_trace
/tmp/trace

OS90515EN15GLA0
Copyright ©2015 Nokia Solutions and Networks.
47
System Self Monitoring and Administration Tasks

2.3.1 Monitoring log files


A log directory specific to Log Monitor tool is created during installation. However, log folders
specific to virtual machine are created when the tool is invoked.
When enabled, the script collects logs at run time.
Perform the following steps to enable collecting the logs from the virtual machines:
1. Log in to vcenterselfmon virtual machine as omc user.
2. To view log directories of:
a) NetAct nodes excluding all Performance Manager virtual machines, execute:

./logmonitorconsole.sh -enable

Or
b) NetAct and NetAct Performance Manager VMs except VMs running was_linas services,
execute:

./logmonitorconsole.sh -enableWithPM

This invokes the tool and collects the logs from the virtual machines. The logs collected are stored
at /var/opt/oss/logc directory.

Note:
Log directories can be viewed only as omc user.

6. To stop collecting logs of:


a) only NetAct nodes excluding all Performance Manager virtual machines, execute:
./logmonitorconsole.sh -disable
Or
b) NetAct and NetAct Performance Manager VMs except VMs running was_linas services,
execute:
./logmonitorconsole.sh -disableWithPM
If omc password for NetAct Performance Manager VMs is different from omc password
from other VM's, you are requested to enter the correct omc password.
The tool stops collecting logs from the virtual machines.

OS90515EN15GLA0
Copyright ©2015 Nokia.Solutions and Networks.
48
System Self Monitoring and Administration Tasks

7. To check the connection status of:


a) NetAct nodes excluding all Performance Manager virtual machines,, execute:
./logmonitorconsole.sh -status
Or
b) NetAct and NetAct Performance Manager VMs except VMs running was_linas services,
execute:
./logmonitorconsole.sh -statusWithPM
If omc password for NetAct Performance Manager VMs is different from omc password
from other VM's, you are requested to enter the correct omc password.
The status indicates if log monitor tool is enabled or disabled on each virtual machine.
Note:
When a particular node is down, the script stops without any warning message. Logs are
not available for such nodes. Execute the log monitor script again when the node is up.

2.3.2 Logs for Log Monitor Tool


When the tool is invoked, the following log files are generated:
 activity log file: /var/opt/oss/log/lmc/lmc_activity.log
 error log file: /var/opt/oss/log/lmc/lmc_error.log
These log files contains detail logs generated by script. Debug the errors related to Log Monitor
tool using these log files.

OS90515EN15GLA0
Copyright ©2015 Nokia Solutions and Networks.
49
System Self Monitoring and Administration Tasks

2.4 Preparing NetAct for Hardware Maintenance


Hardware maintenance is required when there are problems with the hardware. System
Administrator may need to replace memory, CPU, or a hard disk. To be able to do this without
interrupting the NetAct services, it is required to evacuate VMs from one server (ESXi host) to
another. Evacuating VMs takes place automatically when setting the host in Maintenance Mode:
1. Access the vSphere Web client as root user.
2. From the vCenter home, locate the right server (ESXi host) that you want to put into
hardware maintenance.
3. Right-click the server and select Enter Maintenance Mode.
VMs are moved automatically to other servers that have resources to run these VMs.
4. From the Confirm Maintenance Mode dialog, make sure the “Move powered-off and
suspended virtual machines to other hosts in the cluster” checkbox is selected, and then click
Yes.
5. From the Recent Tasks pane, check that the Enter maintenance mode task is completed at
100%. Otherwise, make sure the preceding tasks are completed before preparing the server
for hardware maintenance.

OS90515EN15GLA0
Copyright ©2015 Nokia.Solutions and Networks.
50
System Self Monitoring and Administration Tasks

2.5 Restoring a Host from Hardware Maintenance


1. Access the vSphere Web client as root user.
2. From the vCenter home, navigate to the host you want to restore from maintenance mode.
3. Right-click the host, and then select Exit maintenance mode.
4. From the Recent Tasks pane, check that the Exit maintenance mode is completed at 100%.

2.6 Shutting down a Host


Perform the following procedure on all ESXi hosts in the system.
1. Access the vSphere Web client as root user.
2. From the left pane, navigate to the host that you want to shut down.
3. Right-click the host, and then select Enter Maintenance Mode.
4. Click Yes, and wait for the task to finish.
VMs are moved automatically to other servers that have resources to run these VMs.
5. Right-click the host, and then select Shut Down.
6. On the confirmation dialog, enter a reason for shutting down the host, and then click OK.

2.7 Live Migrating Virtual Machines Manually


When detecting performance shortages, the Distributed Resource Scheduler (DRS) automatically
migrates VMs from one server to another in the hardware resource pool. If there is still a need to
live-migrate VMs for performance reasons, you can do it manually as follows:
1. Access the vSphere Web client as root user.
2. From the vCenter home, navigate to the VM you want to move.
3. Right-click the VM and select Migrate.
4. Follow the prompts on the computer screen.
5. When you have finished selecting your options for the migration of the VM, click Finished.
Expected outcome
The Recent Tasks pane confirms that the live-migration of the VM is successful

OS90515EN15GLA0
Copyright ©2015 Nokia Solutions and Networks.
51
System Self Monitoring and Administration Tasks

2.8 Monitoring the Virtual Infrastructure


You can monitor alarms, measurements, CPU memory usage, and storage / disk space.
1. Access the vSphere Web client as root user.
2. From the vCenter home, navigate to and select the component whose status you want to
monitor. The component may be the ESXi host, Resource Pool, Datastore, or a particular
virtual machine.
3. Click the Monitor tab.
Expected outcome
Depending on the component you selected, the Monitor tab may display the current Issues,
Performance, Resource Allocation, Storage Reports, Tasks, and Events of the component

2.9 Recommended system shutdown and startup order


When there is a need to shut down the NetAct environment, this is the recommended shutdown
order for the system:
1. NetAct applications and services
2. Virtual machines (VM), except the vCenter virtual machine
3. ESXi hosts, except the host where the vCenter VM resides
4. the ESXi host where the vCenter VM resides
5. The vCenter VM saves its existing state when its host is powered off.
6. Blade Center and servers
7. Storage system and Storage Area Network equipment
8. Network equipment
Note:
The need to shut down the servers and network equipment is less frequent than a NetAct system
startup and shutdown. An example would be during a planned complete loss of power. Shut down
and then start up the hardware components only when necessary.

OS90515EN15GLA0
Copyright ©2015 Nokia.Solutions and Networks.
52
System Self Monitoring and Administration Tasks

Administration Tasks
Recommended shut-down order of the hardware components and NetAct

1 © Nokia Solutions and Networks 2014

Fig. 13

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . .
OS90515EN15GLA0 . . . . . . . . . . . . . . . . . . . . . . . . .
. . ©2015
Copyright . Nokia
. .Solutions
. . and.Networks.
. . . . . . . . . . . . . . . . . . . . . . . . . . .
53
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Self Monitoring and Administration Tasks

When there is a need to start up the NetAct environment, the recommended startup order is the
exact reverse of the shutdown order.
1. Network equipment
2. Storage system and Storage Area Network equipment
3. Blade Center and servers
4. ESXi host where the vCenter VM resides
5. The vCenter VM automatically starts up when its host is powered on.
6. the rest of the ESXi hosts
7. the rest of the virtual machines
8. The NetAct applications and services assigned to each VM automatically starts up when
its VM is powered on.

OS90515EN15GLA0
Copyright ©2015 Nokia.Solutions and Networks.
54
System Self Monitoring and Administration Tasks

Administration Tasks
Recommended start-up order of the hardware components and NetAct

1 © Nokia Solutions and Networks 2014

Fig. 14

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . .
OS90515EN15GLA0 . . . . . . . . . . . . . . . . . . . . . . . . .
. . ©2015
Copyright . Nokia
. .Solutions
. . and.Networks.
. . . . . . . . . . . . . . . . . . . . . . . . . . .
55
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Self Monitoring and Administration Tasks

2.10 Shutting down NetAct


When there is a need to shut down the NetAct environment, shut down the applications and
services first. This is the recommended shutdown order of NetAct:
 Check the status of the services.
 Shut down the NetAct services.
 Shut down the NetAct virtual machines.
 Shut down the ESXi hosts.
 Shut down the vCenter host.

2.10.1 Checking the status of the services


1. Log in to any NetAct virtual machine (VM), and switch to the root user.
2. To check the status of the virtual machines and services, enter:
[root]# smanager.pl status

2.10.2 Shutting down the NetAct applications and services


1. Log in to a virtual machine (VM) hosting the dirsrv service, and switch to the root user.
2. To stop the vManager service so that it does not handle VM reset operations, enter:
[root]# /opt/cpf/install/bin/cpfvmanager_configure.sh --disable_vcenter--
disable_alarms –-stop
3. To stop the services, enter the following command:
[root]# smanager.pl stop NetAct

Note:
When the VMs are restarted later, the services also restart automatically. As an alternative, you
can also restart the services manually.
Some services may be unstoppable. This is expected, if the service name appears with a (u)
upon checking its status.
4. If you plan to manually restart the services later, enter:
[root]# smanager.pl maintenance all on

OS90515EN15GLA0
Copyright ©2015 Nokia.Solutions and Networks.
56
System Self Monitoring and Administration Tasks

2.10.3 Shutting down the virtual machines


Perform the following procedure on all VMs in the system, except on the vCenter VM.
1. Access the vSphere Web client
2. From the vCenter home page, click vCenter → VMs and Templates.
3. Select your vCenter server, and click the Related Objects tab.
4. Select the Virtual Machines tab.
5. Right-click a VM that is not the vCenter VM, and then select Shut Down Guest OS.
6. To confirm the shut down, click Yes.
7. Repeat steps 4 through 5 for all other VMs, except the vCenter VM.

2.10.4 Shutting down the ESXi hosts


Perform the following procedure on all ESXi hosts in the system, except on the host where the
vCenter VM resides.
1. From the vCenter Web client, click the Hosts tab.
2. Right-click the host that you want to shut down, and then select Enter Maintenance Mode.
3. From the Confirm Maintenance Mode dialog, deselect the “Move powered-off and
suspended virtual machines to other hosts in the cluster” checkbox, and then clickYes.
4. Right-click the host that you entered into maintenance mode, and then select Shut Down.
5. On the confirmation dialog, enter a reason for shutting down the host, and then click OK.
6. From the Recent Tasks pane, check that the task is completed.
7. Repeat steps 2 through 6 for all other remaining hosts, except on the host where the
vCenter VM resides.
8. Refresh the site to check that the host is properly shut down and that state is saved on the
vCenter.
Warning:
Make sure all hosts are completely shut down or are no longer responding before shutting
down the host where the vCenter VM is located. vCenter saves the state of these hosts to
avoid conflicts when the system is restarted.
If you want to locate the host where the vCenter resides, navigate to the vCenter VM, and
then click the Summary tab. The Host: field shows where the vCenter VM is located.

OS90515EN15GLA0
Copyright ©2015 Nokia Solutions and Networks.
57
System Self Monitoring and Administration Tasks

2.10.5 Shutting down the vCenter host


Shutting down the ESXi host where the vCenter virtual machine (VM) is located will also
automatically shut down the vCenter virtual machine. Make sure to shut down this host last.
1. Right-click the host where the vCenter VM is residing, and then select Shut Down.
2. On the confirmation dialog, enter a reason for shutting down the host, and then click OK.
3. Refresh the site to check that the host is properly shut down.
When the host where the vCenter resides is completely shut down or is no longer
responding, connection to the vSphere Web client is terminated.

2.11 Starting up NetAct


2.11.1 Starting up the vCenter host
Use the HP Integrated Lights-Out (ILO) to start up the host where the vCenter is located.
1. Log in to HP ILO site of the host where the vCenter is located.
2. Internet Explorer is recomended when logging in to the HP ILO site.
3. To turn the host on, click Power Management → Server Power.
4. From the Virtual Power Button section, click Momentary Press → OK.
The ON indicator in the Server Power field turns green. Clicking Momentary Press on ILO is
similar to pressing the power button on your server causing the operating system to start
up.
5. To check the status of the host, click Remote Console → Remote Console.
6. From the Integrated Remote Console section, click Launch → Run.
A console appears, showing the host powering up.
Note:
Starting up the ESXi host where the vCenter virtual machine (VM) resides automatically
starts up the vCenter VM. This process may take several minutes to complete. It also starts
up the other NetAct services assigned to this host.

OS90515EN15GLA0
Copyright ©2015 Nokia.Solutions and Networks.
58
System Self Monitoring and Administration Tasks

2.11.2 Starting up the ESXi hosts


Use the HP Integrated Lights-Out (ILO) to start up the remaining hosts in the NetAct system.
1. Log in to the HP ILO site of the host.
2. To power on the host, click Power Management → Server Power.
3. From the Virtual Power Button section, click Momentary Press → OK.
The ON indicator in the Server Power field turns green. Clicking Momentary Press on ILO
is similar to pressing the power button on your server causing the operating system to start
up.
4. To check the status of the host, click Remote Console → Remote Console.
5. From the Integrated Remote Console section, click Launch → Run.
A console appears, showing the host powering up.
6. Repeat steps 1 through 5 for all other remaining hosts.
7. Access the vSphere Web client.
8. From the vCenter home page, click vCenter → VMs and Templates.
9. Select your vCenter server, and click the Related Objects tab.
10. Select the Hosts tab.
11. Right-click a host, and then select Exit Maintenance Mode to restore the host from
maintenance mode.
12. Repeat steps 7 through 11 for all other remaining hosts.

2.11.3 Starting up the virtual machines


Starting up the virtual machines (VM) automatically starts up the NetAct applications and services
assigned to each VM. Start up the VMs based on their assigned services. This is the
recommended start up order:
1. Directory service
2. NFS service
3. Database service
4. All other services except the load balancers
5. The load balancers

OS90515EN15GLA0
Copyright ©2015 Nokia Solutions and Networks.
59
System Self Monitoring and Administration Tasks

2.11.4 Starting up a virtual machine and NetAct service


1. Click the Virtual Machines tab.
2. Right-click a VM, and then select Power On.
Starting up the VMs automatically starts up the NetAct applications and services assigned
to these virtual machines.
3. Repeat steps 1 through 2 for all other remaining VMs.
4. Log in to a VM hosting the dirsrv service, and switch to theroot user.
5. To start the vManager service, enter the following command:
[root]# /opt/cpf/install/bin/cpfvmanager_configure.sh --enable_vcenter --
enable_alarms --start

2.11.5 Restarting NetAct manually


Before performing this task, ensure that you have performed step 4 in Shutting down the NetAct
applications and services.
1. Log in to a NetAct VM, and switch to the root user.
2. To restore the services from maintenance mode, enter the following command:
[root]# smanager.pl maintenance all off
3. To start NetAct, enter:
[root]# smanager.pl start netact
4. To manually start a service, enter:
[root]# smanager.pl start service <service_name>

2.12 Shutting down and starting up the hardware


In some cases, there may be a need to shut down the hardware components. The need to shut
down the hardware is less frequent than a NetAct system startup and shutdown. An example
would be during a planned complete loss of power. Shut down and then start up the hardware
components only when necessary.
Shut down and start up procedures for every hardware component may vary. For more
information, please see the hardware documentation of your respective server or network
equipment.

OS90515EN15GLA0
Copyright ©2015 Nokia.Solutions and Networks.
60
System Self Monitoring and Administration Tasks

3 Exercises

OS90515EN15GLA0
Copyright ©2015 Nokia Solutions and Networks.
61
System Self Monitoring and Administration Tasks

OS90515EN15GLA0
Copyright ©2015 Nokia.Solutions and Networks.
62
System Self Monitoring and Administration Tasks

Exercise 1
Title: NetAct Self - Monitoring

Objectives: Explain the purpose of the Self - Monitoring functionality.


Describe the functionality of O&M Agent.
Describe the functionality of HP SIM

Pre-requisite: none

Task
Please answer the following questions
Query
1. What is the purpose of the NetAct Self Monitoring Functionality?
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________

2. What is the function of O&M Agent in the Self Monitoring Functionality? What is the
difference between the functionality of the O&M Agent and the function of the HP Integrated
Monitor?
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________

3. Which application is used to view the Alarms generated by the Self Monitoring functionality?
__________________________________________________________________________
__________________________________________________________________________

4. Which component in O&M Agent monitors NetAct software?


__________________________________________________________________________
__________________________________________________________________________

OS90515EN15GLA0
Copyright ©2015 Nokia Solutions and Networks.
63
System Self Monitoring and Administration Tasks

Connect to a NetAct 15 environment


5. Which adaptation must be deployed for Self Monitoring to generate FM data? Is it deployed
correctly? Do we have an adaptation for PM data?
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________

6. What is the name of the O&M Agent service that is deployed in the virtual environment? Is
the service running?
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________

7. What is the name of the HP SIM service? Is it Highly Available?


__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________

8. What are the categories of HP SIM alarms?


__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________

OS90515EN15GLA0
Copyright ©2015 Nokia.Solutions and Networks.
64
System Self Monitoring and Administration Tasks

Exercise 2
Title: Administration Tasks

Objectives: Revise the Status of NetAct Functionality using smanager.pl tool.


Setup Preventive Health Checks
Analyze the Log Outputs from Log Monitor Tools

Pre-requisite: none

Task
Please connect to the NetAct 15 environment with the credentials provided by the trainer and
execute the following tasks.

Query

1. Execute the smanager.pl command. Which of your virtual machines are in a status that can
indicate problems in the system? What are the functions of these virtual machines? (Please
search for the VMs functionality in Operating Documentation).
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________

2. Use the diagnostic tool to evaluate the current status of the test system. What are your
findings about the system? List the test cases you are using and what is applicability of them.
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________

OS90515EN15GLA0
Copyright ©2015 Nokia Solutions and Networks.
65
System Self Monitoring and Administration Tasks

3. Start the Collection of Logs using the Log Monitor Tool. Where can you actually see those
logs? List some of the log files available.
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________

4. Execute the Preventive Health Check in your test system. Check the results. Are there any
problematic areas in the system?
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________

OS90515EN15GLA0
Copyright ©2015 Nokia.Solutions and Networks.
66
System Self Monitoring and Administration Tasks

Exercise 3
Title: Administration Tasks: Virtual Infrastructure

Objectives: Configure Servers for Hardware Maintenance.


Shutdown a Host

Pre-requisite: none

Task
Please connect to the NetAct 15 environment with the credentials provided by the trainer and
execute the following tasks.

Query
1. Prepare one of your ESXi Hosts for Maintenance. Which are the actions needed for this?
What will be the system impact of such operation? Is the system losing some functionality
because the maintenance of one server?
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
____________________________________________________________________

OS90515EN15GLA0
Copyright ©2015 Nokia Solutions and Networks.
67
System Self Monitoring and Administration Tasks

2. What is the life migration of VMs used for? Accordingly to the instructions of your trainer
execute the migration of one of the VMs and verify that functionality of NetAct hasn’t been
affected by this operation.
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
______________________________________________________

3. Visualize the Performance data of the Virtual Infrastructure. What can you tell about the
system performance in your current observations? Is it possible to export this data? Is it
possible to setup new charts for the analysis?
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________

OS90515EN15GLA0
Copyright ©2015 Nokia.Solutions and Networks.
68

Vous aimerez peut-être aussi