Hello all, hope you can help me out.

I am having issues getting the Scenario #2 to work, as described in SG24-7722. I will eventually work my way up to scenario #4, but this is where I am stuck.

This is the devmap:

devmap config

Here are some various linux outputs:

# ifconfig

eth0      Link encap:Ethernet  HWaddr BC:AE:C5:8D:76:F1 inet addr:10.7.32.7  Bcast:10.7.32.255  Mask:255.255.255.0 UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1 RX packets:403656 errors:0 dropped:3899 overruns:0 frame:0 TX packets:21458 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:54639565 (52.1 Mb)  TX bytes:3667057 (3.4 Mb) Interrupt:43 Base address:0x4000   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:33178 errors:0 dropped:0 overruns:0 frame:0 TX packets:33178 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:9089568 (8.6 Mb)  TX bytes:9089568 (8.6 Mb)   tap0      Link encap:Ethernet  HWaddr A2:2E:86:02:7E:10 inet addr:10.1.1.1  Bcast:10.1.1.255  Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1 RX packets:14 errors:0 dropped:0 overruns:0 frame:0 TX packets:52 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:840 (840.0 b)  TX bytes:6390 (6.2 Kb)

# route -n

Kernel IP routing table Destination     Gateway         Genmask         Flags Metric Ref    Use Iface 10.7.32.0       0.0.0.0         255.255.255.0   U     0      0        0 eth0 10.1.1.0        0.0.0.0         255.255.255.0   U     0      0        0 tap0 169.254.0.0     0.0.0.0         255.255.0.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         10.7.32.254     0.0.0.0         UG    0      0        0 eth0

And here are some various tso outputs:

tso netstat home

EZZ2350I MVS TCP/IP NETSTAT CS V1R11       TCPIP Name: TCPIP           22:11:49 EZZ2700I Home address list: EZZ2701I Address          Link             Flg EZZ2702I -------          ----             --- EZZ2703I 10.1.1.2         ETH1             P EZZ2703I 127.0.0.1        LOOPBACK

tso netstat route

EZZ2350I MVS TCP/IP NETSTAT CS V1R11       TCPIP Name: TCPIP           22:13:3 EZZ2755I Destination        Gateway         Flags    Refcnt     Interface EZZ2756I -----------        -------         -----    ------     --------- EZZ2757I 10.1.1.2/32        0.0.0.0         UH       0000000000 ETH1 EZZ2757I 127.0.0.1/32       0.0.0.0         UH       0000000000 LOOPBACK

This a snippet of my TCPPARMS(PROFILE)

... DEVICE PORTA  MPCIPA LINK ETH1  IPAQENET PORTA HOME 10.1.1.2  ETH1 BEGINRoutes ;     Destination   SubnetMask    FirstHop       LinkName  Size ROUTE 10.0.0.0      255.0.0.0            =       ETH1 MTU  1492 ROUTE DEFAULT                     10.1.1.1       ETH1 MTU  1492 ENDRoutes ...

It appears that the ROUTE DEFAULT statements are not getting executed for some reason, as I don't see any indication of that route showing up at run-time.

Any clues as to what I need to be doing here?

Vance,

Any luck yet?
How did you implement (or in the Scenario 2 case) not implement the TRL

ADCD.Z111.VTAMLST(OSATRL1)
000100 OSATRL1 VBUILD TYPE=TRL
000200 OSATRL1E TRLE LNCTL=MPC,READ=(0400),WRITE=(0401),DATAPATH=(0402), X
000300 PORTNAME=ADM1ETP, X
000400 MPCLEVEL=QDIO

In other words - you should not have made any changes to OSATRL1

Jay

Hi Jay, thanks for the assistance. Just so you know, I am very green with all things IBM. :)

I have moved on to the scenario #4 and altered some statements in my TCPIP profile in attempt to get the default routes to show up, but nothing seems to be working out for me. I thought that the problem was that both the tunnel address and the external network were on 10.x addresses, but changing them has not helped.

The configuration I am currently working with is as follows:

devmap

... [manager]          # define network adapter (OSA) for communication with host linux name awsosa 22 --path=A0 --pathtype=OSD --tunnel_intf=y --tunnel_ip=192.168.1.1 --tunnel_mask=255.255.255.0 device 400 osa osa device 401 osa osa device 402 osa osa   [manager]          # define network adapter (OSA) for communication over the network name awsosa 24 --path=F0 --pathtype=OSD device 404 osa osa device 405 osa osa device 406 osa osa ...

VTAMLST(ATCCON00)

A0600,NSNAFXX,NSNA70X,NSNA90X,DYNMODEL,XCAE40R,XCAE40E,COSAPPN,        * A0TCP,DB8GLU,OSATRL2,IMS10APL,DB9GLU,CICSAPPL

VTAMLST(OSATRL2)

OSATRL1 VBUILD TYPE=TRL OSATRL1E TRLE LNCTL=MPC,READ=(0400),WRITE=(0401),DATAPATH=(0402), PORTNAME=PORTA, MPCLEVEL=QDIO OSTARL2E TRLE LNCTL=MPC,READ=(0404),WRITE=(0405),DATAPATH=(0406), PORTNAME=PORTB, MPCLEVEL=QDIO

TCPPARMS(PROFILE)

... DEVICE PORTA  MPCIPA LINK ETH1 IPAQENET PORTA HOME 192.168.1.2 ETH1 ; This second device is for public, external connectivity DEVICE PORTB  MPCIPA LINK ETH2 IPAQENET PORTB HOME 10.7.32.11 ETH2 BEGINROUTES ROUTE 192.168.1.1/32     =       ETH1 MTU 1492 ROUTE 10.7.32.254/32     =       ETH2 MTU 1492 ROUTE 192.168.1.0/32 192.168.1.1 ETH1 MTU 1492 ROUTE 10.7.32.0/32   10.7.32.254 ETH2 MTU 1492 ENDROUTES ...

The following is various outputs

TSO NETSTAT HOME

EZZ2350I MVS TCP/IP NETSTAT CS V1R11       TCPIP Name: TCPIP           17:53:56 EZZ2700I Home address list: EZZ2701I Address          Link             Flg EZZ2702I -------          ----             --- EZZ2703I 192.168.1.2      ETH1             P EZZ2703I 10.7.32.11       ETH2 EZZ2703I 127.0.0.1        LOOPBACK

TSO NETSTAT ROUTE

EZZ2350I MVS TCP/IP NETSTAT CS V1R11       TCPIP Name: TCPIP           17:55:21 EZZ2755I Destination        Gateway         Flags    Refcnt     Interface EZZ2756I -----------        -------         -----    ------     --------- EZZ2757I 10.7.32.11/32      0.0.0.0         H        0000000000 ETH2 EZZ2757I 127.0.0.1/32       0.0.0.0         UH       0000000000 LOOPBACK EZZ2757I 192.168.1.2/32     0.0.0.0         H        0000000000 ETH1

.. and in linux

ifconfig

eth0      Link encap:Ethernet  HWaddr BC:AE:C5:8D:76:F1 inet addr:10.7.32.7  Bcast:10.7.32.255  Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1 RX packets:1404385 errors:0 dropped:6379 overruns:0 frame:0 TX packets:50694 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:166299209 (158.5 Mb)  TX bytes:11435467 (10.9 Mb) Interrupt:43 Base address:0x4000   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:103617 errors:0 dropped:0 overruns:0 frame:0 TX packets:103617 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:23805196 (22.7 Mb)  TX bytes:23805196 (22.7 Mb)   tap0      Link encap:Ethernet  HWaddr 0A:D0:B3:AF:C9:1E inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:22 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:0 (0.0 b)  TX bytes:4377 (4.2 Kb)

route -n

Kernel IP routing table Destination     Gateway         Genmask         Flags Metric Ref    Use Iface 10.7.32.0       0.0.0.0         255.255.255.0   U     0      0        0 eth0 192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 tap0 169.254.0.0     0.0.0.0         255.255.0.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         10.7.32.254     0.0.0.0         UG    0      0        0 eth0

