SigmaSystemCenter 3.3 Update Module (SSC0303-0003.zip) 

Patch Name         : SSC0303-0003
Patch Description  : A module to improve problems considered in 
                     SigmaSystemCenter 3.3.
Release Date       : Dec/19/2014
File Name          : SSC0303-0003.zip
Target Product     : SigmaSystemCenter 3.3
Target Versions of Components *1:
  SigmaSystemCenter Version: 3.3-26007, SystemProvisioning 6.3.0023
  System Monitor - Performance Monitoring Services Version: 5.5.1031.0
Necessary Patch    : 
  SigmaSystemCenter: SSC0303-0002-update1
  System Monitor - Performance Monitoring Services: SSC0303-0002-update1
Reboot             : N/A 
Patches Contained in This Patch : N/A

*1) How to check target versions of components

    - SigmaSystemCenter and SystemProvisioning
      A version is displayed at the bottom of the Web Console.

      Target Version:
       "Version: 3.3-26007, SystemProvisioning 6.3.0023"
       (SigmaSystemCenter 3.3 SSC0303-0002-update1 is already applied.)

    - System Monitor - Performance Monitoring Services
      1) Click the [Start] button, select [All Programs]. From [All Programs],
         select [SigmaSystemCenter]. From [SigmaSystemCenter],
         select [System Monitor Management Console] to start the management
         console of System Monitor - Performance Monitoring Services.
      2) The Logon window appears. Click [Cancel].
      3) Click the [Help] menu, select [Version Information] to display the
         Version Information window.
      4) The version is displayed at the Version.

         Target Version: 5.5.1031.0

This update module incorporates the following fixes 
in SigmaSystemCenter 3.3.

1. Fixed Problems

1.1. Fixed Problems in SystemProvisioning

