01 OS90521EN15GLA0 System Platform

System Platform
System Platform
Contents
1 Virtualized Infrastructure 3
1.1 NetAct VM Configuration Overview 4
1.2 Host (Blade Server) Configuration 6
1.3 VM Node Configuration 8
1.4 Command Line Interface for EXSi Hosts 10
1.5 Virtualization Related Logs 18
2 Software Platform 19
2.1 Software 20
2.2 NetAct Storage 24
2.3 System Platform related Logs 34
3 NetAct Time Management 37
3.1 Introduction 38
3.2 Managing the NTP Service 41
4 Service Manager 47
4.1 Introduction 48
4.2 Service Manager Usage 48
4.3 Service Manager in vCenter Client 52
5 Exercises 57
OS90521EN15GLA0
© Nokia Solutions and Networks 2015
.
1
System Platform
OS90521EN15GLA0
2 © Nokia Solutions and Networks 2015
System Platform
1 Virtualized Infrastructure
OS90521EN15GLA0
.
3
System Platform
1.1 NetAct VM Configuration Overview

Please note that this chapter is an overview of the Virtualized Infrastructure configuration for
NetAct 15. All details for this configuration can be found in the Virtualization and Availability
Chapter of the Admin 1 class. The objective is to provide a brief overview of the VM tools that
can be used for NetAct 15 Administration.
1.1.1 vSphere Client

There are two user interfaces for interacting with the vSphere environment: the vSphere
Client and the vSphere Web Client.
The vSphere Client provides all the tools needed to effectively configure and manage the
virtualized datacenter. The vSphere Client can be used to remotely connect to a VMware
vCenter Server instance or to an ESXi host from a Windows System. It also provides console
access to virtual machines.
The VMware vSphere® Web Client, is browser-based, platform-independent implementation
of the vSphere Client.
vSphere client:
vSphere client can be downloaded from the official VMware pages, for example
https://my.vmware.com/web/vmware/info/slug/datacenter_cloud_infrastructure/vmware_vsph
ere/5_5.
1. Download the vSphere Client to your computer.
2. Install the vSphere client application on your laptop / desktop
3. Invoke the application. In the login dialog, provide the IP address of vCenter and login
credentials for ‘Administrator’ user. This user is setup at the time of vCenter installation
4. Click on the login button
5. The vSphere client application window will be displayed
vSphere web –interface:
1. Open a web browser on your laptop / desktop
2. Enter the URL https://<IP address of vCenter>:9043/vsphere-client/
3. In the login dialog, provide the IP address of vCenter and login credentials for
‘Administrator’ user. This user is setup at the time of vCenter installation
4. Click on the login button
5. VM configuration loads in the browser
OS90521EN15GLA0
System Platform
Virtualized Infrastructure
vSphere vCenter Client and vCenter Web Client
Fig. 1
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OS90521EN15GLA0
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Platform
1.2 Host (Blade Server) Configuration

The physical server blades on which the VMs are created and hosted are called as hosts.
The hosts are the actual physical computer on which ESXi software is installed. All virtual
machines run on hosts. If the vSphere Client is connected directly to an ESXi host, only that
host is available for management.
The Hosts and Clusters inventory view in the vCenter client or vCenter Web Client displays
all host and cluster objects in a datacenter. The hosts are displayed in the left tree under
‘NetAct_cluster’ node. There is only one virtualization cluster in NetAct. When you click on a
host, all information pertaining to it is displayed in the right pane as tabs. For example, when
clicking on the Summary Tab, the configuration of the host is displayed. In the ‘Virtual
Machines’ tab, the list of VMs currently running on the host is displayed, together with their
status and information on resource consumption.
OS90521EN15GLA0
System Platform
Host (Blade Server) Configuration
Fig. 2
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OS90521EN15GLA0
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Platform
1.3 VM Node Configuration

The VM nodes in NetAct constitute the VM pool. Resource pools are used to
compartmentalize the CPU and memory resources of a host or virtual cluster. Virtual
machines execute in, and draw their resources from, resource pools.
vCenter Server provides, through the DRS components, various options in monitoring the
status of the resources and adjusting or suggesting adjustments to the virtual machines using
the resources. The monitor tab in the Hosts and VMs view of the vCenter Client or vCenter
Web Client allows monitoring Resource Pool resources.
The VMs are displayed in the left tree under ‘NetActVMpool’. The icon next to the VM name
indicates the node status. By clicking on a VM, all information pertaining to it is displayed in
the right pane as tabs. Click on the ‘Summary’ tab to get an overview of the VM. In this tab
you can also see the host this VM is currently running on and resource information. To get a
detailed view of resource information for this node click on the ‘Resource Allocation’ tab
OS90521EN15GLA0
System Platform
VM Node Configuration
Fig. 3
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OS90521EN15GLA0
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Platform
1.4 Command Line Interface for EXSi Hosts

The vSphere CLI command set, allows performing configuration tasks in the EXSi hosts. The
set consists of several command sets. For a complete list of the command sets and details
on commands, please refer to the VMware Technical documentation in
www.vmware.com/go/sysadmintools.
The administrative user name for the ESXi host is root. The password for root user is set
during installation.
1.4.1 Command Line Interface and Lockdown Mode

For additional security, the administrator can place one or more hosts managed by a vCenter
Server system in lockdown mode. Lockdown mode affects login privileges for the ESXi host.
When Lockdown mode is activated, no users, including the root users, can log in to an ESXi
Shell. It is not possible then to access the shell from the direct console or by using a remote
shell.
For troubleshooting purposes, it is possible to disable lockdown mode as follows.
The administrator user on the vCenter Server system can disable lockdown mode for hosts it
manages from the vCenter Server system, using any of the vCenter Client applications.
Go to the Settings Configuration of the host and browse until the configuration for Lockdown
mode. If enabled, administrator can edit the configuration and disable as in the next figure.
OS90521EN15GLA0
System Platform
ESXi Host Command Line Interface: Lockdown Mode
Fig. 4
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OS90521EN15GLA0
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Platform
1.4.2 Common Commands

1.4.2.1 Host Related Commands (esxcli)
Maintenance mode Configuration

There are two available commands: Get the state of the host and set the host in or out of
Maintenance Mode. The host is in a state of Entering Maintenance Mode until all running
virtual machines are suspended or migrated. When a host is entering maintenance mode,
you cannot power on virtual machines on it or migrate virtual machines to it.
 Get the state of the host: #esxcli system maintenanceMode get
 Set the host in Maintenance Mode:

# esxcli system maintenanceMode set -e true -t 0
Power operations
Using the esxcli command „shutdown“, the host can be either rebooted or shutdown. If the
ESXi server is not in Maintenance Mode mode the operation will not be allowed. Shutting
down a managed host disconnects it from the vCenter Server system, but does not remove
the host from the inventory. It is possible also to shut down a single host or all hosts in a
datacenter or cluster
When executing either reboot or shutdown it is required to provide parameters for “delay” and
“reason”.
~ # esxcli system shutdown poweroff

Error: Missing required parameter -r|--reason
Usage: esxcli system shutdown poweroff [cmd options]
Description:
poweroff Power off the system. The host must be in
maintenance mode.
Cmd options:
-d|--delay=<long> Delay interval in seconds
-r|--reason=<str> Reason for performing the operation (required)
~ #
 Power off the host:

#esxcli system shutdown poweroff --delay=10 --
reason=”Hardware maintenance”
 Reboot the host:
# esxcli system shutdown reboot –d 10 –r ”Hardware
maintenance”
OS90521EN15GLA0
System Platform
Other useful commands are listed below:

 ESXI version and build: esxcli system version get
 List CPUs: esxcli hardware cpu list
 List memory: esxcli hardware memory get
 List VMKernel modules: esxcli system module list
 List advanced settings: esxcli system settings advanced list
OS90521EN15GLA0
.
13
System Platform
ESXi Host Command Line Interface: Host Related Commands example
Fig. 5
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OS90521EN15GLA0
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Platform
1.4.2.2 System Monitoring Commands (ESXTOP)

System Administrator can perform some monitoring of ESXi system using vCLI commands.
The „esxtop“ utility available in the ESXi Shell allows to communicate with the ESXi host’s
management interface. In order to use „esxtop“ it is required to have root user privileges.
Type the command, using the options as needed:
#esxtop [-] [h] [v] [b] [s] [a] [c filename] [R vm-support_dir_path]
[d delay] [n iter]
h: Prints help for esxtop command-line options.
v: Prints esxtop version number.
s: Calls esxtop in secure mode. In secure mode, the “-d command”, which specifies delay
between updates, is disabled.
d: Specifies the delay between updates. The default is five seconds. The minimum is two
seconds. Change this with the interactive command s. If you specify a delay of less than two
seconds, the delay is set to two seconds.
n: Number of iterations. Updates the display n times and exits. Default value is 10000.
a: Show all statistics. This option overrides configuration file setups and shows all statistics.
The configuration file can be the default ~/.esxtop50rc configuration file or a user-defined
configuration file.
From the command output, the first eight lines contain lowercase and uppercase letters to
specify which fields appear in which order on the CPU, memory, storage adapter, storage
device, virtual machine storage, network, interrupt, and CPU power panels. The letters
correspond to the letters in the Fields or Order panels for the respective esxtop panel. The
ninth line contains information on the other options.
Options for changing to different views in ESXTOP tool:
 m - Memory
 c – CPU
 n – Network
 i – Interrupts
 d – Disk Adapter
 u – Disk Device
 v – Disk VM
 p – Power states
 V – show only virtual machine instances
 Spacebar – refresh screen
OS90521EN15GLA0
.
15
System Platform
ESXi Host Command Line Interface: Monitoring the host performance with
ESXTOP utility
Fig. 6
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OS90521EN15GLA0
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Platform
1.4.2.3 VM related Commands (vmware)

 List of registered VMs: vmware-cmd -l
 Register a VM: vmware-cmd -s register /vmfs/volumes/<volume

name>/<vm>/<vm>.vmx <datacenter> <resource pool>
 Un-register a VM: vmware-cmd -s unregister /vmfs/volumes/<volume
name>/<vm>/<vm>.vmx
 Power on a VM: vmware-cmd -s unregister /vmfs/volumes/<volume
name>/<vm>/<vm>.vmx start
 Shutdown a VM: vmware-cmd -s unregister /vmfs/volumes/<volume
name>/<vm>/<vm>.vmx stop [ soft | hard ]
 Power off a VM: vmware-cmd -s unregister

/vmfs/volumes/<volumename>/<vm>/<vm>.vmx stop [ soft | hard]
 Reset a VM: vmware-cmd -s unregister /vmfs/volumes/<volume

name>/<vm>/<vm>.vmx reset [soft | hard ]
 Suspend a VM: vmware-cmd -s unregister /vmfs/volumes/<volume
name>/<vm>/<vm>.vmx suspend [soft | hard ]
 Resume a VM: vmware-cmd -s unregister /vmfs/volumes/<volume

name>/<vm>/<vm>.vmx resume [soft | hard ]
 Get VM Uptime: vmware-cmd -s unregister /vmfs/volumes/<volume
name>/<vm>/<vm>.vmx getuptime
OS90521EN15GLA0
.
17
System Platform
1.5 Virtualization Related Logs