There is definitely a syntax error in my TCPIP profile configuration. From MVS, when I issue P TCPIP and then S TCPIP, the system responds with many errors. Unfortunately I cannot see the beginning of the list because it scrolls by too fast, but this is the portion that I can see:

... AT: 'ENDROUTES' 12.04.06 STC00040  EZZ0401I SYNTAX ERROR IN FILE: DD:PROFILE ON LINE: 105 AT: '01060001' 12.04.06 STC00040  EZZ0324I UNRECOGNIZED STATEMENT 01060001 FOUND ON LINE 105 12.04.06 STC00040  EZZ0324I UNRECOGNIZED STATEMENT 01070001 FOUND ON LINE 106 12.04.06 STC00040  EZZ0324I UNRECOGNIZED STATEMENT 01080001 FOUND ON LINE 107 12.04.06 STC00040  EZZ0324I UNRECOGNIZED STATEMENT 01090001 FOUND ON LINE 108 12.04.06 STC00040  EZZ0324I UNRECOGNIZED STATEMENT 01100001 FOUND ON LINE 109 12.04.06 STC00040  EZZ0324I UNRECOGNIZED STATEMENT 01110009 FOUND ON LINE 110 12.04.06 STC00040  EZZ0316I PROFILE PROCESSING COMPLETE FOR FILE DD:PROFILE 12.04.06 STC00040  EZZ0303I INITIAL PROFILE FILE CONTAINS ERRORS 12.04.06 STC00040  EZZ0334I IP FORWARDING IS DISABLED ...

Here is the entire configuration file, maybe you can help me spot the error. And how do I pause the MVS output? I really would like to see exactly what's going on there ;)

USER.TCPPARMS(PROFILE)

000100 ARPAGE 5 000200 DATASETPREFIX TCPIP 000300 AUTOLOG 5 000400     FTPD JOBNAME FTPD1   ; FTP Server 000500     PORTMAP              ; Portmap Server 000600 ENDAUTOLOG 000700 PORT 000800      7 UDP MISCSERV            ; Miscellaneous Server 000900      7 TCP MISCSERV 001000      9 UDP MISCSERV 001100      9 TCP MISCSERV 001200     19 UDP MISCSERV 001300     19 TCP MISCSERV 001400     20 TCP OMVS      NOAUTOLOG ; FTP Server 001500     21 TCP OMVS                ; FTP Server 001600     23 TCP TN3270              ; Telnet Server 001700     25 TCP SMTP                ; SMTP Server 001800     53 TCP NAMESRV             ; Domain Name Server 001900     53 UDP NAMESRV             ; Domain Name Server 002000     69 UDP OMVS                ; OE TFTP SERVER 002100     80 TCP OMVS                ; OE WEB SERVER 002200    111 TCP PORTMAP             ; Portmap Server 002300    111 UDP PORTMAP             ; Portmap Server 002400    135 UDP LLBD                ; NCS Location Broker 002500    161 UDP OSNMPD              ; SNMP Agent 002600    162 UDP SNMPQE              ; SNMP Query Engine 002700    433 TCP OMVS                ; OE WEB Server 002800    443 TCP OMVS                ; Secure Server 002900    512 TCP RXSERVE             ; Remote Execution Server 003000    513 UDP OMVS                ; OE RLOGIN SERVER 003100    514 UDP OMVS                ; OE syslog server 003200    514 TCP RXSERVE             ; Remote Execution Server 003300    515 TCP LPSERVE             ; LPD Server 003400    520 UDP OROUTED             ; RouteD Server 003500    580 UDP NCPROUT             ; NCPROUTE Server 003600    750 TCP MVSKERB             ; Kerberos 003700    750 UDP MVSKERB             ; Kerberos 003800    751 TCP ADM@SRV             ; Kerberos Admin Server 003900    751 UDP ADM@SRV             ; Kerberos Admin Server 004000 ;  1021 TCP OMVS                ; OE FTP SERVER 004100    1023 TCP OMVS                ; OE TELNET SERVER 004200    1023 UDP OMVS ; OE TELNET SERVER 004300    1024 TCP OMVS                ; OE SERVICES 004400    1415 TCP CSQ1CHIN            ; CSQ1 MQ TCP Listener 004500    3000 TCP CICSTCP             ; CICS Socket 004600    32200 TCP BBN7ACRS             ; Daemon IP port 004700    32201 TCP BBN7ACRS NODELAYACKS ; Daemon SSL port 004800    32202 TCP BBNS001            ; SOAP JMX Connector port 004900    32203 TCP BBNS001            ; ORB port 005000    32204 TCP BBNS001 NODELAYACKS ; ORB SSL port 005100    32205 TCP BBNS001             ; Administrative console port 005200    32206 TCP BBNS001 NODELAYACKS ; Administrative console secure port 005300    32207 TCP BBNS001             ; HTTP transport port 005400    32208 TCP BBNS001 NODELAYACKS ; HTTPS transport port 005500    32209 TCP BBNS001             ; Administrative Local Port 005600    32210 TCP BBNS001             ; High availability manager comm port 005700    32211 TCP BBNS001             ; Service Integration port 005800    32212 TCP BBNS001 NODELAYACKS ; Service Integration secure port 005900    32213 TCP BBNS001S            ; Service Integration MQ interoper 006000    32214 TCP BBNS001S NODELAYACKS ; Service Integration MQ inter secure 006100    32215 TCP BBNS001            ; Session Initiation Protocol (SIP) 006200    32216 TCP BBNS001 NODELAYACKS ; Session Init Protocol (SIP) secure 006300    8879 TCP BBODMGR             ; SOAP JMX Connector port 006400    7277 TCP BBODMGR             ; Cell Discovery port 006500    9809 TCP BBODMGR             ; ORB port 006600    9090 TCP BBODMGR             ; HTTP port 006700    9043 TCP BBODMGR             ; HTTPS port 006800    5755 TCP BBODMNC             ; Daemon port 006900    5756 TCP BBODMNC             ; Daemon SSL port 007000 ; WAS Base Node entries 007100   8880 TCP BBOS001             ; SOAP JMX Connector port 007200 ; 2809 TCP BBOS001             ; ORB port (COMMENT THIS ONE OUT) 007300   9080 TCP BBOS001             ; HTTP port 007400   9443 TCP BBOS001             ; HTTPS port 007500   5655 TCP BBODMNB             ; Daemon port 007600   5656 TCP BBODMNB             ; Daemon SSL port 007700 ; WAS ND Node entries 007800   8879 TCP BBODMGR             ; SOAP JMX Connector port 007900   7277 TCP BBODMGR             ; Cell Discovery port 008000   9809 TCP BBODMGR             ; ORB port 008100   9090 TCP BBODMGR             ; HTTP port 008200   9043 TCP BBODMGR             ; HTTPS port 008300   5755 TCP BBODMNC             ; Daemon port 008400   5756 TCP BBODMNC             ; Daemon SSL port 008500 ; WAS Federation entries 008600   8878 TCP BBON001             ; SOAP JMX Connector port 008700   7272 TCP BBON001             ; Node Discovery port 008800   2809 TCP BBON001             ; Node Agent s ORB port 008900   9810 TCP BBOS001             ; Base Server s ORB port 009000 SACONFIG DISABLED 009100 ; This device defines the tunnel 009200 DEVICE PORTA  MPCIPA 009300 LINK ETH1 IPAQENET PORTA 009410 HOME 192.168.1.2 ETH1 009500 ; This second device is for public, external connectivity 009600 DEVICE PORTB  MPCIPA 009700 LINK ETH2 IPAQENET PORTB 009800 HOME 10.7.32.11 ETH2 009900 BEGINROUTES 010100    ROUTE 192.168.1.1/32     =       ETH1 MTU 1492 010300    ROUTE 10.7.32.254/32     =       ETH2 MTU 1492 010400    ROUTE 192.168.1.0/32 192.168.1.1 ETH1 MTU 1492 010410    ROUTE 10.7.32.0/32   10.7.32.254 ETH2 MTU 1492 010500 ENDROUTES 010600 ITRACE OFF 010700 IPCONFIG NODATAGRAMFWD 010800 UDPCONFIG RESTRICTLOWPORTS 010900 TCPCONFIG RESTRICTLOWPORTS 011000 START PORTA 011100 START PORTB ****** **************************** Bottom of Data ****************************

