Page 1: Resource Management
ServerView Resource Orchestrator Cloud Edition V3.1.1 User's Guide for Infrastructure Administrators (Resource Management) Windows/Linux J2X1-7612-05ENZ0(03) March 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 Point Refer to the user role manuals displayed in the table below for roles that are not in the diagram. Roles that are not in the diagram Roles that are in the diagram Infrastructure operator...
Page 3 Purpose This manual provides an outline of the operation method of the ROR console provided by ServerView Resource Orchestrator (hereinafter Resource Orchestrator). Target Readers This manual is written for system administrators who will use Resource Orchestrator to operate the infrastructure in private cloud or data center environments.
Page 4 Chapter 15 L-Server Template Operations Explains how to operate L-Server templates. Chapter 16 Creating L-Servers Explains how to create L-Servers. Chapter 17 L-Server Operations Explains how to operate L-Servers. Chapter 18 Linking L-Servers with Configured Physical Servers or Virtual Machines Explains how to link a configured physical server to a physical L-Server and how to link a configured virtual machine to a virtual L- Server.
Page 5 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 6 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 Microsoft(R) Windows Server(R) 2003 R2, Enterprise Edition Windows...
Page 7 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 8 Abbreviation Products Red Hat(R) Enterprise Linux(R) 5.8 (for x86) Red Hat(R) Enterprise Linux(R) 5.8 (for Intel64) Red Hat(R) Enterprise Linux(R) 6.2 (for x86) Red Hat(R) Enterprise Linux(R) 6.2 (for Intel64) Red Hat Enterprise Linux 6 Red Hat(R) Enterprise Linux(R) 6.3 (for x86) Red Hat(R) Enterprise Linux(R) 6.3 (for Intel64) Red Hat(R) Enterprise Linux(R) 5.4 (for x86) Linux Virtual Machine Function RHEL5-Xen...
Page 9 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 10 All other brand and product names are trademarks or registered trademarks of their respective owners. Notices The contents of this manual shall not be reproduced without express written permission from FUJITSU LIMITED. The contents of this manual are subject to change without notice.
Page 11: Table Of Contents
Contents Chapter 1 Resource Management Overview...........................1 Chapter 2 License Setup and Confirmation..........................2 Chapter 3 Configuring Users for Infrastructure Administrators....................3 3.1 Registering User Accounts..................................3 3.2 Viewing a User Account..................................4 3.3 Modifying a User Account..................................5 3.4 Deleting a User Account..................................5 Chapter 4 BladeViewer................................7 Overview......................................7 4.2 Screen...
Page 12 5.10 Registering Power Monitoring Devices............................51 5.11 Registering Admin LAN Subnets..............................52 5.12 Registering BMC BladeLogic Server Automation..........................58 Chapter 6 Changing Admin Server Settings...........................59 6.1 Changing Admin IP Addresses................................59 6.2 Changing Port Numbers..................................63 6.3 Changing the Maximum Number of System Image Versions......................66 6.4 Changing the Maximum Number of Cloning Image Versions (Physical Servers)................66 6.5 Changing the Maximum Number of Cloning Image Versions (Virtual...
Page 13 Chapter 9 Deleting Resources...............................93 9.1 Deleting Chassis....................................93 9.2 Deleting Managed Servers.................................93 9.3 Canceling VIOM Integration................................94 9.4 Deleting LAN Switches and Network Devices..........................95 9.4.1 Deleting LAN Switch Blades..............................95 9.4.2 Deleting LAN Switches and Network Devices..........................95 9.5 Deleting Network Resources................................96 9.6 Deleting VM Management Software..............................97 9.7 Clearing the Power Monitoring Environment...........................97...
Page 14 Chapter 15 L-Server Template Operations.......................... 149 15.1 Operations Using the Wizard GUI..............................149 15.1.1 Viewing....................................149 15.1.2 Creating....................................151 15.1.2.1 Creating a Physical L-Server Template...........................151 15.1.2.2 Creating a Virtual L-Server Template..........................155 15.1.3 Modifying....................................160 15.1.4 Copying....................................161 15.1.5 Deleting....................................161 15.1.6 Export......................................162 15.1.7 Import......................................162 15.1.8 Creating a Template Using Another Existing Template......................162 15.2 Editing a Template Using an Editor..............................163...
Page 15 17.8 Allocating and Releasing Resources to L-Servers.........................224 17.8.1 Installation....................................225 17.8.2 Operations....................................227 17.8.2.1 Allocating Resources...............................227 17.8.2.2 Releasing Resources................................227 17.8.2.3 Modifying Configuration Definition Information......................227 17.9 Changing Physical Server Usage..............................228 17.9.1 Configuring L-Servers for Usage Change..........................228 17.9.1.1 When only the Configuration Definition (defined) is Created..................228 17.9.1.2 When Resources are Already Allocated (allocated)......................229...
Page 16 A.1 ROR Console....................................267 Menus......................................270 A.2.1 List of Menus...................................271 A.2.2 Popup Menus...................................274 A.3 Status Panel.....................................284 A.4 Tree Panel.......................................285 A.5 [Resource List] Tab..................................289 A.6 [Resource Details] Tab...................................290 A.6.1 Chassis Attributes..................................292 A.6.2 Server Attributes..................................293 A.6.3 Physical OS, VM Host, and VM Guest Attributes........................297 A.6.4 Network Device Attributes..............................301 A.6.5 Power Monitoring Devices (PDU or UPS)
Page 17: Chapter 1 Resource Management Overview
Chapter 1 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 18: Chapter 2 License Setup And Confirmation
Chapter 2 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 19: Chapter 3 Configuring Users For Infrastructure Administrators
Chapter 3 Configuring Users for Infrastructure Administrators Only users with the infrastructure administrator, tenant administrator, or administrator role can create user accounts. For details on operation methods by a tenant administrator, refer to "Chapter 10 Tenant" in the "User's Guide for Tenant Administrators CE".
Page 20: Viewing A User Account
E-mail address Specify the email address of the user. Specify a string using up to 64 alphanumeric characters or symbols. User Groups Select the user group to configure for the user account from the already created user group. Scopes/Roles (Optional) Access Scope Select the scope of access to set for the user account.
Page 21: Modifying A User Account
3.3 Modifying a User Account This section explains how to modify user accounts and passwords. User Accounts Use the following procedure to modify a user account: In the ROR console, select [Settings]-[User Accounts]. The [User Accounts] dialog is displayed. Select the user account to modify. Click <Modify>.
Page 22 Select the user account to delete. Click <Delete>. The [Delete User Account] dialog is displayed. Confirm the user account to delete. Click <OK>. The selected user account is deleted. From the command-line, execute rcxadm user delete. For details on the rcxadm user delete command, refer to "7.1 rcxadm user" in the "Reference Guide (Command/XML) CE". - 6 -...
Page 23: Chapter 4 Bladeviewer
Chapter 4 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". 4.1 Overview This section provides a functional overview of BladeViewer. BladeViewer provides an intuitive representation of blade servers and their statuses.
Page 24: 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. 4.2 Screen Layout This section explains how the BladeViewer screen is organized.
Page 25: Status Panel
4.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 26: Blade Panel
Table 4.4 Chassis Icon Icon Meaning Chassis For details on the different chassis statuses, refer to "Table 4.3 Status Icons" of "4.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 "4.3.3 Blade Panel".
Page 27 Figure 4.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 4.7 Server Blade Power Buttons Power button Color Status...
Page 28 Table 4.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 4.3 Status Icons" in "4.3.1 Status Panel". When a server blade is used as the admin server, the following admin server icon is displayed. Table 4.9 Admin Server Icon Icon Status...
Page 29: 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 4.11 Resource Icons Icon Meaning...
Page 30 Figure 4.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 4.13 VM Guest Icon Icon Meaning VM guest For details on the different VM guest statuses, refer to "Table 4.3 Status Icons"...
Page 31: 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 "4.4.2 VM Guest" for details. 4.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 32 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 4.5 Power Operation Dialog "Shutdown"...
Page 33: Vm Guest
Figure 4.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 34: 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 35: 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 "4.5.1 Listing and Editing of Labels and Comments".
Page 36: 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 37 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 38: Chapter 5 Registering Resources
Chapter 5 Registering Resources This chapter explains how to register 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 39: 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)) 5.2 Registering VM Management Software This section explains how to register VM management software.
Page 40 source IP address is the IP address of the protocol with the highest priority of protocol binding. When changing the SNMP trap source IP address, change the order of protocol binding. User ID Enter the user ID to use to control VM management software. Enter up to 84 characters, including alphanumeric characters and symbols (ASCII characters 0x20 to 0x7e).
Page 41 associate the VM management software with the VM host. A definition file must be created to associate VM management software with a VM host. Use the UTF-8 character code for definition files. Figure 5.1 Configuration When the IP Address Information of VM Hosts Differ Between the Manager and VM Management Software *1: When the VM host is a rack mount server or another maker's server, only the admin LAN IP address of the VM host can be obtained.
Page 42: Storage Management Software
# Oracle VM Server 192.168.0.10 = 192.168.10.10 192.168.0.11 = 192.168.10.11,172.16.0.11 192.168.0.12 = 192.168.10.12,host01 5.3 Storage Management Software In the following cases, it is necessary to register storage management software with Resource Orchestrator for coordination. When the server type is "Physical" When using RHEL5-Xen as server virtualization software Note For storage management software, only PRIMECLUSTER GDS can be coordinated, when using RHEL5-Xen.
Page 43: Registering Chassis
5.4.1 Registering Chassis This section explains how to register a chassis. Registering chassis makes it possible to use the optional power monitoring settings. When collecting power data, perform the power data collection settings according to "7.8.1 Changing Environmental Data Settings". For details on devices supporting power monitoring, refer to "2.5 Hardware Environment"...
Page 44 Figure 5.2 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 "7.1.10 Changing Boot Options". [Use Admin LAN redundancy] checkbox Check this when performing redundancy for the NIC on the admin LAN. [Apply Admin LAN NIC settings] checkbox 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 Connection Ports
Note VLANs cannot be configured on PRIMERGY BX 900 and BX 400 LAN switch blades operating in IBP mode. 5.4.5 Configuring VLANs on External Connection Ports When not performing automatic VLAN configuration, use the following procedure to configure VLANs on a LAN switch blade's external connection ports.
Page 50: Hba Address Rename Settings
To use this feature, the following settings must first be defined: Port VLAN VLAN ID Enter the VLAN ID to assign to the LAN switch blade port that is connected to the network interface selected in step 2. Tagged VLAN VLAN ID Enter the tagged VLAN ID(s) to assign to the LAN switch blade port that is connected to the network interface selected in step 2.
Page 51: Registering Rack Mount Or Tower Servers
5.5.1 Registering Rack Mount or Tower Servers This section explains how to register a rack mount or tower server. When using VIOM for I/O virtualization, VIOM server profiles should be registered in advance according to the procedure described in "5.1.1 Registering VIOM Server Profiles".
Page 52 Association with server management software (ServerView) Enable/Disable SNMP Community Admin LAN IP address MAC address (NIC1) For physical L-Servers, specify the MAC address of the second specified NIC decided in "9.1.1 Admin LAN Network Design" in the "Design Guide CE". SAN Boot/Admin LAN Redundancy [Use Admin LAN redundancy] checkbox MAC address (NIC2)
Page 53 Remote management controller IP address Enter the IP address of this server's remote management controller. User ID Enter the ID of a remote management controller user account with administrative authority over this server. Enter up to 16 characters, including alphanumeric characters and symbols (ASCII characters 0x20 to 0x7e). Password Enter the password of the above remote management controller user account.
Page 54 MAC address (NIC2) Enter the MAC address of the second admin LAN network interface. This network interface will be used to enable admin LAN redundancy on the registered server. Enter a physical MAC address in either one of the following formats: hyphen-delimited ("xx-xx-xx-xx-xx-xx"), or colon- delimited ("xx:xx:xx:xx:xx:xx").
Page 55: Registering Lan Switches
When using HBA address rename setup service, please confirm that the registered server can boot properly using the HBA address rename setup service. If the server cannot be booted properly, ensure that the specified MAC address (NIC2) is correct. 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 56: Hba Address Rename Settings
Example If subnet mask is "255.255.255.0", the number of addresses in the specified range could be any value between 1 and 256. 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 ("-").
Page 57 The HBA address rename function allows the admin server to control the WWNs set on a managed server's HBAs. Since the admin server carried over these settings when performing maintenance on or switching managed servers, it is not necessary to set the storage side configuration again.
Page 58 Figure 5.4 Procedures for Single-path Configurations Figure 5.5 Procedures for Multi-path Configurations - 42 -...
Page 59: Registering Network Resources
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" on board: 2 Values actually set by the admin server on the HBA (WWPNs are generated automatically) WWNN value for ports 1 and 2 of the HBA : 20:00:00:17:42:51:00:00...
Page 60: Registering Network Devices
Prerequisites for Resource Orchestrator Operation The prerequisites for the network environment, VM host, and physical server used to run Resource Orchestrator differ depending on the L-Server used. For Physical L-Servers Refer to "D.4 Network Preparations" in the "Design Guide CE". For Virtual L-Servers Refer to "Appendix E Preparations for Creating a Virtual L-Server"...
Page 61: Creating The Network Configuration Information (Xml Definition)
The devices that need to be registered as network devices must meet the following conditions: Network devices to be automatically configured using the "auto-configuration for network device" function Network devices to be monitored using the "Network monitoring" function Resource Orchestrator supports registration of the following types of network devices. Firewall Server Load Balancer LAN Switches...
Page 62: When Using Primequest Servers
Deletion of a network device using the rcxadm netdevice delete command is not possible because the target network device cannot be identified. Refer to "9.4.2 Deleting LAN Switches and Network Devices" to delete the target network device. The intended network device may not be automatically configured. Disaster Recovery may fail.
Page 63: Registering Primequest Servers
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. Click <OK>. The mounted chassis will be displayed under the server resource tree. chassis_name - partition mounted...
Page 64: Registering Sparc Enterprise (M3000/T Series) And Sparc M10-1/M10-4
SNMP Community Enter the SNMP community of the XSCF used to manage the target chassis. Either select [public] or enter an arbitrary string. Enter a string of up to 32 alphanumeric characters, underscores ("_"), and hyphens ("-"). Remote management controller (XSCF) User ID Enter the ID of an XSCF user account with administrative authority over the target chassis.
Page 65 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. Physical Server Name [Register agent] checkbox Remote management controller (ILOM/XSCF) Controller type IP address User ID Password...
Page 66 with an alphabet character. This user should have "platadm" privileges for XSCF. The user ID reserved for the system cannot be used. Create another user ID. For details, refer to the XSCF manuals. Password Enter the password of the above XSCF user account. Enter up to 32 characters, including alphanumeric characters, blank spaces ("...
Page 67: Registering Power Monitoring Devices
User ID Enter the user ID to log in to the VM host. Specify the user ID "root" which has VM host administrator authority. Note When using Solaris 11, if user accounts are created during installation, root will be registered for the role. Therefore, the root account cannot be used for login.
Page 68: Registering Admin Lan Subnets
Enter a string of up to 32 alphanumeric characters, underscores ("_"), and hyphens ("-"). This SNMP community will be used to collect power consumption data from this power monitoring device (via SNMP protocol). Voltage Enter the voltage (V) supplied to this power monitoring device. Enter a number between 10 and 999. Power consumption data is calculated using the electrical current value obtained from this power monitoring device and its specified voltage.
Page 69 The name of the primary node is displayed for 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...
Page 70 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 71 The [New DHCP Service Properties] window will be displayed. Change the [Resource Name] on the [General] tab, and set the paths given in the following table. Item Value to Specify Database path Drive_name :\Fujitsu\ROR\SVROR\dhcp\ Drive_name :\Fujitsu\ROR\SVROR\dhcp\ Monitoring file path Backup path Drive_name :\Fujitsu\ROR\SVROR\dhcp\backup\ After making the settings, click <Apply>.
Page 72 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 73 Shared Disk Local Disk 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 74: Registering Bmc Bladelogic Server Automation
5.12 Registering BMC BladeLogic Server Automation This section explains how to register BMC BladeLogic Server Automation. Registration of BMC BladeLogic Server Automation enables use of virtual L-Servers of Solaris zones. For details on the required BMC BladeLogic Server Automation settings, refer to "H.1 Coordination with BMC BladeLogic Server Automation"...
Page 75: Chapter 6 Changing Admin Server Settings
Chapter 6 Changing Admin Server Settings This chapter explains how to change the settings for the admin server. 6.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 76 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 CE". 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 77 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 78 In the [Failover Cluster Management] window, right-click the "PXE Services" resource in [Summary of RC-manager]-[Other Resources], and select [Properties] from the popup menu. The [PXE Services Properties] window will be displayed. Click <Add> on the [Registry Replication] tab. The [Registry Key] window will be displayed. Configure the above registry key in [Root registry key].
Page 79: Changing Port Numbers
Change the takeover logical IP address in the following line to the new takeover logical IP address. option dhcp-server-identifier takeover logical IP address ; 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;...
Page 80 Resource Coordinator Sub Web Server(Mongrel3) (*1) Resource Coordinator Sub Web Server(Mongrel4) (*1) Resource Coordinator Sub Web Server(Mongrel5) (*1) Resource Coordinator DB Server (PostgreSQL) Related Services Deployment Service TFTP Service PXE Services DHCP Server (*2) [Linux Manager] Manager Services rcxmanager rcxtaskmgr rcxmongrel1 rcxmongrel2 rcxmongrel3 (*1)
Page 81 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 82: 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 83: Changing The Maximum Number Of Cloning Image Versions (Virtual Servers)
For details of the methods for changing and checking the generations of cloning images, refer to "5.9 rcxadm imagemgr" in the "Reference Guide (Command/XML) CE". Note If the specified limit is smaller than the number of existing cloning image versions, older versions will not be deleted automatically. In this case, collecting a new cloning image version will require selecting a previous image version for deletion.
Page 84 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 85: 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. Click <Add> on the [Registry Replication] tab. The [Registry Key] window will be displayed. Configure the above registry key in [Root registry key].
Page 86: Chapter 7 Changing Resources
Chapter 7 Changing Resources This chapter explains how to change settings for the admin server or resources registered on the admin server. 7.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 87: Changing Admin Ip Addresses
7.1.3 Changing Admin IP Addresses This section explains how to change admin IP addresses. To change the IP addresses of remote management controllers, refer to "7.1.5 Changing Server Management Unit Configuration Settings". Chassis Use the following procedure to change the IP address of a chassis. Change the IP address of the management blade.
Page 88: Changing Snmp Communities
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. 7.1.4 Changing SNMP Communities This section explains how to change SNMP community settings. For blade servers, PRIMEQUEST servers, or SPARC Enterprise M4000/M5000/M8000/M9000 servers, or servers in SPARC M10-4S Use the following procedure to change SNMP community used by chassis and managed servers.
Page 89: Changing Server Management Unit Configuration Settings
Change [SNMP Community]. Click <OK>. The SNMP community is changed. 7.1.5 Changing Server Management Unit Configuration Settings This section explains how to modify server management unit settings. For rack mount or tower servers Use the following procedure to change remote management controller settings. Change settings on the remote management controller.
Page 90: Changing Port Numbers
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. Then, change the [User ID] and [Password] of [Remote Server Management].
Page 91: Changing The Vlan Settings Of Lan Switch Blades
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. The [Change Login Information] dialog is displayed. Enter the new login account information that was changed on the VM host.
Page 92: Changing Admin Lan Subnets
7.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 93: Changing The Ip Address Of The Hba Address Rename Server
Change the IP address of the admin server according to "7.1.3 Changing Admin IP Addresses", and change the admin IP address for the HBA address rename setup service according to step 12. 7.2.2 Changing the IP Address of the HBA address rename Server This section explains how to change the IP address of the HBA address rename server.
Page 94: Changing Vlans Set For External Connection Ports Of Lan Switch Blades
Connection method SNMP community name Note When changing LAN switch settings as follows due to a configuration change, delete the registered LAN switch blade and register it again. When changing from VCS to another mode, or vice versa When changing a VCS ID or RBridge ID Complete the changes to the settings on the target LAN switch before performing this procedure.
Page 95 When using end host mode for the following LAN switch blades, it is not possible to modify the port VLAN ID, or remove a tag vlan for the external ports which meet the following conditions. When performing the operation, inactivate the target external port, or change the VLAN ID for internal ports which have the same VLAN ID as the target external port.
Page 96 Repeat step 1 and set the new VLAN ID in the [VLAN Settings] dialog. VLAN Select "Create new" or "Change" in the VLAN information and select the VLAN ID to be changed. Physical Port, Link Aggregation Select [Tagged] from the VLAN type of the port number to configure or link aggregation group name. Click <OK>.
Page 97: Re-Discovering Lan Switches
To use this feature, the following settings must first be defined: VLAN Select "Change" and select the VLAN ID that has been changed. Physical Port, Link Aggregation Select [None] from the VLAN type of the port number to delete VLANs or link aggregation group name. Click <OK>.
Page 98: Changing Network Device Settings
Yes: Modification is possible No: Modification is not possible *1: Even after changing external connection ports, virtual switches, port groups, and virtual bridges that have been deployed can be used as is. New information on the external connection ports will be reflected on the configuration of virtual switches, port groups, and virtual bridges deployed after modification of the network resource.
Page 99: Changing Network Device Settings
When the network configuration information retrieved from Resource Orchestrator using the rcxadm netconfig export command exists For how to create network configuration information (XML definitions), refer to "9.4.8 When Registering Network Devices as Resources" in the "Design Guide CE". For details on the rcxadm netconfig command, refer to "3.7 rcxadm netconfig" in the "Reference Guide (Command/XML) CE". 7.6.2 Changing Network Device Settings This section explains how to change settings of a network device.
Page 100: Changing Power Monitoring Environment Settings
The following settings can be changed. Location IP address User ID Password Here the method for changing settings registered with Resource Orchestrator is explained. Complete reconfiguration within the VM management software admin console before performing this procedure. Use the following procedure to change VM management software settings: In the ROR console management software tree, right-click the target management software, and select [Modify]-[Registration Settings] from the popup menu.
Page 101: Canceling Collection Settings For Power Monitoring Environments
Polling interval (in minutes) Enter the time interval of the data collection (1-6 or 10). The number of devices that can be monitored simultaneously depends on the value of this polling interval and the load put on the admin server. The following values are guidelines. Table 7.2 Polling Interval Polling Interval Number of Devices that can be Monitored Simultaneously...
Page 102: Changing Monitoring Information Settings
Use the following procedure to change power monitoring device settings: From the ROR console, right-click the power monitoring device tree, then select [Modify]-[Registration Settings] from the popup menu. The [Modify Power Monitoring Device] dialog is displayed. Make changes to the values as needed. Click <OK>.
Page 103: Changing Storage Unit Basic Information
The following settings can be changed. Label Comments Use the following procedure to change the basic settings of storage management software: In the ROR console storage tree, right-click the target storage management software, and select [Modify]-[Registration Settings] from the displayed menu. The [Resource Change Setting] dialog is displayed.
Page 104: Changing Disk Resource 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>. The basic information of the virtual storage resource is modified. 7.10.4 Changing Disk Resource Basic Information This section explains how to modify the basic information for disk resources.
Page 105 Comments Enter the Comment of the Management software. Enter up to 256 alphanumeric characters or symbols. Click <OK>. The target BMC BladeLogic Server Automation settings are changed. - 89 -...
Page 106: Chapter 8 Configuring The Operating Environments Of Managed Servers
Chapter 8 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 8.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 107 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 108: 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. 8.2 Deploying Cloning Images For the second and subsequent servers, operating systems are created using the cloning image collected from the first server.
Page 109: Chapter 9 Deleting Resources
Chapter 9 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 110: 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 111: Deleting Lan Switches And Network Devices
When there are spare server settings involving the VIOM server profile exchange method When there are servers using the VIOM server profile exchange method that are in the following states Being switched over Have been switched over (prior to failback) Being failed back Server blades that are managed using VIOM, and are currently the target of operations by Resource Orchestrator (power control, image-related processes, etc.)
Page 112: Deleting Network Resources
Note The network devices already deployed to an L-Platform cannot be deleted. When no information is displayed in the line of "AllocatedResources[XXX]:" after executing the rcxadm netdevice show command, it shows that the network device has not been deployed to the L-Platform. For details on the rcxadm netdevice show command, refer to "3.8 rcxadm netdevice"...
Page 113: Deleting Vm Management Software
9.6 Deleting VM Management Software This section explains how to delete VM management software. Use the following procedure to delete VM management software. In the ROR console management software tree, right-click the target management software, and select [Delete] from the popup menu.
Page 114: Deleting Bmc Bladelogic Server Automation
Note It is not possible to delete the information of subnets which have managed servers registered. Before deleting subnet information, delete all managed servers that have been registered on the relevant subnet. 9.9 Deleting BMC BladeLogic Server Automation This section explains how to delete the registered BMC BladeLogic Server Automation. Use the following procedure to delete the registered BMC BladeLogic Server Automation.
Page 115: Chapter 10 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 116 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 "5.1 Registering VIOM Coordination"...
Page 117: 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 118 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 119 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 120: 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 CE". 10.3 Exporting the System Configuration File This section explains the method for exporting a system configuration file containing the current system settings.
Page 121: Chapter 11 Network Map
Chapter 11 Network Map This chapter provides an overview of the Network Map and describes its features. 11.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 122: 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 123: Screen Layout
Network links between two supported LAN switches may not be displayed properly if an unregistered or un-supported LAN switch is placed between them. Example In such a case, the following inconsistencies may be displayed. A LAN switch port maybe seen as being connected to multiple switches (multiple links are shown attached to that switch port).
Page 124 Local map button Selecting a resource icon in the network view will show a button on the upper-right side of this icon. Clicking this button shows the local map. Point The local map and overall map buttons in the map selection area are initially disabled. Selecting a chassis in the network view enables them.
Page 125: Resource Icons
Moreover, selecting a port from a switch in IBP mode will show a list of port groups to which the selected port belongs. If the selected port belongs to more than one port group, all port groups are shown in the displayed list. Expand button Selecting an item listed below will show this button on the upper-right side of this icon.
Page 126 Table 11.2 Server Icons Icon Status Meaning normal No new errors or warnings were detected from the server. warning A warning was detected from the server. unknown The status of the server could not be obtained. error An error was detected from the server. fatal A fatal error was detected from the server, which is now unusable.
Page 127 Table 11.4 VM Host Icons Icon Status Meaning normal No new errors or warnings were detected from the VM host. warning A warning was detected from the VM host. unknown The status of the VM host could not be obtained. error An error was detected from the VM host.
Page 128 Table 11.6 Virtual Switch Icons Icon Status Meaning normal No new errors or warnings were detected from the virtual switch. warning A warning was detected from the virtual switch. unknown The status of the virtual switch could not be obtained. error An error was detected from the virtual switch.
Page 129 Table 11.8 Firewall Icon Status Meaning normal The status of the firewall has been obtained. unknown The status of the firewall could not be obtained. Table 11.9 SLB Icon Status Meaning normal The status of the SLB has been obtained. unknown The status of the SLB could not be obtained.
Page 130: Vlan Display
The port opposite to the selected port. In IBP mode, all ports that belong to the selected port group. In IBP mode, all ports that belong to the same port group as the selected port. 11.4.2 VLAN Display The following resource icons are used when displaying VLANs in the Network Map. Table 11.12 Resource Icons for VLAN Display Icon Meaning...
Page 131: Other Icons
Icon Meaning Integrated network device 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 "11.4.1 Resource Statuses".
Page 132: Network Links
11.5 Network Links This section details the network links displayed in the Network Map. 11.5.1 Link Display The following table details the physical and virtual links displayed between resources. Table 11.15 Links Link Meaning Represents a physical or virtual link. Represents a VLAN link.
Page 133: Display Filters
Example Note Selecting a displayed resource will focus display on that resource. In such a focus mode, all links that are not directly related to the selected resource will be shown in lighter colors. 11.6 Display Filters This section explains how to use display filters. - 117 -...
Page 134 Resource descriptions The display filter area includes the following filters (checkboxes). Selecting or clearing a filter's checkbox will either show or hide the content associated with that filter. Physical links The display filter area includes the following filters (checkboxes). Disabling this filter will hide all physical links between resources on the network map.
Page 135: Chapter 12 Cloning [Physical Servers]
Chapter 12 Cloning [Physical Servers] This chapter explains how to use the server cloning function. 12.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 136: Collecting
EXT3 EXT4 LinuxSwap When the managed server is Windows Server 2012, collection of cloning images from system disks that include ReFS data areas is not possible. The following conditions must be met for the managed server to collect the cloning image from and the managed server to deploy the cloning image to.
Page 137 Has been placed into maintenance mode Cloning images cannot be collected from VM hosts or VM guests. Preparations Install the desired operating system and necessary applications on the managed server from which a cloning image will be collected. Additionally, apply any required patches and other necessary settings. Make sure that the source server operates properly after those steps.
Page 138 Some programs may experience problems when started with a different hostname. If such programs have been installed, configure their services not to start automatically. This has to be configured before collecting the cloning image. Some programs may experience problems when the same server name exists. If such programs have been installed, configure their services not to start automatically.
Page 139 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 .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...
Page 140 With MAK (Already Encrypted Password) [ActivationInfo] .cmd.remotescript.1.params.makkey=11111-22222-33333-44444-55555 .cmd.remotescript.1.params.ieproxy=proxy.activation.com:8080 .cmd.remotescript.1.params.password=xyz123456 encrypted=yes Collecting Cloning Images Use the following procedure to collect cloning images: Place the target server into maintenance mode. In the ROR console server resource tree, right-click the desired server (or its physical OS), and select [Maintenance Mode]- [Set] from the popup menu.
Page 141 When creating a new cloning image, select [New] and enter a new cloning image name. For a cloning image name, enter a character string beginning with an alphabetic character and containing up to 32 alphanumeric characters and underscores ("_"). Update When updating an existing cloning image, select [Update] and select a cloning image from the list.
Page 142: Deploying
12.3 Deploying Once collected, cloning images can be deployed to one or more destination servers. Cloning images collected from the source server can only be deployed to destination servers which satisfy the following conditions: Destination servers should be in either "normal", "warning", "unknown", or "stop" status. Destination servers should have been placed into maintenance mode.
Page 143 It is recommended to back up destination servers before deploying cloning images, as this will simplify the recovery procedure in case of the deployed cloning image is faulty. For details on backing up, refer to "Backup". Note Cloning images cannot be deployed to servers that have been set up as spare servers for other managed servers, when not using I/O virtualization.
Page 144 Select the cloning image to deploy, and set the following items. Server name after deployment Enter the name of the server to which the cloning image is to be deployed. By default, the physical OS name is entered if the physical OS is registered. If the physical OS is not registered, the physical server name is entered.
Page 145 The [Server Name] column displays the names of each destination servers. By default, server names (computer name or hostname) or physical server names are displayed. The names specified in this column will be assigned to destination servers as their computer names (for Windows systems) or system node names (for Linux systems).
Page 146 Release maintenance mode. This step is not required if the [Release from Maintenance Mode after deployment] checkbox was enabled in the [Deploy a Cloning Image] dialog. 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.
Page 147: Viewing
12.4 Viewing This section explains how to display collected cloning images. 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 12.1 Cloning Image List For details on the "Cloning Image List", refer to "A.8 [Image List]...
Page 148: Chapter 13 Collecting Power Consumption Data And Displaying Graphs
Chapter 13 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. 13.1 Exporting Power Consumption Data This section explains how to export power consumption data.
Page 149 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 150: 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 13.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 151 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 152 Click <Graph Output>. After switching to the graph display window, the selected power consumption data can be displayed in line graphs. Figure 13.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 153: Chapter 14 Registering Resources In Resource Pools
Chapter 14 Registering Resources in Resource Pools This section explains how to register a resource managed by Resource Orchestrator to a resource pool. A resource pool is a type of resource folder displayed on the orchestration tree of ROR console, which stores the resources for selection when creating or adding L-Servers.
Page 154: Vm Host Resources
14.1 VM Host Resources This section explains how to register a VM host in a VM pool. Moving an L-Server (migration) is only possible between VM hosts belonging to the same cluster group, when two or more cluster groups are registered in the same VM pool. Use the following procedure to register a VM host in a VM pool: In the ROR console orchestration tree, right-click the target VM pool, and select [Register Resources] from the popup menu.
Page 155: Creating New Network Resources
Network resources can be created using the following methods: Creating new network resources Refer to "14.3.1 Creating New Network Resources". Creating network resources using already registered admin LAN subnets Refer to "14.3.2 Creating Network Resources Using Already Registered Admin LAN Subnets".
Page 156 If a type other than [Admin LAN] is selected. Enter up to 32 characters beginning with an alphanumeric character (upper or lower case), and including alphanumeric characters (upper or lower case), underscores ("_"), periods ("."), or hyphens ("-"). Type Set the network resources type to create using the following option buttons: When creating the public LAN, a network resource name and a VLAN ID must be entered.
Page 157 Port Displays the port number for the external connection port. If the external port is a link aggregation group, the port numbers of the member ports are displayed, separated by commas (","). If the external port is a link aggregation group, the link aggregation group name is displayed. Untagged VLAN Displays the Untagged VLAN information set in the external connection port.
Page 158 Information If a subnet address has been set for the network resource, the IP address can be automatically set when deploying an image to an L-Server. If no subnet address is set, the DHCP settings are adopted. Subnet address/mask xxx . xxx . xxx . xxx " format. Enter the subnet address and subnet mask to set using the "...
Page 159: Creating Network Resources Using Already Registered Admin Lan Subnets
Enter a maximum of 32 characters. Comment (Optional) A custom comment can be defined for the network resource. For example, registering detailed work content, troubleshooting, and recovery procedures can speed up recovery. Enter a maximum of 256 characters. Click <OK>. The network resource is created and registered in a network pool.
Page 160: Network Devices
14.4 Network Devices This section explains how to register a network device in a network pool. Use the following procedure to register a network device in a network pool as a resource: Right-click the target network pool in the orchestration tree, and select [Register Resources] from the popup menu. The [Register Resources] dialog is displayed.
Page 161 Note If iSCSI boot information already registered is specified, the registered information continues to exist. If the registered information is changed, delete the iSCSI boot information using the unregister subcommand, and then register the iSCSI boot information by using the register subcommand again. For Virtual L-Servers Virtual Storage Resources Refer to...
Page 162 In the ROR console orchestration tree, right-click the target storage pool, and select [Register Resources] from the popup menu. The [Register Resources] dialog is displayed. Select the storage resource to register from [Resources]. Resources Virtual storage When creating a specified size of disk automatically from the virtual storage during L-Server creation, select [Virtual storage]. When [Virtual Storage] is selected, the virtual storage resources which can be registered are displayed in the resource list.
Page 163: Address Set Resources
Note When using a LUN that has been created in advance and a LUN for iSCSI boot as a disk resource, if the L-Server is deleted or disks are deleted from L-Servers, the content of disks will remain (is not deleted). When using disk resources that are registered in global pools, perform operation carefully, as the disk resources can be allocated to any users.
Page 164: Virtual Image Resources
14.7.1 Virtual Image Resources This section explains how to register a cloning image to a resource pool. When an image (template) has been created in advance using VM management software, register it to the image pool using the following procedure: When a VM host not managed with server management software is used, it is not necessary to register cloning images.
Page 165: Chapter 15 L-Server Template Operations
Chapter 15 L-Server Template Operations This section explains how to operate an L-Server template. An L-Server template comprises pre-defined specifications (number of CPUs, memory capacity, disk capacity, number of NICs, etc.) for an L-Server. Use the following XML format. There are two ways to create an L-Server template: Using the Wizard GUI L-Server templates can be created using the wizard GUI.
Page 166 The information of registered L-Server templates is displayed on the [L-Server Template Management] tab. The L-Server template information and the buttons that will be displayed are shown below. Buttons <Create> button Click when creating an L-Server template. For details, refer to "15.1.2 Creating".
Page 167: Creating
L-Server List In each page of the list, 10 items can be displayed. It is possible to specify the page number to display, move forwards and backwards by single pages, and move to the first or last page. Server Name The L-Server name is displayed.
Page 168 Label (Optional) Enter a label for the L-Server template. The character string within 32 characters is specified. Comments (Optional) Enter a comment for the L-Server template. The character string within 256 characters is specified. Server Type Select a server type. Select "Physical"...
Page 169 - PRIMERGY RX900 S1 - PRIMERGY TX150 S7 - PRIMERGY TX150 S6 - PRIMERGY TX200 S6 - PRIMERGY TX200 S5 - PRIMERGY TX300 S6 - PRIMERGY TX300 S5 - PRIMERGY TX300 S4 - PRIMEQUEST 1000 - Other PC servers Set the basic information, and click <Next>. Enter information on the CPU and memory.
Page 170 NIC Num Enter the number of network resources (NumOfNetworkLinks) contained in the NIC redundancy group. Specify a number in the following range: 1 - 4098 One network resource is set to NIC and the NIC redundancy group when omitting it. Click <Add NIC Group>...
Page 171: Creating A Virtual L-Server Template
When not configuring the method, select " ". Select "name_order", when selecting a server from the servers with the same model name in alphabetical order. When selecting a server with the same or higher level of performance values, or a server with the least difference in the performance levels, select "keep_spec".
Page 172 The character string within 32 characters is specified. Comments (Optional) Enter a comment for the L-Server template. The character string within 256 characters is specified. Server Type Select a server type. Select "VM" when creating a virtual L-Server template. VM type Select a VM type.
Page 173 [OVM for x86] Enter a number between 0.3 and 8.0. [Solaris Zones] Enter a number between 1 and 8. CPU Reserve (Optional) Enter the minimum size of CPU resources to be reserved for the L-Server. Enter when using the overcommit function. Enter the value in the range from 0 to the upper_limit_of_the_CPU_performance .
Page 174 Memory Share (Optional) Enter the relative proportion for allocation of memory resources on the L-Server. It is possible to specify it for VMware. Enter when using the overcommit function. Enter an integer between 0 and 1000000. If left blank, the value specified for the memory size * 1024 * 10 is configured when creating an L-Server. Memory buffer (Optional) Specify the memory buffer.
Page 175 Enter the disk information. Disk Enter the disk capacity, in units of GB. Enter a number in the following range: 0.1 to 2048 (GB) [Xen] 0.1 to 999.9 (GB) [Solaris Zones] 0.1 to 9600 (GB) Clicking <Add> adds a disk. Enter the disk number.
Page 176: Modifying
Select "false" when not releasing automatically. Nothing is set by default. In this case, the value set to the definition file is used when an L-Server is created. [Xen] Only "false" can be specified. It can be omitted. ServerImageLink Specify "all" when deploying all disks with the same configuration for images, including data disks. Specification is possible for VMware and Hyper-V.
Page 177: Copying
Select the ROR console orchestration tree, and select [File]-[L-Server Template]-[Edit] from the ROR console menu. The [L-Server Template Management] tab is displayed on the [ROR L-Server Template Editor] window. Select an L-Server template to edit on the [L-Server Template Management] tab, and click <Modify>. The [Modify L-Server Template] dialog is displayed.
Page 178: Export
15.1.6 Export Use the following procedure to export an L-Server template: Select the ROR console orchestration tree, and select [File]-[L-Server Template]-[Edit] from the ROR console menu. The [L-Server Template Management] tab is displayed on the [ROR L-Server Template Editor] window. Select an L-Server template to export on the [L-Server Template Management] tab, and click <Export>.
Page 179: Editing A Template Using An Editor
15.2 Editing a Template Using an Editor This section explains how to edit an L-Server template using an editor. Use the following procedure: Export an L-Server Template For details on how to export L-Server templates, refer to "15.2.1 Export". Edit with an Editor For details on editing a template with an editor, refer to "15.2.2 Editing".
Page 180: Import
Note When creating a virtual L-Server, the values in the VM specific information definition file are used even if those values have not been set in the L-Server template. If there are discrepancies between the L-Server template and VM specific information definition file (e.g. CPU performance is lower than CPU Reserve), L-Server creation will fail.
Page 181: Chapter 16 Creating L-Servers
Chapter 16 Creating L-Servers This chapter explains how to create L-Servers. For an overview of the functions, refer to "2.2.3 L-Server" in the "Design Guide CE". L-Servers can be created using the following two methods: Creation Using an L-Server Template Resources are automatically selected from a resource pool.
Page 182: Creation Using An L-Server Template
[OVM for SPARC] When using OVM for SPARC, virtual L-Servers cannot be created. In this case, link L-Servers with configured virtual machines. For details, refer to "Chapter 18 Linking L-Servers with Configured Physical Servers or Virtual Machines". Information [Physical Servers] For details on physical L-Servers, refer to "B.5 Creating an L-Server"...
Page 183 [KVM] Enter up to 64 characters beginning with an alphanumeric character (upper or lower case), and including alphanumeric characters (upper or lower case), underscores ("_"), or hyphens ("-"). [OVM for x86] Enter the location using 32 characters or less. [Solaris Zones] Enter up to 52 characters beginning with an alphanumeric character (upper or lower case), and including alphanumeric characters (upper or lower case), underscores ("_"), periods ("."), and hyphens ("-").
Page 184 When selecting a storage location, only specify system disks on the [Disk] tab. If different locations are specified for system disks and data disks, L-Server creation with cloning image deployment may fail. Disks are created in the same location even if there is a mixture of disks with Thin Provisioning attributes and disks with no Thin Provisioning attributes in the cloning image.
Page 185 Network (NIC) Select a network resource to connect to the NIC of the L-Server. A list of the NICs defined in the L-Server template is displayed. Select the network to connect to each NIC from the [Network to connect] column. Click <Select>...
Page 186 Point Association of an L-Server Name with a VM Guest Name When installing an operating system manually on the L-Server or using the management console of server virtualization software, select Guest_name displayed in [Resource Details]. the L-Server in the orchestration tree, and operate the VM for the Guest_name : The following name is automatically allocated for L-Server_name - Number...
Page 187: Creation Of Physical L-Servers Using Parameters
16.2 Creation of Physical L-Servers Using Parameters This section explains how to configure a physical L-Server with server, storage, and network specifications configured, without using an L-Server template. Specify the values on the following tabs: [General] Tab [Server] Tab [Disk] Tab [Network] Tab [OS] Tab Use the following procedure to create L-Servers:...
Page 188: General] Tab
If the disk resources are created from the virtual storage (RAID group, for example) that is the subject of ETERNUS Dynamic LUN Mirroring, the LUN created on the remote site receives the same alias. If the alias name of the ETERNUS LUN corresponding to the disk created from the virtual storage has been changed using the ETERNUS WebGUI, the alias name in the disk details will be updated with the regular update.
Page 189: Server] Tab
Note When the admin LAN network settings for a physical server registered in a server pool are different, an admin LAN network resource is automatically registered, if a physical server is selected for use in the [Server] tab. Also, if an admin LAN network resource is specified for the NIC in [Network (NIC)], when [Physical server] is selected on the [Server] tab, only a physical server or server pool with a NIC configuration matching that of the admin LAN network will be displayed.
Page 190 The default is "Automatic". When [Automatic] is Selected Select a physical server automatically from the resource pool with high priority. When selecting [Automatic], operate a resource pool with priorities. When there are multiple resource pools with the same priority, physical servers will be selected satisfying the conditions for a resource pool which has been searched in advance.
Page 191 Note When resources of the same servers are shared due to a change in usage, ensure that [Resource release] is set for the L-Server they are allocated to. When the server resources are allocated to the L-Server for which [Resource release] is not configured, the server resources cannot be shared.
Page 192: Disk] Tab
When not performing batch power operations, check the [Exclude from batch power operations] checkbox. FC settings FC connection pattern If the number of FCs fitted or their location differs from physical server to physical server, specify an FC connection pattern file. This setting can be made when the storage units are the following: For details, refer to "B.1 Creating Definition Files"...
Page 193 Disk type Select a disk type. SAN (Storage Area Network) Select when using SAN storage. iSCSI Select when using iSCSI storage. Disk Clicking <Add> displays the [Disk Definitions] dialog. Specify the following items for each disk: Size * Number of Disks Size Enter a number with up to one decimal place, in units of gigabytes.
Page 194: Network] Tab
When specifying search conditions, the relevant disk resource list is displayed. Select from the displayed disk resources. The specified disk resources are allocated to the L-Server. Search conditions Storage pool Select the storage pool of the storage destination of the disk resource. Search size Enter the lowest value of the disk size to be searched as a number with up to one decimal place, in units of gigabytes.
Page 195 IP address (Optional) Specify the IP address to allocate to the L-Server. This should be entered for direct specification of the IP address to be allocated to the L-Server. The specified IP address will be converted to the IP address of the physical server during creation of the L-Server. Note If a LUN created beforehand is used to create a physical L-Server, specify the IP address of the OS stored in the LUN.
Page 196: Os] Tab
16.2.5 [OS] Tab Enter the parameters to set for the OS when creating the L-Server. This setting is valid only if an image is specified in the [General] tab. When using an L-Server with the server type [Physical], refer to "B.7 [OS] Tab Configuration" in the "Setup Guide CE". 16.3 Creation of Virtual L-Servers Using Parameters This section explains how to configure a virtual L-Server with server, storage, and network specifications configured, without using an L-Server template.
Page 197: General] Tab
When using OVM for SPARC, virtual L-Servers cannot be created. In this case, link L-Servers with configured virtual machines. For details, refer to "Chapter 18 Linking L-Servers with Configured Physical Servers or Virtual Machines". 16.3.1 [General] Tab Name (Label) Enter a name for the L-Server. [VMware] [Hyper-V] Enter up to 64 characters beginning with an alphanumeric character (upper or lower case), and including alphanumeric characters (upper or lower case), underscores ("_"), periods ("."), and hyphens ("-").
Page 198: Server] Tab
Information When a cloning image is specified, the sizes of system disks of virtual L-Servers will be changed into the size of when the cloning image was deployed. When deploying cloning images, the OS image included in a cloning image is used, but the values of CPU, memory and network are overwritten with the values used when creating an L-Server.
Page 199 [KVM] The upper limit of the number of CPUs is 64. [Solaris Zones] The size of resources of hardware where VM hosts operate can be specified. CPU Performance Enter the server CPU speed to allocate to the L-Server. Enter a number with up to one decimal place, in units of gigahertz. A number between 0.1 and 8 can be specified.
Page 200 file. For details on VM specific information definition files, refer to "C.1 Definition Files Commonly Shared when Creating Virtual L-Servers" and "Chapter 8 Creating Definition Files" in the "Setup Guide CE". [KVM] The maximum size of available memory can be specified. [OVM for x86] The size of resources of hardware where VM hosts operate can be specified.
Page 201 [Solaris Zones] When the specifying VM host to use, please choose a VM host suitable for specification of "Server Recovery". If the [HA] checkbox is selected Choose a VM host with spare server settings. Resource release Specify whether add the CPU and memory of the VM guests allocated to the L-Server to the total of the VM pool, when the power of the L-Server is OFF.
Page 202 There are no VM hosts without a spare server configured There is no available CPU or memory The status, power status, and maintenance mode of other VM hosts are not suitable. Information If the HA function is located on an enabled VM host, the HA function of the server virtualization software will be enabled. When a problem occurs on the physical server that the VM host is operating on, the virtual machine can be recovered by restarting it on a VM host that is operating normally.
Page 203: Disk] Tab
16.3.3 [Disk] Tab Disk Click <Add>, and specify the following items for each disk. Size * Number of Disks Size Enter a number with up to one decimal place, in units of gigabytes. Values of 0.1 or larger can be specified. [VMware] [Hyper-V] Specify a number between 0.1 and 2048.
Page 204: Network] Tab
[Hyper-V] When creating an L-Server or changing the configuration, a maximum of four disks can be specified at one time. To perform addition of five or more disks, please perform an additional configuration change. Saved disk resources that are created from virtual storage can only be connected to the L-Server when using Microsoft(R) System Center 2012 Virtual Machine Manager.
Page 205: Os] Tab
DNS server Specify the DNS server. Note [Hyper-V] IP addresses can be automatically configured, on the following guest OSs on which the integrated services are installed. Microsoft(R) Windows Server(R) 2012 Microsoft(R) Windows Server(R) 2008 R2 Microsoft(R) Windows Server(R) 2008 Microsoft(R) Windows Server(R) 2003 R2 Microsoft(R) Windows Server(R) 2003 Microsoft(R) Windows(R) 8 Microsoft(R) Windows(R) 7...
Page 206 Definition File Name The definition file name can be used by dividing into definitions that are available for each user group and definitions that are common to the system. If the key of the definition file common to the system is the same as a definition file for a user group, priority is given to the values indicated in the definition file for the user group.
Page 207: Chapter 17 L-Server Operations
Chapter 17 L-Server Operations This chapter explains how to operate L-Servers. L-Servers can perform the following operations: Table 17.1 Available Operations Physical L- Operation Virtual L-Server Reference Server Starting an L-Server Refer to "17.1.1 Starting an L-Server". For details, refer to "17.1.2 Stopping an L- Stopping an L-Server Server".
Page 208: Power Operations
Physical L- Operation Virtual L-Server Reference Server Refer to "Deletion" of "17.6.2 Backup and System image deletion Restore". Moving L-Servers between VM hosts Yes (*1, *2, *3, Refer to "17.7 Migration between VM Hosts". (migration) Allocating resources to L-Servers Yes (*1, *2) Refer to "17.8.2.1 Allocating Resources".
Page 209: Stopping An L-Server
For details on the statuses when configuration definitions have been created (defined), servers have been released (preserved), and resources have been allocated (allocated), refer to "17.8 Allocating and Releasing Resources to L-Servers". From the command-line, execute rcxadm lserver start. For details on the rcxadm lserver start command, refer to "3.6 rcxadm lserver" in the "Reference Guide (Command/XML) CE". Note From virtual L-Servers to which resources have been allocated (allocated) or from which servers have been released (preserved), a startup command is sent out to VM guests even in the following cases.
Page 210: Restarting An L-Server
[OVM for SPARC] When the function is not supported by Oracle VM Server for SPARC, stopping and rebooting of the L-Server cannot be performed. Based on the virtual machine status, either directly operate the virtual machine, or perform a forced stop or forced reboot. 17.1.3 Restarting an L-Server This section explains how to restart an L-Server.
Page 211 Right-click the target resource folder or tenant in the orchestration tree, and select [Power]-[ON] from the popup menu. The [Power On L-Servers] dialog is displayed. Point A list of L-Servers that are targets of the power operation is displayed. The display order is in descending order of priority. Even if the list of L-Server is not displayed, the power supply can be operated.
Page 212: Modifying
Click <OK>. L-Servers in a resource folder are restarted in the order of priority. From the command-line, execute rcxadm folder restart. For details on the rcxadm folder restart command, refer to "3.5 rcxadm folder" in the "Reference Guide (Command/XML) CE". 17.2 Modifying This section explains how to perform L-Server configuration changes.
Page 213 Changing L-Server Specifications For the configuration to use the same name for both a virtual L-Server and a VM machine, refer to "Table 17.4 List of Items Specified in the Definition File" of "17.8.1 Installation". *2: [Solaris Zones] CPU performance and the number of CPUs should be changed when the cap values of CPUs are changed, and when resource pools used in non-global zone are changed as follows.
Page 214: Modifying Specifications
17.2.1 Modifying Specifications This section explains how to modify L-Server specifications. Use the following procedure to modify L-Server specifications: [Solaris Zones] Calculate the cap value to configure for the non-global zone from the number of CPUs and the CPU performance. For details, refer to "C.7.6 Creating an L-Server"...
Page 215 Changing Virtual L-Server Specifications The following items can be changed when the power status of the virtual L-Server is ON. For details, refer to the manuals of VM products. CPU Performance Number of CPUs Memory Size OS Type (When no images are not deployed) [OVM for x86] The OS type cannot be changed, regardless of whether images are deployed or not.
Page 216: Modifying The Basic Information
Check whether the memory/CPU hot plug has been enabled from the VM management software if an existing VM guest is to be linked to a virtual L-Server. If it is not enabled, enable the setting from the VM management software. Refer to the manual for the VM management software network device for information on how to enable the memory/CPU hot plug with the VM management software.
Page 217: Attaching And Detaching Disks
The differences in VM guest configuration are reflected on the configuration of the L-Server by periodic queries made to the VM management software. For details on reflection of L-Server configuration by periodic queries, refer to "17.2 Modifying". Changing an L-Server name changes the VM guest name on server virtualization software as well. For associating an L-Server name with a VM guest name, refer to "Association of an L-Server Name with a VM Guest Name"...
Page 218 Automatic assignment Select the appropriate resources, and allocate storage pools and virtual storage resources or disk resources to the L-Server. Set "Automatic" for the default value. Note When there are storage pools with and without Thin Provisioning attributes configured that have the same priority, the storage pool that will be given priority is decided based on definition files.
Page 219 Specify when searching for disks whose names begin with the specified string. - Includes Specify when searching for disks whose names include the specified string. Click <OK>. Make the disk available following the disk attachment procedure provided by the OS. From the command-line, execute rcxadm lserver attach.
Page 220 When Using NetApp Storage Using storage management software, the data disk can be accessed from managed servers by defining LUNs of iSCSI boot disk and of the data disk in the same igroup. Detaching a Disk Use the following procedure to detach a disk allocated to an L-Server: Right-click the target L-Server in the orchestration tree, and select [Change Settings]-[Detach Disk] from the popup menu.
Page 221 When the snapshots are collected from a virtual L-Server on Hyper-V, detached disk resources cannot be saved. From the command-line, execute rcxadm lserver detach. To detach a disk from an L-Server while the power of the L-Server is on, specify the -online option command. For details on the rcxadm lserver detach command, refer to "3.6 rcxadm lserver"...
Page 222: Sharing Disks Between L-Servers
SCSI:3:0 - SCSI:3:14 AM When changed to use a path through disk or difference disk Note that changing the device path for the system disk enables deletion of disks for all disks. Once a virtual L-Server is created, do not change the device path of the system disk using VM management software as doing so results in the following behavior.
Page 223: Modifying Network Resource Settings
When specifying these items as search conditions, connected shared disks can be filtered. For details, refer to "16.2.3 [Disk] Tab". Attaching Shared Disks Use the following procedure to attach disk resources to L-Servers created in advance and to share the disks: Attaching shared disks to the first L-Server To attach disks, use the procedure of "Attach new disks"...
Page 224 L-Server Status Physical L- Server Physical L-Server Virtual L-Server Operation (iSCSI Boot) Define Define Preserved Allocated Preserved Allocated (Example: Changing the combination of NIC1 and 2 to NIC1 only) *1: Changing IP addresses across subnets is not possible. *2: IP addresses and network resources of virtual L-Servers can only be changed when the server's status is "defined". *3: Select "Admin LAN (MAC address 1)"...
Page 225: Increasing Disk Capacity
Note When resources have not been allocated (preserved) or have been allocated (allocated) to the L-Server, only the network resources of physical L-Servers can be modified. For Physical L-Servers Right-click the target L-Server in the orchestration tree, and select [Change Settings]-[Network Configuration] from the popup menu.
Page 226: Using The L-Server Console
When linking a configured virtual machine to a virtual L-Server, disk capacity can be increased for L-Servers that can operate servers and disks. The disks of which the disk capacity can be increased are system disks and data disks. Only disks created using virtual storage are the targets of increase, and Raw Device Mapping (RDM), Pass-through Disks, and difference disks are not supported.
Page 227 [Windows] Remote desktop connection [Linux] SSH connection Prerequisites for Console Connections When using a console connection, the prerequisites differ depending on the server type of the L-Server used. For Physical L-Servers When the hardware is PRIMERGY, and the iRMC video console redirection function can be used, connection to the console is possible. Note For console connection, use functions of ServerView Operations Manager.
Page 228: Deleting An L-Server
[Hyper-V] Admin clients must be in the same domain as SCVMM or VM hosts. It is necessary to install the VMM management console for SCVMM that is of the same version as the SCVMM registered as VM management software. Console This chapter explains the L-Server console connection.
Page 229: Cloning Image Operations
Note When deleting an L-Server, log off from the ETERNUSmgr of ETERNUS storage registered on ESC. When operating NetApp storage in cluster environments and operating a partial system due to system trouble, recover the NetApp storage and return the system to cluster operation before re-commencing operations. When the disk resource is a LUN created in advance, a LUN for iSCSI boot, or a disk resource for virtual L-Servers, it is recommended to delete the data on the disk, as the data is not deleted when deleting the L-Server to which the disk resource is allocated.
Page 230 Cloning Image Name Enter a name to identify the collected cloning image. For a cloning image name, enter a character string, beginning with an alphabetic character (upper or lower case), and containing up to 32 alphanumeric characters (upper or lower case) and underscores ("_"). When there is already a cloning image of the same image type with the same name in the image pool a cloning image is being registered to, it will be registered as the next version of that cloning image.
Page 231 Note For virtual L-Servers, the results of cloning image collection vary based on the disk configurations as follows. [VMware] When the target L-Server includes Raw Device Mapping (RDM) disks, the target disks are treated as virtual disks and the image will be collected.
Page 232: Viewing
[KVM] For details on how to collect cloning images on RHEL-KVM, refer to step 3 in "C.6.6 Creating an L-Server" in the "Setup Guide CE". [OVM for x86] For details on how to collect cloning images on OVM for x86, refer to "C.5.7 Collecting Cloning Images" in the "Setup Guide CE". Point [VMware] When "Default"...
Page 233: Deleting
Right-click the target image pool in the orchestration tree, and select [Unregister] from the popup menu. The [Unregister a Resource] dialog is displayed. Click <OK>. The cloning image is unregistered. From the command-line, execute rcxadm pool unregister. For details on the rcxadm pool unregister command, refer to "3.10 rcxadm pool" in the "Reference Guide (Command/XML) CE". Note a_numeric_value is added at the end of the image name to change its name as follows: When unregistering a cloning image,...
Page 234: Snapshots, And Backup And Restoration Of L-Servers
17.6 Snapshots, and Backup and Restoration of L-Servers This section explains how to perform snapshots, and backup and restore of an L-Server. 17.6.1 Snapshot This section provides an overview of snapshots for L-Servers. Snapshot is the function that saves the state and configuration of an L-Server disk at the time the snapshot is taken. When using virtual L- Servers, the snapshot function of server virtualization software is used.
Page 235 deleted. Use the rcxadm imagemgr command to change the maximum number of snapshot versions. For details on the rcxadm imagemgr command, refer to "5.9 rcxadm imagemgr" in the "Reference Guide (Command/XML) CE". To collect a snapshot, it is recommended that the power of the L-Server is "OFF" to avoid any inconsistencies occurring in the data and file system on the disk.
Page 236: Backup And Restore
From the command-line, execute rcxadm image snapshot. For details on the rcxadm image snapshot command, refer to "4.1 rcxadm image" in the "Reference Guide (Command/XML) CE". Restore This section explains how to restore a snapshot. To restore a snapshot, the L-Server must be stopped. Right-click the target L-Server in the orchestration tree, and select [Snapshot]-[Restore] from the popup menu.
Page 237 Note Not supported when using clustering software on physical L-Servers. To back up and restore L-Server system images, the following conditions must be met: For Backup The status of the L-Server is that in which resources have already been allocated (allocated) The L-Server has been started An agent on the L-Server has already been registered For Restoration...
Page 238: Migration Between Vm Hosts
Click <OK>. The backup of the system image is deleted. From the command-line, execute rcxadm image delete. For details on the rcxadm image delete command, refer to "4.1 rcxadm image" in the "Reference Guide (Command/XML) CE". 17.7 Migration between VM Hosts This section explains how to move (migrate) an L-Server between servers.
Page 239: Forced Migration Between Vm Hosts
In the [Modify an L-Server] dialog, change the value for "VM host" to "Pool", check the resources to be allocated, and then perform server migration again when necessary. In the [Modify an L-Server] dialog, change the value for "VM host" to "VM host", check the resources to be allocated, and then perform server migration again when necessary.
Page 240: Allocating And Releasing Resources To L-Servers
Note Do not start the VM guest before deleting it. When the migrated VM guest is also operating on the migration target VM host, the L-Server disk data may be damaged as the VM guest will be mounted twice. Release maintenance mode. Use the virsh command to delete the VM guest definitions.
Page 241: Installation
Note For an L-Server from which VM guests have been deleted using server virtualization software, "unknown" is displayed for the resource allocation status. For details, refer to "Message number 67154" or "Message number 67178" in "Messages". Figure 17.1 State Transition of L-Servers L-Servers can be deleted when their status is something other than "undefined"...
Page 242 [Linux Manager] /etc/opt/FJSVrcvmr/customize_data Definition File Name l_server.rcxprop Definition File Format For the definition file, write each line in the following format: Key = Value Definition File Items Specify the following items. Table 17.4 List of Items Specified in the Definition File Item Value Remarks...
Page 243: Operations
Item Value Remarks The names of L-Servers created with "false" set for this item will automatically change when VM names are changed. However, the VM name must conform to the naming conventions for L-Servers. 17.8.2 Operations This section explains how to allocate resources to, and release resources from, L-Servers and how to modify configuration definition information.
Page 244: Changing Physical Server Usage
Note When modifying the configuration definition for an already defined L-Server that has been updated from an earlier version, alive monitoring is disabled. When enabling alive monitoring, modify the configuration of the L-Server again. 17.9 Changing Physical Server Usage This section explains how to change physical server usage. Changing server usage is the function for preparing more L-Servers than physical servers and is used by switching the startup L-Server.
Page 245: When Resources Are Already Allocated (Allocated)
Check the [Automatic (when powered off)] checkbox of [Resource release] on the [Server] tab. Operation The operation method is shown below. When using multiple L-Servers, switching between them, on a single physical server Usage can be changed by repeating the following procedure. Check the Physical Server and L-Server of the Source L-Server for Usage Change Stop the Source L-Server for Usage Change Stop L-Servers operating on physical servers which are required for change usage.
Page 246 Create and Register Each Resource Perform resource creation and registration, referring to "Chapter 5 Registering Resources" and "Chapter 14 Registering Resources in Resource Pools". Release the resources of the source L-Server for usage change Resources are released while the resource details of the source L-Server for usage change are preserved. For details, refer to "17.8.2.2 Releasing Resources".
Page 247: Operation
Start the Destination L-Server for Usage Change For details, refer to "17.1.1 Starting an L-Server". After changing the configuration, the L-Server before changing cannot be operated, until the new L-Server has finished starting. When using multiple L-Servers, switching between them, on unused physical servers in a server pool Usage can be changed by repeating the following procedure.
Page 248 Change L-Server Configuration for Fixed Operation Clear the [Automatic (when powered off)] checkbox of [Resource release] in the [Modify an L-Server] dialog, and click <OK>. For details, refer to "17.2.1 Modifying Specifications". Delete Unnecessary L-Servers When unnecessary L-Servers exist, use the procedure in "17.4 Deleting an L-Server"...
Page 249: Chapter 18 Linking L-Servers With Configured Physical Servers Or Virtual Machines
Chapter 18 Linking L-Servers with Configured Physical Servers or Virtual Machines This chapter explains how to link a configured physical server to a physical L-Server and how to link a configured virtual machine to a virtual L-Server. Information It is possible to import L-Servers into the L-Platform management function. For details, refer to "7.2.3 Import to L-Platforms"...
Page 250: Available Range
For Physical L-Servers MAC address, IP address (only for admin LAN) For Virtual L-Servers MAC address (Media Access Control address) When admin server has been configured on a virtual machine, do not link that virtual machine to an L-Server. 18.2 Available Range The functional range available when a configured physical server or virtual machine is linked to an L-Server is as follows: Note The range of available functions differs according to the role of the user and user group who operate it.
Page 251 Type of L-Server L-Server Function Physical Server Using HBA Physical Server Using VIOM Other Physical Servers address rename iSCSI boot Allocating and releasing resources Blade chassis high availability Storage chassis high availability Disaster Recovery Deletion Releasing an L-Server *1: The following items can be modified. Server redundancy, spare server selection methods, and spare server pools Startup priority *2: Configured physical servers for which server switchover has been already set cannot be managed.
Page 252 When disk configurations cannot be supported by an L-Server When only Raw Device Mapping (RDM), a pass-through disk(Pass-through Disk), and a difference disk are included When a configuration including device paths which are not described, Raw Device Mapping(RDM), a path through disk (Pass-through Disk), or difference disks are included When the non-global zone of Solaris containers is not managed using BMC BladeLogic Server Automation [Solaris Zones] In the case of the non-global zone of Solaris 11 [Solaris Zones]...
Page 253: Prerequisites
18.3 Prerequisites When linking a configured physical server to a physical L-Server, or when linking a configured virtual machine to a virtual L-Server, the available management scope varies depending on the configured hardware and software environments. 18.3.1 Manageable Hardware When using the hardware listed in "Table 2.69 Required Hardware" in "2.5 Hardware Environment" in the "Design Guide CE", only servers can be managed.
Page 254 Virtual machines are managed using VMware and vCenter Server Datastores are used, and the datastores are displayed in the storage tree as virtual storage SAN storage or NAS storage supported by VMware, excluding built-in disks on the server and iSCSI storage, is used The following device paths are used for data disks SCSI:0:1 - SCSI:0:6 SCSI:0:8 - SCSI:0:14...
Page 255: When Using Server Virtualization Software
18.3.4 When Using Server Virtualization Software Virtual machines of server virtualization software supported by Resource Orchestrator can be managed as virtual L-Servers in the following cases: When the virtual machine is managed by VM management software When a Solaris zone is used When OVM for SPARC is used.
Page 256 Register Resources in Resource Pools Register physical server resources in a server pool. In the [Register Resources] dialog for the server pool, check the [Display servers with OS installed] checkbox and specify a physical server with an OS installed. Register the disks that are connected to the physical server to be linked with the L-Server in a storage pool. Register address set resources.
Page 257: For Physical Servers
Confirmation from the GUI Select the L-Server in the orchestration tree, display the [Resource Details] tab, and check the information is displayed in [Controlled resources] on the [Status] table. In [Controlled resources], the following text strings are displayed. When [Server] is displayed A physical L-Server A server can be operated by a virtual L-Server When [Server,Storage] is displayed...
Page 258: For Virtual Machines
Click <OK>. The physical server becomes manageable as a physical L-Server. From the command-line, execute rcxadm lserver convert. For details on the rcxadm lserver convert command, refer to "3.6 rcxadm lserver" in the "Reference Guide (Command/XML) CE". 18.4.3 For Virtual Machines Use the following procedure to use a virtual machine as a virtual L-Server: In the ROR console orchestration tree, right-click a VM host in the registered VM pool, and select [Convert to L-Server] from the popup menu.
Page 259: Changing Configuration
[Hyper-V] When a virtual machine with a network adapter that has never been started before is linked with an L-Server, the MAC address the L- Server uses on the network might be set to "00:00:00:00:00:00". In that case, cancel the link between the virtual machine and L-Server and assign a static MAC address to that virtual machine using VM management software, or start the virtual machine, wait for 3 minutes, and then create the link with the L-Server.
Page 260: Chapter 19 Resource Operations
Chapter 19 Resource Operations This chapter explains how to perform resource operations with resource pools. 19.1 Registration Use the following procedure to register a resource to a resource pool: Right-click the target resource pool in the orchestration tree, and select [Register Resources] from the popup menu. The [Register Resources] dialog is displayed.
Page 261 Moving Individual Resources Use the following procedure to move a resource to another resource pool. Right-click the target resource in the orchestration tree, and select [Move a Resource] from the popup menu. The [Move a Resource] dialog is displayed. For "Destination Pool", select the destination resource pool. Click <OK>.
Page 262: Unregistration
Note Storage resources with Thin Provisioning attributes cannot be moved to storage pools for which Thin Provisioning attributes are not configured. Storage resources with Thick Provisioning attributes cannot be moved to storage pools for which Thin Provisioning attributes are configured. When using datastores of VMware, they can be moved to both storage pools for which Thin Provisioning attributes are configured and storage pools for which Thin Provisioning attributes are not configured.
Page 263 When registering resources, directories and files that are necessary for performance monitoring are created on the server where the resources are registered. This directory is not automatically deleted when resources are deleted. Delete it manually. Refer to "C.6.9 Advisory Notes for RHEL-KVM Usage" in the "Setup Guide CE" for details. - 247 -...
Page 264: Chapter 20 Resource Pool Operations
Chapter 20 Resource Pool Operations This chapter explains how to add new resource pools, and delete or modify existing resource pools. For an overview of the functions, refer to "2.2.2 Resource Pool" in the "Design Guide CE". 20.1 Overview This function manages all the resources allocated when creating an L-Server. A resource pool is a type of resource folder that exists in the orchestration tree, and has the following features that differ from regular folders: Pools are selected as resources when creating or adding L-Servers.
Page 265: Modifying Settings
Storage Pool Network Pool Address Pool Image Pool Priority Select the priority of the resource pool for automatically selecting a resource when creating an L-Server. Select a value between [1] and [10]. Smaller values indicate a higher priority. [5] is selected by default. Attributes Enter attributes for the resource pool.
Page 266: Moving
Note Once a storage pool is created, its thin provisioning attributes cannot be changed. For a workaround, create a new storage pool with the desired Thin Provisioning attributes settings, and then move the resources of the current pool to the new one. When resource pool is used in L-Platform, do not rename servers included in the deployed L-Platform, and VM pool, server pool, and storage pool used in the L-Platform template.
Page 267: Viewing
Note When resource pool is used in L-Platform, do not delete servers included in the deployed L-Platform, and VM pool, server pool, and storage pool used in the L-Platform template. 20.6 Viewing The pool list in the resource list display the resource folders, total size of resources, and free space available. In the L-Server list, when the server is a physical L-Server, the physical server for the L-Server is displayed.
Page 268 The combined total of the capacity of the virtual storage and disk resources registered in the resource pool is displayed for the total capacity of the storage pool. If a disk resource that has been separated from a virtual storage and that virtual storage exist in the same resource pool, the capacity of the disk resource will not be included in the calculation of the total storage capacity of the storage pool.
Page 269 When the HA function provided by server virtualization software is available for the VM hosts, and CPU capacity and memory capacity are reserved for failover In the case of VM hosts that meet the following conditions, the total capacity and the free capacity of the CPU and memory resources are set to 0.
Page 270 Free storage space Total_resource_capacity - (Total_of_resources_used_for_L-Server (*6) + Total_of_images (*7)) Free disk space Free space as a resource is not displayed. The free space is calculated as the free space of a resource pool when the following conditions are met: Disks are not used for L-Servers or cloning images Number of creatable L-Servers is displayed as follows: When the number of disks specified for an L-Server template is 1, and when the disk capacity specified for an L-Server...
Page 271 values of CPU/memory has been set to "Unlimited" using VM management software, the calculation is performed assuming the following values as the maximum values: When no limit has been set for CPU performance The physical CPU performance on the VM host is used When no limit has been set for memory size The memory size set for the virtual machine [Hyper-V]...
Page 272 *3: This does not include the overhead used for the VM host. *4: This includes not only the resources for active virtual machines, but also those of resources of stopped virtual machines. [VMware] This includes the overhead memory used for the virtual machine. The resources of VMware FT secondary virtual machines are included.
Page 273 Point For details on how to select the deployment location of a virtual L-Server, refer to "Selection location of an L-Server" of "2.2.3 L-Server" in the "Design Guide CE". - 257 -...
Page 274: Chapter 21 Resource Folder Operations
Chapter 21 Resource Folder Operations This appendix explains resource folders, which are used when managing a large number of resources or when you want to divide resources according to certain conditions. Resource Folders Resource folders are used when managing a large number of resources or when you want to divide resources according to certain conditions. Resources stored in resource folders can be freely placed.
Page 275: Overview
Figure 21.1 Sharing and Dividing Resources Using Tenants 21.1 Overview Resource folders are used when managing a large number of resources or when you want to divide resources according to certain conditions. Resource folders can be created in the orchestration tree or the server resource tree. Resource folders created in the orchestration tree can store the following resources: L-Server Resource Pools...
Page 276: Creating
Using hierarchical folders, other resource folders can be stored in the resource folders. Using resource folders enable you to do the following: Since the number of resources handled at once is reduced, it becomes easier to select resources Resources can be categorized in detail Also, in the orchestration tree, the access scope of roles can be restricted and used in combinations to restrict the resource folders that can be accessed for each administrator.
Page 277: Viewing
21.3 Viewing This section explains how resource folders are displayed. Resource folders are displayed in the following format: Resource_folder_name ( label ) When label is not set, only resource_folder_name is displayed. If you select the [Resource List] tab with a target resource folder selected in the tree, a list of information for the resources that belong to the resource folder are displayed.
Page 278: Moving
Click <OK>. The target resource folder is deleted. From the command-line, execute rcxadm folder delete. For details on the rcxadm folder delete command, refer to "3.5 rcxadm folder" in the "Reference Guide (Command/XML) CE". For Server (server) Right-click the target resource folder in the server tree, and select [Delete] from the popup menu. The [Delete a Folder] dialog is displayed.
Page 279: Chapter 22 Network Device Operations
Chapter 22 Network Device Operations This chapter explains how to operate network devices. 22.1 Switchover of Maintenance Mode This section explains operations temporarily excluding the network devices from the target of monitoring or auto-configuration in order to perform operations such as regular maintenance of network devices configuring network devices, or configuring a network device as the target of monitoring or auto-configurations after regular maintenance completion.
Page 280: Switchover Of The Target Of Auto-Configuration
Indicates that maintenance mode is released. For details on the rcxadm netdevice command, refer to "3.8 rcxadm netdevice" in the "Reference Guide (Command/XML) CE". Note When configuring maintenance mode for a network device, auto-configuration is not executed on the network device. Therefore, when a network device configured for maintenance mode is in a redundancy configuration, it may be unable to keep the redundancy configuration depending on the configuration details.
Page 281 # /opt/FJSVrcvmr/bin/rcxadm netdevice set -name nd01 -attr auto_conf=true <RETURN> When an infrastructure administrator is excluding the network device from auto-configuration # /opt/FJSVrcvmr/bin/rcxadm netdevice set -name nd01 -attr auto_conf=false <RETURN> You can confirm either of the following operations if the network device is the target of auto-configuration. From the GUI: Select the target network device in the network device tree.
Page 282: Chapter 23 Network Resource Operations
Chapter 23 Network Resource Operations This chapter explains how to operate network resources. 23.1 Automatic Network Configuration Automatic network configuration is normally performed when creating an L-Server for the first time, but it can also be performed beforehand. By performing it beforehand, the creation of an initial L-Server can be made faster. Automatic network configuration is performed as follows: Select the target network resource on the orchestration tree, and then select [Automatic Network Configuration] from [Operation] of the ROR console menu.
Page 283: 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 4 Login to the ROR Console" in the "Setup Guide CE". For details on BladeViewer, refer to "Chapter 4 BladeViewer".
Page 284 Users with restricted access If a warning or error event occurs on a managed server, the status monitoring area starts to blink. If you click the blinking area, the server's information is displayed on the main panel. For details on different statuses, refer to "A.3 Status Panel".
Page 285 Server VM Host VM Guest LAN Switch NICs LAN Switch Port Storage In the Storage Tree, resources managed by Resource Orchestrator are displayed in a tree view. The following resource types are displayed: Storage Management Software Storage Units RAID Groups LUNs Virtual Disks of VM Guests Orchestration Tree...
Page 286: Menus
[Resource Details] Tab Displays more detailed information on the resource selected in the tree, or a resource that was double-clicked in the [Resource List] tab. [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.
Page 287: List Of Menus
A.2.1 List of Menus The menus provided on the menu bar of the ROR console are listed in the table below. Options available vary according to the authority level of the user account. Table A.1 Menu Items Menu Items Function Menu Submenu Imports the system configuration file for pre-...
Page 288 Menu Items Function Menu Submenu Creates a resource folder in the server resource tree or Folder orchestration tree. Tenant (*1) Creates a tenant in the orchestration tree. Pool Creates a resource pool in the orchestration tree. Create L-Server Create an L-Server. Network Resource (New) Creates a new network resource.
Page 289 Menu Items Function Menu Submenu Reboots a server after shutting down its operating Reboot system. Reboots a server without shutting down its operating Reboot (Forced) system. Turns the maintenance LED on. LED (*4) Turns the maintenance LED off. Switchover Switches over a server with one of its spare servers. Failback Switches back a server to its pre-switchover state.
Page 290: Popup Menus
*3: Cannot be selected for PRIMEQUEST and SPARC Enterprise Partition Models. *4: Available only for PRIMERGY BX servers. *5: Cannot be set for PRIMERGY BX900/BX400 LAN switch blades operating in IBP mode. *6: Cannot be selected for PRIMEQUEST. *7: Available only for SPARC Servers/SPARC Enterprise. *8: Not available for PRIMERGY BX900/BX400 LAN switch blades operating in IBP mode.
Page 291 Popup Menu Function Menu Submenu Registration Settings Modifies a server's registration settings. HBA address rename settings (*2) Modifies the HBA address rename settings of a server. Modify Network Settings (*3, *4) Modifies the network settings of a server. Spare Server Settings (*2) Modifies a server's recovery settings.
Page 292 Popup Menu Function Menu Submenu Network Settings (*4, *5, *6) Modifies the network settings of a server. Spare Server Settings (*3, *4) Modifies a server's recovery settings. Monitoring Settings Modifies the monitoring information for a server. Modifies the registered login account used to VM Host Login Account (*7) communicate with the VM host.
Page 293 After installing the VM management console, select this menu item and follow the instructions shown in the displayed dialog. *11: Available only for VM guests. Table A.6 Popup Menus Available for Physical OSs [Solaris] Popup Menu Function Menu Submenu Delete Deletes a SPARC Servers/SPARC Enterprise.
Page 294 Table A.8 Popup Menus Available for System Images Popup Menu Function Menu Submenu Restore Restores a system image to a server. Delete Deletes a system image. Table A.9 Popup Menus Available for Cloning Images Popup Menu Function Menu Submenu Deploy Deploys a cloning image to a server.
Page 295 Table A.13 Popup Menus Available for Management Software Popup Menu Function Menu Submenu Management Software (vCenter Registers VM management software (VMware vCenter Server) Server). Registers VM management software (System Center Management Software (SCVMM) Virtual Machine Manager). Register Management Software (OVM Registers management software (OVM Manager).
Page 296 Table A.17 Popup Menus Available for Resource Pools (VM Hosts, Servers, Storage, and Images) Popup Menu Function Menu Submenu Register Resources Registers a resource to the selected resource pool. Unregister Resources Unregisters resources from the selected resource pool. Move Resources Moves registered resources in the selected resource pool to another resource pool.
Page 297 Popup Menu Function Menu Submenu Powers off all L-Servers in a resource folder. Reboot Reboots all L-Servers in a resource folder. Table A.21 Popup Menus Available for Folders Popup Menu Function Menu Submenu Folder Creates a resource folder. Tenant Create tenants. Create Pool Creates a resource pool.
Page 298 Popup Menu Function Menu Submenu Reboot (Forced) Reboots an L-Server forcibly. Migrate Moves an L-Server between servers. Collect Collects a snapshot of the specified L-Server. Snapshot Restore Restores a snapshot to the L-Server. Delete Deletes a snapshot. Backup Backs up a system image from an L-Server. Backup/Restore Restore Restore a system image.
Page 299 Popup Menu Function Menu Submenu Move Resources Moves a resource to another resource pool. Places a server into maintenance mode. Maintenance Mode Release Sets a server to active mode. External Management Opens a server management screen. Software Creates a link between an L-Server and a configured Convert to L-Server physical machine.
Page 300: Status Panel
Popup Menu Function Menu Submenu Automatic Network Automatically configures the network before creating an Configuration L-Server. Move Resources Moves a resource to another resource pool. Table A.31 Popup Menus Available for Network Devices Popup Menu Function Menu Submenu Unregister Unregisters the selected resource from a resource pool. Update Updates a resource.
Page 301: Tree Panel
Figure A.3 Status Panel Status Monitoring Area The Event Log monitors a history of events that have occurred on managed resources. Based on detected events, the status monitoring area will change color and blink. Clicking the status monitoring area will stop the blinking.
Page 302 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 303 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 304 Storage Units RAID Groups LUNs Virtual Disks of VM Guests Orchestration Tree Manages and operates L-Servers and resource pools. All resources authorized for access by the logged in user are displayed. The resources displayed differ depending on the role and access rights of the user.
Page 305: Resource List] Tab
Note To enable the above mentioned setting, restart the manager after editing the definition file. The orders of some lists, such as for blade servers in the server tree, cannot be changed. A.5 [Resource List] Tab The [Resource List] tab in the Main Panel displays a list of resources related to the resource that was selected in the resource tree. For details on the icons used to indicate different resources, refer to "11.2 Resource Status"...
Page 306: Resource Details] Tab
VM Management Software Information on storage resources that are operating using the selected VM management software is displayed. Storage Units Information on virtual storage and disk resources that are operating on the selected storage unit is displayed. Virtual Storage Information on the disk resources of the selected virtual storage is displayed. L-Server Information on the selected L-Server is displayed.
Page 307 Chassis Server Physical OS VM Host VM Guest Network Device PDU or UPS Management Software (vCenter Server, OVM Manager, SCVMM, or VIOM) Storage Management Software Storage Units Virtual Storage VM Management Software Folder Tenant L-Platform L-Server VM Pool Server Pool Storage Pool Network Pool Address Pool...
Page 308: Chassis Attributes
Image Meaning Detected storage blade. Currently displayed server blade. Server blade selected within the chassis image. Server blade that has not been registered yet. Empty slot. Attributes of Displayed Resources The [Resource Details] tab displays different attributes for each resource, as described below. A.6.1 Chassis Attributes General Area Chassis name...
Page 309: Server Attributes
Launch XSCF Web UI The link to the remote management controller (XSCF) Web UI is displayed. Only displayed for SPARC Enterprise M4000/M5000/M8000/M9000 or SPARC M10-4S. Partition Configuration The following information is displayed only when the chassis of a PRIMEQUEST, SPARC Enterprise M4000/M5000/M8000/M9000, or SPARC M10-4S is selected.
Page 310 Status Server status is displayed. Slot A slot number representing the mounted location is displayed. Displayed only for PRIMERGY BX servers. Partition ID The partition number is displayed. Only displayed when a PRIMEQUEST, or a SPARC Enterprise M4000/M5000/M8000/M9000 server, or a server in a SPARC M10-4S is selected.
Page 311 Admin LAN (MAC address 2) The MAC address of the network interface used for the HBA address rename setup service or for admin LAN redundancy is displayed. Not displayed when SPARC Servers/SPARC Enterprise are selected. Displayed only for servers other than PRIMERGY BX servers. Admin LAN Redundancy Displayed when NIC redundancy has been configured for admin LANs.
Page 312 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 313: 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 or VM host is displayed. Admin LAN (IP Address) The IP address on the admin LAN is displayed. Not displayed for VM guests. Status The status of the physical OS, VM host, or VM guest is displayed.
Page 314 VM guests A list of hosted VM guests is displayed. VM Home Positions (VM Guests) A list of the VM guests with the selected VM host set as their VM Home Position is displayed. VM Guest Information Area The following information is displayed only for VM guests. VM type The type of the VM is displayed.
Page 315 Active server Displays the name of the physical server that is currently running. 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.
Page 316 Port Groups Area (IBP) NIC Index The mounted position (index) of each network interface on the server is displayed. Group The names of the port groups set on the LAN switch ports connected to each network interface (for LAN switch blades operating in IBP mode) are displayed.
Page 317: 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 318 When VCS is not configured, a hyphen ("-") is displayed. Maintenance mode The status of maintenance mode is displayed. One of the following is displayed: active maintenance Type The type of a network device is displayed. One of the following is displayed: L2-Switch Firewall For network devices with multiple types, all types are displayed separated by commas (",").
Page 319 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 320 PY CB Eth Switch/IBP 1Gb 36/12 PY CB Eth Switch/IBP 1Gb 18/6 Network links For LAN switch blades, connection information of network devices is not displayed. 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 321: Power Monitoring Devices (Pdu Or Ups) Attributes
failed unchecked Monitoring Settings Area SNMP community name Displays the community name used for SNMP communications with the network device. Monitoring method The type of monitoring used on the network device is displayed. One of the following is displayed: None ping SNMP (Simple Network Management Protocol) ping+SNMP...
Page 322: Management Software Attributes
Hardware version The hardware version of the PDU is displayed. This is not displayed for UPSs. 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.
Page 323: Storage Unit Attributes
Label The label set for the resource is displayed. Comments Comments set for the resource are displayed. Configuration Information Management Software Type The management software type of the storage management software is displayed. Version The version of the storage management software is displayed. IP Address The IP address used to access the storage management software is displayed.
Page 324: Vm Management Software Attributes
Serial Number Information used to identify the chassis of the storage unit is displayed. IP address The IP address used to access the storage management software is displayed. Virtual Storage List Status The status of the registered virtual storage is displayed. Capacity (Unused Capacity/Total Capacity) The capacity of the registered virtual storage is displayed.
Page 325: Virtual Storage Attributes
User ID The user name of the storage management software is displayed. Management software A link to the web interface of the management software is displayed. Virtual Storage List Status The status of the registered virtual storage is displayed. Capacity (Unused Capacity/Total Capacity) The capacity of the registered virtual storage is displayed.
Page 326: Folder Attributes
When thin provisioning is configured "yes" is displayed. When thick provisioning is configured or no attribute is specified "no" is displayed. Total Capacity The total storage capacity is displayed. Unused Capacity The free storage capacity is displayed. A.6.11 Folder Attributes General Area Name (Label) The name of the resource is displayed.
Page 327 L-Server List Name (Label) The name of the L-Server directly under the root/folder/tenant is displayed. Status L-Server status is displayed. Server type The server type of the L-Server is displayed. For Physical L-Servers "Physical" is displayed. For Virtual L-Servers The VM type of the L-Server is displayed. The icon that represents the L-Server's OS is displayed.
Page 328: L-Server Attributes
Number of CPUs (Allocated) The number of CPUs of the physical server actually allocated to the L-Server is displayed. Memory (Defined) The memory capacity defined during L-Server creation is displayed. Memory Capacity (Allocated) The memory capacity of the physical server actually allocated to the L-Server is displayed. Number of NICs The number of NICs on the L-Server is displayed.
Page 329 When a cap value is set, the CPU performance is calculated using the following formulas: cap values of CPUs / 100 (rounding up the number of decimal places) Number of CPUs = cap values of CPUs /( Number of CPUs * 100)) * physical CPU performance (GHz) CPU performance = ( When the cap values calculated using the CPU performance and the number of CPUs for L-Servers are the same as those configured for the non-global zone, the CPU performance and the number of CPUs for L-Servers are not updated, and the...
Page 330 Defined Value The model name of the physical server actually allocated to the L-Server is displayed. Allocated Value The model name defined during L-Server creation is displayed. Type The server type of the L-Server is displayed. Disk type The type of disks on the physical L-Server is displayed. One of the following is displayed: iSCSI SAN (Storage Area Network)
Page 331 Spare server specs The method to select a spare server of the L-Server is displayed. Spare server pool The spare server pool for the L-Server is displayed. Alive monitoring The alive monitoring configuration status is displayed. When Alive Monitoring is Configured "on"...
Page 332 FC Single path mode For physical L-Servers, whether only one path has been configured for VIOM or HBAar is displayed. When single path mode is set "on" is displayed. When single path mode is not set "off" is displayed. Status OS Type The OS type of the L-Server is displayed.
Page 333 Allocated Resource Information(Virtual WWN address information) WWNN The information of the WWNN allocated to the L-Server is displayed. WWPN (World Wide Port Name) The information of the WWPN allocated to the L-Server is displayed. When single path mode is set, one of the displayed addresses is set for the WWPN address. Disk Information The disk number set for the L-Server is displayed.
Page 334: L-Platform Attributes
Network resource name The network name configured for the L-Server is displayed. VLAN The VLAN ID for the network resource is displayed. When "Untagged VLAN" is configured for the physical L-Server, "-" is displayed. Snapshots/System images Version The version of the snapshot image collected from the L-Server is displayed. Collection Date The date and time the snapshot image was collected from the L-Server is displayed.
Page 335 Current Resource The following information is displayed according to the L-Server allocation status. When resources are already allocated (allocated) The name of the physical server or VM host that has been allocated is displayed. When servers have been released (preserved) The name of the physical server or VM host that was used the last time the L-Server was started is displayed.
Page 336: Firewall Attributes
Type The type of the resource allocated to the L-Platform is displayed. "Firewall" is displayed. Ruleset The name of the directory containing the ruleset used by the resources allocated to the L-Platform is displayed. Use Resource The name and status of the network device configuring the resources allocated to the L-Platform are displayed in the following format.
Page 337: Slb Attributes
Parameter File Name The name of the parameter file set for the ruleset is displayed. network device Preserved resource The name of the network device that configures the resource allocated to the L-Platform. Clicking the link displays the [Resource Details] tab of the network device. Status The status of the resource to be used is displayed.
Page 338 Global Pool List Name (Label) The name (label) of the global pool is displayed. Type The resource pool type of the global pool is displayed. Priority The priority of the resource pool for automatically selecting a resource when creating an L-Server is displayed. Stored Resource Number The number of resources stored in the global pool is displayed.
Page 339 The icon that represents the L-Server's OS is displayed. For the list of supported OSs and their icons, refer to "11.2 Resource Status" in the "Operation Guide CE". If the L-Server's OS is not listed in the table, a hyphen ("-") is displayed in place of an icon. Current Resource The following information is displayed according to the L-Server allocation status.
Page 340: Vm Pool Attributes
Model(Defined) The model name defined during L-Server creation is displayed. Model(Allocated) The model name of the physical server actually allocated to the L-Server is displayed. A.6.17 VM Pool Attributes General Area Name (Label) The name of the resource is displayed. Type The type of the resource is displayed.
Page 341 Cluster Group Displayed when using cluster configurations. CPU Capacity (Unused/Total) The CPU capacity of the registered VM host is displayed. Memory Capacity (Unused/Total) The memory capacity of the registered VM host is displayed. VM Host Attributes General Area Name (Label) The name of the resource is displayed.
Page 342 VM Management Software Specific Information VMware HA The ON/OFF status of VMware HA is displayed. One of the following is displayed: Displayed when the VM host is VMware. When not in a cluster configuration, a hyphen ("-") is displayed. VMware DRS The ON/OFF status of VMware DRS is displayed.
Page 343: Server Pool Attributes
One of the following is displayed: Displayed when the VM host is VMware or Hyper-V. When not in a cluster configuration, a hyphen ("-") is displayed. VM Guest List Name (Label) The name of the VM guest is displayed. Status The status of the VM guest is displayed.
Page 344 Capacity Number of Servers Total Units The total number of servers registered in the server pool is displayed. Unused Units The number of available servers registered in the server pool is displayed. Physical Server List Physical Server Name The name of the physical server is displayed. Status The status of the physical server is displayed.
Page 345 Partition ID The partition number is displayed. Displayed only when a PRIMEQUEST or SPARC Enterprise M4000/M5000/M8000/M9000 server is selected. Maintenance Mode The maintenance mode of the physical server is displayed. Not displayed when SPARC Enterprise servers are selected. LED status The illumination status of the maintenance LED for the physical server is displayed.
Page 346: Storage Pool Attributes
Network Properties (Physical Connections) Index The network number that belongs to the physical server is displayed. LAN Switch The name of the LAN switch that belongs to the physical server is displayed. Port Name The name of the port that belongs to the physical server is displayed. hardware maintenance(NIC Summary) For servers other than PRIMERGY BX servers and PRIMEQUEST servers, only admin LAN information is displayed.
Page 347 Capacity Disk Capacity Total Capacity The total disk capacity of the storage pool is displayed. Unused Capacity The free disk capacity of the storage pool is displayed. Virtual Storage List Name (Label) The name of the registered virtual storage is displayed. Status The status of the registered virtual storage is displayed.
Page 348 Virtual Storage Attributes General Area Name (Label) The name of the resource is displayed. Type The type of the resource is displayed. Label The label set for the resource is displayed. Comments Comments set for the resource are displayed. Configuration Information Status The status of the resource is displayed.
Page 349 When thin provisioning is configured "Thin Provisioning" is displayed. When thick provisioning is configured "Thick Provisioning" is displayed. Allocated L-Server The name of the L-Server to which a disk has been allocated is displayed. Disk Details Attributes General Area Name (Label) The disk name is displayed.
Page 350: Network Pool Attributes
Thin Provisioning Thin provisioning configuration information is displayed. When thin provisioning is configured "yes" is displayed. When thick provisioning is configured "no" is displayed. Alias If the disk type is ETERNUS, the alias name set in LUN is displayed. A hyphen ("-") is displayed in the following cases: When the disk type is one other than ETERNUS If an alias name has not been set in LUN Information...
Page 351 Unused Number The number of unused IP addresses registered in the network pool is displayed. Network Resource List Name (Label) The network resource name is displayed. Admin LAN Whether it is being used as an admin LAN is displayed. When used as an admin LAN "yes"...
Page 352 Network Resource Attributes General Area Name (Label) The network resource name is displayed. Type The network resource is displayed. Label The label for the network resource is displayed. Comments Comments for the network resource are displayed. Capacity IP address Total Number The total number of IP addresses registered in the network pool is displayed.
Page 353 When automatic configuration is not performed "no" is displayed. Start Address The start address of the IP addresses to be automatically configured is displayed. End Address The end address of the IP addresses to be automatically configured is displayed. Subnet address The subnet address of the network resource is displayed.
Page 354: Address Pool Attributes
VLAN Type The VLAN type is displayed. When used as Tagged VLAN "tagged" is displayed. When used as Untagged VLAN "untagged" is displayed. When VLAN is not used "none" is displayed. Status of virtual switch automatic configuration The following information is displayed when automatic network configuration has been performed on the target of network resource automatic configuration or when a VM host on which automatic network configuration has been performed exists in the cluster.
Page 355 Capacity Number Of Address Total Number The total number of IP addresses stored in the address pool is displayed. Unused Number The number of unused IP addresses stored in the address pool is displayed. General Area Name (Label) The name of the address set is displayed. Address Type The address type of the address set is displayed.
Page 356: Image Pool Attributes
Excluded Address List Address The list of IP addresses to be excluded from the address set is displayed. A.6.22 Image Pool Attributes General Area Name (Label) The name of the resource is displayed. Type The type of the resource is displayed. Label The label set for the resource is displayed.
Page 357: Recovery Settings] Tab
Image Information Image Type The image type of the cloning image is displayed. The name of the operating system stored in the cloning image is displayed. Version List Name (Label) The name of the image is displayed. Version The version of the image is displayed. Collection Date The date and time the image was collected is displayed.
Page 358: Image List] Tab
A.8 [Image List] Tab The [Image List] tab displays information regarding available images. Those lists can be used to manage both system images and cloning images. The following two tables list the items that are displayed in System Image List and Cloning Image List. System Image List Server Name The name used to identify a physical OS or VM host is displayed.
Page 359: Available Pool
A.10 Available Pool This section describes the available pools displayed in the ROR console. For each resource pool type, the list of resource pools that can be used according to the role and scope of access of the logged in user is displayed.
Page 360 Path The path to the location of the folder or the tenant on the orchestration tree in which a resource pool is stored is displayed. Priority The priority of the resource pool is displayed. Resource Number The number of resources registered in the resource pool is displayed. Capacity(Unused/Total) The capacity of the virtual storage or disk resources registered in the resource pool is displayed.
Page 361: Template List
Image Pool Name (Label) The name used to identify the resource pool is displayed. Path The path to the location of the folder or the tenant on the orchestration tree in which a resource pool is stored is displayed. Priority The priority of the resource pool is displayed.
Page 362: Event
Status The status of the executed operation is displayed. The date and time at which the process was completed is displayed. Point When an operation is executed in a tab other than the [Resource] tab, e.g., the [L-Platform] tab, multiple entries might be displayed in the Recent Operations for that single operation.
Page 363 Event Information Status Displays the level of the event. There are three levels: "Error", "Warning", or "Info". Date Date and time at which the event occurred. Tenant Name Name of the tenant associated with the event. Resource Name Name of the resource associated with the event. Event ID Identifier related to the event.
Page 364: Search
A.14 Search This section explains the search screen of the ROR console. Figure A.8 Search This screen can be used to search resources on the orchestration tree by type and name. The following conditions can be specified during a search. Resource Type Specify the research type to search.
Page 365 Point The "L-Platform Name" or "Server Name" displayed on the [L-Platform] tab may be set for the comment. Detailed conditions other than the type and name can be specified during a search. Tenant To search only the resources in a certain tenant, specify the name of the tenant. Status To search only the resources which have a certain status, specify the target status.
Page 366: Dialogs
Tenant The name of the tenant associated with the resource is displayed. Path The path of the resource on the orchestration tree is displayed. Clicking a column heading will change the color of the selected column and sort events in either ascending or descending order. In each page of the list, 10 items can be displayed.
Page 367: 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 368: 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 2 Login and Logout" in the "User's Guide for Infrastructure Administrators CE". Select [File]-[System Configuration File]-[Download Template] from the ROR console menu.
Page 369 RCXCSV V3.1 and Later "SPARCEnterprise" 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 370 Register 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 371 Table B.2 Section Order and Section Names Order Section Name Subnet VIOManager 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.
Page 372: Resource Definitions
Comments lines Strings enclosed in parenthesis "( )" indicating omitted values Extra commas at the end of lines (",") 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.
Page 373 ip_address Enter the IP address of the terminal on which VIOM is installed. Specify "127.0.0.1". 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.
Page 374 PRIMEQUEST Chassis Management Data Section Name Enter [PRIMERGYPartitionModelChassis] 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 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 375 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 376 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 377 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 378 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 379 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 380 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 381 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 382 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 383 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 384 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 385 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 386 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 387 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 388 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 389 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 390 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 391 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 392: 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 393 [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 394 -,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 395 -,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 396: 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 397: 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 398 Auto-Recovery A function which continues operations by automatically switching over the system image of a failed server to a spare server and restarting it in the event of server failure. This function can be used when managed servers are in a local boot configuration, SAN boot configuration, or a configuration such as iSCSI boot where booting is performed from a disk on a network.
Page 399 CCM (ETERNUS SF AdvancedCopy Manager Copy Control Module) This is a module that does not require installation of the ETERNUS SF AdvancedCopy Manager agent on the server that is the source of the backup, but rather uses the advanced copy feature of the ETERNUS disk array to make backups. chassis A chassis used to house server blades and partitions.
Page 400 end host mode This is a mode where the uplink port that can communicate with a downlink port is fixed at one, and communication between uplink ports is blocked. environmental data Measured data regarding the external environments of servers managed using Resource Orchestrator. Measured data includes power data collected from power monitoring targets.
Page 401 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 402 The IPCOM EX IN series fits into this category. 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 403 iSCSI storage Storage that uses an iSCSI connection. LAG (Link Aggregation Group) A single logical port created from multiple physical ports using link aggregation. LAN switch blades A LAN switch that is mounted in the chassis of a blade server. LDAP (Lightweight Directory Access Protocol) A protocol used for accessing Internet standard directories operated using TCP/IP.
Page 404 LUN (Logical Unit Number) A logical unit defined in the channel adapter of a storage unit. MAC address (Media Access Control address) A unique identifier that is assigned to Ethernet cards (hardware). Also referred to as a physical address. Transmission of data is performed based on this identifier. Described using a combination of the unique identifying numbers managed by/assigned to each maker by the IEEE, and the numbers that each maker assigns to their hardware.
Page 405 Cold migration Migration of an inactive (powered-off) VM guest. Live migration Migration of an active (powered-on) VM guest. multi-slot server A server that occupies multiple slots. NAS (Network Attached Storage) A collective term for storage that is directly connected to a LAN. network device The unit used for registration of network devices.
Page 406 The OS used by an operating server (a physical OS or VM guest). overcommit A function to virtually allocate more resources than the actual amount of resources (CPUs and memory) of a server. This function is used to enable allocation of more disk resources than are mounted in the target server. PDU (Power Distribution Unit) A device for distributing power (such as a power strip).
Page 407 Each RDN must be unique within the same entry. 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 408 For Dell/IBM servers BMC (Baseboard Management Controller) Remote Server Management A PRIMEQUEST feature for managing partitions. Reserved SB Indicates the new system board that will be embedded to replace a failed system board if the hardware of a system board embedded in a partition fails and it is necessary to disconnect the failed system board.
Page 409 The script lists contain the scripts used to perform automatic configuration. There are the following eight types of script lists: script lists for setup script lists for setup error recovery script lists for modification script lists for modification error recovery script lists for setup (physical server added) script lists for setup error recovery (physical server added) script lists for deletion (physical server deleted)
Page 410 ServerView Update Manager Express Insert the ServerView Suite DVD1 or ServerView Suite Update DVD into the server requiring updating and start it. This is software that performs batch updates of BIOS, firmware, drivers, and hardware monitoring software. Single Sign-On A system among external software which can be used without login operations, after authentication is executed once. slave slot A slot that is not recognized as a server when a server that occupies multiple slots is mounted.
Page 411 switchover state The state in which switchover has been performed on a managed server, but neither failback nor continuation have been performed. system administrator The administrator who manages the entire system. They perform pre-configuration and installation of Resource Orchestrator. Administrator privileges for the operating system are required. Normally the roles of the infrastructure administrator and system administrator are performed concurrently.
Page 412 Example \\hostname\dir_name 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 413 Using a Virtual LAN, network configuration can be performed freely without the need for modification of the physical network configuration. VLAN ID A number (between 1 and 4,095) used to identify VLANs. Null values are reserved for priority tagged frames, and 4,096 (FFF in hexadecimal) is reserved for mounting. VM (Virtual Machine) A virtual computer that operates on a VM host.
Page 414 WWNN (World Wide Node Name) A name that is set as a common value for the Fibre Channel ports of a node. However, the definitions of nodes vary between manufacturers, and may also indicate devices or adapters. Also referred to as a node WWN. WWPN (World Wide Port Name) A name that is a unique value and is set for each Fibre Channel port (HBA, CA, fibre channel switch ports, etc.), and is the IEEE global MAC address.

This manual is also suitable for:

Serverview resource orchestrator cloud edition v3.1.1

Fujitsu ServerView Resource Orchestrator Cloud Edition V3.1.0 User Manual

Chapter 1 Resource Management Overview

Chapter 2 License Setup and Confirmation

Chapter 3 Configuring Users for Infrastructure Administrators

Chapter 4 Bladeviewer

Chapter 5 Registering Resources

Chapter 6 Changing Admin Server Settings

Chapter 7 Changing Resources

Chapter 8 Configuring the Operating Environments of Managed Servers

Chapter 9 Deleting Resources

Chapter 10 Pre-Configuration for Resource Registration and Modification

Chapter 11 Network Map

Chapter 12 Cloning [Physical Servers]

Chapter 13 Collecting Power Consumption Data and Displaying Graphs

Chapter 14 Registering Resources in Resource Pools

Chapter 15 L-Server Template Operations

Chapter 16 Creating L-Servers

Chapter 17 L-Server Operations

Chapter 18 Linking L-Servers with Configured Physical Servers or Virtual Machines

Chapter 19 Resource Operations

Chapter 20 Resource Pool Operations

Chapter 21 Resource Folder Operations

Chapter 22 Network Device Operations

Chapter 23 Network Resource Operations

Appendix A User Interface

Quick Links

(Resource Management)

Related Manuals for Fujitsu ServerView Resource Orchestrator Cloud Edition V3.1.0

Summary of Contents for Fujitsu ServerView Resource Orchestrator Cloud Edition V3.1.0