Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
 HP Insight Dynamics – VSE for ProLiant 4.1 Update 1 Release Notes > Chapter 2 Installation, Configuration, and Licensing

ID-VSE 4.1 Update 1
» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

spacerspacerspacer
spacer
spacer
  		 
 

ID-VSE 4.1 Update 1 contains Windows CMS, Integrity Linux managed node, and HP-UX managed node updates.

Windows Central Management Server

ID-VSE 4.1 Update 1 for the Windows CMS resolves the following known issues with VSE Software, Application Discovery, Instant Capacity Manager, and Logical Server Management. See “Downloading the Windows CMS Update Kit” for instructions.

  • Agentless Data Collection Fails for Systems Configured in SIM with Domain Credentials  If Active Domain credentials (e.g., DOMAIN\login) are configured in SIM as WBEM credentials (or sign-in credentials that are used as WBEM credentials) for systems that are configured for agentless data collection in Insight Dynamics-VSE, data collection will fail for these systems. In this case, the error displayed both in the Visualization tab and when attempting to collect Capacity Advisor data is:

    Connection to host [hostname] was denied, due to incorrect/invalid WBEM credentials.  Configure valid WBEM credentials in Global or Systems Credentials for this host.

    ID-VSE 4.1 Update 1 resolves this issue.

  • Application Discovery Incorrectly Matches Processes to Templates after Restart   When Application Discovery is restarted on the CMS, Application Discovery no longer correctly distinguishes different application instances for those templates that require it, such as “Oracle instance=%1”, “SAP Systems %1”, and two other templates using the % (percent) sign in the template definition. Application Discovery incorrectly groups all the instances under the first instance discovered.

    ID-VSE 4.1 Update 1 resolves this issue by ensuring that Application Discovery correctly groups all application instances after Application Discovery is restarted on the CMS.

  • Instant Capacity Manager May Not Display Complex Names  In certain cases, special characters in the name of a complex or the existence of Serviceguard clusters may inhibit the display of complex names in iCAP Manager.

    ID-VSE 4.1 Update 1 resolves this issue by ensuring that Application Discovery correctly groups all application instances after Application Discovery is restarted on the CMS. Download the HP Application Discovery Agent A.04.01.01.107, provided as part of ID-VSE 4.1 Update 1.

The following issues apply to logical server management.

  • Default Timeout Value Changed from Five to Ninety Minutes   When you create a Hyper-V virtual machine logical server, the initial activation of the logical server requires creating the virtual hard disk. If you specified a large storage size (approximately 20GB or larger), the initialization may take a long time, but logical server management returns a timeout error after five minutes.

    ID-VSE 4.1 Update 1 corrects this problem by setting the default timeout value to 90 minutes. An alternate workaround is to edit the file <VSE>vse\conf\lsa\vmm\vmmController.properties, adding the following line: vmm.api.timeout = 5400000. Then restart the LSM service.

  • Fibre Channel Port Speed Reset to Disabled on VC Profile Using 8GB VC FC Module During Import  Importing a Virtual Connect blade with a VC profile that has an FC SAN connection port speed of 8GB or 1GB may incorrectly reset the FC SAN connection port speed to Disabled when the imported logical server is deactivated and reactivated. This may negatively impact the FC SAN storage performance for the logical server.

    ID-VSE 4.1 Update 1 corrects this problem by enabling Virtual Connect to auto-negotiate an FC port speed for the blade.

  • Activating ESX Virtual Machine Logical Server Does Not Allow 64–Bit Operating System Provisioning  ID-VSE 4.1 Update 1 corrects the problem of not allowing 64-bit Operating system provisioning by selecting the network type based on the operating system type.

  • Duplicate MAC Addresses Displayed if Virtual Machine Logical Server Has Two Networks with Same Name   If you created a virtual machine logical server and defined two or more networks using the same network name, duplicate MAC addresses are incorrectly displayed for these networks after activation. The created virtual machine is not affected by this problem, and correctly assigns unique MAC addresses to each network.

    ID-VSE 4.1 Update 1 corrects this problem by displaying the correct MAC address for these networks on the View Logical Server Details screen and the Modify Logical Server Network tab after activation.

  • Reactivating Logical Server Fails after Modifying Storage  If you modify the storage configuration of a virtual machine logical server after it has been activated and then deactivated, attempting to reactivate the logical server fails.

    ID-VSE 4.1 Update 1 corrects this problem.

  • Unrecoverable Delete of Logical Server Hangs but Deletes the VM Guest  

    Occasionally an unrecoverable deletion of a virtual machine logical server hangs at 0.0% complete. This occurs when logical server management is not notified that the deletion of the VM guest is complete. In this case, the logical server continues to exist after the operation fails, even though the underlying VM guest has been deleted.

    ID-VSE 4.1 Update 1 corrects this problem by ensuring that both the logical server and the VM guest are deleted during an unrecoverable logical server deletion.

  • Cannot Create Virtual Machine with Windows Server 2008 OS on ESX 3.5 Host  On an ESX 3.5 host, you cannot create a virtual machine with an operating system of Windows Server 2008, Standard. This occurs because an invalid OS key is used when the virtual machine is created.

    ID-VSE 4.1 Update 1 corrects this problem.

Downloading the Windows CMS Update Kit

To download the update kit for Microsoft Windows, use the following procedure.

  1. Go to http://www.hp.com and select the Support & Drivers link.

  2. Enter the name (or partial name) of a product in the product search field, such as “HP ProLiant DL585”.

  3. Select the desired product from the resulting list of products, such as “HP ProLiant DL585 G5 Server”.

  4. Select a supported Environment from the list available on the resulting page, such as “Microsoft Windows Server 2003”.

  5. On the Software Index page, select the “Software - System Management” category.

  6. Click the link to “Virtual Server Environment 4.1 Update 1” to review the release notes and installation instructions.

  7. Click the Download button to download the selected update kit to a host system.

