SYSMANHELP.HLB  —  CONFIGURATION  SET

1  –  CLUSTER_AUTHORIZATION

    Modifies security data in a local area cluster.

    Requires SYSPRV privilege.

    Format

      CONFIGURATION SET CLUSTER_AUTHORIZATION

1.1  –  Qualifiers

1.1.1    /GROUP_NUMBER

       /GROUP_NUMBER=[n]

    Specifies the cluster group number that is recorded in
    SYS$SYSTEM:CLUSTER_AUTHORIZE.DAT. A group number uniquely
    identifies each local area cluster on a single Ethernet. This
    number must be in the range from 1 to 4095 or 61440 to 65535.

1.1.2    /PASSWORD

       /PASSWORD=password

    Specifies a password for cluster access. A password consists of
    1 to 31 characters, including alphanumeric characters, dollar
    signs, and underscores. A password provides a second level of
    validation to ensure the integrity of individual clusters on the
    same Ethernet that accidentally use identical group numbers. A
    password also prevents an intruder who discovers the group number
    from joining the cluster.

1.2  –  Description

    The CONFIGURATION SET CLUSTER_AUTHORIZATION command modifies the
    group number and password of a local area cluster, as recorded
    in SYS$SYSTEM:CLUSTER_AUTHORIZE.DAT. If your configuration has
    multiple system disks, SYSMAN automatically updates each copy
    of CLUSTER_AUTHORIZE.DAT, provided the environment is defined as
    a cluster (SET ENVIRONMENT/CLUSTER). For more information about
    CLUSTER_AUTHORIZE.DAT, see VSI OpenVMS Cluster Systems.

                                 CAUTION

       If you change either the group number or the password, you
       must reboot the entire cluster.

    The file CLUSTER_AUTHORIZE.DAT is initialized during execution
    of CLUSTER_CONFIG.COM and maintained through SYSMAN. Under
    normal conditions, altering records in the CLUSTER_AUTHORIZE.DAT
    file interactively is not necessary. To protect the integrity
    of the cluster membership use the CONFIGURATION SET CLUSTER_
    AUTHORIZATION command.

1.3  –  Example

  SYSMAN> SET ENVIRONMENT/CLUSTER/NODE=NODE21
  SYSMAN> SET PROFILE /PRIVILEGES=SYSPRV
  SYSMAN> CONFIGURATION SET CLUSTER_AUTHORIZATION/PASSWORD=GILLIAN
  %SYSMAN-I-CAFOLDGROUP, existing group will not be changed
  %SYSMAN-I-GRPNOCHG, Group number not changed
  SYSMAN-I-CAFREBOOT, cluster authorization file updated.
  The entire cluster should be rebooted.

      The CONFIGURATION SET CLUSTER_AUTHORIZATION command in this
      example sequence modifies the cluster password. Note that
      the environment is defined to be a cluster, and the SYSPRV
      privilege is established before entering the CONFIGURATION SET
      CLUSTER_AUTHORIZATION command.

2  –  TIME

    Modifies the current system time.

    Requires OPER, LOG_IO, and SYSPRV privileges, and, in a cluster
    environment, SYSLCK privilege.

    Format

      CONFIGURATION SET TIME [time]

2.1  –  Description

    The CONFIGURATION SET TIME command enables you to reset the
    system time. Specify a time value using the following format:

    [dd-mmm-yyyy[:]] [hh:mm:ss.cc]

    You can also enter a delta time value. For more information about
    time formats, see the OpenVMS User's Manual.

    In an environment of individual nodes, SYSMAN sets the time to
    the specified value on each node. Without a time specification,
    SYSMAN sets the time according to the time-of-year clock on each
    node.

    In an OpenVMS Cluster environment, SYSMAN sets the time to the
    specified value on each node. If you do not specify a value,
    SYSMAN uses the time-of-year clock. In a local cluster, SYSMAN
    reads the clock on the node from which you are executing SYSMAN
    and assigns this value to all nodes in the cluster. In a remote
    OpenVMS Cluster, SYSMAN reads the clock on the target node in
    the cluster and assigns that value to all nodes. Note that the
    time-of-year clock is optional for some processors; for more
    information, see your processor handbook.

    SYSMAN uses special processing in an OpenVMS Cluster environment
    to ensure that all processors in the cluster are set to the same
    time. Because of communication and processing delays, it is not
    possible to synchronize clocks exactly. However, the variation
    is typically less than a few hundredths of a second. If SYSMAN
    cannot set the time to within one half second of the specified
    time, you receive a warning message that names the node that
    failed to respond quickly enough.

    As a result of slight inaccuracies in each processor clock,
    times on various members of a cluster tend to drift apart.
    The following procedure synchronizes system times in a cluster
    environment:

    $  SYNCH_CLOCKS:
    $  RUN SYS$SYSTEM:SYSMAN
           SET ENVIRONMENT/CLUSTER
           CONFIGURATION SET TIME
           EXIT
    $  WAIT 6:00:00
    $  GOTO SYNCH_CLOCKS

    The procedure sets the time on all cluster nodes to the value
    obtained from the local time-of-year clock, waits 6 hours, then
    resets the time for the cluster.

2.2  –  Example

  SYSMAN> SET ENVIRONMENT/NODE=(NODE21,NODE22,NODE23)
  SYSMAN> SET PROFILE /PRIVILEGE=LOG_IO
  SYSMAN> CONFIGURATION SET TIME 12:38:00

      The CONFIGURATION SET TIME command in this example sequence
      modifies the system time on NODE21, NODE22, and NODE23.
Close Help