The only difference I see is that I have a port name in z/VM that i do not
have in z/OS. But the z/OS that works does not have a port name specified
either.
*q lan tstlan details*
LAN SYSTEM TSTLAN Type: HIPERS Connected: 2 Maxconn: INFINITE
PERSISTENT UNRESTRICTED IP MFS: 16384 Accounting: OFF
Adapter Owner: TCPIP NIC: 0720 Name: *IT2TA*
RX Packets: 151 Discarded: 0 Errors: 0
TX Packets: 169 Discarded: 833 Errors: 0
RX Bytes: 9644 TX Bytes: 9637
Device: 0722 Unit: 002 Role: DATA
Options: Broadcast Multicast IPv4 VLAN
Unicast IP Addresses:
10.6.0.4 MAC: 02-00-00-00-00-05
199.44.nnn.nn MAC: 02-00-00-00-00-05
Multicast IP Addresses:
224.0.0.1 MAC: 01-00-5E-00-00-01
Adapter Owner: ZOS19 NIC: 0724 Name: *IUTIQDFF*
RX Packets: 169 Discarded: 0 Errors: 0
TX Packets: 151 Discarded: 0 Errors: 0
RX Bytes: 9637 TX Bytes: 9644
Device: 0726 Unit: 002 Role: DATA
Options: Broadcast Multicast IPv4 VLAN
Unicast IP Addresses:
10.6.0.5 MAC: 02-00-00-00-00-06
Multicast IP Addresses:
224.0.0.1 MAC: 01-00-5E-00-00-01
On Mon, May 12, 2008 at 12:55 PM, Brian Nielsen <[EMAIL PROTECTED]>
wrote:
> On Mon, 12 May 2008 10:47:39 -0400, Mark Pace <[EMAIL PROTECTED]> wrote:
>
> >I created a Hipersockets VLAN.
> >I stopped the interface in TCPIP, detached the real hipersockets, define
> d
> a
> >NIC and coupled it to the VLAN.
> >I did the same on the z/OS guest, (which required an IPL, the devices we
> re
> >still active after stopping the adapter, VTAM?) and now the z/VM on the
>
> VLAN
> >and the z/OS on the VLAN can talk to one another.
> >So it's either a real hardware issue, doubtful, or some interaction
> between
> >z/VM and z/OS.
> >I haven't found any hits searching IBMLink.
>
> With this connection functioning do a Q LAN DETAILS on the hipersocket LA
> N
> to double check that the IP address of your z/OS guest is what you expect
>
> it to be, and that it's not VLAN tagged differently or a different PORT
>
> name than what you're doing with the other stacks on the real hipersocket
> .
>
> Also, from the z/OS guest what, if any, differences show in various
> display command outputs from when it was connected to the real
> hipersocket? What about differences in the JES log for the TCPIP stack?
>
> As an aside, you could have avoided removing your VM TCPIP's connection t
> o
> the real hipersocket by bringing up a second version of it connected to
>
> the hipersocket LAN. Another option would have been to connect your VM
>
> TCPIP stack to both the real hipersocket and the hipersocket LAN.
>
> Brian Nielsen
>
>
--
Mark Pace
Mainline Information Systems
