Mark Perry wrote: > Mauro Souza wrote: >> 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? >> > Hi Mario, > rather than just giving up on this and switch to a vswitch solution as > suggested by others (what happens if you want to run the guest in a > native LPAR later for example?) > > Check the routing tables before and after adding the VIPA(s): > > ip route show > > mark > Also 1) You are not directly using an OSA, you are accessing a (closed) z/VM GuestLAN 2) Syntax: vconfig add eth0 100
mark ---------------------------------------------------------------------- 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
