Still having problems seeing posts so sorry about the cut'n paste here.
>The setup looks good from what I can see. _Something_ is going in and >out of that interface (about 20 packets worth). Is the TCPIP Service >Virtual Machine the default gateway at 155.180.147.33? Can you ping >that? >From the linux server I'm installing I can not ping 155.180.147.33 >and can ping it from other guests running sles8 currently it is defined this way DEVICE OSAVM1 OSD 0FA0 PORTNAME OSAG0C5 PRIROUTER AUTORESTART LINK ETH1 QDIOETHERNET OSAVM1 DEVICE OSAVM2 OSD 0FD0 PORTNAME OSAG0CD PRIROUTER AUTORESTART LINK ETH2 QDIOETHERNET OSAVM2 DEVICE VMGLAN OSD 5000 PORTNAME GUESTLAN AUTORESTART LINK ETH3 QDIOETHERNET VMGLAN HOME 10.238.192.110 ETH1 10.238.192.238 ETH2 155.180.147.33 ETH3 then we use OSPF so MPROUTE is configured >What are the IP addresses of the other systems on the GuestLAN? At the time of these tests the following servers where up and are reachable via IP 155.180.147.36 cohzlnx01 test 1 server 155.180.147.37 cohzlnx02 test 2 server 155.180.147.39 cohzlnx04 NFS Server The server in question is reachable after IPL'ing from the RDR and entering the IP info for it, after completing the YAST setup,this is the one unreachable via IP 155.180.147.41 cohzlnx06 one being installed. >Does "arp -an" show anything after a "ping -c 3 -b 155.180.147.47" ? cohzlnx06:~ # ping -c 3 -b 155.180.147.47 ping -c 3 -b 155.180.147.47 WARNING: pinging broadcast address PING 155.180.147.47 (155.180.147.47) 56(84) bytes of data. --- 155.180.147.47 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2015ms cohzlnx06:~ # arp -an arp -an cohzlnx06:~ # William 'Doug' Carroll Mainframe Systems Engineer II Global Technology Infrastructure (614) 213-4954 Office (877) 899-1697 Pager (614) 244-9897 Fax http://www.bankone.com "Post, Mark K" <[EMAIL PROTECTED] To: [email protected] m> cc: Sent by: Linux on Subject: Re: Can't Access YAST to complete install 390 Port <[EMAIL PROTECTED] ist.edu> 08/15/2005 11:11 PM Please respond to Linux on 390 Port Ok, if you've figured out how to be able to issue ping commands, then the following commands will be of interest: #cp q nic details #cp q lan details ifconfig -a route -n lsmod Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Doug Carroll Sent: Monday, August 15, 2005 5:17 PM To: [email protected] Subject: Re: Can't Access YAST to complete install Sorry, I'm not seeing post on my topic at all, just checked the archives and saw some replies. for some of the questions, the SLES9 host is on the same subnet as my SLES8 hosts and I can not ping in either direction. SLES8 and SLES8 are both on the same guestlan. i.e. SLES8 can not ping SLES9 host and visa-versa I can not ping the Gateway either from the SLES9 host I can ping the SLES9s own IP from SLES9 the /28 is the correct subnet for the host i have tried re-ipling the SLES9 server and it goes through skipping the customization steps it is still unreachable William 'Doug' Carroll Mainframe Systems Engineer II Global Technology Infrastructure (614) 213-4954 Office (877) 899-1697 Pager (614) 244-9897 Fax http://www.bankone.com ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
