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
 VSE Management Software Release Notes Version A.03.00.01 > Chapter 4 Known Problems and Workarounds

Installing, Uninstalling and Reinstalling VSE Management Software
» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

spacerspacerspacer
spacer
spacer
  		 
 

Incompatibility With HP SIM Version 5.1

VSE Management Software is not supported under HP SIM version 5.1 (C.05.01.00.00.xx). If you have installed that version of HP SIM, upgrade to HP SIM version C.05.01.00.01.xx.

Workaround

If your CMS is HP SIM version C.05.01.00.00.xx, perform the following actions on the CMS:

  1. Uninstall VSE Management Software, if it is installed. For instructions, see the VSE Management Software Installation and Update Guide.

  2. Upgrade to HP SIM version C.05.01.00.01.xx. For instructions, see the HP Systems Insight Manager Installation and Configuration Guide for HP-UX .

  3. If applicable, restore the VSE Management Software database from a backup that was performed prior to updating HP SIM. For information about backing up and restoring the VSE Management Software database, see vseinitconfig(1M). This manpage is included in the VSE Management Software Installation and Update Guide.

Upgrading from VSE Management Software Version 2.x to Version 3.0 Can Leave Non-Functional Menus

Upgrading from VSE Management Software Version 2.x to VSE Management Software Version 3.0.1 on HP SIM Version C.05.00.02.00.XX or C.05.01.00.01.XX can leave non-functional menus that should have been removed.

Workaround

  • If you see two View Scenarios... entries when you select Configure->Capacity Advisor->, then execute this command to remove the extra menu: 

    /opt/mx/bin/mxtool -r -t "View Scenarios"

  • If you see an Install Unix-Linux VSE Agents... entry when you select Configure->Configure VSE Agents->, then execute these commands: 

    /opt/mx/bin/mxtool -r -t "Install Unix-Linux VSE Agents"
/opt/mx/bin/mxtool -r -t "Install Unix-Linux VSE Agents - subtask"
/opt/mx/bin/mxtool -r -t "Install Windows VSE Agents - subtask"

Removing and Reinstalling Software Might Change Workload IDs

Removing and then reinstalling the VSE Management Software deletes all workload information about the managed systems from the CMS. This leaves the workload information on the managed systems inconsistent with the CMS.

Workaround

Usually, this situation can be corrected by selecting Tools->Update System Workloads, as described in the “Update System Workloads” topic in the Virtualization Manager help system. This action removes the information on the managed systems about monitored workloads that are no longer defined on the CMS, and synchronizes the workload IDs of the whole-OS workload and the hostname.OTHER workload.

However, if all of the following conditions apply, then the CMS and managed-system workload definitions can still be inconsistent after running Update System Workloads.

  • You created new monitored workloads after reinstalling the software and before running Update System Workloads.

  • Any of the new workloads have the same name as a workload that was known on the managed system before the software was reinstalled on the CMS.

In this case, the IDs of the workloads that were previously known on the managed system are not updated by Update System Workloads. These workload definitions should be deleted and re-created.

To avoid this problem in the future, back up the VSE Management Software database before removing the software, and restore the database after it is reinstalled. For information about backing up and restoring the VSE Management Software database, see vseinitconfig(1M).

Data Associated with Wrong Workload After Reinstallation

Removing and reinstalling the VSE Management Software does not delete the data collected from the managed systems. As new workloads are created, the new workloads might reuse the IDs of some of the old workloads. In that case, data stored on the managed nodes using the old workload ID might be collected and associated with a new workload that happens to have the same ID.

Workaround

To fix this problem after it has occurred, use the Capacity Advisor profile editor to mark any data older than the reinstallation time as invalid data.

To avoid this problem in the future, back up the VSE Management Software database before removing the software, and restore the database after it is reinstalled. For information about backing up and restoring the VSE Management Software database, see vseinitconfig(1M).

Failure to Open SSH Channel

If you are using HP-UX Secure Shell (OpenSSH) version A.04.30.x, or if you have upgraded from that version to a more recent version, the following message can be displayed on the CMS when attempting to establish an ssh connection to a managed system: “The administrator does not permit this channel to be opened. open failed. The failure is due to configuration problems and and/or potential defects in the target systems SSH server.”

Workaround

HP-UX Secure Shell version A.04.30.x is not supported for use with the VSE Management Software. If you are using that version, upgrade to the latest version. For more information, see the VSE Management Software Installation and Update Guide Version A.03.00.01 (“Table 2-7 Additional Software Required on Managed Systems”).

After upgrading to HP-UX Secure Shell version A.04.40.x or later, perform either of the following additional steps:

  • Restart HP SIM on the CMS. Run the command mxstop to stop HP SIM, then restart HP SIM using mxstart.

  • Login to the managed system and kill the existing ssh connections. These connections will be displayed in the process list with the name root@notty.

swverify Warnings

Depending on the product selection and the order of installation, the swverify command may produce warnings such as "WARNING: hostname: 1 files had warnings during this operation." Subsequent swjob commands (or inspection of the swagent.log) reveal that the warning is against the directory /etc/opt/vse.

Workaround

These warnings can be safely ignored. They can be removed by determining the affected fileset from swjob or the swagent.log, then executing 

swmodify -x files=/etc/opt/vse PRODUCT.FILESET

Typically PRODUCT.FILESET is VSE-CMS.VSE-RUN, but other filesets might be causing the warnings.

Agent Software Installation Does Not Remove VSEMgmtAgents Bundle

If you installed the VSEMgmtAgents bundle that was delivered with release 2.5 of the VSE Management Software, the swlist command lists the software as shown below: 

VSEMgmtAgents,r=A.02.50.00.04

When the agent software is updated to version 3.0.1 using the process described in the VSE Management Software Installation and Update Guide Version A.03.00.01 (“Installing VSE Agent Software on Managed Systems”), the older bundle is not removed. The swlist command continues to indicate that the older bundle is installed, although the individual agents and providers are correctly updated.

Workaround

No workaround is necessary, since the agent software is correctly updated. If desired, you can use swremove to remove the VSEMgmtAgents bundle.



Chapter 4 Known Problems and Workarounds
  		 


Data Collection Issues  
Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2006-2007 Hewlett-Packard Development Company, L.P.