MasterScope Virtual DataCenter Automation v3 › en_HK › en › global › prod › masterscope › vdcaut… · MasterScope Virtual DataCenter Automation v3.0 Cluster Construction

MasterScope Virtual DataCenterAutomation v3.0

Cluster Construction GuideFor Windows/EXPRESSCLUSTER X

1st EditionJune, 2016

NEC Corporation

DisclaimerThe copyrighted information noted in this document shall belong to NEC Corporation.

Copying or revising this document, in whole or in part, is strictly prohibited without thepermission of NEC Corporation.

This document may be changed without prior notice.

NEC Corporation shall not be liable for any technical or editing errors or omissions in thisdocument.

NEC Corporation shall not be liable for the accuracy, usability, or certainty of information notedin this document.

Copyright Information• SigmaSystemCenter, MasterScope, Network Manager, NEC Storage, ESMPRO,

EXPRESSBUILDER, EXPRESSSCOPE, SIGMABLADE, UNIVERGE, andProgrammableFlow are registered trademarks of NEC Corporation.

• VMware is a trademark or registered trademark of VMware, Inc. in the United States and othercountries.

• Microsoft, Windows, Windows Server, Windows Vista, Internet Explorer, SQL Server, andHyper-V are trademarks or registered trademarks of Microsoft Corporation in the United Statesof America and other countries.

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

• Red Hat is a trademark or registered trademark of Red Hat, Inc. in the United States and othercountries.

• Intel and Itanium are trademarks or registered trademarks of Intel Corporation in the UnitedStates of America and other countries.

• Apache, Apache Tomcat, and Tomcat are trademarks or registered trademarks of ApacheSoftware Foundation.

• Oracle, Solaris, Java, and WebLogic are registered trademarks of Oracle Corporation and itssubsidiaries and affiliates in the United States of America and other countries.

• SAP is a trademark or registered trademark of SAP AG in Germany and other countries.

• Fortinet, FortiGate, and FortiGuard are registered trademarks of Fortinet, Inc. Other Fortinetproducts contained in this guide are trademarks of Fortinet, Inc.

• Thunder Series and AX Series of A10 Networks is a registered trademark of A10 Networks,Inc.

• Catalyst, IOS, Cisco IOS, Cisco, Cisco Systems, and Cisco logo are trademarks or registeredtrademarks of Cisco Systems, Inc. in the United States of America and other countries.

• F5, F5 Networks, F5 logo, and product names in the text are trademarks or registeredtrademarks of F5 Networks, Inc. in the United States of America and other countries.

Other system names, company names, and product names in this document are trademarks orregistered trademarks of their respective companies.

i

The ® and ™ marks are not included in this document.

Notes on exporting this productIf this product (including its software) is subject to regulation under the Foreign Exchange andForeign Trade Law, it will be necessary to follow the procedures required by this law when exportingthis product, such as obtaining an export license from the Japanese Government. If you requiredocuments from NEC in order to obtain an export license, please contact the dealer where youpurchased your MasterScope product, or your local NEC sales office.

ii

PrefaceTarget Readers and Objective

This document is intended for system administrators who configure the cluster system for the VirtualDataCenter Automation management server and includes details of how to configure it.

Notation Rules of This DocumentThis document describes precautions, important items, and related information as follows.

NoteIndicates precautions, warnings, and supplementary notes for the function, operation, and setting

TipIndicates the location of reference destination information

Notation rulesIn addition, the following notation rules are applied in this document.

Notation How to use Example

XXXXX Used before and after the items (text boxes,check boxes, or tabs, etc.) to be displayed inthe dialog box or used for screen names(dialog boxes, windows, and others).

Enter the machine name in theMachine name text box.All check boxSetting window

" "XXXXX

Used used before and after other manualname.

"Installation Guide"Installation Guide

[ ] in a commandline

Indicates that the specification of the valuein [ ] can be omitted.

add [/a] Gr1

Monospace font(courier new)

Indicates the outputs (messages, prompts,and others) from the command line orsystem.

Perform the following command.replace Gr1

Italicizedmonospace font(courier new)< >

Indicates the items to be replaced with avalid value and input by users.When a space is included in the value, place“ “ before and after the value.

add GroupNameInstallPath="Install Path"<Install DVD>

iii

ContentsChapter 1. Overview .................................................................................................................... 1

1.1 Target Software .....................................................................................................................2

1.2 Configuration ........................................................................................................................2

1.3 Software Configuration .........................................................................................................3

1.4 Hardware Configuration........................................................................................................31.4.1 Network Interface Card ...............................................................................................31.4.2 HBA (Host Bus Adapter) ............................................................................................41.4.3 Shared disk..................................................................................................................41.4.4 Mirror Disk .................................................................................................................4

1.5 Sample Scripts ......................................................................................................................4

Chapter 2. Preparation................................................................................................................ 52.1 Installing Windows Server ....................................................................................................6

2.2 Setting Up the Shared and Mirror Disks................................................................................6

2.3 Installing EXPRESSCLUSTER X ........................................................................................6

2.4 Installing the Required Software ...........................................................................................62.4.1 Installing SQL Server 2014 .........................................................................................6

2.5 DHCP Server Configuration..................................................................................................6

2.6 Setting Up the Windows Firewall..........................................................................................7

Chapter 3. Cluster Configuration for a Global Management Server ..................................... 83.1 [Active] Checking the SQL Server Startup Status .................................................................9

3.2 [Active] Using the Virtual DataCenter Automation Integrated Installer for Installation.......10

3.3 [Active] Setting Up the Operation Management Function Services.....................................11

3.4 [Active] Detaching the Operation Management Function Database, Moving and Attaching aDatabase File, and Re-creating Users..................................................................................113.4.1 Positioning and modifying the SQL scripts ...............................................................113.4.2 Detaching a Database File .........................................................................................123.4.3 Moving a Database File.............................................................................................123.4.4 Attaching the Database..............................................................................................133.4.5 Re-creating Database Users .......................................................................................133.4.6 Acquiring the SID and Modifying an SQL Script ......................................................133.4.7 Detaching a Database File .........................................................................................13

3.5 [Active] Changing the Procedure of Starting an SQL Server Service ..................................14

3.6 [Active] Application Server SSL Settings ...........................................................................14

3.7 [Active] Configuring the Application Server Environment..................................................14

3.8 Setting Up Monitoring ........................................................................................................14

3.9 Moving to the Standby System............................................................................................14

3.10 [Standby] Using the Virtual DataCenter Automation Integrated Installer for Installation ..14

iv

3.11 [Standby] Stopping the FW Product Services and Changing the Startup Settings ..............15

3.12 [Standby] Copying Data from the Active System..............................................................15

3.13 [Standby] Detaching and Attaching a Database, and Re-creating Users ............................163.13.1 Attaching a Databases .............................................................................................163.13.2 Re-creating Users ....................................................................................................163.13.3 Detaching a Database ..............................................................................................16

3.14 [Standby] Changing the Procedure of Starting an SQL Server Service..............................16

3.15 [Standby] Application Server SSL Settings .......................................................................17

3.16 [Standby] Configuring the Application Server Environment .............................................17

3.17 Moving to the Active System ............................................................................................17

3.18 Setting Up the Script Resources ........................................................................................17

3.19 Saving and Uploading Cluster Information .......................................................................18

3.20 Suspending the Cluster......................................................................................................18

3.21 [Active] Registering the License to the Operation Management Function .........................19

3.22 [Standby] Registering the License to the Operation Management Function.......................19

3.23 [Active] Initializing the Operation Management and Asset Management Functions..........20

3.24 Setting the Service Governor.............................................................................................20

3.25 Setting up the Property File for the Service Governor .......................................................20

3.26 Resuming the Cluster ........................................................................................................20

3.27 Rebooting the Cluster........................................................................................................21

Chapter 4. Cluster Configuration for a Management Server................................................ 224.1 [Active] Adding Upgrade and Instance to the SQL Server 2014 Product Version................24

4.1.1 Upgrading an Existing Instance .................................................................................254.1.2 Adding the New Instance ..........................................................................................25

4.2 [Active] Using the Virtual DataCenter Automation Integrated Installer for Installation.......25

4.3 [Active] Setting Up the SigmaSystemCenter Services.........................................................26

4.4 [Active] Setting Up the IIS Server Certificate .....................................................................28

4.5 [Active] Detaching the SigmaSystemCenter Database ........................................................28

4.6 [Active] Stopping a Database Instance and Changing the Startup Settings of theSigmaSystemCenter Database.............................................................................................29

4.7 [Active] Checking the SQL Server Startup..........................................................................29

4.8 [Active] Setting Up the Operation Management Function Services.....................................29

4.9 [Active] Detaching the Operation Management Function Database, Moving and Attaching aDatabase File, and Re-creating Users..................................................................................304.9.1 Positioning and Modifying the SQL Scripts ..............................................................304.9.2 Detaching a Database File .........................................................................................324.9.3 Moving a Database File.............................................................................................324.9.4 Attaching the Databases ............................................................................................324.9.5 Re-Creating Database Users ......................................................................................324.9.6 Acquiring the SID and Modifying an SQL Script ......................................................33

v

4.9.7 Detaching a Database File .........................................................................................33

4.10 [Active] Copying a SigmaSystemCenter Database File .....................................................33

4.11 Modifying an SQL Script ..................................................................................................34

4.12 [Active] Changing the Procedure of Starting an SQL Server Service ................................34

4.13 [Active] Copying a File or Folder Used by ESMPRO/ServerManager ..............................354.13.1 Copying the Work Folder ........................................................................................354.13.2 Setting Up the Access Rights ..................................................................................354.13.3 Copying the Service Folder and Editing the Configuration File...............................354.13.4 Copying the DB Folder ...........................................................................................364.13.5 Copying the Package Storage Folder .......................................................................36

4.14 [Active] Editing ESMPRO/ServerManager Configuration Files........................................36

4.15 [Active] Copying the Folder Used by DPM.......................................................................37

4.16 [Active] Copying the SystemProvisioning Local Script.....................................................37

4.17 [Active] Revising the SigmaSystemCenter Related Registry.............................................374.17.1 Revising the Registry Used by ESMPRO/ServerManager .......................................374.17.2 Revising the Registry Used by DPM .......................................................................384.17.3 Registry Used by PVM............................................................................................38

4.18 Setting Up Monitoring ......................................................................................................39

4.19 Creating NWAutomation Folder........................................................................................39

4.20 Moving to the Standby System..........................................................................................39

4.21 [Standby] Adding Upgrade and Instance to the SQL Server 2014 Product Version ...........39

4.22 [Standby] Using the Virtual DataCenter Automation Integrated Installer for Installation ..39

4.23 [Standby] Setting Up the SigmaSystemCenter Services ....................................................40

4.24 [Standby] Setting Up the IIS Server Certificate .................................................................40

4.25 [Standby] Detaching the SigmaSystemCenter Database ....................................................40

4.26 [Standby] Stopping a Database Instance and Changing the Startup Settings of theSigmaSystemCenter Database.............................................................................................40

4.27 [Standby] Stopping the FW Product Services and Changing the Start Setting ...................40

4.28 [Standby] Copying Data from the Active System..............................................................41

4.29 [Standby] Detaching and Attaching a Database, and Re-creating Users ............................414.29.1 Attaching the Database............................................................................................424.29.2 Re-Creating Users ...................................................................................................424.29.3 Detaching the Database ...........................................................................................42

4.30 [Standby] Changing the Procedure of Starting an SQL Server Service..............................42

4.31 [Standby] Editing ESMPRO/ServerManager Configuration Files .....................................42


4.33 Setting Up the Registry Synchronous Resources ...............................................................43




vi

4.37 [Active] Moving the DPM Backup Image Storage Folder / Image Storage Folder ............46

4.38 [Active] Registering the License in SigmaSystemCenter...................................................47

4.39 [Active] Registering the License in the Operation Management Function .........................47

4.40 [Standby] Registering the License in the Operation Management Function.......................47

4.41 [Active] Registering a Subsystem in SigmaSystemCenter.................................................48

4.42 [Active] Setting Up the Linkage of the Operation Management and SigmaSystemCenterFunctions ............................................................................................................................48

4.43 [Active] Initializing the Operation Management Functions ...............................................48

4.44 [Active] Setting monitoring definition of Management Server performance monitoring ...48

4.45 [Active] Linkage Settings with Global Management Server ..............................................48

4.46 [Active] Setting the Accumulation Period of Statistical Information .................................49

4.47 [Active] Changing the Environment Configuration of SystemMonitor PerformanceMonitoring..........................................................................................................................49

4.48 Perform the Cluster Resume..............................................................................................49

4.49 Reboot the Cluster.............................................................................................................49

Chapter 5. Cluster Configuration of the VM Monitoring Server ......................................... 505.1 [Active] Using the Virtual DataCenter Automation Installer for Installation .......................51

5.2 [Active] Setting Up the Services .........................................................................................52

5.3 [Active]Checking the SQL Server Startup...........................................................................53

5.4 [Active] Detaching the Database, and Moving and Attaching a Database File ....................535.4.1 Positioning and Modifying the SQL Scripts ..............................................................535.4.2 Detaching a Database File .........................................................................................545.4.3 Moving a Database File.............................................................................................545.4.4 Attaching the Database..............................................................................................545.4.5 Re-Creating Database Users ......................................................................................555.4.6 Acquiring the SID and Modifying an SQL Script ......................................................555.4.7 Detaching the Database .............................................................................................55

5.5 [Active] Changing the Procedure of Starting an SQL Server Service ..................................55


5.7 [Standby] Using the Virtual DataCenter Automation Installer for Installation .....................56

5.8 [Standby] Setting Up the Services .......................................................................................56

5.9 [Standby] Copying Data from the Active System................................................................56

5.10 [Standby] Re-Creating Database Users..............................................................................575.10.1 Attaching the Database............................................................................................575.10.2 Re-Creating Users ...................................................................................................575.10.3 Detaching the Database ...........................................................................................57

5.11 [Standby] Changing the Procedure of Starting an SQL Server Service ..............................57



vii



5.16 [Active] Registering License .............................................................................................60

5.17 [Standby] Registering License...........................................................................................60

5.18 [Active] Default Setting of the VM Monitoring Server .....................................................61

5.19 Setting the Service Governor.............................................................................................61

5.20 Resuming the Cluster Resume...........................................................................................61


Chapter 6. Cluster Configuration for an ID Management Server ........................................ 626.1 Assumption .........................................................................................................................63

6.2 [Active] Installing the MasterScope Identity Manager ........................................................646.2.1 Installation ................................................................................................................646.2.2 Changing the Service Start Setting ............................................................................646.2.3 Setting the System Environment Variable..................................................................64

6.3 [Active] Setting Up MasterScope Identity Manager ............................................................646.3.1 Changing the Database Directory and Log Directory ................................................646.3.2 Changing the Control File .........................................................................................65


6.5 [Standby] Installing MasterScope Identity Manager............................................................66

6.6 [Standby] Setting Up MasterScope Identity Manager..........................................................666.6.1 Changing the Database Directory and Log Directory ................................................666.6.2 Changing the Control File .........................................................................................66

6.7 Moving to the Active System ..............................................................................................67

6.8 Setting Up the Registry Synchronous Resources .................................................................67

6.9 Setting Up the Script Resources ..........................................................................................67

6.10 Setting Up Service Resources............................................................................................68

6.11 Setting Up the Monitor Resources.....................................................................................68



6.14 Resuming the Cluster ........................................................................................................69


6.16 Cautions ............................................................................................................................706.16.1 Actions to take when a failover occurs ....................................................................706.16.2 Stopping the EDS Protocol Server service...............................................................706.16.3 When stopping Tomcat ............................................................................................70

Chapter 7. Cluster Configuration for a Management Agent................................................. 717.1 Assumption .........................................................................................................................72

7.2 Installing the Management Agent........................................................................................72

7.3 [Active] Setting up the Data Area Folder of the Management Agent...................................72

viii


7.5 [Standby] Setting up the Data Area Folder of the Management Agent ................................73

7.6 Moving to the Active System ..............................................................................................74

7.7 [Active] Configuring Management Agent ...........................................................................74

Chapter 8. Cluster Configuration for a Database Server ...................................................... 75

Chapter 9. Upgrading the Cluster Environment .................................................................... 769.1 Upgrading the Global Management Server..........................................................................77

9.1.1 Suspending the cluster...............................................................................................779.1.2 [Active] Stopping the service ....................................................................................779.1.3 [Active] Backup of the service governor ...................................................................779.1.4 [Active] Upgrading the global management server....................................................789.1.5 [Active] Updating the database .................................................................................789.1.6 [Active] Switching back the Service Governor Setup................................................789.1.7 [Active] Changing the Procedure of Starting a service governor and stopping the

services ........................................................................................................................799.1.8 [Standby] Upgrading the global management server .................................................799.1.9 [Standby] Switching back the Service Governor Setup..............................................799.1.10 [Standby] Changing the Procedure of Starting a service governor and stopping the

services ........................................................................................................................799.1.11 Setting up the Script Resource .................................................................................799.1.12 Saving and Uploading Cluster Information .............................................................809.1.13 Setting up the Service Governor..............................................................................819.1.14 [Active] Starting the service ....................................................................................819.1.15 Resuming the cluster ...............................................................................................819.1.16 Applying the standard workflow template ...............................................................829.1.17 Editing Trace Log Settings of Resource Management Function ..............................82

9.2 Upgrading the Management Server .....................................................................................829.2.1 Suspending the cluster...............................................................................................829.2.2 [Active] Stopping the service ....................................................................................829.2.3 [Active] Upgrading the management server ..............................................................839.2.4 [Active] Updating the database .................................................................................839.2.5 [Active] Stopping the service ....................................................................................839.2.6 [Standby] Upgrading the management server ............................................................839.2.7 [Standby] Stopping the service..................................................................................849.2.8 [Active] Starting the service ......................................................................................849.2.9 Resuming the cluster .................................................................................................849.2.10 Upgrading the SigmaSystemCenter .........................................................................849.2.11 Applying the standard workflow template ...............................................................85

9.3 Upgrading the VM Monitoring Server ................................................................................859.3.1 Suspending the cluster...............................................................................................859.3.2 [Active] Stopping the service ....................................................................................859.3.3 [Active] Upgrading the VM monitoring server ..........................................................859.3.4 [Active] Updating the database .................................................................................859.3.5 [Standby] Upgrading the VM monitoring server .......................................................869.3.6 [Standby] Stopping the service..................................................................................86

ix

9.3.7 [Active] Starting the service ......................................................................................869.3.8 Resuming the cluster .................................................................................................86

9.4 Upgrading the ID Management Server ................................................................................879.4.1 [Active] Extracting the existing data .........................................................................879.4.2 Uninstalling MasterScope Identity Manager on the ID Management Server..............879.4.3 Cluster configuration for an ID management server ..................................................899.4.4 [Active] Reflecting the existing data .........................................................................89

9.5 Upgrading the Management Agent......................................................................................899.5.1 Stopping the failover group .......................................................................................899.5.2 Starting the disk resource and floating IP resource ....................................................899.5.3 [Active] Stopping the service ....................................................................................909.5.4 [Active] Upgrading the management agent ...............................................................909.5.5 [Active] Starting the service ......................................................................................909.5.6 Stopping the disk resource and floating IP resource ..................................................909.5.7 Starting the disk resource and floating IP resource ....................................................909.5.8 [Standby] Stopping the service..................................................................................909.5.9 [Standby] Upgrading the management agent .............................................................919.5.10 [Standby] Starting the service..................................................................................919.5.11 Stopping the disk resource and floating IP resource.................................................919.5.12 Starting the failover group .......................................................................................91

Chapter 10. Rolling update in the cluster environment ......................................................... 9210.1 Rolling update the Global Management Server .................................................................93

10.1.1 [Active] Updating the database ...............................................................................9310.1.2 [Active] Backup of the service governor .................................................................9310.1.3 [Standby] Upgrading the global management server ...............................................9410.1.4 [Standby] Changing the Procedure of Starting a service governor and stopping the

services ........................................................................................................................9410.1.5 [Standby] Switching back the Service Governor Setup............................................9410.1.6 Stopping the failover group .....................................................................................9410.1.7 Setting up the Script Resource.................................................................................9510.1.8 Saving and Uploading Cluster Information .............................................................9610.1.9 Starting the failover group .......................................................................................9610.1.10 Applying the standard workflow template .............................................................9710.1.11 [Active] Upgrading the global management server ................................................9710.1.12 [Active] Changing the Procedure of Starting a service governor and stopping the

