Sun Storage 7000 Unified Storage System: Verifying that the Unified Storage has been configured correctly for Fibre-Channel connectivity

Asset ID:	1-71-1434004.1
Update Date:	2012-03-12
Keywords:

Solution Type Technical Instruction Sure

Solution 1434004.1 : Sun Storage 7000 Unified Storage System: Verifying that the Unified Storage has been configured correctly for Fibre-Channel connectivity

Applies to:

Sun Storage 7210 Unified Storage System - Version: Not Applicable to Not Applicable - Release: N/A to N/A
Sun ZFS Storage 7120 - Version: Not Applicable to Not Applicable   [Release: N/A to N/A]
Sun Storage 7110 Unified Storage System - Version: Not Applicable to Not Applicable   [Release: N/A to N/A]
Sun Storage 7310 Unified Storage System - Version: Not Applicable to Not Applicable   [Release: N/A to N/A]
Sun Storage 7410 Unified Storage System - Version: Not Applicable to Not Applicable   [Release: N/A to N/A]
Information in this document applies to any platform.

Goal

How to verify that the Unified Storage has been configured correctly for Fibre-Channel connectivity

Solution

On the appliance, Fibre-Channel (FC) connectivity problems could be due to:

The FC Lun has not been configured
The FC initiator has not been configured correctly
The appliance is not presenting the LUN to the initiator correctly. In other words, the lun is not correctly mapped to the initiator.

After verifying the configuration using the steps below, correct any configuration problems by referring to the product documents: Oracle ZFS Storage Appliance Product Documentation. In particular, refer to the system administration documentation.

Verify if the FC target LUN has been configured

By default, all FC ports are used by the appliance to connect to a tape SAN for purposes of backup. This means that the FC ports are configured as initiators.
To share LUNs via FC, one or more FC ports must be configured to be in target mode.
Configuring a port to be in target mode requires the appliance to be reset, but multiple ports may be configured to be in target mode simultaneously. The mode of a port will be preserved across any subsequent reboots or upgrades. You must have root permissions to change the mode of a port. Each FC port is assigned a World Wide Name (WWN), and (as with other block protocols) FC targets may be grouped into target groups.

Follow the steps below to identify the target luns.

Using the CLI

1. Log on to the appliance using ssh

2. Run following commands to verify the configured target Lun and the target group

Please note that the outputs shown below are for a cluster. ss7320-sin06-a-node1:configuration> san ss7320-sin06-a-node1:configuration san> targets ss7320-sin06-a-node1:configuration san targets> fc ss7320-sin06-a-node1:configuration san targets fc> show Properties: targets = wwn.2100001B321BAA4C,wwn.2101001B323BAA4C Targets: NAME MODE WWN PORT SPEED target-000 target wwn.2100001B321BAA4C PCIe 0: Port 1 2 Gbit/s target-001 target wwn.2101001B323BAA4C PCIe 0: Port 2 2 Gbit/s Children: groups => Manage groups ss7320-sin06-a-node1:configuration san targets fc> select target-000 ss7320-sin06-a-node1:configuration san targets fc target-000> show Properties: wwn = wwn.2100001B321BAA4C port = PCIe 0: Port 1 mode = target speed = 2 Gbit/s discovered_ports = 0 link_failure_count = 1 loss_of_sync_count = 0 loss_of_signal_count = 0 protocol_error_count = 0 invalid_tx_word_count = 0 invalid_crc_count = 0 ss7320-sin06-a-node1:configuration san targets fc target-001> show Properties: wwn = wwn.2101001B323BAA4C port = PCIe 0: Port 2 mode = target speed = 2 Gbit/s discovered_ports = 0 link_failure_count = 1 loss_of_sync_count = 0 loss_of_signal_count = 0 protocol_error_count = 0 invalid_tx_word_count = 0 invalid_crc_count = 0 ss7320-sin06-a-node1:configuration san targets fc groups> show Groups: GROUP NAME group-000 targets-0 | +-> TARGETS wwn.2100001B321BAA4C -> target port defined on node 1 wwn.21000024FF2E4EC6 -> target port defined on node 2 wwn.21000024FF2E4EC7 -> target port defined on node 2 wwn.2101001B323BAA4C -> target port defined on node 1

In the above case, the target group is targets-0 in which the targets are configured.
If this is a non-cluster configuration, then only target ports for the node in question will be seen above.

Using the BUI

Note that in a cluster configuration, you will have to set ports to Target mode on each head node separately.
1. Click Configuration > SAN -> to display the Storage Area Network (SAN) screen
2. Click the Targets tab at the right and then select Fiber Channel Ports at the top of the left panel

The targets and the target groups are shown.
In a cluster, the targets from the other node will be also shown as part of the target group.

To share LUNs only via particular targets or to particular initiators, build Target Groups and Initiator Groups, respectively.
If not, then the target belongs to the default group.

Verify if the FC initiator is configured correctly

FC initiator

