| Document revision date: 30 March 2001 | |
![]() |
|
|
|
| Previous |
Network security should promote interoperability and uniform security approaches throughout networks. The following list shows three major areas of network security:
OpenVMS Cluster system managers should also ensure consistency in the
use of DECnet software for intracluster communication.
1.9.1 Mechanisms
Depending on the level of network security required, you might also want to consider how other security mechanisms, such as protocol encryption and decryption, can promote additional security protection across the cluster.
Reference: See the OpenVMS Guide to System Security.
1.10 Coordinating System Files
Follow these guidelines to coordinate system files:
| IF you are setting up... | THEN follow the procedures in... |
|---|---|
| A common-environment OpenVMS Cluster that consists of newly installed systems | OpenVMS System Manager's Manual to build these files. Because the files on new operating systems are empty except for the Digital-supplied accounts, very little coordination is necessary. |
| An OpenVMS Cluster that will combine one or more computers that have been running with computer-specific files | <REFERENCE>(build_uaf_upgrade) to create common copies of the files from the computer-specific files. |
In a common-environment cluster with one common system disk, you use a common copy of each system file and place the files in the SYS$COMMON:[SYSEXE] directory on the common system disk or on a disk that is mounted by all cluster nodes. No further action is required.
To prepare a common user environment for an OpenVMS Cluster system that includes more than one common VAX system disk or more than one common Alpha system disk, you must coordinate the system files on those disks.
Rules: The following rules apply to the procedures described in Table 1-4:
| Step | Action |
|---|---|
| 1 | Decide where to locate the SYSUAF.DAT and NETPROXY.DAT files. In a cluster with multiple system disks, system management is much easier if the common system files are located on a single disk that is not a system disk. |
| 2 | Copy SYS$SYSTEM:SYSUAF.DAT and SYS$SYSTEM:NETPROXY.DAT to a location other than the system disk. |
| 3 | Copy SYS$SYSTEM:RIGHTSLIST.DAT and SYS$SYSTEM:VMSMAIL_PROFILE.DATA to the same directory in which SYSUAF.DAT and NETPROXY.DAT reside. |
| 4 |
Edit the file SYS$COMMON:[SYSMGR]SYLOGICALS.COM
on each system disk and define logical names that specify the
location of the cluster common files.
Example: If the files will be located on $1$DJA16,
define logical names as follows:
|
| 5 |
To ensure that the system disks are mounted correctly with each reboot,
follow these steps:
$ @SYS$SYSDEVICE:[VMS$COMMON.SYSMGR]CLU_MOUNT_DISK.COM $1$DJA16: volume-label |
| 6 |
When you are ready to start the queuing system, be sure you have moved
the queue and journal files to a cluster-available disk. Any cluster
common disk is a good choice if the disk has sufficient space.
Enter the following command:
|
In OpenVMS Cluster systems on the LAN and in mixed-interconnect clusters, you must also coordinate the SYS$MANAGER:NETNODE_UPDATE.COM file, which is a file that contains all essential network configuration data for satellites. NETNODE_UPDATE.COM is updated each time you add or remove a satellite or change its Ethernet or FDDI hardware address. This file is discussed more thoroughly in <REFERENCE>(MAINTAIN_SATELLITE).
In OpenVMS Cluster systems configured with DECnet for OpenVMS software,
you must also coordinate NETNODE_REMOTE.DAT, which is the remote node
network database.
1.11 System Time on the Cluster
When a computer joins the cluster, the cluster attempts to set the joining computer's system time to the current time on the cluster. Although it is likely that the system time will be similar on each cluster computer, there is no assurance that the time will be set. Also, no attempt is made to ensure that the system times remain similar throughout the cluster. (For example, there is no protection against different computers having different clock rates.)
An OpenVMS Cluster system spanning multiple time zones must use a
single, clusterwide common time on all nodes. Use of a common time
ensures timestamp consistency (for example, between applications,
file-system instances) across the OpenVMS Cluster members.
1.11.1 Setting System Time
Use the SYSMAN command CONFIGURATION SET TIME to set the time across the cluster. This command issues warnings if the time on all nodes cannot be set within certain limits. Refer to the OpenVMS System Manager's Manual for information about the SET TIME command.
|
| privacy and legal statement | ||
| 4477STARTUP_002.HTML | ||