FUJITSU J2X1-7611-03ENZ0 User Manual

Download

ServerView Resource Orchestrator Cloud Edition V3.1.1

Operation Guide

Windows/Linux

J2X1-7611-05ENZ0(03)

March 2013

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.

Chapter 10 Backup and Restoration

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 and Disaster Recovery

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

Sections related to Windows manager

[VMware] Sections related to VMware [Hyper-V] Sections related to Hyper-V [Xen] Sections related to RHEL5-Xen [KVM] Sections related to RHEL-KVM [Solaris Zones] Sections related to Solaris zones

- iii -

[OVM for x86] Sections related to Oracle VM Server for x86 [OVM for SPARC] Sections related to Oracle VM Server for SPARC [Physical Servers] Sections related to physical servers

[VM host]

Sections related to VMware, Windows Server 2008 with Hyper-V enabled, Xen, RHEL-KVM, Solaris zones, and OVM for SPARC

- 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.

- Oracle Solaris Zones may also be indicated as Solaris Containers or Solaris Container.

- Oracle VM Server for x86 may also be indicated as Oracle VM.

- In Resource Orchestrator the following servers are referred to as SPARC Servers/SPARC Enterprise.

- SPARC Enterprise M3000/M4000/M5000/M8000/M9000

- SPARC Enterprise T5120/T5140/T5220/T5240/T5440

- SPARC M10-1/M10-4/M10-4S

- 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:

- iv -

Windows

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 Microsoft(R) Windows Server(R) 2003 R2, Standard x64 Edition Microsoft(R) Windows Server(R) 2003 R2, Enterprise x64 Edition Windows(R) 8 Pro Windows(R) 8 Enterprise Windows(R) 7 Professional Windows(R) 7 Ultimate Windows Vista(R) Business Windows Vista(R) Enterprise Windows Vista(R) Ultimate Microsoft(R) Windows(R) XP Professional operating system

Windows Server 2012

Windows Server 2008

Windows 2008 x86 Edition

Windows 2008 x64 Edition

Windows Server 2003

Windows 2003 x64 Edition

Windows 8

Windows 7

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) 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) 8 Pro Windows(R) 8 Enterprise

Windows(R) 7 Professional Windows(R) 7 Ultimate

Windows Vista

Windows XP

Linux

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)

- v -

Abbreviation Products

Red Hat Enterprise Linux

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) 6.3 (for x86) Red Hat(R) Enterprise Linux(R) 6.3 (for Intel64) SUSE(R) Linux Enterprise Server 11 for x86 SUSE(R) Linux Enterprise Server 11 for EM64T

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) Red Hat(R) Enterprise Linux(R) 6.3 (for x86) Red Hat(R) Enterprise Linux(R) 6.3 (for Intel64)

Red Hat Enterprise Linux 5

- vi -

Abbreviation Products

Red Hat Enterprise Linux 6

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) 6.3 (for x86) Red Hat(R) Enterprise Linux(R) 6.3 (for Intel64)

RHEL5-Xen

RHEL-KVM

DOS

SUSE Linux Enterprise Server

OVM for x86 Oracle VM Server for x86 OVM for SPARC Oracle VM Server for SPARC ESC ETERNUS SF Storage Cruiser GLS PRIMECLUSTER GLS Navisphere EMC Navisphere Manager Solutions Enabler EMC Solutions Enabler MSFC Microsoft Failover Cluster

Solaris

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 Red Hat(R) Enterprise Linux(R) 6.3 (for x86) Virtual Machine Function Red Hat(R) Enterprise Linux(R) 6.3 (for Intel64) Virtual Machine Function

Microsoft(R) MS-DOS(R) operating system, DR DOS(R) SUSE(R) Linux Enterprise Server 11 for x86

SUSE(R) Linux Enterprise Server 11 for EM64T

Oracle Solaris10 05/09 (Update7) Media Pack Oracle Solaris11 11/11 Media Pack Oracle Solaris11.1 Media Pack

SCVMM

VMware

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 5.1 VMware vSphere(R) 5.1 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

System Center Virtual Machine Manager 2008 R2 System Center 2012 Virtual Machine Manager

VMware vSphere(R) 4 VMware vSphere(R) 4.1 VMware vSphere(R) 5 VMware vSphere(R) 5.1

VMware(R) ESX(R)

- vii -

Abbreviation Products

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 BladeLogic BMC BladeLogic Server Automation

Windows(R) Internet Explorer(R) 8

Internet Explorer

ServerView Agent

Windows(R) Internet Explorer(R) 9 Windows(R) Internet Explorer(R) 10

ServerView SNMP Agents for MS Windows (32bit-64bit) ServerView Agents Linux

ServerView Agents VMware for VMware ESX Server RCVE ROR ServerView Resource Orchestrator ROR VE ServerView Resource Orchestrator Virtual Edition ROR CE ServerView Resource Orchestrator Cloud Edition

Resource Coordinator

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, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S.

Patent and Trademark Office, and may be registered or pending registration in other countries.

- EMC, EMC2, CLARiiON, Symmetrix, and Navisphere are trademarks or registered trademarks of EMC Corporation.

- HP is a registered trademark of Hewlett-Packard Company.

- Linux is a trademark or registered trademark of Linus Torvalds in the United States and other countries.

Microsoft, Windows, MS-DOS, Windows Server, Windows Vista, 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.

- viii -

- 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, Second Edition J2X1-7611-02ENZ0(00) October 2012, Third Edition J2X1-7611-03ENZ0(00) December 2012, Fourth

Edition January 2013, Fifth Edition J2X1-7611-05ENZ0(00) January 2013, 5.1 J2X1-7611-05ENZ0(01) January 2013, 5.2 J2X1-7611-05ENZ0(02) March 2013, 5.3 J2X1-7611-05ENZ0(03)

J2X1-7611-04ENZ0(00)

- ix -

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 Admin 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

- x -

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

8.10 Setting for Directory Service Connection Information....................................................................................................................41

Part 3 Retention......................................................................................................................................................................42

Chapter 9 Hardware Maintenance..........................................................................................................................................43

9.1 Overview............................................................................................................................................................................................43

9.2 Blade Server Maintenance.................................................................................................................................................................48

9.2.1 Maintenance LED.......................................................................................................................................................................48

9.2.2 Reconfiguration of Hardware Properties....................................................................................................................................49

9.2.3 Replacing Servers.......................................................................................................................................................................50

9.2.4 Replacing Non-Server Hardware................................................................................................................................................52

9.3 Maintenance for Servers Other Than Blade Servers.........................................................................................................................53

9.3.1 Reconfiguration of Hardware Properties....................................................................................................................................53

9.3.2 Replacing Servers.......................................................................................................................................................................55

9.3.3 Replacing and Adding Server Components................................................................................................................................60

9.3.4 Replacing Non-server Hardware................................................................................................................................................61

9.4 For Servers not Using Server Management Software.......................................................................................................................61

9.5 Network Device Maintenance...........................................................................................................................................................62

9.5.1 Replacement Procedure of Network Devices.............................................................................................................................62

9.5.1.1 When the Device to Replace has Failed..............................................................................................................................63

9.5.1.2 When the Device to Replace has not Failed........................................................................................................................64

9.5.2 Regular Maintenance Procedure of Network Devices................................................................................................................67

9.5.3 Procedure for Addition of Network Devices..............................................................................................................................68

9.5.3.1 Adding L2 Switches to Handle Insufficient Numbers of Ports when Adding Servers........................................................68

9.5.3.2 Adding Firewalls, Server Load Balancers, and L2 Switches for Additional Tenants.........................................................70

9.5.4 Procedure for Addition or Modification of Connection Destinations of Network Devices.......................................................72

9.6 Storage Device Maintenance.............................................................................................................................................................73

9.7 Power Monitoring Device (PDU or UPS) Maintenance....................................................................................................................73

Chapter 10 Backup and Restoration......................................................................................................................................75

10.1 Backup and Restoration of Admin Servers......................................................................................................................................75

10.1.1 Mechanism of Backup and Restoration....................................................................................................................................76

10.1.2 Offline Backup of the Admin Server........................................................................................................................................82

10.1.2.1 Stopping the Manager........................................................................................................................................................83

10.1.2.2 Back up the Resources of this Product..............................................................................................................................83

10.1.2.3 Starting the Manager..........................................................................................................................................................83

10.1.3 Online Backup of the Admin Server.........................................................................................................................................84

10.1.3.1 Items to be Determined Before Periodic Execution..........................................................................................................86

10.1.3.2 Settings for Periodic Execution of Backup........................................................................................................................86

10.1.4 Restoring the Admin Server.....................................................................................................................................................89

10.1.4.1 Stopping the Manager........................................................................................................................................................89

- xi -

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

10.2.2 Backup of Network Devices.....................................................................................................................................................94

10.2.3 Restoration of Network Devices...............................................................................................................................................95

Part 4 Monitoring....................................................................................................................................................................97

Chapter 11 Monitoring Resources..........................................................................................................................................98

11.1 Overview..........................................................................................................................................................................................98

11.2 Resource Status................................................................................................................................................................................99

11.3 Addressing Resource Failures.......................................................................................................................................................102

11.4 Monitoring Networks.....................................................................................................................................................................102

11.4.1 Identification of Error Locations............................................................................................................................................103

11.4.1.1 When Notified of an Error by a Tenant Administrator or Tenant User...........................................................................103

11.4.1.2 When a Change in State is Detected during Status Confirmation Using the ROR Console...........................................104

11.4.2 Firewall Status Confirmation..................................................................................................................................................105

11.4.2.1 When an L-Platform Using a Firewall is Identified........................................................................................................105

11.4.2.2 When a Change in Firewall Status is Detected during Status Confirmation Using the ROR Console...........................106

11.4.3 Server Load Balancer Status Confirmation............................................................................................................................107

11.4.3.1 When an L-Platform Using a Server Load Balancer is Identified...................................................................................107

11.4.3.2 When an L-Platform Using a Server Load Balancer is Identified...................................................................................108

11.4.4 L2 Switch Status Confirmation...............................................................................................................................................109

11.4.5 Status Confirmation of Other Network Devices.....................................................................................................................110

11.5 Monitoring Storage........................................................................................................................................................................110

Chapter 12 Collecting Power Consumption Data and Displaying Graphs............................................................................112

12.1 Overview........................................................................................................................................................................................112

12.2 Exporting Power Consumption Data.............................................................................................................................................112

12.3 Power Consumption Data File (CSV Format)...............................................................................................................................112

12.4 Displaying Power Consumption Data Graphs...............................................................................................................................113

Chapter 13 Monitoring Resource Pools (Dashboard)...........................................................................................................114

Chapter 14 Monitoring L-Platforms.......................................................................................................................................115

Chapter 15 Accounting.........................................................................................................................................................116

15.1 Overview........................................................................................................................................................................................116

15.2 Manage Accounting Information...................................................................................................................................................117

15.2.1 Information Maintained by Product Master............................................................................................................................118

15.2.2 Accounting Information File Format......................................................................................................................................121

15.3 Operate Accounting Information...................................................................................................................................................124

15.3.1 Register Accounting Information...........................................................................................................................................125

15.3.2 Modify Accounting Information.............................................................................................................................................127

15.3.3 Delete Accounting Information..............................................................................................................................................128

15.3.4 Reference Accounting Information........................................................................................................................................129

15.4 Calculation of Usage charges........................................................................................................................................................130

15.4.1 Overview of Usage charge Calculation..................................................................................................................................130

15.4.2 Resource Usage Times............................................................................................................................................................130

15.4.3 How to Charge for Resources.................................................................................................................................................131

15.4.4 Resource Usage Amounts and Times.....................................................................................................................................131

15.4.5 Example of Usage charge Calculation....................................................................................................................................132

15.4.6 Sending Usage charges...........................................................................................................................................................135

15.4.6.1 Usage Charge List File....................................................................................................................................................135

- xii -

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

16.3 Operation Logs (Activity)..............................................................................................................................................................159

16.3.1 Operation Logs for Accounting..............................................................................................................................................159

16.4 Investigation Logs..........................................................................................................................................................................159

16.4.1 Investigation Logs on Admin Servers....................................................................................................................................159

Part 5 High Availability and Disaster Recovery....................................................................................................................162

Chapter 17 High Availability of Managed Resources...........................................................................................................163

17.1 High Availability of Managed Resources......................................................................................................................................163

17.1.1 High Availability of L-Servers...............................................................................................................................................163

17.1.2 Blade Chassis High Availability.............................................................................................................................................166

17.1.3 High Availability for Storage Chassis....................................................................................................................................168

17.2 High Availability for Admin Servers.............................................................................................................................................173

Chapter 18 Disaster Recovery.............................................................................................................................................177

Appendix A Notes on Operating ServerView Resource Orchestrator..................................................................................178

Appendix B Metering Log.....................................................................................................................................................182

B.1 Types of Metering Logs..................................................................................................................................................................182

B.2 Output Contents of Metering Logs.................................................................................................................................................183

B.3 Formats of Metering Log Files.......................................................................................................................................................188

B.4 Deleting Metering Logs..................................................................................................................................................................191

Glossary...............................................................................................................................................................................192

- xiii -

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

[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

- 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] [Solaris Zones] [OVM for SPARC] The agent consists of the following services.

- Agent Service

# /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

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 "10.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 LPlatform:

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 Zone and OVM for SPARC. 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 "10.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 "10.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

OSs except Linux and Microsoft(R) Windows Server(R) 2008 R2

If the virtualization software is RHEL-KVM and the guest OS is neither Linux nor Windows Server(R) 2008 R2, it is necessary to manually configure the IP address, default gateway, and host name of the guest OS. Users cannot access the deployed server until this configuration

- 16 -

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. To prevent problems caused by this situation, collect a cloning image from a server that has been configured as follows:

- Do not set the IP address to a fixed value.

- Disable Windows file sharing and other services that cause problems when the host name conflicts with other servers.

After deploying a server with this cloning image, the infrastructure administrator looks up the IP address and host name in the L-Platform tab, and also looks up the default gateway in the Resource tab, and then connects with the deployed server by using the console connection function and sets these values manually. In addition, the administrator includes a description like "The IP address needs to be configured by the administrator after deployment" in the description field of the L-Platform template, and after the configuration is completed, notifies users that the server has become accessible. For a deployment with a cloning image that has not been configured as described earlier, the infrastructure administrator creates an LServer by using the Resource tab after receiving a request from a user, and imports the L-Server to the L-Platform management function by following the description of "7.2.3.2 Importing L-Servers", and then notifies users that the server has become accessible.

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 L-Platform ID, 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 "10.10 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 -

