JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Sun ZFS Storage 7000 System Administration Guide
search filter icon
search icon

Document Information

Preface

1.  Introduction

2.  Status

3.  Configuration

Configuration

Introduction

Initial

Initial Configuration

Prerequisites

Summary

BUI

Configuring Management Port

CLI

Performing Initial Configuration with the CLI

Network

Network Configuration

Devices

Datalinks

Interfaces

IP MultiPathing (IPMP)

Performance and Availability

Routing

Routing Entries

Routing Properties

BUI

Configuration

Addresses

Routing

CLI

Tasks

BUI

CLI

Infiniband Upgrade Procedures for Q3.2010

Storage

Introduction

Configure

Verification and Allocation

Profile Configuration

Import

Add

Unconfig

Scrub

Tasks

BUI

SAN

SAN

Terminology

Targets and Initiators

Target and Initiator Groups

BUI

CLI

Terms

SAN Terminology

FC

Fibre Channel

Target Configuration

Clustering Considerations

Initiator Configuration

Switch Considerations

Clustering Considerations

Performance Considerations

Troubleshooting

Queue Overruns

Link-level Issues

BUI

Changing modes of FC ports

Viewing discovered FC ports

Creating FC Initiator Groups

Associating a LUN with an FC initiator group

CLI

Changing modes of FC ports

Viewing discovered FC ports

Creating FC Initiator Groups

Associating a LUN with an FC initiator group

Scripting Aliases for Initiators and Initiator Groups

FCMPxIO

Configuring FC Client Multipathing

Configuring Solaris Initiators

Configuring Windows Initiators

Windows Tunables - Microsoft DSM Details

Configuring Linux Initiators

Configuring VMware ESX Initiators

Troubleshooting

See Also

iSCSI

Introduction

Target Configuration

Clustering Considerations

Initiator Configuration

Planning Client Configuration

Solaris iSCSI/iSER and MPxIO Considerations

Troubleshooting

Observing Performance

BUI

Creating an Analytics Worksheet

CLI

Adding an iSCSI target with an auto-generated IQN

Adding an iSCSI target with a specific IQN and RADIUS authentication

Adding an iSCSI initiator which uses CHAP authentication

Adding an iSCSI target group

Adding an iSCSI initiator group

SRP

Introduction

Target configuration

Clustering Considerations

Initiator configuration

Observing Performance

Multipathing Considerations

Linux with OFED SRP Initiator

OFED 1.5 Issues

VMWare 4.0

Path Selection Plugin (psp)

Storage Array Type Plugin (satp)

VMWare ESX 4.0 Issues

BUI

iSER Target Configuration

SRP Target Configuration

CLI

Users

Introduction

Roles

Authorizations

Properties

Users

Roles

BUI

CLI

Tasks

BUI

CLI

Generic

Preferences

Introduction

BUI

CLI

SSH Public Keys

Alerts

Introduction

Actions

Send Email

Send SNMP trap

Send Syslog Message

Resume/Suspend Dataset

Resume/Suspend Worksheet

Threshold Alerts

BUI

CLI

Tasks

BUI

Workflows

Introduction

Workflow execution context

Workflow parameters

Constrained parameters

Optional parameters

Error Handling

Input validation

Execution auditing

Execution reporting

Versioning

Appliance versioning

Workflow versioning

Workflows as alert actions

Alert action execution context

Auditing alert actions

Example: device type selection

BUI

CLI

Downloading workflows

Viewing workflows

Executing workflows

Cluster

Clustering

Features and Benefits

Drawbacks

Terminology

Subsystem Design

Cluster Interconnect I/O

Resource Management Concepts

Takeover and Failback

Configuration Changes in a Clustered Environment

Clustering Considerations for Storage

Clustering Considerations for Networking

Clustering Considerations for Infiniband

Redundant Path Scenarios

Preventing "Split-Brain" Conditions

Estimating and Reducing Takeover Impact

Setup Procedure

Node Cabling

JBOD Cabling

BUI

Unconfiguring Clustering

4.  Services

5.  Shares

6.  Analytics

7.  Application Integration

Glossary

Index

iSCSI

Introduction

Internet SCSI is one of several block protocols supported by the appliance for sharing SCSI based storage.

Target Configuration

When using the iSCSI protocol, the target portal refers to the unique combination of an IP address and TCP port number by which an initiator can contact a target.

When using the iSCSI protocol, a target portal group is a collection of target portals. Target portal groups are managed transparently; each network interface has a corresponding target portal group with that interface's active addresses. Binding a target to an interface advertises that iSCSI target using the portal group associated with that interface.

An IQN (iSCSI qualified name) is the unique identifier of a device in an iSCSI network. iSCSI uses the form iqn.date.authority:uniqueid for IQNs. For example, the appliance may use the IQN: iqn.1986-03.com.sun:02:c7824a5b-f3ea-6038-c79d-ca443337d92c to identify one of its iSCSI targets. This name shows that this is an iSCSI device built by a company registered in March of 1986. The naming authority is just the DNS name of the company reversed, in this case, "com.sun". Everything following is a unique ID that Sun uses to identify the target.

Target Property
Description
Target IQN
The IQN for this target. The IQN can be manually specified or auto-generated.
Alias
A human-readable nickname for this target.
Authentication mode
One of None, CHAP, or RADIUS.
CHAP name
If CHAP authentication is used, the CHAP username.
CHAP secret
If CHAP authentication is used, the CHAP secret.
Network interfaces
The interfaces whose target portals are used to export this target.

In addition to those properties, the BUI indicates whether a target is online or offline:

icon
description
Status: On
Target is online
Status: Off
Target is offline
Clustering Considerations

