- Server Configuration window

# Server Configuration window

Contents

This window supports the range of server configuration tasks. For instructions on how to add servers, see Add one or more HA servers.

Under Server Configuration, you can:

• | Add an object storage server. Click + Add Server or + Add More Servers.

• | View existing servers for all file systems.

• | View Server State: This indicator tells you the alert status for that server. A green check mark indicates that all is well with that server. A red exclamation mark indicates an active alert has been generated for this server; you can mouse over the exclamation mark to learn the cause of the alert. See View all status messages for more information.

• | View the Profile associated with each server. When you add a new server, you select the server profile for that server. The profile defines the role of that server. There are generally four server profiles available, however your installation may list more. The four common server profiles are:

▪ | Managed storage server

▪ | Monitored storage server

▪ | POSIX HSM Agent Node

▪ | Robinhood Policy Engine server

• | Determine LNet state for a given server. Possible LNet states are: LNet up, LNet down, and LNet unloaded.

• | Click on the server name (hostname) to open a Server Detail window to learn more about that server and access configuration options.

• | Under Actions, specific to each server, you can perform the following commands. These commands are used primarily to decommission servers. See Decommissioning a server for an MGT, MDT, or OST.

▪

Reboot: Initiate a reboot on this server. If this server is configured as the primary server of an HA pair, the file system will failover to the secondary server until this server is back online. The file system will then fail back to the primary server. If this is not configured as an HA server, then any file systems targets that rely on this server will be unavailable until rebooting is complete.

▪ | Shutdown: Initiate an orderly shutdown on this server. If this server is configured as the primary server of an HA pair, the file system will failover to the secondary server. If this is not configured as an HA server, then any file systems targets that rely on this server will be unavailable until this server is rebooted.

▪ | Remove: Remove this server. If this server is configured as the primary server of an HA pair, then the file system will failover to the secondary server.

▪ | Warning: If this is not configured as an HA server, then any file systems or targets that rely on this server will also be removed.

▪ | Power Off: Switch power off for this server. Any HA-capable targets running on the server will be failed-over to a peer. Non-HA-capable targets will be unavailable until power for the server is switched on again. This action is visible only if PDUs have been added and outlets assigned to servers.

▪ | Power On: Switch power on for this server. This action is visible only if PDUs have been added and outlets assigned to servers, and after the server has been powered-off at PDU.

▪ | Power Cycle: Switch power off and then back on again for this server Any HA-capable targets running on the server will be failed over to a peer. Non-HA-capable targets will be unavailable until the server has finished booting. This action is visible only if PDUs have been added and outlets assigned to servers.

▪ | Remove: Remove this server. If this server is configured as the primary server of an HA pair, then the file system will failover to the secondary server. If this not configured as an HA server, then any file systems or targets that rely on this server will also be removed.

▪ | Force Remove: This action removes the record for the storage server in the manager database, without attempting to contact the storage server. All targets that depend on this server will also be removed without any attempt to unconfigure them. Warning: You should only perform this action if the server is permanently unavailable.

Under Server Actions, you can perform the commands listed next. Note that these commands are bulk action commands. This means that when you click one of the following commands, you can then select which server(s) to perform this command on. You can enter a host name or host name expression in the file to generate a list of existing servers. You can chose Select All, Select None, or Invert Selection. At the far right, under Select Server, you can also select or deselect a server. After selecting the desired server(s), you can proceed to perform the command and it will be run on all selected servers.

• | Detect File Systems: Detect an existing file system to be monitored at the manager GUI.

• | Re-write Target Configuration: Update each target with the current NID for the server with which it is associated. This is necessary after making changes to server/target configurations and is done after rescanning NIDs. Also see Handling network address changes (updating NIDs).

•

Install Updates: When an updated release of Intel® Manager for Lustre* software is installed at the manager server, a notification is displayed at the manager GUI that updated software is also available for installation on a managed server or servers. This button become enabled. After clicking the Install Updates button, a list of servers (default: all) to be included in this update operation is displayed in the Update dialog. Clicking the Run button in this dialog will cause the updated packages to be installed on the managed servers.