HP Virtual Server Environment Management for Integrity Version 4.0 Release Notes

[mysystem#3] > grep 15.11.100.17 /etc/hosts
15.11.100.17 mysystem.mydomain.com mysystem
d. Verify that the reverse lookup of the IP address returns the same fully qualified
domain name as configured in /etc/hosts.
[mysystem#4] > nslookup 15.11.100.17
Trying DNS
Name: mysystem.mydomain.com
Address: 15.11.100.17
Fix any issues by editing /etc/hosts or for additional information, see:
— The HP-UX IP Address and Client Management Administrator's Guide, available online at
http://docs.hp.com.
— The BIND 9 Administrator Reference Manual, available from the Internet Systems
Consortium at http://www.isc.org/sw/bind/arm93.
— The Windows documentation.
Error During Discovery of Compartments The following message might be displayed when
you use the Manage New Systems wizard or the gwlm discover command:
Error during discovery of compartments.
In addition, the /var/opt/gwlm/gwlmagent.log.0 file contains the following message:
com.hp.gwlm.common.PlatformException: /usr/sbin/parstatus -w exited
with a non-zero exit status. Captured stderr is: Error: Unable to
get the local partition number.
Workaround This is most likely due to having an outdated version of the nPartition
Provider software. Global Workload Manager uses a command that is made available by
the nPartition Provider, which is typically in every version of HP-UX, to determine system
capabilities.
You can also use the /opt/vse/bin/vseassist command to diagnose the issue.
Install the latest nPartition software, even if you are not using nPartitions.
For HP-UX 11i v1, use version B.11.11.01.03.01.01 or later.
For HP-UX 11i v2 on HP 9000 servers, use version B.11.23.01.03.01.01 or later.
For HP-UX 11i v2 on HP Integrity servers, use version B.11.23.01.04 or later.
You can find the nPartition Provider at the following locations:
— The quarterly AR CD starting May 2005
— The Software Depot website http://software.hp.com
Modifying Java While gWLM is Running gWLM does not support any actions (including
the use of update-ux) that remove, overwrite, or otherwise modify the version of Java that
gWLM is using in a managed node or CMS that is part of a deployed SRD.
Workaround Undeploy an SRD before taking any actions that affect the version of Java
that gWLM is using on systems that are part of the SRD. If you used update-ux, be sure
to:
— Restart the CMS daemon on the CMS
Using the command-line interface: /opt/gwlm/bin/gwlmcmsd
Using the HP SIM interface: Select the menus Configure Configure VSE Agents
Start gWLM CMS Daemon
— Restart the agent on the managed nodes
Using the command-line interface: /opt/gwlm/bin/gwlmagent
Global Workload Manager 45