Page 1 ServerView Resource Orchestrator Virtual Edition V3.1.1 User's Guide Windows/Linux J2X1-7606-05ENZ0(01) January 2013...
Page 2 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".
Page 3 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.
Page 4 Operations on the ROR console can be performed using either the menu bar or pop-up menus. By convention, procedures described in this manual only refer to pop-up menus. Regarding Installation Folder Paths The installation folder path may be given as C:\Fujitsu\ROR in this manual. Replace it as shown below. When using Windows 64-bit (x64)
Page 5 When using Windows 32-bit (x86) C:\Program Files\Resource Orchestrator Abbreviations The following abbreviations are used in this manual: Abbreviation Products 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 Microsoft(R) Windows Server(R) 2003 R2, Standard Edition...
Page 6 Abbreviation Products Windows PE Microsoft(R) Windows(R) Preinstallation Environment 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)
Page 7 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(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)
Page 8 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)
Page 9 Abbreviation Products 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 Oracle Enterprise Linux Release 5 Update 5 for x86 (32 Bit) Oracle Enterprise Linux Release 5 Update 5 for x86_64 (64 Bit) Oracle Solaris10 05/09 (Update7) Media Pack Solaris Oracle Solaris11 11/11 Media Pack...
Page 10 Export Administration Regulation Declaration Documents produced by FUJITSU may contain technology controlled under the Foreign Exchange and Foreign Trade Control Law of Japan. Documents which contain such technology should not be exported from Japan or transferred to non-residents of Japan without first obtaining authorization from the Ministry of Economy, Trade and Industry of Japan in accordance with the above law.
Page 11 J2X1-7606-01ENZ0(03) March 2012, 1.4 J2X1-7606-01ENZ0(04) April 2012, 1.5 J2X1-7606-01ENZ0(05) July 2012, Second J2X1-7606-02ENZ0(00) Edition October 2012, Third J2X1-7606-03ENZ0(00) Edition December 2012, Fourth J2X1-7606-04ENZ0(00) Edition January 2013, Fifth J2X1-7606-05ENZ0(00) Edition January 2013, 5.1 J2X1-7606-05ENZ0(01) Copyright 2010-2013 FUJITSU LIMITED - x -...
Page 12: Table Of Contents
Contents Chapter 1 Login and Logout..............................1 Chapter 2 Home..................................4 2.1 Editing the Home Messages................................4 Chapter 3 Resource Management Overview...........................6 Chapter 4 License Setup and Confirmation..........................7 Chapter 5 Managing User Accounts............................8 Chapter 6 BladeViewer................................10 Overview......................................10 6.2 Screen Layout....................................11 6.3 Resource Status Monitoring................................11 6.3.1 Status Panel....................................12...
Page 13 8.1 Changing Admin IP Addresses................................57 8.2 Changing Port Numbers..................................61 8.3 Changing the Maximum Number of System Image Versions......................64 8.4 Changing the Maximum Number of Cloning Image Versions ......................65 8.5 Changing the Image Folder Location..............................65 8.6 Changing the Password for the Resource Orchestrator Database......................66 Chapter 9 Changing Resources.............................68...
Page 14 11.7 Deleting Admin LAN Subnets.................................91 11.8 Unregistering ETERNUS SF Storage Cruiser..........................91 Chapter 12 Pre-configuration for Resource Registration and Modification................92 12.1 Overview......................................92 12.2 Importing the System Configuration File............................94 12.3 Exporting the System Configuration File............................97 Chapter 13 Network Map................................98 13.1 Overview......................................98 13.2 Preparations.....................................99 13.3 Screen Layout....................................100...
Page 15 18.3 Changing Server Switchover Settings............................150 18.4 Canceling Server Switchover Settings............................150 Chapter 19 Collecting Power Consumption Data and Displaying Graphs................152 19.1 Exporting Power Consumption Data.............................152 19.2 Displaying Power Consumption Data Graphs..........................154 Appendix A User Interface..............................157 A.1 ROR Console....................................157 Menus......................................159 A.2.1 List of Menus...................................159 A.2.2 Popup Menus...................................162...
Page 16: Chapter 1 Login And Logout
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.
Page 17 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.
Page 18 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.
Page 19: Chapter 2 Home
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.
Page 20 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. Click [OK].
Page 21: Chapter 3 Resource Management Overview
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.
Page 22: Chapter 4 License Setup And Confirmation
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: After logging in to Resource Orchestrator, select [Tools]-[Licenses] from the menu, and click <Add> in the displayed dialog. The [Register License] dialog is displayed.
Page 23: Chapter 5 Managing User Accounts
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. From the ROR console menu, select [Settings]-[User Accounts]. The [User Accounts] dialog is displayed.
Page 24 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. Click <OK>.
Page 25: Chapter 6 Bladeviewer
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.
Page 26: Screen Layout
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.
Page 27: Status 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.
Page 28: Blade Panel
Table 6.4 Chassis Icon Icon Meaning Chassis 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".
Page 29 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...
Page 30 Table 6.8 Physical Server Icons Icon Meaning Server Spare server Unregistered server Maintenance mode server 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...
Page 31: Vm Guest List
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...
Page 32 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 For details on the different VM guest statuses, refer to "Table 6.3 Status Icons"...
Page 33: Resource Details
Power button Color Status Meaning Power OFF in Orange (blinking) Power OFF in progress. 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.
Page 34 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"...
Page 35: Vm Guest
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 <OK> 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"...
Page 36: Status Panel Operations
Power button Color Status Action Green (lit) Power ON 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"...
Page 37: Listing And Editing Of Labels And Comments
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".
Page 38: Editing Contacts
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 <Modify>. 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.
Page 39 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.
Page 40: Chapter 7 Registering Resources
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.
Page 41: Registering Vm Management Software
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: Boot from the first admin LAN network interface (NIC1 (Index1)) 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.
Page 42: When Using Blade Servers
Password Enter the password for VM management software. Enter up to 128 characters, including alphanumeric characters and symbols (ASCII characters 0x20 to 0x7e). Click <OK>. 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.
Page 43: Registering Blade Servers
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 ("-"). Click <OK>. 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_name - Slot_number [Unregistered]].
Page 44 Figure 7.1 Status Transition Diagram for Managed Servers Use the following procedure to register blade servers. 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.
Page 45 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.
Page 46 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.
Page 47: Registering Lan Switch Blades
Click <OK>. 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.
Page 48: Configuring Vlans On Lan Switches
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.
Page 49: Configuring Vlans On External Ports
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. In the ROR console server resource tree, right-click the target LAN switch blade and select [Modify]-[Network Settings] from the popup menu.
Page 50: Hba Address Rename Settings
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 (","). Click <OK>...
Page 51 Figure 7.2 Status Transition Diagram for Managed Servers Use the following procedure to register rack mount or tower servers. 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. 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.
Page 52 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.
Page 53 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"...
Page 54 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.
Page 55: Registering Lan Switches
7.4.2 Registering LAN Switches Use the following procedure to register LAN switches: Discover LAN switches. For instructions, refer to "Discovery". Register LAN switches displayed in the network device tree. For instructions, refer to "Registration". Discovery From the ROR console menu, select [Tools]-[Topology]-[Discover LAN switches]. The [Discover LAN Switches] dialog is displayed.
Page 56: Hba Address Rename Settings
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 ("-"). Click <OK>. 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.
Page 57 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".
Page 58 Figure 7.4 Procedures for Multi-path Configurations Example For a server with two ports, WWNs could be configured as follows. WWNN value provided by "I/O Virtualization Option": 20:00:00:17:42:51:00:00 Values to set in the [HBA address rename settings] dialog "WWNN" value 20:00:00:17:42:51:00:00 "HBA port number"...
Page 59: When Using Primequest Servers
The server restart is not required in other cases. The WWN that has been set is enabled at the next restart. Click <OK>. 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.
Page 60: Registering Primequest Servers
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.
Page 61: Registering Sparc Enterprise (M3000/T Series) And Sparc M10-1/M10-4
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.
Page 62 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. 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.
Page 63 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.
Page 64: Registering Power Monitoring Devices
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"...
Page 65: Registering Admin Lan Subnets
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.
Page 66 . Delete the registry replication settings from the following "Services and Applications" of the manager. Based on the following table, delete registry replication for the resources. Resources for Registry Key Deletion [HKEY_LOCAL_MACHINE\]SOFTWARE\Wow6432Node\Fujitsu \SystemcastWizard\ResourceDepot Deployment Service [HKEY_LOCAL_MACHINE\]SOFTWARE\Wow6432Node\Fujitsu \SystemcastWizard\DatabaseBroker\Default [HKEY_LOCAL_MACHINE\]SOFTWARE\Wow6432Node\Fujitsu PXE Services...
Page 67 Using Explorer, copy the following folder from the local disk of the primary node to the folder on the shared disk. Local Disk (Source) Shared Disk (Target) %SystemRoot%\System32\dhcp Drive_name :\Fujitsu\ROR\SVROR\dhcp Example When the OS has been installed on the C drive, it is %SystemRoot%C:\Windows. - 52 -...
Page 68 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: Drive_name :\Fujitsu\ROR\SVROR\dhcp /T /P "NT AUTHORITY\SYSTEM:F" "BUILTIN >cacls \Administrators:F" "NT SERVICE\DHCPServer:F" <RETURN>...
Page 69 Copy the files and directory on the local disk of the primary node to the shared disk for managers. Execute the following command: # tar cf - copy_target | tar xf - -C Shared_disk_mount_point /Fujitsu/ROR/SVROR <RETURN> Files and Directory to Copy - /etc/dhcpd.conf (*1) - /etc/dhcp/dhcpd.conf (*2)
Page 70 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 Change the settings of the DHCP service (Primary node) Change the following files when registering the admin LAN subnet, and set the takeover logical IP address after the change to the DHCP server.
Page 71: Registering Eternus Sf Storage Cruiser
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.
Page 72: Chapter 8 Changing Admin Server Settings
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. Log on to the admin server with OS administrative privileges.
Page 73 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". 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"...
Page 74 On the primary node, bring online the shared disk and IP address, and take all other resources offline. Next, remove the following registry key from the registry replication settings set for the [PXE Services] cluster resource. SOFTWARE\Wow6432Node\Fujitsu\SystemcastWizard\DHCP SOFTWARE\Fujitsu\SystemcastWizard\DHCP Use the following procedure to remove the registry key.
Page 75 Click <Add> on the [Registry Replication] tab. The [Registry Key] window will be displayed. Configure the above registry key in [Root registry key]. Click <OK>. After configuration of the registry keys is complete, click <Apply>. Click <OK> to close the dialog. Assign the manager's shared disk and IP address to the secondary node.
Page 76: Changing Port Numbers
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. Unmount the shared disk.
Page 77 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.
Page 78 Change the port numbers. Open the Windows Registry Editor, and search for the following subkey: When using a 32-bit version of Windows: Key name: HKEY_LOCAL_MACHINE\SOFTWARE\Fujitsu\SystemcastWizard\CLONE When using a 64-bit version of Windows: Key name: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Fujitsu\SystemcastWizard\CLONE Select "PortBase" from the registry entries under this subkey.
Page 79: Changing The Maximum Number Of System Image Versions
Change the port numbers. Edit the following file: /etc/opt/FJSVscw-common/scwconf.reg. In PortBase (under HKEY_LOCAL_MACHINE\SOFTWARE\Fujitsu\SystemcastWizard\CLONE), set the first value of the port number to be used by deployment services. This value should be entered in hexadecimal format. To avoid conflicts with ephemeral ports, use a value not included in the ephemeral port range defined by "net.ipv4_local_port_range".
Page 80: Changing The Maximum Number Of Cloning Image Versions
Bring the manager's shared disk online, and take all other resources offline. Next, remove the following registry key from the registry replication settings set for the [Deployment Service] cluster resource. SOFTWARE\Wow6432Node\Fujitsu\SystemcastWizard\ResourceDepot SOFTWARE\Fujitsu\SystemcastWizard\ResourceDepot Use the following procedure to remove the registry key.
Page 81: Changing The Password For The Resource Orchestrator Database
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. In the [Registry Replication] tab, select the above registry key. Click <Remove>.
Page 82 Log on to the admin server with OS administrative privileges. Stop the manager. Stop the manager, referring to "2.1 Starting and Stopping the Manager" in the "Operation Guide VE". Change the password for the Resource Orchestrator database. Execute the rcxadm dbctl modify command. Enter the new password interactively.
Page 83: Chapter 9 Changing Resources
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.
Page 84: Changing Admin Ip Addresses
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".
Page 85: Changing Snmp Communities
Change [Admin LAN (IP address)]. Click <OK>. 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.
Page 86: Changing Server Management Unit Configuration Settings
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. Change [SNMP Community]. Click <OK>. The SNMP community is changed. 9.1.5 Changing Server Management Unit Configuration Settings This section explains how to modify server management unit settings.
Page 87: Changing Port Numbers
Change the remote server management settings. If the user account is changed, it should still have administrator authority. 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. Select the [Modify remote server management login account] checkbox.
Page 88: Changing The Vlan Settings Of Lan Switch Blades
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. In the ROR console server resource tree, right-click the target VM host, and select [Modify]-[VM Host Login Account] from the popup menu.
Page 89: Changing Admin Lan Subnets
9.1.11 Changing Admin LAN Subnets Use the following procedure to change an admin LAN subnet. From the ROR console menu, select [Settings]-[Admin LAN Subnet]. The [Admin LAN Subnet] dialog is displayed. Select the subnet to change. The [Change Admin LAN Subnet] dialog is displayed. In the [Change Admin LAN Subnet] dialog, set the following items.
Page 90: Changing The Ip Address Of The Admin Server
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.
Page 91: Changing Lan Switch Settings
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. Click <OK>. To change registered VIOM server profiles, follow the procedure described in "7.1.1 Registering VIOM Server Profiles"...
Page 92: Changing Vlans Set For External Ports Of Lan Switch Blades
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 "...
Page 93 Physical Port, Link Aggregation Select [Untagged] from the VLAN type of the port number to configure or link aggregation group name. Click <OK>. 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: In the ROR console server resource tree, right-click the target LAN switch blade and select [Modify]-[Network Settings] from the popup menu.
Page 94: Re-Discovering Lan Switches
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: In the ROR console server resource tree, right-click the target LAN switch blade and select [Modify]-[Network Settings] from the popup menu.
Page 95: Changing Power Monitoring Environment Settings
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 .
Page 96: Canceling Collection Settings For Power Monitoring Environments
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. Click <Apply>.
Page 97: Changing Monitoring Information Settings
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...
Page 98: Changing Storage Unit Basic Information
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. Click <OK>. 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.
Page 99: Changing Disk Resource Basic Information
Click <OK>. 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 Select the target virtual storage in the ROR console storage tree.
Page 100: Chapter 10 Configuring The Operating Environments Of Managed Servers
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.
Page 101 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. 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"...
Page 102: Deploying Cloning Images
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.
Page 103: Chapter 11 Deleting Resources
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.
Page 104: Canceling Viom Integration
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.
Page 105: Deleting Lan Switches
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.
Page 106: Deleting Power Monitoring Devices
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: In the ROR console power monitoring devices tree, right-click the target power monitoring device and select [Delete] from the popup menu.
Page 107: Chapter 12 Pre-Configuration For Resource Registration And Modification
Resource Orchestrator provides a sample in CSV format. To obtain a copy of the Excel template (hereafter system configuration template), please contact Fujitsu technical staff. This system configuration template makes it easy to create system configuration files in CSV format.
Page 108 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"...
Page 109: Importing The System Configuration File
Note The following operations cannot be performed by the pre-configuration function, and should be performed from the ROR console. Deleting registered resources from Resource Orchestrator Changing the name of a registered chassis, physical server (only for servers other than PRIMERGY BX servers) or a power monitoring device Deleting registered admin LAN subnets Discovering, registering, or changing registration settings of a LAN switch...
Page 110 In the ROR console, select [File]-[System Configuration File]-[Import] from the menu. The [Import System Configuration File] dialog is displayed. Specify a configuration file prepared in step 1. Click <OK>. 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.
Page 111 When changing physical server names during pre-configuration, it cannot be performed at the same time as other pre- configuration operations. Import the "Server" section separately from other sections. 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.
Page 112: Exporting The System Configuration File
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.
Page 113: Chapter 13 Network Map
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.
Page 114: Preparations
The following actions are available in the Network Map. Switching between map types Screen scrolling Scroll button Map drag and drop Navigation map drag and drop Maximizing and minimizing of the display area Configuring automatic update to show the latest status Updating to show the latest status Hiding of the navigation map Hiding of display filter options...
Page 115: Screen Layout
Detect physical network links From the ROR console menu, select [Tools]-[Topology]-[Detect physical links]. The [Detect Physical Links] dialog is displayed. Click <OK>. 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.
Page 116: Map Types
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.
Page 117: Resource Icons
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.
Page 118 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.
Page 119 Table 13.3 LAN Switch Blade Icons Icon Status Meaning No new errors or warnings were normal detected from the LAN switch (*1) (*2) blade. A warning was detected from the warning LAN switch blade. (*1) (*2) The status of the LAN switch blade unknown could not be obtained.
Page 120 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.
Page 121: Vlan Display
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.
Page 122: Other Icons
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".
Page 123: Network Links
Table 13.10 Admin Server Icon Icon Status Meaning Admin server 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.
Page 124: Aggregate Display Of Network Links
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.
Page 125: Display Filters
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).
Page 126: Chapter 14 Power Control
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. In the ROR console server resource tree, right-click the desired server (or the physical OS or VM host running on the server) or VM guest, select [Power] from the popup menu, and select one of the following options: This option powers on a halted resource and starts its operating system.
Page 127: Chassis Power Control
[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.
Page 128: Chapter 15 Control Of Vm Environments
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"...
Page 129: Vm Maintenance Mode Of Vm Hosts
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"...
Page 130: Migrating To 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.
Page 131: External Software
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.
Page 132: Chapter 16 Backup And Restore
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.
Page 133: Backup
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.
Page 134 > Installation_folder \SVROR\Manager\bin\rcxadm server set -name physical server -attr bootagt=dos <RETURN> [Linux Manager] physical server -attr bootagt=dos <RETURN> #/opt/FJSVrcvmr/bin/rcxadm server set -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"...
Page 135 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.
Page 136: Restore
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. Place the target server into maintenance mode.
Page 137 Click <OK>. 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.
Page 138: Viewing
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.
Page 139: Chapter 17 Cloning [Physical Servers]
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.
Page 140: Collecting
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.
Page 141 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"...
Page 142 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.
Page 143 "yes" means that the password is encrypted. If this line exists, the rcxadm deployctl command does not operate. Example With KMS (Automatic Search) [ActivationInfo] .cmd.remotescript.1.params.kmscheck=AUTO .cmd.remotescript.1.params.ieproxy=proxy.activation.com:8080 .cmd.remotescript.1.params.password=PASSWORD With KMS (Manual Settings) [ActivationInfo] .cmd.remotescript.1.params.kmscheck=MANUAL .cmd.remotescript.1.params.kmsname=fujitsu.activation.com .cmd.remotescript.1.params.kmsport=4971 .cmd.remotescript.1.params.ieproxy=proxy.activation.com:8080 .cmd.remotescript.1.params.password=PASSWORD With MAK [ActivationInfo] .cmd.remotescript.1.params.makkey=11111-22222-33333-44444-55555 - 128 -...
Page 144 .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"...
Page 145 Collect a cloning image. 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. To use this feature, the following settings must first be defined: Cloning Image Name Enter a name to identify the collected cloning image.
Page 146: Deploying
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. Click <OK>. 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).
Page 147 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)"...
Page 148 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: Place the destination server(s) into maintenance mode (only for agent-registered servers).
Page 149 [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. Click <OK>. The cloning image deployment process starts.
Page 150 Click <OK>. The cloning image deployment process starts. The process status can be checked in the Recent Operations area of the ROR console. Clicking <Cancel> 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.
Page 151: Viewing
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 cannot be performed simultaneously on the cloning...
Page 152: Deleting
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".
Page 153 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.
Page 154 [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.conf) The definition file is made up of the following entries: One or more node entries...
Page 155 Table 17.3 Node Entry Settings Setting Keyword Expected Values: Description Managed server Physical server Physical server name that was set when NODE_NAME name name 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.
Page 156 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.
Page 157: Operation Checks And Preparations
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 <RETURN> [Linux] # /opt/FJSVrcxat/bin/rcxadm lanctl enable <RETURN> For details on the command, refer to "5.9 rcxadm lanctl" in the "Reference Guide (Command) VE". 17.6.1 Operation Checks and Preparations Use the following procedure to actually apply the definition file's settings on the reference server and prepare a cloning image to be used for further server deployments.
Page 158: Maintenance
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". Using the /opt/FJSVhanet/usr/sbin/dsppoll Command # /opt/FJSVhanet/usr/sbin/dsppoll <RETURN>...
Page 159: Clearing Settings
[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.
Page 160 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 auto- configuration function: Register the newly added servers. Perform the following procedure on a reference server chosen between already running servers: Clearing Network Parameter Settings Execute the rcxadm lanctl unset command to clear the network parameters configuration.
Page 161: Chapter 18 Server Switchover Settings
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.
Page 162 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.
Page 163 [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.
Page 164 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.
Page 165: Changing Server Switchover Settings
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...
Page 166 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. Clear the checkbox in the [Select] column for the desired spare server. Click <OK>.
Page 167: Chapter 19 Collecting Power Consumption Data And Displaying Graphs
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.
Page 168 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.
Page 169: Displaying Power Consumption Data Graphs
Rate Output time span Output device count Daily Last year Monthly Select "Custom" and specify 5 years Annual Select "Custom" and specify 5 years 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.
Page 170 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)
Page 171 Click <Graph Output>. 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.
Page 172: Appendix A User Interface
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".
Page 173 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.
Page 174: Menus
[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.
Page 175 Privileged Menu Submenu General User Function User Returns the layout of the ROR console View Reset Layout to its initial state. Chassis Registers a chassis. Server Registers a server. SPARC Enterprise Registers a SPARC Enterprise (M3000/T Series) (M3000/T series) server. SPARC Enterprise Registers SPARC Enterprise M4000/ (Partition Model)
Page 176 Privileged Menu Submenu General User Function User Performs viewing, registration, Admin LAN Subnet Yes (*8) changing or deletion of the admin LAN subnet information. Update Updates a resource. Powers on a server. Powers off a server after shutting down its operating system. Powers off a server without shutting OFF (Forced) Power...
Page 177: Popup Menus
Privileged Menu Submenu General User Function User Modifies client and environmental data Options Yes (*11) settings. Environmental Data Displays environmental data graphs. Graph *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.
Page 178 * 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. Register Agent Register the agent. Delete Deletes a server. Update Updates a server.
Page 179 Table A.5 Popup Menus Available for SPARC Servers/SPARC Enterprise Popup Menu Function Menu Submenu Server (*1) Registers a server. Register Agent Register the agent. Delete Deletes a SPARC Servers/SPARC Enterprise. Update Updates a SPARC Servers/SPARC Enterprise. Modifies a SPARC Servers/SPARC Enterprise's Registration Settings registration settings.
Page 180 Popup Menu Function Menu Submenu Reboots a server after shutting down its operating Reboot system. Reboots a server without shutting down its operating Reboot (Forced) system. Switchover Switches over a server with one of its spare servers. Spare Server (*1, *3, Failback Switches back a server to its pre-switchover state.
Page 181 Popup Menu Function Menu Submenu Powers on an operating system. Powers off a server after shutting down its operating system. Powers off a server without shutting down its operating OFF (Forced) Power system. Reboots a server after shutting down its operating Reboot system.
Page 182 Popup Menu Function Menu Submenu Delete 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...
Page 183: Status Panel
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.3 Status Panel Status Monitoring Area The Event Log monitors a history of events that have occurred on managed resources.
Page 184 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.
Page 185 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.
Page 186: Resource List] Tab
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_ORDER RESOURCE_TREE_SORT_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. registered: Displays the resource list in the order in which the resources were registered or created.
Page 187: Resource Details] Tab
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.
Page 188: Chassis Attributes
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 Registered server blade. Detected storage blade. Currently displayed server blade. Server blade selected within the chassis image.
Page 189 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.
Page 190: Server Attributes
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.
Page 191 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.
Page 192 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.
Page 193: Physical Os, Vm Host, And Vm Guest Attributes
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.
Page 194 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.
Page 195 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.
Page 196 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...
Page 197: Network Device Attributes
The model name of a network device is displayed. For NS appliances, "NSAppliance" is displayed. Vendor The vendor name of a network device is displayed. For NS appliances, "Fujitsu" is displayed. Serial number The serial number of a network device is displayed. For NS appliances, "-" is displayed.
Page 198 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.
Page 199: Power Monitoring Devices (Pdu Or Ups) Attributes
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.
Page 200: Management Software Attributes
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.
Page 201: Image List] Tab
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.
Page 202: Network Map
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 For details on the Network Map, refer to "Chapter 13 Network Map".
Page 203: Event
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.
Page 204: Dialogs
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.
Page 205 <Deselect All> button Deselects all dialog checkboxes. Click <Apply>. The new settings are applied. - 190 -...
Page 206: Appendix B Format Of Csv System Configuration Files
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.
Page 207: File Format
From the ROR console The System Configuration Template can be obtained from a Resource Orchestrator manager installation. Open and log in to the ROR console according to "Chapter 1 Login and Logout". Select [File]-[System Configuration File]-[Download Template] from the ROR console menu. Displays the [File Download] window.
Page 208 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].
Page 209 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".
Page 210 Order Section Name Chassis PRIMERGYPartitionModelChassis SPARCEnterprisePartitionModelChassis SPARCM10PartitionModelChassis LanSwitch LanSwitchNet Server SPARCEnterprise PRIMERGYPartitionModelServer ServerNet SPARCEnterprisePartitionModelServer SPARC SPARCM10 SPARCM10PartitionModelServer ServerWWNN (*1) SpareServer (*1) VMManager ServerAgent (*2, *3) ServerVMHost (*2, *3) MonitorSetting PowerDevice Memo (*2) *1: When loading from the system configuration template in the Excel format, the operation column information will be skipped. *2: When loading from the system configuration template in the Excel format, the whole section will be skipped.
Page 211: Resource Definitions
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).
Page 212 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"...
Page 213 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 ("-").
Page 214 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.
Page 215 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.
Page 216 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.
Page 217 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. PY CB Eth Switch/IBP 1Gb 36/12 PY CB Eth Switch/IBP 1Gb 36/8+2 PY CB Eth Switch/IBP 1Gb 18/6 PY CB Eth Switch/IBP 10Gb 18/8...
Page 218 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.
Page 219 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"...
Page 220 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).
Page 221 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.
Page 222 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. "!", "@", "#", "$", "%", "^", "&", "*", "[", "]", "{", "}", "(", ")", "-", "+", "=", "~", ",", ">", "<", "/", "'", "?", ";", ":"...
Page 223 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.
Page 224 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"...
Page 225 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.
Page 226 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.
Page 227 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.
Page 228 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).
Page 229 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"...
Page 230 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 ("-").
Page 231: Examples Of Csv Format
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.
Page 232 [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.150,public [PRIMERGYPartitionModelChassis] operation,chassis_name,ip_address,snmp_community_name,mgmt_user_name,mgmt_passwd,mgmt_passwd_enc -,pqchassis0,192.168.3.207,public,administrator,administrator,plain -,pqchassis1,192.168.3.208,public,administrator,administrator,plain [SPARCEnterprisePartitionModelChassis] operation,chassis_name,ip_address,snmp_community_name,mgmt_user_name,mgmt_passwd,mgmt_passwd_enc -,spechassis,192.168.3.212,public,fujitsu,fujitsu,plain [SPARCM10PartitionModelChassis] operation,chassis_name,ip_address,snmp_community_name,mgmt_user_name,mgmt_passwd,mgmt_passwd_enc -,sparcm10-1,192.168.10.26,public,xscf,Xk8n5z6MfEg=,encrypted [LanSwitch] operation,chassis_name,slot_no,switch_name,ip_address,snmp_community_name,user_name,passwd,passwd_enc,privile ged_passwd,privileged_passwd_enc,product_name,connection_type -,chassis01,1,switch-01,192.168.3.161,public,admin,admin,plain,admin,plain,BX600 GbE Switch Blade 30/12,telnet -,chassis01,2,switch-02,192.168.3.162,public,admin,admin,plain,admin,plain,BX600 GbE Switch Blade 30/12,telnet [LanSwitchNet] operation,chassis_name,slot_no,port_no,vlan_id -,chassis01,1,31,1/U;10/T;20/T -,chassis01,1,32,1/U -,chassis01,1,33,1/U -,chassis01,1,34,1/U -,chassis01,1,35,1/U...
Page 233 -,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.168.3.157,,,,,,,,1,4,ON -,chassis01,9,blade003,192.168.3.159,,,,,,,,1,4,ON -,,,rackmount001,192.168.3.200,00:E5:35:0C:34:AB,,public,192.168.3.199,admin,admin,plain,,,OFF -,,,rackmount002,192.168.3.202,00:E5:35:0C:34:AC,,public,192.168.3.201,admin,admin,plain,,,OFF [SPARC] operation,server_name,ip_address,mgmt_snmp_community_name,mgmt_ip_address,mgmt_protocol,mgmt_user_name,m gmt_passwd,mgmt_passwd_enc -,spe001,192.168.3.203,public,192.168.3.204,XSCF,fujitsu,fujitsu,plain -,spe002,192.168.3.205,public,192.168.3.206,ILOM,fujitsu,fujitsu,plain [SPARCM10] operation,server_name,ip_address,mgmt_snmp_community_name,mgmt_ip_address,mgmt_protocol,mgmt_user_name,m gmt_passwd,mgmt_passwd_enc -,Sparcm10-1-11,192.168.10.162,public,192.168.10.22,XSCF,xscf,Xk8n5z6MfEg=,encrypted -,Sparcm10-1-12,192.168.10.163,public,192.168.10.23,XSCF,xscf,Xk8n5z6MfEg=,encrypted [SPARCM10PartitionModelServer] operation,chassis_name,partition_no,server_name,ip_address -,sparcm10-1,0,sparcm10-1-0,192.168.10.166 [PRIMERGYPartitionModelServer] operation,chassis_name,partition_no,server_name,ip_address,boot_option -,pqchassis0,0,pqserver01,192.168.3.209,legacy -,pqchassis0,1,pqserver02,192.168.3.210,legacy -,pqchassis0,2,pqserver03,192.168.3.211,legacy [ServerNet] operation,server_name,nic_no,vlan_id -,blade001,1,1/U;10/T;20/T -,blade001,3,1/U -,blade001,5,1/U -,blade002,1,1/U;10/T;20/T...
Page 234 -,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.214 [ServerWWNN] operation,server_name,port_count,wwnn -,blade001,1,20 00 00 17 42 51 00 01 -,blade002,1,20 00 00 17 42 51 00 02 [SpareServer] operation,server_name,spare_server,vlan_switch,auto_switch,boot_type,spare_server_force_off,spare_server_with_vm_g uest -,blade001,blade003,ON,ON,local,OFF,OFF [VMManager] operation,name,ip_address,product,login_name,login_passwd,passwd_enc -,vCenterServer,127.0.0.1,vmware-vc,Administrator,admin,plain [ServerAgent] operation,server_name -,blade001 -,rackmount001 -,rackmount002 [ServerVMHost] operation,server_name,vm_login_name,vm_login_passwd,vm_passwd_enc -,blade002,admin,admin,plain [MonitorSetting] operation,server_name,ping_timeout,recovery_action,reboot_count...
Page 235: Appendix C Maintenance Mode
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.
Page 236: Glossary
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.
Page 237 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.
Page 238 A Solaris environment that has been installed on a physical server. GLS (Global Link Services) Fujitsu network control software that enables high availability networks through the redundancy of network transmission channels. GSPB (Giga-LAN SAS and PCI_Box Interface Board) A board which mounts onboard I/O for two partitions and a PCIe (PCI Express) interface for a PCI box.
Page 239 A system image or a cloning image. Also a collective term for them both. I/O virtualization option An optional product that is necessary to provide I/O virtualization. The WWNN address and MAC address provided is guaranteed by Fujitsu Limited to be unique. Necessary when using HBA address rename. IPMI (Intelligent Platform Management Interface) IPMI is a set of common interfaces for the hardware that is used to monitor the physical conditions of servers, such as temperature, power voltage, cooling fans, power supply, and chassis.
Page 240 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.
Page 241 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.
Page 242 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.
Page 243 The RAID management tool differs depending on the model or the OS of PRIMERGY servers. Remote Management Controller A unit used for managing servers. Used for gathering server data, failure notification, power control, etc. For Fujitsu PRIMERGY servers iRMC2 For SPARC Servers/SPARC Enterprises ILOM (T series servers)
Page 244 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.
Page 245 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.
Page 246 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.
Page 247 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.

This manual is also suitable for:

Serverview resource orchestrator virtual edition v3.1.1

Fujitsu ServerView Respurce Orchestrator Virtual Edition V3.1.0 User Manual

Chapter 1 Login and Logout

Chapter 2 Home

Chapter 3 Resource Management Overview

Chapter 4 License Setup and Confirmation

Chapter 5 Managing User Accounts

Chapter 6 Bladeviewer

Chapter 7 Registering Resources

Chapter 8 Changing Admin Server Settings

Chapter 9 Changing Resources

Chapter 10 Configuring the Operating Environments of Managed Servers

Chapter 11 Deleting Resources

Chapter 12 Pre-Configuration for Resource Registration and Modification

Chapter 13 Network Map

Chapter 14 Power Control

Chapter 15 Control of VM Environments

Chapter 16 Backup and Restore

Chapter 17 Cloning [Physical Servers]

Chapter 18 Server Switchover Settings

Chapter 19 Collecting Power Consumption Data and Displaying Graphs

Appendix A User Interface

Appendix B Format of CSV System Configuration Files

Appendix C Maintenance Mode

Quick Links

Related Manuals for Fujitsu ServerView Respurce Orchestrator Virtual Edition V3.1.0

Summary of Contents for Fujitsu ServerView Respurce Orchestrator Virtual Edition V3.1.0

This manual is also suitable for:

Table of Contents