- 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

1. The tenant user performs L-Platform creation, modification or deletion, or network device configuration or modification.

2. Problem Occurrence

L-Platform creation, modification or deletion, or network device configuration or modification ends abnormally.

3. Investigation Request

The tenant user requests investigation of the cause of the operation failure by the tenant administrator. When requesting investigation, provide detailed information about the failed operation or output message.

The tenant administrator provides the information obtained from the tenant user to the infrastructure administrator, and requests investigation of the cause of the operation failure.

4. Problem Cause Investigation

Based on the information obtained from the tenant administrator, the infrastructure administrator investigates problems with the script configuring the network devices, the hardware, or the communication route.

5. Corrective Action

The infrastructure administrator performs the following corrective actions:

- When there are errors in the script configuring the network device, the infrastructure administrator modifies the script.

- When an error occurs on hardware or the communication route, the infrastructure administrator replaces the hardware.

6. Reporting of Investigation Results

After completing corrective action, the infrastructure administrator reports the results of investigation to the tenant administrator or the tenant user, and requests operation of the L-Platform.

7. Operation of the L-Platform

The tenant user performs operation of the L-Platform again.

7.2.7 Setting Alive Monitoring

When using alive monitoring on an L-Platform, it needs to be deployed specifying an L-Server template in which the setting of activity monitoring is enabled.

- 18 -

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.

Example

- L-Server template name where heartbeat settings are disabled

VMware_Small

- L-Server template name where heartbeat settings are enabled

VMware_Small_Monitoring

7.2.8 Redundancy Settings

When deploying a server with redundancy settings to an L-Platform, it is necessary to deploy by specifying an L-Server template that has redundancy settings enabled. Refer to "Chapter 15 L-Server Template Operations" in the "User's Guide for Infrastructure Administrators (Resource Management) CE" for information on how to create L-Server templates.

If the settings are changed after deployment, change the "Type of Server(specifications)" by reconfiguring the L-Platform. Register different L-Server templates where redundancy settings are enabled and disabled. Also use L-Server template names that make it easy to distinguish whether redundancy settings are enabled or disabled.

Example

- L-Server template name where redundancy settings are disabled

VMware_Small

- L-Server template name where redundancy settings are enabled

VMware_Small_HA

7.2.9 Automatic Server Release Settings

When deploying a server with automatic server release settings to an L-Platform, it is necessary to deploy by specifying an L-Server template that has automatic server release settings enabled. Refer to "Chapter 15 L-Server Template Operations" in the "User's Guide for Infrastructure Administrators (Resource Management) CE" for information on how to create L-Server templates.

If the settings are changed after deployment, change the "Type of Server(specifications)" by reconfiguring the L-Platform. Register different L-Server templates where automatic server release settings are enabled and disabled. Also use L-Server template names that make it easy to distinguish whether automatic server release settings are enabled or disabled.

Example

- L-Server template name where automatic server release settings are disabled

VMware_Small

- 19 -

- 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. Rather, the following values are applied:

[VMware]

- CPU Reserved: 0.1GHz

- CPU Shares: 1000

- Memory Reserved: Memory Size

- Memory Shares: Memory Size * 10240

[Hyper-V]

- CPU Reserved: 0.1GHz

- CPU Weight: 100

- Memory RAM: Memory Size

- Memory Weight: 5000

With L-Server templates used in L-Platforms, set the values for overcommit in the L-Server templates rather than in a definition VM specific information definition file.

7.2.11 Changing Server Specifications on a VM Host

In L-Platform subscription and L-Platform configuration changes, the upper limits of the server's specifications are determined by the maximum number of CPUs, maximum CPU frequency, and the maximum memory capacity values specified in the L-Platform template's image information.

After deploying an L-Platform, and if the server's CPUs, CPU frequency, and memory capacity are to be changed from the VM host, make sure you specify values that do not exceed the maximum values specified in the image information of the L-Platform template.

If the values specified for the CPUs, CPU frequency, and memory capacity exceed the maximum values specified in the image information of the L-Platform template, those values will be changed back to match the maximum values when the configuration is changed.

Point

Do not change the server's CPUs, CPU frequency, and memory capacity from the VM host if possible.

- 20 -

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. Use the LDIF file to register an application process assessor at the directory server. Follow the procedure below to register as application process assessor.

1. Create an infrastructure administrator or dual-role administrator.

2. Add the infrastructure administrator or dual-role administrator as a member of the IflowUsers group.

Note

- Infrastructure administrators and dual-role administrators who have not been registered in the "IflowUsers" group cannot

conduct assessment in application processes. Also, if infrastructure administrators and dual-role administrators not registered in the "IflowUsers" group select the Request tab in the ROR Console, the following error message appears:

Error message : Failed to authenticate the user.

- Administrators (dual-role administrators) created during installation are not registered in the "IflowUsers" group. Add them to

the "IflowUsers" group.

- If an email address is not set, assessment request emails are not sent, and reservation notification emails are not sent when an

error occurs.

- If no infrastructure administrators or dual-role administrators are registered in the IflowUsers group, the following message is

displayed after the application is forwarded from the Forward screen window when the user subscribes to the service:

PCS1002 An error occurred while processing application. Please contact the infrastructure administrators.

Refer to "18.2.1 Registering an Application Process Assessor" in the "Setup Guide CE" for information on how to register application process assessor.

8.1.2 Deleting an Application Process Assessor

This section explains how to delete an infrastructure administrator or dual-role administrator from the application process assessors.

8.1.2.1 Deleting an Infrastructure Administrator/dual-role Administrator from IflowUsers

Group

Follow the procedure below to delete an infrastructure administrator or dual-role administrator from the IflowUsers group members.

For OpenDS

1. Create an LDIF file.

Edit a sample LDIF file to create the file. An example of an LDIF file is shown below.

- 21 -

# Delete manager from IflowUsers dn: cn=IflowUsers,ou=group,dc=fujitsu,dc=com changetype: modify delete: member member:cn=manager,ou=users,dc=fujitsu,dc=com

2. Execute the ldapmodify command.

[Windows Manager] Specify the created LDIF file, and then execute the ldapmodify command.

OpenDS Installation_folder\bat\ldapmodify.bat" -p <port number> -f <ldif file> -D <administrator user DN> -w <password>

An execution example is shown below.

c:\> c:\Program Files (x86)\Fujitsu\ServerView Suite\opends\bat\ldapmodify -p 1473 -D "cn=Directory Manager" -w admin -f c:\ldif\deleteuserfromgroup.ldif 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

[Linux Manager] Specify the created LDIF file, and then execute the ldapmodify command.

# 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.

- For the directory service port number, administrator DN, and administrator DN password, enter the values that were set during

installation.

For Active Directory

1. From the Start menu, open [Control Panel]-[Administrative Tools]-[Active Directory Users and Computers].

Select the name of a domain that is managed by Active Directory.

3. Right-click "IflowUsers" of the organizational unit "Group", and select [Property].

4. Select the [Members] tab, and select the members to delete from the member list, and click the [Remove] button.

5. A confirmation dialog will be displayed. Click [Yes].

6. After returning to the property window of the group, confirm that the members have been deleted correctly,

and click the [OK] button.

8.2 Settings for Sending Email

This section explains how to change settings for sending an email.

- 22 -

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.

Refer to "18.1 Settings for Sending Email" in the "Setup Guide CE" for information on how to change settings for e-mail sent from tenant administrators.

Settings for Email Sent from the L-Platform Management Window

Email sent from the L-Platform management window notifies the end or failure of processing to the tenant administrators and the tenant users when the tenant users have used the ROR Console to perform an application to use L-Platform, an L-Platform modification, or an application to cancel L-Platform.

Refer to "18.1 Settings for Sending Email" in the "Setup Guide CE" for information on how to change settings for email sent from the LPlatform Management window.

Email Sent from the Usage Charge Calculator

Email will be enabled if the calculator for charges is used. A usage charge file is sent to the set email address with the monthly usage charges for each tenant.

Refer to "18.1.4 Email Sent from the Usage Charge Calculator" in the "Setup Guide CE" for information on the email settings used for the usage charge calculator.

Email Sent via an Application Process

An email will be sent via the application process when changes or requests have been made. The following notification will be sent for an application to use L-Platform, an L-Platform modification, or an application to cancel LPlatform from the L-Platform management window:

- Notification of acceptance of application, rejection of application, and dismissal of application to the tenant users

- Notification of request for approval and dismissal of application to the tenant administrators

- Notification of request for assessment to the infrastructure administrators

Refer to "18.1.6 Settings for Email Sent via the Application Process" in the "Setup Guide CE" for information on how to change settings for email sent from an application process."

Settings for the Email Sent from the Dashboard

Email sent from the Dashboard will be enabled only if using the dashboard alert function. The dashboard sends notifications to e-mail address setting in Customizing Email Send Settings if the global pool use rate exceeds the threshold value.

Refer to "18.1.7 Settings for Email Sent from the Dashboard" in the "Setup Guide CE" for information on how to set settings for email sent from the dashboard alert function.

8.3 Settings for Port Number of Admin Servers

This section explains how to change the port number of the admin server as follows:

- ROR console server port number

- L-Platform management port number

Stop the manager before changing the port number. Restart the manager after changing the port number. Refer to "2.1 Starting and Stopping the Manager" for information on how to start and stop the manager. Note that there is no need to stop and start the manager for each port number.

Changing the Port Number of the ROR Console Server

The procedure for changing the port number is as follows.

- 23 -

1. 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

2. 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 > Interstage > Application Server > Interstage Management Console. [Linux Manager]

1. Start the Web browser.

2. Specify the URL of the Interstage Management Console.

The URL format is as follows: (If SSL encrypted communication is not being used)

http://[

Host name

(If SSL encrypted communication is being used) https://[

Host name

]:[

Port number

]:[

Port number

]/IsAdmin/

3. Login to the Interstage Management Console.

3. Change the port number.

Select System > Services > Web Server > RCXCT-ext > Web Server Settings to change the port number.

Changing the port number of L-Platform management

The procedure for changing the port number is as follows.

1. 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 URL:

- vsys.host

An example is shown below. The parts in italics show the information that is changed.

vsys.host = http://192.168.11.22:8013/vsys/services/VSYS/

- 24 -

2. 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.

8.4 Editing Information in the Home Window

This section explains how to edit the information that is displayed on the lower part of the home window of the ROR Console.

Point

- The information can also be used to notify tenant administrators and tenant users of who to contact.

- The messages can also be edited in the home window. Refer to "3.2 Editing the Home Messages" in the "User's Guide for Infrastructure

Administrators CE" for details.

Information are divided into those for infrastructure administrators and those for tenant administrators and tenant users, so use the following respective text files to edit them:

For infrastructure administrators

[Windows Manager]

Installation_folder\SVROR\Manager\etc\customize_data\home_tab\home_infra_mes.txt

[Linux Manager]

/etc/opt/FJSVrcvmr/customize_data/home_tab/home_infra_mes.txt

For tenant administrators and tenant users

[Windows Manager]

Installation_folder\SVROR\Manager\etc\customize_data\home_tab\home_tenant_mes.txt

[Linux Manager]

/etc/opt/FJSVrcvmr/customize_data/home_tab/home_tenant_mes.txt

Settings

Enter the message, line by line, in the following format:

date, message

- UTF-8 must be used as the character code in the text file.

- There is no schedule format specified. If no schedule is required, use a comma at the start of the line, and then subsequently enter the

message.

- 25 -

- 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.

8.5 Settings for L-Platform Management

This section explains how to change the settings for L-Platform management.

8.5.1 Settings for Permissions to Change L-Platform Templates

Specify whether to permit modification of the value specified in the L-Platform template when an L-Platform usage application is made in the L-Platform Management window.

Note that if modification is not permitted, it is not possible to modify the configuration of L-Platforms that have already been deployed.

Point

Settings for Permissions to Change L-Platform Templates can be set by "Setup Wizard" on the ROR Console. For details of "Setup Wizard", refer to "3.1 Setup Wizard" in the "User's Guide for Infrastructure Administrators CE".

Stopping the manager

Stop the manager. Refer to "2.1 Starting and Stopping the Manager" for information on how to stop the manager.

Changing L-Platform templates

The procedure for changing the settings for whether or not changes to the L-Platform templates in the L-Platform management window are to be permitted is as follows: Open the following file.

[Windows Manager]

Installation_folder\RCXCTMG\MyPortal\config\custom_config.xml

[Linux Manager]

/etc/opt/FJSVctmyp/config/custom_config.xml

The following information must be modified:

- The entry tag with no-configuration as the key value

Modify the value of the entry tag with no-configuration as the key value. The section in italics is the information to be modified. Specify "false" to allow the L-Platform template to be modified. Specify "true" to not allow it to be modified. The default value is "false".

<entry key="no-configuration">false</entry>

Starting the manager

Start the manager. Refer to "2.1 Starting and Stopping the Manager" for information on how to start the manager.

- 26 -

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 LPlatform. Use the following procedure to use network resource names rather than IP addresses to select which subnets to allocate to segments during subnet setup.

Refer to "8.3.14 L-Platform Reconfiguration" in the "User's Guide for Tenant Administrators CE" for details on changing the configuration.

Point

Subnet Setting at Segment Editing can be set by "Setup Wizard" on the ROR Console. For details of "Setup Wizard", refer to "3.1 Setup Wizard" in the "User's Guide for Infrastructure Administrators CE".

1. Open the Manager View settings file in a text editor.

The Manager View settings file is stored in the following location: [Windows Manager]

Installation_folder\RCXCTMG\MyPortal\config\managerview_config.xml

[Linux Manager]

/etc/opt/FJSVctmyp/config/managerview_config.xml

2. Add the following key and value.

Key name Content

network-list-show-resource-name false: Uses the IP address to select a subnet. (This is the default

value. This is applicable even when this key is not defined.) true: Uses the network resource name to select a subnet.

3. Save the file.

4. Restart the manager.

Refer to "2.1 Starting and Stopping the Manager" for information on how to Restart the manager.

8.5.3 Settings for the Simplified Reconfiguration Function

The simplified reconfiguration function is a function that allows specification changes to be performed for a server, when a new system is being created or when a configuration is being changed after deployment, simply by selecting a server type.

When this function is enabled, individual values cannot be changed directly. To change the settings for this function, perform the following procedure. Refer to "8.3.14 L-Platform Reconfiguration" in the "User's Guide for Tenant Administrators CE" for details on changing the configuration.

Point

