HP Integrity Virtual Machines Installation, Configuration, and Administration Version A.03.50

hpvmnet(1M)
NAME
hpvmnet -- Create and control an Integrity Virtual Machines virtual network switch (vswitch).
SYNOPSIS
hpvmnet [ -S vswitch-name | -s vswitch-number ] [ -X | -M | -V ] [-v]
hpvmnet -c -S vswitch-name [-n nic-id]
hpvmnet -C [ -S vswitch-name | -s vswitch-number ] -n nic-id [-N
new-vswitch-name]
hpvmnet -d [ -S vswitch-name | -s vswitch-number ] [-F] [-Q]
hpvmnet -b [ -S vswitch-name | -s vswitch_number ]
hpvmnet -h [ -S vswitch_-name | -s vswitch_number ] [-F] [-Q]
hpvmnet -r [ -S vswitch-name | -s vswitch-number ] [-F] [-Q]
hpvmnet { -S vswitch_name | -s vswitch-number } -u portid:portid[,...]:vlanid:
{{vlan-id } | none }
hpvmnet { -S vswitch-name | -s vswitch-number } [ -p {all | portid} ] [-A] [ -M | -X ]
[-Z] [-v]
DESCRIPTION
A virtual machine accesses its network through a virtual network interface (vNIC) connected to
a virtual network switch (vswitch). The virtual network switch is connected in turn to a single
physical network interface (pNIC) on the VM Host. The hpvmnet command is used to create
and manage vswitches.
A vswitch works like an actual network switch. It accepts outbound network traffic from all
guests configured to use it and transmits the traffic over the physical interface. It accepts inbound
network traffic for all guests configured to use it and directs the traffic to the appropriate guest.
A virtual switch can be associated with at most one physical network interface. The VM Host's
physical network interface must be attached to a network with connectivity to the desired subnets.
The network interface may optionally be configured on the VM Host with an IP address or
multiple IP alias addresses, but this is only necessary if the VM Host shares the interface with
the vswitch and directs its own network traffic over the card. If you alter any characteristics of
a network interface associated with a running vswitch, for instance, through the ifconfig
commands on the VM Host, you must stop and restart the vswitch. Otherwise, any guests using
that vswitch will experience intermittent network failures. Stopping and restarting a vswitch
can occur while its guests are running; no guest shutdown is required.
You must reboot the vswitch (using the -r option) 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 network interface characteristics, for example, by using the lanadmin 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 guests while the vswitch is down.
There is no need to restart the guests that are using the vswitch. After you restart the vswitch,
restart communication from the guest side. For example, on the guest, ping the VM Host.
By default, Integrity VM creates a vswitch named localnet that is not associated with a physical
interface. It is used only for communication between the guests running on the same VM Host;
the VM Host itself does not participate in a localnet. There is no nameserver or router
configured on a localnet, unless one of the guests performs this function.
Only superusers can execute the hpvmnet command.
224