On 26.02.2003 at 09:49:32, Kyle Stewart <[EMAIL PROTECTED]> wrote: > I can\'t even find the ping command on the initrd ipl file system--I get > command not found. Do you have any tips about this?
Eek, cannot help there. I would take this up with your Red Hat support people. Try specifying the path to the file, such as /bin/ping or /sbin/ping, to see if the problem is just that the PATH is not being set. > Thanks for the info > about the subnet. Mine is set up like: OS/390 10.254.36.115 <--> Linux > 10.254.36.117. We use this as a class-a network, i.e. no subnetting. I read this (and your earlier messages) as saying your LAN/WAN uses 10.0.0.0/8 [1], and you are giving the Linux system an IP address in the 10 network. For this to work, you will need to use Proxy ARP on OS/390 TCPIP to reach your Linux system from the LAN/WAN. Does CS/390 provide Proxy ARP? > Should I put my end of the CTC on an entirely different network, e.g. > 192.168.99.99, not on any 10.x.x.x network right? Not critical: it might help you avoid an address conflict on the LAN, but will not help the connection work. Since the subnet mask for p-t-p links is 255.255.255.255, *any* IP address is on a different subnet. Folks used to use a single IP address at the VM end for all (v)CTCs to reduce the number of addresses being used, but as another recent thread tells this can come unstuck in a move to Guest LAN. Kyle, the first thing to do will be to verify whether CS/390 can perform a Proxy ARP function, and work out how to turn it on and configure. If it cannot, you will need to talk to the network people about using a different subnet for the Linux images. Next, decide on the IP address to use at the CS/390 end of the CTC (you can use the same address as the OSA, if you like). If you are using a new subnet for Linuxen, choose an address for the Linux system too. Then, make sure that your TCPIP.PROFILE has the correct HOME and GATEWAY statements to match your chosen config. Of course, your Linux routing config should correspond to CS/390, but that is be the easy part. Make sure that IPCONFIG NOFWD (if that is the exact syntax, might be NODATAGRAMFWD) has *not* been coded in TCPIP.PROFILE, as this would stop CS/390 from routing IP packets. At this point, things should work. If you have changed to a unique subnet for Linux, you will need to have arranged with the network folk for the LAN/WAN to forward IP packets for the Linux subnet via CS/390\'s OSA. This is probably the one thing that a flat IP network makes easy: you can do a test on your PC (add the route to your PCs table) to verify before you get the network guys to make router changes. Of course, you could skip all of the above and make it all easier by sharing the OSA port between the Linux system and OS/390. If this is an OSA-2 you will have to reconfigure it using OSA-SF (to add the LPAR to the OAT), but you would have to do that anyway (adding the Linux IP address to the OS/390 LPAR in the OAT) unless your OS/390 system is primary-router desigated. Hope this is helpful (and not *too* verbose) Cheers, Vic Cross [1] Sorry, Alan A., but I would not be able to tell if 10/8 was a Class A IP network, a date in August, or a really odd music beat ;-)
