MasterScope Virtual DataCenter Automation v4.0

Transcription

1 MasterScope Virtual DataCenter Automation v4.0 Standard Edition Setup Guide 1st Edition April, 2017 NEC Corporation

2 Disclaimer The 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 the permission 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 this document. NEC Corporation shall not be liable for the accuracy, usability, or certainty of information noted in this document. Copyright Information SigmaSystemCenter, MasterScope, Network Manager, NEC Storage, ESMPRO, EXPRESSBUILDER, EXPRESSSCOPE, SIGMABLADE, UNIVERGE, and ProgrammableFlow are registered trademarks of NEC Corporation. VMware is a trademark or registered trademark of VMware, Inc. in the United States and other countries. Microsoft, Windows, Windows Server, Windows Vista, Internet Explorer, SQL Server, and Hyper-V are trademarks or registered trademarks of Microsoft Corporation in the United States of America and other countries. Linux is a trademark or registered trademark of Linus Torvalds in the United States of America and other countries. Red Hat is a trademark or registered trademark of Red Hat, Inc. in the United States and other countries. Intel and Itanium are trademarks or registered trademarks of Intel Corporation in the United States of America and other countries. Apache, Apache Tomcat, and Tomcat are trademarks or registered trademarks of Apache Software Foundation. Oracle, Solaris, Java, and WebLogic are registered trademarks of Oracle Corporation and its subsidiaries 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, FortiClient, and FortiGuard are registered trademarks of Fortinet, Inc. Other Fortinet products 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 registered trademarks 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 registered trademarks of F5 Networks, Inc. in the United States of America and other countries. The OpenStack Word Mark and the OpenStack logos are registered trademarks or trademarks of the OpenStack Foundation in the United States of America and other countries. i

3 MySQL is a registered trademark of Oracle Corporation and/or its affiliates in the United States of Amerida and other countries. Other system names, company names, and product names in this document are trademarks or registered trademarks of their respective companies. The and marks are not included in this document. Notes on exporting this product If this product (including its software) is subject to regulation under the Foreign Exchange and Foreign Trade Law, it will be necessary to follow the procedures required by this law when exporting this product, such as obtaining an export license from the Japanese Government. If you require documents from NEC in order to obtain an export license, please contact the dealer where you purchased your MasterScope product, or your local NEC sales office. ii

4 Preface Target Readers and Objective This document is intended for system administrators and includes details of how to install and uninstall Virtual DataCenter Automation Standard Edition. Overview of the Document This document describes the procedure for installation Virtual DataCenter Automation Standard Edition. Notation Rules of This Document This document describes precautions, important items, and related information as follows. Note Indicates precautions, warnings, and supplementary notes for the function, operation, and setting Tip Indicates the location of reference destination information Notation rules In addition, the following notation rules are applied in this document. Notation How to use Example XXXXX " " XXXXX [ ] in a command line Monospace font (courier new) Italicized monospace font (courier new) < > Used before and after the items (text boxes, check boxes, or tabs, etc.) to be displayed in the dialog box or used for screen names (dialog boxes, windows, and others). Used used before and after other manual name. Indicates that the specification of the value in [ ] can be omitted. Indicates the outputs (messages, prompts, and others) from the command line or system. Indicates the items to be replaced with a valid value and input by users. When a space is included in the value, place before and after the value. Enter the machine name in the Machine name text box. All check box Setting window "Installation Guide" Installation Guide add [/a] Gr1 Perform the following command. replace Gr1 add GroupName InstallPath="Install Path" <Install DVD> iii

5 Contents Chapter 1. Overview of Virtual DataCenter Automation Standard Edition Installation Virtual DataCenter Automation Standard Edition Integrated Installer Installation Modes of the Virtual DataCenter Automation Standard Edition DVD Configuration of Virtual DataCenter Automation...2 Chapter 2. Performing installation by selecting functions Types of Functions to be Installed Server Configuration Diagram of Virtual DataCenter Automation Standard Edition Roles of Each Function Software Required to be Installed in Advance List of Software to be Installed in Advance Installing Internet Information Service (IIS) Manager and ASP.NET Installing.Net Framework 3.5 Service Pack Installing.Net Framework Installing.Net Framework Installing Visual C Redistributable Packages Installing SQL Server Installing MySQL Installing the components of Management Server Components Installed on the Management Server Software Required to be Installed in Advance DHCP Server Configuration Setting Up the Windows Firewall Precautions When Setting NEC ESMPRO Manager User Group Precautions When Installing Virtual DataCenter Automation Management Server Cautions before Performing Installation Installing the components of Management Server Installing the components of Management Server Console Components Installed on the Management Server Console Cautions before Performing Installation Installing the components of Management Server Console Installing the components of VM Monitoring Server Components Installed on the VM monitoring Server Software Required to be Installed in Advance Setting up the Windows Firewall Cautions before Performing Installation Installing the components of VM Monitoring Server Installing the components of VM Monitoring Server Console Components Installed on the VM monitoring Server Console Cautions before Performing Installation Installing the components of VM Monitoring Server Console Installing the Stack Management Server...31 iv

6 2.7.1 Components to Be Installed to the Stack Management Server Software Required to be Installed in Advance Firewall Settings Installing the Stack Management Server Installing the components of Managed Machine VMWare ESXi Virtualization Infrastructure Hyper-V Virtualization Infrastructure KVM Virtualization Infrastructure Installing the components of Managed Machine (Windows) Software Required to be Installed in Advance Cautions before Performing Installation Installing the components of Managed Machine (Windows) Installing the components of Managed Machine (Linux) Software Required to be Installed in Advance Cautions before Performing Installation Installing the components of Managed Machine (Linux) Registering and Setting up the Management Server Registering License to SigmaSystemCenter Function Registering License to SystemManager G Function Registering Code Word to SystemManager G Function Virtual DataCenter Automation Standard Edition Portal setting Portal setting of Resource Management function Connection Settings to ServiceGovernor Connection Settings to SystemManager G Setting SSL/TLS for Tomcat Default Settings of SystemManager G Function Pre-importing Monitoring Settings Registering and Setting up the VM Monitoring Server Registering the License to the SystemManager G Function Registering Code Word to SystemManager G Function Default Settings of SystemManager G Function Pre-importing Monitoring Settings Registering and Setting up the Stack Management Server Registering the License of Virtual DataCenter Automation Standard Edition Topology Template Registering License to Orchestrator Option Function Settings for connecting to SigmaSystemCenter Settings for connecting to SystemManager G TLS, SSL setting of OpenStack Setting up the Managed Machine Creating the VM Template of the Managed Machine...53 Chapter 3. Basic setting after installation Resource Management Function Registering Related Products to the SigmaSystemCenter Registering the Virtualization Infrastructure to the SigmaSystemCenter Registering a Storage Device to the SigmaSystemCenter...57 v

7 Registering a Virtual DataCenter Automation Component to the SigmaSystemCenter Performing Various Settings of the SigmaSystemCenter Performing Hardware Settings of the VM Server Registering VM Server on SigmaSystemCenter Performing Setting to Manage the VM Server with the OOB Management Setting the Machine Properties of the VM Server Creating a Resource Pool Creating a Category of the VM Server Creating an Operation Group of the VM Server Setting an Operation Group of the VM Server Defining a Resource Pool Allocating a Sub-pool Registering a VM Server Resource Registering a Logical Network Registering a Storage Resource Allocating a Disk Volume Setting a Storage Tag About using Resource Manager Function Monitoring Function Configuring the Monitoring Manager Setting up DeploymentManager Setting up Virtual DataCenter Automation Standard Edition Portal About using Monitoring Function...69 Chapter 4. Performing Uninstallation Precautions before Uninstallation Uninstalling the components of Management Server Uninstalling the components of Management Server Console Uninstalling the components of VM Monitoring Server Uninstalling the components of VM Monitoring Server Console Uninstalling the Stack Management Server Uninstalling the components of Managed Machine(Windows) Uninstalling the components of Managed Machine(Linux)...82 vi

8 List of Tables Table 2-1 Selection of function...10 Table 2-2 Instance name to create...10 Table 2-3 Log on user of the SQL Server services...10 Table 2-4 SQL Server network configuration...11 Table 2-5 Adding a fixed server role member...11 vii

9 Chapter 1. Overview of Virtual DataCenter Automation Standard Edition Installation Chapter 1. Overview of Virtual DataCenter Automation Standard Edition Installation This chapter describes how to read this document and the Virtual DataCenter Automation Integrated Installer for installing and uninstalling Virtual DataCenter Automation Standard Edition. Contents 1.1 Virtual DataCenter Automation Standard Edition Integrated Installer DVD Configuration of Virtual DataCenter Automation...2 1

10 1.1 Virtual DataCenter Automation Standard Edition Integrated Installer Virtual DataCenter Automation Standard Edition can be installed using the Virtual DataCenter Automation Standard Edition Integrated Installer. The Virtual DataCenter Automation Standard Edition Integrated Installer allows you to install the product components of Management Server, Management Server Console, VM Monitoring Server, VM Monitoring Server Console 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 Installation Modes of the Virtual DataCenter Automation Standard Edition The Virtual DataCenter Automation Integrated Installer has two installation modes. Typical mode This mode allows you to install the product components comprising the Virtual DataCenter Automation Standard Edition function in a batch. Select the functions to be installed. Custom mode Note This mode starts the installer of the products comprising Virtual DataCenter Automation Standard Edition. Use this to update the versions of product components that make up the Virtual DataCenter Automation Standard Edition function. It is also used for adding functions of product components, performing maintenance, and changing the server configuration of Virtual DataCenter Automation Standard Edition if required. For details of upgrading Virtual DataCenter Automation Standard Edition, refer to the manual for each product. 1.2 DVD Configuration of Virtual DataCenter Automation The Virtual DataCenter Automation Standard Edition Integrated Installer is stored on the vdca/nwa install DVD as follows. \ install \ Windows Chapter 1. Overview of Virtual DataCenter Automation Standard Edition Installation vdca/nwa Install DVD \ vdcainst_se.exe Virtual DataCenter Automation Standard Edition Integrated Installer (Windows) 2

11 Chapter 1. Overview of Virtual DataCenter Automation Standard Edition Installation vdca/nwa Install DVD \ Linux \ vdcainst_se.sh Virtual DataCenter Automation Standard Edition Integrated Installer (Linux) 3

12 Chapter 2. Performing installation by selecting functions Chapter 2. Performing installation by selecting functions This chapter describes the installation procedures for each function type of Virtual DataCenter Automation Standard Edition. It describes the required settings in Windows Server before installation using the Virtual DataCenter Automation Standard Edition Integrated Installer, tools to be in advance, and installation of product components using the Integrated Installer. Contents 2.1 Types of Functions to be Installed Software Required to be Installed in Advance Installing the components of Management Server Installing the components of Management Server Console Installing the components of VM Monitoring Server Installing the components of VM Monitoring Server Console Installing the Stack Management Server Installing the components of Managed Machine Installing the components of Managed Machine (Windows) Installing the components of Managed Machine (Linux) Registering and Setting up the Management Server Registering and Setting up the VM Monitoring Server Registering and Setting up the Stack Management Server Setting up the Managed Machine

13 2.1 Types of Functions to be Installed This section describes the types and configuration of the functions comprising Virtual DataCenter Automation Standard Edition Server Configuration Diagram of Virtual DataCenter Automation Standard Edition The followings are the types of functions to be installed in the installation procedure of this document. Management Server Management Server Console VM Monitoring Server VM Monitoring Server Console Stack Management Server Managed Machine - Basis of virtualization - Virtual Machines (VM), VM Templates Minimum configuration example Chapter 2. Performing installation by selecting functions Load balancing configuration example 5

