Hi: I recommend that you put dummy0 on a different network address not on 192.168.1.x. Also not sure what you are trying to accomplish by putting both vnics on the same guest lan? David Kreuter
________________________________ From: Linux on 390 Port on behalf of Mauro Souza Sent: Thu 10/30/2008 5:55 PM To: LINUX-390@VM.MARIST.EDU Subject: VIPA + OSA + VLAN? Hi people! I am facing some problems setting up a network infraestructure. I had never worked with vlan + vipa before, so... Environment: zVM 5.3 and RHEL4.6. I have to set up two linuxes, and they have direct access to an OSA. We have 2 OSA interfaces, so I defined one interface for each, for the high availability sake. I am not using vswitch, only the direct attached OSA. First, I have defined the LAN: DEFINE LAN INTERNET OWNER SYSTEM TYPE QDIO IP UNRESTRICTED MAXCONN INFINITE Then, in USER DIRECT NICDEF 6000 TYPE QDIO LAN SYSTEM INTERNET NICDEF 7000 TYPE QDIO LAN SYSTEM INTERNET After booting both Linuxes, I configured the VLAN on both: vconfig eth0 add 100 vconfig eth1 add 100 linux1: ifconfig eth0.100 192.168.1.1 ifconfig eth1.100 192.168.1.2 linux2: ifconfig eth0.100 192.168.1.4 ifconfig eth1.100 192.168.1.5 So far, so good. Until here, I am able to ping both interfaces from both Linuxes. So I added VIPA: modprobe dummy linux1: ifconfig dummy0 192.168.1.3 qethconf vipa add 192.168.1.3 eth0 qethconf vipa add 192.168.1.3 eth1 linux2: ifconfig dummy0 192.168.1.6 qethconf vipa add 192.168.1.6 eth0 qethconf vipa add 192.168.1.6 eth1 As soon as I activate the dummy0 interface, a blackout strikes the network. Both linuxes can ping only their own interfaces, and cannot ping each other interfaces. I tried to create a route to VIPA thru the VLAN (e.g. route add -host 192.168.1.3 -dev eth0.100), but no luck. As soon as I destroy the VIPA (qethconf vipa del 192.168.1.6 eth0 ; qethconf vipa del 192.168.1.6 eth1 ; ifdown dummy0 ; rmmod dummy) I can ping again. I am not pretty sure if adding VIPA to eth0 instead of eth0.100 is the right thing to do. I tried to add a vipa to eth0.100, but qethconf complained about an illegal, incorrect and inexistent eth0.100. I am now thinking about changing the interface naming convention to use vlan100 instead of eth0.100... Someone have an advice? Mauro http://mauro.limeiratem.com - registered Linux User: 294521 Scripture is both history, and a love letter from God. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
