Name
[Windows Manager]
Installation_folder\SVROR\Manager\bin\rcxadm server - Managed server operations
[Linux Manager]
/opt/FJSVrcvmr/bin/rcxadm server - Managed server operations
BasicFormat
rcxadm server start -name resource [-nowait]
rcxadm server stop -name resource [-force] [-nowait]
rcxadm server restart -name resource [-force] [-nowait]
rcxadm server switchover -name resource [-spare spare_server] [-nowait]
rcxadm server failback -name resource [-nowait]
rcxadm server takeover -name resource [-nowait]
rcxadm server list [{[-type {physical|vmguest [-server_role]|all [-server_role]}] | [-spare] | [-bootagt] | [-target_disk]} ]
rcxadm server migrate -name guest_name -to vmhost [-mode {live|cold}] [-nowait]
rcxadm server migrate -home [-name vmhost] [-nowait]
rcxadm server set -name resource -attr vmm_mode={maintenance|active}
rcxadm server set -name resource -attr {vmm_mode={maintenance|active}|vmware.maintenance={maintenance|active}} [VMware]
rcxadm server set -name resource -attr vmm_mode={maintenance|active|maintenance_with_move}[Hyper-V] [Citrix Xen]
rcxadm server set -name resource -attr bootagt={dos|winpe}
rcxadm server set -name resource -attr server_role={none|manager}
rcxadm server set -name resource -attr target_disk=disk_number
rcxadm server unset -name resource -target_disk
rcxadm server show -name resource -disk
rcxadm server collect -name resource -disk [-nowait]
rcxadm server backup -name resource -attr os=solaris (when using SPARC M10/M12)Information
rcxserver is an abbreviated form of the rcxadm server command. Both forms provide the same subcommands and options, and produce the same results.
Point
[VMware]
There are following two formats of the command options for setting and releasing the VM maintenance mode of VM hosts:
rcxadm server set -name resource -attr vmm_mode=maintenance|active
rcxadm server set -name resource -attr vmware.maintenance=maintenance|active
Format b is only provided to support ServerView Resource Coordinator VE V2.1.0.
As this format may not be provided in future versions, it is recommended to use method a. if you are starting to use Resource Orchestrator.
ExtendedFormat
rcxadm server start -name resource [-nowait]
rcxadm server stop -name resource [-force] [-nowait]
rcxadm server restart -name resource [-force] [-nowait]
rcxadm server switchover -name resource [-spare spare_server] [-nowait]
rcxadm server failback -name resource [-nowait]
rcxadm server takeover -name resource [-nowait]
rcxadm server list [{[-type {physical|vmguest [-server_role]|all [-server_role]}] | [-spare] | [-bootagt] | [-target_disk]} ]
rcxadm server migrate -name guest_name -to vmhost [-mode {live|cold}] [-nowait]
rcxadm server migrate -home [-name vmhost] [-nowait]
rcxadm server set -name resource -attr vmm_mode={maintenance|active}
rcxadm server set -name resource -attr {vmm_mode={maintenance|active}|vmware.maintenance={maintenance|active}} [VMware]
rcxadm server set -name resource -attr vmm_mode={maintenance|active|maintenance_with_move}[Hyper-V] [Citrix Xen]
rcxadm server set -name resource -attr bootagt={dos|winpe}
rcxadm server set -name resource -attr server_role={none|manager}
rcxadm server set -name resource -mode {active|maintenance}
rcxadm server set -name resource -attr target_disk=disk_number
rcxadm server unset -name resource -target_disk
rcxadm server show -name resource -disk
rcxadm server collect -name resource -disk [-nowait]
rcxadm server backup -name resource -attr os=solaris (when using SPARC M10/M12)Information
rcxserver is an abbreviated form of the rcxadm server command. Both forms provide the same subcommands and options, and produce the same results.
Point
[VMware]
There are following two formats of the command options for setting and releasing the VM maintenance mode of VM hosts:
rcxadm server set -name resource -attr vmm_mode=maintenance|active
rcxadm server set -name resource -attr vmware.maintenance=maintenance|active
Format b is only provided to support ServerView Resource Coordinator VE V2.1.0.
As this format may not be provided in future versions, it is recommended to use method a. if you are starting to use Resource Orchestrator.
Description
rcxadm server is the command used to control server resources. This function provides the following functionality:
Display of server statuses (physical OS, VM host, or VM guest)
Startup, shutdown, or restart of a designated server (physical server, physical OS, VM host, or VM guest)
Switchover, failback, or takeover of a designated server (physical OS or VM host)
VM guest migration
VM maintenance mode settings for VM hosts
Migration to VM Home Position
Change the boot agent of the specified server (physical server)
Collection and display of the disk information of the specified server (physical server)
Configure and display of the image operation of the target disk of the specified server (physical server)
Saving of OVM for SPARC configuration information as XML files
Setting and releasing of maintenance mode of a specified server (a physical server/a physical server already allocated to an L-Server)
For a physical server already allocated to an L-Server, only setting and releasing of maintenance mode is possible.
Setting of the server role for VM guests
When stopping or restarting a VM host, any VM guests that are running will also be stopped.
Verify that stopping the affected VM guests will not cause any problems before stopping or restarting a VM host.
For details on the switchover, failback and takeover operations, refer to "Chapter 18 Settings for Server Switchover" in the "User's Guide VE".
For details on VM guest migrations, refer to "15.1 Migration of VM Guests between Servers" in the "User's Guide VE".
For details on VM maintenance mode settings, refer to "15.2 VM Maintenance Mode of VM Hosts" in the "User's Guide VE".
For details on server role settings of VM guests, refer to "9.10 Changing Server Roles" in the "User's Guide VE".
Subcommands
Starts the target server (physical server, physical OS, VM host, or VM guest).
Stops the target server (physical server, physical OS, VM host, or VM guest).
Restarts the target server (physical server, physical OS, VM host, or VM guest).
Switches over the target server (physical OS or VM host) with one of its spare servers.
Switches back a server in switchover state (physical OS or VM host). The spare server that was switched over with is stopped, and the operating system will be restarted on the primary server.
Sets a post-switchover configuration as final, and allows the spare server to take over the role of the original primary server (physical OS or VM host). After takeover, both servers exchange their roles: the original spare server becomes the new primary server, while the original primary server becomes the new spare server.
Displays all registered servers (physical OS's, VM hosts, and VM guests).
The following properties are displayed for each server (when no options are specified).
Item Name | Description |
|---|---|
PHYSICAL_SERVER | Physical server name |
SERVER | Server name (physical OS or VM host) |
ADMIN_IP | Admin LAN IP address |
STATUS | Server status Displays one of the following:
For an explanation of possible server statuses, refer to "11.2 Resource Status" in the "Operation Guide VECE". |
MAINTENANCE | Current maintenance mode
For details on the maintenance mode, refer to "Appendix C Maintenance Mode" in the "User's Guide VEfor Infrastructure Administrators (Resource Management) CE". |
Migrates a VM guest to a VM host on a different physical server.
Sets or releases VM maintenance mode for a given VM host.
Change the boot agent used when manipulating images.
Sets the server role of a VM guest.
Configures the image operation target disk.
Releases the configuration of the image operation target disk.
Displays the information of a disk on which image operations can be performed.
Collects the information of a disk on which image operations can be performed.
Restarts the target server (physical server, physical OS, VM host, or VM guest) to acquire the disk information.
Saves configuration information of OVM for SPARC as XML files. When a server is powered on and its status is normal, its configuration information can be saved as an XML file.
XML files of OVM configuration information are saved in the following location on the control domain.
[Control Domain]
/etc/opt/FJSVrcvat/config
ovm_config.xml
Options
The following option can be specified for subcommands other than the list subcommand:
Specify the name of the target server in resource.
The following option can be specified when using subcommands other than the list, set, unset, or, show subcommand:
Use this option to return directly to the command prompt without waiting for the command to complete its execution.
The following option can be specified for the stop and restart subcommands:
Use this option to forcibly stop or restart a server without shutting down its operating system.
The following option can be specified for the switchover subcommand:
This defines the spare server (physical server) to be switched over with. If omitted, an appropriate server will be automatically selected from the list of spare servers already assigned to the target server.
The following options can be specified for the list subcommand:
This defines the type of server (physical servers, VM guests, all servers) to be listed up.
The following properties are displayed for each server. The option column shows the relationship between displayed properties and the option given in -type ("always" in the table below designates properties that are always displayed, independently from the option given in -type).
Item Name | Description | Options |
|---|---|---|
PHYSICAL_SERVER | Physical server name | always |
SERVER | Server name (for a Physical OS, VM host, or VM guest) | always |
TYPE | Server type Displays one of the following:
| physical all |
VM_HOST | VM host name For a VM guest, this shows the name of the VM host on which this VM guest operates. | vmguest all |
ADMIN_IP | Admin LAN IP address | always |
STATUS | Server status Displays one of the following:
For an explanation of possible server statuses, refer to "11.2 Resource Status" in the "Operation Guide VECE". | always |
MAINTENANCE | Current maintenance mode
For details on the maintenance mode, refer to "Appendix C Maintenance Mode" in the "User's Guide VEfor Infrastructure Administrators (Resource Management) CE". | physical all |
SERVER_ROLE | Server role of the VM guest. One of the following is displayed:
| vmguest -server_role all -server_role |
When using spare servers, this shows the spare server(s) (physical server) assigned to each server.
The following properties are displayed for each server.
Item Name | Description |
|---|---|
SERVER | Server name (physical OS or VM host) |
PRIMARY | Primary server Name of the physical server that will be switched over with a spare server during a server switchover. |
SPARE | Spare server Name of the spare server (switchover destination) assigned to the primary server. |
VLAN_SWITCH (*) | Network reconfiguration flag This flag defines whether network settings will be reconfigured during a server switchover.
|
AUTO_SWITCH | Auto-Recovery flag This flag defines whether Auto-Recovery is enabled.
|
ACTIVE | Active server Displays the name of the currently active physical server. |
SWITCHOVER_STATE | Switchover state Displays the current switchover state. Displays one of the following:
|
* Note: When a LAN switch blade is in IBP mode or Converged Fabric mode, the details of settings are displayed in this parameter.
Displays the information about the boot agent used when manipulating images.
The following properties are displayed for each server.
Item Name | Description |
|---|---|
PHYSICAL_SERVER | Physical server name |
BOOT_AGENT | Set boot agent Displays one of the following:
|
Displays the information related to the image operation target disk.
The following properties are displayed for each server.
Item Name | Description |
|---|---|
PHYSICAL_SERVER | Physical server name |
DISK_NUMBER | Disk number of the configured image operation target disk
|
DISK_SIZE | Size of the image operation target disk
|
PARTITION_COUNT | Number of partitions that exist on the image operation target disk
|
When disk information collection, image operations, or switchover using the backup and restore method is performed, the values of DISK_NUMBER may be modified based on the latest disk recognition order acquired by Resource Orchestrator.
When disks that are the targets of operations cannot be checked, image operations are determined to be invalid by the pre-operation check of Resource Orchestrator, and the image operations cannot be performed. Perform collection of the disk information and configuration of the image operation target disk again.
When using this option, if the physical server is a SPARC Enterprise, the information is not output in the list.
The following options can be specified for the migrate subcommand:
Specify the name of the destination target VM guest in guest_name.
Specify the name of the destination VM host in vmhost.
The type of migration method to perform is given for mode.
Depending on the power state of the VM guest to migrate, only one of those types may be available. When omitted, the appropriate type will be chosen depending on the state of the VM guest.
The following values can be specified.
Performs a live migration: migration of an active (powered-on) VM guest.
Performs a cold migration: migration of an inactive (powered-off) VM guest.
The power status of the VM guest after migration will be the same as it was before migration.
[KVM]
When -mode cold is specified for migration of a powered-on VM guest, migration may fail.
In that case, power off the VM guest and perform migration, then wait for a while before powering it back on.
Specify when performing migration to the VM Home Position.
Specify the name of the operation target VM host in vmhost.
The following options can be specified for the set subcommand:
Sets VM maintenance mode for the VM host.
Releases VM maintenance mode for the VM host.
Sets VM maintenance mode for the target VM host and migrates the VM guest when set.
Changes the boot agent used when manipulating images to DOS or Windows PE.
When the managed server has the following configuration, this option must be specified before manipulating images to change the boot agent settings.
When using Red Hat Enterprise Linux 6 or the Red Hat Enterprise Linux 7 ext4 file system and one of the following conditions applies, it needs to be changed to Windows PE.
SAN boot environment using HBA address rename
Rack mount or tower servers have been registered with "Disabled" selected for "Association with server management software (ServerView)"
In a SAN boot environment using HBA address rename and where the following model or OS is used, it needs to be changed to Windows PE.
PRIMERGY BX960 S1
XenServer6 or later
This option cannot be specified for the following models:
SPARC M10/M12 or SPARC Enterprise
PRIMEQUEST
When configuring DOS as the boot agent, it is necessary to configure the Microsoft LAN Manager Module. Contact Fujitsu technical staff before manipulating images using DOS.
Sets the server role of a VM guest.
When Resource Orchestrator is operating on a VM guest, setting "manager" limits the operations that stop the manager of Resource Orchestrator.
This prevents the Resource Orchestrator manager from being stopped unintentionally due to incorrect operations.
In disk_number, specify the number of the disk configured as the image operation target disk.
An integer larger than 1 can be specified for the disk number.
Check which disk numbers can be specified using the rcxadm server show -name resource -disk command.
When using this option, it is only possible to specify the disk number of a physical server for which the disk information has been acquired in advance by execution of the rcxadm server collect -name resource -disk command.
When a backup of an admin server is restored, the actual disk configuration and the disk information may not match. Perform collection of the disk information and configuration of the image operation target disk again.
For resource, specify a server name to place into or release from maintenance mode.
Specify whether the server is to be placed into or released from maintenance mode.
Release maintenance mode.
Places into maintenance mode.
The following options can be specified for the unset subcommand:
Deletes the configuration of the image operation target disk for the specified server.
The following options can be specified for the show subcommand:
When the server is a physical server for which the disk information has already been acquired, the following information is displayed.
Number of disks (Number of Disk: 0 or larger)
Disk number (Equal to the number of disks, 1 or larger)
Disk name (Hardware display name)
Disk size unit: MByte
Number of partitions
Partition number (Equal to the number of partitions, 1 or larger)
Partition type
(One of PRIMARY, EXTENDED, LOGICAL, ESP, MSR, DATA, LINUXSWAP, WINRE, or UNKNOWN)
File systems of partitions
(One of FAT12, FAT16, NTFS, FAT32, LINUXSWAP, EXT2, EXT3, EXT4, DISKDUMP, REISERFS, VMFS, EXTENDED, or UNKNOWN)
Partition size
Usage area of partitions
When the disk information has not been acquired, no value is displayed.
The following options can be specified for the collect subcommand:
When a physical server is in the following configuration, it is necessary to acquire and configure the information of disks for which image operations are possible before starting image operations.
When using a SAN data disk environment with a built-in disk boot
This option can only be executed while the physical server is in maintenance mode, and stopped. Start the physical server to acquire the disk information from, and stop it after acquiring the disk information.
When performing update of a physical server for which the disk information has already been acquired, save the disk information acquired during the latest update.
This option cannot be specified for the following models:
SPARC Enterprise
The following option can be specified for the backup subcommand:
Specify the name of the VM host (control domain).
Sets Solaris for the target OS.
Requirements
One of the following permissions is required:
OS Administrator
Resource Orchestrator Privileged User
Admin server
Example
To display a list of registered servers and their properties
>rcxadm server list <RETURN> PHYSICAL_SERVER SERVER ADMIN_IP STATUS MAINTENANCE --------------- ------ -------- ------ ----------- blade01 WebServer01 192.168.1.4 normal ON rackserver01 AppServer01 192.168.1.2 normal OFF rackserver02 DBServer01 192.168.1.6 stop OFF rackserver03 DBServer02 192.168.1.7 normal ON |
To display spare server settings
>rcxadm server list -spare <RETURN> SERVER PRIMARY SPARE VLAN_SWITCH AUTO_SWITCH ACTIVE SWITCHOVER_STATE ------ ------- ----- ----------- ----------- ------ ---------------- Server1 blade1-1 blade1-9 ON ON blade1-9 failback running Server2 blade1-2 blade1-9,blade1-10 OFF ON blade1-2 normal |
To display a list of physical servers (including physical OS's and VM hosts)
>rcxadm server list -type physical <RETURN> PHYSICAL_SERVER SERVER TYPE ADMIN_IP STATUS MAINTENANCE --------------- ------ ---- -------- ------ ----------- blade1-1 Server1 native 192.168.3.121 stop ON blade1-10 - - 192.168.3.130 stop - blade1-2 Server2 native 192.168.3.122 normal OFF blade1-3 Server3 native 192.168.3.123 stop ON blade1-5 Server5 native 192.168.3.125 normal ON blade1-7 vmesx1 vm_host 192.168.3.127 normal OFF blade1-8 Server8 native 192.168.3.128 normal OFF blade1-9 - - 192.168.3.129 stop - |
To display a list of VM guests
>rcxadm server list -type vmguest <RETURN> PHYSICAL_SERVER SERVER VM_HOST ADMIN_IP STATUS --------------- ------ ------- ------------- ------ blade1-7 vm-1 vmesx1 192.168.3.127 normal blade1-7 vm-2 vmesx1 192.168.3.127 normal >rcxadm server list -type vmguest -server_role <RETURN> PHYSICAL_SERVER SERVER VM_HOST ADMIN_IP STATUS SERVER_ROLE --------------- ------ ------- ------------- ------ ------------ blade1-7 vm-1 vmesx1 192.168.3.127 normal manager blade1-7 vm-2 vmesx1 192.168.3.127 normal none |
To display a list of all server resources (including physical OS's, VM hosts, and VM guests)
>rcxadm server list -type all <RETURN> PHYSICAL_SERVER SERVER TYPE VM_HOST ADMIN_IP STATUS MAINTENANCE --------------- ------- ------- -------- ------------- ------ ----------- blade1-1 Server1 native - 192.168.3.121 stop ON blade1-10 - - - 192.168.3.130 stop - blade1-2 Server2 native - 192.168.3.122 normal OFF blade1-3 Server3 native - 192.168.3.123 stop ON blade1-5 Server5 native - 192.168.3.125 normal ON blade1-7 vmesx1 vm_host - 192.168.3.127 normal OFF blade1-7 vm-1 vm_guest vmesx1 192.168.3.127 normal OFF blade1-7 vm-2 vm_guest vmesx1 192.168.3.127 normal OFF blade1-8 Server8 native - 192.168.3.128 normal OFF blade1-9 - - - 192.168.3.129 stop - sparcm10-1 ovm vm_host - 192.168.3.131 normal OFF sparcm10-1 ovm-1 vm_guest ovm 192.168.3.131 normal OFF sparcm10-1 ovm-2 vm_host ovm 192.168.3.132 normal OFF sparcm10-1 ovm-2-1 vm_guest ovm-2 192.168.3.132 normal OFF >rcxadm server list -type all -server_role <RETURN> PHYSICAL_SERVER SERVER TYPE VM_HOST ADMIN_IP STATUS MAINTENANCE SERVER_ROLE --------------- ------- ------- -------- ------------- ------ ----------- ------------ blade1-1 Server1 native - 192.168.3.121 stop ON - blade1-10 - - - 192.168.3.130 stop - - blade1-2 Server2 native - 192.168.3.122 normal OFF - blade1-3 Server3 native - 192.168.3.123 stop ON - blade1-5 Server5 native - 192.168.3.125 normal ON - blade1-7 vmesx1 vm_host - 192.168.3.127 normal OFF - blade1-7 vm-1 vm_guest vmesx1 192.168.3.127 normal OFF manager blade1-7 vm-2 vm_guest vmesx1 192.168.3.127 normal OFF none blade1-8 Server8 native - 192.168.3.128 normal OFF - blade1-9 - - - 192.168.3.129 stop - - sparcm10-1 ovm vm_host - 192.168.3.131 normal OFF - sparcm10-1 ovm-1 vm_guest ovm 192.168.3.131 normal OFF none sparcm10-1 ovm-2 vm_host ovm 192.168.3.132 normal OFF - sparcm10-1 ovm-2-1 vm_guest ovm-2 192.168.3.132 normal OFF none |
To migrate an active VM guest
>rcxadm server migrate -name vm_guest01 -to vm_host02 -mode live <RETURN> |
To migrate an inactive VM guest
>rcxadm server migrate -name vm_guest01 -to vm_host02 -mode cold <RETURN> |
When displaying the information for the current boot agent
>rcxadm server list -bootagt <RETURN> PHYSICAL_SERVER BOOT_AGENT --------------- ---------- blade1-1 DOS blade1-10 Windows PE blade1-2 DOS |
When displaying the information of a disk on which image operations can be performed
>rcxadm server show -name blade1-1 -disk <RETURN>
Number of Disk: 2
Disk Number: 1
Disk Name: FUJITSU MBD2300RC SCSI Disk Device
Disk Size: 1902400
Number of Partition: 2
Partition Number: 1
Partition Type: PRIMARY
Partition Filesystem: EXT3
Partition Size: 1002400
Partition Usage: 81000
Partition Number: 2
Partition Type: LOGICAL
Partition Filesystem: EXT3
Partition Size: 900000
Partition Usage: 7500
Disk Number: 2
Disk Name: FUJITSU ETERNUS_DXL SCSI Disk Device
Disk Size: 100000
Number of Partition: 1
Partition Number: 1
Partition Type: EXTENDED
Partition Filesystem: EXT3
Partition Size: 100000
Partition Usage: 30000 |
When displaying the information of disk configured as the image operation target
>rcxadm server list -target_disk <RETURN> PHYSICAL_SERVER DISK_NUMBER DISK_SIZE PARTITION_COUNT --------------- ----------- ---------------- -------------- blade1-1 1 83710 0 blade1-10 - - - blade1-2 2 23014000 13 blade1-3 (lost) 234700 3 |
When saving the configuration information of OVM for SPARC as XML files
>rcxadm server backup -name m10-4s-1 -attr os=solaris <RETURN> |
Exit Status
This command returns the following values:
The command executed successfully.
An error has occurred.
Note
A VM guest can be configured to automatically start or stop whenever its VM host starts up or shuts down. This can be achieved by setting up the VM guest's startup and shutdown options in the server virtualization software used.
For more information, refer to the server virtualization software manual.
As a result of power operation being performed on a VM guest, an error may occur if the VM guest is moved to another VM host and processes executed.
Refer to "9.2.2 Functional Differences between Products" in the "Design Guide VE" for details.
VM guests should be properly configured in order to use the "stop" or "restart" subcommands.
Stopping or restarting a VM guest that was not properly configured will result in an error unless the -force option is specified.
Refer to "9.2.1 Configuration Requirements" in the "Design Guide VE" for details.
For PRIMEQUEST servers, the warning message will not be displayed, even if there is a chance that the switchover will not be correctly performed using Reserved SB settings.
If ServerView Deployment Manager is used on the admin LAN, the switchover and failback subcommands cannot be used if the managed servers match any of the following conditions.
For more details, refer to "B.2I.2 Co-Existence with ServerView Deployment Manager" in the "Setup Guide VECE".
Servers in local boot environments
Servers in SAN boot environments without VIOM or ISM profiles
The changes to the boot agent are valid while the physical server is registered. After reregistering the physical server, change the boot agent using the command if necessary.