Brian,
I'll pass on this feedback from Vic Cross from a question I posted in
December:
+++
Dave, if your z/VM is 4.3 and you are using the so-called QDIO Guest LAN
(DEFINE LAN xxx QDIO), you will define your connection to the LAN as if it
was an OSA-Express. If your using z/VM 4.2, or you have defined a
HiperSockets Guest LAN on z/VM 4.3 (DEFINE LAN xxx HIPER), the option you
will use is the one James mentioned.
Regardless, the installation system contains the required drivers. It is
when installing Red Hat that special action needs to be taken to include
the qeth.o driver.
+++ (end of VC's comments)
I think for this to work, you'd have to configure VM's MPROUTE ahead
of time to provide the proper routing to whatever lan subnet you'll be
running the putty/yast portion of the install from?? Is that true route
gurus out there?
If you're using OSA you could also share the OSA port between VM and the
linux ram system.
I did this with OSA/EXPRESS today for an SLES8 install under zVM 4.3 and it
came up fine.
Just use 3 other device numbers for the OSA and same portname as the one
defined in VM's IP stack.
Feel free to email me if you run into quirks with the SLES8 install.
The SLES8 doc didn't exactly match the process :o)
Make sure to read the readme file on CD1.
Dave Myers
Denver Solutions Group
Senior Systems Engineer
Office Phone:�� (303) 996-7112
Cellular Phone: (303) 619-0782
Fax:���������������� �(303) 706.1713
e-mail: [EMAIL PROTECTED]
"Jones, Brian P"
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
ORTEK.COM> cc:
Sent by: Linux on 390 Subject: Hipersockets SLES8
Port
<[EMAIL PROTECTED]
DU>
01/15/2003 04:20 PM
Please respond to
Linux on 390 Port
> 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
>