14 Chapter 2. Performing installation by selecting functions *1 The Stack Management Server is required only for the configuration that uses the Virtual DataCenter Automation Standard Edition Topology Template Orchestrator Option. Note About Virtual DataCenter Automation Standard Edition Portal, refer to Virtual DataCenter Automation Standard Edition Portal User Manual (Install), Virtual DataCenter Automation Standard Edition Portal User Manual (Resource Management) and Virtual DataCenter Automation Standard Edition Portal User Manual (Monitoring). When Virtual DataCenter Automation Standard Edition Topology Template Orchestrator Option are used, refer to Virtual DataCenter Automation Standard Edition Portal User Manual (Resource Management) Topology Template Orchestrator Option and Virtual DataCenter Automation Standard Edition Portal User Manual (Monitoring) Topology Template Orchestrator Option About Virtual DataCenter Automation Standard Edition Topology Template Orchestrator Option, refer to Topology Template Orchestrator User Manual Roles of Each Function The roles of each function are as follows. Function Management Server Management Server Console VM Monitoring Server Role Manages and monitors all resources in Virtual DataCenter Automation Standard Edition in an integrated fashion. Provides a single-point gateway function working with an external function such as Virtual DataCenter Automation Standard Edition Portal. Provides functions to monitor and control the resources managed by the Management Server. Provides functions to monitor and control virtual machines. Plays the role of reducingthe Management Server load when monitoring virtual machines. 6

15 Chapter 2. Performing installation by selecting functions Function VM Monitoring Server Console Managed Machine Stack Management Server Role Provides functions to monitor and control the resources managed by the VM Monitoring Server. Provides functions to monitor and control by installation on the virtualization infrastructure such as a managed virtual machine. The function to assign and delete multiple resources at a time according to the system configuration information defined in the topology template are provided. Note For the system requirements of each function, see Chapter 6. Operating Environments/System Requirements in Virtual DataCenter Automation First Step Guide. For the Stack Management Server system requirements, refer to Chapter 1 Operating Environment of Virtual DataCenter Automation Standard Edition Topology Template Orchestrator Option User s Guide. 2.2 Software Required to be Installed in Advance This section describes the software required before installation using the Virtual DataCenter Automation Standard Edition Integrated Installer List of Software to be Installed in Advance In Virtual DataCenter Automation Standard Edition, the following software must be installed before installing for Management Server. Internet Information Service Management Server Necessary.NET Framework 3.5 Service Pack 1 Necessary *1.NET Framework 4.0.NET Framework Visual C Redistributable Packages Necessary Necessary Necessary SQL Server / client tool Necessary *2 *1 When using SQL Server 2014, it's necessary. *2 To use a separate server for the DBMS, install SQL Server on the DBMS server, and install the SQL Server client tools on the machine on which the Management Server is installed. For the required software of the DB server, see 6.10 DB server in Virtual DataCenter Automation First Step Guide. If the DBMS is not separately used as a server, the\ SQL Server client tools do not have to be installed. Before installing the Stack Management Server, install the following software. Stack Management Server MySQL Necessary For VM Monitoring Server and consoles (Management Server and VM Monitoring Server), there is no software required to be installed in advance. 7

16 2.2.2 Installing Internet Information Service (IIS) Manager and ASP.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 [Server Manager]. 2. Select the following check box on the [Select Server Roles] dialog box, and perform installation. [Web Server] - [Common HTTP Features] - [Static Content] [Web Server] - [Application Development] -[ASP.NET 4.5] (Windows Server 2012, Windows Server 2012 R2) [Web Server] - [Application Development] -[ASP.NET 4.6] (Windows Server 2016) [Management Tools] - [IIS Management Console] [Management Tools] - [IIS 6 Metabase Compatibility] Installing.Net Framework 3.5 Service Pack1 Install.Net Framework 3.5 Service Pack1. The following is the example when installing from the powershell command. 1. Insert the Windows Server install DVD into the DVD drive. 2. To start PowerShell, click Start, click the Windows PowerShell folder, right-click Windows PowerShell, and then click Run as Administrator. 3. run the following command: (when the DVD drive letter is E) Chapter 2. Performing installation by selecting functions PS > Install-WindowsFeature Net-Framework-Core -source E:\sources\sxs Installing.Net Framework 4.0 Note For Windows Server 2012 or later, this operation is not required because it is installed as standard. Execute the following command on the command prompt to start the installer, and perform installation by following the wizard. > <Install DVD>:\ssc\dotNet Framework40\Windows6.0-KB v2-x64.msu > <Install DVD>:\ssc\dotNet Framework40\Windows6.0-KB v2-x86.msu Installing.Net Framework Note For Windows Server 2012 R2, be sure to install the Windows Update (KB ) before installing.net Framework If the Windows Update (KB ) is not installed, installing.net Framework will fail. Check whether the Windows Update (KB ) is installed according to the following procedure. 8

17 Chapter 2. Performing installation by selecting functions Run Msinfo32.exe to check the exact version of Windows Server 2012 R2. If Windows Server 2012 R2 Update is installed, the value reported for the hardware abstraction layer is If the value is smaller than , install the Windows Update (KB ). For Windows Server 2016, this operation is not required because it is installed as standard. 1. Execute the following command on the command prompt to start the installer, and perform installation by following the wizard. > <Install DVD>:\ssc\dotNet Framework462\NDP462-KB x86-x64- AllOS-ENU.exe Installation is not necessary when the Net Framework maintenance screen is displayed. Select Cancel Installing Visual C Redistributable Packages Install Microsoft Visual C Redistributable Packages by the following procedure. 1. Execute the following command on the command prompt to start the installer, and perform installation by following the wizard. > <Install DVD>:\ssc\DPM\Setup\VCRTL\vcredist_x86_2013.exe Installing SQL Server In Virtual DataCenter Automation Standard Edition, SQL Server is used on the Management Server. As the product types of SQL Server, Express Edition, Standard Edition, and Enterprise Edition can be used. If Express Edition is used, a cluster environment cannot be built (an upgrade from Express Edition to Standard Edition or Enterprise Edition is required). This section describes how to install SQL Server Enterprise Edition. When the DBMS is separately used as a server, install SQL Server on the DBMS server machine by the following procedure. The SQL Server client tools must be installed on the machine on which the Management Server is installed. If the DBMS is not separately used as a server, the SQL Server client tools do not have to be installed. Installing SQL Server Check the name of the instance created for each server by referring to table: [Instance name to create] below. For the Management Server, perform this installation operation three times for each instance. 1. Execute Setup.exe to start the SQL Server installer. 2. On the [SQL Server Installation Center] screen, click [New SQL Server stand-alone installation or add features to an existing installation] in [Install]. 3. On the [Product Key] screen, enter the product key, and click [Next]. 4. On the [License Terms] screen, select the [I accept the license terms.] check box, and click [Next]. 5. On the [Product Update] screen, a search for the update program starts. Click [Next]. 6. On the [Install Rules] screen, click [Next]. 9

18 7. On the [Setup Role] screen, click [Next]. 8. On the [Feature Selection] screen, select the necessary function indicated on the following, and click [Next]. Function to select Table 2-1 Selection of function 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, enter an appropriate instance name in the text box, and click [Next].Enter it by referring to table: [Instance name to create] below. Machine type Table 2-2 Instance name to create Chapter 2. Performing installation by selecting functions Instance name to create FWCMDB *1 SSCCMDB DPMDBI Management Server Create Create Create *1 To install the DBMS on a separate server, create only one FWCMDB instance on the server on which the DBMS is installed. It does not have to be created on the Management 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 the computer. Setting the logon user of the SQL Server services Perform setting of the required instances by referring to table: [Log on user of the SQL Server Services] below. Table 2-3 Log on user of the SQL Server services Instance name FWCMDB SSCCMDB DPMDBI Logon User Local System NT Service\MSSQL $SSCCMDB (Default value) NT Service\MSSQL $DPMDBI (Default value) 1. Start the SQL Server Configuration Manager. 10