Settings for the Simplified Reconfiguration Function can be set by "Setup Wizard" on the ROR Console. For details of "Setup Wizard", refer to "3.1 Setup Wizard" in the "User's Guide for Infrastructure Administrators CE"

1. Open the settings file in a text editor.

The settings file is stored in the following location: [Windows Manager]

Installation_folder\RCXCTMG\MyPortal\config\managerview_config.xml

- 27 -

[Linux Manager]

/etc/opt/FJSVctmyp/config/managerview_config.xml

2. 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

3. Save the file.

4. Restart the manager.

Refer to "2.1 Starting and Stopping the Manager" for information on how to restart the manager.

8.5.4 Distribution Ratio Settings

The distribution ratio settings set a simple selection method for the distribution ratios of CPUs and memory that correspond to the distribution ratio settings of VMware.

Note that the settings are enabled only if the simplified reconfiguration function has been disabled. To change the settings, implement the following procedure: Refer to "8.3.14 L-Platform Reconfiguration" in the "User's Guide for Tenant Administrators CE" for details on changing the configuration.

Point

Distribution Ratio Settings can be set by "Setup Wizard" on the ROR Console. For details of "Setup Wizard", refer to "3.1 Setup Wizard" in the "User's Guide for Infrastructure Administrators CE".

1. Use the editor to open the settings file.

The settings file is stored in the following location: [Windows Manager]

Installation_folder\RCXCTMG\MyPortal\config\managerview_config.xml

[Linux Manager]

/etc/opt/FJSVctmyp/config/managerview_config.xml

2. Add the following keys and values:

Key name Content

share-easy-setting false: Directly edits values. (This is the default value. This is applicable even when this key

is not defined.) true: Selects from a list box the values to be set that show the distribution ratio of memory. The values to be set are as follows:

Value Distribution ratio (share)

Low (500) 500 Standard (1,000) 1,000 High (2,000) 2,000

3. Save the file.

- 28 -

4. 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.

Note

If the application process is being changed from "use" to "do not use" after the manager starts its operation, make sure that there are no pending processes before changing it. If there are pending processes, finish all of them by cancelling, approving, rejecting, accepting, or dismissing each of them. Pending L-platforms can be checked using the listUnapprovalLplatform command (List of L-Platform Applications). Refer to "10.8 listUnapprovalLplatform (List of L-Platform Applications)" in the "Reference Guide (Command/XML) CE".

Refer to "18.2 Application Process Settings" in the "Setup Guide CE" for information on how to change the setting for whether or not an application process is used.

8.5.5.2 How to Modify Application Process to be Used

This section explains how to modify the application process to be used.

Note

If the application process to be used is being changed after the manager starts its operation, make sure that there are no pending processes before changing it. If there are pending processes, finish all of them by cancelling, approving, rejecting, accepting, or dismissing each of them.

Refer to "18.2 Application Process Settings" in the "Setup Guide CE" for information on how to change the application process to be used.

8.5.6 Editing the Environment Setup File for the L-Platform API

Refer to "18.7 Editing the Environment Setup File for the L-Platform API" in the "Setup Guide CE" for information on how to change the environment settings for the L-Platform API.

8.5.7 Edit the License Agreement

Refer to "18.12 Edit the License Agreement" in the "Setup Guide CE" for information on how to edit the license displayed in the L-Platform Management window.

8.5.8 Settings when RHEL5-Xen is used

Refer to "18.8 Settings when RHEL5-Xen is used" in the "Setup Guide CE" for information on the settings for when RHEL5-Xen is to be used.

8.5.9 Default Password Setting for Sent Emails

Refer to "18.1 Settings for Sending Email" in the "Setup Guide CE" for information on how to set whether to include the deployed server's default password in the emails sent when an L-Platform is deployed or a server is added to an L-Platform.

- 29 -

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.

1. Use the editor to open the settings file.

The settings file is stored in the following location: [Windows Manager]

Installation_folder\RCXCTMG\MyPortal\config\managerview_config.xml

[Linux Manager]

/etc/opt/FJSVctmyp/config/managerview_config.xml

2. Add the following keys and values:

Key name Content

maximum-number-of-connections-in-template Specify the maximum number of L-Servers that can be placed

in the L-Platform Template. Without a key, the default value is 30.

maximum-number-of-connections-in-segment Specify the maximum number of NICs in the segment of the

L-Platform Template. Without a key, the default value is 30.

Note

If there is a firewall, the maximum number of connections in the segment defined in the ruleset will be the smaller value out of the maximum number of servers in the ruleset and the configured value of the "maximum-number-of-connections-in-segment". Segments that are not defined in the firewall ruleset will use the configured value.

3. Save the file.

4. Restart the manager.

Refer to "2.1 Starting and Stopping the Manager" for information on how to restart the manager.

8.5.11 Customizing the User Rights for L-Platform Operations

It is possible to customize the user rights in the L-Platform management window to suit the role of the user (tenant administrator or tenant user).

Customize user rights according to the design changes made in "5.2 Customizing Access Authority for L-Platform Operations" in the "Design Guide CE".

You can use a command to customize user rights. Refer to "Chapter 12 Access Authority Customize Commands" in the "Reference Guide (Command/XML) CE" for information on the

command to customize user rights.

8.6 Settings for Tenant Management and Account Management

This section explains how to change the settings for the tenant management and the account management, and explains how to edit the user agreement that is displayed when registering a user.

- 30 -

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.

- Setting for registration format of tenant users

This section explains the procedure for changing the setting for whether a provisional account of a tenant user is to be registered or whether the tenant user is to be registered directly, when a tenant administrator registers a tenant user.

- Setting for execution authority of the tenant management

This section explains the procedure for changing the setting for whether or not a tenant administrator can perform the following tenant management:

- Add users

- Delete users

- Delegate user privileges

- Set user password

- Password change notification email settings

This section explains the procedure for modifying the settings when determining whether or not to include a new password within the body of the password change notification email that is sent once password settings are complete, in the event that a tenant administrator sets the user's password.

- Setting for execution authority of the account management

This section explains the procedure for changing the setting for whether or not a tenant administrator or tenant user can perform the following account management:

- Changing the user's own information

- Changing the user's own password

- Directory service operation setting

This section explains the procedure for changing the setting for whether or not registration to directory service can be performed and for whether or not password modification is to be allowed, when an infrastructure administrators or a tenant administrator registers a user.

Point

Setting for registration format of tenant users and Setting for execution authority of the tenant management can be set by "Setup Wizard" on the ROR Console. See the table below for the settings items can be set by "Setup Wizard" on the ROR Console.

For details of "Setup Wizard", refer to "3.1 Setup Wizard" in the "User's Guide for Infrastructure Administrators CE".

Stopping the manager

Stop the manager. Refer to "2.1 Starting and Stopping the Manager" for information on how to stop the manager.

Tenant Management Settings

The procedure for changing the setting of the tenant management is as follows.

1. Open the following file.

[Windows Manager]

Installation_folder\RCXCTMG\SecurityManagement\conf\portal.properties

[Linux Manager]

- 31 -

/etc/opt/FJSVctsec/conf/portal.properties

2. The following information must be modified:

Setting item Settings

visible.tenantuser Setting for infrastructure

administrators operation

Specify "on" if both tenant administrators 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. The initial value is "on". If "off" has been specified, the tenant users will not be displayed in the User List window of the tenant management.

provisional.acount (*) Setting for tenant

administrator operation

allowUpdate (*) Specify "on" if the tenant management is

setPassword.tenantadmin.mailwithpasswd When setting the user's password in

Specify "on" if a provisional account of a tenant user is to be created when the tenant management is to be used to register the tenant user, and specify "off" if the tenant user is to be registered directly. The initial value is "on". If "off" has been specified, the window for directly registering a tenant user will be displayed when registering a tenant user.

to be performed, and specify "off" if it is not to be performed. The initial value is "off". If "off" has been specified, the Tenant tab will not be displayed on the ROR Console.

tenant management, configure the settings to "on" to include the new password in the body of the password change notification email, or to "off" when not including the password in the email. The default value is set to "on". A new password will be included in the body of the password change notification email in the event that this value is omitted and/or the key is undefined.

leftMenu.modifyUser.admin.visible Specify "on" if changing user account is

to be performed using the account management, and specify "off" if it is not to be performed. The initial value is "on". If "off" has been specified, the Change user account button will not be displayed in the Account window of the account management.

leftMenu.changePassword.admin.visible Specify "on" if changing user password is

to be performed using the account management, and specify "off" if it is not to be performed. The initial value is "on". If "off" has been specified, the Change

- 32 -

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

operation

Specify "on" if changing user account is to be performed using the account management, and specify "off" if it is not to be performed. The initial value is "on". If "off" has been specified, the Change user account button will not be displayed in the Account window of the account management.

leftMenu.changePassword.user.visible Specify "on" if changing user password is

to be performed using the account management, and specify "off" if it is not to be performed. The initial value is "on". If "off" has been specified, the Change user password button will not be displayed in the Account window of the account management.

* note : this can be set by "Setup Wizard" on the ROR Console. A setting example is shown below.

If the line in red font below is missing, please add it.

... omitted allowUpdate = on

setPassword.tenantadmin.mailwithpasswd=off

... omitted leftMenu.modifyUser.admin.visible=on leftMenu.changePassword.admin.visible=on leftMenu.modifyUser.user.visible=on leftMenu.changePassword.user.visible=on

visible.tenantuser=on provisional.acount=on

3. Open the following directory service operation definition file.

[Windows Manager]

Installation_folder\ROR\SVROR\Manager\etc\customize_data\ldap_attr.rcxprop

[Linux Manager]

/etc/opt/FJSVrcvmr/customize_data/ldap_attr.rcxprop

4. The following information must be modified:

Setting item

directory_service (*) Setting for infrastructure

administrators, tenant administrator, and tenant user operation

Settings

Specify "true" if user registration to directory service can be performed and password modification is to be allowed when the tenant management is to be used to register a user, and specify "false" if no user registration to directory service is to be performed and no password modification is to be allowed. The initial value is "true".

- 33 -

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. Note that, if "false" is specified, users must already be registered in the directory service. Perform user registration according to the directory service to be used.

* note : this can be set by "Setup Wizard" on the ROR Console. Edit only the "directory_service" line in the definition file. A setting example is shown below.

directory_service=true

Starting the manager

Start the manager. Refer to "2.1 Starting and Stopping the Manager" for information on how to start the manager.

8.6.2 Editing the User Agreement when Registering a User

Refer to "18.13 Editing the User Agreement when Registering a User" in the "Setup Guide CE" for information on how to edit the agreement displayed in the "Registering Users" window when new tenant users perform the registration procedure.

8.7 Accounting Settings

This section explains how to modify the accounting settings.

8.7.1 Display Function Settings for Estimated Price

Usage fee (the estimated price) for the L-Platform template can be displayed in the L-Platform Management window based on L-Platform template accounting information. This section describes how to modify settings according to whether usage fee (the estimated price) for the L-Platform template will be displayed.

Point

Display Function Settings for Estimated Price can be set by "Setup Wizard" on the ROR Console. See the table below for the settings items can be set by "Setup Wizard" on the ROR Console.

For details of "Setup Wizard", refer to "3.1 Setup Wizard" in the "User's Guide for Infrastructure Administrators CE".

Procedures to modify the settings are as follows:

1. Open the following file.

[Windows Manager]

Installation_folder\RCXCFMG\config\vsys_config.xml

[Linux Manager]

- 34 -

/etc/opt/FJSVcfmg/config/vsys_config.xml

2. The following information must be modified:

Key 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.

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd">

... omitted

<entry key="charge-host">localhost</entry>

<entry key="charge-uri">/resource/ver1.0</entry>

... omitted

</properties>

3. Open the following file.

[Windows Manager]

Installation_folder\RCXCTMG\MyPortal\config\custom_config.xml

[Linux Manager]

/etc/opt/FJSVctmyp/config/custom_config.xml

4. The following information must be modified:

Key Description Default value

estimation-mode (*1) Specifies whether usage fee (the estimated price) for the

L-Platform template will be displayed.

- 3: Display

- 0: Do not display

Set to "3" if use-charge in vsys_config.xml is set to "yes", or to "0" if use-charge is set to "no".

compatible-estimation (*2)

When overcommit is enabled, specify whether to calculate usage fee (the estimated price) using the

false

operating value or the reserved value.

- true: Calculate using operating value (CPU

performance and/or memory capacity)

- false: Calculate using reserved value (reserved CPU

performance and/or reserved memory capacity)

*1 : this can be set by "Setup Wizard" on the ROR Console. *2 : These settings are only valid when the overcommit function is enabled. Refer to "18.6 Settings for the Overcommit Function" in the "Setup Guide CE" for further details. Note also that these settings are only valid when either VMware or Hyper-V is used as the virtual software. If any other virtual

- 35 -

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"?>

... omitted

</properties>

5. Restart the manager.

Refer to "2.1 Starting and Stopping the Manager" for information on how to restart the manager.

8.7.2 Currency Information Settings

Currency information can be changed. Default setting is USD ($). The currency that can be used is shown below.

Currency Currency sign Number of decimal places

United States Dollar $ 2 Japanese Yen ¥ 0 Euro EUR 2 Singapore dollar S$ 2

To change the currency information, perform the following procedure:

1. Stop the manager.

Refer to "2.1 Starting and Stopping the Manager" for information on how to stop the manager.

2. Execute the Change currency information setting command to change the currency information.

Refer to "11.3 currencyset (Change Currency Information Setting)" in the "Reference Guide (Command/XML) CE" for information

on how to use the Change currency information setting command.

3. Start the manager.

Refer to "2.1 Starting and Stopping the Manager" for information on how to start the manager.

Note

Determine the currency used when installing the system. Do not change the currency information once the operation starts.

8.7.3 Metering Log Settings

This section explains how to change the metering log operational settings. Follow the steps below to change the metering log operational settings.

1. Open the following operational settings file for metering logs:

[Windows Manager]

Installation_folder\RCXCTMG\Charging\conf\metering_log.properties

[Linux Manager]

/etc/opt/FJSVctchg/conf/metering_log.properties

- 36 -

2. Change the relevant items in the operational settings file for metering logs:

Key Description Default value

retention_period Retention period of log entries

Logs will be deleted once their retention period has passed.

Use the following format to specify the retention period:

YYYY-MM-DD Example:

0000-03-00: Retain logs for 3 months. 0005-00-00: Retain logs for 5 years.

periodic_log_use (*1)

Specify whether or not to use the periodic log function:

