Hi Dennis
Thanks for your reply. Below are details of the different cp commands that you
requested:
----------------
CP QUERY CPLEVEL
z/VM Version 4 Release 2.0, service level 0000 (64-bit)
Generated at 08/29/01 18:40:17 EST
IPL at 11/20/02 10:42:05 EST
CP QUERY VMLAN
VMLAN general activity:
PERSISTENT Limit: INFINITE Current: 1
TRANSIENT Limit: INFINITE Current: 1
CP QUERY NIC DETAIL
Adapter 0960 Type: QDIO Name: UNASSIGNED Devices: 3
Port 0 MAC: 00-04-AC-00-00-0A LAN: SYSTEM LNXLAN02 MFS: 16384
Connection Name: HALLOLE State: Startup
Device: 0960 Unit: 000 Role: CTL-READ
Unassigned Devices:
Device: 0961 Unit: 001 Role: Unassigned
Device: 0962 Unit: 002 Role: Unassigned
Adapter 0963 Type: HIPER Name: UNASSIGNED Devices: 3
Port 0 MAC: 00-04-AC-00-00-0C LAN: SYSTEM LNXLAN02 MFS: 16384
Connection Name: HALLOLE State: Session Established
Device: 0964 Unit: 001 Role: CTL-READ
Device: 0965 Unit: 002 Role: CTL-WRITE
Device: 0963 Unit: 000 Role: DATA
CP QUERY LAN LNXLAN02 OWNER SYSTEM DETAIL
LAN SYSTEM LNXLAN02 Type: QDIO Active: 4 MAXCONN: INFINITE
PERSISTENT UNRESTRICTED MFS: 16384
Adapter Owner: RATATOSK NIC: 0960 Name: UNASSIGNED
Adapter Owner: TCPIP NIC: 0960 Name: LNXLAN02
<AN_IP_ADDRESS>
Adapter Owner: URD NIC: 0960 Name: UNASSIGNED
Adapter Owner: URD NIC: 0963 Name: UNASSIGNED
----------------
The guest linux that I am currently working with is named "URD".
--
Best regards,
Jxrgen Birkhaug
Quoting Dennis Musselwhite <[EMAIL PROTECTED]>:
> Hi...
>
> I think your chandev.conf file is OK (but I am no expert on driver
> configuration).
>
> The IDX Termination code 0x17 usually means that the data device could not
> be found,
> or it belongs to a different adapter.
>
> If you can access the primary 3270 virtual console where you logon and IPL
> your Linux
> system, there are some CP commands that might provide more insight:
>
> (1) What version of CP are you running? Enter:
>
> CP QUERY CPLEVEL
>
> I would expect to see something like this:
>
> z/VM Version 4 Release 2.0, service level 0000 (64-bit)
> Generated at 10/28/02 14:32:45 EST
> IPL at 10/30/02 12:04:46 EST
>
> If you get an error message instead, then you may need to use a different
> method to
> enter CP commands. CP is the layer that runs between your Linux system and
> the
> real machine. One way to enter a CP command is:
> Signal PA1 (Programmed Attention 1) from your telnet-3270 client.
> This
> should put your session in CP READ status (displayed in the lower
> right corner of the 3270 session). The command that you enter
> in CP READ status goes directly to CP. Depending on your virtual
> machine settings, you may go back to a VM status after each command.
> If that is the case, you will need to signal PA1 before each command.
> If you STAY in CP READ after each command, enter "CP BEGIN" after
> the last command to get your virtual machine running again.
>
> (2) What level of VM Guest LAN service has been installed? Enter:
>
> CP QUERY VMLAN
>
> (3) How is your adapter defined? Enter:
>
> CP QUERY NIC DETAIL
>
> (4) How is the LAN defined? Not relevent to this problem, but for future
> reference,
> your adapter at 0960 may indicate it is connected to a LAN identified by
> two tokens.
> The first is the ownerid, the second is the lanname. If (for example)
> ownerid = SYSTEM
> and lanname = LNXLAN02 then you could find out who is currently connected
> to that
> LAN with the command:
>
> CP QUERY LAN LNXLAN02 OWNER SYSTEM DETAIL
>
> (4) Don't forget to enter CP BEGIN if you are still in CP READ status.
>
>
> Please post the results.
>
> Regards,
> Dennis Musselwhite ([EMAIL PROTECTED])
> IBM Corporation -- z/VM Development -- CP Network Simulation
>
>
> Jxrgen Birkhaug <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 11/29/2002 08:31:00
> AM
>
> Please respond to Linux on 390 Port <[EMAIL PROTECTED]>
>
> Sent by: Linux on 390 Port <[EMAIL PROTECTED]>
>
>
> To: [EMAIL PROTECTED]
> cc:
> Subject: [LINUX-390] HiperSockets and Guest LAN
>
>
>
> Hi
>
> I'm having problems setting getting my qeth interface to work running on a
> virgin 2.4.19 kernel patched with the may 2002 stream.
>
> I suspect that it might be a problem with chandev and syntax, and I have
> been screwing around with chandev for some time but to no avail.
>
> insmod qeth returns:
>
> ------
> IPv6 v0.8 for NET4.0
> IPv6 over IPv4 tunneling driver
> 802.1Q VLAN Support v1.7 Ben Greear <[EMAIL PROTECTED]>
> All bugs added by David S. Miller <[EMAIL PROTECTED]>
> qdio: loading QDIO base support version 2 ($Revision: 1.120.2.1
> $/$Revision: 1.56.2.2 $)
> debug: qdio_setup: new level 2
> debug: qdio_labs: new level 2
> debug: qdio_sense: new level 2
> debug: qdio_trace: new level 2
> qeth: loading qeth S/390 OSA-Express driver ($Revision: 1.260.2.13
> $/$Revision: 1.86.2.2 $/$Revision: 1.31 $:IPv6:VLAN)
> qeth: allocated 0 spare buffers
> debug: qeth_setup: new level 3
> debug: qeth_misc: new level 2
> debug: qeth_data: new level 2
> debug: qeth_control: new level 2
> debug: qeth_sense: new level 2
> debug: qeth_qerr: new level 2
> debug: qeth_trace: new level 2
> qeth: Trying to use card with devnos 0x960/0x961/0x962
> qeth: received an IDX TERMINATE on irq 0x11/0x12 with cause code 0x17
> qeth: IDX_ACTIVATE on read channel irq 0x11: negative reply
> qeth: There were problems in hard-setting up the card.
> ------
>
> /etc/chandev.conf contains:
>
>
noauto;qeth0,0x0960,0x0961,0x0962;addparms,0x10,0x0960,0x0962,portname:LNXLAN02
>
>
> I have been given these paramaters by the kind people in charge of our z/VM
> (ie. i know linux, not so much mainframes and z/VM), and if needed I could
> probably provide more details of the hardware and how things are "coupled".
>
>
> --
> Best regards/hilsen
> Jxrgen Birkhaug
>
>
