Technical data

7 Networking Information
This chapter contains notes about configuring networks for virtual machines.
7.1 Changes and Issues in This Release
The following sections contain networking information for the V4.3 release.
7.1.1 Integrity VM virtual iLO Remote Console Limitations
Integrity VM virtual iLO Remote Console limitations include the following:
• If the IP address or network settings are modified, and the Remote Console stops working,
you can restart the Remote Console by deleting and re-adding it:
# hpvmmodify -P guest -K 0
# hpvmmodify -P guest -K IP address -L netmask
• The virtual iLO Remote Console does not support captive accounts.
Prior to the virtual iLO Remote Console, guest administrators had to be created as captive
accounts, by changing the default shell. For example:
# useradd -r no -g users -s /opt/hpvm/bin/hpvmconsole \
-c "Console access to guest 'testme'" \
-d /var/opt/hpvm/guests/testme \
testme1
With the virtual iLO Remote Console, captive accounts are not supported. The guest
administrator should be created with the default shell:
# useradd -g users \
-c "Console access to guest 'testme'" \
testme1
The hpvmmodify -P -u testme1:admin [-u testme1:oper] is still required, as well as
the setting of a password for the user testme.
7.1.2 New Features Added to Integrity VM AVIO Networking
The following two new features have been added to Integrity VM AVIO networking:
• Multiple localnet support
By using this feature, you can create multiple instances of localnet vswitches. AVIO guests
configured on each localnet vswitches can communicate only among themselves. Additionally,
guests configured on the localnet vswitches cannot communicate with the VM Host or the
external world.
• Guest VLAN support for AVIO localnet
Integrity VM V4.3 introduces support for Guest VLAN tagging for local networks. Prior to
V4.3, this feature was supported only for guests that were configured on vswitches backed
by physical PPA. Starting with Integrity VM V4.3, the same Guest VLAN tagging support is
also supported on localnet vswitches.
For information about managing AVIO local networks, see the HP Integrity Virtual Machines 4.3:
Installation, Configuration, Administration manual.
7.1.3 IP Aliases Configured on the LAN Bound to a vswitch
If IP aliases were configured on the LAN bound to a vswitch, hpvmnet did not display the correct
primary IP address of the LAN. This problem has been corrected.
7.1 Changes and Issues in This Release 27