HP Insight Dynamics 6.2 Integrity CMS Installation and Configuration Guide

After upgrading from a previous version
HP SIM upgrade If you upgraded HP SIM, follow any postinstallation instructions described
in the HP SIM documentation. Make sure that you have installed all required HP-UX or application
patches.
Stop and restart HP SIM by executing the following commands on the CMS:
# /opt/mx/bin/mxstop
# /opt/mx/bin/mxstart
It might take several minutes for HP SIM to restart completely. To verify that HP SIM has finished
restarting, execute the following command on the CMS:
# /opt/mx/bin/mxuser -lt
This command lists the users defined in HP SIM. If an error is displayed, wait several minutes
and try the command again.
Reapply demo licenses to managed systems After upgrading to ID-VSE for Integrity version
6.0 any systems that previously had a temporary demonstration (demo) license applied must be
explicitly licensed after the upgrade. To apply an ID-VSE for Integrity version 6.0 demo license
to a managed system, use either Insight managed system setup wizard or the vselicense -t
command. See “Using managed system setup wizard” (page 21) or the vselicense(1M) for more
details.
Verify gWLM communication and redeploy your SRDs If you are using gWLM, execute the
following command on the CMS to verify that the CMS is configured properly and can
communicate with installed agents:
# /opt/gwlm/bin/gwlm list
If the output of this command lists various policies, the CMS is configured properly. If not, error
messages are displayed. Wait a few seconds and try the command again. If you still get errors,
perform the actions recommended in the error messages.
Once communication is verified, redeploy any SRDs. In addition, for partition-based SRDs, follow
the procedure described next.
Rediscover partition-based SRDs If you are using gWLM, and you have upgraded the gWLM
agents in the partitions from gWLM A.02.xx to gWLM A.6.2.0.*, you cannot add other partitions
in the same complex to the SRD if you have either of the following types of partition-based SRDs:
• A Virtual Partition SRD inside an nPartition
• An nPartition SRD using Instant Capacity
Reestablish the SRD using Procedure 3-12.
Procedure 3-12 Rediscover partition-based SRDs
1. With the SRD deployed, rediscover the SRD. For a virtual partition SRD, execute the following
command:
# /opt/gwlm/bin/gwlm discover --type=vpar \
--file=/tmp/myfile.xml hosts
For an nPartition-based SRD, execute the following command:
# gwlm discover --type=npar \
--file=/tmp/myfile.xml hosts
In these commands, replace hosts with a space-separated list of the partitions in the SRD.
2. Make the following adjustments to /tmp/myfile.xml, as described in gwlmxml(4):
• Ensure that the mode attribute for the sharedResourceDomain element is set to the
desired value (Managed or Advisory):
mode="Managed"
• Ensure that the interval attribute for the sharedResourceDomain element is set
to the desired value:
After upgrading from a previous version 23