MasterScope Virtual DataCenter Automation v3 - NEChk.nec.com/en_HK/en/global/prod/masterscope/vdcautomation/en/... · MasterScope Virtual DataCenter Automation v3.0 Installation Guide

MasterScope Virtual DataCenterAutomation v3.0

Installation Guide

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 and includes details of how to install, upgrade,upgrade from Network Automation and uninstall Virtual DataCenter Automation.

Overview of the DocumentThis document describes the procedure for installation, upgrade installation, upgrade from NetworkAutomation and uninstallation of the Virtual DataCenter Automation.

The subsequent sections describe the basic functions and configuration of the Virtual DataCenterAutomation Integrated Installer.

For a new installation of Virtual DataCenter Automation, refer to "Chapter 2. Performinginstallation by selecting functions (page 4)".

For upgrade installation of Virtual DataCenter Automation, refer to "Chapter 4. Upgrading (page107)".

For upgrade from Network Automation, refer to "Chapter 5. Upgrading from Network Automation(page 142)".

For uninstallation of Virtual DataCenter Automation, refer to "Chapter 6. Performing Uninstallation(page 147)".

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

iii

Notation How to use Example

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>

iv

ContentsChapter 1. Overview of Virtual DataCenter Automation Installation ................................... 1

1.1 Virtual DataCenter Automation Integrated Installer ..............................................................21.1.1 Installation Modes of the Virtual DataCenter Automation ...........................................2

1.2 DVD Configuration of Virtual DataCenter Automation ........................................................2

Chapter 2. Performing installation by selecting functions....................................................... 42.1 Types of Functions to be Installed .........................................................................................5

2.1.1 Server Configuration Diagram of Virtual DataCenter Automation ..............................52.1.2 Roles of Each Function ...............................................................................................62.1.3 Cautions Regarding Installing Multiple Functions on the Same Machine ....................62.1.4 Cautions Regarding Installing Global Management Server and Management Server on

the Same Machine..........................................................................................................7

2.2 Software Required to be Installed in Advance.....................................................................102.2.1 List of Software to be Installed in Advance ...............................................................102.2.2 Installing Internet Information Service (IIS) Manager and ASP.NET ........................112.2.3 Installing .Net Framework 3.5 Service Pack1 ............................................................112.2.4 Installing .Net Framework 4.0 ...................................................................................122.2.5 Installing .Net Framework 4.5.2 ................................................................................122.2.6 Installing SQL Server................................................................................................122.2.7 Installing the Services for NFS..................................................................................162.2.8 Installing VMware vSphere PowerCLI......................................................................162.2.9 Installing NEC ESMPRO Agent ...............................................................................162.2.10 Installing NEC ESMPRO Agent for VMWare .........................................................16

2.3 Installing the components of Global Management Server....................................................162.3.1 Components Installed on the Global Management Server .........................................172.3.2 Software Required to be Installed in Advance ...........................................................172.3.3 Setting up the Windows Firewall...............................................................................182.3.4 Cautions before Performing Installation ....................................................................182.3.5 Installing the components of Global Management Server..........................................18

2.4 Installing the components of Global Management Server Console......................................232.4.1 Components installed on the Global Management Server Console ............................232.4.2 Cautions before Performing Installation ....................................................................232.4.3 Installing the components of Global Management Server Console ............................23

2.5 Installing the components of Management Server ...............................................................262.5.1 Components Installed on the Management Server .....................................................272.5.2 Software Required to be Installed in Advance ...........................................................272.5.3 DHCP Server Configuration......................................................................................282.5.4 Setting Up the Windows Firewall ..............................................................................282.5.5 Precautions When Setting NEC ESMPRO Manager User Group ..............................282.5.6 Precautions When Installing Virtual DataCenter Automation Management Server....292.5.7 Cautions before Performing Installation ....................................................................292.5.8 Installing the components of Management Server .....................................................29

2.6 Installing the components of Management Server Console .................................................34

v

2.6.1 Components Installed on the Management Server Console .......................................342.6.2 Cautions before Performing Installation ....................................................................352.6.3 Installing the components of Management Server Console .......................................35

2.7 Installing the components of VM Monitoring Server ..........................................................382.7.1 Components Installed on the VM monitoring Server.................................................382.7.2 Software Required to be Installed in Advance ...........................................................382.7.3 Setting up the Windows Firewall...............................................................................382.7.4 Cautions before Performing Installation ....................................................................392.7.5 Installing the components of VM Monitoring Server.................................................39

2.8 Installing the components of VM Monitoring Server Console.............................................422.8.1 Components Installed on the VM monitoring Server Console ...................................422.8.2 Cautions before Performing Installation ....................................................................422.8.3 Installing the components of VM Monitoring Server Console...................................43

2.9 Installing the components of ID Management Server ..........................................................462.9.1 Components Installed on the ID Management Server ................................................462.9.2 Software Required to be Installed in Advance ...........................................................462.9.3 Setting up the Windows Firewall...............................................................................462.9.4 Cautions before Performing Installation ....................................................................462.9.5 Installing the components of ID Management Server ................................................47

2.10 Installing the components of Managed Machine................................................................492.10.1 VMWare ESXi / ESX Virtualization Infrastructure .................................................502.10.2 Hyper-V Virtualization Infrastructure ......................................................................502.10.3 KVM Virtualization Infrastructure ..........................................................................50

2.11 Installing the components of Managed Machine (Windows) .............................................502.11.1 Software Required to be Installed in Advance .........................................................502.11.2 Cautions before Performing Installation ..................................................................512.11.3 Installing the components of Managed Machine (Windows) ...................................51

2.12 Installing the components of Managed Machine (Linux)...................................................552.12.1 Software Required to be Installed in Advance .........................................................552.12.2 Cautions before Performing Installation ..................................................................552.12.3 Installing the components of Managed Machine (Linux).........................................55

2.13 Installing the components of Management Agent..............................................................602.13.1 Components Installed on the Management Agent....................................................602.13.2 Software Required to be Installed in Advance .........................................................612.13.3 Installing Visual C++ 2005 Redistributable Package ...............................................612.13.4 Installing .Net Framework 3.5 Service Pack1 ..........................................................612.13.5 Installing the components of Management Agent ....................................................61

2.14 Registering and Setting up the Global Management Server ...............................................642.14.1 Registering License to Operation Management Function ........................................642.14.2 Registering CodeWord to Operation Management Function....................................662.14.3 Registering Option License and Codeword .............................................................662.14.4 Setting up the Service Governor..............................................................................672.14.5 SSL Settings of Application Server .........................................................................692.14.6 Setting up the Property File for the Service Governor .............................................702.14.7 Default Settings of Asset Management Function .....................................................73

vi

2.14.7.1 Registering New Company............................................................................732.14.7.2 Setting up Agent Environment ......................................................................74

2.14.8 Default Settings of Operation Management Function ..............................................762.14.9 Editing Trace Log Settings of Resource Management Function ..............................782.14.10 Redundant Configuration of the Service Governor ................................................79

2.15 Registering and Setting up the Management Server ..........................................................792.15.1 Registering License to SigmaSystemCenter Function..............................................792.15.2 Registering License to Operation Management Function ........................................802.15.3 Registering Code Word to Operation Management Function...................................812.15.4 Setting up WebAPI for SSC ....................................................................................812.15.5 Default Settings of Operation Management Function ..............................................822.15.6 Setting the Monitoring Definition of Management Server Performance Monitoring822.15.7 Linkage setting between Global Management Server ..............................................832.15.8 Setting the Accumulation Period of Statistical Information .....................................84

2.16 Registering and Setting up the VM Monitoring Server......................................................852.16.1 Registering the License to the Operation Management Function .............................852.16.2 Registering Code Word to Operation Management Function...................................862.16.3 Default Settings of Operation Management Function ..............................................862.16.4 Linkage setting between Management Server..........................................................862.16.5 Deleting scenario settings ........................................................................................872.16.6 Setting the Monitoring Definition of VM Monitoring Server Performance

Monitoring...................................................................................................................872.16.7 Setting the Accumulation Period of Statistical Information .....................................88

2.17 Registering and Setting up the Management Agent ...........................................................882.17.1 Registering the VM Server ......................................................................................882.17.2 Registering the Storage ...........................................................................................90

2.18 Registering and Setting up the ID Management Server .....................................................922.18.1 Setting up the Services ............................................................................................922.18.2 Changing the Password of the Administrator User ..................................................922.18.3 Use of the ID Management Server...........................................................................94

2.19 Setting up the Managed Machine ......................................................................................942.19.1 Creating the VM Template of the Managed Machine ..............................................94

Chapter 3. Performing Installation According to the Purpose.............................................. 953.1 Redundant Configuration of the Service Governor..............................................................96

3.1.1 Installing the ServiceGovernor ..................................................................................963.1.2 Uninstalling the ServiceGovernor ...........................................................................101

Chapter 4. Upgrading .............................................................................................................. 1074.1 Upgrading the Global Management Server........................................................................108

4.1.1 Stop the services......................................................................................................1084.1.2 Backup of the service governor ...............................................................................1084.1.3 Upgrading the global management server................................................................1084.1.4 Editing Trace Log Settings of Resource Management Function ..............................1124.1.5 Updating the Database ............................................................................................113

4.1.5.1 Updating the local database...........................................................................1134.1.5.2 Updating the remote database........................................................................114

vii

4.1.6 Upgrading the service governor...............................................................................1144.1.7 Start the services .....................................................................................................1144.1.8 Applying the standard workflow template ...............................................................115

4.2 Upgrading the Global Management Server Console..........................................................1164.2.1 Upgrading the Global Management Server Console ................................................116

4.3 Upgrading the Management Server ...................................................................................1164.3.1 Stop the services......................................................................................................1164.3.2 Upgrading the Management Server .........................................................................1174.3.3 Updating the Database ............................................................................................118

4.3.3.1 Updating the local database(Database for Network Manager = Other DB) ....1184.3.3.2 Updating the local database(Database for Network Manager = Bundled DB)1194.3.3.3 Updating the remote database(Database for Network Manager = Bundled DB) ..

............................................................................................................................1194.3.4 Start the services .....................................................................................................1204.3.5 Applying the standard workflow template ...............................................................1204.3.6 Upgrading the SigmaSystemCenter .........................................................................1204.3.7 Registering License to SigmaSystemCenter ............................................................120

4.4 Upgrading the Management Server Console .....................................................................1204.4.1 Upgrading the Management Server Console ...........................................................120

4.5 Upgrading the VM Monitoring Server ..............................................................................1224.5.1 Stop the services......................................................................................................1224.5.2 Upgrading the VM Monitoring Server.....................................................................1224.5.3 Updating the Database ............................................................................................123

4.5.3.1 Updating the local database ...........................................................................1234.5.3.2 Updating the remote database........................................................................124

4.5.4 Start the services .....................................................................................................124

4.6 Upgrading the VM Monitoring Server Console.................................................................1244.6.1 Upgrading the VM Monitoring Server Console .......................................................124

4.7 Upgrading the ID Management Server ..............................................................................1264.7.1 Extracting the existing data .....................................................................................1264.7.2 Uninstalling the ID management server of the current version ................................1274.7.3 Installing the ID management server of the new version .........................................1274.7.4 Reflecting the existing data .....................................................................................128

4.8 Upgrading the Managed Machine .....................................................................................1294.8.1 Managed machine (Windows) .................................................................................129

4.8.1.1 Stop the service .............................................................................................1294.8.1.2 Upgrading the Managed Machine(Windows) ................................................1294.8.1.3 Upgrading the DeploymentManager client(Windows)...................................1304.8.1.4 Start the service.............................................................................................133

4.8.2 Managed machine (Linux) ......................................................................................1334.8.2.1 Stop the service .............................................................................................1334.8.2.2 Cautions before Upgrading............................................................................1334.8.2.3 Upgrading the Managed Machine(Linux) ......................................................1344.8.2.4 Upgrading the DPM Client(Linux) ................................................................1384.8.2.5 Start the service.............................................................................................139

4.8.3 Managed machine (virtual base VMware ESX environment) ..................................1404.8.3.1 Stop the service .............................................................................................140

viii

4.8.3.2 Managed machine (virtual base VMware ESX environment) ........................1404.8.3.3 Start the service.............................................................................................140

4.8.4 Managed machine (virtual base Hyper-V environment) ..........................................1404.8.4.1 Stop the service .............................................................................................1404.8.4.2 Managed machine (virtual base Hyper-V environment).................................1404.8.4.3 Start the service.............................................................................................141

Chapter 5. Upgrading from Network Automation ............................................................... 1425.1 Upgrading the Global Management Server........................................................................143

5.1.1 Preparation ..............................................................................................................1435.1.2 Registering the upgrade license ...............................................................................1435.1.3 Upgrading the Global management server ...............................................................1435.1.4 Registering and setting up the Global management server.......................................143

5.2 Upgrading the Global Management Server Console..........................................................1445.2.1 Upgrade installation of the global management server console................................144

5.3 Upgrading the Management Server ...................................................................................1445.3.1 Preparation..............................................................................................................1445.3.2 Upgrading the management server ..........................................................................1445.3.3 Registering and Setting up the Management Server ................................................145

5.4 Upgrading the Management Server Console .....................................................................1455.4.1 Upgrade installation of the management server console ..........................................145

5.5 Upgrading the ID Management Server ..............................................................................1465.5.1 Changing the registry ..............................................................................................146

Chapter 6. Performing Uninstallation ................................................................................... 1476.1 Before Uninstallation ........................................................................................................148

6.1.1 Precautions before Uninstallation ............................................................................148

6.2 Uninstalling the Components Installed on Windows .........................................................1486.2.1 Uninstalling the components of Global Management Server ...................................1486.2.2 Uninstalling the components of Global Management Server Console .....................1526.2.3 Uninstalling the components of Management Server...............................................1546.2.4 Uninstalling the components of Management Server Console .................................1596.2.5 Uninstalling the components of VM Monitoring Server ..........................................1616.2.6 Uninstalling the components of VM Monitoring Server Console ............................1636.2.7 Uninstalling the components of ID Management Server..........................................1656.2.8 Uninstalling the components of Managed Machine .................................................1666.2.9 Uninstalling the components of Management Agent ...............................................1676.2.10 Uninstalling the SQL Server Client Tools..............................................................1686.2.11 Uninstalling SQL Server .......................................................................................1696.2.12 Uninstalling VMware vSphare PowerCLI .............................................................170

6.3 Uninstalling the components installed in Linux.................................................................1706.3.1 Cautions before Performing Uninstallation..............................................................1706.3.2 Uninstalling the components of Managed Machine .................................................170

Chapter 7. Troubleshooting..................................................................................................... 1737.1 SigmaSystemCenter Troubleshooting................................................................................174

7.1.1 Messages during ESMPRO/ServerManager Installation / Uninstallation.................174

ix

7.1.2 Messages after ESMPRO/ServerManager Uninstallation ........................................1747.1.3 After Installation to Windows Server 2008 Management Server, Web Console Does

Not Start. ...................................................................................................................174

7.2 Troubleshooting for the Installer .......................................................................................1757.2.1 A restart is requested during installation of the Management Server........................1757.2.2 An error occurs during installation ..........................................................................1767.2.3 Collecting Failure Information ................................................................................177

7.3 Operation and Asset Management Functions Troubleshooting ..........................................1787.3.1 The console cannot be started. .................................................................................1787.3.2 An error dialog is displayed as the console starts up................................................1787.3.3 Context Menu of [Asset Management] Node Is Not Displayed ...............................1797.3.4 Collecting Failure Information ................................................................................180

Appendix A. Revision History................................................................................................. 181

Appendix B. License Information........................................................................................... 182

Appendix C. Network and Protocol ....................................................................................... 183

Appendix D. Certificate in the SSL Setting ........................................................................... 193

x

List of TablesTable 2-1 Selection of function ...............................................................................................13Table 2-2 Instance name to create ...........................................................................................13Table 2-3 Log on user of the SQL Server services ..................................................................14Table 2-4 SQL Server network configuration..........................................................................14Table 2-5 Adding a fixed server role member .........................................................................14

xi

Chapter 1. Overview of Virtual DataCenterAutomation InstallationThis chapter describes how to read this document and the Virtual DataCenter Automation IntegratedInstaller for installing and uninstalling Virtual DataCenter Automation.

Contents1.1 Virtual DataCenter Automation Integrated Installer .....................................................................2

1.2 DVD Configuration of Virtual DataCenter Automation ...............................................................2

Chapter 1. Overview of Virtual DataCenter Automation Installation

1

1.1 Virtual DataCenter Automation IntegratedInstaller

Virtual DataCenter Automation can be installed using the Virtual DataCenter Automation IntegratedInstaller.

The Virtual DataCenter Automation Integrated Installer allows you to install the product componentsof Global Management Server, Global Management Server Console, Management Server,Management Server Console, VM Monitoring Server, VM Monitoring Server Console, IDManagement Server and Managed Machine.

Note• The installer is unavailable for the UNC path and on the drive to which the network drive is allocated.

Use the installer on the DVD drive.• Perform "Programs and Features" instead of "Add or Remove Programs" when using Windows Server

2008.

1.1.1 Installation Modes of the Virtual DataCenter AutomationThe Virtual DataCenter Automation Integrated Installer has two installation modes.

• Typical mode

This mode allows you to install the product components comprising the Virtual DataCenterAutomation function in a batch.

Select the functions to be installed.

• Custom mode

This mode starts the installer of the products comprising Virtual DataCenter Automation.

Use this to update the versions of product components that make up the Virtual DataCenterAutomation function.

It is also used for adding functions of product components, performing maintenance, andchanging the server configuration of Virtual DataCenter Automation if required.

NoteTo uninstall Virtual DataCenter Automation, follow the uninstallation method for each product.

1.2 DVD Configuration of Virtual DataCenterAutomation

The Virtual DataCenter Automation Integrated Installer is stored on the vDCA/NWA install DVD asfollows.

vDCA/NWA Install DVD

\ install

\ Windows

| \ vDCAInst.exe Virtual DataCenter Automation Integrated Installer(Windows)

\ Linux


2

vDCA/NWA Install DVD

\ vDCAInst.sh Virtual DataCenter Automation Integrated Installer(Linux)


3

Chapter 2. Performing installation by selectingfunctionsThis chapter describes the installation procedures for each function type of Virtual DataCenterAutomation. It describes the required settings in Windows Server before installation using the VirtualDataCenter Automation Integrated Installer, tools to be installed in advance, and installation ofproduct components using the Integrated Installer.

Contents2.1 Types of Functions to be Installed ................................................................................................5

2.2 Software Required to be Installed in Advance............................................................................10

2.3 Installing the components of Global Management Server...........................................................16

2.4 Installing the components of Global Management Server Console.............................................23

2.5 Installing the components of Management Server ......................................................................26

2.6 Installing the components of Management Server Console ........................................................34

2.7 Installing the components of VM Monitoring Server .................................................................38

2.8 Installing the components of VM Monitoring Server Console....................................................42

2.9 Installing the components of ID Management Server .................................................................46

2.10 Installing the components of Managed Machine.......................................................................49

2.11 Installing the components of Managed Machine (Windows) ....................................................50

2.12 Installing the components of Managed Machine (Linux)..........................................................55

2.13 Installing the components of Management Agent.....................................................................60

2.14 Registering and Setting up the Global Management Server ......................................................64

2.15 Registering and Setting up the Management Server .................................................................79

2.16 Registering and Setting up the VM Monitoring Server.............................................................85

2.17 Registering and Setting up the Management Agent ..................................................................88

2.18 Registering and Setting up the ID Management Server ............................................................92

2.19 Setting up the Managed Machine .............................................................................................94

Chapter 2. Performing installation by selecting functions

4

2.1 Types of Functions to be InstalledThis section describes the types and configuration of the functions comprising Virtual DataCenterAutomation.

2.1.1 Server Configuration Diagram of Virtual DataCenterAutomation

The followings are the types of functions to be installed in the installation procedure of thisdocument.

• Global Management Server

• Global Management Server Console

• Management Server

• Management Server Console

• VM Monitoring Server

• VM Monitoring Server Console

• ID Management Server

• Managed Machine

- Physical Machines

- Basis of virtualization

- Virtual Machines (VM), VM Templates

• Management Agent

Note• Configurations where Global Manager Server of Network Automation and Management Server of

Virtual DataCenter Automation are not supported.


5

• Refer to Virtual DataCenter Automation Portal user manual (Installation Guide) and VirtualDataCenter Automation Portal user manual (Operations Guide) about Virtual DataCenter AutomationPortal.

2.1.2 Roles of Each FunctionThe roles of each function are as follows.

Function Role

Global Management Server Manages and monitors all resources in Virtual DataCenter Automation in anintegrated fashion.Provides a single-point gateway function working with an external function such asCloud Manager.

Global Management ServerConsole

Provides functions to monitor and control the resources managed by the GlobalManagement Server.

Management Server Provides functions to monitor and control the storage, network, virtualizationinfrastructure, and virtual machines (VM).

Management ServerConsole

Provides functions to monitor and control the resources managed by the ManagementServer.

VM Monitoring Server Provides functions to monitor and control virtual machines. Plays the role of reducingthe Management Server load when monitoring virtual machines.The VM Monitoring Server is installed when IaaS providers monitor virtual machinesin detail.

VM Monitoring ServerConsole

Provides functions to monitor and control the resources managed by the VMMonitoring Server.

ID Management Server The ID Management Server provides the function to integrate login accounts of IaaSproviders and login accounts for resources assigned to tenants and manage them.The ID Management Server can be installed along with the Global ManagementServer, and Management Server.

Managed Machine Provides functions to monitor and control by installation on the virtualizationinfrastructure such as a managed virtual machine, physical machine, ESX or Hyper-V.

Management Agent Provides functions to monitor servers where the Management Agent is installed,storage devices to be managed, vCenterServer, and ESXi.

NoteFor the system requirements of each function, see Chapter 6. Operating Environments/System Requirementsin Virtual DataCenter Automation First Step Guide.

2.1.3 Cautions Regarding Installing Multiple Functions on theSame Machine

When installing multiple functions on the same machine, observe the following combination rules.

GlobalManagement

Server

ManagementServer

VM MonitoringServer

IDManagement

Server

ManagedMachine

GlobalManagement

Server

- √ √ *1

ManagementServer

√ - √ *1


6

GlobalManagement

Server

ManagementServer

VM MonitoringServer

IDManagement

Server

ManagedMachine

VM MonitoringServer

- √ *1

ID ManagementServer

√ √ √ - *1

ManagedMachine

*1 *1 *1 *1 -

*1 If a version earlier than Ver2.1 is installed, installation can be performed on the same machine.

√: Can be installed on the same machine.

No mark: Cannot be installed on the same machine.

2.1.4 Cautions Regarding Installing Global ManagementServer and Management Server on the Same Machine

When installing Global Management Server and Management Server on the same machine, becareful to avoid duplicating port numbers.

1. Port for internal communication between the Application Server and Virtual DataCenterAutomation components

The Application Server on the global management server communicates internally with theVirtual DataCenter Automation components on the global management server and the VirtualDataCenter Automation components on the management server.

For the Virtual DataCenter Automation components used for the communication, port number8081 is used by default. When installing the global management server and managementserver on the same machine, change one of the port numbers.

• Changing the communication port for the Application Server and Virtual DataCenterAutomation components

Indicates the port of "Virtual DataCenter Automation WebService View" of the globalmanagement server component and the management server component in "AppendixC. Network and Protocol (page 183)"

- On the [Setting of GlobalManager] screen displayed when the global managementserver is installed, change [WebService Port] from 8081. (For the detailed screens ofthe installer, refer to "2.3.5 Installing the components of Global ManagementServer (page 18)".)

- On the [Setting of Management Server] screen displayed when the managementserver is installed, change [WebService Port] from 8081. (For the detailed screens ofthe installer, refer to "2.5.8 Installing the components of Management Server (page29)".)

Along with the change above, specify an appropriate port number in the configuration file ofthe Application Server on the global management server according to "2.14.4 Setting up theService Governor (page 67)".

2. Communication port for the global management server and management server orcommunication port for the management server and agent


7

For internal communication between the Virtual DataCenter Automation components on theglobal management server and the Virtual DataCenter Automation components on themanagement server and for communication between the management server and agent, 12520is used by default. When installing the global management server and management server onthe same machine, change the communication port number of the communication port for theglobal management server and management server or the communication port for themanagement server and agent during installation.

• Changing the communication port for the global management server and managementserver

- On the [Setting of GlobalManager] screen displayed when the global managementserver is installed, change [Management Server/Agent Port] from 12520. (For thedetailed screens of the installer, refer to "2.3.5 Installing the components of GlobalManagement Server (page 18)".)

- On the [Setting of Management Server] screen displayed when the managementserver is installed, change [GlobalManager Port] from 12520. Change it to the samevalue as set in [Management Server/Agent Port] for the global management server.(For the detailed screens of the installer, refer to "2.5.8 Installing the componentsof Management Server (page 29)".)

• Changing the communication port for the management server and VM MonitoringServer/Agent

- On the [Setting of Management Server] screen displayed when the managementserver is installed, change [VM Monitoring Server/Agent Port] from 12520. (For thedetailed screens of the installer, refer to "2.5.8 Installing the components ofManagement Server (page 29)".)

- On the [Setting of VM Monitoring Server] screen displayed when the VMMonitoring Server is installed, change [Management Server Port] from 12520. (Forthe detailed screens of the installer, refer to "2.7.5 Installing the components of VMMonitoring Server (page 39)".)

- On the [Setting of Managed machine] screen displayed when the managed machineis installed, change [Manager Port] from 12520. Change it to the same value as setin [VM Monitoring Server/Agent Port] for the management server. (For the detailedscreens of the installer, refer to "2.11.3 Installing the components of ManagedMachine (Windows) (page 51)" or "2.12.3 Installing the components of ManagedMachine (Linux) (page 55)".)

3. Own host name of the global management server or management server

For the own host name of the global management server or management server, the host nameis specified by default. When installing the global management server and management serveron the same machine, change one of the own host names during installation to avoid overlap.

• Changing the own host name of the global management server

- On the [Setting of GlobalManager] screen displayed when the global managementserver is installed, change [Self Hostname]. (For the detailed screens of the installer,refer to "2.3.5 Installing the components of Global Management Server (page18)".)

- On the [Setting of Management Server] screen displayed when the managementserver is installed, change [GlobalManager Hostname]. Change it to the same valueas set in [Self Hostname] for the global management server. (For the detailed screens


8

of the installer, refer to "2.5.8 Installing the components of Management Server(page 29)".)

- On the [Setting of GlobalManager View] screen displayed when the globalmanagement server console is installed, change [GlobalManager Hostname].Change it to the same value as set in [Self Hostname] for the global managementserver. (For the detailed screens of the installer, refer to "2.4.3 Installing thecomponents of Global Management Server Console (page 23)".)

• Changing the own host name of the management server

- On the [Setting of Management Server] screen displayed when the managementserver is installed, change [Self Hostname]. (For the detailed screens of the installer,refer to "2.5.8 Installing the components of Management Server (page 29)".)

- On the Setting of Managed machine [Setting of Managed machine] screen displayedwhen the managed machine is installed, change [Manager Hostname]. Change it tothe same value as set in [Self Hostname] for the management server. (For thedetailed screens of the installer, refer to "2.11.3 Installing the components ofManaged Machine (Windows) (page 51)" or "2.12.3 Installing the components ofManaged Machine (Linux) (page 55)".)

- On the [Setting of Management Server View] screen displayed when themanagement server console is installed, change [Management Server Hostname].Change it to the same value as set in [Self Hostname] for the management server.(For the detailed screens of the installer, refer to "2.6.3 Installing the componentsof Management Server Console (page 35)".)

