>>> On 2/2/2015 at 02:00 PM, Steve P <[email protected]> wrote: > So I've tried to Ping the Lpar IP from the hmc under Network Diagnostics to > see if the lpar is communicating at all through the hmc. But it fails. So I > wonder if the failure is because of the the network connection. > > Any thoughts?
If you get into a shell 1. Do you see the network interface? (ip link show) 2. If you have a network interface, does it have an IP address? (ip addr show) 2a. Does it have the right network mask? (ip addr show) 3. If you have an IP address, is the default gateway set? (ip route show) 4. Can you ping the default gateway? (ping -c 3 ip.addr.of.gateway) If all those are OK and you can ping your gateway, then the problem is somewhere beyond the gateway. Only your network people can help you at that point. Also, note that the LPAR does _not_ "communicate through the HMC." The traffic from the OSA adapter you're using goes out through whatever switches and routes your network team has hooked up, and then to the (usually well isolated) NIC on the HMC. As I said, all that part of the network is outside of your control, so it might be a good idea to see if you can access another FTP/HTTP/SMB/NFS server somewhere else on the network. We have had at least one report of someone using the z/OS FTP server to install Linux in an LPAR. Not necessarily a lot of fun, but it's another possible avenue. Mark Post ---------------------------------------------------------------------- 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 more information on Linux on System z, visit http://wiki.linuxvm.org/