services ........................................................................................................................9710.1.13 [Active] Switching back the Service Governor Setup ............................................9710.1.14 Moving to the Active System ................................................................................97

Chapter 11. Upgrading from NW Automation on the Cluster Environment....................... 9911.1 Upgrading the Global Management Server......................................................................100

11.1.1 Preparation ............................................................................................................10011.1.2 Suspending the cluster ...........................................................................................10011.1.3 [Active] Stopping the service ................................................................................10011.1.4 [Active] Upgrading the global management server ................................................100

x

11.1.5 [Active] Changing the Procedure of Starting a service governor and stopping theservices ......................................................................................................................101

11.1.6 [Standby] Upgrading the global management server..............................................10111.1.7 [Standby] Changing the Procedure of Starting a service governor and stopping the

services ......................................................................................................................10111.1.8 Setting up the Script Resource ...............................................................................10111.1.9 Saving and Uploading Cluster Information............................................................10211.1.10 [Active] Starting the service ................................................................................10311.1.11 Setting up the global management server .............................................................10311.1.12 Resuming the cluster ...........................................................................................103

11.2 Upgrading the Management Server .................................................................................10411.2.1 Preparation ............................................................................................................10411.2.2 Stopping the failover group ...................................................................................10411.2.3 Starting the disk resource and floating IP resource ................................................10411.2.4 [Active] Starting the SQL server ...........................................................................10411.2.5 [Active] Attaching the databases ...........................................................................10411.2.6 [Active] Re-creating database users .......................................................................10411.2.7 [Active] Upgrading the management server...........................................................10511.2.8 [Active] Setting up the SigmaSystemCenter ..........................................................10511.2.9 [Active] Stopping the service ................................................................................10511.2.10 [Active] Detaching the databases.........................................................................10511.2.11 [Active] Stopping the SQL server ........................................................................10511.2.12 Stopping the disk resource and floating IP resource.............................................10611.2.13 Starting the disk resource and floating IP resource ..............................................10611.2.14 [Standby] Starting the SQL server .......................................................................10611.2.15 [Standby] Attaching the databases .......................................................................10611.2.16 [Standby] Re-creating database users ..................................................................10611.2.17 [Standby] Upgrading the management server ......................................................10611.2.18 [Standby] Setting up the SigmaSystemCenter......................................................10611.2.19 [Standby] Stopping the service ............................................................................10711.2.20 [Standby] Detaching the databases ......................................................................10711.2.21 [Standby] Stopping the SQL server .....................................................................10711.2.22 Stopping the disk resource and floating IP resource.............................................10711.2.23 Starting the failover group ...................................................................................10711.2.24 Setting Up the registry synchronous resources.....................................................10811.2.25 Setting up the script resources .............................................................................10811.2.26 Saving and Uploading Cluster Information..........................................................10911.2.27 Suspending the cluster .........................................................................................10911.2.28 Registering and setting up the management server ..............................................10911.2.29 Resuming the Cluster ..........................................................................................11011.2.30 Rebooting the cluster ...........................................................................................110

11.3 Upgrading the ID Management Server ............................................................................11011.3.1 Changing the registry ............................................................................................110

Chapter 12. Changing a single configuration (non-cluster) environment to a clusterconfiguration........................................................................................................................11112.1 Applying a cluster configuration to the global management server..................................112

xi

12.1.1 Stopping the service ..............................................................................................11212.1.2 Moving the data area folder ...................................................................................11212.1.3 Create a link to the data area folder .......................................................................11212.1.4 Editing the SysMonMgr.ini ...................................................................................11212.1.5 Editing the registry ................................................................................................11312.1.6 Cluster Configuration for a Global Management Server........................................113

12.2 Applying a cluster configuration to the management server ............................................11312.2.1 Stopping the service ..............................................................................................11312.2.2 Moving the data area folder ...................................................................................11312.2.3 Create a link to the data area folder .......................................................................11412.2.4 Editing the SysMonMgr.ini ...................................................................................11412.2.5 Editing the registry ................................................................................................11412.2.6 Cluster Configuration for a Management Server ...................................................114

12.3 Applying a cluster configuration to the VM monitoring server........................................11412.3.1 Stopping the service ..............................................................................................11512.3.2 Moving the data area folder ...................................................................................11512.3.3 Create a link to the data area folder .......................................................................11512.3.4 Editing the SysMonMgr.ini ...................................................................................11512.3.5 Editing the registry ................................................................................................11512.3.6 Cluster Configuration for a VM Monitoring Server ...............................................116

Chapter 13. Notes ..................................................................................................................... 117

Appendix A. Revision History................................................................................................. 118

Appendix B. User Customizable Files and Folders............................................................... 119

xii

List of FiguresFigure 1-1 System configuration example of a shared disk type cluster......................................2Figure 1-2 System configuration example of a mirror disk type cluster ......................................3

xiii

List of TablesTable 1-1 IP address setting ......................................................................................................3Table 1-2 Floating IP address setting ........................................................................................4Table 3-1 Setting values for global management server ..........................................................10Table 4-1 Setting value of management server........................................................................25Table 5-1 Setting value of VM monitoring server ...................................................................52Table 6-1 When not replicating...............................................................................................67Table 6-2 When replicating.....................................................................................................68Table 6-4 When not replicating...............................................................................................68Table 6-5 When replicating.....................................................................................................68

xiv

Chapter 1. OverviewThis document provides example procedures for configuring clusters for a Virtual DataCenterAutomation global management server, management server, and VM Monitoring server with twonodes. In this document, the host system included in a cluster is referred to as a node.

Contents1.1 Target Software ............................................................................................................................2

1.2 Configuration ...............................................................................................................................2

1.3 Software Configuration ................................................................................................................3

1.4 Hardware Configuration...............................................................................................................3

1.5 Sample Scripts .............................................................................................................................4

Chapter 1. Overview

1

1.1 Target Software• Virtual DataCenter Automation v3.0

• EXPRESSCLUSTER X 3.3 for Windows

1.2 ConfigurationIn this document, a shared or mirror disk type failover cluster system as shown below is configured.Each of them consists of two nodes: "active" and "standby". The active system is used for usualoperation, and when it goes down, the standby system takes over (one-way standby configuration).Only one failover group is used.

The procedures in this document are described based on these configuration examples. Please replacethe IP address, drive letter, or other elements in accordance with your environment.

Figure 1-1 System configuration example of a shared disk type cluster

Chapter 1. Overview

2

Figure 1-2 System configuration example of a mirror disk type cluster

1.3 Software ConfigurationIn the configuration examples in this document, the following software is installed in each of thenodes. Each is installed onto the local disk of each node.

OS Cluster software DBMS

Windows Server 2012 R2 EXPRESSCLUSTER X 3.3 for Windows SQL Server 2014

NoteFor the Virtual DataCenter Automation operating environment, refer to Chapter 6. Operating Environments/System Requirements in the Virtual DataCenter Automation First Step Guide.

1.4 Hardware Configuration1.4.1 Network Interface Card

In the configuration examples in this document, the interconnect LAN is also used as a public LAN.A floating IP address is set for this interface.

In the configuration examples above, "192.168.0.1" is assigned to the active server, "192.168.0.2" isassigned to the standby server, and "192.168.0.11" is assigned to the floating IP address.

Also, another host name is defined for the floating IP address, and name resolution from the hostname to the floating IP address is set up. In this document, the hostname that can solve the floating IPaddress is called "Virtual hostname".

Table 1-1 IP address setting

Server IP address Host name

Active server 192.168.0.1 vdca1

Standby server 192.168.0.2 vdca2

Chapter 1. Overview

3

Table 1-2 Floating IP address setting

Server Floating IP address Virtual host name

Active server 192.168.0.11 vdca

Standby server 192.168.0.11 vdca

1.4.2 HBA (Host Bus Adapter)Logical disks are assigned to the HBAs of the active and standby systems constituting the shared disktype cluster so that the shared disk and server are connected.

1.4.3 Shared diskThis disk, which contains the data used for the Virtual DataCenter Automation management server, isused to transfer the resources to the standby system. The shared disk to be used inEXPRESSCLUSTER X is created on the storage.

1.4.4 Mirror DiskThis disk, which contains the data used for the Virtual DataCenter Automation management server, isused to transfer the resources to the standby system. The mirror disk to be used inEXPRESSCLUSTER X is created on the node of each of the active and standby systems.

1.5 Sample ScriptsThe scripts included in this document are samples. Attaching or detaching the database used inVirtual DataCenter Automation and starting or stopping the service can be controlled by registeringany of said scripts, as the script sources, in EXPRESSCLUSTER X, or by copying them to the localdisk of each of the active and standby nodes and editing them as appropriate.

The sample spricts are stored in the following directory of the installation DVD.

<Install DVD>:\script

Chapter 1. Overview

4

Chapter 2. PreparationThis chapter describes the preparations required for configuring clusters for a global managementserver, management server, and VM monitoring server. Be sure to perform these preparations.

Contents2.1 Installing Windows Server ...........................................................................................................6

2.2 Setting Up the Shared and Mirror Disks.......................................................................................6

2.3 Installing EXPRESSCLUSTER X ...............................................................................................6

2.4 Installing the Required Software ..................................................................................................6

2.5 DHCP Server Configuration.........................................................................................................6

2.6 Setting Up the Windows Firewall.................................................................................................7

Chapter 2. Preparation

5

2.1 Installing Windows ServerInstall Windows Server in the active and standby systems. For the system requirements, refer toChapter 6. Operating Environments/System Requirements in the Virtual DataCenter AutomationFirst Step Guide.

2.2 Setting Up the Shared and Mirror DisksSet up the partition and drive letter for the shared disk or mirror partition according to Setup afterHardware Configuration in the EXPRESSCLUSTER X Installation and Configuration Guide.

2.3 Installing EXPRESSCLUSTER XInstall EXPRESSCLUSTER X in the active and standby systems and initialize it according to theEXPRESSCLUSTER X Installation and Configuration Guide. Create failover group "failover", andregister only the floating IP and shared disk resources to ensure all the settings allow switchingbetween active and standby systems.

Any procedure in the next or subsequent chapter must be performed with the system switched to theactive system.

2.4 Installing the Required SoftwareInstall software according to 2.2 Software Required to be Installed in Advance in the VirtualDataCenter Automation Installation Guide.

Perform the installation for both the active and standby nodes.

2.4.1 Installing SQL Server 2014Install SQL Server 2014 Standard Edition or Enterprise Edition. Express Edition is not available in acluster environment.

Perform the installation process for both the active and standby nodes.

Install the server according to 2.2.6 Installing SQL Server in Virtual DataCenter AutomationInstallation Guide.

2.5 DHCP Server ConfigurationPrepare the DHCP server according to the 2.5.3 DHCP Server Configuration in the VirtualDataCenter Automation Installation Guide.

NoteIf the DHCP server is installed in the same machine as the Virtual DataCenter Automation managementserver, the DHCP server will offer its service by using the IP address being set in the node, whereas theVirtual DataCenter Automation management server will offer its service by using the floating IP address. Inthis case, it is necessary to set up the Virtual DataCenter Automation management and DHCP servers on theassumption that they are operating in separate machines.


6

2.6 Setting Up the Windows FirewallIf the Windows firewall is currently enabled, it is necessary to perform the exception settings that arenot set during installation.

Add it to the exception list according to 2.5.4 Setting Up the Windows Firewall and Appendix C.Network and Protocol in the Virtual DataCenter Automation Installation Guide.


7

Chapter 3. Cluster Configuration for a GlobalManagement Server

Contents3.1 [Active] Checking the SQL Server Startup Status ........................................................................9

3.2 [Active] Using the Virtual DataCenter Automation Integrated Installer for Installation..............10

3.3 [Active] Setting Up the Operation Management Function Services............................................11

3.4 [Active] Detaching the Operation Management Function Database, Moving and Attaching aDatabase File, and Re-creating Users.........................................................................................11

3.5 [Active] Changing the Procedure of Starting an SQL Server Service .........................................14

3.6 [Active] Application Server SSL Settings ..................................................................................14

3.7 [Active] Configuring the Application Server Environment.........................................................14

3.8 Setting Up Monitoring ...............................................................................................................14

3.9 Moving to the Standby System...................................................................................................14

3.10 [Standby] Using the Virtual DataCenter Automation Integrated Installer for Installation .........14

3.11 [Standby] Stopping the FW Product Services and Changing the Startup Settings .....................15

3.12 [Standby] Copying Data from the Active System.....................................................................15

3.13 [Standby] Detaching and Attaching a Database, and Re-creating Users ...................................16

3.14 [Standby] Changing the Procedure of Starting an SQL Server Service.....................................16

3.15 [Standby] Application Server SSL Settings ..............................................................................17

3.16 [Standby] Configuring the Application Server Environment ....................................................17

3.17 Moving to the Active System ...................................................................................................17

3.18 Setting Up the Script Resources ...............................................................................................17

3.19 Saving and Uploading Cluster Information ..............................................................................18

3.20 Suspending the Cluster.............................................................................................................18

3.21 [Active] Registering the License to the Operation Management Function ................................19

3.22 [Standby] Registering the License to the Operation Management Function..............................19

3.23 [Active] Initializing the Operation Management and Asset Management Functions.................20

3.24 Setting the Service Governor....................................................................................................20

3.25 Setting up the Property File for the Service Governor ..............................................................20

3.26 Resuming the Cluster ...............................................................................................................20

3.27 Rebooting the Cluster...............................................................................................................21

Chapter 3. Cluster Configuration for a Global Management Server

8

Before starting the work described in this chapter, perform the work described in "Chapter2. Preparation (page 5)".

The procedures in this chapter assume that those in the subsequent sections must be performed in theorder as described. [Active] and [Standby] represent the systems in which to perform the proceduresdescribed in this section.

All procedures in subsequent sections must be performed after the failover group created in thepreparation has been switched so that access can be obtained from the active system to the shared (ormirror) disk.

In this document, the following IP addresses, host names, and virtual host names (host name bywhich the floating IP address is resolved) are set for the respective nodes.

• Active server: 192.168.0.1, gm1

• Standby server: 192.168.0.2, gm2

• Floating IP: 192.168.0.11, gm

The S: drive is used for the shared disk of the active and standby servers.

3.1 [Active] Checking the SQL Server StartupStatus

Check that the following services are active. If they are not active, start them.

• SQL Server (FWCMDB)

• SQL Server Browser

NoteIf the SQL Server Agent (FWCMDB) is specified to start automatically, change the setting to Disabled.


9

3.2 [Active] Using the Virtual DataCenterAutomation Integrated Installer for Installation

Install the server according to the procedure in 2.3 Installing the components of Global ManagementServer in the Virtual DataCenter Automation Installation Guide.

On the integrated management server setting screen of Virtual DataCenter Automation, enter thefollowing setting values.

The configuration examples in this document use the settings shown below. The sections in bold facediffer from the configuration examples in Virtual DataCenter Automation Installation Guide.

Table 3-1 Setting values for global management server

Setting Value

Install Directory Path Default value

Self Hostname <Global management server name>*1*2

Management Server/Agent Port 12520 (default value)

Viewer Port 12521 (default value)

Change Data Directory Yes

Data Directory S:\vDCA\GM\FW

Store Initial Setting Data Yes (default value)

Application Server Type Tomcat(default value)

Application Server - HTTP Port 12080

Application Server - HTTPS Port 12443

Tomcat - Management Port 12005

Tomcat - AJP/1.3 Port 12009

Portal - SQL Server Host Name localhost(default value)

Portal - SQL Server Instance Name FWCMDB(default value)

Portal - SQL Server Port 1433(default value)

WebService Port 8081

Database - Hostname localhost(default value)

Database - Instance Name FWCMDB(default value)

Database - Database Name GM_<Global management server name>*1*2

Database - Authentication Type Windows authentication(default value)

Database - Password No(default value)

*1 For the setting values of the host names, see "Chapter 13. Notes (page 117)"*2 Specify the host name of the global management server. For a cluster configuration, specify the virtual

host name of the global management server (host name by which the floating IP address is resolved).In the configuration examples in this chapter, <global management server name> is gm.

Once installation has finished, restart the system.


10

NoteWhen restarting the system, use EXPRESSCLUSTER WebManager cluster reboot so thatEXPRESSCLUSTER X will not regard it as an abnormal end.

3.3 [Active] Setting Up the OperationManagement Function Services

Stop the following services, and change [Startup type] to [Manual].

• MasterScope UMF Operations Manager_101

• MasterScope UMF Operations Web Service__VDCGMProxy_n

Note(The "n" at the end should be 1 or a greater number. The number varies depending on the installationenvironment.)

3.4 [Active] Detaching the OperationManagement Function Database, Moving andAttaching a Database File, and Re-creating Users3.4.1 Positioning and modifying the SQL scripts

Edit the SQL scripts required for database clustering. A sample script is stored in Install DVD:\script\cluster-pro\GM . After the SQL scripts have been created, place them in the folder in thesame path on each of the local disks of the active and standby system hosts. This document providesan example where the script storage location is C:\MSSQL and the database file storage location is S:\MSSQL\Data.

Script Description

1 C:\MSSQL\DEACT.sql Used to detach a database file.

2 C:\MSSQL\ACT.sql Used to attach a database file.

3 C:\MSSQL\ACT2.sql Used to re-create a user account.

4 C:\MSSQL\SELECT.sql Used to acquire the SID of an mco database user.

5 C:\MSSQL\RECRTUSR.sql Used to re-create an mco database user.

The actual script contents are shown below. If the database storage location (S:\MSSQL and after)differs from that shown here, change the bold-face fields accordingly.

Note"@Password" is internally used by the components of Virtual DataCenter Automation. Do not change this.

DEACT.sql

ALTER DATABASE GM_<global management server name> SET OFFLINE WITH ROLLBACK IMMEDIATEEXEC sp_detach_db 'GM_<global management server name>', TRUE


11

ACT.sql

EXEC sp_attach_db 'GM_<global management server name>', @filename1 = 'S:\MSSQL\Data\GM_<global management server name>.mdf', @filename2 = 'S:\MSSQL\Data\GM_<global management server name>_log.ldf'

ACT2.sql

use GM_<global management server name>EXEC sp_change_users_login 'Auto_Fix', 'GM_<global management server name>', NULL, 'GM_<global management server name>@Password'EXEC sp_password NULL, 'GM_<global management server name>@Password', 'GM_<global management server name>'

SELECT.sql

SELECT SUSER_SID('GM_<global management server name>')

RECRTUSR.sql

ALTER DATABASE GM_<global management server name> SET OFFLINE WITH ROLLBACK IMMEDIATEEXEC sp_detach_db 'GM_<global management server name>', TRUEEXEC sp_droplogin @loginame = N'GM_<global management server name>'EXEC sp_attach_db 'GM_<global management server name>', @filename1 = 'S:\MSSQL\Data\GM_<global management server name>.mdf', @filename2 = 'S:\MSSQL\Data\GM_<global management server name>_log.LDF'CREATE LOGIN GM_<global management server name> WITH PASSWORD = 'GM_<global management server name>@Password', DEFAULT_DATABASE = GM_<global management server name>, SID = 0x????, CHECK_POLICY = OFF

The "SID = 0x????" field needs to be edited in accordance with your environment. Editing isperformed in "3.4.6 Acquiring the SID and Modifying an SQL Script (page 13)", so it is not part ofthe procedure in this section.

3.4.2 Detaching a Database FileExecute a detach process in the active system host in order to move a database file onto the shareddisk. Open the command prompt window, and execute the following commands.

> osql /E /S localhost\FWCMDB /i C:\MSSQL\DEACT.sql /o C:\MSSQL\DEACT.logAfter command execution, view C:\MSSQL\DEACT.log to confirm that no error message has beenoutput.

3.4.3 Moving a Database FileAfter the detach processing is complete, move the database file onto the shared disk.

If the instance name FWCMDB is in use, the default value of the path in which the source databasefile is stored is as follows.

C:\Program Files\Microsoft SQL\MSSQL12.FWCMDB\MSSQL\DATA


12

File name Destination

GM_<Global management servername>.mdf

