Re: TCPIP4VSE and z/VM OSAX QDIO VSWITCH

2006-05-31 Thread Hooker, Don - OIT
Oops... I forgot to include my TCPIP definition:

DEFINE LINK,ID=VM_TCPIP,TYPE=OSAX,DEV=(D00,D01),MTU=8192, - 
DATAPATH=D02,FRAGMENT=NO,PORTNAME=UNASSIGNED

(I also tried it with DEFINE ADAPTER 0).

TIA,
Don


Re: TCPIP4VSE and z/VM OSAX QDIO VSWITCH

2006-05-31 Thread Rich Smrcina
On Wednesday 31 May 2006 2:43 pm, Hooker, Don - OIT wrote:
   0S39I ERROR DURING OSA EXPRESS PROCESSING,REASON=0035
 
  CUU=0D00,RETCODE=E080
  0S02I A CANCEL OR CANCEL ALL MACRO WAS ISSUED
  0S00I SUB SPINCPU  CANCELED
 
  Alan Altmark wrote:

 Now *this* I can help with.  See that RETCODE?  I recognize it as an OSA

 reject code.  Those are documented in an appendix of the OSA/SF book.
 It
 means that:
 - a cable is not plugged into the port (both ends)
 - the port has been disabled by the Support Element
 - the port is not enabled on the physical switch

 Bottom line: The OSA is suffering from sensory deprivation of one form
 or
 another.





 Alan, this is a virtual NIC connected to a VSWITCH.  What could be
 unplugged?



 Do I need multiple DEFINE ADAPTER statements?

-- 
Rich Smrcina
VM Assist, Inc.
Main: (262)392-2026
Cell: (414)491-6001
Ans Service:  (360)715-2467
rich.smrcina at vmassist.com

Catch the WAVV!  http://www.wavv.org
WAVV 2007 - Green Bay, WI - May 18-22, 2007


Re: TCPIP4VSE and z/VM OSAX QDIO VSWITCH

2006-05-31 Thread Rich Smrcina
Don,

You defined the NIC, but that's only part of the story.  The NIC needs to be 
coupled to the VSwitch (plugged in).  Use the NICDEF statement in the 
directory:

NICDEF D00 TYPE QDIO LAN SYSTEM vswitchname

On Wednesday 31 May 2006 2:43 pm, Hooker, Don - OIT wrote:
   0S39I ERROR DURING OSA EXPRESS PROCESSING,REASON=0035
 
  CUU=0D00,RETCODE=E080
  0S02I A CANCEL OR CANCEL ALL MACRO WAS ISSUED
  0S00I SUB SPINCPU  CANCELED
 
  Alan Altmark wrote:

 Now *this* I can help with.  See that RETCODE?  I recognize it as an OSA

 reject code.  Those are documented in an appendix of the OSA/SF book.
 It
 means that:
 - a cable is not plugged into the port (both ends)
 - the port has been disabled by the Support Element
 - the port is not enabled on the physical switch

 Bottom line: The OSA is suffering from sensory deprivation of one form
 or
 another.





 Alan, this is a virtual NIC connected to a VSWITCH.  What could be
 unplugged?



 Do I need multiple DEFINE ADAPTER statements?

-- 
Rich Smrcina
VM Assist, Inc.
Main: (262)392-2026
Cell: (414)491-6001
Ans Service:  (360)715-2467
rich.smrcina at vmassist.com

Catch the WAVV!  http://www.wavv.org
WAVV 2007 - Green Bay, WI - May 18-22, 2007


Re: TCPIP4VSE and z/VM OSAX QDIO VSWITCH

2006-05-31 Thread Neale Ferguson








You defined the NICs but did you COUPLE
them to the VSWITCH? 















Alan, this is a virtual NIC connected to a VSWITCH.
What could be unplugged?



Do I need multiple DEFINE ADAPTER
statements?





















Re: TCPIP4VSE and z/VM OSAX QDIO VSWITCH

2006-05-31 Thread Alan Altmark
On Wednesday, 05/31/2006 at 03:43 AST, Hooker, Don - OIT 
[EMAIL PROTECTED] wrote:
 Alan, this is a virtual NIC connected to a VSWITCH.  What could be 
unplugged?
 
 Do I need multiple DEFINE ADAPTER statements?

As others have said, the virtual NIC is not COUPLEd to the VSWITCH.  Their 
advice on how to fix it is good.  (Sorry I didn't pay attn to the VSWITCH 
part of the problem.)

Alan Altmark
z/VM Development
IBM Endicott


Re: TCPIP4VSE and z/VM OSAX QDIO VSWITCH

2006-05-31 Thread Hooker, Don - OIT








Thanks to all who replied. Yes the problem was the NIC was
not coupled to the VSWITCH.



Up and running.



Thanks again.

Don








TCPIP4VSE and z/VM OSAX QDIO VSWITCH

2006-05-24 Thread Hooker, Don - OIT








FINALLY we are licensed to run TCPIP4VSE!



We are trying to get it to get to the network via a virtual
NIC TYPE QDIO associated with a

VSWITCH under z/VM 5.2.



However, I cant get it to initialize. 



I did upgrade TCPIP to 1.5E on our VSE/ESA 2.62 systems.




Here are some definitions:

In the VM directory entry for the VSE guest:



nicdef D00 type QDIO dev 3 lan system dtcvsw1



In the VSE IPL proc:



ADD D00:D02,OSAX,EML (I had 1st tried
it w/o the ,EML  same results)



In VM SYSTEM CONFIG:



Define vswitch dtcvsw1 rdev b000 c000 connect controller
dtcvsw1, 

 IP vlan
unaware




In IPINITxx.L:



DEFINE LINK,ID=VM_TCPIP,TYPE=OSAX,DEV=(D00,D01),MTU=8192,
- 

DATAPATH=D02,IPADDR=172.30.8.53,FRAGMENT=NO,PORTNAME=UNASSIGNED



(Should the IP address used here be the same as VSEs
IP address?).



When TCP4VSE comes up, I get:



T1 0137 IPN631I Control has been passed to the TCP/IP
engine 

T1 0137 0001: IPL605E Unable to Initialize IJBOSA, return
code: 1 

T1 0137 0001: IPL609E Unable to initialize OSA Express,
Link: VM_TCPIP

AR 0014 0P27I I UNKNWN DEV
SYSXXX=D00



CCSW=06CB280E000100
CCB=00


 SNS=
8200




I opened an ETR with IBM and they referred me to a couple of
APARS but they do not seem applicable.



Any ideas? Do the definitions look correct? I
cant find the return code for IPL605E anywhere.

Does anyone know what it means? (Leo?)



Thanks in advance,

Don Hooker