HP Integrity Virtual Machines Version 4.2 Release Notes

7.2.18 Guest AVIO Interface Behavior
The following list describes the guest AVIO interface behavior when guest boots while vswitch
is down or resetting:
• If you boot a guest while the vswitch is not up, AVIO interfaces associated with the vswitch
might not be claimed in the guest. For example, this might occur if the guest is booted prior
to booting the vswitch or if the corresponding network interface on the VM Host is not
cabled. If you encounter this problem, first fix the vswitch state (that is, ensure that hpvmnet
displays its state as Up), and then execute the ioscan command in the guest. These actions
will claim the AVIO interfaces.
• After ioscan claims the AVIO devices in the guest, you might notice that the AVIO devices
cannot communicate with another VIO guest interface configured on the same vswitch.
When this occurs, invoke the hpvmnet -r option on the vswitch to restore connectivity.
• If the vswitch is in an unstable state while the guest is booting, guest AVIO interfaces might
fail initialization and move to the DOWN state (as displayed by thelanscan command).
When this occurs, first ensure that the vswitch enters a stable state, then reset the guest
interface using lanadmin.
7.2.19 AVIO LAN Devices Not Claimed by Guest with DOWN vswitch at Boot Time
In addition to running ioscan, you must re-run the necessary network startup scripts, so that
IP addresses can be reconfigured on the network interface cards (NICs). For example:
/sbin/rc2.d/S340net start
/sbin/rc2.d/S340net-ipv6 start
7.2.20 Do Not Use TCP Software Packet Reassembly in IGSSN Driver
For AVIO, there have been problems with TCP Software Packet reassembly in the igssn driver
in a guest HP-UX image. For this release, do not enable it on a guest. By default, software packet
reassembly (known with acronyms as drv_pr for driver packet reassembly) is enabled in igssn
in the guest.
To determine if drv_pr is enabled, an administrator can execute the following command:
lanadmin -x drv_pr ppa
where ppa is the Card instance # (Crd in#) from lanscan.
To manually disable drv_pr, an administrator can execute the following command:
lanadmin -X drv_pr_off ppa
To manually enable drv_pr, an administrator can execute the following command:
lanadmin -X drv_pr_on ppa
NOTE: These change are not carried over to subsequent reboots of the system. To maintain the
configuration over reboots of the guest, the administrator must edit the guest file, /etc/
rc.config.d/hpigssnconf.
For each igssn device that must have drv_pr disabled, you must construct a block of information
in the hpigssnconf file. For example, if your guest needed to have both lan0 and lan3 disable
drv_pr, you might have:
HP_IGSSN_INTERFACE_NAME[0]=lan0
HP_IGSSN_STATION_ADDRESS[0]=
HP_IGSSN_MTU[0]=
HP_IGSSN_DRV_PR[0]=0
HP_IGSSN_INTERFACE_NAME[3]=lan3
HP_IGSSN_STATION_ADDRESS[3]=
HP_IGSSN_MTU[3]=
HP_IGSSN_DRV_PR[3]=0
7.2 Known Issues and Information 73