(1) The plotting interval of LUN's graphs become incorrect in machine
    performance summary graph when set plotting interval to
    "Auto adjustment". (#16156)

    Phenomenon:
    In an environment that display LUN's graph, when set the plotting interval
    to "Auto adjustment" in the graph setting of machine performance
    summary graph, the plotting interval of LUN's graphs become incorrect
    and do not display the continuous line in graphs.

    Problem Explanation:
    Because did not use the LUN monitoring profile to calculate the plotting
    interval when set the plotting interval to "Auto adjustment", 
    the plotting interval of LUN's graph became incorrect.

    Solution:
    When set the plotting interval to "Auto adjustment", use the LUN
    monitoring profile to calculate the plotting interval.

(2) When System Monitor - Performance Monitoring Services is operating 
    on other management server from SigmaSystemCenter, the data line 
    on LUN's graph cannot be displayed. (#16157)

    Phenomenon:
    When the management server of System Monitor - Performance Monitoring Services
    is different from SigmaSystemCenter, the data line on LUN's graph
    cannot be displayed. 
    And when the port of System Monitor - Performance Monitoring Services is not
    set to "26200", the data line on LUN's graph also cannot be displayed.

    Problem Explanation:
    Because did not use the value of SysmonServerIP and SysmonServerPort under
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\PVM\SysmonPerf\iStorage
    registry where set the performance monitoring setting for NEC Storage,
    the default value "127.0.0.1" and "26200" are used.
    For this reason, when the management server of System Monitor - Performance
    Monitoring Services is not "127.0.0.1" and "26200", the data line on
    LUN's graph cannot be displayed.

    Solution:
    Use the value of SysmonServerIP and SysmonServerPort under the NEC Storage
    performance monitoring registry setting.

(3) Two groups which have the same name is created on the [Operations] view.
    (#16172)

    Phenomenon:
    If you start up two command prompt windows and specifying ssc create group command
    in the same group name respectively, two groups with the same names
    might be created when each command will be executed without any intervals.

    Problem Explanation: 
    SigmaSystemCenter checks if the newly created group name will not be overlapped
    in the existed ones. However, as can be seen above, the group with the
    overlapped name will be created when the commands, in specifying with the same
    group names, will be executed without any intervals before the first command
    is completed.
    In this situation, the second command decides that the group name is not
    overlapped and creates the group with the same name.

    Solution:
    Fixed the process so that the checking of overlapped name in the second
    command is started after the first command is completed.

(4) The IP address of the NIC 1 is reflected instead of the management IP address
    in System Monitor - Performance Monitoring Services. (#16453)

    Phenomenon:
    If you reflect the host setting information of SystemProvisioning in System
    Monitor - Performance Monitoring Services by operation of Apply SystemProvisioning
    Configuration, the IP address of the NIC 1 will be appeared, instead
    of the management IP address of System Monitor - Performance Monitoring Services
    in the [IP Address] under the [General] tab of the machine setting screen of
    SystemMonitor Management Console.

    Problem Explanation: 
    When executing Apply SystemProvisioning Configuration, SystemProvisioning
    should return the management IP address configured in the SystemProvisioning host
    as the IP address of the monitoring target to System Monitor - Performance Monitoring
    Services. However, there are some problems in the process, the IP address of
    the NIC 1 is returned.

    Solution:
    Fixed the process so that the management IP address is returned to System
    Monitor - Performance Monitoring Services as the host information of the IP address
    of the monitoring target.

(5) The OS name is reflected which differs from the OS name of the host profile
    in System Monitor - Performance Monitoring Services. (#16537)

    Phenomenon:
    If you reflect the host setting information of SystemProvisioning in System
    Monitor - Performance Monitoring Services by operation of Apply SystemProvisioning
    Configuration, the OS name, which is different from the host profile
    OS name of SystemProvisioning, will be appeared in the [OS Name] under 
    the [General] tab of the machine setting screen of SystemMonitor Management Console.

    Problem Explanation: 
    When executing Apply SystemProvisioning Configuration, SystemProvisioning
    should return the OS name of the host profile applied to the SystemProvisioning host
    as the OS name of the host of System Monitor - Performance Monitoring Services.
    However, there are some problems in the process, the wrong OS name is retuned.

    Solution:
    Fixed the process so that the OS name of the host profile is returned to
    System Monitor - Performance Monitoring Services Console as the OS name of
    the monitoring target host.

1.2. Fixed Problems in System Monitor - Performance Monitoring Services

(1) The local user script with same command is executed multiple times in the
    same data collection period. (#16151)

    Phenomenon:
    When specify performance indicators which executing a local user script
    with the same command to multiple monitored targets, The local user script
    is executed multiple times in the same data collection period.
    As the result of this issue, because the performing of the local user script
    is not finished in the data collection period, the next data collection can
    not be performed.
    
    In the same data collection timing, even if specify a local user script
    with the same command is executed by multiple times, the local user script
    can execute in the first execution only in System Monitor - Performance
    Monitoring Services.

    Problem Explanation:
    When specify performance indicators which executing a local user script
    with same command to multiple monitored targets, the executed commands
    have been normally excluded in order not to execute again.
    But sometimes, it is executed by multiple times without being excluded.

    Solution:
    Fixed so that the same command is not executed for multiple times.

(2) Other performance data collections cannot be executed when taking
    an extremely-long time to collect the performance data by executing a local
    user script. (#16196)

    Phenomenon:
    When taking an extremely-long time to collect the performance data
    by executing a local user script, other performance data collections
    cannot be executed until the execution is completed. 
    Therefore, other performance data collections cannot be performed
    in this interval.

    Problem Explanation:
    The performance data collection by executing a local user script and 
    other data collections share the real work thread.
    When the data collection by executing a local user script hold the
    work thread, other executions cannot be performed.
    If the data collection by executing a local user script takes 
    an extremely-long time, other procedures might be delayed.

    Solution:
    The performance data collection by executing a local user script and
    other data collections use different work thread.
    This process allow other performance data collections not to be 
    affected by the long time execution of a user script.

(3) The summary data cannot be obtained from the collected performance data
    which is collected by executing a local user script. (#16198)

    Phenomenon:
    The performance data that is gathered by executing a local user script 
    may not be displayed on the graph.
     - The collection interval of the performance indicator which collect
       performance data by executing a local user script is set to 
       30 minutes.
     - The performance data with 5 minutes interval is collected. 

    Problem Explanation:
    As can be seen above, there are some data which is not included in the summary
    of the data processing when the data of multiple times is registered by a local
    user script within a collection interval. 
    Therefore, some data cannot be registered correctly in the summary table.
    The graph is not displayed correctly when executing the graph display in
    the setting of a plot interval which uses the data of the summary table.

    Solution:
    When specifying the performance data of a local user script, the collection
    interval is extended to assume the possibility of being registered the data of
    multiple times during the collection interval. This avoids the unprocessed
    data is existed. 

(4) Missing data is occurred when collecting LUN's performance data under
    the environment of managing the large scale system and the management server
    is in high-intensity performance.(#16336)

    Phenomenon:
    In the environment of collecting LUN's performance by collaborating with
    NEC StorageManager and PerforMate environment, if you should manage the large
    scale system and the management server is in high-intensity performance, there
    might be some performance data which cannot be collect when collecting
    the LUN's performance data.

    Problem Explanation:
    Under the environment of managing the large scale system and the management
    server is in high-intensity performance, the variability of the executing
    time of processing performance data through System Monitor - Performance
    Monitoring Services is likely to increase. Because the period of the collecting
    performance data is depend on the local user script which corresponding with
    NEC StorageManager and PerforMate, when the variability is widened, some
    performance data might not be collected. 

    Solution:
    Fixed so that the target period of the collecting performance data is not
    varied even if the executing timing of the local script is varied widely.

(5) Enhance the performance for collecting performance data by executing
    local user script in a large-scale environment. (#16337)

    Phenomenon:
    In a large-scale environment, the processing of performance data might take
    much time when using a local user script to collect for multiple monitored
    targets and multiple performance indicators by the same command.

    Problem Explanation:
    System Monitor - Performance Monitoring Services save the executing information
    to an inner cache in order not to execute the local user script in multiple times
    when using a local user script to collect for multiple monitored targets and
    multiple performance indicators by the same command. However, the use of cache
    is still inefficient and it takes much time.

    Solution:
    Enhance the operating performance by improving the efficient in use of cache.

(6) The data of CPU Usage (MHz) for Windows/Linux physical machine is set to 0.
    (#16520)

    Phenomenon:
    The data of CPU Usage (MHz) for Windows/Linux physical machine is set to 0.

    Problem Explanation:
    For calculating the performance data of CPU Usage (MHz), the number of CPUs
    of Windows/Linux physical machine that register on NEC ESMPRO Manager
    should obtain from  SystemProvisioning. But it does not use the CPU number
    to calculate the performance data of CPU Usage (MHz).
    For this reason, the number of CPUs is calculated as 0 and the value
    of CPU Usage (MHz) is set to 0.

    Solution:    
    Use the number of CPUs of Windows/Linux physical machine that register on
    NEC ESMPRO Manager to calculate the performance data of CPU Usage (MHz)
    for Windows / Linux physical machine.

    - Note that the performance data of CPU Usage (MHz) for Windows/Linux
      physical machine do not consider the number of Cores and hyper threading.
      Because only the number of Sockets can be obtained from NEC ESMPRO Manager,
      the number of Cores and others cannot be obtained.

===============================================================================
Installation Procedures and Release Modules List
===============================================================================

For the procedures to unzip and install this software, other information 
regarding installation, and release modules list, see Install.txt.

In addition, if you set up SigmaSystemCenter components in a clustering 
environment, see Clustering.txt for the installation procedures in a clustering
environment.


===============================================================================
Notes on Unzipping a .zip File
===============================================================================

[Notes 1]

 Before unzipping the zip file of this software, confirm and delete the ZoneID
 information with the following procedure.
 If you unzip the zip file and install the software with the ZoneID 
 information, the module after installing the software will not work properly.

 The information called "ZoneID" has been added to a file downloaded 
 from a site in a zone configured other than [Intranet] on Internet Explorer 
 of Windows Vista, Windows XP Service Pack 2 or later, 
 or Windows Server 2003 Service Pack 1 or later.

 If ZoneID is added to the zip file, the ZoneID information is succeeded to a
 deployed file and a warning of security is displayed when executing the file,
 consequently, services or processed may not start.

 (1) Checking and changing the policy setting (Hide mechanisms to remove zone
     information):

     1) Click the [Start] button, and click [Run].

     2) Enter "gpedit.msc", and click [OK].

     3) The Group Policy Object Editor dialog box appears. Click [User
        Configuration], click [Administrative Templates], double-click 
        [Windows Components], and double-click [Attachment Manager].

     4) Check the [State] of [Hide mechanisms to remove zone information].
        If it is "Enabled," click [Disabled] on the Hide mechanisms to remove
        zone information Properties dialog box, and click [OK].
        If it is "Disabled" or "Not Configured," you do not need to change 
        the setting.

 (2) Deleting the ZoneID information of the zip file:

     1) Open the properties dialog box of the zip file, and click the [General]
        tab.

     2) If the following message is displayed, click [Unblock], and click [OK].

          Security:  This file came from another 
                     computer and might be blocked to
                     help protect this computer.

 (3) Changing the policy setting (Hide mechanisms to remove zone information):
     If you changed the policy setting (Hide mechanisms to remove zone
     information) from "Enabled" to "Disabled," configure it to "Enabled" with
     the same procedure.

[Notes 2]

  When unzipping the zip file of this software, specify a path whose length is 
  not over 80 bytes as the path to extract.
  If you specify a path whose length is over 80 bytes, the zip file might
  not be extracted properly. 


--------------------------------------------------------------------------------
[Terms of Use]

Terms for use of this update module conform to "NEC Software License Agreement"
of the product to which this software will be applied.


--------------------------------------------------------------------------------
[Trademark and Copyright Information]

All rights reserved. Copyright in this software is owned by NEC Corporation.

* All other brands and products used in this document are the trademarks or
  registered trademarks of their respective trademark holders.
--------------------------------------------------------------------------------
   Copyright NEC Corporation 2014