- yes: Use

- no: Do not use

periodic_log_schedule_time (*1)

periodic_log_schedule_type (*1)

Output time of periodic log Use the following format to specify the output time:

HH:mm Output frequency of periodic log

Specify one of the following strings:

- DAILY: Every day

- WEEKLY: Every week

0000-03-00

yes

00:00

DAILY

periodic_log_schedule_day (*1)

- MONTHLY: Every month

Output day of periodic log If periodic_log_schedule_type is WEEKLY or

MONTHLY, this item is mandatory.(*2)

- If periodic_log_schedule_type is WEEKLY:

Use the following strings to specify the day of the week:

- MON

- TUE

WED

- THU

- FRI

- SAT

- SUN

Commas can be used as delimiters to specify a number of days of the week.

- If periodic_log_schedule_type is MONTHLY:

Use one of the following methods to specify a date:

No specification

- Numerics from 1 to 28 indicating the date

- LASTDAY string indicating the last day of the

month

- 37 -

Key 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

# ex. 3 months ago 0000-03-00

retention_period=0000-03-00

# schedule of periodlog insert

periodic_log_use=yes

periodic_log_schedule_time=00:00

periodic_log_schedule_type=DAILY

periodic_log_schedule_day=

3. If an item other than retention_period has been changed, execute the Change periodic log schedule settings command.

Refer to "11.1 ctchg_chgschedule (Change Periodic Log Schedule Settings)" in the "Reference Guide (Command/XML) CE" for

information on the Change periodic log schedule settings command.

Note

Points to note when using the usage charge calculator

- Specify either the default value (3 months) or a period longer than the default value for retention_period.

- Do not change the values for the following keys from the default:

- periodic_log_use

- periodic_log_schedule_time

- periodic_log_schedule_type

- periodic_log_schedule_day

8.7.4 Usage Charge Calculator Settings

This section describes how to change the settings for the usage charge calculator function. The procedure for changing the settings is as follows:

1. Open the following operating environment file:

[Windows Manager]

Installation_folder\RCXCTMG\Charging\conf\accounting.properties

[Linux Manager]

/etc/opt/FJSVctchg/conf/accounting.properties

2. Set the following items in the operating environment file:

- 38 -

Key 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. Specify a value between 1 and 31. In cases where the specified date does not exist, the cut-off date will be the end of the month. For example, if 31 is specified, but the month only contains 30 days, then the 30th will be the cut-off date.

gui.sendmailaddress (*) Specify the default for the address to send

the usage fee displayed in the tenant management window of the ROR console.

usedtime.metering.cpu.perf.vserver When overcommit is enabled, specify

whether to calculate the CPU clock of the virtual server using CPU performance or CPU reserve performance.

- cpu_perf: Calculate with CPU

performance

None

cpu_reserve

- cpu_reserve: Calculate with CPU

reserve performance

usedtime.metering.memory.vserver When overcommit is enabled, specify

whether to calculate the memory usage of the virtual server using memory or memory reserve.

- memory_size: Calculate with memory

- memory_reserve: Calculate with

memory reserve

* note: This can be set by "Setup Wizard" on the ROR Console.

An example is shown below:

accounting.use = yes

... omitted

gui.cutoffdate = 20

gui.sendmailaddress = example@xxx.com

... omitted

usedtime.metering.cpu.perf.vserver = cpu_reserve

usedtime.metering.memory.vserver = memory_reserve

... omitted

3. Restart the Manager.

memory_reserve

Refer to "2.1 Starting and Stopping the Manager" for information on how to restart the manager.

8.8 System Condition Server List Settings

This section explains how to change the System Condition Server List settings.

- 39 -

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.

Note

If the overcommit function is used, the settings must match those of the L-Platform Management overcommit function.

Point

System Condition Server List Setting can be set by "Setup Wizard" on the ROR Console. For details of "Setup Wizard", refer to "3.1 Setup Wizard" in the "User's Guide for Infrastructure Administrators CE".

Use the procedure below to change the System Condition Server List settings.

1. Open the following file:

[Windows Manager]

Installation_folder\SWRBAM\CMDB\FJSVcmdbm\CMDBConsole\WEB-INF\classes\viewlist_en.xml

[Linux Manager]

/opt/FJSVcmdbm/CMDBConsole/WEB-INF/classes/viewlist_en.xml

2. Set the following items:

Settings item

serverByOrg_ROR.bottom.column.11.isEnable Set "true" to display the CPU Reserve Clock Rate. Set "false" to

hide it. The default value is "false".

serverByOrg_ROR.bottom.column.14.isEnable Set "true" to display the Memory Reserve Size. Set "false" to hide

it. The default value is "false".

A settings example is shown below.

<?xml version="1.0" encoding="UTF-8"?>

... omitted

<entry key="serverByOrg_ROR.bottom.column.11.isEnable">false</entry>

<entry key="serverByOrg_ROR.bottom.column.11.label">Reserved CPU clock speed(GHz)</entry>

<entry key="serverByOrg_ROR.bottom.column.11.path">/cmdb:item/cmdb:record[@type='observed']/

rc:LogicalServer/@reservedCPUClock</entry>

... omitted

<entry key="serverByOrg_ROR.bottom.column.14.isEnable">false</entry>

<entry key="serverByOrg_ROR.bottom.column.14.label">Reserved memory size(GB)</entry>

<entry key="serverByOrg_ROR.bottom.column.14.path">/cmdb:item/cmdb:record[@type='observed']/

rc:LogicalServer/@reservedMemorySize</entry>

... omitted

</properties>

Explanation

Note

- If the L-Platform Management overcommit function is disabled, when the viewlist_en.xml overcommit setting is enabled, the CPU

Reserve Clock Rate and the Memory Reserve Size columns are displayed but the values are not displayed.

- 40 -

- 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.

Use the following procedure to change the settings that determine whether to prevent start/end messages from being output to event logs or not.

1. Open the following files

[Windows Manager]

Installation_folder\SWRBAM\CMDB\FJSVcmdbm\axis2\WEB-INF\services\mdr_cfmg\cmdb.properties

Installation_folder\SWRBAM\CMDB\FJSVcmdbm\axis2\WEB-INF\services\mdr_ror\cmdb.properties

[Linux Manager]

/opt/FJSVcmdbm/axis2/WEB-INF/services/mdr_cfmg/cmdb.properties

/opt/FJSVcmdbm/axis2/WEB-INF/services/mdr_ror/cmdb.properties

2. Set the following items:

- schedule.syslog.disable

Change the value above. A modification example is shown below. Change the part in italics.

Set this item to "true" to prevent start/update messages from being output to event logs, or "false" otherwise.

schedule.syslog.disable=true

3. Restart the CMDB.

Open a command prompt and execute the following commands:

[Windows Manager]

Installation_folder\SWRBAM\CMDB\FJSVcmdbm\bin\cmdbstop

Installation_folder\SWRBAM\CMDB\FJSVcmdbm\bin\cmdbstart

[Linux Manager]

/opt/FJSVcmdbm/bin/cmdbstop.sh

/opt/FJSVcmdbm/bin/cmdbstart.sh

8.10 Setting for Directory Service Connection Information

This section explains the procedure for changing the directory service connection information. Refer to "12.4.2 Modifying Directory Service Connection Information" in the "Design Guide CE".

- 41 -

Part 3 Retention

Chapter 9 Hardware Maintenance..................................................................................................................43

Chapter 10 Backup and Restoration..............................................................................................................75

- 42 -

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

use L-Platforms running on the hardware which is the target of maintenance (regular maintenance or patch application) that

maintenance operations will be implemented.

As one method of notification, Resource Orchestrator provides the function which shows the information by displaying

"Information" on the ROR console for tenant administrators or tenant users.

For details, refer to "3.2 Editing the Home Messages" in the "User's Guide for Infrastructure Administrators CE".

2. Stop Managed Servers

When using a physical L-Server, the tenant user must stop the managed server.

3. Change to Maintenance Status

The infrastructure administrator places the resource of the maintenance target into maintenance mode.

- When the maintenance target is a managed server

- When using physical L-Servers

The infrastructure administrator places the physical L-Server 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".

- 43 -

- 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" 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 places the managed server 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".

- When the maintenance target is a network device

When the maintenance target is a network device, the infrastructure administrator places the relevant network device into maintenance mode, and excludes it from being the target of monitoring and auto-configuration.

For details, refer to "Chapter 22.1 Switchover of Maintenance Mode" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

4. Implement Regular Maintenance

The infrastructure administrator performs the maintenance operations such as regular maintenance or patch application.

For details on the maintenance of managed servers, refer to the following sections:

- "9.2 Blade Server Maintenance"

- "9.3 Maintenance for Servers Other Than Blade Servers"

- "9.4 For Servers not Using Server Management Software"

For details on the maintenance of network devices, refer to the following section:

- "9.5 Network Device Maintenance"

5. Release Maintenance Status

The infrastructure administrator releases the resource from maintenance mode.

- When the maintenance target is a managed server

- When using physical L-Servers

The infrastructure administrator releases the physical L-Servers from maintenance mode. For details on maintenance mode, refer to "Appendix C Maintenance Mode" in the "User's Guide for Infrastructure

Administrators (Resource Management) CE".

- For SPARC M10

When replacing or adding server components, if the resources are targets of monitoring, ensure that the information has been updated from the ROR console and then release them from maintenance mode.

When changing the CPU or memory, check the following:

- The [Resource List] tab of the orchestration tree [CPU Capacity (Unused/Total)] and [Memory Capacity (Unused/Total)] of the [VM Host List]

- The [Resource Details] tab of the orchestration tree [CPU Capacity] and [Memory Capacity] under the [VM Host List] and [Capacity]

- The [Available Pool] tab of the orchestration tree [VM Host List], [CPU Capacity (Unused/Total)], and [Memory Capacity (Unused/Total)]

The infrastructure administrator releases the managed servers from maintenance mode.

- 44 -

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.

For details on maintenance mode, refer to "Appendix C Maintenance Mode" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

- When the maintenance target is a network device

The infrastructure administrator adds the network device as the target of monitoring or auto-configuration by releasing it from maintenance mode.

For details, refer to "Chapter 22.1 Switchover of Maintenance Mode" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

6. Notify Users of Maintenance Operation Completion

The infrastructure administrator notifies tenant administrators and tenant users that manage or use L-Platforms running on the

hardware which was the target of maintenance that maintenance operations have been completed.

As one method of notification, Resource Orchestrator provides the function which shows the information by displaying

"Information" on the ROR console for tenant administrators or tenant users.

For details, refer to "3.2 Editing the Home Messages" in the "User's Guide for Infrastructure Administrators CE".

Flow of Corrective Actions when Hardware Fails

The flow of corrective actions when hardware fails is as below.

Figure 9.2 Flow of Corrective Actions when Hardware on which an L-Platform Operates Fails

1. Error Detection

Errors are detected at the following timing:

- When operation errors are reported to the tenant user by the user of the application running on the L-Platform

- When hardware errors are detected by the infrastructure administrator or the infrastructure monitor

- When the status of L-Platform resources used on the ROR console change to something other than "normal"

- 45 -

2. 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.

3. Status Confirmation

The infrastructure administrator identifies the hardware to which resources are allocated using the obtained information, and

confirms their status.

4. Problem Cause Investigation

The infrastructure administrator identifies the cause, by investigating the hardware on which the problem occurred.

5. Corrective Action

The infrastructure administrator takes corrective actions in order to resolve the problems with hardware.

6. Reporting of Investigation Results

The infrastructure administrator reports the results of the investigation, after completing corrective action.

Flow of Hardware Maintenance when a Server Fails

The following flowchart shows the procedure for maintaining hardware when failures occur on registered servers.

- 46 -

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". *3: For details on server switchover, failback, and takeover, refer to "Chapter 4 Server Switchover" in the "Operation Guide VE". *4: For details on backing up and restoring system images, refer to "Chapter 16 Backup and Restore" in the "User's Guide VE". *5: For details on maintenance LED operations, refer to "9.2.1 Maintenance LED". Please note that maintenance LED operations are only supported for PRIMERGY BX servers. *6: For details on reconfiguring hardware properties, refer to "9.3.1 Reconfiguration of Hardware Properties". *7: For details on power control, refer to "Chapter 14 Power Control" in the "User's Guide VE".

The following hardware replacements can be performed:

- Replacing Servers

Replace a server that has been registered in Resource Orchestrator. For details on replacing servers, refer to "9.3.2 Replacing Servers".

- Replacing Server Components

Replace hardware components (such as a NIC, HBA, or hard disk) of a registered server. For details on replacing or adding server components, refer to "9.3.3 Replacing and Adding Server Components".

- 47 -

- 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. Activating a server blade's maintenance LED make it easy to identify a server from others. When replacing servers, it is recommended to use this function to identify which server blade should be replaced.

To activate the maintenance LED of a managed server running either a physical OS or a VM host, the server should be placed into maintenance mode first. For details on maintenance mode, refer to "Appendix C Maintenance Mode" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

Note

- Maintenance LED control is only available for PRIMERGY BX servers. The actual LED used as an identification LED differs between

server models.

- For PRIMERGY BX600 servers, the power LED is used (blinks when activated).

- For PRIMERGY BX900 servers, the ID indicator is used (lit when activated).

- If SNMP agent settings within the management blade configuration are incorrect, maintenance LED operations in Resource

Orchestrator will end successfully, but the state of the identification LED will not change. Configure the settings correctly, referring to "8.2 Configuring the Server Environment" in the "Design Guide CE".

Activating a Maintenance LED

Use the following procedure to activate a server blade's maintenance LED.

1. In the ROR console server resource tree, right-click the target server, and select [LED]-[ON] from the popup menu.

The [Turning on Maintenance LED] dialog is displayed.

2. Click <OK>.

Selecting the [Automatically turn off] checkbox will automatically shut down the server after activating its maintenance LED.

Note

Once the maintenance LED of a server blade is activated, new errors detected in that server cannot be checked from its LED anymore.

Check the server status directly from the ROR console.

Deactivating a Maintenance LED

Use the following procedure to deactivate a server blade's maintenance LED.

1. In the ROR console server resource tree, right-click the target server, and select [LED]-[OFF] from the popup menu.

The [Turning off Maintenance LED] dialog is displayed.

- 48 -

2. 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. If it is not, there is a possibility that operations on the server will not run correctly.

- After replacing the hardware, the server status becomes "unknown". The appropriate status can be restored by reconfiguring the

hardware properties from the server.

Prerequisites

The following prerequisites must be satisfied before this operation can be performed:

- Both the replaced server and replacement server must be the same model

A warning message is shown if the model of the replacement server differs from that of the replaced server.

- When replacing a PRIMERGY BX server, the replacement server must be inserted into the same slot as used for the replaced server

Hardware properties cannot be reconfigured from a server inserted in a different slot. An error occurs if no server is inserted in the slot occupied by the previous server.

- The replaced server and replacement server must both be of the same blade type

If the blade types of the replaced and replacement servers are different, an error will occur.

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.

Pre-Configuration

For PRIMERGY BX servers, the hardware properties are automatically reconfigured. If automatic reconfiguration is not necessary for PRIMERGY BX servers, delete the following file, and then restart the manager.

Placeholder for the Definition File

[Windows Manager]

Installation_folder

[Linux Manager] /etc/opt/FJSVrcvmr/customize_data

Name of the Definition File

\SVROR\Manager\etc\customize_data

auto_replace.rcxprop

Reconfiguring Hardware Properties after Server Replacement

If the definition file has already been created, there is no need to set the hardware information again. If the definition file has not been created, use the following procedure to reconfigure properties for replaced hardware.

- 49 -

1. 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.

2. 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.

The [Re-configure Hardware Properties] dialog is displayed.

3. Click <OK>.

The original hardware properties of the selected managed server are updated with new hardware properties obtained from the

replacement server. If the maintenance LED is on it will be turned off automatically.

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.2.3 Replacing Servers

This section details the procedure to follow when replacing servers.

Information

- Follow the same procedure when replacing servers where VM hosts are running.

- No specific action is required in Resource Orchestrator when replacing admin servers or HBA address rename setup service servers.

- Replacing a Server with Spare Servers Assigned

Use the following procedure to switch applications over to a spare server and replace a server with minimal interruption.

1. Perform Server Switchover

Switch over the server to replace with its spare server. For server switchover, refer to "Chapter 4 Server Switchover" in the "Operation Guide VE". After the server has been switched over, its maintenance LED is automatically activated, and the server is powered down.

2. Replace the Server

Replace the server whose maintenance LED is activated. 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" in the "Design Guide CE". Shut down the server after completing BIOS settings.

3. 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". After hardware properties have been reconfigured, the maintenance LED is automatically turned off in the ROR console.

4. 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".

- 50 -

- Replacing a Server with no Spare Server Assigned

Use the following procedure to smoothly replace a server and resume its applications.

1. 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".

2. 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.

3. Activate the Maintenance LED

Activate the maintenance LED on the server that is to be replaced before shutting it down. For details on how to activate maintenance LEDs, refer to "9.2.1 Maintenance LED".

4. Replace the Server

5. Reconfigure Hardware Properties after Replacement

6. Restore the Boot Disk

- Local Boot

There is no need to restore the boot disk if the original disk is installed on the replaced server. Simply power on the replacement server.

If the boot disk was replaced and a system image backup was collected, restore that backup. Refer to "16.3 Restoring a System Image" in the "User's Guide VE" for details on how to restore a system image. After the system image is restored, the server will be automatically powered on. If there is no backup of the system image, run the installation program again.

- SAN Boot

As the replaced server can be easily configured to access the original boot disk using HBA address rename there is no need to restore the boot disk. Simply power on the replacement server.

7. Release Maintenance Mode

Release the replaced server from maintenance mode. For details on maintenance mode, refer to "Appendix C Maintenance Mode" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

- Servers with no Agent Registered

Use the following procedure to replace servers on which no Resource Orchestrator agent was registered.

1. Activate the Maintenance LED

Activate the maintenance LED on the server that is to be replaced and shut down the server if it is still powered on. For details on how to activate maintenance LEDs, refer to "9.2.1 Maintenance LED".

2. Replace the Server

Replace the server whose maintenance LED is activated. Change the BIOS settings of the replacement server to match the operating environment.

- 51 -

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.

3. Reconfigure Hardware Properties after Replacement

9.2.4 Replacing Non-Server Hardware

This section explains how to replace hardware external to servers.

- Replacing Chassis

No specific action is required in Resource Orchestrator.

- Replacing Management Blades

No specific action is required in Resource Orchestrator.

- Replacing LAN Switch Blades

No specific action is required for PRIMERGY BX900/BX400 LAN switch blades in IBP mode. For other LAN switch blades of PRIMERGY BX models, after replacing a switch blade, update the new LAN switch blade with the VLAN settings that were previously configured in Resource Orchestrator. Use the following procedure to replace a LAN switch blade.

1. Replace the faulty LAN switch blade.

2. Restore the LAN switch blade configuration backup (which includes all of the LAN switch blade settings) to the new LAN

switch blade. For LAN switch blades (PY CB DCB SW 10Gb 18/6/6), the Automatic Migration of Port Profile (AMPP) configuration of all

ports and VLAN settings of external ports must be restored manually. If the LAN switch blade configuration was not been backed up in advance, it has to be restored by configuring each setting

(except VLAN settings) to the same values set during the initial installation. Refer to the manual of the LAN switch blade used for details on how to back up and restore LAN switch blade configurations.

3. Update the new LAN switch blade with the latest VLAN settings configured in Resource Orchestrator. a. In the ROR console server resource tree, right-click the target LAN switch, and select [Restore] from the popup menu.

The [Restore LAN Switch] dialog is displayed.

b. Click <OK>.

VLAN settings are applied to the specified LAN switch blade. For LAN switch blades (PY CB DCB SW 10Gb 18/6/6), only the VLAN settings of internal ports for which an Automatic

Migration of Port Profile (AMPP) has not been configured are restored.

Note

To replace LAN switch blades with different models, first delete the registered LAN switch blade, and then register the replacement LAN switch blade. After the LAN switch blade is registered, the VLAN settings must be configured for the internal and external ports. For details on the VLAN settings, refer to "5.4.4 Configuring VLANs on LAN Switch Blades" in the "User's Guide for Infrastructure Administrators (Resource Management) CE". When the following configurations before and after replacement of a PRIMERGY BX900/BX400 series LAN switch blade are different, delete the registered LAN switch blade and register it again.

- Operation mode (IBP and another mode, VCS and another mode)

- VCS ID

- 52 -

- 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.

Use the following procedure to replace a storage blade that contains the boot disk of a server blade.

1. Replace the storage blade.

2. Insert the server blade's boot disk in the new storage blade.

3. If the boot disk's content was backed up, restore it.

Information

The backup and restore functions available in Resource Orchestrator can be used to restore the boot disk contents. For details, refer to "Chapter 16 Backup and Restore" in the "User's Guide VE".

9.3 Maintenance for Servers Other Than Blade Servers

This section explains server maintenance for servers other than blade servers.

9.3.1 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.

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. If it is not, there is a possibility that operations on the server will not run correctly.

- When the system board or GSPB of a PRIMEQUEST server has been changed, ensure that this operation is performed.

If it is not, there is a possibility that operations on the server will not run correctly.

- After replacing the hardware, the server status becomes "unknown". The appropriate status can be restored by reconfiguring the

hardware properties from the server.

Prerequisites

The following prerequisites must be satisfied before this operation can be performed:

- Both the replaced server and replacement server must be the same model

A warning message is shown if the model of the replacement server differs from that of the replaced server.

- The replaced server and replacement server must both be of the same blade type

If the blade types of the replaced and replacement servers are different, an error will occur.

- 53 -

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.

1. If the agent or ServerView Agents has already been registered, power on the server.

Additional Information

When a server using SAN boot has a hardware exchange that results in the MAC address used for the admin LAN being changed, the OS and an agent cannot be started. In this case, the server should be started once, and the MAC address confirmed on the BIOS (hardware) screen. After the MAC address is confirmed, power off the server again.

2. In the ROR console server resource tree, right-click the target server and select [Hardware Maintenance]-[Reconfigure] from

the popup menu. The [Re-configure Hardware Properties] dialog is displayed.

3. Enter MAC addresses for the network interfaces used on the admin LAN.

This step can be skipped if no network interface was replaced.

- Admin LAN MAC Address (NIC1)

Required only if the agent is not registered.

Additional Information

When a server is powered off for the reason given in the Additional Information in step 1, the item for input of the value of NIC1 is displayed. In this case, input the MAC address confirmed in the Additional Information in step 1.

- MAC address (NIC2) under SAN Boot/admin LAN redundancy

This item is only required for the following cases:

- When using the HBA address rename setup service

- When using GLS for admin LAN redundancy on the target server

- For the spare server of a managed server using admin LAN redundancy

4. Click <OK>.

The original hardware properties of the selected managed server are updated with new hardware properties obtained from the replacement server.

- For PRIMEQUEST Servers

Use the following procedure to reconfigure properties for replaced hardware.

1. Replace the system board or GSPB, and insert the server.

2. 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. The [Re-configure Hardware Properties] dialog is displayed.

3. Click <OK>.

The original hardware properties of the selected managed server are updated with new hardware properties obtained from the replacement server.

- For SPARC Servers/SPARC Enterprise Servers

Note that in this case there is no need to set the hardware information again.

- 54 -

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.

Information

- Follow the same procedure when replacing servers where VM hosts are running.

- No specific action is required in Resource Orchestrator when replacing admin servers or HBA address rename setup service servers.

For Rack Mount and Tower Servers

- Replacing a Server Assigned with Spare Servers

Use the following procedure to switch applications over to a spare server and replace a server with minimal interruption.

1. Perform Server Switchover

Switch over the server to replace with its spare server. For server switchover, refer to "Chapter 4 Server Switchover" in the "Operation Guide VE". The server to replace is automatically powered off after switchover.

2. Replace the Server

Replace the server. 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" in the "Design Guide CE". Shut down the server after completing BIOS settings. Configure the remote management controller of the replacement server with the same IP address, user name, password, and SNMP trap destination as those set on the original server.

3. Reconfigure Hardware Properties after Replacement

When using VIOM, refer to the manual of ServerView Virtual-IO Manager and perform inventory boot on ServerView VirtualIO Manager.

4. 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.

1. Place the Server into Maintenance Mode

- 55 -

2. Create a System Image Backup

3. Power OFF

Shut down the server to replace if it is still powered on. For details on shutting down servers, refer to "Chapter 14 Power Control" in the "User's Guide VE".

4. Replace the Server

5. Reconfigure Hardware Properties after Replacement

When using VIOM, refer to the manual of ServerView Virtual-IO Manager and perform inventory boot on ServerView VirtualIO Manager.

6. Restore the Boot Disk

- Local Boot

There is no need to restore the boot disk if the original disk is installed on the replaced server. Simply power on the replacement server. If the boot disk was replaced and a system image backup was collected, restore that backup. Refer to "16.3 Restoring a System Image" in the "User's Guide VE" for details on how to restore a system image. After the system image is restored, the server will be automatically powered on. If there is no backup of the system image, run the installation program again.

- SAN Boot

The replaced server can be easily configured to access the original boot disk using I/O virtualization. Therefore, there is no need to restore the boot disk. Simply power on the replacement server.

7. Release Maintenance Mode

- Servers with no Agent Registered

Use the following procedure to replace servers on which no Resource Orchestrator agent was registered.

1. Power OFF

Shut down the server to replace if it is still powered on. For details on shutting down servers, refer to "Chapter 14 Power Control" in the "User's Guide VE".

2. Replace the Server

Replace the target server. 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" in the "Design Guide CE". Shut down the server after completing BIOS settings. Configure the remote management controller of the replacement server with the same IP address, user name, password, and SNMP trap destination as those set on the original server.

- 56 -

3. Reconfigure Hardware Properties after Replacement

When using VIOM, refer to the manual of ServerView Virtual-IO Manager and perform inventory boot on ServerView VirtualIO Manager.

For SPARC Servers/SPARC Enterprise Servers

- Replacing a Server with Spare Servers Assigned

Use the following procedure to switch applications over to a spare server and replace a server with minimal interruption.

- When Replacing an HBA

1. Perform Server Switchover

2. Replace the Server

Replace the HBA of the server. Change the OBP settings of the replacement server to match the operating environment. For details on OBP settings, refer to "8.2 Configuring the Server Environment" in the "Design Guide CE". Shut down the server after completing OBP settings. Configure the remote management controller of the replacement server with the same IP address, user name, password, and SNMP trap destination as those set on the original server.

3. Change the WWN Information Settings

Change the WWN information settings for after server replacement to the WWN value of the HBA after server replacement. Leave the value of the target CA as the one before changes were made.

4. 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".

Note

If takeover was performed before replacement of the HBA, release the spare server settings. Change the WWN information settings following the procedure in "Replacing a server with no spare server assigned".

- When not Replacing an HBA

1. Perform Server Switchover

2. Replace the Server

Replace components (other than the HBA) of the server. Change the OBP settings of the replacement server to match the operating environment. For details on OBP settings, refer to "8.2 Configuring the Server Environment" in the "Design Guide CE". Shut down the server after completing OBP settings. Configure the remote management controller of the replacement server with the same IP address, user name, password, and SNMP trap destination as those set on the original server.

- 57 -

3. 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.

1. Delete the Target CA

When there are target CA settings in the WWN information, stop the server and then delete the target CA settings (set them as hyphens ("-")).

2. Replace the Server

Replace the HBA of the server. Change the OBP settings of the replacement server to match the operating environment. For details on OBP settings, refer to "8.2 Configuring the Server Environment" in the "Design Guide CE". Shut down the server after completing OBP settings. When the target CA was deleted in step 1, configure zoning and host affinity settings in the WWPN value of the replacement HBA. For details, refer to the ESC users guide.

3. Change the WWN Information Settings

Change the WWN information settings for after server replacement to the WWN value of the HBA after server replacement. When the target CA was deleted in step 1, configure a new target CA. After configuration, restart the server. After starting the server, check the status of the server's HBA from ESC. When the HBA status is "unknown", delete it. When the HBA status is displayed as "access path inheritance is required" (yellow icon), perform access path inheritance. For details, refer to the ESC users guide. When the target CA was not deleted in step 1, configure the target CA as a hyphen ("-").

- When SPARC M10-4S are in a Building Block Configuration

No specific action is required in Resource Orchestrator.

For PRIMEQUEST Servers

- Replacing a Server Assigned with Spare Servers

Use the following procedure to switch applications over to a spare server and replace a server with minimal interruption.

1. Perform Server Switchover

Switch over the server to replace with its spare server. For server switchover, refer to "Chapter 4 Server Switchover" in the "Operation Guide VE". The server is automatically powered off after switchover.

2. 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" in the "Design Guide CE". Shut down the server after completing BIOS settings.