I think I have answered my last question about viewing MVS output.. In the SYSLOG output I see the following messages:

S TCPIP $HASP100 TCPIP    ON STCINRDR IEF695I START TCPIP    WITH JOBNAME TCPIP    IS ASSIGNED TO USER TCPIP , GROUP OMVSGRP $HASP373 TCPIP    STARTED IEF403I TCPIP - STARTED - TIME=12.14.28 IEE252I MEMBER CTIEZB00 FOUND IN ADCD.Z111S.PARMLIB IEE252I MEMBER CTIIDS00 FOUND IN SYS1.PARMLIB IEE252I MEMBER CTINTA00 FOUND IN SYS1.PARMLIB EZZ7450I FFST SUBSYSTEM IS NOT INSTALLED EZZ0162I HOST NAME FOR TCPIP IS BTHUNDER EZZ0300I OPENED PROFILE FILE DD:PROFILE EZZ0309I PROFILE PROCESSING BEGINNING FOR DD:PROFILE EZZ0401I SYNTAX ERROR IN FILE: DD:PROFILE ON LINE: 1 AT: '00010001' EZZ0324I UNRECOGNIZED STATEMENT 00010001 FOUND ON LINE 1 EZZ0324I UNRECOGNIZED STATEMENT 00020001 FOUND ON LINE 2 EZZ0318I 00030001 WAS FOUND ON LINE 3 AND PROC NAME, VALID AUTOLOG OPTION, OR ENDAUTOLOG WAS EXPECTED EZZ0323I AUTOLOG STATEMENT ON LINE 3 HAD NO ENTRIES EZZ0324I UNRECOGNIZED STATEMENT 00030001 FOUND ON LINE 3 EZZ0318I 00070001 WAS FOUND ON LINE 7 AND PORT NUMBER WAS EXPECTED EZZ0401I SYNTAX ERROR IN FILE: DD:PROFILE ON LINE: 90 AT: '00900001' EZZ0324I UNRECOGNIZED STATEMENT 00900001 FOUND ON LINE 90 EZZ0324I UNRECOGNIZED STATEMENT 00920001 FOUND ON LINE 92 EZZ0324I UNRECOGNIZED STATEMENT 00930009 FOUND ON LINE 93 EZZ0318I 00941010 WAS FOUND ON LINE 94 AND IP ADDRESS OR NEXT STATEMENT WAS EXPECTED EZZ0324I UNRECOGNIZED STATEMENT 00960009 FOUND ON LINE 96 EZZ0324I UNRECOGNIZED STATEMENT 00970009 FOUND ON LINE 97 EZZ0318I 00980009 WAS FOUND ON LINE 98 AND IP ADDRESS OR NEXT STATEMENT WAS EXPECTED EZZ0318I 00990009 WAS FOUND ON LINE 99 AND ROUTE WAS EXPECTED EZZ0401I SYNTAX ERROR IN FILE: DD:PROFILE ON LINE: 104 AT: 'ENDROUTES' EZZ0401I SYNTAX ERROR IN FILE: DD:PROFILE ON LINE: 105 AT: '01060001' EZZ0324I UNRECOGNIZED STATEMENT 01060001 FOUND ON LINE 105 EZZ0324I UNRECOGNIZED STATEMENT 01070001 FOUND ON LINE 106 EZZ0324I UNRECOGNIZED STATEMENT 01080001 FOUND ON LINE 107 EZZ0324I UNRECOGNIZED STATEMENT 01090001 FOUND ON LINE 108 EZZ0324I UNRECOGNIZED STATEMENT 01100001 FOUND ON LINE 109 EZZ0324I UNRECOGNIZED STATEMENT 01110009 FOUND ON LINE 110 EZZ0316I PROFILE PROCESSING COMPLETE FOR FILE DD:PROFILE EZZ0303I INITIAL PROFILE FILE CONTAINS ERRORS EZZ0334I IP FORWARDING IS DISABLED EZZ4308I ERROR: CODE=80103016 DURING ACTIVATION OF DEVICE PORTA. DIAGNOSTIC CODE: 02 EZZ4308I ERROR: CODE=80103016 DURING ACTIVATION OF DEVICE PORTB. DIAGNOSTIC CODE: 02 EZZ0338I TCP PORTS 1 THRU 1023 ARE RESERVED EZZ0338I UDP PORTS 1 THRU 1023 ARE RESERVED EZZ4202I Z/OS UNIX - TCP/IP CONNECTION ESTABLISHED FOR TCPIP EZB6473I TCP/IP STACK FUNCTIONS INITIALIZATION COMPLETE. EZAIN11I ALL TCPIP SERVICES FOR PROC TCPIP ARE AVAILABLE. EZD1176I TCPIP HAS SUCCESSFULLY JOINED THE TCP/IP SYSPLEX GROUP EZBTCPCS +CSQX023I %CSQ7 CSQXLSTT Listener started, 394 port 1416 address *, TRPTYPE=TCP INDISP=QMGR EZZ6003I TELNET LISTENING ON PORT    23

It's like the system is trying to process the line numbers from the profile configuration.

Vance, couple of things.

1. You can scroll the System Log (TSO M from Main Menu then SDSF from the sub menu or m.5 from the main menu - then select LOG) up (PF8 or UP nn and down PF7 or DOWN nn) and right and left.

2. You complicated you life considerablly by going from scenario 2 to 5 - without getting scenario 2 to fly.

3. IBM RED BOOK OSA-Express Implementation Guide will give you many examples to use for a syntax reference.

4. When I have have a minute today I will copy all my scenario 2 changes (it was mostly not getting thrown off by the Config Guide changes).

5. Scenario 2 is not much good for anything except FTP back on forth between zPDT zOS/TSO and the Linux. Don't forget to ioncrease the MIH values for OSA.

Jay/Fidelity Investements

A few changes to my routing configuration:

009900 BEGINROUTES 010100    ROUTE 192.168.1.0/32     =       ETH1 MTU 1492 010300    ROUTE 10.7.32.0/32       =       ETH2 MTU 1492 010400    ROUTE DEFAULT        10.7.32.254 ETH2 MTU 1492 010500 ENDROUTES

I am still getting the same syntax errors when starting TCPIP and still not getting a valid default route.

Okay, I think I've found the main culprit here. When I scroll right on my profile configuration member, I see many numbers in the right hand column. These obviously shouldn't be here, but the editor will not let me delete them. Even when I insert a new line and start typing, the numbers are auto-generated. I figure that it has something to do with the member parameters but I have no idea how to correct this behavior.

Any advice would be very much appreciated.

I added semicolons to the end of each line in my configuration member and now it is processing correctly. I'm sure this is a hack, but I have nothing else to work on now and would like to continue getting this machine up and running.

In any case, now I am getting routes and stuff like I expected to before, but my interfaces are not coming up.

- 13.58.47           V TCPIP,,START,PORTA 13.58.47 STC00057  EZZ0060I PROCESSING COMMAND: VARY TCPIP,,START,PORTA 13.58.47 STC00057  EZZ0053I COMMAND VARY START COMPLETED SUCCESSFULLY - 13.58.47 STC00057  EZZ4308I ERROR: CODE=80103016 DURING ACTIVATION OF -  DEVICE PORTA. DIAGNOSTIC CODE: 02 - 13.59.01           V TCPIP,,START,PORTB 13.59.01 STC00057  EZZ0060I PROCESSING COMMAND: VARY TCPIP,,START,PORTB 13.59.01 STC00057  EZZ0053I COMMAND VARY START COMPLETED SUCCESSFULLY - 13.59.01 STC00057  EZZ4308I ERROR: CODE=80103016 DURING ACTIVATION OF -  DEVICE PORTB. DIAGNOSTIC CODE: 02