S:\MSSQL\Data\GM_<Global management server name>.mdf

GM_<Global management servername>_log.ldf

S:\MSSQL\Data\GM_<Global management server name>_log.ldf

3.4.4 Attaching the DatabaseOpen the command prompt window, and execute the following commands.

> osql /E /S localhost\FWCMDB /i C:\MSSQL\ACT.sql /o C:\MSSQL\ACT.logAfter command execution, view C:\MSSQL\ACT.log to confirm that no error message has beenoutput.

3.4.5 Re-creating Database UsersOpen the command prompt window, and execute the following commands.

> osql /E /S localhost\FWCMDB /i C:\MSSQL\ACT2.sql /o C:\MSSQL\ACT2.logAfter command execution, view C:\MSSQL\ACT2.log to confirm that no error message has beenoutput.

3.4.6 Acquiring the SID and Modifying an SQL ScriptOpen the command prompt window, and execute the following commands.

> osql /U <sa_user> /P <sa_password> /S localhost\FWCMDB /i C:\MSSQL\SELECT.sql /o C:\MSSQL\SELECT.logNote

Change <sa_user> and >sa_password< in accordance with your environment.<sa_user>SQL Server administrator user name (sa)<sa_password>SQL Server administrator user name’s password

After command execution, check the contents of the output log file. This command outputs ahexadecimal number of 32 characters beginning with 0x. Apply this number to the "0x????" field inthe script file.

Log file name Destination reflected

SELECT.log S:\MSSQL\RECRTUSR.sql

3.4.7 Detaching a Database FileOpen the command prompt window, and execute the following commands.

> osql /E /S localhost\FWCMDB /i C:\MSSQL\DEACT.sql /o C:\MSSQL\DEACT.logAfter command execution, view C:\MSSQL\DEACT.log to confirm that no error message has beenoutput.


13

3.5 [Active] Changing the Procedure of Startingan SQL Server Service

Stop the following service, and set [Startup type] to [Manual].


3.6 [Active] Application Server SSL SettingsSetting SSL according to the procedure in 2.14.5 SSL Settings of Application Server in VirtualDataCenter Automation Installation Guide.

3.7 [Active] Configuring the Application ServerEnvironment


• Apache Tomcat 8.0 ServiceGovernor

3.8 Setting Up MonitoringSet up the monitoring function according to Chapter 6 Setting up MISSION CRITICALOPERATIONS and Chapter 9 Setting up Monitoring in the Virtual DataCenter AutomationConfiguration Guide. Set up this monitoring function for either the active or the standby system.

3.9 Moving to the Standby SystemIn the EXPRESSCLUSTER WebManager window, right-click the failover group and select [Move]to move to the standby system.

3.10 [Standby] Using the Virtual DataCenterAutomation Integrated Installer for Installation

Install the operation management function and service governor function in the standby system.

Perform the same procedure as for installation to the active system("3.2 [Active] Using the VirtualDataCenter Automation Integrated Installer for Installation (page 10)") , except for the followingthree steps:

• Set the [Store initial setting data] setting to [No].

• Specify the same value as the active system in "Database setting - Database name".

• After installation has finished, do not restart the system.


14

NoteBefore performing installation on the standby system host, check that you can access the shared disk fromthe standby system host. If you cannot access the shared disk from the standby system host, perform settingto allow access before installation.

3.11 [Standby] Stopping the FW Product Servicesand Changing the Startup Settings



• MasterScope UMF Operations Web Service__vDCGMProxy_n

NoteThe "n" at the end should be 1 or a greater number. The number varies depending on the installationenvironment.

Once setup has finished, restart the system.

NoteTo restart the system, use the cluster reboot function of EXPRESSCLUSTER WebManager to avoid theerror termination of the EXPRESSCLUSTER X.

NoteAfter cluster reboot, the failover group moves to the active system. Thus, restart the system, and then retrymoving to the standby system.

3.12 [Standby] Copying Data from the ActiveSystem

Copy the files from the active system host to the standby system host as follows.

Copy source (active system) Copy destination(standby system)

C:\Program Files (x86)\NEC\vDCA\GM\FW\Manager\sg\SysMonMgr.ini Same path

C:\Program Files (x86)\NEC\vDCA\GM\FW\Manager\sg\ConfigurationSettingMgr.ini

Same path

C:\Program Files (x86)\NEC\vDCA\GM\FW\Manager\sg\wfdbmgr\WFDB.ini Same path

C:\MSSQL\DEACT.sql Same path

C:\MSSQL\ACT.sql Same path

C:\MSSQL\ACT2.sql Same path

C:\MSSQL\SELECT.sql Same path

C:\MSSQL\RECRTUSR.sql Same path


15

3.13 [Standby] Detaching and Attaching aDatabase, and Re-creating Users

Perform the settings in the following sections by using the SQL script copied in "3.12 [Standby]Copying Data from the Active System (page 15)".

NoteThe <sa_user> and <sa_password> values used in this section need to be changed in accordance with yourenvironment.<sa_user>SQL Server administrator user name (sa)<sa_password>SQL Server administrator user name’s password

NoteThe result from execution of a command line in this section may show a message as listed below, but this isnot a problem.Message 15007, Level 16, Status 1, Server ServerName, Procedure sp_droplogin, Line 26'GM_<Global management server name>' is not valid login or has no authority.

3.13.1 Attaching a DatabasesExecute the following two commands to attach a database.

> osql /U <sa_user> /P <sa_password> /S localhost\FWCMDB /i C:\MSSQL\ACT.sql /o C:\MSSQL\ACT.log> osql /U <sa_user> /P <sa_password> /S localhost\FWCMDB /i C:\MSSQL\ACT2.sql /o C:\MSSQL\ACT2.log

3.13.2 Re-creating UsersExecute the following command to re-create the users.

> osql /U <sa_user> /P <sa_password> /S localhost\FWCMDB /i C:\MSSQL\RECRTUSR.sql /o C:\MSSQL\RECRTUSR.log

3.13.3 Detaching a DatabaseExecute the following command to detach the database.

> osql /U <sa_user> /P <sa_password> /S localhost\FWCMDB /i C:\MSSQL\DEACT.sql /o C:\MSSQL\DEACT.log

3.14 [Standby] Changing the Procedure ofStarting an SQL Server Service

Stop the following services, and set the [Startup type] to [Manual].



16

3.15 [Standby] Application Server SSL SettingsSetting SSL according to the procedure in "3.6 [Active] Application Server SSL Settings (page14)".

3.16 [Standby] Configuring the ApplicationServer Environment



3.17 Moving to the Active SystemIn the EXPRESSCLUSTER WebManager window, right-click the failover group and select [Move]to move to the active system.

3.18 Setting Up the Script ResourcesFrom the EXPRESSCLUSTER WebManager, add the script files included in this document to thefailover group as the script resources.

File name Description

<Install DVD>:\script\cluster-pro\GM\start.bat Service starting script

<Install DVD>:\script\cluster-pro\GM\stop.bat Service stopping script

Perform the following actions.

1. From the EXPRESSCLUSTER WebManager, change to Config Mode, click failover group,and select the [Add] in the [Edit].

2. On the displayed dialog, change [Type] to [script resurce], and select [Next].


17

3. On the displayed dialog, select the [Detail] tab, and click the [Add] button to register the script.

NoteEdit the script (*.bat) accordingly in the following cases.

• The path of the shared disk is different.• The instance name of SQL Server is different.• The number at the end of the service name of MasterScope UMF Operations Web Service is different.

3.19 Saving and Uploading Cluster InformationFrom the EXPRESSCLUSTER WebManager, save the cluster configuration information and uploadthe information files.

NoteIf the upload is skipped, the cluster will not operate normally because no configuration information isreflected to the active or standby system.

3.20 Suspending the ClusterFrom the steps to date, the cluster should be left suspended while the shared (or mirror) disk remainsinvisible.


1. From the EXPRESSCLUSTER WebManager, perform the cluster resume and cluster startactions.

2. Ensure the failover group has started with on the active system. Then, suspend the cluster.


18

3. Open the EXPRESSCLUSTER task manager, and stop monitoring all the active services.

3.21 [Active] Registering the License to theOperation Management Function

Register the code word to the operation management function according to 2.14.1 RegisteringLicense to Operation Management Function and 2.14.2 Registering CodeWord to OperationManagement Function in Virtual DataCenter Automation Installation Guide.

Install the global management server console if not installed.

3.22 [Standby] Registering the License to theOperation Management Function

Register the code word to the operation management function for the standby node. The license keyto register must be the same as that defined in "3.21 [Active] Registering the License to theOperation Management Function (page 19)".

Use the command line tool for registration. Using the following command, change the currentdirectory before starting the registration.

> cd "C:\Program Files (x86)\NEC\vDCA\GM\FW\Manager\bin"

1. Use the following command to list up the registered licenses:

> LicenseCmd.exe LIST

Acquire the application code from the license information that was output, and apply for thecode word.

2. If the license is not registered, register the license key by executing the following command. Ifthe license is already registered, this step is not necessary. Apply for the code word in 3.

> LicenseCmd.exe ADD <ProductCode_1> <LicenseKey_1>> LicenseCmd.exe ADD <ProductCode_2> <LicenseKey_2>> LicenseCmd.exe ADD <ProductCode_3> <LicenseKey_3>

Output the license list again.

3. The code word can be registered by using the following listed commands.


19

> LicenseCmd.exe REGISTER <LicenseKey_1> <Codeword_1>> LicenseCmd.exe REGISTER <LicenseKey_2> <Codeword_2>> LicenseCmd.exe REGISTER <LicenseKey_3> <Codeword_3>

NoteEnter <ProductCode_n>, <LicenseKey_n>, and <Codeword_n> according to the license information.

3.23 [Active] Initializing the OperationManagement and Asset Management Functions

Initialize the operation management and asset management functions according to 2.14.7 DefaultSettings of Asset Management Function and 2.14.8 Default Settings of Operation ManagementFunction in the Virtual DataCenter Automation Installation Guide.

3.24 Setting the Service GovernorPerform the procedure in 2.14.4 Setting up the Service Governor in Virtual DataCenter AutomationInstallation Guide.

NotePerform the procedures 1 to 5. in both manners of [Active] and [Standby].

Notecopy the following file onto manner of [Standby] when the service governor is operated in the clusterconfiguration.C:\Program Files (x86)\NEC\vDCA\GM\FW\Tomcat\vDCApiKey.jks

3.25 Setting up the Property File for the ServiceGovernor

Perform the same procedures as 2.14.6 Setting up the Property File for Service Governor in theVirtual DataCenter Automation Installation Guide.

NoteThe configuration file of the service governor and the log that is output by the service governor areseparately managed for [Active] and [Standby] when the service governor is operated in the clusterconfiguration.

3.26 Resuming the ClusterFrom EXPRESSCLUSTER WebManager, resume the cluster.


20

3.27 Rebooting the ClusterFrom EXPRESSCLUSTER WebManager, reboot the cluster.

After rebooting the cluster, move the failover group to verify that neither the active nor standbysystem causes any error.


21

Chapter 4. Cluster Configuration for aManagement Server

Contents4.1 [Active] Adding Upgrade and Instance to the SQL Server 2014 Product Version.......................24

4.2 [Active] Using the Virtual DataCenter Automation Integrated Installer for Installation..............25

4.3 [Active] Setting Up the SigmaSystemCenter Services................................................................26

4.4 [Active] Setting Up the IIS Server Certificate ............................................................................28

4.5 [Active] Detaching the SigmaSystemCenter Database ...............................................................28

4.6 [Active] Stopping a Database Instance and Changing the Startup Settings of theSigmaSystemCenter Database....................................................................................................29

4.7 [Active] Checking the SQL Server Startup.................................................................................29

4.8 [Active] Setting Up the Operation Management Function Services............................................29

4.9 [Active] Detaching the Operation Management Function Database, Moving and Attaching aDatabase File, and Re-creating Users.........................................................................................30

4.10 [Active] Copying a SigmaSystemCenter Database File ............................................................33

4.11 Modifying an SQL Script .........................................................................................................34

4.12 [Active] Changing the Procedure of Starting an SQL Server Service .......................................34

4.13 [Active] Copying a File or Folder Used by ESMPRO/ServerManager .....................................35

4.14 [Active] Editing ESMPRO/ServerManager Configuration Files...............................................36

4.15 [Active] Copying the Folder Used by DPM..............................................................................37

4.16 [Active] Copying the SystemProvisioning Local Script............................................................37

4.17 [Active] Revising the SigmaSystemCenter Related Registry....................................................37

4.18 Setting Up Monitoring .............................................................................................................39

4.19 Creating NWAutomation Folder...............................................................................................39

4.20 Moving to the Standby System.................................................................................................39

4.21 [Standby] Adding Upgrade and Instance to the SQL Server 2014 Product Version ..................39

4.22 [Standby] Using the Virtual DataCenter Automation Integrated Installer for Installation .........39

4.23 [Standby] Setting Up the SigmaSystemCenter Services ...........................................................40

4.24 [Standby] Setting Up the IIS Server Certificate ........................................................................40

4.25 [Standby] Detaching the SigmaSystemCenter Database ...........................................................40

4.26 [Standby] Stopping a Database Instance and Changing the Startup Settings of theSigmaSystemCenter Database....................................................................................................40

4.27 [Standby] Stopping the FW Product Services and Changing the Start Setting ..........................40

Chapter 4. Cluster Configuration for a Management Server

22

4.28 [Standby] Copying Data from the Active System.....................................................................41

4.29 [Standby] Detaching and Attaching a Database, and Re-creating Users ...................................41

4.30 [Standby] Changing the Procedure of Starting an SQL Server Service.....................................42

4.31 [Standby] Editing ESMPRO/ServerManager Configuration Files ............................................42


4.33 Setting Up the Registry Synchronous Resources ......................................................................43




4.37 [Active] Moving the DPM Backup Image Storage Folder / Image Storage Folder ...................46

4.38 [Active] Registering the License in SigmaSystemCenter..........................................................47

4.39 [Active] Registering the License in the Operation Management Function ................................47

4.40 [Standby] Registering the License in the Operation Management Function..............................47

4.41 [Active] Registering a Subsystem in SigmaSystemCenter........................................................48

4.42 [Active] Setting Up the Linkage of the Operation Management and SigmaSystemCenterFunctions ...................................................................................................................................48

4.43 [Active] Initializing the Operation Management Functions ......................................................48

4.44 [Active] Setting monitoring definition of Management Server performance monitoring ..........48

4.45 [Active] Linkage Settings with Global Management Server .....................................................48

4.46 [Active] Setting the Accumulation Period of Statistical Information ........................................49

4.47 [Active] Changing the Environment Configuration of SystemMonitor Performance Monitoring ....................................................................................................................................................49

4.48 Perform the Cluster Resume.....................................................................................................49

4.49 Reboot the Cluster....................................................................................................................49


23

Before starting the work described in this chapter, perform the work described in "Chapter2. Preparation (page 5)".

The procedures in this chapter assume that those in the subsequent sections must be performed in theorder as described. [Active] and [Standby] represent the systems in which to perform the proceduresdescribed in this section.

All procedures in subsequent sections must be performed after the failover group created duringpreparation has been switched so that the shared (or mirror) disk can be accessed from the activesystem.

In this document, the following IP addresses, host names, and virtual host names (host name bywhich the floating IP address is resolved) are set for the respective nodes.

• Active server: 192.168.0.201, mom1

• Standby server: 192.168.0.202, mom2

• Floating IP address: 192.168.0.211, mom

NoteConfigure the vCenter cluster environment when using VMWare on the virtual base according to theEXPRESSCLUSTER X for Windows VMWare vCenter Server Cluster System Configuration Guide.

4.1 [Active] Adding Upgrade and Instance to theSQL Server 2014 Product Version

After SigmaSystemCenter is installed, SQL Server 2014 Express is installed and used as the DBMS.Because it will be used in a cluster configuration, it needs to be upgraded to Standard Edition orEnterprise Edition. If Standard Edition or Enterprise Edition is already being used, this procedure isnot necessary. In addition, because another new SQL Server instance will be needed, install the newinstance when upgrading.


24

4.1.1 Upgrading an Existing InstanceUpgrade the database instance by the following procedure. If Standard Edition or Enterprise Editionis already being used, this procedure is not necessary.

1. Insert the media of the SQL Server product version and start the SQL Server installationcenter.

2. Select [Maintenance] from the left side menu.

3. Select [Edition Upgrade].

4. Follow the wizard to upgrade the "SSCCMDB" instance.

5. Also perform steps "3. (page 25)" and "4. (page 25)" for the "DPMDBI" instance.

4.1.2 Adding the New InstanceAdds the instance by the procedure in 2.2.6 Installing SQL Server in the Virtual DataCenterAutomation Installation Guide. This document assumes that "FWCMDB" has been specified as theinstance name like in the installation guide.

4.2 [Active] Using the Virtual DataCenterAutomation Integrated Installer for Installation

Install the server according to the procedure in 2.5 Installing the components of Management Serverin Virtual DataCenter Automation Installation Guide.

On the management server setting screen of Virtual DataCenter Automation, enter the followingsetting values.


Table 4-1 Setting value of management server

Setting Value


Self Hostname <Management server name>*1*2

VM Monitoring Server/Agent Port 12520 (default value)



Data Directory S:\vDCA\MoM\FW


GlobalManager Hostname Specify the host name of the global managementserver.*1*3

GlobalManager Port 12520 (default value)


Database - Hostname localhost (default value)

Database - Instance Name FWCMDB (default value)

Database - Database Name MoM_<Management server name>*1*2


25

Setting Value

Database - Authentication Type Windows authentication (default value)

Database - Password No (default value)

Database - Database for Network Manager External (default value)

Database - Port for Network Manager DB 12630 (default value)

ESMPRO/ServerManager - Administrator Name Determine it.

ESMPRO/ServerManager - Administrator's Password Determine it.

DeploymentManager - Management Server's IP Address Specify the management server IP address.*4

*1 For notes concerning the host names, see "Chapter 13. Notes (page 117)".*2 Specify the host name of the management server. For the cluster configuration, specify the virtual host

name of the management server (host name by which the floating IP address is resolved). Deletesymbols other than underscores (_) from the host name. In the configuration examples in this chapter,<Management server name> is mom.

*3 In the configuration examples in this document, the global management server name is gm due to thecluster configuration.

*4 Specify the IP address of the management server. For a cluster configuration, specify the floating IPaddress of the management server. In the configuration examples in this chapter, the address is192.168.0.211.


Note• When restarting the system, use EXPRESSCLUSTER WebManager cluster reboot so that

EXPRESSCLUSTER X will not regard it as an abnormal end.• When the EXPRESSCLUSTER X screen is activated, close the screen before installing the

management server.

4.3 [Active] Setting Up the SigmaSystemCenterServices


• ESMPRO/SM

- Alert Manager Socket(R) Service

- Alert Manager WMI Service

- DianaScope ModemAgent

- Dmi Event Watcher

- ESM Alert Service

- ESM Base Service

- ESM Command Service

- ESM Remote Map Service

- ESMPRO/SM Base Alert Listener

- ESMPRO/SM Base Service


26

- ESMPRO/SM Common Component

- ESMPRO/SM Event Manager

- ESMPRO/SM Web Container

NoteBecause ESMPRO/SM has dependency between services, stop the services in the following order.

Order Display name Service name

1 DianaScope ModemAgent DianaScope ModemAgent

2 ESMPRO/SM Web Container ESMWebContainer

3 ESMPRO/SM Event Manager ESMEventManager

4 ESMPRO/SM Base Alert Listener ESMBaseAlertListener

5 ESMPRO/SM Common Component ESMCommonComponent

6 Alert Manager Socket(R) Service AlertManagerSocketReceiveService

7 ESMPRO/SM Base Service ESMDSVNT

8 Dmi Event Watcher*1 DmiEventWatcher

9 ESM Alert Service ESMASVNT

10 ESM Command Service Nvcmd

11 ESM Remote Map Service Nvrmapd

12 ESM Base Service Nvbase

13 Alert Manager WMI Service AlertManagerWMIService

*1 Need not be started unless DMI alerts are received.

NoteAdd the services indicated by (*1) to "start.bat" and "stop.bat" when using these services because theyare not included in "start.bat" and "stop.bat" in the Virtual DataCenter Automation media. In this case,describe "stop.bat" in the above order. Describe "start.bat" in the reverse order of the above.