19 2. Click [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. 3. On the [Log On] tab, select the [Built-in account:] radio button, select an appropriate user from the drop-down list, and click [OK]. Select it by referring to "Log on user of the SQL Server services" below. 4. Click [Yes] in the message displayed. 5. Click [Restart]. When restart processing is complete, click [OK] to finish the SQL Server Configuration Manager. Setting the network configuration of SQL Server Perform setting of the required instances by referring to table: [SQL Server Network Configuration] below. Protocol name Table 2-4 SQL Server network configuration Chapter 2. Performing installation by selecting functions Instance name FWCMDB SSCCMDB DPMDBI 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 Instance Name] displayed, and change the state of an appropriate protocol displayed on the right pane. Change it by referring to "SQL Server network configuration" below. 3. Click [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. 4. Click [Restart]. When restart processing is complete, click [OK] to finish the SQL Server Configuration Manager. Adding a fixed server role member of SQL Server Perform setting of the required instances by referring to table: [Adding a fixed server role member] below. Table 2-5 Adding a fixed server role member Instance name FWCMDB SSCCMDB DPMDBI Adding a fixed server role member Do not add Add Add 1. Open the command prompt. 2. Execute the following commands. 11

20 Chapter 2. Performing installation by selecting functions > sqlcmd.exe -E -S ".\<Instance Name>" 1> alter server role [sysadmin] add member [NT AUTHORITY\SYSTEM] 2> go 1> exit 3. When the operation above is complete, restart each of the instances by the following procedure. 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 SQL Server Configuration Manager. SQL Connection Settings for Virtual DataCenter Automation Standard Edition Portal Refer to 2.2 SQL Connection Settings in Virtual DataCenter Automation Standard Edition User Manual (Install), and configure SQL Connection Settings. 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 the SQL 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 client tools This section describes the installation method for the Express Edition. 1. Start the installer. 2. Click [New SQL Server stand-alone installation or add features to an existing installation]. 3. On the [Product Updates] screen, click [Next] after the search for the update program is complete. 4. On the [Install Setup Files] screen, the next screen is displayed automatically after installation of SQL Server setup is complete. 5. On the [Setup Support Rules] screen, the next screen is displayed automatically after the rule check is complete. 6. On the [Installation Type] screen, select the [Perform a new installation of SQL Server] radio button, and click [Next]. 7. On the [License Terms] screen, select the [I accept the license terms.] check box, and click [Next]. 8. On the [Feature Selection] screen, select [Management Tools - Basic], and click [Next]. If the SQL Server 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 tools is not required. Cancel the installation. 9. On the [Installation Rules] and [Disk Space Requirements] screens, the next screen is displayed automatically. 10. On the [Error Reporting] screen, click [Next]. 12

21 11. On the [Installation Configuration Rules] screen, the next screen is displayed automatically after the rule check is complete. 12. On the [Installation Progress] screen, the [Complete] screen is displayed after installation of the management tool is complete. Click [Close]. 13. Close the SQL Server Install Center Installing MySQL For the configuration that uses the Virtual DataCenter Automation Standard Edition Topology Template Orchestrator Option, the Stack Management Server uses MySQL. For the MySQL editions, Standard Edition and Enterprise Edition can be used. Install MySQL by referring to Virtual DataCenter Automation Standard Edition Topology Template Orchestrator Option User s Guide. 2.3 Installing the components of Management Server The subsequent sections describe how to install the components to the Virtual DataCenter Automation Standard Edition Management Server. Before installing the components by using the Virtual DataCenter Automation Standard Edition Integrated Installer, the following preparations are required. Software Required to be Installed in Advance (see "2.3.2 Software Required to be Installed in Advance (page 14)") 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 Standard Edition Management Server Note When installing the components of Management Server by upgrading, or performing installation again when installation is interrupted, stop the services in the order below in advance. After installation, start the services manually. Note MasterScope UMF Operations Manager_102 When installing a new management server in an environment in which SigmaSystemCenter manager is installed, first update the version of the SigmaSystemCenter manager to 3.6. Note Chapter 2. Performing installation by selecting functions When installing a new Management Server in an environment in which MasterScope SystemManager Manager is installed, first update the version of MasterScope SystemManager G Manager to 7.0. To update the version, add MasterScope SystemManager G Manager to the service in which MasterScope SystemManager Manager is installed in the custom mode. 13

22 2.3.1 Components Installed on the Management Server For 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 SystemManager G Manager Application Server *1*2 MasterScope vdc Automation Service Governor WebAPI Base Option MasterScope vdc Automation Portal MasterScope SigmaSystemCenter *1 Java 8u121 and Tomcat 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 Chapter 2. Performing installation by selecting functions <installation folder> is the installation destination folder of Management Server. The default value of the installation folder is "C:\Program Files (x86)\nec\vdca\mom" Software Required to be Installed in Advance Before starting installation of the components of the Management Server, install the following software..net Framework 3.5 Service Pack 1 *1.NET Framework 4.0.NET Framework Visual C Redistributable Packages SQL Server *2 SQL Server client tools *2 Internet Information Service *1 When using SQL Server 2014, it's necessary. *2 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 is not separately used as a server, the SQL Server client tools do not have to be installed. Install it by referring to the procedure in "2.2 Software Required to be Installed in Advance (page 7)" DHCP Server Configuration If HYPER-V or KVM is used as the virtualization infrastructure server, or if physical server provisioning is used, a DHCP server is required in the same network as Virtual DataCenter Automation Standard Edition. 14

23 Prepare the DHCP server before installing the Virtual DataCenter Automation Standard Edition. The DHCP server can be installed on the same machine as the management server. Multiple DHCP servers can exist within the same network segment. For the DHCP server, specify gateway and IP pools for all IP subnets to be used. Tip For setup methods and precautions of the DHCP server, see Network Environment in the DeploymentManager First Step Guide and Setting UP the DHCP Sever in the DeploymentManager Installation 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 Setting Up the Windows Firewall If the Windows Firewall function is enabled on the Management Server, the port used by the Management Server must be opened. Some ports are registered automatically during the installation, while others must be registered manually. For details, refer to the following manuals. Virtual DataCenter Automation Standard Edition Portal User Manual (Install) 5.1 Virtual DataCenter Automation Service Governor WebAPI Base Option Installation Guide (Windows) 3.7 About the Port Numbers Used SigmaSystemCenter manual SystemManager G manual Chapter 2. Performing installation by selecting functions Precautions When Setting NEC ESMPRO Manager User Group When using Windows GUI of ESMPRO/ServerManager, the users must belong to the group known as "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 Precautions When Installing Virtual DataCenter Automation Management Server Check that the IP address for the OS network connection of the Virtual DataCenter Automation Standard Edition Management 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 port used by DeploymentManager and the port used by other services and applications, preventing the DeploymentManager service from running. For details on how to check and troubleshoot ephemeral ports, see 2.2 Precautions Regarding System Configuration in the DeploymentManager First Step Guide. 15

24 For the other precautions, see 2.1 Installing DPM Server in the DeploymentManager Installation Guide and 2.2 Precautions Regarding System Configuration in the DeploymentManager First Step Guide Cautions before Performing Installation Be sure to exit all applications and Web browsers being used before starting the installation Installing the components of Management Server 1. Insert the vdca/nwa install DVD into the DVD drive. 2. Execute the following command on the command prompt or Explorer to start the Virtual DataCenter Automation Standard Edition Integrated Installer. > <Install DVD>:\install\Windows\vDCAInst_SE.exe 3. The installer starts up. 4. Select [Typical], and click [Next]. The [Selection of Function] screen is displayed. 5. Select the [Management Server] check box. Functions other than [VM Monitoring Server] and [Managed Machine] can be installed on the Management Server. To install them, select the check boxes. 6. Click [Next]. The [Setting of Management Server] screen is displayed. Chapter 2. Performing installation by selecting functions 7. Set the following required items. Select the setting item name and click [Edit]. Perform setting in the screen displayed. [Self Hostname] (Example:vdca_mom) 16

25 8. The following items are required when SigmaSystemCenter is not installed. Select the setting item name and click [Edit]. Perform setting in the screen displayed. [ESMPRO/ServerManager - Administrator Name] (Example: Administrator) [ESMPRO/ServerManager - Administrator's Password] (Example: Password) 9. Set the setting items as required. Click the setting item and click [Edit], or double-click the setting item. The setting screen for the selected setting item opens. Item Name [Install Directory Path] [Using Monitoring] [Self Hostname] [Agent Port] [Viewer Port] Value 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 If "Yes" is selected, the following components will be installed. MasterScope SystemManager G Manager MasterScope vdc Automation Service Governor WebAPI Base Option The default value is "Yes". *7 Specify the computer name of the Management Server. The default value is machine name (e.g. MANAGER). *2*7 Specify the port number on the manager side used for connection from the agent. The default value is "12520". *7 Specify the port number on the manager side used for connection from the Management Server Console. The default value is "12521". *7 [Change Data Directory] The default value is "No". *3*7 Chapter 2. Performing installation by selecting functions [Data Directory] [Store Initial Setting Data] [Application Server Type] [Application Server - HTTP Port] [Application Server - HTTPS Port] [Tomcat - Management Port] [Tomcat - AJP/1.3 Port] It can be specified if "Yes" is selected in [Change Data Directory]. *3*7 It can be specified if "Yes" is selected in [Change Data Directory]. *3*7 The default value is "Yes". Specify the Application Server type. Only "Tomcat" can be specified in this version. *8 Specify the HTTP port number of the Application Server. The default value is "12080". *8 Specify the HTTPS port number of the Application Server. The default value is "12443". *4*8 Tomcat - Management Port Specify the Management port number of the Tomcat. The default value is "12005". *8 Specify the AJP/1.3 port number of the Tomcat. The default value is "12009". *8 17

26 Chapter 2. Performing installation by selecting functions Item Name [Portal - ServiceGovernor connection protocol] [Portal - SQL Server Host Name] [Portal - SQL Server Instance Name] [Portal - SQL Server Port] [Using Resource Management] [ESMPRO/ServerManager - Administrator Name] [ESMPRO/ServerManager - Administrator's Password] [DeploymentManager - Management Server's IP Address] Value Specify the hconnection protocol between Portal to ServiceGovernor. "http" or "https" can be specified. The default value is "http". *9 Specify the host name of the machine on which the database is installed. The default value is "localhost". *9 Specify the instance name of the database. Specify the name of the instance created in "2.2.7 Installing SQL Server (page 9)". The default value is "FWCMDB". *9 Specify the port number of the database. The default value is "1433". *9 If "Yes" is selected, the following component will be installed. MasterScope SigmaSystemCenter The default value is "Yes". *5 Specify the name of the administrator of ESMPRO Manager. *5 Specify the password of the administrator of NEC ESMPRO Manager.* *5 Specify the IP address of the DPM management server. *5*6 *1 Note that [Install Directory Path] and [Data Directory] are not case-sensitive. The following characters 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 machines connected. 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 IP address or virtual host name. *3 Specify "Yes" to use a cluster configuration. Since this document does not support cluster configuration, specify "No". *4 In vcenter Server 5.5, port is used. Change the port number because it affects WebAPI (https) when installing vcenter Server 5.5 in the identical server. *5 This can be specified when MasterScope SigmaSystemCenter is not installed. *6 If it is omitted, all the LAN boards on the Management Server will be used by the DPM server. *7 This can be specified when MasterScope SystemManager G Manager is not installed. *8 This can be specified when Application Server is not installed. *9 This can be specified when MasterScope vdc Automation Portal is not installed. 10. Click [Next]. The installation confirmation screen is displayed. 18

27 Note Chapter 2. Performing installation by selecting functions If other functions are installed simultaneously, click [Next] to display the setting screens. For the setting screens, see the procedure for installing the functions. 11. Check the details, and click [Start]. 12. Click [Yes] on the confirmation message displayed. Installation starts. 13. When the installation is complete, the installation result screen is displayed with the installation result. If MasterScope SigmaSystemCenter is already installed, "Skipped" is displayed as the result of installing MasterScope SigmaSystemCenter. If MasterScope SystemManager G Manager is already installed, "Skipped" is displayed as the result of installing MasterScope SystemManager G Manager. 19

28 Chapter 2. Performing installation by selecting functions 14. Click [Finish]. 15. If the restart message is displayed, click [OK]. 16. Restart the server. 17. Perform license registration and setting of the Management Server. A license is registered after installation of the Management Server console. See "2.4 Installing the components of Management Server Console (page 20)". For setting the Management Server, see "2.11 Registering and Setting up the Management Server (page 43)". 2.4 Installing the components of Management Server Console The subsequent sections describe how to install the components of the Virtual DataCenter Automation Standard Edition Management Server Console Components Installed on the Management Server Console The components installed on the Management Server Console are as follows. MasterScope SystemManager G View Cautions before Performing Installation Be sure to exit all applications and Web browsers being used before starting the installation. 20

29 2.4.3 Installing the components of Management Server Console 1. Insert the vdca/nwa install DVD into the DVD drive. 2. Execute the following command on the command prompt or Explorer to start the Virtual DataCenter Automation Standard Edition Integrated Installer. > <Install DVD>:\install\Windows\vDCAInst_SE.exe 3. The installer starts up. 4. Select [Typical], and click [Next]. The [Selection of Function] screen is displayed. 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. Chapter 2. Performing installation by selecting functions 7. Select the required items, and click [Edit] to set a value. For the setting values, see the table in the 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. 8. Set the setting items as required. Click the setting item and click [Edit], or double-click the setting item. To install multiple components of Management Server Consoles, set the setting items for each installation target. The setting screen for the selected setting item opens. 21

30 Chapter 2. Performing installation by selecting functions Item Name [Install Directory Path] [Management Server Hostname] [Management Server Port] Value Specify the installation destination folder. The default value is "C:\Program Files (x86)\nec\vdca \MoMView". Specify the folder path using up to 55 characters. *1 Specify the IP address or host name of the Management Server. *2 Specify the port number specified in [Viewer Port] in the configuration 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]. The installation confirmation screen is displayed. Note If other functions are installed simultaneously, click [Next] to display the setting screens. For the setting screens, see the procedure for installing the functions. 22

31 Chapter 2. Performing installation by selecting functions 10. Check the details, and click [Start]. 11. Click [Yes] on the confirmation message displayed. Installation starts. When the installation is complete, the installation result screen is displayed with the installation result. 12. Click [Finish]. 23

32 2.5 Installing the components of VM Monitoring Server The subsequent sections describe how to install the components on the Virtual DataCenter Automation Standard Edition VM Monitoring Server. Note When installing the components of VM Monitoring Server by upgrading, or performing installation again when installation is interrupted, stop the services in the order below in advance. After installation, start the services manually. Note MasterScope UMF Operations Manager_103 When installing a new VM Monitoring Server in an environment in which MasterScope SystemManager Manager is installed, first update the version of MasterScope SystemManager G Manager to 7.0. To update the version, add MasterScope SystemManager G Manager to the service in which MasterScope SystemManager Manager is installed in the custom mode Components Installed on the VM monitoring Server For 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 SystemManager G Manager Software Required to be Installed in Advance Before starting installation of the components of the VM Monitoring Server, install the following software..net Framework 3.5 Service Pack 1.NET Framework 4.0 SQL Server *1 SQL Server client tools *1 Chapter 2. Performing installation by selecting functions *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 VM Monitoring Server is installed. If the DBMS is not separately used as a server, the SQL Server client tools do not have to be installed. Install it by referring to the procedure in "2.2 Software Required to be Installed in Advance (page 7)" Setting up the Windows Firewall If the Windows Firewall function is enabled in the VM Monitoring Server, the port used by the VM Monitoring Server must be opened. Some ports are automatically registered during installation, but some items require manual registration. For details, refer to the following manuals. SystemManager G manual 24

33 2.5.4 Cautions before Performing Installation Be sure to exit all applications and Web browsers being used before starting the installation Installing the components of VM Monitoring Server 1. Insert the vdca/nwa install DVD into the DVD drive. 2. Execute the following command on the command prompt or Explorer to start the Virtual DataCenter Automation Standard Edition Integrated Installer. > <Install DVD>:\install\Windows\vDCAInst_SE.exe 3. The installer starts up. 4. Select [Typical], and click [Next]. The [Selection of Function] screen is displayed. 5. Select the [VM Monitoring Server] check box. Functions other than [Management Server] and [Managed Machine] can be installed 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. Chapter 2. Performing installation by selecting functions 7. Select the required items, and click [Edit] to set a value. For the setting values, see the table by the following procedure. 8. Set the setting items as required. Click the setting item and click [Edit], or double-click the setting item. The setting screen for the selected setting item opens. 25

34 Chapter 2. Performing installation by selecting functions Item Name [Install Directory Path] [Self Hostname] [Agent Port] [Viewer Port] Value Specify the installation destination folder. The default value is "C:\Program Files (x86)\nec\vdca\rm". Specify the folder path by using up to 55 characters. *1 Specify the computer name of the VM Monitoring Server. The default value is machine name (e.g., MANAGER). *2*4 Specify the port number on the manager side used for connection from the Managed Machine. The default value is "12520". *4 Specify the port number on the manager side used for connection from the VM Monitoring Server Console. The default value is "12521". *4 [Change Data Directory] Specify "No" (default value). *3*4 [Data Directory] [Store Initial Setting Data] It can be specified if "Yes" is selected in [Change Data Directory]. *3*4 It can be specified if "Yes" is selected in [Change Data Directory]. *3*4 The default value is "Yes". *1 Note that [Install Directory Path] and [Data Directory] are not case-sensitive. The following characters 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 [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 IP address or virtual host name. *3 Specify "Yes" to use a cluster configuration. Since this document does not support cluster configuration, specify "No". *4 This can be specified when MasterScope SystemManager G Manager is not installed. 9. Click [Next]. The installation confirmation screen is displayed. 26

35 Chapter 2. Performing installation by selecting functions 10. Check the details, and click [Start]. 11. Click [Yes] on the confirmation message displayed. Installation starts. 12. When the installation is complete, the installation result screen is displayed with the installation result. If MasterScope SystemManager G Manager is already installed, "Skipped" is displayed as the result of installing MasterScope SystemManager G Manager. 27

36 Chapter 2. Performing installation by selecting functions 13. Click [Finish]. 14. Restart the server. 15. Perform license registration and setting of the VM Monitoring Server. A license is registered after installation of the VM Monitoring Server console. See "2.6 Installing the components of VM Monitoring Server Console (page 28)". For setting the VM Monitoring Server, see "2.12 Registering and Setting up the VM Monitoring Server (page 51)". 2.6 Installing the components of VM Monitoring Server Console The subsequent sections describe how to install the components of the Virtual DataCenter Automation Standard Edition VM Monitoring Server Console Components Installed on the VM monitoring Server Console The components installed on the VM Monitoring Server Console are as follows. MasterScope SystemManager G View Cautions before Performing Installation Be sure to exit all applications and Web browsers being used before starting the installation Installing the components of VM Monitoring Server Console 1. Insert the vdca/nwa install DVD into the DVD drive. 28

37 Chapter 2. Performing installation by selecting functions 2. Execute the following command on the command prompt or Explorer to start the Virtual DataCenter Automation Standard Edition Integrated Installer. > <Install DVD>:\install\Windows\vDCAInst_SE.exe 3. The installer starts up. 4. Select [Typical], and click [Next]. The [Selection of Function] screen is displayed. 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. 7. Select the required items, and click [Edit] to set a value. For the setting values, see the table by the following procedure. 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 the setting item. To install multiple VM Monitoring Server Consoles, set the setting items for each installation target. The setting screen for the selected setting item opens. Item Name [Install Directory Path] Value Specify the installation destination folder. The default value is "C:\Program Files (x86)\nec\vdca \RMView". 29

38 Chapter 2. Performing installation by selecting functions Item Name [VM Monitoring Server Hostname] [VM Monitoring Server Port] [Service Identifier] Value Specify the folder path by using up to 55 characters. *1 Specify the IP address or host name of the VM Monitoring Server. *2 Specify the port number specified in [Viewer Port] in the configuration of the VM Monitoring Server. The default value is "12521". Identifier to distinguish multiple consoles installed. *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]. The installation confirmation screen is displayed. Note If other functions are installed simultaneously, click [Next] to display the setting screens. For the setting screens, see the procedure for installing the functions. 10. Check the details, and click [Start]. 30

39 11. Click [Yes] on the confirmation message displayed. Installation starts. Chapter 2. Performing installation by selecting functions 12. When the installation is complete, the installation result screen is displayed with the installation result. 13. Click [Finish]. 2.7 Installing the Stack Management Server The procedure to install the TTO Management Server components is described below. The procedure described in this section is required only for the configuration that uses the Virtual DataCenter Automation Standard Edition Topology Template Orchestrator Option. Before installing the components, prepare the following items. Software Required to be Installed in Advance"2.2 Software Required to be Installed in Advance (page 7)" Firewall settings Components to Be Installed to the Stack Management Server For the Stack Management Server system requirements, refer to Chapter 1 Operating Environment of Virtual DataCenter Automation Standard Edition Topology Template Orchestrator Option User s Guide. The components to be installed in the Stack Management Server are as follows. SSC Resource Plug-in 31

40 2.7.2 Software Required to be Installed in Advance Before installing the Stack Management Server's components, install the following software. MySQL OpenStack - Identity Service (keystone) - Orchestration Service (heat) RabbitMQ Install components by referring to Chapter 2.1 Installing the software to be prepared in advance of Virtual DataCenter Automation Standard Edition Topology Template Orchestrator Option User s Guide Firewall Settings If the Firewall function is enabled on the Stack Management Server, the port used by the Stack Management Server must be opened. If you use the support script described in the manual below to install the software that needs to be installed in advance, it will be released automatically. For details, refer to the following manual: Chapter 2 Installation of Virtual DataCenter Automation Standard Edition Topology Template Orchestrator Option User s Guide Installing the Stack Management Server For details about how to install the Stack Management Server, refer to the following manual: Chapter 2.2 Installing SSC Resource Plug-in of Virtual DataCenter Automation Standard Edition Topology Template Orchestrator Option User s Guide 2.8 Installing the components of Managed Machine 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 Standard Edition. Install it to use the specific function. Install the DPM client and SystemManager G agent using the Virtual DataCenter Automation Standard Edition Integrated Installer VMWare ESXi Virtualization Infrastructure Chapter 2. Performing installation by selecting functions To use the VMWare ESXi virtualization infrastructures, install the following components. Managed machine NEC ESMPRO Agent DPM client SystemManager G agent VMware ESXi virtualization infrastructure Windows Managed Machine (virtual machine) Not required Not required Not required Option Required Required 32

41 Chapter 2. Performing installation by selecting functions Managed machine NEC ESMPRO Agent DPM client SystemManager G agent Linux Managed Machine (virtual machine) Option Required Required Hyper-V Virtualization Infrastructure To use the Hyper-V virtualization infrastructure, install the following components. Managed machine NEC ESMPRO Agent DPM client SystemManager G agent Hyper-V virtualization infrastructure Windows Managed Machine (virtual machine) Option Option Not required Option Required Required KVM Virtualization Infrastructure To use the KVM virtualization infrastructure, install the following components. Managed machine NEC ESMPRO Agent DPM client SystemManager G agent KVM virtualization infrastructure Linux Managed Machine (virtual machine) Required Required Not required Option Required Required 2.9 Installing the components of Managed Machine (Windows) Software Required to be Installed in Advance Before starting installation of the components of the Managed Machine, install the following software as required. NEC ESMPRO Agent Install it by referring to the procedure in "2.2 Software Required to be Installed in Advance (page 7)" Cautions before Performing Installation Be sure to exit all applications and Web browsers being used before starting the installation Installing the components of Managed Machine (Windows) 1. Insert the vdca/nwa install DVD into the DVD drive. 2. Execute the following command on the command prompt or Explorer to start the Virtual DataCenter Automation Standard Edition Integrated Installer. 33

42 Chapter 2. Performing installation by selecting functions > <Install DVD>:\install\Windows\vDCAInst_SE.exe 3. The installer starts up. 4. Select [Typical], and click [Next]. The [Selection of Function] screen is displayed. 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 SP1 redistributable package (x86)" may be required. Install the "Microsoft Visual C SP1 redistributable package (x86)" according to the screen. 7. Select the required items, and click [Edit] to set a value. For the setting values, see the table by the following procedure. 34

43 8. Set the setting items as required. Click the setting item and click [Edit], or double-click the setting item. The setting screen for the selected setting item opens. Chapter 2. Performing installation by selecting functions Item Name [Install Directory Path] [Template/Image] [Self Hostname] [Manager Hostname] [Manager Port] [Port for Agent Internal Communication] [Tenant ID] [Start Service] [Install DeploymentManager Client] [DeploymentManager - Management Server s IP Address] Value Specify the installation destination folder. The default value is "C:\Program Files (x86)\nec\vdca \Agent". Specify the folder path by using up to 55 characters. *1 Specify the machine type of the managed machine. The default value is "Yes". Specify "Yes" to create a virtual machine template. 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 is automatically added to the end on new installation. The UUID value can be checked on the [installation confirmation screen]. Specify the IP address or host name of the upper-level manager.* *2*3 Specify the port number specified in [Agent Port] in a management server configuration and [Agent Port] in a VM monitoring server configuration. The default value is "12520". Specify the port number for the agent internal communication. The default value is "25570". Specify the tenant ID of the tenant to which the managed machine will belong.* *3 After a new installation, specify whether to start the service of the SystemManager G agent (MasterScope UMF Operations Agent_104). If "No" is selected in [Template/Image], the default value is "Yes". *3*4 Specify whether to install the DeploymentManager client. The default value is "Yes" (Install). Specify the IP address (xxx.xxx.xxx.xxx format) of the DeploymentManager management server. *5*6 *1 Note that [Install Directory Path] and [Data Directory] are not case-sensitive. The following characters 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]. It is recommended to specify the fully qualified format (FQDN) (e.g., manager.domain.net.jp) or the 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. 35

