I am attempting to setup a Guest Lan on zVM 4.3 on a z800. I have one Linux
machine, lnxrtr1, up and running with a CTC connection to the zVM TCPIP
virtual machine. My goal is to have the lnxrtr1 linux machine act be a
router for my Guest Lan. I am now trying to get lnxrtr1 to communicate to
the Guest Lan. I have defined the LAN as follows:
cp q lan qdiolan2 details
LAN SYSTEM QDIOLAN2 Type: QDIO Active: 1 MAXCONN: INFINITE
PERSISTENT RESTRICTED MFS: 8192 ACCOUNTING: OFF
Authorized userids:
LNXRTR1 SYSTEM
Adapter Owner: LNXRTR1 NIC: 7000 Name: BEARS
Ready; T=0.01/0.01 17:34:01
In lnxrtr1, I have defined the NIC and have coupled it to the LAN, as shown
with the following query commands:
CP Q NIC DETAILS
Adapter 7000 Type: QDIO Name: BEARS Devices: 3
Port 0 MAC: 00-04-AC-00-00-00 LAN: SYSTEM QDIOLAN2 MFS: 8192
RX Packets: 0 Discarded: 0 Errors: 0
TX Packets: 0 Discarded: 0 Errors: 0
RX Bytes: 0 TX Bytes: 0
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
CP Q V 7000
OSA 7000 ON NIC 7000 UNIT 000 SUBCHANNEL = 0015
7000 QDIO-ELIGIBLE
Now the linux setup information:
My /etc/chandev.conf file in lnxrtr1 contains the following:
ctc0,0x7100,0x7101
add_parms 0x10,0x7000,0x7002,portname:BEARS
qeth1,0x7000,0x7001,0x7002
My /etc/modules.conf file in lnxrtr1 contains the following:
#
alias eth0 lcs
#alias eth1 off
alias eth1 qeth
alias tr0 off
I load qdio and qeth as shown below:
lnxrtr1:~ # insmod qdio
Using /lib/modules/2.4.17/kernel/drivers/s390/net/qdio.o
lnxrtr1:~ # insmod qeth
Using /lib/modules/2.4.17/kernel/drivers/s390/net/qeth.o
lnxrtr1:~ # lsmod
Module Size Used by
qeth 138992 0 (unused)
qdio 40128 1 [qeth]
ipv6 249664 -1 (autoclean)
ctc 53808 1 (autoclean)
fsm 1984 0 (autoclean) [ctc]
lvm-mod 47280 0 (autoclean)
My current ip settings:
lnxrtr1:~ # ifconfig
ctc0 Link encap:Serial Line IP
inet addr:147.185.179.2 P-t-P:147.185.2.158 Mask:255.255.255.128
UP POINTOPOINT RUNNING NOARP MTU:8992 Metric:1
RX packets:465 errors:0 dropped:0 overruns:0 frame:0
TX packets:422 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:53351 (52.1 Kb) TX bytes:53154 (51.9 Kb)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 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
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
When I define the IP configuration for the eth1 with the following command,
I lose all IP connectivity and there are no messages in the TN3270 window.
lnxrtr1:~ # ifconfig eth1 147.185.179.65
>From the TC3270 window I can run ifconfig and get the following:
ifconfig
ctc0 Link encap:Serial Line IP
inet addr:147.185.179.2 P-t-P:147.185.2.158 Mask:255.255.255.128
UP POINTOPOINT RUNNING NOARP MTU:8992 Metric:1
RX packets:1438 errors:0 dropped:0 overruns:0 frame:0
TX packets:1413 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:162163 (158.3 Kb) TX bytes:245515 (239.7 Kb)
eth1 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:147.185.179.65 Mask:255.255.0.0
inet6 addr: fe80::200:ff:fe00:0/10 Scope:Link
UP RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:51 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:14376 (14.0 Kb)
Interrupt:21
If I bring eth1 down from the TN3270 window I can logon on with putty.
I have used presentations from Share, presentations from IBM's zVM/zOS
Technical Conference, IBM's Large Scale Linux Deployment Redbook and the
Device Drivers and Installation Commands Manual as reference in this effort.
If anyone can see what I did wrong please let me know, I have been fighing
this for days. Your help is greatly appreciated. I apologize for the length
of this email.
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 forward, copy, print, 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
**********************************************************************