4. Communication port with the console

For communication between the global management server and global management serverconsole and for communication between the global management server and globalmanagement server console, 12521 is used by default. When installing the global managementserver and management server on the same machine, change one of the port numbers.

• Changing the communication port for the global management server and globalmanagement server console

- On the [Setting of GlobalManager] screen displayed when the global managementserver is installed, change [Viewer Port]. (For the detailed screens of the installer,refer to "2.3.5 Installing the components of Global Management Server (page18)".)

- On the [Setting of GlobalManager View] screen displayed when the globalmanagement server console is installed, change [GlobalManager Port]. Change it tothe same value as set in [Viewer Port] for the global management server. (For thedetailed screens of the installer, refer to "2.4.3 Installing the components of GlobalManagement Server Console (page 23)".)

• Changing the own host name of the management server

- On the [Setting of Managed machine] screen displayed when the management serveris installed, change [Viewer Port]. (For the detailed screens of the installer, refer to"2.5.8 Installing the components of Management Server (page 29)".)

- On the [Setting of Management Server View] screen displayed when themanagement server console is installed, change [Management Server Port]. Changeit to the same value as set in [Viewer Port] for the management server. (For thedetailed screens of the installer, refer to "2.6.3 Installing the components ofManagement Server Console (page 35)".)


9

2.2 Software Required to be Installed in AdvanceThis section describes the software required before installation using the Virtual DataCenterAutomation Integrated Installer.

2.2.1 List of Software to be Installed in AdvanceIn Virtual DataCenter Automation, the following software must be installed before installing for eachmachine type.

GlobalManagement

Server

ManagementServer

VM MonitoringServer

Internet Information Service - Necessary -

.NET Framework 3.5 Service Pack 1 Necessary Necessary Necessary

.NET Framework 4.0 Necessary Necessary Necessary

.NET Framework 4.5.2 - Necessary -

SQL Server / client tool Necessary*1 Necessary*1 Necessary*1

VMware vSphere PowerCLI - Optional*2 -

Services for NFS Optional*3 Optional*3*4 Optional*3

*1 To use a separate server for the DBMS, install SQL Server on the DBMS server, and install the SQLServer client tools on the machine on which the Global Management Server, Management Server, andVM Monitoring Server are installed. For the required software of the DB server, see 6.10 DB server inVirtual DataCenter Automation First Step Guide. If the DBMS is not separately used as a server, theSQL Server client tools do not have to be installed.

*2 It is necessary when VMware is used as the virtualization infrastructure to use the template sharingfunction. PowerCLI of the version which corresponds to the VMware vCenter Server version andESX/ESXi version is needed. For details, see document of VMware.

*3 To construct storage for the software repository with NFS sharing, the NFS service must be installed.*4 It is necessary for using the template sharing function when NFS is used as the communication

protocol between the file server and Management Server. It is not necessary if the template sharingfunction is not used or CIFS is used as the communication protocol.

Managedmachine(Windows

)

Managedmachine(Linux)

VirtualizationinfrastructureVMWare ESX

NEC ESMPRO Agent Optional*1 Optional*1 -

NEC ESMPRO Agent for VMware - - Optional*1

*1 It is necessary only if NEC ESMPRO Manager is used.

For consoles (Global Management Server, Management Server, and VM Monitoring Server) and IDManagement Server, there is no software required to be installed in advance.

File sharing software required for storage access is shown in the table below. ("-" in the tableindicates it is not applicable.)


10

Function VM template sharing Distribution software paches from globalmanagement server

Protocolscorrespondingto the storage

to be used√:Support

-:Unsupported

Shared disk Local disk ofeach server

NFS CIFS NFS CIFS FWown

√ √ √ √Need thesetting

allowing Guestaccess is

required forthe shared

disk

√

Globalmanagementserver

- - Need NFSservice

Unnecessary(Standardsupport)

Unnecessary(Distributed withthe FW corepath)

Managementserver

Need NFSservice


Need NFSservice



VM monitoringserver

- - Need NFSservice



Managedmachine

- - Unnecessary(Distributed withthe FW corepath)



2.2.2 Installing Internet Information Service (IIS) Manager andASP.NET

1. For Windows Server 2012 R2, start [All Programs]-[Administrative Tools]-[Server Manager]from the [Start] menu, and install [Web Server (IIS)] from the [Add Role] wizard in [ServerManager].

2. Select the following check box on the [Select Server Roles] dialog box, and performinstallation.

• [Web Server] - [Common HTTP Features] - [Static Content]

• [Web Server] - [Application Development] -[ASP.NET 4.5]

• [Management Tools] - [IIS Management Console]

• [Management Tools] - [IIS 6 Metabase Compatibility]

2.2.3 Installing .Net Framework 3.5 Service Pack1For Windows Server 2008 R2, start [All Programs]-[Administrative Tools]-[Server Manager] fromthe [Start] menu, and install [.NET Framework 3.5.1 Features] from [Add features] in [ServerManager].

Install Windows Server 2012 and Windows Server 2012 R2 following the instructions at the URLbelow.


11

http://support.microsoft.com/kb/2734782/en-us

2.2.4 Installing .Net Framework 4.0Note

For Windows Server 2012/Windows Server 2012 R2, this operation is not required because it is installed asstandard.

Execute the following command on the command prompt to start the installer, and performinstallation by following the wizard.

> <Install DVD>:\ssc\dotNet Framework40\Windows6.0-KB942288-v2-x64.msu

> <Install DVD>:\ssc\dotNet Framework40\Windows6.0-KB942288-v2-x86.msu

2.2.5 Installing .Net Framework 4.5.2Note

This work procedure is necessary when installing .Net Framework 4.5, 4.5.1, or 4.5.2.

1. Execute the following command on the command prompt to start the installer, and performinstallation by following the wizard.

> <Install DVD>:\ssc\dotNet Framework452\NDP452-KB2901907-x86-x64-AllOS-ENU.exe

Installation is not necessary when the Net Framework 4.5.2 maintenance screen is displayed.Select Cancel.

2.2.6 Installing SQL ServerIn Virtual DataCenter Automation, SQL Server is used on the Global Management Server,Management Server, and VM Monitoring Server. As the product types of SQL Server, ExpressEdition, Standard Edition, and Enterprise Edition can be used. If Express Edition is used, a clusterenvironment cannot be built (an upgrade from Express Edition to Standard Edition or EnterpriseEdition is required). This section describes how to install SQL Server Enterprise Edition.

When the DBMS is separately used as a server, install SQL Server 2014 on the DBMS servermachine by the following procedure. The SQL Server 2014 client tools must be installed on themachine on which the Global Management Server, Management Server, and VM Monitoring Serverare installed. If the DBMS is not separately used as a server, the SQL Server 2014 client tools do nothave to be installed.

• Installing SQL Server 2014

Check the name of the instance created for each server by referring to table: [Instance name tocreate] below. For the Management Server, perform this installation operation three times foreach instance.

1. Execute Setup.exe to start the SQL Server 2014 installer.

2. On the [SQL Server Installation Center] screen, click [New SQL Server stand-aloneinstallation or add features to an existing installation] in [Install].

3. On the [Product Key] screen, enter the product key, and click [Next].


12

http://support.microsoft.com/kb/2734782/en-us

4. On the [License Terms] screen, select the [I accept the license terms.] check box, andclick [Next]

5. On the [Product Update] screen, a search for the update program starts. Click [Next].

6. On the [Install Rules] screen, click [Next].

7. On the [Setup Role] screen, click [Next].

8. On the [Feature Selection] screen, select the necessary function indicated on thefollowing, and click [Next].

Table 2-1 Selection of function

Function to select Instance name

FWCMDB SSCCMDB DPMDBI

DatabaseEngine service Select Select Select

SQL Server Replication Do not select Do not select Select

9. On the [Instance Configuration] screen, select the [Named instance:] radio button, enteran appropriate instance name in the text box, and click [Next].Enter it by referring totable: [Instance name to create] below.

Table 2-2 Instance name to create

Machine type Instance name to create

FWCMDB*1 SSCCMDB DPMDBI

Global ManagementServer

Create Do not create Do not create

Management Server Create Create Create

VM Monitoring Server Create Do not create Do not create

*1 To install the DBMS on a separate server, create only one FWCMDB instance on theserver on which the DBMS is installed. It does not have to be created on the GlobalManagement Server, Management Server, or VM Monitoring Server.

10. On the [Server Configuration] screen, click [Next].

11. On the [Database Engine Configuration] screen, set the following.

a. Select the [Mixed Mode (SQL Server authentication and Windows authentication)]radio button in [Authentication Mode], and enter the password in [Enter Password:]and [Confirm Password:] text boxes.

b. In [Specify SQL Server administrators], click [Add Current User].Click [Next].

12. On the [Ready to Install] screen, click [Install].

13. When the installation is complete, the [Complete] screen is displayed. Click [Close].

14. Close the SQLServer Install Center.

15. After installation of SQL Server, a restart may be requested. In that case, restart thecomputer.

• Setting the logon user of the SQL Server 2014 services

Perform setting of the required instances by referring to table: [Log on user of the SQL ServerServices] below.


13

Table 2-3 Log on user of the SQL Server services

Instance name


Logon User Local System NT Service\MSSQL$SSCCMDB

(Default value))

NT Service\MSSQL$DPMDBI

(Default value))

1. Start the SQL Server Configuration Manager.

2. Click [SQL Server Services] on the left pane, and double-click [SQL Server (InstanceName)] displayed on the right pane.

The [SQL Server (Instance Name) Properties] screen is displayed.

3. On the [Log On] tab, select the [Built-in account:] radio button, select an appropriate userfrom the drop-down list, and click [OK]. Select it by referring to "Log on user of the SQLServer services" below.

4. Click [Yes] in the message displayed.

5. Click [Restart]. When restart processing is complete, click [OK] to finish the SQL ServerConfiguration Manager.

• Setting the network configuration of SQL Server 2014

Perform setting of the required instances by referring to table: [SQL Server NetworkConfiguration] below.

Table 2-4 SQL Server network configuration

Protocol name Instance name


Shared memory -*1 Enabled Enabled

Named pipe Enabled -*1 -*1

TCP/IP Enabled -*1 -*1

*1 "-" indicates it can be enabled or disabled. Leave it as the default value.

1. Start the SQL Server Configuration Manager.

2. Click [SQL Server Network Configuration] on the left pane, select [Protocols for InstanceName] displayed, and change the state of an appropriate protocol displayed on the rightpane. Change it by referring to "SQL Server network configuration" below.

• Adding a fixed server role member of SQL Server 2014

Perform setting of the required instances by referring to table: [Adding a fixed server rolemember] below.

Table 2-5 Adding a fixed server role member

Instance name


Adding a fixed server rolemember

Do not add Add Add

1. Open the command prompt.


14

2. Execute the following commands.

> sqlcmd.exe -E -S “.\Instance Name”1> exec master..sp_addsrvrolemember @loginame =N'NT AUTHORITY\SYSTEM', @rolename = N'sysadmin'2> go1> exit

3. When the operation above is complete, restart each of the instances by the followingprocedure.

a. Select [SQL Server Services] on the left pane, and double-click [SQL Server(Instance Name)] displayed on the right pane.

The [SQL Server (Instance Name) Properties] screen is displayed.

b. Click [Restart]. When restart processing is complete, click [OK] to finish the SQLServer Configuration Manager.

• Changing the startup type of the SQL Server Browser service

Set the startup type of the SQL Server Browser service to [Auto] and start the service.

1. Select [Control Panel] -> [Administrative Tools] -> [Service]. If the startup type of theSQL Server Browser service is not [Auto], change it to [Auto].

2. If the SQL Server Browser service is not active, start it.

• Installing the SQL Server 2014 client tools

This section describes the installation method for the Express Edition.

1. Execute SQLManagementStudio_x64_JPN.exe to start the installer.

2. Click [New SQL Server stand-alone installation or add features to an existinginstallation].

3. On the [Product Updates] screen, click [Next] after the search for the update program iscomplete.

4. On the [Install Setup Files] screen, the next screen is displayed automatically afterinstallation of SQL Server setup is complete.

5. On the [Setup Support Rules] screen, the next screen is displayed automatically after therule check is complete.

6. On the [Installation Type] screen, select the [Perform a new installation of SQL Server2012] radio button, and click [Next].

7. On the [License Terms] screen, select the [I accept the license terms.] check box, andclick [Next].

8. On the [Feature Selection] screen, select [Management Tools - Basic], and click [Next]. Ifthe SQL Server 2014 client tools have been installed on the server, [Management Tools -Basic] is grayed out and selected. In this case, installation of the SQL Server client toolsis not required. Cancel the installation.

9. On the [Installation Rules] and [Disk Space Requirements] screens, the next screen isdisplayed automatically.

10. On the [Error Reporting] screen, click [Next].

11. On the [Installation Configuration Rules] screen, the next screen is displayedautomatically after the rule check is complete.


15

12. On the [Installation Progress] screen, the [Complete] screen is displayed after installationof the management tool is complete. Click [Close].

13. Close the SQLServer Install Center.

2.2.7 Installing the Services for NFSFor Windows Server 2012 R2, start [All Programs]-[Administrative Tools]-[Server Manager] fromthe [Start] menu, and install [File Services] from the [Add Role and Function] wizard in [ServerManager]. In [Select Role Services], select [Network File System Server].

For Windows Server 2008 R2, start [All Programs]-[Administrative Tools]-[Server Manager] fromthe [Start] menu, and install [File Services] from the [Add Role] wizard in [Server Manager]. In[Select Role Services], select [Services for Network File System].

* If the file service has been installed, select [File Services] on the left pane of [Server Manager], andselect [Services for Network File System] from the [Add role services] wizard.

2.2.8 Installing VMware vSphere PowerCLINote

Using VMware for a virtual foundation, and when using the template sharing function, it's necessary.

Install VMware vSphere PowerCLI by downloading it from the URL below.

https://www.vmware.com/support/developer/PowerCLI/index.html

* Registration to My VMware is nedded to download VMware vSphere PowerCLI.

For details about the system requirements and installation method, refer to the VMware documents,and perform installation.

2.2.9 Installing NEC ESMPRO AgentInstall with EXPRESSBUILDER (included in the NEC Express series).

2.2.10 Installing NEC ESMPRO Agent for VMWarePurchase UL1032-102 NEC ESMPRO Agent for VMware separately.

2.3 Installing the components of GlobalManagement Server

The subsequent sections describe how to install the components of the Virtual DataCenterAutomation Global Management Server.

NoteWhen installing the components of Global Management Server by upgrading, or performing installationagain when installation is interrupted, stop the services in the order below in advance.After installation, start the services manually.

• MasterScope UMF Operations Web Service__vDCGMProxy_n(The "n" at the end digit should be 1 or greater number. The number varies depending on theinstallation environment.)

• MasterScope UMF Operations Manager_101


16

https://www.vmware.com/support/developer/PowerCLI/index.html

2.3.1 Components Installed on the Global Management ServerFor the system requirements of the Global Management Server, see Chapter 6. OperatingEnvironments/System Requirements in Virtual DataCenter Automation First Step Guide.

The components installed on the Global Management Server are as follows.

• MasterScope MISSION CRITICAL OPERATIONS Manager

• MasterScope vDC Automation Manager

• MasterScope AsRiCommon Manager

• MasterScope AssetSuite Manager

• MasterScope vDC Automation WebService View

• MasterScope vDC Automation Service Governor

• Application Server*1*2

• MasterScope vDC Automation Portal*1 Java 8u72 and Tomcat 8.0.33 will be installed.*2 The log files of Tomcat keep growing and become huge if you do not delete them periodically. So

delete the files on a regular basis.The log files of Tomcat are output to the following folder.<installation folder>\FW\Tomcat\logs

Note<installation 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".

"vdca.log" files placed in the same folder as Tomcat log files rotate. The maximum number of the filesis 100 with the default settings. So you do not have to delete the vdca.log files.

2.3.2 Software Required to be Installed in AdvanceBefore starting installation of the components of the Global Management Server, install the followingsoftware.

• .NET Framework 3.5 Service Pack 1

• .NET Framework 4.0

• SQL Server*1

• SQL Server client tools*1

• Services for NFS*2

*1 When the DBMS is separately used as a server, install SQL Server on the DBMS server, and install theSQL Server client tools on the machine on which the Global Management Server is installed. If theDBMS is not separately used as a server, the SQL Server client tools do not have to be installed.

*2 To construct storage for the software repository with NFS sharing, the NFS service must be installed.

Install it by referring to the procedure in "2.2 Software Required to be Installed in Advance (page10)".


17

2.3.3 Setting up the Windows FirewallIf the Windows Firewall function is enabled in the Global Management Server, the port used by theGlobal Management Server must be opened. Some ports are automatically registered duringinstallation, but some items require manual registration.

For details, see "Appendix C. Network and Protocol (page 183)".

2.3.4 Cautions before Performing InstallationBe sure to exit all applications and Web browsers being used before starting the installation.

2.3.5 Installing the components of Global Management Server1. Insert the vDCA/NWA install DVD into the DVD drive.

2. Execute the following command on the command prompt or Explorer to start the VirtualDataCenter Automation Integrated Installer.

> <Install DVD>:\install\Windows\vDCAInst.exe

3. The installer starts up, and the following screen is displayed.

4. Select [Typical], and click [Next].

The [Selection of Function] screen is displayed.


18

5. Select the [GlobalManager] check box.

Functions other than [VM Monitoring Server] and [Managed Machine] can be installed on theGlobal Management Server. To install them, select the check boxes.

6. Click [Next].

The [Setting of GlobalManager] screen is displayed.

7. Set the setting items as required. Click the setting item and click [Edit], or double-click thesetting item.

The setting screen for the selected setting item opens.

Setting Value

[Install Directory Path] Specify the installation destination folder.The default value is C:\Program Files (x86)\NEC\vDCA\GM


19

Setting ValueSpecify the folder path using up to 55 characters.*1

[Self Hostname] Specify the computer name of the Global Management Server.

The default value is machine name (e.g., MANAGER).*2

[Management Server/Agent Port] Specify the manager port number used to establish a connectionfrom the agent or lower manager.The default value is "12520".

[Viewer Port] Specify the port number on the manager side used forconnection from the Global Management Server Console.The default value is "12521".

[Change Data Directory] Specify "No" (default value).*3

[Data Directory] It can be specified if "Yes" is selected in [Change DataDirectory].*3

[Store Initial Setting Data] It can be specified if "Yes" is selected in [Change DataDirectory].*3

The default value is "Yes".

[Application Server Type] Specify the Application Server type.Only "Tomcat" can be specified in this version.

[Application Server - HTTP Port] Specify the HTTP port number of the Application Server.The default value is "12080".

[Application Server - HTTPS Port] Specify the HTTPS port number of the Application Server.

The default value is "12443".*4

[Tomcat - Management Port] Tomcat - Management Port Specify the Management portnumber of the Tomcat.The default value is "12005".

[Tomcat - AJP/1.3 Port] Specify the AJP/1.3 port number of the Tomcat.The default value is "12009".

[Portal - SQL Server Host Name] Specify the host name of the machine on which the database isinstalled.The default value is "localhost".

[Portal - SQL Server Instance Name] Specify the instance name of the database.Specify the name of the instance created in "2.2.6 InstallingSQL Server (page 12)".The default value is "FWCMDB".

[Portal - SQL Server Port] Specify the port number of the database.The default value is "1433".

[WebService Port] Specify the port number for internal communication with theApplication Server.The default value is "8081".

[Database - Hostname] Specify the host name of the machine on which the database isinstalled.

The default value is "localhost".*5

[Database - Instance Name] Specify the instance name of the database.Specify the name of the instance created in "2.2.6 InstallingSQL Server (page 12)".


20

Setting ValueThe default value is "FWCMDB".*5

[Database - Database Name] Specify the database name. "-" (hyphen) cannot be used.

The default value is "GM_" + computer name.*5*6

[Database - Authentication Type] Specify the type of database authentication of SQL Server.The default value is "Windows authentication".

[Database - Password] Specify the authentication password of the sa user of thedatabase (SQL Server) if [SQL Server Authentication] isselected in [Database - Authentication Type].

*1 Note that [Install Directory Path] and [Data Directory] are not case-sensitive. The followingcharacters cannot be used in [Install Directory Path] /[ Data Directory].\ / : * ? " < > | ; , & ^"\" can be used as a delimiter.

*2 Check that name resolution for [Self Hostname] can be performed from other machinesconnected. It is recommended to specify the fully qualified domain name (e.g.,manager.domain.net.jp) or the IP address. For a cluster configuration, specify the floating IPaddress or virtual host name. For details, see Virtual DataCenter Automation ClusterConstruction Guide. [Self Hostname] cannot be changed after installation. To change them, re-installation is required.

*3 Specify "Yes" to use a cluster configuration. Since this document does not support clusterconfiguration, specify "No". For cluster configuration, see Virtual DataCenter AutomationCluster Constrcution Guide.

*4 In vCenter Server 5.5, port 12443 is used. Change the port number because it affects WebAPI(https) when installing vCenter Server 5.5 in the identical server.

*5 Check it so as not to designate the same host name, instance name, database name ofManagement Server and VM Monitoring Server.

*6 Hyphens in the computer name are omitted.

8. Click [Next].

Connection to the database is checked. If connection to the database can be established, theinstallation confirmation screen is displayed.

Note• If connection to the database cannot be established, you cannot proceed. Review the settings.• If other functions are installed simultaneously, click [Next] to display the setting screens. For

the setting screens, see the procedure for installing the functions.


21

9. Check the details, and click [Start].

10. Click [Yes] on the confirmation message displayed.

Installation starts. When the installation is complete, the installation result screen is displayed.

11. Click [Finish].

12. Restart the server.

13. Perform license registration and setting of the global management server. License registrationis performed after installing the global management server console See "2.4 Installing thecomponents of Global Management Server Console (page 23)". For details on setting of the


22

global management server, see "2.14 Registering and Setting up the Global ManagementServer (page 64)".

2.4 Installing the components of GlobalManagement Server Console

The subsequent sections describe how to install the components of the Virtual DataCenterAutomation Global Management Server Console.

2.4.1 Components installed on the Global Management ServerConsole

The components installed on the Global Management Server Console are as follows.

• MasterScope MISSION CRITICAL OPERATIONS View

• MasterScope vDC Automation View

• MasterScope AsRiCommon View

• MasterScope AssetSuite View


2.4.3 Installing the components of Global Management ServerConsole

1. Insert the vDCA/NWA install DVD into the DVD drive.



3. The installer starts up.



5. Select the [GlobalManager View] check box.

Functions other than [Managed Machine] can be installed on the Global Management ServerConsole. To install them, select the check boxes.

6. Click [Next].

The [Setting of GlobalManager View] screen is displayed.


23

7. Select the required items, and click [Edit] to set a value. For the setting values, see the table inthe following procedure.



Setting Value

[Install Directory Path] Specify the installation destination folder.The default value is C:\Program Files (x86)\NEC\vDCA\GMView

Specify the folder path using up to 55 characters.*1

[GlobalManager Hostname] Specify the IP address or host name of the Global ManagementServer in which [Global Manager] is installed.

[GlobalManager Port] Specify the port number specified in [Viewer Port] in theconfiguration of the Global Management Server in which[Global Manager] is installed.The default value is "12521".

*1 Note that [Install Directory Path] is not case-sensitive. The following characters cannot be usedin [Install Directory Path].\ / : * ? " < > | ; , & ^"\" can be used as a delimiter.

9. Click [Next].

The installation confirmation screen is displayed.


24

NoteIf other functions are installed simultaneously, click [Next] to display the setting screens. For thesetting screens, see the procedure for installing the functions.



Installation starts. When the installation is complete, the installation result screen is displayedwith the installation result.


25

12. Click [Finish].

2.5 Installing the components of ManagementServer

The subsequent sections describe how to install the components to the Virtual DataCenterAutomation Management Server.

Before installing the components by using the Virtual DataCenter Automation Integrated Installer,the following preparations are required.

• Software Required to be Installed in Advance (see "2.5.2 Software Required to be Installed inAdvance (page 27)").

• DHCP Server Configuration

• Setting up the Windows Firewall

• Cautions regarding the NEC ESMPRO Manager user group setting

• Cautions regarding installation of the Virtual DataCenter Automation Management Server

NoteWhen installing the components of Management Server by upgrading, or performing installation again wheninstallation is interrupted, stop the services in the order below in advance.After installation, start the services manually.

• MasterScope UMF Operations Web Service__vDCMoMProxy_n(The "n" at the end digit should be 1 or greater number. The number varies depending on theinstallation environment.)

• NvPRO ResourceManagerAPI Service• NvPRO Base Manager


26

• MasterScope UMF Operations Manager_102• FTBase service

NoteWhen installing a new management server in an environment in which SigmaSystemCenter manager isinstalled, first update the version of the SigmaSystemCenter manager to 3.5.

2.5.1 Components Installed on the Management ServerFor the system requirements of the Management Server, see Chapter 6. Operating Environments/System Requirements in Virtual DataCenter Automation First Step Guide.

The components installed on the Management Server are as follows.


• MasterScope Network Manager Manager

• MasterScope vDC Automation Manager

• MasterScope vDC Automation WebService View

• MasterScope SigmaSystemCenter Manager

NoteFor distribution and sharing of software / patch in multiple sites, the components for the Managed Machinemust be installed on one of the Management Server which belong to the site that contains GlobalManagement Server.For installation of the components for the Managed Machine, see "2.11.3 Installing the components ofManaged Machine (Windows) (page 51)".

2.5.2 Software Required to be Installed in AdvanceBefore starting installation of the components of the Management Server, install the followingsoftware.



• .NET Framework 4.5.2

• SQL Server*1



• Internet Information Service*1 When the DBMS is separately used as a server, install SQL Server on the DBMS server, and install the

SQL Server client tools on the machine on which the Management Server is installed. If the DBMS isnot separately used as a server, the SQL Server client tools do not have to be installed.However, if a separate server is used for the DBMS and [Other DB] is set in [Database - Database forNetwork Manager] during installation, SQL Server must be installed on the machine on which theManagement Server is installed. When installing SQL Server, make sure that the instance settings(instance name, authentication method, authentication password, etc.) match the instance setting of theDBMS server.If SQL Server is not installed on the machine on which the Management Server is installed, set[Bundled DB] in [Database - Database for Network Manager] during installation.


27

*2 It is necessary for using the VM template sharing function when NFS is used as the communicationprotocol between the file server and management server. It is not necessary if the template sharingfunction is not used or CIFS is used as the communication protocol.To construct storage for the software repository with NFS sharing, the NFS service must be installed.


2.5.3 DHCP Server ConfigurationIf HYPER-V or KVM is used as the virtualization infrastructure server, or if physical serverprovisioning is used, a DHCP server is required in the same network as Virtual DataCenterAutomation.

Prepare the DHCP server before installing the Virtual DataCenter Automation.

The DHCP server can be installed on the same machine as the management server. Multiple DHCPservers can exist within the same network segment.

For the DHCP server, specify gateway and IP pools for all IP subnets to be used as the providermanagement VLAN.

TipFor setup methods and precautions of the DHCP server, see 2.2.1 Network Environment in theDeploymentManager First Step Guide and 1.2.2 Setting UP the DHCP Sever in the DeploymentManagerInstallation Guide.

Note• If not setting the DHCP server, the functions using backing up/restoration of DeploymentManager,

disk replication OS installation, OS clear installation, and VM Provisioning are restricted.• When not using a DC resource, also specify routing for all IP subnets to be used as the provider