Log Location Description
/var/log/vmware/vpx/* vCenter logs
vmware.log VM specific log on ESXi host
/var/log/vmksummary.log Summary of ESXi host startup and shutdown,

and an hourly heartbeat with uptime,
number of virtual machines running, and
service resource consumption
/var/log/vmkernel.log Core VMkernel logs, including device

discovery, storage and networking device
and driver events, and virtual machine
startup
/var/log/syslog.log Management service initialization,

watchdogs, scheduled tasks and DCUI use
/var/log/hostd.log Host management service logs, including

virtual machine and host Task and Events,
communication with the vSphere Client and
vCenter Server vpxa agent, and SDK
connections
OS90521EN15GLA0
System Platform
2 Software Platform
OS90521EN15GLA0
.
19
System Platform
2.1 Software
2.1.1 Components
NetAct 15 contains several software layers that are installed in the correct order. After
hardware and OEM software installation, NetAct SW platform is installed to the servers. On
top of NetAct 15, there are Mediations, adaptations and applications.
The following list presents the current version information about the key 3rd party SW
components used in the NetAct 15 release. Please note that this information is non-binding
and the list is subject to changes.
OEM Software Version
Red Hat Enterprise LINUX 6.5
Oracle 11G Enterprise Edition 11.2.0.3.0
Red Hat Directory Server LDAP v3
WebSphere Application Server 8
NFS Version 3
Load Balancer LINUX Virtual Server (LVS)
Red Hat Enterprise Linux (RHEL) is a Linux distribution produced by Red Hat and targeted
towards the commercial market, including mainframes. Red Hat Enterprise Linux is often
abbreviated to RHEL.
The Oracle Database is a relational database management system (RDBMS) produced and
marketed by Oracle Corporation. Current version is 11G Enterprise Edition.
Red Hat Directory Server is an LDAP based server that centralizes application settings, user
profiles, group data, policies and access control information into an operating system -
independent network-based registry.
IBM WebSphere Application Server (WAS) is a software application server.
Network File System (NFS) is used to implement shared file access.
Load Balancer is used to balance the load across the Application Servers in the NetAct
cluster.
OS90521EN15GLA0
System Platform
System Platform
Software: Components
NetAct 15 Software Installation with RedHat Package Manager

# rpm –qa | grep – i NSN
Mediations,
Adaptation Applications
NE3S,
SNMP, FTP
s (FM, PM, CM) Red Hat Entrerprise Linux 6.5
 /etc/redhat-release
OSS Application Platform
Computing Platform
# yum repolist
HW and Virtualized Infrastructure  /var/log/yum.log
NetAct 15 version
 /etc/netact-release
Fig. 7
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OS90521EN15GLA0
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Platform
2.1.2 Environment Variables

Please note that environment variables are created only on the relevant nodes (VMs) and not
necessarily on all nodes. For e.g. GEP_HOME is defined only on FM_PIPE node. Similarly
CPF_WAS_HOME is defined only on the WAS nodes.
OS90521EN15GLA0
System Platform
System Platform
Software: Environment Variables
$OMCROOT /opt/nokia/oss
$PRODUCTROOT root disk
$ETCROOT /etc/opt/nokia/oss global disk
$VARROOT /var/opt/nokia/oss root disk
$OMCLOGDIR
$NMSLOGDIR $VARROOT/local/common/log root disk
$CPF_WAS_HOME /opt/WebSphere/AppServer
$GEP_HOME /opt/oss/gep
$JACORB_HOME /opt/nokia/oss/jacorb
$NWI3_HOME /opt/oss/NSN-nwi3
$NX2S_HOME /opt/oss/NSN-nx2s
$NBI3GC_HOME /opt/oss/nbi/bin root disk
$NBISNMP_HOME /opt/oss/NSN-nbisnmp
$FMASCII_HOME /opt/oss/NSN-fmascii
1 $ORACLE_HOME
© Nokia Solutions and Networks 2015 /opt/oracle/product/11gR2 root disk
Fig. 8
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OS90521EN15GLA0
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Platform
2.2 NetAct Storage

2.2.1 Global Storage Subsystem
The global storage subsystem composes of two independent parts:
 Disk array: Aggregates multiples of physical disks under one or more LUNs. On the server
side the LUNs are seen as ordinary disks (SCSI targets). LUNs are internally striped and
mirrored inside the disk array ("hardware RAID")
 SAN switches: Two independent Fibre Channel (FC) switches between servers and
storage devices providing "Redundant Fibre Channel Fabric“. There is a FC connection to
the global disk both from AS and DS.
In NetAct 15, the HP BL460c G8 blades have Host Bus Adapter (HBA) cards from the vendor
QLogic. These HBA cards are Dual Port cards. The NetAct 15 servers can also be integrated
into the customer’s existing SAN infrastructure. This is made possible by the Open SAN
concept.
There are a total of seven LUNs that are a pre-requisite for NetAct 15 installation. These
LUNs are available to all ESXi hosts:
 LUN #1: VMGuestDisk1
 LUN #4: redo - contains online redo logs for Oracle DB
 LUN #5: db - contains data files for Oracle DB
 LUN #6: arc - contains archived redo logs for DB
 LUN #7: global - contains /home and /d/oss/global that is exported to all nodes via
NFS
The VMGuestDisks are used to store VM files (local OS per VM). The storage of VM files is
rotated among the three disks. VMGuestDisk1 has VM1 files, VMGuestDisk2 has VM2 files,
VMGuestDisk3 has VM3 files, VMGuestDisk1 has VM4 files and so on.
OS90521EN15GLA0
System Platform
The virtual machines in the ESXi hosts are not directly aware of the LUNs and their storage
mechanism. VMware infrastructure virtualizes the SAN storage (via data stores) and present
the required disks to the VMs. For example,. VM4 (DB node) requires three disks - db, db-
arc and db-redo for the Oracle service. The ESXi host which is currently running VM4 will
provide these three LUNs to VM4. So when the mount command is run on VM4, these disks
will be visible. If a VM mounting a LUN(s) is relocated to another host, the hypervisor
software ESXi on new host is responsible for making the required disks available and then
visible to the VM.
In addition to these seven LUNs, there are LUNs for each of the server blades. The ESXi
host is installed on this LUN. So NetAct 15 small configuration will have four additional LUNs,
while mainstream and large will six additional LUNs. The host LUN is visible only to the
respective host and not to the other hosts in the cluster.
OS90521EN15GLA0
.
25
System Platform
System Platform
Storage: Storage Subsystem
HP Blade 1 HP Blade 3 HP Blade 5 HP Blade 6

EXSi …… EXSi …… EXSi EXSi
LAN
LAN
FC
FC LAN
LAN
FC
FC LAN
LAN
FC
FC LAN
LAN
FC
FC
Traffic LAN
SAN
SW1 SW2
FC FC FC FC
CTRL A CTRL B
VMGuest VMGuest VMGuest

Host-1 Host-2 Host-6
…… Disk-1 Disk-1 Disk-1
DB disk DB-arch DB-redo Global PM Global Backup

disk disk disk disk disk
Fig. 9
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OS90521EN15GLA0
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Platform
2.2.2 NetAct Disks Configuration

The file systems in NetAct 15 are mounted to specific VMs accordingly to the services
running in the VM. All mounts from the global disk are via ‘ext4’ file system
NFS is used in NetAct 15 to implement a shared file structure. There are only two volume
groups that need to be shared by all nodes that is /home and /d/oss/global, located in
LUN#7. The VM node running the NFS service (VM5) mounts these logical volumes and
exports it to all the nodes via NFS. The command ‘showmount –e’ displays the currently
NFS mounted file systems in the VM that is currently serving NFS service. The
/var/lib/nfs/rmtab file contains a record of all clients that have done remote mounts of
file systems from this node. Whenever a remote mount is done, an entry is made in the
rmtab file of the machine serving that file system. The corresponding umount on the remote
client will remove the entry.
NFS is started by the init script /etc/init.d/nfs. If NFS settings are changed, it is
necessary to restart the NFS daemon with using the command ‘/etc/init.d/nfs
restart’ for the changes to take effect.
The VM node running the ‘db’ service mounts the three database related logical volumes.
OS90521EN15GLA0
.
27
System Platform
System Platform
Storage: Disks Configuration
HP Blade 1 HP Blade 3 HP Blade 5 HP Blade 6

EXSi …… EXSi …… EXSi EXSi
LAN
LAN
FC
FC LAN
LAN
FC
FC LAN
LAN
FC
FC LAN
LAN
FC
FC
Traffic LAN
SAN
SW1 SW2
FC FC FC FC
CTRL A CTRL B
VMGuest VMGuest VMGuest

Host-1 Host-2 Host-6
…… Disk-1 Disk-1 Disk-1
DB disk DB-arch DB-redo Global PM Global Backup

disk disk disk disk disk
Fig. 10
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OS90521EN15GLA0
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Platform
System Platform
Storage: Disks Configuration
Fig. 11
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OS90521EN15GLA0
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Platform
2.2.3 Directories
NetAct 15 uses the following basic directory structure:
 Binaries: /opt/oss/bin and /opt/nokia/oss/bin
 Installation time templates: /opt/oss/install/template
 Installation time configuration files: /opt/oss/install/conf
 Log files: /var/log, /var/opt/nokia/oss/log
 Static configuration files: /opt/oss/<subsystem>/conf
 Database data files: /d/db/oradata/oss
 Database redo log files: /d/db-redo/oss
 Database archive log files: /d/db-arc/oss
Please note that some folders are present only on nodes where the component is installed
and not on all nodes.
OS90521EN15GLA0
System Platform
System Platform
Storage: Directories
$ORACLE_HOME
11gR2
DB node – VM4
Other nodes
opt oracle product
Root
/ Root /
Binaries
/boot etc /opt
db nokia oss bin

/tmp
/tmp
db-arc
/var d oss NSN-<Component...>
/var
db-redo
DB disks from SAN /home
bin
NFS node – VM5 NFS
/d/oss/global
gep
/ Binaries
Root nbi
/boot
home NFS
/tmp
d oss global
/var
1
VG Home and VG Global disks from SAN
Fig. 12
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OS90521EN15GLA0
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
© Nokia
. Solutions
. . and. Networks
. . .2015. . . . . . . . . . . . . . . . . . . . . . . . . . . .
.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Platform
2.2.4 Oracle
The Oracle Database that is used in NetAct is Oracle 11g Enterprise Edition (11.2).
TIP
For more details on Oracle database please refer to the chapter Data Storages.
2.2.5 LDAP
The Lightweight Directory Access Protocol (LDAP) is a set of open protocols used to access
centrally stored information over a network. It is based on the X.500 standard for directory
sharing, but is less complex and resource-intensive.
The NetAct implementation of LDAP is realized with Red Hat Directory Server. RHDS is a
powerful and scalable distributed directory server based on the industry-standard Lightweight
Directory Access Protocol (LDAP).
In NetAct, the LDAP directory is used for centralizing configuration data which is needed by
processes that are:
 managing authorization data
 performing user authentication to various network resources
TIP
For more details on LDAP database please refer to the chapter Data Stores.
OS90521EN15GLA0
System Platform
System Platform
Storage: LDAP
The LDAP directory is a list of information about objects arranged in some

order that gives details about each object.
LDAP directory
e.g.
Users management data
LDAP software in NetAct is Red Hat Directory Service

(RHDS)
Fig. 13
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OS90521EN15GLA0
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
33
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Platform
2.3 System Platform related Logs

2.3.1 Linux Logs
LINUX logs are stored in /var/log in all the NetAct VMs.
Log Description
/var/log/boot Logs messages from the boot and

initialization scripts
/var/log/btmp Logs bad console login attempts
/var/log/cron Logs commands and scripts that have

been run by LINUX cron
var/log/messages Logs messages produced by the LINUX

system and RHCS
/var/log/secure Logs SSH logins
/var/log/maillog Logs mail daemon messages
/var/log/rpmpkgs Logs all the rpms installed.

Equivalent to ‘rpm –qa’
/var/log/spooler Logs print messages and events in

case the system is connected to a
printer
/var/log/wtmp Logs information of users who have

successfully logged-in and logged-
out of the system
/var/log/yum.log Logs YUM events
/var/log/ha Service manager log files
OS90521EN15GLA0
System Platform
2.3.2 Computer Platform Logs

Please note that these log files are available only on the node where the software or service
is installed
Log Description
/var/log/cpf/oracle/ Oracle database installation

log file
/opt/oracle/admin/oss/adump/*.aud Database security auditing

files
/opt/oracle/product/11gR2/rdbms/audit/ The default location for the

* security audit files, if the
AUDIT_FILE_DEST parameter is
not specified.
/opt/oracle/diag/rdbms/oss/oss/trace/* Database log files
/opt/oracle/product/11gR2/network/log/ Oracle client logs

*
/opt/oracle/product/11gR2/network/trac Network listener trace file

e/* directory
/opt/oracle/product/11gR2/sysman/log/* Management agent log file
/var/log/was_configuration.log WebSphere Application Server

configuration log files
/opt/IBMHttpServer/logs/* HTTP server log files
/opt/WebSphere/AppServer/profiles/<AS IBM service log. To be

node>/logs/activity.log viewed using showLog tool
/opt/WebSphere/AppServer/profiles/<AS WebSphere Application Server

node>/logs/server1/* log files
/var/log/messages Load Balancer messages from

Linux Virtual Server
/opt/JacORB/etc/jacorb/* CORBA related log files
/var/log/dirsrv/slapd- Logs connections,

<instance_name>/access authentications, searches,
addition, modification,
deletion and replication
/var/log/dirsrv/slapd- Logs LDAP related
OS90521EN15GLA0
.
35
System Platform
<instance_name>/errors operational errors
OS90521EN15GLA0
System Platform
3 NetAct Time Management
OS90521EN15GLA0
.
37
System Platform
3.1 Introduction
NetAct receives its time reference from the Network Time Protocol (NTP) servers located
outside of NetAct. The NTP service in each virtual machine (VM) sends time queries to
external NTP servers to receive the Coordinated Universal Time (UTC) reference. Based on
the information received, the NTP service updates the system clock. Time queries to the
external NTP time servers are made by all NetAct virtual machines individually. In a multiple
virtual machine environment, the NTP services of all VMs use each other as time reference
for UTC, if external NTP servers stop responding for some reason.
The NTP service configuration file, /etc/ntp.conf, is configured automatically during
installation. The file can be modified when needed, for example, if the external NTP server
host address is changed. If there are changes made to the /etc/ntp.conf file, the NTP
service must be restarted.
Configuration and output can vary in actual use depending on the practical network
environment.
Nokia Solutions and Networks recommends to have 2-3 external NTP servers.
[root@n83-vm03 ~]# more /etc/ntp.conf
tinker panic 0
disable monitor
restrict default kod nomodify notrap nopeer noquery
restrict 127.0.0.1
server 10.88.4.226
peer 10.88.2.198
peer 10.88.2.199
peer 10.88.2.200
peer 10.88.2.201
peer 10.88.2.202
peer 10.88.2.203
peer 10.88.2.204
peer 10.88.2.205
peer 10.88.2.206
peer 10.88.2.207
peer 10.88.2.208
peer 10.88.2.209
peer 10.88.2.210
peer 10.88.2.211
peer 10.88.2.212
peer 10.88.2.213
peer 10.88.2.214
peer 10.88.2.215
peer 10.88.2.216
peer 10.88.2.217
driftfile /var/lib/ntp/drift
[root@n83-vm03 ~]#
OS90521EN15GLA0
System Platform
3.1.1 Configuring NTP in the network elements

Many network elements (NEs) use NTP to get accurate time from NetAct. NTP is configured
in the NEs using an Element Manager connection on MML.
If NetAct is used as the time source, then the NE is configured so that the time source is any
combination of the NetAct VMs. One VM is enough, but it is recommended to use at least
two of the VMs and if possible, all of them.
If an external NTP server is in place, then the NE needs to be configured with the external
NTP server’s IP address and its backup (based on the operator network environment).
OS90521EN15GLA0
.
39
System Platform
NetAct Time Management

Overview
In the NetAct 8 environment,

the NTP services of all VMs
use each other as the time
reference for UTC, if the
external NTP servers stop
responding
Fig. 14
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OS90521EN15GLA0
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Platform
3.2 Managing the NTP Service

3.2.1 Checking the NTP service status
1. Log in to the required VM, as root user.
2. To check the NTP service status, enter:
[root]# service ntpd status
Expected outcome
ntpd (pid 12345) is running...
For more information, see the NTP logs at /var/log/messages with process name
ntpd, which can be used to grep NTP-related messages.
3.2.2 Stopping the NTP service

2. To stop the NTP application, enter:
[root]# service ntpd stop
Expected outcome
Shutting down ntpd:
3.2.3 Starting the NTP service

2. 2. To start the NTP application, enter:
[root]# service ntpd start
Expected outcome
Starting ntpd:
For more information, see the NTP logs at /var/log/messages with process name ntpd,
which can be used to grep NTP-related messages.
OS90521EN15GLA0
.
41
System Platform

Managing the NTP Service
To check the status of NTP service, log to the required VM node as root user and
execute:
[root@n83-vm21 ~]# service ntpd status
ntpd (pid 26701) is running...
To stop the NTP service, log to the required VM node as root user and execute:
[root@n83-vm21 ~]# service ntpd stop
Shutting down ntpd: [ OK ]
To start the NTP service, log to the required VM node as root user and execute:
[root@n83-vm21 ~]# service ntpd start
Starting ntpd: [ OK ]
Fig. 15
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OS90521EN15GLA0
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Platform
3.2.4 Checking NetAct Time Synchronization

To check that NetAct time is synchronized and accurate, enter:
[root]# ntpq -p
Expected outcome
[root@n83-vm21 ~]# ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
#10.88.4.226 10.171.8.5 4 u 51 128 377 1.193 -12.951 1.352
#n83-vm03.n83.ob 10.88.2.213 8 u 79 128 337 0.134 -5.084 1.631
+n83-vm04.n83.ob 10.88.2.201 8 u 88 128 376 0.123 -3.629 0.983
n83-vm05.n83.ob .STEP. 16 u 39 64 0 0.000 0.000 0.000
+n83-vm06.n83.ob 10.88.2.208 8 u 11 128 377 0.003 -2.517 1.233
*n83-vm07.n83.ob 10.88.2.200 7 u 80 128 175 0.251 -5.030 1.483
+n83-vm08.n83.ob 10.88.2.206 7 u 27 128 377 0.058 -2.733 1.158
+n83-vm09.n83.ob 10.88.2.208 8 u 31 128 377 0.136 -2.962 1.065
+n83-vm10.n83.ob 10.88.2.202 7 u 69 128 376 0.004 -2.583 1.056
+n83-vm11.n83.ob 10.88.2.200 9 u 2 128 377 0.072 -2.444 1.035
+n83-vm12.n83.ob 10.88.2.201 8 u 78 128 376 0.134 -2.982 0.953
+n83-vm13.n83.ob 10.88.2.204 11 u 125 128 376 0.350 -2.793 0.983
+n83-vm14.n83.ob 10.88.2.198 7 u 129 128 376 0.191 -2.788 1.105
+n83-vm15.n83.ob 10.88.2.204 7 u 19 128 377 0.053 -2.509 1.115
+n83-vm16.n83.ob 10.88.2.208 8 u 118 128 372 0.127 -5.059 111.426
+n83-vm17.n83.ob 10.88.2.213 8 u 10 128 377 0.192 -2.328 1.217
+n83-vm18.n83.ob 10.88.2.209 8 u 68 128 376 0.100 -2.548 1.146
+n83-vm19.n83.ob 10.88.2.208 8 u 12 128 377 0.208 -2.464 1.180
+n83-vm20.n83.ob 10.88.2.204 8 u 75 128 356 0.047 -2.640 1.499
+n83-vm22.n83.ob 10.88.2.204 8 u 16 128 377 0.043 -2.674 1.164
+n83-vm23.n83.ob 10.88.2.204 8 u 64 128 333 0.045 -2.433 1.632
[root@n83-vm21 ~]#
There should be at least one entry in the output with an asterisk (*), indicating that the NTP
server is synchronized to that source. The asterisk is a tally code character. For more
information, see Tally Codes in http://doc.ntp.org/4.2.0/ntpq.html.
The reach value for the given time source should be 377 or close to it. The number should be
over 100.
OS90521EN15GLA0
.
43
System Platform
Note: When the tally code character and reach values show that one or more VMs are not
synchronized, it is recommended to manually synchronize the clocks. For more information,
see Manually synchronizing the clock on all NetAct virtual machines.
3.2.5 Manually synchronizing the clock on all NetAct virtual

machines
After checking NetAct time synchronization, if the time skew on one or more VMs is
noticeably different when compared to the others, it is recommended to manually
synchronize the clocks.
1. Log in to each NetAct VM, and switch to the root user.
2. To check the status of the NTP service on each VM, enter the following command:
[root]# smanager.pl status service ntp-<vm name>
Expected outcome
ntp-<vm name>:<vm name>:started
3. Depending on the service status, do one of the following:
a) If the NTP service status is started, then put the service in maintenance mode by
entering the following command and proceed to step 4.
[root]# smanager.pl maintenance ntp-<vm name> on
Expected outcome
Service ntp-<vm name> maintenance mode is set to on
Note: When the service is in maintenance mode, Service Monitoring no longer
controls the service.
b) b) If the NTP service status is frozen, then proceed to step 4.
4. To stop the NTP service running on each NetAct VM, enter:
[root]# service ntpd stop
5. To ensure that the NTP service is no longer running on each VM, enter:
[root]# service ntpd status
Expected outcome
At this point, the output below appears on all NetAct VMs.
ntpd is stopped
Note: Proceed to the next step only if the NTP service is stopped on all NetAct VMs.
OS90521EN15GLA0
System Platform
6. To manually synchronize the clock to an external NTP server as defined in /etc/ntp.conf

on each VM, enter:
[root]# ntpd -gq
Expected outcome
An output similar to the one below appears. The value of s depends on the environment.
ntpd: time slew +0.101608s
Note: Proceed to the next step only if step 6 is completed on all NetAct VMs.
7. To start the NTP service on each VM, enter:
[root]# service ntpd start
Expected outcome
Starting ntpd:
8. To remove the NTP service from maintenance mode on each VM, enter:
[root]# smanager.pl maintenance ntp-<vm name> off
Note: Since the service is no longer under maintenance mode, Service Monitoring
now controls the service.
Expected outcome
After a few minutes, the clock is synchronized with the external time server.
OS90521EN15GLA0
.
45
System Platform

Checking NetAct Synchronization
There should be at least one entry in the output with an asterisk (*), indicating that the NTP server is
synchronized to that source. When the tally code character and reach values show that one or more
VMs are not synchronized, it is recommended to manually synchronize the clocks
[root@n83-vm21 ~]# ntpq -p

remote refid st t when poll reach delay offset jitter
==============================================================================
#10.88.4.226 10.171.8.5 4 u 51 128 377 1.193 -12.951 1.352
#n83-vm03.n83.ob 10.88.2.213 8 u 79 128 337 0.134 -5.084 1.631
+n83-vm04.n83.ob 10.88.2.201 8 u 88 128 376 0.123 -3.629 0.983
n83-vm05.n83.ob .STEP. 16 u 39 64 0 0.000 0.000 0.000
+n83-vm06.n83.ob 10.88.2.208 8 u 11 128 377 0.003 -2.517 1.233
*n83-vm07.n83.ob 10.88.2.200 7 u 80 128 175 0.251 -5.030 1.483
+n83-vm08.n83.ob 10.88.2.206 7 u 27 128 377 0.058 -2.733 1.158
+n83-vm09.n83.ob 10.88.2.208 8 u 31 128 377 0.136 -2.962 1.065
+n83-vm10.n83.ob 10.88.2.202 7 u 69 128 376 0.004 -2.583 1.056
+n83-vm11.n83.ob 10.88.2.200 9 u 2 128 377 0.072 -2.444 1.035
+n83-vm12.n83.ob 10.88.2.201 8 u 78 128 376 0.134 -2.982 0.953
+n83-vm13.n83.ob 10.88.2.204 11 u 125 128 376 0.350 -2.793 0.983
+n83-vm14.n83.ob 10.88.2.198 7 u 129 128 376 0.191 -2.788 1.105
+n83-vm15.n83.ob 10.88.2.204 7 u 19 128 377 0.053 -2.509 1.115
+n83-vm16.n83.ob 10.88.2.208 8 u 118 128 372 0.127 -5.059 111.426
+n83-vm17.n83.ob 10.88.2.213 8 u 10 128 377 0.192 -2.328 1.217
+n83-vm18.n83.ob 10.88.2.209 8 u 68 128 376 0.100 -2.548 1.146
+n83-vm19.n83.ob 10.88.2.208 8 u 12 128 377 0.208 -2.464 1.180
Fig. 16
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OS90521EN15GLA0
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Platform
4 Service Manager
OS90521EN15GLA0
.
47
System Platform
4.1 Introduction
NetAct services are managed using a Service Manager tool. The script
/opt/cpf/bin/smanager.pl is an enhanced replacement of the OSS 5.x script
hamgrmx.pl.
While hamgrmx.pl was only a wrapper script for OSS 5.x RHCS, smanager.pl covers all
nodes and their services in NetAct 15. It also provides options to start/stop services as well
start/stop the clusters and the whole of NetAct.
4.2 Service Manager Usage

The output of the command ‘/opt/cpf/bin/smanager.pl status’ is very similar to
‘hamgrmx.pl -status’ of OSS 5.x. It provides the status of the services in each of the
nodes. Unlike OSS 5.x and NetAct 7, there is no concept of service relocation to another
node in NetAct 15. There is no virtual IP associated with each service in NetAct 15; hence it
is marked as standAlone.
View the status of a specific service using the command:
smanager.pl status service <name_of_service>
View the status of the services on a specific VM using the command:
smanager.pl status node <name_of_node_or_VM>
There is a special service called tomcat_vcentplg running only on VM3. This service
provides a HTTP interface for external applications and components to obtain the service
manager status via HTTP. This service is currently used by vCenter to obtain the status of
NetAct 15 services.
OS90521EN15GLA0
System Platform
Service Manager
Usage
smanager.pl
status
status cluster [name of cluster]
status service [name of service]
status node [name of node] Script: smanager.pl
start cluster [name of cluster]
start <product>
Location: /opt/cpf/bin
stop <product>
stop cluster [name of cluster]
start service [service] [node]
stop service [service]
stop node [node]
disable service name
disable node name
enable service name
enable node name
maintenance [service|all] on|off
maintenance node [node_name] on|off
-help
Fig. 17
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OS90521EN15GLA0
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
49
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Platform
Service Manager
Checking Status
Status of NetAct
DomainNode Service Status VirtualIP
Site: Local
All
n83-vm03
netfs-n83-vm03 started standAlone
#smanager.pl status
cpfnx2s-n83-vm03 started standAlone
OMAgentAF-n83-vm03 started standAlone
ssh-n83-vm03 started (u) standAlone
ntp-n83-vm03 started (u) standAlone
DNS-Master started (u) standAlone
dirsrv started (u) standAlone
tomcat_vcentplg started standAlone tomcat_vcentplg: vCenter Plugin
n83-vm04
cpfnx2s-n83-vm04 started standAlone Status (u): unstoppable:
ssh-n83-vm04 started (u) standAlone It is not possible to stop this
ntp-n83-vm04 started (u) standAlone service using smanager.pls
db started standAlone
n83-vm05
nfs started (u) standAlone
dirsrv-secondary started (u) standAlone
n83-vm06
pulse-jbi started standAlone
n83-vm07
1 OMAgent started
© Nokia Solutions and Networks 2014 standAlone
vcenterselfmon started standAlone
hpsim started standAlone
Fig. 18
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OS90521EN15GLA0
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Platform
Service Manager
Checking Status: status options
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
The service has failed to recover, and the Service Monitoring application is trying
Recovering
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.
1
Locked The service is disabled
Fig. 19
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OS90521EN15GLA0
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Platform
4.3 Service Manager in vCenter Client

It is possible to check the status of NetAct Service manager using the vSphere client. This is
possible due to the Tomcat vCenter plug-in that is running as a service on VM3 as
tomcat_vcentplg. This service exposes an HTTP interface to obtain the smanager.pl status
from NetAct.
In the vSphere client, click on a VM node in the left tree. On the right, select the ‘NetAct
Services Plug-in’ tab. The status of services running on the node is displayed.
4.3.1 Enabling visualization of the vCenter NetAct plugin

4.3.1.1 To enable the vCenter NetAct plugin using Internet Explorer
1. Access the vSphere Web client using Internet Explorer.
2. From the vCenter home, click Hosts and Clusters, and then select your vCenter server
name.
3. Click Clusters, and then select a cluster.
4. Click the Classic Solutions tab.
5. From the error message that appears, click Show Content.
6. Log out from the vSphere Web client, and restart your Internet Explorer session.
7. Repeat steps 1 through 4.
Expected outcome
The NetAct Cluster status page appears.
OS90521EN15GLA0
System Platform
4.3.1.2 5.2 To enable the vCenter NetAct plugin using Mozilla Firefox
8. Access the vSphere Web client using Mozilla Firefox.
9. From the vCenter home, click Hosts and Clusters, and then select your vCenter server
name.
10. Click Clusters, and then select a cluster.
11. Click the Classic Solutions tab.
12. From the error page that appears, copy the server name and TCP port.
13. Note: The server name and TCP port are usually highlighted in bold text and appears in
14. this format: virtualmachine.netact.example.net:8094
15. Open a new tab.
16. In the URL field, type https://, and paste the values you copied from step 5.
17. Press Enter, and expand the section I Understand the Risks.
18. Click Add Exception.
19. From the Add Security Exception dialog, select the Permanently store this exception
20. checkbox.
21. Click Confirm Security Exception, and then close the tab.
22. Log out from the vSphere Web client, and restart your Firefox Mozilla session.
23. Repeat steps 1 through 4.
Expected outcome
The NetAct Cluster status page appears
OS90521EN15GLA0
.
53
System Platform
Service Manager
Plugin in vCenter: Enabling visualization of NetAct Plugin
Fig. 20
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OS90521EN15GLA0
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Platform
Service Manager
Plugin in vCenter
Fig. 21
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OS90521EN15GLA0
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
55
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Platform
OS90521EN15GLA0
System Platform
5 Exercises
OS90521EN15GLA0
.
57
System Platform
Exercise 1
Title: NetAct System Platform: Software
Objectives: List the main components of the Software Installation.

Verify the installation of the main NetAct Software components.
Identify the System Platform Logs.
Pre-requisite: none
Task
Please open a console session with the corresponding NetAct VM with the credentials
provided by your trainer. Execute the following tasks and answer the related questions.
1. Please fill in the following figure the missing names about the Software components in
NetAct.
OS90521EN15GLA0
System Platform
2. List the Key 3rd Party SW Components of the NetAct delivery:
 __________________________________
 __________________________________
 __________________________________
 __________________________________
3. Select three different VM Nodes. What is the RHEL version installed on these VM
Nodes? What is the version of the NetAct 15 system and build installed?
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
4. Select one VM Node. In your node, how many NetAct RPMs are installed?
______________________________________________________________________
______________________________________________________________________
OS90521EN15GLA0
.
59
System Platform
Exercise 2
Title: System Platform: Storage
Objectives: Describe the Storage Subsystem.

Explain the usage of NFS in NetAct storage configuration.
Identify the location of NetAct files and logs.
Pre-requisite: none
Task
Please open a console session with the corresponding NetAct VM node with the credentials
provided by your trainer. Execute the following tasks and answer the related questions.
1. What are the components of the Storage Subsystem?

______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
2. How are the NetAct VM Nodes connected to the global disk?

______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
3. How is NFS used in NetAct 15?

______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
4. Where is the NFS configuration defined? Open the corresponding file and list the defined
exported file systems and the export options.
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
OS90521EN15GLA0
System Platform
5. Are any of the VM nodes mounting a file system from the global vg? How can you verify
from the VM nodes these mountings? If yes which one(s) and is there shared access to
these file systems?
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
6. What is the location of NetAct log files?

______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
7. Which are the 3 key database file systems in the NetAct? In what VM are they
mounted? Open session to this VM and check the contents of these file systems.
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
OS90521EN15GLA0
.
61
System Platform
Exercise 3
Title: Service Manager
Objectives: Explain the function of the Service Manager tool.

Check the status of the NetAct system services.
Revise the status of the NetAct system services using the vCenter
Client.
Pre-requisite: none
Task
Please open a console session with the corresponding NetAct VM ndoe with the credentials
provided by your trainer. Execute the following tasks and answer the related questions
1. Check the status of all NetAct Services using the Service Manager tool. What is the
current status of the nodes and services?
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
_____________________________________________________________________
2. Using the Service Manager tool, is it possible to relocate one server to a different node?
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
3. Stop the service nbi3gc. Use the command “watch” to see the status of the service.
Does it start automatically on the same node? Does it automatically start in a different
node?
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
4. Kill the nbi3gc process. Is the process started automatically? If yes, in which node is
started?
______________________________________________________________________
______________________________________________________________________
OS90521EN15GLA0
System Platform
5. Open session to the vCenter with the vCenter Web Client. Revise the status of the
vCenter NetAct plugin. What information can you see in the display of the plugin? (Note:
if the plugin visualization is not activated, follow the instructions in this document to
activate it)
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
OS90521EN15GLA0
.
63
System Platform
Exercise 4
Title: Time Management
Objectives: Revise the synchronization status of NetAct.
Pre-requisite: none
Task
Please open a console session with the corresponding NetAct VM node with the credentials
provided by your trainer. Execute the following tasks and answer the related questions
1. How is the time in the VMs synchronized? Open a session with VM03 and check the
corresponding time configuration. What is the time reference used there? Compare it
with other VMs to verify if the configuration is the same.
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
____________________________________________________________________
2. Select one VM node of your preference. Check the synchronization status of the node
and the status of the NTP service. Accordingly to the results of your queries, is it
necessary to run a manual synchronization? List the steps required for the verification
tasks.
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
OS90521EN15GLA0
System Platform
Exercise 5
Title: Virtualized Infrastructure
Objectives: Explain the functionality of the main components of the Virtualized

Infrastructure used in NetAct.
Use the vCenter Client or vCenter Web client to check configuration
and monitor the status of the virtualized infrastructure in NetAct.
Use the command line tool to get host configuration and data for an
ESXi host.
Monitor the performance of an ESXi host using command line tool.
Pre-requisite: none
Task
Please open a session to the vCenter using either the vCenter Client or vCenter Web Client
with the credentials provided by your trainer. Execute the following tasks and answer the
related questions.
Query
1. By checking the configuration of NetAct virtualization infrastructure using vCenter Client,
list the VMware components used for NetAct and briefly describe the usage of each of
them.
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
2. Explain how you can check the health status and configuration of the VM nodes and
ESXi host using the vCenter Client (or vCenter Web Client)
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
OS90521EN15GLA0
.
65
System Platform
3. Select a VM node. Determine which server blade it is running on. What are the other
VMs running on the same blade?
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
4. Do any of the hosts have a problem with resource allocation and consumption? How
can you check this information?
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
5. Connect to a ESXi host via ssh. Check the maintenance status of your selected ESXi
host by using command line tool. Set the selected host in Maintenance Mode. Verify
using the vCenter client what happens to the VMs running in your host during and after
the maintenance command execution.
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
6. Use the ESXTOP tool to monitor the performance of your selected host. Check in detail
the memory consumption. List the commands required for this task
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
OS90521EN15GLA0

01 OS90521EN15GLA0 System Platform

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

01 OS90521EN15GLA0 System Platform

Загружено:

Авторское право:

Доступные форматы

System Platform

1.1 NetAct VM Configuration Overview

1.1.1 vSphere Client

1 © Nokia Solutions and Networks 2014

1.2 Host (Blade Server) Configuration

1 © Nokia Solutions and Networks 2015

1.3 VM Node Configuration

1 © Nokia Solutions and Networks 2015

1.4 Command Line Interface for EXSi Hosts

1.4.1 Command Line Interface and Lockdown Mode

1 © Nokia Solutions and Networks 2015

1.4.2 Common Commands

Maintenance mode Configuration

 Set the host in Maintenance Mode:

~ # esxcli system shutdown poweroff

 Power off the host:

Other useful commands are listed below:

 List CPUs: esxcli hardware cpu list

 List memory: esxcli hardware memory get

 List VMKernel modules: esxcli system module list

 List advanced settings: esxcli system settings advanced list

1 © Nokia Solutions and Networks 2015

1.4.2.2 System Monitoring Commands (ESXTOP)

1 © Nokia Solutions and Networks 2015

1.4.2.3 VM related Commands (vmware)

 Register a VM: vmware-cmd -s register /vmfs/volumes/<volume

 Power off a VM: vmware-cmd -s unregister

 Reset a VM: vmware-cmd -s unregister /vmfs/volumes/<volume

 Resume a VM: vmware-cmd -s unregister /vmfs/volumes/<volume

1.5 Virtualization Related Logs

/var/log/vmware/vpx/* vCenter logs

vmware.log VM specific log on ESXi host

/var/log/vmksummary.log Summary of ESXi host startup and shutdown,

/var/log/vmkernel.log Core VMkernel logs, including device

/var/log/syslog.log Management service initialization,

/var/log/hostd.log Host management service logs, including

OEM Software Version

Red Hat Enterprise LINUX 6.5

Oracle 11G Enterprise Edition 11.2.0.3.0

Red Hat Directory Server LDAP v3

WebSphere Application Server 8

Load Balancer LINUX Virtual Server (LVS)

NetAct 15 Software Installation with RedHat Package Manager

1 © Nokia Solutions and Networks 2015

2.1.2 Environment Variables

$ETCROOT /etc/opt/nokia/oss global disk

$VARROOT /var/opt/nokia/oss root disk

2.2 NetAct Storage

HP Blade 1 HP Blade 3 HP Blade 5 HP Blade 6

VMGuest VMGuest VMGuest

DB disk DB-arch DB-redo Global PM Global Backup

1 © Nokia Solutions and Networks 2015

2.2.2 NetAct Disks Configuration

HP Blade 1 HP Blade 3 HP Blade 5 HP Blade 6

VMGuest VMGuest VMGuest

DB disk DB-arch DB-redo Global PM Global Backup

1 © Nokia Solutions and Networks 2015

1 © Nokia Solutions and Networks 2015

 Binaries: /opt/oss/bin and /opt/nokia/oss/bin

 Installation time templates: /opt/oss/install/template

 Installation time configuration files: /opt/oss/install/conf

 Log files: /var/log, /var/opt/nokia/oss/log

 Static configuration files: /opt/oss/<subsystem>/conf

 Database data files: /d/db/oradata/oss