OVNPM 1.5.2 - Performance Agent for NonStop Server Management Guide

Managing Distributed Servers 61
The DSN architecture displayed below shows two nodes on the EXPAND network, with the DSN server installed
on Node 1. Two additional processes are integrated, Distributed Navigator Server and a TCP communication
process TCPSN.
Figure 9-2 DSN Architecture
9-2-1 DSN (Web Interface) Installation Requirements
1. Before installing DSN distributed server, each node to be monitored must have the OVNPM product
installed and be part of an Expand Network.
NOTE: OVNPM is operational after every single installation. A user can gain access to OVNPM by
connecting to a local node to retrieve associated OVNPM data.
2. The user needs to select one of the EXPAND linked Nodes on which to install the DSN server. Only one
DSN Server is required per EXPAND network.
3. Remote Passwords between DSN nodes and other nodes must be set.
4. Expand security must allow OVNPM processes to open each other over the EXPAND network.
9-2-2 DSN Installation and Management
The VCONF utility must be used to configure DSN.
VCONF Option 3, Configure Distributed Servers generates the following data:
• DSN environment, which includes the name, CPU and priority of DSN processes. This information
is saved in the file DSNENV in the OVPMTACL subvolume.
• DSN configuration, which consists of the list of nodes. This information is saved in the file DSNCFG
in the OVPMCFG subvolume.
There are two OVNPM TACL Macros available for Managing (Starting/Stopping) the DSN Server.
• SV_START DSN <OVNPM TACL Macro – Starts Distributed Server Environment
• SV_STOP DSN <OVNPM TACL Macro – Stop Distributed Server Environment
NOTE: Once configured the command “sv_start subsys” will start all OVNPM applications, including
DSN.
Managing Distributed Servers