SigmaSystemCenter 2.1 Release Notes

Transcription

1 1 SigmaSystemCenter 2.1 Release Notes Welcome to SigmaSystemCenter 2.1 Published: 2009/Feb/27, Edition 2.0 Release Name SigmaSystemCenter 2.1 Update 1 Release Date 2009/Mar/02 Internal Revision r7936 SigmaSystemCenter is an integrated management software product that can manage machines, storages, and networks. This is an integrated management tool for system administrators operating a medium to large IT environment, which abstracts complex IT systems and make it easy to perform configuration change or other management operations. SigmaSystemCenter is a suite product of DeploymentManager, NEC ESMPRO, SystemProvisioning, and SystemMonitor. About This Document This document is a release note mainly describing changes in SigmaSystemCenter 2.1. For more details of functions and settings, see related documents and manuals. NEC may make changes to this document, at any time without notice. What's New 2.1 Update 1 Release Notes 2.1 Release Notes What's New Fixes for issues detected by 2.1 and several functional enhancements are implemented in SigmaSystemCenter 2.1 Update 1. The changes in Update 1 are: Supporting Cluster and EVC - SigmaSystemCenter can now manage a clustered environment, which enables you to manage an environment where Enhanced VMotion Compatibility (EVC) is enabled. EVC is a function that realizes VMotion between ESXs that have CPUs of various generations. (#4894) Creating and Assigning Xen Server Virtual Machine - Disk Clone realized customizing virtual machines. (#5234) Linked Clone - Linked Clone function which refers to an image of a master VM and create a virtual machine is newly supported. This function is provided as a trial in this release. (#4178) Disk Clone - Disk Clone function which copies configuration files and virtual disks of a VM to create a clone of the VM is newly supported. (#4178) Enhanced Performance of Collecting Process of Machines List - Reconsidered the process of collecting a list of machines, and an issue of slow display of a machine list if there are large quantities of machines is resolved. Previously, there was a case that it took several minutes to collect information of machines if there were large quantities of machines, however, in Update 1, the process is improved to complete in several seconds. (#5110) Improved Heartbeat Alarm Setting Function - The way to created a Heartbeat alarm is

2 2 changed. You can now change the setting for Heartbeat alarm in VirtualCenter 2.5u1 or later. You can also control creation of the Heartbeat alarm even in earlier versions of VirtualCenter with this release. (#5313) Ssc Command Support - Commands for operations that take time with GUI, such as creating hosts, are provided. The ssc commands are newly supported. This support is offered as a trial in SigmaSystemCenter 2.1 Update 1. In our future release, specifications, including an option specifying method, will be changed. (#3645, #5185) Enhanced VM Controlling Commands - The following functions of VM controlling commands are added: A function to leave virtual disk when deleting a VM (#5314,#5188) A function to specify whether starting up a virtual machine or not when moving a VM (#5316, #5189) A function to specify a destination Datastore when moving a VM (#5319) A function to move all VMs on a VM server to other VM server (#4999, #5315) Copying Policy - Added a function to create a new policy by copying an already created policy. (#5133) VM Standard Policy - Added the Standard Policy (Virtual Machine) for VMs as a policy template. (#5187) Improved Storage setting - In earlier releases, it took time to display information on a Storage setting if there were large quantities of disk arrays and disk volumes. This release this issue is resolved by separating registration of disk arrays and disk volumes. (#5062) Exclusive Control of When Multiperforming Is Done to One Device - When you executed multiple VLAN control processes or load balancer control processes, a timeout used to occur in the communication with MasterScope Network Manager, and the processes might throw an error. This release resolved the issue. (#5303) Fixed VHD on Hyper-V - Starting with this release, if a virtual machine of a HW Profile Clone Template has a fixed-sized VHD, a VM created by Create and Assign Machine from the template has a fixed-sized a virtual disk. (#4623) Changed Destination of Machine Move of When Releasing Assignment - Now you can return a machine to a group pool when you release an assignment of the machine created by Create and Assign Machine or registered by Register Master Machine. (#5138) Enhanced Virtual Machine Server Selection in VM Optimized Placement - Changed to use memory usage as a selection criterion of a VM server in VM Optimized Placement. (#5344) Server Core - Operations, such as backup, restore, and update, on Server Core are now available. (#4092) However, there is a defect in restoring an image of Sysprep deployment (Disk Duplication Installation), and it is not supported in this release. (#5567) Resolved Simultaneous Startup - This release resolved an issue of a DB connection error generation if you started up 100 or more units of machines by Optimized Startup. (#5176, #5072) Other enhancements in SigmaSystemCenter 2.1 from version 2.0 includes: VMware ESXi - You can now manage VMware ESXi with SigmaSystemCenter 2.1. You can manage ESXi both from SigmaSystemCenter directly and via VirtualCenter.

3 3 VC2.5u2 - Supported VC2.5u2 English version as a management target. (#3685) Microsoft Hyper-V - The Windows Server 2008 Hyper-V environment is supported. (#2877, #3673) Managing the Hyper-V environment had been the trial, but this time, it is officially supported. (Updated on 2008/Dec/25) Citrix XenServer SigmaSystemCenter 2.1 supports XenServer 4.1 as a management target. (#3533, #3957) Citrix XenServer SigmaSystemCenter 2.1 supports XenServer 5.0 as a management target. (#4379, #4755) (Updated on 2008/Dec/25) VMware VM Console - SigmaSystemCenter 2.1 enables you to open the console screen of virtual machines on VMware ESX from the SigmaSystemCenter Web Console in the Virtual view. (#699) This function is offered as a trial. MasterScope Network Manager 2.0: With SigmaSystemCenter 2.1, you can manage network devices managed in MasterScope Network Manager collectively. (#3736, #3737) iscsi Support - With SigmaSystemCenter 2.1, you can change the configuration of storages of NEC Storage E1 from SigmaSystemCenter using the local script function. (#2049) In addition, it enables backup / restore and disk copy for disks on iscsi. (#3399) EXPRESS CLUSTER X Event - SigmaSystemCenter 2.1 can receive events of EXPRESS CLUSTER X. (#3438) Optimized Restart - The VM Optimized Startup function is extended in SigmaSystemCenter 2.1, and enabled to move VMs to an optimal VM server when restarting as well. (#3880) Improved VLAN Controlling Sequence - The timing of VLAN control when activating a machine or making a machine stand by, including replacing a machine is improved. (#3895) Local Script - Executing local scripts after shutting down a machine is implemented. (#4106) SigmaSystemCenter 2.1 incorporates all changes in SigmaSystemCenter 2.0 as well as fixes for some issues detected in SigmaSystemCenter 2.0.

4 4 Legal Notices Copyright (C) NEC Corporation Microsoft, Windows, Windows Server, Microsoft Internet Explorer, SQL Server, and Hyper-V are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Linux is a registered trademark or trademark of Linus Torvalds in the United States and/or other countries. SUSE is a registered trademark or trademark of Novell, Inc., in the United States and/or other countries. Red Hat is a registered trademark or trademark of Red Hat, Inc. in the United States and/or other countries. Intel, Pentium, Itanium, and Xeon are trademarks of Intel Corporation in the U.S. and other countries. AMD is a trademark of Advanced Micro Devices, Inc. EMC, Symmetrix, and CLARiiON are registered trademarks of EMC Corporation in the United States and other countries. VMware, ESX, ESXi and VMotion are registered trademarks or trademarks of VMware, Inc. in the United States and other countries. Xen, Citrix, XenServer, and XenCenter are registered trademarks or trademarks of Citrix Systems, Inc. ORACLE is a registered trademark of Oracle Corporation and/or its affiliates. PXE Software Copyright (C) Intel Corporation. Copyright (C) 2005, 2007, ALAXALA Networks Corporation. All rights reserved. (C) Cisco Systems Inc. All rights reserved. Foundry Networks, FastIron, ServerIron and the 'Iron' family of marks are trademarks or registered trademarks of Foundry Networks, Inc. in the United Status and other countries. BIG-IP is a registered trademark of F5 Networks, Inc. in the United States and/or other countries. InstallShield is a registered trademark and service mark of Macrovision Corporation and/or Macrovision Europe Ltd. in the United States and/or other countries. Java and all Java related trademarks are registered trademarks of Sun Microsystems, Inc. in the United States and other countries. This product includes software developed by the Apache Software Foundation ( This product contains JRE (Java Runtime Environment), which is distributed by Sun Microsystems, Inc. without charge, and Tomcat, which is distributed by Apache Software Foundation without charge. Use these products after accepting their license agreements. For details of copyright and ownership rights, refer to the following license files: Tomcat: <folder where Tomcat is installed>\license JRE: <folder where JRE is installed>\license Some icons used in this program are based on Silk Icons released by Mark James under Creative Commons Attribution 2.5 License. Visit for more details. All other brands and products used in this document are the trademarks or registered trademarks of their respective trademark holders. The (R) and TM marks are not explicitly in this document.

5 5 Term & Definitions (#xxxx) Internal tracking number Related Information Product Information: SigmaSystemCenter 2.1 First Step Guide SigmaSystemCenter 2.1 Installation Guide SigmaSystemCenter 2.1 Configuration Guide SigmaSystemCenter 2.1 Reference Guides 2.1 Update 1 Release Notes SigmaSystemCenter 2.1 Update 1 is an update release to improve upon version 2.1 and includes enhancements in both quality and functions. You can upgrade 2.1 to Update 1 by applying the patch, SSC Installation from 2.1 to 2.1 Update 1 with the installation media is not supported. You can upgrade the version earlier than 2.1 with the installation media. The installation media is marked as "2.1 Update 1." Update 1 release will be a base patch of 2.1 for future releases. Resource Specific Information Operating System as Managed Machine Support for the following managed machine operating systems has been added for Update 1. Windows Server 2008 Standard (x86) (Server Core Installation) Windows Server 2008 Standard (x64) (Server Core Installation) Windows Server 2008 Enterprise (x86) (Server Core Installation) Windows Server 2008 Enterprise (x64) (Server Core Installation) VMware Cluster, EVC Support - The ability to manage a clustered environment is provided in SigmaSystemCenter 2.1 Update 1. This enables to manage an environment where Enhanced VMotion Compatibility (EVC) is configured as well. EVC is a function that realizes VMotion between ESXs with CPUs of various generations. By registering ESX to a cluster to which EVC is enabled, you can execute VMotion between CPU with different generations. With this release, the cluster of VirtualCenter is implemented to be handled as the datacenter of SigmaSystemCenter so you do not see levels between datacenters and clusters, and see them on a same line on the Web Console. (#4894) Note the following points in managing a cluster. Creating a cluster is not supported. Set a unique name for a datacenter and cluster in Virtual Center.

6 6 You cannot make a Datastore shared between a datacenter and cluster. VM Console - You can operate a console of a VM from SigmaSystemCenter. With our prior releases, you needed to install the MKS Plugin to your browser and started the console from ESX manually. SigmaSystemCenter 2.1 Update 1 automated the installation of the MKS Plugin to a browser. When you attempt to access to a VM console, the system urges you to install the MKS Plugin. (#5107) The VM console is offered as a trial continuously. Improved Heartbeat Alarm Setting - SigmaSystemCenter creates a Heartbeat alarm of a VM in VirtualCenter. This release changed the creation method of the Heartbeat alarm to configure settings for the alarm in VirtualCenter 2.5u1 or later. In addition, even with VirtualCenter of earlier version, you can suppress creation of the Heartbeat alarm by creating "DisableHeartbeatEvent" of DWORD value with one to the registry subkey below. To reflect the setting on registry, you need to restart SigmaSystemCenter. (#5313) HKEY_LOCAL_MACHINE\Software\NEC\PVM\Provider\VM\VMware\Event ESX Provisioning - In earlier releases, SigmaSystemCenter had registered ESX with its IP address after installing the ESX in ESX Provisioning. However, SigmaSystemCenter 2.1 Update 1 changes the default action to register ESX with its host name to VirtualCenter. A host name is acquired from the Host Name specified on Host Setting, and FQDN of a domain is acquired from the Domain Suffix specified on the OS Setting of a group. You need to note that when you register ESX with its host name, the host name and IP address need to be resolved in the system. (#5403) In addition, you can register ESX with its IP address by creating "EnableIPSetting" of the DWORD value with one to the following registry subkey. HKEY_LOCAL_MACHINE\Software\NEC\PVM\Provider\VM\VMware Enhanced Retry Action in Timeout - Added APIs to retry operations for when calling VI API is timed out. (#4453) ESX 3.5 Update 3 KB KB is issued for ESX 3.5 Update 3, which affects the VM startup check process in SigmaSystemCenter. SigmaSystemCenter uses Heartbeat of a VM to check if a VM is started; so that KB slows down starting and restarting a VM. Apply the workaround of editing config.xml to set heartbeatdelayinsecs to zero which is described in KB (#5482) Microsoft Windows Server 2008 Hyper-V Fixed VHD - Starting with this release, if a virtual machine of a HW Profile Clone Template has a fixed-sized VHD, a VM created by Create and Assign Machine from the template has a fixed-sized a virtual disk. (#4623) Lifted Notes - The following notes in SigmaSystemCenter 2.1 are lifted in this release: Display of VM servers on details of a virtual manager - Names of VM servers that host a VM are not displayed under Running VM List and Unused VM List on details of a Hyper-V Manager in the Virtual view. (#5038) Specifying a default VHD path of Hyper-V - If you specify a directory that does not exist as a default VHD path of Hyper-V, registering a VM server and collecting information fails. (#5048) A number of CPUs of a VM server - If the number of CPUs of a VM server is two

7 7 sockets or more, the number is displayed fewer than actual when displaying information of the virtual machine server on the Web Console. (#5095) Resolved an issue that a cancelation process is called twice and an error is recorded if a timeout occurs in creating a VM. (#5050) Citrix XenServer Create and Assign Machine to Xen Machine - With Disk Clone, you can now customize a VM from SigmaSystemCenter. (#5234) Note the following when creating a VM. A specified virtual network setting for a creating VM of Xen by Create and Assign Machine is not reflected. A setting specified to its template is succeeded. (#5234) ColdMigration to a Stopped Host - If you execute ColdMigration to a stopped host, although the move process succeeds, starting up the VM after the move throws an error. The program is changed not to allow ColdMigration to a stopped host.(#4626, #5226) Resolved an Issue that Multiple NICs with the Same MAC address Are Registered for a Xen Server - There was a case that multiple NICs with the same MAC address were registered for a Xen Server. The trouble shooting of Subsection , "Multiple NICs With the Same MAC Addresses Are Registered on a Virtual Machine Server" in Reference Guide is deleted with this release. (#4702, #5227) Improved an Issue of Taking a Long Time to Fail Over on Xen Server5.0 - For judging vitality of a XenServer, host_metrics.live was used in prior releases. With XenServer 5.0, it took around ten minutes for host_metrics.live to transit to false. And in failover, the system took time to process operations as it kept waiting to for host_metrics.live to transit to false, which deteriorates the performance. The judgment of vitality of XenServer is changed to only the session connection to not wait till transit to false. (#5496) Change of Virtual Disk Name - Changed a virtual disk name display to a name in the "[SR name]" format. (#5289) Maintenance - Changed the version of a library to control the XenServer environment to 5.0. (#5291) Network Subsystem Improved Edit VLAN - The following points on the Edit VLAN window are improved. (#5407) The program is changed to not be able to change a VLAN name and VLAN ID if the VLAN is configured to an operation group. Previously, if you changed them with the VLAN configured to an operation group, when you executed Allocate Machine on an operation group, an error, "Failed to find VLAN defined in a server group." might appear. The program is changed configure or release VLAN to only changed ports when you add or delete ports. In SigmaSystemCenter 2.0 and 2.1, the system released settings of all ports once and configured VLAN setting to necessary ports when you added or deleted ports. In addition, in this release, you can configure VLAN setting or release VLAN by setting a target machine Maintenance On even if a port is occupied by a running machine (resource allocated). Even if you changed only Description, the system used to release settings of all ports

8 8 and configured VLAN to the ports. Network Manager Exclusive Control in Multiperforming to One Device - When you executed multiple VLAN control processes or load balancer control processes, a timeout occurred in the communication with MasterScope Network Manager, and the processes might throw an error. With this release, this issue has been resolved. (#5303) Enhanced Guard of Changing LB Group - If you changed a LB group setting specified to an operation group to which a running machine belongs and then, made the machine stand by, the LB group could not be deleted from a load balancer device. To resolve this issue, we enhanced guarding to not change settings if a target machine is running. Verify that changing a LB group setting during operation does not affect the operation, and perform the following steps (#5406, #4774) 1. Release a LB group from its operation group Edit the LB group. Configure the LB group to an operation group. Improved Operation Logs - The application or release process skips processing when a current status of the setting is already applied or released. In this release, the program is changed to record the skip in the Operation log. (#5304) Storage Subsystem Improved Storage Setting - The Register disk array and disk volume window, which can be opened from "Resource" > "Storage" > "Register Disk Array & Volume, was a window that displayed information of all acquired unregistered disk arrays and disk volumes in a tree and made you select a target so if there were quantities of disk arrays and disk volumes, it took a long time to display them. In this release, registering disk arrays and registering disk volumes are separated. (#5062) Releasing the Restriction of When Using a Shared Disk Volume - In controlling NEC Storage, when you set a machine in a pool shared by groups with different OS types that were set in the Operations view, and set also a disk volume shared, the SQL timeout occurred in the access path control process of storage and the process fails. In this release, this issue is resolved. (#4709) Releasing the Restriction of When Using CLARiiON CX You could not use the fourth or fifth port of CX3-20 service processor with prior releases. In this release, the number of usable ports is extended 12 ports. (#4923) Correction of an Issue of Multiple NEC Storages Connected to One HBA - If multiple NEC Storage devices are connected to one HBA, the process of connecting / disconnecting to storage is processed to LDs that belongs to each device. There was a defect in the process of searching the LDs, and the system regarded a LD that does not belong to any device as that belongs to a device, and executed the connection / disconnection process, which caused an error. This release resolved this issue to not cause the error in the connection / disconnection process by selecting a correct LD that belongs to a device. (#5384, #5556, SSC PVM) General System Management Enhanced Operations Log / Job Window - Starting with this release, a function to

9 9 narrow a list down by an Event Category is added. In addition, on the Operations Log window, a function to search a log that corresponds to a Job ID or event number is added. With this enhancement, the window displays a log matching to a specified Job ID and event number. (#5175) Sending Mails - SigmaSystemCenter implements a function to send an event by mail at the same time that it outputs an event log. This release resolves an issue that you could not specify multiple addresses, separating by "," (#4969) Power Control Timeout - A timeout value is extended from 30 minutes to 60 minutes. (#5416) Resolved an Issue of a Job Not Displayed on Dashboard - Previously, there was a case that the system determined a job whose status was changed to Warning was completed even though the job was still being executed. The dashboard displays jobs being executed and those that have completed in three minutes so in the above case, jobs in still processing were not displayed on the dashboard and could not be referred to or canceled. If you executed a job that contains multiple actions, if a warning occurred during one of the actions, the system updated the status of the job to Warning at that point, and it determined the job still in processing was completed. This update is fixed to update the job status after acquiring results of all actions of a job. (#5578) Streamlining Collecting Machines - Identifying a target machine in a database in the process of collecting physical machine information is improved. (#5583) Speeding up Imaging - With this release, the Javascript processing on the Web UI is reconsidered and improved imaging performance. The time until displaying images can be cut by half partly, but in average, improved by 15 to 20%. (#5040, #4255, #5110) Acceleration of Acquiring Machine List - In this release, the process of acquiring a machine list is reconsidered and an issue of slow display of a machine list in the case when there were quantities of machines is resolved. Acquiring the information would take several minutes in the case when there were quantities of machines, but in Update 1, the processing can take only several seconds. (#5110) Improved Column Width - The column width in the list display is reconsidered. This update resolved an issue of some breaking IP addresses and MAC addresses. (#5097) Misc. Resolved an Issue of Taking Time to Stop the Service of SystemProvisioning in Rare Cases - Previously, stopping the SystemProvisioning service could take ten minutes or more. (#5284) VM Management Deleting VM Leaving a Virtual Disk - When deleting a VM, a virtual disk, including vmdk and VHD files, was also deleted. In this update, you can select to leave a virtual disk or not when deleting a VM. (#5188) Power Status After Moving a VM - In earlier releases, when you executed Move VM, the system changed the power status of the VM to On. With this update, you can select to not start the VM after moving the VM. (#5189) Evacuate VM - A function to evaluate all VMs on a VM server to other server is added. A template is not moved. (#4999) Evacuate VM moves stopped VMs as well. VMs after the

10 10 move are in the stopped status. You can execute Evacuate VM with the ssc evacuate machine command at the command line. You cannot specify Evacuate VM as a policy action. Displaying Usage Status on a Datastore List - On the details of a VM server that can be displayed in Virtual view, this release displays usage size, free capacity, and usage rate. In addition, the usage size is changed to be displayed in GB. (#4726) Note that after creating a VM and template, the size of a Datastore is not updated automatically. Suspend Operation to a VM Server - Started from SigmaSystemCenter 2.0, the suspend operation to a VM server was displayed on UI, but the operation itself was not supported. In SigmaSystemCenter 2.1 Update 1, the display on the UI is deleted. The following windows are changed. (#5544) On details of a datacenter > Operation menu on VM Server List On details of a VM server > Operation menu Resolved Wrong Status of a VM on ESXi/Hyper-V - There was an issue of exclusion between the changing configuration process and creating a VM process, which caused the wrong status of a VM when you were creating the VM on ESXi and Hyper-V. (#5244, #5136) Resolved an Issue of Displaying One Template Doubly - If the template creating process and collecting information process were executed simultaneously, one template might be displayed doubly under Template List. This issue is fixed in this release. (#5374) Resolved an Issue of Ability to Set a Machine in a Pool Unmanaged on Edit Datacenter - You can set VMs and VM servers, including their belonging datacenter, unmanaged from details of a datacenter > Edit Datacenter. The issue that you could set a machine unmanaged even if the machine is in a group pool is fixed in this release. (#5473) VM Creation The following two methods for creating a VM as well as Full Clone and HW Profile Clone are added: Linked Clone - When creating a VM from a master VM, the system links the VM to the master VM and keeps the difference data instead of copying the whole image of the master VM, which shortens the time for creating a VM and reduces its disk capacity. In SigmaSystemCenter 2.1 Update 1, this function is offered as a trial, and it allows only creating a VM on Windows XP and Vista OS. This will be officially supported in our future release of VirtualPCCenter. Please give us your feedback on this function. (#4178, #4726) There considers an operation model of applying a patch to a master VM to facilitate patch application for created VMs, however, this release does not support the function. Note that defragmentation to each VM causes increase of difference data and you cannot reduce disk capacity. You can use Linked Clone in the VMware environment, including the Virtual Center and Standalone ESXi environments, and Microsoft Hyper-V environment. This Linked Clone can be an optional product in our future release. Disk Clone - This is a method of copying configuration files and a virtual disk of a VM, and creating a clone from them. (#4726) This is realized by combining the copy function of virtualization products with customization by DeploymentManager, and this enables to create a VM faster than HW Profile Clone which distributes images via networks. In addition, you can now execute Create VM to XenServer that you could not execute with earlier release of SigmaSystemCenter.

11 11 You need to note the following points on Linked Clone and Disk Clone. Ensure not to execute the following operations from VI Client if you configure Linked Clone in the VMware environment. Deleting a master VM - If you do, you will not be able to use all VMs created from a Linked Clone template that refers to the master VM. Deleting a created VM - If you do, you will not be able to use all VMs created from the same Linked Clone template and its master VM. Deleting a snapshot of a master VM after creating a template - If you do, you will not be able to use all VMs created from a Linked Clone template that refers to the master VM. Deleting a snapshot of a created VM - If you do, you will not be able to use all VMs created from the same Linked Clone template and its master VM. Do not change hardware configuration of a master VM after creating a Linked Clone template. This release supports Linked Clone on client operation systems (XP or Vista), but not on server operation systems. This release does not support Disk Clone in the VMware Virtual Center environment. If you are operating the VMware Virtual Center environment, use a Full Clone template. You cannot execute Allocate Machine if you register a Disk Clone or Linked Clone (when managing ESXi) template as software of a model or group. (#5312) Disk capacity of a virtual difference disk of a VM created by Linked Clone is not displayed correctly. VM Optimized Placement Improved Selection of a VM Server - In VM Optimized Placement, the program is changed to use memory usage as a selection criterion for a VM server. (#5344) Resolved Simultaneous Startup Issue - This release resolves an issue of a DB connection error occurrence if you executed optimized startup to 100 or more units of machines simultaneously. (#5176, #5072) Deterrence of Excessive Move at Power Save - The VM Optimized Placement moves VMs to run on fewer number of virtual machine servers triggered by a low load event. This function powers off virtual machine servers with no VM, but you can set a unit of spare machines to not power off even if the system can. In the earlier version there is a case that VM is moved between spare machine and another without need. In this release, this issue is resolved.(#5401) Resolved Confliction Between Power Save and VM Startup Processes - This release resolves an issue that the system might power off a machine which is starting a VM due to a conflict between the power save process and VM start process. (#5392) Improved Power Save Deterrence Process - The power save function executes load distribution and failover preferentially, and if there is a subsequent processing of these processes, the function deters shutdown to execute preferential processes. The system could execute the power save process occurred in other group in parallel, but still executed deterring control in that case. With this release, the program is changed to skip the deterring process to other group. (#5435) Improved Operation Log - The more detailed messages are outputted to the Operations

12 12 Log, starting from this release. (#5349) Deployment and Provisioning Changing Destination of a Released Machine - Starting with this release, a machine created by Create and Assign Machine or registered by Register Master Machine can be return to a group pool when the machine is released from its group. (#5138) Setting the Retry Count In Registering a Machine to NEC ESMPRO Manager - You can now change a retry count and retry interval for when registering a machine to NEC ESMPRO Manager on the Environment Setting. (#5161) Server Core - You can now execute operations, such as backup, restore, and update, on Server Core. (#4092) However, there is a defect on restoring a Sysprep deployment (Disk Duplication Installation) image, and it is not supported in this release. (#5567) Resolves an Issue of Taking Time to Process Scenario Execution Cancellation - This release resolves an issue that cancelling scenario execution might take time to complete. (#5066, #5258) Improved Operation Log - The program is changed to output more detailed messages for errors to the Operation Log. (#4704, #4902, #4494, #5063, #5104) Resolved an Issue of a User Confirmation Screen Not Displayed When Executing the Automatic Update Function - There was a defect on DPMTray.exe that displayed a user confirmation screen. And the screen might not be displayed when a user logged in and the screen should have been displayed, depending on timing. The issue is fixed in this release. (#5620) Fix of an Issue that the Command Option Is Ignored When You Select [Perform at next startup] During the Scenario Execution - If you selected [Perform at next startup] for the remote update scenario execution, a command option specified when creating a package was ignored. This issue is fixed in this release. (#5621) Resolved an Issue of Wrong Output to Event Log of Schedule Monitoring Service - When the DeploymentManager schedule monitoring service outputted a message on the Event Log, the message, "The description for Event ID 2 from source schwatch cannot be found." was displayed. Also output (message) source is wrong value (sharedll).this issue is fixed in this release.(#4643, SSC DPM) Policy and Action Copying a Policy - The function to copy a created policy and create a new policy is added. (#5133) VM Standard Policy - A Standard Policy for managing a virtual environment, which is "Standard Policy (Virtual Machine)," is newly added. (#5187) Reduced Load of the Event Processing - By cashing policy settings stored in a database to memory, load on processing of when receiving quantities of events is reduced. (#4466) Improvement of the Policy Action "Machine Status / Set Ready Status" - A function to change the policy status to "On" with a policy action "Machine Status / Set Ready Status" if a target machine is ON is added. (#5426) Revised an Issue of Disability to Manage Specific Event Occurred on a Linux Machine - There was a case that an action was not performed when configuring a policy on

13 13 an event detected by NEC ESMPRO Agent on Linux. (#5051, #4772) NEC ESMPRO Agent on Linux sends a notification source name in uppercase in either of the following cases. There was a case-sensitive process that reads the notification source name, and NEC ESMPRO Agent on Linux could not compare a received event from an event defined to a policy. If a notification source name was read from a notification table If a source of user definition was added from the Syslog monitoring event setting window Command pvmutl pvmutl vmdelete /u - The option "/u" is added to pvmutl vmdelete to not delete a virtual disk in this release. (#5314, #5188) pvmutl vmmigrateandmove /n - The option "/n" is added to pvmutl vmmigrateandmove to not start a stopped VM after moving in this release. (#5316, #5189) pvmutl vmdelete /d - If you omit specifying a target machine with pvmutl vmdelete /d and pvmutl delete, the system selects a target machine in running machines. In the process, a different machine might be selected for each method. The specification of vmdelete /d is changed to select a machine that belongs to multiple group pools, according to the specification of delete in this release. (#5119) ssc This release supports configuring multiple managed machines collectively by executing commands from a script with ssc.exe, which is a new command. Previously, you needed to configure settings to each machine from the Web Console, however, this function can reduce burden of setting up a large-scale environment. (#3645, #5185) The specification of this ssc command will be changed in the way to specify options in our future release. This function is offered as a trial in this release. Our future release will provide useful function for script processing. The available functions in Update 1 are: ssc create host - Creates a host in a group. ssc evacuate machine - Can execute Evacuate VM and Failover with a command. (#5315, #5318, #5185, #4999) ssc update host - Can Move VM to another group. (#5319, #5185) ssc maintenance cmdb - Can manage a database, including resolving fragmentation of a table. Misc. Installer Registering Exception to Windows Firewall - Previously, when the system failed to register an exception to Windows Firewall, SigmaSystemCenter displayed an error dialog box. This did not indicate failure of installation, and actually, it was not that installation itself failed. In addition, the message was ambiguous, so starting from this release, the

14 14 error dialog box is not displayed. (#3428) Database Prevention of Overlap Registration to a Specific Table in a High Load Condition - There was an issue that uniqueness constraint of a key on a used key value table (TBL_GeneralParameter) was not assured, which causes double registration in the numbering process of event numbers when load is high, and the GUI operations below might fail with an error. (#4789, #4799, #5217) Virtual View > Create Template Virtual View and Resource View > Template > Edit Monitor View > Environment Setting Maintenance Improvement of Steps to Exchange a Primary NIC - You needed to delete a machine once to exchange a primary NIC (NIC1). With this update, you can execute the operation comparatively easily with the GUI operations. (#5393) Trace Log The following is added as a target of a trace log of SystemProvisioning. PVM/log/MaintenanceCmdb%d.log DB maintenance processing (#5217)

15 Release Notes This chapter and the following chapters provide changes in SigmaSystemCenter 2.1 except those in the Update 1 release. Release Name SigmaSystemCenter 2.1 Release Date 2008/10/31 Internal Revision r7112

16 16 Product Configuration SystemProvisioning Administers the various functions, including the provisioning function and policy function, as an orchestration function. The version of SystemProvisioning is upgraded from 5.0 to 5.1. DeploymentManager Administers the function to deploy Windows and Linux machines. The version of DeploymentManager included in SigmaSystemCenter 2.1 is Ver 5.2. The version of DeploymentManager (Windows/Linux) is upgraded from Ver5.1 to Ver5.2. ESMPRO Administers the function to monitor machines and manage machines. ESMPRO is composed of NEC ESMPRO Manager as a manager and ESMPRO Agent as an agent. SigmaSystemCenter does not contain NEC ESMPRO Agent, for it has a dependency on a machine. It is bundled with NEC Express series. The version of NEC ESMPRO Manager is upgraded from Ver4.41 to Ver4.42. System Monitor - Performance Monitoring Services Provides the function to monitor machine performance values. The version of System Monitor - Performance Monitoring Services is changed from to 4.1. (#3946) Other Subsystems The following products are not contained in SigmaSystemCenter releases, but necessary depending on an environment. Storage NEC Storage Manager NEC Storage Manager Integration Base EMC Solutions Enabler EMC Navisphere Network MasterScope Network Manager MasterScope Network Manager NetworkProvisioning Function License Virtual Environment VMware Virtual Center Citrix XenServer Enterprise Edition Product Configuration and License Scheme This chapter includes information about the product configuration and license scheme of

17 17 SigmaSystemCenter. According to the nature of the contents, not only changes but also the overall system is described. Edition Basic Edition is added as an edition. (#3830) The Basic Edition is an edition composed of the same product configuration as the Standard Edition with different maximum management units. It was added in July, SigmaSystemCenter has editions provided by different media, Basic/Standard Edition and Enterprise Edition. The media is configured in Japanese for Japanese market, and in English for overseas markets. We provide Enterprise License instead of Enterprise Edition for overseas markets. In addition, we define the VPCC Edition License as an infrastructure of VirtualPCCenter. The product configuration of the VPCC Edition is same as that of the Standard Edition Basic Edition The Basic Edition is an edition that limits the number of target licenses to eight units. The product configuration is the same as the Standard Edition, and you can use the all functions with this edition. You can upgrade this edition to the Standard Edition. Standard Edition This edition supports Windows and Linux servers and clients of Windows XP. SigmaSystemCenter Standard Edition is for a middle-scale system, that can manage the server OS up to 100 units, and the client OS up to 4000 units. This edition features a configuration control function for servers, storages, networks, and virtual machines, which enables you to integrate both machines and clients. To change configuration of virtual machines with Standard Edition, you need the Virtual Server Management Option. Enterprise Edition This is an edition for a large scale environment without limit of additional target license number. With the Enterprise License you can upgrade Standard Edition to the Enterprise Edition. Enterprise Edition includes the Virtual Server Management Option. VPCC Edition The configuration of the VPCC Edition is the same as that of the Standard Edition. The Virtual Server Management Option is included. With this edition you can manage only a Windows Client, such as Windows XP, in the Operations view. VirtualPCCenter Starter Edition The number of target licenses that you can add is 120. VirtualPCCenter Standard Edition You can add target licenses without limitation. Management Server License A license for one management server is included in each edition product. This is called a Base license or main license. For one management server, one main license is necessary.

18 18 We defines Management Server Additional License that you can use in systems for a same purpose to add a management server. Enterprise License With the overseas edition, the Enterprise License is defined as a substitute for the Enterprise Edition. The Enterprise Edition is a kind of MSL. Applying this license enables the equivalent target license number that you can add and options to the Enterprise Edition. Option License Other various optional licenses that are required for each management server are defined. Optional licenses are necessary to enable various functions of SigmaSystemCenter. Virtual Server Management Option This option enables the virtual environment management function. Management Server Clustering License:: This license is required for operating a management server in the cluster configuration. You can apply this one license to one standby node server. Target License This is a license required for each managed machine. SigmaSystemCenter consumes licenses by assigning a machine to a host (activating) in the Operations view, and bringing back the licenses by releasing the assignment (making a machine standby). You do not need a target license to activate a VM server, such as ESX and XenServer as a VM server. No change on target licenses is made in this release.

19 19 Install System Architecture Requirements Ensure that your computers have met the system architecture requirements. For the details, see Chapter 3, "Operational Environment" in First Step Guide. Management Server Recommended Minimum Hardware Configuration CPU Intel Compatible 2GHz 2 Core or faster Memory Capacity 2GB or greater Disk Capacity 2GB or greater OS Windows Server 2003 with SP1/SP2, Standard x86 Edition Windows Server 2003 with SP1/SP2, Enterprise x86 Edition Windows Server 2003 R2 with SP1/SP2, Standard x86 Edition Windows Server 2003 R2 with SP1/SP2, Enterprise x86 Edition Windows Server 2008 Standard x86 Edition Windows Server 2008 Enterprise x86 Edition Required Software ASP.NET 2.0 IIS 6.0, 7.0 Installation of SigmaSystemCenter Before upgrading SigmaSystemCenter, you need to uninstall a part of components. For the details, see Chapter 3, " Upgrading From Earlier Version" in Installation Guide. The outline of the upgrading procedure from each version is provided below. Upgrading from Pre-uninstallation 1. Apache Tomcat 2. Web Server for DPM 2. Upgrade Upgrading from Pre-uninstallation

20 20 1. Apache Tomcat Web Server for DPM SystemProvisioning Web Components Stopping Management Server for DPM manually Upgrade Runtime Environment.NET Framework.NET Framework is being used as runtime environment of SigmaSystemCenter. SigmaSystemCenter 2.0 or later requires.net 3.0 for WCF. WCF is used with the UC layer of SystemProvisioning. There is no change on this point. Java JRE Java JRE is an execution environment of Java. JRE is used by DeploymentManager. DeploymentManager supports JRE 6.0_07. Tomcat Apache Tomcat is used by DeploymentManager. DeploymentManager supports Tomcat ASP.NET IIS SigmaSystemCenter 2.1 uses ASP.NET 2.0. There is no change on this point. SigmaSystemCenter 2.1 supports IIS 6.0 and 7.0. There is no change on this point. Database Database is used to store various configuration information that is managed by SigmaSystemCenter. Microsoft SQL Server 2005 Express Edition is bundled with SigmaSystemCenter. The default DB instance name is SSCCMDB. There is no change about the database. Browser We have confirmed the operation of SigmaSystemCenter 2.1 (SystemProvisioning) on; Microsoft Internet Explorer 6 Microsoft Internet Explorer 7 Mozilla Firefox 2.0 Mozilla Firefox 3.0 (#3882) (New in 2.1)

21 21 Resource Specific Information This chapter provides information about hardware supported by the SigmaSystemCenter 2.1 release. Operating System as Management Server There is no change with OS support on a management server with this release. VMware Retry When Timed Out - VI API may fail due to a timeout. In this release, the program is changed to retry a process when the system throws a timeout error in the calling RetrieveProperties process. (#4453) ESXi Now you can manage not only VMware ESX, but also VMware ESXi with our SigmaSystemCenter 2.1. (#2025) You can manage ESXi from SigmaSystemCenter directly and via VirtualCenter. Managing and operating ESXi from SigmaSystemCenter can simplify your system and make setting up virtual environment a lot easier, and it meets your demands, such as you do not need functions up to improving availability using Hot Migration / Cold Migration, but you want to reduce the system management costs by introducing virtual environment. As you can manage ESXi from SigmaSystemCenter, you do not need VMware VirtualCenter. You can manage multiple ESXi collectively as ESXi and all VMs on ESXi are displayed in the Virtual view. Furthermore, you can create, execute power operation to a VM, and change resources, such as CPU and memory, assign to a VM. To manage ESXi via VMware VirtualCenter, automatic recovery by failover and optimized placement function are allowed; however, the HW monitoring function of ESXi is not supported, so you cannot execute operations, for example, moving a virtual machine with Hot Migration to other virtual machine server by detecting the sign of HW failure. You can change managing ESXi from directory to via VirtualCenter with SigmaSystemCenter, while you cannot change the managing way in the opposite direction from SigmaSystemCenter. (#3955) To register Standalone ESXi to SigmaSystemCenter, enable "Set ESXi To Be Manager" on the top page of the Virtual view and register the ESXi. Monitoring ESXi Host SystemProvisioning monitors the vitality of an ESXi host by polling, and creates the following events; (#3991) Alarm Host connection state on VMS changed from Green to Red: Lost response from a host. Alarm Host connection state on VMS changed from Red to Green: Response from the host is revived. After continuous ten times of access failure to an ESXi host with each ten seconds of wait, which counts up to 100 seconds, the system determines the condition of the ESXi host down. VirtualCenter 2.x

22 22 This release supports VC2.5 update1 Japanese version and VC 2.5 update2 English version. (#3602, #3685) Alarm names are localized to an OS language with VC 2.5 update2 English version. (#3685) SigmaSystemCenter translates Japanese alarm names. Folder/Cluster/Resource Pool of VirtualCenter 2.0 is not supported. (#308) Therefore, you cannot use EVC (Enhanced VMotion Compatibility) of VirtualCenter 2.5 that uses Cluster from SigmaSystemCenter 2.1. We are going to support EVC in a patch release of 2.1 in Feb, A host name of ESX is changed to case-insensitive. In addition, when a host name does not match, or when an IP address is registered to the Manager information, the system compares with its IP address. Microsoft Windows Server 2008 Hyper-V SigmaSystemCenter 2.1 enables managing the Windows Server 2008 Hyper-V environment as part of integrated VM management. You can create a VM, perform power operations, and change resources, including CPU and memory, which are assigned to a VM, with this release and more functions will be supported in our future releases. (#2877, #3673) When registering Hyper-V to SigmaSystemCenter, enable "Set Hyper-V To Be Manager" on the top page of the Virtual view first, and then, register a Hyper-V host. Although the Hyper-V environment management function was offered only as a trial in SigmaSystemCenter 2.1, it is officially supported on 12/25/2008. Note the following points on this. Note on using the vmadd command of pvmutl - A host of Hyper-V can have only one Datastore. You do not need to specify the /DATASTORE option when using the vmadd command of the pvmutl in the Hyper-V environment. (#5169) Display of VM servers on details of a virtual manager - A name of a VM server that hosts a VM is not displayed under Running VM List and Unused VM List on details of a Hyper-V Manager in the Virtual view. (#5038) Specifying a default VHD path of Hyper-V - If you specify a directory that does not exist as a default VHD path of Hyper-V, registering a virtual machine server and collecting information fails. In that case, specify a correct path, and register and collect information again. When registering a virtual machine server fails, or when executing Collect, specifying a virtual machine server in the Resource view fails, "Not found" is outputted in the Operations log. (#5048) A number of CPUs of a VM server - If the number of CPUs of a VM server is two sockets or more, when displaying details of the virtual machine server on the Web Console, the number is displayed fewer than actual. (#5095) Citrix XenServer XenServer 4.1 Enterprise Edition is supported as a management target. (#3957) There was an issue of Citrix XenServer of not being able to use a VM created from a template created in NFS. This issue is resolved in 4.1. (#2587) An issue of collecting information of XenServer is resolved. (#3959) Treating storage of when creating a VM and template in the XenServer environment is improved. (#4432) An issue of ability to acquire CPU usage rate of a stopped Slave machine in System Monitor