Filter
Top Products
2–Boot from SAN
ql4xdisablesysfsboot Settings and Adapter Boot Mode
2-34 IS0054604-00 A
2 Non-Boot
from SAN
a
No target
info is in
the firm-
ware
1 or 0 Disable Use
iscsiadm
for discov-
ery and login to targets. The
correct
qla4xxx
iface
must be used.
Discovery:
# iscsiadm -m
discovery -t st -p
<target IP> -I
<qla4xxx iface>
Login:
#iscsiadm -m node -l
To check the sessions:
# iscsiadm -m session
Since there are no
entries in Flash or firm-
ware, target manage-
ment is done by
iscsiadm
and
isc-
sid
. The driver is just
pass-through.
3 Boot from
SAN
Boot tar-
get info is
in the firm-
ware/
Flash
1 Manual To check sessions:
#iscsiadm -m session
Since
ql4xdisable-
sysfsboot
= 1, the
qla4xxx
driver does
the login to the target.
b
4 Boot from
SAN
Boot tar-
get info is
in the firm-
ware/
Flash
0 Manual To check boot target info:
#iscsiadm -m fw
To check sessions:
# iscsiadm -m session
If login is not done automati-
cally use:
# iscsiadm -m fw -l
Since
ql4xdisable-
sysfsboot
= 0, the
driver will not log in to
boot targets. The iscsi
initiator tools (such as
iscsistart
in
RHEL) do the login to
the boot targets.
a
In this configuration you can use the iscsi-client from yast to add targets and login to the targets.
b
This configuration is basically compatible with older qla4xxx infrastructure in SLES 11 SP1.
NOTE
In all these configurations you can use the iscsiadm command to do
additional discovery and login. The only exception is boot targets for Boot
from SAN. For Boot from SAN, target information must be in the firmware or
Flash, having been added using the CTRL+Q option of BIOS.
Table 2-2. Configurations and Tools for Checking iSCSI Sessions (Continued)
No.
Configu-
ration
Target
info
ql4xdisable
sysfsboot
Adapter
Boot
Mode
iscsiadm command Remarks