HP Matrix Operating Environment 7.3 Update 1 Installation and Configuration Guide for Provisioning with Virtual Resources

1. Modify the configuration file (shown in the default location) at C:\Program Files\HP\
Virtual Server Environment\conf\hp_lsa_service.conf.
2. Increase the value of wrapper.java.maxmemory=1024. HP suggests a value of 2048.
3. Restart the HP Logical Server Automation service.
Suggested action 2
To correct the PermGen space error, modify the configuration file to increase permanent generation
size:
1. Modify the configuration file (shown in the default location) at C:\Program Files\HP\
Virtual Server Environment\conf\hp_lsa_service.conf.
2. Add the following line. (Change additional.2 to additional.3 if a line with
additional.2 already exists; change additional.2 to additional.4 if lines with
additional.2 and additional.3 already exist, and so on.)
wrapper.java.additional.2=-XX:PermSize=32m -XX:MaxPermSize=128m
3. Restart the HP Logical Server Automation service.
Insight Control virtual machine management troubleshooting
Virtual machine logical server displayed with incorrect association
Issue
After a virtual machine logical server has been created, it appears in the Logical Server perspective
of Matrix OE visualization. This screen might display Active on unknown host for the location of
the logical server, or the logical server might be displayed without any host.
Possible causes
• The Active on unknown host condition is normal for up to 5 minutes after a new virtual machine
logical server has been created. Wait at least 5 minutes before attempting corrective action.
• When a virtual machine logical server is deactivated, the virtual machine is unregistered from
the VM host. The virtual machine is then displayed without an association in Matrix OE
visualization perspectives. This behavior is expected.
• The VMware WBEM provider might have returned invalid or incomplete data due to an error
in the WBEM provider.
• Other environmental changes:
Name resolution of the VM host might no longer be configured correctly.◦
◦ Credentials for the VM host might have been modified and are no longer correct in HP
SIM.
◦ Network connectivity between the CMS and the VM host may not be available.
Suggested actions
• For a newly-created virtual machine, navigate to the VM host System page, and verify that
the newly-created virtual machine appears. If the VM appears, select Options→Identify Systems.
This operation adds the virtual machine to HP SIM and update the Logical Server view to
display the VM name as the location.
• Check the VM host System Page in HP SIM to determine if HP SIM has the correct host-guest
associations:
Troubleshooting procedures 161