3. Reconfigure Hardware Properties after Replacement

- 58 -

4. 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.

1. Place the Server into Maintenance Mode

2. Create a System Image Backup

3. Power OFF

Shut down the server to replace if it is still powered on. For details on shutting down servers, refer to "Chapter 14 Power Control" in the "User's Guide VE".

4. Replace the Server

5. Reconfigure Hardware Properties after Replacement

6. Restore the Boot Disk

- Local Boot

- SAN Boot

As the replaced server can be easily configured to access the original boot disk using HBA address rename there is no need to restore the boot disk. Simply power on the replacement server.

7. Release Maintenance Mode

- Servers with no Agent Registered

Use the following procedure to replace servers on which no Resource Orchestrator agent was registered.

1. Power OFF

Shut down the server to replace if it is still powered on. For details on shutting down servers, refer to "Chapter 14 Power Control" in the "User's Guide VE".

- 59 -

2. Replace the Server

3. Reconfigure Hardware Properties after Replacement

9.3.3 Replacing and Adding Server Components

This section explains how to replace and add server components.

- Replacing and Adding Network Interfaces (Admin LAN, Public LAN)

The procedure used to replace and add network interfaces is the same as that described in "9.3.2 Replacing Servers". For details, refer to "9.3.2 Replacing Servers".

When adding or removing network interfaces, if the target server is running Red Hat Enterprise Linux 5 or Citrix XenServer, after completing the steps described in "9.3.2 Replacing Servers", log in with administrative privileges on the managed server and execute the following command.

# /usr/local/sbin/macbindconfig create <RETURN>

[Xen] When using Citrix XenServer, reinstall XenServer referring to the Citrix XenServer manual.

When using Red Hat Enterprise Linux 5 Virtualization (Xen-Based) and not using I/O Virtualization (VIOM), perform the following procedure.

1. Execute the following command to temporally disable automatic startup of the xend daemon and then restart the managed

server.

# chkconfig xend off <RETURN>

2. Once the server has restarted, execute the following commands to update MAC address bindings, re-enable automatic startup

of the xend daemon, and restart the xend daemon itself.

# /usr/local/sbin/macbindconfig create <RETURN> # chkconfig xend on <RETURN> # service xend start <RETURN>

[Linux] When the configuration of server components has been changed, check the configuration file of the OS, and make any necessary corrections. For details, refer to "Configuration File Check" in "2.2.1.1 Software Preparation and Checks" in the "Setup Guide CE".

[Red Hat Enterprise Linux 6] When adding or removing network interfaces, if the target server is running Red Hat Enterprise Linux 6, after completing the steps described in "9.3.2 Replacing Servers", modify the configuration file. For details, refer to "Configuration File Check" in "2.2.1.1 Software Preparation and Checks" in the "Setup Guide CE".

- Replacing a GSPB

The procedure used to replace a GSPB is the same as that described in "Replacing a network interface". Replace NIC with GSPB in the procedure.

- Replacing an HBA

The procedure used to replace an HBA is the same as that described in "9.3.2 Replacing Servers".

- 60 -

- 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" in the "User's Guide VE".

- Replacing a boot disk (in local boot environments)

Use the following procedure to replace a boot disk.

1. Replace the faulty boot disk with a new one.

2. If the boot disk's content was backed up, restore it.

Information

The backup and restore functions available in Resource Orchestrator can be used to restore the boot disk contents. For details, refer to "Chapter 16 Backup and Restore" in the "User's Guide VE".

- Replacing a System Board

The procedure used to replace a system board is the same as that described in "9.3.2 Replacing Servers".

- Replacing an IO Board

No specific action is required in Resource Orchestrator when replacing an IO board.

- Replacing Other Server Components

No specific action is required in Resource Orchestrator when replacing onboard server components like memory modules or other parts.

[Solaris Zones] When replacing, adding, or removing a CPU, add the replaced, added, or removed CPU to the resource pool for Solaris Zones, or remove it depending on your environment.

For details, refer to "C.7 Solaris Zones" in the "Setup Guide CE".

9.3.4 Replacing Non-server Hardware

This section explains how to replace hardware external to servers.

- Replacing Management Blades

No specific action is required in Resource Orchestrator. No specific action is required when updating firmware. When performing replacements or upgrading firmware, the status of the chassis and server blades mounted in the chassis may change to "unknown".

- Replacing Management Boards

- Replacing LAN Switches

No specific action is required in Resource Orchestrator when replacing a LAN switch. No specific action is required when updating firmware. When performing replacements or upgrading firmware, the status of LAN switches may change to "unknown".

9.4 For Servers not Using Server Management Software

This section explains how to maintain servers not using server management software.

- 61 -

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.

- For Virtual L-Servers

For details on definition files, refer to "C.1.4 Configuration when Creating a Virtual L-Server Using a Server which cannot Use ServerView Agents" in the "Setup Guide CE".

- For Physical L-Servers

For details on definition files, refer to "B.1.6 Configuration when Creating a Physical L-Server without Specifying a Model Name in the L-Server Template" in the "Setup Guide CE".

In the following cases, reflect the correct value on the definition file before reconfiguring the hardware information.

- When defining the configuration information (CPU core count, CPU clock speed, memory capacity, etc.) of the target server after

registering it with Resource Orchestrator

- When modifying the configuration information (CPU core count, CPU clock speed, memory capacity, etc.) of a server that has been

registered with Resource Orchestrator, in the definition file

For details on reconfiguring hardware properties, refer to "9.3.1 Reconfiguration of Hardware Properties".

9.5 Network Device Maintenance

This section explains how to maintain network devices that are the target of management in Resource Orchestrator.

9.5.1 Replacement Procedure of Network Devices

This section explains the procedure to replace network devices when it becomes necessary due to failure.

- 62 -

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.

When the Management Function for Network Device Configuration Files is not Used

1. Announcement of planned maintenance operations.

2. Change the target network device to "maintenance mode".

3. Replace the network devices. (Hardware maintenance person)

4. Restore configuration of replaced network devices following the maintenance procedure for the network device.

5. Release the "maintenance mode" of network devices, when problems with network devices after replacement have been solved.

6. Notification that maintenance operations are complete.

- 63 -

When the Management Function for Network Device Configuration Files is Used

1. Announcement of planned maintenance operations.

2. Change the target network device to "maintenance mode".

3. Replace the network devices. (Hardware maintenance person)

4. 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.

- When performing restoration by logging in to the replaced network device directly

1. Retrieve the network device file which was backed up beforehand using the rcxadm netdevice cfexport command.

2. Restore the exported network device file using the maintenance procedure of the network device.

- When performing restoration using the restoration function of the management function for network device files

1. Configure the replaced network device definition as necessary for operation management.

2. Restore the network device file.

Information

- When the replaced network device is a "Cisco ASA 5500 series", restoration using the rcxadm netdevice cfrestore command

is not required. Using the function of the "Cisco ASA 5500 series", the same configuration as the device in active state is reflected 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.

5. Back up the current network device files from the network devices with operational status.

If the content of the backed up device configuration file is up to date, this step is not required. If the content is not up to date, take a backup of the network device configuration file using the rcxadm netdevice cfbackup command. The date and time of backup can be checked using the rcxadm netdevice cflist command.

6. Check that there are no differences in the definitions that become a problem in the redundancy configurations that use the network

device files used in step 4 and the network device configuration file in the network device file backed up in step 5. Export each network device configuration file using the rcxadm netdevice cfexport command and check the difference. When there is difference that becomes a problem, please resolve difference following the maintenance procedure for network

devices. For the maintenance procedures for network devices, refer to the manual of the network device.

7. Release the "maintenance mode" of network devices, when problems with network devices after replacement have been solved.

8. Notification that maintenance operations are complete.

9.5.1.2 When the Device to Replace has not Failed

This section explains the replacement procedure when the network device that is the target of replacement has not failed.

When the Management Function for Network Device Configuration Files is not Used

1. Announcement of planned maintenance operations.

2. Log in the network device directly to check if the target network device of replacement is in active status or standby status.

When the target network device of replacement is in active status, switch over the device with the standby network device of redundancy configuration, and change the status of target network device for replacement from active status to standby status.

- 64 -

3. Change the target network device to "maintenance mode".

4. Back up the current environment (such as definitions) from the network devices that are switched to "maintenance mode".

5. Replace the network devices. (Hardware maintenance person)

6. Restore the configuration of the replaced network device using the environment backed up in step 4, following the maintenance

procedure for the network device.

7. Back up the current definitions from the network devices with operational status.

8. Check that there are no differences in the definitions in the redundancy configurations using environments backed up in step 7 and

environment definitions backed up in step 4. When there is difference that is a problem, log in to the network device directly after replacement, and resolve the difference.

9. Release the "maintenance mode" of network devices, when problems with network devices after replacement have been solved.

10. Notification that maintenance operations are complete.

When the Management Function for Network Device Configuration Files is Used

1. Announcement of planned maintenance operations.

2. Log in the network device directly to check if the target network device of replacement is in active status or standby status.

3. Change the target network device to "maintenance mode".

4. Back up the current network device files from the network devices that have been switched to "maintenance mode".

5. Replace the network devices. (Hardware maintenance person)

Information

When registering a "Nexus 5000 series" as a network device using the management function for the network device file, check the note of "9.4.8.2 When Using the Network Device File Management Function" in the "Design Guide CE" before executing the restoration in step 6.

6. Restore the configuration of the replaced network device using the network device file which was backed up in step 4, following

the maintenance procedure for the network device.

- When performing restoration by logging in to the replaced network device directly

1. Export the network device file which was backed up in step 4 with the rcxadm netdevice cfexport command.

2. Restore the exported network device file using the maintenance procedure of the network device.

- When performing restoration using the restoration function of the management function for network device files

1. Configure the replaced network device definition as necessary for operation management.

2. Restore the network device file.

Information

- When the replaced network device is a "Cisco ASA 5500 series", restoration using the rcxadm netdevice cfrestore command

is not required. Using the function of the "Cisco ASA 5500 series", the same configuration as the device in active state is reflected

- 65 -

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.

7. Back up the current network device files from the network devices with operational status.

8. Check that there are no differences in the definitions that become a problem in the redundancy configurations that use the network

device files used in step 4 and the network device configuration file in the network device file backed up in step 7. Export each network device configuration file using the rcxadm netdevice cfexport command and check the difference. When there is difference that becomes a problem, please resolve difference following the maintenance procedure for network

devices. For the maintenance procedures for network devices, refer to the manual of the network device.

9. Release the "maintenance mode" of network devices, when problems with network devices after replacement have been solved.

10. Notification that maintenance operations are complete.

See

- When checking the configuration of a network device, you may not be able to confirm it from the network device environment file.

Check in the manual of the network device if it is possible to check the configuration of the network device from the network device environment file, in advance.

- For details on how to configure and release the maintenance mode, refer to "22.1 Switchover of Maintenance Mode" in the "User's

Guide for Infrastructure Administrators (Resource Management) CE".

- For details on the rcxadm netdevice command, refer to "3.8 rcxadm netdevice" in the "Reference Guide (Command/XML) CE".

Note

- Replacement using the same model is a prerequisite when replacing network devices.

- Confirm the following items, using the manuals of network devices, in advance.

- The replacement procedure when using redundancy configurations

- The operations for network devices (status check and switchover)

- Environmental differences which become problems when configuring redundancy configurations

When the network device file management function is not used, confirm the following item, in the manuals of network devices, in advance.

- The operations for network devices (backup methods and restore methods)

- When using the network devices of redundancy configurations, replace network devices in the following order.

1. Replace network devices with standby status

2. Set the status of the network device before replacement to standby, and replace the device

When replacing multiple network devices of redundancy configurations simultaneously, perform replacement operations in units of the same redundancy configurations.

- 66 -

- 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.

9.5.2 Regular Maintenance Procedure of Network Devices

This section explains the procedure of regular maintenance (patch application or firmware update) of network devices. Use the following procedure when performing maintenance operations while continuing operations using the network devices of

redundancy configurations by switching between active and standby. When there is no description, the following operations are performed by an infrastructure administrator.

1. Announce that regular maintenance operations are being started.

2. Confirm that the network device that is the target of regular maintenance is in standby status, by directly logging in to the network

device.

3. Back up the current network device configuration file from the network device with standby status.

- When the Management Function for Network Device Configuration Files is Used

If the content of the configuration file is up to date, this step is not required. If the content is not up to date, back up the configuration file using the rcxadm netdevice cfbackup command. The date and time of backup can be checked using the rcxadm netdevice cflist command.

- When the Management Function for Network Device Configuration Files is not Used

Back up the configuration files from network devices. For information about the backup method, refer to the network device manuals.

4. Change the target network device in standby status to "maintenance mode".

5. A hardware maintenance person performs the regular maintenance operations for network devices (patch application or firmware

update).

6. Back up the current network device configuration files from the network devices with operational status.

- When the Management Function for Network Device Configuration Files is Used

- When the Management Function for Network Device Configuration Files is not Used

Back up the configuration files from network devices. For information about the backup method, refer to the network device manuals.

7. Check that there are no differences between the network device configuration files backed up in step 3 and those backed up in step

- When the Management Function for Network Device Configuration Files is Used

Export the configuration file using the rcxadm netdevice cfexport command, and check for any differences. When there is difference that is a problem, log in to the network device with standby status, and resolve the difference.

- When the Management Function for Network Device Configuration Files is not Used

Export the network device file from the network device and check it for difference. When there is difference that is a problem, log in to the network device with standby status, and resolve the difference. For information about how to export, refer to the network device manuals.

For information about login to network devices, refer to the network device manuals.

8. Release the network device from "maintenance mode", after checking that problems with network devices with standby status have

been solved.

- 67 -

9. 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.

10. 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.

11. Announce that maintenance operations are complete.

See

- For details on how to configure and release the maintenance mode, refer to "22.1 Switchover of Maintenance Mode" in the "User's

Guide for Infrastructure Administrators (Resource Management) CE".

- For details on the rcxadm netdevice command, refer to "3.8 rcxadm netdevice" in the "Reference Guide (Command/XML) CE".

Note

- Regular maintenance may not be able to be performed using the described procedure depending on the maintenance details for

individual network devices. Before performing regular maintenance operations, ensure you check the information provided from the network device vendors regarding the maintenance operations of network devices.

- Confirm the following items, using the manuals of network devices, in advance.

- The operations for network devices (status check, switchover and backup methods)

- Environmental differences which become problems due to redundancy configurations

- When performing regular maintenance for multiple network devices of redundancy configurations simultaneously, perform

