Here are my IOCP definitions for the network interface on my MP3000. For EMIO
each control unit can only support one device, therefore there are two CU
definitions for the even/odd pair of addresses. Even though IOCP uses CTC's, I
defined it to Debian with lcs.
+------------------------ View Control Unit Definition -----------------------
| CBDPCU40 Row 1 of 1 More: >
| Command ===> ____________________________________________ Scroll ===> CSR
|
| Control unit number . : FC04 Ethernet adapter #3 even address
| Control unit type . . : CTC Serial number . . . :
|
| Connected switch.ports :
|
|
| ----------------Channel Path ID . Link Address-----------------
| Proc.CSSID 1------ 2------ 3------ 4------ 5------ 6------ 7------ 8------
| SERVER2 FC
|
|
|
| ENTER to continue.
+------------------------ View Control Unit Definition ---------------------
| CBDPCU40 Row 1 of 1 More:
| Command ===> ____________________________________________ Scroll ===> CSR
|
| Control unit number . : FC05 Ethernet adapter #3 odd address
| Control unit type . . : CTC Serial number . . . :
|
| Connected switch.ports :
|
|
| ENTER to continue.
|
| ----------------Channel Path ID . Link Address-----------------
| Proc.CSSID 1------ 2------ 3------ 4------ 5------ 6------ 7------ 8------
| SERVER2 FC
+-------------------------- View Device Definition ---------------------------+
| CBDPDV40
|
| Device number . . . . . . . : 0B30
| Device type . . . . . . . . : CTC
|
| Serial number . . . . . . . :
| Description . . . . . . . . : Ethernet adapter #3 even address
|
| Volume serial number . . . . : (for DASD)
|
| Connected to CUs : FC04
|
| ENTER to continue.
|
+-------------------------- View Device Definition ------------------
| CBDPDV40
|
| Device number . . . . . . . : 0B31
| Device type . . . . . . . . : CTC
|
| Serial number . . . . . . . :
| Description . . . . . . . . : Ethernet adapter #3 odd address
|
| Volume serial number . . . . : (for DASD)
|
| Connected to CUs : FC05
|
| ENTER to continue.
>>> [EMAIL PROTECTED] 01/05/05 12:53PM >>>
I'm trying to install woody on a Multiprise 3000. The user doesn't mind
running in basic mode (and in fact I defined the first LPAR IOCDS on the
box), but it appears the only way to IPL from CD is in LPAR mode. So I
defined an LPAR IOCDS. I can get the CD to IPL, but it doesn't see the
network interface (I've got an LCS defined in the emulated I/O configuration
at 0E20/0E21, as OS/390 has been using it successfully). I can't leave the
box in LPAR mode, either, since the OS/390 LPAR won't IPL for some reason I
can't figure out. (Yes, the IPL device is defined and assigned to the OS/390
LPAR.)
1) Is is possible to IPL the CD from basic mode? If not, how do I get an
emulated tape somewhere that the system can find it?
2) Is there something basic I'm missing in defining the LCS to the Linux
LPAR?
3) Can there be two emulated LCSes on one network adapter in the MP3000? (Or
does it come standard with two?) I doubt this, but feel compelled to ask.
I probably won't get to try this again; I'm in Madrid, and tomorrow is a
national holiday here - and I fly home Friday. Even so, I might be able to
guide the local expert in getting the install done on their system.
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
