Server Properties Dialog

The Server Properties dialog is available from a server context menu or from the Edit menu. This dialog displays the properties for a particular server. The properties for the server will also be displayed in the properties panel if it is enabled.

The three tabs of this dialog are described below. The OK button applies any changes that have been made and then closes the window. The Apply button applies any changes that have been made. The Cancel button closes the window without saving any changes made since Apply was last clicked.

General Tab

• • Name. Name of the selected server.
    

• • State. Current state of the server. These are the possible server state values:
    

• º

ALIVE – server is available.

• º

DEAD – server is unavailable.

• º

UNKNOWN – state could not be determined. The GUI server may not be available.

• • Permission. The permission level of the user currently logged into that server. These are the possible permission values:
    

• º

Administrator – the user can perform any LifeKeeper task.

• º

Operator – the user can monitor LifeKeeper resource and server status, and can bring resources in service and take them out of service.

• º

Guest – the user can monitor LifeKeeper resource and server status.

• • Shutdown Strategy. (editable if the user has Administrator permission) The setting that governs whether or not resources are switched over to a backup server in the cluster when a server is shutdown. The setting “Switchover Resources” indicates that resources will be brought in service on a backup server in the cluster. The setting “Do not Switchover Resources” indicates that resources will not be brought in service on another server in the cluster.
    

• • Failover Strategy. The setting allows you to require the confirmation of failovers from specific systems in the LifeKeeper cluster. It is only available to LifeKeeper administrators. Operators and guests will not be able to see it. By default, all failovers proceed automatically with no user intervention. However, once the confirm failover flag is set, failovers from the designated system will require confirmation by executing the command: lk_confirmso -y system. The failover may be blocked by executing the command: lk_confirmso -n system. The system will take a pre-programmed default action unless one of these commands is executed within a specified interval. Two flags in the /etc/default/LifeKeeper file govern this automatic action.
    

• º

CONFIRMSODEF

This specifies the default action. If set to “0”, the default action is to proceed with failover. If set to “1”, the default action is to block failover.

• º

CONFIRMSOTO

This is set to the time in seconds that LifeKeeper should wait before taking the default action.

CommPaths Tab

• • Server. The server name of the other server the communication path is connected to in the LifeKeeper cluster.
    

• • Priority. The priority determines the order by which communication paths between two servers will be used. Priority 1 is the highest and priority 99 is the lowest.
    

• • State. State of the communications path in the LifeKeeper Configuration Database (LCD). These are the possible communications path state values:
    

• º

ALIVE – functioning normally.

• º

DEAD – no longer functioning normally.

• º

UNKNOWN – state could not be determined. The GUI server may not be available.

• • Type. The type of communications path, TCP (TCP/IP) or TTY, between the server in the list and the server specified in the Server field.
    

• • Address/Device. The IP address or device name that this communications path uses.
    

• • Comm Path Status. Summary communications path status determined by the GUI based on the state of the communications paths in the LifeKeeper Configuration Database (LCD). These are the possible communications path status values displayed below the detailed text in the lower panel:
    

• º

NORMAL – all comm paths functioning normally.

• º

FAILED – all comm paths to a given server are dead.

• º

UNKNOWN – comm path status could not be determined. The GUI server may not be available.

• º

WARNING – one or more comm paths to a given server are dead.

• º

DEGRADED – one ore more redundant comm paths to a given server are dead.

• º

NONE DEFINED – no comm paths defined.

Resources Tab

• • Name. The tag name of a resource instance on the selected server.
    

• • Application. The application name of a resource type (gen, scsi, …)
    

• • Resource Type. The resource type, a class of hardware, software, or system entities providing a service (for example, app, filesys, nfs, device, disk,…)
    

• • State. The current state of a resource instance:
    

• º

ISP – In-service locally and protected.

• º

ISU – In-service locally, but local recovery will not be attempted.

• º

OSF – Out-of-service, failed.

• º

OSU – Out-of-service, unimpaired.

• º

ILLSTATE – Resource state has not been initialized properly by the resource initialization process which is run as part of the LifeKeeper startup sequence. Resources in this state are not under LifeKeeper protection.

• º

UNKNOWN – Resource state could not be determined. The GUI server may not be available.

Copyright © 2024 SIOS TECHNOLOGY CORP.