replacement operations in units of the same redundancy configurations.

9.5.3 Procedure for Addition of Network Devices

This section explains the operation for adding network devices.

9.5.3.1 Adding L2 Switches to Handle Insufficient Numbers of Ports when Adding Servers

This section explains the procedure for addition, assuming a case where it is necessary to add L2 switches, since the LAN ports of the L2 switch to connect to are insufficient when adding servers.

The explanation is mainly about operations related to L2 switches. When there is no description, the following operations are performed by an infrastructure administrator.

- 68 -

Figure 9.5 Image of L2 Switches to Add

1. Design additional configurations. (Network device administrator)

2. 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

3. Register the resources of the server.

It is necessary to register chassis or LAN switch blades for a blade server.

4. Create network configuration information (XML definition) using the acquired network device information.

5. Register an additional L2 switch as a network device.

Use the rcxadm netdevice create command to register as a network device.

- 69 -

6. 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.

- When using a model for which sample scripts are not prepared, or even when using a model which has been used in the system

until now, by configuring definitions using the different rules (scripts)

- Even when using a model for which sample scripts are prepared, and when using a model with definitions configured using

different rules (scripts)

Note

Details of sample scripts may be reviewed and modified. When using rulesets modified from prepared sample scripts, the modified details will be cleared by replacing the modified scripts with the sample scripts, when updating sample scripts. In order to prevent this type of problem, when creating scripts by referring to sample scripts, create the new rulesets after copying the rulesets of the sample script, and perform necessary modifications.

7. Change all resources using the additional network devices.

It is necessary to add the information about uplink ports of the added chassis, when adding a blade server. Use the rcxadm network modify command to modify a network resource.

8. Register the added server as a resource in the necessary resource pool.

See

- For details on the initial configurations of network devices, refer to "9.2.3 Settings for Managed Network Devices" in the "Design

Guide CE".

- For details on how to create network configuration information (XML definition), refer to "15.6 Network Configuration Information"

in the "Reference Guide (Command/XML) CE".

- For details on the rcxadm netdevice command, refer to "3.8 rcxadm netdevice" in the "Reference Guide (Command/XML) CE".

- For details on ruleset creation and the registration destinations, refer to "F.3 Creating a Folder for Registering Rulesets" in the "Setup

Guide CE".

- For details on the rcxadm network command, refer to "3.9 rcxadm network" in the "Reference Guide (Command/XML) CE".

- For details on how to register a resource in a resource pool, refer to "Chapter 19 Resource Operations" in the "User's Guide for

Infrastructure Administrators (Resource Management) CE".

9.5.3.2 Adding Firewalls, Server Load Balancers, and L2 Switches for Additional Tenants

This section explains the procedure for addition, assuming a case where it is necessary to add a network device or a server in order to add a tenant.

The explanation is mainly about operations related to firewalls, server load balancers, and L2 switches. When there is no description, the following operations are performed by an infrastructure administrator.

- 70 -

Figure 9.6 Image of Tenants to Add

1. Design additional configurations. (Network device administrator)

2. 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

3. Register the resources of the server.

It is necessary to register chassis or LAN switch blades for a blade server.

4. Create network configuration information (XML definition) using the acquired network device information.

- 71 -

5. 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.

6. 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.

- When using a model for which sample scripts are not prepared, or even when using a model which has been used in the system

until now, by configuring definitions using the different rules (scripts)

- Even when using a model for which sample scripts are prepared, and when using a model with definitions configured using

different rules (scripts)

Note

7. Create a tenant and register a tenant administrator.

8. Back up environments using the functions provided by the firewall and server load balancer.

Backups can be used for restoration when replacing firewalls or server load balancers due to device failure. For details on how to back up environments, refer to the manuals of the firewall and server load balancer being used.

9. Register additional servers, firewalls, and server load balancers in a resource pool for tenants as resources.

See

- For details on the initial configurations of network devices, refer to "9.2.3 Settings for Managed Network Devices" in the "Design

Guide CE".

- For details on how to create network configuration information (XML definition), refer to "15.6 Network Configuration Information"

in the "Reference Guide (Command/XML) CE".

- For details on the rcxadm netdevice command, refer to "3.8 rcxadm netdevice" in the "Reference Guide (Command/XML) CE".

- For details on ruleset creation and the registration destinations, refer to "F.3 Creating a Folder for Registering Rulesets" in the "Setup

Guide CE".

- For details on how to create a tenant, refer to "11.3 Creating Tenants" in the "User's Guide for Infrastructure Administrators CE".

- For details on how to register tenant administrators, refer to "Chapter 3 Operating User Accounts" in the "User's Guide for Infrastructure

Administrators (Resource Management) CE".

- For details on how to register a resource in a resource pool, refer to "Chapter 19 Resource Operations" in the "User's Guide for

Infrastructure Administrators (Resource Management) CE".

9.5.4 Procedure for Addition or Modification of Connection Destinations of

Network Devices

This section explains the procedure for adding or modifying destinations for network device connection. When there is no description, the following operations are performed by an infrastructure administrator.

1. Notify your infrastructure administrator about the addition or modification of the destination for network device connection.

(Network device administrator)

- 72 -

2. Create network configuration information (XML definition) using the acquired network device information.

3. 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.

If there is any difference, check with the system administrator that network device configurations have not been modified, and change the network configuration information if necessary.

The network configuration information of network devices registered in Resource Orchestrator can be obtained using the rcxadm netconfig export command.

4. Modify the network device by setting the confirmed network configuration information as the input information.

Use the rcxadm netdevice modify command to modify network devices.

5. Confirm from the ROR console that the network device information has changed, and the status is normal.

See

- For details on how to create network configuration information (XML definition), refer to "15.6 Network Configuration Information"

in the "Reference Guide (Command/XML) CE".

- For details on the rcxadm netconfig command, refer to "3.7 rcxadm netconfig" in the "Reference Guide (Command/XML) CE".

- For details on the rcxadm netdevice command, refer to "3.8 rcxadm netdevice" in the "Reference Guide (Command/XML) CE".

9.6 Storage Device Maintenance

This section explains how to maintain storage devices.

- Replacing storage devices

No specific action is required in Resource Orchestrator. In Resource Orchestrator, the settings for storage devices are not restored. Restore the settings for storage devices based on the information in hardware manuals.

- Replacing Fibre Channel switches

No specific action is required in Resource Orchestrator. In Resource Orchestrator, the settings for Fibre Channel switches are not restored. Restore the settings for Fibre Channel switches based on the information in hardware manuals.

9.7 Power Monitoring Device (PDU or UPS) Maintenance

This section explains how to maintain power monitoring devices (PDU or UPS).

- Replacing power monitoring devices (PDU or UPS)

After replacing a power monitoring device, reconfigure the hardware properties of the power monitoring device (PDU or UPS). Use the following procedure to replace a power monitoring device.

1. Replace the faulty power monitoring device.

2. Set the admin LAN IP address and SNMP community on the replacement device to the same values as those that were set on

the faulty device.

- 73 -

3. Reconfigure the power monitoring device's hardware properties. a. 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.

b. Click <OK>.

The target power monitoring device's hardware properties are reconfigured.

- 74 -

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. With either method, backup can be performed by executing one command (the rcxmgrbackup command). For details on the rcxmgrbackup command, refer to "6.6 rcxmgrbackup" in the "Reference Guide (Command/XML) CE".

- Offline Backup

The manager of this product is stopped and then resources are backed up. A backup is taken at the following times:

- When installation of this product has completed

When using an offline backup, backup of the following resource is not performed:

- Audit log

- Network device configuration file

- Online Backup

Resources are backed up without the manager of this product being stopped. Backing up periodically is recommended for online backups.

To save time when restoring configuration information at operation, take an online backup if configuration information is to be updated. When using an online backup, backup of the following resources is not performed:

- Dashboard Information

- Usage Condition Information

- Audit Logs

- Application Information

- Definition File

- Some L-Platform Management Settings

- Tenant Management and Account Management Settings

- Operational Status Server List Settings

- CMDB Agent Event Log Output Settings

- Network device configuration file

Online backup uses the PostgreSQL Point-In-Time Recovery (PITR) mechanism. There are two online backup methods, each with a different database collection range, as follows:

- Base Backup

Base backup is the backup of the entire database cluster (file group in which database data is recorded). A base backup is taken by executing the rcxmgrbackup -base command. Refer to "Base Backup" in "10.1.3 Online Backup of the Admin Server" for details.

- Differential Backup

With differential backup, the contents of updates to the database are output to multiple files in 16 MB-sized lots. These files are called Write-Ahead Logging (WAL) files.

- 75 -

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. 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.

Refer to "Differential Backup" in "10.1.3 Online Backup of the Admin Server" for details.

Restoring the Admin Server

Database restoration restores by applying to the base backup the contents of updates to the database in WAL files that have been output after the base backup was taken. The rcxmgrrestore command is used for restoration.

Refer to Section "10.1.4 Restoring the Admin Server" for details.

10.1.1 Mechanism of Backup and Restoration

This section describes the mechanism of backup and restoration, including environment requirements, points to note, and the restart position after restoration, in a system in which this product is installed.

Backup and Restoration Environment Requirements

The following conditions must be satisfied in the environments to be backed up and restored:

- The operating systems match.

Note that this does not include operating system version differences.

- The host information (host name or IP address) matches.

- The character code systems match.

- The directory services match.

- The product installation folders match.

Points to Note at Backup and Restoration

This section describes the points to note when backup and restoration is being performed.

- Administrator privileges are required in order to execute the commands.

- If, and only if, resources backed up using online backup are to be restored, execute the command that disables a service application

for which an application process no longer exists (recoverAllService command).

- Perform backup and restore operations as described below for ServerView Operations Manager, which is mandatory software. Refer

to a ServerView Operations Manager manual for details.

- Backup Operations

Perform system backup in accordance with admin server system backup operations. When a registration or update of user information has occurred, perform backup again.

- Restoration Operations a. Perform restoration of the entire admin server system. b. Use the restoration procedure described in this document to perform restoration.

- If systems backed up using offline and online backup are to be restored, perform restoration in the following order:

1. Restoration of systems backed up using offline backup

2. Restoration of systems backed up using online backup

- When moving backup resources, move the folder specified in the backup destination as well as all folders and files under that folder.

- 76 -

- 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.

- Backup to folders that include spaces.

- Restoration from the following folders cannot be performed using the restore command:

- Restoration from folders that include spaces.

- When the network device file management function is used, after offline backup is performed, save the following folders and files

under those folders. [Windows Manager]

Installation_folder

[Linux Manager] /var/opt/FJSVrcvmr/netdevice/

\SVROR\Manager\var\netdevice\

- When the network device file management function is used, before restoration of the admin server is performed, replace the folder

saved when backing up with the original folder.

Resources Managed by This Product and Timing of Update

The resource files managed by Resource Orchestrator are as shown below: When an operation described in the timing of update column has been performed, a backup should be made.

Table 10.1 Resources to be Backed Up and Timing of Update

Necessity of

Target Resources When Backup is Necessary

Stopping

Managers

Remarks

Certificates None

After password saving (after

Session encryption keys

System images and cloning images

Configuration definition information

Information related to image files

execution of the rcxlogin -save command)

After addition, deletion, and modification of Physical L-Server images

After creation, registration, modification, unregistration, and deletion of L-Servers and resources

Physical L-Server registration, deletion, movement. usage changes, power operations, conversion, and reversion

After the registration and unregistration of VM hosts

Not

Required

Not

Required

Not

Required

Not

Required

Not

Required

Backup of system images and cloning images of virtual LServers are performed as a part of virtual machine backup operations. Perform backup operations of virtual machines using the corresponding functions of VM management software.

- 77 -

Necessity of

Target Resources When Backup is Necessary

Definition files Modification of definition files No (Note)

Stopping

Managers

Remarks

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

- Tenant management and account management settings

- Operational status server list settings

- CMDB agent event log output settings

Image management information

Metering information

Home window announcement information

License agreement when users are added License agreement change Yes

Dashboard information As required Yes

Usage condition information As required Yes

Application information

Remarks) Capacity Planning data is not included in backups. Export the data to CSV or Excel files by using the Capacity Planning window as necessary.

After rcxadm imagemgr command operations

Creation, change, deletion, move, or power operation of an L-Platform or L-Server

Announcement change Yes

Application to use, modify, or cancel an L-Platform, or approval, assessment, dismissal, or cancellation of application

Change to terms of use or terms of cancellation

Not

Required

Not

Required

Because it is updated as needed, stop the Manager and take a backup as required.

Yes

Disk Space Necessary for the Backup

Disk space necessary for the backup is as follows.

Table 10.2 Resource to be Backed Up and Disk Space Necessary for the Backup

Target Resources Disk Space Necessary for the Backup

The file size of backup files varies depending on the number of resources defined in the configuration definition information.

Configuration definition information

When the number of VM guests is 1000VM, collection information temporarily becomes about 150 MB. It becomes less than 2 MB by compressing it. Please prepare the backup area referring to this size.

- 78 -

Target Resources Disk Space Necessary for the Backup

System image or cloning image

Every time, when backing up, it is necessary. Therefore, when the backup is executed three times for instance, the capacity of image save area is three times necessary. For the capacity of the image storage area, refer to "2.4.2.7 Dynamic Disk Space" in the "Design Guide VE".

Certificates Session cryptography key Definition files Image management information Home window announcement information License agreement when users are added Terms of use or terms of cancellation of L-Platform

Metering information

Dashboard information

Usage condition information

The size of the file backed up changes according to the number of files backed up.

Please prepare the backup area referring to this size to need only the area of less than 1 MB even if these 100 files are stored by 10 KB or less any file.

[Offline backup] The size increases and decreases to the file backed up in proportion

to the increase and decrease at the number of resources of metering objects and the retention period of the metering log. (*)

[Online backup] 1 KB (*) The size increases and decreases to the file backed up in proportion

to the increase and decrease of the number of L-Server templates and the number of tenants. Please prepare the backup area referring to the following formulas when there are 10 L-Server templates defined. When the number of tenants is 100, about 6.6 GB is necessary.

disk space = (67.0 + (55.5 number of * tenants)) * 1.2 (MB) 20 MB

Application information

The size increases and decreases to the file backed up according to the operating environment. Please calculate the total of the amount of disk under the control of the following directories, and prepare the backup area of the amount.

[Windows Manager]

system drive

Installation_folder

[Linux Manager]

\SWRBADB (If the directory exists)

\SWRBAM \SWOMGR

