How to Make SCSI Logical Units Available

compared with
Current by DenaSteward
on Jul 20, 2009 16:20.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (10)

View page history
*# Adding one or more views for each logical unit - Adding a view creates a bridge between the logical unit and the host initiator. When an initiator from the host group logs into a target port contained in the Target Group, the logical unit is visible.
{note:title=Tip}Don't confuse a Target Group with a Target Portal Group (TPG). A TPG is a list of IP addresses that an iSCSI target listens to. A TPG can help you restrict an iSCSI target so that is it available only through one specific IP address. See the [stmfadm(1M)|http://docs.sun.com/app/docs/doc/819-2240/stmfadm-1m?a=view] man page for more information on Target Groups. See [How to Create a Target Portal Group] for more information on TPGs.{note}
 
 
A view entry consists of four components: Host Group,Target Group, logical unit number (LUN), and logical unit identifier. Of these four components, only the logical unit identifier is required. If the other components are omitted, the following default values are assumed:
* If the Host Group is omitted, the {{All Initiators}} value is assumed.
# Obtain the Global Unique Identification (GUID) number for the logical unit.
{code}
# sbdadm list-lu # stmfadm list-lu -v
# stmfadm list-lu -v
{code}
# Add a view for the logical unit.
{code}
{code:none}
HBA Port WWN: *210000e08b83378d*
OS Device Name: /dev/cfg/c4
Manufacturer: Qlogic Corp.
Model: QLA2462
Firmware Version: 4.0.27
Fcode/BIOS Version: N/A
Type: N-port
State: online
Supported Speeds: 1Gb 2Gb 4Gb
Current Speed: 4Gb
Node WWN: 210000e08b83378d
HBA Port WWN: *210100e08ba3378d*
OS Device Name: /dev/cfg/c5
Manufacturer: Qlogic Corp.
Model: QLA2462
Firmware Version: 4.0.27
Fcode/BIOS Version: N/A
Type: N-port
State: online
Supported Speeds: 1Gb 2Gb 4Gb
Current Speed: 4Gb
Node WWN: 210100e08ba3378d
HBA Port WWN: *210000e08b83378d* OS Device Name: /dev/cfg/c4 Manufacturer: Qlogic Corp. Model: QLA2462 Firmware Version: 4.0.27 Fcode/BIOS Version: N/A Type: N-port State: online Supported Speeds: 1Gb 2Gb 4Gb Current Speed: 4Gb Node WWN: 210000e08b83378d HBA Port WWN: *210100e08ba3378d* OS Device Name: /dev/cfg/c5 Manufacturer: Qlogic Corp. Model: QLA2462 Firmware Version: 4.0.27 Fcode/BIOS Version: N/A Type: N-port State: online Supported Speeds: 1Gb 2Gb 4Gb Current Speed: 4Gb Node WWN: 210100e08ba3378d
{code}
# For all configurations, create a Host Group.
# stmfadm add-hg-member -g Host-A wwn.210000e08b83378d wwn.210100e08ba3378d
{code}
# Follow the instructions within each port provider to identify the name of each SCSI target you want to add to your view. This step is optional if you want the logical unit to be available through all SCSI targets. You can list the SCSI targets that are already available with {{stmfadm list-target}}.
{code:none}
stmfadm list-target
stmfadm create-tg Targets-0
{code}
# Specify the members for the Target Group, adding the target names as members. Each SCSI target can be a member of only one Target Group.
{code:none}
stmfadm add-tg-member -g Targets-0 wwn.501000e092376af7
* For example, on a Solaris Fibre Channel initiator host, verify that the target logical unit is visible by running the following script.
{code:none}
#!/bin/ksh fcinfo hba-port |grep "^HBA" | awk '{print $4}' | while read 1n do fcinfo remote-port -p $1n -s >/dev/null 2>&1 done
fcinfo hba-port |grep "^HBA" | awk '{print $4}' | while read 1n
do
fcinfo remote-port -p $1n -s >/dev/null 2>&1
done
{code}
All subsequent logical units appear in the format output because the script forces the initiator to touch all the logical units through all the ports. If the LUNs are not visible, run the {{format}} command again. If the LUNs are still not visible, ensure that the service is enabled on the target by using the {{svcs stmf}} command. Also ensure that you added view entries for the LUN, as described in this procedure.

The individuals who post here are part of the extended Sun Microsystems community and they might not be employed or in any way formally affiliated with Sun Microsystems. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Sun nor any other party necessarily agrees with them.

Copyright 1994-2009 Sun Microsystems, Inc.
Powered by Atlassian Confluence
Sun Guidelines on Public Discourse Privacy Policy Terms of Use Trademarks Site Map Employment Investor Relations Contact