Hi Brian, I think your interface drivers are configured properly. You have defined a HiperSockets NIC and you are using the "hsi0" interface. HiperSockets does not require a portname, and does not care if you provide one, so don't worry about that part.
Your IP address is visible on the LAN (your QUERY LAN command shows that it is associated with your Linux user's connection). > LAN SYSTEM VMSNAPV Type: HIPERS Active: 2 MAXCONN: INFINITE > PERSISTENT UNRESTRICTED MFS: 16384 > Adapter Owner: TCPIP NIC: 0D20 Name: VMPORT3 > 129.80.16.54 129.80.45.128 129.80.45.193 > 129.80.45.225 > Adapter Owner: TMP04LNX NIC: 7000 Name: UNASSIGNED > 129.80.45.226 It appears that you have sent 9 packets from 129.80.45.226 (with 0 responses). > ifconfig > hsi0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > inet addr:129.80.45.226 Mask:255.255.255.224 > inet6 addr: fe80::200:ff:fe00:0/10 Scope:Link > UP RUNNING NOARP MTU:8192 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:9 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:100 > RX bytes:0 (0.0 b) TX bytes:792 (792.0 b) > Interrupt:25 I don't know why TCPIP is not responding, but both interfaces look valid, so if you 'ping 129.45.225 -c 1' from your linux user, it should be delivered to the TCPIP user. I know of two easy ways this can fail on the way back: (1) TCPIP has another gateway definition that sends this IP address out a different interface. (2) TCPIP thinks this datagram has to go through an intermediate node with a different IP address (this may send it into the right LAN segment but with the wrong next-hop address which makes it invisible to your Linux connection). Regards, Dennis Musselwhite ([EMAIL PROTECTED]) IBM Corporation -- z/VM Development -- CP Network Simulation "Jones, Brian P" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 01/15/2003 06:20:25 PM Please respond to Linux on 390 Port <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: [LINUX-390] Hipersockets SLES8 > Hi > I have been attempting to install SLES8, for s/390 using hipersockets > support to a guest LAN and can't get the network to work. I have tried > beta-6 and rc-6. I can never get the gateway address to ping, resulting > in an install failure. I have the same problem when I try and > ifconfig an installed system. Is there any known problems with the > hipersockets support? > You will see that I did not have a portname defined on the Linux side, but > I have tried adding a portname on a (non-starter) system, also to no avail. > > Here is my Linux config: > ifconfig > hsi0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > inet addr:129.80.45.226 Mask:255.255.255.224 > inet6 addr: fe80::200:ff:fe00:0/10 Scope:Link > UP RUNNING NOARP MTU:8192 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:9 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:100 > RX bytes:0 (0.0 b) TX bytes:792 (792.0 b) > Interrupt:25 > #*#: route > route > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use > Iface > 129.80.45.224 * 255.255.255.224 U 0 0 0 > hsi0 > default 129.80.45.225 0.0.0.0 UG 0 0 0 > hsi0 > #*#: > > Here is my VM config: > LAN SYSTEM VMSNAPV Type: HIPERS Active: 2 MAXCONN: INFINITE > PERSISTENT UNRESTRICTED MFS: 16384 > Adapter Owner: TCPIP NIC: 0D20 Name: VMPORT3 > 129.80.16.54 129.80.45.128 129.80.45.193 > 129.80.45.225 > Adapter Owner: TMP04LNX NIC: 7000 Name: UNASSIGNED > 129.80.45.226 > > CP Q NIC DETAILS > Adapter 7000 Type: HIPER Name: UNASSIGNED Devices: 3 > Port 0 MAC: 00-04-AC-00-00-11 LAN: SYSTEM VMSNAPV MFS: 16384 > Connection Name: HALLOLE State: Session Established > Device: 7000 Unit: 000 Role: CTL-READ > Device: 7001 Unit: 001 Role: CTL-WRITE > Device: 7002 Unit: 002 Role: DATA > Unicast IP Addresses: > 129.80.45.226 > > NETSTAT HOME: > 129.80.45.225 VM1VLAN3 > > > NETSTAT GATE: > 129.80.0.0 <direct> US 1500 0.0.255.224 0.0.45.224 > VM1VLAN3 > > > > Thanks, > Brian Jones > (303) 661-4626 phone > StorageTek > INFORMATION made POWERFUL >
