Page 1: Operation Guide
ServerView Resource Orchestrator Cloud Edition V3.1.1 Operation Guide Windows/Linux J2X1-7611-05ENZ0(03) March 2013...
Page 2 Preface Resource Orchestrator Documentation Road Map The documentation road map for Resource Orchestrator is as shown below. Resource Orchestrator Documentation Road Map Point Refer to the user role manuals displayed in the table below for roles that are not in the diagram. Roles that are not in the diagram Roles that are in the diagram Infrastructure operator...
Page 3 Purpose This manual explains how to operate 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. When setting up systems, it is assumed that readers have the basic knowledge required to configure the servers, storage, network devices, and server virtualization software to be installed.
Page 4 Chapter 12 Collecting Power Consumption Data and Displaying Graphs 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. Chapter 13 Monitoring Resource Pools (Dashboard) Explains the monitoring of resource pools.
Page 5 Operations on the ROR console can be performed using either the menu bar or pop-up menus. By convention, procedures described in this manual only refer to pop-up menus. Regarding Installation Folder Paths The installation folder path may be given as C:\Fujitsu\ROR in this manual. Replace it as shown below. When using Windows 64-bit (x64)
Page 6 Abbreviation Products Microsoft(R) Windows Server(R) 2012 Standard Microsoft(R) Windows Server(R) 2012 Datacenter Microsoft(R) Windows Server(R) 2008 Standard Microsoft(R) Windows Server(R) 2008 Enterprise Microsoft(R) Windows Server(R) 2008 R2 Standard Microsoft(R) Windows Server(R) 2008 R2 Enterprise Microsoft(R) Windows Server(R) 2008 R2 Datacenter Microsoft(R) Windows Server(R) 2003 R2, Standard Edition Microsoft(R) Windows Server(R) 2003 R2, Enterprise Edition Windows...
Page 7 Abbreviation Products Red Hat(R) Enterprise Linux(R) 5.3 (for Intel64) Red Hat(R) Enterprise Linux(R) 5.4 (for x86) Red Hat(R) Enterprise Linux(R) 5.4 (for Intel64) Red Hat(R) Enterprise Linux(R) 5.5 (for x86) Red Hat(R) Enterprise Linux(R) 5.5 (for Intel64) Red Hat(R) Enterprise Linux(R) 5.6 (for x86) Red Hat(R) Enterprise Linux(R) 5.6 (for Intel64) Red Hat(R) Enterprise Linux(R) 5.7 (for x86) Red Hat(R) Enterprise Linux(R) 5.7 (for Intel64)
Page 8 Abbreviation Products Red Hat(R) Enterprise Linux(R) 5.8 (for x86) Red Hat(R) Enterprise Linux(R) 5.8 (for Intel64) Red Hat(R) Enterprise Linux(R) 6.2 (for x86) Red Hat(R) Enterprise Linux(R) 6.2 (for Intel64) Red Hat Enterprise Linux 6 Red Hat(R) Enterprise Linux(R) 6.3 (for x86) Red Hat(R) Enterprise Linux(R) 6.3 (for Intel64) Red Hat(R) Enterprise Linux(R) 5.4 (for x86) Linux Virtual Machine Function RHEL5-Xen...
Page 9 Export Administration Regulation Declaration Documents produced by FUJITSU may contain technology controlled under the Foreign Exchange and Foreign Trade Control Law of Japan. Documents which contain such technology should not be exported from Japan or transferred to non-residents of Japan without first obtaining authorization from the Ministry of Economy, Trade and Industry of Japan in accordance with the above law.
Page 10 All other brand and product names are trademarks or registered trademarks of their respective owners. Notices The contents of this manual shall not be reproduced without express written permission from FUJITSU LIMITED. The contents of this manual are subject to change without notice.
Page 11 Contents Part 1 Overview..................................1 Chapter 1 Overview of Operations, Maintenance, and Monitoring...................2 1.1 Operation, Maintenance, and Monitoring by Infrastructure Administrators..................3 1.2 Operation, Maintenance, and Monitoring by Tenant Administrators....................4 1.3 Operation, Maintenance, and Monitoring by Tenant Users.........................4 Part 2 Operation..................................5 Chapter 2 Starting and Stopping Managers and Agents......................6 2.1 Starting and Stopping the Manager..............................6...
Page 12 8.5.5.2 How to Modify Application Process to be Used.........................29 8.5.6 Editing the Environment Setup File for the L-Platform API......................29 8.5.7 Edit the License Agreement................................29 8.5.8 Settings when RHEL5-Xen is used............................29 8.5.9 Default Password Setting for Sent Emails..........................29 8.5.10 Settings for the Maximum Number of Connections for the L-Platform Template..............30 8.5.11 Customizing the User Rights for L-Platform Operations......................30...
Page 13: Table Of Contents
10.1.4.2 Restoring the Resources of This Product...........................89 10.1.4.3 Starting the Manager................................90 10.1.4.4 Updating Backup Information of Network Device Files....................90 10.1.4.5 Disabling L-Platform Applications............................90 10.1.4.6 Updating the Configuration Information in the Operational Status Information..............90 10.1.5 Online Backup Settings for Metering............................91 10.2 Backup and Restoration of Network Devices..........................94 10.2.1 Mechanism of Backup and Restoration............................94...
Page 14 15.4.6.2 Usage charge Detail File..............................136 Chapter 16 Monitoring Logs..............................139 16.1 Operation Logs....................................139 16.1.1 Overview....................................139 16.1.2 Usage Method..................................142 16.1.3 Retention....................................143 16.1.4 Scope of Operations Recorded in Operation Logs.........................144 16.2 Audit Logs.....................................144 16.2.1 Configuration Management Audit Log...........................144 16.2.2 Audit Logs of Output by the Tenant Management, Accounting, Access Control and System Condition......150 16.2.3 Application Process Audit Log...............................156...
Page 15: Part 1 Overview
Part 1 Overview Chapter 1 Overview of Operations, Maintenance, and Monitoring..............2 - 1 -...
Page 16: Chapter 1 Overview Of Operations, Maintenance, And Monitoring
Chapter 1 Overview of Operations, Maintenance, and Monitoring This chapter provides an overview of operation, maintenance, and monitoring of Resource Orchestrator. For additional information on the operation, maintenance, and monitoring of this product, refer to the configuration information in the "Setup Guide CE".
Page 17: Operation, Maintenance, And Monitoring By Infrastructure Administrators
Configure firewalls When configuring an application on an L-Server that has been deployed on the public LAN, the tenant user needs to create a rule that enables access to that L-Server from the public LAN. Configure applications The tenant user performs the installation and environment settings necessary for the application to be provided as a service by the L-Server.
Page 18: Operation, Maintenance, And Monitoring By Tenant Administrators
Create a tenant administrator Creation, modification, and deletion of user accounts Management of templates Creation, modification, and deletion of L-Platform templates (*) Creation, modification, and deletion of L-Server templates * Note: To check subscription requests submitted by using a created L-Platform template, use a dual-role administrator account. For more details, refer to "Appendix B Applying (Subscribe) for L-Platform Usage by Dual-Role Administrators"...
Page 19: Part 2 Operation
Part 2 Operation Chapter 2 Starting and Stopping Managers and Agents..................6 Chapter 3 Managing User Accounts.......................11 Chapter 4 Managing Tenants.........................12 Chapter 5 Managing Templates........................13 Chapter 6 Managing Resources and Resource Pools...................14 Chapter 7 Management of L-Platform......................15 Chapter 8 Changing Settings.........................21 - 5 -...
Page 20: Chapter 2 Starting And Stopping Managers And Agents
Chapter 2 Starting and Stopping Managers and Agents This chapter explains how to manually start or stop managers and agents. To use Resource Orchestrator, both the manager and agents must be running. The manager and agent services are configured to start automatically upon startup of their respective servers (admin server, managed server).
Page 21 PXE Services DHCP Server (*) Systemwalker SQC DCM Interstage BPM Analytics eRule Engine (EFServer) Systemwalker MpJobsch9 Systemwalker MpMjes Systemwalker MpMjes9 Systemwalker Runbook Automation DB Service Shunsaku Conductor cmdbc Shunsaku Sorter cmdbo01 * Note: Required when managed servers belonging to different subnets from the admin server exist. From the Windows Control Panel, open [Administrative Tools].
Page 22: Starting And Stopping An Agent
For details on the command, refer to "5.19 rcxmgrctl" in the "Reference Guide (Command/XML) CE". To start or stop a manager in a clustered configuration, use the cluster administration view (Cluster Admin). For details, refer to the PRIMECLUSTER manual. Note When using ServerView Deployment Manager on an admin LAN, all services related to Resource Orchestrator will be automatically disabled.
Page 23 Agent Service Resource Coordinator Agent Related Services Deployment Agent Systemwalker SQC DCM From the Windows Control Panel, open [Administrative Tools]. Then, open the [Services] window to check the state of each service. The following explains how to start and stop each service. Agent Service Agents can be started and stopped using the start and stop subcommands of the rcxadm agtctl command.
Page 24 # /etc/init.d/scwagent start <RETURN> # /etc/rc2.d/S99ssqcdcm start <RETURN> Stop # /etc/init.d/scwagent stop <RETURN> # /etc/rc0.d/K00ssqcdcm stop <RETURN> [Solaris] [Solaris Zones] [OVM for SPARC] The agent consists of the following services. Agent Service Execute the following commands to determine whether the agent is running or not. If those commands show that the processes for the agent and deployment services are running, then the agent can be asserted to be running.
Page 25: Chapter 3 Managing User Accounts
Chapter 3 Managing User Accounts This chapter explains the management of user accounts. Creation, Viewing, and Modification of User Accounts Only users that hold the role of infrastructure administrator, tenant administrator, or administrator can create user accounts. For details on operations by infrastructure administrators, refer to "Chapter 3 Configuring Users for Infrastructure Administrators" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Page 26: Chapter 4 Managing Tenants
Chapter 4 Managing Tenants This chapter explains the management of tenants. Tenant Creation The flow of tenant creation is as follows: Register Tenants Input the tenant information and register tenants. Create a Tenant Administrator Create a tenant administrator. Create a Local Pool for Tenants The following two types of resource pool operations can be performed: Local Pool A resource pool which can be used only for tenants.
Page 27: Chapter 5 Managing Templates
Chapter 5 Managing Templates This chapter explains the management of templates. L-Platform Templates An L-Platform template is the template to define the logical configuration of ICT resources and software. An L-Platform is composed of an L-Platform template. Use the [Template] tab to create, modify, and delete L-Platform templates. For details on the [Template] tab, refer to "Chapter 8 Template"...
Page 28: Chapter 6 Managing Resources And Resource Pools
Chapter 6 Managing Resources and Resource Pools This chapter explains the management of resources and resource pools. 6.1 Managing Resource Pools This section explains the management of resource pools. The following resource pool operations are possible: Addition and modification of tenants and local pools Deletion of local pools within tenants Addition, modification, and deletion of global pools When changing the global pool that can be used by tenants, perform the operation from the [Tenant] tab on the ROR console.
Page 29: Chapter 7 Management Of L-Platform
Chapter 7 Management of L-Platform This chapter explains how to management of L-Platform. 7.1 Review for L-Platform Usage Applications Use the [Request] tab of the ROR console to review applications to use from tenant users for operations such as usage application, configuration modification, and cancel of L-Platforms.
Page 30: Network Information Settings For Converted L-Servers
Importing the L-Server for which network information has been set Refer to "7.2.3.2 Importing L-Servers". Import L-Servers created in the ROR console into the L-Platform Refer to "7.2.3.2 Importing L-Servers". 7.2.3.1 Network Information Settings for Converted L-Servers Set the network information for the L-Servers converted in "Use of Physical Servers or Virtual Machines as L-Servers".
Page 31: Startup Priority Level Settings
is completed. When a deployment finishes, the IP address and host name of the guest OS are the same values as the server from which the cloning image has been collected. Therefore, if two or more users subscribe servers simultaneously, multiple servers with same settings might be deployed on the same network.
Page 32: Setting Alive Monitoring
Configuration or modification of network devices such as firewalls or server load balancers Figure 7.1 Flow of Corrective Actions when a Problem Occurs during L-Platform Operation The tenant user performs L-Platform creation, modification or deletion, or network device configuration or modification. Problem Occurrence L-Platform creation, modification or deletion, or network device configuration or modification ends abnormally.
Page 33: Redundancy Settings
For information on creating L-Server templates, refer to "Chapter 15 L-Server Template Operations" in the "User's Guide for Infrastructure Administrators (Resource Management) CE". If the settings are changed after deployment, change the "Type of Server(specifications)" by reconfiguring the L-Platform. Register different L-Server templates where heartbeat settings are enabled and disabled. Also use L-Server template names that make it easy to distinguish whether heartbeat settings are enabled or disabled.
Page 34: Definition Vm Specific Information Definition File
L-Server template name where automatic server release settings are enabled VMware_Small_Repurpose 7.2.10 Definition VM Specific Information Definition File If an overcommit value has not been set for the L-Server template selected in "type" on the Reconfiguration page of the L-Platform subscription window, then the values set in VM specific information definition file will not be used, even if the file is used.
Page 35: Chapter 8 Changing Settings
Chapter 8 Changing Settings This chapter explains how to change settings. 8.1 Registering and Deleting Application Process Assessors This section explains how to register and delete application process assessors. 8.1.1 Registering an Application Process Assessor This section explains how to register an infrastructure administrator or dual-role administrator as an application process assessor. Add all infrastructure administrator and dual-role administrator to the directory service IflowUsers group in order to use application processes.
Page 36: Settings For Sending Email
# OpenDS Installation_folder/bin/ldapmodify" -p <port number> -f <ldif file> -D <administrator user DN> -w <password> An execution example is shown below. # /opt/fujitsu/ServerViewSuite/opends/bin/ldapmodify -p 1473 -D "cn=Directory Manager" -f /tmp/ ldif/adduser2group.ldif -w admin Processing MODIFY request for cn=IflowUsers,ou=group,dc=fujitsu,dc=com MODIFY operation successful for DN cn=IflowUsers,ou=group,dc=fujitsu,dc=com Note In the command input line, enter the command as one line without entering any line feeds.
Page 37: Settings For Port Number Of Admin Servers
Settings for the Email Sent from Tenant Management Email sent from the tenant management will be enabled only if the tenant has set the Performing tenant management setting. When an operation such as registering a tenant or adding or changing a user has been performed, notification to that effect is sent to the tenant administrators, tenant users, and tenant email addresses within that same tenant.
Page 38 Modify the portal.properties file. Open the following file: [Windows Manager] Installation_folder\RCXCTMG\SecurityManagement\conf\portal.properties [Linux Manager] /etc/opt/FJSVctsec/conf/portal.properties Change the port numbers specified in the following URLs. Set the same values in the port numbers: portalSsl.url authedPortal.url sendmail.auth.url Start the Interstage Management Console. The procedure for starting the Interstage Management Console is as follows: [Windows Manager] From the Start menu, select All Programs >...
Page 39: Editing Information In The Home Window
Modify the managerview_config.xml file. Open the following file. [Windows Manager] Installation_folder\RCXCTMG\MyPortal\config\managerview_config.xml [Linux Manager] /etc/opt/FJSVctmyp/config/managerview_config.xml Modify the value of the entry tag with vsys-port as the key value. The entry tag with vsys-port as the key value An example is shown below. The section in italics is the information to be modified. <entry key="vsys-port">8013</entry>...
Page 40: Settings For L-Platform Management
Enter a string of up to 30 characters for the schedule. Commas (,) cannot be included. Enter a string of up to 250 characters for the message. Commas (,) can be included. Example of settings 2011/11/11,Maintenance is scheduled for the Kanto network on the weekend. ,Upgraded the operation management software.
Page 41: Subnet Settings At Segment Editing
8.5.2 Subnet Settings at Segment Editing It is possible to change the method for setting up the subnets that are allocated to segments when performing an application to use L- Platform. Use the following procedure to use network resource names rather than IP addresses to select which subnets to allocate to segments during subnet setup.
Page 42: Distribution Ratio Settings
[Linux Manager] /etc/opt/FJSVctmyp/config/managerview_config.xml Add the following key and value: Key name Content enable-easy-reconfigure false: Disables the function. (This is the default value. This is applicable even when this key is not defined.) true : Enables the function Save the file. Restart the manager.
Page 43: Application Process Settings
Restart the manager. Refer to "2.1 Starting and Stopping the Manager" for information on how to restart the manager. 8.5.5 Application Process Settings This section explains how to modify the application process settings. 8.5.5.1 How to Modify the Application Process Settings This section explains how to modify the setting whether to use the application process.
Page 44: Settings For The Maximum Number Of Connections For The L-Platform Template
8.5.10 Settings for the Maximum Number of Connections for the L-Platform Template The maximum number of L-Servers that can be placed in an L-Platform Template and the maximum number of NICs in a segment of an L-Platform Template can be modified. Use the editor to open the settings file.
Page 45: Settings For Tenant Management And Account Management
8.6.1 Settings for Tenant Management and Account Management This section explains how to change the settings for the tenant management and the account management. Display setting for user list This section explains the procedure for changing the setting for whether or not tenant users are to be displayed, when an infrastructure administrators has used the tenant management to display the user list.
Page 46 /etc/opt/FJSVctsec/conf/portal.properties The following information must be modified: Setting item Settings visible.tenantuser Setting for infrastructure Specify "on" if both tenant administrators administrators operation and tenant users are to be displayed in the user list for the tenant management, and specify "off" if only tenant administrators are to be displayed.
Page 47 Setting item Settings user password button will not be displayed in the Account window of the account management. leftMenu.modifyUser.user.visible Setting for tenant user Specify "on" if changing user account is operation to be performed using the account management, and specify "off" if it is not to be performed.
Page 48: Editing The User Agreement When Registering A User
Setting item Settings If "false" has been specified, the Set password button will not be displayed in the User List window of the tenant management. In addition, the Change user password button will not be displayed in the Account window of the account management.
Page 49 /etc/opt/FJSVcfmg/config/vsys_config.xml The following information must be modified: Description Default value use-charge (*) Specifies whether usage fee (the estimated price) for the L-Platform template will be displayed. yes: Display no: Do not display * note: this can be set by "Setup Wizard" on the ROR Console. A setting example is shown below.
Page 50: Currency Information Settings
software is used, the usage fee (the estimated price) will be calculated using the operating value regardless of whether or not overcommit is enabled or disabled. A setting example is shown below. <?xml version="1.0" encoding="UTF-8"?> <properties> <entry key="estimation-mode">3</entry> <entry key="compatible-estimation">true</entry> ...
Page 51 Change the relevant items in the operational settings file for metering logs: Description Default value retention_period Retention period of log entries 0000-03-00 Logs will be deleted once their retention period has passed. Use the following format to specify the retention period: YYYY-MM-DD Example:...
Page 52: Usage Charge Calculator Settings
Description Default value A number of days cannot be specified with this method. *1: Changes to this setting are enabled by executing the Change periodic log schedule settings command after changing the settings file. *2: If periodic_log_schedule_type is DAILY, the periodic_log_schedule_day value will be ignored. An example of setting the operational settings file is shown below: # delete setting of meteringlog database # YYYY-MM-DD...
Page 53: System Condition Server List Settings
Description Default value accounting.use (*) Specify whether to use the usage charge calculator. yes: Use the usage charge calculator. no: Do not use the usage charge calculator. gui.cutoffdate (*) Specify the default for the cut-off date displayed in the tenant management window of the ROR console.
Page 54 If the L-Platform Management overcommit function is enabled, the CPU and memory settings displayed in the System Condition Server List can be changed. Refer to "18.6 Settings for the Overcommit Function" in the "Setup Guide CE" for information on the L-Platform Management overcommit function settings.
Page 55: Settings For Event Log Output For Cmdb Agent
When editing the viewlist_en.xml file, do not change any settings items other than serverByOrg_ROR.bottom.column.11.isEnable and serverByOrg_ROR.bottom.column.14.isEnable. Save the viewlist_en.xml file before you edit the file. If any settings other than serverByOrg_ROR.bottom.column.11.isEnable and serverByOrg_ROR.bottom.column.14.isEnable are changed, restore the saved file. 8.9 Settings for Event Log Output for CMDB Agent This section explains how to change the settings that determine whether the start/end messages for CMDB agent information collection are output to event logs.
Page 56: Part 3 Retention
Part 3 Retention Chapter 9 Hardware Maintenance........................43 Chapter 10 Backup and Restoration......................75 - 42 -...
Page 57: Chapter 9 Hardware Maintenance
Chapter 9 Hardware Maintenance This chapter explains how to perform hardware maintenance. 9.1 Overview This section explains how to perform maintenance on the hardware devices managed by Resource Orchestrator. Hardware Maintenance Flow The flow of maintenance for hardware used to operate an L-Platform is shown below. Figure 9.1 Flow of Maintenance for L-Platform Hardware Notify Users of Maintenance Operations The infrastructure administrator managing hardware devices notifies the tenant administrator and the tenant users that manage or...
Page 58 For SPARC M10 The infrastructure administrator places the managed servers into maintenance mode. Also place the managed servers into maintenance mode when reducing the capacity of the CPU on the system using the Capacity on Demand(CoD) function of SPARC M10. For details on maintenance mode, refer to "Appendix C Maintenance Mode"...
Page 59 For details on maintenance mode, refer to "Appendix C Maintenance Mode" in the "User's Guide for Infrastructure Administrators (Resource Management) CE". When using a server for which spare servers are not configured When using a server for which spare servers are not configured, the infrastructure administrator releases the managed server from maintenance mode.
Page 60 Investigation Request The tenant user requests investigation of the cause of the error by the tenant administrator, based on the information related to detected errors (error details, the name of the resource where the error occurred, the L-Platform name). The tenant administrator requests investigation of the cause of the error by the infrastructure administrator, based on the information obtained from the tenant user.
Page 61 Figure 9.3 Flow of Hardware Maintenance when a Server Fails *1: For details on how to identify failures, refer to "11.3 Addressing Resource Failures". *2: For details on how to configure and release the maintenance mode, refer to "Appendix C Maintenance Mode" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Page 62: Blade Server Maintenance
Replacing Non-Server Hardware Replace registered chassis, management blades, or any other hardware components external to servers. For details on replacing non-server hardware, refer to "9.3.4 Replacing Non-server Hardware". 9.2 Blade Server Maintenance This section explains the maintenance of blade servers. 9.2.1 Maintenance LED This section explains how to operate maintenance LEDs.
Page 63: Reconfiguration Of Hardware Properties
Click <OK>. The maintenance LED is turned off. 9.2.2 Reconfiguration of Hardware Properties This section explains how to reconfigure hardware properties for replaced hardware. After hardware replacement, it is necessary to reconfigure Resource Orchestrator with the new hardware properties. For PRIMERGY BX servers, the hardware properties are automatically reconfigured. Note Ensure this operation is performed only after the replacement of one of the following: a server itself, the NIC used for either the admin or public LAN, or the HBA.
Page 64: Replacing Servers
After hardware replacement, insert the server and check that the following message is displayed in the event log. Server blade added After the message is displayed, shut down the server if it is still powered on. After approximately 30 seconds, right-click the target server in the ROR console server resource tree, and select [Hardware Maintenance]-[Re-configure] from the popup menu.
Page 65 Replacing a Server with no Spare Server Assigned Use the following procedure to smoothly replace a server and resume its applications. Place the Server into Maintenance Mode Place the primary server to replace into maintenance mode. For details on maintenance mode, refer to "Appendix C Maintenance Mode" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Page 66: Replacing Non-Server Hardware
For details on BIOS settings, refer to "8.2 Configuring the Server Environment" in the "Design Guide CE". Shut down the server after completing BIOS settings. Reconfigure Hardware Properties after Replacement After replacing the server, reconfigure Resource Orchestrator with the latest hardware properties. For details on how to reconfigure hardware properties, refer to "9.3.1 Reconfiguration of Hardware Properties".
Page 67: Maintenance For Servers Other Than Blade Servers
RBridge ID Replacing Fibre Channel Switch Blades No specific action is required in Resource Orchestrator. In Resource Orchestrator, the settings for Fibre Channel switch blades are not restored. Restore the settings for Fibre Channel switch blades based on the information in hardware manuals. Replacing Storage Blades No specific action is required in Resource Orchestrator when replacing a storage blade that does not contain the boot disk of a server blade.
Page 68 To move a server to a different slot within a chassis, the server must be deleted first, and then registered again after being inserted in its new slot. Reconfiguring Hardware Properties after Server Replacement For Rack Mount and Tower Servers Use the following procedure to reconfigure properties for replaced hardware.
Page 69: Replacing Servers
Note When registering an agent and performing backups of system images or cloning images, perform one of the following. Restart the managed server after reconfiguring the hardware properties Restart the related services described in "2.2 Starting and Stopping an Agent" 9.3.2 Replacing Servers This section details the procedure to follow when replacing servers.
Page 70 Create a System Image Backup For local boot servers, create a system image backup when possible. For details on backing up system images, refer to "Chapter 16 Backup and Restore" in the "User's Guide VE". In SAN boot environments, the boot disk can be restored without having to back up and restore a system image. Power OFF Shut down the server to replace if it is still powered on.
Page 71 Reconfigure Hardware Properties after Replacement After replacing the server, reconfigure Resource Orchestrator with the latest hardware properties. For details on how to reconfigure hardware properties, refer to "9.3.1 Reconfiguration of Hardware Properties". When using VIOM, refer to the manual of ServerView Virtual-IO Manager and perform inventory boot on ServerView Virtual- IO Manager.
Page 72 Perform Post-server Switchover Operations For details on the operations that must be performed after server switchover, refer to "4.3 Post-Switchover Operations" in the "Operation Guide VE". Replacing a Server with no Spare Server Assigned When WWN information has been configured, use the following procedure to change the WWN information to that of the WWPN value of the replaced HBA.
Page 73 Perform Post-server Switchover Operations For details on the operations that must be performed after server switchover, refer to "4.3 Post-Switchover Operations" in the "Operation Guide VE". Replacing a Server with no Spare Server Assigned Use the following procedure to smoothly replace a server and resume its applications. Place the Server into Maintenance Mode Place the primary server to replace into maintenance mode.
Page 74: Replacing And Adding Server Components
Replace the Server Replace the server. Use the Maintenance Wizard of the Management Board Web-UI to perform replacement. For details on the Maintenance Wizard, refer to the PRIMEQUEST manual. Also, change the BIOS settings of the replacement server to match the operating environment. For details on BIOS settings, refer to "8.2 Configuring the Server Environment"...
Page 75: For Servers Not Using Server Management Software
When using I/O virtualization, the replacement HBA will automatically inherit the WWN originally set on the replaced HBA. Therefore, there is no need to reconfigure access paths on the storage side. When configuring WWN information, it is necessary to change WWN information settings to the replaced HBA WWN values. For details on how to change WWN information, refer to "9.1.12 Changing WWN Settings for ETERNUS SF Storage Cruiser Integration"...
Page 76: Network Device Maintenance
When replacing an entire server, a CPU, or memory, if there are differences in the CPU or memory specifications before and after the replacement, reflect the new CPU and memory specifications of the replaced server in the definition file before reconfiguring hardware information.
Page 77: When The Device To Replace Has Failed
Figure 9.4 Image of Network Device Replacement It is assumed that you perform replacement while continuing operations using the network devices of redundancy configurations of an active and standby switch configuration. When there is no description, the operations are performed by an infrastructure administrator. 9.5.1.1 When the Device to Replace has Failed This section explains the replacement procedure when the device to replace has failed.
Page 78: When The Device To Replace Has Not Failed
When the Management Function for Network Device Configuration Files is Used Announcement of planned maintenance operations. Change the target network device to "maintenance mode". Replace the network devices. (Hardware maintenance person) Restore the configuration of the replaced network device using the network device file which was backed up beforehand in accordance with the maintenance procedure of the network device.
Page 79 Change the target network device to "maintenance mode". Back up the current environment (such as definitions) from the network devices that are switched to "maintenance mode". Replace the network devices. (Hardware maintenance person) Restore the configuration of the replaced network device using the environment backed up in step 4, following the maintenance procedure for the network device.
Page 80 automatically. For details, please refer to the manual of the "Cisco ASA 5500 series". For restoration of network device files, please refer to "10.2.3 Restoration of Network Devices". For the maintenance procedures for network devices, refer to the manual of the network device. Back up the current network device files from the network devices with operational status.
Page 81: Regular Maintenance Procedure Of Network Devices
When the network device to replace has failed, step 4 cannot be performed. It is recommended to back up environments regularly in preparation for failures of network devices. When performing regular backup of environments, the load of restoration operations after replacement of network devices can be reduced, by using the latest backup environment.
Page 82: Procedure For Addition Of Network Devices
Switch over the network device in active status that is the target of regular maintenance and the network device of the redundancy configuration which is in standby status. Then change the status of the remaining network device that is the target of regular maintenance from operational status to standby status, and perform steps 3 to 8.
Page 83 Figure 9.5 Image of L2 Switches to Add Design additional configurations. (Network device administrator) Provide the additional network device information to the infrastructure administrator. (Network device administrator) Add a network device in the state where the following operations have been completed. Initial configuration Operation test Integration of the device into a physical network configuration...
Page 84: Adding Firewalls, Server Load Balancers, And L2 Switches For Additional Tenants
When the following applies to the additional network device, create and register rulesets. When adding an L2 switch of a model for which sample scripts are not prepared, or an L2 switch of a model that has not been used in the system until now. In this case, it is necessary to create a directory to allocate rulesets to.
Page 85 Figure 9.6 Image of Tenants to Add Design additional configurations. (Network device administrator) Provide the additional network device information to the infrastructure administrator. (Network device administrator) Add a network device in the state where the following operations have been completed. Initial configuration Operation test Integration of the device into a physical network configuration...
Page 86: Procedure For Addition Or Modification Of Connection Destinations Of Network Devices
Register the added firewall, server load balancer, and L2 switch as network devices. Use the rcxadm netdevice create command to register as a network device. When the following applies to the additional network device, create and register rulesets. When adding a firewall, server load balancer, or L2 switch of a model for which sample scripts are not provided, or those of a model that has not been used in the system until now In this case, it is necessary to create a directory to allocate rulesets to.
Page 87: Storage Device Maintenance
Create network configuration information (XML definition) using the acquired network device information. Confirm there are no differences besides the link information (under Links tag) regarding the added or modified destinations for connection, by comparing the network configuration information of network devices registered in Resource Orchestrator and the network configuration information created in step 2.
Page 88 Reconfigure the power monitoring device's hardware properties. In the ROR console server resource tree, right-click the target power monitoring device (PDU or UPS), and from the popup menu, select [Hardware Maintenance]-[Re-configure]. The [Re-configure Hardware Properties] dialog is displayed. Click <OK>. The target power monitoring device's hardware properties are reconfigured.
Page 89: Chapter 10 Backup And Restoration
Chapter 10 Backup and Restoration This chapter describes how to operate the backup and restoration of ServerView Resource Orchestrator Cloud Edition. 10.1 Backup and Restoration of Admin Servers This section describes how to operate the backup and restoration of the admin server of ServerView Resource Orchestrator Cloud Edition. Backing up the Admin Server The two methods of backing up the admin server are shown below.
Page 90: Mechanism Of Backup And Restoration
Usually, for each 16 MB written, the WAL file being written to is switched, and the WAL file for which writing has been completed is saved to the "wal" directory under the backup directory. Periodically executing the rcxmgrbackup command allows the contents of updates to the database that are recorded in saved WAL files to be maintained for a certain period of time.
Page 91 Do not delete backup resources during execution of the restore command. To delete backup resources, delete the folder specified in the backup destination as well as all folders and files under that folder. Backup to the following media cannot be performed using the backup command: Backup to optical disks such as CD-R and DVD-R To back up user resources to optical disks, back up once to local disks, and then write to the media.
Page 92 Necessity of Target Resources When Backup is Necessary Stopping Remarks Managers Note) If the following definition files are to be backed up, the Manager must be stopped and offline backup must be performed. - Some L-Platform management settings Definition files Modification of definition files No (Note) - Tenant management and account...
Page 93 Target Resources Disk Space Necessary for the Backup Every time, when backing up, it is necessary. Therefore, when the backup is executed three times for instance, the capacity of image System image or cloning image save area is three times necessary. For the capacity of the image storage area, refer to "2.4.2.7 Dynamic Disk Space"...
Page 94 * Note: The backup of metering information is gathered under the control of the directory specified by the rcxmgrbackup command at an off-line backup, and it is gathered in the area besides the specified directory at an online backup. Please calculate a necessary amount of disk by backing up metering information referring to the following examples. "The amount of disk space necessary for the base backup"...
Page 95 Table 10.7 Disk Space Necessary for Operation of Online Backup Disk space necessary for operation of online backup = Disk space necessary for base backup + Disk space necessary for difference backup = 1.3 GB + 11.3 GB = 12.6GB Storage Destination for Backing Up Resources This section describes the storage destination for backing up Admin Server resources.
Page 96: Offline Backup Of The Admin Server
Command processing time offline backup : 3 minutes online backup (base backup) : 2 minutes online backup (differential backup) : 2 minutes restore : 4 minutes System Restart Point after Restoration In the system operations flow used by this product, the restart point of the system will vary according to the timing of the backup of resources.
Page 97: Stopping The Manager
10.1.2.1 Stopping the Manager Stop the Manager and check that it is in a stopped state. Stopping the Manager Execute the command shown below to stop the Manager. For details on the command, refer to "5.19 rcxmgrctl" in the "Reference Guide (Command/XML) CE". [Windows Manager] >Installation_folder\SVROR\Manager\bin\rcxmgrctl stop <RETURN>...
Page 98: Online Backup Of The Admin Server
Saving Image Management Information Check the following image management information, the number of stored snapshot generations and the image file storage folder: Number of Stored Snapshot Generations Image File Storage Folder Execute the following command to set the number of stored snapshot generations and the image storage folder information to a standard output, by redirecting the information to a file, and then saving it.
Page 99 PANIC: could not locate required checkpoint record HINT: If you are not restoring from a backup, try removing the file "C:/Fujitsu/ROR/RCXCTMG/Charging/pgsql/data/backup_label". * Note: The "xxxxxxxx" and "xx" parts of the log are undefined. In a case like this, delete the file shown below. When this file is deleted, start of the Manager will end normally. When this file is deleted, start of the Manager will end normally.
Page 100: Items To Be Determined Before Periodic Execution
Execute the rcxmgrbackup command. Periodically executing the rcxmgrbackup command allows the contents of updates to the database that are recorded in saved WAL files to be maintained for a certain period of time. For example, when the rcxmgrbackup command is executed every hour, the contents of updates performed in the most recent one-hour period will be saved.
Page 101 To manage tasks hierarchically, use the following procedure to create a folder: In the Task Scheduler menu, after selecting Task Scheduler Library, select [Actions]-[New Folder], and then enter any folder name in the dialog box that is displayed and click <OK>. Selecting the created folder and then creating another folder by selecting [Actions]-[New Folder] from the Task Scheduler menu allows a further hierarchical level to be added.
Page 102 Point When using the Create Basic Task Wizard, execution for a time interval shorter than one day cannot be set, so once the task has been registered for a different frequency, change the properties. From the Windows [Start] menu, select [Administrative Tools]-[Task Scheduler] to start the Task Scheduler. To manage tasks hierarchically, use the following procedure to create a folder: From the Task Scheduler menu, after selecting Task Scheduler Library, select [Actions]-[New Folder], and then enter a folder name in the dialog box that is displayed and click the <OK>...
Page 103: Restoring The Admin Server
Open the Triggers tab, select the existing trigger, and click the Edit button. Check the [task every:] checkbox in [Advanced settings], and select "1 hour" (set by default). For the [for a duration of], select "1 day" (set by default). Click the OK button.
Page 104: Manager
[Windows Manager] value , specify the number of stored generations that were saved at backup. >Installation_folder\SVROR\Manager\bin\rcxadm imagemgr set -attr vm.snapshot.maxversion=value <RETURN> [Linux Manager] # /opt/FJSVrcvmr/bin/rcxadm imagemgr set -attr vm.snapshot.maxversion=value <RETURN> For details on the rcxadm imagemgr command, refer to "5.9 rcxadm imagemgr" in the "Reference Guide (Command/XML) CE". 10.1.4.3 Starting the Manager Execute the command shown below to start the Manager.
Page 105: Metering
Manager". Changing the Backup Destination Directory This section describes how to change the backup destination directory, based on the example shown below. [Windows Manager] Directory Type Directory Path Before C:\Fujitsu\ROR\RCXCTMG\backup\data change Backup directory After change D:\basebackup Before C:\Fujitsu\ROR\RCXCTMG\backup\wal change WAL save directory...
Page 106 # chown -R rcxctdbdhg:rcxctdbchg /walbackup <RETURN> Copy (move) files from the existing directory to the new directory. [Windows Manager] >xcopy c:\Fujitsu\ROR\RCXCTMG\backup\data\* D:\basebackup\ /E /H /K /X <RETURN> >xcopy c:\Fujitsu\ROR\RCXCTMG\backup\wal\* E:\walbackup\ /E /H /K /X <RETURN> [Linux Manager] # cp -pR /var/opt/FJSVctchg/backup/data/* /basebackup/. <RETURN>...
Page 107 Use "/" as a delimiter. Modify the operational settings file for the online backup. Open the following file: [Windows Manager] Installation_folder\RCXCTMG\bin\conf\ctmgbackup.properties Change as follows: Setting before Change BASE_BACKUP_DIR=C:/Fujitsu/ROR/RCXCTMG/backup/data WAL_ARCHIVE_DIR=C:/Fujitsu/ROR/RCXCTMG//backup/wal Setting after Change BASE_BACKUP_DIR=D:/basebackup WAL_ARCHIVE_DIR=E:/walbackup Point Use "/" as a delimiter.
Page 108: Devices
- firmware_version_number - time .tgz ipcomenv- host_name: Target IPCOM EX series host name firmware_version_number: current firmware version IPCOM EX series number running-config.cli Fujitsu time: The time when backup was performed startup-config.cli Example: ipcomenv-ipcom- E20L10NF0001B01-20120802-103845.tgz IP_address .tgz nsappliance- running-config.cli NS Appliance startup-config.cli...
Page 109: Devices
When performing automatic configuration of network devices When executing the rcxadm netdevice cfbackup command specifying the network device Point When performing the following operation to manage the newest file for the network device, be sure to back up the file for configuration of the network device in the rcxadm netdevice cfbackup command.
Page 110 For details on the rcxadm netdevice command, refer to "3.8 rcxadm netdevice" in the "Reference Guide (Command/XML) CE". - 96 -...
Page 111: Part 4 Monitoring
Part 4 Monitoring Chapter 11 Monitoring Resources........................98 Chapter 12 Collecting Power Consumption Data and Displaying Graphs............112 Chapter 13 Monitoring Resource Pools (Dashboard)...................114 Chapter 14 Monitoring L-Platforms.......................115 Chapter 15 Accounting..........................116 Chapter 16 Monitoring Logs.........................139 - 97 -...
Page 112: Chapter 11 Monitoring Resources
Chapter 11 Monitoring Resources This chapter explains how to monitor the configuration and status of managed resources. 11.1 Overview Resource Orchestrator can centrally monitor the configuration and status of servers or other managed resources directly from the ROR console. This enables the identification of resources experiencing problems, which reduces the time spent on system maintenance. Moreover, Resource Orchestrator can easily launch external management software to precisely locate faulty parts within a managed resource.
Page 113: Resource Status
Table 11.2 List of Regularly Updated Resources and Their Related Resources Resources Subject to Regular Update Related Resources Data Source Chassis Chassis Server management unit Server ServerView Agents (*2) Physical OS Server Server management unit VM host (*1) Server virtualization software VM guest (*1) LAN switch blade LAN switch blade...
Page 114 Table 11.3 Resource Icons Icon Meaning Server resource Chassis Server Physical OS VM host VM guest LAN switch blade L2 switch Firewall Server load balancer Integrated network device Power monitoring device (*) PDU (*) UPS (*) Management software * Note: Power monitoring devices (PDU or UPS) are not subject to monitoring. The following table shows the status icons used in Resource Orchestrator and their associated meanings.
Page 115 Note On the SPARC Enterprise T series, as statuses cannot be obtained from ILOM using SNMP, only "normal", "stop" or "unknown" statuses are shown, while "warning", "error", and "fatal" statuses cannot be detected. If an SNMP Trap indicating an error is displayed, check the status of the server on ILOM.
Page 116: Failures
For network devices, only "normal" and "unknown" are displayed. 11.3 Addressing Resource Failures This section explains how to address problems like hardware failures that occur in a system. Basic Procedure The following procedure is used to confirm and resolve problems using the ROR console: Confirm the Existence of a Problem For the confirmation method, refer to "11.2 Resource...
Page 117: Locations
Detection of changes in state by software for network management An infrastructure administrator checks the status of the network device and takes corrective action if the problem can be solved. If the problem cannot be solved by the infrastructure administrator, notification of the following information is sent to the network device administrator, requesting solving of the problem.
Page 118: Console
When the network device on which a change in state occurs is something other than a firewall and a server load balancer Confirm the name of the network resource. The name of the network resource can be confirmed in the items of the displayed results of the rcxadm netdevice show command (AllocatedResources[Network]).
Page 119: Confirmation
When the network device on which the change in state has occurred is a server load balancer Confirm the status of the server load balancer. For details on how to confirm the status of the server load balancer, refer to "11.4.3 Server Load Balancer Status Confirmation".
Page 120: Console
Configuration files for interfaces When it is possible that the hardware has failed, in cases where the firewall device status is "unknown" or the link status is "down", unless changed intentionally by the infrastructure administrator. The infrastructure administrator must request confirmation the status from the administrator of the network device, in cases where firewall hardware has not failed.
Page 121: Identified
Confirm the name of the L-Platform using the firewall by checking the items in displayed results of the rcxadm firewall show command (L-Platform Name). Specify the firewall name confirmed in a. as the firewall name to be specified for the name option.
Page 122: 11.4.3.2 When An L-Platform Using A Server Load Balancer Is
Scripts for configurations Parameter files Configuration files for interfaces Further, confirm that the server to be load balanced is operating normally because the problem may be due to an error in the server. It is possible that the hardware has failed, in cases where the server load balancer device status is "unknown" or the link status is "down", unless changed intentionally by the infrastructure administrator.
Page 123: 11.4.4 L2 Switch Status
Identify the L-Platform in use. Confirm the name of the server load balancer allocated using auto-configuration by checking the items displayed in the results for the rcxadm netdevice show command (AllocatedResources[SLB]). Confirm the name of the L-Platform using the server load balancer by checking the items in results displayed for the rcxadm slb show command (L-Platform Name).
Page 124: Devices
Take corrective action based on the results of checked scripts and files. When there are no errors in the scripts or settings in files checked in step 4. Confirm with the administrator of the network device that the L2 switch configuration has not been modified, since an unexpected definition modification may have been made.
Page 125 For EMC CLARiiON storage Refer to the "EMC Navisphere Manager Administrator's Guide". For EMC Symmetrix DMX storage and EMC Symmetrix VMAX storage Refer to the "EMC Navisphere Manager Administrator's Guide". For NetApp storage Refer to the "Data ONTAP Storage Management Guide". - 111 -...
Page 126: Chapter 12 Collecting Power Consumption Data And Displaying Graphs
Chapter 12 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. 12.1 Overview This section details the power consumption data that is collected from registered power monitoring targets.
Page 127: Graphs
Time This column displays the date and time at which each data sample was collected. Within data lines, the entry corresponding to this column is displayed in the following format: " YYYY-MM-DD hh:mm:ss " (" YYYY ": Year, " MM ": Month, " DD ": Date, " hh:mm:ss ": Hours:Minutes:Seconds). The time is displayed according to the time zone set in the admin server operating system.
Page 128: Chapter 13 Monitoring Resource Pools (Dashboard)
Chapter 13 Monitoring Resource Pools (Dashboard) This chapter explains how to monitor resource pools. Use the [Dashboard (Pool Conditions)] tab of the ROR console to monitor the usage status of resource pools allocated to tenants and resource pools of overall systems. For details on the [Dashboard (Pool Conditions)] tab, refer to "Chapter 4 Dashboard (Pool Conditions)"...
Page 129: Chapter 14 Monitoring L-Platforms
Chapter 14 Monitoring L-Platforms This chapter explains how to monitor L-Platforms. The operation status of L-Servers can be monitored from the [Dashboard (System Conditions)] tab on the ROR console. For details on the [Dashboard (System Conditions)] tab, refer to "Chapter 5 Dashboard (System Conditions)" in the "User's Guide for Infrastructure Administrators CE".
Page 130: Chapter 15 Accounting
Chapter 15 Accounting This chapter explains the accounting. 15.1 Overview This section explains an overview of the accounting. This function provides the basis to usage charge corresponding to the L-Platforms used by each tenant. The accounting includes following functions. Manage accounting information of L-Platform templates Add, modify, or delete the accounting information of L-Platform templates.
Page 131: Information
[Management and operation of accounting information by the infrastructure administrator] 1. The infrastructure administrator registers L-Platform template information using the L-Platform management window of the ROR Console. 2. The infrastructure administrator registers the accounting information using the product master maintenance command. Refer to "15.3 Operate Accounting Information"...
Page 132: Master
Note Usage fee (the estimated price) for the L-Platform template will be displayed provided that settings for the estimated price display function are enabled. Refer to "8.7.1 Display Function Settings for Estimated Price" for information on settings for the estimated price display function.
Page 133 the existing disk capacity will be added together in accordance with the number of L-Servers to which the disk is attached. Resource allocation methods differ between extension disks and existing disks. For this reason, the storage pool used for an existing disk should not be the same as one used for an extension disk.
Page 134 L-Platform usage fee (the estimated price) = monthly template price + monthly price for all L-Server + monthly price for all system disks + monthly price for all data disks Template monthly price = template unit price * converted monthly price Virtual L-Server monthly price = image unit price * converted monthly converted +(CPU unit price * monthly converted price + CPU clock unit price * CPU clocks * converted monthly price) * number of CPUs...
Page 135: Format
Physical L-Server monthly price = image unit price * converted monthly converted +(CPU unit price * monthly converted price + CPU clock unit price * CPU clocks * converted monthly price) * number of CPUs + memory unit price * amount of memory * converted monthly price System disk monthly price = system disk unit price * amount of disk * monthly converted price Data disk monthly price = data disk unit price * amount of disk * monthly converted price - If the price is hourly basis, usage fee (the estimated price) is calculated for 24 hours * 30 days.
Page 136 Name Omit Explanation memory: memory capacity vm: virtual L-Server pm: physical L-Server sys_disk: system disk capacity disk: extension disk capacity template: template Resource identifier Specify information to identify the accounting target resource with 128 or less alphanumeric characters. Resource identifiers vary by the category. (*2) cpu, cpu_clock, memory: VM pool name or sever pool name vm: virtual L-Server image name pm: physical L-Server image name...
Page 137 The unit price for product ID "ME-0001" is $1.00 on 2011-08-15 because data B has higher priority even though both data A and data B are in the applicable period. An example description of accounting information file "ME-0001",0,"2012-01-01T00:00:00.000+0900",,"memory","/VMPool","month",200,"Standard memory","Standard memory" "ME-0001",1,"2012-08-01T00:00:00.000+0900","2012-08-31T23:59:59.999+0900","memory","/ VMPool","month",100,"Standard memory(Campaign)","Standard memory(Campaign)"...
Page 138: Information
</vdisk> </vdisks> <image> <imageName>image1</imageName> </image> </server> </servers> </template> </templates> Example description of accounting information file "TP-0001",0,"2012-01-01T00:00:00.000+0900",,"template","templateId1","month",1000,"Web/DB Windows Server 2008 R2 Standard","Service Windows Server 2008 R2 Standard" "VM-0001",0,"2012-01-01T00:00:00.000+0900",,"vm","image1","month",500,"Windows Server 2008 R2 Standard","VM Windows Server 2008 R2 Standard" "CP-0001",0,"2012-01-01T00:00:00.000+0900",,"cpu","/VMHostPool","month",100,"Xeon5110","Xeon5110" "CL-0001",0,"2012-01-01T00:00:00.000+0900",,"cpu_clock","/VMHostPool","month", 50,"Xeon5110","Xeon5110" "ME-0001",0,"2012-01-01T00:00:00.000+0900",,"memory","/VMHostPool","month",200,"Standard memory","Standard memory"...
Page 139: Information
It is also possible to modify accounting information for L-Servers that were imported into the system. Refer to "15.3.2 Modify Accounting Information" for information on how to modify the accounting information. Delete accounting information Delete the accounting information if the following conditions are met. The L-Platform templates are disabled.
Page 140 Enable the L-Platform template. Enable the L-Platform template on the start of applicable date. Refer to "8.3.6 Publishing and Hiding L-Platform Template" in the "User's Guide for Infrastructure Administrators CE" for information on how to enable the L-Platform templates. Registering Accounting Information for L-Servers imported into the System Use the following procedures to import an L-Server into the system and register accounting information for the imported L-Server.
Page 141: Information
15.3.2 Modify Accounting Information Modify the accounting information of the L-Platform templates that are already enabled. This corresponds to the case of raising the price or setting limited time price for campaign. It is also possible to modify accounting information for L-Servers imported into the system. Follow the procedures below to modify accounting information for either L-Platform templates registered in the product master or L- Servers imported into the system.
Page 142: Information
- Priority: Higher priority than the existing data A - Unit price: New unit price - Start of applicable date: Start date of the period - End of applicable date: End date of the period Refer to "15.2.2 Accounting Information File Format"...
Page 143: Information
Check Metering Log Check that the log that shows the usage result of the corresponding L-Platform templates does not exist in the metering log. Output the metering log by the output metering logs command to check that no resource identifiers corresponding to the category code of that accounting information and no information for the item ID corresponding to that exists in the metering log.
Page 144: Charges
(Product Master Maintenance)" in the "Reference Guide (Command/XML) CE" for information on the output function of the product master maintenance command. Reference the output accounting information file. Reference the accounting information file that was output by the output function of the product master maintenance command. Refer to "15.2.2 Accounting Information File Format"...
Page 145: Times
15.4.3 How to Charge for Resources Resources can be charged by a fixed rate or by the amount used. With fixed charging, the usage charges are charged according to a fixed fee rather than the usage time of the resources. With charging by the amount used, the usage charges are charged according to the usage time of the resources.
Page 146: Calculation
Point Usage Charges for physical L-Servers. The calculation of Usage Charges for the CPU, CPU clock, and memory capacity of the physical L-Server are calculated using the values input into the L-Platform Management window (input value). Also, a server that is close to the input value in the specified server pool will be deployed as the physical L-Server.
Page 147 Resource Resource identifier Unit codes Unit price /VMPool hour $0.001 cpu_clock /VMPool hour $0.002 memory /VMPool hour $0.001 sys_disk /StoragePool hour $0.001 disk /StoragePool hour $0.002 Operation Operations on the L-Platform are as follows: Date/time Operation 2012-07-01 10:10:00 Deploy L-Platform 1 2012-07-01 10:11:00 Start L-Server 2012-07-02 18:10:00...
Page 148 Point Fractions in usage charges When the calculations of usage charge produce a figure that includes fractions less than the lowest unit in the currency, the remainder is rounded off. - 134 -...
Page 149: File
L-Platform transfers When an L-Platform is moved, the usage charges for resources charged by amount are divided between the departure tenant and destination tenant, according to the amounts used. When resources are charged by a fixed amount, the departure tenant is billed. 15.4.6 Sending Usage charges The usage charges for the previous month confirmed the day after the cut-off date are attached as a usage charge file and sent to the email address.
Page 150: Usage Charge Detail File
Item Description Format:ZZZZZZZZZZZ9 (*2) Example:800 FileVersion This is the version of the file. Fixed as 1.0. LplatformId This is the L-Platform ID. (*1) LplatformName This is the L-Platform name. (*1) LplatformDeletedDate Date that the L-Platform was returned. Output only if the L-Platform has already been returned. Empty string is output if this has not been returned.
Page 151 Item Description ChargeAmount The amount of usage charges for each L-Platform. The amounts are values, so they are not enclosed with double-quotes ("). Format:ZZZZZZZZZZZ9 (*1) Example:1000 FileVersion This is the version of the file. Fixed as 1.0. ItemColumn1 This is a breakdown (item 1). The template name, virtual L-Server name, or physical L-Server name is output.
Page 152 "","","","","","","",,"","Physical server(pserverA)","CPU","/ServerPool","1core, 10GHz","\1.6667,\0.5560/h","18h",26 "","","","","","","",,"","Physical server(pserverA)","Memory capacity","/ ServerPool","10GB","\20.0000/h","18h",360 "","","","","","","",,"","Physical server(pserverA)","Disk Capacity(system disk)","/ StragePool","10GB","\8.0000/h","18h",144 "","","","","","","",,"","Physical server(pserverA)","Disk Capacity","/StragePool2","10GB","\9.0000/ h","2h",18 "","","","","","","",,"","Physical server(pserverA)","Disk Capacity","/StragePool3","10GB","\9.7230/ h","6h",59 - 138 -...
Page 153: Chapter 16 Monitoring Logs
Chapter 16 Monitoring Logs This chapter explains how to monitor logs. 16.1 Operation Logs This section explains the operation logs of Resource Orchestrator. Note Operation logs should be used by only infrastructure administrators or administrators, as all user operations of Resource Orchestrator can be viewed.
Page 154 Element Name Description Remarks Operation_identifier ) Starting( End of operations Operation_identifier ) Completed( Errors during operations Error( Operation_identifier ) A resource name and a resource identifier are output in the following format: Resource Resource name Resource_name )" "Resource identifier( The parameters received by the manager are output. Event Operations For the information that will be output, refer to...
Page 155 2011-03-10 23:42:37.171 admin 10.20.30.53 Starting(BX620-1_40) BX620-1_578(image_test) server_images destroy 2011-03-10 23:42:47.460 admin 10.20.30.53 Completed(BX620-1_40) BX620-1_578(image_test) server_images destroy 2011-03-10 23:51:06.620 userA groupA 127.0.0.1 Starting(BX620-1_41) BX620-1_806(LS_RT_A001) l_servers create 2011-03-10 23:53:06.437 userA groupA 127.0.0.1 Completed(BX620-1_41) BX620-1_806(LS_RT_A001) l_servers create 2011-03-10 23:53:39.265 userA groupA 127.0.0.1 Starting(BX620-1_42) BX620-1_806(LS_RT_A001) l_servers start 2011-03-10 23:54:26.640...
Page 156: Usage Method
16.1.2 Usage Method This section explains the methods for configuring and operating operation logs. Perform the following procedure: Disk space estimation Infrastructure administrator (infra_admin) estimates the disk size to use for storing operation logs. Estimate the amount of disk space using the following formula, and then decide the number of days to retain operation logs. Number_of_operations_of_the_resource_in_1_day ) * ( Number_of_target_resources ) * 1(KB)} * retention_period) Example...
Page 157: Retention
16.1.3 Retention This section explains the retention of operation logs. Periodic deletion Due to extended periods of operation or modification of retention periods, operation logs which have exceeded a certain retention period are periodically deleted. The timing of deletion (based on retention period checks) is set to take place as the first operation after the date changes. Note The recording period is the retention period + 1.
Page 158: Scope Of Operations Recorded In Operation Logs
Performing this procedure resets the recording period of operation logs to 0. 16.1.4 Scope of Operations Recorded in Operation Logs The scope of operations recorded in operation logs and the character strings displayed in the Event column are as indicated below. Table 16.1 Scope of Operations Resource Type Action...
Page 159 The file name, file size, and number of generations of the audit log are shown below: Number of Log name Description File size generations vsys_audit_log Audit logs are output to this log. 10 MB generations * Note: If the number of saved generations exceeds 10 generations, old generations will be deleted, starting with the oldest generation. The file size and the number of generations to be saved can be changed.
Page 160 Item Description operation result "SUCCESS" if the operation was successful and "FAILURE" if the operation failed. * Note: The operation types are as follows: Operation type Description AccessControl#evaluate Checking access permissions. AccessControl#getAuthority Obtaining information about resource operation privileges for a user. DeployMaster#delete Deleting configuration information.
Page 161 Operation type Description Templates#getDetail Obtaining detailed L-Platform template information. Templates#importPublic Registering L-Platform template information. Templates#search Searching an L-Platform template. Templates#updatePublic Updating templates VDisk#getList Obtaining a list of existing disks. VServer#addPatch Registering patch information. VServer#attach Adding an expansion disk. VServer#backup Creating a snapshot. VServer#cancelError Releasing the error status of snapshots or restorations.
Page 162 Operation type Description VSYS#flowRejectApplication Rejecting deployment application. VSYS#flowRelease Returning all L-Platforms as a batch. (For flows: no operation after authorization.) VSYS#flowReleaseApplication Applying to return an L-Platform. VSYS#flowReleaseForward Setting the status of a return application to "forwarding complete". VSYS#flowSaveCancel Canceling the application to deploy an L-Platform or change a configuration. VSYS#flowUpdate Reconfiguring an L-Platform.
Page 163 The following table shows the settings file and the location to change: [Windows Manager] Log name Settings file Location to change (one location) vsys_audit_log Installation_folder \RCXCFMG\config <param name="File" value="C:\ProgramData \vsys_log4j.xml \Fujitsu\SystemwalkerCF-MG\logs \vsys_audit_log" /> [Linux Manager] Log name Settings file Location to change (one location) vsys_audit_log /etc/opt/FJSVcfmg/config/ <param name="File" value="/var/opt/FJSVcfmg/ vsys_log4j.xml...
Page 164: Audit Logs Of Output By The Tenant Management, Accounting, Access Control And System Condition
Log name Settings file Location to change (one location) Example: value="100MB" (to change the size of the audit log file to 100 MB) Restart the manager. Refer to "2.1 Starting and Stopping the Manager" for information on how to Restart the manager. Procedure for changing the number of generations to be saved Use the following procedure to change the number of audit log generations to be saved.
Page 165 [Linux Manager] /opt/fujitsu/ServerViewSuite/opends/logs/access Refer to the OpenDS website for details on OpenDS access logs. URL: https://docs.opends.org/2.2/page/DefAccessLog (As of February2012) Output format Audit logs are CSV files where the following items are output in the following order: Output format operation date/time , user ID , tenant name , operation type , operation information , operation result...
Page 166 Function Output file Accounting [Windows Manager] (GUI operations from Installation_folder \RCXCTMG\Charging\log\charging_audit.log the ROR Console) [Linux Manager] /var/opt/FJSVctchg/log/charging_audit.log Accounting [Windows Manager] (Published API Installation_folder \RCXCTMG\Charging\log\accounting_audit.log operation) [Linux Manager /var/opt/FJSVctchg/log/accounting_audit.log Access Control [Windows Manager] Installation_folder \RCXCTMG\SecurityManagement\log\ctac_audit.log [Linux Manager] /var/opt/FJSVctsec/log/ctac_audit.log System condition [Windows Manager] Installation_folder \SWRBAM\CMDB\FJSVcmdbm\var\log\audit\uigui\cmdb_audit.log [Linux Manager] /opt/FJSVcmdbm/var/log/audit/uigui/cmdb_audit.log...
Page 167 Operation information (*1) Tenant registUser Notify user "mail=""xxx@com""" management registration (GUI createUser Create users "userid=""< user ID of the user created >""&mail=""xxx@com"" operations last name >""&firstname=""< first name > &lastname=""< from the ""&auth=""tenant_admin|tenant_operator|tenant_monitor| tenant_user"" Console) &explanation=""xxxx""&corporatename=""fujitsu"" &emergencymail=""yyy@com""&emergencytel=""0000""" - 153 -...
Page 168 ID of the user updated >""&mail=""xxx@com"" updateUser Update user "userid=""< last name >""&firstname=""< first name >""" information &lastname=""< &auth=""infra_admin|infra_operator|administrator|monitor| operator|tenant_admin|tenant_operator|tenant_monitor| tenant_user"" &explanation=""xxxx""&corporatename=""fujitsu"" &emergencymail=""yyy@com""&emergencytel=""0000""" listUser Get a list of user None. information user ID of the user that has been moveUser Relocate users "userid=""<...
Page 169 None. information user ID of the user created >""&mail=""xxx@com"" Tenant createUser Create users "userid=""< management &lastname=""< last name >""&firstname=""< first (creating name >""""&auth=""tenant_user"" users from &explanation=""xxxx""&corporatename=""fujitsu"" the ROR &emergencymail=""yyy@com""&emergencytel=""0000""" Console: Provisional account registration method) Accounting updatePMaster Update product None. master...
Page 170: Application Process Audit Log
Function Operation type Content Operation information (*1) registerUsagePoi Register usage "date=""< date of data registered >(*5)""&id=""< L-Platform ID >""&name=""< L-Platform name >""&tenantname=""< tenant frequency (*4) name of managed tenant >""&tenantdeletedate=""< date when managed tenant was deleted >(*6)""" getDailyCharge Get daily usage None.
Page 171 Installation_folder\SWRBAM\bin\swrba_audit The process instance audit information that can be obtained will be the process instance information that was complete after the command was executed the previous time. Privilege Required/Execution Environment [Windows Manager] Administrator privileges are required. If the operating system is Windows Server 2008, execute as the administrator. This command can be executed on the admin server.
Page 172 Item Description Process instance name Process instance name L-PlatformSubscription_xxx,L-PlatformChange_xxx,L-PlatformUnsubscription_xxx State of process instance State of process instance closed: Closed Process instance end time Time that the process instance ended yyyy-mm-dd hh:mm:ss.sss Activity name Activity name Application,Approve,Assess,Pending state,Cancel Task execution date/time The date/time the task was executed Person responsible User ID of the user that executed the task...
Page 173: Operation Logs (Activity)
16.3 Operation Logs (Activity) This section explains operation logs. Operation logs are used as maintenance information when investigating and dealing with errors. 16.3.1 Operation Logs for Accounting The following table shows the files where operation logs used for maintenance information accounting are output: Copy the files described below to collect maintenance information.
Page 174 Rewrite the settings files corresponding to each log. The following table shows the settings file and the location to change: [Windows Manager] Log name Settings file Location to change (one location) Installation_folder \RCXCFMG\config vsys_trace_log <param name="File" value="C:\ProgramData \vsys_log4j.xml \Fujitsu\SystemwalkerCF-MG\logs \vsys_trace_log" /> - 160 -...
Page 175 Settings file Location to change (one location) vsys_batch_log Installation_folder \RCXCFMG\config <param name="File" value="C:\ProgramData \batch_log4j.xml \Fujitsu\SystemwalkerCF-MG\logs \vsys_batch_log" /> myportal_trace.log Installation_folder \RCXCTMG <param name="file" value=" C:/Fujitsu/ROR/ \MyPortal\config RCXCTMG/MyPortal/log/myportal_trace.log" /> \managerview_log4j.xml cfmg_api_log Installation_folder \RCXCFMG\config <param name="file" value="C:\ProgramData \api_log4j.xml \Fujitsu\SystemwalkerCF-MG\logs \cfmg_api_log" /> [Linux Manager]...
Page 176: Part 5 High Availability And Disaster Recovery
Part 5 High Availability and Disaster Recovery Chapter 17 High Availability of Managed Resources...................163 Chapter 18 Disaster Recovery........................177 - 162 -...
Page 177: Chapter 17 High Availability Of Managed Resources
Chapter 17 High Availability of Managed Resources This chapter explains failover. 17.1 High Availability of Managed Resources This section explains how to realize high availability of managed resources. The methods of environment creation and operation for enabling higher availability of managed resources vary depending on resources involved.
Page 178 Number of NICs Check the number of NICs mounted on a compatible server and L-Server. A server is considered as a server satisfying the conditions, in the following cases: The number of NICs mounted on the compatible server is the same as the number in the L-Server definition The number is more than the number in the L-Server definition Selection of Suitable Spare Servers When the [Use a low spec server] checkbox is not selected, a spare server is automatically set.
Page 179 Definition File Format For the definition file, write each line in the following format: Key = Value When adding comments, start with a number sign ("#"). Definition File Items Specify the following items in a definition file. Table 17.1 List of Items Specified in Definition Files for Checking Spare Server Models and Configurations Item Value Remarks...
Page 180: Blade Chassis High Availability
| error OVERALL_POLICY=skip # Server model compatibility list SPARE_SVR_COMPAT0=["BX920 S1", "BX920 S2"] 17.1.2 Blade Chassis High Availability This section explains high availability for when operating L-Servers on blade servers. When the server is a physical L-Server for a blade server, this function which enables restarting of L-Servers, by manually switching over servers to spare servers when there are blade servers are specified as spare servers on other chassis.
Page 181 To initialize the management blade, select "controlled by VIOM" in the management window of the management blade. After performing the configuration to forcibly reset the local VIOM settings on the displayed screen, restart the management board. In either case, if any concerns arise, contact Fujitsu technical staff. Mount a blade on the chassis.
Page 182: High Availability For Storage Chassis
Start the L-Server. For details on how to start an L-Server, refer to "17.1.1 Starting an L-Server" in the "User's Guide for Infrastructure Administrators (Resource Management) CE". 17.1.3 High Availability for Storage Chassis This section explains high availability of storage chassis connected to physical L-Servers. If performing replication between two storage units of LUNs used by a physical L-Server, quick restoration of physical L-Servers is possible, even when storage units have failed.
Page 183 Replication Definition Files The replication definition file must be created in advance. In the replication definition file, describe the relationship between the operating storage and the standby storage for replication. The format of the replication definition file is as follows: IP_address_of_operating_storage_unit , Operating_volume_identifier , IP_address_of_standby_storage_unit , Standby_volume_identifier Configure the definition file using a unique combination of an IP address for an operating or standby storage unit, and an identifier for an operating or standby volume.
Page 184 L-Server targeted by the failover script. To forcibly stop the server without shutting down the operating system running on the L- Server, specify the -force option when executing the physical L-Server stopping script. If an error occurs during execution of the script, contact Fujitsu technical staff. Note Physical L-Servers are stopped in the order of the entries in the physical L-Server stopping script.
Page 185 Execute the physical L-Server startup script on the server where the manager is being operated. This operation starts the physical L-Server. If an error occurs during execution of the script, contact Fujitsu technical staff. Note Physical L-Servers are started in the order of the entries in the physical L-Server startup script. When the specification of the order of starting physical L-Servers is necessary, edit the physical L-Server startup script.
Page 186 L-Server targeted by the failback script. To forcibly stop the server without shutting down the operating system running on the L- Server, specify the -force option when executing the physical L-Server stopping script. If an error occurs during execution of the script, contact Fujitsu technical staff. Note Physical L-Servers are stopped in the order of the entries in the physical L-Server stopping script.
Page 187: High Availability For Admin Servers
When operating an L-Platform, use the cfmg_syncdiskinfo command to reflect the information for switched disks on the L-Platform configuration information. [Windows Manager] Installation_folder \RCXCFMG\bin\cfmg_syncdiskinfo <RETURN> > [Linux Manager] # /opt/FJSVcfmg/bin/cfmg_syncdiskinfo <RETURN> For details on the cfmg_syncdiskinfo command, refer to "10.7 cfmg_syncdiskinfo (disk information synchronization)" in the "Reference Guide (Command/XML) CE".
Page 188 Manager High Availability in Windows Guest Environments in Hyper-V environments Install an operating system and configure a domain controller on the domain controller server. Perform installation and configuration of the admin server. The following operations are necessary: Primary Node Connection with shared storage Configure BIOS Install Hyper-V roles Install and configure EMC Solutions Enabler (when used)
Page 189 VM guest, ETERNUS may not be able to return from the status of processing to normal status. In this case, to restore, forcibly log on from ETERNUSmgr, then log off. In the case of ETERNUS DX60/DX80/DX90, contact Fujitsu technical staff. For details on how to restore ETERNUS, refer to the ETERNUS manual.
Page 190 ETERNUS may not be able to return from the status of processing to normal status. In this case, to restore, forcibly log on from ETERNUSmgr, then log off. In the case of ETERNUS DX60/DX80/DX90, contact Fujitsu technical staff. For details on how to restore ETERNUS, refer to the ETERNUS manual.
Page 191: Chapter 18 Disaster Recovery
Chapter 18 Disaster Recovery This chapter provides information on Disaster Recovery for the admin server where Resource Orchestrator manager operates. Resource Orchestrator provides simple and highly reliable Disaster Recovery, through exporting and importing the following information that Resource Orchestrator manager handles: L-Platform Templates L-Platform Configuration Information Resource Information...
Page 192 Appendix A Notes on Operating ServerView Resource Orchestrator This appendix provides important reminders for the operation of Resource Orchestrator. Redundancy Configurations for the Admin LAN If communication issues occur on the admin LAN, or one of the network interfaces used by a managed server on the admin LAN fails, the following operations may result in errors.
Page 193 Parameter Meaning Initial Value When restarting Specify "true". When not restarting Specify "false". RESTART_HOUR Specify the restart time (hour) from 0 to 23. RESTART_MIN Specify the restart time (minutes) from 0 to 59. RESTART_CYCLE Specify the restart interval (days) from 1 to 5. Parameter Change Procedure Stop the manager.
Page 194 Place the shared disk of the manager online. Place other cluster resources offline. Change the TASK_WORKER_COUNT values for rcx_base.rcxprop files on the shared disk. When there is no rcx_base.rcxprop file, create one. Drive_name \Fujitsu\ROR\SVROR\customize_data\rcx_base.rcxprop Start the manager. [Linux Manager] Stop the manager.
Page 195 Multiplicity Increase in Memory Use (Unit: MB) 6 - 14 1080 + ( Multiplicity * 40) Multiplicity * 40) 15 - 30 2104 + ( - 181 -...
Page 196: Appendix B Metering Log
Appendix B Metering Log This chapter explains the metering log. Metering logs is saved in the database as Information based on bill calculations so that fees can be charged based on the resources that have been used by tenants. The Output metering log command is used to output metering logs to metering log files. Refer to "11.2 ctchg_getmeterlog (Output Metering Logs)"...
Page 197: B.2 Output Contents Of Metering Logs
Event Event identifier Timing of event Resource L-Platform template (*2) Software *1: If the timing of output of the periodic log is to be changed, overwrite the metering log operational settings file and then execute the Change periodic log schedule settings command. Refer to "8.7.3 Metering Log Settings"...
Page 198 Item ID Output for each event Item name Description CHAN DELET START STOP PERIO event Event ADD: Deploy CHANGE: Change DELETE: Delete START: Start STOP: Stop PERIOD: Period resource_type Configured vsys: L-Platform resource type vserver: Virtual L-Server pserver: Physical L-Server vdisk: Expansion disk template: L-Platform template...
Page 199 Item ID Output for each event Item name Description CHAN DELE STAR STOP PERIO vsys_id L-Platform ID ASCII: 1 to 32 characters ID identifying the L-Platform server_id L-Server ID ASCII: 1 to 64 characters ID identifying the L-Server system_name L-Platform UTF-8: 1 to 256 characters name Name of the L-Platform...
Page 200 Item ID Output for each event Item name Description CHAN DELET START STOP PERIO org_id Tenant name ASCII: 1 to 32 characters Name of the tenant user_id User account ASCII: 1 to 32 characters User that owns the L- Platform vsys_id L-Platform ID ASCII: 1 to 32 characters...
Page 201 Disk In addition to the common items output, the following items will be output: Item ID Output for each event Item name Description CHANGE DELETE PERIOD org_id Tenant name ASCII: 1 to 32 characters Name of the tenant user_id User account ASCII: 1 to 32 characters User that owns the L- Platform...
Page 202: B.3 Formats Of Metering Log Files
Item ID Output for each event Item name Description CHANGE DELETE PERIOD org_id Tenant name ASCII: 1 to 32 characters Name of the tenant user_id User account ASCII: 1 to 32 characters User that owns the L- Platform vsys_id L-Platform ID ASCII: 1 to 32 characters ID identifying the L-Platform server_id...
Page 203 Item ID Item name Data type status Status String user_id User account String server_id L-Server ID String disk_id Disk ID String software_id Software ID String system_name L-Platform name String server_name L-Server name String disk_name Disk name String template_id Template ID String Reserved base_template_id...
Page 204 verId001","","softwareId001","systemName001","","","","","","","",,"",,,,,,,,,,, 2.0,"2011-08-08T10:20:10.000+0900","","vsysId001","orgId001","PERIOD","vserver","RUNNING","userId001 ","serverId001","","","systemName001","serverName002","","","","","imageInfoName001","/ StoragePool002",100,"/VMPool001",2,30,60,10,50,serverType001,,,,, 2.0,"2011-08-08T10:20:10.000+0900","","vsysId001","orgId001","PERIOD","vdisk","","userId001","server Id001","diskId001","","systemName001","","diskName001","","","","","/StoragePool002", 200,"",,,,,,,,,,, 2.0,"2011-08-08T10:20:10.000+0900","","vsysId001","orgId001","PERIOD","vsys","","userId001","","","" ,"systemName001","","","","","baseTemplateId001","","",,"",,,,,,,,,,, XML format files The format of XML format files is as follows: <?xml version="1.0" encoding="UTF-8"?> <meterlog> <entry><Item ID>Value</Item ID>...</entry> <entry><Item ID>Value</Item ID>...</entry> </meterlog> The first row of the CSV format corresponds to the <entry> element. The first column of the CSV format corresponds to the <Item ID>...
Page 205: B.4 Deleting Metering Logs
If snapshot restore has been performed, an event log with CHANGE as the event will be output even if there was no change. At execution of the Import L-Server command of the L-Platform Management function, the following event log will be output: If a stopped L-Server has been imported Event log with ADD as the event If an active L-Server has been imported...
Page 206: Glossary
Glossary access path A logical path configured to enable access to storage volumes from servers. active mode The state where a managed server is performing operations. Managed servers must be in active mode in order to use Auto-Recovery. Move managed servers to maintenance mode in order to perform backup or restoration of system images, or collection or deployment of cloning images.
Page 207 Auto-Recovery A function which continues operations by automatically switching over the system image of a failed server to a spare server and restarting it in the event of server failure. This function can be used when managed servers are in a local boot configuration, SAN boot configuration, or a configuration such as iSCSI boot where booting is performed from a disk on a network.
Page 208 CCM (ETERNUS SF AdvancedCopy Manager Copy Control Module) This is a module that does not require installation of the ETERNUS SF AdvancedCopy Manager agent on the server that is the source of the backup, but rather uses the advanced copy feature of the ETERNUS disk array to make backups. chassis A chassis used to house server blades and partitions.
Page 209 end host mode This is a mode where the uplink port that can communicate with a downlink port is fixed at one, and communication between uplink ports is blocked. environmental data Measured data regarding the external environments of servers managed using Resource Orchestrator. Measured data includes power data collected from power monitoring targets.
Page 210 A Solaris environment that has been installed on a physical server. GLS (Global Link Services) Fujitsu network control software that enables high availability networks through the redundancy of network transmission channels. GSPB (Giga-LAN SAS and PCI_Box Interface Board) A board which mounts onboard I/O for two partitions and a PCIe (PCI Express) interface for a PCI box.
Page 211 The IPCOM EX IN series fits into this category. I/O virtualization option An optional product that is necessary to provide I/O virtualization. The WWNN address and MAC address provided is guaranteed by Fujitsu Limited to be unique. Necessary when using HBA address rename. IPMI (Intelligent Platform Management Interface) IPMI is a set of common interfaces for the hardware that is used to monitor the physical conditions of servers, such as temperature, power voltage, cooling fans, power supply, and chassis.
Page 212 iSCSI storage Storage that uses an iSCSI connection. LAG (Link Aggregation Group) A single logical port created from multiple physical ports using link aggregation. LAN switch blades A LAN switch that is mounted in the chassis of a blade server. LDAP (Lightweight Directory Access Protocol) A protocol used for accessing Internet standard directories operated using TCP/IP.
Page 213 LUN (Logical Unit Number) A logical unit defined in the channel adapter of a storage unit. MAC address (Media Access Control address) A unique identifier that is assigned to Ethernet cards (hardware). Also referred to as a physical address. Transmission of data is performed based on this identifier. Described using a combination of the unique identifying numbers managed by/assigned to each maker by the IEEE, and the numbers that each maker assigns to their hardware.
Page 214 Cold migration Migration of an inactive (powered-off) VM guest. Live migration Migration of an active (powered-on) VM guest. multi-slot server A server that occupies multiple slots. NAS (Network Attached Storage) A collective term for storage that is directly connected to a LAN. network device The unit used for registration of network devices.
Page 215 The OS used by an operating server (a physical OS or VM guest). overcommit A function to virtually allocate more resources than the actual amount of resources (CPUs and memory) of a server. This function is used to enable allocation of more disk resources than are mounted in the target server. PDU (Power Distribution Unit) A device for distributing power (such as a power strip).
Page 216 Each RDN must be unique within the same entry. Remote Management Controller A unit used for managing servers. Used for gathering server data, failure notification, power control, etc. For Fujitsu PRIMERGY servers iRMC2 For SPARC Servers/SPARC Enterprises ILOM (T series servers)
Page 217 For Dell/IBM servers BMC (Baseboard Management Controller) Remote Server Management A PRIMEQUEST feature for managing partitions. Reserved SB Indicates the new system board that will be embedded to replace a failed system board if the hardware of a system board embedded in a partition fails and it is necessary to disconnect the failed system board.
Page 218 The script lists contain the scripts used to perform automatic configuration. There are the following eight types of script lists: script lists for setup script lists for setup error recovery script lists for modification script lists for modification error recovery script lists for setup (physical server added) script lists for setup error recovery (physical server added) script lists for deletion (physical server deleted)
Page 219 ServerView Update Manager Express Insert the ServerView Suite DVD1 or ServerView Suite Update DVD into the server requiring updating and start it. This is software that performs batch updates of BIOS, firmware, drivers, and hardware monitoring software. Single Sign-On A system among external software which can be used without login operations, after authentication is executed once. slave slot A slot that is not recognized as a server when a server that occupies multiple slots is mounted.
Page 220 switchover state The state in which switchover has been performed on a managed server, but neither failback nor continuation have been performed. system administrator The administrator who manages the entire system. They perform pre-configuration and installation of Resource Orchestrator. Administrator privileges for the operating system are required. Normally the roles of the infrastructure administrator and system administrator are performed concurrently.
Page 221 Example \\hostname\dir_name UPS (Uninterruptible Power Supply) A device containing rechargeable batteries that temporarily provides power to computers and peripheral devices in the event of power failures. Resource Orchestrator uses UPSs with current value display functions as power monitoring devices. URL (Uniform Resource Locator) The notational method used for indicating the location of information on the Internet.
Page 222 Using a Virtual LAN, network configuration can be performed freely without the need for modification of the physical network configuration. VLAN ID A number (between 1 and 4,095) used to identify VLANs. Null values are reserved for priority tagged frames, and 4,096 (FFF in hexadecimal) is reserved for mounting. VM (Virtual Machine) A virtual computer that operates on a VM host.
Page 223 WWNN (World Wide Node Name) A name that is set as a common value for the Fibre Channel ports of a node. However, the definitions of nodes vary between manufacturers, and may also indicate devices or adapters. Also referred to as a node WWN. WWPN (World Wide Port Name) A name that is a unique value and is set for each Fibre Channel port (HBA, CA, fibre channel switch ports, etc.), and is the IEEE global MAC address.

Fujitsu ServerView Resource Orchestrator Cloud Edition V3.1.1 Operation Manual

Table of Contents

Chapter 1 Overview of Operations, Maintenance, and Monitoring

Part 2 Operation

Chapter 2 Starting and Stopping Managers and Agents

Chapter 3 Managing User Accounts

Chapter 4 Managing Tenants

Chapter 5 Managing Templates

Chapter 6 Managing Resources and Resource Pools

Chapter 7 Management of L-Platform

Chapter 8 Changing Settings

Chapter 9 Hardware Maintenance

Chapter 10 Backup and Restoration

Appendix A Notes on Operating Serverview Resource Orchestrator

Part 4 Monitoring

Chapter 11 Monitoring Resources

Chapter 12 Collecting Power Consumption Data and Displaying Graphs

Chapter 13 Monitoring Resource Pools (Dashboard)

Chapter 14 Monitoring L-Platforms

Chapter 15 Accounting

Chapter 16 Monitoring Logs

Chapter 17 High Availability of Managed Resources

Chapter 18 Disaster Recovery

Appendix B Metering Log

Quick Links

Operation Guide

Chapters

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

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

Table of Contents