management VLAN.

2.5.4 Setting Up the Windows FirewallIf the Windows Firewall function is enabled on the Management Server, the port used by theManagement Server must be opened. Some ports are registered automatically during the installation,while others must be registered manually.


2.5.5 Precautions When Setting NEC ESMPRO Manager UserGroup

When using Windows GUI of ESMPRO/ServerManager, the users must belong to the group knownas "“NEC ESMPRO User Group" for security reasons.

The "NEC ESMPRO User Group" will be determined at the installation of the ESMPRO/ServerManager. The "Administrators" group is specified by default.


28

2.5.6 Precautions When Installing Virtual DataCenterAutomation Management Server

• To install the DeploymentManager management function, check that the network with themanagement LAN is connected.

• Check that the IP address for the OS network connection of the Virtual DataCenter AutomationManagement Server is set to an unchanging IP address instead of automatic acquisition.

• Depending on the operating system, an ephemeral port may cause a conflict between the portused by DeploymentManager and the port used by other services and applications, preventingthe DeploymentManager service from running. For details on how to check and troubleshootephemeral ports, see 2.2 Precautions Regarding System Configuration in theDeploymentManager First Step Guide.

• For the other precautions, see 2.1 Installing DPM Server in the DeploymentManagerInstallation Guide and 2.2 Precautions Regarding System Configuration in theDeploymentManager First Step Guide.


2.5.8 Installing the components of Management Server1. Insert the vDCA/NWA install DVD into the DVD drive.






5. Select the [Management Server] check box.

Functions other than [VM Monitoring Server] and [Managed Machine] can be installed on theManagement Server. To install them, select the check boxes.

6. Click [Next].

The [Setting of Management Server] screen is displayed.


29

7. Set the following required items. Select the setting item name and click [Edit]. Perform settingin the screen displayed.

• [GlobalManager Hostname] (Example: vdca_gm)

8. The following items are required when SigmaSystemCenter is not installed. Select the settingitem name and click [Edit]. Perform setting in the screen displayed.

• [ESMPRO/ServerManager - Administrator Name] (Example: Administrator)

• [ESMPRO/ServerManager - Administrator's Password] (Example: Password)



Setting Value

[Install Directory Path] Specify the installation destination folder.The default value is "C:\Program Files (x86)\NEC\vDCA\MoM".

Specify the folder path by using up to 55 characters.*1

[Self Hostname] Specify the computer name of the Management Server.

The default value is machine name (e.g. MANAGER).*2

[VM Monitoring Server/Agent Port] Specify the port number on the manager side used forconnection from the VM Monitoring Server and agent.The default value is "12520".

[Viewer Port] Specify the port number on the manager side used forconnection from the Management Server Console.The default value is "12521".

[Change Data Directory] The default value is "No".*3


30

Setting Value




[GlobalManager Hostname] Specify the host name of the Global Management Server.*2*4

[GlobalManager Port] Specify the communication port number to connect to theGlobal Management Server.The default value is "12520".





The default value is "FWCMDB".*5

[Database - Database Name] Specify the database name. "-" (hyphen) cannot be used.

The default value is "MoM_" + computer name.*5*6



[Database - Database for NetworkManager]

Select whether to save Network Manager data in the internaldatabase of Network Manager or in the external database ofNetwork Manager (SQL Server as Virtual DataCenterAutomation).

The default value is [Other DB].*7

If SQL Server does not operate on the Management Server,select [Bundled DB].

[Database - Port for Network ManagerDB]

Specify the network port of TCP/IP communication with theinternal database if [Bundled DB] is selected in [Database -Database for Network Manager].The default value is "12630".

[ESMPRO/ServerManager -Administrator Name]

Specify the name of the administrator of ESMPRO Manager.*8

[ESMPRO/ServerManager -Administrator’s Password]

Specify the password of the administrator of NEC ESMPROManager.*8

[DeploymentManager - ManagementServer’s IP Address]

Specify the IP address of the DPM management server.*8*9

*1 Note that [Install Directory Path] and [Data Directory] are not case-sensitive. The followingcharacters cannot be used in [Install Directory Path]/[Data Directory].


31

\ / : * ? " < > | ; , & ^"\" can be used as a delimiter.

*2 Check that name resolution for [Self Hostname] and [GlobalManager Hostname] can beperformed from other machines connected. It is recommended to specify the fully qualifiedformat (FQDN) (e.g., manager.domain.net.jp) or the IP address. For a cluster configuration,specify the floating IP address or virtual host name. For details, see the separate VirtualDataCenter Automation Cluster Construction Guide. [Self Hostname] and [GlobalManagerHostname] cannot be changed after installation. To change them, re-installation is required.

*3 Specify "Yes" to use a cluster configuration. Since this document does not support clusterconfiguration, specify "No". For details of the cluster configuration, see the separate VirtualDataCenter Automation Cluster Construction Guide.

*4 [GlobalManager Hostname] must match the notation in [Self Hostname] of the GlobalManagement Server. If [Self Hostname] of the Global Management Server is omitted, the hostname of the global management server is the computer name.The host name of the global management server can be confirmed in HostName Properties inthe [SelfNode] section of C:\Program C:\Program Files (x86)\NEC\vDCA\GM\FW\Manager\sg\SysMonMgr.ini.

*5 Do not specify the same host name, instance name, and database name as the names used in theGlobal Management server and VM monitoring server.

*6 Hyphens in the computer name are omitted.*7 If a separate server is used for the DBMS, select [Bundled DB].*8 This can be specified when SigmaSystemCenter is not installed.*9 If it is omitted, all the LAN boards on the Management Server will be used by the DPM server.

10. Click [Next].


Note• If connection to the database cannot be established, you cannot proceed. Review the settings.• If other functions are installed simultaneously, click [Next] to display the setting screens. For

the setting screens, see the procedure for installing the functions.


32



Installation starts.

NoteIf [Bundled DB] is selected in the setting item [Database - Database for Network Manager], thefollowing dialog box is displayed during installation. Click [Yes].

13. When the installation is complete, the installation result screen is displayed with theinstallation result.


33

If SigmaSystemCenter is already installed, "Skipped" is displayed as the result of installingSigmaSystemCenter.

14. Click [Finish].

15. If the restart message is displayed, click [OK].


17. Perform license registration and setting of the Management Server. A license is registered afterinstallation of the Management Server console. See "2.6 Installing the components ofManagement Server Console (page 34)". For setting the Management Server, see"2.15 Registering and Setting up the Management Server (page 79)".

2.6 Installing the components of ManagementServer Console

The subsequent sections describe how to install the components of the Virtual DataCenterAutomation Management Server Console.

2.6.1 Components Installed on the Management ServerConsole

The components installed on the Management Server Console are as follows.


• MasterScope Network Manager View



34


2.6.3 Installing the components of Management ServerConsole







5. Select the [Management Server View] check box.

Functions other than [Managed Machine] can be installed on the Management Server Console.To install other functions, select the check boxes.

6. Click [Next].

The [Setting of Management Server View] screen is displayed.

7. Select the required items, and click [Edit] to set a value. For the setting values, see the table inthe following procedure.

Multiple components of Management Server Console can be installed by clicking the [Add]button. To delete a new [Management Server View] from the list, click the [Delete] button.


35

8. Set the setting items as required. Click the setting item and click [Edit], or double-click thesetting item. To install multiple components of Management Server Consoles, set the settingitems for each installation target.


Setting Value

[Install Directory Path] Specify the installation destination folder.The default value is "C:\Program Files (x86)\NEC\vDCA\MoMView".


[Management Server Hostname] Specify the IP address or host name of the ManagementServer.*2

[Management Server Port] Specify the port number specified in [Viewer Port] in theconfiguration of the Management Server.The default value is "12521".

[Service Identifier] Identifier to distinguish multiple consoles installed*3

*1 Note that the folder path is not treated as case-sensitive at the installation destination folder.The following characters cannot be used for an installation destination folder:\ / : * ? " < > | ; , & ^"\" can be used as a delimiter.

*2 Check that name resolution can be performed if a host name is specified.*3 Note that the service identifier is not treated as case-sensitive.

The following characters cannot be used for service identifiers.b!"#$%&'()*+,./:;<=>?@[\]^`{|}~* "b" indicates a 1-byte space.

9. Click [Next].




36




12. Click [Finish].


37

2.7 Installing the components of VM MonitoringServer

The subsequent sections describe how to install the components on the Virtual DataCenterAutomation VM Monitoring Server.

NoteWhen installing the components of VM Monitoring Server by upgrading, or performing installation againwhen installation is interrupted, stop the services in the order below in advance.After installation, start the services manually.

• MasterScope UMF Operations Web Service__vDCRMProxy_n(The "n" at the end digit should be 1 or greater number. The number varies depending on theinstallation environment.)


2.7.1 Components Installed on the VM monitoring ServerFor the system requirements of the VM Monitoring Server, see Chapter 6. Operating Environments/System Requirements in Virtual DataCenter Automation First Step Guide.

The components installed on the VM Monitoring Server are as follows.


• MasterScope Virtual DataCenter Automation Manager

• MasterScope Virtual DataCenter Automation WebService View

2.7.2 Software Required to be Installed in AdvanceBefore starting installation of the components of the VM Monitoring Server, install the followingsoftware.



• SQL Server*1



*1 When the DBMS is separately used as a server, install SQL Server on the DBMS server, and install theSQL Server client tools on the machine on which the VM Monitoring Server is installed. If the DBMSis not separately used as a server, the SQL Server client tools do not have to be installed.

*2 To construct storage for the software repository with NFS sharing, the NFS service must be installed.


2.7.3 Setting up the Windows FirewallIf the Windows Firewall function is enabled in the VM Monitoring Server, the port used by the VMMonitoring Server must be opened. Some ports are automatically registered during installation, butsome items require manual registration.


38



2.7.5 Installing the components of VM Monitoring Server1. Insert the vDCA/NWA install DVD into the DVD drive.






5. Select the [VM Monitoring Server] check box.

Functions other than [GlobalManager], [Management Server] and [Managed Machine] can beinstalled on the VM the VM Monitoring Server. To install them, select the check boxes.

6. Click [Next].

The [Setting of VM Monitoring Server] screen is displayed.

7. Select the required items, and click [Edit] to set a value. For the setting values, see the table bythe following procedure.



39


Setting Value

[Install Directory Path] Specify the installation destination folder.The default value is "C:\Program Files (x86)\NEC\vDCA\RM".


[Self Hostname] Specify the computer name of the VM Monitoring Server.

The default value is machine name (e.g., MANAGER).*2

[Agent Port] Specify the port number on the manager side used forconnection from the Managed Machine.The default value is "12520".

[Viewer Port] Specify the port number on the manager side used forconnection from the VM Monitoring Server Console.The default value is "12521".

[Change Data Directory] Specify "No" (default value).*3




[Management Server Hostname] Specify the host name of the Management Server.*2*4

[Management Server Port] Specify the communication port number to connect to theManagement Server.The default value is "12520".





The default value is "FWCMDB".*5

[Database - Database Name] Specify the instance name of the database. "-" (hyphen) cannotbe used.

The default value is "RM_" + computer name.*5*6



*1 Note that [Install Directory Path] and [Data Directory] are not case-sensitive. The followingcharacters cannot be used in [Install Directory Path] /[Data Directory].\ / : * ? " < > | ; , & ^


40

"\" can be used as a delimiter.*2 Check that name resolution can be performed for [Self Hostname] and [Management Server

Hostname]. It is recommended to specify the fully qualified format (FQDN) (e.g.,manager.domain.net.jp) or the IP address. For a cluster configuration, specify the floating IPaddress or virtual host name. For details, see the separate Virtual DataCenter AutomationCluster Construction Guide.

*3 Specify "Yes" to use a cluster configuration. Since this document does not support clusterconfiguration, specify "No". For details of the cluster configuration, see the separateVirtualDataCenter Automation Cluster Construction Guide.

*4 [Management Server Hostname] must match the notation in [Self Hostname] of the GlobalManagement Server. If [Self Hostname] of the Global Management Server is omitted, the hostname of the global management server is the computer name.The host name of the global management server can be confirmed in HostName Properties inthe [SelfNode] section of C:\Program Files (x86)\NEC\vDCA\MoM\FW\Manager\sg\SysMonMgr.ini.

*5 Do not specify the same host name, instance name, and database name as the names used in theGlobal Management server and Management server.

*6 Hyphens in the computer name are omitted.

9. Click [Next].


Note• If connection to the database cannot be established, you cannot proceed. Review the settings.




41



13. Click [Finish].


15. Perform license registration and setting of the VM Monitoring Server. A license is registeredafter installation of the VM Monitoring Server console. See "2.8 Installing the components ofVM Monitoring Server Console (page 42)". For setting the VM Monitoring Server, see"2.16 Registering and Setting up the VM Monitoring Server (page 85)".

2.8 Installing the components of VM MonitoringServer Console

The subsequent sections describe how to install the components of the Virtual DataCenterAutomation VM Monitoring Server Console.

2.8.1 Components Installed on the VM monitoring ServerConsole

The components installed on the VM Monitoring Server Console are as follows.




42

2.8.3 Installing the components of VM Monitoring ServerConsole







5. Select the [VM Monitoring Server View] check box.

Functions other than [Managed Machine] can be installed on the VM Monitoring Server View.To install other functions, select the check boxes.

6. Click [Next].

The [Setting of VM Monitoring Server View] screen is displayed.


Multiple components of VM Monitoring Server Console can be installed by clicking the [Add]button. To delete a new [VM Monitoring Server View] from the list, click the [Delete] button.

8. Set the setting items as required. Click the setting item and click [Edit], or double-click thesetting item. To install multiple VM Monitoring Server Consoles, set the setting items for eachinstallation target.



43

Setting Value

[Install Directory Path] Specify the installation destination folder.The default value is "C:\Program Files (x86)\NEC\vDCA\RMView".


[VM Monitoring Server Hostname] Specify the IP address or host name of the VM MonitoringServer.*2

[VM Monitoring Server Port] Specify the port number specified in [Viewer Port] in theconfiguration of the VM Monitoring Server.The default value is "12521".

[Service Identifier] Identifier to distinguish multiple consoles installed.*3


*2 Check that name resolution can be performed if a host name is specified.*3 Note that the service identifier is not treated as case-sensitive.

The following characters cannot be used for service identifiers.b!"#$%&'()*+,./:;<=>?@[\]^`{|}~* "b" indicates a 1-byte space.

9. Click [Next].




44





13. Click [Finish].


45

2.9 Installing the components of ID ManagementServer

The subsequent sections describe how to install the components of the Virtual DataCenterAutomation ID Management Server.

2.9.1 Components Installed on the ID Management ServerFor the system requirements of the ID Management Server, see Chapter 6. Operating Environments/System Requirements in Virtual DataCenter Automation First Step Guide.

The components installed when installing the ID Management Server are as follows.

• MasterScope Identity Manager

2.9.2 Software Required to be Installed in AdvanceFor ID Management Server, Microsoft Visual C++ 2008 Redistributable Package (x64) is required.

1. Obtaining the installation program

Download the Microsoft Visual C++ 2008 Redistributable Package (x64) from Microsoft'sdownload website.

2. Executing the installation program

Execute the downloaded installation program.

In addition, in the case of Windows Server 2012 R2, installing KB2919355, the update program forWindows Server 2012 R2 is required. Follow the descriptions below to install the program.

https://support.microsoft.com/en-us/kb/2919355/ja

2.9.3 Setting up the Windows FirewallIf the Windows Firewall function is enabled in the ID Management Server, the port used by the IDManagement Server must be opened. Some ports are automatically registered during installation, butsome items require manual registration.



To install the components of ID Management Server on the machine using the remote desktopservice, perform installation by the following method (Windows Server 2008 R2).


2. Select [Control Panel (C)] - [Install Application on Remote Desktop Server] from the [Start]menu.

3. The [Install Program From Floppy Disk or CD-ROM] screen is displayed. Click [Next>].

4. The [Run Install Program] screen is displayed. Specify the following installer of VirtualDataCenter Automation, and click [Next >].

<Install DVD>:\install\Windows\vDCAInst.exeThe install wizard of Virtual DataCenter Automation starts up.


46

https://support.microsoft.com/en-us/kb/2919355/ja

5. Subsequently, perform installation in the same procedure as in the normal conditions.

To upgrade the ID management server in an environment in which the ID management server(MasterScope Identity Manager) is already installed, follow the procedure described in"4.7 Upgrading the ID Management Server (page 126)".

2.9.5 Installing the components of ID Management Server1. Insert the vDCA/NWA install DVD into the DVD drive.






5. Select the [ID Management Server] check box.

Functions other than [Managed Machine] can be installed on the ID Management Server. Toinstall other functions, select the check boxes.

6. Click [Next>].

The [Setting of ID Management Server] screen is displayed.




47

Setting Value

[Install Directory Path] Specify the installation destination folder.The default value is "C:\Program Files (x86)\NEC\vDCA\SM".


[Shutdown Port] Specify the MasterScope Identity Manager shutdown port.The default value is "12636".

[Web Monitoring Port (HTTP)] Specify the MasterScope Identity Manager Web screen portnumber.The default value is "12637".

[Web Monitoring Port (AJP)] Specify the MasterScope Identity Manager Web screen portnumber.The default value is "12638".

[Web Monitoring Port (HTTPS)] Specify the MasterScope Identity Manager Web screen (SSL)port number.The default value is "12639".


8. Click [Next].




48




11. Click [Finish].

12. Perform setting of the ID Management Server. See "2.18 Registering and Setting up the IDManagement Server (page 92)".

NoteIf installation of the components of ID Management Server fails, perform re-installation of the IDManagement Server according to the procedure in "6.2.7 Uninstalling the components of ID ManagementServer (page 165)" before performing installation of the ID Management Server again.

2.10 Installing the components of ManagedMachine

The subsequent sections describe how to install the components to the Managed Machine.

The components installed on each of the virtualization infrastructures are described.

Note• The component indicated as "Option" in tables, it is not essential in the function range used by Virtual

DataCenter Automation. Install it to use the specific function.• Install the DPM client and MISSION CRITICAL OPERATIONS agent using the Virtual DataCenter

Automation Integrated Installer.


49

2.10.1 VMWare ESXi / ESX Virtualization InfrastructureTo use the VMWare ESXi and VMWare ESX virtualization infrastructures, install the followingcomponents.

Managed machine NEC ESMPRO Agent DPM client MISSION CRITICALOPERATIONS agent

VMware ESXvirtualization infrastructure

Option Option Not required

VMware ESXivirtualization infrastructure

Not required Not required Not required

Windows ManagedMachine (physical/virtualmachine)

Option Required Required

Linux Managed Machine(physical/virtual machine)


2.10.2 Hyper-V Virtualization InfrastructureTo use the Hyper-V virtualization infrastructure, install the following components.


Hyper-V virtualizationinfrastructure

Option Option Not required

Windows ManagedMachine (physical/virtualmachine)


2.10.3 KVM Virtualization InfrastructureTo use the KVM virtualization infrastructure, install the following components.


KVM virtualizationinfrastructure

Required Required Not required

Linux Managed Machine(physical/virtual machine)


2.11 Installing the components of ManagedMachine (Windows)2.11.1 Software Required to be Installed in Advance

Before starting installation of the components of the Managed Machine, install the followingsoftware as required.

• NEC ESMPRO Agent



50


2.11.3 Installing the components of Managed Machine(Windows)







5. Select the [Managed machine] check box.

6. Click [Next].

The [Setting of Managed machine] screen is displayed.

In some environments, installation of the "Microsoft Visual C++ 2005 SP1 redistributablepackage (x86)" may be required. Install the "Microsoft Visual C++ 2005 SP1 redistributablepackage (x86)" according to the screen.


51




Setting Value

[Install Directory Path] Specify the installation destination folder.The default value is "C:\Program Files (x86)\NEC\vDCA\Agent".


[Template/Image] Specify the machine type of the managed machine.The default value is "Yes". Specify "Yes" to create a virtualmachine template.

[Self Hostname] Specify the computer name of the Managed Machine.

The default value is machine name (e.g., AGENT).*2*3

If you select "No" in [Template/Image], __UUID isautomatically added to the end on new installation. The UUIDvalue can be checked on the [installation confirmation screen].

[Manager Hostname] Specify the IP address or host name of the upper-levelmanager.*2*3

[Manager Port] Specify the port number specified in [Management Server/Agent Port] in a global management server configuration, [VMMonitoring Server/Agent Port] in a management serverconfiguration, and [Agent Port] in a VM monitoring serverupper-level manager configuration.The default value is "12520".

[Port for Agent Internal Communication] Specify the port number for the agent internal communication.


52

Setting ValueThe default value is "25570".

[Tenant ID] Specify the tenant ID of the tenant to which the managedmachine will belong.*3

[Start Service] After a new installation, specify whether to start the service ofthe MISSION CRITICAL OPERATIONS agent (MasterScopeUMF Operations Agent_104).If "No" is selected in [Template/Image], the default value is"Yes".*3*4

[Install DeploymentManager Client] Specify whether to install the DeploymentManager client.The default value is "Yes" (Install).

[DeploymentManager - ManagementServer’s IP Address]

Specify the IP address (xxx.xxx.xxx.xxx format) of theDeploymentManager management server.*5*6

*1 Note that [Install Directory Path] and [Data Directory] are not case-sensitive. The followingcharacters cannot be used in [Install Directory Path]/[Data Directory].\ / : * ? " < > | ; , & ^"\" can be used as a delimiter.

*2 Check that name resolution can be performed for [Self Hostname] and [Manager Hostname]. Itis recommended to specify the fully qualified format (FQDN) (e.g., manager.domain.net.jp) orthe IP address.

*3 This can be specified if "No" is selected in [Template/Image].*4 This setting is disabled for overwrite install. The service state before overwrite install is

maintained.*5 If it is omitted, a management server is automatically searched for after completion of

installation.*6 This can be specified if "Yes" is selected in [Install DeploymentManager Client].

9. Click [Next].



53





13. Click [Finish].


54

14. Perform setting of the Managed Machine. See "2.19 Setting up the Managed Machine (page94)".

2.12 Installing the components of ManagedMachine (Linux)2.12.1 Software Required to be Installed in Advance

Before starting installation of the components of the Managed Machine, install the followingsoftware as required.

• NEC ESMPRO Agent


NoteInstall some required packages and libraries by referring to the 6.5.3. Managed Guest OS in VirtualDataCenter Automation First Step Guide. If the required package or library is not installed, it does not workproperly.

2.12.2 Cautions before Performing InstallationDepending on the environment, the files in the vDCA/NWA install DVD may not be executed due tothe execution right.

In this case, execute the following commands to copy the fw/Linux directory and Install/Linuxdirectory of the vDCA/NWA install DVD on a directory on the hard disk, execute the chmodcommand to give the execution right of all the files, and start install/Linux/vDCAInst.sh.

# mkdir -p /tmp/media# cd /mnt/dvd# tar cvf - ./fw/Linux | (cd /tmp/media; tar vxf -)# tar cvf - ./install/Linux | (cd /tmp/media; tar vxf -)# tar cvf - ./ssc | (cd /tmp/media; tar vxf -)# cd /tmp/media# chmod 755 -R .# cd ./install/Linux# ./vDCAInst.sh

2.12.3 Installing the components of Managed Machine (Linux)The procedure for installing the components of the Managed Machine (Linux) is described below.

1. Log in to the system as user root.


3. Execute the following command to mount the DVD.

In this example, the mount point is "mnt/dvd".

# mount /mnt/dvd

4. Change the current directory.


55

# cd /mnt/dvd/install/Linux

5. Execute vDCAInst.sh.

# ./vDCAInst.sh

6. The Virtual DataCenter Automation Integrated Installer starts up, and the following screen isdisplayed.

NoteIf the installation screen is unstable, set the environment variable TERM to vt100, and start theinstaller again. Expand the terminal display size as needed.

*************************************MasterScope Installer*************************************

Welcome to MasterScope installer.

1. Typical : installs all products necessary to the function typeof MasterScope Virtual DataCenter Automation you select.(Recommendation)

2. Custom : allows you to install the necessary products to thefunction type of MasterScope Virtual DataCenter Automation separately.

Please select the operation.(1:Typical 2:Custom q:quit program):

Enter 1[Enter].

(1:Typical 2:Custom q:quit program):1

7. Subsequently, the following screen of the Virtual DataCenter Automation Integrated Installeris displayed.

*************************************Welcome to MasterScope Installer !!*************************************

This program will install/uninstall products.

1. Install

Please select the operation.(1:install q:quit program):

Enter 1[Enter].

(1:install q:quit program):1

8. A list of components that can be installed is displayed.


56

--------Products--------

1 [ ] MasterScope Virtual DataCenter Managed machine components 3.0.0.0

--------------------------------------------Please select product(s) by entering numbers separated by commas.[Example: 1, 3, 4](b:back q:quit program):

Select MasterScope Virtual DataCenter Managed machine components 3.0.0.0 as shownbelow.

(b:back q:quit program):1

9. The confirmation screen of the components to be installed is displayed.

------------Confirmation------------

1 [*] MasterScope Virtual DataCenter Managed machine components 3.0.0.0

--------------------------------------------These product(s) will be installed, OK to continue?(default:y y:yes n:no q:quit program):

Enter y[Enter] to continue.

(default:y y:yes n:no q:quit program):y

10. The configuration setting screen of the components to be installed is displayed.

---------------------Installation settings---------------------

Other(*)1 MasterScope Virtual DataCenter Managed machine components 3.0.0.0 2 New Product

--------------------------------------------(*) marked products or services objects require specific settings beforeinstallation.--------------------------------------------Please select operation to perform from following commands.[Example: 's1' configure settings for first service listed above.]

(r[n.n]:remove s[n]:setting v[n]:view c:clear b:back q:quit program):

Enter [s1] to perform setting of [Agent]-[Service1].


57

(r[n.n]:remove s[n]:setting v[n]:view c:clear b:back q:quit program):s1

11. You are asked to enter for each setting item. Perform the following settings.

Setting Value

Install directory path Specify the installation destination directory in the full path.The default value is "/opt/NEC/vDCA/Agent".

Specify the directory path using up to 123 characters.*1

Template/Image Specify the machine type of the managed machine.The default value is "[y]" (Yes). Specify "Yes" to create a virtualmachine template.

Self hostname Specify the computer name of the Managed Machine. If it isomitted, a host name (e.g., agent.domain.net.jp) is automaticallyset.*2*3

If the number of specified characters is 26 or less, __UUID isautomatically added to the end on new installation. The UUIDvalue can be checked on the [Confirmation screen].

Manager hostname Specify the IP address or host name of the upper-levelmanager.*2*3

Manager port Specify the port number specified in [Management Server/Agent Port] in a global management server configuration, [VMMonitoring Server/Agent Port] in a management serverconfiguration, and [Agent Port] in a VM monitoring serverupper-level manager configuration.The default value is "12520".

Port for Agent Internal Communication Specify the port number for the agent internal communication.The default value is "25570".

Tenant ID Specify the tenant ID of the tenant to which the managedmachine will belong.*3

Start service Specify whether to start the [MasterScope MISSIONCRITICAL OPERATIONS Agent] and [MasterScopeAsRiCommon Agent] services (MasterScope UMF OperationsAgent_104) on new installation.

The default value is "[y]" (Yes).*3*4

(Optional) Install DPM Client Specify whether to install the DeploymentManager client.The default value is "[y]" (Yes).

(Optional) IP address of the DPMmanagement server

Specify the IP address (xxx.xxx.xxx.xxx format) of theDeploymentManager management server.*5*6

