On Tuesday, 10/28/2003 at 10:56 EST, Steve Gentry <[EMAIL PROTECTED]> wrote: > I was able to load a more current version of the RH kernel, etc. and > displays and response look much better. qeth/qdio appears to be in this > kernel, IFCONFIG diplays eth0 with the data I entered, but I still can't > get to the Linux guest. Admittedly, networking isn't my strong suit. I've > talked to the network guys and they have helped me as much as they can. We > both are confused by some of the terminology. I need define my network > environ a little more and all of this is behind a firewall. We have a > z800 with two osa express cards, therefore a total of 4 ports. Port > 0(card 1) has 10.140.1.22 as it's ip addr Port 0(card 2) has 10.140.1.24. > When we first installed the box I tried to put both of these on card 1, > port 0 and port 1 respectively.
Terminology: Both ports on a single OSA Express card are port 0 because there are actually two OSA devices (chpids) in each card, each with a single port (0). There is an OSA-2 (old style) combo ethernet/token ring card that has two ports on a single chpid that required you to worry about port 0 and 1. A real, live drawing of the network you are trying to build is always the best place to start. Seeing it in picture form clarifies what you are trying to do and will lead you to the Right Answer. > I never could get it to work. Well come > to find out and I may have the terminology wrong, you can't have two ip > addrs with the same subnet on the same card. Yes, you can. > When I moved 10.140.1.24 to > card 2, port 0, my original network started to work. Right or wrong it is > working. However, if it is wrong, please tell me as I don't want to run > into problems later on. I suspect issues in the switch or cabling. > To continue, I read some where that Linux should or must be installed in > it's own subnet. I seem to remember this from the early days but had > forgotten it. Is this still true? Thus the ip addr of 10.140.2.x If you are connecting Linux to a guest LAN on z/VM, then yes it needs to be in its own subnet (unless you're using z/VM 4.4. virtual switch). If you are giving real OSA subchannels to the Linux guest, then it must have IP addresses in the real LAN subnet. > Back to the linux config: I've listed below the prompts during network > config when I start linux. > Enter the IP address of you new Linux guest: 10.140.2.40 (No problem with this > one) Wrong subnet, I think, based on above. > Enter the network address of the new Linux guest: 10.140.2.0 (I'm not 100% > sure of this answer, from looking at countless examples, the > 4th > octet > should be 0(zero).) Correct. But you can just press ENTER on this question and it will select the right value based on netmask. > Enter the netmask of the new Linux guest: 255.255.255.0 (No problem with this > one) > Enter teh broadcast address for the new Linux guest: 10.140.2.255 (Not 100% > about this one either, most examples code it this way i.e., the > 4th > octet is 255) Correct. Again, ENTER will give you a good default. > Enter the default gateway: 10.140.2.254 (This is where I get confused. a) > should it be 255 instead of 254? If so, > is the reply to the previous question > wrong? or b) does it mean the > default gateway for the rest of my network. In this case it would be > 10.140.1.254 (but the 254/255 > question still lingers). It is the IP address of the router on the 10.140.2 subnet. But based on the above discussion, you don't really have a .2 subnet, so there is no router. If you had assigned an IP address to Linux in the .1 subnet, then the 10.140.1.254 is the correct answer. > Enter your DNS server(s), seperated by colons( : ): 162.133.1.19:162.133.1.22 > (This one isn't clear to me, i.e., does it want the DNS server name or > the ip addr. I assume ip addr(s). It doesn't fuss about it. However, > I've never entered the DNS server name(s)). IP addresses. If you specified names, it couldn't resolve them into IP addresses without knowing where the DNS servers are! > Enter your DNS search domain(s) (if any), seperated by colons ( : ): > vm.llic.com (I'm not sure about this one either, however it has to be one of > two replies (for us) vm.llic.com or llic.com. I have tried llic.com and it > doesn't seem to make a difference) This is just the list of domain names Linux will append to any host name you use if you don't provide one. Eg. "foohost" will be treated as "foohost.vm.llic.com", but "barhost.ibm.com" will not be affected. You're right, though, it won't have any affect on connectivity. Alan Altmark Sr. Software Engineer IBM z/VM Development
