Vic Cross wrote:
I had to do this once, but do you think I can remember how? :)
Either with NETSTAT CP or with SEND CP TCPIP ...
The first approach when your network colleagues are cooperative, the
second for when you rely on your VM Systems Programmer being helpful.
Rob
This past weekend we had our DR test, and while my linux guests came up
and could talk to each other on the GLAN, none could contact the vm
TCPIP router/gateway (or send traffic outside the virtual network). A
#CP Q NIC DETAILS from the linux guests showed TX Packets getting
discarded, presumably
G'day Daniel,
If there were no changes to PROFILE TCPIP, SYSTEM CONFIG or the directory
before the DR test, it would Just Work. I suspect that a change to one of
these snuck in, and either VM TCPIP had the wrong IP address (at the Guest
LAN interface) or the TCPIP machine was not attached to the
G'day Vic!
and either VM TCPIP had the wrong IP address (at the Guest
LAN interface)
In this case would the ping to the gateway ip address from
the outside have succeeded?
or the TCPIP machine was not attached to the Guest LAN.
For future reference... how would we reattach it :)?
They
Like I said, we
could ping the router from the outside, and none of the glan
guests from
the outside, and on the inside we could ping all the glan
guests but not
the vm tcpip router.
Was the OSA port you were using defined as PRIROUTER or SECROUTER? If
not, then you'd be able to get to the
On Monday, 07/26/2004 at 11:02 AST, Daniel Jarboe
[EMAIL PROTECTED] wrote:
They tried a:
DEFINE NIC 700 QDIO DEV 3
COUPLE 700 SYSTEM VMGLAN
from TCPMAINT, but I think it should have been done for TCPIP
instead. How would they have done that?
Use the NICDEF or SPECIAL statement in TCPIP's
On Mon, 26 Jul 2004, Daniel Jarboe wrote:
In this case would the ping to the gateway ip address from
the outside have succeeded?
It may well have -- at least it would on most Linux systems. Linux, for
example, will respond to a packet addressed to any of it's configured IP
addresses from any
