On Wednesday, 07/26/2006 at 11:09 MST, Tom Cluster <[EMAIL PROTECTED]> wrote: > Taking your advice, I've spoken with the network guy about this. (He > didn't laugh at me. He's an ex-mainframer and a good guy.)
An excellent pedigree! :-) > (As a side issue, when we do trace routes to the VSE guests that do > work, we get a timeout for the point where the packet is going > through VM TCP/IP. Is there something to turn on within VM TCP/IP to > allow it to respond to trace route commands to those machines for > which he provides proxy arp services?) No. Proxy ARP has limitations and that's one of them. Enter, stage right: The Right Good Honorable VSWITCH. Proxy ARP evil. Hates it. Haaaates it! > When I do NETSTAT GATE DEV HOME I see no difference between the > guests that do work and the one that doesn't. All of them have > "Flgs" of UHS. All the CTCAs are connected and the VSE IP stack is > up and running. > > You mention the OBEYFILE command, with MORETRACE IPDOWN. Where do I > do this? From MAINT? Is there something I must configure before i > can issue this command? Is it disruptive in any way to the users who > are successfully using TCPIP? (I've got CMS users and connections to > VSE and Linux guests that are working.) TRACE, MORETRACE, and NOTRACE are TCP/IP configuration statements. They can be issued dynamically with OBEYFILE (as with most other config statements). Look in the Planning book for the discussion of both OBEYFILE and the trace statements. You can also do things like NETSTAT OBEY MORETRACE IPDOWN and then NETSTAT OBEY NOTRACE IPDOWN. Alan Altmark z/VM Development IBM Endicott