Further output "TSO NETSTAT DEV":

EZZ2350I MVS TCP/IP NETSTAT CS V1R11       TCPIP Name: TCPIP           20:03:06 EZZ2760I DevName: LOOPBACK          DevType: LOOPBACK EZZ2766I   DevStatus: Ready EZZ2761I   LnkName: LOOPBACK          LnkType: LOOPBACK    LnkStatus: Ready EZZ2821I     ActMtu: 65535 EZZ2768I   Routing Parameters: EZZ2769I     MTU Size: n/a               Metric: 00 EZZ2770I     DestAddr: 0.0.0.0           SubnetMask: 0.0.0.0 EZZ2810I   Multicast Specific: EZZ2811I     Multicast Capability: No EZZ3080I   Link Statistics: EZZ3081I     BytesIn                           = 568 EZZ3082I     Inbound Packets                   = 2 EZZ3083I     Inbound Packets In Error          = 0 EZZ3084I     Inbound Packets Discarded         = 0 EZZ3085I     Inbound Packets With No Protocol  = 0 EZZ3086I     BytesOut                          = 568 EZZ3087I     Outbound Packets                  = 2 EZZ3088I Outbound Packets In Error         = 0 EZZ3089I     Outbound Packets Discarded        = 0 EZZ2760I DevName: PORTA             DevType: MPCIPA EZZ2766I   DevStatus: Not Active    CfgRouter: Non  ActRouter: Unknown EZZ2761I   LnkName: ETH1              LnkType: IPAQENET    LnkStatus: Not Activ e EZZ2764I     IpBroadcastCapability: No EZZ2821I     ActMtu: Unknown EZZ2822I     VLANid: None                   VLANpriority: Unknown EZZ2825I     SecClass: 255                  MonSysplex: No EZZ2768I   Routing Parameters: EZZ2769I     MTU Size: n/a               Metric: 00 EZZ2770I     DestAddr: 0.0.0.0           SubnetMask: 255.255.255.0 EZZ2810I   Multicast Specific: EZZ2811I     Multicast Capability: Unknown EZZ3080I   Link Statistics: EZZ3081I     BytesIn                           = 0 EZZ3082I     Inbound Packets                   = 0 EZZ3083I     Inbound Packets In Error          = 0 EZZ3084I     Inbound Packets Discarded         = 0 EZZ3085I     Inbound Packets With No Protocol  = 0 EZZ3086I     BytesOut                          = 0 EZZ3087I     Outbound Packets                  = 0 EZZ3088I     Outbound Packets In Error         = 1 EZZ3089I     Outbound Packets Discarded        = 0 EZZ2760I DevName: PORTB             DevType: MPCIPA EZZ2766I   DevStatus: Not Active    CfgRouter: Non  ActRouter: Unknown EZZ2761I   LnkName: ETH2              LnkType: IPAQENET    LnkStatus: Not Activ e EZZ2764I     IpBroadcastCapability: No EZZ2821I     ActMtu: Unknown EZZ2822I     VLANid: None                   VLANpriority: Unknown EZZ2825I     SecClass: 255                  MonSysplex: No EZZ2768I   Routing Parameters: EZZ2769I     MTU Size: n/a               Metric: 00 EZZ2770I     DestAddr: 0.0.0.0           SubnetMask: 255.255.255.0 EZZ2810I   Multicast Specific: EZZ2811I     Multicast Capability: Unknown EZZ3080I   Link Statistics: EZZ3081I     BytesIn                           = 0 EZZ3082I     Inbound Packets                   = 0 EZZ3083I     Inbound Packets In Error          = 0 EZZ3084I     Inbound Packets Discarded         = 0 EZZ3085I     Inbound Packets With No Protocol  = 0 EZZ3086I     BytesOut                          = 0 EZZ3087I     Outbound Packets                  = 0 EZZ3088I     Outbound Packets In Error         = 53 EZZ3089I     Outbound Packets Discarded        = 0 EZZ2826I IPv4 LAN Group Summary EZZ2772I No IPv4 Lan Groups EZZ2639I OSA-Express Network Traffic Analyzer Information: EZZ2664I No OSA-Express Network Traffic Analyzer interfaces are defined

According to IBM support pages:

Problem(Abstract) EZZ4308I ERROR: CODE=80103016 DURING ACTIVATION OF DEVICE xxxxxx. DIAGNOSTIC CODE: 02   Cause This message is issued at TCP initialization or when a VARY TCPIP,,START,xxxxxx command is issued to start an MPCPTP device from TCP/IP and the TRLE associated with that device is not yet active.   Resolving the problem Activate the TRLE being used to start the MPCPTP device.

How do I activate the TRLE? I really don't have a clue as to what this means.

At this point I am just documenting as I discover for posterity. Any assistance is still much appreciated.

If I understand correctly, the TRLE is the OSATRL2 configuration where I set the device id numbers for each interface. By running the MVS command 'D NET,TRL' I see the following:

- 14.14.12           d net,trl 14.14.12 STC00004  IST097I DISPLAY ACCEPTED 14.14.12 STC00004  IST350I DISPLAY TYPE = TRL IST924I ------------------------------------------------------------- IST1954I TRL MAJOR NODE = ISTTRL IST1314I TRLE = IUTIQDIO  STATUS = NEVAC       CONTROL = MPC IST1314I TRLE = IUTSAMEH  STATUS = NEVAC       CONTROL = MPC IST1454I 2 TRLE(S) DISPLAYED IST924I ------------------------------------------------------------- IST1954I TRL MAJOR NODE = OSATRL2 IST1314I TRLE = OSATRL1E  STATUS = NEVAC       CONTROL = MPC IST1314I TRLE = OSTARL2E  STATUS = NEVAC       CONTROL = MPC IST1454I 2 TRLE(S) DISPLAYED IST314I END

The STATUS=NEVAC means that the TRL is not being activated. I went back and looked at the original member ADCD.Z111S.VTAMLST(OSATRL2) and noticed there were some X's at the end of the lines being continued. I replaced my OSATRL2 with the original and IPLed the system.

At this point, the tunnel interface is coming up, but the external one is not. I can connect with x3270 via the tunnel. Investigating further, will update as I come across anything.

It turns out that the public IP address I was given was already in use by another host. Using a different IP address on ETH2 corrected the remote connectivity issue.

CS V1R11: Pinging host WWW.GOOGLE.COM (74.125.47.99) Ping #1 response took 0.065 seconds.

That feels good, now on to RACF configurations :)

Ah, another thing. In omvs, I see the following:

IBMUSER:/u/ibmuser: >cat /etc/hosts 192.168.252.167 adcd.dfw.ibm.com adcd

I cannot seem to run ifconfig to verify what IP address unix is seeing out on, but DNS is working there. Do I just edit the hosts file and carry on? I'd like to be able to run ifconfig and route from omvs, but I cannot locate the programs.

IBMUSER:/u/ibmuser: >cd /usr/sbin IBMUSER:/Z111S/usr/sbin: >ls IBM         dmd         fome46ds    mailq       osnmpd      smtpd automount   ds2ldif31   fome620s    mailstats   otelnetd    sntpd chmount     ds2ldif64   fome640s    mknod       pagent      sshd chroot      dsconfig    ftpd        mount       popper      syslogd confighfs   filecache   ftpdns      named       purgestat   tftpd configstk   fome31is    hoststat    newaliases  rlogind     timed configstrm  fome40bs    iked        nssd        rlogind2    trapfwd cron        fome45br    inetd       omproute    rpcbind     trmd db2pwden    fome45bs    init        orexecd     rsvpd       unmount dcas        fome46dr    kerninfo    orshd       sendmail    uucpd

Morning Vance, looks like you solved your problems before I had the time to get back to you - sorry.

So you got Scenario 5 to work and tested inbound and outbound from zOS?

Can you post your final USER.TCPPARMS(PROFILE),(TCPPARMS)and(TCPDATA)and USER.VTAMLST(OSATRL1)

