NET/MASTER Management Services (MS) System Management Guide

Continuous Availability
Introduction to Managing NonStop NET/MASTER MS
115414 NonStop NET/MASTER MS System Management Guide 1–13
Secure Access to Remote
Nodes
You can control every user’s ability to access a remote node. Users can only log on to
and otherwise use NonStop NET/MASTER MS systems to which they are defined. If
you allow a user to log on to remote systems, the user must have a user ID definition
record in each node that will be accessed.
Logging of User Activity Security management requires information about activities that may breach security.
Such information is usually contained in an activity log. NonStop NET/MASTER MS
logs many events about which security administrators want reports, including, but not
limited to, the following:
User logons and logoffs
Failed logon attempts
All commands invoked by all users
Failed attempts to invoke commands
Failed attempts to use external utilities
Changes in the UMS database, such as those required to either grant or deny user
access to features
An activity logging feature records all commands entered by NonStop NET/MASTER
MS users. The logging of activity assures accountability of command use. You use the
Activity Log Browse Facility to view messages in the log. You use the LOGPROC
NCL procedure to suppress messages, such as EMS messages, that you do not want to
record in it.
See Section 10, “Managing Activity Logs,” for additional information about the
activity log.
Continuous
Availability
NonStop NET/MASTER MS is designed for high availability. It can automatically
create and stop processes in accordance with fluctuations in workload and message
traffic. Several NonStop NET/MASTER MS processes usually run as process pairs,
while others usually run as persistent processes.
Processes that run as process pairs have a primary and backup process running in
separate CPUs. If the primary process of a pair fails, the related backup process takes
over immediately at the same point of execution. In the event of a failure, processes
that run as process pairs can continue operating without loss of service.
The following processes, which maintain and manage the NonStop NET/MASTER MS
processing environment, usually run as process pairs:
The NonStop NET/MASTER MS control process (NCP). This process manages all
processes in the NonStop NET/MASTER MS processing environment, and starts
and stops other processes within the processing environment as required.
Global memory manager (GMM) processes. These processes serve as a conceptual
repository of information accessed and shared by all NonStop NET/MASTER MS
processes.