HP Integrity Virtual Machines 4.2.5: Release Notes
nwmgr CommandLegacy CommandTask
# nwmgr -s -A vmtu=0 -c lan0
lano current values:
New Virtual MTU=0
# lanadmin -X vmtu 0 0
Virtual MTU is set to 0
Turn TSO off on lan0.
# nwmgr -s -c lan0 -A all
--sa -fr cu
Manually edit the configuration file in
/etc/rc.config.d, or use SAM
interface. See the Ethernet Support
Guide for details.
Allow the TSO attribute change along
with the rest of the lan attributes to be
perserved between system reboots by
saving the current attributes to the lan
configuration file.
7.2.22 Restarting Vswitches
It is necessary to restart the vswitch when:
• You replace the physical network card associated with the vswitch.
• You change a VM Host IP address associated with the vswitch's network interface card.
• You change the network interface characteristics on the VM Host; for example, by using the
nwmgr command to change checksum offloading (CKO).
• You notice that there is no communication from an avio_lan interface to a lan interface
after booting the guest(s) while the vswitch is down.
For information about how to restart vswitches, see the HP Integrity Virtual Machines 4.2: Installation,
Configuration, and Administration manual.
When you restart a vswitch, it is not necessary to restart the guests using the vswitch.
7.2.23 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 nwmgr.
7.2.24 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.25 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
7.2 Known Issues and Information 77