Re: TCPIP4VSE and z/VM OSAX QDIO VSWITCH
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
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
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
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
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
Thanks to all who replied. Yes the problem was the NIC was not coupled to the VSWITCH. Up and running. Thanks again. Don
