Red Hat Bugzilla – Bug 110876
Setup process would not accept parm iucv=TCPIP.
Last modified: 2007-11-30 17:06:59 EST
Description of problem:
We use IUCV for network connectivity for the Linux guests on
z/VM 3.10. No matter where I place the statement "iucv=TCPIPLNX"
in the REDHAT PRM file, the install program wouldn't never accept
"iucv=TCPIPLNX" just like other parameters in the REDHAT PRM file.
I had tried all upper, lower, or combination of upper/lower case
for iucv=TCPIPLNX" with no success. The install process will not
prompt with IUCV=TCPIPLNX in uppercase, but it failed to establish
the network connectivity between the Linux guest
and TCPIPLNX (IP Stack) machine.
'SPOOL PUNCH * RDR'
'PUNCH KERNEL IMG B (NOH'
'PUNCH REDHAT PRM A (NOH'
'PUNCH INITRD IMG B (NOH'
The circumvention is to exclude "iucv=TCPIPLNX" in the parm file
and key it in when prompted during the install.
File REDHAT PRM - a CMS file on z/VM.
ROOT=/DEV/RAM0 RAMDISK_SIZE=40000 RO IP=OFF DASD=100,200,501
Console log of the Linux guest machine.
Starting the zSeries initrd to configure networking. Version is
Enter iucv kernel module options (usually iucv=HOST,
where HOST is TCPIP for the VM TCP/IP service machine
or the name (in capital letters) of another
IUCV lowlevel driver Version: 1.39 initialized
divert: not allocating divert_blk for non-ethernet device iucv0
NETIUCV driver Version: 1.21 initialized
iucv0: connected with remote side
Version-Release number of selected component (if applicable):
Include "iucv=TCPIP" in the cms file REDHAT PRM, then start to
install by IPL 00C from the guest machine.
Steps to Reproduce:
I was prompted to enter iucv=TCPIP.
It shouldn't prompt to enter iucv=TCPIP.
Workaround is to use something like IUCV=iucv=TCPIP
*** This bug has been marked as a duplicate of 107162 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.