ServerView Resource Orchestrator Cloud Edition V3.1.
Preface Resource Orchestrator Documentation Road Map The documentation road map for Resource Orchestrator is as shown below. Resource Orchestrator Documentation Road Map Point Refer to the user role manuals displayed in the table below for roles that are not in the diagram.
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.
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 LServer.
[KVM] Sections related to RHEL-KVM [Solaris Containers] Sections related to Solaris containers [Oracle VM] Sections related to Oracle VM [Physical Servers] Sections related to physical servers [VM host] Sections related to Windows Server 2008 with VMware or Hyper-V enabled - Unless specified otherwise, the blade servers mentioned in this manual refer to PRIMERGY BX servers. - Oracle Solaris may also be indicated as Solaris, Solaris Operating System, or Solaris OS.
Abbreviation Products Windows(R) 7 Professional Windows(R) 7 Ultimate Windows Vista(R) Business Windows Vista(R) Enterprise Windows Vista(R) Ultimate Microsoft(R) Windows(R) XP Professional operating system Windows Server 2008 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 Windows 2008 x86 Edition Microsoft(R) Wi
Abbreviation Products Red Hat(R) Enterprise Linux(R) 5.1 (for Intel64) Red Hat(R) Enterprise Linux(R) 5.2 (for x86) Red Hat(R) Enterprise Linux(R) 5.2 (for Intel64) Red Hat(R) Enterprise Linux(R) 5.3 (for x86) 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.
Abbreviation Products SCVMM System Center Virtual Machine Manager 2008 R2 System Center 2012 Virtual Machine Manager VMware VMware vSphere(R) 4 VMware vSphere(R) 4.1 VMware vSphere(R) 5 VMware ESX VMware(R) ESX(R) VMware ESX 4 VMware(R) ESX(R) 4 VMware ESXi VMware(R) ESXi(TM) VMware ESXi 5.0 VMware(R) ESXi(TM) 5.0 VMware Tools VMware(R) Tools VMware vSphere 4.0 VMware vSphere(R) 4.0 VMware vSphere 4.1 VMware vSphere(R) 4.
- EMC, EMC2, CLARiiON, Symmetrix, and Navisphere are trademarks or registered trademarks of EMC Corporation. - HP is a registered trademark of Hewlett-Packard Company. - Linux is a trademark or registered trademark of Linus Torvalds in the United States and other countries.
Contents Chapter 1 Resource Management Overview...........................................................................................................................1 Chapter 2 License Setup and Confirmation..............................................................................................................................2 Chapter 3 Configuring Users for Infrastructure Administrators.................................................................................................3 3.
5.10 Registering Power Monitoring Devices...........................................................................................................................................50 5.11 Registering Admin LAN Subnets....................................................................................................................................................51 5.12 Registering BMC BladeLogic Server Automation...............................................................................................
Chapter 9 Deleting Resources............................................................................................................................................... 91 9.1 Deleting Chassis................................................................................................................................................................................91 9.2 Deleting Managed Servers..............................................................................................................
Chapter 15 L-Server Template Operations..........................................................................................................................148 15.1 Operations Using the Wizard GUI.................................................................................................................................................148 15.1.1 Viewing....................................................................................................................................................
17.8.2 Operations...............................................................................................................................................................................222 17.8.2.1 Allocating Resources.......................................................................................................................................................222 17.8.2.2 Releasing Resources........................................................................................................
A.2.1 List of Menus...........................................................................................................................................................................263 A.2.2 Popup Menus...........................................................................................................................................................................266 A.3 Status Panel..............................................................................................................
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.
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: 1. After logging in to Resource Orchestrator, select [Tools]-[Licenses] from the menu, and click in the displayed dialog. The [Register License] dialog is displayed. 2. In the [Register License] dialog, enter the license key to register. 3.
Chapter 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". 3.1 Registering User Accounts This section explains how to register user accounts of infrastructure administrators.
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. Role Select the role to set for the user account. Label (Optional) Enter a label for the user account. Enter a maximum of 32 characters.
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: 1. In the ROR console, select [Settings]-[User Accounts]. The [User Accounts] dialog is displayed. 2. Select the user account to modify. 3. Click . The [Change User Account] dialog is displayed. 4. Change the items you want to modify. 5. Click . The user account information is modified.
2. Select the user account to delete. 3. Click . The [Delete User Account] dialog is displayed. 4. Confirm the user account to delete. 5. Click . 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".
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. This makes it easier to monitor resource states or perform basic operations on blade servers. Figure 4.
- 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. The BladeViewer screen consists of a status panel, a chassis panel, and a blade 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. The table below shows the status and meaning associated with each light icon. Table 4.
Table 4.4 Chassis Icon Icon Meaning Chassis See 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". Information Selecting a chassis icon from the chassis panel displays the contents of that chassis in the blade panel. For details, refer to "4.3.
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 Meaning Green (lit) Power ON Power ON status. Gray (not lit) Power OFF Power OFF status. Green (blinking) Power ON in progress Power ON or reboot in progress. Orange (blinking) Power OFF in progress Power OFF in progress.
Table 4.8 Physical Server Icons Icon Meaning Server Spare server Unregistered server Maintenance mode server See For details on the different physical server statuses, refer to "Table 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 Admin server Meaning Indicates the server used as the admin server. An OS icon is displayed below the physical server icon.
- If the OS name cannot be acquired (because the OS has not been installed or for other reasons) The server name (physical server name or VM guest name) is displayed. The following table shows the resource icons used in BladeViewer and their associated meanings. Table 4.11 Resource Icons Icon Meaning Physical OS VM host VM guest See For details on the resource status, refer to "Table 4.3 Status Icons" in "4.3.1 Status Panel".
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 See For details on the different VM guest statuses, refer to "Table 4.3 Status Icons" in "4.3.1 Status Panel". A user-defined label is displayed on the upper-right side of the VM guest icon. - If no label is set The OS name is displayed.
Power button Color Status Orange (blinking) Power OFF in progress Meaning Power OFF in progress. Information The power status of a VM guest can be easily controlled by clicking on its power button. Refer to "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. - Chassis Clicking a chassis icon (from the blade panel) opens up its management blade's Web interface in a new window.
Power Off and Reboot Clicking on a power button that shows "Power ON" status will either shut down or reboot the target server blade. A [Power Operation] dialog is displayed, in which the appropriate action can be selected. Figure 4.5 Power Operation Dialog - "Shutdown" Selecting "Shutdown" will shut down the target server blade. A confirmation dialog is displayed first. Clicking in the confirmation dialog shuts down the OS and powers off the managed server.
Figure 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 in the confirmation dialog will power off the managed server without waiting for its OS to shut down cleanly. At this time, the power button changes to an intermediate "Power OFF in progress" state (orange - blinking).
Power button Color Green (lit) Status Power ON Action Shuts down or reboots a VM guest. Note - VM guests need to be properly configured in order to use the shut down or reboot buttons. Attempting to shut down or reboot a VM guest that is not properly configured will result in an error. For details, refer to "D.2 Configuration Requirements" in the "Design Guide VE".
Contact icon Displays the [Contact] dialog. This dialog shows the contact information that was set for the entire system. Tools icon Enables selection of the following menu options: Display Label List Displays the [Label List] dialog. Displays a list of labels. This list also allows modification of labels and comments. For details on editing labels and comments, refer to "4.5.1 Listing and Editing of Labels and Comments". Set Contact Information Displays the [Set Contact Information] dialog.
Editing Labels and Comments This function is only available to privileged users. General users are only able to consult labels and comments. - Privileged user In the [Label List] dialog, select a server and click . The [Modify Server Settings] dialog is displayed. The label and comment of the selected server can be edited directly from the [Modify Server Settings] dialog. Enter the following items: Label Enter up to 32 alphanumeric characters or symbols (ASCII characters 0x20 to 0x7e).
- Privileged user New password (Confirm password) Enter a string using up to 16 alphanumeric characters or symbols. - General user Current password Enter the password that is currently set. Enter a string using up to 16 alphanumeric characters or symbols. New password (Confirm password) Enter a string using up to 16 alphanumeric characters or symbols.
Chapter 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 registration settings of multiple resources in batches using the pre-configuration function.
Note HBA address rename and VIOM cannot be used together within the same chassis. When using backup and restore or cloning, prioritize the following two boot operations: 1. Boot from the first admin LAN network interface (NIC1 (Index1)) 2. Boot from the network interface used by the admin LAN (NIC2 (Index2)) 5.2 Registering VM Management Software This section explains how to register VM management software.
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). Password Enter the password for VM management software.
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. *2: Depending on the VM management product, an IP address that differs from that of the admin LAN of the VM host may be obtained.
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. Use the following procedure to register storage management software: 1.
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" in the "Design Guide CE". By registering a chassis, every server blade mounted in the chassis will be automatically detected and displayed as an unregistered server in the server resource tree.
Figure 5.2 Status Transition Diagram for Managed Servers Use the following procedure to register blade servers. 1. In the ROR console server resource tree, right-click an unregistered server blade or partition in the target chassis, and select [Register]-[Server] from the popup menu. The [Register Server] dialog is displayed. 2. To use this feature, the following settings must first be defined: Physical Server Name Enter a name to assign to this physical server.
- With Agent Registration Agents are automatically registered after server registration is completed. Admin LAN (IP address) Enter the IP address used by this server on the admin LAN. When IP address is displayed Entering an admin LAN (IP address) is not required. Agents are automatically registered. 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.
Password Enter the password of the user to log in to the VM host. Boot option Only set this when the targets of operations are PRIMEQUEST servers. Specify the boot option configured from BIOS when installing the OS. - For UEFI Select [UEFI]. - For Legacy Boot Select [Legacy boot]. By default, [UEFI] is selected. These settings can be changed after server registration. For details on how to modify these settings, refer to "7.1.10 Changing Boot Options".
take a few minutes to obtain hardware information and update internal properties. Confirm that the correct MAC address is displayed correctly before registering the server again. For details on the appropriate corrective action, refer to "Message number 61142" in "Messages". - A server running a VM host can still be registered as a physical OS if its [Server OS category] is set to [Windows/Linux]. (For Windows Server 2008, etc.
User ID Enter the name of a telnet or SSH user account that can log in to this LAN switch blade. Password Enter the password of the above telnet or SSH user account. Connection method Select either [Telnet] or [SSH]. The default setting is [Telnet]. Administrative password Enter the password of this LAN switch blade's telnet or SSH administrator account.
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. 1. In the ROR console server resource tree, right-click the target LAN switch blade and select [Modify]-[Network Settings] from the popup menu. The [VLAN Settings] dialog is displayed. 2.
5. Confirm the configuration set in the [Network Settings] dialog. 6. Click . VLAN settings are applied to the related LAN switch blade. Note The VLAN configuration of a registered LAN switch blade should be set from the ROR console instead of the LAN switch's own Webbased and command-based interfaces. If the Port VLAN ID field is left blank and a value is entered for Tagged VLAN ID in the [VLAN Configuration] dialog, the tagged LAN only will be enabled.
Figure 5.3 Status Transition Diagram for Managed Servers Use the following procedure to register rack mount or tower servers. 1. In the ROR console server resource tree, right-click [Server Resources], and select [Register]-[Server] from the popup menu. The [Register Server] dialog is displayed. 2. To use this feature, the following settings must first be defined: Enter items differ depending on whether the [Register agent] checkbox is selected, as described below.
- Admin LAN - IP address - MAC address (NIC1) 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) 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". Automatic registration of agents is not performed after server registration.
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. Enter up to 16 characters, including alphanumeric characters and symbols (ASCII characters 0x20 to 0x7e). This field can be omitted if no password has been set for this user account.
("xx:xx:xx:xx:xx:xx"). This field can be omitted in the following cases. - When not using GLS for admin LAN redundancy on the managed server - For a spare server whose primary servers are not using admin LAN redundancy OS Type This option is displayed if the target server runs a physical OS or VM host. Select the appropriate server OS category (Physical OS or VM host). Selecting [VM Host] activates the user ID and password input fields.
- 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. - The VM guest name displayed in the ROR console is either the VM name defined in its server virtualization software or the host name defined in the guest OS.
SNMP Community Enter the SNMP community that was set on this LAN switch. Either select [public] or enter an arbitrary string. Enter a string of up to 32 alphanumeric characters, underscores ("_"), and hyphens ("-"). 3. Click . Resource Orchestrator starts scanning for LAN switches within the specified network range. Discovered LAN switches will be displayed under the network device tree with the status [[Unregistered]]. Registration 1.
Note - The HBA address rename function is not available if ServerView Deployment Manager is used on the admin LAN. For details, refer to "Appendix B Co-Existence with ServerView Deployment Manager" in the "Setup Guide VE".
Figure 5.4 Procedures for Single-path Configurations Figure 5.
Example For a server with two ports, WWNs could be configured as follows.
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" in the "Design Guide CE".
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 Use the following procedure to register a network device: 1.
- 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. - Under redundancy configuration, it is only enabled for the same vendor and model.
Note The [User ID] and [Password] of [Remote server management] are different from the user name and password used to log in on the Web-UI for management board. 3. Click . The mounted chassis will be displayed under the server resource tree. Any partition mounted within this chassis will be detected automatically and shown as: [chassis_namepartition_number[Unregistered]].
Remote management controller (XSCF) User ID Enter the ID of an XSCF user account with administrative authority over the target chassis. Enter a string of up to 31 alphanumeric characters, hyphens ("-"), and underscores ("_"). This name must start with an alphabet character. This user should have "platadm" privileges for XSCF. Password Enter the password of an XSCF user account with administrative authority over the target chassis.
[Register agent] checkbox - Without Agent Registration Automatic registration of agents is not performed after server registration. After registering servers, register agents as required. If registering agents, register agents after checking the product name is displayed in the General Area of [Resource Details] tab. Executing [Update] acquires the latest information. - With Agent Registration Agents are automatically registered after server registration is completed.
SNMP Community Enter the SNMP community name of this server's remote management controller (ILOM). Either select [public] or enter an arbitrary string. Enter a string of up to 32 alphanumeric characters, underscores ("_"), and hyphens ("-"). Admin LAN IP address Enter the IP address used by this server on the admin LAN. Server OS Category Select the appropriate server OS category (Physical OS or VM host). Selecting [Solaris Containers] activates the user name and password input fields.
2. To use this feature, the following settings must first be defined: Device name Enter a name to assign to this power monitoring device. When exporting power consumption data, use this name to select power monitoring devices for which to export data. Enter a character string beginning with an alphabetical character and containing up to 15 alphanumeric characters and hyphens ("-"). Admin LAN (IP address) Enter the IP address that was set on this power monitoring device.
3. To use this feature, the following settings must first be defined: Subnet name Set the subnet name for registration. The name must start with an alphabetic character and can be up to 16 alphanumeric characters long (including underscores, "_", hyphens, "-", and periods, "."). Network address Configure the network address of the subnet used as the admin LAN. Enter valid values for the network address. Subnet mask Enter valid values for the subnet mask.
- x64 Resources for Deletion Registry Key [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 \SystemcastWizard\DHCP PXE Services [HKEY_LOCAL_MACHINE\]SOFTWARE\Wow6432Node\Fujitsu \SystemcastWizard\PXE\ClientBoot\ - x86 Resources for Deletion Registry Key [HKEY_LOCAL_MACHINE\]SOFTWARE\Fujitsu\SystemcastWizard \Resour
Local Disk (Source) Shared Disk (Target) %SystemRoot%\System32\dhcp Drive_name:\Fujitsu\ROR\SVROR\dhcp Example When the OS has been installed on the C drive, it is %SystemRoot%C:\Windows. 9. Configure access rights for the folder for the DHCP Server that was copied to the shared disk. Execute the following command using the command prompt of the primary node: >cacls Drive_name:\Fujitsu\ROR\SVROR\dhcp /T /P "NT AUTHORITY\SYSTEM:F" "BUILTIN \Administrators:F" "NT SERVICE\DHCPServer:F" 10.
d. Click . When configuring the second registry key as well, repeat steps b. to d. e. After configuration of the registry keys is complete, click . f. Click to close the dialog. 12. Configure the dependencies of the resources of the manager "service or application". Configure the dependencies of resources based on the following table. If some resources have been configured, select AND from [AND/OR] and add the dependent resource.
# mv -i source_file_name target_file_name 5. Configure symbolic links for the shared disk (Primary node) Configure symbolic links from the files and directory on the local disk of the primary node for the files on the shared disk. Execute the following command: # ln -s shared_disk local_disk Table 5.1 Files to Link Shared Disk Local Disk Mount_destination_of_shared_disk/Fujitsu/ROR/SVROR/etc/dhcpd.conf (*1) /etc/dhcpd.
b. Perform step 5 and configure symbolic links for the shared disk. 10. Unmount the shared disk. (Secondary node) Unmount the shared disk for managers from the secondary node. 11. Start cluster applications. Use the cluster system's operation management view (Cluster Admin) and start the manager cluster service (cluster application). 12. Register the admin LAN subnet. 5.12 Registering BMC BladeLogic Server Automation This section explains how to register BMC BladeLogic Server Automation.
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. 1. Log on to the admin server with OS administrative privileges. 2. Stop the manager. Stop the manager, referring to "2.1 Starting and Stopping the Manager" in the "Operation Guide CE". 3.
8. Stop the agents on managed servers. [Windows] [Hyper-V] [Linux] [Xen] [KVM] Stop the agent referring to "2.2 Starting and Stopping the Agent" in the "Operation Guide CE". 9. Change Agent settings. [Windows] [Hyper-V] [Linux] [Xen] [KVM] Use the rcxadm agtctl modify command to set the new manager IP address. [Windows] [Hyper-V] >"Installation_folder\Agent\bin\rcxadm" agtctl modify -manager IP_address [Linux] [Xen] [KVM] # /opt/FJSVrcxat/bin/rcxadm agtctl modify -manager IP_address 10.
1. Stop the manager's cluster service. Stop the manager's cluster service from the cluster administration view (Cluster Admin). 2. Log in to the admin server's primary node. Log in to the operating system of the admin server's primary node with administration privileges. 3. Mount the shared disk on the primary node. Mount the admin server's shared disk on the primary node. 4. Change takeover the logical IP address.
a. 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. b. Click on the [Registry Replication] tab. The [Registry Key] window will be displayed. c. Configure the above registry key in [Root registry key]. d. Click . e. After configuration of the registry keys is complete, click . f.
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; option vendor-class-identifier "PXEClient"; option dhcp-server-identifier 192.168.4.100; (*) subnet 192.168.4.0 netmask 255.255.255.
- 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) - rcxmongrel4 (*1) - rcxmongrel5 (*1) - rcxhttpd - rcxdb - Related Services - scwdepsvd - scwpxesvd - scwtftp
1. Stop the manager. Stop the manager, referring to "2.1 Starting and Stopping the Manager" in the "Operation Guide CE". 2. Change the port numbers. Use the rcxadm mgrctl modify command to set a new port number for a given service name.
number (65534). In a clustered manager configuration, change port numbers on both the primary and secondary node. 2. Restart the server on which the port number has been changed. [Linux Manager] 1. 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.
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. Delete unused image versions manually if they are no longer necessary.
2. Log on to the admin server with OS administrative privileges. 3. Stop the manager. Stop the manager, referring to "2.1 Starting and Stopping the Manager" in the "Operation Guide CE". 4. Change the location of the image file storage folder. Change the location of the image file storage folder according to the instructions given in "5.9 rcxadm imagemgr" in the "Reference Guide (Command/XML) CE". Because image files are actually copied over to the new location, this step may take some time to complete.
a. In the [Failover Cluster Management] window, right-click the [Deployment Service] resource in [Summary of RC-manager][Other Resources], and select [Properties] from the popup menu. The [Deployment Service Properties] window is displayed. b. Click on the [Registry Replication] tab. The [Registry Key] window will be displayed. c. Configure the above registry key in [Root registry key]. d. Click . e. After configuration of the registry keys is complete, click . f.
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 the chassis and managed servers. If collecting the system images and cloning images of managed servers, collect them after completing changes to managed server settings. For details on backing up system images, refer to "Backup".
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. 1. Change the IP address of the management blade. 2. In the ROR console server resource tree, right-click the target chassis and select [Modify]-[Registration Settings] from the popup menu.
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 Use the following procedure to change SNMP community used by chassis and managed servers. 1.
3. Change [SNMP Community]. 4. Click . 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. 1. Change settings on the remote management controller. If the user account is changed, it should still have administrator authority. 2.
3. Select the [Modify remote server management login account] checkbox. Then, change the [User ID] and [Password] of [Remote Server Management]. - For SPARC Enterprise M4000/M5000/M8000/M9000 servers Use the following procedure to change remote management controller (XSCF) settings. 1. Change settings on the remote management controller (XSCF). If the user account is changed, it should still have administrator authority ("platadm" privileges). 2.
2. Enter the new login account information that was changed on the VM host. User ID Enter the user ID to log in to the VM host. Specify a user ID that has VM host administrator authority. Password Enter the password of the user to log in to the VM host. 3. Click . VM host login information is changed. 7.1.8 Changing the VLAN Settings of LAN Switch Blades This section explains how to change LAN switch VLAN settings.
2. Select the subnet to change. The [Change Admin LAN Subnet] dialog is displayed. 3. In the [Change Admin LAN Subnet] dialog, set the following items. Subnet name The name must start with an alphabetic character and can be up to 16 alphanumeric characters long (including underscores, "_", hyphens, "-", and periods, "."). Network address Enter valid values for the network address. Subnet mask Enter valid values for the subnet mask.
Use the following procedure to change the IP address of the HBA address rename server. 1. Log in to the HBA address rename server with administrator authority. 2. Stop the HBA address rename setup service. Stop the HBA address rename setup service according to "Chapter 10 Settings for the HBA address rename Setup Service" in the "Setup Guide CE". 3. Change the IP address set within the operating system. Change the IP address according to the OS manual. 4. Restart the HBA address rename setup service.
1. In the ROR console server resource tree or network resource device tree, right-click the target LAN switch name and select [Modify][Registration Settings] from the popup menu. The [Modify LAN Switch] dialog is displayed. 2. Make changes to the values as needed. 3. Click . The settings for the LAN switch are changed with the entered information. Note - It is possible to set the IP address of the target switch to another unregistered LAN switch.
Changing VLAN IDs This section explains how to change VLAN IDs set on the external ports of a LAN switch. - With Port VLANs Use the following procedure to change VLAN IDs: 1. In the ROR console server resource tree, right-click the target LAN switch blade and select [Modify]-[Network Settings] from the popup menu. The [VLAN Settings] dialog is displayed. 2. To use this feature, the following settings must first be defined: VLAN Select "Change" and select the VLAN ID that has been changed.
1. In the ROR console server resource tree, right-click the target LAN switch blade and select [Modify]-[Network Settings] from the popup menu. The [VLAN Settings] dialog is displayed. 2. To use this feature, the following settings must first be defined: VLAN Select "Change" and select the VLAN ID that has been changed. Physical Port, Link Aggregation Change the VLAN type (Untagged] or [Tagged]) of the port number to configure or link aggregation group name. 3. Click . The VLAN type is changed.
Note When using "auto-configuration for network device" function on a LAN switch, register it as a network device using the method described in "5.7 Registering Network Devices" instead of re-executing LAN switch discovery. 7.5 Modifying Network Resource Specifications This section explains how to modify specifications of network resources. The availability of modification for each item depending on the network resource type is shown below: Table 7.
1. Right-click the target network resource in the orchestration tree, and select [Change Settings]-[Modify Specification] from the popup menu. The [Modify a network resource] dialog is displayed. 2. Change the items you want to modify. 3. Click . The network resource is changed. Note - The default gateway address of an admin LAN resource which is the same subnet address as that of the manager cannot be changed.
- Location - Type Information - Maintenance mode - Group ID - SNMP Information - Login Information - Monitoring Settings - Web Interface URL Network device settings can be changed using the following methods: - When modifying network devices individually Use the rcxadm netdevice modify command. - When modifying multiple network devices at one time Use the rcxadm netconfig import command. See - For details on the rcxadm netdevice command, refer to "3.
1. In the ROR console management software tree, right-click the target management software, and select [Modify]-[Registration Settings] from the popup menu. The [Modify Management Software(name) Settings] dialog is displayed. The name of the selected VM management software is displayed in name. 2. Enter the following items: Location Select the location of the VM management software registration to change. - If VM management software is installed on the admin server Select [Admin Server].
Data storage period Enter storage periods for each collection rate. Data older than the configured storage period will be deleted every day. Enlarging data storage periods reduces the number of devices that can be monitored simultaneously. Use the default storage period values when monitoring chassis and servers. 3. Click . The new settings are applied.
7.9 Changing Monitoring Information Settings This section explains how to change and cancel monitoring information settings. 7.9.1 Changing Monitoring Information Settings This section explains how to change monitoring information settings. The following settings can be changed. - Enabling or disabling of ping monitoring - Time-out - Recovery method - Number of reboots Use the following procedure to change settings: 1.
2. Modify the values for the following items: Label Enter up to 32 alphanumeric characters or symbols. Comments Enter up to 256 alphanumeric characters or symbols. 3. Click . Basic information for the storage management software is modified. 7.10.2 Changing Storage Unit Basic Information This section explains how to change the basic information of storage units. The following settings can be changed. - Label - Comments Use the following procedure to change the basic information of storage units: 1.
3. Click . The basic information of the virtual storage resource is modified. 7.10.4 Changing Disk Resource Basic Information This section explains how to modify the basic information for disk resources. The following settings can be changed. - Label - Comments Use the following procedure to modify the basic information for disk resources 1. Select the target virtual storage in the ROR console storage tree. The disk resource list is displayed in the [Resource List] tab. 2.
Chapter 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.
1. In the ROR console server resource tree, right-click the target physical server, and select [Modify]-[WWN Settings] from the popup menu. The [WWN Settings] dialog is displayed. 2. To use this feature, the following settings must first be defined: HBA ports Select the following values according to the system configuration. - Procedures for Single-path Configurations Specify "1" for HBA ports. - Procedures for Multi-path Configurations Select the number of multi-paths for HBA ports.
- If the target CA is not displayed, confirm the status of the following settings: - ESC is correctly registered on Resource Orchestrator. - Fibre Channel switches and storage units are correctly registered. - Only one access path is configured on ESC for each CA of an HBA. 8.2 Deploying Cloning Images For the second and subsequent servers, operating systems are created using the cloning image collected from the first server. For details on cloning, refer to "Chapter 12 Cloning [Physical Servers]".
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.
Information - If HBA address rename has already been set up on the managed server, the HBA WWN is reset to the factory default. When this occurs, the managed server is turned on temporarily, after the power is forcibly turned off once. When the operating system is running on a managed server, it is recommended to shut it down before deleting the server. - VM guests can be deleted using the management console of the server virtualization software used.
- 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.) 9.
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" in the "Reference Guide (Command/XML) CE". 9.5 Deleting Network Resources This section explains how to delete network resources.
1. In the ROR console management software tree, right-click the target management software, and select [Delete] from the popup menu. The [Delete Resource] dialog is displayed. 2. Click . The target management software is deleted. 9.7 Clearing the Power Monitoring Environment This section explains how to clear the power monitoring environment. Clearing the power monitoring environment is done by deleting power monitoring targets. For details on how to release collection settings, refer to "7.8.
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. 1. In the ROR console management software tree, right-click the target management software (BladeLogic), and select [Delete] from the popup menu. The [Delete management software(BladeLogic)] dialog is displayed. 2. Click . The target BMC BladeLogic Server Automation is deleted.
Chapter 10 Pre-configuration for Resource Registration and Modification This chapter provides an overview of the pre-configuration function and explains how to use system configuration files. 10.1 Overview Using the Pre-configuration function, it is possible to create system definition files that can be later used to setup a Resource Orchestrator environment. Importing system configuration files makes it easy to perform various registration settings in one operation.
- When saving a file in CSV format from the system configuration template, or exporting a system configuration file from the ROR console Export will be performed using the latest file format given in "B.2 File Format". The following operations, usually performed from the ROR console, can be equally performed using the pre-configuration function. - Registration - "5.1 Registering VIOM Coordination" - "5.4 When using Blade Servers" - "5.5.2 Registering LAN Switches" - "5.
Note - The following operations cannot be performed by the pre-configuration function, and should be performed from the ROR console.
3. In the ROR console, select [File]-[System Configuration File]-[Import] from the menu. The [Import System Configuration File] dialog is displayed. 4. Specify a configuration file prepared in step 1. 5. Click . The import process starts. The system configuration file is verified first, and then resources are imported one by one, following the order defined by the system configuration file. The processing of resource registration or change is executed after the verification.
- When changing physical server names during pre-configuration, it cannot be performed at the same time as other preconfiguration operations. Import the "Server" section separately from other sections. 6. When the import is completed successfully, a message is displayed in the Recent Operations area. Point - Error handling The processing of resource registration or change is executed after the verification of the system configuration file during import.
- If the agent is registered, perform either one of the following to enable further backup or cloning operations. - Restart the managed server. - Restart the Related Service described in "2.2 Starting and Stopping the Agent" in the "Operation Guide CE". 10.3 Exporting the System Configuration File This section explains the method for exporting a system configuration file containing the current system settings.
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.
- 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 - Showing or hiding of the following information - Resource descriptions - Network links - VLANs - Resetting to initial display - Highlighting of a selected resource - Showing or hiding of details for the following res
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). 11.3 Screen Layout This section describes the Network Map's layout. The main part of the Network Map is the network view. 11.3.1 Network Map Layout This section describes the Network Map's layout. Network view Shows the statuses of registered resources and the network links between them.
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. Local map The local map displays all resources contained in the selected resource, as well as their connections (network links) with other resources.
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. Clicking this button expands the resource contents.
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. stop The server was detected to have been powered off. Table 11.
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. fatal A fatal error was detected from the VM host, which is now unusable. stop The VM host was detected to have been powered off. Table 11.
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. fatal A fatal error was detected from the virtual switch, which is now unusable. stop The virtual switch was detected to have been powered off. Table 11.
Table 11.8 Firewall Icon Status Meaning normal No new errors or warnings were detected from the firewall. warning A warning was detected from the firewall. unknown The status of the firewall could not be obtained. error An error was detected from the firewall. fatal A fatal error was detected from the firewall, which is now unusable. stop The firewall was detected to have been powered off. Table 11.
Table 11.10 Integrated Network Device Icons Icon Status Meaning normal No new errors or warnings were detected from the integrated network device. warning A warning was detected from the integrated network device. unknown The status of the integrated network device could not be obtained. error An error was detected from the integrated network device. fatal A fatal error was detected from the integrated network device, which is now unusable.
Icon Meaning Server (*) LAN switch blade VM host VM guest Virtual switch LAN switch Firewall SLB Integrated network device Port * Note: When operating in IBP mode - 113 -
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". 11.4.3 Other Icons The following tables detail the icons displayed in the Network Map. Table 11.13 Admin Server Icon Icon Status Admin server Meaning Indicates the server used as the admin server. Table 11.
11.5.2 Link Statuses Link statuses are shown by adding colored outlines to displayed links (as described in "11.5.1 Link Display"). The following table shows display examples of abnormal link statuses. Table 11.16 Statuses of Physical or Virtual Links Link Meaning Represents a link with an error status (e.g. its opposite port or NIC is disabled, or the cable between this link and its opposite port or NIC is disconnected). Represents a link with a warning status.
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.
Resource descriptions The display filter area includes the following filters (checkboxes). Selecting or clearing a filter's checkbox will either show or hide the content associated with that filter. Physical links The display filter area includes the following filters (checkboxes). Disabling this filter will hide all physical links between resources on the network map. VLANs Only displayed when the VLAN tree is displayed. The display filter area includes the following filters (checkboxes).
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.
- EXT3 - EXT4 - LinuxSwap - The following conditions must be met for the managed server to collect the cloning image from and the managed server to deploy the cloning image to. - All server models must be identical. - The hardware configuration of each server must be identical, including optional cards, expansion boards, and the slots they are mounted in. - The same BIOS settings must have been made for all servers according to the procedure in "8.2.
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. - When the configurations of managed servers are as below, execute the following commands before collecting cloning images.
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. This has to be configured before collecting cloning images.
Format Parameter Value Specify the KMS host. When "MANUAL" is selected, make sure to set .cmd.remotescript. 1.params.kmsname. MAK Comm on .cmd.remotescript. 1.params.kmsname The host name (FQDN), computer name, or IP address of the KMS host. .cmd.remotescript. 1.params.kmsport KMS host port number. The default is 1688. .cmd.remotescript. 1.params.makkey (Mandatory) MAK key. .cmd.remotescript. 1.params.ieproxy Host name (FQDN) and the port number of the proxy server.
- 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: 1. Place the target server into maintenance mode. a.
New 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. Cloning images with the same name can be saved up until the maximum number of image versions.
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. - Destination servers should be of the same model as the source server.
- 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. Cancel any such settings before deploying a cloning image.
b. 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. [Windows] A string composed of up to 63 alphanumeric characters, underscores, ("_"), and hyphens, ("-"). The string cannot be composed solely of numbers.
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). Those names can be changed using the following procedure. 1. Double-click the [Server name after deployment] cell of a server.
4. 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. a. In the ROR console server resource tree, right-click the source server (or its physical OS) and select [Maintenance Mode][Release] from the popup menu. The [Release Maintenance Mode] dialog is displayed. b. Click . The target server is released from maintenance mode.
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] Tab". 12.5 Deleting This section explains how to delete a cloning image. Use the following procedure to delete cloning images: 1.
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. The power consumption data for each power monitoring target that is registered in the power monitoring environment can be exported in CSV format.
Target Resources Specify the power monitoring target to export the power consumption data of. Select the checkboxes of each desired target. More than one target can be selected. Data Type Specify the type of data to export. Check the checkbox of each desired data type. More than one data type can be selected. Output time span Select the time span for which to export data from the drop-down menu.
Rate Output time span Output device count Daily Last year 30 Monthly Select "Custom" and specify 5 years 60 Annual Select "Custom" and specify 5 years 60 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.
Target Resources Specify the power monitoring target name to display the power consumption data graph of. Select the checkboxes of each desired target. Up to 18 targets can be selected. Graph Settings Data Type Specify the type of data to display the graph. Specify either one of the following for the data type: - Power (Instantaneous power consumption) - Average power (Average power consumption during the selected time span) Output Time Span Select the time span for the data from the drop-down menu.
3. Click . After switching to the graph display window, the selected power consumption data can be displayed in line graphs. Figure 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.
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. A resource pool type is specified when creating a resource pool, and only resources of a specific type are stored in each type of resource pool.
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: 1. In the ROR console orchestration tree, right-click the target VM pool, and select [Register Resources] from the popup menu. The [Register Resources] dialog is displayed. 2.
- Creating network resources using already registered admin LAN subnets Refer to "14.3.2 Creating Network Resources Using Already Registered Admin LAN Subnets". The network resource for the admin LAN that is directly connected from the manager is automatically created with the values of "AdminLan" for the network resource name and "1" for the VLAN ID. To change these values, delete "AdminLan", and then create a new network resource following the procedure provided in "14.3.
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. When creating a network resource for the admin LAN, a network resource name, a VLAN ID, a subnet address, and a subnet mask must be entered. When creating a network resource for iSCSI boot, a network resource name, a VLAN ID, a subnet address, and a subnet mask must be entered.
- LAG 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. - Tagged VLAN Displays the Tagged VLAN information set in the external connection port, separated by commas (","). Make the settings for the external port as follows. a. Click in [VLAN ID/Uplink port settings] in the [Create a network resource] dialog. The [Uplink port settings] dialog is displayed. b.
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 Enter the subnet address and subnet mask to set using the "xxx.xxx.xxx.xxx" format. The maximum value for a subnet mask is 255.255.255.255 (32-bit mask) and the minimum value is 255.255.0.0 (16-bit mask). However, 255.255.255.254 cannot be specified.
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. 3. Click . The network resource is created and registered in a network pool. When checking the [Automatically configure VLANs for the uplink ports.
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: 1. Right-click the target network pool in the orchestration tree, and select [Register Resources] from the popup menu. The [Register Resources] dialog is displayed. 2. Check the [Select] checkbox for the resource to register. 3. Click . The network device is registered in the network pool as a resource.
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 "Virtual Storage Resources and Disk Resources for Physical L-Servers".
1. 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. 2. 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].
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.
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: 1. In the ROR console orchestration tree, right-click the target image pool, and select [Register Resources] from the popup menu. The [Register Resources] dialog is displayed. 2. Select a cloning image to register. 3. Click .
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. For details, refer to "15.1 Operations Using the Wizard GUI".
2. The registered information of L-Server templates is displayed. The L-Server template information and the buttons that will be displayed are shown below. Buttons button Click when creating an L-Server template. For details, refer to "15.1.2 Creating". button Click when importing an L-Server template. For details, refer to "15.1.7 Import". L-Server template List In each page of the list, 10 items can be displayed.
Server Name The L-Server name is displayed. Server Type The server type is displayed. For physical L-Servers, "Physical" is displayed. For virtual L-Servers, "VM" is displayed. Server Specifications When the server type is "Physical", the model name of the server is displayed. When the server type is "VM", the CPU frequency multiplied by the number of CPUs, and the memory size are displayed. Disk Capacity The disk capacity is displayed, in units of GB.
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" when creating a physical L-Server template. Server Specification Methods When Server Type is "Physical", the "Model", and "CPU and Memory" of the server are displayed. Click to select a model name to allocate to the L-Server.
- PRIMERGY TX300 S6 - PRIMERGY TX300 S5 - PRIMERGY TX300 S4 - PRIMEQUEST 1000 - Other PC servers Set the basic information, and click . b. Enter information on the CPU and memory. CPU Perf Select the CPU frequency. Enter a number between 0.1 and 10. CPU Num Enter the number of CPUs to be allocated to the L-Server. Enter a number between 1 and 240. Memory Size Enter the memory capacity to be allocated to the L-Server. Enter a number between 0.1 and 8192. Set the basic information, and click .
Click to add a NIC Group. Click to delete a NIC Group. NICs Select a NIC index to configure as the NIC redundancy group. Two NICs must be specified for the group. Enter the NIC information, and click . d. Enter the disk information. Disk Enter the disk capacity. Enter a number in the following range: 0.1 to 2048 Clicking adds a disk. Clicking deletes a disk. Up to 60 disk indexes can be added, in the range between 0 to 59.
FC connection pattern Specify the name of the pattern file for FC connections. The list of file names of pattern files for FC connections located under the directory in the manager environment is displayed as a pull-down menu. [Windows Manager] Installation_folder\SVROR\Manager\etc\customize_data\fc_connection_pattern [Linux Manager] /etc/opt/FJSVrcvmr/customize_data/fc_connection_pattern "" is selected when there is no FCConnectionPattern file. As for default, "" is selected.
VM type Select a VM type. The following VM types are displayed: - VMware - Hyper-V - RHEL-Xen - RHEL-KVM - Oracle VM - Solaris Containers Set the basic information, and click . b. Configure the overcommit function. When the VM type of basic information is one of following types, the functions can be configured. - VMware - Hyper-V - RHEL-KVM - Solaris Containers Overcommit Decide whether to use the Overcommit function. Select "true" when using the overcommit function.
CPU Share (Optional) Enter the relative proportion for allocation of CPU resources. It is possible to specify it for VMware. Enter when using the overcommit function. Enter an integer between 1 and 1000000. By default the value is set to number of CPUs * 1000 when an L-Server is created. CPU Allocation Priority (Optional) Enter CPU allocation priority. It is possible to specify it for Hyper-V. A number between 1 and 10000 can be specified. If left blank, "100" is set when creating an L-Server.
A number between 5 and 2000 can be specified. By default, "20" is set when enabling a dynamic memory when L-Server is created. Memory Weight (Optional) Specify the memory allocation priority. It is possible to specify it for Hyper-V. A number between 0 and 10000 can be specified. If left blank, "5000" is set when creating an L-Server. Startup RAM (Optional) Specify the amount of an initial memory. It is possible to specify it for Hyper-V. Enter a number between 0.1 and memory capacity.
Clicking adds a disk. Enter the disk number. [VMware] A number between 0 and 55 can be specified. [Hyper-V] [Oracle VM] A number between 0 and 59 can be specified. [Xen] A number between 0 and 251 can be specified. [RHEL-KVM] A number between 0 and 16 can be specified. [Solaris Containers] 0 can be specified. Enter the disk information and click . f. Enter the information on server redundancy, alive monitoring, boot location, and ServerImageLink.
When "all" is specified in the definition file for L-Server creation, priority is given to "all" even if this setting is not specified. g. Click . The dialog to confirm the entered information is displayed. When "Are you sure to create a new L-Server Template?" is displayed, confirm the content, and then click . See For the input ranges for the [Create L-Server Template] dialog, refer to "14.2.2 Virtual L-Server Templates" in the "Reference Guide (Command/XML) CE".
15.1.5 Deleting Use the following procedure to delete an L-Server template: 1. Select the ROR console orchestration tree, and select [File]-[L-Server Template]-[Edit] from the ROR console menu. The [ROR L-Server Template Editor] window is displayed. 2. Select an L-Server template to delete on the [ROR L-Server Template Editor] window, and click . 3. When "Are you sure you want to delete this Template?" is displayed, confirm the content, and then click .
15.1.8 Creating a Template using an Another Existing Template It is possible to create an L-Server using another L-Server template that has already been made. Use the following procedure to create an L-Server template from an L-Server: 1. Select the ROR console orchestration tree, and select [File]-[L-Server Template]-[Edit] from the ROR console menu. The [L-Server Template Editor] window is displayed. 2. Select the L-Server to save as an L-Server Template, and click .
From the command-line, execute rcxadm template export. For details on the rcxadm template export command, refer to "8.1 rcxadm template" in the "Reference Guide (Command/XML) CE". Note When exporting an L-Server template, the XML file is generated based on the XML specifications. 15.2.2 Editing This section explains how to edit an L-Server template. Edit the L-Server template exported in "15.2.1 Export" using the editor.
L-Server templates that are no longer required, including the sample template, can be deleted. Use the following method to delete an L-Server template: On the [Template List] tab, right-click the L-Server template to delete, and select [Delete] from the popup menu. From the command-line, execute rcxadm template delete. For details on the rcxadm template delete command, refer to "8.1 rcxadm template" in the "Reference Guide (Command/XML) CE".
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. - Creation Without Using an L-Server Template Specify a resource or a resource pool.
Information [Physical Servers] For details on physical L-Servers, refer to "B.5 Creating an L-Server" in the "Setup Guide CE". [VMware] For details on VMware, refer to "C.2 VMware" in the "Setup Guide CE". [Hyper-V] For details on Hyper-V, refer to "C.3 Hyper-V" in the "Setup Guide CE". [KVM] For details on RHEL-KVM, refer to "C.4 RHEL5-Xen" in the "Setup Guide CE". [Oracle VM] For details on Oracle VM, refer to "C.5 Oracle VM" in the "Setup Guide CE".
[Solaris Containers] 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 ("-"). Enter up to 63 characters beginning with an alphanumeric character (upper or lower case), and including alphanumeric characters (upper or lower case), underscores ("_"), periods ("."), and hyphens ("-"). However, names which start with "SUNW" cannot be used.
Information For virtual L-Servers, when creating an L-Server, even if the size of the system disk is specified in advance, if the specified size differs from that of the deployed cloning image, the size will be changed to that of the deployed cloning image. [VMware] [Hyper-V] Depending on the server virtualization software used, some restrictions may apply to the operating systems that parameters can be set for and the prerequisites for performing the settings.
Specify when not connecting network resources, only creating a configuration definition. Note The network (NIC) number corresponds to a NIC number (NICIndex) + 1 that is defined in L-Server templates. [Oracle VM] One or more networks must be specified. Label (Optional) A custom label can be defined for the L-Server. User-defined labels make it easier to identify the server. Enter a maximum of 32 characters. Comment (Optional) A custom comment can be defined for the L-Server.
- When the status of the VM host and virtual storage is one other than "normal", the resource will be excluded from L-Server allocation regardless of its available space. - When operating a VM host in a cluster system, create an L-Server with the storage resources shared between VM hosts specified. L-Server cannot be created using storage resources that are not shared between VM hosts. - Depending on the [None (Definition only)] checkbox, the power status of an L-Server after its creation is as follows.
Note Each item to set has an upper limit. Even when valid values are specified, the creation of an L-Server may fail depending on the availability of resources in resource pools and the hardware configuration. L-Servers cannot be created for physical servers that are in maintenance mode. Information - For the storage units that support the setting of LUN alias names, when disk resources are created with Resource Orchestrator, set the alias (if possible) based on the disk resource name in the LUN.
Server type Enter the type of server for the L-Server to be created. Select [Physical]. Image Specify a cloning image to deploy. a. Click
16.2.2 [Server] Tab Server Specification Methods Select a method to specify a server. Click to select a model name to allocate to the L-Server. Clicking enables you to enter the number of CPUs, CPU performance, and memory size of the server allocated to the L-Server. Note When is selected, you must enter the number of CPUs, the CPU performance, and the memory size. Number of CPUs Enter the number of server CPUs to allocate to the L-Server.
When creating an L-Server for which only a configuration definition has been created, a physical server not allocated to the LServer can be selected from the list. When the [Currently unusable] checkbox is checked, failed physical servers and physical servers that have inconsistencies in their admin LAN network configurations are displayed in the list.
When selecting the [HA] checkbox, the [Use a low spec server] checkbox of [Spare server specs], and
Indicates the settings for when the server starts FC path When installing an OS manually, check the [Single path mode] checkbox. When an image is not specified, it is automatically checked. After installing a multi-path driver on an OS, perform [17.2.1 Modifying Specifications], and clear the "Single path mode" checkbox. For details, refer to "B.5 Creating an L-Server" in the "Setup Guide CE". Boot Mode Specify the L-Server boot method.
- Number Clicking will display the [Disk Definitions] dialog, and then specify the number of disks to add. Specify a number 1 or larger. Resource type Specify the disk to allocate to the L-Server. Select from the following items. - Automatic assignment Select a suitable virtual storage resource from those registered in the appropriate storage pool. Create the specified size of disk resources, and allocate them to the L-Server. Set [Automatic] for the default value.
Allocated L-Server Specify an L-Server when sharing the disk resources. Disk name Specify the name of the disk to be found. - Begins with Specify when searching for disks whose names begin with the specified string. - Includes Specify when searching for disks whose names include the specified string. 16.2.4 [Network] Tab Specify the following items. NIC/Network Configure the network to connect with the NIC used in the L-Server. Clicking displays the [Add a Network] dialog.
Table 16.3 Correspondence Relationships of Network Information [Windows] OS Information IP address specified for network interface Information for L-Server Configuration Number of NICs Name of network interface (configured by a tenant administrator) (number of NICs on the back side of rack mount servers) IP Address 192.168.1.1 Local area connection 1 1 192.168.1.1 192.168.2.1 Local area connection 2 2 192.168.2.1 Table 16.
2. Set the items required in each tab, and click to create the L-Server. Note - Each item to set has an upper limit. Even when valid values are specified, the creation of an L-Server may fail depending on the availability of resources in resource pools, the hardware configuration, and the VM management software specifications. - When creating a virtual L-Server, if there are any values configured in the VM specific information definition file, those values are used.
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". Destination folder Select a resource folder or a tenant to store L-Servers. Template Specify [None] in the selection list. Server type Enter the type of server for the L-Server to be created. Select [VM]. When [VM] is selected for the server type, select the VM type on the [Server] tab.
Comment (Optional) Enter any comments for the L-Server. Enter a maximum of 256 characters. 16.3.2 [Server] Tab VM type Select the VM type for the L-Server to be created. It is not necessary to specify this when deploying an image, because the VM type of the image is used. Number of CPUs Enter the number of server CPUs to allocate to the L-Server. Enter an integer between 1 and 8. [Oracle VM] The range that can be entered differs depending on the OS type of VM guests.
[Oracle VM] Specify the size within the range of 0.3 to the_resource_size_of_the_hardware_on_which_the_VM_hosts_operate. [Solaris Containers] Specify the size within the range of 0.1 to the_resource_size_of_the_hardware_on_which_the_VM_hosts_operate. Memory Size Enter the memory capacity to allocate to the L-Server. Enter a number with up to one decimal place, in units of gigabytes. A number between 0.1 and 255 can be specified.
[KVM] Linux, Windows, and Linux (SELinux) can be selected. A personalized guest OS can only be selected for Linux. When creating a new guest VM, the information will be displayed. When information of a newly created VM guest is lost during backup and restoration, "unknown" may be displayed. [Oracle VM] The OS type cannot be changed. [Solaris Containers] The OS type cannot be changed. VM host (Optional) Individually specify the resources to allocate to the L-Server.
- If the [HA] checkbox is not selected The HA function will be preferentially located on a disabled VM host. However, the HA function will place a VM guest on an enabled VM host in the following cases: - The HA function is not located on a disabled VM host - There is no available CPU or memory - The status, power status, and maintenance mode of other VM hosts are not suitable. [Solaris Containers] - If the [HA] checkbox is selected It is located on a VM host with a spare server configured.
If you specify a resource folder name, one's own L-Server can be included in the resource folder.
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. For details on definition files, refer to "C.1 Definition Files Commonly Shared when Creating Virtual L-Servers" in the "Setup Guide CE". - Storage pool Select a virtual storage resource registered in the specified storage pool. Create the specified size of disk resources, and allocate them to the L-Server.
[VMware] 0 to 10 [Hyper-V] 0 to 8 [Xen] 0 to 15 [KVM] 0 to 8 [Oracle VM] 1 to 8 [Solaris Containers] 0 to 8 IP address (Optional) Specify the IP address to allocate to the L-Server. To manually specify the IP address to allocate to the L-Server, enter the IP address. 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.
OS Property Definition File By setting the default values in an OS property definition file in advance, the default values of the information on the [OS] tab, etc. are generated when creating an L-Server. Use the UTF-8 character code for OS property definition files. Use the OS property definition file for VM products. It is necessary to indicate the required parameters between VM management software in the definition files.
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 LServer Virtual L-Server Starting an L-Server Yes Yes Refer to "17.1.1 Starting an L-Server". Stopping an L-Server Yes Yes For details, refer to "17.1.2 Stopping an LServer". Restarting an L-Server Yes Yes Refer to "17.1.3 Restarting an L-Server".
Operation Physical LServer Virtual L-Server Reference Moving L-Servers between VM hosts (migration) No Yes Refer to "17.7 Migration of VM Hosts between Servers". Allocating resources to L-Servers Yes Yes Refer to "17.8.2.1 Allocating Resources". Releasing resources from L-Servers Yes Yes For details, refer to "17.8.2.2 Releasing Resources". Changing physical server usage Yes No Refer to "17.9 Changing Physical Server Usage". *1: Only possible when using SAN boot.
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.
1. Right-click the target L-Server in the orchestration tree, and select [Power]-[Reboot] from the popup menu. The confirmation dialog is displayed. 2. Click . The L-Server is restarted. Use the following procedure to restart forcibly: 1. Right-click the target L-Server in the orchestration tree, and select [Power]-[Reboot (Forced)] from the popup menu. The confirmation dialog is displayed. 2. Click . The L-Server is restarted forcibly. From the command-line, execute rcxadm lserver restart.
When the following conditions are met on an L-Server with a configuration definition already been created (defined), the L-Server will not be the target of powering on. - The cloning image is specified - Boot disks (system volumes) are dynamically created from virtual storage - The L-Server is a virtual L-Server on RHEL-KVM When an L-Server uses resources in another tenant, the L-Server will not be the target of powering on. From the command-line, execute rcxadm folder start.
Point - Resource Orchestrator makes periodic queries to VM management software. - When the configuration of a virtual machine is modified using VM management software, periodic queries will reflect the changes on the virtual machines used by a virtual L-Server. - When addition, modification, or deletion of storage is performed using VM management software, changes to the configuration/ status of storage of the virtual L-Server are detected.
*3: When using VMware, the value to be reflected varies depending on the memory limit settings. When Unlimited is set for the memory limit, the specified memory size is reflected. When a particular value is specified for memory limit, that value is reflected. When using Hyper-V, the value to be reflected varies depending on the dynamic memory settings. When dynamic memory is enabled, the setting for the maximum memory is reflected.
2. Change the values. The current values for each item are displayed in the [Modify an L-Server] dialog. Items that have been changed are indicated with an asterisk ("*") in front of the item. 3. Click . When making changes while the power of the virtual L-Server is on, only the configuration of the virtual L-Server can be changed. 4.
- VMware - Hyper-V - KVM The items that can be changed depend on the type of VM product and the settings. Refer to "Table 17.2 Items that can be changed while the power is on" for details. Table 17.
Note Immediately after a snapshot is restored, there may be differences between the configuration of VM guests managed by L-Server and those managed by VM management software. 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".
Prerequisites - For physical L-Servers, attachment and detachment of disks is only possible when using SAN boot. - [Solaris Containers] Attaching and detaching of disks is not possible from the ROR console. However, it is possible from the global zone. Attaching a Disk Use the following procedure to attach a disk to an L-Server: 1. Right-click the target L-Server in the orchestration tree, and select [Change Settings]-[Attach Disk] from the popup menu. The [Attach a New Disk] dialog is displayed. 2.
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. Allocation status Specify the status for the disk to allocate to the L-Server. - Unallocated Specify when selecting a disk resource which is not allocated to another L-Server. - Allocated Specify when selecting a disk resource which is allocated to another L-Server.
- Saved disk resources which are created from virtual storage can only be attached to virtual L-Servers on Hyper-V when using Microsoft(R) System Center 2012 Virtual Machine Manager. - The only disk resources that can be attached to a virtual L-Server on Hyper-V are disk resources that are not used for other virtual LServers. - Saved disk resources cannot be attached to virtual L-Servers on Hyper-V from which snapshots have been collected when using Microsoft(R) System Center 2012 Virtual Machine Manager.
Note - When using RHEL-KVM virtual L-Servers, the L-Server must be powered off in order to detach a disk. - When using a virtual L-Server on something other than RHEL-KVM, and when detaching a disk resource virtual L-Server on HyperV, the content of the detached disk is deleted. After checking the advisory notes in the displayed dialog, check the [Detach disks.] checkbox. - If disks are detached while the server is powered on, it is necessary to change the status of the disk into unused in advance.
- When changed to use a device path other than the following: - SCSI:0:0 - SCSI:0:6 - SCSI:0:8 - SCSI:0:14 - SCSI:1:0 - SCSI:1:6 - SCSI:1:8 - SCSI:1:14 AM - SCSI:2:0 - SCSI:2:6 - SCSI:2:8 - SCSI:2:14 AM - SCSI:3:0 - SCSI:3:6 - SCSI:3:8 - SCSI:3:14 AM - When changed to use Raw Device Mapping [Hyper-V] - When changed to use a device path other than the following: - IDE:0:0 - SCSI:0:1 - SCSI:0:14 - SCSI:1:0 - SCSI:1:14 AM - SCSI:2:0 - SCSI:2:14 AM - SCSI:3:0 - SCSI:3:14 AM - When changed to use a path through
Prerequisites - Sharing of disks is possible when the managed servers and storage are shared using Fibre Channel connections. - First disk (System Volume) cannot be shared between L-Servers. - Control of simultaneous access to shared disks is performed by other applications, such as cluster systems. - Disk sharing between L-Servers is only possible for physical L-Servers that are use SAN boot.
Table 17.
When the L-Server status is "defined" 1. Right-click the target L-Server in the orchestration tree, and select [Change Settings]-[Definition] from the popup menu. The [Modify L-Server's definition] dialog is displayed. 2. Use the [Network] tab to change network resource settings of the L-Server. Information - For Physical L-Servers For details on operation of the [Network] tab, refer to "16.2.4 [Network] Tab". - For Virtual L-Servers For details on operation of the [Network] tab, refer to "16.3.
Untagged VLAN Select whether or not to use untagged VLAN for a NIC or a NIC group. 3. Click . From the command-line, execute rcxadm lserver modify. For details on the rcxadm lserver modify command, refer to "3.6 rcxadm lserver" in the "Reference Guide (Command/XML) CE". For Virtual L-Servers Use the rcxadm lserver attach and detach commands for adding and deleting NICs. For details on the rcxadm lserver attach command, refer to "3.6 rcxadm lserver" in the "Reference Guide (Command/XML) CE". 17.
[VMware] Normally, the admin server notifies the admin client of the IP address of the admin LAN of the VM host registered with the admin server to use as the connection destination for the console. For this reason, the console cannot be connected to by admin clients that exist on networks that are not connected to the admin LAN.
4. After performing the configuration, close the web browser. Log in to Resource Orchestrator again using a web browser, and the console screen can then be started from the ROR console. - In cases where the following VM products are used for a virtual L-Server, starting the ROR console turns the L-Server "ON" when the selected L-Server was "OFF". - VMware vSphere 4.0 - VMware vSphere 4.
17.5.1 Collecting and Registering This section explains how to collect cloning images. Use the following methods to collect cloning images: - Collect cloning images from L-Servers with an OS installed - Collect Cloning Images from Templates of Server Virtualization Software - Register the server management software (BMC BladeLogic Server Automation) package Note For physical L-Servers, agents must be registered before collecting cloning images. For details, refer to "B.
Comment (Optional) Enter a comment that identifies the cloning image. Up to 128 characters other than percent signs ("%"), back slashes ("\"), double quotes ("), and line feed characters can be specified. 3. Click . Cloning images are stored in image pools. When is clicked in the Recent Operations area, the confirmation dialog to quit the process is displayed. From the command-line, execute rcxadm image create. For details on the rcxadm image create command, refer to "4.
[VMware] For details on how to collect cloning images on VMware, refer to "Collecting a Cloning Image" in "C.2.8 Collecting Cloning Images" in the "Setup Guide CE". [Hyper-V] For details on how to collect cloning images on Hyper-V, refer to "Collecting Cloning Images" of "C.3.8 Collecting and Deleting Cloning Images" in the "Setup Guide CE". [Xen] For details on how to collect cloning images on RHEL5-Xen, refer to step 3 in "C.4.6 Creating an L-Server" in the "Setup Guide CE".
[Oracle VM] When an Oracle VM image is selected in the Orchestration tree to display the [Resource Details] tab, the [OS] under [Image Information] is not displayed. From the command-line, execute rcxadm image list. For details on the rcxadm image list command, refer to "4.1 rcxadm image" in the "Reference Guide (Command/XML) CE". 17.5.3 Unregistration This section explains how to unregister cloning images. Use the following procedure to unregister cloning images. 1.
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". Note [Hyper-V] For details on how to delete cloning images on Hyper-V, refer to "C.3.8 Collecting and Deleting Cloning Images" in the "Setup Guide CE". 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.
Note If the OS of the L-Server is Linux, the user name and password used when collecting the snapshot will be saved. It is recommended to change the password after collecting a snapshot to maintain security. [VMware] CPU reservation performance and memory reservation capacity are not restored. Changing this value may prevent an L-Server from starting, depending on the amount of resources used by other VM guests on the same VM host.
Collection This section explains how to collect a snapshot. 1. Right-click the target L-Server in the orchestration tree, and select [Snapshot]-[Collect] from the popup menu. The [Create a Snapshot] dialog is displayed. 2. Enter the following items: Comments Enter a comment that identifies the snapshot. Up to 128 characters other than percent signs ("%"), back slashes ("\"), double quotes ("), and line feed characters can be specified. The snapshot is collected. 3. Click .
3. Click . 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.6.2 Backup and Restore This section explains how to back up and restore L-Servers. These functions are only provided for physical L-Servers. Backup and restore of L-Servers is the function for performing backup and restoration of L-Server system images.
From the command-line, execute rcxadm image restore. For details on the rcxadm image restore command, refer to "4.1 rcxadm image" in the "Reference Guide (Command/XML) CE". Delete This section explains how to delete unnecessary versions of backups of system images. 1. Right-click the target L-Server in the orchestration tree, and select [Backup/Restore]-[Delete a Backup] from the popup menu. The [Delete a System Image] dialog is displayed. 2. Select the version of the backup to delete. 3. Click .
- When [VM Pool] is specified for [Resource type] The migration is performed with a destination VM host selected from a VM pool. For environments using overcommit, the same overcommit settings must be configured for both the L-Server and VM pools. - When [VM Host] is specified for [Resource type] The migration will fail because the destination does not exist.
- Automatically release server resources for L-Servers If releasing server resources when the L-Server is turned off, set [Resource release] during L-Server creation. For details, refer to "16.2.2 [Server] Tab" and "16.3.2 [Server] Tab". When the power of an L-Server for which this setting is configured is turned off, "[preserved]" is displayed.
17.8.1 Installation By setting the values in the following definition file in advance, it is possible to change L-Server related behaviors and default values displayed on the [General] tab and [Server] tab when creating an L-Server. For the values available for L-Server templates, when an L-Server template does not have values configured, the values of the definition file are adopted.
Item Key Value Remarks For details on numbering, refer to "Association of an L-Server Name with a VM Guest Name" in "16.1 Creation Using an L-Server Template". - When using the same name for both a virtual L-Server and a VM when not using numbering Specify "false". If left blank, "true" is set. Switching the value for this item does not automatically change existing virtual L-Server names or VM names.
1. Right-click the target L-Server in the orchestration tree, and select [Change Settings]-[Definition] from the popup menu. The [Modify L-Server's definition] dialog is displayed. 2. Change the items to modify. For details on setting values in the [Modify L-Server's definition] dialog, refer to "Chapter 16 Creating L-Servers". 3. Click . The L-Server configuration definition information is modified. From the command-line, execute rcxadm lserver modify.
1. Create and Register Each Resource Create and register each resource. Perform resource creation and registration, referring to "Chapter 5 Registering Resources" and "Chapter 14 Registering Resources in Resource Pools". 2. Create an L-Server Create an L-Server for which only the configuration definition (defined) is created, referring to "Chapter 16 Creating L-Servers". Perform the following configuration: - Set [Deploy] for image deployment from the select a cloning image section of the [General] tab.
2. Create an L-Server (First server) Create an L-Server for which resources are already allocated (allocated), referring to "Chapter 16 Creating L-Servers". Perform the following configuration: - Set [Deploy] for image deployment from the select a cloning image section of the [General] tab. - Do not check the [None (Definition only)] checkbox from the [General] tab. - Check the [Automatic (when powered off)] checkbox of [Resource release] on the [Server] tab. 3.
Operation The methods for operating physical servers after usage changes are as follow. Perform the procedure before performing any operations. - When using multiple L-Servers, switching between them, on a single physical server Usage can be changed by repeating the following procedure. 1. Confirm the Physical Servers to Use 2. Stop the Source L-Server for Usage Change Stop L-Servers operating on physical servers which are required for change usage. For details, refer to "17.1.2 Stopping an L-Server". 3.
Point - Usage cannot be changed, while the L-Server is stopped temporarily during L-Server restart. - When power operation has been performed directly on the physical server using the ROR console or commands, without performing power operation of the L-Server, the L-Server which was last operated will start. - If the last L-Server that was operated has already been started on another physical server, its status will change so there is no boot disk and it will fail to start. 17.9.
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" in the "Operation Guide CE". 18.
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. For details on roles and available operations, refer to "5.1.2 Roles and Available Operations" in the "Design Guide CE".
Type of L-Server L-Server Function Physical Server Using VIOM Physical Server Using HBA address rename Other Physical Servers Disaster Recovery No No No Deletion Yes Yes Yes Releasing an L-Server Yes Yes Yes *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.
In the following cases, the "L-Server for Server/Storage Management" is used. - When using storage listed in "18.3.
- Has 2 HBA ports on the server. - An agent has been registered. Note - When not using VIOM or HBA address rename, disk information of connected SAN disks is not displayed. - When importing an L-Server into an L-Platform in an environment where an admin LAN with multiple subnets has been configured, before linking to the L-Server, create an admin LAN network resource with the subnet addresses including the IP address of the admin LAN for the physical server. 18.3.
- SCSI:3:0 - SCSI:3:6 - SCSI:3:8 - SCSI:3:14 AM Note When using Raw Device Mapping, or when using a device path other than those listed above, only servers can be managed. For disks using any other device path, assign 56 or higher as the disk number. When collecting a cloning image for deploying an L-Server, use SCSI:0:0 for the system disk.
Note If "2.4.2.2 Required Software" in the "Design Guide CE" is not installed, a new L-Server cannot be deployed on that VM host. When using VMware, the virtual machine on a VM host which is not managed with VM management software can be linked to an LServer. Power operations (starting up, stopping, and restarting) and modification of basic information (label/comments) can be performed for the L-Server.
When the IP address used for a configured physical server, a virtual machine, or other devices is included in the subnet address scope, specify the IP address in the "IP addresses to be excluded". When linking a configured virtual machine to an L-Server, perform the following procedure to register a resource in a resource pool. a. Register VM host resources in a VM pool. b. Register the virtual storage and disks that are used for a virtual machine to be linked with the L-Server in a storage pool. c.
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 ("-"). Destination folder Select a resource folder or a tenant to store L-Servers. If omitted, the L-Server is stored in the root folder of the user that executed the operation. Label (Optional) Enter a label for the L-Server. Enter a maximum of 32 characters. Comment (Optional) Enter any comments for the L-Server.
3. Click . The virtual machine becomes manageable as a virtual 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". Note When operating an admin server on a virtual machine on VMware or Hyper-V environment, do not link that virtual machine to an LServer. VMware FT secondary virtual machines cannot be linked with L-Servers.
From the command-line, execute rcxadm lserver revert. For details on the rcxadm lserver revert command, refer to "3.6 rcxadm lserver" in the "Reference Guide (Command/XML) CE". However, for L-Servers created using Resource Orchestrator, the link between the L-Server and a physical server or virtual machine cannot be reverted.
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: 1. Right-click the target resource pool in the orchestration tree, and select [Register Resources] from the popup menu. The [Register Resources] dialog is displayed. 2. When a resource to register is a disk resource, click in the search condition area.
Move individual resources Use the following procedure to move a resource to another resource pool. 1. 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. 2. For "Destination Pool", select the destination resource pool. 3. Click . The target resource is moved to the selected resource pool.
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.
- 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.
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.
- 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. This item is displayed only when "VM Pool" or "Storage Pool" is selected for [Type].
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. 20.4 Moving Use the following procedure to move a resource pool to another resource folder. 1. Right-click the target resource pool in the orchestration tree, and select [Move to Folder] from the popup menu. The [Move a Pool] dialog is displayed. 2.
For the already allocated resources, the following information is displayed, depending on the status of resource allocation. - allocated Resource name - preserved Resource name + "(preserved)" - defined "(defined)" For resources in use, the resources configured as [Physical server] or [VM host] are displayed as icon + resource name.
- The maintenance mode of server virtualization software has not been set. [VMware] - For VM hosts for which standby mode has been set by server virtualization software, calculation results are displayed for free space even when the status is "stop". In Resource Details for the VM host, and when using the command (rcxadm pool list -name Resource_pool_name), the total CPU capacity is displayed in the format of CPU_performance * CPU_core_count.
- When the number of disks specified for an L-Server template is 2 or larger, or something other than the above 0 is displayed. [Hyper-V] As the saved disk resources that are created from the virtual machine cannot be used as system disks, the number is 0, even if the L-Server is unused.
Free CPU capacity and memory size are calculated based on the CPU performance and initial memory size reserved for the LServer template. - When Dynamic Memory is Disabled Free CPU capacity/memory size are calculated based on the CPU performance/memory size reserved for the virtual machine. The number of L-Servers that can be created is calculated based on the CPU reservation performance and memory capacity specified in the L-Server template.
- When the policy is slots *6: This includes not only the resources for active L-Servers, but also those of resources of stopped L-Servers. *7: Images include cloning images and snapshots. However, the size of images is not displayed. [Xen] When using RHEL5-Xen on the managed server, refer to "C.4.7 Advisory Notes for RHEL5-Xen Usage" in the "Setup Guide CE". *8) [VMware] This does not include the overhead memory allocated when creating a virtual machine from an L-Server template.
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. Using hierarchical folders, other resource folders can be stored in the resource folders.
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.
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.
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. If you select the [Resource Details] tab, detailed information for the resource folder is displayed.
3. Click . 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) 1. Right-click the target resource folder in the server tree, and select [Delete] from the popup menu. The [Delete a Folder] dialog is displayed. 2. Click . The target resource folder is deleted. From the command-line, execute rcxadm folder delete.
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.
- OFF Indicates that maintenance mode is released. See 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.
# /opt/FJSVrcvmr/bin/rcxadm netdevice set -name nd01 -attr auto_conf=true - When an infrastructure administrator is excluding the network device from auto-configuration # /opt/FJSVrcvmr/bin/rcxadm netdevice set -name nd01 -attr auto_conf=false You can confirm either of the following operations if the network device is the target of auto-configuration. - From the GUI: 1. Select the target network device in the network device tree. 2. Select the [Resource Details] tab. 3.
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: 1.
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". A.1 ROR Console This section explains how the [Resource] tab of the ROR console is organized.
- 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". Tree Panel By switching between tree types, it is possible to select from the following 7 types of trees. If resource folders have been created in the server tree, these resource folders are also displayed.
- 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 Manages and operates L-Servers and resource pools. All resources authorized for access by the logged in user are displayed.
- [Recovery Settings] Tab Displays information on the spare servers assigned to the resource selected in the resource tree. - [Image List] Tab Displays system and cloning image information. - [Network Map] Tab Displays a network diagram of registered resources. - Available Pool A list of resource pools available for use is displayed. The resource pools displayed are restricted according to the role and scope of access of the user. - Template List A list of registered L-Server templates is displayed.
Menu Items Function Menu Submenu Download Template Downloads a sample of the system configuration file (CSV format) for pre-configuration. Import Imports an L-Server template. Export Exports an L-Server template. Edit Creates and edits an L-Server template. Chassis Exports environmental data collected from chassis. Server Exports environmental data collected from servers. Power Monitoring Devices Exports environmental data collected from power monitoring devices.
Menu Items Function Menu Submenu HBA address rename settings (*3) Modifies the HBA address rename settings of a server. Network Settings (*4, *5) Modifies the network settings of a LAN switch. Global pool Modifies the global pool information for the tenant. Spare Server Settings (*6) Modifies a server's recovery settings. Monitoring Settings Modifies the monitoring information for a server. WWN Settings (*7) Modifies the WWN settings for a server.
Menu Items Function Menu Submenu Restore LAN Switch (*8) Restores a LAN switch configuration. Set Places a server into maintenance mode. Release Sets a server to active mode. Backup Backs up a system image from a server. Restore Restores a system image to a server. Delete Deletes backup system images. Collect Collects a snapshot of the L-Server. Restore Restores a snapshot to the L-Server. Delete Deletes a snapshot. Collect Collects a cloning image from a server.
Table A.1 Popup Menus Available for the "Server Resources" Tree Node Popup Menu Function Menu Register Submenu Chassis Registers a chassis. Server Registers a server. PRIMEQUEST Registers the chassis of a PRIMEQUEST. Environmental Data (Chassis) Exports environmental data collected from chassis. Environmental Data (Servers) Exports environmental data collected from servers. Folder Creates a resource folder. Export Create Table A.
Popup Menu Function Menu Submenu Reboot (Forced) Reboots a server without shutting down its operating system. ON Turns the maintenance LED on. OFF Turns the maintenance LED off. Hardware Maintenance Re-configure Detects and re-configures the properties of a replaced server. Backup/Restore Restore Restores a system image to a server. Cloning Deploy Deploys a cloning image to a server. Console Screen (*5) - Opens the server console.
Popup Menu Function Menu Submenu Switchover Switches over a server with one of its spare servers. Failback Switches back a server to its pre-switchover state. Takeover Accepts a switched over configuration as final (without switching back to the original configuration). Maintenance Mode (*1, *4) Set Places a server into maintenance mode. Release Sets a server to active mode. Backup/Restore (*1, *4) Backup Backs up a system image from a server. Restore Restores a system image to a server.
Popup Menu Function Menu Spare Server Submenu OFF (Forced) Powers off a SPARC Enterprise server without shutting down its operating system. Reboot Reboots a SPARC Enterprise server after shutting down its operating system. Reboot (Forced) Reboots a SPARC Enterprise server without shutting down its operating system. Switchover Switches over a server with one of its spare servers. Failback Switches back a server to its pre-switchover state.
Note If ServerView Deployment Manager is used on the admin LAN, the popup menu for cloning images cannot be used. Table A.9 Popup Menus Available for Network Devices Popup Menu Function Menu Submenu Discover LAN switches Discovers LAN switches within the admin LAN. Detect physical links Acquires physical link data from registered LAN switches. Topology Table A.
Popup Menu Function Menu Submenu Update - Updates management software information. Modify Registration Settings Modifies registration settings for management software. Table A.14 Popup Menus Available for Network Devices Popup Menu Function Menu Submenu Unregister - Deregisters the selected network devices from a resource pool. Update - Obtains and updates the information on the selected network devices. Move Resources - Moves the selected network devices to another resource pool.
Table A.17 Popup Menus Available for Network Pools Popup Menu Function Menu Register Resources Submenu - Registers a resource to the selected resource pool. New Create a network resource. Create Network Resource Using existing admin LAN subnet Creates a network resource from a registered admin LAN subnet as an admin LAN. Delete - Deletes the specified network pool. Change Settings Basic Information Modifies a network pool's registration settings.
Popup Menu Function Menu Submenu Change Settings Basic Information Modifies a tenant's registration settings. Move to Folder - Moves the specified tenant and all resources registered there. ON Powers on all L-Servers in a resource folder. OFF Powers off all L-Servers in a resource folder. Reboot Reboots all L-Servers in a resource folder. Power Table A.21 Popup Menus Available for L-Platforms Popup Menu Function Menu Move to Folder Submenu - Moves an L-Platform to another folder. Table A.
Popup Menu Function Menu Install VM Tool Revert Submenu - Connects the ISO images for installing VMware Tools to an L-Server. - Cancels the link between an L-Server and a physical server or virtual machine. Only the L-Servers that were created by linking are displayed. Table A.23 Popup Menus Available for VM Hosts Popup Menu Function Menu Submenu Unregister - Unregisters the selected resource from a resource pool. Update - Updates a resource.
Popup Menu Function Menu Submenu Update - Updates a resource. Change Settings Basic Information Modifies the selected resource's registration settings. Move Resources - Moves a resource to another resource pool. Start Management Software Console - Opens a management console. The following menus are displayed from the disk list displayed when selecting a storage pool. Table A.
Table A.31 Popup Menus Available for Address Sets Popup Menu Function Menu Submenu Delete - Deletes the specified network resource. Move Resources - Moves a resource to another resource pool. The following menus are displayed when selected from the orchestration tree. Table A.32 Popup Menus Available for Cloning Images Popup Menu Function Menu Submenu Unregister - Unregisters the selected resource from a resource pool. Update - Updates a resource.
Table A.35 Monitor Status List Monitoring Status Background Color Details Corrective action Monitoring events Grey This indicates a normal state. No warning or error-level events have occurred on the displayed resources. No action is necessary. Warning event detected Yellow This indicates a warning state. A warning-level event has occurred on one or more of the displayed resources. Click the status monitoring area to stop the blinking and fix the cause of the problem.
Resource Orchestrator detects server blades takes precedence. Resources displayed in the resource tree are represented by an icon and their resource name. For details on the icons used to indicate different resources, refer to "11.2 Resource Status" in the "Operation Guide CE". For a non-registered resource, one of the following registration states is displayed at the end of the resource's name. Table A.
Management Software Management software (vCenter Server, SCVMM, and VIOM) used in coordination with Resource Orchestrator is displayed in a tree view. For details on the icons used to indicate different management software, refer to "11.2 Resource Status" in the "Operation Guide CE". Clicking a management software on the tree displays information related to it in the Main Panel. Right-clicking a management software will display a list of available operations in a popup menu.
An L-Server can be created using an L-Server template. Sorting the Resources in the Tree The tree displays the resources in ascending order of name, by resource type. To sort the resource list within the same type of resource, use the following method. Storage Location of the Definition File [Windows Manager] Installation_folder\SVROR\Manager\etc\customize_data [Linux Manager] /etc/opt/FJSVrcvmr/customize_data Definition File Name gui_config.
Network Devices Information on the selected network device is displayed. Unregistered Server Information on the selected unregistered server. Network Resources Information on all registered network resources is displayed. Power Monitoring Devices Information on all registered power monitoring devices. Management Software Information on all registered management software. Management Software (vCenter Server, SCVMM, OVM Manager, or VIOM) Information on the selected management software.
Address Pool Information on all registered address sets is displayed. Image Pool Information on all registered cloning images is displayed. Cloning Image Information on the selected cloning image is displayed. Double-clicking a resource in the [Resource List] tab displays its [Resource Details] tab in the Main Panel. This tab shows detailed information on the selected resource. In the [Resource List] tab, resources experiencing problems are shown with a status icon displayed on top of their resource icon.
- Image Pool Note For items that there is no content to display the details for, a hyphen ("-") is displayed. Selecting a blade server displays the following chassis image in the [Resource Details] tab. This image shows the slot positions of all server blades installed in the chassis. Figure A.5 Chassis The resource images shown in the above chassis image are explained in the table below. Table A.38 Meaning of the Resources Shown in the Chassis Image Image Meaning A. Registered server blade. B.
Server blades The number of server blades mounted in the chassis is displayed. Displayed only when the chassis of a blade server is selected. Partition count The number of mounted partitions is displayed. Displayed only when the chassis of a PRIMEQUEST or SPARC Enterprise M4000/M5000/M8000/M9000 server is selected. LAN Switch blades The number of LAN switches mounted in the chassis is displayed. Displayed only when the chassis of a blade server is selected. See Refer to "11.
A.6.2 Server Attributes General Area Physical server name The name used to identify a server is displayed. Model name The model name of the server is displayed. When the server has been registered as a managed server and powered on, the server model name obtained from ServerView Operations Manager is displayed. For other servers, no model name is displayed. Product name The product name of the server is displayed. For PRIMERGY BX servers, the product name obtained from the management blade is displayed.
Memory Size The total capacity of server memory is displayed. This attribute is displayed as "-" for servers other than PRIMERGY BX servers or SPARC Enterprise M servers. For SPARC Enterprise M4000/M5000/M8000/M9000 servers, this is displayed only when the server is powered on. 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 Enterprise servers are selected.
Network Properties Area Physical Connections The list of physical connections between the server's network interfaces and LAN switch ports is displayed. When a column heading in the list is clicked, the color of the selected column will change and the resources can be sorted in either ascending or descending order. Hardware Maintenance Area NIC Summary The MAC addresses and IP addresses of each server are displayed.
Admin LAN (IP Address) The IP address on the admin LAN is displayed. Not displayed for VM guests. Status The status of the physical OS, VM host, or VM guest is displayed. Type The type of the OS running on the server is displayed. One of the following is displayed: - Physical OS - VM Host - VM Guest OS The type of the OS running on the server is displayed. Physical server name The name of the server on which the physical OS, VM host, or VM guest is operating is displayed. Not displayed for VM guests.
VM Guest Information Area The following information is displayed only for VM guests. VM type The type of the VM is displayed. VM host name The name of the VM host on which the VM guest is stored is displayed. VM name The name of the VM is displayed. VM management software The link to the web interface of a server virtualization software is displayed. Hardware Details Area The following information is not displayed for VM guests.
Network switchover Shows whether network settings will be automatically adjusted during server switchover. Force spare server to power off during switchover The setting whether the spare server is turned off forcibly when switching over to the spare server is displayed. Switch over to spare server running VM guests The setting whether the server is switched to a VM host on which a VM guest exists is displayed.
- The corresponding LAN switch port has not been assigned to a port group Monitoring Information Timeout(sec) The time-out value (in seconds) for ping monitoring is displayed. Recovery method The recovery performed when an error is detected is displayed. Number of reboots The number of times reboot is performed during recovery is displayed. WWN Settings Area The following information is not displayed for VM guests or servers other than SPARC Enterprise servers.
IP address The IP address on the admin LAN is displayed. Device name (Product name) The product name of the network device is displayed. For NS appliances, "NSAppliance" is displayed. Model The model name of a network device is displayed. For NS appliances, "NSAppliance" is displayed. 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.
Auto configuration Displays whether the network device is set to be automatically set or not. - true - false Redundant Configuration The following attributes are not displayed for PRIMERGY BX900/BX400 LAN switch blades operating in IBP mode. Group ID The group ID is displayed. Network Devices Another device in the redundancy configuration is displayed. When there are multiple devices, the names of those devices are displayed separated by commas (",").
Link aggregation information The following information is only displayed when LAN switch blades (*) are selected. Link aggregation group name The name of the link aggregation group to which the port of the selected LAN switch blade belongs is displayed. Port name The link aggregation port name is displayed.
ruleset Name (Label) The name of the ruleset is displayed. This is only displayed when the type of a network device is "Firewall" or "SLB". Description A description of the ruleset is displayed. Login Information Area Tenant Displays the name of the tenant that can be used as login information for the network device. If the network device type is "L2-Switch", a hyphen ("-") is displayed. IP address The IP address which the network device logs into is displayed.
Monitoring interval (sec) Displays the monitoring interval (in seconds) for the network device. Retry count Displays the number of retries when monitoring of the network device fails (no response before timeout). Timeout(sec) Displays the time (in seconds) a response is waited for before it is determined monitoring of the network device has failed. A.6.5 Power Monitoring Devices (PDU or UPS) Attributes General Area Device name The name used to identify a PDU or UPS is displayed.
A.6.6 Management Software Attributes General Area Management software name The name used to identify the management software is displayed. Type The type of the management software is displayed. One of the following is displayed: - vCenter Server - SCVMM - OVM Manager - VIOM IP address The IP address used to connect to the management software is displayed. Status The status of the management software is displayed. Management software A link to the web interface of the management software is displayed. A.6.
User ID The user name of the storage management software is displayed. Management software A link to the management software for the storage management software is displayed. Physical Storage Unit List Name (Label) The name of the storage unit is displayed. Model The model name of the storage unit is displayed. Storage Management Software The storage management software for the storage unit is displayed. A.6.8 Storage Unit Attributes General Area Name (Label) The name of the resource is displayed.
Storage Management Software The storage management software for the virtual storage is displayed. Physical Storage Unit The storage unit for the virtual storage is displayed. A.6.9 VM Management Software Attributes General Area Name (Label) The name of the resource is displayed. Resource Type The resource type of the virtual storage is displayed. Label The label is displayed. Comments Comments set for the resource are displayed.
Storage Management Software The storage management software for the virtual storage is displayed. Physical Storage Unit The storage unit for the virtual storage is displayed. A.6.10 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.
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. Tenant/L-Platform/Folder List Name (Label) The name used to identify a tenant is displayed. Type The type of a tenant is displayed. Stored Resource Number The number of stored resources is displayed. Pool List Name (Label) The name used to identify the resource pool is displayed. Type The type of the resource pool is displayed.
- 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. The name is followed by "(preserved)". - When only the configuration definitions have already been created (defined) "(defined)" is displayed.
A.6.12 L-Server 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. Server Information(Server Specification) Name The name of the L-Server template used for the L-Server is displayed. CPU performance The CPU performance defined for the L-Server is displayed.
Note [Solaris Containers] The number of CPUs is displayed based on a cap value when a resource pool used in non-global zone is changed from unmanaged to managed.
- When PXE boot is not configured "Disable" is displayed. Server Properties (VM Management Software Specific Information) CPU Reserve The minimum size of CPU resources (minimum reserved value) to be allocated for the VM guest is displayed. CPU Share The relative proportion of CPU resources to be allocated when CPU resources run out is displayed. Memory Reserved The minimum size of memory resources (minimum reserved value) to be allocated for the VM guest is displayed.
Boot Location The L-Server's physical location change status is displayed. Releasing Resources Resource release settings are displayed. - When Repurpose is Configured "on" is displayed. - When Repurpose is not Configured "off" is displayed. Current resource The information set for "Physical server" or "VM host" during L-Server creation is displayed. - When neither server nor host is specified (Automatic) "Automatic" is displayed.
Displays the resource types being managed. When there are multiple resource types being managed, they are displayed separated by commas ("). - When server resources are being managed "Server" is displayed. - When storage resources are being managed "Storage" is displayed. - When no resources are being managed A hyphen ("-") is displayed. For the L-Servers that were created in Resource Orchestrator, a hyphen ("-") is displayed.
Usage The usage of the disk set for the L-Server is displayed. Resource name The disk name set for the L-Server is displayed. - When a Disk is Allocated A link to the detailed information of the allocated disk is displayed. - When No Disk is Allocated The name of the resource to be used is displayed. Type The type of the disk allocated to the L-Server is displayed. When type information cannot be obtained, a hyphen ("-") is displayed. Share The shared disk status is displayed.
A.6.13 L-Platform 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. 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 physical servers The server pool icon and resource pool name are displayed. - For a VM host The VM host icon and VM host name are displayed. CPU performance (Defined) The CPU performance value defined during L-Server creation is displayed. Number of CPUs (Allocated) The CPU performance value of the physical server actually allocated to the L-Server is displayed. Memory (Defined) The memory capacity defined during L-Server creation is displayed.
"SLB" 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. When multiple network devices are configured, network device names and statuses will be displayed separated by commas (","). Name(Status),Name(Status) A.6.
Network Device Basic Information Name (Label) The name of the directory containing the ruleset used by the resources allocated to the L-Platform is displayed. Description A description of the ruleset is displayed. 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.
Pool List Name (Label) The name used to identify the resource pool is displayed. Type The type of the resource pool is displayed. Priority The priority of the resource pool is displayed. Stored Resource Number The number of resources registered in the resource pool is displayed. 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 a VM host The VM host icon and VM host name are displayed. CPU performance (Defined) The CPU performance value defined during L-Server creation is displayed. CPU performance (Allocated) The CPU performance value of the physical server actually allocated to the L-Server is displayed. Number of CPUs (Defined) The number of CPUs defined during L-Server creation is displayed. Number of CPUs (Allocated) The number of CPUs of the physical server actually allocated to the L-Server is displayed.
Capacity CPU Capacity Total Capacity The total CPU capacity of the VM host is displayed. Unused Capacity The free CPU capacity of the VM host is displayed. Memory Size Total Capacity The total memory capacity of the VM host is displayed. Unused Capacity The free memory capacity of the VM host is displayed. VM Host List Name (Label) The name of the registered VM host is displayed. Status The status of the registered VM host is displayed. VM type The VM type of the registered VM host is displayed.
Memory Size Total Capacity The total memory capacity of the VM host is displayed. Unused Capacity The free memory capacity of the VM host is displayed. VM Host Information Area Status The status of the VM host is displayed. VM type The VM type of the VM host is displayed. Cluster Group Displayed when using cluster configurations. Number of VM guests The number of VM guests belonging to the VM host is displayed.
Displayed when the VM host is VMware. When not in a cluster configuration, a hyphen ("-") is displayed. Admission Control The enabled/disabled status of the admission control function provided by VMware is displayed. One of the following is displayed: - on - off Displayed when the VM host is VMware. When not in a cluster configuration, a hyphen ("-") is displayed. Standby Mode The values based on the status of VMware standby mode and VMware DPM are displayed.
Memory Capacity The memory capacity of the VM guest is displayed. Allocated L-Server The name of the L-Server allocated to the VM guest is displayed. A.6.18 Server 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. Comments Comments set for the resource are displayed. Priority The priority of the server pool is displayed.
Number of CPUs The memory capacity of the physical server is displayed. Memory Capacity The memory capacity of the registered server is displayed. Allocated L-Server The L-Server name allocated to the physical server is displayed. Server Attributes General Area Physical server name The name of the server on which the physical OS, VM host, or VM guest is operating is displayed.
Memory Size The memory capacity of the physical server is displayed. This attribute is displayed as "-" for servers other than PRIMERGY BX servers or SPARC Enterprise M servers. For SPARC Enterprise M4000/M5000/M8000/M9000 servers, this is displayed only when the server is powered on. Admin LAN Redundancy Displayed when NIC redundancy has been configured for admin LANs. HBAAR LAN (MAC address) The MAC address used for the HBA address rename setup service is displayed.
L-Server Properties Allocated L-Server L-Server name allocated to the physical server is displayed. A.6.19 Storage Pool Attributes General Area Name (Label) The name of the resource is displayed. Type The type of the resource is displayed. Priority The priority of the storage pool is displayed. Attributes The setting status of Thin Provisioning attributes is displayed. - When Thin Provisioning attributes are set [Thin Provisioning] is displayed.
Attributes The type of the virtual storage is displayed. Disk Resource List Name (Label) The disk name is displayed. A link to the detailed information of the allocated disk is displayed. Status The disk status is displayed. Size The disk size is displayed. Virtual Storage The disk allocation destination is displayed. Share The shared settings of the disk are displayed. Attributes The attributes that have been set are displayed. - When thin provisioning is configured "Thin Provisioning" is displayed.
Thin Provisioning Thin provisioning configuration information is displayed. - 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. Disk Resource List Name (Label) The disk name is displayed. A link to the detailed information of the allocated disk is displayed. Status The disk status is displayed.
Comments Comments set for the disk are displayed. Configuration Information Status The disk status is displayed. Size The disk size is displayed. Allocation The disk allocation status is displayed. L-Server that was last used If a disk is unallocated, the name of the L-Server that the disk was last allocated to is displayed. If it is an L-Server located in a tenant or resource folder, the name of the tenant or resource folder is also displayed.
L-Server Properties Allocated L-Server The name of the L-Server to which a disk has been allocated is displayed. Disk No. The disk number is displayed. Disk Usage The usage of the disk is displayed. A.6.20 Network Pool Attributes General Area Name (Label) The name used to identify the network pool is displayed. Type The type of the network pool is displayed. Priority The priority for automatic selection of resources when multiple network pools are available is displayed.
Subnet Address The subnet address of the network resource is displayed. Subnet Mask The subnet mask of the network resource is displayed. Address Number (Unused Number/Total Number) The total number and number of unused IP addresses registered in the network resource are displayed. Network Device List Network Device Name The network device name is displayed. Model The model name is displayed. Status The operational status of the network device is displayed.
Attribute Information Admin LAN Whether it is to be used as an admin LAN is displayed. - When used as an admin LAN "yes" is displayed. - When not used as an admin LAN "no" is displayed. iSCSI boot The LAN for iSCSI boot is displayed. use configured virtual switches. If no virtual network, virtual switch, or port group corresponding to the network resource exists, information on whether those resources will be automatically configured is displayed.
physical LAN segment The physical LAN segment set for the network resource is displayed. When no physical LAN segment is set, a hyphen ("-") is displayed. The physical LAN segment item will not be displayed if no server NIC has been defined. Excluded IP List Start IP Address The start address of the IP addresses to be excluded from automatic configuration is displayed. End IP Address The end address of the IP addresses to be excluded from automatic configuration is displayed.
- VMware - Hyper-V Virtual Switch / Port Group When the VM type is VMware, the virtual switch and port group names are displayed. When it is Hyper-V, the virtual network name is displayed. A hyphen ("-") is displayed in the following cases. - When the same configuration that is to be configured automatically has been created by the user beforehand. - When a configuration change made by the user with VM management software after automatic configuration is detected by this product. A.6.
Address Number (Unused Number/Total Number) The unused number and total number of IP addresses in the address set are displayed. Address Set 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. Attribute Information Start Address The start address of the address set is displayed.
Cloning Image 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. Image Type The image type of the image is displayed. VM type The VM type of the image is displayed. Comments Comments for the image are displayed. Cloning Image Attributes General Area Name (Label) The name of the resource is displayed. Type The type of the resource is displayed.
A.7 [Recovery Settings] Tab The [Recovery Settings] tab displays a list of spare servers assigned to the resource selected in the server resource tree. The table below shows the information displayed in the [Recovery Settings] tab. [Recovery Settings] Tab 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. Primary Server The name of the server on which the physical OS or VM host is operating is displayed.
Version The version of the cloning image is displayed. Collection Date The name used to identify a cloning image is displayed. OS The name of the operating system stored in the cloning image is displayed. Comments Comments describing the cloning image are displayed. Right-clicking a resource in the list displays a list of available operations in a popup menu. Refer to "A.2.2 Popup Menus" for details on the operations available from popup menus.
Attributes When using a VM pool with overcommit, [Over Commit] is displayed. The calculation method for free space is displayed. Max. Number of Possible New L-Servers When an L-Server template is selected, the number of L-Servers that can be created using resource pools is displayed. Server 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 in which a resource pool is stored is displayed.
Network 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 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. IP Address Number(Unused/Total) The number of IP addresses of the network resources registered in the resource pool.
A.12 Recent Operations This section describes the recent operations area of the ROR console. Figure A.6 Recent Operations The recent operations area shows the status of operations that were recently performed. The result of a completed operation shows the operation's completion time and the related resource name. For operations that are still running, a progress bar is shown to indicate the current progress state. Each operation displayed in the recent operation area provides the following information.
A.13 Event This section describes the event area of the ROR console. Figure A.7 Event The event log displays a history of events that have occurred on managed resources. These events are added to the log automatically. Each event provides the following information. 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.
- Date The conditions set for events are displayed above the list. To clear the conditions, click displayed on the right of the list. 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. It is possible to specify the page to display, move forwards and backwards by single pages, and move to the first or last page.
Appendix B Format of CSV System Configuration Files This appendix explains the format of the CSV system configuration files used by Resource Orchestrator's pre-configuration function. B.1 Obtaining the System Configuration File (CSV Format) The system configuration files can be obtained as follows. - From the selection window of the Resource Orchestrator DVD-ROM [Windows] Setting the Resource Orchestrator DVD-ROM in the CD-ROM drive automatically displays the screen below.
- From the ROR console The System Configuration Template can be obtained from a Resource Orchestrator manager installation. 1. Open and log in to the ROR console according to "Chapter 2 Login and Logout" in the "User's Guide for Infrastructure Administrators CE". 2. Select [File]-[System Configuration File]-[Download Template] from the ROR console menu. Displays the [File Download] window. 3. Click . 4. Specify the destination directory and the file name. 5. Click . B.
- RCXCSV V3.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" SPARC Enterprise (M3000-/T series) performs import/export of a system configuration file (CSV format) by a section name [SPARC].
- new 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". Optional parameters can be omitted by using hyphens ("-").
Table B.
- As with chassis for server blades, and chassis for LAN switch blades, items that need to be registered in advance to enable registration of other should be defined in the system configuration file or registered in advance. Character Code The system configuration files (CSV format) used for pre-configuration are saved using ASCII (often referred to as "ANSI" in Windows systems). When files that use a character code other than ASCII are imported, the system may not operate correctly.
login_name Enter the name of a VIOM user account. When specifying a domain, use the following syntax: "domain_name\user_name". login_passwd Enter the password of the above VIOM user account. passwd_enc Enter one of the following. - If login_passwd is plain text "plain" - If the password is encrypted "encrypted" Chassis Data - Section Name Enter [Chassis] as the section name. - Section Header operation Enter the desired operation for the current line. Enter a hyphen ("-") to skip this line.
- Section Header operation Enter the desired operation for the current line. Enter a hyphen ("-") to skip this line. chassis_name Enter the name that will be used to identify the chassis. Enter a character string beginning with an alphabetical character and containing up to 10 alphanumeric characters and hyphens ("-"). Note Chassis names should be unique between all chassis. Names are not case-sensitive. ip_address Enter the same IP address as that set on the management board.
chassis_name Enter the name that will be used to identify the chassis. Enter a character string beginning with an alphabetical character and containing up to 10 alphanumeric characters and hyphens ("-"). Note Chassis names should be unique between all chassis. Names are not case-sensitive. ip_address Enter the same IP address as that configured on the XSCF. Enter a string of numeric values (between 0 and 255) and periods. Note IP addresses should be unique between all resources.
slot_no Enter the slot number where the LAN switch blade is installed. Enter a number between 1 and 8. switch_name Enter the name to assign to this LAN switch blade. Enter a string of up to 15 alphanumeric characters, underscores ("_"), and hyphens ("-"). Note LAN switch blade names should be unique between all LAN switch blades. The names are case-sensitive. ip_address Enter the same IP address as that set on the LAN switch blade. Enter a string of numeric values (between 0 and 255) and periods.
product_name Enter the model of the LAN switch blade. Note that if a hyphen ("-") is entered, it is treated as "BX600 GbE Switch Blade 30/12". One of the following models can be entered.
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. Server Management Information - Section Name Enter [Server] as the section name. - Section Header operation Enter the desired operation for the current line. Enter a hyphen ("-") to skip this line. chassis_name Enter the chassis name (the value of "chassis_name" in the [Chassis] section).
mac_address Enter the MAC address of the admin LAN network interface: NIC1 (Index1). Enter a string delimited by hyphens ("-") or colons (":") ("xx-xx-xx-xx-xx-xx" or "xx:xx:xx:xx:xx:xx"). second_mac_address Enter the MAC address of the network interface used for the HBA address rename setup service or for admin LAN redundancy. The second network interface (Index 2) should be used. Enter a string delimited by hyphens ("-") or colons (":") ("xx-xx-xx-xx-xx-xx" or "xx:xx:xx:xx:xx:xx").
ipmi_passwd Enter the password of the remote management controller user account. Enter a string of up to 16 alphanumeric characters and symbols (ASCII character codes: 0x20 to 0x7e). This field can be omitted if no password has been set for this user account. Note If the password of the current administrator account on the remote management controller is longer than 16 characters, either create a new account or change its password (within 16 characters). ipmi_ passwd_enc Enter one of the following.
SPARC 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. Enter a character string beginning with an alphabetical character and containing up to 15 alphanumeric characters and hyphens ("-"). ip_address Enter the same IP address as that set within the server's operating system.
- For ILOM Enter between 8 and 16 characters, including alphanumeric characters, blank spaces (" "), and any of the following symbols. "!", "@", "#", "$", "%", "^", "&", "*", "[", "]", "{", "}", "(", ")", "-", "+", "=", "~", ",", ">", "<", "/", "'", "?", ";", ":" mgmt_passwd_enc Enter one of the following. - If mgmt_passwd is plain text "plain" - If the password is encrypted "encrypted" PRIMEQUEST Server Management Data - Section Name Enter [PRIMERGYPartitionModelServer] as the section name.
Server Blade VLAN Data - Section Name Enter [ServerNet] as the section name. - Section Header operation Enter the desired operation for the current line. Enter a hyphen ("-") to skip this line. server_name Enter the server name (the value of "server_name" in the [Server] section). nic_no This is the index number of the server blade's network interface. Enter a number between 1 and 12.
partition_no The number of a partition. Enter a number between 0 and 23. server_name Enter the resource name that will be used to identify the server. Enter a character string beginning with an alphabetical character and containing up to 15 alphanumeric characters and hyphens ("-"). 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.
- Section Header operation Enter the desired operation for the current line. Enter a hyphen ("-") to skip this line. server_name Enter the server name (the value of "server_name" in the [Server] section). 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".
ip_address Enter the IP address used to connect to this VM management software or a hyphen ("-"). Enter a string of numeric values (between 0 and 255) and periods. If a hyphen ("-") is entered, this VM management software will be seen as being installed on the admin server. 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.
- Section Header operation Enter the desired operation for the current line. Enter a hyphen ("-") to skip this line. server_name Enter the server name (the value of "server_name" in the [Server] section). 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.
reboot_count Enter the number of times to reboot. Enter a number from 1 to 3. 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 ("-").
Memo - Section Name Enter [Memo] as the section name. This is required when registering the labels, comments, and contact information (displayed in BladeViewer) using the pre-configuration function. - Section Header operation Enter the desired operation for the current line. Enter a hyphen ("-") to skip this line. resource_type Enter the type of the resource for which to set this memo. Enter one of the following.
RCXCSV,V3.5 # ServerView Resource Orchestrator # System configuration file [Subnet] operation,subnet_name,network_address,subnet_mask,gateway -,subnet1,172.16.0.0,255.255.0.0,172.16.0.1 -,subnet2,192.168.1.0,255.255.255.0,192.168.1.1 [VIOManager] operation,name,ip_address,login_name,login_passwd,passwd_enc -,VIOM,127.0.0.1,administrator,administrator,plain [Chassis] operation,chassis_name,ip_address,snmp_community_name -,chassis01,192.168.3.
-,chassis01,2,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.
[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.
Appendix C Maintenance Mode This appendix explains the maintenance mode available in Resource Orchestrator and how to use it. Maintenance mode is used during hardware maintenance of managed servers. It is also used during the installation and maintenance of physical OSs and VM hosts. Maintenance mode avoids unwanted error notifications and disables execution of Auto-Recovery upon server failure.
Glossary access path A logical path configured to enable access to storage volumes from servers. active mode The state where a managed server is performing operations. Managed servers must be in active mode in order to use Auto-Recovery. Move managed servers to maintenance mode in order to perform backup or restoration of system images, or collection or deployment of cloning images. active server A physical server that is currently operating.
- When using a local boot configuration The system is recovered by restoring a backup of the system image of the failed server onto a spare server. - When booting from a SAN or a disk on a LAN The system is restored by having the spare server inherit the system image on the storage. Also, when a VLAN is set for the public LAN of a managed server, the VLAN settings of adjacent LAN switches are automatically switched to those of the spare server.
cloning Creation of a copy of a system disk. cloning image A backup of a system disk, which does not contain server-specific information (system node name, IP address, etc.), made during cloning. When deploying a cloning image to the system disk of another server, Resource Orchestrator automatically changes server-specific information to that of the target server. Cloud Edition The edition which can be used to provide private cloud environments.
ESC (ETERNUS SF Storage Cruiser) Software that supports stable operation of multi-vendor storage system environments involving SAN, DAS, or NAS. Provides configuration management, relation management, trouble management, and performance management functions to integrate storage related resources such as ETERNUS.
global zone The actual OS that is used for a Solaris container. 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.
IBP (Intelligent Blade Panel) One of operation modes used for PRIMERGY switch blades. This operation mode can be used for coordination with ServerView Virtual I/O Manager (VIOM), and relations between server blades and switch blades can be easily and safely configured.
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. LDAP provides functions such as direct searching and viewing of directory services using a web browser. license The rights to use specific functions. Users can use specific functions by purchasing a license for the function and registering it on the manager.
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. maintenance mode The state where operations on managed servers are stopped in order to perform maintenance work. In this state, the backup and restoration of system images and the collection and deployment of cloning images can be performed.
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. L2 switches, firewalls, and server load balancers fit into this category. network device configuration file These files contain definitions of settings regarding communication, such as VLAN information for network devices and interfaces, rules for firewalls and server load balancers, etc.
PDU (Power Distribution Unit) A device for distributing power (such as a power strip). Resource Orchestrator uses PDUs with current value display functions as Power monitoring devices. physical LAN segment A physical LAN that servers are connected to. Servers are connected to multiple physical LAN segments that are divided based on their purpose (public LANs, backup LANs, etc.). Physical LAN segments can be divided into multiple network segments using VLAN technology.
private cloud A private form of cloud computing that provides ICT services exclusively within a corporation or organization. public LAN A LAN used for operations by managed servers. Public LANs are established separately from admin LANs. rack A case designed to accommodate equipment such as servers. rack mount server A server designed to be mounted in a rack. RAID (Redundant Arrays of Inexpensive Disks) Technology that realizes high-speed and highly-reliable storage systems using multiple hard disks.
resource General term referring to the logical definition of the hardware (such as servers, storage, and network devices) and software that comprise a system. resource folder An arbitrary group of resources. resource pool A unit for management of groups of similar resources, such as servers, storage, and network devices. resource tree A tree that displays the relationships between the hardware of a server and the OS operating on it using hierarchies.
- script lists for deletion (physical server deleted) - script lists for deletion server A computer (operated with one operating system). server blade A server blade has the functions of a server integrated into one board. They are mounted in blade servers. server management unit A unit used for managing servers. A management blade is used for blade servers, and a Remote Management Controller is used for other servers. server name The name allocated to a server.
SMB (Server Message Block) A protocol that enables the sharing of files and printers over a network. SNMP (Simple Network Management Protocol) A communications protocol to manage (monitor and control) the equipment that is attached to a network. software initiator An initiator processed by software using OS functions. Solaris container resource pool The Solaris Containers resource pool used in the global zone and the non-global zone. Solaris Containers Solaris server virtualization software.
System Board A board which can mount up to 2 Xeon CPUs and 32 DIMMs. system disk The disk on which the programs (such as the OS) and files necessary for the basic functions of servers (including booting) are installed. system image A copy of the contents of a system disk made as a backup. Different from a cloning image as changes are not made to the server-specific information contained on system disks.
URL (Uniform Resource Locator) The notational method used for indicating the location of information on the Internet. VIOM (ServerView Virtual-IO Manager) The name of both the I/O virtualization technology used to change the MAC addresses of NICs and the software that performs the virtualization. Changes to values of WWNs and MAC addresses can be performed by creating a logical definition of a server, called a server profile, and assigning it to a server.
VM Home Position The VM host that is home to VM guests. VM host A server on which server virtualization software is operated, or the server virtualization software itself. VM maintenance mode One of the settings of server virtualization software, that enables maintenance of VM hosts. For example, when using high availability functions (such as VMware HA) of server virtualization software, by setting VM maintenance mode it is possible to prevent the moving of VM guests on VM hosts undergoing maintenance.
Xen A type of server virtualization software. XSB (eXtended System Board) Unit for domain creation and display, composed of physical components. XSCF (eXtended System Control Facility) The name of the Remote Management Controller for SPARC Enterprise M series servers. zoning A function that provides security for Fibre Channels by grouping the Fibre Channel ports of a Fibre Channel switch into zones, and only allowing access to ports inside the same zone.
