JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle® ZFS Storage Appliance Administration Guide
Oracle Technology Network
Print View
search filter icon
search icon

Document Information

Using This Documentation

Chapter 1 Oracle ZFS Storage Appliance Overview

Chapter 2 Status

Chapter 3 Initial Configuration

Chapter 4 Network Configuration

Chapter 5 Storage Configuration

Chapter 6 Storage Area Network Configuration

SAN Targets and Initiators

SAN Target and Initiator Groups

Configuring SAN Using the BUI

Configuring SAN Using the CLI

SAN Terminology

SAN Fibre Channel

FC Port Target Configuration

Clustering Considerations

FC Initiator Configuration

Clustering Considerations

Performance Considerations

Troubleshooting FC

FC Queue Overruns

FC Link-level Issues

Configuring FC Using the BUI

Changing Modes of FC Ports

Viewing Discovered FC Ports

Creating FC Initiator Groups

Associating a LUN with an FC Initiator Group

Configuring FC Using the 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


Target Configuration

Clustering Considerations

Initiator Configuration

Planning Client Configuration

Troubleshooting iSCSI

Observing iSCSI Performance

Configuring iSCSI Using the BUI

Creating an Analytics Worksheet

iSER Target Configuration

Configuring iSCSI Using the 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 Target Configuration

Clustering Considerations

Initiator Configuration

Observing SRP Performance

Configuring SRP Targets Using the BUI

SRP Target Configuration

Configuring SRP Targets Using the CLI

Chapter 7 User Configuration

Chapter 8 Setting ZFSSA Preferences

Chapter 9 Alert Configuration

Chapter 10 Cluster Configuration

Chapter 11 ZFSSA Services

Chapter 12 Shares, Projects, and Schema

Chapter 13 Replication

Chapter 14 Shadow Migration

Chapter 15 CLI Scripting

Chapter 16 Maintenance Workflows

Chapter 17 Integration


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.

Note: Multiple connections per session is not supported.

An IQN (iSCSI qualified name) is the unique identifier of a device in an iSCSI network. iSCSI uses the form for IQNs. For example, the appliance may use the IQN: 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 Oracle uses to identify the target.

Table 6-2  iSCSI Target Properties
Target Property
Target IQN
The IQN for this target. The IQN can be manually specified or auto-generated.
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:

Table 6-3  Target Status Icons
image:Status: On
Target is online
image: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.