ServerView Resource Orchestrator Virtual Edition V3.1.
Preface Resource Orchestrator Documentation Road Map The documentation road map for Resource Orchestrator is as shown below. Resource Orchestrator Documentation Road Map For information about the documents for Resource Orchestrator, refer to "Chapter 1 Documentation Road Map" in the "Design Guide VE". Purpose This manual provides an outline of the operation method of the ROR console provided by ServerView Resource Orchestrator (hereinafter Resource Orchestrator).
Chapter 9 Changing Resources Explains how to change settings for the admin server or resources registered on the admin server. Chapter 10 Configuring the Operating Environments of Managed Servers Explains how to install software to the registered managed servers and set up their operating environment. Chapter 11 Deleting Resources Explains how to delete resources.
[Red Hat Enterprise Linux] Sections related to Red Hat Enterprise Linux [Solaris] Sections related to Solaris [VMware] Sections related to VMware [Hyper-V] Sections related to Hyper-V [Xen] Sections related to Xen [KVM] Sections related to RHEL-KVM [Solaris Zones] Sections related to Solaris zones [OVM for x86] Sections related to Oracle VM Server for x86 [OVM for SPARC] Sections related to Oracle VM Server for SPARC [Physical Servers] Sections related to physical servers [VM host] Sect
When using Windows 32-bit (x86) C:\Program Files\Resource Orchestrator Abbreviations The following abbreviations are used in this manual: Abbreviation Products Windows Microsoft(R) Windows Server(R) 2012 Standard Microsoft(R) Windows Server(R) 2012 Datacenter Microsoft(R) Windows Server(R) 2008 Standard Microsoft(R) Windows Server(R) 2008 Enterprise Microsoft(R) Windows Server(R) 2008 R2 Standard Microsoft(R) Windows Server(R) 2008 R2 Enterprise Microsoft(R) Windows Server(R) 2008 R2 Datacenter Microsof
Abbreviation Products Windows PE Microsoft(R) Windows(R) Preinstallation Environment Linux Red Hat(R) Enterprise Linux(R) AS (v.4 for x86) Red Hat(R) Enterprise Linux(R) ES (v.4 for x86) Red Hat(R) Enterprise Linux(R) AS (v.4 for EM64T) Red Hat(R) Enterprise Linux(R) ES (v.4 for EM64T) Red Hat(R) Enterprise Linux(R) AS (4.5 for x86) Red Hat(R) Enterprise Linux(R) ES (4.5 for x86) Red Hat(R) Enterprise Linux(R) AS (4.5 for EM64T) Red Hat(R) Enterprise Linux(R) ES (4.
Abbreviation Products Oracle Enterprise Linux Release 5 Update 4 for x86_64 (64 Bit) Oracle Enterprise Linux Release 5 Update 5 for x86 (32 Bit) Oracle Enterprise Linux Release 5 Update 5 for x86_64 (64 Bit) Red Hat Enterprise Linux Red Hat(R) Enterprise Linux(R) AS (v.4 for x86) Red Hat(R) Enterprise Linux(R) ES (v.4 for x86) Red Hat(R) Enterprise Linux(R) AS (v.4 for EM64T) Red Hat(R) Enterprise Linux(R) ES (v.4 for EM64T) Red Hat(R) Enterprise Linux(R) AS (4.
Abbreviation Products Red Hat(R) Enterprise Linux(R) 5.3 (for Intel64) Red Hat(R) Enterprise Linux(R) 5.4 (for x86) Red Hat(R) Enterprise Linux(R) 5.4 (for Intel64) Red Hat(R) Enterprise Linux(R) 5.5 (for x86) Red Hat(R) Enterprise Linux(R) 5.5 (for Intel64) Red Hat(R) Enterprise Linux(R) 5.6 (for x86) Red Hat(R) Enterprise Linux(R) 5.6 (for Intel64) Red Hat(R) Enterprise Linux(R) 5.7 (for x86) Red Hat(R) Enterprise Linux(R) 5.7 (for Intel64) Red Hat(R) Enterprise Linux(R) 5.
Abbreviation Products Oracle Enterprise Linux Oracle Enterprise Linux Release 5 Update 4 for x86 (32 Bit) Oracle Enterprise Linux Release 5 Update 4 for x86_64 (64 Bit) Oracle Enterprise Linux Release 5 Update 5 for x86 (32 Bit) Oracle Enterprise Linux Release 5 Update 5 for x86_64 (64 Bit) Solaris Oracle Solaris10 05/09 (Update7) Media Pack Oracle Solaris11 11/11 Media Pack Oracle Solaris11.
Abbreviation Products ROR ServerView Resource Orchestrator ROR VE ServerView Resource Orchestrator Virtual Edition ROR CE ServerView Resource Orchestrator Cloud Edition Resource Coordinator Systemwalker Resource Coordinator Resource Coordinator VE ServerView Resource Coordinator VE Systemwalker Resource Coordinator Virtual server Edition Resource Orchestrator ServerView Resource Orchestrator Export Administration Regulation Declaration Documents produced by FUJITSU may contain technology contr
Month/Year Issued, Edition Manual Code November 2011, First Edition J2X1-7606-01ENZ0(00) December 2011, 1.1 J2X1-7606-01ENZ0(01) December 2011, 1.2 J2X1-7606-01ENZ0(02) February 2012, 1.3 J2X1-7606-01ENZ0(03) March 2012, 1.4 J2X1-7606-01ENZ0(04) April 2012, 1.
Contents Chapter 1 Login and Logout.....................................................................................................................................................1 Chapter 2 Home.......................................................................................................................................................................4 2.1 Editing the Home Messages..................................................................................................................
8.1 Changing Admin IP Addresses..........................................................................................................................................................57 8.2 Changing Port Numbers.....................................................................................................................................................................61 8.3 Changing the Maximum Number of System Image Versions...........................................................................
11.7 Deleting Admin LAN Subnets.........................................................................................................................................................91 11.8 Unregistering ETERNUS SF Storage Cruiser.................................................................................................................................91 Chapter 12 Pre-configuration for Resource Registration and Modification............................................................................
18.3 Changing Server Switchover Settings...........................................................................................................................................150 18.4 Canceling Server Switchover Settings...........................................................................................................................................150 Chapter 19 Collecting Power Consumption Data and Displaying Graphs............................................................................
Chapter 1 Login and Logout This chapter describes how to open and close the ROR console. Preparations Before opening the ROR console, be sure to read the following instructions and restrictions. - When accessing the ROR console, be sure to enable the Compatibility View in Internet Explorer. Select [View]-[Encoding] in Internet Explorer, and check if [Auto-Select] is checked. If [Auto-Select] is not checked, select it.
URL: https://Admin_server_IP_address:23461/ On a Windows admin server, the ROR console can also be opened by selecting [start]-[All Programs]-[Resource Orchestrator]-[ROR console]. Note - If the login screen is not displayed, confirm the following. - URL entered in address bar of the Web browser. - The proxy settings of the Web browser are correct. - The firewall settings on the admin server are correct.
Note - If the Web browser is closed without logging out first, user authentication may be skipped the next time Resource Orchestrator is accessed. In that case, users will be automatically logged in using the previously used session. It is advised that the users log out properly after using the ROR console or BladeViewer. - If the ROR console or BladeViewer has been opened simultaneously in several Web browser windows, those login sessions may be terminated.
Chapter 2 Home This chapter explains the ROR Console Home window. When the ROR Console is started, the Home window is displayed. Refer to "Chapter 1 Login and Logout" for information on how to start the ROR Console. The elements of the Home window are explained below. - Functions list The functions list displays the items that can be operated using ROR Console tabs. Click the triangle icon next to the Function list to toggle Display/Hide.
c. Set the following items: Schedule There is no specified format. When not displaying the date, leave this field blank. Enter up to 30 alphanumeric characters or symbols. Commas (",") cannot be used. Messages Enter up to 250 alphanumeric characters or symbols. d. Click [OK]. The information is updated. Moving Information This section explains how to move information in the list. Perform the following procedure to move information: a. Select the information to move from the list. b.
Chapter 3 Resource Management Overview This chapter provides an overview of the two views available on the [Resource] tab in Resource Orchestrator. Resource Orchestrator provides two different GUIs on the [Resource] tab: the default window and BladeViewer. Choosing an appropriate GUI depends on the administrator's authority level, or the kind of operations to be performed. - ROR console The ROR console gives access to all functions of Resource Orchestrator.
Chapter 4 License Setup and Confirmation This chapter explains how to configure and confirm licenses. License Setup When using Resource Orchestrator, it is necessary to configure the license first. Use the following procedure to configure the license: 1. After logging in to Resource Orchestrator, select [Tools]-[Licenses] from the menu, and click in the displayed dialog. The [Register License] dialog is displayed. 2. In the [Register License] dialog, enter the license key to register. 3.
Chapter 5 Managing User Accounts This chapter explains how to register, modify, and delete user accounts. Add User Account Only privileged users can perform this operation. When using Single-Sign-On, register user information in ServerView Operations Manager beforehand. 1. From the ROR console menu, select [Settings]-[User Accounts]. The [User Accounts] dialog is displayed. 2. Click . The [Add User Account] dialog is displayed. 3.
New password (Confirm password) Enter a string using up to 16 alphanumeric characters or symbols. Authority Level No change/Change Select the appropriate action. By default, the "No change" option is selected. Authority level Select either "Manage" or "Monitor". By default, the current authority level is selected. 4. Click . The password and authority level for the user account are changed. Delete User Account Only privileged users can perform this operation.
Chapter 6 BladeViewer This chapter provides an overview of BladeViewer and explains its features. Please note that BladeViewer is only available for PRIMERGY BX servers. For details on the ROR console, refer to "Appendix A User Interface". 6.1 Overview This section provides a functional overview of BladeViewer. BladeViewer provides an intuitive representation of blade servers and their statuses. This makes it easier to monitor resource states or perform basic operations on blade servers. Figure 6.
- Display of contact information BladeViewer allows users to define technical (support) contact information for their entire IT system. This contact information can be shown by clicking on the Contact icon. Registering contact details of technical support staff beforehand can help streamline recovery procedures when problems occur. 6.2 Screen Layout This section explains how the BladeViewer screen is organized. The BladeViewer screen consists of a status panel, a chassis panel, and a blade panel.
6.3.1 Status Panel The status panel displays a summary of resources statuses (including resources other than PRIMERGY BX servers). When a problem occurs in the system, a red or yellow light icon starts blinking on the left side of the status panel. Clicking the light icon changes its color back to gray. The table below shows the status and meaning associated with each light icon. Table 6.
Table 6.4 Chassis Icon Icon Meaning Chassis See For details on the different chassis statuses, refer to "Table 6.3 Status Icons" of "6.3.1 Status Panel". If a chassis icon shows a warning or error status, it means that a problem occurred in a resource contained in the chassis. For details on how to identify faulty resources, refer to "6.3.3 Blade Panel". Information Selecting a chassis icon from the chassis panel displays the contents of that chassis in the blade panel. For details, refer to "6.3.
Figure 6.3 Blade Panel: Resource List Server Blade A power button is displayed in the upper-part of each server blade. This power button is used to represent the power status of each server, as shown below. Table 6.7 Server Blade Power Buttons Power button Color Status Meaning Green (lit) Power ON Power ON status. Gray (not lit) Power OFF Power OFF status. Green (blinking) Power ON in progress Power ON or reboot in progress. Orange (blinking) Power OFF in progress Power OFF in progress.
Table 6.8 Physical Server Icons Icon Meaning Server Spare server Unregistered server Maintenance mode server See For details on the different physical server statuses, refer to "Table 6.3 Status Icons" in "6.3.1 Status Panel". When a server blade is used as the admin server, the following admin server icon is displayed. Table 6.9 Admin Server Icon Icon Status Admin server Meaning Indicates the server used as the admin server. An OS icon is displayed below the physical server icon.
- If the OS name cannot be acquired (because the OS has not been installed or for other reasons) The server name (physical server name or VM guest name) is displayed. The following table shows the resource icons used in BladeViewer and their associated meanings. Table 6.11 Resource Icons Icon Meaning Physical OS VM host VM guest See For details on the resource status, refer to "Table 6.3 Status Icons" in "6.3.1 Status Panel".
Figure 6.4 Blade Panel: VM Guest List A VM guest icon is shown on the left side of each VM guest displayed in the VM guest list. Table 6.13 VM Guest Icon Icon Meaning VM guest See For details on the different VM guest statuses, refer to "Table 6.3 Status Icons" in "6.3.1 Status Panel". A user-defined label is displayed on the upper-right side of the VM guest icon. - If no label is set The OS name is displayed.
Power button Color Status Orange (blinking) Power OFF in progress Meaning Power OFF in progress. Information The power status of a VM guest can be easily controlled by clicking on its power button. Refer to "6.4.2 VM Guest" for details. 6.3.4 Resource Details To view a resource's details, click on its icon (chassis, LAN switch, or physical server icon) from the blade panel. - Chassis Clicking a chassis icon (from the blade panel) opens up its management blade's Web interface in a new window.
Power Off and Reboot Clicking on a power button that shows "Power ON" status will either shut down or reboot the target server blade. A [Power Operation] dialog is displayed, in which the appropriate action can be selected. Figure 6.5 Power Operation Dialog - "Shutdown" Selecting "Shutdown" will shut down the target server blade. A confirmation dialog is displayed first. Clicking in the confirmation dialog shuts down the OS and powers off the managed server.
Figure 6.6 Power Operation Dialog (with Additional Options) - "Force Shutdown" Selecting "Force Shutdown" will forcibly power off the target server blade. A confirmation dialog is displayed first. Clicking in the confirmation dialog will power off the managed server without waiting for its OS to shut down cleanly. At this time, the power button changes to an intermediate "Power OFF in progress" state (orange - blinking).
Power button Color Green (lit) Status Power ON Action Shuts down or reboots a VM guest. Note - VM guests need to be properly configured in order to use the shut down or reboot buttons. Attempting to shut down or reboot a VM guest that is not properly configured will result in an error. For details, refer to "D.2 Configuration Requirements" in the "Design Guide VE".
Contact icon Displays the [Contact] dialog. This dialog shows the contact information that was set for the entire system. Tools icon Enables selection of the following menu options: Display Label List Displays the [Label List] dialog. Displays a list of labels. This list also allows modification of labels and comments. For details on editing labels and comments, refer to "6.5.1 Listing and Editing of Labels and Comments". Set Contact Information Displays the [Set Contact Information] dialog.
Editing Labels and Comments This function is only available to privileged users. General users are only able to consult labels and comments. - Privileged user In the [Label List] dialog, select a server and click . The [Modify Server Settings] dialog is displayed. The label and comment of the selected server can be edited directly from the [Modify Server Settings] dialog. Enter the following items: Label Enter up to 32 alphanumeric characters or symbols (ASCII characters 0x20 to 0x7e).
- Privileged user New password (Confirm password) Enter a string using up to 16 alphanumeric characters or symbols. - General user Current password Enter the password that is currently set. Enter a string using up to 16 alphanumeric characters or symbols. New password (Confirm password) Enter a string using up to 16 alphanumeric characters or symbols.
Chapter 7 Registering Resources This chapter explains how to register, change, and delete resources used by Resource Orchestrator. The Resource Orchestrator manager must be completely installed beforehand. In addition to the usual method of registering each resource individually, it is also possible to register or change registered settings of multiple resources in batches using the pre-configuration function.
Note HBA address rename and VIOM cannot be used together within the same chassis. When using backup and restore or cloning, prioritize the following two boot operations: 1. Boot from the first admin LAN network interface (NIC1 (Index1)) 2. Boot from the network interface used by the admin LAN (NIC2 (Index2)) 7.2 Registering VM Management Software This section explains how to register VM management software.
Password Enter the password for VM management software. Enter up to 128 characters, including alphanumeric characters and symbols (ASCII characters 0x20 to 0x7e). 3. Click . VM management software is registered with the entered information. Information Registration and management of multiple VM management software packages (VMware vCenter Server, etc) are possible. It is also possible to register a single VM management product multiple times and use it for management.
SNMP Community Enter the SNMP community that was set on the chassis management blade. Select either "public" or enter an arbitrary string. Enter a string of up to 32 alphanumeric characters, underscores ("_"), and hyphens ("-"). 3. Click . The mounted chassis will be displayed under the server resource tree. Any server blade mounted within this chassis will be detected automatically and shown as: [chassis_nameSlot_number[Unregistered]].
Figure 7.1 Status Transition Diagram for Managed Servers Use the following procedure to register blade servers. 1. In the ROR console server resource tree, right-click an unregistered server blade or partition in the target chassis, and select [Register]-[Server] from the popup menu. The [Register Server] dialog is displayed. 2. To use this feature, the following settings must first be defined: Physical Server Name Enter a name to assign to this physical server.
Note - If ServerView Agents (mandatory software) is not running, message number 67231 will be displayed. In this case, server registration succeeds, but the agent is not registered. For details on the appropriate corrective action, refer to "Message number 67231" in "Messages". - If the admin LAN (IP address) of servers not running a physical OS or a VM host are displayed, old information may have been being displayed.
These settings can be changed after server registration. For details on how to modify these settings, refer to "9.1.10 Changing Boot Options". [Apply Admin LAN NIC settings] checkbox The checkbox is displayed only for blade servers (PRIMERGY BX servers). - When not changing the Admin LAN NIC settings NIC1 (Index1) and NIC2 (Index2) are used, without changing the NICs used for the admin LAN, the HBA address rename setup service, or for redundancy of the admin LAN.
3. Click . The registered server will be displayed in the server resource tree. Note - When an agent is registered on a VM host, all VM guests running on that VM host are also registered automatically. Whenever a VM guest is created, modified, deleted, or moved on a registered VM host, the changes are automatically updated in the server resource tree.
Administrative password Enter the password of this LAN switch blade's telnet or SSH administrator account. If the user ID and the password of the administrator account for the LAN switch blade were set in [User ID] and [Password], simply re-enter the same password in this field. In this case, Resource Orchestrator does not check whether the password entered here matches the password set on the LAN switch blade. SNMP Community Enter the SNMP community that was set on this LAN switch blade.
Note VLANs cannot be configured on PRIMERGY BX 900 and BX 400 LAN switch blades operating in IBP mode. 7.3.5 Configuring VLANs on External Ports Use the following procedure to configure VLANs on a LAN switch blade's external ports. 1. In the ROR console server resource tree, right-click the target LAN switch blade and select [Modify]-[Network Settings] from the popup menu. The [VLAN Settings] dialog is displayed. 2.
Tagged VLAN VLAN ID Enter the tagged VLAN ID(s) to assign to the LAN switch blade port that is connected to the network interface selected in step 2. Multiple VLAN IDs can be entered by separating them with commas (","). 4. Click Note that the VLAN settings are not applied onto the LAN switch blade at this stage. To configure VLANs for multiple network interfaces, repeat steps 2 to 4. 5. Confirm the configuration set in the [Network Settings] dialog. 6. Click .
Figure 7.2 Status Transition Diagram for Managed Servers Use the following procedure to register rack mount or tower servers. 1. In the ROR console server resource tree, right-click [Server Resources], and select [Register]-[Server] from the popup menu. The [Register Server] dialog is displayed. 2. To use this feature, the following settings must first be defined: Enter items differ depending on whether the [Register agent] checkbox is selected, as described below.
- Admin LAN - IP address - MAC address (NIC1) - SAN Boot/Admin LAN Redundancy - MAC address (NIC2) Automatic registration of agents is not performed after server registration. After registering servers, register agents as required. If registering agents, register agents after checking the product name is displayed in the General Area of [Resource Details] tab. Executing [Update] acquires the latest information.
Association with server management software (ServerView) Enable/Disable For PRIMERGY BX servers Select [Enable] and enter an [SNMP Community]. For servers other than PRIMERGY servers Select [Disable]. By default, [Enable] is selected. SNMP Community Enter the SNMP community that was set on this server. Select either "public" or enter an arbitrary string. Enter a string of up to 32 alphanumeric characters, underscores ("_"), and hyphens ("-").
For a Physical OS Select [Windows/Linux]. For a VM Host Select [VM Host], and enter the VM host login account information. This login account information will be used by Resource Orchestrator to control and communicate with the registered VM host. User ID Enter the user ID to log in to the VM host. Specify a user ID that has VM host administrator authority. Password Enter the password of the user to log in to the VM host. Note - For details about the network interfaces used on the admin LAN, refer to "7.
7.4.2 Registering LAN Switches Use the following procedure to register LAN switches: 1. Discover LAN switches. For instructions, refer to "Discovery". 2. Register LAN switches displayed in the network device tree. For instructions, refer to "Registration". Discovery 1. From the ROR console menu, select [Tools]-[Topology]-[Discover LAN switches]. The [Discover LAN Switches] dialog is displayed. 2.
SNMP Community Enter the SNMP community that was set on this LAN switch. Either select [public] or enter an arbitrary string. Enter a string of up to 32 alphanumeric characters, underscores ("_"), and hyphens ("-"). 3. Click . The registered LAN switch will be displayed in the network device tree. Note It is possible to set an automatically detected IP address to another unregistered LAN switch.
2. Define the following settings: WWNN Specify the WWNN value provided by the "I/O virtualization Option". The admin server generates WWPNs automatically from the values that are input into the WWNN and the number of HBA ports. HBA ports Specify the following values according to the system configuration. - To create a single-path configuration, specify "1". For details, refer to "Figure 7.3 Procedures for Single-path Configurations". - To create a multi-path configuration, specify "2".
Figure 7.4 Procedures for Multi-path Configurations Example For a server with two ports, WWNs could be configured as follows.
The server restart is not required in other cases. The WWN that has been set is enabled at the next restart. 4. Click . Information When using a server without an OS, the resource name displayed on the server resource tree is the same as that of the physical server. 5. Restart the HBA address rename setup service. The HBA address rename setup service must be running to use the HBA address rename function.
Password Enter the password of the above remote server management user account. This password must be between 8 and 16 alphanumeric characters long. Note The [User ID] and [Password] of [Remote server management] are different from the user name and password used to log in on the Web-UI for management board. 3. Click . The mounted chassis will be displayed under the server resource tree.
Chassis name Enter a name to assign to this chassis. Enter a character string beginning with an alphabetical character and containing up to 10 alphanumeric characters and hyphens ("-"). SNMP Community Enter the SNMP community of the XSCF used to manage the target chassis. Either select [public] or enter an arbitrary string. Enter a string of up to 32 alphanumeric characters, underscores ("_"), and hyphens ("-").
- For SPARC Enterprise M4000/M5000/M8000/M9000 or SPARC M10-4S Right-click the server in the chassis, and select as follows: Select [Register]-[Server] from the popup menu. The [Register Server] dialog is displayed. 2. To use this feature, the following settings must first be defined: When using SPARC Enterprise M4000/M5000/M8000/M9000 or SPARC M10-4S, the items related to Remote Management Controller are not displayed.
IP address Enter the IP address of this server's remote management controller (XSCF). User ID Enter the ID of a XSCF user account with administrative authority over this server. Enter up to 31 characters, including alphanumeric characters, underscores ("_"), or hyphens ("-"). This name should start with an alphabet character. This user should have "platadm" privileges for XSCF. The user ID reserved for the system cannot be used. Create another user ID. For details, refer to the XSCF manuals.
For a VM Host Select [VM Host], and enter the VM host login account information. This login account information will be used by Resource Orchestrator to control and communicate with the registered VM host. User ID Enter the user ID to log in to the VM host. Specify the user ID "root" which has VM host administrator authority. Note When using Solaris 11, if user accounts are created during installation, root will be registered for the role. Therefore, the root account cannot be used for login.
Admin LAN (IP address) Enter the IP address that was set on this power monitoring device. This IP address will be used to collect power consumption data from this power monitoring device. SNMP Community Enter the SNMP community that was set on this power monitoring device. Either select [public] or enter an arbitrary string. Enter a string of up to 32 alphanumeric characters, underscores ("_"), and hyphens ("-").
Subnet mask Enter valid values for the subnet mask. Gateway Enter the settings for the gateway used for communication with the admin server on the admin LAN. 4. Click . Information When registering an admin LAN subnet for the first time, change the simplified DHCP service for Resource Orchestrator to the OS standard DHCP Service. Resource Orchestrator takes exclusive possession of the OS standard DHCP Service.
Resources for Deletion Registry Key [HKEY_LOCAL_MACHINE\]SOFTWARE\Wow6432Node\Fujitsu \SystemcastWizard\PXE\ClientBoot\ - x86 Resources for Deletion Registry Key [HKEY_LOCAL_MACHINE\]SOFTWARE\Fujitsu\SystemcastWizard \ResourceDepot Deployment Service [HKEY_LOCAL_MACHINE\]SOFTWARE\Fujitsu\SystemcastWizard \DatabaseBroker\Default [HKEY_LOCAL_MACHINE\]SOFTWARE\Fujitsu\SystemcastWizard\DHCP PXE Services [HKEY_LOCAL_MACHINE\]SOFTWARE\Fujitsu\SystemcastWizard\PXE \ClientBoot\ Perform the following procedure
9. Configure access rights for the folder for the DHCP Server that was copied to the shared disk. Execute the following command using the command prompt of the primary node: >cacls Drive_name:\Fujitsu\ROR\SVROR\dhcp /T /P "NT AUTHORITY\SYSTEM:F" "BUILTIN \Administrators:F" "NT SERVICE\DHCPServer:F" 10. Add the DHCP Server to "Services and Applications" for the manager. a.
Resource for Configuration PXE Services Dependent Resource DHCP Server 13. Restart the manager. Right-click [Services and Applications]-[RC-manager] on the Failover Cluster Management tree, and select [Bring this service or application online] from the displayed menu. [Linux Manager] Information When configuring a cluster system in an environment that already has an admin LAN registered, in addition to the installation procedure for the cluster system, perform steps 1 to 2 and 4 to 11.
Table 7.1 Files to Link Shared Disk Local Disk Mount_destination_of_shared_disk/Fujitsu/ROR/SVROR/etc/dhcpd.conf (*1) /etc/dhcpd.conf Mount_destination_of_shared_disk/Fujitsu/ROR/SVROR/etc/dhcp/dhcpd.conf (*2) /etc/dhcp/dhcpd.conf Mount_destination_of_shared_disk/Fujitsu/ROR/SVROR/var/lib/dhcpd /var/lib/dhcpd *1: When using Red Hat Enterprise Linux 5 *2: When using Red Hat Enterprise Linux 6 6.
7.9 Registering ETERNUS SF Storage Cruiser This section explains how to register ETERNUS SF Storage Cruiser. Registering ETERNUS SF Storage Cruiser enables server switchover integrated with Fibre Channel switch zoning using ESC and host affinity reconfiguration on storage devices. This operation is necessary when using server switchover (storage affinity switchover method) functions on managed servers (for Solaris) in SAN boot environments.
Chapter 8 Changing Admin Server Settings This chapter explains how to change the settings for the admin server. 8.1 Changing Admin IP Addresses Use the following procedure to change the IP address used on the admin LAN by the admin server. 1. Log on to the admin server with OS administrative privileges. 2. Stop the manager. Stop the manager, referring to "2.1 Starting and Stopping the Manager" in the "Operation Guide VE". 3.
8. Stop the agents on managed servers. [Windows] [Hyper-V] [Linux] [Xen] [KVM] Stop the agent referring to "2.2 Starting and Stopping the Agent" in the "Operation Guide VE". 9. Change Agent settings. [Windows] [Hyper-V] [Linux] [Xen] [KVM] Use the rcxadm agtctl modify command to set the new manager IP address. [Windows] [Hyper-V] >"Installation_folder\Agent\bin\rcxadm" agtctl modify -manager IP_address [Linux] [Xen] [KVM] # /opt/FJSVrcxat/bin/rcxadm agtctl modify -manager IP_address 10.
2. Log in to the admin server's primary node. Log in to the operating system of the admin server's primary node with administration privileges. 3. Mount the shared disk on the primary node. Mount the admin server's shared disk on the primary node. 4. Change takeover the logical IP address. Release PRIMECLUSTER GLS virtual interface settings from the PRIMECLUSTER resource, then change the PRIMECLUSTER GLS configuration. For details, refer to the PRIMECLUSTER Global Link Services manual. 5.
b. Click on the [Registry Replication] tab. The [Registry Key] window will be displayed. c. Configure the above registry key in [Root registry key]. d. Click . e. After configuration of the registry keys is complete, click . f. Click to close the dialog. 4. Assign the manager's shared disk and IP address to the secondary node.
Example When the takeover logical IP address is 192.168.4.100 before being changed # # DHCP Server Configuration file. # see /usr/share/doc/dhcp*/dhcpd.conf.sample # ddns-update-style none; option vendor-class-identifier "PXEClient"; option dhcp-server-identifier 192.168.4.100; (*) subnet 192.168.4.0 netmask 255.255.255.0 { * Note: Change the IP address in this line to the new takeover logical IP address. 6. Unmount the shared disk. Un-mount the shared disk from the primary node. 7.
- Related Services - Deployment Service - TFTP Service - PXE Services - DHCP Server (*) [Linux Manager] - Manager Services - rcxmanager - rcxtaskmgr - rcxmongrel1 - rcxmongrel2 - rcxhttpd - rcxdb - Related Services - scwdepsvd - scwpxesvd - scwtftpd - dhcpd (*) * Note: Necessary when managing a managed server in a separate subnet to the admin server. Change the ports used by the above services if there is a possibility that they will conflict with other applications or services.
# /opt/FJSVrcvmr/bin/rcxadm mgrctl modify -port name=number In a clustered manager configuration, bring offline all cluster resources except for the manager's shared disk and IP address, move all cluster resources from the primary node to the secondary node, then execute the rcxadm mgrctl modify command on all the nodes that are hosting cluster resources. 3. Restart manager services. Start the manager referring to "2.1 Starting and Stopping the Manager" in the "Operation Guide VE".
c. From the menu, select [Edit]-[Modify]. The [Edit DWORD Value] dialog is displayed. d. Select [Decimal] and click . This port value will define the first port of the range used by deployment services. However, because the related services can use up to 16 port numbers, ensure that all ports included between "PortBase" (defined here) and "PortBase+15" do not conflict with any other applications or services.
8.4 Changing the Maximum Number of Cloning Image Versions Use the following procedure to change the maximum number of cloning image versions. 1. Change the maximum number of cloning image versions. 2. Check the maximum number of cloning image versions. For details of the methods for changing and checking the generations of cloning images, refer to "5.8 rcxadm imagemgr" in the "Reference Guide (Command) VE".
a. In the [Failover Cluster Management] window, right-click the [Deployment Service] resource in [Summary of RC-manager][Other Resources], and select [Properties] from the popup menu. The [Deployment Service Properties] window is displayed. b. In the [Registry Replication] tab, select the above registry key. c. Click . The selected key is removed from the "Root registry key" list. d. After removing the registry key, click . e. Click to close the dialog. 2.
1. Log on to the admin server with OS administrative privileges. 2. Stop the manager. Stop the manager, referring to "2.1 Starting and Stopping the Manager" in the "Operation Guide VE". 3. Change the password for the Resource Orchestrator database. Execute the rcxadm dbctl modify command. Enter the new password interactively.
Chapter 9 Changing Resources This chapter explains how to change settings for the admin server or resources registered on the admin server. 9.1 Changing Chassis and Managed Server Settings This section explains how to change the settings for chassis and managed servers. If collecting the system images and cloning images of managed servers, collect them after completing changes to managed server settings. For details on backing up system images, refer to "16.2 Backup".
4. If the network parameter auto-configuration function is used in the deployment of the cloning images, the "Physical Server Name" set in the definition file must also be changed. For details on the network parameter auto-configuration function, refer to "17.6 Network Parameter Auto-Configuration for Cloning Images". 9.1.3 Changing Admin IP Addresses This section explains how to change admin IP addresses. To change the IP addresses of remote management controllers, refer to "9.1.
5. Change [Admin LAN (IP address)]. 6. Click . The admin IP address of the managed server is changed. Note It is not possible to change IP address settings of a managed server (primary server) with a spare server configured to a different subnet from the spare server. 9.1.4 Changing SNMP Communities This section explains how to change SNMP community settings.
2. In the ROR console server resource tree, right-click the target chassis and select [Modify]-[Registration Settings] from the popup menu. The [Modify Chassis Settings] dialog is displayed. 3. Change [SNMP Community]. 4. Click . The SNMP community is changed. 9.1.5 Changing Server Management Unit Configuration Settings This section explains how to modify server management unit settings. - For rack mount or tower servers Use the following procedure to change remote management controller settings. 1.
1. Change the remote server management settings. If the user account is changed, it should still have administrator authority. 2. In the ROR console server resource tree, right-click the target chassis and select [Modify]-[Registration Settings] from the popup menu. The [Modify Chassis Settings] dialog is displayed. 3. Select the [Modify remote server management login account] checkbox. Then, change the [User ID] and [Password] of [Remote Server Management].
If the login account information (user ID and password) of the VM host entered when the VM host was registered is changed, change the login account information of the VM host that was registered in Resource Orchestrator. The method for changing the VM host login account is shown below. 1. In the ROR console server resource tree, right-click the target VM host, and select [Modify]-[VM Host Login Account] from the popup menu. The [Change Login Information] dialog is displayed. 2.
9.1.11 Changing Admin LAN Subnets Use the following procedure to change an admin LAN subnet. 1. From the ROR console menu, select [Settings]-[Admin LAN Subnet]. The [Admin LAN Subnet] dialog is displayed. 2. Select the subnet to change. The [Change Admin LAN Subnet] dialog is displayed. 3. In the [Change Admin LAN Subnet] dialog, set the following items.
9.2.1 Changing the IP Address of the Admin Server This section explains how to change the IP address of the admin server. When this setting is changed, the HBA address rename setup service automatically checks whether it can communicate with the new admin server IP address. Changing this setting also requires changing the port on the admin server side beforehand. Change the IP address of the admin server according to "9.1.
2. To use this feature, the following settings must first be defined: User ID Enter the ID of a VIOM user account. Password Enter the password of the above VIOM user account. 3. Click . To change registered VIOM server profiles, follow the procedure described in "7.1.1 Registering VIOM Server Profiles" to open the Web interface of ServerView Virtual-IO Manager and change the settings. Changes made inside Virtual-IO Manager are automatically reflected in Resource Orchestrator. 9.
If the IP address of the target switch is set to the same address as that of another unregistered LAN switch unintentionally, change back the target LAN switch IP address to its original value according to the instructions given in this section. If there are more than one LAN switch with inconsistent IP address configurations, delete all registered LAN switches according to "11.4.2 Deleting LAN Switches " first, then perform discovery and registration according to "7.4.2 Registering LAN Switches".
Physical Port, Link Aggregation Select [Untagged] from the VLAN type of the port number to configure or link aggregation group name. 3. Click . The VLAN ID is changed. - With Tagged VLANs First delete the VLAN ID was set on the desired LAN switch blade port before setting the new VLAN ID. Use the following procedure to change VLAN IDs: 1. In the ROR console server resource tree, right-click the target LAN switch blade and select [Modify]-[Network Settings] from the popup menu.
Deleting VLAN IDs This section explains how to delete VLAN IDs. - Deleting VLAN IDs from LAN switch blades Use the following procedure to delete VLAN IDs: 1. In the ROR console server resource tree, right-click the target LAN switch blade and select [Modify]-[Network Settings] from the popup menu. The [VLAN Settings] dialog is displayed. 2. To use this feature, the following settings must first be defined: VLAN Select "Change" and select the VLAN ID that has been changed. 3. Click .
1. In the ROR console management software tree, right-click the target management software, and select [Modify]-[Registration Settings] from the popup menu. The [Modify Management Software(name) Settings] dialog is displayed. The name of the selected VM management software is displayed in name. 2. Enter the following items: Location Select the location of the VM management software registration to change. - If VM management software is installed on the admin server Select [Admin Server].
Data storage period Enter storage periods for each collection rate. Data older than the configured storage period will be deleted every day. Enlarging data storage periods reduces the number of devices that can be monitored simultaneously. Use the default storage period values when monitoring chassis and servers. 3. Click . The new settings are applied.
9.7 Changing Monitoring Information Settings This section explains how to change and cancel monitoring information settings. 9.7.1 Changing Monitoring Information Settings This section explains how to change monitoring information settings. The following settings can be changed. - Enabling or disabling of ping monitoring - Time-out - Recovery method - Number of reboots Use the following procedure to change settings: 1.
2. Modify the values for the following items: Label Enter up to 32 alphanumeric characters or symbols. Comments Enter up to 256 alphanumeric characters or symbols. 3. Click . Basic information for the storage management software is modified. 9.8.2 Changing Storage Unit Basic Information This section explains how to change the basic information of storage units. The following settings can be changed. - Label - Comments Use the following procedure to change the basic information of storage units: 1.
3. Click . The basic information of the virtual storage resource is modified. 9.8.4 Changing Disk Resource Basic Information This section explains how to modify the basic information for disk resources. The following settings can be changed. - Label - Comments Use the following procedure to modify the basic information for disk resources 1. Select the target virtual storage in the ROR console storage tree. The disk resource list is displayed in the [Resource List] tab. 2.
Chapter 10 Configuring the Operating Environments of Managed Servers This chapter explains how to install software to the registered managed servers and set up their operating environment. Figure 10.1 Procedure for Setting up Operating Environments *1: HBA address rename and VIOM cannot be used together within the same chassis. I/O virtualization settings for all the servers mounted in one chassis must be made using either HBA address rename or VIOM.
1. In the ROR console server resource tree, right-click the target physical server, and select [Modify]-[WWN Settings] from the popup menu. The [WWN Settings] dialog is displayed. 2. To use this feature, the following settings must first be defined: HBA ports Select the following values according to the system configuration. - Procedures for Single-path Configurations Specify "1" for HBA ports. - Procedures for Multi-path Configurations Select the number of multi-paths for HBA ports.
- If the target CA is not displayed, confirm the status of the following settings: - ESC is correctly registered on Resource Orchestrator. - Fibre Channel switches and storage units are correctly registered. - Only one access path is configured on ESC for each CA of an HBA. 10.2 Deploying Cloning Images For the second and subsequent servers, operating systems are created using the cloning image collected from the first server. For details on cloning, refer to "Chapter 17 Cloning [Physical Servers]".
Chapter 11 Deleting Resources This chapter explains how to delete resources. It is possible to register and delete a managed server and LAN switch as a single resource when they are in the same chassis. Note that operation of a server cannot be performed while the LAN switch is being registered and removed. If the operation is performed simultaneously for multiple resources, one of the following messages is displayed.
Information - If HBA address rename has already been set up on the managed server, the HBA WWN is reset to the factory default. When this occurs, the managed server is turned on temporarily, after the power is forcibly turned off once. When the operating system is running on a managed server, it is recommended to shut it down before deleting the server. - VM guests can be deleted using the management console of the server virtualization software used.
- Server blades that are managed using VIOM, and are currently the target of operations by Resource Orchestrator (power control, image-related processes, etc.) When using VIOM coordination as I/O virtualization with rack mount servers, if VIOM server profiles are left assigned when VIOM coordination is deleted, the MAC addresses on the target rack mount servers remain with I/O virtualization. When using rack mount servers, VIOM server profiles need to be unassigned before deleting VIOM coordination. 11.
11.6.1 Deleting Power Monitoring Devices This section explains how to delete power monitoring devices. Use the following procedure to delete power monitoring devices: 1. In the ROR console power monitoring devices tree, right-click the target power monitoring device and select [Delete] from the popup menu. The [Delete Resource] dialog is displayed. 2. Click . The target power monitoring devices are deleted from the tree view. 11.
Chapter 12 Pre-configuration for Resource Registration and Modification This chapter provides an overview of the pre-configuration function and explains how to use system configuration files. 12.1 Overview Using the Pre-configuration function, it is possible to create system definition files that can be later used to setup a Resource Orchestrator environment. Importing system configuration files makes it easy to perform various registration settings in one operation.
- When saving a file in CSV format from the system configuration template, or exporting a system configuration file from the ROR console Export will be performed using the latest file format given in "B.2 File Format". The following operations, usually performed from the ROR console, can be equally performed using the pre-configuration function. - Registration - "7.1 Registering VIOM Coordination" - "7.3 When Using Blade Servers" - "7.4.2 Registering LAN Switches" - "7.
Note - The following operations cannot be performed by the pre-configuration function, and should be performed from the ROR console.
3. In the ROR console, select [File]-[System Configuration File]-[Import] from the menu. The [Import System Configuration File] dialog is displayed. 4. Specify a configuration file prepared in step 1. 5. Click . The import process starts. The system configuration file is verified first, and then resources are imported one by one, following the order defined by the system configuration file. The processing of resource registration or change is executed after the verification.
- When changing physical server names during pre-configuration, it cannot be performed at the same time as other preconfiguration operations. Import the "Server" section separately from other sections. 6. When the import is completed successfully, a message is displayed in the Recent Operations area. Point - Error handling The processing of resource registration or change is executed after the verification of the system configuration file during import.
- If the agent is registered, perform either one of the following to enable further backup or cloning operations. - Restart the managed server. - Restart the Related Service described in "2.2 Starting and Stopping the Agent" in the "Operation Guide VE". 12.3 Exporting the System Configuration File This section explains the method for exporting a system configuration file containing the current system settings.
Chapter 13 Network Map This chapter provides an overview of the Network Map and describes its features. 13.1 Overview The Network Map displays the following information for resources managed in Resource Orchestrator. - Network configuration of physical and virtual servers (including virtual switches and VM guests) - Statuses of network links between all resources - VLAN configuration affecting each physical and virtual server Two different maps (listed below) are available within the Network Map.
The following actions are available in the Network Map.
2. Detect physical network links a. From the ROR console menu, select [Tools]-[Topology]-[Detect physical links]. The [Detect Physical Links] dialog is displayed. b. Click . Note - If no LAN switch blades have been registered, only network links between external LAN switches will be displayed. If only one external switch is registered, no network links will be displayed at all. - If a non-supported LAN switch is registered, network links may not be properly displayed for that switch.
Update button Update the network map to show the latest status. Display filter area Provides checkboxes to select which information to display in the network view. Map navigation area Shows a zoomed-out version of the selected map (including items which are too far away to be displayed in the network view). VLAN display area Displays the selected VLAN ID in the VLAN tree. 13.3.2 Map Types This section explains the different types of map available.
- When selecting a server The following items are displayed: - NICs In addition, the following items will be displayed when the selected server is a VM host: - VM guests - Virtual switches - Ports - Network links - When selecting a LAN switch blade The following items are displayed: - Ports Selecting a LAN switch blade will show all its ports. For PRIMERGY BX900/BX400 LAN switch blades operating in IBP mode, a list of port groups is displayed.
Table 13.1 Chassis Icons Icon Status Meaning normal No new errors or warnings were detected from the chassis. warning A warning was detected from the chassis. unknown The status of the chassis could not be obtained. error An error was detected from the chassis. fatal A fatal error was detected from the chassis, which is now unusable. stop The chassis was detected to have been powered off. Table 13.
Table 13.3 LAN Switch Blade Icons Icon (*1) (*1) (*1) (*1) Status (*2) Meaning normal No new errors or warnings were detected from the LAN switch blade. warning A warning was detected from the LAN switch blade. unknown The status of the LAN switch blade could not be obtained. error An error was detected from the LAN switch blade. fatal A fatal error was detected from the LAN switch blade, which is now unusable. stop The LAN switch blade was detected to have been powered off.
Table 13.5 VM Guest Icons Icon Status Meaning normal No new errors or warnings were detected from the VM guest. warning A warning was detected from the VM guest. unknown The status of the VM guest could not be obtained. error An error was detected from the VM guest. fatal A fatal error was detected from the VM guest, which is now unusable. stop The VM guest was detected to have been powered off. Table 13.
Table 13.7 LAN Switch Icons Icon Status Meaning normal No new errors or warnings were detected from the LAN switch. warning A warning was detected from the LAN switch. unknown The status of the LAN switch could not be obtained. error An error was detected from the LAN switch. fatal A fatal error was detected from the LAN switch, which is now unusable. stop The LAN switch was detected to have been powered off. Table 13.
Icon Meaning Server (*1) (*2) LAN switch blade VM host VM guest Virtual switch LAN switch Port *1: When operating in IBP mode *2: When operating in VCS mode Information If a problem occurs on a resource, a status icon indicating the problem is shown on top of the resource's own icon. For details on status icons, refer to "13.4.1 Resource Statuses". 13.4.3 Other Icons The following tables detail the icons displayed in the Network Map.
Table 13.10 Admin Server Icon Icon Status Admin server Meaning Indicates the server used as the admin server. Table 13.11 Map Navigation Icons Icon Meaning Chassis Server VM host VM guest Switch VM switch 13.5 Network Links This section details the network links displayed in the Network Map. 13.5.1 Link Display The following table details the physical and virtual links displayed between resources. Table 13.12 Links Link Meaning Represents a physical or virtual link. Represents a VLAN link.
13.5.3 Aggregate Display of Network Links When two resources are linked by two or more links, those links are represented as one aggregated link (please note that this appellation is not related with the Link Aggregation Protocol, but only refers to the display representation of multiple links as one entity). Aggregated links are shown as thick lines in the Network Map. The following diagram shows an example of aggregate display.
13.6 Display Filters This section explains how to use display filters. Resource descriptions The display filter area includes the following filters (checkboxes). Selecting or clearing a filter's checkbox will either show or hide the content associated with that filter. Physical links The display filter area includes the following filters (checkboxes). Disabling this filter will hide all physical links between resources on the network map. VLANs Only displayed when the VLAN tree is displayed.
Chapter 14 Power Control This chapter explains how to remotely control the power state of managed resources. 14.1 Server Power Control This section explains how to remotely control the power states of physical servers, VM hosts, and VM guests. Use the following procedure to perform power control operations. 1.
[Windows] - Take caution regarding the following points when shutting down or rebooting a managed server running a Windows operating system. - If Windows is not configured to shut down when the computer's power button is pressed, the power operations in Resource Orchestrator may not function properly. To check this option, access the Control Panel, open the [Power Options], and check the settings of the [Advanced] tab in the [Power Options Properties] window.
Chapter 15 Control of VM Environments This chapter explains the Resource Orchestrator functions that are specific to VM guests and VM hosts. Some functions may or may not be available depending on the server virtualization software used. Refer to "D.1 Common Functions of Server Virtualization Software" in the "Design Guide VE" for details. Other functions are similar in use to those available for regular physical OSs (without server virtualization software). 15.
15.2 VM Maintenance Mode of VM Hosts This section explains how to set and release VM maintenance mode on VM hosts. For details on VM maintenance mode, refer to "D.3 Functional Differences between Products" in the "Design Guide VE". VM maintenance mode can also be set or released from the command-line, using the rcxadm server set command. For details, refer to "3.2 rcxadm server" in the "Reference Guide (Command) VE". 15.3 VM Home Position This section explains VM Home Position.
15.3.2 Migrating to VM Home Position Migrate VM guests back to their original VM hosts using the relationship information that was registered in advance. The method used for VM guest migration is automatically selected from cold migration and live migration after each VM guest's power status is checked. Migrating all VM Guests to their VM Home Positions Use the following procedure to migrate the VM guests of a system to their VM Home Position: 1.
15.4 External Software This section explains how to configure the settings required by Resource Orchestrator to interact with third party software. VM Management Console To launch an external VM management console (provided by the virtualization software used) from the ROR console, users must be granted the permission to launch this management console in the Java Plug-in policy settings. For details on the VM management consoles that can be started from the ROR console, refer to "D.
Chapter 16 Backup and Restore This chapter explains how to use the backup and restore functions provided in Resource Orchestrator. 16.1 Overview The backup and restore functions allow the backup and restoration of system images from physical OSs or VM hosts. The system image backup and restore function enables backup of images of physical OSs and VM hosts over the network, and stores them on a disk on the admin server. A system image backup can be used for the following purposes.
files). During restore, because the target VM host will be automatically set to VM maintenance mode, the VM host should be in a state that allows VM maintenance mode to be set. If the target VM host is in a high-availability configuration, all VM guests stored on shared disks should be migrated to another VM host beforehand. After restoring the VM host, migrate the VM guests back to their original VM host. Refer to the server virtualization software manual and "D.
>Installation_folder\SVROR\Manager\bin\rcxadm server set -name physical server -attr bootagt=dos [Linux Manager] #/opt/FJSVrcvmr/bin/rcxadm server set -name physical server -attr bootagt=dos - When using the Red Hat Enterprise Linux 6 ext4 file system, and one of the following conditions is met - In a SAN boot environment using HBA address rename - When using a rack mount or tower server and the server is registered with "Disable" of "Association with server management software (ServerVie
b. Set the following items as necessary: Comments Enter a comment to identify the system image. A comment can be up to 128 characters long. Use of percent signs ("%"), backslashes ("\"), double quotes ("), and linefeed characters are not allowed. Note A list of the resources that will be powered off during backup is displayed in the text area. Confirm that it is safe to shut down those resources before continuing with the backup operation.
16.3 Restore This section explains how to restore a system image backup. System images can also be restored using commands. Refer to "Chapter 4 Image Operations" in the "Reference Guide (Command) VE" for details. Restoring a System Image Use the following procedure to restore a system image to a managed server. 1. Place the target server into maintenance mode. a.
b. Click . The target server is released from maintenance mode. Note If the target VM host is in a high-availability configuration, all VM guests stored on shared disks should be migrated to another VM host beforehand. During restore, because the target VM host will be automatically set to VM maintenance mode, the VM host should be in a state that allows VM maintenance mode to be set. After restoring the VM host, migrate the VM guests back to their original VM host.
16.4 Viewing This section explains how to browse and view existing system image backups. System images can also be listed using commands. Refer to "Chapter 4 Image Operations" in the "Reference Guide (Command) VE" for details. In the ROR console, select the [Image List] tab. The System Image List is displayed. Figure 16.1 System Image List Refer to "A.8 [Image List] Tab" for details on the System Image List.
Chapter 17 Cloning [Physical Servers] This chapter explains how to use the server cloning function. 17.1 Overview Cloning is a function used to deploy a cloning image collected from a single managed server (source server) to other managed servers (destination servers). This function shortens the time required for an initial installation as it can be used to install the same operating system and software on multiple servers.
- Cloning images can be collected with the following file systems. Note that LVM (Logical Volume Manager) partitions are not supported. - NTFS - EXT3 - EXT4 - LinuxSwap - When the managed server is Windows Server 2012, collection of cloning images from system disks that include ReFS data areas is not possible. - The following conditions must be met for the managed server to collect the cloning image from and the managed server to deploy the cloning image to. - All server models must be identical.
A cloning image can be collected only from a managed server on which an agent has been registered. For details on registering agents, refer to "Chapter 7 Installing Software and Registering Agents on Managed Servers" in the "Setup Guide VE". A cloning image can be collected from a managed server that satisfies the following conditions: - The status is either "normal" or "warning" - Has been placed into maintenance mode Cloning images cannot be collected from VM hosts or VM guests.
The maximum number of image versions is three by default. This setting can be changed by following the instructions given in "8.4 Changing the Maximum Number of Cloning Image Versions ". - When deploying cloning images, the destination server temporarily starts up with its hostname set to either the physical server name or the source server's hostname. If the same server names are detected on the same network, a network duplication error will occur.
Table 17.2 Structure of the Definition File Format Parameter Value KMS host search type. Select one of the following: - AUTO .cmd.remotescript. 1.params.kmscheck (Mandatory) KMS Automatically searches KMS hosts. - MANUAL Specify the KMS host. When "MANUAL" is selected, make sure to set .cmd.remotescript. 1.params.kmsname. MAK Comm on .cmd.remotescript. 1.params.kmsname The host name (FQDN), computer name, or IP address of the KMS host. .cmd.remotescript. 1.params.kmsport KMS host port number.
.cmd.remotescript.1.params.ieproxy=proxy.activation.com:8080 .cmd.remotescript.1.params.password=PASSWORD If the Administrator password has been changed, execute the following command. The password specified in the .cmd.remotescript.1.params.password parameter of the definition file is changed to the encrypted string, and the line "encrypted=yes" is added to indicate that the password is encrypted. For details, refer to "5.6 rcxadm deployctl" in the "Reference Guide (Command) VE".
3. Collect a cloning image. a. In the ROR console server resource tree, right-click the physical OS of the source server and select [Cloning]-[Collect] from the popup menu. The [Collect a Cloning Image] dialog is displayed. b. To use this feature, the following settings must first be defined: Cloning Image Name Enter a name to identify the collected cloning image. New When creating a new cloning image, select [New] and enter a new cloning image name.
a. In the ROR console server resource tree, right-click the source server (or its physical OS) and select [Maintenance Mode][Release] from the popup menu. The [Release Maintenance Mode] dialog is displayed. b. Click . The target server is released from maintenance mode. - While a cloning image is being collected, no other operations can be performed on that image or other versions of that image (images sharing the same image name).
- When using the Red Hat Enterprise Linux 6 ext4 file system, and one of the following conditions is met - In a SAN boot environment using HBA address rename - When using a rack mount or tower server and the server is registered with "Disable" of "Association with server management software (ServerView)" is selected [Windows Manager] >Installation_folder\SVROR\Manager\bin\rcxadm server set -name physical server -attr bootagt=winpe [Linux Manager] #/opt/FJSVrcvmr/bin/rcxadm server set -name physical
- When using local disks as system disks, and iSCSI storage as data disks, refer to the advisory notes described in "Table 8.1 Supported Storage Device Configurations" in "8.1.1 Storage Configuration" in the "Design Guide VE". Deploying a Cloning Image Use the following procedure to deploy a cloning image to one or more destination servers: 1. Place the destination server(s) into maintenance mode (only for agent-registered servers). a.
[Release from Maintenance Mode after deployment] checkbox Enable this option to automatically release the destination server from maintenance mode after cloning image deployment. If this option disabled, maintenance mode should be released manually after collecting the cloning image. c. Click . The cloning image deployment process starts. The process status can be checked in the Recent Operations area of the ROR console.
d. Click . The cloning image deployment process starts. The process status can be checked in the Recent Operations area of the ROR console. Clicking in the Recent Operations area displays a confirmation dialog and stops the process. Note When this process is cancelled, cloning image deployment to all destination servers is cancelled. Please note that canceling the deployment of a cloning image does not restore the destination server to the state before the deployment took place. 3.
- Microsoft Internet Explorer settings (RSS feeds subscription information, information stored by the Autocomplete function, saved passwords) - Microsoft Outlook Express settings (mail/directory server passwords) - Network card driver settings (drivers without a digital signature should be replaced by the latest updated drivers with a digital signature) - Access rights to the '\Documents and Settings\Default User' folder - While a cloning image is being deployed, collection, deployment, and deletion canno
In the ROR console, select the [Image List] tab. A list of cloning images is displayed under the cloning image list. Use this list to manage the cloning images used by Resource Orchestrator. Figure 17.1 Cloning Image List For details on the "Cloning Image List", refer to "A.8 [Image List] Tab". 17.5 Deleting This section explains how to delete a cloning image. Use the following procedure to delete cloning images: 1. In the ROR console, select the [Image List] tab.
- When Using LAN Redundancy [Linux] - The "NIC switching mode (Physical IP address takeover function)" of PRIMECLUSTER Global Link Services Figure 17.2 Setup Procedure When Using the Network Parameter Auto-configuration Function Note [Physical Servers] The network parameter auto-configuration function cannot be used on the admin LAN. If it is used, deployment commands may fail when deploying new servers may fail, or communication issues may occur during collection or deployment of cloning images.
[Windows] Installation_folder\Agent\etc\FJSVrcx.conf Installation_folder\Agent\etc\ipaddr.conf [Linux] /etc/FJSVrcx.conf /etc/opt/FJSVnrmp/lan/ipaddr.conf Sample configuration of the definition file (FJSVrcx.conf) admin_LAN=192.168.1.11 hostname=node-A - admin_LAN Enter the IP address used by the reference server on the admin LAN. - hostname Enter the physical server name of the reference server. Format of the definition file (ipaddr.
Table 17.3 Node Entry Settings Setting Managed server name Keyword NODE_NAME Expected Values: Physical server name Description Physical server name that was set when registering the managed server. Note Specify additional entries for any node (server) that may be added in the future (one entry per server). - Interface Entries (without Redundancy) The following table explains how to define each interface entry. Keywords for interface entries should be appended with a number between 0 and 99.
When there is a mixture of interfaces with and without redundancy, assign values in ascending order to the interfaces without redundancy as well. Interface entries with redundancy settings are only activated with Linux. With Windows, these interface entries will be ignored. Table 17.5 Interface Entry Settings (with Redundancy) Setting Keyword Expected Values: Description PRIMECLUSTER GLS virtual interface name VIF_NAME shaX X is an integer between 0 and 255.
2. Enable the Network Parameter Auto-Configuration Function Enable the network parameter auto-configuration function by executing the following command. Execute this command from a managed server. [Windows] >"Installation_folder\Agent\bin\rcxadm" lanctl enable [Linux] # /opt/FJSVrcxat/bin/rcxadm lanctl enable For details on the command, refer to "5.9 rcxadm lanctl" in the "Reference Guide (Command) VE". 17.6.
Items to confirm - The status of the virtual interface must be "Active". - When the standby patrol function is used ("p" mode), the status of the virtual interface set in standby patrol ("sha2" in the output example above) must be "Active".
[Linux] /var/opt/FJSVnrmp/logs/error_lan.log For details on meanings of message and the appropriate corrective actions, refer to "Messages". The file size limit is 32 KB and only one version is maintained. Old logs will have the extension ".old" appended to the file name and remain in the same directory. 17.6.3 Clearing Settings This section explains how to disable the network parameter auto-configuration function and clear the settings that were applied.
Deploying New Managed Servers with Automated Public LAN Configuration Use the following procedure to add new managed servers and automate their public LAN settings using the network parameter autoconfiguration function: 1. Register the newly added servers. 2. Perform the following procedure on a reference server chosen between already running servers: a. Clearing Network Parameter Settings Execute the rcxadm lanctl unset command to clear the network parameters configuration. b.
Chapter 18 Server Switchover Settings This chapter explains how to use server switchover settings and automatically recover from server failures. 18.1 Status Display Current recovery settings can be confirmed by selecting a physical OS or VM host in the server resource tree of the ROR console and from the spare server settings displayed in the [Resource Details] tab.
Servers that have agents registered can be used as spare servers. When using a server on which an agent is registered as a spare server, the server must meet one of the following conditions: - When the WWPN of the target CA is the same value as that of the primary server - When the AffinityGroup value is different from the value of the primary server - When agents are not registered on ETERNUS SF Storage Cruiser ETERNUS SF Storage Cruiser cannot perform event monitoring of spare servers.
[Power off forced when the server is switched over] checkbox Check this checkbox if the spare server is to be turned off forcibly when the spare server in started before switchover takes place. When shutting down the spare server, clear this checkbox. This option is not selected by default. [Switchover to server where VM guest exists] checkbox When a spare server is a VM host, check this checkbox if switching to a spare server in which the VM host contains a VM guest.
with Resource Orchestrator. The testing method for automatic server recovery is the same as for manual server switchover. Make sure the server is operational by performing the manual server switchover test. For details on switchover and failback methods, refer to "Chapter 4 Server Switchover" in the "Operation Guide VE". Note For servers other than those using I/O virtualization and those with WWN settings registered, the following checks will not be enabled.
ADMIN_IP=failover_admin_ip zfs_storage_pool[,zone_name,zone_name2] - Blank spaces before and after commas (",") are ignored. - When adding comments, start the line with a number sign ("#"). Definition File Items Specify the following items. failover_admin_ip Enter the admin IP address of the switchover source server. zfs_storage_pool Enter the name of the ZFS storage to import to the switchover destination server zone_name Enter the zone on the ZFS storage.
1. In the ROR console server resource tree, right-click a server (or a physical OS or VM host on the server) and select [Modify]-[Spare Server Settings] from the popup menu. The [Spare Server Settings] dialog is displayed. 2. Clear the checkbox in the [Select] column for the desired spare server. 3. Click . The selected spare server is no longer set as a spare server.
Chapter 19 Collecting Power Consumption Data and Displaying Graphs This chapter explains how to export the power consumption data collected from registered power monitoring targets and how to display it as graphs, and also describes the exported data's format. 19.1 Exporting Power Consumption Data This section explains how to export power consumption data. The power consumption data for each power monitoring target that is registered in the power monitoring environment can be exported in CSV format.
Target Resources Specify the power monitoring target to export the power consumption data of. Select the checkboxes of each desired target. More than one target can be selected. Data Type Specify the type of data to export. Check the checkbox of each desired data type. More than one data type can be selected. Output time span Select the time span for which to export data from the drop-down menu.
Rate Output time span Output device count Daily Last year 30 Monthly Select "Custom" and specify 5 years 60 Annual Select "Custom" and specify 5 years 60 19.2 Displaying Power Consumption Data Graphs This section explains how to display power consumption data as graphs. The power consumption data for each power monitoring target that is registered in the power monitoring environment can be displayed as graphs.
Target Resources Specify the power monitoring target name to display the power consumption data graph of. Select the checkboxes of each desired target. Up to 18 targets can be selected. Graph Settings Data Type Specify the type of data to display the graph. Specify either one of the following for the data type: - Power (Instantaneous power consumption) - Average power (Average power consumption during the selected time span) Output Time Span Select the time span for the data from the drop-down menu.
3. Click . After switching to the graph display window, the selected power consumption data can be displayed in line graphs. Figure 19.3 Graph Display Window The following operations can be performed from the graph display window. - Switching resource display By selecting and clearing the checkbox of the [Target Resources], it is possible to display or hide the corresponding graph.
Appendix A User Interface Resource Orchestrator includes two graphical user interfaces: the ROR console and BladeViewer. This appendix provides an overview of the ROR console. For details on how to open and close the ROR console, refer to "Chapter 3 Login to the ROR Console" in the "Setup Guide VE ". For details on BladeViewer, refer to "Chapter 6 BladeViewer". A.1 ROR Console This section explains how the [Resource] tab of the ROR console is organized.
- Physical OS - VM Host - VM Guest - LAN Switch (LAN Switch Blades) Network Devices The resources below are shown in a tree view. A status icon is displayed over each resource's icon. - Network Devices (Firewalls) - Network Devices (Server Load Balancers) - Network Devices (L2 Switches) Network Resources The resources below are shown in a tree view. A status icon is displayed over each resource's icon.
- [Recovery Settings] Tab Displays information on the spare servers assigned to the resource selected in the resource tree. - [Image List] Tab Displays system and cloning image information. - [Network Map] Tab Displays a network diagram of registered resources. - Events Resource Orchestrator events and related information are displayed. The event log displays a history of events that have occurred on managed resources.
Menu View Privileged User General User Function - Yes Yes Returns the layout of the ROR console to its initial state. Chassis Yes No Registers a chassis. Server Yes No Registers a server. SPARC Enterprise (M3000/T Series) Yes No Registers a SPARC Enterprise (M3000/T series) server. SPARC Enterprise (Partition Model) Yes No Registers SPARC Enterprise M4000/ M5000/M8000/M9000 servers. SPARC M10-1/ M10-4 Yes No Registers a SPARC M10-1/M10-4.
Menu Submenu Privileged User General User Function Performs viewing, registration, changing or deletion of the admin LAN subnet information. Admin LAN Subnet - Yes Yes (*8) Update - Yes Yes Updates a resource. ON Yes No Powers on a server. OFF Yes No Powers off a server after shutting down its operating system. OFF (Forced) Yes No Powers off a server without shutting down its operating system. Reboot Yes No Reboots a server after shutting down its operating system.
Menu Submenu Privileged User General User Function Modifies client and environmental data settings. Options - Yes Yes (*11) Environmental Data Graph - Yes Yes Displays environmental data graphs. *1: If multiple ROR consoles or BladeViewer sessions exist, the login sessions may be terminated. *2: Cannot be selected for a VM guest. *3: Cannot be selected for PRIMEQUEST or SPARC Servers/SPARC Enterprise. *4: Available only for PRIMERGY BX servers.
* Note: This option is only available for chassis equipped with power monitoring capabilities. Table A.4 Popup Menus Available for Servers Popup Menu Function Menu Submenu Server (*1) Registers a server. Agent Register the agent. Delete - Deletes a server. Update - Updates a server. Registration Settings Modifies a server's registration settings. HBA address rename settings (*2) Modifies the HBA address rename settings of a server.
Table A.5 Popup Menus Available for SPARC Servers/SPARC Enterprise Popup Menu Function Menu Submenu Server (*1) Registers a server. Agent Register the agent. Delete - Deletes a SPARC Servers/SPARC Enterprise. Update - Updates a SPARC Servers/SPARC Enterprise. Registration Settings Modifies a SPARC Servers/SPARC Enterprise's registration settings. WWN Settings Modifies the WWN settings for a server. Spare Server Settings Modifies a server's recovery settings.
Popup Menu Function Menu Submenu Reboot Reboots a server after shutting down its operating system. Reboot (Forced) Reboots a server without shutting down its operating system. Switchover Switches over a server with one of its spare servers. Failback Switches back a server to its pre-switchover state. Takeover Accepts a switched over configuration as final (without switching back to the original configuration). Maintenance Mode (*1, *4) Set Places a server into maintenance mode.
Popup Menu Function Menu Power Spare Server Submenu ON Powers on an operating system. OFF Powers off a server after shutting down its operating system. OFF (Forced) Powers off a server without shutting down its operating system. Reboot Reboots a server after shutting down its operating system. Reboot (Forced) Reboots a server without shutting down its operating system. Switchover Switches over a server with one of its spare servers.
Popup Menu Function Menu Delete Submenu - Deletes a cloning image. Note If ServerView Deployment Manager is used on the admin LAN, the popup menu for cloning images cannot be used. Table A.11 Popup Menus Available for Network Devices Popup Menu Function Menu Submenu Discover LAN switches Discovers LAN switches within the admin LAN. Detect physical links Acquires physical link data from registered LAN switches. Topology Table A.
Table A.15 Popup Menus Available for Management Software (vCenter Server/SCVMM/VIOM) Popup Menu Function Menu Submenu Delete - Deletes management software. Update - Updates management software information. Modify Registration Settings Modifies registration settings for management software. A.3 Status Panel This section explains the different statuses that are displayed in the ROR console. Figure A.
Figure A.4 Tree Panel In the tree panel, clicking the area on the upper-left enables selection and display of the following 5 types of tree: server resources, network devices, power monitoring devices, management software, and VLAN. Server Resources Chassis, servers, physical OSs, VM hosts, VM guests, and LAN switches managed in Resource Orchestrator are displayed in a tree view. Resources are primarily displayed in registration order.
Information For a VM host coordinated with VMware vCenter Server, the name (IP address or host name) entered when registering with VMware vCenter Server will be displayed. network device External LAN switches (those other than LAN switch blades) managed in Resource Orchestrator are shown in a tree view. Resources are sorted and displayed by name in alphabetical order. Resources displayed in the resource tree are represented by an icon and their resource name.
Storage Location of the Definition File [Windows Manager] Installation_folder\SVROR\Manager\etc\customize_data [Linux Manager] /etc/opt/FJSVrcvmr/customize_data Definition File Name gui_config.rcxprop Definition File Format RESOURCE_TREE_SORT_ORDER=RESOURCE_TREE_ORDER Items in the Definition File RESOURCE_TREE_ORDER Specify either one of the following options: name: Displays the resource list in ascending (alphabetical) order of resource names.
Network Resources Information on all registered network resources is displayed. Power Monitoring Devices Information on all registered power monitoring devices. Management Software Information on all registered management software. Management Software (vCenter Server, SCVMM, or VIOM) Information on the selected management software. Double-clicking a resource in the [Resource List] tab displays its [Resource Details] tab in the Main Panel. This tab shows detailed information on the selected resource.
Figure A.5 Chassis The resource images shown in the above chassis image are explained in the table below. Table A.19 Meaning of the Resources Shown in the Chassis Image Image Meaning A. Registered server blade. B. Detected storage blade. C. Currently displayed server blade. D. Server blade selected within the chassis image. E. Server blade that has not been registered yet. F. Empty slot.
See Refer to "11.2 Resource Status" in the "Operation Guide VE" for details on resource statuses. Hardware Details Area Launch Management Blade Web UI The link to the management blade's Web interface is displayed. Not displayed for SPARC Enterprise M4000/M5000/M8000/M9000 or SPARC M10-4S. Launch XSCF Web UI The link to the remote management controller (XSCF) Web UI is displayed. Only displayed for SPARC Enterprise M4000/M5000/M8000/M9000 or SPARC M10-4S.
A.6.2 Server Attributes General Area Physical server name The name used to identify a server is displayed. Model name The model name of the server is displayed. When the server has been registered as a managed server and powered on, the server model name obtained from ServerView Operations Manager is displayed. For other servers, no model name is displayed. Product name The product name of the server is displayed. For PRIMERGY BX servers, the product name obtained from the management blade is displayed.
- SPARC Enterprise M-Series - SPARC M10 Memory Size The total capacity of server memory is displayed. When using servers other than the following, a hyphen ("-") is displayed. - PRIMERGY BX Series Servers - SPARC Enterprise M-Series - SPARC M10 Admin LAN (MAC address 2) The MAC address of the network interface used for the HBA address rename setup service or for admin LAN redundancy is displayed. Not displayed when SPARC Servers/SPARC Enterprise are selected.
Network Properties Area Physical Connections The list of physical connections between the server's network interfaces and LAN switch ports is displayed. When a column heading in the list is clicked, the color of the selected column will change and the resources can be sorted in either ascending or descending order. Hardware Maintenance Area NIC Summary The MAC addresses and IP addresses of each server are displayed.
A.6.3 Physical OS, VM Host, and VM Guest Attributes General Area Server name The name used to identify a physical OS, VM host, or VM guest is displayed. Admin LAN (IP Address) The IP address on the admin LAN is displayed. Not displayed for VM guests. Status The status of the physical OS, VM host, or VM guest is displayed. Type The type of the OS running on the server is displayed. One of the following is displayed: - Physical OS - VM Host - VM Guest OS The type of the OS running on the server is displayed.
VM Home Positions (VM Guests) A list of the VM guests with the selected VM host set as their VM Home Position is displayed. VM Guest Information Area The following information is displayed only for VM guests. VM type The type of the VM is displayed. VM host name The name of the VM host on which the VM guest is stored is displayed. VM name The name of the VM is displayed. VM management software The link to the web interface of a server virtualization software is displayed.
Server switchover method The method used to perform server switchover is displayed. Server boot method The boot type of the system disk is displayed. Automatic server recovery Shows whether automatic server recovery is enabled or not. Network switchover Shows whether network settings will be automatically adjusted during server switchover. Force spare server to power off during switchover The setting whether the spare server is turned off forcibly when switching over to the spare server is displayed.
Group The names of the port groups set on the LAN switch ports connected to each network interface (for LAN switch blades operating in IBP mode) are displayed. Only "-" is displayed under the following conditions. - The corresponding LAN switch is not registered - The corresponding LAN switch is not operating in IBP mode - The corresponding LAN switch port has not been assigned to a port group Monitoring Information Timeout(sec) The time-out value (in seconds) for ping monitoring is displayed.
A.6.4 Network Device Attributes General Area Network device name The name used to identify a network device is displayed. System Name (sysName) The name of the device specified as a network device is displayed. IP address The IP address on the admin LAN is displayed. Device name (Product name) The product name of the network device is displayed. For NS appliances, "NSAppliance" is displayed. Model The model name of a network device is displayed. For NS appliances, "NSAppliance" is displayed.
Member Port When the name of a port with link aggregation is displayed for the port name, the port names of the physical port with link aggregation are displayed separated by commas (","). When the physical port name is displayed as the port name, a hyphen ("-") is displayed. Link Status The operational status of the port is displayed. One of the following is displayed: - up - down - unknown Speed/DuplexMode The speed and duplex mode of the operating port are displayed.
- PY CB Eth Switch/IBP 1Gb 36/12 - PY CB Eth Switch/IBP 1Gb 18/6 Network links The following information is only displayed for LAN switch blades. Resource Name (left side) The name of the selected network device is displayed. I/F (left side) The port name of the network device is displayed. I/F (right side) The interface name of the resource connected to the network device is displayed. Resource Name (right side) The name of the resource connected to the network device is displayed.
Firmware version The firmware version of the device (PDU or UPS) is displayed. Date of manufacture The date of manufacture of the PDU or UPS is displayed. Outlets The number of outlets provided by the PDU is displayed. This is not displayed for UPSs. Intended orientation The intended orientation (horizontal or vertical) of the PDU is displayed. This is not displayed for UPSs. A.6.
Switchover State The current switchover state is displayed. Spare Server The configured spare server is displayed. The switchover state is indicated by an arrow shown next to the currently active Primary Server. The messages "Switchover in progress", "Failback in progress", or "Takeover in progress" are displayed respectively during a server switchover, failback, or takeover process. If more than one spare server has been set, the first server listed is the one that is currently running.
A.9 Network Map Resource Orchestrator displays the following information. - Network configuration of physical and virtual servers (including virtual switches and VM guests) - Statuses of network links between all resources - VLAN configuration affecting each physical and virtual server See For details on the Network Map, refer to "Chapter 13 Network Map". A.10 Recent Operations This section describes the recent operations area of the ROR console. Figure A.
When the link in the [Operation] column is clicked, the [Progress Details] dialog is displayed. The [Progress Details] dialog displays the following information: Progress List The list of the executed processes and the status are displayed for the selected operation. If an operation is performed simultaneously for multiple resources, the processes are displayed in a tree view for each target resource. Message List The list of any error messages that occurred during the operation is displayed.
Event Log Content of the event. When the link in the [Event Log] column is clicked, an error dialog is displayed. The error dialog provides detailed information of events. Events can be filtered using the checkboxes displayed in the window. Selecting a checkbox will show the events whose status corresponds to that of the selected checkbox. Clearing a checkbox will hide such events. When is clicked in the window, the [Filter Settings] dialog is displayed.
button Deselects all dialog checkboxes. 3. Click . The new settings are applied.
Appendix B Format of CSV System Configuration Files This appendix explains the format of the CSV system configuration files used by Resource Orchestrator's pre-configuration function. B.1 Obtaining the System Configuration File (CSV Format) The system configuration files can be obtained as follows. - From the selection window of the Resource Orchestrator DVD-ROM [Windows] Setting the Resource Orchestrator DVD-ROM in the CD-ROM drive automatically displays the screen below.
- From the ROR console The System Configuration Template can be obtained from a Resource Orchestrator manager installation. 1. Open and log in to the ROR console according to "Chapter 1 Login and Logout". 2. Select [File]-[System Configuration File]-[Download Template] from the ROR console menu. Displays the [File Download] window. 3. Click . 4. Specify the destination directory and the file name. 5. Click . B.
- RCXCSV V3.2 and Later "PRIMERGYPartitionModelChassis", "PRIMERGYPartitionModelServer" - RCXCSV V3.3 and Later "Subnet", "SPARCEnterprisePartitionModelChassis", "SPARCEnterprisePartitionModelServer", "MonitorSetting" - RCXCSV V3.4 and Later "VIOManager" - RCXCSV V3.5 and Later "SPARC", "SPARCM10PartitionModelChassis", "SPARCM10", "SPARCM10PartitionModelServer" SPARC Enterprise (M3000-/T series) performs import/export of a system configuration file (CSV format) by a section name [SPARC].
- change Modification - Hyphens, ("-") Do nothing - Parameter This describes the parameter value to be set. Note The order of operation and parameter columns should follow the order defined in section header under "B.3 Resource Definitions". Allowed Characters For details on the characters allowed for each resource definition, refer to "B.3 Resource Definitions". Optional parameters can be omitted by using hyphens ("-").
Order Section Name 3 Chassis 4 PRIMERGYPartitionModelChassis 5 SPARCEnterprisePartitionModelChassis 6 SPARCM10PartitionModelChassis 7 LanSwitch 8 LanSwitchNet 9 Server 10 SPARCEnterprise 11 PRIMERGYPartitionModelServer 12 ServerNet 13 SPARCEnterprisePartitionModelServer 14 SPARC 15 SPARCM10 16 SPARCM10PartitionModelServer 17 ServerWWNN (*1) 18 SpareServer (*1) 19 VMManager 20 ServerAgent (*2, *3) 21 ServerVMHost (*2, *3) 22 MonitorSetting 23 PowerDevice 24 Memo (
- As with chassis for server blades, and chassis for LAN switch blades, items that need to be registered in advance to enable registration of other should be defined in the system configuration file or registered in advance. Character Code The system configuration files (CSV format) used for pre-configuration are saved using ASCII (often referred to as "ANSI" in Windows systems). When files that use a character code other than ASCII are imported, the system may not operate correctly.
login_name Enter the name of a VIOM user account. When specifying a domain, use the following syntax: "domain_name\user_name". login_passwd Enter the password of the above VIOM user account. passwd_enc Enter one of the following. - If login_passwd is plain text "plain" - If the password is encrypted "encrypted" Chassis Data - Section Name Enter [Chassis] as the section name. - Section Header operation Enter the desired operation for the current line. Enter a hyphen ("-") to skip this line.
- Section Header operation Enter the desired operation for the current line. Enter a hyphen ("-") to skip this line. chassis_name Enter the name that will be used to identify the chassis. Enter a character string beginning with an alphabetical character and containing up to 10 alphanumeric characters and hyphens ("-"). Note Chassis names should be unique between all chassis. Names are not case-sensitive. ip_address Enter the same IP address as that set on the management board.
chassis_name Enter the name that will be used to identify the chassis. Enter a character string beginning with an alphabetical character and containing up to 10 alphanumeric characters and hyphens ("-"). Note Chassis names should be unique between all chassis. Names are not case-sensitive. ip_address Enter the same IP address as that configured on the XSCF. Enter a string of numeric values (between 0 and 255) and periods. Note IP addresses should be unique between all resources.
chassis_name Enter the name that will be used to identify the chassis. Enter a character string beginning with an alphabetical character and containing up to 10 alphanumeric characters and hyphens ("-"). Note Chassis names should be unique between all chassis. Names are not case-sensitive. ip_address Enter the same IP address as that configured on the XSCF. Enter a string of numeric values (between 0 and 255) and periods. Note IP addresses should be unique between all resources.
slot_no Enter the slot number where the LAN switch blade is installed. Enter a number between 1 and 8. switch_name Enter the name to assign to this LAN switch blade. Enter a string of up to 15 alphanumeric characters, underscores ("_"), and hyphens ("-"). Note LAN switch blade names should be unique between all LAN switch blades. The names are case-sensitive. ip_address Enter the same IP address as that set on the LAN switch blade. Enter a string of numeric values (between 0 and 255) and periods.
product_name Enter the model of the LAN switch blade. Note that if a hyphen ("-") is entered, it is treated as "BX600 GbE Switch Blade 30/12". One of the following models can be entered.
Example 10/U 10/U;20/T;30/T 10/T;20/T Note If a hyphen ("-") is entered, VLAN settings will not be performed. This section will be ignored for PRIMERGY BX900/BX400 LAN switch blades operating in IBP mode. The settings in this section will be ignored for a LAN switch blade PY CB DCB SW 10Gb 18/6/6. Server Management Information - Section Name Enter [Server] as the section name. - Section Header operation Enter the desired operation for the current line. Enter a hyphen ("-") to skip this line.
ip_address Enter the same IP address as that set within the server's operating system. Enter a string of numeric values (between 0 and 255) and periods. Note IP addresses should be unique between all resources. mac_address Enter the MAC address of the admin LAN network interface: NIC1 (Index1). Enter a string delimited by hyphens ("-") or colons (":") ("xx-xx-xx-xx-xx-xx" or "xx:xx:xx:xx:xx:xx").
Note If the name of the current administrator account on the remote management controller is longer than 16 characters, either create a new account or rename the current account (within 16 characters). ipmi_passwd Enter the password of the remote management controller user account. Enter a string of up to 16 alphanumeric characters and symbols (ASCII character codes: 0x20 to 0x7e). This field can be omitted if no password has been set for this user account.
- When not using the NIC specified in the admin_lan2_nic_number as the backup for admin LAN redundancy "OFF" SPARC Enterprise M3000/T Series Management Data - Section Name Enter [SPARC] as the section name. - Section Header operation Enter the desired operation for the current line. Enter a hyphen ("-") to skip this line. server_name Enter the resource name that will be used to identify the server.
mgmt_passwd Enter the password of the remote management controller (ILOM/XSCF) to manage a server. - For XSCF Enter up to 32 characters, including alphanumeric characters, blank spaces (" "), and any of the following symbols. - For ILOM Enter between 8 and 16 characters, including alphanumeric characters, blank spaces (" "), and any of the following symbols.
- For XSCF Enter up to 31 characters, including alphanumeric characters, underscores ("_"), or hyphens ("-"). This name should start with an alphabet character. mgmt_passwd Enter the password of the remote management controller (XSCF) user account. - For XSCF Enter up to 32 characters, including alphanumeric characters, blank spaces (" "), and any of the following symbols. mgmt_passwd_enc Enter one of the following.
- When installing using a legacy boot "legacy" - When installing using UEFI "uefi" Server Blade VLAN Data - Section Name Enter [ServerNet] as the section name. - Section Header operation Enter the desired operation for the current line. Enter a hyphen ("-") to skip this line. server_name Enter the server name (the value of "server_name" in the [Server] section). nic_no This is the index number of the server blade's network interface. Enter a number between 1 and 12.
SPARC Enterprise M4000/M5000/M8000/M9000 Server Management Data - Section Name Enter [SPARCEnterprisePartitionModelServer] as the section name. - Section Header operation Enter the desired operation for the current line. Enter a hyphen ("-") to skip this line. chassis_name Enter the chassis name (the "chassis_name" in the [SPARCEnterprisePartitionModelChassis] section). partition_no The number of a partition. Enter a number between 0 and 23.
Note Server names should be unique between all servers. Names are not case-sensitive. ip_address Enter the same IP address as that set within the server's operating system. Enter a string of numeric values (between 0 and 255) and periods. Note IP addresses should be unique between all resources. HBA address rename Information of a Server - Section Name Enter [ServerWWNN] as the section name. - Section Header operation Enter the desired operation for the current line.
spare_server Enter the physical server name of a server to be assigned as a spare server. To specify multiple spare servers, separate each server name using semicolons (";"). To remove current spare server settings, enter "-DELETE". vlan_switch (optional) Specify whether VLAN settings or port group settings should be automatically transferred to the spare server when a server switchover occurs. Enter "ON", "OFF" or a hyphen ("-").
product Enter the name of this VM management software. Enter one of the following. - When using VMware vCenter Server as VM management software. "vmware-vc" - When using System Center Virtual Machine Manager as VM management software. "ms-scvmm" login_name Enter the name of the user account set for this VM management software. Use a string of up to 84 alphanumeric characters and symbols (ASCII character codes: from 0x21 to 0x7e). When specifying a domain, use the following syntax: "domain_name\user_name".
vm_login_name Enter the name of the user account used to remotely log into the VM Host. vm_login_passwd Enter the password of the above user account (for remote login). vm_passwd_enc Enter one of the following. - If the password is plain text "plain" - If the password is encrypted "encrypted" Monitoring Settings - Section Name Enter [MonitorSetting] as the section name. - Section Header operation Enter the desired operation for the current line. Enter a hyphen ("-") to skip this line.
Power Monitoring Device Data - Section Name Enter [PowerDevice] as the section name. - Section Header operation Enter the desired operation for the current line. Enter a hyphen ("-") to skip this line. device_name Enter the name that will be used to identify the power monitoring device. Enter a character string beginning with an alphabetical character and containing up to 15 alphanumeric characters and hyphens ("-"). Note Device names should be unique between all power monitoring devices.
Memo - Section Name Enter [Memo] as the section name. This is required when registering the labels, comments, and contact information (displayed in BladeViewer) using the pre-configuration function. - Section Header operation Enter the desired operation for the current line. Enter a hyphen ("-") to skip this line. resource_type Enter the type of the resource for which to set this memo. Enter one of the following.
RCXCSV,V3.5 # ServerView Resource Orchestrator # System configuration file [Subnet] operation,subnet_name,network_address,subnet_mask,gateway -,subnet1,172.16.0.0,255.255.0.0,172.16.0.1 -,subnet2,192.168.1.0,255.255.255.0,192.168.1.1 [VIOManager] operation,name,ip_address,login_name,login_passwd,passwd_enc -,VIOM,127.0.0.1,administrator,administrator,plain [Chassis] operation,chassis_name,ip_address,snmp_community_name -,chassis01,192.168.3.
-,chassis01,2,36,1/U -,chassis01,2,37,1/U -,chassis01,2,38,1/U -,chassis01,2,39,1/U -,chassis01,2,40,1/U -,chassis01,2,41,1/U -,chassis01,2,42,1/U -,chassis01,2,43,1/U -,chassis01,2,44,1/U [Server] operation,chassis_name,slot_no,server_name,ip_address,mac_address,second_mac_address,snmp_community_name,ipm i_ip_address,ipmi_user_name,ipmi_passwd,ipmi_passwd_enc,admin_lan1_nic_number,admin_lan2_nic_number,admin_ lan_nic_redundancy -,chassis01,1,blade001,192.168.3.151,,,,,,,,1,4,ON -,chassis01,7,blade002,192.
-,blade002,6,1/U -,blade003,2,1/U -,blade003,4,1/U -,blade003,6,1/U [SPARCEnterprisePartitionModelServer] operation,chassis_name,partition_no,server_name,ip_address -,spechassis,3,speserver3,192.168.3.213 -,spechassis,4,speserver4,192.168.3.
Appendix C Maintenance Mode This appendix explains the maintenance mode available in Resource Orchestrator and how to use it. Maintenance mode is used during hardware maintenance of managed servers. It is also used during the installation and maintenance of physical OSs and VM hosts. Maintenance mode avoids unwanted error notifications and disables execution of Auto-Recovery upon server failure.
Glossary access path A logical path configured to enable access to storage volumes from servers. active mode The state where a managed server is performing operations. Managed servers must be in active mode in order to use Auto-Recovery. Move managed servers to maintenance mode in order to perform backup or restoration of system images, or collection or deployment of cloning images. active server A physical server that is currently operating.
BACS (Broadcom Advanced Control Suite) An integrated GUI application (comprised from applications such as BASP) that creates teams from multiple NICs, and provides functions such as load balancing. Basic Mode A function that can be used by configuring a Cloud Edition license after installing ROR VE. BASP (Broadcom Advanced Server Program) LAN redundancy software that creates teams of multiple NICs, and provides functions such as load balancing and failover.
DR Option The option that provides the function for remote switchover of servers or storage in order to perform disaster recovery. end host mode This is a mode where the uplink port that can communicate with a downlink port is fixed at one, and communication between uplink ports is blocked. environmental data Measured data regarding the external environments of servers managed using Resource Orchestrator. Measured data includes power data collected from power monitoring targets.
hardware maintenance mode In the maintenance mode of PRIMEQUEST servers, a state other than Hot System Maintenance. HBA (Host Bus Adapter) An adapter for connecting servers and peripheral devices. Mainly used to refer to the FC HBAs used for connecting storage devices using Fibre Channel technology. HBA address rename setup service The service that starts managed servers that use HBA address rename in the event of failure of the admin server.
iSCSI A standard for using the SCSI protocol over TCP/IP networks. LAN switch blades A LAN switch that is mounted in the chassis of a blade server. license The rights to use specific functions. Users can use specific functions by purchasing a license for the function and registering it on the manager. link aggregation Function used to multiplex multiple ports and use them as a single virtual port.
In regards to the network device file management function, these files are excluded from the scope of version management (They are not automatically deleted). master slot A slot that is recognized as a server when a server that occupies multiple slots is mounted. multi-slot server A server that occupies multiple slots. NAS (Network Attached Storage) A collective term for storage that is directly connected to a LAN. network device The unit used for registration of network devices.
OS The OS used by an operating server (a physical OS or VM guest). PDU (Power Distribution Unit) A device for distributing power (such as a power strip). Resource Orchestrator uses PDUs with current value display functions as Power monitoring devices. physical LAN segment A physical LAN that servers are connected to. Servers are connected to multiple physical LAN segments that are divided based on their purpose (public LANs, backup LANs, etc.).
public LAN A LAN used for operations by managed servers. Public LANs are established separately from admin LANs. rack A case designed to accommodate equipment such as servers. rack mount server A server designed to be mounted in a rack. RAID (Redundant Arrays of Inexpensive Disks) Technology that realizes high-speed and highly-reliable storage systems using multiple hard disks. RAID management tool Software that monitors disk arrays mounted on PRIMERGY servers.
ROR console The GUI that enables operation of all functions of Resource Orchestrator. SAN (Storage Area Network) A specialized network for connecting servers and storage. server A computer (operated with one operating system). server blade A server blade has the functions of a server integrated into one board. They are mounted in blade servers. server management unit A unit used for managing servers.
SNMP (Simple Network Management Protocol) A communications protocol to manage (monitor and control) the equipment that is attached to a network. software initiator An initiator processed by software using OS functions. Solaris Zone Solaris server virtualization software. On Solaris servers, it is possible to configure multiple virtual Solaris servers that are referred to as a Solaris Zone. Solaris zone resource pool The Solaris Zone resource pool used in the global zone and the non-global zone.
UPS (Uninterruptible Power Supply) A device containing rechargeable batteries that temporarily provides power to computers and peripheral devices in the event of power failures. Resource Orchestrator uses UPSs with current value display functions as power monitoring devices. URL (Uniform Resource Locator) The notational method used for indicating the location of information on the Internet.
VM Home Position The VM host that is home to VM guests. VM host A server on which server virtualization software is operated, or the server virtualization software itself. VM maintenance mode One of the settings of server virtualization software, that enables maintenance of VM hosts. For example, when using high availability functions (such as VMware HA) of server virtualization software, by setting VM maintenance mode it is possible to prevent the moving of VM guests on VM hosts undergoing maintenance.
