Matthew Thanks for the response.
There's a bit more detail in the NETSTAT GATE output than in the GATEWAY statement you showed us before and there is a possibly crucial difference in the hipersockets IQDIO1 entry which has managed to acquire a "1" in the third octet where you reported a "0" before. In your 11:04 pm post of Tues, Oct 17 2006, corrected in your 11:19 pm post. you provided the following: GATEWAY 10.0.0.0 = Z990CH41LNK1 1492 0.255.248.0 0.2.8.0 192.0.0.0 = IQDIO1 8192 0.255.255.0 0.0.0.0 DEFAULTNET 10.2.8.2 Z990CH41LNK1 1492 0 But the NETSTAT GATE (and NETSTAT ROUTE) indicates the following: GATEWAY 10.0.0.0 = Z990CH41LNK1 1492 0.255.248.0 0.2.8.0 10.2.12.103 = Z990CH41LNK1 1492 HOST 192.0.1.0 = IQDIO1 8192 0.255.255.0 0.0.0.0 192.0.1.68 = IQDIO1 8192 HOST DEFAULTNET 10.2.8.2 Z990CH41LNK1 1492 0 The "LOOPBACK" entry appears because of the following taken from the z/OS V1R8.0 Communications Server IP Configuration Reference manual - which appears, because of revision lines, first explicitly to be mentioned only in this level of the manual: <quote> 1.2.29 HOME ... The default LOOPBACK address of 127.0.0.1 is internally defined by the TCP/IP stack. If you try to define this LOOPBACK address, it is flagged as a duplicate entry. You can use a link_name value of LOOPBACK in the HOME list to define additional LOOPBACK addresses. No DEVICE or LINK statement is needed for LOOPBACK, and it cannot be started or stopped (LOOPBACK is always active). ... </quote> The "host" entry for 10.2.12.103 is not necessary since it is included in the address range specified by your network 10.2.8.0/mask 255.255.248.0 entry. Also the "host" entry for 192.0.1.68 is not necessary since it is included in the address range specified by your network 192.0.1.0/mask 255.255.255.0 entry. Once this is converted to a BEGINROUTES/ENDROUTES block, we should have the following: BEGINROUTES ROUTE 10.2.8.0/21 = Z990CH41LNK1 MTU 1492 ROUTE 10.2.12.103/32 = Z990CH41LNK1 MTU 1492 ROUTE 192.0.1.0/24 = IQDIO1 MTU 8192 ROUTE 192.0.1.68/32 = IQDIO1 MTU 8192 ROUTE DEFAULT 10.2.8.2 Z990CH41LNK1 MTU 1492 ENDROUTES As I mentioned above, the entries with "/32" are not necessary. I'm wondering whether these "/32" entries are present in order to support some mechanism which requires host entries to be present in the routing table. Thus they may have been added dynamically. If this BEGINROUTES/ENDROUTES block still does not work - with or without the "/32" entries, please post the results of the PING tests I described in an earlier post starting with router 10.2.8.2. As for the hipersockets interface, a PING to any and all of the partner hipersockets interfaces is the only PING test you need. When reading up on hipersockets, I noticed a claim that the hipersockets connections formed a sort-of virtual LAN. I'd be interested in whether a PING command such as 192.0.1.255 managed to elicit a response from each of the hipersockets partner interfaces. I suspect it won't as hipersockets connections probably don't mimic a LAN in all respects. Chris Mason ----- Original Message ----- From: "Matthew Stitt" <[EMAIL PROTECTED]> Newsgroups: bit.listserv.ibm-main To: <[email protected]> Sent: Tuesday, 24 October, 2006 4:34 PM Subject: Re: I love TCPIP (not!) Ok, sorry it has taken me a little while to respond. Here is the output from the NETSTAT GATE command: EZZ2350I MVS TCP/IP NETSTAT CS V1R7 TCPIP Name: TCPIP 14:32:15 EZZ2635I Known gateways: EZZ2636I NetAddress FirstHop Link Pkt Sz Subnet Mask Subnet Value 637I ---------- -------- ---- ------ ----------- ------ ------ EZZ2638I Defaultnet 10.2.8.2 Z990CH41 1492 <none> EZZ2638I 10.0.0.0 <direct> Z990CH41 1492 0.255.248.0 0.2.8.0 EZZ2638I 10.2.12.103 <direct> Z990CH41 1492 HOST EZZ2638I 127.0.0.1 <direct> LOOPBACK 65535 HOST EZZ2638I 192.0.0.0 <direct> IQDIO1 8192 0.255.255.0 EZZ2638I 192.0.1.68 <direct> IQDIO1 8192 HOST And here is the output from the NETSTAT ROUTE command: EZZ2350I MVS TCP/IP NETSTAT CS V1R7 TCPIP Name: TCPIP 14:34:07 EZZ2755I Destination Gateway Flags Refcnt Interface EZZ2756I ----------- ------- ----- ------ --------- EZZ2757I Default 10.2.8.2 UGS 000000 Z990CH41LNK1 EZZ2757I 10.2.8.0/21 0.0.0.0 US 000000 Z990CH41LNK1 EZZ2757I 10.2.12.103/32 0.0.0.0 UH 000000 Z990CH41LNK1 EZZ2757I 127.0.0.1/32 0.0.0.0 UH 000002 LOOPBACK EZZ2757I 192.0.1.0/24 0.0.0.0 US 000000 IQDIO1 EZZ2757I 192.0.1.68/32 0.0.0.0 UH 000000 IQDIO1 On Fri, 20 Oct 2006 01:01:41 +0200, Chris Mason <[EMAIL PROTECTED]> wrote: >Richard > >An excellent idea. > >Matthew > >Let me build on what Richard is suggesting, in effect, the purely pragmatic >approach to creating a BEGINROUTES/ENDROUTES block from your existing >GATEWAY statement. Proceed as follows: > >1. Set your system up with the working GATEWAY statement. >2. Issue NETSTAT GATE and note how the GATEWAY statement maps into the >output of this command. Note that <direct> under "FirstHop" is the >equivalent of the equal sign, "=", and <none> under "Subnet Mask" is the >equivalent of "0" >3. Issue NETSTAT ROUTE and note what appears. >4. Create the BEGINROUTES/ENDROUTES block from what you see in the NETSTAT >ROUTE output.You can ignore the "Flags" and "Refcnt" columns and you need to >interpret "0.0.0.0" under "Gateway" as an equal sign, "=". Also you'll need >to add the "MTU" keyword and value which, in fact, you can discover by using >the NETSTAT ROUTE DETAIL command. > >Perhaps you can let me know how I managed to give you the wrong information >concerning how to perform the transformation. > >If this isn't clear, please post the NETSTAT GATE and NETSTAT ROUTE output. > >Chris Mason > >----- Original Message ----- >From: "Richard Peurifoy" <[EMAIL PROTECTED]> >Newsgroups: bit.listserv.ibm-main >To: <[email protected]> >Sent: Thursday, 19 October, 2006 10:34 PM >Subject: Re: I love TCPIP (not!) > > >> Chris Mason wrote: >> >> > Matthew >> > >> > It worries me that you are testing with FTP which really isn't the place >to >> > start when you have problems. Much better is to use PING and, possibly, >take >> > a peek at the ARP tables. >> > >> >> Another thing to do is use NETSTAT to look at what is actually being used >by >> TCP/IP. >> >> NETSTAT GATE will show the routes formated similar to the GATEWAY >statments, >> while >> NETSTAT ROUTE will show them formated similar to the BEGINROUTES style. >> >> This will work weather you use either form of definition, or even for >routes >> from OMPROUTE >> or redirects if you allow them. >> >> Richard ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
