HP-UX vPars and Integrity VM V6.3 Administrator Guide

After configuring the /etc/ntp.conf file of the guest, assuming NTP is already enabled (that
is, the XNTPD variable in /etc/rc.config.d/netdaemons is set to 1, as in export XNTPD=1),
you can run the following commands on an HP-UX guest to sync its time with the VSP and restart
the xntpd command:
/sbin/init.d/xntpd stop
/usr/sbin/ntpdate -b <VM-HOST-SERVER-NAME>
/sbin/init.d/xntpd start
NOTE: For guests that are on a different subnet than the VSP, the VSP might not be the best
source of time if there is another accurate time server available with less network latency. In different
subnets, measure latency from the guest to various time servers using the ping and traceroute
commands to determine the potential time server that has the least network latency. Using the VSP
might be the best solution, but this depends on your local network topology and the relative network
distance to alternate time servers. If it appears best to use an alternate (non VSP) time server, it
might be helpful for the alternate time server and the VSP to use each other for peer mutual time
synchronization.
12.3.2 VSP requirements and setup
All the latest HP-UX patches that Integrity VM requires, and any required Integrity VM patches must
be installed. For more information about vPars and Integrity VM installation, including supported
VSP operating system versions, patches, and other system requirements, see HP-UX vPars and
Integrity VM Release Notes, available at http://www.hp.com/go/hpux-hpvm-docs. Required
patches are available at https://hpsc-pro-athp.austin.hp.com/portal/site/hpsc/public.
12.3.2.1 VSP processors for online migration
VSPs can be different Integrity server models with different number of processors, different I/O
adapters and configurations, different amounts of memory, different firmware revisions, and so
on. In particular, guests can migrate between radically different size, capacity, and power VSPs.
However, for online migration, all the eligible VSP servers in a group must have equivalent
architecture implementations. The processors on the source and destination VSPs must all be within
one of the following groups:
• All Integrity VM supported variants of the Itanium 2 processor prior to the 9000
• Itanium 2 9000 and the Itanium 2 9100
• Itanium 9300
• Itanium 9500
NOTE: Starting with HP-UX vPars and Integrity VM V6.3, the inter-processor family migration
between 9300 and 9500 series is supported. For more information about online migration support,
see Section 12.4 (page 215).
Different processor frequencies and cache sizes are supported for OVMM. Table 28 (page 207)
lists the recent Itanium processors showing different values for processor family.
Table 28 Itanium processor families
SeriesModelFamily
Itanium 2031
Itanium 2131
Itanium 2231
Itanium 9000032
12.3 VSP and VM configuration considerations 207