An FC initiator is defined to allow access from one or more servers to particular volumes. Permissions to volumes should be configured so that a minimum number of FC initiators are allowed to access a particular volume.
The FC initiator definition contains the host WWNs. To identify the host to the Sun ZFS Storage Appliance, the Oracle Solaris FC initiator WWNs must be registered with the appliance.
If zoning has been configured on the FC switches, the WWNs of the Oracle Solaris host should be displayed (assuming they are not assigned to an alias already).

FC Initiator Group

Related FC initiators are combined into logical groups to allow commands to execute on multiple FC initiators, for example, assigning LUN access to all FC initiators in a group with one command. For the following example, the FC initiator group will contain two initiators.
Note that in a cluster, where multiple servers are treated as a single logical entity, the initiator group may contain many more initiators.
If no initiator group is defined, then the initiator's belong to the default group.

Using the CLI

ss7320-sin06-a-node1:configuration san initiators> fc ss7320-sin06-a-node1:configuration san initiators fc> show Initiators: NAME ALIAS initiator-000 c3 | +-> INITIATOR wwn.21000024FF2A967D initiator-001 c2 | +-> INITIATOR wwn.21000024FF2A967C Children: groups => Manage groups ss7320-sin06-a-node1:configuration san initiators fc> groups ss7320-sin06-a-node1:configuration san initiators fc groups> show Groups: GROUP NAME group-000 initiators-0 | +-> INITIATORS wwn.21000024FF2A967C -> Host initiator 1 wwn.21000024FF2A967D -> Host Initiator 2

The above initiators belong to initiator group "initiator-0"

Using the BUI

1. Click Configuration > SAN to display the Storage Area Network (SAN) screen.
2. Click the Initiators tab at the right and then select Fibre Channel Initiators at the top of the left panel.

Verify is the target has been correctly associated with the initiator

Using the CLI

ss7320-sin06-a-node1:shares> show Properties: pool = pool-node1 Projects: FCLuns Children: replication => Manage remote replication schema => Define custom property schema ss7320-sin06-a-node1:shares> select FCLuns ss7320-sin06-a-node1:shares FCLuns> show Properties: aclinherit = restricted atime = true checksum = fletcher4 compression = off dedup = false compressratio = 100 copies = 1 creation = Thu Sep 01 2011 08:38:32 GMT+0000 (UTC) logbias = latency mountpoint = /export quota = 0 readonly = false recordsize = 128K reservation = 0 secondarycache = all nbmand = false sharesmb = off sharenfs = on snapdir = hidden vscan = false sharedav = off shareftp = off sharesftp = off sharetftp = pool = pool-node1 canonical_name = pool-node1/local/FCLuns default_group = other default_permissions = 700 default_sparse = false default_user = nobody default_volblocksize = 8K default_volsize = 0 exported = true nodestroy = false space_data = 13.0G space_unused_res = 0 space_unused_res_shares = 0 space_snapshots = 19K space_available = 7.12T space_total = 13.0G origin = Shares: Filesystems: NAME SIZE MOUNTPOINT prets_1 94.5K /export/prets_1 LUNs: NAME SIZE GUID fctest1 5.00G 600144F0F8D6944400004E60900A0003 fctest2 3.00G 600144F0F8D6944400004E6090280004 fctest3 2G 600144F0F8D6944400004EBBFF2E0003 fctest4 3G 600144F0F8D6944400004F45D8820002 Children: groups => View per-group usage and manage group quotas replication => Manage remote replication snapshots => Manage snapshots users => View per-user usage and manage user quotas ss7320-sin06-a-node1:shares FCLuns> select fc fctest1 fctest2 fctest3 fctest4 ss7320-sin06-a-node1:shares FCLuns> select fctest1 ss7320-sin06-a-node1:shares FCLuns/fctest1> show Properties: checksum = fletcher4 (inherited) compression = off (inherited) dedup = false (inherited) compressratio = 100 copies = 1 (inherited) creation = Fri Sep 02 2011 08:12:58 GMT+0000 (UTC) logbias = latency (inherited) secondarycache = all (inherited) volblocksize = 8K lunguid = 600144F0F8D6944400004E60900A0003 volsize = 5G sparse = false writecache = false pool = pool-node1 canonical_name = pool-node1/local/FCLuns/fctest1 exported = true (inherited) nodestroy = false space_data = 5.00G space_snapshots = 0 space_total = 5.00G space_available = 7.12T initiatorgroup = initiators-0 ====> initiator group targetgroup = targets-0 ====> target group lunumber = auto assignednumber = 0 ===> Lun number status = online ===> status fixednumber = false origin = Children: snapshots => Manage snapshots replication => Manage remote replication ss7320-sin06-a-node1:shares FCLuns/fctest1>

Note: Two different luns cannot have the same lun number in the same target/initiator group.
You may set the first LUN to 0 and then "auto-assign" the rest of them.

Using the BUI
1. Select Shares to display the Projects screen
2. Click on the "LUNS" option
3. For the luns shown, click on the pencil symbol on the far right of each of the LUNs when the cursor is moved on the LUN entry
4. For the selected LUN, click on the "Protocol" tab

The target group and the initiator group defined for this LUN are shown, along with the LUN number and its operational status.

Attachments

This solution has no attachment