*1 Do not enter multi-byte characters such as Japanese in [Install directory path]. The followingcharacters can be used in addition to the delimiter "/".One-byte alphanumeric characters . _ - + ,

*2 Check that name resolution can be performed for [Self hostname] and [Manager hostname]. Itis recommended to specify the fully qualified format (FQDN) (e.g., manager.domain.net.jp) orthe IP address.

*3 The entry screen is not displayed if [y] is specified in [Template/Image].*4 This setting is disabled for overwrite install. The service state before overwrite install is

maintained.


58

*5 If it is omitted, a management server is automatically searched for after completion ofinstallation.

*6 The entry screen is not displayed if [n] is specified in [(Optional) Install DPM Client].

12. When all the setting items have been input, the settings are displayed.

If the number of characters specified in [Self hostname] is 26 or less, __UUID is automaticallyadded.

------------Confirmation------------Install directory path: /opt/NEC/vDCA/AgentTemplate/Image: NoSelf hostname: redhat56.localdomain__UUIDManager hostname: <Manager Host Name>Manager port: 12520Port for Agent Internal Communication: 25570Tenant ID: <tenant ID>Start service: Yes(Optional) Install DPM Client: Yes(Optional) IP address of the DPM management server:

--------------------------------------------Are these settings correct?(default:y y:yes n:no q:quit program):

Check that the settings are OK, and enter y[Enter].


13. The configuration setting screen of the components to be installed is displayed again.

Enter e[Enter].

(a[n]:add r[n.n]:remove s[n]:setting v[n]:view c:clear b:back e:execute q:quit program):e

14. The [Final confirmation] screen is displayed.

------------------Final confirmation------------------

Other 1 MasterScope Virtual DataCenter Managed machine components 3.0.0.0

-------------------------------------------Is it OK to start installation?(default:y y:yes n:no q:quit program):

Enter y[Enter].



59

15. The installation status is displayed, and the installation result is displayed at the end. Checkthat no error has occurred.

MasterScope Virtual DataCenter Managed machine components 3.0.0.0 Preparing for Installation (1/1)MasterScope Virtual DataCenter Managed machine components 3.0.0.0 Installation in progress (1/1)Check rcfile

=============================================================Installation of MasterScope MISSION CRITICAL OPERATIONS Agent was successful.Installation of MasterScope AsRiCommon Agent was successful.Installation of DeploymentManager Client was successful.=============================================================

MasterScope Virtual DataCenter Managed machine components 3.0.0.0 was successfully installed (1/1)

-------------------Installation result-------------------1 MasterScope Virtual DataCenter Managed machine components 3.0.0.0 (Success)-------------------Success:1, Failure:0

NoteWhen an installation error occurs, "Installation of <Product Name> failed. [ErrorNumber]" is displayed in a message during installation. Check that this message is not displayed.


2.13 Installing the components of ManagementAgent

The subsequent sections describe how to install the components to the Virtual DataCenterAutomation Management Agent.

2.13.1 Components Installed on the Management AgentFor the system requirements, see Chapter 6. Operating Environments/System Requirements in VirtualDataCenter Automation First Step Guide.

The components installed when installing the Management Agent are as follows.

• MasterScope MISSION CRITICAL OPERATIONS Agent

NoteIf a management agent is used, you must purchase an "Infrastructure agent monitoring option license".


60

2.13.2 Software Required to be Installed in AdvanceBefore starting installation of the components of the Management Agent, install the followingsoftware.

• Microsoft Visual C++ 2005 SP1 redistributable package (x86)

• .Net Framework 3.5 (Windows Server 2012/Windows Server 2012 R2)

2.13.3 Installing Visual C++ 2005 Redistributable PackageThe installation procedure is as follows.


2. Execute the following file on the command prompt or Explorer to start the installer.

> <Install DVD>:\fw\tools\Microsoft\2005\vcredist_x86\vcredist_x86.exe

3. Follow the instructions on the screen to perform installation.

2.13.4 Installing .Net Framework 3.5 Service Pack1Install Windows Server 2012 and Windows Server 2012 R2 following the instructions at the URLbelow.

http://support.microsoft.com/kb/2734782/ja

2.13.5 Installing the components of Management Agent1. Insert the vDCA/NWA install DVD into the DVD drive.





61

http://support.microsoft.com/kb/2734782/ja

4. Select [Custom], and click [Next].

5. Select [MasterScope Media], and click [Run].

The MasterScope framework media installer starts up, and the following screen is displayed.


62

6. Check that [Install] is selected, and click [Next ].

7. The [Choose Components] dialog box is displayed. Select all of the following components.

• Product name: MasterScope MISSION CRITICAL OPERATIONS

• Type: Agent

8. Click [Next].

The [Product Installation Settings] dialog box is displayed.

Select [Framework Product], [Agent], and then [Service 1] and perform the following settings:

(Depending on the installation status of other components, the configuration name may be[Service 2] or others instead of [Service 1].In that case, substitute your correct servicenumber.)

Setting Value

[Install directory path] Specify the installation destination folder.The default value in a 32-bit environment is "%Program Files%\NEC\UMF\Operations".The default value in a 64-bit environment is "%Program Files(x86)%\NEC\UMF\Operations".Specify the folder path using up to 90 characters.

[Self hostname] Specify the name for MISSION CRITICAL OPERATIONS toidentify the agent.Maximum digits are 64. It can be specified separately from thecomputer name.If it is omitted, the computer name is specified.

[Manager hostname] Specify the host name or IP address of the manager.

[Manager port] Specify the manager port number used to establish a connectionto the manager.The default value is 12520.


63

Setting Value

[Service Identifier] It is an identifier used when multiple instances of the agentexist. No specification is required if there is one instance.Maximum number of digits: 16Available characters: 1-byte alphanumeric _ - 2-byte characters

[Port for Agent Internal Communication] Port for internal communications of the agent.Normally, use the default value without any change.

[Service number] This item can be omitted. (default value)If specifying this, a value different from the [Self hostname] tobe specified in the other agents must be set here. The specifiedvalue is added to the end of the Windows service name.Values from 1 to 999 are available. If this setting is omitted, thevalue is automatically assigned.

9. Click [Next].

10. The [Installation Confirmation] screen is displayed. Check that the settings are OK, and click[Start].

11. After the installation, the [Finish] screen is displayed. Confirm that all the components havebeen successfully installed from the displayed message. Click [Finish] to complete theinstallation work. If there is any component that failed to install, take actions by referring to"7.2.2 An error occurs during installation (page 176)".

12. Click [Exit] to end the installation.

2.14 Registering and Setting up the GlobalManagement Server

This section describes license registration performed after installation of the components of theGlobal Management Server and the settings of the Global Management Server.

2.14.1 Registering License to Operation ManagementFunction

The license is automatically registered on new installation. The registered license keys will expire inone month unless a "codeword" described in the next section is registered.

A different codeword is issued for each of the Global Management Servers. Apply for a codewordaccording to the explanation in Virtual DataCenter Automation Release Memo.

If the license is already registered, the steps described in this section are not necessary.

If the license is not automatically registered, register the license key by performing the followingprocedure.

1. Open the file <Install DVD>:\fw\licensekeys\licensekey_GM.txt.

2. The license keys for each component are described as below.

Register the license keys listed here to the operation management function.

## This file contains a license key for Virtual DataCenter Automation Global Management Server.


64

# The use of this license key other than as Virtual DataCenter Automation is strictly prohibited.# Please consult with the EULA for more information.#

<MISSION CRITICAL OPERATIONS> ProductCode: VDC0300-MCOB00 LicenseKey: xxxxxxxxxxxxxxxxxxxxxxx

<AssetSuite> ProductCode: VDC0300-ASNB00 LicenseKey: xxxxxxxxxxxxxxxxxxxxxxx

<MISSION CRITICAL OPERATIONS_GM> ProductCode: VDC0300-GMGB00 LicenseKey: xxxxxxxxxxxxxxxxxxxxxxx

<Network Automation> ProductCode: VDC0300-NWAB00 LicenseKey: xxxxxxxxxxxxxxxxxxxxxxx

3. Start up the console of the operation management function.

Execute the shortcut [MasterScope MISSION CRITICAL OPERATIONSConsole__vDCGMSvc] created on the desktop or on the Start menu.

4. The [Login] screen is displayed. Enter the following default password to log in as anadministrator.

• [Login name]: Administrator

• [Password]: websam

5. Click [Setting] and then [Configuration Mode] from the pull-down menu to enter theconfiguration mode.

6. Click [Setting] and then [License Management] from the pull-down menu.

7. The [License Management] dialog box is displayed. Click the [Product Code] tab and [Add].

8. The [License Key Registration] screen is displayed. Enter the value of ProductCode ofMISSION CRITICAL OPERATIONS in the previous file in [ProductCode], and enter thevalue of LicenseKey in [LicenseKey].

9. Click [Registration].

10. Record the string displayed in [Request Code], and click [Close].

11. Perform Steps 5 to 8 for MISSION CRITICAL OPERATIONS_GM and AssetSuite.

12. Delete all the trial version licenses registered during installation.


65

On the [Product Code] tab, specify the licenses with "Trial License Key", and click [Delete].When the confirmation dialog box is displayed, click [Yes].

13. Click [OK].

14. Shut down the console of the operation management function.

15. Restart the following services.


Registration of the license keys to the operation management function is now complete. Theregistered license keys will expire in one month unless a "codeword" described in the next section isregistered.

A different codeword is issued for each of the Global Management Servers. Apply for a codewordaccording to the explanation in Virtual DataCenter Automation Release Memo.

2.14.2 Registering CodeWord to Operation ManagementFunction

Acquire the code word of the license key registered to the operation management function, and thenregister the code word as the procedure below.

1. Start up the console of the operation management function, and log in.

Execute the shortcut [MasterScope MISSION CRITICAL OPERATIONSConsole__vDCGMSvc] created on the desktop or on the Start menu.


3. Click [Setting] and then [License Management] from the pull-down menu.

4. On the [Product Code] tab, select the license of MISSION CRITICAL OPERATIONS, andclick [Registration].

5. Enter the code word sent to [Codeword].

6. Click [Registration].

7. Perform Steps from "4" to "6" for the license keys of MISSION CRITICALOPERATIONS_GM, AssetSuite and Network Automation.

2.14.3 Registering Option License and CodewordTo use the functions purchased as options, you must register the license keys listed on the codewordapplication form of each option license to the system to get the codeword of the registered licensekeys, and register the codeword.

The number of license keys and the functions that require registration vary depending on the optionlicense. The functions that require registration for each option license are as follows. Perform therequired operations according to the purchased options.

• MasterScope Virtual DataCenter Automation Network Automation Option Device License

One license key must be registered. Log into the console of the global management server, andregister the license and codeword to the operation management function.

• MasterScope Virtual DataCenter Automation performance analysis option

There is one license key that requires registration. Log into the console of the ManagementServer and register the license and codeword to the operation management function. For the


66

registration procedure, see "2.15.2 Registering License to Operation Management Function(page 80)" and "2.15.3 Registering Code Word to Operation Management Function (page 81)".

• MasterScope Virtual DataCenter Automation infrastructure agent monitoring option 1monitoring target license

There are three license keys that require registration. Three codeword application forms areprovided. Perform the following operation for each product names listed on the codewordapplication form.

Note that functions that require registration vary depending on the license key.

- MasterScope Virtual DataCenter Automation infrastructure agent monitoring option 1monitoring target license (MISSION CRITICAL OPERATIONS)

Register the license and codeword to the operation management function. For theregistration procedure for monitoring with the Global Management Server, see"2.14.1 Registering License to Operation Management Function (page 64)" and"2.14.1 Registering License to Operation Management Function (page 64)".

For monitoring with the Management Server, see "2.15.2 Registering License toOperation Management Function (page 80)" and "2.15.3 Registering Code Word toOperation Management Function (page 81)".

For monitoring with the VM Monitoring Server, see "2.16.1 Registering the License tothe Operation Management Function (page 85)" and "2.16.2 Registering Code Word toOperation Management Function (page 86)".

- MasterScope Virtual DataCenter Automation infrastructure agent monitoring option 1monitoring target license (AssetSuite)

Register the license and codeword to the asset management function. For the registrationprocedure, see "2.14.1 Registering License to Operation Management Function (page64)" and "2.14.1 Registering License to Operation Management Function (page 64)".

2.14.4 Setting up the Service GovernorCreate an authentication key for the Service Governor.

1. Log into the Global Management Server with the Administrators right.

2. Open the Tools folder in the installation destination folder of the components of the GlobalManagement Server.

3. Log into the Global Management Server with Administrators right, execute the vDCTool.batcommand as follows, and create the access key.

> cd "C:\Program Files (x86)\NEC\vDCA\GM\FW\Tools"> vDCTool.bat createkey <UserName> -description "<Description>"

Specify arbitrary values for <UserName> and <Description>.

Confirm that the following is displayed as a standard output.

NORMAL END.command exit code:0COMMAND SUCCEEDED.

4. Confirm the created access key.

Perform the following command to display the created access key.


67

> cd "C:\Program Files (x86)\NEC\vDCA\GM\FW\Tools"> vDCTool.bat showkey <UserName>


-------------------------------------------------------------UserName : <UserName>Description : <Description>AccessKeyId : /TZfHsSFsdfsL3ghfE9hKyRYLW2ufSbcnYWf1m4RBVrw=SecretAccessKey : rSQ2z2Yn/OgSHhL3R7j6IWuiErtMl1CBMJQWtWpE5rXuU=-------------------------------------------------------------NORMAL END.

command exit code:0COMMAND SUCCEEDED.

Specify the AccessKeyId and SecretAccessKey displayed to portal products.

Write down the values of the authentication access key (AccessKeyId) and authenticationsecret key (SecretAccessKey) and specify them to portal products. To use WebAPI of theService Governor, it is necessary to include the assigned access key in the Http request headerfor using WebAPI.

5. When the portal products (MasterScope CloudManager, etc.) use WebAPI, create the Httprequest header as follows.

Use the following Http request header for authentication.

HTTP header Description

Date Specifies in the WebAPI request date (RFC1123 format).

Authorization Specifies the created access key and signature described later.Specifies "SharedKeyLite" as the authentication method.

Use the following algorithm to create the Authorization header.

• Read the access key created in the vDCTool.bat command of the Global ManagementServer.

AccessKeyId : /TZfHsSFsdfsL3ghfE9hKyRYLW2ufSbcnYWf1m4RBVrw=SecretAccessKey : rSQ2z2Yn/OgSHhL3R7j6IWuiErtMl1CBMJQWtWpE5rXuU=

• Determine the request date.

Date = "Wed, 19 Dec 2012 08:01:10 GMT"

• Acquire the WebAPI path with the query character string ("?" or after) excluded.

CanonicalizedResource = "/umf/api/jobs/createhost"

• Concatenate the request date and path with a line feed character (CRLF) and create thecharacter strings to be authenticated.

CRLF = "\x0D\x0A"StringToSign = Date + CRLF + CanonicalizedResource


68

• Create the HMAC (SHA256) from the character strings to be authenticated andSecretAccessKey and encode it with Base64.

Signature = Base64(HmacSHA256(SecretAccessKey, StringToSign))#=> "8FPVWlEQVY52AuTQMCnHv1ZmrqPQoamI4DzW91H0bOw="

• Create the HTTP request header.

Example of Http request header:

Date: Wed, 19 Dec 2012 08:01:10 GMTAuthorization: SharedKeyLite /TZfHsSFsdfsL3ghfE9hKyRYLW2ufSbcnYWf1m4RBVrw=:8FPVWlEQVY52AuTQMCnHv1ZmrqPQoamI4DzW91H0bOw=

NoteSpecify the HTTP request in the RFC 4627 JSON format. Return the HTTP response in the JSON orPNG image. The character encoding of the JSON data is UTF-8.

NoteThis procedure is required in order to perform setup on the portal product (MasterScopeCloudManager, etc.) side which uses the WebAPI of the Service Governor.

2.14.5 SSL Settings of Application ServerThis procedure is not required if SSL communication is not performed.

NotePerform the setting process for both the active and standby nodes when the service governor is operated inthe cluster configuration.

1. Setting certificate

Prepare the server certificate in advance before performing this procedure.

For the example of how to set the server certificate, see "Appendix D. Certificate in the SSLSetting (page 193)".

2. Changing the Tomcat setting

Edit the following file with a text editor.

<Installation folder>\FW\Tomcat\conf\server.xml

* <Installation folder>is the installation destination of the service governor. "C:\Program Files(x86)\NEC\vDCA\GM\FW\Tomcat\conf\server.xml" is set by default.

Follow the procedure below to correct a file:

 *(3) Delete


69

*Set <Key store file name> and <Key store password> that were specified in "AppendixD. Certificate in the SSL Setting (page 193)" for <Key store file name> and <Key storepassword>, respectively.

Setting example:

<Connector port="12443" protocol="HTTP/1.1" SSLEnabled="true" maxThreads="150" scheme="https" secure="true" keystoreFile="C:\keystore.jks" keystorePass="changeit" clientAuth="false" sslProtocol="TLS" />

3. Changing env.bat

Change the following parameers in the C:\Program Files (x86)\NEC\vDCA\GM\FW\Tools\env.bat batch file when SSL is enabled: For the SSL port, change MANAGER_PROTOCOLto [https].

Setting example:

set MANAGER_PROTOCOL=httpsset MANAGER_PORT=12443

4. Restarting the service

Restart the "Apache Tomcat 8.0 ServiceGovernor" service.

2.14.6 Setting up the Property File for the Service GovernorSet the properties of the Service Governor.

The property setting file is "\FW\Tomcat\conf\vdcapi.properties" in the installation destination folderof the components of the Global Management Server.

The description of each parameter and setting example are shown below.

• Parameter description

Parameter name Description

proxysvc.gm It specifies the host name and port number of the proxy SVC of the GlobalManagement Server.The default value is "http://localhost:8081, localhost, GM".

vdc.manager(n).host It specifies the URL and port number of the proxy SVC of the Management Server andVM Monitoring Server. This parameter must be specified.The format of the parameter is as follows.vdc.manager{n}.host={URL},{MCO SelfHost},{SSC Port},{SSC AccessKey},{SSCSecretKey},{Alias},{vDC Version}The default value of port number is 8081.

• Format of the vdc.manager(n).host parameter

Enter a serial number in {n} part of the vdc.manager{n}.host key string. When there are twounits of the Management Server, set the following.

vdc.manager1.host={URL},{MCO SelfHost},{SSC Port},{SSC AccessKey},{SSC SecretKey},{Alias},{vDC Version}

vdc.manager2.host={URL},{MCO SelfHost},{SSC Port},{SSC AccessKey},{SSC SecretKey},{Alias},{vDC Version}


70

Set the following elements to the setting values. Use a comma (,) as a separator.

Setting element Value

{URL} http://<Management Server Name>:8081Specify the URL above. "8081" is the port for internal communication with MISSIONCRITICAL OPERATIONS WebService.

{MCO SelfHost} Specify <Management Server Name>.The Management Server name must be the same as the HostName property of the[SelfNode] section set in the following file under the installation destination folder ofthe Management Server.C:\Program Files (x86)\NEC\vDCA\MoM\FW\Manager\sg\SysMonMgr.ini[SelfNode]HostName=MOM01

{SSC Port} Specify the same port number as ServerPort in the [SSCAPI] section listed in theSysMonMgr.ini file of the Management Server.[SSCAPI]ServerPort=26105It is not required for the VM Monitoring Server.

{SSC AccessKey} Specify the same string as AccessKeyId in the [SSCAPI] section listed in theSysMonMgr.ini file of the Management Server.[SSCAPI]AccessKeyId=xxxxxxxxxxxxxxxxxxxIt is not required for the VM Monitoring Server.

{SSC SecretKey} Specify the same string as SecretAccessKey in the [SSCAPI] section listed in theSysMonMgr.ini file of the Management Server.[SSCAPI]SecretAccessKey=yyyyyyyyyyyyyyyyyyyIt is not required for the VM Monitoring Server.

{Alias} Specify the alias to the Management Server to identify the server as unique. One-bytealphanumeric characters only.* For the Service Governor, identifiers are assigned to uniquely identify resources thatbelong to each Management Server.An alias is assigned to each identifier.

{vDC Version} Specify the version of Virtual DataCenter Automation installed in the relevant MoM.

• Setting example

proxysvc.asset.timeout=2100proxysvc.mco.timeout=2100response.stacktrace.enable=falseproxysvc.gm=http://localhost:8081,localhost#vdc.manager{n}.host={URL},{MCO SelfHost},{SSC Port},{SSC AccessKey},{SSC SecretKey},{vDC Version}vdc.manager1.host=http://mom03:8081,mom03,26105,SiwVT4jiK2FddOaMwoJ7sF18sYeO5SeIngYYUSIUXsg=,sLk4/X6bdQAkAstqfdM7Hb56vFlpodfW2g3CWWSTWMo=,mom3,3.0vdc.manager2.host=http://mom04:8081,mom04,26105,7wkfthHUCahf4zNXcRCv0K6yLW48eyHs4RcDLgw+eY4=,yhZigmZngjFO8ZsXkcKDIFLQH2qGwMfbB2dQcSOGHFc=,mom4,2.2vdc.manager3.host=http://rm01:8081,rm01,,,,rm1,3.0mom.info.prefix=%a


71

mom.info.prefix.start=(*mom.info.prefix.end=*)job.id.separator=|

• Reflect the changed properties

Execute the following command on the Global Management Server to reflect the changedproperties.

Log into the Global Management Server with Administrators rights, execute the vDCTool.batcommand as follows to reflect the changed properties.

> cd "C:\Program Files (x86)\NEC\vDCA\GM\FW\Tools"> vDCTool.bat properties reload


Normal End. PropertyFile(vdcapi.properties) was reload.

-------------------------------------------------------------COMMAND SUCCEEDED.HTTP STATUS: 200SUCCEEDED.


NoteIf the configuration of [Service Governor - HTTP Port] was changed in the procedure for installing thecomponents of Global Management Server, the following error message is output.

Abort Connection Error :IO error has happened. http response cord can't be received.

The specified port number and the port number in the vDCTool.bat batch file must match. If the valuehas been changed from the default value (12080), change the following parameters in the vDCTool.batbatch file. For the SSL port, change MANAGER_PROTOCOL to [https].

set MANAGER_PROTOCOL=httpset MANAGER_PORT=12080

Execute the following command to check the loaded property values.

> cd "C:\Program Files (x86)\NEC\vDCA\GM\FW\Tools"> vDCTool.bat properties show


proxysvc.asset.timeout=2100proxysvc.mco.timeout=2100response.stacktrace.enable=falseproxysvc.gm=http://localhost:8081,localhostvdc.manager1.host=http://MOM3:8081,MOM3,26105,8c+8ZS0zgKC3risK7J83OqC1KIICzplAk8HiNRWnVgA=,i/yQbtBRIQ2tR9RrHAzWjpVSCjH2uq45T1S5FXJR6L8=,MOM3,3.0


72

vdc.manager2.host=http://MOM4:8081,MOM4,26105,eTU4Iadq24oSi4ma8zZ9D6px/f+bQKbkVC+sFJ3g8Ws=,XxzoJeX3UfYwORnCNVf5oHJyalEpwFzqRi/V/wA3Ef8=,MOM4,2.2mom.info.prefix=%amom.info.prefix.start=(*mom.info.prefix.end=*)job.id.separator=|------------------------------------------------------------

HTTP STATUS: 200SUCCEEDED.


2.14.7 Default Settings of Asset Management FunctionTo manage the virtual machine on which the Managed Machine is installed, default setting of theasset management function must be specified. It is described in the sections from"2.14.7.1 Registering New Company (page 73)" to "2.14.7.2 Setting up Agent Environment (page74)".

To manage the virtual machine on which the Managed Machine is installed, at least one "company"must be created. For the details of “company”, refer to Chapter 3. System Design in the VirtualDataCenter Automation First Step Guide.

This section describes the procedure from registering a company to performing agent environmentsetting. All operations are performed from the AssetSuite console. Start the AssetSuite console andswitch it to definition mode by the following procedure.

1. Starting up the console of the asset management function. Perform the shortcut “MasterScopeAssetSuite Console” created on the desktop.

2. The [Login] dialog box is displayed. Enter the following default password to log in as anadministrator.

• Login name: Administrator

• Password: websam

3. Click [Setting] and then [Configuration mode] from the pull-down menu to enter theconfiguration mode.

2.14.7.1 Registering New CompanyRegister a company as following procedures.

1. In the tree view, right-click the [Asset Management] node, and then select [RegisterCompany].

2. The [Register a new company] dialog box is displayed. Enter [Company name], and then clickthe [OK] button.


73

For details of the setting items, see 3.1.1 Registering a company in the MasterScope AssetSuiteAdministration Manual.

2.14.7.2 Setting up Agent EnvironmentPerform agent environment setting for the "company" registered in "2.14.7.1 Registering NewCompany (page 73)".


74

1. Right-click the registered company node, and click [Agent Environment Settings].

2. The [Set agent environment] screen is displayed. Select [Windows] as [OS type].

3. Perform the following settings.

Tab Setting Value

Common to all agents SG distribution interval 240 minutes (default value)

Task tray message display level Clear all the check boxes.

Number of days to manage tasktray log file

14 days (default value)

Asset management Collection schedule*1 Select the [System startup] and [Every week]check boxes.Select the [Every week] check box and all thecheck boxes from [Mondays] to [Sunday].Enter the starting time to collect theconfiguration information in [Starting time].

*1 In Virtual DataCenter Automation, configuration information is frequently updated due tocreation or change of the virtual machine, so configuration information must be collected atsystem startups and on a regular basis (once a day). Therefore, set [Collection schedule] asspecified in the setting value.

4. Click [OK].

5. Right-click the registered company node again, and click [Agent Environment Settings].

6. The [Set agent environment] screen is displayed. Set the [OS type] to [Linux].


75

7. Perform the following settings.

Tab Setting Value

Common to all agents SG distribution interval 240 minutes (default value)

Asset management Collection schedule Select the [System startup] and [Every week]check boxes.Select the [Every week] check box and all thecheck boxes from [Mondays] to [Sunday].Enter the starting time to collect theconfiguration information in [Starting time].

8. Click [OK].

2.14.8 Default Settings of Operation Management FunctionAs the default setting to perform monitoring of Managed Machines, perform the setting of theperformance monitoring function and disable the message monitoring function. The setting isperformed on the console of the operation management function.

1. Starting up the console of the operation management function.

Execute the shortcut [MasterScope MISSION CRITICAL OPERATIONSConsole__vDCGMSvc] created on the desktop.

2. The [Login] screen is displayed. Log in as an administrator with the initially set password asfollows.




4. Click [Setting] and then [Option].

5. Select the [Performance Monitor] tab.

6. Specify 300 Sec. as the [Monitoring Interval] value.


76

TipTo change the setting value, determine the monitoring interval by referring to 9.3.1 Specifications forMonitoring Settings of the MISSION CRITICAL OPERATIONS in Virtual DataCenter AutomationConfiguration Guide.

7. Click [OK].

8. Click [Setting] and then [Option].

9. Select the [Message Monitor] tab.

10. Clear the [Use Message Monitor] check box.


77

11. Click [OK].

2.14.9 Editing Trace Log Settings of Resource ManagementFunction

Here explains how to change trace log file size of resource management function. We recommendthat you set larger log file size than default because sufficient information for analysing error causemay not be got if the trace file size remains default.

1. Edit the following file with text editor.

<Installation path>\FW\Manager\sg\RpResource\RpResourceMgr.ini<Installation path> is the path you specified to Install Directory Path in "2.3.5 Installing thecomponents of Global Management Server (page 18)", step7.

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

