The Server Properties dialog is available from the Edit Menu or from a server popup menu. This dialog displays the properties for a particular server. When accessed from the Edit menu, you can select the server. The Server Properties dialog updates itself when the selected server changes.

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.

  • Name. Name of the selected server.
  • 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 for Windows task.
    • Operator – the user can monitor LifeKeeper for Windows resource and server status, and can bring resources in service and take them out of service.
    • Guest – the user can monitor LifeKeeper for Windows resource and server status.
  • 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.
  • ShutdownStrategy (editable). The setting that governs whether or not resources which are in service are switched over to a backup server in the cluster when a server is shut down. The setting “Switch Over Resources” indicates that resources will be brought in service on a backup server in the cluster. The setting “Do not Switch Over Resources” indicates that resources will not be brought in service on another server in the cluster.
  • Server Name. Automatic failover capabilities from the local server to other servers in the cluster may be configured here. All servers in the cluster should be operational (i.e. at least one LifeKeeper for Windows comm path must be active) as inactive servers are not listed. The name of each active server in the cluster is listed, excluding the local server. For each server, two types of failover capabilities are configurable. By default, all failover capabilities are enabled.
    • Disable Resource Failover – Select the remote server(s) to be disqualified as a backup server for any failed resource hierarchy on the local server. When disabled, the designated server is disqualified as a failover site if a local resource fails. Unselect to re-enable automatic failover capabilities.
    • Disable System Failover – Select the remote server(s) to be disqualified as a backup server for a complete failure of the local server. When disabled, the designated server is disqualified as a failover site if the local server completely fails. Unselect to re-enable automatic failover capabilities.

Note: If all remote servers are disabled for resource failovers, then the failed resource will be marked as “Failed” and no additional quick check or deep check monitoring will be performed for the failed resource. However, the failed resource as well as other dependent resources in the hierarchy will not be removed from service and no failover will be attempted.

  • Server. The server name of the other server to which the communication path is connected in the LifeKeeper for Windows cluster.
  • Type. The type of comm path between the server in the list and the server specified in the Server field (TCP/IP or Shared Disk).
  • State. State of the comm path in the LifeKeeper Configuration Database (LCD). These are the possible comm path state values:
    • ALIVE – functioning normally
    • DEAD – no longer functioning normally
    • UNKNOWN – state could not be determined. The GUI server may not be available.
  • Address/Device. The IP address or device name that this comm path uses.
  • Comm Path Status. Summary comm path status determined by the GUI based on the state of the comm paths in the LifeKeeper Configuration Database (LCD). These are the possible comm 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, or only one comm path exists.
    • DEGRADED – one or more redundant comm paths to a given server are dead
    • NONE DEFINED – no comm paths defined

  • 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, volume, TCP/IP, SQL…)
  • 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 for Windows startup sequence. Resources in this state are not under LifeKeeper for Windows protection.
    • UNKNOWN – Resource state could not be determined. The GUI server may not be available.

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment