AppLogic 2.7/2.8 Documentation The latest production release is AppLogic 3.0.30
Server Management Commands
The following commands are supported:
list
| Description: | List servers |
| Syntax: | server list [--batch [--extended] ] [--verbose] [--map] |
| Arguments: | --batch | Display output in UDL format |
| --verbose | Display all server information in the list |
| --extended | Include extended server information - only valid if --verbose is specified |
| --map | Display list of components running on each server |
| Examples: | server list - List all servers of the grid. |
| Notes: | A specification of the output of this command can be found here. |
Typical Output
Name State CPU Mem(MB) BW (Mbps) Role
Alloc Free Alloc Free Alloc Free
srv1 up 0.14 7.76 448 30841 14 1986 primary
srv2 up 0.00 8.00 0 31802 0 2000 secondary
info
| Description: | Retrieve detailed information for a specific server. |
| Syntax: | server info name [ --batch ] [--extended] [ --map ] |
| Arguments: | name | Name of server for which to retrieve information. |
| --batch | Display information in UDL format |
| --extended | Display extended server information |
| --map | Display list of components running on the server |
| Examples: | server info srv1 - Display information for 'srv1' |
| Notes: | A specification of the output of this command can be found here. |
Typical Output
Name : srv1
State : up
HA Role : primary
--- CPU Information ---
Type : Intel(R) Xeon(R) CPU E5320 @ 1.86GHz
Frequency : 1861 Hz
Bogomips : 3725
Load : 0.49
--- Resource Information ---
Resource Count Total Reserved Alloc Service Free
--------------------------------------------------------------------------------
CPU 2 8 0.10 0.14 - 7.76
MEM - 32.00 GB 1.44 GB 448.00 MB - 30.12 GB
BW - 2.00 Gbps 0.00 Mbps 14.00 Mbps - 1.99 Gbps
DISK 1 1.59 TB 10.00 GB 82.62 GB - 1.50 TB
reboot
| Description: | Reboot a server |
| Syntax: | server reboot name [ reason=reason ] [ --kill] [ --force ] |
| Arguments: | name | Name of the server to reboot. If name is "--all", then all servers are rebooted. |
| reason | Reason why server is being rebooted |
| --kill | Force reboot of server even though there may be an application currently running on the server. This option is supported in AppLogic 2.8.x+. |
| --force | Skip user verification. Prior to AppLogic 2.8.x, this option had the same functionality as the --kill option. |
| Examples: | server reboot srv1 - Reboot 'srv1' |
| server reboot srv2 reason=”BIOS Update” - reboot 'srv2' |
| server reboot --all - reboot all servers |
| Notes | This command will fail if there is an application currently running on the server (a volume is in use, or a component on the server) and if the --kill option is not specified. |
| Prior to AppLogic 2.8.x, this command will fail if there is an application currently running on the server (a volume is in use, or a component on the server) and if the --force option is not specified. |
shutdown
| Description: | Shutdown a server |
| Syntax: | server shutdown name [ reason=reason ] [ --kill ] [ --force ] |
| Arguments: | name | Name of the server to shutdown. If name is "--all", then all servers are shutdown. |
| reason | Reason why server is being shutdown |
| --kill | Force shutdown of server even though there may be an application currently running on the server. This option is supported in AppLogic 2.8.x+. |
| --force | Skip user verification. Prior to AppLogic 2.8.x, this option had the same functionality as the --kill option. |
| Examples: | server shutdown srv3 reason="Memory upgrade" - Shutdown 'srv3' |
| Notes | This command will fail if there is an application currently running on the server (a volume is in use, or a component on the server) and if the --kill option is not specified. |
| Prior to AppLogic 2.8.x, this command will fail if there is an application currently running on the server (a volume is in use, or a component on the server) and if the --force option is not specified. |
enable
| Description: | Enable a server for scheduling |
| Syntax: | server enable name |
| Arguments: | name | Name of the server to enable. If name is "--all", then all servers that are currently disabled are enabled. |
| Examples: | server enable srv1 - Enable 'srv1' for scheduling |
| server enable --all - Enable all servers for scheduling |
| Notes: | No error will be displayed when this command is executed on a server that is already enabled. |
| Enabling a server, even if it is already enabled, resets the server's flapping counter that is maintained by AppLogic. The server flapping counter is the number of server failures that have occurred within the last 24 hours. Once a server has failed 3 times in a 24 hour period, AppLogic automatically disables the server. |
disable
| Description: | Disable a server for scheduling |
| Syntax: | server disable name |
| Arguments: | name | Name of the server to disable. If name is "--all", then all servers are disabled. |
| Examples: | server disable srv1 - Disable srv1 for scheduling |
| server disable --all - Disable all servers for scheduling |
| Notes: | This command does not affect the operation of appliances and volumes that are already on the server; it just prevents the placement of new appliances and volumes on that server. |
set
| Description: | Set the server’s role in the grid for controller high-availability |
| Syntax: | server set name role=role [ --force ] |
| Arguments: | name | Name of the server |
| role | Server's role. May be one of the following:
primary - Server that is currently running the AppLogic grid controller
secondary - Server that may run the AppLogic grid controller in case of a controller server failure
none - Server will never run the AppLogic grid controller and does not participate in controller HA |
| --force | Skip the user verification prompt when setting a new primary server for a grid |
| Examples: | server set srv2 role=primary - set srv2's role to primary |
| server set srv4 role=secondary - set srv4's role to secondary |
| Notes: | If a server is assigned to be the new primary server for a grid, the grid controller is immediately migrated to the new primary server. The old primary server will be assigned the previous role of the new primary server (the roles are swapped). |
| The only way to change the role of a primary server is to assign a different server in the grid as the new primary server (users are not allowed to explicitely change a server's role from primary to either none or secondary). |
| A grid must have one and only one primary server; a grid may have from 0 to 7 secondary servers. By default upon grid installation/upgrade, a grid with 3 or more servers has 1 primary server and 2 secondary servers. Additional secondary servers may be assigned using this CLI command. |
| In order for a grid to recover from a controller server failure, there must be at least 2 secondary servers up and running at the time of the server failure. If this requirement is not met (e.g., there is only one secondary server at the time of the primary server failure), the grid controller remains down and requires grid maintainer intervention in order to restore the grid controller to an operational state. If this type of controller failure is encountered, please contact your service provider for assistance. |
| If there are not enough secondary servers in a grid to recover from a future primary server failure, AppLogic notifies the user by posting a grid dashboard message. |
| Please see the AppLogic High-Availability reference for more information regarding server roles and controller HA. |
power_on
| Description: | Power on a server |
| Syntax: | server power_on name |
| Arguments: | name | Name of the server to power on. If name is "--all", then power on all servers that are currently powered down. |
| Examples: | server power_on srv3 - power on 'srv3' |
| Notes | None. |
power_off
| Description: | Power off a server |
| Syntax: | server power_off name [ reason=reason ] [ --kill ] [ --force ] |
| Arguments: | name | Name of the server to power off. If name is "--all", then all servers are powered off. |
| reason | Reason why server is being powered off |
| --kill | Force power off of server even though there may be an application currently running on the server. This option is supported in AppLogic 2.8.x+. |
| --force | Skip user verification. Prior to AppLogic 2.8.x, this option had the same functionality as the --kill option. |
| Examples: | server power_off srv3 reason="Memory upgrade" - Power off 'srv3' |
| Notes | This command will fail if there is an application currently running on the server (a volume is in use or a component is running on the server) and if the --kill option is not specified. |
| Prior to AppLogic 2.8.x, this command will fail if there is an application currently running on the server (a volume is in use, or a component on the server) and if the --force option is not specified. |
power_cycle
| Description: | Power cycle a server |
| Syntax: | server power_cycle name [ reason=reason ] [ --kill ] [ --force ] |
| Arguments: | name | Name of the server to power cycle. If name is "--all", then all servers are power cycled. |
| reason | Reason why server is being power cycled |
| --kill | Force power cycle of server even though there may be an application currently running on the server. This option is supported in AppLogic 2.8.x+. |
| --force | Skip user verification. Prior to AppLogic 2.8.x, this option had the same functionality as the --kill option. |
| Examples: | server power_cycle srv3 - Power cycle 'srv3' |
| Notes | This command will fail if there is an application currently running on the server (a volume is in use or a component is running on the server) and if the --kill option is not specified. |
| Prior to AppLogic 2.8.x, this command will fail if there is an application currently running on the server (a volume is in use, or a component on the server) and if the --force option is not specified. |
-- BeckyH - 23 May 2006
Copyright © CA 2005-2011. All Rights Reserved.
AppLogic27 Web