When the modules are loaded, the order ends up in such a way that the driver for
the Qlogic FC controller gets loaded before the driver for the Adaptec SCSI
Controller. This causes the probing for the devices to occur such that the Fabric
gets assigned
sda
,
sdb
, and so on followed by the local SCSI disks. Make the
following modifications to ensure that the SCSI module is loaded before the Fibre
module. This will ensure that the probing and naming assigns the
sda
device to the
first local disk.
1.
First, modify the
/etc/modules.conf
file by adding the line
″
options scsi_mod
max_scsi_luns=128
″
to the end of
modules.conf
. Also remove unnecessary
information and reorder the way the modules are loaded. An example of an
edited file is as follows:
Original modules.conf:
alias eth0 e1000
alias scsi_hostadapter qla2x00
alias scsi_hostadapter1 aic7xxx
alias scsi_hostadapter2 ips
alias parport_lowlevel parport_pc
alias scsi_hostadapter2 qla2x00
alias usb-controller usb-ohci
alias scsi_hostadapter4 aic7xxx
Edited modules.conf:
alias eth0 e1000
alias scsi_hostadapter aic7xxx
alias scsi_hostadapter1 ips
alias eth1 e1000 alias eth1 e1000
alias parport_lowlevel parport_pc
alias scsi_hostadapter3 aic7xxx
options scsi_mod max_scsi_luns=128
2.
Next, rebuild the two initrd images:
mkinitrd
initrd-2.4.2-2.img 2.4.2-2 -f
mkinitrd
initrd-2.4.2-2smp.img 2.4.2-2smp -f
3.
Reboot the node.
KVM
GUI does not appear on first node
If the GUI display does not appear on the first node of the C2T chain, use the text
mode.
2x8 Switch powers on with console port B
To remedy this go into the menu settings and change from cooperative to
preemptive mode, reselect port 2 and console A will appear. When working
properly do a Snapshot to save the setting.
Cluster port 1 reboots
The Cluster Port 1 may reboot on power up, and either boots up in text mode
blinking every 5 seconds or boots up with a white screen. There are two methods
to remedy this situation:
1.
Manually select the other ports in the C2T string, then reselect node 1.
2.
Unplug the server connections from the port, reattach them in order, and
re-power the server.
128
Installation and Service
Summary of Contents for System Cluster 1350
Page 1: ...eServer Cluster 1350 Cluster 1350 Installation and Service IBM...
Page 2: ......
Page 3: ...eServer Cluster 1350 Cluster 1350 Installation and Service IBM...
Page 8: ...vi Installation and Service...
Page 10: ...viii Installation and Service...
Page 12: ...x Installation and Service...
Page 20: ...2 Installation and Service...
Page 30: ...12 Installation and Service...
Page 32: ...14 Installation and Service...
Page 52: ...34 Installation and Service...
Page 68: ...50 Installation and Service...
Page 70: ...52 Installation and Service...
Page 72: ...54 Installation and Service...
Page 74: ...56 Installation and Service...
Page 92: ...74 Installation and Service...
Page 96: ...78 Installation and Service...
Page 98: ...80 Installation and Service...
Page 104: ...86 Installation and Service...
Page 110: ...92 Installation and Service...
Page 124: ...106 Installation and Service...
Page 126: ...108 Installation and Service...
Page 138: ...120 Installation and Service...
Page 139: ...Part 4 Appendixes Copyright IBM Corp 2003 121...
Page 140: ...122 Installation and Service...
Page 144: ...126 Installation and Service...
Page 148: ...130 Installation and Service...
Page 154: ...136 Installation and Service...
Page 160: ...142 Installation and Service...
Page 169: ......
Page 170: ...IBMR Printed in U S A...