Edit properties of section key of trace log as follows, and save the file.

• In Trace section, set 1048576 to Size, 256 to MaxBufferTrace.


78

• Add TraceLog section and TraceRes section as following example.

Example:

[Trace]Size=1048576QueueSize=100Level=0MaxBufferTrace=256

[TraceLog] Size=104857600QueueSize=10000Level=0WriteLevel=3MaxBufferTrace=1024

[TraceRes]Size=104857600QueueSize=5000Level=0WriteLevel=3MaxBufferTrace=1024

2.14.10 Redundant Configuration of the Service GovernorNormally, the Global Management Server and Service Governor are installed together. The ServiceGovernor can be installed on separate machines for redundant configuration. Load balancing can beachieved by assigning processing to multiple Service Governor terminals with a load balancer.

For the procedure for redundant configuration of the Service Governor, see "3.1 RedundantConfiguration of the Service Governor (page 96)".

2.15 Registering and Setting up the ManagementServer

This section describes license registration performed after installation of the components of theManagement Server and the settings of the Management Server.

2.15.1 Registering License to SigmaSystemCenter FunctionTo use the functions of the Management Server, the license keys of Virtual DataCenter Automationmust be registered to the system. This section and the next section describe the procedure forregistering license keys for SSC and license keys for the operation management function.

This section describes how to register the license keys for SSC. There are two types of licenses forSSC: the MasterScope Virtual DataCenter Automation agent basic license, and the license within theinstallation media.

Purchase the MasterScope Virtual DataCenter Automation agent basic license in advance.

For the license in the installation media, the following license key can be found when opening the file<Install DVD>:\ssc\licensekey.txt Register this license key to SigmaSystemCenter.


79

Further the license for evaluation for which everything's function of SSC can be used is registered bydefault and is effective for 60 days. When registering an agent basic license and a license in theinstallation media, eliminate a license for evaluation.

# This file contains a license key for SigmaSystemCenter.# The use of this license key other than as vDC Automation is strictly prohibited.# Please consult with the EULA for more information.#AAAAA-BBBBB-CCCCC-DDDDD-EEEEE

1. Start the SystemProvisioning Web Console.

In the [Start] menu, select [SigmaSystemCenter] to start the [SystemProvisioning WebConsole]. The web browser starts and the SigmaSystemCenter login dialog box is displayed.

2. Enter the user name and password, and then click [Login].

You can login with the user name "admin" and password "admin" by default.

3. Click [Management].

4. Click [License].

5. When installing SigmaSystemCenter, a registered license key is eliminated.

6. Enter the license key described above in [License Key].

7. Click [Add].

8. To register all MasterScope Virtual DataCenter Automation agent basic licenses, repeat thefollowing procedures.

a. Enter the license key of the MasterScope Virtual DataCenter Automation agent basiclicense in [License Key].

b. Click [Add].

9. Restart the following service.

• PVMService

2.15.2 Registering License to Operation ManagementFunction


A different codeword is issued for each of the Management Servers. Apply for a codeword accordingto the explanation in Virtual DataCenter Automation Release Memo.



1. Open the file <Install DVD>:\fw\licensekeys\licensekey_MoM.txt

2. The license keys for each component are described as below. Register the license keysdescribed to the operation management function.

Log into the console of the Management Server and register the licenses for MISSIONCRITICAL OPERATIONS and Network Manager.


80

## This file contains a license key for Virtual DataCenter Automation Management Server.# The use of this license key other than as Virtual DataCenter Automation is strictly prohibited.# Please consult with the EULA for more information.#


<Network Manager> ProductCode: VDC0300-NPVB00 LicenseKey: xxxxxxxxxxxxxxxxxxxxxxx

For the registration procedure, see "2.14.1 Registering License to Operation ManagementFunction (page 64)".

3. After the license is registered, restart the following service.


2.15.3 Registering Code Word to Operation ManagementFunction


1. Log into the console of the Management Server and register the codewords for ManagementServer.

2. For the registration procedure, see "2.14.2 Registering CodeWord to Operation ManagementFunction (page 66)".

2.15.4 Setting up WebAPI for SSCCreate a server certificate and SSC API key for the Management Server.

It is required to prepare the server certificate when using the Web API. For details about how topurchase the server certificate and how to install to IIS, confirm with the company issuing servercertificate.

This section describes the method of setting the server certificate by using the self-signed certificate.

1. Open the Internet Information Services (IIS) Manager.

2. Click the server name on the left pane, and double-click [Server Certificates] displayed on theright pane.

3. Click [Create Self-Signed Certificate] in [Actions].

4. Enter "ssc" in the [Specify a friendly name for the certificate:] text box, and click [OK].

5. Click [Sites] displayed when you click the server name on the left pane, and select [DefaultWeb Site] displayed on the right pane.

6. Click [Bindings] in [Actions].

7. Click [Add] in the [Site Bindings] screen.

8. Perform the following setting in the [Add Site Binding] screen, and click [OK].


81

Item Value

Type https

IP address All Unassigned

Port 26105

SSL certificate ssc

9. Click [Close] on the [Site Bindings] screen.

10. Click the server name on the left pane, and double-click [Server Certificates] displayed on theright pane.

11. Double-click [ssc] on the right pane.

12. Select the [Details] tab on the [Certificate] screen, and click [Copy to File].

13. Click [Next].

14. Select the [No, do not export the private key] radio button on the [Export Private Key] screen,and click [Next].

15. Select the [Base-64 encoded X.509 (.CER)] radio button on the [Export File Format] screen,and click [Next].

16. Enter the storage destination full path and file name of the file in the [File name:] text box, orclick [Browse] and specify the file name and storage destination.

NoteAny file name can be specified, but the subject name recorded earlier is recommended.

17. Click [Next].

18. Click [Finish] on the [Completing the Certificate Export Wizard] screen, and click [OK] in themessage displayed.

19. Copy and import SSC API key to the Global Management Server. Import SSC API key to theGlobal Management Server by referring to "2.14.4 Setting up the Service Governor (page67)" and "2.14.6 Setting up the Property File for the Service Governor (page 70)".


For the procedure, see "2.14.8 Default Settings of Operation Management Function (page 76)".

In the case of Management Server,[MasterScope MISSION CRITICAL OPERATIONSConsole__vDCGMSvc] shall be replaced with [MasterScope MISSION CRITICAL OPERATIONSConsole__vDCMoMSvc].

2.15.6 Setting the Monitoring Definition of Management ServerPerformance Monitoring

Set the monitoring definition to monitor the performance of the Management Server. When setmonitoring definistion in VM Monitoring Server This setting is not required.



82

Execute the shortcut [MasterScope MISSION CRITICAL OPERATIONSConsole__vDCMoMSvc] created on the desktop or on the Start menu.


3. In the Topology View of the Management Server Console, right-click the [Automation] groupnode, and select [Monitor Setting Import] from the shortcut menu displayed.

4. Click [Browse] on the [Group Import Service] screen, and select the import file from thescreen displayed. When importing, the import file of the vDCA/NWA install DVD cannot bespecified directly. Copy the import file in the following folder to the local drive of theManagement Server and select it.

<Install DVD>:\fw\tools\MCO\Template\Performance

5. According to the imported filing, select an OS type (Windows or Linux), and click [OK].Setting about each OS type.

2.15.7 Linkage setting between Global Management ServerPerform the linkage setting between Global Management Server and Management Server by thefollowing procedure.


Execute the shortcut [MasterScope MISSION CRITICAL OPERATIONSConsole__vDCMoMSvc] created on the desktop.

2. The [Login] dialog box is displayed. Enter the following default password to log in asadministrator.




4. Click [Setting] and then [Option] to open the [Option Setting] dialog box.

5. Select the [Manager Linker] tab.

6. Select the [Use Manager Linker] check box.

7. Click [OK].

8. In the tree view, right-click the [Manager Linker], and then select [Upper Manager Setting].

9. The [New Upper Manager] dialog box is displayed. Perform the following settings.

Item name Value

Upper Manager Host name of Global Management Server.

HostName Host name of Global Management Server.

Port 12520(default value)

10. Click [OK].

11. Confirm that the severity color (Background color of the icon) of "Manager Linker" is"Normal".

If the severity color is "Unknown", Confirm that the Global Management Server has beenstarted, and then restarts the operation management functions of the Management Server.


83

(In default severity color, "Normal" is displayed as follows.)

2.15.8 Setting the Accumulation Period of StatisticalInformation

Set the period in which statistical information of the Managed Machine is accumulated.

1. Edit the configuration file:

Open C:\Program Files (x86)\NEC\vDCA\MoM\FW\Manager\sg\PerfStatisticsMgr.ini with atext editor such as Notepad, and specify the following setting values.

Select the appropriate path of the installation destination folder according to the environment.

[AutoMakeCounter195]HistoryDuration=8

The following can be specified for the accumulation period of statistical information.

Value Description

0 Unlimited

1 1 week

2 2 weeks

3 1 month

4 2 months

5 3 months

6 6 months

7 9 months

8 1 year

2. After editing is complete, restart the following service.


NoteTo change setting of accumulation period, calculate the disk size used for collection of performanceinformation and statistical information, and perform it as required. For the calculation method for the disksize used, see the following in MISSION CRITICAL OPERATIONS Release Memo.

• 11.12. Accumulating statistical dataVirtual DataCenter Automation only creates statistical information for ten minutes, one hour and one day.To change the statistical information to be created, open and edit the following configuration file by usingNotepad. Specify a value divisible by 60 (seconds) in the range from 60 to 86400 (seconds). Multiple valuescan be specified by delimiting them with commas.Select the appropriate path of the installation destination folder according to the environment.

• When performing basic monitoring (to disclose performance information to the tenant administratorvia the service portal) in Virtual DataCenter AutomationC:\Program Files (x86)\NEC\vDCA\MoM\FW\Manager\sg\PerfStatisticsMgr.ini


84

[AutoMakeCounter195]Interval=600,3600,86400

• When displaying the storage performance from the physical view in the integrated topology viewC:\Program Files (x86)\NEC\vDCA\MoM\FW\Manager\sg\IpPerformanceMgr.ini

[Create]DataInterval=600,3600,86400

• When using the multi graph view or print viewC:\Program Files (x86)\NEC\vDCA\MoM\FW\Manager\sg\PerfGraphMgr.ini

[Create]DataInterval=600,3600,86400

To change the accumulation period of performance information and disk size, see the following in theMISSION CRITICAL OPERATIONS Release Memo.

• 11.11 Accumulation of Collected Performance Data

2.16 Registering and Setting up the VMMonitoring Server

This section describes license registration performed after installation of the components of theVirtual DataCenter Automation VM Monitoring Server and the settings of the VM MonitoringServer.

2.16.1 Registering the License to the Operation ManagementFunction


A different codeword is issued for each of the VM Monitoring Servers. Apply for a codewordaccording to the explanation in Virtual DataCenter Automation Release Memo.



1. Open <Install DVD>:\fw\licensekeys\licensekey_RM.txt .

2. The license keys for the components are listed as shown below. Register the license keys listedhere to the operation management function.

Log into the console of VM Monitoring Server and register the license for MISSIONCRITICAL OPERATIONS.

## This file contains a license key for Virtual DataCenter Automation VM Monitoring Server.# The use of this license key other than as Virtual DataCenter Automation is strictly prohibited.# Please consult with the EULA for more information.#


85


For the registration procedure, see "2.14.1 Registering License to Operation ManagementFunction (page 64)".

3. After the license is registered, restart the following service.


2.16.2 Registering Code Word to Operation ManagementFunction


1. Log into the console of the VM Management Server and register the codeword for VMManagement Server.

For the registration procedure, see "2.14.2 Registering CodeWord to Operation ManagementFunction (page 66)".


For the procedure, see"2.14.8 Default Settings of Operation Management Function (page 76)".

2.16.4 Linkage setting between Management ServerPerform the linkage setting between Management Server and VM Monitoring Server by thefollowing procedure.


Execute the shortcut [MasterScope MISSION CRITICAL OPERATIONSConsole__vDCRMSvc] created on the desktop.





4. Click [Setting] and then [Option] to open the [Option Setting] dialog box.

5. Select the [Manager Linker] tab.

6. Select the [Use Manager Linker] check box.

7. Click [OK].

8. In the tree view, right-click the [Manager Linker], and then select [Upper Manager Setting].

9. The [New Upper Manager] dialog box is displayed. Perform the following settings.


86

Item name Value

Upper Manager Host name of Management Server

HostName Host name of Management Server

Port 12520(default value)

10. Click [OK].

11. Confirm that the severity color (Background color of the icon) of "Manager Linker" is is"Normal"

If the severity color is "Unknown", Confirm that the Management Server has been started, andthen restarts the operation management functions of the VM Monitoring Server.

(In default severity color, "Normal" is displayed as follows.)

2.16.5 Deleting scenario settingsDelete the unused scenario definitions on the VM Monitoring Server.


Execute the shortcut [MasterScope MISSION CRITICAL OPERATIONSConsole__vDCRMSvc] created on the desktop or on the Start menu.





4. Disable all the scenarios under the [Scenario View]-[Automation] group by the following oneof ways.

• Select each of the scenario nodes, and clear the [Enabled] check box from the right-clickmenu.

• Execute the following command on the command prompt.

> cd "C:\Program Files (x86)\NEC\vDCA\RM\FW\Manager\bin"> ScenarioCmd.exe ENABLE -D

5. Select the [Automation] group, and select [Delete] from the right-click menu.

6. The confirm dialog box is displayed. Click [Yes] to delete the scenarios.

2.16.6 Setting the Monitoring Definition of VM MonitoringServer Performance Monitoring

Set the monitoring definition to monitor the performance of the VM Monitoring Server.



87

Execute the shortcut [MasterScope MISSION CRITICAL OPERATIONSConsole__vDCRMSvc] created on the desktop or on the Start menu.


3. In the topology view of the VM Monitoring Server Console, right-click the [Automation]group node, and select [Monitor Setting Import] from the shortcut menu displayed.

4. Click [Browse] on the[Group Import Service] screen, and select the import file stored in thefollowing folder from the screen displayed. When importing, the import file of thevDCA/NWA install DVD cannot be specified directly. Copy the import file in the followingfolder to the local drive of the Management Server and select it.

<Install DVD>:\fw\tools\MCO\Template\Performance

5. Select an OS type (Windows or Linux), and click [OK].

2.16.7 Setting the Accumulation Period of StatisticalInformation

Specify the period to accumulate statistical information on the managed machine.

For the setting procedure, see "2.15.8 Setting the Accumulation Period of Statistical Information(page 84)".

Replace the configuration file path as follows:

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

2.17 Registering and Setting up the ManagementAgent

This section describes how to register the managed VM servers and storages after installation ofcomponents of the Virtual DataCenter Automation Management Agent.

2.17.1 Registering the VM ServerDescribe the settings of the VM server whose configuration information you want to collect in thefollowing file on the Management Agent.

C:\Program Files (x86)\NEC\UMF\Operations\Agent\sg\iNvmCODC\iVMCollectInfoHost.ini

The description method for the setting file is as follows.

A setting example of iVMCollectInfoHost.ini

[HOST]HOSTTYPE=ESX

IPADDRESS=192.168.1.1USERNAME=userPASSWORD=password

Item Item name Value

HOSTTYPE Device type The following items can be specified.


88

Item Item name Value• ESX• ESXi• HyperV• KVM

IPADDRESS IP address ofdevice

Specify IPADRESS.Specify IPv4.

PORT PORT Valid only when the device category is KVM.Specify the port number used for ssh.Default value when omitted: 22

USERNAME User Name Specify the user name for device access.If the device category is HyperV, specify the following items:• For domain user:

Domain name\user name• For work group user:

IPADDRESS\user name

PASSWORD Password Specify the password.This setting is not required if the device category is KVM and theauthentication method is public key authentication.If PASSWORD is specified in this case, it is used as the passphrase.

AUTHTYPE Authenticationmethod

Valid only when the device category is KVM.Specify the authentication method used in ssh.• 0: Password authentication• 1: Public key authentication (default value)

OpenSSH is used.Create the key by using the ssh-keygen command on the KVM server.

KEYFILE Secret Key file Valid only when the device category is KVM and the authentication methodis public key authentication.Specify the absolute path of the secret key file.

When setting multiple VM servers, describe multiple [Host] sections as follows.

A setting example of iVMCollectInfoHost.ini

[HOST]HOSTTYPE=ESXIPADDRESS=192.168.1.1USERNAME=userPASSWORD=password

[HOST]HOSTTYPE=HyperVIPADDRESS=192.168.1.3USERNAME=domain\userPASSWORD=password

[HOST]HOSTTYPE=KVM


89

IPADDRESS=192.168.1.10USERNAME=userAUTHTYPE=1PORT=22KEYFILE=C:\Users\UserName\Documents\id_rsa

2.17.2 Registering the StorageDescribe the settings of the storage whose configuration information you want to collect in thefollowing file on the Management Agent.

C:\Program Files (x86)\NEC\UMF\Operations\Agent\sg\Storage\StorageArrayInfoCmd.ini

The description method for the setting file is as follows.

A setting example of StorageArrayInfoCmd.ini

[ArrayInfo]EMC1.Name=cs1EMC1.IP=192.168.1.1EMC1.Auth=-User admin -Password admin -Scope 1EMC1.PerfCollect=NoEMC2.Name=cs2EMC2.IP=192.168.1.2EMC2.Auth=-secfilepath C:\EMC_SECEMC2.PerfCollect=YESNetApp1.Name=FAS1NetApp1.IP=192.168.1.2NetApp1.User=rootNetApp1.Password=passwordNetApp1.PerfCollect=YesiStorage1.Name=iStorageArray1iStorage1.PerfCollect=Yes[Path]iStorage=C:\Program Files (x86)\NEC\iSMsvr\

• When the device type is EMC>

To collect storage information, set the following in the setting file on the machine on whichNavisphere/Unisphere CLI is installed.

- EMC1.Name

Set the name of the EMC device so that it matches Unisphere.

- EMC1.IP

Set the IP address of SP of the EMC device.

- EMC1.Auth

Set the authentication parameter to execute Navisphere/Unisphere CLI on the EMC device.

- EMC1.PerfCollect

Set "Yes" to collect performance information.

* To register the second EMC device, use "EMC2".

* For the EMC device from which statistical information is collected, a PerformanceAnalyzerlicense is required.


90

* To collect performance information, performance information must be accumulated withUnisphere in advance.

• When the device type is NetApp>

To collect storage information, set the following information in the setting file.

To collect performance information, install the Management Agent on the same machine asOnCommand Unified Manager.

- NetApp1.Name

Set the name (Hostname) of the NetApp device.

- NetApp1.IP

Set the IP address of the NetApp device.

- NetApp1.User

Set the user for connecting to the NetApp device.

- NetApp1.Password

Set the password for connecting to the NetApp device.

- NetApp1.PerfCollect


* To register the second NetApp device, use "NetApp2".

* To collect performance information, performance information must be accumulated withOnCommand Unified Manager in advance.

• When the device type is NEC Storage

To collect performance information, install the Management Agent on the same machine asNEC Storage Manager.

To collect performance information, perform the following settings.

- iStorage1.Name

Set the device name of the NEC Storage.

- iStorage1.PerfCollect


- NEC Storage

Set the installation path of NEC Storage Manager.

* To register the second NEC Storage, use "iStorage2".

* For the NEC Storage from which statistical information is collected, the PerforMate license isrequired.

* Performance information of the NEC Storage must be accumulated with NEC StorageManager.


91

2.18 Registering and Setting up the IDManagement Server

This section describes the settings of the ID Management Server performed after installation of thecomponents of the ID Management Server.

2.18.1 Setting up the ServicesSelect [Start]->[Control Panel] and [Administrative Tools]->[Services]. From the [Services] screen,set the startup type of the following services to [Automatic].

Start the following services if they are not running.

• EDS Protocol Server

• Apache Tomcat ForEIM

2.18.2 Changing the Password of the Administrator User1. Open the command prompt in the ID Management Server.

2. Execute the following commands to change the password of the two administrator users. Setthe same password for both of the administrator users. For available characters for passwordfor the administrator user, see "* Available characters for password for the administrator user".

> cd "C:\Program Files (x86)\NEC\vDCA\SM\SECUREMASTER\EDS\BIN"> edpasswd -h localhost -p 1389 -D cn=ldapAdministrator,c=JP -w adminpwd -u uid=eidmadministrator,ou=user,ou=tenant0,ou=edseidm,c=JPinput new password of this user : ********input the same password again : ********success.

> edpasswd -h localhost -p 1389 -D cn=ldapAdministrator,c=JP -w adminpwd -u cn=ldapadministrator,c=JPinput new password of this user : ********input the same password again : ********success.

3. Execute the following command to output the encrypted userPassword.

> edsearch -h localhost -p 1389 -D cn=ldapAdministrator,c=JP -W -b uid=eidmadministrator,ou=user,ou=tenant0,ou=edseidm,c=JP -s 0 -attr userpasswordpassword? ********* Password of the administrator user of the ID Management Server set in *2# uid=eidmadministrator,ou=user,ou=tenant0,ou=edseidm,c=JPversion: 1dn: uid="eidmAdministrator" , ou="user" , ou="tenant0" , ou="edseidm" , c="JP"userPassword: {x-eds-crypt}xxxxxxxsearch entry count: 1

4. Open %windir%\IDM\eidmcommon.conf with Notepad, and replace the value of"eidmPassword:" with the encrypted userPassword "{x-eds-crypt}xxxxxxxx" output in 3, andsave it.


92

eidmPassword: {x-eds-crypt} xxxxxxxx

5. Restart the Apache Tomcat For EIM service.

• Apache Tomcat ForEIM

* Available characters for password for the administrator user

Password for the administrator user is 128 characters or less one or more characters. Availablecharacters for password for the administrator user are as follows.

• Alphanumeric:a-z, A-Z, 0-9

• Single-byte smbols:

- !(exclamation mark)

- "(double quotation mark)

- #(numerical sign)

- $(doller sign)

- %(percent)

- &(ampersand)

- '(single quotation mark)

- ((parenthesis)

- )(parenthesis)

- *(asterisk)

- +(plus sign)

- ,(comma)

- -(minus sign)

- .(period)

- /(slash)

- :(colon)

- ; (semi colon)

- < (less than sing)

- = (equal)

- > (greater than sign)

- ? (question mark)

- @ (at sign)

- [ (bracket)

- ] (bracket)

- ^ (caret)

- _ (underscore)