Ever figure out the ifconfig problem?

The RACF changes are easy.

Sincerely,

Jay

Jay,

No problem on that, I get more enjoyment figuring stuff out on my own anyways ;)

One thing though, I implemented Scenario 4, not 5. Here are the data members you requested.

USER.TCPPARMS(PROFILE)

ARPAGE 5 ; DATASETPREFIX TCPIP ; AUTOLOG 5 ; FTPD JOBNAME FTPD1   ; FTP Server PORTMAP              ; Portmap Server ENDAUTOLOG ; PORT ; 7 UDP MISCSERV            ; Miscellaneous Server 7 TCP MISCSERV ; 9 UDP MISCSERV ; 9 TCP MISCSERV ; 19 UDP MISCSERV ; 19 TCP MISCSERV ; 20 TCP OMVS      NOAUTOLOG ; FTP Server 21 TCP OMVS                ; FTP Server 23 TCP TN3270              ; Telnet Server 25 TCP SMTP                ; SMTP Server 53 TCP NAMESRV             ; Domain Name Server 53 UDP NAMESRV             ; Domain Name Server 69 UDP OMVS                ; OE TFTP SERVER 80 TCP OMVS                ; OE WEB SERVER 111 TCP PORTMAP             ; Portmap Server 111 UDP PORTMAP             ; Portmap Server 135 UDP LLBD                ; NCS Location Broker 161 UDP OSNMPD              ; SNMP Agent 162 UDP SNMPQE              ; SNMP Query Engine 433 TCP OMVS                ; OE WEB Server 443 TCP OMVS                ; Secure Server 512 TCP RXSERVE             ; Remote Execution Server 513 UDP OMVS                ; OE RLOGIN SERVER 514 UDP OMVS                ; OE syslog server 514 TCP RXSERVE             ; Remote Execution Server 515 TCP LPSERVE             ; LPD Server 520 UDP OROUTED             ; RouteD Server 580 UDP NCPROUT             ; NCPROUTE Server 750 TCP MVSKERB             ; Kerberos 750 UDP MVSKERB             ; Kerberos 751 TCP ADM@SRV             ; Kerberos Admin Server 751 UDP ADM@SRV             ; Kerberos Admin Server ;  1021 TCP OMVS                ; OE FTP SERVER 1023 TCP OMVS                ; OE TELNET SERVER 1023 UDP OMVS                ; OE TELNET SERVER 1024 TCP OMVS                ; OE SERVICES 1415 TCP CSQ1CHIN            ; CSQ1 MQ TCP Listener 3000 TCP CICSTCP             ; CICS Socket 32200 TCP BBN7ACRS             ; Daemon IP port 32201 TCP BBN7ACRS NODELAYACKS ; Daemon SSL port 32202 TCP BBNS001            ; SOAP JMX Connector port 32203 TCP BBNS001            ; ORB port 32204 TCP BBNS001 NODELAYACKS ; ORB SSL port 32205 TCP BBNS001             ; Administrative console port 32206 TCP BBNS001 NODELAYACKS ; Administrative console secure port 32207 TCP BBNS001             ; HTTP transport port 32208 TCP BBNS001 NODELAYACKS ; HTTPS transport port 32209 TCP BBNS001             ; Administrative Local Port 32210 TCP BBNS001             ; High availability manager comm port 32211 TCP BBNS001             ; Service Integration port 32212 TCP BBNS001 NODELAYACKS ; Service Integration secure port 32213 TCP BBNS001S            ; Service Integration MQ interoper 32214 TCP BBNS001S NODELAYACKS ; Service Integration MQ inter secure 32215 TCP BBNS001            ; Session Initiation Protocol (SIP) 32216 TCP BBNS001 NODELAYACKS ; Session Init Protocol (SIP) secure 8879 TCP BBODMGR             ; SOAP JMX Connector port 7277 TCP BBODMGR             ; Cell Discovery port 9809 TCP BBODMGR             ; ORB port 9090 TCP BBODMGR             ; HTTP port 9043 TCP BBODMGR             ; HTTPS port 5755 TCP BBODMNC             ; Daemon port 5756 TCP BBODMNC             ; Daemon SSL port ; WAS Base Node entries 8880 TCP BBOS001             ; SOAP JMX Connector port ; 2809 TCP BBOS001             ; ORB port (COMMENT THIS ONE OUT) 9080 TCP BBOS001             ; HTTP port 9443 TCP BBOS001             ; HTTPS port 5655 TCP BBODMNB             ; Daemon port 5656 TCP BBODMNB             ; Daemon SSL port ; WAS Federation entries 8878 TCP BBON001             ; SOAP JMX Connector port 7272 TCP BBON001             ; Node Discovery port 2809 TCP BBON001             ; Node Agent s ORB port 9810 TCP BBOS001             ; Base Server s ORB port SACONFIG DISABLED ; ; This device defines the tunnel DEVICE PORTA  MPCIPA ; LINK ETH1 IPAQENET PORTA ; HOME 192.168.1.2 ETH1 ; ; This second device is for public, external connectivity DEVICE PORTB  MPCIPA ; LINK ETH2 IPAQENET PORTB ; HOME 10.7.32.8 ETH2 ; BEGINROUTES ; ROUTE 192.168.1.0/24     =       ETH1 MTU 1492 ; ROUTE 10.7.32.0/24       =       ETH2 MTU 1492 ; ROUTE DEFAULT        10.7.32.254 ETH2 MTU 1492 ; ENDROUTES ; ITRACE OFF ; IPCONFIG NODATAGRAMFWD ; UDPCONFIG RESTRICTLOWPORTS ; TCPCONFIG RESTRICTLOWPORTS ; START PORTA ; START PORTB ;

I did not implement a USER.TCPPARMS(TCPPARMS) data member..

USER.TCPPARMS(TCPDATA)

