- Server Detail window

# Server Detail window

Contents

Each Server Detail window contains the full extent of information for that server. To open a Server Detail window, click Configuration > Servers, and then click on the server of interest.

This window is divided into five sections:

• | Server Detail

• | Pacemaker configuration

• | Corosync configuration

• | LNet detail

• | NID configuration

## Server Detail

This section lists:

• | Address: This is the IP address or the node name.

• | State: The type of server, HA managed or unmanaged.

• | FQDN: Fully qualified domain name

• | Node name: The name previously assigned to this node.

• | Profile: Indicates the profile assigned to this server during the Add Server process, including the OS.

• | Boot time: Date of last boot

• | State changed: Date of last State change; see State above.

• | Alerts: Any alerts received pertinent to this server.

Click the Actions menu to access the following commands that are available for this server:

•

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: This will switch power off for this server. If this is a primary server to any targets, those targets will be failed-over to the secondary server. Non-HA-capable targets (targets not supported by a secondary server) 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 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.

## Pacemaker configuration

Pacemaker configuration and enabling is performed automatically by Intel® Manager for Lustre* software. However, an administrator may need to reset or configure Pacemaker when performing maintenance on a server, altering the server's configuration, or troubleshooting problems with Pacemaker.

Click the Actions menu to access the following commands:

• | Stop Pacemaker: This command stop Pacemakers. If this is a primary server, then failover to the secondary server occurs. The file system remains available but not in a high-availability state.

• | Unconfigure Pacemaker: This command stops and unconfigures Pacemaker. If this is a primary server, then failover to the secondary server occurs. The file system remains available but not in a high-availability state.

• | Configure Pacemaker: Visible if Pacemaker is unconfigured. This command configures Pacemaker, but does not start it. To start Pacemaker and restore this server to HA capability, click Start Pacemaker.

•

Start Pacemaker: Visible if Pacemaker is stopped or unconfigured. Start Pacemaker to restore this server to HA capability. If failover has occurred from this server to the backup server, then after starting Pacemaker, manually failback the affected target(s) to this primary server. To do this, open the Status window, locate any warnings for target(s) running on the secondary server (and served by this primary server) and under Actions, click Failback.

## Corosync configuration

Corosync configuration and enabling is performed automatically by Intel® Manager for Lustre* software. However, an administrator may need to reset or configure Corosync when performing maintenance on a server, altering the server's configuration, or troubleshooting problems with Corosync.

Click the Actions menu to access the following commands:

• | Stop Corosync: This command stops Corosync and also stops Pacemaker. If this is a primary server, then failover to the secondary server occurs. The file system remains available, but not in a high-availability state. Corosync must be restarted before Pacemaker can be started again.

• | Unconfigure Corosync: This command stops and unconfigures Corosync and also stops Pacemaker. If this is a primary server, then failover to the secondary server occurs. The file system remains available, but not in a high-availability state. Corosync must be restarted before Pacemaker can be started again.

• | Configure Corosync: Visible if Corosync is unconfigured. This command will configure Corosync, but not start it. To configure and start Corosync, click Start Corosync. After Corosync is started, you need to start Pacemaker.

• | Start Corosync: Visible if Corosync is stopped or unconfigured. After Corosync is started, you also need to start Pacemaker. If failover occurred from this server to the backup server, then after Corosync and Pacemaker are running, you need to manually failback the affected target(s) to this primary server. See Start Pacemaker, above.

Clicking Configure to change the mcast port number.

## LNet detail

LNet operations for a given server may need to be reset during maintenance. Doing so will take this server and any volumes it hosts offline, and depending on the server, will degrade or stop the file system.

Click the Actions menu to access the following commands:

• | Stop LNet: Shut down the LNet networking layer and stop any targets running on this server.

• | Unload LNet: If LNet is running, stop LNet and unload the LNet kernel module to ensure that it will be reloaded before any targets are started again.

• | Load LNet: Load the LNet kernel module for this server.

• | Start LNet: Start LNet.

## NID configuration

An administrator may need to reconfigure NIDs for a server when performing maintenance on a server, altering the server's configuration, or troubleshooting problems network interfaces. For each interface, you can set the network driver and assign the Lustre network. To be able to edit NID configuration, the file system first needs to taken offline. Perform these steps:

1. | At the menu bar, click Configuration > File Systems.

2. | For this listed file system, at the right under Actions, select Stop.

3. | Return to the Server Detail window for the server in question. Click Configuration > Servers. Click on the desired server.

4. | Under NID Configuration, click Configure.

5. | The IP address is not editable. At the Network Driver drop-down menu, the available driver types are dependent on the network interface. Select the appropriate driver.

6. | If you are ready to place the file system online again, click Configuration > File Systems. Then for this file system, under Actions, select Start.