Tom, >From what I can tell, your routing looks right. The ifconfig output is really strange, though: RX packets:882347 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
_Something_ is sending you lots of packets, but nothing is going the other way. Just out of curiosity, have you tried downloading the latest OCO modules for the OSA card that match your kernel level, and see if they act any differently? (I know they've opened up the source code for them, but I don't want you to have to rebuild your kernel just to poke at this problem.) Also, pinging the local IP address from Linux doesn't show anything, really. The interface doesn't even get exercised by that, so unless it _fails_, it means very little. You've tried pinging the gateway router by it's IP address? Does that change the "TX packets" numbers on the ifconfig command any? Mark Post -----Original Message----- From: Geyer, Thomas L. [mailto:[EMAIL PROTECTED]] Sent: Monday, March 18, 2002 11:01 AM To: [EMAIL PROTECTED] Subject: FW: Problem with OSA/2 Adapter Mark is was a pleasure meeting you as well. I do hope to be able to attend Share again in the future. The address of the first router pass the OSA card is 147.185.2.1. The following is the output from the "route -n" command. route -n route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 147.185.2.47 0.0.0.0 255.255.255.255 UH 0 0 0 eth0 147.185.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 147.185.2.1 0.0.0.0 UG 0 0 0 eth0 Here is the output from the ifconfig command: ifconfig eth0 Link encap:Ethernet HWaddr 00:04:AC:5E:E0:D5 inet addr:147.185.2.47 Bcast:147.185.2.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:882347 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:3924 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 We tried pinging from the gateway 147.185.2.1 and it failed. I tried the following from the linux virtual machine: [root@vmlinux /root]# ping -c 3 147.185.2.47 ping -c 3 147.185.2.47 PING 147.185.2.47 (147.185.2.47): 56 data bytes 64 bytes from 147.185.2.47: icmp_seq=0 ttl=255 time=0.2 ms 64 bytes from 147.185.2.47: icmp_seq=1 ttl=255 time=0.1 ms 64 bytes from 147.185.2.47: icmp_seq=2 ttl=255 time=0.2 ms --- 147.185.2.47 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.1/0.1/0.2 ms [root@vmlinux /root]# Any suggestions or help is greatly appreciated. Thanks. Thomas L. Geyer Email:[EMAIL PROTECTED] Phone:(330) 471-2073 Fax:(330) 471-4034 -----Original Message----- From: Post, Mark K [mailto:[EMAIL PROTECTED]] Sent: Friday, March 15, 2002 1:29 PM Subject: Re: Problem wit OSA/2 Adapter Tom, It was nice meeting you at SHARE. I hope you get to come back and bring others from Timken with you. What does your routing table look like when you're attempting the pings? For that matter, what is the IP address of your OSA, and the first router past the OSA card? Post the output from "route -n" and "ifconfig" so that we can help you out. Mark Post -----Original Message----- From: Geyer, Thomas L. [mailto:[EMAIL PROTECTED]] Sent: Friday, March 15, 2002 11:18 AM To: [EMAIL PROTECTED] Subject: Problem wit OSA/2 Adapter I attended Share last week and I followed the Linux/390 track. I want to thank all of you who presented, all presentations were excellent and very informative. Share was especially "special" since I got to spend time with an old friend, Scott Courtney. Scott you and your talents are missed and it was great seeing you again. Now to my question. Since I returned from Share I have been trying to install the Marist distribution on our VM processor. I attended the installation workshop at Share, which was fantastic, but in the workshop we used IUCV for the TCP/IP. In fact from Nashville I had started the installation and had gotten to the point of needing to ftp the Linux filesystem tar file into the Linux virtual machine, but I did not have a TCP/IP connection for my virtual machine. When I returned to work I approached our VM system programmer and he tells me I should be using the OSA Adapter. Well being a Unix Systems Administrator this was foreign to me. So I started looking for information on doing the install with the OSA adapter. I have downloaded the LCS manual and Linux/390 Installation Guide from the Marist website. I have reviewed the Linux-390 list archives and have used Alan Altmark's handouts form his "Connecting to Linux for S/390" presentation. Currently I am able to punch the kernel, parm file, and ram disk file to the reader and ipl giving me Linux with a ram disk. I respond "yes" to the network question, I select 2 for OSA Ethernet, and pass the following lcs parameters: noauto=1 devno_portno_pairs=0x5002,0 I then respond to the remaining questions as I would for any other host on the same subnet. The messages that follow all respond with a "OK". I did have an error that stated the resource was busy, that went away when I used 0x5002,0 instead of 0x5002,1. the Dedicate statement in the virtual machine definition is: DEDICATE 5002 5002 DEDICATE 5003 5003 When I try to ping the Linux virtual machine using the IP address the request times out. When I run the ifconfig command in the Linux virtual machine I see that the RX packets continue to increase while the TX packets remain very close to zero for "eth0" Any help and/or suggestions would be greatly appreciated. Thomas L. Geyer Email:[EMAIL PROTECTED] Phone:(330) 471-2073 Fax:(330) 471-4034 ********************************************************************** This message and any attachments are intended for the individual or entity named above. If you are not the intended recipient, please do not read, copy, use or disclose this communication to others; also please notify the sender by replying to this message, and then delete it from your system. The Timken Company **********************************************************************