44 Chapter 2. Performing installation by selecting functions *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]. The installation confirmation screen is displayed. 10. Check the details, and click [Start]. 11. Click [Yes] on the confirmation message displayed. Installation starts. 12. When the installation is complete, the installation result screen is displayed with the installation result. 36

45 Chapter 2. Performing installation by selecting functions 13. Click [Finish]. 14. Perform setting of the Managed Machine. See "2.14 Setting up the Managed Machine (page 53)" Installing the components of Managed Machine (Linux) Software Required to be Installed in Advance Before starting installation of the components of the Managed Machine, install the following software as required. NEC ESMPRO Agent Install it by referring to the procedure in "2.2 Software Required to be Installed in Advance (page 7)". Note Install some required packages and libraries by referring to the Managed Guest OS in Virtual DataCenter Automation First Step Guide. If the required package or library is not installed, it does not work properly Cautions before Performing Installation Depending on the environment, the files in the vdca/nwa install DVD may not be executed due to the execution right. In this case, execute the following commands to copy the fw/linux directory and Install/Linux directory of the vdca/nwa install DVD on a directory on the hard disk, execute the chmod command to give the execution right of all the files, and start install/linux/vdcainst.sh. 37

46 Chapter 2. Performing installation by selecting functions # 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 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. 2. Insert the vdca/nwa install DVD into the DVD drive. 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. # cd /mnt/dvd/install/linux 5. Execute vdcainst.sh. #./vdcainst_se.sh 6. The Virtual DataCenter Automation Standard Edition Integrated Installer starts up, and the following screen is displayed. Note If the installation screen is unstable, set the environment variable TERM to vt100, and start the installer again. Expand the terminal display size as needed. ************************************* 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. Please select the operation. (1:Typical 2:Custom q:quit program): Enter 1[Enter]. 38

47 Chapter 2. Performing installation by selecting functions (1:Typical 2:Custom q:quit program):1 7. Subsequently, the following screen of the Virtual DataCenter Automation Standard Edition Integrated Installer is 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 Products [ ] MasterScope Virtual DataCenter Automation Standard Edition Managed machine components Please select product(s) by entering numbers separated by commas. [Example: 1, 3, 4] (b:back q:quit program): Select MasterScope Virtual DataCenter Automation Managed machine components as shown below. (b:back q:quit program):1 9. The confirmation screen of the components to be installed is displayed Confirmation [*] MasterScope Virtual DataCenter Automation Standard Edition Managed machine components These product(s) will be installed, OK to continue? (default:y y:yes n:no q:quit program): Enter y[enter] to continue. 39