• DPM

- DeploymentManager API Service

- DeploymentManager Backup/Restore Management

- DeploymentManager Get Client Information

- DeploymentManager PXE Management

- DeploymentManager PXE Mtftp

- DeploymentManager Remote Update Service

- DeploymentManager Schedule Management

- DeploymentManager Transfer Management

• PVM

- PVMService

• Sysmon


27

- System Monitor Performance Monitoring Service

4.4 [Active] Setting Up the IIS Server CertificateTo enable the use of a WebAPI supported by the SigmaSystemCenter function, set up IIS. Issue anyserver certificate that is used in a clustered Virtual DataCenter Automation management server inadvance.

• Importing server certificate

1. Start "mmc" after specifying the file name and executing the file.

2. Click [File] - [Add/Remove Snap-in].

3. Add [Certificates] from the available snap-in items and click [OK].

4. Select [Computer account] and click [Next].

5. Select [Local Machine] and click [Finish].

6. Click [OK].

7. Click [Certificates (Local Computer)], right-click the logical store name [Person], andclick [AllTasks]-[Imoprt]. The import wizard screen for the certificate appears.

8. Click [Next].

9. Select the file name <certificate>.pfx and click [Next].

10. Enter "changeit" as the password of the secret key and perform the import according tothe wizard.

11. Click [Certificates (Local Computer)], right-click the logical store name [Trusted RootCertification Authorities], and click [AllTasks]-[Imoprt].

12. Repeat the procedures "8. (page 28)" to "10. (page 28)".

• Binding the server certificate

1. Start up [Internet Information Services (IIS) Manager].

2. Right-clicks [Default Web Site] in [Sites] and select [Edit Bindings].

3. Click [Add].

4. Configure as the following list and click [OK].

Item Value

Type https

IP address All unused IP Addresses

Port 26105

SSL certificate Preregistered certificate name

4.5 [Active] Detaching the SigmaSystemCenterDatabase

Detach the database used for the SigmaSystemCenter function.

1. Start the command prompt, and execute the following command.


28

> sqlcmd -E -S "(local)\SSCCMDB"

2. Execute the following query, and detach the PVM/SYSMON database file.

1> alter database [PVMINF] set offline with ROLLBACK IMMEDIATE2> exec sp_detach_db 'PVMINF',TRUE3> alter database [RM_PerformanceDataBase2] set offline with ROLLBACK IMMEDIATE4> exec sp_detach_db 'RM_PerformanceDataBase2',TRUE5> go

3. Start the command prompt, and execute the following command.

> sqlcmd -E -S "(local)\DPMDBI"

4. Execute the following query, and detach the DPM database file.

1> alter database [DPM] set offline with ROLLBACK IMMEDIATE2> exec sp_detach_db 'DPM',TRUE3> go

This concludes detaching the database used for the SigmaSystemCenter function.

4.6 [Active] Stopping a Database Instance andChanging the Startup Settings of theSigmaSystemCenter Database

Stop a database instance used for the SigmaSystemCenter function so that it will not startautomatically. Stop the following two services, and set [Startup type] to [Manual].

• SQL Server (DPMDBI)

• SQL Server (SSCCMDB)

4.7 [Active] Checking the SQL Server StartupCheck that the following services are active. If they are not active, start them.



4.8 [Active] Setting Up the OperationManagement Function Services

Stop the following services, and change the [Startup type] to [Manual].

• FTBase service

• NvPRO Base Manager

• NvPRO ResourceManagerAPI Service


29


• MasterScope UMF Operations Web Service__vDCMoMProxy_n


4.9 [Active] Detaching the OperationManagement Function Database, Moving andAttaching a Database File, and Re-creating Users4.9.1 Positioning and Modifying the SQL Scripts

Edit the SQL scripts required for database clustering. A sample script is stored in <Install DVD>:\script\cluster-pro\MoM. After the SQL scripts have been created, place them in the folder in thesame path on each of the local disks of the active and standby system hosts. This document providesan example where the script storage location is C:\MSSQL and the database file storage location is S:\MSSQL\Data.

Script Value

1 C:\MSSQL\DEACT.sql Used to detach an mco database file.

2 C:\MSSQL\ACT.sql Used to attach an mco database file.




6 C:\MSSQL\NVSELECT.sql Used to acquire the SID of an nvprodb database user.

7 C:\MSSQL\NVRECRTUSR.sql Used to re-create an nvprodb database user.

8 C:\MSSQL\attach_d.sql Used to attach a dpm database file.

9 C:\MSSQL\attach_p.sql Used to attach a pvm database file.

10 C:\MSSQL\detach_d.sql Used to detach a dpm database file.

11 C:\MSSQL\dettach_p.sql Used to detach a pvm database file.

The actual script contents are shown below. If the database storage location (S:\MSSQL and after)differs from that shown here, change the bold-faced fields accordingly.

Then, replace "MoM_<management server name>" with the string used to specify the database nameby using the management server setting value in "4.2 [Active] Using the Virtual DataCenterAutomation Integrated Installer for Installation (page 25)".

Note"@Password" is internally used by the components of the Virtual DataCenter Automation. Do not changethis.

• DEACT.sql

ALTER DATABASE MoM_<Management server name> SET OFFLINE WITH ROLLBACK IMMEDIATE


30

EXEC sp_detach_db 'MoM_<Management server name>', TRUE

ALTER DATABASE nvprodb SET OFFLINE WITH ROLLBACK IMMEDIATEEXEC sp_detach_db 'nvprodb', TRUE

• ACT.sql

EXEC sp_attach_db 'MoM_<Management server name>', @filename1 = 'S:\MSSQL\Data\MoM_<Management server name>.mdf', @filename2 = 'S:\MSSQL\Data\MoM_<Management server name>_log.ldf'

EXEC sp_attach_db 'nvprodb', @filename1 = 'S:\MSSQL\Data\nvprodb.mdf', @filename2 = 'S:\MSSQL\Data\nvprodb_log.ldf'

• ACT2.sql

use MoM_<Management server name>EXEC sp_change_users_login 'Auto_Fix', 'MoM_<Management server name>', NULL, 'MoM_<Management server name>@Password'EXEC sp_password NULL, 'MoM_<Management server name>@Password', 'MoM_<Management server name>'

use nvprodbEXEC sp_change_users_login 'Auto_Fix','nvprodb', NULL, 'nvprodb@Password'EXEC sp_password NULL, 'nvprodb@Password', 'nvprodb'

• SELECT.sql

SELECT SUSER_SID('MoM_<Management server name>')

• RECRTUSR.sql

ALTER DATABASE MoM_<Management server name> SET OFFLINE WITH ROLLBACK IMMEDIATEEXEC sp_detach_db 'MoM_<Management server name>', TRUEEXEC sp_droplogin @loginame = N'MoM_<Management server name>'EXEC sp_attach_db 'MoM_<Management server name>', @filename1 = 'S:\MSSQL\Data\MoM_<Management server name>.mdf', @filename2 = 'S:\MSSQL\Data\MoM_<Management server name>_log.LDF'CREATE LOGIN MoM_<Management server name> WITH PASSWORD = 'MoM_<Management server name>@Password', DEFAULT_DATABASE = MoM_<Management server name>, SID = 0x????, CHECK_POLICY = OFF

The "SID = 0x????" field needs to be edited in accordance with your environment. Editing isperformed in "4.9.6 Acquiring the SID and Modifying an SQL Script (page 33)"Script", so it isnot part of the procedure in this section.

• NVSELECT.sql

SELECT SUSER_SID('nvprodb')

• NVRECRTUSR.sql


31

ALTER DATABASE nvprodb SET OFFLINE WITH ROLLBACK IMMEDIATEEXEC sp_detach_db 'nvprodb', TRUEEXEC sp_droplogin @loginame = N'nvprodb'EXEC sp_attach_db 'nvprodb', @filename1 = 'S:\MSSQL\Data\nvprodb.mdf', @filename2 = 'S:\MSSQL\Data\nvprodb_log.LDF'CREATE LOGIN nvprodb WITH PASSWORD = 'nvprodb@Password', DEFAULT_DATABASE = nvprodb, SID = 0x????, CHECK_POLICY = OFF

The "SID = 0x????" field needs to be edited in accordance with your environment. Editing isperformed in "4.9.6 Acquiring the SID and Modifying an SQL Script (page 33)", so it is notpart of the procedure in this section.

4.9.2 Detaching a Database FileExecute detach processing in the active system host in order to move a database file onto the shareddisk. Open the command prompt window, and execute the following commands.

> osql /E /S localhost\FWCMDB /i C:\MSSQL\DEACT.sql /o C:\MSSQL\DEACT.log

After command execution, view C:\MSSQL\DEACT.log to confirm that no error message has beenoutput.

4.9.3 Moving a Database FileAfter completion of detach processing, move the database file onto the shared disk.


C:\Program Files\Microsoft SQL\MSSQL12.FWCMDB\MSSQL\DATA


MoM_<Management servername>.mdf

S:\MSSQL\Data\MoM_<Management server name>.mdf

MoM_<Management servername>_log.ldf

S:\MSSQL\Data\MoM_<Management server name>_log.ldf

nvprodb.mdf S:\MSSQL\Data\nvprodb.mdf

nvprodb_log.ldf S:\MSSQL\Data\nvprodb_log.ldf

4.9.4 Attaching the DatabasesOpen the command prompt window, and execute the following commands.

> osql /E /S localhost\FWCMDB /i C:\MSSQL\ACT.sql /o C:\MSSQL\ACT.log

After command execution, view C:\MSSQL\ACT.log to confirm that no error message has beenoutput.

4.9.5 Re-Creating Database UsersOpen the command prompt window, and execute the following commands.


32

> osql /E /S localhost\FWCMDB /i C:\MSSQL\ACT2.sql /o C:\MSSQL\ACT2.logAfter command execution, view C:\MSSQL\ACT2.log to confirm that no error message has beenoutput.

4.9.6 Acquiring the SID and Modifying an SQL ScriptOpen the command prompt window, and execute the following two commands.

> osql /U <sa_user> /P <sa_password> /S localhost\FWCMDB /i C:\MSSQL\SELECT.sql /o C:\MSSQL\SELECT.log> osql /U <sa_user> /P <sa_password> /S localhost\FWCMDB /i C:\MSSQL\NVSELECT.sql /o C:\MSSQL\NVSELECT.logNote

Change <sa_user> and <sa_password> in accordance with your environment.• <sa_user>

SQL Server administrator user name (sa)• <sa_password>

SQL Server administrator user password

After command execution, check the contents of the output log file. This command outputs ahexadecimal number of 32 characters beginning at 0x. Reflect them to the "0x????" field in the scriptfile.


SELECT.log S:\MSSQL\RECRTUSR.sql

NVSELECT.log S:\MSSQL\NVRECRTUSR.sql

4.9.7 Detaching a Database FileOpen the command prompt window, and execute the following commands.



4.10 [Active] Copying a SigmaSystemCenterDatabase File

Copy a database file onto the shared disk as follows.

Copy source Copy destination

C:\Program Files\Microsoft SQL Server\MSSQL12.SSCCMDB\MSSQL\DATA\PVMINF.mdf

S:\MSSQL\Data\PVMINF.mdf

C:\Program Files\Microsoft SQL Server\MSSQL12.SSCCMDB\MSSQL\DATA\pvminf_2.ndf

S:\MSSQL\Data\pvminf_2.ndf

C:\Program Files\Microsoft SQL Server\MSSQL12.SSCCMDB\MSSQL\DATA\PVMINF_log.ldf

S:\MSSQL\Data\PVMINF_log.ldf


33


C:\Program Files\Microsoft SQL Server\MSSQL12.SSCCMDB\MSSQL\DATA\RM_PerformanceDataBase2.mdf

S:\MSSQL\Data\RM_PerformanceDataBase2.mdf

C:\Program Files\Microsoft SQL Server\MSSQL12.SSCCMDB\MSSQL\DATA\RM_PerformanceDataBase2_log.ldf

S:\MSSQL\Data\RM_PerformanceDataBase2_log.ldf

C:\Program Files\Microsoft SQL Server\MSSQL12.DPMDBI\MSSQL\DATA\DPM_DATA.MDF

S:\MSSQL\Data\DPM_DATA.MDF

C:\Program Files\Microsoft SQL Server\MSSQL12.DPMDBI\MSSQL\DATA\DPM_LOG.LDF

S:\MSSQL\Data\DPM_LOG.LDF

Each path under "Source" above is available if the default installation has been executed. If the SQLServer version or installation folder differs from that for the default installation, check the path inaccordance with your environment.

4.11 Modifying an SQL ScriptIf the destination path of the database file differs from that assumed in this document, edit thedatabase attach scripts attach_p.sql and attach_d.sql to make them identical to that in this document(bold-faced fields below).

The script is included in the <Install DVD>\script\cluster-pro\MoM.

• attach_p.sql

create database pvminf on (filename='S:\MSSQL\Data\PVMINF.mdf'), (filename='S:\MSSQL\Data\PVMINF_log.LDF'), (filename='S:\MSSQL\Data\PVMINF_2.ndf')for attach create database RM_PerformanceDatabase2 on (filename='S:\MSSQL\Data\RM_PerformanceDataBase2.mdf'), (filename='S:\MSSQL\Data\RM_PerformanceDataBase2_log.ldf')for attach

• attach_d.sql

create database DPM on (filename='S:\MSSQL\Data\DPM_DATA.MDF'), (filename='S:\MSSQL\Data\DPM_LOG.LDF')for attach





34

4.13 [Active] Copying a File or Folder Used byESMPRO/ServerManager4.13.1 Copying the Work Folder

Copythe work folder onto the shared (or mirror) disk.

Copy Source Copy Destination

C:\Program Files (x86)\NEC\vDCA\MoM\SSC\SMM\ESMWORK S:\vDCA\MoM\SSC\SMM\NVWORK

4.13.2 Setting Up the Access RightsSet up access rights for the work folder and all its sub-folders.

1. Select S:\vDCA\MoM\SMM\NVWORK and open [Properties].

2. Select the [Security] tab and set it as follows.

Group or user name Access right

Administrators Full control

Everyone Read and execute

SYSTEM Full control

4.13.3 Copying the Service Folder and Editing theConfiguration File

Copy the service folder onto the shared (or mirror) disk.


C:\Program Files (x86)\NEC\vDCA\MoM\SSC\SMM\ESMWEB\wbserver\webapps\esmpro\WEB-INF\service

S:\vDCA\MoM\SSC\SMM\WEB-INF\service

After copying, edit S:\vDCA\MoM\SSC\SMM\WEB-INF\service\options.txt as follows.

:EU_RM_PKG_DATAPOOL_PATH=S:\vDCA\MoM\SSC\SMM\pkgpool (*1) :CLUSTER_FIP=192.168.0.211 (*2)

(*1) The update package storage folder detailed later.

(*2) Floating IP address. (Create the entry if not yet created.)

Next, edit "S:\vDCA\MoM\SSC\SMM\WEB-INF\service\esmpro\eventman\indication\subscribeSetting.properties" according to the following procedure.

Describe "indicationReceiveGlobalIp" in FIP.

The following is a configuration example when setting the FIP address to "192.168.0.211".

indicationReceiveGlobalIp=192.168.0.211


35

4.13.4 Copying the DB FolderCopy the DB folder onto the shared (or mirror) disk as follows.


C:\Program Files (x86)\NEC\SMM\ESMWEB\wbserver\webapps\esmpro\WEB-INF\db

S:\vDCA\SMM\WEB-INF\db

4.13.5 Copying the Package Storage FolderCopy the package storage folder onto the shared (or mirror) disk as follows.


C:\Program Files (x86)\NEC\vDCA\MoM\SSC\SMM\ESMWEB\pkgpool S:\vDCA\MoM\SSC\SMM\pkgpool

4.14 [Active] Editing ESMPRO/ServerManagerConfiguration Files

Edit the configuration files as follows.

1. C:\Program Files (x86)\NEC\vDCA\MoM\SSC\SMM\ESMWEB\jslalert\jsl.ini

wrkdir=S:\vDCA\MoM\SSC\SMM\WEB-INF\servicestderr=S:\vDCA\MoM\SSC\SMM\WEB-INF\service\log\jslalert\stderr.logstdout=S:\vDCA\MoM\SSC\SMM\WEB-INF\service\log\jslalert\stdout.log

2. C:\Program Files (x86)\NEC\vDCA\MoM\SSC\SMM\ESMWEB\jslcmn\jsl.ini

wrkdir=S:\vDCA\MoM\SSC\SMM\WEB-INF\servicestderr=S:\vDCA\MoM\SSC\SMM\WEB-INF\service\log\jslcmn\stderr.logstdout=S:\vDCA\MoM\SSC\SMM\WEB-INF\service\log\jslcmn\stdout.log

3. C:\Program Files (x86)\NEC\vDCA\MoM\SSC\SMM\ESMWEB\jslweb\jsl.ini

wrkdir=S:\vDCA\MoM\SSC\SMM\WEB-INF\servicestderr=S:\vDCA\MoM\SSC\SMM\WEB-INF\service\log\jslweb\stderr.logstdout=S:\vDCA\MoM\SSC\SMM\WEB-INF\service\log\jslweb\stdout.log

4. C:\Program Files (x86)\NEC\vDCA\MoM\SSC\SMM\ESMWEB\jslem\jsl.ini

wrkdir=S:\vDCA\MoM\SSC\SMM\WEB-INF\servicestderr=S:\vDCA\MoM\SSC\SMM\WEB-INF\service\log\jslem\stderr.logstdout=S:\vDCA\MoM\SSC\SMM\WEB-INF\service\log\jslem\stdout.log

5. C:\Program Files (x86)\NEC\vDCA\MoM\SSC\SMM\ESMWEB\wbserver\webapps\axis2\WEB-INF\classes\eci.service.properties

options.txt.fullpath=S:\\vDCA\\MoM\\SSC\\SMM\\WEB-INF\\service\\options.txt

NoteUse "\\" as the folder delimiter.


36

4.15 [Active] Copying the Folder Used by DPMCopy the folder onto the shared (or mirror) disk.


C:\Program Files (x86)\NEC\vDCA\MoM\SSC\DeploymentManager\Datafile

S:\vDCA\MoM\SSC\DeploymentManager\Datafile

4.16 [Active] Copying the SystemProvisioningLocal Script

Copy the folder onto the shared (or mirror) disk.


C:\Program Files (x86)\NEC\vDCA\MoM\SSC\PVM\Script S:\vDCA\MoM\SSC\PVM\Script

C:\Program Files (x86)\NEC\vDCA\MoM\SSC\PVM\conf S:\vDCA\MoM\SSC\PVM\conf

C:\Program Files (x86)\NEC\vDCA\MoM\SSC\PVM\deployfiles S:\vDCA\MoM\SSC\PVM\deployfiles

4.17 [Active] Revising the SigmaSystemCenterRelated Registry4.17.1 Revising the Registry Used by ESMPRO/ServerManager

• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\NVBASE

Name Initial data New data

CommunityName

mgr_<ComputerName> mgr_ESMPRO

WorkDir C:\Program Files (x86)\NEC\vDCA\MoM\SSC\SMM\NVWORK

S:\vDCA\MoM\SSC\SMM\NVWORK

GeneralFilter

C:\Program Files (x86)\NEC\vDCA\MoM\SSC\SMM\NVWORK\Alert\filter\genericsg

S:\vDCA\MoM\SSC\SMM\NVWORK\Alert\filter\genericsg

DiosaFilter

C:\Program Files (x86)\NEC\vDCA\MoM\SSC\SMM\NVWORK\Alert\filter\odiosasg

S:\vDCA\MoM\SSC\SMM\NVWORK\Alert\filter\odiosasg

• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\NVBASE\AlertViewer


AlertPath C:\Program Files (x86)\NEC\vDCA\MoM\SSC\SMM\NVWORK\alert

S:\vDCA\MoM\SSC\SMM\NVWORK\alert

• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\ESMSM\CurrentVersion\ODBC


37


LocalFileDirectory

C:\Program Files (x86)\NEC\vDCA\MoM\SSC\SMM\NVWORK\ESMPRO

S:\vDCA\MoM\SSC\SMM\NVWORK\ESMPRO