;*********************************************************************** ;                                                                      * ;   Name of Data Set:     TCPIP.DATA                                   * ;                                                                      * ;   COPYRIGHT = NONE.                                                  * ;                                                                      * ;   This data, TCPIP.DATA, is used to specify configuration            * ;   information required by TCP/IP client and server programs.         * ;                                                                      * ;                                                                      * ;   Syntax Rules for the TCPIP.DATA configuration data set:            * ;                                                                      * ;   (a) All characters to the right of and including a ; or # will     * ;       be treated as a comment.                                       * ;                                                                      * ;   (b) Blanks and <end-of-line> are used to delimit tokens.           * ; * ;   (c) The format for each configuration statement is:                * ;                                                                      * ;       <SystemName||':'>  keyword  value                              * ;                                                                      * ;       where <SystemName||':'> is an optional label that can be       * ;       specified before a keyword; if present, then the keyword-      * ;       value pair will only be recognized if the SystemName matches   * ;       the name of the MVS system.                                    * ;       SystemName is derived from the MVS image name. Its value should* ;       be the IEASYSxx parmlib member's SYSNAME= parameter value.     * ;       The SystemName can be specified by either restartable VMCF     * ;       or the subsystem definition of VMCF in the IEFSSNxx member of  * ;       PARMLIB.                                                       * ;                                                                      * ;       For SMTP usage use the NJENODENAME statement in the SMTP       * ;       configuration data set to specify the JES nodename for mail    * ;       delivery on the NJE network.                                   * ;                                                                      * ;*********************************************************************** ; ; TCPIPJOBNAME statement ; ====================== ; TCPIPJOBNAME specifies the name of the started procedure that was ; used to start the TCPIP address space.    TCPIP is the default for ; most cases.  However, for applications which use LE services, the ; lack of a TCPIPJOBNAME statement causes applications that issue ; __iptcpn() to receive a jobname of NULL, and some of these ; application will use INET instead of TCPIP.  Although this presents ; no problem when running in a single-stack environment, this can ; potentially cause errors in a multi-stack environment. ; ; If multiple TCPIP stacks are run on a single system, each stack will ; require its own copy of this file, each with a different value for ; TCPIPJOBNAME. ; TCPIPJOBNAME TCPIP ; ; ; HOSTNAME statement ; ================== ; HOSTNAME specifies the TCP host name of this system as it is known ; in the IP network.  If not specified, the default HOSTNAME will be ; the name specified by either restartable VMCF or the subsystem ; definition of VMCF in the IEFSSNxx member of PARMLIB. ; If the VMCF name is not available then the IEASYSxx parmlib member's  ; SYSNAME= parameter value will be used. ; ; For example, if this TCPIP.DATA data set is shared between 2 ; systems, OURMVSNAME and YOURMVSNAME, then the following 2 lines ; will define the HOSTNAME correctly on each system. ; ; OURMVSNAME:    HOSTNAME  OURTCPNAME ; YOURMVSNAME:   HOSTNAME  YOURTCPNAME ; ; No prefix is required if the TCPIP.DATA file is not being shared. ; HOSTNAME BTHUNDER ; ; ; NOTE - Use either DOMAINORIGIN/DOMAIN or SEARCH to specify your domain ;         origin value ; ; DOMAINORIGIN or DOMAIN statement ; ================================ ; DOMAINORIGIN or DOMAIN specifies the domain origin that will be ; appended to host names passed to the resolver.  If a host name ; ends with a dot, then the domain origin will not be appended to the ; host name. ; DOMAINORIGIN  WTCS.WTAMU.EDU ; ; ; SEARCH statement ; ================ ; SEARCH specifies a list of 1 to 6 domain origin values that will be ; appended to host names passed to the resolver.  If a host name ; ends with a dot, then none of the domain origin values will be ; appended to the host name. ;  The first domain origin value specified by SEARCH will be used as the ; DOMAINORIGIN/DOMAIN value. ; ; SEARCH YOUR.DOMAIN.NAME my.domain.name domain.name ; ; ; DATASETPREFIX statement ; ======================= ; DATASETPREFIX is used to set the high level qualifier for dynamic ; allocation of data sets in TCP/IP. ; ; The character string specified as a parameter on ; DATASETPREFIX takes precedence over the default prefix of "TCPIP". ; ; The DATASETPREFIX parameter can be up to 26 characters long ; and the parameter must NOT end with a period. ; ; For more information please see "Dynamic Data Set Allocation" in ; the IP Configuration Guide. ; DATASETPREFIX TCPIP ; ; ; MESSAGECASE statement ; ===================== ; MESSAGECASE MIXED indicates to some servers, such as FTPD, that ; messages should be displayed in mixed case.  MESSAGECASE UPPER ; indicates that all messages should be displayed in uppercase.  Mixed ; case strings that are inserted in messages will not be uppercased. ; ; If MESSAGECASE is not specified, mixed case messages will be used. ; ; MESSAGECASE MIXED ; MESSAGECASE UPPER ; ; ; NSINTERADDR or NAMESERVER statement ; =================================== ; NSINTERADDR or NAMESERVER specifies the IP address of the name server. ; LOOPBACK (127.0.0.1) specifies your local name server.  If a name ; server will not be used, then do not code an NSINTERADDR statement ; or NAMESERVER statement. ; ; The NSINTERADDR or NAMESERVER statement can be repeated up to sixteen ; times to specify alternate name servers.  The name server listed first ; will be the first one attempted. ; NSINTERADDR  10.7.32.5 NSINTERADDR  10.7.32.7 NSINTERADDR  172.16.20.66 ; ; ; NSPORTADDR statement ; ==================== ; NSPORTADDR specifies the foreign port of the name server. ; 53 is the default value. ; ; NSPORTADDR 53 ; ; ; RESOLVEVIA statement ; ==================== ; ; RESOLVEVIA specifies how the resolver is to communicate with the ; name server.  TCP indicates use of TCP connections.  UDP indicates ; use of UDP datagrams.  The default is UDP. ; RESOLVEVIA UDP ; ; ; RESOLVERTIMEOUT statement ; ========================= ; RESOLVERTIMEOUT specifies the time in seconds that the resolver ; will wait for a response from the name server (either UDP or TCP). ; The default is 30 seconds. ; RESOLVERTIMEOUT 10 ; ; ; RESOLVERUDPRETRIES statement ; ============================ ; ; RESOLVERUDPRETRIES specifies the number of times the resolver ; should try to connect to the name server when using UDP datagrams. ; The default is 1. ; RESOLVERUDPRETRIES 1 ; ; ; LOOKUP statement ; ================ ; LOOKUP indicates the order of name and address resolution.  DNS means ; use the DNSs listed on the NSINTERADDR and NAMESERVER statements. ; LOCAL means use the local host tables as appropriate for the ; environment being used (UNIX System Services or Native MVS). ; LOOKUP DNS ; ; ; LOADDBCSTABLES statement ; ======================== ; LOADDBCSTABLES indicates to the FTP server and FTP client which DBCS ; translation tables should be loaded at initialization time. Remove ; from the list any tables that are not required. If LOADDBCSTABLES is ; not specified, no DBCS tables will be loaded. ; ; LOADDBCSTABLES JIS78KJ JIS83KJ SJISKANJI EUCKANJI HANGEUL KSC5601 ; LOADDBCSTABLES TCHINESE BIG5 SCHINESE ; ; ; SOCKDEBUG statement ; =================== ; Use the SOCKDEBUG statement to turn on the tracing of TCP/IP C and ; REXX socket library calls. ; This command is for debugging purposes only. ; ; SOCKDEBUG ; ; ; SOCKNOTESTSTOR statement ; ======================== ; SOCKTESTSTOR is used to check socket calls for storage access errors ; on the parameters to the call.  SOCKNOTESTSTOR stops this checking ; and is better for response time.  SOCKNOTESTSTOR is the default. ; ; SOCKTESTSTOR ; SOCKNOTESTSTOR ; ; ; TRACE RESOLVER statement ; ======================== ; TRACE RESOLVER will cause a complete trace of all queries to and ; responses from the name server or site tables to be written to ; the user's joblog.  This command is for debugging purposes only.  ; ; TRACE RESOLVER ; ; ; OPTIONS statement ; ================= ; Use the OPTIONS statement to specify the following: ;  DEBUG ;   Causes resolver debug messages to be issued. This is equivalent to ;    TRACE RESOLVER ;  NDOTS:n ;   Indicates the number of periods (.) that need to be contained in a ;    domain name for it to be considered a fully qualified domain name ; ; OPTIONS NDOTS:1 DEBUG ; ; ; SORTLIST statement ; ================== ; Use the SORTLIST statement to specify the ordered list (maximum of 4) ; of network numbers (subnets or networks) for the resolver to prefer ; if it receives multiple addresses as the result of a name query. ; ; SORTLIST 128.32.42.0/24 128.32.42.0/255.255.0.0 9.0.0.0 ; ; ; TRACE SOCKET statement ; ====================== ; TRACE SOCKET will cause a complete trace of all calls to TCP/IP ; through the C socket library. ; This statement is for debugging purposes only. ; ; TRACE SOCKET ; ; ; ALWAYSWTO statement ; =================== ; ALWAYSWTO causes messages for some servers, such as SMTP and LPD, ; to be issued as WTOs. Specifying YES can cause excessive operator ; console messages to be issued. ; ALWAYSWTO NO ; ALWAYSWTO YES ; ; Obsolete statements ; =================== ; The following statements no longer have any effect when included in ; this file: ;   SOCKBULKMODE ;   SOCKDEBUGBULKPERF0 ; ; End of file. ;

USER.VTAMLST(ATCCON00)

(I changed this data member to point to OSATRL2 instead of 1)

A0600,NSNAFXX,NSNA70X,NSNA90X,DYNMODEL,XCAE40R,XCAE40E,COSAPPN,        * A0TCP,DB8GLU,OSATRL2,IMS10APL,DB9GLU,CICSAPPL

USER.VTAMLST(OSATRL2)