48 Chapter 2. Performing installation by selecting functions (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 Automation Standard Edition Managed machine components New Product (*) marked products or services objects require specific settings before installation 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]. (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. Item Name Install directory path Template/Image Self hostname Manager hostname Manager port Port for Agent Internal Communication Tenant ID Value 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 Specify the machine type of the managed machine. The default value is "[y]" (Yes). Specify "Yes" to create a virtual machine template. Specify the computer name of the Managed Machine. If it is omitted, a host name (e.g., agent.domain.net.jp) is automatically set. *2*3 If the number of specified characters is 26 or less, UUID is automatically added to the end on new installation. The UUID value can be checked on the [Confirmation screen]. Specify the IP address or host name of the upper-level manager. *2*3 Specify the port number specified in [Agent Port] in a management server configuration and [Agent Port] in a VM monitoring server configuration. The default value is "12520". Specify the port number for the agent internal communication. The default value is "25570". Specify the tenant ID of the tenant to which the managed machine will belong *3 40

49 Chapter 2. Performing installation by selecting functions Start service Item Name (Optional) Install DPM Client (Optional) IP address of the DPM management server Value Specify whether to start the [MasterScope SystemManager G Agent] services (MasterScope UMF Operations Agent_104) on new installation. The default value is "[y]" (Yes). *3*4 Specify whether to install the DeploymentManager client. The default value is "[y]" (Yes).* Specify the IP address (xxx.xxx.xxx.xxx format) of the DeploymentManager management server. *5*6 *1 Do not enter multi-byte characters such as Japanese in [Install directory path]. The following characters 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]. It is recommended to specify the fully qualified format (FQDN) (e.g., manager.domain.net.jp) or the 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. *5 If it is omitted, a management server is automatically searched for after completion of installation. *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 automatically added Confirmation Install directory path: /opt/nec/vdca/agent Template/Image: No Self hostname: redhat56.localdomain UUID Manager hostname: <Manager Host Name> Manager port: Port for Agent Internal Communication: Tenant 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]. (default:y y:yes n:no q:quit program):y 13. The configuration setting screen of the components to be installed is displayed again. 41

50 Chapter 2. Performing installation by selecting functions 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 Automation Standard Edition Managed machine components Is it OK to start installation? (default:y y:yes n:no q:quit program): Enter y[enter]. (default:y y:yes n:no q:quit program):y 15. The installation status is displayed, and the installation result is displayed at the end. Check that no error has occurred. MasterScope Virtual DataCenter Automation Standard Edition Managed machine components Preparing for Installation (1/1) MasterScope Virtual DataCenter Automation Standard Edition Managed machine components Installation in progress (1/1) Check rcfile ============================================================= Installation of MasterScope SystemManager G Agent was successful. ============================================================= MasterScope Virtual DataCenter Automation Standard Edition Managed machine components was successfully installed (1/1) Installation result MasterScope Virtual DataCenter Automation Standard Edition Managed machine components (Success) Success:1, Failure:0 Note When an installation error occurs, "Installation of <Product Name> was failure.[error Number]" is displayed in a message during installation. Check that this message is not displayed. 16. Perform setting of the Managed Machine. See "2.14 Setting up the Managed Machine (page 53)". 42

51 2.11 Registering and Setting up the Management Server This section describes license registration performed after installation of the components of the Management Server and the settings of the Management Server Registering License to SigmaSystemCenter Function Purchase the SigmaSystemCenter license in advance and register license. Further the license for evaluation for which everything's function of SSC can be used is registered by default and is effective for 60 days. 1. Start the SystemProvisioning Web Console. In the [Start] menu, select [SigmaSystemCenter] to start the [SystemProvisioning Web Console]. 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. Restart the following service. PVMService Registering License to SystemManager G Function Purchase the SystemManager G license in advance and register license. Further when installing Management Server, Trial Licenses is registered by default and is effective for 3 months. 1. Start up the console of the Management Server function. Execute the shortcut [MasterScope SystemManager G Console vdcmomsvc] created on the desktop or on the Start menu. 2. The [Login] screen is displayed. Enter the following default password to log in as an administrator. [Login name]: Administrator [Password]: websam 3. Click [Setting] and then [Configuration Mode] from the pull-down menu to enter the configuration mode. 4. Click [Setting] and then [License Management] from the pull-down menu. 5. The [License Management] dialog box is displayed. Click the [Product Code] tab and [Add]. 6. The [License Key Registration] screen is displayed. Input "ProductCode" and "LicenseKey". 7. Click [Registration]. Chapter 2. Performing installation by selecting functions 43

52 8. Record the string displayed in [Request Code], and click [Close]. 9. Delete all the trial version licenses registered during installation. On the [Product Code] tab, specify the licenses with "Trial License Key", and click [Delete]. When the confirmation dialog box is displayed, click [Yes]. 10. Click [OK]. 11. Shut down the console of the Management Server function. 12. Restart the following services. WebSAM UMF Operations Manager_102 Registration of the license keys to the operation management function is now complete. The registered license keys will expire in one month unless a "codeword" described in the next section is registered Registering Code Word to SystemManager G Function Acquire the code word of the license key registered to the SystemManager G function, and then register the code word as the procedure below. 1. Start up the console of the Management Server function. Execute the shortcut [MasterScope SystemManager G Console vdcmomsvc] created on the desktop or on the Start menu. 2. Click [Setting] and then [Configuration Mode] from the pull-down menu to enter the configuration mode. 3. Click [Setting] and then [License Management] from the pull-down menu. 4. On the [Product Code] tab, select the license of SystemManager G, and click [Registration]. 5. Enter the code word sent to [Codeword]. 6. Click [Registration] Virtual DataCenter Automation Standard Edition Portal setting For details of setting, refer to Chapter 5. Setting after the Installation in the MasterScope Virtual DataCenter Automation Standard Edition Portal User Manual (Install) Portal setting of Resource Management function If you want to use the Resource Management function, set the SigmaSystemCenter. For details of setting, refer to 4.1 Setting of SigmaSystemCenter in the MasterScope Virtual DataCenter Automation Standard Edition Portal User Manual (Install) Connect setting The setting is automatically registered on Virtual DataCenter Automation Standard Edition Installer as follows. Host Name: localhost Port number: Creating an IIS certificate and configuring the binding settings Acquiring and configuring the SigmaSystemCenter API key Chapter 2. Performing installation by selecting functions 44

53 The setting is automatically registered on Virtual DataCenter Automation Standard Edition Installer. Check the execution result of the following command to confirm the setting. > ssc apikey show CloudPortal UserName : CloudPortal Description : Portal for SigmaSystemCenter AccessKeyId : [AccessKeyId] SecretAccessKey : [SecretAccessKey] Execution end:0 Also refer to the set value of following key in the setting file.(c:\program Files (x86)\nec \vdca\mom\fw\tomcat\conf\nec\webframework.properties) product.cloudportal.provider.ssc.access.key.id product.cloudportal.provider.ssc.secret.access.key Connection Settings to ServiceGovernor If you want to use the Monitoring function, set the ServiceGovernor. For details of setting, refer to 4.2 Connection Settings to ServiceGovernor in the MasterScope Virtual DataCenter Automation Standard Edition Portal User Manual (Install). 1. Connection Settings The setting is automatically registered on Virtual DataCenter Automation Standard Edition Installer as follows. protocol: The protocol selected at the time of installation [Portal - ServiceGovernor connection protocol] ("http" or "https") Host Name: localhost Port Number: The port number selected at the time of installation [Application Server - HTTP(HTTPS) Port] (The default value is "12080(12443)") 2. Acquiring and Setting of the MasterScope Virtual DataCenter Automation API Key The setting is automatically registered on Virtual DataCenter Automation Standard Edition Installer. Check the execution result of the following command to confirm the setting. > cd "<Install folder>\tools" > WebApiTool.bat showkey cloudportal UserName : cloudportal Description : Portal for WebAPI Base Option AccessKeyId : [AccessKeyId] SecretAccessKey : [SecretAccessKey] NORMAL END. command exit code:0 COMMAND SUCCEEDED. Chapter 2. Performing installation by selecting functions 45

54 Also refer to the set value of following key in the setting file.(c:\program Files (x86)\nec \vdca\mom\fw\tomcat\conf\nec\webframework.properties) product.cloudportal.service.monitoring.provider.webapibase.access.key.id product.cloudportal.service.monitoring.provider.webapibase.secret.access.key Connection Settings to SystemManager G If you want to use the Monitoring function, set the WebAPI Base Option. For details of setting, refer to Chapter 3. Setting Up WebAPI Base Option in the MasterScope Virtual DataCenter Automation Service Governor WebAPI Base Option Installation Guide Setting SSL/TLS for a Manager Settings for Adding a Manager Setting SSL/TLS for Tomcat When doing the following setting at the time of Management Server installation ("2.3.8 Installing the components of Management Server (page 16)"), SSL setting of Tomcat is needed. [Portal - ServiceGovernor connection protocol]: "https" For details of setting, refer to Chapter 3. Setting Up WebAPI Base Option in the MasterScope Virtual DataCenter Automation Service Governor WebAPI Base Option Installation Guide Setting SSL/TLS for Tomcat Importing the Certificate Modifying the Tomcat Settings Changing env.bat Restarting the Service After the Tomcat Settings Are Monitored Default Settings of SystemManager G Function As the default setting to perform monitoring of Managed Machines, perform the setting of the performance monitoring function and disable the message monitoring function. The setting is performed on the console of the Management Server. 1. Start up the console of the Management server function. Execute the shortcut [MasterScope SystemManager G Console vdcmomsvc] created on the desktop or on the Start menu. 2. The [Login] screen is displayed. Enter the following default password to log in as an administrator. [Login name]: Administrator [Password]: websam 3. Click [Setting] and then [Configuration Mode] from the pull-down menu to enter the configuration mode. 4. Click [Setting] and then [Option] from the pull-down menu. 5. Select the [Performance Monitor] tab. 6. Specify 300 Sec. as the [Monitoring Interval] value. Chapter 2. Performing installation by selecting functions 46

55 Chapter 2. Performing installation by selecting functions Tip To change the setting value, determine the monitoring interval by referring to Specifications for Monitoring Settings in MasterScope SystemManager G Manual (Help) 7. Click [OK]. 8. Click [Setting] and then [Option]. 9. Select the [Message Monitor] tab. 10. Clear the [Use Message Monitor] check box. 47

56 Chapter 2. Performing installation by selecting functions 11. Click [OK] Pre-importing Monitoring Settings By presetting monitoring definitions for the VM to be provisioned, the monitoring definitions can be automatically applied when the provisioned agent is connected to the manager, and the monitoring process can start immediately. Configure the settings in the SystemManager G window according to the following flow. 1. Preparation There is a need to create a [Automation] group in the topology view of SystemManager before generating the first VM. Edit the configuration file of the following managers, you can generate a [Automation] group by re-start the manager. <Install folder>\manager\sg\sysmonmgr.ini As follows, and then written in the form of "Automation = 1" to the [SelfNode] section. [SelfNode] Automation=1 2. Preparing the monitoring definitions You can create the monitoring definitions to be imported by exporting definitions set to an agent. After setting definitions to an agent, create a definition file according to "Export the definition for the monitored agents and generate the definition file" in the SystemManager manual. For details about monitoring definitions, see "Monitor the agents" in the SystemManager manual. 48

57 Note Chapter 2. Performing installation by selecting functions If there is the filter settings for application log monitoring definition or event log monitoring definition or syslog monitoring definition, it is not in the definition files that are available in other agent. Please export [Display Setting] of the [Node] from then changed to "$NODE$". If you do not make this setting, because the value of the node of the message is not a message originating agent name, it can not be the message is properly monitored. 3. Importing monitoring definitions a. Start up the console of the Management server function. Execute the shortcut [MasterScope SystemManager G Console vdcmomsvc] created on the desktop or on the Start menu. b. Click [Setting] and then [Configuration Mode] from the pull-down menu to enter the configuration mode. c. Select the [Automation] group or its subgroup in [Topology View], right-click it, and select [Monitor Setting Import] from the displayed pop-up menu. d. When the [Group Import Service] window opens, click the [Browse] button, and then specify the directory containing the exported definition file. e. When a list of services that can be imported is displayed, select the check boxes for the services that you want to import. f. select the OS category to which the monitoring definitions will be applied from Windows or Linux and click the [OK] button. 49