4.17.2 Revising the Registry Used by DPM• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\DeploymentManager


AuReportDir

C:\Program Files (x86)\NEC\vDCA\MoM\SSC\DeploymentManager\DataFile\LogFile\AuReport

S:\vDCA\MoM\SSC\DeploymentManager\DataFile\LogFile\AuReport

BmpDir C:\Program Files (x86)\NEC\vDCA\MoM\SSC\DeploymentManager\DataFile\bmp

S:\vDCA\MoM\SSC\DeploymentManager\DataFile\bmp

ClientDir C:\Program Files (x86)\NEC\vDCA\MoM\SSC\DeploymentManager\DataFile\Client

S:\vDCA\MoM\SSC\DeploymentManager\DataFile\Client

DataFileDir

C:\Program Files (x86)\NEC\vDCA\MoM\SSC\DeploymentManager\DataFile

S:\vDCA\MoM\SSC\DeploymentManager\DataFile

ScenarioDir

C:\Program Files (x86)\NEC\vDCA\MoM\SSC\DeploymentManager\DataFile\Scenario

S:\vDCA\MoM\SSC\DeploymentManager\DataFile\Scenario

SnrReportDir

C:\Program Files (x86)\NEC\vDCA\MoM\SSC\DeploymentManager\DataFile\LogFile\SnrReport

S:\vDCA\MoM\SSC\DeploymentManager\DataFile\LogFile\SnrReport

• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\DeploymentManager_DB


DBInstallDir

C:\Program Files\MicrosoftSQL Server\MSSQL12.DPMDBI\MSSQL\DATA

S:\MSSQL\Data

4.17.3 Registry Used by PVM• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\PVM\DPMProvider\Script


ScriptFolder

C:\Program Files (x86)\NEC\vDCA\MoM\SSC\PVM\Script

S:\vDCA\MoM\SSC\PVM\Script

• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\PVM


ConfPath C:\Program Files (x86)\NEC\vDCA\MoM\SSC\PVM\conf

S:\vDCA\MoM\SSC\PVM\conf

• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\PVM\DPMProvider


DeployFile

C:\Program Files (x86)\NEC\vDCA\MoM\SSC\PVM\deployfiles

S:\vDCA\MoM\SSC\PVM\deployfiles


38

4.18 Setting Up MonitoringSet up the monitoring function according to Chapter 3 Setting up Network Manager, Chapter 6Setting up MISSION CRITICAL OPERATIONS and Chapter 9 Setting up Monitoring in VirtualDataCenter Automation Configuration Guide. Set up this monitoring function for either the active orthe standby system.

4.19 Creating NWAutomation FolderCreate the NWAutomation folder on the shared disk.

The path of the created folder is as follows.

S:\vDCA\MoM\FW\Manager\sg\NWAutomation


4.21 [Standby] Adding Upgrade and Instance tothe SQL Server 2014 Product Version

Also for the standby system, upgrade the database and add the instance by the same procedure as"4.1 [Active] Adding Upgrade and Instance to the SQL Server 2014 Product Version (page 24)".

4.22 [Standby] Using the Virtual DataCenterAutomation Integrated Installer for Installation

Install the operation management function in the standby system.

Perform the same procedure as the installation into the active system ("4.2 [Active] Using theVirtual DataCenter Automation Integrated Installer for Installation (page 25)"), except the followingthree:





39

4.23 [Standby] Setting Up theSigmaSystemCenter Services

Also for the standby system, set up the SigmaSystemCenter function services by the same procedureas "4.3 [Active] Setting Up the SigmaSystemCenter Services (page 26)".

4.24 [Standby] Setting Up the IIS ServerCertificate

Also for the standby system, set up the IIS server certificate by the same procedure as "4.4 [Active]Setting Up the IIS Server Certificate (page 28)".

4.25 [Standby] Detaching theSigmaSystemCenter Database

Also for the standby system, detach the database by the same procedure as "4.5 [Active] Detachingthe SigmaSystemCenter Database (page 28)".

4.26 [Standby] Stopping a Database Instance andChanging the Startup Settings of theSigmaSystemCenter Database

Stop the following two services, and set [Startup type] to [Manual].



4.27 [Standby] Stopping the FW Product Servicesand Changing the Start Setting


• FTBase service





NoteThe "n" at the end should be 1 or a greater number. The number varies depending on the installationenvironment.)

Once setup has finished, restart the system.


40

NoteTo restart the system, use cluster reboot of EXPRESSCLUSTER WebManager. This is in order to avoid anabnormal end from the view of EXPRESSCLUSTER X.

NoteAfter rebooting the cluster, the failover group moves to the active system. Thus, restart the system, and thenretry moving to the standby system.




C:\Program Files (x86)\NEC\vDCA\MoM\FW\Manager\sg\SysMonMgr.ini Same path

C:\Program Files (x86)\NEC\vDCA\MoM\FW\Manager\sg\ConfigurationSettingMgr.ini

Same path

C:\Program Files (x86)\NEC\vDCA\MoM\FW\Manager\sg\wfdbmgr\WFDB.ini Same path

C:\Program Files (x86)\NEC\vDCA\MoM\FW\Manager\sg\NvPRO\NvPROBaseMgr.ini

Same path






C:\MSSQL\NVSELECT.sql Same path

C:\MSSQL\NVRECRTUSR.sql Same path

C:\MSSQL\attach_d.sql Same path

C:\MSSQL\attach_p.sql Same path

C:\MSSQL\detach_d.sql Same path

C:\MSSQL\detach_p.sql Same path

4.29 [Standby] Detaching and Attaching aDatabase, and Re-creating Users

Perform the settings in the following sections by using the SQL scripts copied in "4.28 [Standby]Copying Data from the Active System (page 41)".

NoteThe <sa_user> and <sa_password> values used in this section need to be changed in accordance with yourenvironment.

• <sa_user>SQL Server administrator user name (sa)


41

• <sa_password>SQL Server administrator user name’s password

NoteThe result from execution of a command line in this section may show a message as listed below, but this isnot a problem.Message 15007, Level 16, Status 1, Server ServerName, Procedure sp_droplogin, Line 26 'mco' is not avalid login or unauthorized.Message 15007, Level 16, Status 1, Server ServerName, Procedure sp_droplogin, Line 26 'nvprodb' is not avalid login or unauthorized.

4.29.1 Attaching the DatabaseExecute the following two commands to attach a database.


4.29.2 Re-Creating UsersExecute the following two commands to re-create the users.

> osql /U <sa_user> /P <sa_password> /S localhost\FWCMDB /i C:\MSSQL\RECRTUSR.sql /o C:\MSSQL\RECRTUSR.log> osql /U <sa_user> /P <sa_password> /S localhost\FWCMDB /i C:\MSSQL\NVRECRTUSR.sql /o C:\MSSQL\NVRECRTUSR.log

4.29.3 Detaching the DatabaseExecute the following command to detach the database.





4.31 [Standby] Editing ESMPRO/ServerManagerConfiguration Files

Also for the standby system, editing ESMPRO/ServerManager Configuration FIles by the sameprocedure as "4.14 [Active] Editing ESMPRO/ServerManager Configuration Files (page 36)".


42


4.33 Setting Up the Registry SynchronousResources

Register the registry synchronous resources into the failover group from EXPRESSCLUSTERWebManager. The following eight registries are the registries to register.

• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\ESMSM

• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\NVBASE

• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\ESMAlertMan\BaseSetting\Receive

• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\ESMAlertMan\Socket\Socketr

• HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Nvbase

• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\DeploymentManager

• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\DeploymentManager_DB

• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\PVM



2. On the displayed dialog, change [Type] to [registry synchronization resource], and select[Next].


43

3. On the displayed dialog, register the each registry key.

4.34 Setting Up the Script ResourcesFrom the EXPRESSCLUSTER WebManager, add the script files included in this document to thefailover group as the script resources.


<Install DVD>:\script\cluster-pro\MoM\vDCA\start.bat Service starting script

<Install DVD>:\script\cluster-pro\MoM\vDCA\stop.bat Service stopping script





44




NoteWhen being different from a default folder in an installation destination of a Management Server, pleasecorrect a installed path(2 Points) of a service script(start.bat).

rem *******************rem Set Routingrem *******************call "C:\Program Files (x86)\NEC\vDCA\MoM\FW\Manager\bin\NWAutomation\nwa_routerestore.bat"


NoteIf the upload is skipped, the cluster will not operate normally because no configuration information isapplied to the active or standby system.




2. Ensure the failover group has started with the active system. Then, select the cluster suspend.


45


4.37 [Active] Moving the DPM Backup ImageStorage Folder / Image Storage Folder

Operate the active system, and perform the actions with the cluster suspended.

1. Create the following two empty folders on the shared (or mirror) disk.

• S:\vDCA\MoM\SSC\DeploymentManager\DeployBackup

• S:\vDCA\MoM\SSC\DeploymentManager\Deploy

2. Open the DPM Web console, and log in to the system.

http://192.168.0.211/DPM

NoteThe specified IP addresses are floating IP addresses.The initial login ID and password are admin and admin.

3. Select [DPM Server] from the [Management] view.

4. Select the [Detail Setting] in the [Configuration].

5. Set the [General] sttings as follows.

Setting Value

[Server Information] - [IP Address] Specify the floating IP address.

[Image Setting] - [Forlder for BackupImage]

S:\vDCA\MoM\SSC\DeploymentManager\DeployBackup

[Image Setting] - [Folder for Image] S:\vDCA\MoM\SSC\DeploymentManager\Deploy

6. For the [DHCP Server] tab, select [DHCP Server is installed on another machine].

7. Click [OK] to save the settings. Although the error message dialog box may be displayed,close it and click [OK] again because there is no problem.

8. From the [Operations] view, select [Scenarios] - [Built-in Scenarios].

9. Edit the scenario files System_Backup and System_Restore_Unicast as follows.

Setting Value

[Back Up / Restore]- [Image File]

S:\vDCA\MoM\SSC\DeploymentManager\DeployBackup\backup.lbr

10. Click [OK] to save the settings.

11. This closes the Web console.


46

4.38 [Active] Registering the License inSigmaSystemCenter

Register the license key according to 2.15.1 Registering License to SigmaSystemCenter Function inthe Virtual DataCenter Automation Installation Guide.

4.39 [Active] Registering the License in theOperation Management Function

Register the code word in the operation management function according to 2.15.2 RegisteringLicense to Operation Management Function and 2.15.3 Registering Code Word to OperationManagement Function in the Virtual DataCenter Automation Installation Guide.

Install the global management server console if not installed.

4.40 [Standby] Registering the License in theOperation Management Function

Register the code word in the operation management function with regard to the standby node. Thelicense key to register must be the same as that defined in "4.39 [Active] Registering the License inthe Operation Management Function (page 47)".

Use the command line tool for registration on the standby node. Using the following command,change the current directory before starting the registration.

> cd "C:\Program Files (x86)\NEC\vDCA\MoM\FW\Manager\bin"





> LicenseCmd.exe ADD <ProductCode_1> <LicenseKey_1>> LicenseCmd.exe ADD <ProductCode_2> <LicenseKey_2>


3. The code word can be registered by using the following listed commands.

> LicenseCmd.exe REGISTER <ProductCode_1> <LicenseKey_1>> LicenseCmd.exe REGISTER <ProductCode_2> <LicenseKey_2>

NoteEnter <ProductCode_n>, <LicenseKey_n>, and <Codeword_n> according to the license information.


47

4.41 [Active] Registering a Subsystem inSigmaSystemCenter

Register the DPM server in the SigmaSystemCenter subsystem according to 4.1.3 Registering aVirtual DataCenter Automation Component to the SigmaSystemCenter in the Virtual DataCenterAutomation Configuration Guide. When registering it, be sure to specify the floating IP address.

4.42 [Active] Setting Up the Linkage of theOperation Management and SigmaSystemCenterFunctions

Set up the linkage of the operation management and asset management functions according to step 19or later of 2.15.4 Setting up WebAPI for SSC in Virtual DataCenter Automation Installation Guide.

For the HostName key in the [SSCAPI] section, specify the floating IP address or virtual host name(host name by which the floating IP address is resolved).

4.43 [Active] Initializing the OperationManagement Functions

Initialize the operation management and asset management functions according to 2.15.5 DefaultSettings of Operation Management Function in the Virtual DataCenter Automation InstallationGuide.

4.44 [Active] Setting monitoring definition ofManagement Server performance monitoring

Refer to 2.15.6 Setting the Monitoring Definition of Management Server Performance Monitoring inVirtual DataCenter Automation Installation Guide, then set monitoring definition for monitoringperformance of Management Server.

4.45 [Active] Linkage Settings with GlobalManagement Server

Refer to 2.15.7 Linkage setting between Global Management Server in Virtual DataCenterAutomation Installation Guide, then perform the linkage setting between Global Management Serverand Management Server. Upper-level manager name and upper-level manager host name specifyfloating IP address or virtual host name(host name that can be resolved floating IP address).


48

4.46 [Active] Setting the Accumulation Period ofStatistical Information

Refer to 2.15.8 Setting the Accumulation Period of Statistical Information in Virtual DataCenterAutomation Installation Guide, then set accumulationperiod of statistical information of managedmachine.

4.47 [Active] Changing the EnvironmentConfiguration of SystemMonitor PerformanceMonitoring

1. Execute the SystemMonitor management console.

2. In the "Environment configuration" dialog box, select the [SystemProvisioning] tab andchange [SystemProvisioning management server] to "localhost".

4.48 Perform the Cluster ResumeFrom the EXPRESSCLUSTER WebManager, resume the cluster.

4.49 Reboot the ClusterFrom the EXPRESSCLUSTER WebManager, reboot the cluster.



49

Chapter 5. Cluster Configuration of the VMMonitoring Server

Contents5.1 [Active] Using the Virtual DataCenter Automation Installer for Installation ..............................51

5.2 [Active] Setting Up the Services ................................................................................................52

5.3 [Active]Checking the SQL Server Startup..................................................................................53

5.4 [Active] Detaching the Database, and Moving and Attaching a Database File ...........................53

5.5 [Active] Changing the Procedure of Starting an SQL Server Service .........................................55


5.7 [Standby] Using the Virtual DataCenter Automation Installer for Installation ............................56

5.8 [Standby] Setting Up the Services ..............................................................................................56

5.9 [Standby] Copying Data from the Active System.......................................................................56

5.10 [Standby] Re-Creating Database Users.....................................................................................57

5.11 [Standby] Changing the Procedure of Starting an SQL Server Service .....................................57





5.16 [Active] Registering License ....................................................................................................60

5.17 [Standby] Registering License..................................................................................................60

5.18 [Active] Default Setting of the VM Monitoring Server ............................................................61

5.19 Setting the Service Governor....................................................................................................61

5.20 Resuming the Cluster Resume..................................................................................................61


Chapter 5. Cluster Configuration of the VM Monitoring Server

50

The procedures in this chapter are performed only in the case of using the cluster configuration of theVM monitoring server.

For the VM Monitoring Server, assume one-way standby configuration similar to those which aredescribed in the "1.2 Configuration (page 2)".

In this document, the following IP addresses are set for the respective nodes.

• Active server: 192.168.0.101, rm1

• Standby server: 192.168.0.102, rm2

• Floating IP: 192.168.0.111, rm

The following chapters are described and that are intended to be performed in the order listed.[Active] and [Standby] represent the systems in which to perform the procedures described in thissection.

All procedures in subsequent sections must be performed after the failover group created in thepreparation has been switched so that access can be obtained from the active system to the shared (ormirror) disk.

5.1 [Active] Using the Virtual DataCenterAutomation Installer for Installation

Installs the operation management functions in the procedure of 2.7 Installing the components of VMMonitoring Server in the Virtual DataCenter Automation Installation Guide

On the VM monitoring server setting screen of Virtual DataCenter Automation, enter the followingsetting values.



51

Table 5-1 Setting value of VM monitoring server

Setting Value


Self Hostname <VM monitoring server name>*1*2

Agent Port 12520 (default value)




Data Directory S:\vDCA\RM\FW


Management Server Hostname Specify the host name of the management server.*1*3

Management Server Port 12520 (default value)

Database - Hostname localhost (default value)

Database - Instance Name FWCMDB (default value)

Database - Database Name RM_<VM monitoring server name>*1*2

Database - Authentication Type Windows authentication (default value)

Database - Password No (default value)

*1 For notes concerning the host names, see "Chapter 13. Notes (page 117)"*2 Specify the host name of the VM monitoring server. For the cluster configuration, specify the virtual

host name of the VM monitoring server (host name by which the floating IP address is resolved). Inthe configuration examples in this chapter, <VM Monitoring server name> is rm.

*3 In the configuration examples in this document, the global management server name is mom due tothe cluster configuration.


NoteWhen restarting the system, use EXPRESSCLUSTER WebManager cluster reboot so thatEXPRESSCLUSTER X will not regard it as an abnormal end.

NoteWhen the EXPRESSCLUSTER X screen is activated, close the screen before installing the managementserver.

5.2 [Active] Setting Up the ServicesStops the following services, and then change the [StartupType] to [Manual].

• MasterScopeUMF Operations Manager_103

• MasterScopeUMF Operations Web Service__VDCRMProxy_n



52

5.3 [Active]Checking the SQL Server StartupCheck that the following services are active. Otherwise start them.



5.4 [Active] Detaching the Database, and Movingand Attaching a Database File5.4.1 Positioning and Modifying the SQL Scripts

Edit the SQL scripts required for database clustering. The sample script is stored in <Install DVD>:\script\cluster-pro\RM. After the SQL scripts have been created, place them in the folder in the samepath on each of the local disks of the active and standby system hosts. This document provides anexample where the script storage location is C:\MSSQL and the database file storage location is S:\MSSQL\Data.

Script Value

1 C:\MSSQL\DEACT.sql Used to detach a database file.

2 C:\MSSQL\ACT.sql Used to attach a database file.




The actual script contents are shown below. If the database storage location (S:\MSSQL and after)differs from that shown here, change the bold-faced fields accordingly.

Note"@Password" is internally used by the components of Virtual DataCenter Automation. Do not change it.

• DEACT.sql

ALTER DATABASE RM_<VM Monitoring server> SET OFFLINE WITH ROLLBACK IMMEDIATEEXEC sp_detach_db 'RM_<VM Monitoring server>', TRUE

• ACT.sql

EXEC sp_attach_db 'RM_<VM Monitoring server>', @filename1 = 'S:\MSSQL\Data\RM_<VM Monitoring server>.mdf', @filename2 = 'S:\MSSQL\Data\RM_<VM Monitoring server>_log.ldf'

• ACT2.sql

use RM_<VM Monitoring server>EXEC sp_change_users_login 'Auto_Fix', 'RM_<VM Monitoring server>', NULL, 'RM_<VM Monitoring server>@Password'EXEC sp_password NULL, 'RM_<VM Monitoring server>@Password', 'RM_<VM Monitoring server>'


53

• SELECT.sql

SELECT SUSER_SID('RM_<VM Monitoring server>')

• RECRTUSR.sql

ALTER DATABASE RM_<VM Monitoring server> SET OFFLINE WITH ROLLBACK IMMEDIATEEXEC sp_detach_db 'RM_<VM Monitoring server>', TRUEEXEC sp_droplogin @loginame = N'RM_<VM Monitoring server>'EXEC sp_attach_db 'RM_<VM Monitoring server>', @filename1 = 'S:\MSSQL\Data\RM_<VM Monitoring server>.mdf', @filename2 = 'S:\MSSQL\Data\RM_<VM Monitoring server>_log.LDF'CREATE LOGIN RM_<VM Monitoring server> WITH PASSWORD = 'RM_<VM Monitoring server>@Password', DEFAULT_DATABASE = RM_<VM Monitoring server>, SID = 0x????, CHECK_POLICY = OFF

The "SID = 0x????" field needs to be edited in accordance with your environment. Editing isperformed in "5.4.6 Acquiring the SID and Modifying an SQL Script (page 55)", so it is notpart of the procedure in this section.

5.4.2 Detaching a Database FileExecute a detach process in the active system host in order to move a database file onto the shareddisk. Open the command prompt window, and execute the following commands.



5.4.3 Moving a Database FileAfter completion of detach processing, move the database file onto the shared disk.


C:\Program Files\Microsoft SQL Server\MSSQL12.FWCMDB\MSSQL\DATA


