Embed Size (px)
Citation preview
MasterScope Virtual DataCenterAutomation Media v3.0
Release Memo
1st EditionJune, 2016
NEC CorporationRWT00WN5030E-I01-1
DisclaimerThe copyrighted information noted in this document shall belong to NEC Corporation.
Copying or revising this document, in whole or in part, is strictly prohibited without thepermission of NEC Corporation.
This document may be changed without prior notice.
NEC Corporation shall not be liable for any technical or editing errors or omissions in thisdocument.
NEC Corporation shall not be liable for the accuracy, usability, or certainty of information notedin this document.
Copyright Information• SigmaSystemCenter, MasterScope, Network Manager, NEC Storage, ESMPRO,
EXPRESSBUILDER, EXPRESSSCOPE, SIGMABLADE, UNIVERGE, andProgrammableFlow are registered trademarks of NEC Corporation.
• VMware is a trademark or registered trademark of VMware, Inc. in the United States and othercountries.
• Microsoft, Windows, Windows Server, Windows Vista, Internet Explorer, SQL Server, andHyper-V are trademarks or registered trademarks of Microsoft Corporation in the United Statesof America and other countries.
• Linux is a trademark or registered trademark of Linus Torvalds in the United States of Americaand other countries.
• Red Hat is a trademark or registered trademark of Red Hat, Inc. in the United States and othercountries.
• Intel and Itanium are trademarks or registered trademarks of Intel Corporation in the UnitedStates of America and other countries.
• Apache, Apache Tomcat, and Tomcat are trademarks or registered trademarks of ApacheSoftware Foundation.
• Oracle, Solaris, Java, and WebLogic are registered trademarks of Oracle Corporation and itssubsidiaries and affiliates in the United States of America and other countries.
• SAP is a trademark or registered trademark of SAP AG in Germany and other countries.
• Fortinet, FortiGate, and FortiGuard are registered trademarks of Fortinet, Inc. Other Fortinetproducts contained in this guide are trademarks of Fortinet, Inc.
• Thunder Series and AX Series of A10 Networks is a registered trademark of A10 Networks,Inc.
• Catalyst, IOS, Cisco IOS, Cisco, Cisco Systems, and Cisco logo are trademarks or registeredtrademarks of Cisco Systems, Inc. in the United States of America and other countries.
• F5, F5 Networks, F5 logo, and product names in the text are trademarks or registeredtrademarks of F5 Networks, Inc. in the United States of America and other countries.
Other system names, company names, and product names in this document are trademarks orregistered trademarks of their respective companies.
i RWT00WN5030E-I01-1
The ® and ™ marks are not included in this document.
Notes on exporting this productIf this product (including its software) is subject to regulation under the Foreign Exchange andForeign Trade Law, it will be necessary to follow the procedures required by this law when exportingthis product, such as obtaining an export license from the Japanese Government. If you requiredocuments from NEC in order to obtain an export license, please contact the dealer where youpurchased your MasterScope product, or your local NEC sales office.
ii RWT00WN5030E-I01-1
PrefaceThank you for always using our products. This document describes how to use MasterScope VirtualDataCenter Automation Media at your company.
iii RWT00WN5030E-I01-1
ContentsChapter 1. MasterScope Virtual DataCenter Automation....................................................... 1
1.1 Product Contents...................................................................................................................2
1.2 New functions and fixed problems ........................................................................................31.2.1 New functions .............................................................................................................31.2.2 Fixed problems............................................................................................................4
1.3 Component............................................................................................................................5
Chapter 2. Media Configuration ................................................................................................ 72.1 Directory Configuration ........................................................................................................8
2.2 Product document (/doc) .......................................................................................................8
2.3 Installers other than SigmaSystemCenter and SERCUREMASTER (/fw).............................8
2.4 Virtual DataCenter Automation Integrated Installer(/install) .................................................9
2.5 Code word application form (/licenseform)...........................................................................9
2.6 License clauses (/oss_license) ...............................................................................................9
2.7 Sample script(/script) ............................................................................................................9
2.8 Virtual DataCenter Automation Standard Edition (/SE) ........................................................9
2.9 Identity Manager installer (/securemaster).............................................................................9
2.10 SigmaSystemCenter installer (/ssc) .....................................................................................9
Chapter 3. Operating Environments........................................................................................ 10
Chapter 4. License...................................................................................................................... 114.1 License Key ........................................................................................................................12
4.2 Software License Information .............................................................................................12
Chapter 5. Precautions and Restrictions ................................................................................. 13
iv RWT00WN5030E-I01-1
Chapter 1. MasterScope Virtual DataCenterAutomation
Contents1.1 Product Contents..........................................................................................................................2
1.2 New functions and fixed problems ...............................................................................................3
1.3 Component...................................................................................................................................5
Chapter 1. MasterScope Virtual DataCenter Automation
1 RWT00WN5030E-I01-1
1.1 Product ContentsMasterScope Virtual DataCenter Automation is software making it possible to achieve infrastructuremanagement of the cloud system data center.
TipFirst-time users read Virtual DataCenter Automation First Step Guide.
MasterScope Virtual DataCenter Automation makes it possible to perform the following functions.
• Resource pool management
IT infrastructures owned (networks, storages, and servers) are managed as shared resources inpools. Responding to requests from service users, the managed shared resources can be properlyallocated.
• Orchestration/Provisioning
In response to requests from service users, required processes such as creation of a virtualmachine from a template, network setting, storage allocation, and middleware installation areexecuted according to the workflow. Validated workflows are provided that can reduce SI costsincluding customization.
By using the OpenFlow technology in the same DC, different VLANs can be handled as one bignetwork segment, and virtual servers can be assigned according to requests from IaaS userswithout being aware of the specifications of physical resources.
• Resource control
Menu for operation and instruction of virtual machines is provided. Startup and shutdown ofvirtual machines, backup (snapshot) creation, and restore instruction are available.
• Monitoring
Information about usage of virtual machines (CPU and memory) is collected and accumulated.The accumulated information can be output in CSV format to be utilized as source informationfor billing, etc.
• Software repository
Templates, OS images, middleware, and patches that the provider provides for tenants can bemanaged in an integrated fashion to reduce operation costs. It can be shared among multiplemanagement servers.
• Integrated ID management
To utilize various ICT resources in a data center within an appropriate function range, individualauthentication and an approval framework are required. Users registered in the service portalcan be managed in an integrated fashion. By linking with the operation management functionand network devices, operation with an integrated login account can be performed. Thiseliminates the need to set user registration and right individually to the operation managementfunction and each of network devices, which reduces management and operation costs.
• Large-scale implementation
By using hierarchical management servers, tens of thousands of virtual machines can bemanaged.
• Provisioning of physical machines
Chapter 1. MasterScope Virtual DataCenter Automation
2 RWT00WN5030E-I01-1
As a resource to assign to tenants, Virtual DataCenter Automation is compatible not only withvirtual machines on the virtualization base, but also with physical machines. Existing physicalmachines can be used effectively.
• Tenant network visualization
Tenant networks assigned by Virtual DataCenter Automation (VLANs, tenant firewalls, loadbalancers, etc.) and the logical configuration diagrams in the servers allocated to those networkscan be automatically created and checked by using Virtual DataCenter Automation. The createdlogical configuration diagrams can also be freely edited and saved by system operators.
The functions that can be implemented in Network Automation, whose role is to simply orchestratenetwork resources, are described below.
• Resource management
Virtual appliances such as virtual load balancers and virtual firewalls, as well as networkresources such as IP addresses and VLAN IDs can be pooled. Resource management, such asmanaging the total amount of resources, the amount of used and unused resources, and theamount of reserved resources, can be performed in pool units.
• Orchestration/Provisioning
All the network settings required to use services, such as allocation of L2 switches, firewalls,and load balancers to VLANs, filter policy settings, user authentication settings, are automated.Network provisioning across multiple data centers can be automated by linking with theUNIVERGE PF series, which uses OpenFlow technology.
• Integrated ID management
Supported in the same way as Virtual DataCenter Automation.
• Tenant network visualization
Supported in the same way as Virtual DataCenter Automation.
1.2 New functions and fixed problems1.2.1 New functions
The new functions of MasterScope Virtual DataCenter Automation v3.0 are as follows.
• Network
- FortiGate 5.2 is now supported as a provisioned device.
- New devices supporting FortiGate have been added.
- The Unified Network function (PF5340 configuration) in UNIVERGE PF6800 NetworkCoordinator V6.2 or later is now supported.
- Access control settings that are specified when each network device is provisioned cannow be defined in advance.
• Scenario/Workflow
- Network scenarios can now be received at the same time.
- The information of all devices can now be deleted at the same time when a scenario erroroccurs.
Chapter 1. MasterScope Virtual DataCenter Automation
3 RWT00WN5030E-I01-1
- A "reservation information acquisition command" is now provided to check the ID ofreservations that were waiting for commitment or cancellation when a scenario erroroccurred.
• Resource group
- Import and export of management group setting information has been supported.
- For SSL-VPN and backend FW, multiple virtual nodes can be configured from the samedevice.
- The IP subnet range can now be specified for common group and management group.
- The authentication type can now be switched.
- You can now select whether to specify tenant IP address range in management group andcommon group.
- Free VLAN information has been added to the DC resource group detail acquisition API.
- IP Address Information Acquisition API, IP Address Information Registration API, and IPAddress Information Registration Cancellation API were added.
• Portal
- Monitoring portal
Not only providers but also tenant users can now centrally monitor virtual machines andservice statuses of their own tenant.
- Multi-stage approval
The number of workflow stages can now be set from 0 (no approval) to 5.
- Email reporting
An email can now be sent to an applicant or authorizer when a request is registered orapproved.
- Topology display
The status of the connection between the network and server can now be displayedgraphically.
- Output of billing information
A command to output the history of server creation and changes is now provided toproviders.
1.2.2 Fixed problemsThe fixed problems of MasterScope Virtual DataCenter Automation v3.0 are as follows.
• Network
- Network provisioning fails when locking a log file. This problem has been fixed.
- A failure of logical network deletion can now be detected.
- The problem that acquiring configuration information on UNIVERGE PF6800 NetworkCoordinator fails if 10000 or more logical ports exist has been resolved.
• Scenario/Workflow
- How to assign a reservation ID after a scenario error is resolved has been revised.
Chapter 1. MasterScope Virtual DataCenter Automation
4 RWT00WN5030E-I01-1
- The problem that creating a port group fails if a data store with the same name exists on adifferent path from where ESX exists has been resolved.
• Resource group
- The management server to be specified at vSW registration is now to be specified on theconsole.
• VM
- The NIC driver could not recognize a created virtual machine (VMware) correctly. Thisproblem can now be worked around.
- The default setting when reconfiguring VMs has been changed so that VMs do not have tobe stopped before changing the configuration and then restarted to collect configurationinformation. The user can also select whether to perform these operations.
- A scenario name can now be specified by using the command to register a VM templatecreated by a provider.
• Portal
- The default time zone when creating a server has been changed to "(UTC+09:00) Osaka,Sapporo, and Tokyo".
- There were inconsistencies and spelling mistakes in the GUI of this product. These havebeen corrected.
• Others
- The scenario execution and screen display performance has been improved.
- The error codes for reservation errors and scenario errors have been revised according tothe events.
- The log output amount and content have been revised.
- An application error occurred when stopping the service (MasterScope UMF OperationsManager_101/102/103). This problem has been fixed.
- TLSv1 is now supported as the SSL authentication protocol of UNIVERGE PF6800Network Coordinator.
1.3 ComponentMasterScope Virtual DataCenter Automation consists of the following components:
• [Necessary components]
- SigmaSystemCenter (platform management)
- MISSION CRITICAL OPERATIONS (integration management and server monitoring)
- Network Manager (network monitoring)
- AssetSuite (asset management)
- Virtual DataCenter Automation Portal
• [Optional]
- Invariant Analyzer (performance analysis)
- Application Navigator (middleware monitoring)
- Identity Manager (ID management)
Chapter 1. MasterScope Virtual DataCenter Automation
5 RWT00WN5030E-I01-1
MasterScope Network Automation consists of the following components:
• [Necessary components]
- MISSION CRITICAL OPERATIONS (integration management and server monitoring)
- Network Manager (network monitoring)
- Virtual DataCenter Automation Portal
• [Optional]
- Identity Manager (ID management)
The storage location of the installer varies for each component. Thoroughly check the contentsdescribed in "Chapter 2. Media Configuration (page 7)", Virtual DataCenter AutomationInstallation Guide and Network Automation Installation Guide. For a description of each component,please refer to the Virtual DataCenter Automation First Step Guide.
Chapter 1. MasterScope Virtual DataCenter Automation
6 RWT00WN5030E-I01-1
Chapter 2. Media Configuration
Contents2.1 Directory Configuration ...............................................................................................................8
2.2 Product document (/doc) ..............................................................................................................8
2.3 Installers other than SigmaSystemCenter and SERCUREMASTER (/fw)....................................8
2.4 Virtual DataCenter Automation Integrated Installer(/install) ........................................................9
2.5 Code word application form (/licenseform)..................................................................................9
2.6 License clauses (/oss_license) ......................................................................................................9
2.7 Sample script(/script) ...................................................................................................................9
2.8 Virtual DataCenter Automation Standard Edition (/SE) ...............................................................9
2.9 Identity Manager installer (/securemaster)....................................................................................9
2.10 SigmaSystemCenter installer (/ssc) ............................................................................................9
Chapter 2. Media Configuration
7 RWT00WN5030E-I01-1
2.1 Directory ConfigurationMasterScope Virtual DataCenter Automation Media consists of a single copy of DVD. The directoryconfiguration is as follows:
[Root] ┬ doc Product document ├ fw Installers other than SigmaSystemCenter │ and Identity Manager ├ install Virtual DataCenter Automation Integrated Installer ├ licenseform Code word application form ├ oss_license License clauses ├ script Sample script ├ SE Virtual DataCenter Automation Standard Edition ├ securemaster Identity Managerinstaller ├ ssc SignaSystemCenter installer ├ vDCA_Relememo.pdf MasterScope Virtual DataCenter Automation Media │ Release Memo (this document) └ version.txt version id
2.2 Product document (/doc)The manuals for MasterScope Virtual DataCenter Automation and components are placed.
Table 2-1 Component Name and Document Storage Location
Directory name Component name
doc Entire product
doc/AppNavi Application Navigator
doc/AssetSuite AssetSuite
doc/MCO MISSION CRITICAL OPERATIONS
doc/NvPro Network Manager
doc/nwa Network Automation
doc/Portal Virtual DataCenter Automation Portal
doc/SecureMaster Identity Manager
doc/SecureMonitor AssetSuite
doc/ssc SigmaSystemCenter
doc/SysMgr SystemManager
2.3 Installers other than SigmaSystemCenter andSERCUREMASTER (/fw)
Installation assets of MISSION CRITICAL OPERATIONS, Network Manager, and AssetSuite areplaced. For details of how to install, please refer to Virtual DataCenter Automation InstallationGuide.
Chapter 2. Media Configuration
8 RWT00WN5030E-I01-1
2.4 Virtual DataCenter Automation IntegratedInstaller(/install)
Installation assets of Virtual DataCenter Automation fucntions are placed. For details of how toinstall, refer to Virtual DataCenter Automation Installation Guide.
2.5 Code word application form (/licenseform)The code word application form for the license to be registered in MISSION CRITICALOPERATIONS, SystemManager, Network Manager, and AssetSuite are stored. For details, see"Chapter 4. License (page 11)".
2.6 License clauses (/oss_license)License clauses for the open source software, etc. to be used in Virtual DataCenter Automation arestored.
2.7 Sample script(/script)A sample script for starting and stopping services required by the cluster environment is stored here.
2.8 Virtual DataCenter Automation StandardEdition (/SE)
Installation assets of Virtual DataCenter Automation Standard Edtion are placed. For details of howto install, refer to Virtual DataCenter Automation Standard Edtion Setup Guide.
2.9 Identity Manager installer (/securemaster)Installation assets of MasterScope Identity Manager are placed. For details of how to install, refer toVirtual DataCenter Automation Installation Guide.
2.10 SigmaSystemCenter installer (/ssc)The installation asset of SigmaSystemCenter is placed. For details of how to install, refer to VirtualDataCenter Automation Installation Guide.
Chapter 2. Media Configuration
9 RWT00WN5030E-I01-1
Chapter 3. Operating EnvironmentsPlease refer to Chapter 6. Operating Environments/System Requirements in the Virtual DataCenterAutomation First Step Guide about a operating platform and a system requirements of VirtualDataCenter Automation.
Chapter 3. Operating Environments
10 RWT00WN5030E-I01-1
Chapter 4. License
Contents4.1 License Key ...............................................................................................................................12
4.2 Software License Information ....................................................................................................12
Chapter 4. License
11 RWT00WN5030E-I01-1
4.1 License KeyTo use MasterScope Virtual DataCenter Automation, multiple license keys must be registered.
Register the license by following the procedure in the Virtual DataCenter Automation InstallationGuide, and register the license keys listed in the "Software License Key Sheet" attached with thisproduct. In addition, a "code word" must be entered to register some licenses. If the code word is notentered, the license will be disabled 1 month after the registration.
The code word is issued for each Virtual DataCenter Automation management server. Send the"Code word application form" attached to this product to the address specified on the applicationform. For details, see the description contents in the application form. The code word applicationform is stored in Excel format file in the following directory of the installation DVD:
<Installation DVD>:\licenseform\CodewordRequestForm.xlsx
4.2 Software License InformationOther than the authorized software, this product employs open source software, etc. The licenseinformation of the used software is stored in the following directory of the installation DVD.
<Installation DVD>:\oss_license
Chapter 4. License
12 RWT00WN5030E-I01-1
Chapter 5. Precautions and RestrictionsThis chapter describes cautions and restrictions for MasterScope Virtual DataCenter Automation. SeeChapter 1 The Life Cycle of Virtual DataCenter Automation, 5.1 Precautions, 7.1 Precautions or 15.1Precautions in the Virtual DataCenter Automation Configuration Guide etc, described about cautionsof each fuctions.
• Restrictions
No item.
• Cautions
- During parallel execution of scenarios, if multiple scenarios wait for the completion of thepreceding scenario, determination of the scenario to be called next does not depend on theorder in which the scenarios started waiting. Therefore, if the scenario execution ordermust be strictly observed, it is necessary to confirm completion of the preceding scenariobefore executing the subsequent scenario.
- If the subsequent scenarios wait for the completion of the preceding scenario duringparallel execution of scenarios, the completion time of the subsequent scenarios may bedelayed for the length of the processing time of the preceding scenario. When setting atimeout for the period to wait for the completion of scenario execution, this processingtime must be taken into account. Network scenarios may also wait for the completion ofvirtual machine scenarios. Therefore, set a value that takes into account the processingtime of a virtual machine for the timeout value for network scenarios.
- After making the settings on the DC resource view, do not change the authenticationmethod of the following configuration file:
<Install folder>\Manager\sg\RpResource\RpResourceMgr.ini
- For the category when creating a physical server, specify "Gold," "Silver," or "Bronze". Setthe specified category in the [Cluster Group Name] field for physical server creation beforeexecuting the creation process.
- When using FortiGate as the FW device that is used as the tenant FW, the FW device namemust be no more than 11 characters due to the device specifications. If <Count> is used asthe tenant FW naming rule, the name of the replaced FW device must be specified so thatits length is no more than 11 characters.
- When creating a physical server in a resource management group without VLANexpansion, a tenant FW or tenant LB must be created in advance.
- The VLANs not selected when creating a common group cannot be selected when creatinga management group under that common setting group. Therefore, include all the VLANsyou may be creating in the future when creating a common group.
- The forcible deletion command (nwa_devconfdelete.bat) is supported by the followingnetwork devices:
* Network Coordinator UNIVERGE PF6800 Network Coordinator
* Fortnet FortiGate
* F5 BIG-IP
* A10 Thunder
Chapter 5. Precautions and Restrictions
13 RWT00WN5030E-I01-1
* VMware vSphere Standard Switch
* VMware vSphere Distributed Switch
- The default protocol for Virtual DataCenter Automation SSL has been changed fromSSLv3 to TLS.
- For devices under the network view on the management server console, a node whose icontype is "UNC" cannot be imported or exported. Make the setting in advance in the importdestination environment.
Chapter 5. Precautions and Restrictions
14 RWT00WN5030E-I01-1
MasterScope Virtual DataCenter Automation Media v3.0Release Memo
RWT00WN5030E-I01-1
June, 2016 1st Edition
NEC Corporation
©NEC Corporation 2012-2016
