To get a list of vswitches currently defined for the VM Host, enter
the hpvmnet command. For example:
# hpvmnet
Name Number State Mode PPA MAC Address IP Address
======== ====== ======= ========= ====== ============== ===============
localnet 1 Up Shared N/A N/A
lan0 2 Up Shared N/A N/A
compnet 4 Down Shared lan0 16.116.14.205
clan1 5 Up Shared lan1 0x00306e3977ab
clan2 6 Down Shared lan2
|
The guest configuration file /var/opt/hpvm/guests/guestname/vmm_config.current contains
an entry for each guest virtual network device. For example:
.
.
.
# Virtual Network Devices
#
lan(0,0).0x00306E39F70B = switch(clan1)
.
.
. |
 |
| |
|
 | NOTE: When you are looking at the guest configuration file, remember that
the left side of the equals sign (=) is for the guest and the right side is
for the VM Host. |
|
| |
|
When the guest is booted (through hpvmstart or hpvmconsole), the guest LAN
is configured as specified in the LAN entry in the guest configuration file.
For example:
Entering the lanscan command on the guest compass1 results
in the following:
compass1# lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
0/0/3/0 0x00306E39F70B 0 UP lan0 snap0 1 ETHER Yes 119
0/1/2/0 0x00306E3977AB 1 UP lan1 snap1 2 ETHER Yes 119
0/4/1/0 0x00306E4CE96E 2 UP lan2 snap2 3 ETHER Yes 119
|
Note that the hardware path from the output of lanscan on
the guest matches what was specified in the guest configuration file. The Station
Address in the lanscan output also matches the
guest virtual MAC address in the guest configuration file.
Recreating a Virtual Switch |
|
You do not need to shut down and reboot the guest if you accidentally
delete its vswitch (for example, if you use the following command):
The Integrity VM network stack automatically determines that the guest
vswitch has disappeared. Once the guest's associated vswitch is re-created,
the guest network is alive again. The following console reconnect message
appears on the guest:
compass1# vswitch reconnect = e0000001398624c0
vswitch reconnect = e0000001398624c0... |
The message repeats until the guest vswitch is re-created and reconnected.
To change the vswitch to use another physical NIC on the VM Host (for
example, to change from lan0 to lan1),
delete the vswitch that was associated with lan0. Create
another vswitch with the same name or id and specify -n 1.
Your guest network should be back in a few seconds.
Redefining a Virtual Switch |
|
Modifying the bus/dev IDs of a LAN entry in the
guest configuration file has the same effect as moving a nework adapter from
one hardware slot to another on a nonvirtual machine. Similar to other other
HP-UX systems, the guest file /etc/rc.config.d/netconf must
be modified so that INTERFACE_NAME[0] reflects the new
LAN PPA assigned by the HP-UX network driver on the first guest reboot after
the modification. At this first reboot, the LAN interfaces configuration fails,
as follows:
Configure LAN interfaces ............................................ FAIL
* |
When the guest is running, you can use the lanscan command
to identify the new LAN PPA and to modify netconf accordingly:
# lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
0/0/5/0 0x02636C6E3030 1 UP lan3 snap3 1 ETHER Yes 119
|
In this example, before the modification, the LAN PPA was 0.
The new LAN PPA on the first boot after the modification is 3.
Therefore, you must bring the guest network down, then you must change the INTERFACE_NAME[0] from lan0 to lan3. You can then use /sbin/rc2.d/S340net to
restart the guest network:
# /sbin/rc2.d/S340net stop
# ch_rc -a -p "INTERFACE_NAME[0] = "lan3"
# /sbin/rc2.d/S340net start |
Your guest network is functioning
again.
You must restart a vswitch after the following events:
The MAC address is changed (either by swapping the network
adapter associated with the vswitch or associating the vswitch with a different
network adapter.
The IP address associated with the network adapter associated
with the vswitch is changed.
The way the network adapter accepts and passes on packets
to the next network layer is changed. This can occur as a result of the using
the ifconfig or lanadmin command to
set CKO/NOCKO on or off.
After you restart the vswitch, you must initiate communication from
the guest. For example, enter the ping command on the guest.
It is not necessary to reboot the guest.
Printable version
