On Monday, 01/14/2008 at 02:36 EST, [EMAIL PROTECTED] wrote: > i shut down all my VSE stacks, then shutdown VM's TCPIP > and restarted all the stacks just like we do at system startup. > still cannot reach the problem VSE. > > the COUPLEs are all in place, so what else can be missing?
In a previous post you said: > i see this for the problem vse: > Device SP9D Type: CTC Status: Ready > Queue size: 0 CPU: 0 Address: 0C06 > Link SP9 Type: CTC Net number: 0 > BytesIn: 0 BytesOut: 0 > Forwarding: Enabled > Broadcast Capability: Yes > Multicast Capability: Yes > Group Members > ----- ------- > 224.0.0.1 1 > > Device SP9DA Type: CTC Status: Ready > Queue size: 0 CPU: 0 Address: 0D06 > Link SP9A Type: CTC Net number: 0 > BytesIn: 130196 BytesOut: 0 > Forwarding: Enabled > Broadcast Capability: Yes > Multicast Capability: Yes > Group Members > ----- ------- > 224.0.0.1 1 I see two devices with the same device address (D06) and both are showing Ready. I don't understand that. The output of "ifconfig -a" will be much easier to consume, but we can live with the complete output of "NETSTAT DEV HOME GATE" if we must. If you have physical connectivity. That is, if the links are up with no errors, then the problem isn't physical. Subnet mask issues and lost gateway entries come to mind. The fact that you rebooted all the affected guests and still have the same problem supports this conclusion. You need to look at the VSE equivalent of ifconfig or NETSTAT DEV HOME GATE to ensure that it matches what you see on VM TCP/IP. I take it that you cannot ping the VSE guest from VM? Try TRACERTE and see what it says. Alan Altmark z/VM Development IBM Endicott