RM_<VM Monitoring server>.mdf S:\MSSQL\Data\RM_<VM Monitoring server>.mdf

RM_<VM Monitoringserver>_log.ldf

S:\MSSQL\Data\RM_<VM Monitoring server>_log.LDF

5.4.4 Attaching the DatabaseOpen the command prompt window, and execute the following commands.

> osql /E /S localhost\FWCMDB /i C:\MSSQL\ACT.sql /o C:\MSSQL\ACT.log

After command execution, view C:\MSSQL\ACT.log to confirm that no error message has beenoutput.


54

5.4.5 Re-Creating Database UsersOpen the command prompt window, and execute the following commands.

> osql /E /S localhost\FWCMDB /i C:\MSSQL\ACT2.sql /o C:\MSSQL\ACT2.log

After command execution, view C:\MSSQL\ACT2.log to confirm that no error message has beenoutput.

5.4.6 Acquiring the SID and Modifying an SQL ScriptOpen the command prompt window, and execute the following commands.

> osql /U <sa_user> /P <sa_password> /S localhost\FWCMDB /i C:\MSSQL\SELECT.sql /o C:\MSSQL\SELECT.log

NoteChange <sa_user> and <sa_password> in accordance with your environment.


• <sa_password>SQL Server administrator user password

After command execution, check the contents of the output log file. This command outputs ahexadecimal number of 32 characters beginning at 0x. Reflect them to the "0x????" field in the scriptfile.


SELECT.log C:\MSSQL\RECRTUSR.sql

5.4.7 Detaching the DatabaseOpen the command prompt window, and execute the following commands.








55

5.7 [Standby] Using the Virtual DataCenterAutomation Installer for Installation

Installs the operation management function in the standby system.

Perform the same procedure as the installation into the active system ("5.1 [Active] Using theVirtual DataCenter Automation Installer for Installation (page 51)"), except the following threeitems:




5.8 [Standby] Setting Up the ServicesStops the following services, and change [Startup type] to [Manual].

• MasterScopeUMF Operations Manager_103

• MasterScopeUMF Operations Web Service__VDCRMProxy_n





C:\Program Files (x86)\NEC\vDCA\RM\FW\Manager\sg\SysMonMgr.ini Same path

C:\Program Files (x86)\NEC\vDCA\RM\FW\Manager\sg\ConfigurationSettingMgr.ini

Same path

C:\Program Files (x86)\NEC\vDCA\RM\FW\Manager\sg\wfdbmgr\WFDB.ini Same path







56

5.10 [Standby] Re-Creating Database UsersRe-create a standby system database user. Perform the settings in the following sections by using theSQL scripts copied in "5.9 [Standby] Copying Data from the Active System (page 56)".

NoteThe <sa_user> and <sa_password> values used in this section need to be changed in accordance with yourenvironment.


• <sa_password>SQL Server administrator user password

NoteThe result from execution of a command line in this section may show a message as listed below, but this isnot a problem.Message 15007, Level 16, Status 1, Server ServerName, Procedure sp_droplogin, Line 26 'mco' is not avalid login or unauthorized.

5.10.1 Attaching the DatabaseExecute the following two commands to attach the databases.


5.10.2 Re-Creating UsersExecute the following command to re-create the users.

> osql /U <sa_user> /P <sa_password> /S localhost\FWCMDB /i C:\MSSQL\RECRTUSR.sql /o C:\MSSQL\RECRTUSR.log

5.10.3 Detaching the DatabaseExecute the following command to attach the databases.






57


5.13 Setting Up the Script ResourcesChange SQL Server administrator user name and SQL Server administrator user password in thescript files start.bat and stop.bat included in this document according to the environment.

From the EXPRESSCLUSTER WebManager, add the script files to the failover group as the scriptresources.


<Install DVD>:\script\cluster-pro\RM\Start.bat Service starting script

<Install DVD>:\script\cluster-pro\RM\Stop.bat Service stopping script






58



NoteWhen being different from a default folder in an installation destination of a VM Monitoring server, pleasecorrect a installed path(2 Points) of a service script(start.bat).







2. Ensure the failover group has started with the active system. Then, select the cluster suspend.


59


5.16 [Active] Registering LicenseRegister the code word of MISSIOM CRITICAL OPERATIONS and SystemManager according to2.16.1 Registering the License to Operation Management Function and 2.16.2 Registering CodeWord to Operation Management Function in the Virtual DataCenter Automation Installation Guide.

Install the VM monitoring server console if it is not installed.

5.17 [Standby] Registering LicenseRegister the code word in the operation with regard to the standby node. The license key to registermust be the same as that defined in "5.16 [Active] Registering License (page 60)".

Use the command line tool for registration. Using the following command to change the currentdirectory before starting the registration.

> cd "C:\Program Files (x86)\NEC\vDCA\RM\FW\Manager\bin"





> LicenseCmd.exe ADD <ProductCode_1> <LicenseKey_1>


3. The code word can be registered using the following listed commands.

> LicenseCmd.exe REGISTER <LicenseKey_1> <Codeword_1>

NoteEnter <ProductCode_n>, <LicenseKey_n>, <Codeword_n> according to the license information.


60

5.18 [Active] Default Setting of the VM MonitoringServer

As a default setting of the VM monitoring server, 2.16.3 Default Settings of Operation ManagementFunction, 2.16.4 Linkage setting between Management Server and 2.16.5 Deleting scenario settingsin the Virtual DataCenter Automation Installation Guide.

5.19 Setting the Service GovernorRevise the setting according to 2.14.6. Setting up the Property File for the Service Governor in theVirtual DataCenter Automation Installation Guide.

5.20 Resuming the Cluster ResumeFrom the EXPRESSCLUSTER WebManager, resume the cluster.

5.21 Rebooting the ClusterFrom the EXPRESSCLUSTER WebManager, reboot the cluster.



61

Chapter 6. Cluster Configuration for an IDManagement Server

Contents6.1 Assumption ................................................................................................................................63

6.2 [Active] Installing the MasterScope Identity Manager ...............................................................64

6.3 [Active] Setting Up MasterScope Identity Manager ...................................................................64


6.5 [Standby] Installing MasterScope Identity Manager...................................................................66

6.6 [Standby] Setting Up MasterScope Identity Manager.................................................................66

6.7 Moving to the Active System .....................................................................................................67

6.8 Setting Up the Registry Synchronous Resources ........................................................................67

6.9 Setting Up the Script Resources .................................................................................................67

6.10 Setting Up Service Resources...................................................................................................68

6.11 Setting Up the Monitor Resources............................................................................................68



6.14 Resuming the Cluster ...............................................................................................................69


6.16 Cautions ...................................................................................................................................70

Chapter 6. Cluster Configuration for an ID Management Server

62

6.1 AssumptionThe procedures in this chapter must be performed when using the ID management server in a clusterconfiguration in Virtual DataCenter Automation.

It is also assumed that the same one-way standby configuration as the description in"1.2 Configuration (page 2)" is used for the ID management server.

Before starting the procedures in this chapter, perform the procedures in "2.1 Installing WindowsServer (page 6)", "2.2 Setting Up the Shared and Mirror Disks (page 6)", and "2.3 InstallingEXPRESSCLUSTER X (page 6)" in "Chapter 2. Preparation (page 5)".


In this document, the following IP addresses are set for the respective nodes.

• Active server: 192.168.0.51, sm1

• Standby server: 192.168.0.52, sm2

• Floating IP: 192.168.0.50, sm

The S: drive is used for the shared disk of the active and standby servers.

It is assumed that the procedures in the sections below will be performed in the order described.[Active] and [Standby] represent the systems in which to perform the procedures described in thissection.


63

6.2 [Active] Installing the MasterScope IdentityManager6.2.1 Installation

Using the Virtual DataCenter Automation Integrated Installer, install the MasterScope IdentityManager.

Hereafter, it is assumed that the installation directory of MasterScope Identity Manager is: C:\Program Files (x86)\NEC\vDCA\SM\SECUREMASTER.

6.2.2 Changing the Service Start SettingSelect [Start] - [All Programs] - [MasterScope Identity Manager] - [stopWEB_SERVER_TOMCAT].

Stop the following services.

• Apache Tomcat ForEIM

• EDS Manager

Change [Startup type] to [Manual] for the following services. If the setting is already [Manual], thereis no need to change the setting.


• EDS Protocol Server

6.2.3 Setting the System Environment VariableSelect [Start] - [Control Panel] - [System and Security] - [System] and add the following two systemenvironment variables from [Advanced system settings] window. If the shared disk is the S drive, thedirectories are as follows.

System environmentvariable name

Value

EDS_REPLICA_LAST S:\SECUREMASTER\EDS\log\.replicad.last

EDS_FOR_CLUSTER ON

6.3 [Active] Setting Up MasterScope IdentityManager

Perform the following procedures for the active system machines.

Before starting these procedures, make sure that the following services have been stopped. If theyhave not been stopped, stop them.


• EDS Manager

6.3.1 Changing the Database Directory and Log DirectoryCreate the following two directories.


64

• S:\SECUREMASTER\EDS\

• S:\SECUREMASTER\EIDM\

Move the directory from local disk to shared disk as follows.

Source (local disk) Destination (shareddisk)

C:\Program Files (x86)\NEC\vDCA\SM\SECUREMASTER\EDS\EDSDB S:\SECUREMASTER\EDS\EDSDB

C:\Program Files (x86)\NEC\vDCA\SM\SECUREMASTER\EDS\LOG S:\SECUREMASTER\EDS\LOG

C:\Program Files (x86)\NEC\vDCA\SM\SECUREMASTER\EIDM\DATA S:\SECUREMASTER\EIDM\DATA

C:\Program Files (x86)\NEC\vDCA\SM\SECUREMASTER\EIDM\LOG S:\SECUREMASTER\EIDM\LOG

Execute the following command from the command prompt and create the symbolic link.

> cd /d "C:\Program Files (x86)\NEC\vDCA\SM\SECUREMASTER\EDS"> mklink /D EDSDB S:\SECUREMASTER\EDS\EDSDB> mklink /D LOG S:\SECUREMASTER\EDS\LOG> cd /d "C:\Program Files (x86)\NEC\vDCA\SM\SECUREMASTER\EIDM"> mklink /D DATA S:\SECUREMASTER\EIDM\DATA> mklink /D LOG S:\SECUREMASTER\EIDM\LOG

6.3.2 Changing the Control FileMove the file from local disk to shared disk as follows. When the source file does not exist, there isno need to move the file.

Source (local disk) Destination (shared disk)

C:\Windows\EDS\.replicad.last S:\SECUREMASTER\EDS\log\.replicad.last

C:\Windows\EDS\.replicad.last_backup S:\SECUREMASTER\EDS\log\.replicad.last_backup

C:\Windows\EDS\.dbsaveflush.last S:\SECUREMASTER\EDS\log\.dbsaveflush.last

C:\Windows\EDS\.dbsaveflush.last_backup S:\SECUREMASTER\EDS\log\.dbsaveflush.last_backup


> cd /d C:\Windows\EDS> mklink ".replicad.last" "S:\SECUREMASTER\EDS\log\.replicad.last"> mklink ".replicad.last_backup" "S:\SECUREMASTER\EDS\log\.replicad.last_backup"> mklink ".dbsaveflush.last" "S:\SECUREMASTER\EDS\log\.dbsaveflush.last"> mklink ".dbsaveflush.last_backup" "S:\SECUREMASTER\EDS\log\.dbsaveflush.last_backup"


65


6.5 [Standby] Installing MasterScope IdentityManager

For the standby system, install MasterScope Identity Manager according to the same procedures as"6.2 [Active] Installing the MasterScope Identity Manager (page 64)".

6.6 [Standby] Setting Up MasterScope IdentityManager

Perform the following procedures for the standby system machines.

Before starting the following procedures, make sure that the following services have been stopped. Ifthey have not been stopped, stop them.


• EDS Manager

6.6.1 Changing the Database Directory and Log DirectoryDelete the following directories.

Deletion directory (local disk)

C:\Program Files (x86)\NEC\vDCA\SM\SECUREMASTER\EDS\EDSDB

C:\Program Files (x86)\NEC\vDCA\SM\SECUREMASTER\EDS\LOG

C:\Program Files (x86)\NEC\vDCA\SM\SECUREMASTER\EIDM\DATA

C:\Program Files (x86)\NEC\vDCA\SM\SECUREMASTER\EIDM\LOG


> cd /d "C:\Program Files (x86)\NEC\vDCA\SM\SECUREMASTER\EDS"> mklink /D EDSDB S:\SECUREMASTER\EDS\EDSDB> mklink /D LOG S:\SECUREMASTER\EDS\LOG> cd /d "C:\Program Files (x86)\NEC\vDCA\SM\SECUREMASTER\EIDM"> mklink /D DATA S:\SECUREMASTER\EIDM\DATA> mklink /D LOG S:\SECUREMASTER\EIDM\LOG

6.6.2 Changing the Control FileDelete the following file. If a deletion source file does not exist, there is no need to delete the file.


66

Files to Delete (Local Disk)

C:\Windows\EDS\.replicad.last

C:\Windows\EDS\.replicad.last_backup

C:\Windows\EDS\.dbsaveflush.last

C:\Windows\EDS\.dbsaveflush.last_backup


> cd /d C:\Windows\EDS> mklink ".replicad.last" "S:\SECUREMASTER\EDS\log\.replicad.last"> mklink ".replicad.last_backup" "S:\SECUREMASTER\EDS\log\.replicad.last_backup"> mklink ".dbsaveflush.last" "S:\SECUREMASTER\EDS\log\.dbsaveflush.last"> mklink ".dbsaveflush.last_backup" "S:\SECUREMASTER\EDS\log\.dbsaveflush.last_backup"


6.8 Setting Up the Registry SynchronousResources

Register the registry synchronous resources to the failover group from EXPRESSCLUSTERWebManager. The following two registries are the registries to register.

• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432node\NEC\PERCIO

• HKEY_USERS\.DEFAULT\Software\NEC\PERCIO\client

6.9 Setting Up the Script ResourcesFrom EXPRESSCLUSTER WebManager, add the script files "start.bat" and "stop.bat" included inthis document to the failover group as the script resources.

Table 6-1 When not replicating


cluster-pro\securemaster\NO_Replica\start.bat Service starting script

cluster-pro\securemaster\NO_Replica\stop.bat Service stopping script


67

Table 6-2 When replicating


cluster-pro\securemaster\Replica\start.bat Service starting script

cluster-pro\securemaster\Replica\stop.bat Service stopping script

6.10 Setting Up Service ResourcesRegister the service resources to the failover group from EXPRESSCLUSTER WebManager. Thefollowing service is registered.


6.11 Setting Up the Monitor ResourcesRegister the following monitor resources used for service monitoring from EXPRESSCLUSTERWebManager.

Property Value

Type service (service monitoring)

Monitor timing In activation

Monitored resources The service resources set in "6.10 Setting Up Service Resources (page68)".

Interval 60 seconds

Time out 60 seconds

Number of retries 1

Wait time until start of monitoring 0 second

Recovery Action Executing failover to the recovery target

Recovery Target failover group

Copy the following script file included in this document to C:\Program Files (x86)\NEC\vDCA\SM\SECUREMASTER\EDS\bin of the active system and standby system machines.

Table 6-4 When not replicating


cluster-pro\securemaster\NO_Replica\EDS_WATCH.bat Service monitoring script

Table 6-5 When replicating


cluster-pro\securemaster\Replica\EDS_WATCH.bat Service monitoring script



68





2. Ensure the failover group has started with the active system. Then, suspend the cluster.


6.14 Resuming the ClusterFrom the EXPRESSCLUSTER WebManager, resume the cluster.

6.15 Rebooting the ClusterFrom the EXPRESSCLUSTER WebManager, reboot the cluster.


69


6.16 Cautions6.16.1 Actions to take when a failover occurs

If a failover occurs due to an abnormal EDS Protocol Server service, the EDS Protocol Server serviceof the machine might not stop completely. If a failover occurs again and the cluster group is movedunder the above conditions, the incompletely stopped machine cannot start the EDS Protocol Serverservice correctly. Take the following actions for the machines when a failover occurs.

1. Eliminate the cause of the failover.

2. Restart the machine by using cluster shutdown. (The machine then enters the "restart aftershutdown" state.)

3. Select the server in the "condition of restart after shutdown" from EXPRESSCLUSTERWebManager and execute sever recovery to recover the server in the cluster.

6.16.2 Stopping the EDS Protocol Server serviceIt may be necessary to restart or stop the EDS Protocol Server to change the environmentconfiguration of the EDS Protocol Server or to initialize the database. In this case, stopEXPRESSCLUSTER monitoring once according to the following procedure, and then restart or stopthe EDS Protocol Server. For details of the ARMLOADC command, see the EXPRESSCLUSTERdocumentation.

1. Enter the following command from the command prompt window of the machine whosefailover group was activated due to stoppage of the operating monitor function

> ARMLOADC EDS_WATCH /W pause

* "EDS_WATCH" is the monitoring ID specified in the startup script.

2. Stop the EDS Manager service.

3. Change the environment configuration or initialize the database.

4. Start the EDS Protocol Server service.

5. To resume the monitoring, enter the following command from the command prompt window.

> ARMLOADC EDS_WATCH /W continue

6.16.3 When stopping TomcatIf the workflow setting is changed, it may be necessary to restart or stop Tomcat. In this case, stop themonitoring of the HTTP service according to the following procedure, and then restart or stopTomcat.

1. Stop the monitoring of the HTTP service

2. Stop the Apatch Tomcat ForEIM service.

3. Start the Apatch Tomcat ForEIM service.

4. Restart the monitoring of the HTTP service.


70

Chapter 7. Cluster Configuration for aManagement Agent

Contents7.1 Assumption ................................................................................................................................72

7.2 Installing the Management Agent...............................................................................................72

7.3 [Active] Setting up the Data Area Folder of the Management Agent..........................................72


7.5 [Standby] Setting up the Data Area Folder of the Management Agent .......................................73

7.6 Moving to the Active System .....................................................................................................74

7.7 [Active] Configuring Management Agent ..................................................................................74

Chapter 7. Cluster Configuration for a Management Agent

71

7.1 AssumptionThe procedures in this chapter must be performed when using the management agent server in acluster configuration in Virtual DataCenter Automation.

It is also assumed that the same one-way standby configuration as the description in"1.2 Configuration (page 2)" is used for the management agent.

Before starting the procedure in this chapter, perform the procedures in "2.1 Installing WindowsServer (page 6)", "2.2 Setting Up the Shared and Mirror Disks (page 6)", and "2.3 InstallingEXPRESSCLUSTER X (page 6)" in the "Chapter 2. Preparation (page 5)".


7.2 Installing the Management AgentPerform cluster configuration for the management agent for the active and standb systems accordingto 2.13 Installing the components of Management Agent in the Virtual DataCenter AutomationInstallation Guide.

The components installed are as follows.

Product name Type

MasterScope MISSION CRITICAL OPERATIONS Agent

The [Choose Components] dialog box is displayed. Select all of the above components.

Next, enter setting values for "MasterScope MISSION CRITICAL OPERATIONS" on the [ProductInstallation Settings] dialog box.

For details about the meaning of each setting item, see 2.13 Installing the components ofManagement Agent in the Virtual DataCenter Automation Installation Guide.

NoteFor notes concerning the self host name and manager host name, see "Chapter 13. Notes (page 117)".

NoteWhen restarting the system, use WebManager cluster reboot so that EXPRESSCLUSTER X will not regardit as an abnormal end.

NoteWhen the EXPRESSCLUSTER X screen is activated, close the screen before installing the managementserver.

7.3 [Active] Setting up the Data Area Folder ofthe Management Agent

Set up a data area folder as the shared disk for the active and standby servers.

In the description below, the S:drive is used for the shared disk of the active and standby servers.

1. Stop the services of the management agent.


72

Stop the service below manually.

• MasterScope UMF Operations Agent_n


2. Copy the data area folder of the management agent to the shared disk.

Open the command prompt window, and execute the following commands.

> xcopy /I "C:\Program Files (x86)\NEC\UMF\Operations\Agent\sg\iNvmCODC" "S:\vDCA\Agt\FW\Agent\sg\iNvmCODC"

