Thanks to all who replied. Yes the problem was the NIC was
not coupled to the VSWITCH.
Up and running.
Thanks again.
Don
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
adv
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?
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
On Wednesday 31 May 2006 2:43 pm, Hooker, Don - OIT wrote:
> > > 0S39I ERROR DURING OSA EXPRESS PR
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 th
> > 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
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
On Thursday, 05/25/2006 at 08:21ZE10, Ivica Brodaric
<[EMAIL PROTECTED]> wrote:
> Message 0P27I says that VSE does not recognize the device at address
> D00, which means that either VSE's driver for OSA Express (which comes
> from IBM, not CSI) needs service or there's something that NICDEF does
>
Message 0P27I says that VSE does not recognize the device at address
D00, which means that either VSE's driver for OSA Express (which comes
from IBM, not CSI) needs service or there's something that NICDEF does
that VSE 2.6 doesn't understand.
Try using good old SPECIAL (e.g. SPECIAL D00 QDIO 3 S
On Wednesday, 05/24/2006 at 02:55 AST, "Hooker, Don - OIT"
<[EMAIL PROTECTED]> wrote:
> 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 VSE?s IP address?).
That *is* V
Thanks for all the replies so far.
Yes the VSE is authorized to use the VSWITCH. The
grant is issued by AUTOLOG1.
There is no port name (Alan Altmark recommended not
specifying a name when we first started setting it up on
VM.
I tried the DEFINE ADAPTER with no better results
Do you
have something like this in your SYSTEM CONFIG? or you could enter the commands
manually.
DEFINE
VSWITCH VSWITCH1 RDEV D00 D01 D02 CONTR * IP IPT 5 NONROUTER
MODIFY VSWITCH VSWITCH1 GRANT VSEA
and have
DTCVSW1 configued and IPL'd
If you
do a Q VSWITCH what do you see?
-O
12 matches
Mail list logo
