Operating System - HP-UX
1834346 Members
2124 Online
110066 Solutions
New Discussion

Re: linkloop fails on vNIC

 
Jerry Jiangwei
Advisor

linkloop fails on vNIC

Hello,

I am working on hpvm creation.

On my box, I connect wire on lan0,
the linkloop cmd output can prove it works.

bash-4.0# linkloop 0x0017087cd802
Link connectivity to LAN station: 0x0017087cd802
-- OK
bash-4.0# lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
0/1/2/0 0x0017087CD802 0 UP lan0 snap0 1 ETHER Yes 119
0/1/2/1 0x0017087CD803 1 UP lan1 snap1 2 ETHER Yes 119
0/4/1/0 0x0017A4767D93 2 UP lan2 snap2 3 ETHER Yes 119

and I create vswitch name vswitch0, connected to lan0, see the hpvmnet command,

bash-4.0# hpvmnet
Name Number State Mode NamePPA MAC Address IP Address
======== ====== ======= ========= ======== ============== ===============
localnet 1 Up Shared N/A N/A
vswitch0 4 Up Shared lan0 0x0017087cd802 16.157.129.250


then, I create vNIC to connect vswitch0

hpvmmodify -P config0 -a network:lan:0,0,0x7214de1aa152:vswitch:vswitch0

but I find on my vm host box, the linkloop commmand failed on vNIC (0x7214de1aa152)


bash-4.0# linkloop 0x7214de1aa152
Link connectivity to LAN station: 0x7214de1aa152
error: get_msg2 getmsg failed, errno = 4
-- FAILED
frames sent : 1
frames received correctly : 0
reads that timed out : 1


How can I make the vNIC really connect the vswitch?

Thanks
-- Jerry
3 REPLIES 3
Michael Steele_2
Honored Contributor

Re: linkloop fails on vNIC

Hi

What is:

grep FRAMES /etc/rc.config.d/hpvmconf
Support Fatherhood - Stop Family Law
Jerry Jiangwei
Advisor

Re: linkloop fails on vNIC

Hi,

The output is empty.

Michael Steele_2
Honored Contributor

Re: linkloop fails on vNIC

Hi

I've pasted in the procedure from the guide. Look at the "...hpvmnet -b -S clan0..." and the arguments used. Note the comments below about this command.


Configure and Start a Virtual Network
The first step is to run ioscan and the hpvmnet command to gather information
about network interfaces, configure a virtual network, and enable the
virtual network as shown in the following commands all run on the host:
# ioscan -f | grep lan
lan 0 0/0/3/0 intl100 CLAIMED INTERFACE Intel PCI Pro 10/100Tx
Server Adapter
lan 1 0/1/2/0 igelan CLAIMED INTERFACE HP PCI 1000Base-T Core
# hpvmnet -c -S clan0 -n0
# hpvmnet -v
Version 1.0.0
Name Number State Mode PPA MAC Address IP Address
======== ====== ======= ========= ====== ============== ===============
localnet 1 Up Shared N/A N/A
clan0 3 Down Shared lan0 192.6.175.13
92 Chapter 3 HP Integrity Virtual Machines
# hpvmnet -b -S clan0
# hpvmnet -v
Version 1.0.0
Name Number State Mode PPA MAC Address IP Address
======== ====== ======= ========= ====== ============== ===============
localnet 1 Up Shared N/A N/A
clan0 3 Up Shared lan0 0x00306ef3ab5c 192.6.175.13
#
The iocan output shows two lan interfaces. lan0 was selected as the
device for which the virtual network would be created. The hpvmnet command
was run with the -c option to create a new virtual network switch, -S to
specify the switch name of clan0, and -n to specify lan0 or PPA 0 as the
physical device to use. The hpvmnet -v command shows in the verbose output
that clan0 is down so hpvmnet -b -S clan0 to start the switch with -b.
The virtual switch has now been created and started, as verified by the
hpvmnet -v command, and can be used by the virtual machines that Iâ ll create
in upcoming steps.
Support Fatherhood - Stop Family Law