Integrity Linux Managed Nodes

ID-VSE 4.1 Update 1 for Integrity Linux managed nodes resolves the following known issue with Application Discovery. See “Downloading and Installing the Application Discovery Agent Update Kit for Linux” for instructions.

  • Application Discovery Displays Provider Registration Error During Agent Installation on Linux  During the Application Discovery agent installation on Linux, an error will occur during the provider registration with the result that Application Discovery will not be able to gather application data from the managed node.

    ID-VSE 4.1 Update 1 resolves this issue. Install the Application Discovery agent for Linux on the CMS.

Downloading and Installing the Application Discovery Agent Update Kit for Linux

To download the Application Discovery agent update kit for Linux, use the following procedure.

  1. Go to http://www.hp.com and select the Support & Drivers link.

  2. Enter the name (or partial name) of a product in the product search field, such as “HP Integrity Servers”.

  3. Select the desired product from the resulting list of products, such as “HP Integrity BL870c Server Blade”.

  4. Select a supported Environment from the list available on the resulting page, such as “Red Hat Enterprise Linux 5 Server (Itanium)”.

  5. On the Software Index page, select the “Software - System Management” category.

  6. Click the link to “Virtual Server Environment 4.1 Update 1 Integrity Linux Agents” to review the release notes and installation instructions.

  7. Click the Download button to download the selected update kit (tar file) to a host system.

To install the Application Discovery agent update kit for Linux, use the following procedure.

  1. Replace the existing files in <vse install dir>/depot directory on a Windows CMS, or /var/opt/vse/depot/ on an HP-UX CMS.

  2. If you have a previous version of Application Discovery installed on your managed Linux nodes, remove it by executing the following steps.

    1. Find the name of the Application Discovery package installed on your system:

      # rpm -qa | grep -i appdisc

    2. Remove the Application Discovery package:

      # rpm -e <AD package name>

    For example, following are the steps to remove Application Discovery from a RedHat 5 node: 

    # rpm -qa | grep -i appdisc
ppdisc_rhe-A.04.01.00.-1
# rpm -e appdisc_rhe-A.04.01.00.-1

  3. Install the new Application Discovery agent by executing the following steps on HP-SIM:

    1. Configure->Configure VSE Agents->Install Linux VSE Agents…

    2. Select the Linux nodes where you want to install the new Application Discovery agent.

    3. Select only the “HP Application Discovery Provider for Integrity systems.” Software.

    4. Click OK.

Optional: You can manually install the new Application Discovery agent by executing the following steps:

  1. Download the Application Discovery agents tar file directly to a directory on your managed node.

  2. Untar the file:

    # tar –xvf hp.com-appdisc.tar

  3. Install the appropriate RPM according to your platform. For example, on a RedHat 5 system, enter:

    # rpm -Uvh appdisc_rh5e-A.04.01.01.rhel5.ia64.rpm

HP-UX Managed Nodes

ID-VSE 4.1 Update 1 for HP-UX managed nodes resolves the following known issues with Application Discovery, Global Workload Manager, and Utilization Provider. See “Downloading HP-UX Agent Updates” for instructions.

  • Application Discovery Agent Cannot Provide Application Data on HP-UX PA-RISC  Installation of the Application Discovery agent on HP-UX PA-RISC managed nodes succeeds, but the agent does not provide application information to the management server. This occurs because of an incorrect library reference.

    ID-VSE 4.1 Update 1, HP Application Discovery Agent A.04.01.01.107, corrects this problem.

  • Global Workload Manager Attempts to Allocate Cores Assigned to vPars not Managed by gWLM  In limited cases, gWLM might attempt to allocate cores assigned to virtual partitions that are not managed by gWLM on a fully owned system.

    ID-VSE 4.1 Update 1 resolves this issue by ensuring that gWLM allocates only cores assigned to partitions managed by gWLM.

    An alternate workaround is to manage all virtual partitions on an nPartition in the same shared resource domain.

  • Utilization Provider Logs Multiple Occurrences of Error in System Log File  Utilization Provider logs multiple occurrences of the message Unable to update the FSS resource partitions in the system logfile /var/adm/syslog/syslog.log. This occurs on HP-UX systems that do not have PRM (Process Resource Manager) tools installed

    ID-VSE 4.1 Update 1, HP-UX Utilization Provider A.01.08.02.01, resolves this problem by ensuring that Utilization Provider does not write error messages in the system logfile.

Downloading HP-UX Agent Updates

Agent updates for HP-UX managed nodes can be installed to the VSE agent repository on the CMS. This allows the updated agents to be installed to managed systems using the VSE Agent Distributor.

To download agent updates for HP-UX managed nodes, use the HP VSE Managed Node Software Update website (http://vsemgmt.external.hp.com/ ).

  1. Go to the HP VSE Managed Node Software Update website at http://vsemgmt.external.hp.com/ .

  2. Enter a contact e-mail address and select the appropriate VSE version.

  3. Select the radio button next to “VSE agent depot for VSE Management Software” and press the “I Accept” button.

  4. Download the updates by following the instructions on the Installation and Content Details page.



Chapter 2 Installation, Configuration, and Licensing
  		 


Back Up Your Existing CMS Configuration Prior To Upgrading The Software  
Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2007–2009 Hewlett-Packard Development Company, L.P.