On Tuesday, 07/11/2006 at 02:33 MST, Tom Cluster <[EMAIL PROTECTED]> wrote: > We have three VSE virtual machines which use TCP/IP in VM as their > gateway, connected via virtual ctca's. The IP stacks are working > correctly in two of the guests, but not in the third. It previously > worked and no changes have been made.
LOL! *Something* changed! > I can see nothing wrong from > the guest's point-of-view. It comes up as if full IP connectivity is > there, but it's not reachable from the outside nor can it reach the > outside. This suggests to me that the connection between VSE and VM > is working fine but that the gateway function in VM TCP/IP is down > for this one IP address. I can't easily bounce the VM TCP/IP machine > because others are using it. It suggests to me a routing problem, not a problem in VM TCP/IP. If you didn't change the host or the hardware, then the network has changed. You will have to ask the network techs to do their thing and find out for you where the problem is. Double check that NETSTAT GATE DEV HOME (or ifconfig on newer systems) shows you what you expect to see (i.e. what it showed when it worked correctly). It is most likely that the packets for the 3rd guest are being routed outbound, but the responses aren't coming back. > There must be some diagnostic commands to help figure out what's > going on, but when I look at the TCP/IP Planning and Customization > Manual I'm not finding them. How can I proceed? The diagnostic commands are tracerte, ping, and netstat/ifconfig. You can OBEYFILE a MORETRACE IPDOWN to watch the stack in action for packet transmission, but if NETSTAT GATE DEV HOME is good, call up the network elves to have them do their magic. Don't forget to tell them how you didn't change anything. They will laugh, of course, but let it pass and stay the course. ;-) Alan Altmark z/VM Development IBM Endicott