- ` (back apostrophe)

- { (brace)

- | (vertical bar)


93

- } (brace)

- ~ (swung dash)

2.18.3 Use of the ID Management ServerFor the information about setting up authentication using the ID Management Server and how toregister users for the ID Management Server, refer to Chapter 8 Setting up the ID ManagementServer in the Virtual DataCenter Automation Configuration Guide.

2.19 Setting up the Managed MachineThis section describes the settings of the Managed Machine performed after installation of thecomponents of the Virtual DataCenter Automation Managed Machine.

2.19.1 Creating the VM Template of the Managed MachineAfter the components are installed on the Managed Machine, create VM templates of the Windowsmaster VM and Linux master VM as required.

For VM template creation, see Chapter 7 Creating a VM Template in Virtual DataCenter AutomationConfiguration Guide.

If a VM template of the Managed Machine is not created, setting of this item is not required.


94

Chapter 3. Performing Installation According tothe PurposeThis chapter describes how to install the components of individually according to the configuration.

Contents3.1 Redundant Configuration of the Service Governor.....................................................................96

Chapter 3. Performing Installation According to the Purpose

95

3.1 Redundant Configuration of the ServiceGovernor

Normally, the Global Management Server and Service Governor are installed together.

The Service Governor can be installed on separate machines for redundant configuration. Loadbalancing can be achieved by assigning processing to multiple Service Governor terminals with aload balancer.

3.1.1 Installing the ServiceGovernorInstall the Service Governor component on the machines to which you want to distribute loadseparate from the Global Management Server.







96



6. Check that [Install] is selected, and click [Next].


97

7. Select [Application Server], [MasterScope vDC Automation Service Governor], and click[Next].

8. Select [Application Server], and set the configuration of the Application Server module.

Set the following items for [Non Framework Product]-[Application Server] in [Configurationlist].

Setting Value

[Install Directory Path] Specify the installation destination folder.The default value is "%Program Files (x86)%\NEC\vDCA".


98

Setting Value

Application Server Type Specify the Application Server type.Only "Tomcat" can be specified in this version.

[HTTP port] Specify the HTTP port number that provides the ServiceGovernor.The default value is "12080".

[HTTPS port] Specify the HTTPS port number that provides the ServiceGovernor.The default value is "12443".

Tomcat - Management Port Specify the Management port number of the Tomcat.The default value is "12005".

Tomcat - AJP/1.3 Port Specify the AJP/1.3 port number of the Tomcat.The default value is "12009".

9. Click [Next]. The [Installation Confirmation] screen is displayed.

Check that the settings are complete, and click [Start].

NoteInstallation cannot be interrupted once started.

10. On the [Finish] screen, check that installation has been completed successfully. Click [Finish].


99

11. Copy the files as follows.

• C:\Program Files (x86)\NEC\vDCA\Tomcat\conf\vdcalog.properties

• C:\Program Files (x86)\NEC\vDCA\Tomcat\conf\vdcapi.properties

• C:\Program Files (x86)\NEC\vDCA\Tomcat\conf\vdcplugins

• C:\Program Files (x86)\NEC\vDCA\Tomcat\cDCApiKey.jks

* Replace the file path in accordance with your environment.

12. Edit the setting file "vdcapi.properties" copied from the Global Management Server.

a. Edit the following copied file of the Service Governor for redundant configuration.

C:\Program Files (x86)\NEC\vDCA\Tomcat\conf\vdcapi.properties

b. Edit the proxysvc.gm property.

Set a URL to access the Global Management Server to the proxysvc.gmproperty.localhost is set by default as shown below. Change it to the host name of theGlobal Management Server.

proxysvc.gm=http://localhost:8081,localhost

Set the following elements to the setting values.Use a comma (,) as a separator.


http://localhost:8081 http://<Global Management Server Name>:8081Specify the URL above. "8081" is the port for internalcommunication with MISSION CRITICAL OPERATIONSWebService.Specify the host name or IP address of the GlobalManagement Server.


100


localhost Specify <Global Management Server Name>.Specify the host name or IP address of the GlobalManagement Server.

The following is an example of setting.

proxysvc.gm=http://GM:8081,GM

NoteDon't edit any property other than the proxysvc.gm property. Other properties must have thesame settings as in the Service Governor of the Global Management Server.

c. Execute the vDCTool.bat command as follows to reflect the changed properties.

> cd "C:\Program Files (x86)\NEC\vDCA\Tools"> vDCTool.bat properties reload

13. SSL setting of the Service Governor for redundant configuration

To perform SSL setting for the Service Governor for redundant configuration, perform theprocedure described in "2.14.5 SSL Settings of Application Server (page 69)".

3.1.2 Uninstalling the ServiceGovernor1. Insert the vDCA/NWA install DVD into the DVD drive.





101





102

6. Check that [Uninstall] is selected, and click [Next].

7. Select [MasterScope vDC Automation Service Governor], and click [Next].

8. Click [Start].


103


10. Perform the procedures 1 to 6. and Select [Application Server], and click [Next].


104

11. Click [Start].



105


106

Chapter 4. UpgradingThis section describes the procedure to upgrade the functions of Virtual DataCenter Automationversion 3.0 from 2.2. when <Install DVD>:\patch exists, refer to Release.txt in the patch and apply it.

Contents4.1 Upgrading the Global Management Server...............................................................................108

4.2 Upgrading the Global Management Server Console.................................................................116

4.3 Upgrading the Management Server ..........................................................................................116

4.4 Upgrading the Management Server Console ............................................................................120

4.5 Upgrading the VM Monitoring Server .....................................................................................122

4.6 Upgrading the VM Monitoring Server Console........................................................................124

4.7 Upgrading the ID Management Server .....................................................................................126

4.8 Upgrading the Managed Machine ............................................................................................129

Chapter 4. Upgrading

107

4.1 Upgrading the Global Management ServerNote

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

4.1.1 Stop the servicesStop the services in the order below.

• MasterScope UMF Operations Web Service__vDCGMProxy_n

(The "n" at the end digit should be 1 or greater number. The number varies depending on theinstallation environment.)


In a version earlier than Version 2.2, stop the following services, and change the [Startup type] to[Manual].

• WebOTX AS Agent Service

4.1.2 Backup of the service governorThis step is not necessary in version 2.2 or later.

Back up the following file in any location.

• For non-cluster:

- <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\domain\domain1\config\vdcplugins

- S:\vDCA\domain\domain1\config\vdcapi.properties

- S:\vDCA\domain\domain1\vDCApiKey.jks

4.1.3 Upgrading the global management server1. Insert the vDCA/NWA install DVD into the DVD drive.





108





109


The [Installation Selection] screen is displayed.

7. Select the check boxes of the following components.

• MasterScope AsRiCommon Manager

• MasterScope AssetSuite Manager




• Application Server


• MasterScope vDC Automation Portal

8. Click [Next]. The [Product Installation Settings] screen is displayed.

Confirm that [Up] is added to the following components.

• The following components under [Manager]-[Service 101]

- MasterScope AsRiCommon Manager

- MasterScope AssetSuite Manager

- MasterScope MISSION CRITICAL OPERATIONS Manager

- MasterScope Virtual DataCenter Automation Manager

• The following components under services under [View] with the service identifier settingof [vDCGMProxy]

- MasterScope Virtual DataCenter Automation WebService View


110

NoteIf the Global Management Server and Management Server are installed on the same machine,two "MasterScope Virtual DataCenter Automation WebService Views" appear in the [ProductInstallation Settings] screen. For the Global Management Server, select the components withthe service identifier setting of [vDCGMProxy]. The service identifier is the setting valuedisplayed when you click [Service n] under [View] on the left tree.

If [Up] is added to other components, select them and click the [Remove] button to removethem from the update range.

In a version earlier than Version 2.2, confirm that [New] is added to the following componentsunder [Non Framework Product].




In Version 2.2 or later, confirm that [Up] is added to the following components under [NonFramework Product].




9. In a version earlier than Version 2.2, set the configuration of the Application Server module asrequired.

Set the following items for [Non Framework Product]-[Application Server] in [Configurationlist].

Setting Value

[Install Directory Path] Specify the installation destination folder.The default value is "%Program Files (x86)%\NEC\vDCA".

[Application Server Type] Specify the Application Server type.Only "Tomcat" can be specified in this version.

[HTTP port] Specify the HTTP port number that provides the ServiceGovernor.The default value is "12080".

[HTTPS port] Specify the HTTPS port number that provides the ServiceGovernor.The default value is "12443".

[Tomcat - Management Port] Specify the Management port number of the Tomcat.The default value is "12005".

[Tomcat - AJP/1.3 Port] Specify the AJP/1.3 port number of the Tomcat.The default value is "12009".

10. In a version earlier than Version 2.2, set the configuration of the MasterScope vDCAutomation Portal module as required.

Set the following items for [Non Framework Product]-[MasterScope vDC Automation Portal]in [Configuration list].


111

Setting Value

[Host name of the database server] Specify the host name of the machine on which the database isinstalled.The default value is "localhost".

[Instance name of the database] Specify the instance name of the database.Specify the name of the instance created in "2.2.6 InstallingSQL Server (page 12)".The default value is "FWCMDB".

[TCP port of the database server] Specify the port number of the database.The default value is "1433".

11. Click [Next].




4.1.4 Editing Trace Log Settings of Resource ManagementFunction

Here explains how to change trace log file size of resource management function. We recommendthat you set larger log file size than default because sufficient information for analysing error causemay not be got if the trace file size remains default. After upgrading the system, log file name ofresource management function changes. Delete log files of old version manually.

1. Edit the following file with text editor.

<Installation path>\FW\Manager\sg\RpResource\RpResourceMgr.ini<Installation path> is the path you specified to Install Directory Path in "4.1.3 Upgradingthe global management server (page 108)", step 9.

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

Edit properties of section key of trace log as follows, and save the file.

• In Trace section, set 1048576 to Size, 256 to MaxBufferTrace.

• Add TraceLog section and TraceRes section as following example.

Example:

[Trace]Size=1048576QueueSize=100Level=0MaxBufferTrace=256

[TraceLog] Size=104857600


112

QueueSize=10000Level=0WriteLevel=3MaxBufferTrace=1024

[TraceRes]Size=104857600QueueSize=5000Level=0WriteLevel=3MaxBufferTrace=1024

2. Following trace files are no more updated after upgrading because trace log file name changes.Delete the following two files if not needed.

Path: <Installation path>\FW\Manager\log• RpResourceMgr.trc

• RpResourceMgr1.trc

<Installation path> is the path you specified to Install Directory Path in "4.1.3 Upgradingthe global management server (page 108)", step 9.

Default: C:\Program Files (x86)\NEC\vDCA\GM\FW\Manager\log\RpResourceMgr.trc

4.1.5 Updating the Database

4.1.5.1 Updating the local databaseWhen the manager server and database server are the same server, perform the procedures below.


2. Copy the database configuration script.

Copy source Copy destination

<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


113

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

4.1.5.2 Updating the remote databaseWhen the manager server and database server are different servers (remote database environment),update the database on the database server. (Log in as a user who can access the database as adatabase administrator.)




<Install DVD>:\fw\Windows\Tools\sql_rupdate <Arbitrary folder>\sql_rupdateExample: C:\work\sql_rupdate


> cd <Arbitrary folder>\sql_rupdate\sqlserver> WfdbCmdbSetup.bat <Database Name> <Server Name> <Instance 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 R_DATABASE_NAME, R_SERVER_NAME and

R_SQL_INSTANCE_NAME where the <Database Name>, <Server Name> and <InstanceName> was indicated on following file on the manager server.<Install folder>\FW\Manager\sg\wfdbmgr\WFDB.INI

4. "The system cannot find the path specified." message is output to the command prompt afterthe command is executed, but it's no problem. When the execution log is output to theexecution folder after the command is executed, make sure that there is no error. (Any errorindicating that the user, role, database, or schema already exists is not a problem.)

4.1.6 Upgrading the service governorThis step is not necessary in version 2.2 or later.

Overwrite the files that were backed up in any location in the procedure in "4.1.2 Backup of theservice governor (page 108)".

• For non-cluster:

- <Install folder>\FW\Tomcat\conf\vdcplugins\default.plugins

- <Install folder>\FW\Tomcat\conf\vdcapi.properties

- <Install folder>\FW\Tomcat\vDCApiKey.jks

• For cluster:

Overwrite a setting file by both of the [Active] system and [Standby] system.

4.1.7 Start the servicesStart the services in the order below.


114




4.1.8 Applying the standard workflow template1. Preparation

• Obtain the configuration mode after connecting the console to the global managementserver and logging in.

• To retain a backup, rename the scenario in the scenario control view.

If no backup is retained, delete it.

2. Applying the standard workflow template

Import the scenario from the install directory. For details of importing, see [Using ScenarioControl] - [Defining Scenarios] - [Creating and Saving Scenarios] - [Importing ScenarioDefinitions] in the MISSION CRITICAL OPERATIONS online manual.

Scenarios are stored in the following path.

C:\Program Files (x86)\NEC\vDCA\GM\FW\Manager\Svc\Common\sg\Scenario\Template\vDCA

3. Enabling a scenario

Enable the imported scenario. There are 2 ways for enabling.

• Enabling individual scenarios

Right-click the imported scenario and select [Enable]. Multiple scenarios cannot beselected.

• Enabling scenarios in a batch

Enable the imported scenarios in a batch by using a command. Move to the followingpath and execute the command.

>cd "C:\Program Files (x86)\NEC\vDCA\GM\FW\Manager\bin"> ScenarioCmd.exe ENABLE -E

4. Updating the configuration file of DC resource management

Open the following file on the global management server (GM), and change and add the IDs ofimported scenarios.

(When the install destination is the default)

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

The ID of the scenario is the value of [ScenarioID] on the [Property View] tab displayed whenyou click the imported scenario.


115

4.2 Upgrading the Global Management ServerConsole4.2.1 Upgrading the Global Management Server Console







The MasterScope framework media installer starts up.




• MasterScope AsRiCommon View

• MasterScope AssetSuite View


• MasterScope Virtual DataCenter Automation View


Confirm that [Up] is added to the components in the [vDCGMSvc] service.


9. Click [Next].




4.3 Upgrading the Management Server4.3.1 Stop the services

Stop the services in the order below.

• MasterScope UMF Operations Web Service__vDCMoMProxy_n


116


• NvPRO ResourceManagerAPI Service

• NvPRO Base Manager


• FTBase service

4.3.2 Upgrading the Management Server1. Insert the vDCA/NWA install DVD into the DVD drive.











• MasterScope Network Manager







- MasterScope Network Manager


• The following components under services under [View] with the service identifier settingof [vDCMoMProxy]


NoteIf the Global Management Server and Management Server are installed on the same machine,two "MasterScope Virtual DataCenter Automation WebService Views" appear in the [ProductInstallation Settings] screen. For the Management Server, select the components with theservice identifier setting of [vDCMoMProxy]. The service identifier is the setting valuedisplayed when you click [Service n] under [View] on the left tree.


117


9. Click [Next].




4.3.3 Updating the DatabaseThe procedure differs depending on the database setting. Perform the procedure according to thesetting.

• When the manager server and database server are the same server and [Database - Database forNetwork Manager] is set to [Other DB] at installation, "4.3.3.1 Updating the localdatabase(Database for Network Manager = Other DB) (page 118)"

• When the manager server and database server are the same server and [Database - Database forNetwork Manager] is set to [Bundle DB] at installation, "4.3.3.2 Updating the localdatabase(Database for Network Manager = Bundled DB) (page 119)"

• When the manager server and database server are different servers (remote databaseenvironment) and [Database - Database for Network Manager] is set to [Bundle DB] atinstallation, "4.3.3.3 Updating the remote database(Database for Network Manager = BundledDB) (page 119)"

NoteFor the setting of [Database - Database for Network Manager] at installation, see the value described in<Install folder>\FW\Manager\sg\wfdbmgr\WFDB.INI.

• For USE_DATABASE=SQL_SERVER, [Other DB] is set.• For USE_DATABASE=POSTGRESQL_WIN, [Bundle DB] is set.

4.3.3.1 Updating the local database(Database for NetworkManager = Other DB)







Tip• Do not insert a line feed in the command.


118

• 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



4.3.3.2 Updating the local database(Database for NetworkManager = Bundled DB)










4.3.3.3 Updating the remote database(Database for NetworkManager = Bundled DB)

Perform the following process on the database server.







119






• FTBase service






4.3.5 Applying the standard workflow templateImport the standard workflow template. For details, see the precautions in "4.1.8 Applying thestandard workflow template (page 115)".

4.3.6 Upgrading the SigmaSystemCenterSSC のバージョンアップ手順を記載する

4.3.7 Registering License to SigmaSystemCenterFor details on registering license to SigmaSystemCenter, see "2.15.1 Registering License toSigmaSystemCenter Function (page 79)".

4.4 Upgrading the Management Server Console4.4.1 Upgrading the Management Server Console




120











• MasterScope Virtual DataCenter Automation View


Confirm that [Up] is added to the components in the service whose service identifier youspecified when installing the Management Server Console.


Note• The default value of the service identifier of the Management Server Console is

[vDCMoMSvc]. The service identifier is the setting value displayed when you click [Service n]under [View] on the left tree.

• If the service identifier was changed during installation, or if multiple Management ServerConsoles are installed, the service identifier can be checked in the [Setting of ManagementServer View] screen of the Virtual DataCenter Automation Integrated Installer.


121

9. Click [Next].




4.5 Upgrading the VM Monitoring Server4.5.1 Stop the services

Stop the services in the order below.

• MasterScope UMF Operations Web Service__vDCRMProxy_n



4.5.2 Upgrading the VM Monitoring Server1. Insert the vDCA/NWA install DVD into the DVD drive.

















• The following components under services under [View] with the service identifier settingof [vDCRMProxy]


122


NoteThe service identifier is the setting value displayed when you click [Service n] under [View] onthe left tree.

In a version earlier than Version 2.2, confirm that [New] is added to the following componentunder [Manager]-[Service 103].


In Version 2.2 or later, confirm that [Up] is added to the following component under[Manager]-[Service 103].



9. Click [Next].




4.5.3 Updating the Database

4.5.3.1 Updating the local databaseWhen the manager server and database server are the same server, perform the procedures below.







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



123


4.5.3.2 Updating the remote databaseWhen the manager server and database server are different servers (remote database environment),update the database on the database server. (Log in as a user who can access the database as adatabase administrator.)














4.6 Upgrading the VM Monitoring Server Console4.6.1 Upgrading the VM Monitoring Server Console



124











Confirm that [Up] is added to the components in the service whose service identifier youspecified when installing the VM Monitoring Server Console.


Note• The default value of the service identifier of the VM Monitoring Server Console is

[vDCRMSvc]. The service identifier is the setting value displayed when you click [Service n]under [View] on the left tree.

• If the service identifier was changed during installation, or if multiple VM Monitoring ServerConsoles are installed, the service identifier can be checked in the [Setting of VM MonitoringServer View] screen of the Virtual DataCenter Automation Integrated Installer.

8. Click [Next].


125




4.7 Upgrading the ID Management ServerTo upgrade the ID management server MasterScope Identity Manager, extraction of the existing data,uninstallation of the current version ID management server, installation of the new version IDmanagement server, and reflection of the existing data are performed in this order.

4.7.1 Extracting the existing dataOpen the command prompt with the administrator authorization in the ID management server.

Set the access control setting to OFF with the “edconfig” command. For the password, enter thepassword of the administrator user of the ID management server (MasterScope Identity Manager).After that, create a working directory, and move to the directory. In the following example, theworking directory is the "C:\tmp\sm" directory.

> edconfig -h localhost -p 1389 -D cn=ldapAdministrator,c=JP -W -replace ldapAccessControl:OFF -applypassword? ******** (Password of the administrator user of the ID management server (MasterScope Identity Manager))

-----------------------The configuration information has been updated.replace ldapAccessControl:OFF

Execute the “edmgrt” command in the working directory on the command prompt. Extract data in aninteractive format. The input locations * and input values in interactive format are shown below.

> mkdir c:\tmp\sm> cd /d c:\tmp\sm> edmgrt1: output directory data2: input directory dataNo.?(default: 1) *1

### output work ###

hostname? (default: xxxx) localhost *2LDAP port (default: 389) 1389 *3Prefer IPv6?(y/n default:n) *4DN of root entry (default: c=JP ) *5Login DN (default: cn=ldapAdministrator,c=JP) *6

password? ******** *7

select configuration item1: minimum


126

2: select3: allNo.? (default: 1) *8

output file path (default: C:\Users\ADMINI~1\AppData\Local\Temp\1\edsldif)C:\tmp\sm *9

All directory data was outputted.

Now,would you like to load directory data?(y/n)? (default: y) n *10

Hit Any Key. :11

No. Item Value

1 No.? Press [Enter] without entering anything (default).

2 hostname? localhost

3 LDAP Port 1389

4 Prefer IPv6? Press [Enter] without entering anything (default).

5 DN of root entry Press [Enter] without entering anything (default).

6 Login DN Press [Enter] without entering anything (default).

7 password? Password of the administrator user of the current ID managementserver (MasterScope Identity Manager)

8 select configuration item 1 (default)

9 output file path Full path of the working directory

10 Now,would you like to loaddirectory data?

n

11 Hit Any Key. Press [Enter] without entering anything

Execute the following commands in the working directory on the command prompt. For thepassword, enter the password of the administrator user of the ID management server (MasterScopeIdentity Manager).

> move old-entry.ldif old-entry.ldif.bk One file has been moved.> edsearch -h localhost -p 1389 -D cn=ldapAdministrator,c=JP -W -b c=JP -s 2 -c 1.2.392.200003.2.3.6.15 -attr * -o old-entry.ldifpassword? ******** search entry count: xxxx

4.7.2 Uninstalling the ID management server of the currentversion

Uninstall MasterScope Identity Manager according to the procedure in "6.2.7 Uninstalling thecomponents of ID Management Server (page 165)".

4.7.3 Installing the ID management server of the new versionInstall MasterScope Identity Manager of the new version according to the procedure in"2.9.5 Installing the components of ID Management Server (page 47)".


127

Change the password of the administrator user of the ID management server (MasterScope IdentityManager) of the new version according to the procedure in "2.18.2 Changing the Password of theAdministrator User (page 92)". Change the password of the administrator user to the same passwordof the administrator user of the uninstalled ID management server (MasterScope Identity Manager).

NoteIf the password of the administrator user of the ID management server (MasterScope Identity Manager) ofthe new version is different from the password of the administrator user of the uninstalled ID managementserver (MasterScope Identity Manager), the procedure in the next section cannot be performed normally.Change the password to the same one.

4.7.4 Reflecting the existing dataOpen the command prompt with the administrator authorization in the ID management server(MasterScope Identity Manager), and move to the working directory created in "4.7.1 Extracting theexisting data (page 126)". In the following procedure, the working directory is assumed to be "C:\tmp\sm".

> cd /d c:\tmp\sm

Perform the following commands on the command prompt. For the password, enter the password ofthe administrator user of the ID management server (MasterScope Identity Manager).

> edconfig -h localhost -p 1389 -D cn=ldapAdministrator,c=JP -W -replace ldapAccessControl:OFF -applypassword? ******** Password of the administrator user of the ID management server (MasterScope Identity Manager)

-----------------------The configuration information has been updated.replace ldapAccessControl:OFF

Execute the “edmgrt” command in the working directory on the command prompt. Reflect data in aninteractive format. The input locations * and input values in interactive format are shown below.

> edmgrt

1: output directory data2: input directory dataNo.?(default: 1) 2 *1

### input work ###

hostname? (default: xxxx) localhost *2LDAP port (default: 389) 1389 *3Prefer IPv6?(y/n default:n) *4DN of root entry (default: c=JP ) *5Login DN (default: cn=ldapAdministrator,c=JP) *6

password? ******** *7input file path (default: C:\Users\ADMINI~1\AppData\Local\Temp\1\edsldif)c:\tmp\sm *8

Completed. All directory data was inputted.


128

Hit Any Key. *9

No. Item Value

1 No.? 2

2 hostname? localhost

3 LDAP Port 1389

4 Prefer IPv6? Press [Enter] without entering anything (default).

5 DN of root entry Press [Enter] without entering anything (default).

6 Login DN Press [Enter] without entering anything (default).

7 password? Password of the administrator user of the ID management server(MasterScope Identity Manager)

8 input file path Full path of the working directory

9 Hit Any Key. Press [Enter] without entering anything (default).

Perform the following commands on the command prompt. For the password, enter the password ofthe administrator user of the ID management server (MasterScope Identity Manager).

> edconfig -h localhost -p 1389 -D cn=ldapAdministrator,c=JP -W -replace ldapAccessControl:ON -apply

password? ******** Password of the administrator user of the ID management server (MasterScope Identity Manager)

The configuration information has been updated. replace ldapAccessControl:ON

If an SSL certificate other than the built-in SSL certificate of the ID management server(MasterScope Identity Manager) is used, the information of the SSL certificate is not transferred inthe procedure above. Perform the setting of the SSL certificate on the new ID management server(MasterScope Identity Manager) according to the procedure in 8.2.4 Setting the SSL Certificate inMasterScope Virtual DataCenter Automation Configuration Guide.

4.8 Upgrading the Managed MachineNote

For VMs that have been assigned by Virtual DataCenter Automation, upgrade them after upgrading themanagement server that manages the VMs.

4.8.1 Managed machine (Windows)

4.8.1.1 Stop the serviceIf the following service is active, stop it.

• MasterScope UMF Operations Agent_104

4.8.1.2 Upgrading the Managed Machine(Windows)1. Insert the vDCA/NWA install DVD into the DVD drive.


129











• MasterScope AsRiCommon Agent



• The following components under [Agent]-[Service 104]

- MasterScope MISSION CRITICAL OPERATIONS Agent

- MasterScope AsRiCommon Agent


9. Click [Next].




4.8.1.3 Upgrading the DeploymentManager client(Windows)Note

If the DeploymentManager client is not installed, the steps described in this section are not necessary.







130

5. Select [SigmaSystemCenter Client], and click [Run].

The [Welcome to the SigmaSystemCenter Setup Wizard] screen is displayed.

6. Click [Next].

The screen for selecting components to install is displayed.

7. Check all the check boxes of the following components to be installed, and then click the[Next] button.


131

• SigmaSystemCenter

• DPM Client 6.5

The [Specify the Windows Firewall setting] screen is displayed.

8. Select one of the radio buttons to specify the Windows firewall, and then click the [Next]button.

The [Configure DPM Client] screen is displayed.


132

9. Enter the IP address of the DeploymentManager management server, and click the [Next >]button. If it is omitted, a management server is automatically searched for after completion ofinstallation.

The [Install SigmaSystemCenter] screen is displayed.

10. Click [Install].

After all the components are installed, the [Finish] screen is displayed.

11. Click [Finish].

4.8.1.4 Start the serviceIf the following service is active before upgrade, start it.


4.8.2 Managed machine (Linux)



4.8.2.2 Cautions before UpgradingDepending on the environment, the files in the vDCA/NWA install DVD may not be executed due tothe execution right.

In this case, execute the following commands to copy the fw/Linux directory and Install/Linuxdirectory of the vDCA/NWA install DVD on a directory on the hard disk, execute the chmodcommand to give the execution right of all the files, and start install/Linux/vDCAInst.sh.


133

# mkdir -p /tmp/media# cd /mnt/dvd# tar cvf - ./fw/Linux | (cd /tmp/media; tar vxf -)# tar cvf - ./install/Linux | (cd /tmp/media; tar vxf -)# tar cvf - ./ssc | (cd /tmp/media; tar vxf -)# cd /tmp/media# chmod 755 -R .# cd ./install/Linux# ./vDCAInst.sh

4.8.2.3 Upgrading the Managed Machine(Linux)1. Log in to the system as user root.




# mount /mnt/dvd




# ./vDCAInst.sh








Enter 2[Enter].


134



************************************* MasterScope Installer*************************************

Please select the product which you'd like to install, and thenthe product installation programs which you select starts.

1. MasterScope Media

2. SigmaSystemCenter Client

Please select the operation.(1:MasterScope Media 2:SigmaSystemCenter q:quit program):

Enter 1[Enter].

(1:MasterScope Media 2:SigmaSystemCenter q:quit program):1

8. Subsequently, the following screen of MasterScope Media Installer is displayed

************************************* Welcome to MasterScope Media Installer !!*************************************

This program will install/uninstall products.

1. Install2. Uninstall

Please select the operation.(1:install 2:uninstall q:quit program):

Enter 1[Enter].

(1:install 2:uninstall q:quit program):1

9. A list of components that can be installed is displayed.

--------Products--------

1 [ ] MasterScope MISSION CRITICAL OPERATIONS Agent 4.3.0.1 [ 4.2.0.0 ]2 [ ] MasterScope MISSION CRITICAL OPERATIONS Logical Agent Agent 4.3.0.13 [ ] MasterScope SystemManager Agent 6.3.0.14 [ ] MasterScope SystemManager Logical Agent Agent 6.3.0.15 [ ] MasterScope Application Navigator Agent 4.2.0.1


135

6 [ ] MasterScope Application Navigator Logical Agent Agent 4.2.0.17 [ ] MasterScope AsRiCommon Agent 3.2.1.17 [ 3.2.1.14 ]

--------------------------------------------Please select product(s) by entering numbers separated by commas.[Example: 1, 3, 4](b:back q:quit program):

Select the following components.


• MasterScope AsRiCommon Agent

(b:back q:quit program):1,7

10. The confirmation screen of the components to be installed is displayed.

------------Confirmation------------

1 [*] MasterScope MISSION CRITICAL OPERATIONS Agent 4.3.0.1 [ 4.2.0.0 ]2 [ ] MasterScope MISSION CRITICAL OPERATIONS Logical Agent Agent 4.3.0.13 [ ] MasterScope SystemManager Agent 6.3.0.14 [ ] MasterScope SystemManager Logical Agent Agent 6.3.0.15 [ ] MasterScope Application Navigator Agent 4.2.0.16 [ ] MasterScope Application Navigator Logical Agent Agent 4.2.0.17 [*] MasterScope AsRiCommon Agent 3.2.1.17 [ 3.2.1.14 ]

--------------------------------------------These product(s) will be installed, OK to continue?(default:y y:yes n:no q:quit program):

Enter y[Enter] to continue.


11. The configuration setting screen of the components to be installed is displayed.

---------------------Installation settings---------------------

Agent 1 Service104 1.1 MasterScope MISSION CRITICAL OPERATIONS Agent 4.3.0.1 [ 4.2.0.0 ] 1.2 MasterScope AsRiCommon Agent 3.2.1.17 [ 3.2.1.14 ] 2 New ServiceRelayManager 3 New ServiceManager 4 New ServiceOther( Not Framework )


136

5 WebSAM vDC Automation Managed machine components 2.2.0.0 6 New Product

--------------------------------------------(*) marked products or services objects require specific settings beforeinstallation.--------------------------------------------Please select operation to perform from following commands.[Example: 's1' configure settings for first service listed above.]

(r[n.n]:remove s[n]:setting v[n]:view c:clear b:back q:quit program):

Enter e[Enter].

(a[n]:add r[n.n]:remove s[n]:setting v[n]:view c:clear b:back e:execute q:quit program):e

12. The [Final confirmation] screen is displayed.

------------------Final confirmation------------------

Agent 1 Service104 1.1 MasterScope MISSION CRITICAL OPERATIONS Agent 4.3.0.1 [ 4.2.0.0 ] 1.2 MasterScope AsRiCommon Agent 3.2.1.17 [ 3.2.1.14 ]

-------------------------------------------Is it OK to start installation?(default:y y:yes n:no q:quit program):

Enter y[Enter].


13. The installation status is displayed, and the installation result is displayed at the end. Checkthat no error has occurred.

MasterScope MISSION CRITICAL OPERATIONS Agent 4.3.0.1 Preparing for Installation (1/2)MasterScope MISSION CRITICAL OPERATIONS Agent 4.3.0.1 Installation in progress (1/2)check rcfileMasterScope MISSION CRITICAL OPERATIONS Agent 4.3.0.1 was successfully installed (1/2)MasterScope AsRiCommon Agent 3.2.1.17 Preparing for Installation (2/2)MasterScope AsRiCommon Agent 3.2.1.17 Installation in progress (2/2)check rcfileMasterScope AsRiCommon Agent 3.2.1.17 was successfully installed (2/2)

--------------------------------------------


137

Installation result--------------------------------------------1 MasterScope MISSION CRITICAL OPERATIONS Agent 4.3.0.1 (Success)2 MasterScope AsRiCommon Agent 3.2.1.17 (Success)--------------------------------------------Success:2, Failure:0

4.8.2.4 Upgrading the DPM Client(Linux)Note

If the DeploymentManager client is not installed, the steps described in this section are not necessary.

1. Log in to the system as user root.




# mount /mnt/dvd




# ./vDCAInst.sh








Enter 2[Enter].


138



************************************* MasterScope Installer*************************************

Please select the product which you'd like to install, and thenthe product installation programs which you select starts.

1. MasterScope Media

2. SigmaSystemCenter Client

Please select the operation.(1:MasterScope Media 2:SigmaSystemCenter q:quit program):

Enter 2[Enter].

(1:MasterScope Media 2:SigmaSystemCenter q:quit program):2

8. The installation status is displayed.

Start DPM Client Installer.

Stopping depagtd services: [ OK ]Client service was stopped.Service registration was canceled.The starting script was deleted.The countdown cancel command was deleted.Uninstallation of client service was completed.

9. The entry request for the DeploymentManager management server IP address is displayed. If itis omitted, a management server is automatically searched for after completion of installation.

Enter the IP address of the management server.(If you omit the IP address, the DPM client service searches the management server automatically, but it might take some time.)>

Enter the IP address of the DeploymentManager management server[Enter].

Starting depagtd services: [ OK ]Installation of client service was completed.





139

4.8.3 Managed machine (virtual base VMware ESXenvironment)


• MasterScope UMF Operations Agent_n


4.8.3.2 Managed machine (virtual base VMware ESXenvironment)

Start the Virtual DataCenter Automation Integrated Installer, and select [Custom] to start theMasterScope Framework Media Installer.

From the MasterScope Framework Media Installer, select [Install]. On the "Installation Selection"screen, select the following product.

Product name Type

MasterScope MISSION CRITICALOPERATIONS

Agent

On the "Product Installation Settings" screen, check that [Up] is assigned to the selected productname when installing.

For details on the installation procedure, see "2.13.5 Installing the components of ManagementAgent (page 61)".




4.8.4 Managed machine (virtual base Hyper-V environment)




4.8.4.2 Managed machine (virtual base Hyper-V environment)Start the Virtual DataCenter Automation Integrated Installer, and select [Custom] to start theMasterScope Framework Media Installer.

From the MasterScope Framework Media Installer, select [Install]. On the "Installation Selection"screen, select the following product.


140

Product name Type

MasterScope MISSION CRITICALOPERATIONS

Agent

On the "Product Installation Settings" screen, check that [Up] is assigned to the selected productname when installing.

For details on the installation procedure, see "2.13.5 Installing the components of ManagementAgent (page 61)".





141

Chapter 5. Upgrading from Network AutomationThis section describes the procedure to upgrade the functions from Network Automation to VirtualDataCenter Automation.

Contents5.1 Upgrading the Global Management Server...............................................................................143

5.2 Upgrading the Global Management Server Console.................................................................144

5.3 Upgrading the Management Server ..........................................................................................144

5.4 Upgrading the Management Server Console ............................................................................145

5.5 Upgrading the ID Management Server .....................................................................................146

Chapter 5. Upgrading from Network Automation

142

5.1 Upgrading the Global Management Server5.1.1 Preparation

Perform preparations required for operation of Virtual DataCenter Automation as a Globalmanagement server.

For details, see "2.2 Software Required to be Installed in Advance (page 10)", "2.3.1 ComponentsInstalled on the Global Management Server (page 17)" through "2.3.3 Setting up the WindowsFirewall (page 18)".

The settings that have been specified do not have to be specified again.

5.1.2 Registering the upgrade licenseRegister the license key of the Virtual DataCenter Automation upgrade license provided when youpurchased Virtual DataCenter Automation to the operation management function. Perform code wordapplication after upgrading.

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

1. Start the Network Automation Integrated Installer and upgrade the version of the Globalmanagement server.

For details on the installation procedure, see Chapter 3.1. Upgrading the Global ManagementServer in Network Automation Installation Guide.

2. Start the Virtual DataCenter Automation Integrated Installer. On the "Selection of Function"screen, select the function of [GlobalManager], check the [Overwrite product component.]check box, and perform installation.

For details on the installation procedure, see "2.3.4 Cautions before Performing Installation(page 18)" and "2.3.5 Installing the components of Global Management Server (page 18)".

5.1.4 Registering and setting up the Global managementserver

Perform license registration and setting of the Global management server.

License registration is performed after upgrading and installing the global management serverconsole.

Please be sure to register a license before registering a new company, see "2.14.7.1 Registering NewCompany (page 73)".

See "5.2 Upgrading the Global Management Server Console (page 144)".

Import the standard workflow template by referring to "4.1.8 Applying the standard workflowtemplate (page 115)".

For the global management server, perform the following setting by referring to "2.14 Registeringand Setting up the Global Management Server (page 64)".

• "2.14.7 Default Settings of Asset Management Function (page 73)"

• "2.14.7.1 Registering New Company (page 73)"


143

• "2.14.7.2 Setting up Agent Environment (page 74)"

• "2.14.8 Default Settings of Operation Management Function (page 76)"

Perform license registration and code word application only for AssetSuite and upgrade licensesregistered before upgrading.

5.2 Upgrading the Global Management ServerConsole5.2.1 Upgrade installation of the global management serverconsole

Upgrade the global management server console by overwriting the old version by using the VirtualDataCenter Automation Integrated Installer after updating the version of each component with theNetwork Automation Integrated Installer.

1. Start the Network Automation Integrated Installer and upgrade the version of the Globalmanagement server console.

For details on the installation procedure, see Chapter 3.2. Upgrading the Global ManagementServer Console in Network Automation Installation Guide.

2. Start the Virtual DataCenter Automation Integrated Installer. On the "Selection of Function"screen, select the function of [GlobalManager View], check the [Overwrite productcomponent.] check box, and perform installation.

For details on the installation procedure, see "2.4.2 Cautions before Performing Installation(page 23)" and "2.4.3 Installing the components of Global Management Server Console (page23)".

5.3 Upgrading the Management Server5.3.1 Preparation

Perform preparations required for operation of Virtual DataCenter Automation as a managementserver.

For details, see "2.2 Software Required to be Installed in Advance (page 10)", "2.5 Installing thecomponents of Management Server (page 26)" through "2.5.7 Cautions before PerformingInstallation (page 29)".

The settings that have been specified do not have to be specified again.

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

1. Start the Network Automation Integrated Installer and upgrade the version of the Managementserver.

For details on the installation procedure, see Chapter 3.3. Upgrading the Management Serverin Network Automation Installation Guide.


144

2. Start the Virtual DataCenter Automation Integrated Installer. On the "Selection of Function"screen, select the function of [Management Server], check the [Overwrite product component.]check box, and perform installation.

For details on the installation procedure, see "2.5.7 Cautions before Performing Installation(page 29)" and "2.5.8 Installing the components of Management Server (page 29)".

During upgrading and installation, the following setting items can be specified. Specify them asneeded.

• [VM Monitoring Server/Agent Port]

• [ESMPRO/ServerManager - Administrator Name]

• [ESMPRO/ServerManager - Administrator’s Password]

• [DeploymentManager - Management Server’s IP Address]

5.3.3 Registering and Setting up the Management ServerPerform license registration and setting of the management server.

License registration is performed after upgrading and installing the management server console.

See "5.4 Upgrading the Management Server Console (page 145)".

Import the standard workflow template.

For the management server, perform the following setting by referring to "2.15 Registering andSetting up the Management Server (page 79)".

• "2.15.5 Default Settings of Operation Management Function (page 82)"

• "2.15.6 Setting the Monitoring Definition of Management Server Performance Monitoring(page 82)"

• "2.15.8 Setting the Accumulation Period of Statistical Information (page 84)"

Perform license registration only for the SigmaSystemCenter function.

5.4 Upgrading the Management Server Console5.4.1 Upgrade installation of the management server console

Upgrade the management server console by overwriting the old version by using the VirtualDataCenter Automation Integrated Installer after updating the version of each component with theNetwork Automation Integrated Installer.

1. Start the Network Automation Integrated Installer and upgrade the version of the managementserver console.

For details on the installation procedure, see Chapter 3.4. Upgrading the Management ServerConsole in Network Automation Installation Guide.

2. Start the Virtual DataCenter Automation Integrated Installer. On the "Selection of Function"screen, select the function of [Management Server View], check the [Overwrite productcomponent.] check box, and perform installation.

For details on the installation procedure, see "2.6.2 Cautions before Performing Installation(page 35)" and "2.6.3 Installing the components of Management Server Console (page 35)".


145

5.5 Upgrading the ID Management Server5.5.1 Changing the registry

Change the value of InstType of the following registry key from NWA to VDCA.

• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\vDCAInst\SecureMaster


146

Chapter 6. Performing UninstallationThis chapter describes how to uninstall the components.

Contents6.1 Before Uninstallation ...............................................................................................................148

6.2 Uninstalling the Components Installed on Windows ................................................................148

6.3 Uninstalling the components installed in Linux........................................................................170

Chapter 6. Performing Uninstallation

147

6.1 Before UninstallationRead this section before starting uninstallation of the components.

6.1.1 Precautions before Uninstallation• Be sure to exit all applications and Web browsers being used before starting the uninstallation.

• The setting file is deleted after the uninstallation. Back up the file as needed.

• When using the installer on Windows Server 2008, the [User Account Control] dialog box maybe displayed. If this dialog box is displayed, click [Allow] and continue the uninstallation.

6.2 Uninstalling the Components Installed onWindows

The subsequent sections describe how to uninstall the installed components.

6.2.1 Uninstalling the components of Global ManagementServer

1. Stop the following services in advance.



(The "n" at the end digit should be 1 or greater number. The number varies depending onthe installation environment.)

2. Execute the following command to delete database files.

> cd C:\Program Files (x86)\NEC\vDCA\GM\FW\Manager\sql\sqlserver> WfdbDropDB.bat <Database Name> <DB Server Name> FWCMDB <sa Password>

TipConfirm the value of DATABASE_NAME and SERVER_NAME where the <Database Name> and<DB Server Name> was indicated on following file.C:\Program Files (x86)\NEC\vDCA\GM\FW\Manager\sg\wfdbmgr\WFDB.INI






148





149

8. Select the [Uninstall] radio button, and click [Next].

The [Uninstallation Selection] screen is displayed.



- MasterScope AsRiCommon Manager

- MasterScope AssetSuite Manager



• The following components under services under [View] with the service identifier settingof [vDCGMProxy]


NoteIf the Global Management Server and Management Server are installed on the same machine,two "MasterScope Virtual DataCenter Automation WebService Views" appear in the[Uninstallation Selection] screen. For the Global Management Server, select the componentswith the service identifier setting of [vDCGMProxy]. The service identifier is the setting valuedisplayed when you click [Service n] under [View] on the left tree.


150

• The following components under [Non Framework Product]

- Application Server

- MasterScope vDC Automation Service Governor

- MasterScope vDC Automation Portal

NoteIf [MasterScope vDC Automation Service Governor WebAPI Base Option] is already installed,uninstall [MasterScope vDC Automation Service Governor WebAPI Base Option] by referringto MasterScope vDC Automation ServiceGovernor WebAPI Base Option Installation Guidebefore uninstalling global management server.If [MasterScope vDC Automation Service Governor WebAPI Base Option] is not installed,delete the following file.

- <Install folder>\FW\Tomcat\conf\fwapi.properties

NoteComponents may not be displayed under [Non Framework Product]. This is not a problembecause you can uninstall them by using the following procedure.

10. Click [Next].

The [Uninstallation Confirmation] screen is displayed.

11. Check [Target products:], and click [Start].

Uninstallation of the selected components is performed. When uninstallation is complete, the[Finish] screen is displayed.

12. Click [Finish].

13. Delete Application Server(Tomcat) Service.

This procedure is not necessary if you uninstall components under [Non Framework Product]with "9. (page 150)".


151

Execute the following command to delete Application Server(Tomcat) Service.

> set "CATALINA_HOME=<Install folder>\FW\Tomcat"> "<Install folder>\FW\Tomcat\bin\service.bat" remove ServiceGovernor

After the deletion of service is complete, delete the following folders.

• C:\Program Files (x86)\NEC\vDCA\GM\FW\Tools

• C:\Program Files (x86)\NEC\vDCA\GM\FW\Tomcat

NoteJava that has been installed cannot be uninstalled. Uninstall other programs that are not used.

14. If upgraded from earlier than Version 2.2, uninstall the following components in [Programsand Features] on the Control Panel.

• WebOTX Application Server ExpressAfter the deletion of WebOTX is complete, delete the following folders.

• <Install folder>\FW\Tools

• <Install folder>\FW\WebOTX

15. If SQL Server is not used in other components in an environment where SQL Server isinstalled on the machine of the Global Management Server, SQL Server can be uninstalledfrom the machine of the Global Management Server. Uninstall SQL Server by referring to"6.2.11 Uninstalling SQL Server (page 169)".

16. If SQL Server is not used in other components on the Global Management Server when theDBMS and Global Management Server are on separate servers, the SQL Server client toolscan be uninstalled from the machine of the Global Management Server. Uninstall the SQLServer client tools by referring to "6.2.10 Uninstalling the SQL Server Client Tools (page168)".

17. Delete the following registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\vDCAInst\GM

• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\vDCAInst\APServer

• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\vDCAInst\Portal

• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\vDCAInst\ServiceGovernor

18. The "Install Directory Path" specified during installation may remain. Delete it if it isunnecessary.

6.2.2 Uninstalling the components of Global ManagementServer Console






152







• The following components under [vDCGMSvc]

- MasterScope AsRiCommon View

- MasterScope AssetSuite View

- MasterScope MISSION CRITICAL OPERATIONS View

- MasterScope Virtual DataCenter Automation View

8. Click [Next].




10. Click [Finish].


• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\vDCAInst\GM_SVC


153


6.2.3 Uninstalling the components of Management ServerNote

Before doing this procedure, please see 16.2 Deleting a Management Server in Virtual DataCenterAutomation Configuration Guide, put the procedure into effect.

1. Stop all DeploymentManager services.

2. Select [SigmaSystemCenter] in [Programs and Features] in Control Panel, and click[Uninstall].

The [Welcome to the SigmaSystemCenter Uninstall Wizard] screen is displayed.

3. Click [Next].

The screen for selecting components to uninstall is displayed.


154

4. Check all the check boxes of the following components to be uninstalled, and then click the[Next] button.

• SigmaSystemCenter

• SystemProvisioning 6.5

• SystemMonitor- Performance Monitoring Services 5.7

• DPM server 6.5

• ESMPRO/ServerManager 6.10

The [Configure SystemProvisioning] screen is displayed.


155

5. Select one of the radio buttons to delete the ports from the Windows Firewall exception list,and click [Next].

The [Configure NEC ESMPRO Manager] screen is displayed.

6. Select one of the radio buttons to delete the preservation folder of the update package, andclick [Next].

The [Uninstall SigmaSystemCenter] screen is displayed.


156

7. Click [Uninstall].

After all the components are uninstalled, the [Finish] screen is displayed.

NoteAfter the uninstallation of NEC ESMPRO Manager, the message "This program might not haveuninstalled correctly" may be displayed after completing the uninstallation, depending on theenvironment. The uninstallation has been completed without any errors. Click [This programuninstalled correctly] or [Cancel] to finish.

8. If a dialog box prompting you to restart the system is displayed, restart the system.

9. Stop the following services in the following order.






• FTBase service


> cd C:\Program Files (x86)\NEC\vDCA\MoM\FW\Manager\sql\sqlserver> WfdbDropDB.bat <Database Name> <DB Server Name> FWCMDB <sa Password>

TipConfirm the value of DATABASE_NAME and SERVER_NAME where the <Database Name> and<DB Server Name> was indicated on following file.


157

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

If [Other DB] is set to [Database - Database for Network Manager] in the installation setting,execute the following command.(Default value is [Other DB])

> NvPRODropDB.bat nvprodb localhost FWCMDB











• e following components under [Manager]-[Service 102]


- MasterScope Network Manager Manager

- MasterScope vDC Automation Manager

• The following components under services under [View] with the service identifier settingof [vDCMoMProxy]

- MasterScope vDC Automation WebService View

NoteIf the Global Management Server and Management Server are installed on the same machine,two "MasterScope vDC Automation WebService View" appear in the [Uninstallation Selection]screen. For the Management Server, select the components with the service identifier setting of[vDCMoMProxy]. The service identifier is the setting value displayed when you click [Servicen] under [View] on the left tree.

18. Click [Next].




20. Click [Finish].

21. If SQL Server is not used in other components in an environment where SQL Server isinstalled on the machine of the Management Server, SQL Server can be uninstalled from themachine of the Management Server. Uninstall SQL Server by referring to"6.2.11 Uninstalling SQL Server (page 169)".


158

22. If SQL Server is not used in other components on the Management Server when the DBMSand Management Server are on separate servers, the SQL Server client tools can be uninstalledfrom the machine of the Management Server. Uninstall the SQL Server client tools byreferring to "6.2.10 Uninstalling the SQL Server Client Tools (page 168)".

23. Delete the setting items of the Management Server set in "2.14.6 Setting up the Property Filefor the Service Governor (page 70)", and execute the following command on the GlobalManagement Server to reflect the change.



• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\vDCAInst\MOM


6.2.4 Uninstalling the components of Management ServerConsole











159

7. Select the check boxes of the following components under the services with the serviceidentifier specified during installation of the Management Server Console.





Note• The default value of the service identifier of the Management Server Console is

[vDCMoMSvc]. The service identifier is the setting value displayed when you click [Service n]under [View] on the left tree.

• If the service identifier was changed during installation, or if multiple Management ServerConsoles are installed, the service identifier can be checked in the [Setting of ManagementServer View] screen of the Virtual DataCenter Automation Integrated Installer.


160

8. Click [Next].




10. Click [Finish].


• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\vDCAInst\MOM_SVC_<service identifier>

NoteThe default value of the service identifier of the Management Server Console is [vDCMoMSvc]. Ifthe service identifier was changed during installation, or if multiple Management Server Consoles areinstalled, the service identifier can be checked in the procedure above.


6.2.5 Uninstalling the components of VM Monitoring ServerNote

Before doing this procedure, please see 16.4 Deleting a VM Monitoring Server in Virtual DataCenterAutomation Configuration Guide, put the procedure into effect.

1. Stop the following services in advance.




161



> cd C:\Program Files (x86)\NEC\vDCA\GM\FW\Manager\sql\sqlserver> WfdbDropDB.bat <Database Name> <DB Server Name> FWCMDB <sa Password>

TipConfirm the value of DATABASE_NAME and SERVER_NAME where the <Database Name> and<DB Server Name> was indicated on following file.C:\Program Files (x86)\NEC\vDCA\GM\FW\Manager\sg\wfdbmgr\WFDB.INI














• The following components under services under [View] with the service identifier settingof [vDCRMProxy]


NoteThe service identifier is the setting value displayed when you click [Service n] under [View] onthe left tree.

10. Click [Next].



Uninstallation of the selected components is performed.When uninstallation is complete, the[Finish] screen is displayed.

12. Click [Finish].

13. If SQL Server is not used in other components in an environment where SQL Server isinstalled on the machine of the VM Monitoring Server, SQL Server can be uninstalled from


162

the machine of the VM Monitoring Server. Uninstall SQL Server by referring to"6.2.11 Uninstalling SQL Server (page 169)".

14. If SQL Server is not used in other components on the VM Monitoring Server if the DBMS andVM Monitoring Server are on separate servers, the SQL Server client tools can be uninstalledfrom the machine of the VM Monitoring Server. Uninstall the SQL Server client tools byreferring to "6.2.10 Uninstalling the SQL Server Client Tools (page 168)".

15. Delete the setting items of the VM Monitoring Server set in "2.14.6 Setting up the PropertyFile for the Service Governor (page 70)", and execute the following command on the GlobalManagement Server to reflect the change.



• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\vDCAInst\RM


6.2.6 Uninstalling the components of VM Monitoring ServerConsole











163

7. Select the check boxes of the following components under the services with the serviceidentifier specified during installation of the VM Monitoring Server Console, and click [Next].



Note• The default value of the service identifier of the VM Monitoring Server Console is

[vDCRMSvc].• If the service identifier was changed during installation, or if multiple VM Monitoring Server

Consoles are installed, the service identifier can be checked on the [Setting of VM MonitoringServer View] screen of the Virtual DataCenter Automation Integrated Installer.


164

8. Click [Next].




10. Click [Finish].


• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\vDCAInst\RM_SVC_<service identifier>

NoteThe default value of the service identifier of the Management Server Console is [vDCRMSvc]. If theservice identifier was changed during installation, or if multiple VM Monitoring Server Consoles areinstalled, the service identifier can be checked in the procedure above.


6.2.7 Uninstalling the components of ID Management Server• To uninstall the ID Management Server from the machine that is the remote desktop session

host server.

Tip[Control Panel] - [program] when "remote desktop Installation of application to a server" checks thescreen and doesn't exist, remote desktop service doesn't consist of it. Perform procedure of "Touninstall the ID Management Server from the machine that is not the remote desktop session hostserver.".


165

(Exsample: Windows Server 2008 R2)


2. Select [Control Panel (C)] - [Install Application on Remote Desktop Server] from the[Start] menu.

3. The [Install Program From Floppy Disk or CD-ROM] screen is displayed. Click [Next].

4. The [Run Install Program] screen is displayed. Specify the following command, and click[Next].

> <Install DVD>:\securemaster\sminstaller.exe -v -uninstall vdc

5. Uninstallation processing starts. It is complete when the following message is displayed.

Reading ini file...Checking ini file...Uninstalling EIM...Uninstalling EFT...Uninstalling EDS...

• To uninstall the ID Management Server from the machine that is not the remote desktop sessionhost server.


2. Open the command prompt window, and execute the following commands.

> <Install DVD>:\securemaster\sminstaller.exe -v -uninstall vdc3. Uninstallation processing starts. It is complete when the following message is displayed.

Reading ini file...Checking ini file...Uninstalling EIM...Uninstalling EFT...Uninstalling EDS...

If uninstallation processing is completed, put below into effect.

1. Delete the ID management server MasterScope Identity Manager installation folder specifiedin "2.9.5 Installing the components of ID Management Server (page 47)". Default value ofInstall folder is the following.

C:\Program Files (x86)\NEC\vDCA\SM


• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\vDCAInst\SecureMaster

6.2.8 Uninstalling the components of Managed MachineNote

Start from Step 1 if the DeploymentManager client is installed, or from Step 5 otherwise.

1. From [Programs and Features] on the Control Panel, select [DeploymentManager], and click[Uninstall].


166

2. The [DeploymentManager Setup Type] screen is displayed. Select [Uninstall] and click [Next].

3. In the displayed confirmation dialog box, click [OK] to uninstall.

4. When the message "Maintenance Completed" is displayed, uninstallation is complete.











• The following components under [Agent]-[Service 104]

- MasterScope MISSION CRITICAL OPERATIONS Agent

- MasterScope AsRiCommon Agent

12. Click [Next].




14. Click [Finish].


• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\vDCAInst\AG


NoteWhen bringing this virtual machine into vDC Automation as a VM image once again, it's necessary to deletethe following file left behind the uninstallation(.WebSAMUMFID)

• For 32-bit environments%CommonProgramFiles%\NEC\WebSAM\Framework\.WebSAMUMFID

• For 64-bit environments%CommonProgramFiles(x86)%\NEC\WebSAM\Framework\.WebSAMUMFID

6.2.9 Uninstalling the components of Management Agent1. Insert the vDCA/NWA install DVD into the DVD drive.


167









7. Select the check boxes of the following components under the services with the serviceidentifier specified during installation of the Management Agent.


8. Click [Next].




10. Click [Finish].


NoteWhen bringing this virtual machine into vDC Automation as a VM image once again, it's necessary to deletethe following file left behind the uninstallation (.WebSAMUMFID)

• For 32-bit environments%CommonProgramFiles%\NEC\WebSAM\Framework\.WebSAMUMFID

• 6For 64-bit environments%CommonProgramFiles(x86)%\NEC\WebSAM\Framework\.WebSAMUMFID

6.2.10 Uninstalling the SQL Server Client ToolsPerform this to install the Global Management Server, Management Server, and VM MonitoringServer if the DBMS is on a separate server.

If SQL Server is not used in other components, delete the SQL Server client tools. The method ofuninstalling the SQL Server 2014 client tools is described below.

1. Select [Microsoft SQL Server 2014] from the list in the [Uninstall or change a program]screen, and click [Uninstall].

2. On the screen displayed, click [Remove].

The [Setup Support Rules] screen is displayed.

3. Click [OK].

The [Select Features] screen is displayed.


168

4. Click [Select All], and click [Next].

The [Removal Rules] screen is displayed.

5. Click [Next].

The [Ready to Remove] screen is displayed.

6. Click [Remove].

The [Complete] screen is displayed.

7. Click [Close].

8. On the [Uninstall or change a program] screen, uninstall the following programs.

• Microsoft SQL Server 2008 R2 management object

• Microsoft SQL Server 2014 Native Client

• Microsoft SQL Server System CLR Types

6.2.11 Uninstalling SQL ServerDelete SQL Server from the Global Management Server, Management Server, and VM MonitoringServer. Also, when the DBMS is installed on a separate server, delete SQL Server from the DBserver. The method of uninstalling SQL Server 2014 is described below.

1. Select [Microsoft SQL Server 2014] from the list in the [Uninstall or change a program]screen, and click [Uninstall].

2. On the screen displayed, click [Remove].

The [Setup Support Rules] screen is displayed.

3. Click [OK].

The [Select Instance] screen is displayed.

4. Select [FWCMDB] from the [Instance to remove features from:] drop-down list, and click[Next].

The [Select Features] screen is displayed.

5. Click [Select All], and click [Next].

The [Removal Rules] screen is displayed.

6. Click [Next].

The [Ready to Remove] screen is displayed.

7. Click [Remove].

The [Complete] screen is displayed.

8. Click [Close].

9. On the [Uninstall or change a program] screen, uninstall the following programs.

• Microsoft SQL Server 2008 setup support file

• Microsoft SQL Server 2014 Transact-SQL ScriptDom

• Microsoft SQL Server 2014 Setup (Japanese)

• SQL Server 2014 for SQL Server Browser


169

6.2.12 Uninstalling VMware vSphare PowerCLI1. Select [VMware vSphare PowerCLI] from the list in the [Uninstall or change a program]

screen, and click [Uninstall].

2. When the uninstallation confirmation screen is displayed, click [Yes].

3. Select [VMware VIX] from the list in the [Uninstall or change a program] screen, and click[Uninstall].

4. When the uninstallation confirmation screen is displayed, click [Yes].

6.3 Uninstalling the components installed inLinux6.3.1 Cautions before Performing Uninstallation

Depending on the environment, the files in the vDCA/NWA install DVD may not be executed due tothe execution right.

In this case, execute the following commands to copy the fw/Linux directory and Install/Linuxdirectory of the vDCA/NWA install DVD to a directory on the hard disk, execute the chmodcommand to give the execution right of all the files, and start install/Linux/vDCAInst.sh.

# mkdir -p /tmp/media# cd /mnt/dvd# tar cvf - ./fw/Linux | (cd /tmp/media; tar vxf -)# tar cvf - ./install/Linux | (cd /tmp/media; tar vxf -)# cd /tmp/media# chmod 755 -R .# cd ./install/Linux# ./vDCAInst.sh

6.3.2 Uninstalling the components of Managed MachineThe procedure for uninstalling the components of the Managed Machine (Linux) is described below.

1. Log into the system with the root account.




# mount /mnt/dvd




# ./vDCAInst.sh



170

NoteIf the installation screen is unstable, set the environment variable TERM to vt100, and start theinstaller again.

*************************************MasterScope Installer*************************************Welcome to MasterScope installer.1. Typical : installs all products necessary to the function type of MasterScope Virtual DataCenter Automation you select. (Recommendation)2. Custom : allows you to install the necessary products to the function type of MasterScope Virtual DataCenter Automation separately.


Enter 1[Enter].


7. The following screen is displayed.

************************************* Welcome to MasterScope Installer !!*************************************This program will install/uninstall products.

2. Uninstall

Please select the operation.(2:uninstall q:quit program):

Enter 2[Enter].

(2:uninstall q:quit program):2

8. A list of installed components is displayed.

-----------------Installed products----------------- Agent 1 Service104 1.1 MasterScope MISSION CRITICAL OPERATIONS Agent 4.3.0.1 1.2 MasterScope AsRiCommon Agent 3.2.1.17 Other 2 MasterScope Virtual DataCenter Managed machine components--------------------------------------------Please select product(s) by entering numbers separated by commas.


171

[Example: 1.1, 2.1](v[n]:view b:back q:quit program):

Select MasterScope Virtual DataCenter Managed machine components as shown below.

(v[n]:view b:back q:quit program):2

9. The confirmation screen of the components to be uninstalled is displayed.

------------------Final confirmation------------------ Other 2 MasterScope Virtual DataCenter Managed machine components-------------------------------------------Is it OK to start uninstallation?(y:yes n:no q:quit program):

Enter y[Enter].

(y:yes n:no q:quit program):

The selected components are uninstalled.

NoteWhen bringing this virtual machine into vDC Automation as a VM image once again, it's necessary to deletethe following file left behind the uninstallation (.WebSAMUMFID)/var/opt/WebSAM/Framwork/.WebSAMUMFID


172

Chapter 7. TroubleshootingThis section specifies how to proceed when failure occurs during the installation, upgradeinstallation, and uninstallation of Virtual DataCenter Automation.

Contents7.1 SigmaSystemCenter Troubleshooting.......................................................................................174

7.2 Troubleshooting for the Installer ..............................................................................................175

7.3 Operation and Asset Management Functions Troubleshooting .................................................178

Chapter 7. Troubleshooting

173

7.1 SigmaSystemCenter Troubleshooting7.1.1 Messages during ESMPRO/ServerManager Installation /Uninstallation

• [Phenomenon]

In Windows Server 2008 R2, a message that explorer operation has stopped may be displayedduring the ESMPRO/ServerManager installation/uninstallation.

• [Message]

Windows Explorer has stopped working

• [Cause]

The message is issued because of a compatibility problem with the installation software.

• [Action]

No actions are required. No actions are required. The installation and uninstallation have beencompleted normally. The system is operating normally.

7.1.2 Messages after ESMPRO/ServerManager Uninstallation• [Phenomenon]

After the ESMPRO/ServerManager uninstallation, the following error message may bedisplayed.

• [Message]

'setup.exe' Make sure you typed the name correctly, and then try again. To search for a file, clickthe Start button, and then click Search.

• [Cause]

Failure of InstallShield 2008.

• [Action]

No actions are required. The uninstallation has been completed normally. The system isoperating normally.

7.1.3 After Installation to Windows Server 2008 ManagementServer, Web Console Does Not Start.

• [Phenomenon]

After installing Virtual DataCenter Automation to Windows Server 2008 Management Server,the following message may be displayed, and the SystemProvisioning Web Console may notstart.

• [Message]

Your browser doesn’t support JavaScript.

• [Cause]

Because the [Static Content] was not added to [Role Services] of "Web server (IIS)" before theVirtual DataCenter Automation installation, the StaticFile handler for the Virtual DataCenterAutomation Web console deployed to IIS was not set appropriately.


174

• [Action]

Firstly, confirm that [Static Content] has been already installed in [Role Services] of "Webserver (IIS)". If [Static Content] has not been installed, click [Add Role Services] to install it.

Next, follow the procedures below to add the StaticFile handler.

1. In the [Start] menu, select [Administrative Tools] and then [Internet Information Services(IIS) Manager] to start the Internet Information Services (IIS) Manager.

2. In the [(default value: machine name)] node on the left side tree view, select [Sites],[Default Web Site], and then [Provisioning] to open "Provisioning Home".

3. Double-click the [Handler Mappings] icon to open it.

4. By double-clicking or right-clicking [StaticFile] and clicking [Edit…], the [Edit ModuleMapping] dialog box is displayed.

5. Confirm that”StaticFileModule” exists in [Module:] of the [Edit Module Mapping] dialogbox. Add it in case you cannot find it.

6. Click [OK].

7.2 Troubleshooting for the Installer7.2.1 A restart is requested during installation of theManagement Server.

• [Phenomenon]

A system restart is requested during installation of the Management Server.

• [Cause]

A restart may be required for installation of the SigmaSystemCenter component on theManagement Server.

• [Action]


175

Confirm that .Net Framework 4.5.2 has been installed. For details about the method ofinstalling .Net Framework 4.5.2, see "2.2.5 Installing .Net Framework 4.5.2 (page 12)".

After installing .Net Framework 4.5.2, start up the Virtual DataCenter Automation IntegratedInstaller again to install Management Server.

• [Phenomenon]

A system restart is requested during installation of the Management Server.

• [Cause]

A restart may be required for installation of the SigmaSystemCenter component on theManagement Server.

• [Action]

After restarting the system, start the Virtual DataCenter Automation Integrated Installer again toinstall the Management Server.

7.2.2 An error occurs during installationWhen installation fails, the error code (err=xxx) is displayed on the installation termination screen.

The details, cause, and action of the error are as follows.

For errors of SigmaSystemCenter and DeploymentManager client, see SigmaSystemCenterInstallation Guide.

Code Description Cause / Action

51 No administrator authorization The user lacks administrator authorization. The user must beauthorized as an administrator.

52 Double-start error Double installer start-up. Confirm whether another installationprocess is going on simultaneously.

54 Recovery error at start-up Recovery at start-up failed. Contact the product customer service.


176

Code Description Cause / Action

55 Temporary folder access error Cannot access the temporary folder (environment variable:%TMP% or %TEMP%). Confirm whether a temporary folderexists and can be written.

56 Install location folder accesserror

Cannot access the install location folder. Confirm whether thefolder can be written.

57 File expansion failure The attempt to expand the file failed. Confirm whether thetemporary folder capacity is available.

59 Incorrect installation path The installation path is not correct. Confirm whether the correctdrive or folder was specified.

61 Downgrade error A newer version of the product has been installed. Confirm theproduct installation status.

63 Service stop error Stopping the service failed. Stop using for a certain period oftime or restart after stopping the related services.

65 Failure in copying file to aninstall location (file busy)

A file in the install location folder is busy. Stop using for acertain period of time or restart after stopping the services.

66 Failure in copying file to atemporary folder (disk full)

The temporary folder capacity is small. Confirm the availablecapacity.

67 Failure in copying file to aninstall location (disk full)

The install folder capacity is small. Confirm the availablecapacity.

68 Failure in copying file to atemporary folder

The temporary folder capacity is small or unable to access thefolder. Confirm whether a temporary folder exists and can bewritten.

69 Failure in copying file to aninstall location

The install folder capacity is small or unable to access the folder.Confirm whether an install location folder can be written.

Others - Collect the failure information by the procedure in"7.2.3 Collecting Failure Information (page 177)" , and contactthe product customer service.

7.2.3 Collecting Failure InformationIf an error that is not described in this document occurs during the installation, collect the failureinformation by the following procedure and contact the product customer service:

In case of installation through the remote desktop connection of Windows, perform the proceduresbelow without cutting the session where the error occurred:

Note that failure information may be deleted when a session is disconnected.

• [For Windows]

- For Typical mode

1. Open the following path with the explorer:

In default case, install folder is C:\Program Files (x86)\NEC\vDCA\FW,

the path is C:\Program Files (x86)\NEC\vDCA .

2. Right-click the "inst_log""folder. Select [Send to]-[Compressed(zipped) folder].

3. Collect the "inst_log.zip" created.

4. Send the collected file when contacting the product customer service.

- For Custom mode


177

1. Open the following path with the explorer:

%TEMP%

2. Right-click the "vDCAInstall.log" and "MASTERSCOPE_FW_LOG" folder underthe opened folder. Select [Send to]-[Compressed(zipped) folder].

3. Collect the "MASTERSCOPE_FW_LOG.zip" created.


• [For Linux]

1. Log in to the system with the root.

2. Perform the following command:

# cd /tmp# tar czvf WEBSAM_FW_LOG.tar.gz WEBSAM_FW_LOG

3. Collect the created "/tmp/MASTERSCOPE_FW_LOG.tar.gz" file.


7.3 Operation and Asset Management FunctionsTroubleshooting7.3.1 The console cannot be started.

• [Phenomenon]

The following dialog is displayed when the console of the operation management function andasset management function is started, and the console cannot be started. The login dialog box isnot displayed.

• [Cause]

This may be due to the following causes.

- "Manager Hostname" or "Manager Port" specified during installation of the console iswrong.

- The communication is blocked by Windows Firewall.

- The manager service has not been started.

7.3.2 An error dialog is displayed as the console starts up• [Phenomenon]


178

The following error dialog is displayed when the console of the operation management functionstarts up.

• [Cause]

The following service may not be started: Confirm that the service is started.

- NvPRO Base Manager

The above service does not start normally if the database is not set correctly.

7.3.3 Context Menu of [Asset Management] Node Is NotDisplayed

• [Phenomenon]

After the console of the asset management function starts up, the context menu is not displayedwhen you right-click the [Asset Management] node in the tree view.

• [Cause]

This may be due to the following causes. Actions are required for each cause:

- The database setting has not been completed.


179

- The database connection is timed out.

The database connection process may be timed out depending on the environment. In thiscase, adjust the time out settings by the procedure below:

1. Edit the configuration file:

Open the file "C:\Program Files (x86)\NEC\vDCA\GM\FW\Manager\sg\AsTopology\AsTopologyMgr.ini" with the text editor such as a memo pad andchange the following setting value:

[DBReConnect]RetryConnectCount=1RetryWaitTime=10000

2. Each setting is described below:

Setting Value

RetryConnectCount

Specify the retry number for the database connection failure. The defaultvalue is 1.

RetryWaitTime Set the wait time until the connection processing time out. If setting a largevalue, the starting process may take longer. The default value is "10000",and the unit is millisecond.

3. Restart the following services after editing:

* MasterScope UMF Operations Manager_101

- [Windows Authentication] is selected as the SQL Server [Authentication].

"Mixed Mode (SQL Server authentication and Windows authentication)" may not beselected in step 15 of Installing SQL Server 2014 in "2.2.6 Installing SQL Server (page12)".

7.3.4 Collecting Failure InformationFor the operation and asset management functions, if an error that is not described in this documentoccurs, use the information collection tool included with the vDCA/NWA install DVD to collect thefailure information.

For the environment in which Virtual DataCenter Automation Ver3.0 is installed, specify the shareddisk before collecting information.

• [Information collection tool for Windows]

<Install DVD>:\fw\tools\dawebsaminfo\Windows\

• [Information collection tool for Linux]

<Install DVD>:\fw\tools\dawebsaminfo\UNIX\

For details of using this tool, see the included "relmemo_sjis.txt (or elmemo_euc.txt)" file.


180

Appendix A. Revision History• First edition (June. 2016): Newly created

Appendix A. Revision History

181

Appendix B. License InformationThis product partially includes open-source software. For details of the licensing conditions of thesoftware, please refer to the following files included. The source code is released based on LGPL.Please make inquiries if replication, alteration, or distribution of the open-source software is desired.

<Install DVD>:\oss_license• PXE Software Copyright (C) 1997 - 2000 Intel Corporation.

• This product includes JRE (Java Runtime Environment) distributed by Oracle Corporation at nocharge. You must agree to the licensing conditions for use. For details of the copyright orproperty, refer to the following LICENSE files. Folder in which JRE is installed\LICENSE

• Some icons used in this program are based on Silk Icons released by Mark James under aCreative Commons Attribution 2.5 License. Visit http://www.famfamfam.com/lab/icons/silk/ formore details.

• This product includes software developed by Routrek Networks, Inc.

Appendix B. License Information

182

Appendix C. Network and ProtocolThe components of Virtual DataCenter Automation are preset so that the network ports below will beused by default. If a firewall function such as Windows Firewall is enabled in the systemenvironment including the Global Management Server, Management Server, VM Monitoring Server,and Managed Machine, open the following port.

TipFor the components of SigmaSystemCenter (SystemProvisioning, DeploymentManager, NEC ESMPROManager, SigmaSystemCenter, and SystemMonitor), see Appendix A Networks and Protocols inSigmaSystemCenter Installation Guide and Appendix A Network Ports and Protocols in SigmaSystemCenterData Reference Guide to perform setting.

NoteWhen installing the global management server and the management server on the same machine, be carefulto avoid duplicating port numbers.For details, see "2.1.3 Cautions Regarding Installing Multiple Functions on the Same Machine (page 6)".

• Global Management Server component

Component Item Programname

Protocol

ConnectiondestinationPort

number

Connectionsource taget

Connectionsource Portnumb

er

Whether thePort

number can

bechanged ornot

MISSIONCRITICALOPERATIONSManagerVirtualDataCenterAutomationManagerAssetSuiteManagerAsRiCommonManager

Communicationbetween theManager andAgent

Program Files(x86)\NEC\vDCA\GM\FW\Manager\bin\SysMonMgr.exe

TCP 12520 Agent of theManagedMachine

Auto Yes

Communicationbetween theManager andManagementServer

TCP 12520 Manager of theManagementServer

Auto Yes

Communicationbetween theManager andconsole

TCP 12521 Console of theGlobalManagementServer

Auto Yes

Communicationbetween theManager andWeb console

TCP 8080 Web console Auto Yes

VirtualDataCenterAutomationWebServiceView

VirtualDataCenterAutomationWebServiceView (forinternalcommunication

Program Files(x86)\NEC\vDCA\GM\FWAP\Svc\bin\SysMonSvc.exe

TCP 8081 Internal Auto No

Appendix C. Network and Protocol

183


Protocol


number



er

Whether thePort

number can

bechanged ornot

with the ServiceGovernor)

ApplicationServer

Apache Tomcat Program Files(x86)\NEC\vDCA\GM\FW\Tomcat\JRE\JavaHome\bin\javaw.exe(The path variesdepending onthe OSenvironment.)

TCP 12080 RESTFul APIClient * Whenhttpcommunicationis used.

Auto Yes

TCP 12443 RESTFul APIClient * Whenhttpcommunicationis used.

Auto Yes

TCP 12005 Tomcatmanagementport

Auto Yes

TCP 12009 Tomcat AJP1.3port

Auto Yes

• Management Server Component


Protocol


number



er

Whether thePort

number can

bechanged ornot

MISSIONCRITICALOPERATIONSManagerNetworkManagerManager


Program Files(x86)\NEC\vDCA\MoM\FW\Manager\bin\SysMonMgr.exe


Auto Yes

Communicationbetween theManager andVM MonitoringServer

TCP 12520 Manager of theVM MonitoringServer

Auto Yes


TCP 12521 Console of theManagementServer

Auto Yes



Auto Yes


184


Protocol


number



er

Whether thePort

number can

bechanged ornot

(individualityreflection)

Communicationbetween theManager andAgent(individualityreflection)

Program Files(x86)\NEC\vDCA\MoM\FW\Manager\bin\SendRouteInfo.exe


Auto No




NetworkManagerManager

Communicationfrom the consoletomanager(Network Managerinfrastructureservice)

Program Files(x86)\NEC\vDCA\MoM\FW\Manager\bin\NvPROBaseMgr.exe


Auto No

Communicationfrom the consoletomanager(Remote login service)

Program Files(x86)\NEC\vDCA\MoM\FW\Manager\bin\NvPROrmapisrv.exe


Auto No

Communicationfrom the consoleto manager(Filetransfer service)

Program Files(x86)\NEC\vDCA\MoM\FTBase\ftbs.exe


Auto No

TFTP Service Program Files(x86)\NEC\vDCA\MoM\FW\Manager\bin\NvPROrmapisrv.exe

UDP 69 Console of theManagementServer

Auto No


VirtualDataCenterAutomationWebServiceView(forinternal

Program Files(x86)\NEC\vDCA\MoM\FWAP\Svc\bin\SysMonSvc.exe

TCP 8081 ServiceGovernor of theGlobalManagementServer

Auto No


185


Protocol


number



er

Whether thePort

number can

bechanged ornot

communicationwith the ServiceGovernor)

DeploymentManager Server*1

Power ON/OFFstatus

- ICMPEchoRequest

- ManagedMachine

- No

Network boot - UDP 67,4011

ManagedMachine

68 No

UDP 4011 ManagedMachine

4011 No

UDP 69 ManagedMachine

Auto No

TCP 26502-26503

ManagedMachine

26502-26503

Yes

Communicationbetween theManager andClient

- TCP 26504-26508

Agent of theManagedMachine

Auto No


26501 Yes

UDP 67 Agent of theManagedMachine

68 No

UDP 69 Agent of theManagedMachine

68 No

ESMPRO/ServerManager*

2

Communicationbetween theManager andAgent(SNMP)

- UDP Auto Agent of theManagedMachine

161 No

Communicationbetween theManager andAgent(SNMPTrap)

- UDP 162 Agent of theManagedMachine

Auto No

*1 For details, see Appendix D Networks and Protocols in DeploymentManager Reference Guide.*2 For details, see Appendix Ports and Protocols in NEC ESMPRO Manager Installation Guide.

• VM Monitoring Server Component


186


Protocol


number



er

Whether thePort

number can

bechanged ornot

MISSIONCRITICALOPERATIONSManager




Auto Yes


TCP 12521 Console of VMMonitoringServer

Auto Yes




VirtualDataCenterAutomationWebServiceView(forinternalcommunicationwith the ServiceGovernor)

Program Files(x86)\NEC\vDCA\MoM\FWAP\Svc\bin\SysMonSvc.exe

TCP 8081 ServiceGovernor of theGlobalManagementServer

Auto No

• Managed Machine Component


Protocol


number



er

Whether thePort

number can

bechanged ornot

MISSIONCRITICALOPERATIONSManager(Windows)

Communicationbetween theManager andAgent(individuality reflection)

Program Files(x86)\NEC\vDCA\Agent\FW\Agent\bin\ReceiveRouteInfo.exe

UDP 12515 Manager of theManagementServer

Auto No

MISSIONCRITICALOPERATIONSManager(Linux)

Communicationbetween theManager andAgent(individuality reflection)

/opt/NEC/vDCA/Agent/FW/Agent/bin/ReceiveRouteInfo.exe


Auto No

DeploymentManager Server*1

Power On/Offstatus

- ICMPEcho

- ManagedMachine

- No


187


Protocol


number



er

Whether thePort

number can

bechanged ornot

Request

Network boot - UDP 68,4011

Manager of theManagementServer

67 No

UDP Auto Manager of theManagementServer

69 No

Communicationbetween theManager andClient

- TCP 26530 Manager of theManagementServer

26530 Yes

TCP 26510-26511

Manager of theManagementServer

Auto No


Auto No


67 No

UDP Auto Manager of theManagementServer

69 No

ESMPRO/ServerManager*

2

Communicationbetween theManager andAgent(SNMP)

- UDP 161 Manager of theManagementServer

Auto No

*1 For details, see Appendix D Networks and Protocols in DeploymentManager Reference Guide.*2 For details, see Appendix Ports and Protocols in NEC ESMPRO Manager Installation Guide.

• Agent of the Managed Machine component


Protocol


number



er

Whether thePort

number can

bechanged ornot

MISSIONCRITICAL

Communicationbetween theManagement

Program Files(x86)\NEC\UMF


Auto Yes


188


Protocol


number



er

Whether thePort

number can

bechanged ornot

OPERATIONSManager

Server andManagementAgent

\Operations\Agent\bin\SysMonAgt.exe

Communicationbetween theManagementAgent andNetApp storage

Program Files(x86)\NEC\UMF\Operations\Agent\bin\StorageArrayInfoCmd.exe


Auto Yes

• ID Management Server


Protocol


number



er

Whether thePort

number can

bechanged ornot

MasterScopeIdentityManager

LDAPcommunication

Program Files(x86)\NEC\vDCA\SM\SECUREMASTER\EDS\bin\edldapd.exe

TCP 1389 GlobalManagementServer,ManagementServer, VMMonitoringServer, networkdevicesperforming Ldapauthentication

Auto Yes

LDAPScommunication

TCP 1636 Auto Yes

For LDAPservermanagement

Program Files(x86)\NEC\vDCA\SM\SECUREMASTER\EDS\bin\edlagent.exe

TCP 11007 Internal Auto Yes

For LDAPserver statemonitoring

TCP 11008 Internal Auto Yes*1

ID applicationhttpcommunication

Program Files(x86)\NEC\vDCA\SM\SECUREMASTER\EIDM\WEBAP\TOMCAT\bin\tomcat7.exe

TCP 12637 Terminalperforming IDapplication

Auto Yes

ID applicationhttpscommunication

TCP 12639 Terminalperforming ID application

Auto Yes

ID applicationAJPcommunication



189


Protocol


number



er

Whether thePort

number can

bechanged ornot

ID applicationshutdowncommunication


The connection destination port number for LDAP server state monitoring is the connectiondestination port number for LDAP server management + 1.

• DB Server

When a separate server is used for the DBMS, certain actions are required.

Set up a firewall on the DBMS server side. No setting is required for the machine on which theGlobal Management Server, Management Server, and VM Monitoring Server are installed.

No setting is required when a separate server is not used for the DBMS.


Protocol


number



er

Whether thePort

number can

bechanged ornot

SQL Server2014

Communicationwith the DBMSclient

Program Files(x86)\MicrosoftSQL Server\MSSQL11.SQLEXPRESS2014\MSSQL\Binn\sqlservr.exe(The path variesdepending onthe settingsduringinstallation.)

TCP /UDP

Allports

The DBMSclient of themachine onwhich theGlobalManagementServer,ManagementServer, and VMMonitoringServer areinstalled

Auto No

SQL ServerBrowser

Communicationwith the DBMSclient

Program Files(x86)\MicrosoftSQL Server\110\Shared\sqlbrowser.exe(The path variesdepending onthe settingsduringinstallation.)

TCP /UDP

1433 /1434

The DBMSclient of themachine onwhich theGlobalManagementServer,ManagementServer, and VMMonitoringServer areinstalled

Auto No


190

• Other


Protocol


number



er

Whether thePort

number can

bechanged ornot

Service Manager Incidentregistration *Only when thelinkage functionis used.

- TCP 12690 Program Files(x86)\NEC\vDCA\MoM\FW\Manager\bin\SysMonMgr.exe

Auto No

VMwarevCenter Server

Shared VMtemplate

- TCP 443 Program Files(x86)\NEC\vDCA\MoM\FW\Manager\bin\Scenario\SWRepository\PS\ImportVM_VMware.ps1,GetTemplateLocation.ps1,RegisterTemplate.ps1

Auto Yes

Hypervisor(ESX/ESXi)

Shared VMtemplate

- TCP 902 Program Files(x86)\NEC\vDCA\MoM\FW\Manager\bin\Scenario\SWRepository\PS\ImportVM_VMware.ps1,CopyTemplate_VMware.ps1

Auto Yes

Hypervisor(Hyper-V)

VM templategeneration

- TCP 135andRPCdynamic port

Program Files(x86)\NEC\vDCA\MoM\FW\Manager\bin\Scenario\SWRepository\PS\GetOSName_Hyper-V.ps1

Auto Yes

File server(Store the VMtemplate)

Shared VMtemplate* Only when theShared VMtemplatefunction is used.

- TCP /UDP

1112049dynamic port

Program Files(x86)\NEC\vDCA\MoM\FW\Manager\bin\Scenario\SWRepository\PS

Auto No


191


Protocol


number



er

Whether thePort

number can

bechanged ornot

* Only when theNFS Sharing isused

\CopyTemplate_VMware.ps1

Shared VMtemplate* Only when theShared VMtemplatefunction is used.* Only when theCIFS Sharing isused.

- TCP 445 Program Files(x86)\NEC\vDCA\MoM\FW\Manager\bin\Scenario\SWRepository\PS\CopyTemplate_VMware.ps1

Auto No

File server(Store thesoftware /patches)

Distributionsoftware /patches* Only when thesoftware /patches storedon a shared disk* Only when theNFS Sharing isused

- TCP /UDP

1112049dynamic port

GlobalManagementServer,ManagementServer, VMMonitoringServer

Auto No

Distributionsoftware /patches* Only when thesoftware /patches storedon a shared disk* Only when theCIFS Sharing isused.

- TCP 445 GlobalManagementServer,ManagementServer, VMMonitoringServer

Auto No


192

Appendix D. Certificate in the SSLSetting

• Introduction

There are mainly two types of server certificate.

One is the method of creating the server certificate by utilizing the official certificate authority.

The other is the method of creating a self-signed certificate by the self-issuance.

The latter can be generally utilized when the access by unspecified number of users is rejected(for example, the server that is used within a company or within the specified members).

Since the SSL setting varies depending on which certificate is used, this documents describesthe examples of procedures in both ways.

Note that the procedures described in this document are just examples that cannot be warranted.

Be sure to use them as a reference.

• The server certificate that utilizes the official certification authority:

1. Create a secret key in the key store.

> keytool.exe -genkey -alias <Any Alias> -keyalg RSA -keystore <Key store file name> -storepass changeit

Set any value for the items that requires the entry after the command execution.

Be sure to specify changeit for the password of the key.

Note- Set the identical password to the key store password when the key password is changed

from changeit.- Specify the host name or the IP address when accessing from the client for Common

Name.

2. Create a request of server certificate issuance.

> keytool.exe -certreq -alias <Any Alias> -keystore <Key store file name> -file <Any document name for requesting a server certificate>.csr -storepass changeit

3. Ask an official certificate authority to issue the server certificate.

For details about how to request to issue the server certificate, contact the provider to beused.

4. Install the intermediate CA certificate.

> keytool.exe -import -noprompt -trustcacerts -alias <Any Alias for the CA certificate> -file <Intermediate CA certificate>.pem -keystore <Key store file name> -storepass changeit

5. Import the server certificate

Appendix D. Certificate in the SSL Setting

193

> keytool.exe -import -v -trustcacerts -alias <Any Alias> -file <Server certificate>.csr -keystore <Key store file name> -storepass changeit

• Self-signed certificate by the self-issuance:

1. Create a secret key.

> openssl genrsa -aes128 1024 > <Any name for a secret key>.key

2. Create a request of server certificate issuance.

> openssl req -new -key <Any name for a secret key>.key > <Any document name for requesting a server certificate>.csr

3. Create a server certificate.

> openssl x509 -in <Any document name for requesting a server certificate>.csr -days 365 -req -signkey <Any name for a secret key>.key > <Any name for a certificate>.crt

4. Convert into the pkcs12 format.

> openssl pkcs12 -export -in <Any name for a certificate>.crt -inkey <Any name for a secret key>.key -out <Any name for a certificate>.p12 -name <Alias name of any certificate>

5. Import the server certificate.

> keytool.exe -importkeystore -srckeystore <Any name for a certificate>.p12 -destkeystore "<Key store file name>" -srcstoretype pkcs12 -deststoretype JKS

Appendix D. Certificate in the SSL Setting

194

MasterScope Virtual DataCenter Automation v3.0Installation Guide

June, 2016 1st Edition

NEC Corporation

©NEC Corporation 2012-2016