On Tuesday, 04/10/2007 at 12:39 AST, Hans Rempel <[EMAIL PROTECTED]> wrote: > Hi all. Sorry for the lengthy post. > > I have a problem trying to get SAG broker in VSE to talk to SAG broker on a > windows platform. For legacy reasons we wish to keep the environment the same > so there is NO VSE TCPIP stack involved. This does make it more complicated but > that is how it has/is been running in production for 4 years.
If it has been working, what changed? > 1) Is there some documentation/tools on reading QDIO traces to I can > analyze this captured trace? No. To get that level of help you need to open a PMR. > 2) Is there a trace I can setup to trace traffic leaving the VSWITCH to > the OSA card or trace certain channels (ports) on the OSA card? Currently one > LPAR uses 0,1,2 and the second LPAR using 3,4,5. The VSWITCH is monitored by > DTCVSW1 userid. You can trace the *VSWITCH* by putting a Linux guest on the VSWITCH with sniffer (promiscuous mode) authority and gather a TCPDUMP. You'll see all the traffic on *that* VSWITCH. Tracing the traffic leaving the OSA itself is done exactly as your network guys are doing - with sniffers. Beware that OSA port sharing enables the OSA to "short cut" the packets if it recognizes the destination MAC or IP address as belonging to the OSA. And you know how I am about providing pictures, IP addys, and subnet masks. I can't tell if the various hosts are [supposed to be] in the same subnet or not. I get sleepy when I read ankle-bone-leg-bone-hip-bone configuration descriptions, particularly where shared OSAs come into play. :-D Alan Altmark z/VM Development IBM Endicott
