Fujitsu J2X1-7611-03ENZ0 User Manual
ServerView Resource Orchestrator
Cloud Edition V3.1.0
Operation Guide
Windows/Linux
J2X1-7611-03ENZ0(00)
October 2012
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
Infrastructure monitor
Tenant operator
Tenant monitor
(Dual-Role) Administrator
(Dual-Role) Operator
(Dual-Role) Monitor
For information about the documents for Resource Orchestrator, refer to "Chapter 1 Documentation Road Map" in the "Quick Start Guide
CE".
Infrastructure administrator
Tenant administrator
Infrastructure administrator and Tenant administrator
- i -
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. Additionally, a basic understanding of directory services such as Active Directory and
LDAP is necessary.
Organization
This manual is composed as follows:
Section 1 Overview
Chapter 1 Overview of Operations, Maintenance, and Monitoring
Provides an overview of the operation, maintenance, and monitoring of Resource Orchestrator.
Section 2 Operation
Chapter 2 Starting and Stopping Managers and Agents
Explains the methods for deliberately starting and stopping managers and agents.
Chapter 3 Managing User Accounts
Explains the management of user accounts.
Chapter 4 Managing Tenants
Explains the management of tenants.
Chapter 5 Managing Templates
Explains the management of templates.
Chapter 6 Managing Resources and Resource Pools
Explains the management of resources and resource pools.
Chapter 7 Management of L-Platform
Explains the management of L-Platforms.
Chapter 8 Changing Settings
Explains how to modify various setting information.
Section 3 Maintenance
Chapter 9 Hardware Maintenance
Explains the maintenance of hardware.
10.1 Backup and Restoration of Admin Servers
Explains how to use the backup and restore provided by Resource Orchestrator.
Section 4 Monitoring
Chapter 11 Monitoring Resources
Explains how to monitor the configuration and status of managed resources.
- ii -
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.
Chapter 14 Monitoring L-Platforms
Explains the monitoring of L-Platforms.
Chapter 15 Accounting
Explains charging.
Chapter 16 Monitoring Logs
Explains the monitoring of logs.
Section 5 High Availability
Chapter 17 High Availability of Managed Resources
Explains failover.
Chapter 18 Disaster Recovery
Explains the Disaster Recovery function for L-Servers.
Appendix A Notes on Operating ServerView Resource Orchestrator
Gives important reminders for the operation of Resource Orchestrator.
Appendix B Metering Log
Explains metering logs.
Glossary
Explains the terms used in this manual. Please refer to it when necessary.
Notational Conventions
The notation in this manual conforms to the following conventions.
- When using Resource Orchestrator and the functions necessary differ due to the necessary basic software (OS), it is indicated as
follows:
[Windows Manager]
[Linux Manager] Sections related to Linux manager
[Windows] Sections related to Windows (When not using Hyper-V)
[Linux] Sections related to Linux
[Solaris] Sections related to Solaris or Solaris Containers
[VMware] Sections related to VMware
Sections related to Windows manager
[Hyper-V] Sections related to Hyper-V
[Xen] Sections related to RHEL5-Xen
[KVM] Sections related to RHEL-KVM
[Solaris Containers] Sections related to Solaris containers
[Oracle VM] Sections related to Oracle VM
- iii -
[Physical Servers] Sections related to physical servers
[VM host] Sections related to Windows Server 2008 with VMware or Hyper-V enabled
- Unless specified otherwise, the blade servers mentioned in this manual refer to PRIMERGY BX servers.
- Oracle Solaris may also be indicated as Solaris, Solaris Operating System, or Solaris OS.
- References and character strings or values requiring emphasis are indicated using double quotes ( " ).
- Window names, dialog names, menu names, and tab names are shown enclosed by brackets ( [ ] ).
- Button names are shown enclosed by angle brackets (< >) or square brackets ([ ]).
- The order of selecting menus is indicated using [ ]-[ ].
- Text to be entered by the user is indicated using bold text.
- Variables are indicated using italic text and underscores.
- The ellipses ("...") in menu names, indicating settings and operation window startup, are not shown.
- The ">" used in Windows is included in usage examples. When using Linux, read ">" as meaning "#".
- The URLs in this manual were correct when the manual was written.
Menus in the ROR console
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)
C:\Program Files (x86)\Resource Orchestrator
When using Windows 32-bit (x86)
C:\Program Files\Resource Orchestrator
Abbreviations
The following abbreviations are used in this manual:
Abbreviation Products
Microsoft(R) Windows Server(R) 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
Windows
Microsoft(R) Windows Server(R) 2003 R2, Enterprise Edition
Microsoft(R) Windows Server(R) 2003 R2, Standard x64 Edition
Microsoft(R) Windows Server(R) 2003 R2, Enterprise x64 Edition
Windows(R) 7 Professional
Windows(R) 7 Ultimate
Windows Vista(R) Business
Windows Vista(R) Enterprise
- iv -
Abbreviation Products
Windows Server 2008
Windows Vista(R) Ultimate
Microsoft(R) Windows(R) XP Professional operating system
Microsoft(R) Windows Server(R) 2008 Standard
Microsoft(R) Windows Server(R) 2008 Enterprise
Microsoft(R) Windows Server(R) 2008 R2 Standard
Microsoft(R) Windows Server(R) 2008 R2 Enterprise
Microsoft(R) Windows Server(R) 2008 R2 Datacenter
Windows 2008 x86 Edition
Windows 2008 x64 Edition
Windows Server 2003
Windows 2003 x64 Edition
Windows 7
Windows Vista
Windows XP
Linux
Microsoft(R) Windows Server(R) 2008 Standard (x86)
Microsoft(R) Windows Server(R) 2008 Enterprise (x86)
Microsoft(R) Windows Server(R) 2008 Standard (x64)
Microsoft(R) Windows Server(R) 2008 Enterprise (x64)
Microsoft(R) Windows Server(R) 2003 R2, Standard Edition
Microsoft(R) Windows Server(R) 2003 R2, Enterprise Edition
Microsoft(R) Windows Server(R) 2003 R2, Standard x64 Edition
Microsoft(R) Windows Server(R) 2003 R2, Enterprise x64 Edition
Microsoft(R) Windows Server(R) 2003 R2, Standard x64 Edition
Microsoft(R) Windows Server(R) 2003 R2, Enterprise x64 Edition
Windows(R) 7 Professional
Windows(R) 7 Ultimate
Windows Vista(R) Business
Windows Vista(R) Enterprise
Windows Vista(R) Ultimate
Microsoft(R) Windows(R) XP Professional operating system
Red Hat(R) Enterprise Linux(R) 5 (for x86)
Red Hat(R) Enterprise Linux(R) 5 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.1 (for x86)
Red Hat(R) Enterprise Linux(R) 5.1 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.2 (for x86)
Red Hat(R) Enterprise Linux(R) 5.2 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.3 (for x86)
Red Hat(R) Enterprise Linux(R) 5.3 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.4 (for x86)
Red Hat(R) Enterprise Linux(R) 5.4 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.5 (for x86)
Red Hat(R) Enterprise Linux(R) 5.5 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.6 (for x86)
Red Hat(R) Enterprise Linux(R) 5.6 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.7 (for x86)
Red Hat(R) Enterprise Linux(R) 5.7 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.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)
SUSE(R) Linux Enterprise Server 11 for x86
SUSE(R) Linux Enterprise Server 11 for EM64T
Red Hat Enterprise Linux
Red Hat(R) Enterprise Linux(R) 5 (for x86)
Red Hat(R) Enterprise Linux(R) 5 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.1 (for x86)
Red Hat(R) Enterprise Linux(R) 5.1 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.2 (for x86)
Red Hat(R) Enterprise Linux(R) 5.2 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.3 (for x86)
- v -
Abbreviation Products
Red Hat Enterprise Linux 5
Red Hat(R) Enterprise Linux(R) 5.3 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.4 (for x86)
Red Hat(R) Enterprise Linux(R) 5.4 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.5 (for x86)
Red Hat(R) Enterprise Linux(R) 5.5 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.6 (for x86)
Red Hat(R) Enterprise Linux(R) 5.6 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.7 (for x86)
Red Hat(R) Enterprise Linux(R) 5.7 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.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(R) Enterprise Linux(R) 5 (for x86)
Red Hat(R) Enterprise Linux(R) 5 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.1 (for x86)
Red Hat(R) Enterprise Linux(R) 5.1 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.2 (for x86)
Red Hat(R) Enterprise Linux(R) 5.2 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.3 (for x86)
Red Hat(R) Enterprise Linux(R) 5.3 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.4 (for x86)
Red Hat(R) Enterprise Linux(R) 5.4 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.5 (for x86)
Red Hat(R) Enterprise Linux(R) 5.5 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.6 (for x86)
Red Hat(R) Enterprise Linux(R) 5.6 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.7 (for x86)
Red Hat(R) Enterprise Linux(R) 5.7 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.8 (for x86)
Red Hat(R) Enterprise Linux(R) 5.8 (for Intel64)
Red Hat Enterprise Linux 6
RHEL5-Xen
RHEL-KVM
DOS Microsoft(R) MS-DOS(R) operating system, DR DOS(R)
SUSE Linux Enterprise Server
Oracle VM Oracle VM Server for x86
ESC ETERNUS SF Storage Cruiser
GLS PRIMECLUSTER GLS
Navisphere EMC Navisphere Manager
Solutions Enabler EMC Solutions Enabler
MSFC Microsoft Failover Cluster
Solaris Solaris(TM) 10 Operating System
SCVMM
Red Hat(R) Enterprise Linux(R) 6.2 (for x86)
Red Hat(R) Enterprise Linux(R) 6.2 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.4 (for x86) Linux Virtual Machine Function
Red Hat(R) Enterprise Linux(R) 5.4 (for Intel64) Linux Virtual Machine Function
Red Hat(R) Enterprise Linux(R) 6.2 (for x86) Virtual Machine Function
Red Hat(R) Enterprise Linux(R) 6.2 (for Intel64) Virtual Machine Function
SUSE(R) Linux Enterprise Server 11 for x86
SUSE(R) Linux Enterprise Server 11 for EM64T
System Center Virtual Machine Manager 2008 R2
System Center 2012 Virtual Machine Manager
- vi -
VMware
Abbreviation Products
VMware vSphere(R) 4
VMware vSphere(R) 4.1
VMware vSphere(R) 5
VMware ESX
VMware ESX 4 VMware(R) ESX(R) 4
VMware ESXi VMware(R) ESXi(TM)
VMware ESXi 5.0 VMware(R) ESXi(TM) 5.0
VMware Tools VMware(R) Tools
VMware vSphere 4.0 VMware vSphere(R) 4.0
VMware vSphere 4.1 VMware vSphere(R) 4.1
VMware vSphere 5 VMware vSphere(R) 5
VMware vSphere Client VMware vSphere(R) Client
VMware vCenter Server VMware(R) vCenter(TM) Server
VMware vClient VMware(R) vClient(TM)
VMware FT VMware(R) Fault Tolerance
VMware DRS VMware(R) Distributed Resource Scheduler
VMware DPM VMware(R) Distributed Power Management
VMware vDS VMware(R) vNetwork Distributed Switch
VMware Storage VMotion VMware(R) Storage VMotion
VIOM ServerView Virtual-IO Manager
VMware(R) ESX(R)
BladeLogic BMC BladeLogic Server Automation
ServerView SNMP Agents for MS Windows (32bit-64bit)
ServerView Agent
RCVE
ROR ServerView Resource Orchestrator
ROR VE ServerView Resource Orchestrator Virtual Edition
ROR CE ServerView Resource Orchestrator Cloud Edition
Resource Coordinator
ServerView Agents Linux
ServerView Agents VMware for VMware ESX Server
ServerView Resource Coordinator VE
Systemwalker Resource Coordinator
Systemwalker Resource Coordinator Virtual server Edition
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.
Trademark Information
- BMC, BMC Software, the BMC logos, and other BMC marks are trademarks or registered trademarks of BMC Software, Inc. in the
U.S. and/or certain other countries.
- EMC, EMC
2
, CLARiiON, Symmetrix, and Navisphere are trademarks or registered trademarks of EMC Corporation.
- HP is a registered trademark of Hewlett-Packard Company.
- vii -
- Linux is a trademark or registered trademark of Linus Torvalds in the United States and other countries.
- Microsoft, Windows, MS, MS-DOS, Windows XP, Windows Server, Windows Vista, Windows 7, Excel, Active Directory, and
Internet Explorer are either registered trademarks or trademarks of Microsoft Corporation in the United States and other countries.
- NetApp is a registered trademark of Network Appliance, Inc. in the US and other countries. Data ONTAP, Network Appliance, and
Snapshot are trademarks of Network Appliance, Inc. in the US and other countries.
- Oracle and Java are registered trademarks of Oracle and/or its affiliates in the United States and other countries.
- Oracle is a registered trademark of Oracle Corporation and/or its affiliates.
- Red Hat, RPM and all Red Hat-based trademarks and logos are trademarks or registered trademarks of Red Hat, Inc. in the United
States and other countries.
- SUSE is a registered trademark of SUSE LINUX AG, a Novell business.
- VMware, the VMware "boxes" logo and design, Virtual SMP, and VMotion are registered trademarks or trademarks of VMware, Inc.
in the United States and/or other jurisdictions.
- ServerView and Systemwalker are registered trademarks of FUJITSU LIMITED.
- 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.
Month/Year Issued, Edition Manual Code
November 2011, First Edition J2X1-7611-01ENZ0(00)
December 2011, 1.1 J2X1-7611-01ENZ0(01)
January 2012, 1.2 J2X1-7611-01ENZ0(02)
February 2012, 1.3 J2X1-7611-01ENZ0(03)
March 2012, 1.4 J2X1-7611-01ENZ0(04)
April 2012, 1.5 J2X1-7611-01ENZ0(05)
July 2012, 2 J2X1-7611-02ENZ0(00)
October 2012, Third Edition J2X1-7611-03ENZ0(00)
Copyright FUJITSU LIMITED 2010-2012
- viii -
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
2.2 Starting and Stopping an Agent...........................................................................................................................................................8
Chapter 3 Managing User Accounts.......................................................................................................................................11
Chapter 4 Managing Tenants.................................................................................................................................................12
Chapter 5 Managing Templates.............................................................................................................................................13
Chapter 6 Managing Resources and Resource Pools...........................................................................................................14
6.1 Managing Resource Pools.................................................................................................................................................................14
6.2 Managing Resources..........................................................................................................................................................................14
6.3 Managing L-Servers..........................................................................................................................................................................14
Chapter 7 Management of L-Platform....................................................................................................................................15
7.1 Review for L-Platform Usage Applications......................................................................................................................................15
7.2 Administration of L-Platform............................................................................................................................................................15
7.2.1 Deleting Unnecessary Data.........................................................................................................................................................15
7.2.2 Updating the Cloning Image.......................................................................................................................................................15
7.2.3 Importing to L-Platform..............................................................................................................................................................15
7.2.3.1 Network Information Settings for Converted L-Servers.....................................................................................................16
7.2.3.2 Importing L-Servers.............................................................................................................................................................16
7.2.3.3 Releasing L-Servers.............................................................................................................................................................16
7.2.4 Setting OS with Deployment on RHEL-KVM...........................................................................................................................16
7.2.5 Startup Priority Level Settings ...................................................................................................................................................17
7.2.6 Action to Take when an Error has Occurred..............................................................................................................................17
7.2.7 Setting Alive Monitoring............................................................................................................................................................18
7.2.8 Redundancy Settings...................................................................................................................................................................19
7.2.9 Automatic Server Release Settings.............................................................................................................................................19
7.2.10 Definition VM Specific Information Definition File................................................................................................................20
7.2.11 Changing Server Specifications on a VM Host........................................................................................................................20
Chapter 8 Changing Settings.................................................................................................................................................21
8.1 Registering and Deleting Application Process Assessors..................................................................................................................21
8.1.1 Registering an Application Process Assessor.............................................................................................................................21
8.1.2 Deleting an Application Process Assessor..................................................................................................................................21
8.1.2.1 Deleting an Infrastructure Administrator/dual-role Administrator from IflowUsers Group...............................................21
8.2 Settings for Sending Email................................................................................................................................................................22
8.3 Settings for Port Number of Management Servers............................................................................................................................23
8.4 Editing Information in the Home Window........................................................................................................................................25
8.5 Settings for L-Platform Management................................................................................................................................................26
8.5.1 Settings for Permissions to Change L-Platform Templates........................................................................................................26
8.5.2 Subnet Settings at Segment Editing............................................................................................................................................27
8.5.3 Settings for the Simplified Reconfiguration Function................................................................................................................27
8.5.4 Distribution Ratio Settings..........................................................................................................................................................28
8.5.5 Application Process Settings......................................................................................................................................................29
8.5.5.1 How to Modify the Application Process Settings................................................................................................................29
- ix -
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
8.6 Settings for Tenant Management and Account Management............................................................................................................30
8.6.1 Settings for Tenant Management and Account Management.....................................................................................................31
8.6.2 Editing the User Agreement when Registering a User...............................................................................................................34
8.7 Accounting Settings...........................................................................................................................................................................34
8.7.1 Display Function Settings for Estimated Price...........................................................................................................................34
8.7.2 Currency Information Settings....................................................................................................................................................36
8.7.3 Metering Log Settings................................................................................................................................................................36
8.7.4 Usage Charge Calculator Settings..............................................................................................................................................38
8.8 System Condition Server List Settings..............................................................................................................................................39
8.9 Settings for Event Log Output for CMDB Agent..............................................................................................................................41
Part 3 Retention......................................................................................................................................................................42
Chapter 9 Hardware Maintenance..........................................................................................................................................43
9.1 Overview............................................................................................................................................................................................43
9.2 Blade Server Maintenance.................................................................................................................................................................47
9.2.1 Maintenance LED.......................................................................................................................................................................47
9.2.2 Reconfiguration of Hardware Properties....................................................................................................................................48
9.2.3 Replacing Servers.......................................................................................................................................................................49
9.2.4 Replacing Non-Server Hardware................................................................................................................................................51
9.3 Maintenance for Servers Other Than Blade Servers.........................................................................................................................52
9.3.1 Reconfiguration of Hardware Properties....................................................................................................................................52
9.3.2 Replacing Servers.......................................................................................................................................................................54
9.3.3 Replacing and Adding Server Components................................................................................................................................58
9.3.4 Replacing Non-server Hardware................................................................................................................................................60
9.4 For Servers not Using Server Management Software.......................................................................................................................60
9.5 Network Device Maintenance...........................................................................................................................................................61
9.5.1 Replacement Procedure of Network Devices.............................................................................................................................61
9.5.1.1 When device that is targeted to replace is a breakdown......................................................................................................61
9.5.1.2 When Device that is Target of Restoration is undamaged...................................................................................................62
9.5.2 Regular Maintenance Procedure of Network Devices................................................................................................................65
9.5.3 Procedure for Addition of Network Devices..............................................................................................................................66
9.5.3.1 Adding L2 Switches to Handle Insufficient Numbers of Ports when Adding Servers........................................................66
9.5.3.2 Adding Firewalls, Server Load Balancers, and L2 Switches for Additional Tenants.........................................................68
9.5.4 Procedure for Addition or Modification of Connection Destinations of Network Devices.......................................................70
9.6 Storage Device Maintenance.............................................................................................................................................................71
9.7 Power Monitoring Device (PDU or UPS) Maintenance....................................................................................................................71
Chapter 10 Backup and Restoration...................................................................................................................................... 73
10.1 Backup and Restoration of Admin Servers......................................................................................................................................73
10.1.1 Mechanism of Backup and Restoration....................................................................................................................................74
10.1.2 Offline Backup of the Admin Server........................................................................................................................................80
10.1.2.1 Stopping the Manager........................................................................................................................................................81
10.1.2.2 Back up the Resources of this Product..............................................................................................................................81
10.1.2.3 Starting the Manager..........................................................................................................................................................81
10.1.3 Online Backup of the Admin Server.........................................................................................................................................82
10.1.3.1 Items to be Determined Before Periodic Execution..........................................................................................................84
10.1.3.2 Settings for Periodic Execution of Backup........................................................................................................................84
10.1.4 Restoring the Admin Server.....................................................................................................................................................87
10.1.4.1 Stopping the Manager........................................................................................................................................................87
10.1.4.2 Restoring the Resources of This Product...........................................................................................................................87
- x -
10.1.4.3 Starting the Manager..........................................................................................................................................................88
10.1.4.4 Disabling L-Platform Applications....................................................................................................................................88
10.1.4.5 Updating the configuration information in the operational status information.................................................................88
10.1.5 Online Backup Settings for Metering.......................................................................................................................................88
10.2 Backup and Restoration of Network Devices..................................................................................................................................91
10.2.1 Mechanism of Backup and Restoration....................................................................................................................................92
10.2.2 Backup of Network Devices.....................................................................................................................................................92
10.2.3 Restoration of Network Devices...............................................................................................................................................93
Part 4 Monitoring....................................................................................................................................................................94
Chapter 11 Monitoring Resources..........................................................................................................................................95
11.1 Overview..........................................................................................................................................................................................95
11.2 Resource Status................................................................................................................................................................................96
11.3 Addressing Resource Failures.........................................................................................................................................................99
11.4 Monitoring Networks.......................................................................................................................................................................99
11.4.1 Identification of Error Locations............................................................................................................................................100
11.4.1.1 When Notified of an Error by a Tenant Administrator or Tenant User...........................................................................100
11.4.1.2 When Changing State is Detected during Status Confirmation Using the ROR Console...............................................101
11.4.2 Firewall Status Confirmation..................................................................................................................................................102
11.4.2.1 When an L-Platform Using a Firewall is Identified........................................................................................................102
11.4.2.2 When a Firewall Changing State is Detected during Status Confirmation Using the ROR Console..............................103
11.4.3 Server Load Balancer Status Confirmation............................................................................................................................104
11.4.3.1 When an L-Platform Using a Server Load Balancer is Identified...................................................................................104
11.4.3.2 When a Changing State of Server Load Balancer is Detected during Status Confirmation Using the ROR Console....105
11.4.4 L2 Switch Status Confirmation...............................................................................................................................................106
11.4.5 Status Confirmation of Other Network Devices.....................................................................................................................107
11.5 Monitoring Storage........................................................................................................................................................................107
Chapter 12 Collecting Power Consumption Data and Displaying Graphs............................................................................109
12.1 Overview........................................................................................................................................................................................109
12.2 Exporting Power Consumption Data.............................................................................................................................................109
12.3 Power Consumption Data File (CSV Format)...............................................................................................................................109
12.4 Displaying Power Consumption Data Graphs...............................................................................................................................110
Chapter 13 Monitoring Resource Pools (Dashboard)...........................................................................................................111
Chapter 14 Monitoring L-Platforms.......................................................................................................................................112
Chapter 15 Accounting.........................................................................................................................................................113
15.1 Overview........................................................................................................................................................................................113
15.2 Manage Accounting Information...................................................................................................................................................114
15.2.1 Information Maintained by Product Master............................................................................................................................115
15.2.2 Accounting Information File Format......................................................................................................................................118
15.3 Operate Accounting Information...................................................................................................................................................121
15.3.1 Register Accounting Information...........................................................................................................................................122
15.3.2 Modify Accounting Information Command...........................................................................................................................123
15.3.3 Delete Accounting Information..............................................................................................................................................125
15.3.4 Reference Accounting Information........................................................................................................................................126
15.4 Calculation of Usage charges........................................................................................................................................................126
15.4.1 Overview of Usage charge Calculation..................................................................................................................................127
15.4.2 Resource Usage Times............................................................................................................................................................127
15.4.3 How to Charge for Resources.................................................................................................................................................127
15.4.4 Resource Usage Amounts and Times.....................................................................................................................................128
15.4.5 Example of Usage charge Calculation....................................................................................................................................128
15.4.6 Sending Usage charges...........................................................................................................................................................131
15.4.6.1 Usage Charge List File....................................................................................................................................................132
15.4.6.2 Usage charge Detail File..................................................................................................................................................133
- xi -
Chapter 16 Monitoring Logs.................................................................................................................................................135
16.1 Operation Logs..............................................................................................................................................................................135
16.1.1 Overview.................................................................................................................................................................................135
16.1.2 Usage Method.........................................................................................................................................................................138
16.1.3 Retention.................................................................................................................................................................................139
16.1.4 Scope of Operations Recorded in Operation Logs.................................................................................................................140
16.2 Audit Logs.....................................................................................................................................................................................140
16.2.1 Configuration Management Audit Log...................................................................................................................................140
16.2.2 Audit Logs of Output by the Tenant Management, Accounting, Access Control and System Condition.............................146
16.2.3 Application Process Audit Log...............................................................................................................................................152
16.3 Operation Logs (Activity)..............................................................................................................................................................154
16.3.1 Operation Logs for Accounting..............................................................................................................................................154
16.4 Investigation Logs..........................................................................................................................................................................155
16.4.1 Investigation Logs on Admin Servers....................................................................................................................................155
Part 5 High Availability and Disaster Recovery....................................................................................................................158
Chapter 17 High Availability of Managed Resources...........................................................................................................159
17.1 High Availability of Managed Resources......................................................................................................................................159
17.1.1 High Availability of L-Servers...............................................................................................................................................159
17.1.2 Blade Chassis High Availability.............................................................................................................................................162
17.1.3 High Availability for Storage Chassis....................................................................................................................................164
17.2 High Availability for Admin Servers.............................................................................................................................................169
Chapter 18 Disaster Recovery.............................................................................................................................................173
Appendix A Notes on Operating ServerView Resource Orchestrator..................................................................................174
Appendix B Metering Log.....................................................................................................................................................178
B.1 Types of Metering Logs..................................................................................................................................................................178
B.2 Output Contents of Metering Logs.................................................................................................................................................179
B.3 Formats of Metering Log Files.......................................................................................................................................................184
B.4 Deleting Metering Logs..................................................................................................................................................................187
Glossary...............................................................................................................................................................................188
- xii -
Part 1 Overview
Chapter 1 Overview of Operations, Maintenance, and Monitoring...................................................................2
- 1 -
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".
Flow of Service Provision Using Applications
The flow of service provision using applications in an environment where Resource Orchestrator has been installed is as shown below.
Figure 1.1 Flow of Service Provision Using Applications
* Note: Necessary when using firewalls (Firewall), server load balancers (SLB), or L2 switches.
1. Application for use
The tenant user applies to use an L-Platform.
For details, refer to "5.2 Subscribe to an L-Platform" in the "User's Guide for Tenant Users CE".
2. Approval
The tenant administrator approves the application by a tenant user to use an L-Platform.
For details, refer to "9.3 Approving an Application" in the "User's Guide for Tenant Administrators CE".
3. Assessment
The infrastructure administrator assesses the content of the application to use an L-Platform from the tenant administrator or tenant
user.
For details, refer to "10.2 Assessing an Application" in the "User's Guide for Infrastructure Administrators CE".
4. Notification of settings for firewalls and server load balancers
When using a firewall or a server load balancer, the infrastructure administrator prepares a script for configuring the firewall or
server load balancer.
Based on the information provided by the infrastructure administrator, the tenant administrator notifies the tenant user of the
configuration information for the firewall or server load balancer.
- 2 -
5. 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.
6. 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.
7. Confirm communication with applications
The tenant user checks that there are no problems with the applications installed on the L-Server, and that the L-Server can be
accessed from the public LAN.
When a firewall has not been configured, configure one.
If there are no problems in the communication check, proceed to the next step.
If there are problems, resolve them and check communication again.
8. Configure server load balancers
When an L-Platform has a server load balancer deployed, the tenant user performs configuration of the server load balancer.
9. Check communication with server load balancers
When an L-Platform has a server load balancer deployed, test that the settings of the server load balancer are correct.
It is necessary to configure the rules for the firewall so that communication using the virtual IP address configured for the server
load balancer is possible.
If there are no problems in the communication check, proceed to the next step.
If there are problems, resolve them and check communication again.
10. Configure firewalls
Configure address translation and firewall rules, and then test that communication with the L-Server is possible.
If the test shows no problems, configuration of the L-Platform operation environment is complete.
If there are problems, resolve them and check communication again.
1.1 Operation, Maintenance, and Monitoring by Infrastructure Administrators
This section explains operation, maintenance, and monitoring by infrastructure administrators when using Resource Orchestrator.
Infrastructure Administrator (infra_admin) Operations
Refer to the "User's Guide for Infrastructure Administrators (Resource Management) CE" for the [Resource] tab operations.
Refer to the "User's Guide for Infrastructure Administrators CE" for other operations.
Infrastructure Administrator (infra_admin) Management Operations
The operations that infrastructure administrators (infra_admin) can perform are as follow.
- Management of resources and resource pools
- Registration, modification, and deletion of resources
- Creation, deletion, modification of global pools and tenant local pools
- Review and confirmation of application status and L-Platform usage applications
- Management of tenants
- Creation, modification, and deletion of tenants
- 3 -
- 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" in "User's Guide
for Infrastructure Administrators".
Infrastructure Administrator (infra_admin) Maintenance Operations
Maintenance operations that infrastructure administrators (infra_admin) can perform are as follow:
- Hardware maintenance
- System maintenance (*2)
- Backup and restoration of admin servers (*2)
*2: OS administrative privileges are necessary for OS maintenance and backup and restore of admin servers.
Infrastructure Administrator (infra_admin) Monitoring Operations
Monitoring operations that infrastructure administrators (infra_admin) can perform are as follow:
- Monitoring of resource pools using dashboard
- Monitoring of L-Platform operation statuses
- Monitoring of resource capacity (servers, storage and network)
- Monitoring of operation logs and audit logs
1.2 Operation, Maintenance, and Monitoring by Tenant Administrators
For details on operations, maintenance and monitoring by tenant administrators, refer to the "User's Guide for Tenant Administrators CE".
1.3 Operation, Maintenance, and Monitoring by Tenant Users
For details on operations, maintenance and monitoring by tenant users, refer to the "User's Guide for Tenant Users CE".
- 4 -
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 -
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). Normally, there should be no need to manually start or stop either the manager or agents. To start or stop a manager or an agent
intentionally, refer to "2.1 Starting and Stopping the Manager" and "2.2 Starting and Stopping an Agent".
Note
When using the HBA address rename function, ensure that the manager is started before starting any managed servers. The power on
procedure should be managed as follows: first, start the admin server together with any storage devices, and start the managed servers 10
minutes later.
Managed servers will not boot up properly if they are started before the manager. Make sure that the manager is running before starting
managed servers.
Additionally, when using the HBA address rename function, the HBA address rename setup service should be started on a dedicated server
(HBA address rename server) and left running continuously. For details on starting, stopping, and confirming the state of the HBA address
rename setup service, refer to "Chapter 10 Settings for the HBA address rename Setup Service" in the "Setup Guide CE".
2.1 Starting and Stopping the Manager
The Resource Orchestrator manager starts automatically on the admin server.
This section explains how to manually start or stop the manager and how to check its running state.
[Windows Manager]
The manager is made up of the following two groups of Windows services:
- Manager Services
Resource Coordinator Manager
Resource Coordinator Task Manager
Resource Coordinator Web Server (Apache)
Resource Orchestrator Sub Web Server (Mongrel)
Resource Orchestrator Sub Web Server (Mongrel2)
Resource Coordinator Sub Web Server (Mongrel3)
Resource Coordinator Sub Web Server (Mongrel4)
Resource Coordinator Sub Web Server (Mongrel5)
Resource Coordinator DB Server (PostgreSQL)
ServerView Resource Orchestrator Service Catalog Manager DB Service(Dashboard)
ServerView Resource Orchestrator Service Catalog Manager DB Service(Charging)
ServerView Resource Orchestrator Service Catalog Manager REST Service(Charging)
- Related Services
Deployment Service
TFTP Service
- 6 -
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]. Then, open the [Services] window to check the state of each service.
Services are started and stopped using the rcxmgrctl command (start and stop subcommands).
Using this command, manager services and related services can be started or stopped at the same time.
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, right-click the manager application shown under the failover cluster manager tree,
and select either [Bring this service or application online] or [Take this service or application offline].
[Linux Manager]
The manager is made up of the following two groups of Linux services:
- Manager Services
rcvmr
Manager services also include the following daemons.
rcxmanager
rcxtaskmgr
rcxmongrel1
rcxmongrel2
rcxmongrel3
rcxmongrel4
rcxmongrel5
rcxhttpd
- Database (PostgreSQL)
rcxdb
- Related Services
scwdepsvd
scwpxesvd
scwtftpd
dhcpd (*)
* Note: Required when managed servers belonging to different subnets from the admin server exist.
The status of each of those services can be confirmed from the service command, as shown below.
# service rcvmr status <RETURN>
# service scwdepsvd status <RETURN>
# service scwpxesvd status <RETURN>
# service scwtftpd status <RETURN>
# service dhcpd status <RETURN>
Services are started and stopped using the rcxmgrctl command (start and stop subcommands).
Using this command, manager services and related services can be started or stopped at the same time.
- 7 -
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. To prevent conflicts with ServerView Deployment Manager, do not start these services in order. For details, refer to
"Appendix B Co-Existence with ServerView Deployment Manager" in the "Setup Guide VE".
- Resource Orchestrator cannot be operated if any of the manager services are stopped. Ensure that all services are running when
Resource Orchestrator is running.
- If the manager is unable to communicate on the admin LAN when started up (because of LAN cable disconnections or any other
causes), PXE Services may not start automatically. If PXE Services are stopped, investigate the network interface used for the admin
LAN and confirm whether it can communicate with other nodes on the admin LAN.
If the manager cannot communicate with admin LAN nodes, restore the admin LAN itself and restart the manager.
- In Basic mode, the following manager services are started.
In Basic mode, the procedure to start and stop the services and the procedure to check their statuses are same as those in standard
mode.
[Windows Manager]
- Manager Services
Resource Coordinator Manager
Resource Coordinator Task Manager
Resource Coordinator Web Server (Apache)
Resource Orchestrator Sub Web Server (Mongrel)
Resource Orchestrator Sub Web Server (Mongrel2)
Resource Coordinator DB Server (PostgreSQL)
[Linux Manager]
- Manager Services
rcvmr
Manager services also include the following daemons.
rcxmanager
rcxtaskmgr
rcxmongrel1
rcxmongrel2
rcxhttpd
2.2 Starting and Stopping an Agent
The Resource Orchestrator agent starts automatically on managed servers.
This section explains how to manually start or stop an agent and how to check its power state.
Note
To prevent conflicts, related services are uninstalled from the Resource Orchestrator agent when using ServerView Deployment Manager
on the admin LAN. In such cases, there is no need to start or stop those services when starting or stopping the Resource Orchestrator agent.
[Windows] [Hyper-V]
The agent consists of the following two Windows services:
- 8 -
- 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.
For details of the command, refer to "5.3 rcxadm agtctl" in the "Reference Guide (Command/XML) CE".
- Related Services
From the Windows Control Panel, open [Administrative Tools]. Then, open the [Services] window to stop or start the following
service.
- Deployment Agent
- Systemwalker SQC DCM
[Linux] [VMware] [Xen] [KVM]
The agent consists of the following services.
- Agent Service
- Related Services
- Deployment Agent
For VMware vSphere 4.0 or later version, Deployment Agent is not automatically started, as backup and restore, and cloning
functions cannot be used. It is not necessary to start up.
[Linux]
- Systemwalker SQC DCM
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.
- Agent Service
# /bin/ps -ef | grep FJSVssagt <RETURN>
- Related Services
# /bin/ps -ef | grep scwagent <RETURN>
To check the running state of the service of Systemwalker SQC DCM, execute the following command:
# /etc/rc0.d/K00ssqcdcm <RETURN>
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.
For details of the command, refer to "5.3 rcxadm agtctl" in the "Reference Guide (Command/XML) CE".
- Related Services
Execute the following command to start or stop the collection of image files, deployment of image files, and server startup control.
Starting an L-Server
- 9 -
# /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]
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.
# /bin/ps -ef | grep FJSVrcvat <RETURN>
The following explains how to start and stop each service.
Agents can be started and stopped using the start and stop subcommands of the rcxadm agtctl command.
For details of the command, refer to "5.3 rcxadm agtctl" in the "Reference Guide (Command/XML) CE".
- 10 -
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".
For details on operations by tenant administrators, refer to "Chapter 10 Tenant" in the "User's Guide for Tenant Administrators CE".
Viewing and Modification of Information of Logged in Users
To view and modify the information of logged in users, use [Account] on the ROR console for the operation.
For details on [Account], refer to "Chapter 13 Account" in the "User's Guide for Infrastructure Administrators CE".
- 11 -
Chapter 4 Managing Tenants
This chapter explains the management of tenants.
Tenant Creation
The flow of tenant creation is as follows:
1. Register Tenants
Input the tenant information and register tenants.
2. Create a Tenant Administrator
Create a tenant administrator.
3. 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.
A resource stored in a local pool cannot be used by a user of another tenant.
- Global Pool
A common resource pool which can be used by the entire system.
For details on how to select resource pools, refer to "Chapter 6 Defining Tenants and Resource Pools" in the "Design Guide CE".
When using a local pool, create a local pool used only by the tenant registered in step 1.
4. Register Resources
Register the resources created in 3.in the local pool.
For details, refer to "11.3 Creating a Tenant" in the "User's Guide for Infrastructure Administrators CE".
Tenant Operation
Use the [Tenant] tab in the ROR console for the following operations.
For details on the [Tenant] tab, refer to "Chapter 11 Tenant" in the "User's Guide for Infrastructure Administrators CE".
- Register Tenants
- Create a Tenant Administrator
- Create a Tenant Resource Pool
- Create and Delete Tenants
- 12 -
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" in the "User's Guide for Infrastructure Administrators CE".
- L-Server Templates
An L-Server template is the template defining the specifications of an L-Server (number of CPUs, memory capacity, disk capacity,
and number of NICs) used for an L-Platform.
Use the [Resource] tab to create, modify, and delete L-Server templates.
For details on L-Server template operations, refer to "Chapter 15 L-Server Template Operations" in the "User's Guide for Infrastructure
Administrators (Resource Management) CE".
- 13 -
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.
For details on the [Tenant] tab, refer to "Chapter 11 Tenant" in the "User's Guide for Infrastructure Administrators CE".
6.2 Managing Resources
This section explains the management of resources.
Use the [Resource] tab in the ROR console to register, change, or delete resources.
- Register Resources
Refer to "Chapter 5 Registering Resources" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
- Change Resources
Refer to "Chapter 7 Changing Resources" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
- Delete Resources
Refer to "Chapter 9 Deleting Resources" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
For details on how to add network devices, refer to "9.5.3 Procedure for Addition of Network Devices", and for details on how to add or
modify connection destinations of network devices, refer to "9.5.4 Procedure for Addition or Modification of Connection Destinations of
Network Devices".
6.3 Managing L-Servers
This section explains the management of L-Servers.
L-Server Operations
Refer to "Chapter 17 L-Server Operations" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Use of Physical Servers or Virtual Machines as L-Servers
Configured physical servers or virtual machines can be used as L-Servers.
For details, refer to "Chapter 18 Linking L-Servers with Configured Physical Servers or Virtual Machines" in the "User's Guide for
Infrastructure Administrators (Resource Management) CE".
- 14 -
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.
For details on the [Request] tab, refer to "Chapter 10 Request" in the "User's Guide for Infrastructure Administrators CE".
7.2 Administration of L-Platform
This section explains how to perform L-Platform operations.
7.2.1 Deleting Unnecessary Data
If an L-Platform or server deployed by this product was accidently deleted by virtualization software such as VMware, it is possible to
delete unneeded information about the system or server remaining in this product.
What is actually done is that the unneeded L-Platform information or server information status is changed to "Finished with return" with
the cfmg_deletesysdata(Unnecessary Data Deletion) command so that it is no longer displayed in the L-Platform management View.
Refer to "12.3 cfmg_deletesysdata (Unnecessary Data Deletion)" in the "Reference Guide (Command/XML) CE" for details on this
command.
7.2.2 Updating the Cloning Image
In this product, the resource ID is used when managing the cloning image.
If the cloning image has been updated, the resource ID will be changed, so the image information must be updated in order to return the
resource ID back to its previous setting.
If the cloning image has been updated, use an operation from the "Template" window to update the image information.
Refer to "8.3.8 Synchronizing Image Information" in the "User's Guide for Infrastructure Administratorsfor CE" details.
Point
To use both cloning masters (the cloning master before the update and the cloning master after the update) in the L-Platform template,
updating a single cloning master will not work. Instead, these cloning masters must be collected separately.
7.2.3 Importing to L-Platform
This section explains how to import physical servers, virtual machines, and L-Servers to an L-Platform.
There are the following two ways of importing physical servers, virtual machines, and L-Servers to the L-Platform Management function:
- Convert configured physical servers or virtual machines into L-Servers, then import the converted L-Servers to the L-Platform
Follow the procedure described below to convert configured physical servers or virtual machines into L-Servers and import to the LÂPlatform:
a. Convert the physical servers or virtual machines into L-Servers
Refer to "Use of Physical Servers or Virtual Machines as L-Servers".
b. Network Information Settings for Converted L-Servers
Refer to "7.2.3.1 Network Information Settings for Converted L-Servers".
- 15 -
c. 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".
Execute the rcxadm lserver attach -define command to set network information.
The setting of network information via the command rcxadm lserver attach -define can only be performed on the L-Server before it is
imported into the L-Platform management function.
Also, the rcxadm lserver attach -define command can only be executed if using Solaris container.
If adding multiple network interface cards (NICs), execute the command rcxadm lserver attach -define only the same number of times as
there are NICs being added.
Refer to "3.6 rcxadm lserver" in the "Reference Guide (Command/XML) CE" for details.
7.2.3.2 Importing L-Servers
The Import L-Server command (cfmg_importlserver) can be used to import servers that have been deployed, or the VM guests that have
been imported using the ROR Console, to the L-Platform Management function.
Refer to "12.4 cfmg_importlserver (Import L-Server)" in the "Reference Guide (Command/XML) CE" for details on this command.
Note
- When an L-Server for infrastructure administrator is imported to an L-Platform, the operation privileges of the L-Server are transferred
to the tenant administrator or the tenant user.
When this L-Server is released from the L-Platform by the cfmg_deletelserver command, the L-Server is changed back to the one for
infrastructure administrator.
- L-Servers without network interface cards (NICs) cannot be imported.
- No initial password information will be set for an L-Server that has been imported without image information being specified. "initial
password is [.]" will be displayed on the initial password confirmation window of the system details window of the L-Platform
management window.
- An L-Server that is under a tenant cannot be imported to a different tenant.
- When importing an L-Server that is not under a tenant, switch the power off for the L-Server targeted for import.
- Do not import physical L-Servers that have VM hosts installed. Refer to "Appendix D Installing VM Hosts on Physical L-Servers"
in the "Setup Guide CE" for information on installing VM hosts on a physical L-Server.
7.2.3.3 Releasing L-Servers
L-Servers that have been imported into the L-Platform management function can be released from the L-Platform by using the L-Server
release command (cfmg_deletelserver).
Refer to "12.2 cfmg_deletelserver (Release L-Server)" in the "Reference Guide (Command/XML) CE" for more information about the
command.
7.2.4 Setting OS with Deployment on RHEL-KVM
Windows OS(excluding Microsoft(R) Windows Server(R) 2008 R2)
When the virtualization software is RHEL-KVM, the following OS configuration procedure is necessary on each deployed server with
Windows OS to enable the settings of the IP addresses, the default gateway, and the host name.
- 16 -
The infrastructure administrator must look up the IP addresses and the host name in the L-Platform management window and the default
gateway in the resource management window, and then connect a console to the deployed server and configure the OS manually.
Users cannot access the server until this configuration is completed.
The administrator should include a description like "The IP address needs to be set by the administrator after deployment" in the description
field of the L-Platform template, and notify users that the server has become accessible after the configuration.
Linux OS with SELinux enabled
The administrator must disable SELinux when creating an image, and should include a description like "SELinux needs to be enabled
after the deployment has been completed" in the description field of the L-Platform template.
Because Linux OS is deployed with SELinux disabled, ensure that there are procedures in place to advise the user to enable SELinux after
deployment.
7.2.5 Startup Priority Level Settings
Any server with a startup priority level set to 0 will not startup or shutdown when performing bundled power supply operations.
An information message will be output to vsys_trace_log for any server that did not startup or shutdown.
If any server that either did not startup or shutdown actually needs to be started up or shut down, refer to the information message and use
the StartLServer or StopLServer command to startup or shutdown individually.
Refer to "2.3.5 StartLServer (Starts a Server)" and "2.3.6 StopLServer (Stops a Server)" in the "Reference Guide (API)" for details on this
command.
7.2.6 Action to Take when an Error has Occurred
When an error has occurred during a cancellation application by a tenant user, the cancellation application may become impossible.
In that case, confirm the system ID of the L-Platform, and use the Disable L-Platform Application command to make the cancellation
application possible again for the user.
For information on the Disable L-Platform Application command, refer to "12.12 recoverService (Disable L-Platform Application)" in
the "Reference Guide (Command/XML) CE".
When a Problem Occurs during L-Platform Operation
The flow of when a problem occurs, after the following operations for an L-Platform are implemented by a tenant user, is as below.
- Creation, modification, or deletion of an L-Platform
- 17 -
Loading...