58 Chapter 2. Performing installation by selecting functions If monitoring definitions have already been imported to the OS in the same category, the following overwrite confirmation message appears: If you click [OK], the current definitions are overwritten by the imported definitions. If you click [Cancel], the current definitions are not overwritten and remain unchanged. Two types of monitoring definitions for the Windows agent and the Linux agent can be imported into each group. Note If you move the target group out of the [Automation] group after the importing the settings, the imported monitoring definitions are deleted. If the agent is placed in the group to be imported, the monitoring definitions are applied to the agent. 4. Applying monitoring definitions After connected to the manager, the provisioned agent is placed in the tenant group under the [Automation] group. If the monitoring definitions were imported into the destination tenant group, the monitoring definitions are applied to the agent placed in the group. Note If the monitoring definitions were not imported into the destination group, the monitoring definitions are searched for in the parent group. If the monitoring definitions are found after searching up to the [Automation] group, those definitions are applied. 50

59 Chapter 2. Performing installation by selecting functions When monitoring definitions were imported into both the destination group and the parent group, the monitoring definitions in the child group are applied preferentially. If the OS category specified when importing the monitoring definitions differs from the OS of the agent, the monitoring definitions are not applied. If you move the agent, the monitoring definitions in the destination group or the parent group are applied Registering and Setting up the VM Monitoring Server This section describes license registration performed after installation of the components of the Virtual DataCenter Automation Standard Edition VM Monitoring Server and the settings of the VM Monitoring Server Registering the License to the SystemManager G Function Purchase the SystemManager G license in advance and register license. Further when installing VM Monitoring Server, Trial Licenses is registered by default and is effective for 3 months. 1. Start up the console of the VM Monitoring Server function. Execute the shortcut [MasterScope SystemManager G Console vdcrmsvc] created on the desktop or on the Start menu. 2. The [Login] screen is displayed. Enter the following default password to log in as an administrator. [Login name]: Administrator [Password]: websam 3. Click [Setting] and then [Configuration Mode] from the pull-down menu to enter the configuration mode. 4. Click [Setting] and then [License Management] from the pull-down menu. 5. The [License Management] dialog box is displayed. Click the [Product Code] tab and [Add]. 6. The [License Key Registration] screen is displayed. Input "ProductCode" and "LicenseKey". 7. Click [Registration]. 8. Record the string displayed in [Request Code], and click [Close]. 9. Delete all the trial version licenses registered during installation. On the [Product Code] tab, specify the licenses with "Trial License Key", and click [Delete]. When the confirmation dialog box is displayed, click [Yes]. 10. Click [OK]. 11. Shut down the console of the VM Monitoring Server function. 12. Restart the following services. WebSAM UMF Operations Manager_103 51

60 Registration of the license keys to the operation management function is now complete. The registered license keys will expire in one month unless a "codeword" described in the next section is registered Registering Code Word to SystemManager G Function Acquire the code word of the license key registered to the SystemManager G function, and then register the code word as the procedure below. 1. Start up the console of the VM Monitoring Server function. Execute the shortcut [MasterScope SystemManager G Console vdcrmsvc] created on the desktop or on the Start menu. 2. Click [Setting] and then [Configuration Mode] from the pull-down menu to enter the configuration mode. 3. Click [Setting] and then [License Management] from the pull-down menu. 4. On the [Product Code] tab, select the license of SystemManager G, and click [Registration]. 5. Enter the code word sent to [Codeword]. 6. Click [Registration] Default Settings of SystemManager G Function As the default setting to perform monitoring of Managed Machines, perform the setting of the performance monitoring function and disable the message monitoring function. The setting is performed on the console of the VM Monitoring Server. For the procedure, see " Default Settings of SystemManager G Function (page 46)" Pre-importing Monitoring Settings By presetting monitoring definitions for the VM to be provisioned, the monitoring definitions can be automatically applied when the provisioned agent is connected to the manager, and the monitoring process can start immediately. Configure the settings in the SystemManager G window according to the following flow. For the procedure, see " Pre-importing Monitoring Settings (page 48)". Chapter 2. Performing installation by selecting functions 2.13 Registering and Setting up the Stack Management Server This section describes license registration performed after installation of the components of the Stack Management Server. The procedure described in this section is required only for the configuration that uses the Virtual DataCenter Automation Standard Edition Topology Template Orchestrator Option Registering the License of Virtual DataCenter Automation Standard Edition Topology Template Registering License to Orchestrator Option Function For Virtual DataCenter Automation Standard Edition, it is necessary to purchase the license of the Virtual DataCenter Automation Standard Edition Topology Template Orchestrator Option. 52

61 For details about the license registration, refer to Chapter 11 vdca SE Topology Template Orchestrator Option operation settings of Virtual DataCenter Automation Standard Edition Portal User Manual (Resource Management) Topology Template Orchestrator Option and enable the vdca SE Topology Template Orchestrator Option Settings for connecting to SigmaSystemCenter Set the SigmaSystemCenter. For details of setting, refer to Settings for connecting to SigmaSystemCenter in the Virtual DataCenter Automation Standard Edition Topology Template Orchestrator Option User s Guide Settings for connecting to SystemManager G If you want to use the Monitoring function, set the SystemManager G. For details of setting, refer to Settings for connecting to MasterScope SystemManager in the Virtual DataCenter Automation Standard Edition Topology Template Orchestrator Option User s Guide TLS, SSL setting of OpenStack When connecting the Management Server and the Stack Management Server by SSL / TLS, SSL setting of OpenStack is needed. Set by referring to 2.3 Setting for SSL communication of Virtual DataCenter Automation Standard Edition Topology Template Orchestrator Option User s Guide Setting up the Managed Machine This section describes the settings of the Managed Machine performed after installation of the components of the Virtual DataCenter Automation Standard Edition Managed Machine Creating the VM Template of the Managed Machine After the components are installed on the Managed Machine, create VM templates of the Windows master VM and Linux master VM as required. Configure the following settings to change the automatic startup setting of the SystemManager G agent before creating the VM template. Windows Linux 1. Log into the master VM system with the Administrator account. 2. Stop the services of the installed SystemManager agent. Stop the following services: - MasterScope UMF Operations Agent_identifier_ If [Startup type] of the SytemManager G agent service is [Automatic], change it to [Manual]. 1. Log into the master VM system with the root account. 2. Stop the services of the installed SystemManager G agent. Stop the following services: - /etc/init.d/umfoperationsagent_ Delete the automatic startup setting of the SystemManager G agent. Chapter 2. Performing installation by selecting functions 53

62 Chapter 2. Performing installation by selecting functions # chkconfig --del UMFOperationsAgent_104 For details about how to create a VM template, see SigmaSystemCenter Configuration Guide. 54

63 Chapter 3. Basic setting after installation Chapter 3. Basic setting after installation This chapter describes the basic setting procedures for using Resource Management and Monitoring function of Virtual DataCenter Automation Standard Edition. Contents 3.1 Resource Management Function Monitoring Function

64 3.1 Resource Management Function Registering Related Products to the SigmaSystemCenter To link the Virtual DataCenter Automation and related products, register the related products in the SigmaSystemCenter. The related products to be registered are as follows: Virtualization infrastructure (VMware vcenter Server, Hyper-V cluster, KVM) Storage device (istorage, VNX, NetApp) Also, register the Virtual DataCenter Automation Standard Edition component in the SigmaSystemCenter. The component to be registered is as follows: DeploymentManager Register the related products to use in the SigmaSystemCenter by following the steps in this section. Tip For information about registering related products, refer to 4.2. Adding a Subsystem in the SigmaSystemCenter Configuration Guide Registering the Virtualization Infrastructure to the SigmaSystemCenter Register the virtualization infrastructure product in the SigmaSystemCenter. Registering the VMware vcenter Server 1. From the [Management] tree of the [Management] view, click [Subsystem]. From the [Configuration] menu, click [Add Subsystem]. 2. From the [Subsystem Type] pull-down box, select [VMware vcenter Server]. 3. Enter [Host Name], [User], and [Password]. Other text boxes can be left blank. Tip Note The default port number is (443) if it is omitted. For details of how to register, refer to Adding the VMware vcenter Server to the Subsystem in the SigmaSystemCenter Configuration Guide. Registering the Hyper-V cluster 1. From the [Management] tree of the [Management] view, click [Subsystem]. From the [Configuration] menu, click [Add Subsystem]. 2. From the [Subsystem Type] pull-down box, select [Hyper-V Cluster]. 3. Enter [Host Name], [Domain\User], and [Password]. Note Chapter 3. Basic setting after installation In [Domain\User], enter the domain name and account name to connect to the Hyper-V cluster separated by a backslash. 56

65 Tip For details of how to register, refer to Adding the Hyper-V cluster to the Subsystem in the SigmaSystemCenter Configuration Guide. Registering the KVM 1. Click [Virtual] from the [Virtual] tree in the [Virtual] view, and then click [Set KVM] from the [Configration] menu. 2. When the confirmation message box appears, click the [OK] button. Tip For the details about the method of registration, see 4.3. Managing ESXi, Hyper-V, and KVM in the SigmaSystemCenter Configuration Guide Registering a Storage Device to the SigmaSystemCenter Perform pre-setting of the storage, and then register the subsystem and disk array as described below. 1. Performing pre-setting of the storage To link the SigmaSystemCenter and the storage device, perform the following setting on the management server. istorage Set the SG file of the MasterScope istoragemanager Integration Base on the management server. a. Copy C:\Program Files (x86)\nec\ismsm\conf\ismsm.sample under the file name "ismsm.conf" in the same folder. b. Open ismsm.conf with the text editor, and set the IP address of the istoragemanager to ismsrv_addr. A setting example: [ismsm] ismsm_mode=api [server] #ismsvr_addr=xxx.xxx.xxx.xxx or hostname ismsvr_addr= #ismsvr_port=8020 c. Restart the [Integration Base] service. VNX or CLARiX Install Navisphere CLI, the management software of the VNX, on the management server. Add the path of Navisphere CLI to the environment variable PATH. NetApp Tip No operation is performed on the management server. For details of the setting, refer to Performing Pre-setting of Each Storage in the SigmaSystemCenter Configuration Guide. Chapter 3. Basic setting after installation 57

66 2. Registering the storage to the subsystem Register the storage management server to the SigmaSystemCenter as a subsystem as described below. a. From the [Management] tree of the [Management] view, click [Subsystem]. From the [Configuration] menu, click [Add Subsystem]. b. Select [NEC Storage], [EMC CLARiiON], or [NetApp Manager] according to the storage type. Tip For details of how to register, refer to Adding the Storage Management Server to the Subsystem in the SigmaSystemCenter Configuration Guide. 3. Registering a disk array Register a disk array to the SigmaSystemCenter as described below. a. From the [System Resource] tree of the [Resource] view, click [Storage]. From the [Configuration] menu, click [Register/Delete Disk Array]. b. For the NEC Storage, select the disk array to register from [Unmanaged Disk Array List], and click [OK]. c. For the VNX and NetApp, click [Add and Register] in [Unmanaged Disk Array List]. Tip For details of how to register, refer to 4.7. Registering a Storage in the SigmaSystemCenter Configuration Guide Registering a Virtual DataCenter Automation Component to the SigmaSystemCenter Register the DeploymentManager, component of the Virtual DataCenter Automation, to the SigmaSystemCenter as a subsystem. 1. From the [Management] tree of the [Management] view, click [Subsystem]. From the [Configuration] menu, click [Add Subsystem]. 2. From the [Subsystem Type] pull-down box, select [DPM Server]. 3. Enter [Host Name] and [Password]. Other text boxes can be left blank. Tip Note In [Password], enter the password set for the user "deployment_user" registered in the DPM server. The default password is (dpmmgr). For information on how to register, refer to Adding the DPM Server to the Subsystem in the SigmaSystemCenter Configuration Guide Performing Various Settings of the SigmaSystemCenter Perform various settings of the Virtual DataCenter Automation Standard Edition. Chapter 3. Basic setting after installation From the [Management] tree of the [Management] view, click [Environment]. Open the [Virtual Resource] tab in the [Environment Setting] window to perform the following setting. 58