- /etc/opt/FJSVswrbam

- /var/opt/FJSVswrbam

- /var/opt/FJSVJMCMN/etc

- /var/opt/FJSVjmcal

- /var/opt/FJSVJOBSC

- /var/opt/FJSVfwseo/config/JM

- /opt/FJSVJOBSC/bin

- /etc/mjes

- 79 -

- /var/spool/mjes

* 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" is necessary for an off-line backup. It is necessary to total the "Disk space necessary for base backup" and the "Disk space necessary for difference backup" for an online backup.

In the following conditions, the amount of disk of about 12.6 GB is necessary for about 1.3 GB and online backups for an off-line backup.

Table 10.3 Condition Necessary for Backup of Metering Information

Item Estimated Value

Number of operating L-Platforms 1000

L-Server Number of resources per LPlatform

Usage status

Online backup frequency

Expansion disk 1

Software 2

Table 10.4 Formula for Metering Logs per Day

- Target capacity for metering logs

- Event Logs for an L-Platform : 2.3 KB/each time (A)

- Event Logs for other than an L-Platform : 0.6 KB/each time (B)

- Regular logs : 2.3 * number of L-Platforms (KB) (C)

- The following operations are executed every day

- Return and deployment of 10 L-Platforms

- Starting of 1,000 L-Servers when starting operations

- Stopping of 1,000 L-Servers when finishing operations

- A regular log is acquired every day

- Keep metering logs for one year

- Execute monthly base backup (every 30 days)

- Execute hourly difference backup.

- Metering logs per day

(A) * operation number for L-Platforms per day + (B) * operation number for other than L-Platforms per day + (C) * number of operating L-Platforms

= 2.3 KB * 20 + 0.6 KB * 2000 + 2.3 KB * 1000 = 3.5 MB

Table 10.5 Disk Space Necessary for Base Backup

Log of the metering each day * For one year

3.5 MB * 365 = 1.3 GB

Table 10.6 Disk Space Necessary for Difference Backup

Disk space per WAL file: 16 MB WAL file space frequency until acquiring base backup (30 days): 24 * 30 16 MB * 24 * 30 = 11.3 GB

- 80 -

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. Use the rcxmgrbackup command to specify a storage destination folder, except in the case of metering information. The folders described in the following table are automatically created in the storage destination folder in order to store the resources. When

restoration is to be performed, restoration occurs from the information in the latest folder of each folder. Therefore, even if a folder is deleted due to the disk capacity status, this will not cause a problem because the information in the latest folder will remain.

When the rcxmgrbackup command is used with the -cleanup option specified, all information older than the latest information collected by the command will be deleted.

Table 10.8 Relationship between Backup Method and Data Collected

Folder Offline Backup

CTMG_OFFyyyymmddhhmmss Yes No No

Online Backup (Base Backup)

Online Backup

(Differential Backup)

CTMG_BASEyyyymmddhhmmss No Yes No CTMGyyyymmddhhmmss No No Yes CFMGyyyymmddhhmmss Yes Yes Yes RORyyyymmddhhmmss Yes Yes Yes RBAyyyymmddhhmmss Yes No No RORSCW Yes Yes Yes

"yyyymmddhhmmss" is the date and time the command was executed.

Note

Backup files of the admin server should be stored on external storage media to prevent the backup data from being corrupted due to server failure.

Refer to "10.1.5 Online Backup Settings for Metering" for information on the storage destination for metering.

Standard at Backup and Restore Processing Time

Estimate the time necessary to perform backup and restoration of the admin server referring to the following command processing time. The command processing time differs according to the operation environment, so check the time necessary in your environment. Base

your estimates on the values you obtain from the test.

Example

- Environment

- CPU : 4CPU

- Memory Size : 16 GB

- 81 -

- 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. Therefore, to ensure that the system can restart from the status it had before backup, operate the system in accordance with whether offline backup or online backup is used for backup, and perform restoration processing in accordance with each backup type.

Figure 10.1 Schedule for Backup and Restoration of Admin Servers (Example)

The flow of the preceding diagram is as follows:

1. A problem occurs in the system (Example: Occurs at 12:35 on August 1, 2011)

2. In order to restore the system, restoration is performed on the environment backed up offline and the environment backed up online.

(Example: Restores at 14:00 on August 1, 2011) Refer to "Points to Note at Backup and Restoration" for information on the restoration order.

3. The latest differential backup files are dated (12:00 on August 1, 2011), so the restart point will be from that date and time.

10.1.2 Offline Backup of the Admin Server

Before performing backup, the systems of this product must be stopped.

1. Stop the Manager

2. Back up the Resources of this Product

3. Start the Manager

- 82 -

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>

[Linux Manager]

# /opt/FJSVrcvmr/bin/rcxmgrctl stop <RETURN>

Checking the Status of the Services of This Product

Check that the Manager and services of this product are stopped. For details on how to check, refer to "2.1 Starting and Stopping the Manager".

10.1.2.2 Back up the Resources of this Product

Back up the resources of this product. Execute the command shown below. For details on the command, refer to "6.6 rcxmgrbackup" in the "Reference Guide (Command/XML) CE".

[Windows Manager]

>Installation_folder\SVROR\Manager\bin\rcxmgrbackup -dir directory [-cleanup] <RETURN>

[Linux Manager]

# /opt/FJSVrcvmr/bin/rcxmgrbackup -dir directory [-cleanup] <RETURN>

When the network device file management function is used, save the following folders and files under those folders.

[Windows Manager]

>Installation_folder\SVROR\Manager\var\netdevice\

[Linux Manager]

# /var/opt/FJSVrcvmr/netdevice/

10.1.2.3 Starting the Manager

Execute the command shown below to start 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 start <RETURN>

[Linux Manager]

# /opt/FJSVrcvmr/bin/rcxmgrctl start <RETURN>

- 83 -

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.

[Windows Manager]

> Installation_folder\SVROR\Manager\bin\rcxadm imagemgr info > file <RETURN>

[Linux Manager]

# /opt/FJSVrcvmr/bin/rcxadm imagemgr info > file <RETURN>

Parameter

file

Specify the name of the file for output.

For details on the rcxadm imagemgr command, refer to "5.9 rcxadm imagemgr" in the "Reference Guide (Command/XML) CE".

10.1.3 Online Backup of the Admin Server

This section describes online backup of the admin server. When using online backup of the admin server, the PostgreSQL Point-In-Time Recovery (PITR) mechanism is used in the backup of the

metering database. When using PITR backup and restoration, the following two resource types are backed up and restored:

- Base Backup

The entire database cluster (file group in which database data is recorded) is backed up.

- WAL File

Write-Ahead Log (WAL) files are files in which the contents of updates to the database are recorded.

Backup of the two preceding resource types is taken when the commands for the two corresponding backup methods (base backup and differential backup) are executed.

Resources that are backed up and restored using PITR are stored in the directory that has been specified in the settings file, regardless of the storage destination specified when the command was executed. Refer to "10.1.5 Online Backup Settings for Metering" for information on how to set this.

Each of the backup methods for performing online backup of the admin server is described below.

Base Backup

Base backup is the backup of the entire database cluster (file group in which database data is recorded). Execute the command shown below. For details on the command, refer to "6.6 rcxmgrbackup" in the "Reference Guide (Command/XML) CE".

[Windows Manager]

>Installation_folder\SVROR\Manager\bin\rcxmgrbackup -dir directory -base [-cleanup] <RETURN>

[Linux Manager]

# /opt/FJSVrcvmr/bin/rcxmgrbackup -dir directory -base [-cleanup] <RETURN>

- 84 -

Note

The backup command may not end normally at times, so do not perform the following operations:

- Forced end using Ctrl+C during execution of the backup command

- Stopping the Manager during execution of the backup command

If the operations listed above have been performed, the following action will be required, depending on the status: Execute the command shown below the next time and any subsequent times the base backup does not end normally. When this command is executed, base backup will end normally. For details on the command, refer to "13.3 ctmg_resetbackuperror (Recover Base Backup Error)" in the "Reference Guide (Command/

XML) CE".

<Installation_folder>\RCXCTMG\bin\ctmg_resetbackuperror.bat

The processing result is output as standard output. The contents and meaning of the processing result are shown in the table below.

Processing Result Return Value Message

Normal end 0 Successfully reset the base-backup error. Error Other than 0 Failed to reset the base-backup error.

- If starting of the Manager fails

When operations continue after a while without the command mentioned above (ctmg_resetbackuperror) being executed, and then the Manager is stopped, subsequent starts of the Manager may fail. If this happens, an error message will be output to the database log files, as follows:

- Database Log Files

Installation_folder\RCXCTMG\Charging\log\psql-nn.log (*)

* Note: The "nn" part is a 2-digit numeral indicating the day on which the log was output.

- Error Message

Example: If the access control database failed to start

LOG: could not open file "pg_xlog/xxxxxxxx" (log file 0, segment xx): No such file or directory (*) LOG: invalid checkpoint record 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.

Installation_folder\RCXCTMG\Charging\pgsql\data\backup_label

Differential Backup

With differential backup, the contents of updates to the database are output to multiple files in 16 MB-sized lots. These files are called Write-Ahead Logging (WAL) files. 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.

- 85 -

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.

For details on the command, refer to "6.6 rcxmgrbackup" in the "Reference Guide (Command/XML) CE".

[Windows Manager]

>Installation_folder\SVROR\Manager\bin\rcxmgrbackup -dir directory [-cleanup] <RETURN>

[Linux Manager]

# /opt/FJSVrcvmr/bin/rcxmgrbackup -dir directory [-cleanup] <RETURN>

10.1.3.1 Items to be Determined Before Periodic Execution

The following items must be determined before periodic execution is implemented.

Items What to Decide

Frequency and timing of base backup

Frequency and timing of differential backup

Location of backup

Refer to "10.1.5 Online Backup Settings for Metering" for information on how to set the backup destination.

Determine the frequency of base backup. Example: 3:00 a.m. on the 1st of every month

Determine the frequency of differential backup. Example: Once per hour

Determine the location of the backup. Setting a disk other than the disk that installed the product is recommended.

In addition, sufficient capacity is required to be able to store the backup file.

10.1.3.2 Settings for Periodic Execution of Backup

The following two settings are required in order to perform periodic execution of backup:

- Settings for periodic execution of base backup

- Setting for periodic execution of WAL file save

Note

- If this procedure has been used to start batch files using the Task Scheduler, a command prompt is displayed while the batch files are

being executed. Do not close this command prompt.

- When an error occurs at periodic execution of online backup, a message with the error code 67198 will be output to the log files. If

the occurrence of errors is being monitored, use software for monitoring the log files to monitor this error message. For details on the error message, refer to "Message number 67198" in "Messages".

Settings for Periodic Execution of Base Backup

Specify settings so that a base backup is taken periodically. Use Windows Task Scheduler as a mechanism for periodically executing commands. Refer to Windows Help for information on how to set the Task Scheduler.

This section describes an example of a setup procedure for implementing a backup at 3:00 a.m. on the 1st of every month.

1. From the Windows [Start] menu, select [Administrative Tools]-[Task Scheduler] to start the Task Scheduler.

- 86 -

FUJITSU J2X1-7611-03ENZ0 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Preface

Contents

Part 1 Overview

1.1 Operation, Maintenance, and Monitoring by Infrastructure Administrators

1.2 Operation, Maintenance, and Monitoring by Tenant Administrators

1.3 Operation, Maintenance, and Monitoring by Tenant Users

Part 2 Operation

Chapter 2 Starting and Stopping Managers and Agents

2.1 Starting and Stopping the Manager

2.2 Starting and Stopping an Agent

Chapter 3 Managing User Accounts

Chapter 4 Managing Tenants

Chapter 5 Managing Templates

Chapter 6 Managing Resources and Resource Pools

6.1 Managing Resource Pools

6.2 Managing Resources

6.3 Managing L-Servers

Chapter 7 Management of L-Platform

7.1 Review for L-Platform Usage Applications

7.2 Administration of L-Platform

7.2.1 Deleting Unnecessary Data

7.2.2 Updating the Cloning Image

7.2.3 Importing to L-Platform

7.2.3.1 Network Information Settings for Converted L-Servers

7.2.3.2 Importing L-Servers

7.2.3.3 Releasing L-Servers

7.2.4 Setting OS with Deployment on RHEL-KVM

7.2.5 Startup Priority Level Settings

7.2.6 Action to Take when an Error has Occurred

7.2.7 Setting Alive Monitoring

7.2.8 Redundancy Settings

7.2.9 Automatic Server Release Settings

7.2.10 Definition VM Specific Information Definition File

7.2.11 Changing Server Specifications on a VM Host

Chapter 8 Changing Settings

8.1 Registering and Deleting Application Process Assessors

8.1.1 Registering an Application Process Assessor

8.1.2 Deleting an Application Process Assessor

8.2 Settings for Sending Email

8.3 Settings for Port Number of Admin Servers

8.4 Editing Information in the Home Window

8.5 Settings for L-Platform Management

8.5.1 Settings for Permissions to Change L-Platform Templates

8.5.2 Subnet Settings at Segment Editing

8.5.3 Settings for the Simplified Reconfiguration Function

8.5.4 Distribution Ratio Settings

8.5.5 Application Process Settings

8.5.5.1 How to Modify the Application Process Settings

8.5.5.2 How to Modify Application Process to be Used

8.5.6 Editing the Environment Setup File for the L-Platform API

8.5.7 Edit the License Agreement

8.5.8 Settings when RHEL5-Xen is used

8.5.9 Default Password Setting for Sent Emails

8.5.11 Customizing the User Rights for L-Platform Operations

8.6 Settings for Tenant Management and Account Management

8.6.1 Settings for Tenant Management and Account Management

8.6.2 Editing the User Agreement when Registering a User

8.7 Accounting Settings

8.7.1 Display Function Settings for Estimated Price

8.7.2 Currency Information Settings

8.7.3 Metering Log Settings

8.7.4 Usage Charge Calculator Settings

8.8 System Condition Server List Settings

8.9 Settings for Event Log Output for CMDB Agent

8.10 Setting for Directory Service Connection Information

Part 3 Retention

Chapter 9 Hardware Maintenance

9.1 Overview

9.2 Blade Server Maintenance

9.2.1 Maintenance LED

9.2.2 Reconfiguration of Hardware Properties

9.2.3 Replacing Servers

9.2.4 Replacing Non-Server Hardware

9.3 Maintenance for Servers Other Than Blade Servers

9.3.1 Reconfiguration of Hardware Properties

9.3.2 Replacing Servers