On clustered platforms, targets which have at least one active interface on that cluster node will be online. Take care when assigning interfaces to targets; a target may be configured to use portal groups on disjoint head nodes. In that situation, the target will be online on both heads yet will export different LUNs depending on the storage owned by each head node. As network interfaces migrate between cluster heads as part of takeover/failback or ownership changes, iSCSI targets will move online and offline as their respective network interfaces are imported and exported.

Targets which are bound to an IPMP interface will be advertised only via the addresses of that IPMP group. That target will not be reachable via that group's test addresses. Targets bound to interfaces built on top of a LACP aggregation will use the address of that aggregation. If a LACP aggregation is added to an IPMP group, a target can no longer use that aggregation's interface, as that address will become an IPMP test address.

Initiator Configuration

iSCSI initiators have the following configurable properties.

Property
Description
Initiator IQN
The IQN for this initiator.
Alias
A human-readable nickname for this initiator.
Use CHAP
Enables or disables CHAP authentication
CHAP name
If CHAP authentication is used, the CHAP username.
CHAP secret
If CHAP authentication is used, the CHAP secret.
Planning Client Configuration

When planning your iSCSI client configuration, you'll need the following information:

To allow the Appliance to perform CHAP authentication using RADIUS, the following pieces of information must match:

Solaris iSCSI/iSER and MPxIO Considerations

MPxIO supports target port aggregation and availability in Solaris iSCSI configurations that configure multiple sessions per target (MS/T) on the iSCSI initiator.

Troubleshooting

For tips on troubleshooting common iSCSI misconfiguration, see the iSCSI section.

Observing Performance

iSCSI performance can be observed via analytics, whereby one can breakdown operations or throughput by initiator, target, or LUN.

BUI

Creating an Analytics Worksheet

To create an analytics worksheet for observing operations by initiator, complete the following:

1. Go to the Analytics screen.

2. Click the Add item add icon for Add Statistic.

A menu of all statistics appears.

3. Select iSCSI operations > Broken down by initiator under the Protocols section of the menu.

A graph of the current operations by initiator appears.

4. To observe more detailed analytics, select the initiator from the field to the left of the graph and click the Analytics: Drilldown icon.

A menu of detailed analytics appears.

CLI

Adding an iSCSI target with an auto-generated IQN
ahi:configuration san targets iscsi> create
ahi:configuration san targets iscsi target (uncommitted)> set alias="Target 0"
ahi:configuration san targets iscsi target (uncommitted)> set auth=none
ahi:configuration san targets iscsi target (uncommitted)> set interfaces=nge1 
ahi:configuration san targets iscsi target (uncommitted)> commit
ahi:configuration san targets iscsi> list
TARGET     ALIAS          
target-000 Target 0       
           |
           +-> IQN
               iqn.1986-03.com.sun:02:daf0161f-9f5d-e01a-b5c5-e1efa9578416
Adding an iSCSI target with a specific IQN and RADIUS authentication
ahi:configuration san targets iscsi> create
ahi:configuration san targets iscsi target (uncommitted)> set alias="Target 1"
ahi:configuration san targets iscsi target (uncommitted)>
     set iqn=iqn.2001-02.com.acme:12345
ahi:configuration san targets iscsi target (uncommitted)> set auth=radius 
ahi:configuration san targets iscsi target (uncommitted)> set interfaces=nge1 
ahi:configuration san targets iscsi target (uncommitted)> commit
ahi:configuration san targets iscsi> list
TARGET     ALIAS          
target-000 Target 0       
           |
           +-> IQN
               iqn.1986-03.com.sun:02:daf0161f-9f5d-e01a-b5c5-e1efa9578416
target-001 Target 1       
           |
           +-> IQN
               iqn.2001-02.com.acme:12345
Adding an iSCSI initiator which uses CHAP authentication
ahi:configuration san initiators iscsi> create
ahi:configuration san initiators iscsi initiator (uncommitted)> 
     set initiator=iqn.2001-02.com.acme:initiator12345
ahi:configuration san initiators iscsi initiator (uncommitted)> set alias="Init 0"
ahi:configuration san initiators iscsi initiator (uncommitted)>
     set chapuser=thisismychapuser
ahi:configuration san initiators iscsi initiator (uncommitted)>
     set chapsecret=123456789012abc
ahi:configuration san initiators iscsi initiator (uncommitted)> commit
ahi:configuration san initiators iscsi> list
NAME          ALIAS
initiator-000 Init 0
              |
              +-> INITIATOR
                  iqn.2001-02.com.acme:initiator12345
Adding an iSCSI target group
ahi:configuration san targets iscsi groups> create
ahi:configuration san targets iscsi group (uncommitted)> set name=tg0
ahi:configuration san targets iscsi group (uncommitted)> 
    set targets=iqn.2001-02.com.acme:12345,
                iqn.1986-03.com.sun:02:daf0161f-9f5d-e01a-b5c5-e1efa9578416
ahi:configuration san targets iscsi group (uncommitted)> commit
ahi:configuration san targets iscsi groups> list
GROUP     NAME
group-000 tg0
          |
          +-> TARGETS
              iqn.2001-02.com.acme:12345
              iqn.1986-03.com.sun:02:daf0161f-9f5d-e01a-b5c5-e1efa9578416
Adding an iSCSI initiator group
ahi:configuration san initiators iscsi groups> create 
ahi:configuration san initiators iscsi group (uncommitted)> set name=ig0
ahi:configuration san initiators iscsi group (uncommitted)> 
    set initiators=iqn.2001-02.com.acme:initiator12345
ahi:configuration san initiators iscsi group (uncommitted)> commit
ahi:configuration san initiators iscsi groups> list
GROUP     NAME
group-000 ig0
          |
          +-> INITIATORS
             iqn.2001-02.com.acme:initiator12345