67 Setting the capacity value and cost value By default, the capacity value of the VM server is 200 and the cost value of a virtual machine is 10, so the number of virtual machines available on each VM server is restricted to 20. If this restriction on the number of units could be an issue in capacity management with the resource pool, set a sufficiently large capacity value for the cost value to virtually disable the restriction. Tip For details of how to specify the capacity value and cost value, refer to Capacity Control of the Virtual Machine Server in the SigmaSystemCenter Reference Guide. Setting the root password of the VMware ESXi Tip Set the root password of the ESXi. The password specified here is used as the default for all ESXis. Note To set an account and password for each VM server, perform setting from the subsystem edit window for each VM server. For the details of environmental setting, see 4. Configuring the Environment in the SigmaSystemCenter Configuration Guide Performing Hardware Settings of the VM Server A VM server is established about hardware. " Registering VM Server on SigmaSystemCenter (page 59)", for, indispensable setting. The case you'd like to make a VM server manage in OOB Management when do " Performing Setting to Manage the VM Server with the OOB Management (page 60)" Registering VM Server on SigmaSystemCenter The setting to register a VM server as a management target of SigmaSystemCenter is performed. When registering a VM server, a resource group is designated. Please register along the following procedure. 1. [Machine] is clicked from a [System Resource] tree of a [Resource] view and [Add Group] from the [Configuration] menu is clicked. 2. The resource group name is input on the [Add Group] screen, and [OK] is clicked. 3. The group made from a [System Resource] tree is clicked and [Register Machine] is clicked from the [Configuration] menu. 4. [OK] is clicked including a check in the VM server a [Register Machine] screen registers from [Unmanaged Machine List]. Tip Chapter 3. Basic setting after installation For details of how to make a category, refer to Registering a Machine in the SigmaSystemCenter Configuration Guide. 59

68 Performing Setting to Manage the VM Server with the OOB Management Perform setting to manage the VM server with the OOB Management of the SigmaSystemCenter. perform setting to manage the registered VM server with OOB Management. For the OOB Management setting procedure, refer to Performing Pre-setting for Using Out-of-Band (OOB) Management in the SigmaSystemCenter Configuration Guide. The points for setting OOB Management are as follows: Required setting for OOB Management To use the OOB Management, BMC must be set to a connectable state. Perform BMC setting by referring to the following sections in the SigmaSystemCenter Configuration Guide Setting an IP Address of BMC Creating a User with Administrator Rights in BMC Setting to use other functions Perform setting of the functions corresponding to the following sections in the SigmaSystemCenter Configuration Guide as required: Setting a PET Report Destination and Report Level in BMC Enabling a Dump Enabling ACPI Shutdown Setting SOL (Serial Over Lan) Setting the Machine Properties of the VM Server From the [Resource] view of the SigmaSystemCenter, set the machine properties of the VM server (This setting is option). The icon of the VM Server for property setting is clicked from a [System Resource] tree of a [Resource] view. [Property] is clicked from a [Configuration], then please set for each tab from a [Machine Property Setting] view. Tip For details, refer to 4.10 Setting Machine Properties in the SigmaSystemCenter Configuration Guide. The points for setting machine properties are as follows: [Network] tab Chapter 3. Basic setting after installation - Assign an NIC number to the MAC address corresponding to the NIC used in the VM server. No number needs to be set for an unused NIC. - The numbering of NIC must be uniform for each of the roles of NIC within the resource pool. For example, when the NICs installed in the VM server have the following roles, assign numbers similarly for all the VM servers in the resource pool: Role of NIC NIC connected to the operations management LAN 1 NIC connected to the provider administration VLAN, tenant administration VLAN, production VLAN NIC used for Live Migration 3 2 NIC number 60

69 Chapter 3. Basic setting after installation Role of NIC NIC used for NAS connection 4 NIC number - No setting is required for the switch and port of the connection destination of NIC. [Storage] tab - Add an HBA connected to storage devices for creating a datastore, and set an HBA number. No number needs to be added for an HBA connected to a storage device without a datastore. - The numbering of HBA must be uniform for each of the roles of HBA within the resource pool. For example, when the HBAs installed in the VM server have the following roles, assign numbers similarly for all the VM servers in the resource pool: [Account] tab Role of HBA HBA connected to istorage 1 HBA connected to VNX or CLARiX 2 HBA number Set the IP address and account information of the BMC installed on the VM server to manage the VM server with the OOB Management Creating a Resource Pool Create an operation group of the VM server with the SigmaSystemCenter, and then define the operation group of the VM server as a resource pool Creating a Category of the VM Server To manage operation groups of the VM server in a hierarchical structure on the [Operation] view of the SigmaSystemCenter, create a category to store the operation groups of the VM server. The icon of the Category to be added or a [Operations] is clicked from a [Operations] tree of a [Operations] view. [Add Category] is clicked from a [Configuration] menu, please enter [Name] and [OK] is clicked. The points for creating a category of the VM server are as follows: Settings of the resource pool, DPM server, and optimized startup are not required. Tip For details of how to make a category, refer to 5.2. Adding a Category in the SigmaSystemCenter Configuration Guide Creating an Operation Group of the VM Server To define the VM server as a resource pool, create an operation group of the VM server with the SigmaSystemCenter. The points for creating an operation group of the VM server are as follows: Create operation groups of the VM server in the following management units: - For VMware: DataCenter or cluster - For Hyper-V: Hyper-V cluster - For KVM: DataCenter or cluster 61

70 OS type of the operation groups of the VM server as follows: Tip - For VMware: Linux - For Hyper-V: Windows Server - For KVM: Linux For details of how to create an operation group, refer to 5.3. Adding an Operation Group in the SigmaSystemCenter Configuration Guide Setting an Operation Group of the VM Server Add the host of the VM server to the operation group of the VM server with the SigmaSystemCenter. Also, perform optimized placement setting, setting to exclude datastores from VM creation destination candidates, and setting of live monitoring and performance monitoring. Set an operation group via the following steps: 1. Click the operation group of the VM server. 2. In the [Host] tab, add hosts for the number of VM servers. a. Click [Add]. b. Enter the host name of the VM server in [Host Name]. Note An after step is option setting. It is not a required setting. 3. In the [Host] tab, set the IP address information for each of the VM servers. a. Refer to the [Host List] group box, and click [Property] of the host. b. Select the [Network] tab. c. Click [Add] to add the NIC to be connected to the operations management LAN. i. In [NIC Number], select the NIC number of the NIC connected to the operations management LAN. ii. Click [Add] and enter the management IP address of the VM server. iii. In [Management IP Address], select the management IP address of the VM server. d. To use NAS, click [Add] to add the NIC to be connected to the LAN for NAS. i. In [NIC Number], select the NIC number of the NIC connected to the LAN for NAS. ii. Tip Click [Add] and enter the IP address of the NIC used for NAS connection. For NIC numbers, refer to " Setting the Machine Properties of the VM Server (page 60)". 4. When using the function of the VM Optimized Placement, Optimized Placement is established. a. Click [Property] on the [Setting] menu. Chapter 3. Basic setting after installation b. Set [High Load Bound], [Target Region] and [Low Load Bound] on the [VM Optimized Placement] tab. 62

71 c. Set a monitoring profile to watch the state of the CPU on the[performance Monitor] tab. d. Click [Apply]. Tip Refer to after steps for [Performance Monitor] tab setttings. 5. In the [Alive Monitor] tab, set whether the VM server is registered to the ESMPRO/ ServerManager. If the ESMPRO/ServerAgent is installed in the VM server, select [Register a machine in the group to NEC ESMPRO Manager]. If the ESMPRO/ServerAgent is not installed in the VM server, clear [Register a machine in the group to NEC ESMPRO Manager]. Tip Normally, the ESMPRO/ServerAgent is installed in the ESX and Hyper-V. The ESMPRO/ ServerAgent is not installed in the ESXi. 6. To use VM optimized placement or perform performance monitoring of the VM server, set the [Performance Monitor] tab. Tip a. Select [Performance Data Collection Settings] check box. b. In [Profile Name], select [Standard Monitoring Profile (x min)] or [Physical Machine Monitoring Profile (x min)]. (Refer to the following related information.) Tip For details of the monitoring profile of performance data, refer to Appendix A Monitoring profile in the SigmaSystemCenter Configuration Guide. c. Set the IP address and port number for System Monitor - Performance Monitoring Services. d. Set the account of the VM server used to obtain performance data. For details of the operation group setting, refer to 5.5. Setting Group Properties in the SigmaSystemCenter Configuration Guide Defining a Resource Pool Define a resource pool for the operation group of the VM server. To add a resource pool, click [Create] of [Resource Pool] from the [Configuration] menu of the operation group of the VM server. The points for defining a resource pool are as follows: Chapter 3. Basic setting after installation Set the resource pool type to [Shared] so that the resource pool is not directly allocated to the category. Instead of allocating the resource pool directly, a sub-pool is extracted and allocated. For the vcpu unit, setting in [Frequency] is recommended. By specifying the virtual CPU unit in frequency, a virtual CPU of the specific specifications can be issued to the tenant independent of the specifications of the physical CPU of the VM server. 63

72 Tip For detail of the defining a resource pool, refer to Adding a Resource Pool in the SigmaSystemCenter Configuration Guide Allocating a Sub-pool Define a Sub-pool for the operation group of the VM server. The points to be noted when creating a Sub-pool are described below. Click the operation group of the VM server under the [Operations] tree in the [Operations] view, open the [Resource Pool] tab and click Create [Sub-pool]. Specify the assignment destination category in [To assign to a group]. Select the "Allow Overcommit Resources" check box to enable overcommitting. This allows you to extract the necessary size of CPU, memory, and storage resources as a sub-pool regardless of the remaining amount of physical resources in the resource pool. Tip For detail of the allocating a Sub-pool, refer to Dividing a Resource Pool into a Sub-Pool in the SigmaSystemCenter Configuration Guide Registering a VM Server Resource Add a CPU resource and memory resource to the resource pool by adding each VM server to the operation group of the VM server of the SigmaSystemCenter. The method to add a VM server to the operation group is as follows: 1. Refer to the [General] tab of the operation group of the VM server. 2. Perform the following for each VM server to be added to the operation group: a. In [Host List], select one host that executes the allocation of the VM server. b. Click [Register Master]. c. Select [Select a machine from shared pool]. d. Select the VM server to allocate to the host. e. The confirmation screen is displayed. Click [Finish]. 3. Perform setting so that disks in which no virtual disk should be allocated (such as the system disk) will not be used. Tip a. From the [Configuration] menu of the operation group of the VM server, click [Property]. b. Click [Datastore Setting] tab. c. Refer to the [Datastore List] group box, and click [Edit] for each datastore with [VM Destination] selected but not used for the creation destination of the VM. d. Clear the [As candidate destination of vm] check box. Chapter 3. Basic setting after installation For details, refer to Registering a Master Machine in the SigmaSystemCenter Configuration Guide. 64

73 3.1.6 Registering a Logical Network In SigmaSystemCenter, the logical network that need to be registered to handle virtual network, you need to be registered in advance. For details of how to register logical network, refer to 4.5. Adding a Logical Network in the SigmaSystemCenter Configuration Guide and MasterScope Virtual DataCenter Automation Standard Edition Portal User Manual(Resource Management). For the configuration that uses the Virtual DataCenter Automation Standard Edition Topology Template Orchestrator Option, the template provisioning function enables to create a logical network from the Virtual DataCenter Automation Standard Edition portal. When permitting register logical network to users, set by referring to Network setting method of Virtual DataCenter Automation Standard Edition Topology Template Orchestrator Option User s Guide. Also, as for the method of creating the topology template including the network, refer to Appendix B. Topology Template Format of Virtual DataCenter Automation Standard Edition Topology Template Orchestrator Option User s Guide Registering a Storage Resource Add a disk volume to the resource pool with the SigmaSystemCenter. Also, set the and tags. Note The Hyper-V does not support the NAS environment Allocating a Disk Volume Create a SAN or NAS disk volume and add it to the resource pool via the following steps: Note If a dialog box that prompts for the maintenance mode is displayed while you are working on the Web Console of the SigmaSystemCenter, turn on the maintenance mode to continue the operation. After the operation is complete, be sure to turn off the maintenance mode. 1. The icon of the group of the machine to be turned on maintenance mode is clicked from a [Operations] tree of a [Operations] view. 2. Select the check box of the machine to be turned on maintenance mode from [Host List] group box or [Group Pool] group box. 3. Click [Maintenance On] from [Operation] menu. 4. If the machine is turned off maintenance mode, click [Maintenance Off] from [Operation] menu. For the maintenance mode, refer to Turning On/Off the Maintenance Mode in the SigmaSystemCenter Configuration Guide. 1. Creating and registering a disk volume Chapter 3. Basic setting after installation To create a new disk volume without using an existing disk volume, create a disk volume. Next, by using the Web Console of the SigmaSystemCenter, select a disk array from the [Resource] view, and click [Register Disk Volume] to register the disk volume as a management target. For details, refer to Registering a Disk Volume in the SigmaSystemCenter Configuration Guide. 65

