On 10/07/2010 06:06 PM, Wiggins, Mark wrote:
Okay first, I had already changed my
/etc/sysconfig/hardware/config-ccw-0.0.a200 to the way that you
suggested based on a recommendation from David Straub.
So on to the "lszfcp" commands. Before and after reboot are the same
for "lszfcp -HV" command
> # lszfcp -HV
Looks like the fcp adapters (HBAs) come up but the LUNs seem missing
after regular boot.
But the "# lszfcp -DV" command shows *nothing* after reboot and shows
this before the reboot,
> # lszfcp -DV
The list looks good. How did you get the LUNs active before the reboot?
By manually calling hwup or by writing to sysfs? Whatever trigger it
was, this trigger seems to be missing during regular boot.
Obviously, that is an issue. So what do you think that I'm missing?
It still seems that I'm missing a configuration file, maybe it's not
/etc/sysconfig/hardware/config-ccw-0.0.a200 in Debian??? I've read
Have you tried tracing the hwup (shell script) command to see if and why
it fails?
# /bin/bash -x `which hwup ...`
Since debian seems to look very much like SLES with respect to
persistent device configuration, you could look out for the command line
tools which YaST uses on SLES to write the hwconf files. SLES ships them
as part of the s390-tools package. Those tools can also be called
directly as user root on the command line and this way you could be sure
to have the hwconf file being syntactically correct and have the correct
name.
To configure fcp adapters:
# zfcp_host_configure
To configure fcp luns (on configured adapters):
# zfcp_disk_configure
Their usage is described in the first few comment lines of those shell
scripts. You can also trace them to see what they do and which files
they write. If that worked, then try rebooting and if the LUNs still
don't come up automatically you could also try to update initramfs and
run zipl and see if it'll then work. Sorry, I don't know anything s390
specific about debian.
BTW, there are more command line tools for persistent device
configuration in SLES (10 and 11):
dasd_configure
qeth_configure
ctc_configure (also works for LCS devices so it actually handles cu3088)
iucv_configure
through IBM's "Device Drivers, Features, and Commands" (amongst a
hundred other documents), but haven't found anything there either. It
shows you how to configure the devices (echo 0x001f000000000000>
0.0.a200/0x50050768011035d9/unit_add) but doesn't suggest where to
put those configuration parameters to make them permanent.
Yes, you won't find distro-specific persistent configuration procedures
in the device drivers book. It describes the kernel/user space interface
which is code IBM contributes, so only dynamic (non-persistent)
configuration. How to configure devices persistently, should be in the
distro documentation since the distros contribute that code.
Steffen
Linux on System z Development
IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Martin Jetter
Geschäftsführung: Dirk Wittkopp
Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294
----------------------------------------------------------------------
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 more information on Linux on System z, visit
http://wiki.linuxvm.org/
