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:
This command lists the users defined in HP SIM. If an error is displayed,
wait several minutes and try the command again.
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.04.00.07, 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-16.
Procedure 3-16 Rediscover Partition-Based SRDs
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.
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):
Ensure that the interval attribute
for the sharedResourceDomain element is set to
the desired value:
Ensure that the ticapMode attribute
for the sharedResourceDomain element is set to all if gWLM should allocate Temporary Instant Capacity
(TiCAP) when needed:
Ensure that the workloadReference entries in the compartment definitions are correct, and adjust the
names in the workload definitions themselves. For example, you might
see “host.OTHER.2” instead of “host.OTHER”.
Import
the file to re-create the SRD:
Because the SRD was already deployed, the new SRD definition is
deployed on import, taking the place of the original SRD.
Verify Capacity Advisor Data Migration. If you are using Capacity Advisor, use the command capprofile -lt to verify that previously
collected historical data has been migrated to the new VSE Management
Software database. This command lists the workload profiles and the
time range of the data stored in the database. For more information,
see capprofile(1M).
Restore Scheduled Capacity Advisor Tasks. If you are using Capacity Advisor, restore each
of your automatically scheduled Capacity Advisor data collection tasks
using Procedure 3-17.
Procedure 3-17 Restore Scheduled Capacity Advisor Tasks
Select Tasks & Logs
View All Scheduled
Tasks from the Capacity Advisor menu bar.
Select
the task from the list Collect Capacity Advisor Data.
Click Edit.
Click Schedule.
Clear
the Disable this task check box.
Click Done.
Verify
that the task you just edited is in the list and now shows Periodic in the Schedule column,
along with the date of the next collection.
Printable version