74 Note To make the newly created disk volume recognized by the SigmaSystemCenter, select the storage registered in [Subsystem] of the [Management] view, and click [Collect]. 2. Performing setting for disk volume allocation a. By using the Web Console of the SigmaSystemCenter, click [Operations] on the title bar to switch to the [Operations] view. b. From the [Operations] tree of the Web Console, click the icon of the target operation group to display detailed information of the operation group in the main window. c. From the [Host List] group box, perform the following for each of the hosts to which the disk volume is to be allocated: Tip i. Click [Property] of the host to which the disk volume is added, select the [Storage] tab, and click [Add]. ii. Select the SAN disk array in [Disk Array] of [Storage Information], and perform setting as follows: A. Enter LUN in [LUN Number] as required. B. [Connect after distribution] need not be selected. C. From [Storage List], select the disk volume to allocate to the VM server. D. In the [HBA information], select [Specify an HBA to connect] and enter the HBA number. Tip For HBA numbers, refer to " Setting the Machine Properties of the VM Server (page 60)". iii. Select the NAS disk array in [Disk Array] of [Storage Information], and perform setting as follows: A. From [Storage List], select the disk volume to allocate to the VM server. B. In [The exported IP address of the destination host], select the IP address allocated to the NIC for NAS connection. For details of the procedure, refer to Configuring Settings on the Storage Tab (if the Model Type is Physical or VM Server) in the SigmaSystemCenter Configuration Guide. 3. Performing disk volume allocation a. By using the Web Console of the SigmaSystemCenter, click the icon of the target operation group from the [Operations] tree to display the detailed information of the operation group on the main window. Select all the check boxes of the target VM server, and click [Change Configuration] in the [Machine Individual Operations...] menu. b. Under [Customize Processing for Selected Machine.], a list of processing for configuration change is displayed. Select only the [Modify Storage] check box, and click [OK]. 4. Making the disk volume recognized by the virtualization infrastructure VMware vcenter Server management environment Chapter 3. Basic setting after installation Format the disk volume for the datastore in VMFS by using the vcenter Server. 66

75 Hyper-V cluster environment By using the failover cluster manager, add the disk volume for datastore in [Storage], and then add the disk volume for datastore added to [Storage] to [Cluster Shared Volumes]. 5. Making the disk volume recognized by the SigmaSystemCenter By using the Web Console of the SigmaSystemCenter, select [VMware vcenter Server] or [Hyper-V Cluster] registered in [Subsystem] on the [Management] view, and click [Collect] Setting a Storage Tag By using the Web Console of the SigmaSystemCenter, set a tag to the datastore. For example, by set a tag to each of the disk volumes according to the service level of the storage device such as "Gold", "Silver", and "Bronze", storage resources at different service levels can be provided. 1. Open the [Resource Pool] tab of the operation group of the VM server. 2. In [Datastore List], click [Edit] of the datastore to which the tag is set, and enter the tag About using Resource Manager Function For details about how to Virtual DataCenter Automation Standard Edition Resouce Manager Function, see below. Virtual DataCenter Automation Standard Edition Portal User Manual (Resouce Management) For the configuration that uses the vdc Automation Standard Edition Topology Template Orchestrator Option, refer to the following manual: Virtual DataCenter Automation Standard Edition Portal User Manual (Resource Management) Topology Template Orchestrator Option 3.2 Monitoring Function Configuring the Monitoring Manager After creating a tenant by using Virtual DataCenter Automation Standard Edition Portal, you must configure the monitoring manager used by the tenant. For details about how to configure the settings, see Virtual DataCenter Automation Standard Edition Portal User Manual (Monitoring) Chapter 3 Operation Flow 3.2 Registering a tenant 3.3 Setting of Monitoring Agent Note For Monitoring manager and port, specify Self hostname and Agent port specified at the time of installation Setting up DeploymentManager Chapter 3. Basic setting after installation To configure the initial settings for the monitoring agent when provisioning the VM, register a scenario to distribute and execute the script for initial settings in SigmaSystemCenter (and DeploymentManager). 67

76 The script for initial settings is stored under (application server installation directory)\tomcat\portal \bin. Use one of the following files according to the OS type. Windows OS : SetupMonitoring.bat Linux OS : SetupMonitoring.sh Note Use CRLF in a Windows OS and LF in a Linux OS as the linefeed code in the script for initial settings. 1. Registering an application in DeploymentManager(DPM) Chapter 3. Basic setting after installation Register the script for initial settings for each OS type as an application by using the DPM image builder. For details about how to register an application by using the image builder, see the DPM manual. Specify the following values at registration. Register the default values as is for items not shown below. Setting item Settings in Windows OS Settings in Linux OS Package ID WindowsSetupMonitoring LinuxSetupMonitoring Type [Execution Settings] tab - Execution file [Applicable OS and language] tab - OS [Applicable OS and language] tab - Lang Application SetupMonitoring.bat SetupMonitoring.sh ALL OS ALL Language 2. Creating a DPM scenario group Create a DPM scenario group with any name. For details about how to create a scenario group, see the DPM manual. 3. Adding a scenario to the scenario group Add a scenario to the scenario group that you created. For details about how to add a scenario, see the DPM manual. Specify the following values when adding a scenario. Setting item Settings in Windows OS Settings in Linux OS Scenario name WindowsSetupMonitoring LinuxSetupMonitoring [Package] tab - Package [Package] tab - Execution Timing Setting Add Local- WindowsSetupMonitoring Add Local-LinuxSetupMonitoring The [Execute Immediately After Distribution] check box is selected. 4. Registering software in SigmaSystemCenter To register a scenario that you created in DPM in SigmaSystemCenter, collect software by using the SigmaSystemCenter Web console. For details about how to collect software, see the SigmaSystemCenter manual. 5. Setting the DPM server to the SigmaSystemCenter operation group 68

77 Chapter 3. Basic setting after installation To enable software distribution by DPM, set the DPM server to each of the SigmaSystemCenter operation groups used by Virtual DataCenter Automation Standard Edtion Portal. For details about how to configure the settings, see the SigmaSystemCenter manual. The SigmaSystemCenter operation group used by Virtual DataCenter Automation Standard Edtion Portal differs depending on whether the resource pool used for VM provisioning is dedicated to the tenant or shared. When using a resource pool dedicated to the tenant, configure the DPM server for the operation group corresponding to the relevant tenant. (The group name is the tenant ID.) The relevant operation group is automatically created in SigmaSystemCenter when you create a tenant by using Virtual DataCenter Automation Standard Edition Poratal. (The group category is "tenant.") When provisioning the VM by using a shared resource pool, create the operation group under the shared resource pool name (the group category is "category") and configure the DPM server Setting up Virtual DataCenter Automation Standard Edition Portal Specify the path to store the monitoring agent execution file in the Virtual DataCenter Automation Standard Edition Portal configuration file for each template before assigning a VM. Specify the following items in (application server installation directory)\tomcat\conf\nec \webframework.properties. product.cloudportal.template.monitoring.agent.setup.path.<template name> = <File path of the agent execution file> The agent execution file is stored in bin in the agent installation location. The following is a setting example for installation in a Windows OS using the default installation destination. product.cloudportal.template.monitoring.agent.setup.path.templatea = C\:\ \Program Files (x86)\\nec\\umf\\operations\\agent\\bin About using Monitoring Function For details about how to Virtual DataCenter Automation Standard Edition Monitoring Function, see below. Virtual DataCenter Automation Standard Edition Portal User Manual (Monitoring) For the configuration that uses the vdc Automation Standard Edition Topology Template Orchestrator Option, refer to the following manual: Virtual DataCenter Automation Standard Edition Portal User Manual (Monitoring) Topology Template Orchestrator Option 69

78 Chapter 4. Performing Uninstallation Chapter 4. Performing Uninstallation This chapter describes how to uninstall the components. Contents 4.1 Precautions before Uninstallation Uninstalling the components of Management Server Uninstalling the components of Management Server Console Uninstalling the components of VM Monitoring Server Uninstalling the components of VM Monitoring Server Console Uninstalling the Stack Management Server Uninstalling the components of Managed Machine(Windows) Uninstalling the components of Managed Machine(Linux)

79 4.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. 4.2 Uninstalling the components of Management Server 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. Chapter 4. Performing Uninstallation 3. Click [Next]. The screen for selecting components to uninstall is displayed. 71

80 Chapter 4. Performing Uninstallation 4. Check all the check boxes of the following components to be uninstalled, and then click the [Next] button. SigmaSystemCenter SystemProvisioning 6.6 SystemMonitor- Performance Monitoring Services 5.9 DPM server 6.6 ESMPRO/ServerManager 6.16 The [Configure SystemProvisioning] screen is displayed. 72

81 Chapter 4. Performing Uninstallation 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, and click [Next]. 73

82 Chapter 4. Performing Uninstallation The [Uninstall SigmaSystemCenter] screen is displayed. 7. Click [Uninstall]. After all the components are uninstalled, the [Finish] screen is displayed. Note After the uninstallation of NEC ESMPRO Manager, the message "This program might not have uninstalled correctly" may be displayed after completing the uninstallation, depending on the environment. The uninstallation has been completed without any errors. Click [This program uninstalled 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. MasterScope UMF Operations Manager_102 Apache Tomcat 8.0 ServiceGovernor 10. Execute the following command to delete database. > sqlcmd -E -S ".\<Portal - SQL Server Instance Name>" 1> drop database cloudportal 2> go 1> drop login cpuser 2> go 1> exit Tip The default of <Portal - SQL Server Instance Name> is "FWCMDB". 11. Insert the vdca/nwa install DVD into the DVD drive. 74

83 Chapter 4. Performing Uninstallation 12. Execute the following command on the command prompt or Explorer to start the Virtual DataCenter Automation Standard Edition Integrated Installer. > <Install DVD>:\install\Windows\vDCAInst_SE.exe 13. The installer starts up. 14. Select [Custom], and click [Next]. 15. Select [MasterScope Media], and click [Run]. The MasterScope framework media installer starts up. 16. Select the [Uninstall] radio button, and click [Next]. The [Uninstallation Selection] screen is displayed. 17. Select the check boxes of the following components. following components under [Manager]-[Service 102] 18. Click [Next]. - MasterScope SystemManager G The [Uninstallation Confirmation] screen is displayed. 19. Check [Target products:], and click [Start]. Uninstallation of the selected components is performed. When uninstallation is complete, the [Finish] screen is displayed. 20. Click [Finish]. 21. Delete Application Server(Tomcat) Service. 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\mom\fw\tools C:\Program Files (x86)\nec\vdca\mom\fw\tomcat Note Java that has been installed cannot be uninstalled. Uninstall other programs that are not used. 22. Delete the following registry: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\vDCAInst\APServer HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\vDCAInst\MOM HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\vDCAInst\Portal HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\vDCAInst \WebAPIBase 23. The "Install Directory Path" specified during installation may remain. Delete it if it is unnecessary. 75

84 4.3 Uninstalling the components of Management Server Console 1. Insert the install DVD into the DVD drive. 2. Execute the following command on the command prompt or Explorer to start the Virtual DataCenter Automation Standard Edition Integrated Installer. > <Install DVD>:\install\Windows\vDCAInst_SE.exe 3. The installer starts up. 4. Select [Custom], and click [Next]. 5. Select [MasterScope Media], and click [Run]. The MasterScope framework media installer starts up. 6. Select the [Uninstall] radio button, and click [Next]. The [Uninstallation Selection] screen is displayed. Chapter 4. Performing Uninstallation 7. Select the check boxes of the following components under the services with the service identifier specified during installation of the Management Server Console. MasterScope SystemManager G 76