3. Delete the data area folder of the management agent in the installation folder.


> rmdir /S /Q "C:\Program Files (x86)\NEC\UMF\Operations\Agent\sg\iNvmCODC"

4. Create a link to the data area folder in the shared disk.


> mklink /J "C:\Program Files (x86)\NEC\UMF\Operations\Agent\sg\iNvmCODC" "S:\vDCA\Agt\FW\Agent\sg\iNvmCODC"


7.5 [Standby] Setting up the Data Area Folder ofthe Management Agent

Set up a data area folder as the shared disk for the active and standby servers.

In the description below, the S:drive is used for the shared disk of the active and standby servers.

1. Stop the services of the management agent.

Stop the service below manually.



73


2. Delete the data area folder of the management agent in the installation folder.


> rmdir /S /Q "C:\Program Files (x86)\NEC\UMF\Operations\Agent\sg\iNvmCODC"

3. Create a link to the data area folder in the shared disk.


> mklink /J "C:\Program Files (x86)\NEC\UMF\Operations\Agent\sg\iNvmCODC" "S:\vDCA\Agt\FW\Agent\sg\iNvmCODC"


7.7 [Active] Configuring Management AgentInstall the agent according to the procedure in 2.17 Registering and Setting up the ManagementAgent in Virtual DataCenter Automation Installation Guide.

The path of the configuration file is under the "Data Directory" configured during installation.


74

Chapter 8. Cluster Configuration for a DatabaseServerThe procedures in this chapter must be performed only when using the database server in a clusterconfiguration.

Perform the installation according to the procedures for configuring a cluster for the database server.

Chapter 8. Cluster Configuration for a Database Server

75

Chapter 9. Upgrading the Cluster EnvironmentThis chapter describes the upgrade procedure in the cluster environment. In the following sections, itis assumed that the cluster is operating in the active system.

Contents9.1 Upgrading the Global Management Server.................................................................................77

9.2 Upgrading the Management Server ............................................................................................82

9.3 Upgrading the VM Monitoring Server .......................................................................................85

9.4 Upgrading the ID Management Server .......................................................................................87

9.5 Upgrading the Management Agent.............................................................................................89

Chapter 9. Upgrading the Cluster Environment

76

9.1 Upgrading the Global Management ServerAfter upgrading the global management server, make sure to upgrade the corresponding monitoringterminals. For details, refer to 4.2 Upgrading the Global Management Server Console in the VirtualDataCenter Automation Installation Guide.

Note<Install folder> is the installation destination folder of Global Management Server.The default value of the installation folder is "C:\Program Files (x86)\NEC\vDCA\GM".

9.1.1 Suspending the clusterTo stop process monitoring that is running, suspend the cluster.

1. From EXPRESSCLUSTER WebManager, perform the operation to suspend the cluster.

9.1.2 [Active] Stopping the serviceStop the following services. You can prevent the warning messages being displayed in the alert viewin EXPRESSCLUSTER WebManager by stopping the services from the EXPRESSCLUSTER taskmanager.



NoteThe "n" at the end digit should be 1 or a greater number. The number varies depending on theinstallation environment.

In a version earlier than Version 2.2, execute the following command.

> otxadmin stop-domain --force --wait_timeout 180 domain1> otxadmin stop-domain --force --wait_timeout 180 WebOTXAdmin

In Version 2.2 or later, stop the following service. You can prevent the warning messages beingdisplayed in the alert view in EXPRESSCLUSTER WebManager by stopping the services from theEXPRESSCLUSTER task manager.


9.1.3 [Active] Backup of the service governorThis step is not necessary when updating the version from Version 2.2 or later.

Back up the configuration file. Back up the following file in any location.

• For non-cluster:


77

- <Install folder>\FW\WebOTX\domains\domain1\config\vdcplugins

- <Install folder>\FW\WebOTX\domains\domain1\config\vdcapi.properties

- <Install folder>\FW\WebOTX\domains\domain1\vDCApiKey.jks

• For cluster:

- S:\vDCA\domains\domain1\config\vdcplugins

- S:\vDCA\domains\domain1\config\vdcapi.properties

- S:\vDCA\domains\domain1\vDCApiKey.jks

9.1.4 [Active] Upgrading the global management serverUpgrade the server according to the procedure in 4.1.3. Upgrading the global management server inthe Virtual DataCenter Automation Installation Guide.

9.1.5 [Active] Updating the database1. Insert the vDCA/NWA install DVD into the DVD drive.

2. Copy the database configuration script.


<Install DVD>:\fw\Windows\Tools\sql_rupdate <Install folder>\FW\Manager\sql_rupdate

3. Execute the following command to updating the database.

> cd <Install folder>\FW\Manager\sql_rupdate\sqlserver> WfdbCmdbSetup.bat <Database Name> <Server Name> <Instance Name> <Database Driver Name>