OSATRL1 VBUILD TYPE=TRL OSATRL1E TRLE LNCTL=MPC,READ=(0400),WRITE=(0401),DATAPATH=(0402),      X PORTNAME=PORTA,                                         X MPCLEVEL=QDIO OSATRL2E TRLE LNCTL=MPC,READ=(0404),WRITE=(0405),DATAPATH=(0406),      X PORTNAME=PORTB,                                         X MPCLEVEL=QDIO

Also, no I have not figured out where ifconfig is located in OMVS. Hopefully I'll come across that soon.

There is no ifconfig in USS. Try Netstat instead. Netstat works on both the TSO side and the USS side. You can also use Display TCPIP from the z/OS console.

RDzJohn

Glad you got things working.

Words of Wisdom:

Keep it simple.
Start small.
Don't change things you don't have to change.

RDz John

John,

Thanks for the advice, I see that netstat in USS behaves much like the one in TSO. That will work just great.

Vance or any of my other RDzUT friends, when trying to get Scenario 4 to run did you have to define (on the Linux side)an alias for the zOS fixed IP address (eth0:0)to go with the Linux IP Address (eth0)?
Jay

With scenario 4, there is no need for an alias or any special route table entries on the linux side. The linux network and the z/OS network are completely isolated from each other. z/OS traffic flows to and from the z/OS network. Linux traffic flows to and from the linux network. You can make the networks talk to each other, but you must use a private tunnel (10.1.1.x in the redbooks) to make this happen.

RDzJohn

Thanks John,
I have implemented and used Scenario 2 for some time now and have been tunneling back and forth between Linux and zOS just fine.

I just updated to scenario 4 (based on Config Guide 8.0.1) and could not ping zOS. The Linux IP is 10.86.43.217. The IP for zOS is 10.86.43.218.

Then I started wondering how the "network" knew where the zOS IP address actually was (as you can tell I am not a Linux guy).

Jay

Simple answer is "magic". The OSA adapter code in the RDzUT emulator knows how to share the physical adapter MAC address so no additional configuration is required. Some things to look at as far getting to/ from your z/OS host.

• To get to your host you need to have a valid adapter, ip address and subnet mask. You can check all of this by starting TCP/IP and the doing a HOMETEST command from TSO option 6. Once this works, you should be able to ping the z/OS host.
• Your hostname must resolve. That means you either have to point your TCPIP.DATA file t a valid DNS where you z/OS IP address resolves to, or you need to code a statement in your HOSTS.LOCAL file and your /etc/hosts file. Alternatively, you can use the z/OS RESOLVER Proc to consolidate resolver requests to one set of files. The RDz config guide does a good job of explaining the required steps. Again, you can use HOMETEST to validate that your hostname resolves.
• To get your host access to your network, you must ensure that the ROUTE statements in your TCPIP.PROFILE dataset are correct. The experts on routing statements are usually your z/OS network people. Use them to help you get these entries correct.

RDzJohn

John, Hometest says
EZA0602I TCP Host Name is: ADCD

EZA0605I Using Host Tables to Resolve ADCD
EZA0609E Error: Found no IP addresses corresponding to TCP Host Name:

I changed to the domain origin to our internal fmr.com and added some working NSINTERADDRS

I did set up a RESOLVER from the Config Guide.

The etc/hosts and TCPIP.HOSTS.LOCAL files would never work but I am not sure how to change them (VI or makesite) can you give me a clue?

Sincerely yours and thanks,
Jay

HOMETEST is a good way to check to see if your host name will resolve so kudos for doing it this way. If you are using the Resolver and you've set it up as the config guide suggests, there should be no need to update the /etc/host or HOSTS.LOCAL since the resolver will now handle all of that for you in one place. The IPNODES member of USER.TCPPARMS is the place to look. You need to add an entry for your hostname as defined in USER.TCPPARMS(TCPDATA) and your ip address as defined in USER.TCPPARMS(PROFILE).

RDzJohn

Thanks John, I will look see into IPNODES.

Here is what I do have:)
my laptop (linux IP) is 10.86.43.217
My assigned IP for zOS is 10.86.43.218
Our network requires pre-registered MAC addresss but I assume the Linux adapter MAC will suffice.

PROFILE (actually called PROFT2) from USER.TCPPARMS
SACONFIG DISABLED

DEVICE ADM1ETP MPCIPA
LINK ETH1 IPAQENET ADM1ETP
HOME 10.1.1.2 ETH1

DEVICE ADM2ETP MPCIPA
LINK ETH2 IPAQENET ADM2ETP
HOME 10.86.43.218 ETH2

BEGINROUTES
ROUTE 10.0.0.0 255.0.0.0 = ETH1 MTU 1492
ROUTE 10.86.43.0 255.255.255.0 = ETH2 MTU 1492
ROUTE DEFAULT 10.86.43.1 ETH2 MTU 1492
ENDROUTES

ITRACE OFF
IPCONFIG NODATAGRAMFWD
UDPCONFIG RESTRICTLOWPORTS
TCPCONFIG RESTRICTLOWPORTS
START ADM1ETP
START ADM2ETP

TCPDATA from USER.TCPPARMS

TCPIPJOBNAME TCPIP
HOSTNAME ADCD (also tried my laptop zOS name found by nslookup ws445341.fmr.com)
DOMAINORIGIN FMR.COM
DATASETPREFIX TCPIP
NSINTERADDR 172.22.102.76 (most addresses resolve here including my machine)
NSINTERADDR ( plus a few others)
RESOLVEVIA UDP
LOOKUP DNS LOCAL
RESOLVERTIMEOUT 10
RESOLVERUDPRETRIES 1
ALWAYSWTO NO

The IPL Log shows Hpostname for TCPIP (whatever I user) active and ADM1ETP and ADM2ETP processing complete.

-bash-3.2$ cat hosts

1. Do not remove the following line, or various programs
2. that require network functionality will fail.

127.0.0.1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6

zOS OMVS
IBMUSER:/ADCD/etc: >cat hosts
192.168.252.167 adcd.dfw.ibm.com adcd
IBMUSER:/ADCD/etc: >

TCPIP.HOSTS.LOCAL
HOST : 192.168.252.167 : adcd.dfw.ibm.com, adcd:

-bash-3.2$ nslookup 10.86.43.217 (Linux IP)
Server: 172.22.102.76
Address: 172.22.102.76#53

Non-authoritative answer:
217.43.86.10.in-addr.arpa name = ws445340.fmr.com.

Also got a name = ws445341.fmr.com for zOS somewhere

Jay

In a previous post you mentioned that you added a valid NSINTRADDR address. In my experience its easiest to just comment out NSINTERADDR and use the local IPNODES file for host name resolution. Unless you have a real reason to resolve host names external to your UT system, I would go ahead and comment out NSINTERADDR. This can be the source of all sorts of nasty name resolution problems.

RDzJohn

Will try commenting it out (as it was in the example) and try it. Wild code up a Local IPNODE and try it as well. Again Thanks for the suggestion. Jay

Don't forget to add the following line to your USER.TCPPARMS(RESOLVER) file:

bold GLOBALIPNODES('USER.TCPPARMS(IPNODES)')

RDzJohn

GLOBALIPNODES('USER.TCPPARMS(IPNODES)')

RDzJohn

John, intesting development.
I had a feeling the host name was bothering the "gizmo" so I changed the USER.TCPPARMS(TCPDATA) parms some.

First I got rid of NSINTERADDR and it had no affect (but I had not put in the GLOBALIP stuff yet - will soon).

; HOSTNAME statement
; ==================
; ADCD, HOSTNAME ws445341.fmr.com or ws445341 J Butler Scenario 4
;HOSTNAME ADCD
HOSTNAME 10.86.43.218

; NSINTERADDR or NAMESERVER statement
;NSINTERADDR 9.38.128.3 Scenario 4 J Butler 08/24/11
NNSINTERADDR 172.22.102.76 Then ran hometest and got:
EZA0619I Running IBM MVS TCP/IP CS V1R11 TCP/IP Configuration Tester

EZA0621I The FTP configuration parameter file used will be "TCPIP.FTP.DATA".

EZA0602I TCP Host Name is: 10.86.43.218

