What I was leading to is, 'Do you have a routing problem?'. If the PC you are having problems with is multi-homed and is on both your regular Intranet and the ICC subnet, perhaps the operator messed up the multi-homing and your tm3270 session is going through the wrong connection.
If your ICC subnet connects into the rest of your Intranet, perhaps the operator did something to mess up that routing. I don't know much about this, except some reading towards (hopefully) getting a z9, so these are mostly guesses. Peter -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of James M Sent: September 10, 2007 15:24 To: [email protected] Subject: Re: z/VM 5.2 ICC console connection problems the icc is on the same subnet as the bad pc. I will scream if this turns out to be a windows problem here's a trace of two seperate tn3270 icc connection failures. notice two different errors before the "terminating session"... any socket programmers out there willing to looks at the trace... [15:04:26.671] [1] Tracing has been enabled [15:04:26.671] Starting program. Mon Sep 10 15:04:26 2007 Switches '-p "C:\Documents and Settings\Terminal User\Application Data\Hummingbird\Connectivity\9.00\Profile\syjim.hep"' [15:04:26.671] Program Description: "HostExplorer for Win32", Version: 9.0.0.0, Ansi CodePage: 1252 [15:04:26.671] Windows 2000 5.0 (Internal 3)(Build 2195) "Service Pack 4" OEM ID 0, Processors 1, ProcessorType 586 [15:04:31.531] [1] Switched into NVT mode [15:04:31.546] [1] WinSock Initialized. Version 1.1 [15:04:31.546] [1] WinSock Description: "WinSock 2.0", Status: "Running" [15:04:31.546] [1] Socket Close. Rc: -1 [15:04:31.546] [1] Resolved 192.207.28.160 to: 192.207.28.160, Port 23 [15:04:56.046] [1] NVT terminal type mode [15:04:56.062] [1] Socket Recv., Rc: 3, WSA Rc 0, Input Size 1024 [15:04:56.062] [1] Recv completed. Data follows: FF FD 28 [15:04:56.062] [1] Blocking Receive events... [15:04:56.062] [1] Got DO TN3270E [15:04:56.062] [1] Reply WILL TN3270E [15:04:56.062] [1] Socket Send. Sending 3 bytes, Rc: 3. WSA Rc: 0 [15:04:56.062] [1] Send completed. Data follows: FF FB 28 [15:04:56.062] [1] Unblocking Receive events... [15:04:56.062] [1] Socket Recv., Rc: -1, WSA Rc 10053, Input Size 1024 [15:04:56.078] [1] Terminating Session [15:04:56.078] [1] Socket Close. Rc: 0 [15:06:59.968] [1] Tracing has been disabled [15:07:05.078] [1] Tracing has been enabled [15:07:11.921] [1] Switched into NVT mode [15:07:11.937] [1] WinSock Initialized. Version 1.1 [15:07:11.937] [1] WinSock Description: "WinSock 2.0", Status: "Running" [15:07:11.937] [1] Socket Close. Rc: -1 [15:07:11.937] [1] Resolved 192.207.28.160 to: 192.207.28.160, Port 23 [15:07:36.437] [1] NVT terminal type mode [15:07:36.453] [1] Socket Recv., Rc: 3, WSA Rc 0, Input Size 1024 [15:07:36.453] [1] Recv completed. Data follows: FF FD 28 [15:07:36.453] [1] Blocking Receive events... [15:07:36.453] [1] Got DO TN3270E [15:07:36.453] [1] Reply WILL TN3270E [15:07:36.453] [1] Socket Send. Sending 3 bytes, Rc: 3. WSA Rc: 0 [15:07:36.453] [1] Send completed. Data follows: FF FB 28 [15:07:36.453] [1] Unblocking Receive events... [15:07:36.453] [1] Socket Recv., Rc: 0, WSA Rc 0, Input Size 1024 [15:07:36.453] [1] Terminating Session [15:07:36.453] [1] Socket Close. Rc: 0 I'm particularly interested in WSA Rc 10053 and also why on the second failure the rc = 0 -Jim hummingbird host explorer emulator On 9/10/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Is this PC multi-homed? Does your ICC Intranet have a connection to your > regular Intranet? > > -----Original Message----- > From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On > Behalf Of James M > Sent: September 10, 2007 14:21 > To: [email protected] > Subject: Re: z/VM 5.2 ICC console connection problems > > I get various results > sometimes I get no error > sometimes I get unable to connect to host > some times unable to find host/gateway > > I have another backup pc that is able to connect to the ICC > ...and on the pc that cannot connect to the icc I am able to connect > to vm's tcpip > very weird...don't know what to do > > diagnostics on the icc shows no errors > ibm ce is here now also scratching his head. (he also accidently > varied off the wrong chpid bringing down my whole ip network). > -Jim > > On 9/10/07, Ivica Brodaric <[EMAIL PROTECTED]> wrote: > > Then it's likely not a card but a network problem. Asymmetric routing > maybe? > > Do you get any errors when you try to connect? > > > > On 11/09/2007, James M < [EMAIL PROTECTED]> wrote: > > > ping works! > > > > > > On 9/10/07, Ivica Brodaric < [EMAIL PROTECTED]> wrote: > > > > That should be OK. Try to ping the IP address from the PC. Do > traceroute > > if > > > > you can't ping. > > > > > > > > > > > > On 11/09/2007, James M < [EMAIL PROTECTED]> wrote: > > > > > I do not have access to all the os's that run in each lpar so I > did > > > > > everything from the HMC. > > > > > I higlighted each image one by one and configured the channel > path > > off. > > > > > I again highlighted each image and this time configured the > channel > > > > online. > > > > > FYI - the only image that is actually using the ICC chpid is the > vm > > > > > 5.2 system which I do have access to. > > > > > -jim > > > > > On 9/10/07, Ivica Brodaric <[EMAIL PROTECTED]> wrote: > > > > > > Let's be clear. On all LPARs: > > > > > > > > > > > > CP VARY OFF PATH xx FROM ALL > > > > > > CP VARY OFF CHPID xx > > > > > > > > > > > > Then on each LPAR: > > > > > > > > > > > > CP VARY ON CHPID xx > > > > > > > > > > > > Did you do that? > > > > > > > > > > > > > > > > > > On 11/09/2007, James M < [EMAIL PROTECTED]> wrote: > > > > > > > OK thanks. I varied all off first and the all on. > > > > > > > I saw all the devices go off and come back online on operx. > > > > > > > ...but it didn't help - I still cannot connect from the pc > to the > > icc > > > > > > port. > > > > > > > I did enable the console cuu before trying. > > > > > > > > > > > > > > On 9/10/07, Ivica Brodaric < [EMAIL PROTECTED]> > wrote: > > > > > > > > Yes. It has to be offline to all LPARs in order to reset > itself. > > > > > > > > > > > > > > > > > > > > > > > > On 11/09/2007, James M < [EMAIL PROTECTED]> wrote: > > > > > > > > > maybe we're getting someplace. > > > > > > > > > are you suggesting that I have to config path off in all > the > > lpars > > > > and > > > > > > > > > then config it on in all? > > > > > > > > > what I did was off/on in lpar 1 - off/on lpar2 and so > on. > > > > > > > > > > > > > > > > > > > > > > > > > > > On 9/10/07, Ivica Brodaric < [EMAIL PROTECTED]> > wrote: > > > > > > > > > > Did you vary it offline from all LPARs at the same > time? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 11/09/2007, James M < [EMAIL PROTECTED]> wrote: > > > > > > > > > > > I did try toggling the chpid off/on in each of the > lpars > > but > > > > I'm > > > > > > not > > > > > > > > > > > sure it worked properly. > > > > > > > > > > > it went from online/online to online/standby. I > never did > > see > > > > the > > > > > > > > > > > current state go to offline! > > > > > > > > > > > > > > > > > > > > > > On 9/10/07, Rich Smrcina < [EMAIL PROTECTED] > > wrote: > > > > > > > > > > > > Resetting the ICC port will only affect the ICC > users, > > if > > > > most > > > > > > of > > > > > > > > your > > > > > > > > > > > > users are coming in through VM's TCP/IP stack, > it's not > > > > using > > > > > > the > > > > > > > > ICC. > > > > > > > > > > > > If only your console or datacenter users use the > ICC, > > you > > > > can > > > > > > reset > > > > > > > > it > > > > > > > > > > > > without affecting your users. > > > > > > > > > > > > > > > > > > > > > > > > James M wrote: > > > > > > > > > > > > > device shows enabled. > > > > > > > > > > > > > I cannot reset the port on the hmc since it's a > dual > > port > > > > card > > > > > > > > (icc & > > > > > > > > > > > > > tcpip) and that would mean dropping many vm & os > > telnet > > > > > > clients. > > > > > > > > > > > > > > > > > > > > > > > > > > On 9/10/07, David Kreuter < > [EMAIL PROTECTED] > > > > > > > wrote: > > > > > > > > > > > > >> > > > > > > > > > > > > >> > > > > > > > > > > > > >> from the hmc try resetting the OSA port at the > chpid > > > > level. > > > > > > > > > > > > >> David > > > > > > > > > > > > >> > > > > > > > > > > > > >> __________________________ ____ __ > > > > > > > > > > > > >> From: The IBM z/VM Operating System on behalf > of > > James M > > > > > > > > > > > > >> Sent: Mon 9/10/2007 10:47 AM > > > > > > > > > > > > >> To: [email protected] > > > > > > > > > > > > >> Subject: [IBMVM] z/VM 5.2 ICC console > connection > > problems > > > > > > > > > > > > >> > > > > > > > > > > > > >> > > > > > > > > > > > > >> > > > > > > > > > > > > >> > > > > > > > > > > > > >> Over the weekend an operator "I did > something..I > > don't > > > > know > > > > > > what" > > > > > > > > > > that > > > > > > > > > > > > >> has rendered the ICC vm console unusable. > > > > > > > > > > > > >> I tried disable/enable cuu, vary off/on path to > cuu > > and > > > > > > dropping > > > > > > > > the > > > > > > > > > > > > >> session from the HMC ICC utilities menu all to > no > > avail. > > > > > > > > > > > > >> Can someone please suggest other possible > solutions. > > > > Thanks > > > > > > > > > > > > >> -Jim > > > > > > > > > > > > >> > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > Rich Smrcina > > > > > > > > > > > > VM Assist, Inc. > > > > > > > > > > > > Phone: 414-491-6001 > > > > > > > > > > > > Ans Service: 360-715-2467 > > > > > > > > > > > > rich.smrcina at vmassist.com > > > > > > > > > > > > http://www.linkedin.com/in/richsmrcina > > > > > > > > > > > > > > > > > > > > > > > > Catch the WAVV! http://www.wavv.org > > > > > > > > > > > > WAVV 2008 - Chattanooga - April 18-22, 2008 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review retransmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error please contact the sender and delete the material from any computer. The integrity and security of this message cannot by guaranteed on the Internet. The Sender accepts no liability for the content of this e-mail or for the consequences of any actions taken on basis of the information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is the property of the TTC and must not be altered or circumvented in any manner. > The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review retransmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error please contact the sender and delete the material from any computer. The integrity and security of this message cannot by guaranteed on the Internet. The Sender accepts no liability for the content of this e-mail or for the consequences of any actions taken on basis of the information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is the property of the TTC and must not be altered or circumvented in any manner.
