HP vPars and Integrity Virtual Machines V6.1 Administrator Guide

For AVIO, HP strongly recommends that you use the same AVIO components from the same release
on both the VSP and vPar/VMs, for example, both from the OE or both from the same Web Release
(for example, WEB1103).
The AVIO network VSP driver allows simultaneous access to a vswitch from vPar/VMs configured
with or without AVIO vPar/VM drivers for their virtual network interface cards (vNICs). Existing
vPar/VMs continue to operate correctly, and their configurations remain unchanged. Virtual clients
configured to use a common vswitch are allowed to share VLANs that are in use by vPar/VMs
with or without AVIO configured. Ports remain distinct for each running a vPar/VM whether or not
AVIO is in use. AVIO networks must use a Supported Host Physical Point Attachment (PPA) network
device. For a list of supported AVIO PPAs, see the HP-UX vPars and Integrity VM V6.1 Release
Notes at http://www.hp.com/go/hpux-hpvm-docs.
NOTE: When using AVIO networking devices for vPar/VMs that are configured as Serviceguard
Packages, be sure that all Serviceguard standby lans are configured using PPA devices supported
by AVIO. Failure to do so causes network connectivity to be lost even if the standby link is up.
2.8 VSP kernel tunables
Upon installation, tunables are set to the following values:
• maxdsiz_64bit – 34359738368 (4294967296)
• filecache_min – 134217728 or 1% (1707212800)
• filecache_max – 134217728 or 1% (17072390144)
• lockable_mem_pct – 99% (90%)
• base_pagesize — 64 (4)
• vx_ninode — 131072 (0)
• vxfs_ifree_timelag — -1 (0)
• vxfs_bc_bufhwm — 64000 (0)
The first value is the modified value and the number in parenthesis is the default .
2.8 VSP kernel tunables 33