Automated Testing

Automated Testing

Automated Testing

Build an automated testing process to enable continuous integration of your hybrid cloud applications including z/OS

 View Only
Back to discussions
Expand all | Collapse all

Another Scenario 4 Networking Issue

  • 1.  Another Scenario 4 Networking Issue

    Posted Fri September 16, 2011 01:06 PM
    Afternoon friends,

    I though I had all the Scenarion 4 issues worked out but when I actually tried to connect to/from TSO and the network
    I found still have some problems which I have traced to:

    The resolver process appreas to be working just fine as I can do the following:

    TSO NSLOOKUPs by Name and IP to the network (Google and Internal Servers)
    TSO NSLOOKUPs by Name and IP to zOS RDzUT itself
    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.113.104, 74.125.113.105, 74.125.113.106, 74.125.11 3.103
    EZB3173I 74.125.113.147, 74.125.113.99
    EZB3175I Aliases: www.google.com

    Network NSLOOPUPs by Name and IP to base Linux (naturally) but can also do NSLOOKUPs by Name and IP to zOS RDzUT (ws445341 at 10.86.43.218)
    -bash-3.2$ nslookup ws445341
    Server: 172.22.102.76
    Address: 172.22.102.76#53
    Non-authoritative answer:
    Name: ws445341.fmr.com
    Address: 10.86.43.218

    Pings are annother issue however:
    bash-3.2$ ping ws445341 (the name of zOS RDzUT)
    PING ws445341.fmr.com (10.86.43.218) 56(84) bytes of data.
    From ws445340.fmr.com (10.86.43.217) icmp_seq=2 Destination Host Unreachable
    -bash-3.2$ ping 10.86.46.218 (the IP of zOS RDzUT)
    PING 10.86.43.218 (10.86.43.218) 56(84) bytes of data.
    From 10.86.43.217 icmp_seq=2 Destination Host Unreachable
    TSO PING WWW.Google.com
    CS V1R11: Pinging host WWW.GOOGLE.COM (74.125.113.103)
    Ping #1 timed out
    TSO PING 74.125.113.103 (IP of google)
    CS V1R11: Pinging host 74.125.113.103
    Ping #1 timed out

    Curriously enough I can Ping from TSO to zOS RDzUT
    TSO PING 10.86.46.218 (IP of RDzUT)
    CS V1R11: Pinging host 10.86.43.218
    Ping #1 response took 0.002 seconds.
    TSO PING ws445341 (host name of RDzUT)
    CS V1R11: Pinging host ws445341.fmr.com (10.86.43.218)
    Ping #1 response took 0.004 seconds.

    My configuration is as follows:
    The static IP Address for the Linux Server is 10.86.43.217 and the one assigned for zOS is 10.86..43.218

    manager
    name awsosa 22 --path=A0 --pathtype=OSD --tunnel_intf=y
    device 400 osa osa
    device 401 osa osa
    device 402 osa osa
    manager
    name awsosa 24 --path=F0 --pathtype=OSD
    device 404 osa osa
    device 405 osa osa
    device 406 osa osa

    USER.TCPPARMS(PROFILE)
    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

    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 DEFAULTSIZE

    USER.VTAMLST(ACCON00) Changed OSATRL1 to OSATRL2

    USER.VTAMLST(OSATRL2)
    OSATRL1 VBUILD TYPE=TRL
    OSATRL1E TRLE LNCTL=MPC,READ=(0400),WRITE=(0401),DATAPATH=(0402), X
    PORTNAME=ADM1ETP, X
    MPCLEVEL=QDIO
    OSATRL2E TRLE LNCTL=MPC,READ=(0404),WRITE=(0405),DATAPATH=(0406), X
    PORTNAME=ADM2ETP, X
    MPCLEVEL=QDIO

    TSO 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 Name Server 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!

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

    USER.TCPPARMS(RESLOVER)
    GLOBALTCPIPDATA('USER.TCPPARMS(TCPDATA)')
    GLOBALIPNODES('USER.TCPPAR(IPNODES)')
    COMMONSEARCH
    USER.TCPPARMS(IPNODES)
    10.86.43.218 ws445341
    127.0.0.1 localhost
    172.22.102.76 nameserver
    172.26.11.82 nameserver
    155.1.167.22 nameserver

    USER.TCPPATRMS(TCPDATA)
    TCPIPJOBNAME TCPIP
    HOSTNAME ws445341
    DOMAINORIGIN fmr.com
    ; SEARCH YOUR.DOMAIN.NAME my.domain.name domain.name
    DATASETPREFIX TCPIP
    NSINTERADDR 172.22.102.76
    ; NSPORTADDR 53
    RESOLVEVIA UDP
    RESOLVERTIMEOUT 10
    RESOLVERUDPRETRIES 1
    LOOKUP DNS LOCAL
    JosephButler


  • 2.  Re: Another Scenario 4 Networking Issue

    Posted Mon September 19, 2011 10:55 AM
    To recap: You can ping the z/OS host from another machine. You cannot ping any other machines from z/OS. Your hostname resolves. This an indication that traffic outbound from the z/OS machine is not working correctly. I don't see any errors in your configuration files below. Check the Syslog for VTAM or TCPIP errors. Make sure there are no errors for TCPIP OSA devices or VTAM LUs during startup..

    RDz_John
    RDzJohn


  • 3.  Re: Another Scenario 4 Networking Issue

    Posted Mon September 19, 2011 12:32 PM
    RDzJohn, here would be my recap:
    Ping from the network to zOS or from zOS to the network will not work but NSLOOKUP will in either case.

    TSO NSLOOKUP CAN resolve (by name or IP) servers external to the network (google) and internal (OurServer).
    TSO NSLOOKUP CAN resolve(by name or IP)the machine it(RDzUT)is running on (ws405341.fmr.com or 10.86.43.218)

    Linix NSLOOKUP CAN resolve (by name or IP) servers external to the network (google) and internal (OurServer).
    Linix NSLOOKUP CAN resolve(by name or IP) the machine RDzUT is running on (ws405341.fmr.com or 10.86.43.218)

    TSO CAN ping (by name or IP) the machine it(RDzUT) is running on (ws405341.fmr.com or 10.86.43.218)
    TSO CAN NOT ping (by name or IP) servers external to the network (google) and internal (OurServer).

    Linux CAN ping (by name or IP) servers external to the network (google) and internal (OurServer).
    Linux CAN NOT ping (by name or IP) the machine it(RDzUT) is running on (ws405341.fmr.com or 10.86.43.218)

    I rebooted Linux and the results are the same regardless if my access is on a VLAN or INTERNAL.

    VTAM Logs have these oddities (see full detals below)
    09.23.07 STC00004 IST116I MEMBER IBMTGPS NOT FOUND ON VTAM DEFINITION LIBRARY
    09.23.07 STC00004 IST1743I IBMTGPS IN IBMTGPS NOT FOUND - PROCESSING CONTIN
    09.23.07 STC00004 IST061I VARY ACT FOR IBMTGPS FAILED - NODE UNKNOWN TO VTAM
    Lots of 09.23.07 STC00004 IST380I ERROR FOR ID = LCLF00 - REQUEST: ACTLINK, SENSE: 081C

    09.23.08 STC00004 IST322I CONFIGURATION IMS10APL ERROR IGNORED - TABLE NOT FOUN
    314 IST330I TABLE TYPE = MODETAB NAME = IMS10TAB
    TCPIP LOGS (See Full details below)
    09.23.30 STC00027 EZZ7450I FFST SUBSYSTEM IS NOT INSTALLED
    09.23.35 STC00027 EZZ0162I HOST NAME FOR TCPIP IS ws445341
    09.23.35 STC00027 EZZ0300I OPENED PROFILE FILE DD:PROFILE
    09.23.35 STC00027 EZZ0309I PROFILE PROCESSING BEGINNING FOR DD:PROFILE
    09.23.35 STC00027 EZZ0655I PORT 8879 TCP BBODMGR IS ALREADY RESERVED
    09.23.35 STC00027 EZZ0655I PORT 7277 TCP BBODMGR IS ALREADY RESERVED
    09.23.35 STC00027 EZZ0655I PORT 9809 TCP BBODMGR IS ALREADY RESERVED
    09.23.35 STC00027 EZZ0655I PORT 9090 TCP BBODMGR IS ALREADY RESERVED
    09.23.35 STC00027 EZZ0655I PORT 9043 TCP BBODMGR IS ALREADY RESERVED
    09.23.35 STC00027 EZZ0655I PORT 5755 TCP BBODMNC IS ALREADY RESERVED
    09.23.35 STC00027 EZZ0655I PORT 5756 TCP BBODMNC IS ALREADY RESERVED
    09.23.35 STC00027 EZZ0316I PROFILE PROCESSING COMPLETE FOR FILE DD:PROFILE
    09.23.35 STC00027 EZZ0334I IP FORWARDING IS DISABLED
    09.23.35 STC00027 EZZ0338I TCP PORTS 1 THRU 1023 ARE RESERVED
    09.23.35 STC00027 EZZ0338I UDP PORTS 1 THRU 1023 ARE RESERVED
    09.23.35 STC00027 EZZ4202I Z/OS UNIX - TCP/IP CONNECTION ESTABLISHED FOR TCPIP
    09.23.35 STC00027 EZB6473I TCP/IP STACK FUNCTIONS INITIALIZATION COMPLETE.
    09.23.35 STC00027 EZAIN11I ALL TCPIP SERVICES FOR PROC TCPIP ARE AVAILABLE.
    09.23.37 STC00027 EZD1176I TCPIP HAS SUCCESSFULLY JOINED THE TCP/IP SYSPLEX GRO
    09.23.38 STC00027 EZZ4313I INITIALIZATION COMPLETE FOR DEVICE ADM2ETP
    09.23.38 STC00027 EZZ4313I INITIALIZATION COMPLETE FOR DEVICE ADM1ETP

    Most or less compleleVTAM LOGs
    09.22.51 STC00004 ---- MONDAY, 19 SEP 2011 ----
    09.22.51 STC00004 IEF695I START VTAM WITH JOBNAME VTAM IS ASSIGNED TO U
    09.22.52 STC00004 $HASP373 VTAM STARTED
    09.22.52 STC00004 IEF403I VTAM - STARTED - TIME=09.22.52
    09.23.05 STC00004 IST2158I VTAM HAS JOINED THE SYSPLEX GROUP ISTCFS01
    09.23.05 STC00004 IST093I ISTCDRDY ACTIVE
    09.23.06 STC00004 IST1798I TOPOLOGY DATASET RETRIEVED WAS CREATED ON 09/18/11 1
    09.23.06 STC00004 IST495I SIZE HAS BEEN SET TO 999
    09.23.06 STC00004 IST315I VTAM INTERNAL TRACE ACTIVE - MODE = INT, SIZE = 999 P
    257 IST199I OPTIONS = PSS SMS
    257 IST314I END
    09.23.06 STC00004 IST984I USER EXIT ISTEXCUV IS ACTIVE
    09.23.07 STC00004 IST093I COSAPPN ACTIVE
    09.23.07 STC00004 IST984I USER EXIT ISTEXCSD IS ACTIVE
    09.23.07 STC00004 IST116I MEMBER IBMTGPS NOT FOUND ON VTAM DEFINITION LIBRARY
    09.23.07 STC00004 IST1743I IBMTGPS IN IBMTGPS NOT FOUND - PROCESSING CONTIN
    09.23.07 STC00004 IST061I VARY ACT FOR IBMTGPS FAILED - NODE UNKNOWN TO VTAM
    09.23.07 STC00004 IST093I ISTRTPMN ACTIVE
    09.23.07 STC00004 IST093I ISTTRL ACTIVE
    09.23.07 STC00004 IST093I A0600 ACTIVE
    09.23.07 STC00004 IST984I USER EXIT ISTEXCGR IS ACTIVE
    09.23.07 STC00004 IST093I NSNAFXX ACTIVE
    09.23.07 STC00004 IST380I ERROR FOR ID = LCLF00 - REQUEST: ACTLINK, SENSE: 081C
    .23.07 STC00004 IST380I ERROR FOR ID = LCLF05 - REQUEST: ACTLINK, SENSE: 081C
    ……...
    09.23.07 STC00004 IST093I NSNA70X ACTIVE
    09.23.07 STC00004 IST380I ERROR FOR ID = LCLF06 - REQUEST: ACTLINK, SENSE: 081C
    ………….
    09.23.07 STC00004 IST093I NSNA90X ACTIVE
    ……...
    09.23.07 STC00004 IST380I ERROR FOR ID = LCLF1D - REQUEST: ACTLINK, SENSE: 081C
    09.23.07 STC00004 IST093I DYNMODEL ACTIVE
    09.23.07 STC00004 IST093I XCAE40R ACTIVE
    09.23.07 STC00004 IST093I XCAE40E ACTIVE
    09.23.08 STC00004 IST093I COSAPPN ACTIVE
    09.23.08 STC00004 IST093I A0TCP ACTIVE
    09.23.08 STC00004 IST093I DB8GLU ACTIVE
    09.23.08 STC00004 IST093I OSATRL2 ACTIVE
    09.23.08 STC00004 IST322I CONFIGURATION IMS10APL ERROR IGNORED - TABLE NOT FOUN
    314 IST330I TABLE TYPE = MODETAB NAME = IMS10TAB
    09.23.08 STC00004 IST093I IMS10APL ACTIVE
    09.23.08 STC00004 IST093I DB9GLU ACTIVE
    09.23.08 STC00004 IST093I CICSAPPL ACTIVE
    09.23.08 STC00004 IST020I VTAM INITIALIZATION COMPLETE FOR CSV1R11
    09.23.08 STC00004 IST1349I COMPONENT ID IS 5695-11701-1B0
    09.23.08 STC00004 IST1348I VTAM STARTED AS INTERCHANGE NODE
    09.23.08 STC00004 IST1214I FFST SUBSYSTEM IS NOT INSTALLED
    09.23.08 STC00004 IST380I ERROR FOR ID = LCL704 - REQUEST: ACTLINK, SENSE: 081C
    09.23.08 STC00004 IST380I ERROR FOR ID = LCL705 - REQUEST: ACTLINK, SENSE: 081C
    09.23.08 STC00004 IST380I ERROR FOR ID = LCL706 - REQUEST: ACTLINK, SENSE: 081C
    09.23.08 STC00004 IST380I ERROR FOR ID = LCL707 - REQUEST: ACTLINK, SENSE: 081C
    09.23.08 STC00004 IST380I ERROR FOR ID = LCL708 - REQUEST: ACTLINK, SENSE: 081C
    ………….
    09.23.08 STC00004 IST380I ERROR FOR ID = LCL712 - REQUEST: ACTLINK, SENSE: 081C
    09.23.08 STC00004 IST380I ERROR FOR ID = LF02 - REQUEST: ACTLINK, SENSE: 081C00
    …...
    09.23.08 STC00004 IST380I ERROR FOR ID = LCL716 - REQUEST: ACTLINK, SENSE: 081C
    09.23.08 STC00004 IST380I ERROR FOR ID = LCL717 - REQUEST: ACTLINK, SENSE: 081C
    09.23.08 STC00004 IST380I ERROR FOR ID = LCL718 - REQUEST: ACTLINK, SENSE: 081C
    …….
    09.23.09 STC00004 IST380I ERROR FOR ID = XGEL06 - REQUEST: ACTLINK, SENSE: 081C

    TCPIP LOGS
    09.23.24 STC00027 ---- MONDAY, 19 SEP 2011 ----
    09.23.24 STC00027 IEF695I START TCPIP WITH JOBNAME TCPIP IS ASSIGNED TO U
    09.23.24 STC00027 $HASP373 TCPIP STARTED
    09.23.24 STC00027 IEF403I TCPIP - STARTED - TIME=09.23.24
    09.23.29 STC00027 IEE252I MEMBER CTIEZB00 FOUND IN ADCD.Z111.PARMLIB
    09.23.30 STC00027 IEE252I MEMBER CTIIDS00 FOUND IN SYS1.PARMLIB
    09.23.30 STC00027 IEE252I MEMBER CTINTA00 FOUND IN SYS1.PARMLIB
    09.23.30 STC00027 EZZ7450I FFST SUBSYSTEM IS NOT INSTALLED
    09.23.35 STC00027 EZZ0162I HOST NAME FOR TCPIP IS ws445341
    09.23.35 STC00027 EZZ0300I OPENED PROFILE FILE DD:PROFILE
    09.23.35 STC00027 EZZ0309I PROFILE PROCESSING BEGINNING FOR DD:PROFILE
    09.23.35 STC00027 EZZ0655I PORT 8879 TCP BBODMGR IS ALREADY RESERVED
    09.23.35 STC00027 EZZ0655I PORT 7277 TCP BBODMGR IS ALREADY RESERVED
    09.23.35 STC00027 EZZ0655I PORT 9809 TCP BBODMGR IS ALREADY RESERVED
    09.23.35 STC00027 EZZ0655I PORT 9090 TCP BBODMGR IS ALREADY RESERVED
    09.23.35 STC00027 EZZ0655I PORT 9043 TCP BBODMGR IS ALREADY RESERVED
    09.23.35 STC00027 EZZ0655I PORT 5755 TCP BBODMNC IS ALREADY RESERVED
    09.23.35 STC00027 EZZ0655I PORT 5756 TCP BBODMNC IS ALREADY RESERVED
    09.23.35 STC00027 EZZ0316I PROFILE PROCESSING COMPLETE FOR FILE DD:PROFILE
    09.23.35 STC00027 EZZ0334I IP FORWARDING IS DISABLED
    09.23.35 STC00027 EZZ0338I TCP PORTS 1 THRU 1023 ARE RESERVED
    09.23.35 STC00027 EZZ0338I UDP PORTS 1 THRU 1023 ARE RESERVED
    09.23.35 STC00027 EZZ4202I Z/OS UNIX - TCP/IP CONNECTION ESTABLISHED FOR TCPIP
    09.23.35 STC00027 EZB6473I TCP/IP STACK FUNCTIONS INITIALIZATION COMPLETE.
    09.23.35 STC00027 EZAIN11I ALL TCPIP SERVICES FOR PROC TCPIP ARE AVAILABLE.
    09.23.37 STC00027 EZD1176I TCPIP HAS SUCCESSFULLY JOINED THE TCP/IP SYSPLEX GRO
    09.23.38 STC00027 EZZ4313I INITIALIZATION COMPLETE FOR DEVICE ADM2ETP
    09.23.38 STC00027 EZZ4313I INITIALIZATION COMPLETE FOR DEVICE ADM1ETP
    09.23.45 STC00027 S FTPD
    EZZ0162I HOST NAME FOR TCPIP IS ws445341
    EZZ0300I OPENED PROFILE FILE DD:PROFILE
    EZZ0309I PROFILE PROCESSING BEGINNING FOR DD:PROFILE
    EZZ0655I PORT 8879 TCP BBODMGR IS ALREADY RESERVED
    EZZ0655I PORT 7277 TCP BBODMGR IS ALREADY RESERVED
    EZZ0655I PORT 9809 TCP BBODMGR IS ALREADY RESERVED
    EZZ0655I PORT 9090 TCP BBODMGR IS ALREADY RESERVED
    EZZ0655I PORT 9043 TCP BBODMGR IS ALREADY RESERVED
    EZZ0655I PORT 5755 TCP BBODMNC IS ALREADY RESERVED
    EZZ0655I PORT 5756 TCP BBODMNC IS ALREADY RESERVED
    EZZ0316I PROFILE PROCESSING COMPLETE FOR FILE DD:PROFILE
    EZZ0334I IP FORWARDING IS DISABLED
    EZZ0338I TCP PORTS 1 THRU 1023 ARE RESERVED
    EZZ0338I UDP PORTS 1 THRU 1023 ARE RESERVED
    SYSLOG

    0090 BPXF024I (OMVSKERN) Sep 19 10:23:18 inetd 65542 : FOMN0090 512
    0090 *:otelnet/tcp: socket: EDC5112I Resource temporarily unavailable.,
    0090 rsn=112B00B6
    0090 BPXF024I (OMVSKERN) Sep 19 10:23:18 inetd 65542 : FOMN0090 513
    0090 *:login/tcp: socket: EDC5112I Resource temporarily unavailable.,
    0090 rsn=112B00B6
    0090 VTAMAP10I Issuing "S TSO /* TIME SHARING OPTION */".

    ………………….

    0090 EZZ0162I HOST NAME FOR TCPIP IS ws445341
    0090 EZZ0300I OPENED PROFILE FILE DD:PROFILE
    0090 EZZ0309I PROFILE PROCESSING BEGINNING FOR DD:PROFILE
    0090 EZZ0655I PORT 8879 TCP BBODMGR IS ALREADY RESERVED
    0090 EZZ0655I PORT 7277 TCP BBODMGR IS ALREADY RESERVED
    0090 EZZ0655I PORT 9809 TCP BBODMGR IS ALREADY RESERVED
    0090 EZZ0655I PORT 9090 TCP BBODMGR IS ALREADY RESERVED
    0090 EZZ0655I PORT 9043 TCP BBODMGR IS ALREADY RESERVED
    0090 EZZ0655I PORT 5755 TCP BBODMNC IS ALREADY RESERVED
    0090 EZZ0655I PORT 5756 TCP BBODMNC IS ALREADY RESERVED
    0090 EZZ0316I PROFILE PROCESSING COMPLETE FOR FILE DD:PROFILE
    0090 EZZ0334I IP FORWARDING IS DISABLED
    0090 EZZ0338I TCP PORTS 1 THRU 1023 ARE RESERVED
    0090 EZZ0338I UDP PORTS 1 THRU 1023 ARE RESERVED
    0090 EZZ4202I Z/OS UNIX - TCP/IP CONNECTION ESTABLISHED FOR TCPIP
    0090 EZB6473I TCP/IP STACK FUNCTIONS INITIALIZATION COMPLETE.
    0090 EZAIN11I ALL TCPIP SERVICES FOR PROC TCPIP ARE AVAILABLE.
    0090 EZD1176I TCPIP HAS SUCCESSFULLY JOINED THE TCP/IP SYSPLEX GROUP EZBTCPCS
    …..
    0090 EZY6061I VMCF Start Accepted
    0090 EZY6011I VMCF Initialization Complete
    0090 IEF404I EZAZSSI - ENDED - TIME=09.23.35
    ….
    0090 GFSC284I NETWORK FILE SYSTEM CLIENT COULD NOT GET GSS CREDENTIALS 726
    0090 FOR THE NFS CLIENT : GSS API krb5_get_default_realm() FAILED
    0090 WITH GSS MAJOR STATUS 96C73ADF GSS MINOR STATUS 00000000
    0090 GFSC700I z/OS NETWORK FILE SYSTEM CLIENT (HDZ1B1N) started. OA29432,
    0090 EZZ4313I INITIALIZATION COMPLETE FOR DEVICE ADM2ETP
    0090 EZZ4313I INITIALIZATION COMPLETE FOR DEVICE ADM1ETP
    0090 EZZ6003I TELNET LISTENING ON PORT 23
    0090 BPXI004I OMVS INITIALIZATION COMPLETE
    0090 CEA0105I COMMON EVENT ADAPTER IS RUNNING IN MINIMUM MODE. 572
    0090 UNIX SYSTEM SERVICE UNLINK ENDED WITH RETURN CODE 0000006F
    0090 REASON CODE EF086015
    0281 ICH408I USER(CEA ) GROUP(SYS1 ) NAME(####################) 571
    0281 /var/CEAServer CL(DIRACC ) FID(00000001000000010000000000000000)
    0281 INSUFFICIENT AUTHORITY TO UNLINK
    0281 ACCESS INTENT(-W-) ACCESS ALLOWED(OTHER R-X)
    0281 EFFECTIVE UID(0000009002) EFFECTIVE GID(0000000000)
    0090 ISF728I SDSF parameters have been activated.
    JosephButler


  • 4.  Re: Another Scenario 4 Networking Issue

    Posted Mon September 19, 2011 01:22 PM
    This all looks good. Could the default router be down. Can you ping 10.86.43.1?

    RDz_John
    RDzJohn


  • 5.  Re: Another Scenario 4 Networking Issue

    Posted Mon September 19, 2011 01:27 PM
    RDzJohn Thanks, I did't think it looked that bad. Will check default routher later today - any other tests I can run.

    Jay
    JosephButler


  • 6.  Re: Another Scenario 4 Networking Issue

    Posted Mon September 19, 2011 01:30 PM
    Other than the physical network being down, or the default router not working (verify by pinging it,) this one has me stumped. If you are convinced everything else is working, you could put a packet sniffer on the network and see exactly whats going on. You'll need one of your network guys to help you as I am not an expert in that area.

    RDz_John
    RDzJohn


  • 7.  Re: Another Scenario 4 Networking Issue

    Posted Mon September 19, 2011 03:06 PM
    RDzJohn, ran PINGS on the default router from XP and LINUX and then TSO and they all worked

    -bash-3.2$ ping 10.86.43.1
    PING 10.86.43.1 (10.86.43.1) 56(84) bytes of data.
    64 bytes from 10.86.43.1: icmp_seq=1 ttl=255 time=1.01 ms
    64 bytes from 10.86.43.1: icmp_seq=2 ttl=255 time=0.879 ms

    TSO PING 10.86.43.1
    CS V1R11: Pinging host 10.86.43.1
    Ping #1 response took 0.005 seconds.

    Other questions:
    Why does a TSO ping to itself (10.86.43.218) work?
    How does the TSO NSLOOKUP get out to the named server to find Google?
    RACF caused some sort of problem (all changes mase by IBMUSER)?
    Some sort of firewall in the way problem?
    How come ifconfig can't see another eth like eth1 (OSA majic hiding that)

    Will see what the network perople have to say if they will talk to me.

    Thanks again.
    Jay

    ALSO ran some other pings and NETSTATS for good measure,
    TSO PING 127.0.0.1
    -bash-3.2$ ping 127.0.0.1
    PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
    64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.024 ms

    CS V1R11: Pinging host 127.0.0.1
    Ping #1 response took 0.001 seconds.

    -bash-3.2$ ping 10.84.43.0
    PING 10.84.43.0 (10.84.43.0) 56(84) bytes of data.
    64 bytes from 10.80.4.182: icmp_seq=1 ttl=244 time=70.9 ms
    64 bytes from 10.80.4.182: icmp_seq=2 ttl=244 time=71.1 ms

    TSO PING 10.86.43.0
    CS V1R11: Pinging host 10.86.43.0
    Ping #1 timed out
    TSO NETSTAT DEV - the eth1 part
    EZZ2760I DevName: ADM2ETP DevType: MPCIPA
    EZZ2766I DevStatus: Ready CfgRouter: Non ActRouter: Non
    EZZ2761I LnkName: ETH2 LnkType: IPAQENET LnkStatus: Ready

    EZZ2762I Speed: 0000001000
    EZZ2764I IpBroadcastCapability: No
    EZZ2767I ArpOffload: Yes ArpOffloadInfo: Yes
    EZZ2821I ActMtu: 1492
    EZZ2822I VLANid: None VLANpriority: Disabled
    EZZ2823I ReadStorage: GLOBAL (4096K) InbPerf: Balanced
    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: Yes
    EZZ2812I Group RefCnt SrcFltMd
    EZZ2813I

    EZZ2814I 224.0.0.1 0000000001 Exclude
    EZZ2808I SrcAddr: None
    EZZ3080I Link Statistics:
    EZZ3081I BytesIn = 38635
    EZZ3082I Inbound Packets = 130
    EZZ3083I Inbound Packets In Error = 0
    EZZ3084I Inbound Packets Discarded = 0
    EZZ3085I Inbound Packets With No Protocol = 0
    EZZ3086I BytesOut = 1451
    EZZ3087I Outbound Packets = 11
    EZZ3088I Outbound Packets In Error = 0
    EZZ3089I Outbound Packets Discarded = 0

    EZZ2826I IPv4 LAN Group Summary
    EZZ2827I LanGroup: 00001
    EZZ2828I Name Status ArpOwner VipaOwner
    EZZ2829I ----

    EZZ2771I ETH2 Active ETH2 Yes
    EZZ2827I LanGroup: 00002
    EZZ2828I Name Status ArpOwner VipaOwner
    EZZ2829I ----

    EZZ2771I ETH1 Active ETH1 Yes

    EZZ2639I OSA-Express Network Traffic Analyzer Information:
    EZZ2664I No OSA-Express Network Traffic Analyzer interfaces are defined
    JosephButler


  • 8.  Re: Another Scenario 4 Networking Issue

    Posted Tue September 20, 2011 01:04 PM
    Some more questions about scenario 4 if anyone has a thought.

    The network people say that the IP address of zOS 10.86.43.218 is properly assigned but there is no evidence that it has "advertised" its availability. The only IP address active is for Linux 10.83.43.217.

    Should ifconfig have something like an eth1 supplying the IP Address of zOS 10.86.43.218? ifcofig shows only:

    eth0 Link encap:Ethernet HWaddr F0:DE:F1:00:29:6E
    inet addr:10.86.43.217 Bcast:10.86.43.255 Mask:255.255.255.0
    inet6 addr: fe80::f2de:f1ff:fe00:296e/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:377412 errors:0 dropped:0 overruns:0 frame:0
    TX packets:28985 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:10
    RX bytes:33384608 (31.8 MiB) TX bytes:5004595 (4.7 MiB)
    Memory:f2600000-f2620000

    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:40019 errors:0 dropped:0 overruns:0 frame:0
    TX packets:40019 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:11916815 (11.3 MiB) TX bytes:11916815 (11.3 MiB)

    tap0 Link encap:Ethernet HWaddr BA:E7:83:EC:AC:B8
    inet addr:10.1.1.1 Bcast:10.1.1.255 Mask:255.255.255.0
    inet6 addr: fe80::b8e7:83ff:feec:acb8/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:712 errors:0 dropped:0 overruns:0 frame:0
    TX packets:29 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:500
    RX bytes:42720 (41.7 KiB) TX bytes:7838 (7.6 KiB)

    I know about the wonderful majic of OSA sharing the Linux adapter but I have no network evidence that is is doing so for me.

    The Linux firewall is stopped.

    There is no firewall on the subnet.

    Any thoughts?

    Jay
    JosephButler


  • 9.  Re: Another Scenario 4 Networking Issue

    Posted Tue September 20, 2011 01:51 PM
    Jay,
    In your OSATRLE definitions, make sure the continuation characters - "X" are in column 72. You'll need to reipl after you change this.

    RDz_John
    RDzJohn


  • 10.  Re: Another Scenario 4 Networking Issue

    Posted Tue September 20, 2011 02:12 PM
    John, check that several times based on previous posts. This input area screws up the formatting but the member has no line numbers and as you can see the x is in col 72. The continued lines (PORTMAP) start in col 16.

    The ADM2ETP NETSTAT DEV displayed in my earlier posts appears to show weverthing was defined.

    How does OSA let the network now that 10.86.43.218 is available?
    Thansk for the idea?

    Jay

    EDIT USER.VTAMLST(OSATRL2) - 01.02 Columns
    ----+----1----+----2----+----3----+----4----+----5----+----6----+----7--
    ***************************** Top of Data ******************************
    -Warning- The UNDO command is not available until you change
    your edit profile using the command RECOVERY ON.
    OSATRL1 VBUILD TYPE=TRL
    OSATRL1E TRLE LNCTL=MPC,READ=(0400),WRITE=(0401),DATAPATH=(0402), X
    PORTNAME=ADM1ETP, X
    MPCLEVEL=QDIO
    OSATRL2E TRLE LNCTL=MPC,READ=(0404),WRITE=(0405),DATAPATH=(0406), X
    PORTNAME=ADM2ETP, X
    MPCLEVEL=QDIO
    JosephButler


  • 11.  Re: Another Scenario 4 Networking Issue

    Posted Fri September 23, 2011 03:43 PM
    Got a friend in Network to snoop on why I could not ping from RDzUT/zOS to the network or from the network to RDzUT/zOS.
    Eventually he got on the sub net router and said everything in the network looked fine (said the following was proof),

    root@ws445340 ~# tcpdump -ni eth0 host 10.46.75.115
    tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
    listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
    13:23:17.716995 IP 10.46.75.115 > 10.86.43.218: ICMP echo request, id 512, seq 57603, length 40
    13:23:23.043631 IP 10.46.75.115 > 10.86.43.218: ICMP echo request, id 512, seq 57859, length 40
    13:23:28.543525 IP 10.46.75.115 > 10.86.43.218: ICMP echo request, id 512, seq 58115, length 40
    13:23:34.043603 IP 10.46.75.115 > 10.86.43.218: ICMP echo request, id 512, seq 58371, length 40
    4 packets captured
    6 packets received by filter
    0 packets dropped by kernel
    root@ws445340 ~#

    We looked at the TCPPARMS(PROFILE) DEV, LINK, HOME, and ROUTE statements which were the following based on
    Scenario 4 Configuration Guide recommendations:

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

    He suggested I make the following change (ROUTE 10.1.1.0) because requests were getting misrouted.

    ROUTE 10.86.43.0 255.255.255.0 = ETH2 MTU 1492
    ROUTE 10.1.1.0 255.255.255.0 = ETH1 MTU 1492
    ROUTE DEFAULT 10.86.43.1 ETH2 MTU 1492

    Pings from RDzUT/zOS to the network or from the network to RDzUT/zOS work just fine now - the tunnel from Linux to zOS still work fine.

    Thanks for all your help.

    Some networks displays after the change follow:

    TSO NETSTAT GATE
    EZZ2350I MVS TCP/IP NETSTAT CS V1R11 TCPIP Name: TCPIP 18:19:31
    EZZ2635I Known gateways:
    EZZ2636I NetAddress FirstHop Link Pkt Sz Subnet Mask Subnet Value
    EZZ2637I
    ----
    -----------

    EZZ2638I Default 10.86.43.1 ETH2 1492 <none>
    EZZ2638I 10.0.0.0 <direct> ETH1 1492 0.255.255.0 0.1.1.0
    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

    TSO NETSTAT HOME
    EZZ2350I MVS TCP/IP NETSTAT CS V1R11 TCPIP Name: TCPIP 18:23:19
    EZZ2700I Home address list:
    EZZ2701I Address Link Flg
    EZZ2702I
    ---- ---
    EZZ2703I 10.1.1.2 ETH1 P
    EZZ2703I 10.86.43.218 ETH2
    EZZ2703I 127.0.0.1 LOOPBACK

    -bash-3.2$ route
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    10.86.43.0 * 255.255.255.0 U 0 0 0 eth0
    10.1.1.0 * 255.255.255.0 U 0 0 0 tap0
    169.254.0.0 * 255.255.0.0 U 0 0 0 eth0
    default R7V0PTR01-02_VL 0.0.0.0 UG 0 0 0 eth0
    -bash-3.2$

    -bash-3.2$ ifconfig
    eth0 Link encap:Ethernet HWaddr F0:DE:F1:00:29:6E
    inet addr:10.86.43.217 Bcast:10.86.43.255 Mask:255.255.255.0
    inet6 addr: fe80::f2de:f1ff:fe00:296e/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:1112367 errors:0 dropped:0 overruns:0 frame:0
    TX packets:73700 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:10
    RX bytes:97254613 (92.7 MiB) TX bytes:12908983 (12.3 MiB)
    Memory:f2600000-f2620000

    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:108641 errors:0 dropped:0 overruns:0 frame:0
    TX packets:108641 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:24931616 (23.7 MiB) TX bytes:24931616 (23.7 MiB)

    tap0 Link encap:Ethernet HWaddr 82:96:13:8E:BC:45
    inet addr:10.1.1.1 Bcast:10.1.1.255 Mask:255.255.255.0
    inet6 addr: fe80::8096:13ff:fe8e:bc45/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:13 errors:0 dropped:0 overruns:0 frame:0
    TX packets:30 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:500
    RX bytes:780 (780.0 b) TX bytes:7948 (7.7 KiB)
    JosephButler


Related Content