Tip• Do not insert a line feed in the command.• If a space is included in the value, enclose it in double quotation marks (").• Confirm the value of DATABASE_NAME, SERVER_NAME, SQL_INSTANCE_NAME and

DATABASE_DRIVER where the <Database Name>, <Server Name>, <Instance Name> and<Database Driver Name> was indicated on following file.<Install folder>\FW\Manager\sg\wfdbmgr\WFDB.INI

4. When the execution log is output to the execution folder after the command is executed, makesure that there is no error. (Any error indicating that the user, role, database, or schema alreadyexists is not a problem.)

9.1.6 [Active] Switching back the Service Governor SetupOverwrite the files that were backed up in any location in the procedure in "9.1.3 [Active] Backupof the service governor (page 77)".

• <Install folder>\FW\Tomcat\conf\vdcplugins

• <Install folder>\FW\Tomcat\conf\vdcapi.properties

• <Install folder>\FW\Tomcat\vDCApiKey.jks


78

9.1.7 [Active] Changing the Procedure of Starting a servicegovernor and stopping the services

Stop the following services, and change the [Startup type] to [Manual]. If registered theEXPRESSCLUSTER task manager, You can prevent the warning messages being displayed in thealert view in EXPRESSCLUSTER WebManager by stopping the services from theEXPRESSCLUSTER task manager.




9.1.8 [Standby] Upgrading the global management serverUpgrade the global management server in the standby system.

Perform the same procedure as the upgrading the active system 4.1.3. Upgrading the globalmanagement server in the Virtual DataCenter Automation Installation Guide, except as follows.

• Set the [Update the Data Directory at startup] setting to [No].

9.1.9 [Standby] Switching back the Service Governor SetupSwitching back the service governor according to the procedure in "9.1.6 [Active] Switching backthe Service Governor Setup (page 78)"

9.1.10 [Standby] Changing the Procedure of Starting a servicegovernor and stopping the services





9.1.11 Setting up the Script ResourceThis step is not necessary when updating the version from Version 2.2 or later.

1. Change into the setting mode from EXPRESSCLUSTER WebManager, click the failovergroup name, select [script] from the [Resources] tab, and then select [Property] from the [Edit]menu.


79

2. Select [start.bat] from the displayed dialog box, and then select [Edit].

call otxadmin start-domain WebOTXAdmin

Overwrite the settings described above with the settings described below:

* There are two locations that must be corrected. Overwrite them separately.

armload service_BundleAPServer /S /WAIT 180 /M /FOV "ServiceGovernor"

3. Select [stop.bat] from the displayed dialog box, and then select [Edit].

call otxadmin stop-domain --force --wait_timeout 180 domain1call otxadmin stop-domain --force --wait_timeout 180 WebOTXAdmin



armkill service_BundleAPServer

After changing the settings, click [Apply] and then click [OK].

9.1.12 Saving and Uploading Cluster InformationThis step is not necessary when updating the version from Version 2.2 or later.

From EXPRESSCLUSTER WebManager, save the cluster configuration information and upload theinformation files.


80

NoteIf the upload is skipped, no configuration information is applied to the active or standby system.

9.1.13 Setting up the Service GovernorPerform the procedure in 2.14.4 Setting up the Service Governor in Virtual DataCenter AutomationInstallation Guide

NotePerform the procedures 1 to 5. in both manners of [Active] and [Standby].

9.1.14 [Active] Starting the serviceStart the following services. Start the services by using [Start Monitoring] if you stopped them fromthe EXPRESSCLUSTER task manager.





> armload service_BundleAPServer /S /WAIT 180 /M /FOV "ServiceGovernor"

In Version 2.2 or later, start the following service. Start the services by using [Start Monitoring] ifyou stopped them from the EXPRESSCLUSTER task manager.


9.1.15 Resuming the cluster1. From EXPRESSCLUSTER WebManager, resume the cluster.

2. After starting, move the failover group to verify that neither the active nor standby systemcauses any error.


81

9.1.16 Applying the standard workflow templateWorkflow templates are not updated in overwrite installation. Import workflow templates byreferring to 4.1.8 Applying the standard workflow template in the Virtual DataCenter AutomationInstallation Guide.

9.1.17 Editing Trace Log Settings of Resource ManagementFunction

Refer to 4.1.4 Editing Trace Log Settings of Resource Management Function of Virtual DataCenterAutomation Installation Guide and edit trace log settings of resource management function.

9.2 Upgrading the Management ServerAfter upgrading the management server, make sure to upgrade the corresponding monitoringterminals. For details, refer to 4.4 Upgrading the Management Server Console in the VirtualDataCenter Automation Installation Guide.

Note<Install folder> is the installation destination folder of Management Server.The default value of the installation folder is "C:\Program Files (x86)\NEC\vDCA\MoM".




Stop the services in the following order.







82

• FTBase service

9.2.3 [Active] Upgrading the management serverUpgrade the server according to the procedure in 4.3.2. Upgrading the Management Server in theVirtual DataCenter Automation Installation Guide.











• FTBase service



9.2.6 [Standby] Upgrading the management serverUpgrade the management server in the standby system.

Perform the same procedure as the upgrading the active system 4.3.2. Upgrading the ManagementServer in the Virtual DataCenter Automation Installation Guide.


83

9.2.7 [Standby] Stopping the serviceStop the services below manually.

• FTBase service




• FTBase service







9.2.10 Upgrading the SigmaSystemCenterRefer to the following procedure manual (Japanese version only) and upgrade SigmaSystemCenter.

https://www.support.nec.co.jp/View.aspx?NoClear=on&id=3140100409

Note• Paraphrase a SigmaSystemCenter Installer in the procedure manual "<Install DVD>:\ManagerSet

up.exe" as the Installer [SigmaSystemCenter Manager] or [SigmaSystemCenter Manager (the clusterenvironment For stand by system upgrades)] which starts from a custom mode of Virtual DataCenterAutomation integration installer.

• Confirm that an installation folder of a component is the same as before the upgrade installation.


84

https://www.support.nec.co.jp/View.aspx?NoClear=on&id=3140100409


9.3 Upgrading the VM Monitoring ServerAfter upgrading the VM monitoring server, make sure to upgrade the corresponding monitoringterminals. For details, refer to 4.6 Upgrading the VM Monitoring Server Console in the VirtualDataCenter Automation Installation Guide.

Note<Install folder> is the installation destination folder of VM Monitoring Server.The default value of the installation folder is "C:\Program Files (x86)\NEC\vDCA\RM".





• MasterScope UMF Operations Web Service__vDCRMProxy_n


9.3.3 [Active] Upgrading the VM monitoring serverUpgrade the server according to the procedure in 4.5.2. Upgrading the VM Monitoring Server in theVirtual DataCenter Automation Installation Guide.




85








9.3.5 [Standby] Upgrading the VM monitoring serverUpgrade the VM monitoring server in the standby system.

Perform the same procedure as the upgrading the active system 4.5.2. Upgrading the VM MonitoringServer in the Virtual DataCenter Automation Installation Guide.

9.3.6 [Standby] Stopping the serviceStop the service below manually.


NoteThe "n" at the end digit should be 1 or a greater number. The number varies depending on the installationenvironment.







86


9.4 Upgrading the ID Management ServerThis section describes the upgrading procedure for the ID management server MasterScope IdentityManager in the cluster environment.

The procedure in this section assumes the cluster environment of the ID management server is builtaccording to the procedure in "Chapter 6. Cluster Configuration for an ID Management Server(page 62)".

Upgrading of the ID management server MasterScope Identity Manager does not support installationby overwriting. Extraction of the existing data, uninstallation of the current version ID managementserver, installation of the new version ID management server, and reflection of the existing data areperformed in this order.

9.4.1 [Active] Extracting the existing dataPerform the procedure of 4.7.1 Extracting the existing data in the Virtual DataCenter AutomationInstallation Guide in the active system.

9.4.2 Uninstalling MasterScope Identity Manager on the IDManagement Server

1. Stop the failover group in the active system.

From EXPRESSCLUSTER WebManager, perform operations to stop the failover group.

2. Deleting the Monitor Resources

From EXPRESSCLUSTER WebManager, delete the script resources registered in"6.11 Setting Up the Monitor Resources (page 68)".

3. Deleting the Service Resources

From EXPRESSCLUSTER WebManager, delete the script resources registered in"6.10 Setting Up Service Resources (page 68)".

4. Deleting the Script Resources


87

From EXPRESSCLUSTER WebManager, delete the script resources registered in"6.9 Setting Up the Script Resources (page 67)".

5. Deleting the Registry Synchronous Resources

From EXPRESSCLUSTER WebManager, delete the script resources registered in"6.8 Setting Up the Registry Synchronous Resources (page 67)".

6. Saving and Uploading Cluster Information

From EXPRESSCLUSTER WebManager, save the cluster configuration information andupload the information files.


7. [Standby] Starting the disk resource and floating IP resource

Start the disk resource and floating IP resource in the standby system.

a. From EXPRESSCLUSTER WebManager, start the disk resource. Select the standbysystem on the "Select Server" dialog.

b. From EXPRESSCLUSTER WebManager, start the floating IP resource. Select thestandby system on the "Select Server" dialog.

8. [Standby] Uninstalling MasterScope Identity Manager on the ID Management Server

Perform the procedure in 6.2.7 Uninstalling the components of ID Management Server in theVirtual DataCenter Automation Installation Guide in the standby system.

9. [Standby] Stopping the disk resource and floating IP resource

Stop the disk resource and floating IP resource in the standby system.

a. From EXPRESSCLUSTER WebManager, stop the disk resource. Select the standbysystem on the "Select Server" dialog.

b. From EXPRESSCLUSTER WebManager, stop the floating IP resource. Select thestandby system on the "Select Server" dialog.

10. [Active] Starting the disk resource and floating IP resource

Start the disk resource and floating IP resource in the active system.

a. From EXPRESSCLUSTER WebManager, start the disk resource. Select the activesystem on the "Select Server" dialog.

b. From EXPRESSCLUSTER WebManager, start the floating IP resource. Select theactive system on the "Select Server" dialog.

11. [Active] Uninstalling MasterScope Identity Manager on the ID Management Server

Perform the procedure in 6.2.7 Uninstalling ID Management Server in the Virtual DataCenterAutomation Installation Guide in the active system.

12. Deleting the Shared Disk Data


88

Delete the shared disk directories created in "6.3.1 Changing the Database Directory and LogDirectory (page 64)" in the active system. If the shared disk is the S drive, the directories are asfollows.

S:\SECUREMASTER

13. [Active] Stopping the disk resource and floating IP resource

Stop the disk resource and floating IP resource in the active system.

a. From EXPRESSCLUSTER WebManager, stop the disk resource. Select the activesystem on the "Select Server" dialog.

b. From EXPRESSCLUSTER WebManager, stop the floating IP resource. Select the activesystem on the "Select Server" dialog.

14. Rebooting the Cluster

From EXPRESSCLUSTER WebManager, reboot the cluster.

9.4.3 Cluster configuration for an ID management serverPerform the procedure described in "Chapter 6. Cluster Configuration for an ID Management Server(page 62)".

9.4.4 [Active] Reflecting the existing dataPerform the procedure of 4.7.4 Reflecting the existing Data in the Virtual DataCenter AutomationInstallation Guide in the active system.

After starting, move the failover group to verify that neither the active nor standby system causes anyerror.

9.5 Upgrading the Management Agent9.5.1 Stopping the failover group

Stop the failover group in the active system.

1. From EXPRESSCLUSTER WebManager, perform operations to stop the failover group.

9.5.2 Starting the disk resource and floating IP resourceStart the disk resource and floating IP resource in the active system.


89

1. From EXPRESSCLUSTER WebManager, start the disk resource. Select the active system onthe "Select Server" dialog.

2. From EXPRESSCLUSTER WebManager, start the floating IP resource. Select the activesystem on the "Select Server" dialog.

9.5.3 [Active] Stopping the serviceStop the service below manually.



9.5.4 [Active] Upgrading the management agentPerform the procedure described in "7.2 Installing the Management Agent (page 72)". No input ofsetting values is required.

On the "Product Installation Setting" screen, check that [Up] is assigned to the selected product namewhen installing.

9.5.5 [Active] Starting the serviceStart the service below manually.



9.5.6 Stopping the disk resource and floating IP resourceStop the disk resource in the active system.

1. From EXPRESSCLUSTER WebManager, stop the disk resource.

2. From EXPRESSCLUSTER WebManager, stop the floating IP resource.

9.5.7 Starting the disk resource and floating IP resourceStart the disk resource and floating IP resource in the standby system.

1. From EXPRESSCLUSTER WebManager, start the disk resource. Select the standby system onthe "Select Server" dialog.

2. From EXPRESSCLUSTER WebManager, start the floating IP resource. Select the standbysystem on the "Select Server" dialog.

9.5.8 [Standby] Stopping the serviceStop the service below manually.



90


9.5.9 [Standby] Upgrading the management agentPerform the procedure described in "7.2 Installing the Management Agent (page 72)". No input ofsetting values is required.

On the "Product Installation Setting" screen, check that [Up] is assigned to the selected product namewhen installing.

9.5.10 [Standby] Starting the serviceStart the service below manually.



9.5.11 Stopping the disk resource and floating IP resourceStop the disk resource in the standby system.



9.5.12 Starting the failover groupFrom EXPRESSCLUSTER WebManager, perform operations to start the failover group. Select theactive system on the "Select Server" dialog.


91

Chapter 10. Rolling update in the clusterenvironmentThis chapter describes the rolling update procedure in the cluster environment. In the followingsections, it is assumed that the cluster is operating in the active system.

Contents10.1 Rolling update the Global Management Server ........................................................................93

Chapter 10. Rolling update in the cluster environment

92

Rolling update is a method of upgrading the cluster configuration. The standby node is upgradedwhile the cluster package is working. The cluster package is moved to the standby node after thecompletion of the upgrade. The shared disk is updated at service startup in the original standby nodethat has switched to the active node.

Automation of the shared disk update allows upgrade with the minimum stop of the cluster package.

A rolling update can be used to update the version of the global management server.

10.1 Rolling update the Global ManagementServer

After rolling update the global management server, make sure to upgrade the correspondingmonitoring terminals. For details, refer to 4.2 Upgrading the Global Management Server Console inthe Virtual DataCenter Automation Installation Guide.

Note<Install folder> is the installation destination folder of Global Management Server.The default value of the installation folder is "C:\Program Files (x86)\NEC\vDCA\GM".










10.1.2 [Active] Backup of the service governorThis step is not necessary when updating the version from Version 2.2 or later.

Back up the configuration file. Back up the following file in any location.

• For non-cluster:


93

- <Install folder>\FW\WebOTX\domains\domain1\config\vdcplugins

- <Install folder>\FW\WebOTX\domains\domain1\config\vdcapi.properties

- <Install folder>\FW\WebOTX\domains\domain1\vDCApiKey.jks

• For cluster:

- S:\vDCA\domains\domain1\config\vdcplugins

- S:\vDCA\domains\domain1\config\vdcapi.properties

- S:\vDCA\domains\domain1\vDCApiKey.jks

10.1.3 [Standby] Upgrading the global management serverUpgrade the global management server in the standby system.

Perform the same procedure as the upgrading the active system 4.1.3. Upgrading the globalmanagement server in the Virtual DataCenter Automation Installation Guide, except as follows.

• Set the [Update the Data Directory at startup] setting to [Yes].






10.1.5 [Standby] Switching back the Service Governor SetupOverwrite the files that were backed up in any location in the procedure in "10.1.2 [Active] Backupof the service governor (page 93)".




10.1.6 Stopping the failover groupStop the failover group in the active system.



94














95





10.1.9 Starting the failover groupStop the following service in the standby system.


From EXPRESSCLUSTER WebManager, perform operations to start the failover group. Select thestandby system on the "Select Server" dialog.

Check that no error occurred when the shared disk update command updated the version of thestandby system.

The path of the shared disk update command log file is <Install folder>\FW\Manager\log\RupInstCmd.log.

The value of ExitCode at the end of the log file of the shared disk update command indicates the exitcode.

In the following example, the exit code is 0.

2016/04/26 12:32:48.356,4144,INF,RupInstCmd_Main,----- Rolling Update Start. --------2016/04/26 12:32:48.356,4144,INF,RupInstCmd_Main,UpdateData path=C:\Program Files (x86)\NEC\vDCA\GM\FW\Manager\UpdateData2016/04/26 12:32:48.396,4144,INF,RollingUpdateLoop,Total target product num=42016/04/26 12:32:48.396,4144,INF,RollingUpdateLoop,RollingUpdate loop 1. Target path=C:\Program Files (x86)\NEC\vDCA\GM\FW\Manager\UpdateData/Product1

: (Snip)

2016/04/26 12:32:52.332,4144,INF,UpdateImage,UpdateImage From=C:\Program Files (x86)\NEC\vDCA\GM\FW\Manager\UpdateData/Product4\Product, To=S:\vDCA\GM\FW\Manager2016/04/26 12:32:52.333,4144,INF,UpdateImage,Backup path=C:\Program Files (


96

x86)\NEC\vDCA\GM\FW\Manager\UpdateData/Product4\Product\Backup2016/04/26 12:32:52.478,4144,INF,CommandLoop,Phase=222016/04/26 12:32:52.478,4144,INF,CommandLoop,Phase=232016/04/26 12:32:52.479,4144,INF,RollingUpdateLoop,RollingUpdate loop 4. RetCode=02016/04/26 12:32:53.548,4144,INF,RupInstCmd_Main,----- Rolling Update End. ---------- ExitCode=0

• Exit code of 1 to 127

The shared disk update command terminated abnormally and the shared disk recovery processsucceeded.

• Exit code of 128 or higher

The shared disk update command terminated abnormally and the shared disk recovery processfailed.


10.1.11 [Active] Upgrading the global management serverUpgrade the global management server in the active system.

Perform the same procedure as the upgrading the standby system 4.1.3. Upgrading the globalmanagement server in the Virtual DataCenter Automation Installation Guide, except as follows.







10.1.13 [Active] Switching back the Service Governor SetupOverwrite the files that were backed up in any location in the procedure in "10.1.2 [Active] Backupof the service governor (page 93)".




10.1.14 Moving to the Active SystemStart the following service in the active system.


97


In the EXPRESSCLUSTER WebManager window, right-click the failover group and select [Move]to move to the active system.

Move the failover group to verify that neither the active nor standby system causes any error.

This concludes rolling update of the Virtual DataCenter Automation general management servercluster system.


98

Chapter 11. Upgrading from NW Automation on theCluster EnvironmentThis chapter describes the upgrade procedures from Network Automation to Virtual DataCenterAutomation in the cluster environment. In the following sections, it is assumed that the cluster isoperating in the active system.

Contents11.1 Upgrading the Global Management Server.............................................................................100

11.2 Upgrading the Management Server ........................................................................................104

11.3 Upgrading the ID Management Server ...................................................................................110

Chapter 11. Upgrading from NW Automation on the Cluster Environment

99

11.1 Upgrading the Global Management ServerAfter upgrading the global management server, make sure to upgrade the corresponding monitoringterminals. For details, refer to 5.2 Upgrading the Global Management Server Console in the VirtualDataCenter Automation Installation Guide.

11.1.1 PreparationPerform preparations required for operation of Virtual DataCenter Automation as a globalmanagement server. For details, see "Chapter 2. Preparation (page 5)". The settings that have beenspecified do not have to be specified again.








> otxadmin stop-domain --force --wait_timeout 180 domain1> otxadmin stop-domain --force --wait_timeout 180 WebOTXAdmin

In Version 2.2 or later, stop the following service. You can prevent the warning messages beingdisplayed in the alert view in EXPRESSCLUSTER WebManager by stopping the services from theEXPRESSCLUSTER task manager.


11.1.4 [Active] Upgrading the global management serverUpgrade the global management server by overwriting the old version by using the VirtualDataCenter Automation Integrated Installer after updating the version of each component with theNetwork Automation Integrated Installer.


100

For details, refer to 5.1. Upgrading the Global Management Server in the Virtual DataCenterAutomation Installation Guide.


Stop the following services, and change the [Startup type] to [Manual]. If registered theEXPRESSCLUSTER task manager, You can prevent the warning messages being displayed in thealert view in EXPRESSCLUSTER WebManager by stopping the services from theEXPRESSCLUSTER task manager.




11.1.6 [Standby] Upgrading the global management serverUpgrade the global management server by overwriting the old version by using the VirtualDataCenter Automation Integrated Installer after updating the version of each component with theNetwork Automation Integrated Installer.

For details, refer to 5.1. Upgrading the Global Management Server in the Virtual DataCenterAutomation Installation Guide.

Perform the same procedure as the upgrading the global management server, except as follows.










101















102







> armload service_BundleAPServer /S /WAIT 180 /M /FOV "ServiceGovernor"

In Version 2.2 or later, start the following service. Start the services by using [Start Monitoring] ifyou stopped them from the EXPRESSCLUSTER task manager.


11.1.11 Setting up the global management serverSet up the global management server.

License registration is performed after upgrading and installing the global management servermonitoring terminal. Perform the procedure described in 5.2 Upgrading the Global ManagementServer Console in the Virtual DataCenter Automation Installation Guide.

Perform the procedure described in 2.14.6 Setting up the Property File for the Service Governor inthe Virtual DataCenter Automation Installation Guide.




103

11.2 Upgrading the Management ServerAfter upgrading the management server, make sure to upgrade the corresponding monitoringterminals. For details, refer to 5.4 Upgrading the Management Server Console in the VirtualDataCenter Automation Installation Guide.

11.2.1 PreparationPerform preparations required for operation of Virtual DataCenter Automation as a globalmanagement server. For details, see "Chapter 2. Preparation (page 5)". The settings that have beenspecified do not have to be specified again.

11.2.2 Stopping the failover groupStop the failover group in the active system.


11.2.3 Starting the disk resource and floating IP resourceStart the disk resource and floating IP resource in the active system.

1. From EXPRESSCLUSTER WebManager, start the disk resource. Select the active system onthe "Select Server" dialog.

2. From EXPRESSCLUSTER WebManager, start the floating IP resource. Select the activesystem on the "Select Server" dialog.

11.2.4 [Active] Starting the SQL serverStart the following services.





11.2.5 [Active] Attaching the databasesPerform the procedure described in "4.9.4 Attaching the Databases (page 32)".

11.2.6 [Active] Re-creating database usersPerform the procedure described in "4.9.5 Re-Creating Database Users (page 32)".


104

11.2.7 [Active] Upgrading the management serverUpgrade the management server by overwriting the old version by using the Virtual DataCenterAutomation Integrated Installer after updating the version of each component with the NetworkAutomation Integrated Installer.

For details, refer to 5.3. Upgrading the Management Server in the Virtual DataCenter AutomationInstallation Guide.

11.2.8 [Active] Setting up the SigmaSystemCenterPerform the following procedure.

• From "4.3 [Active] Setting Up the SigmaSystemCenter Services (page 26)" to "4.6 [Active]Stopping a Database Instance and Changing the Startup Settings of the SigmaSystemCenterDatabase (page 29)".

• In "4.9.1 Positioning and Modifying the SQL Scripts (page 30)".

Perform the procedure following files.

Script Description

8 C:\MSSQL\attach_d.sql Used to attach a dpm database file.

9 C:\MSSQL\attach_p.sql Used to attach a pvm database file.

10 C:\MSSQL\detach_d.sql Used to detach a dpm database file.

11 C:\MSSQL\dettach_p.sql Used to detach a pvm database file.

• From "4.10 [Active] Copying a SigmaSystemCenter Database File (page 33)" to"4.17 [Active] Revising the SigmaSystemCenter Related Registry (page 37)".

11.2.9 [Active] Stopping the serviceStop the services below manually.

• FTBase service



11.2.10 [Active] Detaching the databasesPerform the procedure described in "4.29.3 Detaching the Database (page 42)".

11.2.11 [Active] Stopping the SQL serverStop the following services.






105

11.2.12 Stopping the disk resource and floating IP resourceStop the disk resource in the active system.



11.2.13 Starting the disk resource and floating IP resourceStart the disk resource and floating IP resource in the standby system.

1. From EXPRESSCLUSTER WebManager, start the disk resource. Select the standby system onthe "Select Server" dialog.

2. From EXPRESSCLUSTER WebManager, start the floating IP resource. Select the standbysystem on the "Select Server" dialog.

11.2.14 [Standby] Starting the SQL serverStart the following services.





11.2.15 [Standby] Attaching the databasesPerform the procedure described in "4.9.4 Attaching the Databases (page 32)".

11.2.16 [Standby] Re-creating database usersPerform the procedure described in "4.9.5 Re-Creating Database Users (page 32)".

11.2.17 [Standby] Upgrading the management serverUpgrade the management server by overwriting the old version by using the Virtual DataCenterAutomation Integrated Installer after updating the version of each component with the NetworkAutomation Integrated Installer.

For details, refer to 5.3. Upgrading the Management Server in the Virtual DataCenter AutomationInstallation Guide.

11.2.18 [Standby] Setting up the SigmaSystemCenterPerform the following procedure.

• From "4.23 [Standby] Setting Up the SigmaSystemCenter Services (page 40)" to"4.26 [Standby] Stopping a Database Instance and Changing the Startup Settings of theSigmaSystemCenter Database (page 40)".

• In "4.28 [Standby] Copying Data from the Active System (page 41)".

Perform the procedure following files.

Copy source (active system) Copy destination (standby system)

C:\MSSQL\attach_d.sql Same path


106

Copy source (active system) Copy destination (standby system)

C:\MSSQL\attach_p.sql Same path

C:\MSSQL\detach_d.sql Same path

C:\MSSQL\dettach_p.sql Same path

• "4.31 [Standby] Editing ESMPRO/ServerManager Configuration Files (page 42)".

11.2.19 [Standby] Stopping the serviceStop the services below manually.

• FTBase service



11.2.20 [Standby] Detaching the databasesPerform the procedure described in "4.29.3 Detaching the Database (page 42)".

11.2.21 [Standby] Stopping the SQL serverStop the following services.





11.2.22 Stopping the disk resource and floating IP resourceStop the disk resource in the standby system.



11.2.23 Starting the failover groupFrom EXPRESSCLUSTER WebManager, perform operations to start the failover group. Select theactive system on the "Select Server" dialog.


107

11.2.24 Setting Up the registry synchronous resourcesPerform the procedure described in "4.33 Setting Up the Registry Synchronous Resources (page43)".

11.2.25 Setting up the script resourcesFrom the EXPRESSCLUSTER WebManager, edit the script files included in this document as thescript resources.


<Install DVD>:\script\cluster-pro\MoM\vDCA\start.bat Service starting script

<Install DVD>:\script\cluster-pro\MoM\vDCA\stop.bat Service stopping script


1. From EXPRESSCLUSTER WebManager, change to the “Config Mode”, right-click "script" inthe resource list, and select “Properties”.

2. On the displayed dialog, select the [Details] tab, and click the [Add] button to register thescript.



NoteWhen being different from a default folder in an installation destination of a Management Server, pleasecorrect a installed path(2 Points) of a service script(start.bat).


108


11.2.26 Saving and Uploading Cluster InformationFrom the EXPRESSCLUSTER WebManager, save the cluster configuration information and uploadthe information files.

NoteIf the upload is skipped, the cluster will not operate normally because no configuration information isreflected to the active or standby system.




11.2.28 Registering and setting up the management serverPerform license registration and setting of the management server. License registration is performedafter upgrading and installing the management server monitoring terminal.

Perform the procedure described in 5.4 Upgrading the Management Server Console in the VirtualDataCenter Automation Installation Guide.

1. Perform license registration only for the SigmaSystemCenter function.

Perform setting of the SigmaSystemCenter function.

• From "4.37 [Active] Moving the DPM Backup Image Storage Folder / Image StorageFolder (page 46)" to "4.38 [Active] Registering the License in SigmaSystemCenter(page 47)".

• From "4.41 [Active] Registering a Subsystem in SigmaSystemCenter (page 48)" to"4.43 [Active] Initializing the Operation Management Functions (page 48)".

• "4.47 [Active] Changing the Environment Configuration of SystemMonitorPerformance Monitoring (page 49)".


109

11.2.29 Resuming the ClusterFrom EXPRESSCLUSTER WebManager, resume the cluster.

11.2.30 Rebooting the clusterFrom EXPRESSCLUSTER WebManager, reboot the cluster.


11.3 Upgrading the ID Management Server11.3.1 Changing the registry

In each of the active and standby systems, change the value of InstType of the following registry keyfrom NWA to VDCA.

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\vDCAInst\SecureMaster

This concludes upgrading of the Virtual DataCenter Automation ID management server clustersystem.


110

Chapter 12. Changing a single configuration (non-cluster) environment to a clusterconfigurationThis section describes how to change a newly installed Ver3.0 single configuration (non-cluster)environment to a cluster configuration.

Contents12.1 Applying a cluster configuration to the global management server.........................................112

12.2 Applying a cluster configuration to the management server ...................................................113

12.3 Applying a cluster configuration to the VM monitoring server...............................................114

Chapter 12. Changing a single configuration (non-cluster) environment to a cluster configuration

111

12.1 Applying a cluster configuration to theglobal management server

Note• <Install folder> is the installation destination folder of Global Management Server.

The default value of the installation folder is "C:\Program Files (x86)\NEC\vDCA\GM".• The S: drive is used for the shared disk of the active and standby servers.

<Data Directory> is "S:\vDCA\GM\FW_share".• Use current IP address as floating IP address in a cluster configuration.• Use current host name as virtual host name in a cluster configuration(host name by which the floating

IP address is resolved).

12.1.1 Stopping the serviceStop the following services


• MasterScope UMF Operations Web Service__VDCGMProxy_n


12.1.2 Moving the data area folderMove the data area folder to the shared disk.

Source Destination

<Install folder>\FW_share S:\vDCA\GM\FW_share

12.1.3 Create a link to the data area folderCreate a link to the data area folder.

Open the command prompt window, and execute the following command.

> cd <Install folder>> mklink /j FW_share S:\vDCA\GM\FW_share

12.1.4 Editing the SysMonMgr.iniEdit the configuration files as follows.

<Install folder>\FW\Manager\sg\SysMonMgr.ini

: (Snip): [DirectoryPath]SgPath=S:\vDCA\GM\FW_share\Manager\sgSgMask=1 <-Delete the definition.:


112

(Snip):

12.1.5 Editing the registryEdit the registry as follows.

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\vDCAInst\GM


VDCA_FW_DATA_PATH blank <Data Directory>

VDCA_OTHER_DATA_PATH_FLAG 2 1

12.1.6 Cluster Configuration for a Global Management ServerConfigure the cluster by using the single configuration (non-cluster) environment as the activesystem.

For details, refer to "Chapter 3. Cluster Configuration for a Global Management Server (page 8)"

12.2 Applying a cluster configuration to themanagement server

Note• <Install folder> is the installation destination folder of Management Server.

The default value of the installation folder is "C:\Program Files (x86)\NEC\vDCA\MoM".• The S: drive is used for the shared disk of the active and standby servers.

<Data Directory> is "S:\vDCA\MoM\FW_share".• Use current IP address as floating IP address in a cluster configuration.• Use current host name as virtual host name in a cluster configuration(host name by which the floating


12.2.1 Stopping the serviceStop the following services in the following order.

• MasterScope UMF Operations Web Service__VDCMoMProxy_n





• FTBase service



113

Source Destination

<Install folder>\FW_share S:\vDCA\MoM\FW_share



> cd <Install folder>> mklink /j FW_share S:\vDCA\MoM\FW_share



: (Snip): [DirectoryPath]SgPath=S:\vDCA\MoM\FW_share\Manager\sgSgMask=1 <-Delete the definition.: (Snip):


HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\vDCAInst\MoM




12.2.6 Cluster Configuration for a Management ServerConfigure the cluster by using the single configuration (non-cluster) environment as the activesystem.

For details, refer to "Chapter 4. Cluster Configuration for a Management Server (page 22)"

12.3 Applying a cluster configuration to the VMmonitoring server

Note• <Install folder> is the installation destination folder of VM Monitoring Server.

The default value of the installation folder is "C:\Program Files (x86)\NEC\vDCA\RM".• The S: drive is used for the shared disk of the active and standby servers.


114

<Data Directory> is "S:\vDCA\RM\FW_share".• Use current IP address as floating IP address in a cluster configuration.• Use current host name as virtual host name in a cluster configuration(host name by which the floating


12.3.1 Stopping the serviceStop the following services


• MasterScope UMF Operations Web Service__VDCRMProxy_n



Source Destination

<Install folder>\FW_share S:\vDCA\RM\FW_share



> cd <Install folder>> mklink /j FW_share S:\vDCA\RM\FW_share



: (Snip): [DirectoryPath]SgPath=S:\vDCA\RM\FW_share\Manager\sgSgMask=1 <-Delete the definition.: (Snip):


HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\vDCAInst\RM


115




12.3.6 Cluster Configuration for a VM Monitoring ServerConfigure the cluster by using the single configuration (non-cluster) environment as the activesystem.

For details, refer to "Chapter 5. Cluster Configuration of the VM Monitoring Server (page 50)"


116

Chapter 13. Notes

• Cautions Concerning Host Name Resolution

- When specifying a host name for the global management server, management server, andVM monitoring server, be sure to specify a name that can be resolved as described below.

* A management server name that can be resolved from the global management server

* A global management server name that can be resolved from the management server

* A management server name that can be resolved from the VM monitoring server

- If the host whose name is to be resolved is in a cluster configuration, specify a virtual hostname (host name by which the floating IP address is resolved) that can be resolved.

• Cautions Concerning the Host Name in the SysMonMgr.ini File

- [UpperNode]HostName described in the SysMonMgr.ini file of the lower manager mustmatch [SelfNode]HostName in the SysMonMgr.ini file of the upper manager.

SysMonMgr.ini for Global management server

[SelfNode]HostName=gm

SysMonMgr.ini for management server

[UpperNode]HostName=gm

If the host name of the global management server is gm, specify the settings in theSysMonMgr.ini file for the global management server and management server as describedabove.

Specify the settings for the management server and VM monitoring server in the sameway.

- If the local host is in a cluster configuration, a virtual host name (host name by which thefloating IP address is resolved) or floating IP address must be specified for the local hostname. If the host at the connection destination is in a cluster configuration, specify a virtualhost name or floating IP address.

Chapter 13. Notes

117

Appendix A. Revision History• First edition (May. 2015): Newly created

Appendix A. Revision History

118

Appendix B. User Customizable Filesand Folders

Neither the following files nor folders are stored on the shared (or mirror) disk. For the usercustomization, they must be placed in both the active and standby machines.

• C:\Program Files (x86)\NEC\vDCA\MoM\SSC\PVM\Provisioning\App_Data\Config\CustomizationConfig.xml

In addition, the following cannot be taken over between nodes: the display settings (i.e. graphsettings) and debug log settings of the management console for SystemMonitor performancemonitoring. To change the settings, duplicate the following files on the standby node:

• C:\Program Files (x86)\NEC\vDCA\MoM\SSC\SystemMonitorPerformance\bin\rm_client.xml

• C:\Program Files (x86)\NEC\vDCA\MoM\SSC\SystemMonitorPerformance\bin\rm_service_init.xml

Appendix B. User Customizable Files and Folders

119

MasterScope Virtual DataCenter Automation v3.0Cluster Construction Guide

For Windows/EXPRESSCLUSTER X

June, 2016 1st Edition

NEC Corporation

©NEC Corporation 2012-2016

Documents

MasterScope Virtual DataCenter Automation v3 › en_HK › en › global › prod › masterscope › vdcaut… · MasterScope Virtual DataCenter Automation v3.0 Cluster Construction