EZA0605I Using Host Tables to Resolve 10.86.43.218
EZA0611I The following IP addresses correspond to TCP Host Name: 10.86.43.218
EZA0612I 10.86.43.218

EZA0614I The following IP addresses are the HOME IP addresses defined in PROFIL
E
.TCPIP:
EZA0615I 10.1.1.2
EZA0615I 10.86.43.218
EZA0615I 127.0.0.1
EZA0618I All IP addresses for 10.86.43.218 are in the

EZA0622I Hometest was successful - all Tests Passed!

I think this is progress?
Thnaks,
Jay

This is progress, however, you need to put a hostname in the USER.TCPPARMS(TCPDATA) data set. A hostname that matches your ip address is going to really confuse things going forward. This should be no problem once you get IPNODES configured.

RDzJohn

That's next. Should I code MVS or Unix or both:

'-GLOBALIPNODES -+-('fully qualified MVS dataset name')-+-'
'-(/file system absolute pathname)-----'
looking at the documentation now.

thanks.

See my example above.

RDzJohn

Sorry John was fishing for what exactly goes into GLOBALIPNODES('USER.TCPPARMS(IPNODES)') member but have not found it yet in the documentation but I am assuming it must be similar to USER.TCPPARMS(TCPDATA) member:) Hope you have a nice weekend if you are on your way out - hoping you are not on the storms route.
Jay

Sorry, I misunderstood what you were after. IPNODES looks like this:

192.168.1.211 RDZUT2
127.0.0.1 localhost
One line for each host you would like to resolve.
RDzJohn

Afternoon John (and friends)

Added GLOBALIPNODES to USER.TCPPARMS(RESOLVER)
Created IPNODES member in USER.TCPPARMS
But I can't NSLOOKUP or PING www.google.com from TSO !
Were is the realtime Resolver data stored so I can look at it - etc/hosts and etc/resolve.conf have off the wall stuff?
Any suggestions?

USER.TCPPARMS(PROFT2)

000169 DEVICE ADM1ETP MPCIPA
000172 LINK ETH1 IPAQENET ADM1ETP
000174 HOME 10.1.1.2 ETH1

000182 DEVICE ADM2ETP MPCIPA
000183 LINK ETH2 IPAQENET ADM2ETP
000185 HOME 10.86.43.218 ETH2

000194 BEGINRoutes
000210 ROUTE 10.0.0.0 255.0.0.0 = ETH1 MTU 1492
000211 ROUTE 10.86.43.0 255.255.255.0 = ETH2 MTU 1492
000212 ROUTE DEFAULT 10.86.43.1 ETH2 MTU DEFAULTSIZE
000214 ENDRoutes
000285 START ADM1ETP
000286 START ADM2ETP

USER.PARMLIB(BPXPRMCS) and (BPXPRM4K)
RESOLVER_PROC(RESOLVER)

USER.TCPPARMS(RESOLVER)
GLOBALTCPIPDATA('USER.TCPPARMS(TCPDATA)')
GLOBALIPNODES('USER.TCPPARMS(IPNODES)')
COMMONSEARCH

USER.TCPPARMS(IPNODES)
10.86.43.218 ws445341
127.0.0.1 localhost
172.22.102.76 nameserver

USER.TCPPARMS(TCPDATA)

000058 TCPIPJOBNAME TCPIP
000081 HOSTNAME ws445341
000095 DOMAINORIGIN fmr.com
000107 ; SEARCH YOUR.DOMAIN.NAME my.domain.name domain.name
000124 DATASETPREFIX TCPIP
000136 ; MESSAGECASE MIXED
000152 ;NNSINTERADDR 172.22.102.76
000162 ; NSPORTADDR 53
000172 RESOLVEVIA UDP
000181 RESOLVERTIMEOUT 10
000191 RESOLVERUDPRETRIES 1
000202 LOOKUP LOCAL >>> also tried DNS and DNS LOCAL
000281 ALWAYSWTO NO

USER.PROCLIB(RESOLVER)
//RESOLVER PROC PARMS='CTRACE(CTIRES00)'
//*
//EZBREINI EXEC PGM=EZBREINI,REGION=0M,TIME=1440,
// PARM=&PARMS
//SETUP DD DISP=SHR,DSN=USER.TCPPARMS(RESOLVER),FREE=CLOSE
//*

00- 12.29.41 f resolver,display
- 12.29.41 EZZ9298I DEFAULTTCPIPDATA - None
- 12.29.41 EZZ9298I GLOBALTCPIPDATA - USER.TCPPARMS(TCPDATA)
- 12.29.41 EZZ9298I DEFAULTIPNODES - None
- 12.29.41 EZZ9298I GLOBALIPNODES - USER.TCPPARMS(IPNODES)
- 12.29.41 EZZ9304I COMMONSEARCH
- 12.29.41 EZZ9304I CACHE
- 12.29.41 EZZ9298I CACHESIZE - 200M
- 12.29.41 EZZ9298I MAXTTL - 2147483647
- 12.29.41 EZZ9293I DISPLAY COMMAND PROCESSED
Netstat gate
EZZ2350I MVS TCP/IP NETSTAT CS V1R11 TCPIP Name: TCPIP 18:20:39
EZZ2635I Known gateways:
EZZ2636I NetAddress FirstHop Link Pkt Sz Subnet Mask Subnet
Value
EZZ2637I

---

---

----

---

-----------

---

EZZ2638I Default 10.86.43.1 ETH2 576 <none>
EZZ2638I 10.0.0.0 <direct> ETH1 1492 <none>
EZZ2638I 10.1.1.2 <direct> ETH1 1492 HOST
EZZ2638I 10.0.0.0 <direct> ETH2 1492 0.255.255.0 0.86.43.0
EZZ2638I 10.86.43.218 <direct> ETH2 1492 HOST
EZZ2638I 127.0.0.1 <direct> LOOPBACK 65535 HOST
Hometest
EZA0619I Running IBM MVS TCP/IP CS V1R11 TCP/IP Configuration Tester
EZA0621I The FTP configuration parameter file used will be "TCPIP.FTP.DATA".
EZA0602I TCP Host Name is: ws445341
EZA0605I Using Host Tables to Resolve ws445341
EZA0611I The following IP addresses correspond to TCP Host Name: ws445341
EZA0612I 10.86.43.218
EZA0614I The following IP addresses are the HOME IP addresses defined in PROFILE .TCPIP:
EZA0615I 10.1.1.2
EZA0615I 10.86.43.218
EZA0615I 127.0.0.1
EZA0618I All IP addresses for ws445341 are in the HOME list!
EZA0622I Hometest was successful - all Tests Passed!

---

You are getting close. I assume you are using the devmap and other files located herein? Can you ping the z/OS host from another machine? I'd need to see the joblog for your TCPIP proc and your VTAM proc.

RDzJohn

Hi John, looked at the TCPIP and VTAM Proc Logs and they were clean then started experimenting.

When I added NSINTERADDR back in to USER.TCPPARMS(TCPDATA)and specified LOOKUP DNS LOCAL things got lots better.

TSO NSLOOKUP WWW.GOOGLE.COM
EZB3170I Server: FTCNSSMT2.fmr.com
EZB3172I Address: 172.22.102.76

EZB3110I Non-authoritative answer:
EZB3170I Name: www.l.google.com
EZB3171I Addresses: 74.125.93.106, 74.125.93.147, 74.125.93.103, 74.125.93.99
EZB3173I 74.125.93.104, 74.125.93.105
EZB3175I Aliases: www.google.com

TSO PING 172.22.102.76 (name server on our network)
CS V1R11: Pinging host 172.22.102.76
Ping #1 response took 0.008 seconds.

Pings from the network (Linux and XP) to the zOS on RDzUT also work.

Thanks for all your help and so long until the next problem :)

Sincerely yours
Jay (Fidelity)

OK majic - will check as you suggest. Our mainframe people are too busy to help so I have to figure everything out myslef (read, google, and trial and error). You and frined on this forum are a great help.