Skip Navigation Links | |
Exit Print View | |
Oracle Solaris 11.1 Administration: Devices and File Systems Oracle Solaris 11.1 Information Library |
1. Managing Removable Media (Tasks)
2. Writing CDs and DVDs (Tasks)
4. Dynamically Configuring Devices (Tasks)
5. Managing USB Devices (Tasks)
6. Using InfiniBand Devices (Overview/Tasks)
9. Administering Disks (Tasks)
11. Configuring Storage Devices With COMSTAR (Tasks)
Identifying COMSTAR Software and Hardware Requirements
Configuring Storage Devices With COMSTAR (Tasks)
How to Enable the STMF Service
How to Back Up and Restore a COMSTAR Configuration
How to Enable iSNS Discovery for the Target Device
How to Configure an IB HCA for iSER
Creating iSCSI Target Portal Groups
How to Create a Target Portal Group for iSCSI Targets
Making SCSI Logical Units Available
How to Make a Logical Unit Available to All Systems
How to Restrict Logical Unit Access to Selected Systems
Configuring Fibre Channel Devices With COMSTAR
Configuring Fibre Channel Ports With COMSTAR
How to Display Existing FC Port Bindings
How to Set All FC Ports to a Specific Mode
How to Set Selected FC Ports to Initiator or Target Mode
Making Logical Units Available for FC and FCoE
How to Make Logical Units Available for FC and FCoE
Configuring FCoE Devices With COMSTAR
Enabling 802.3x PAUSE and Jumbo Frames on the Ethernet Interface
How to Create FCoE Target Ports
How to Verify That an FCoE Target Port Is Working
How to Delete FCoE Target Ports
Configuring SRP Devices With COMSTAR
How to Enable the SRP Target Service
How to Verify SRP Target Status
12. Configuring and Managing the Oracle Solaris Internet Storage Name Service (iSNS)
13. The format Utility (Reference)
14. Managing File Systems (Overview)
15. Creating and Mounting File Systems (Tasks)
16. Configuring Additional Swap Space (Tasks)
17. Copying Files and File Systems (Tasks)
This is a general list of tasks associated with configuring storage devices with COMSTAR. Some of the tasks are optional depending on your network configuration needs. Some of the links below will take you to separate documents that describe network configuration and initiator configuration.
Review the following terminology before configuring target devices with COMSTAR.
|
Determine whether you want to configure one of the dynamic device discovery methods or use static iSCSI initiator targets to perform device discovery.
Dynamic device discovery – Two dynamic device discovery methods are available:
SendTargets – If an iSCSI node exposes a large number of targets, such as an iSCSI to Fibre-Channel bridge, you can supply the iSCSI node IP address/port combination and allow the iSCSI initiator to use the SendTargets features to perform the device discovery.
iSNS – The Internet Storage Name Service (iSNS) allows the iSCSI initiator to discover the targets to which it has access using as little configuration information as possible. It also provides state change notification to notify the iSCSI initiator when changes in the operational state of storage nodes occur. To use the iSNS discovery method, you can supply the iSNS server address/port combination and allow the iSCSI initiator to query the iSNS servers that you specified to perform the device discovery. The default port for the iSNS server is 3205. For more information about iSNS, see RFC 4171:
http://www.ietf.org/rfc/rfc4171.txt
The iSNS discovery service provides an administrative model to discover all targets on a network.
For more information about setting up iSNS support in Oracle Solaris, see Chapter 12, Configuring and Managing the Oracle Solaris Internet Storage Name Service (iSNS).
Static device discovery – If an iSCSI node has few targets or if you want to restrict the targets that the initiator attempts to access, you can statically configure the target-name by using the following static target address naming convention:
target,target-address[:port-number]
You can determine the static target address from the array's management tool.
Note - Do not configure an iSCSI target to be discovered by both static and dynamic device discovery methods. The consequence of using redundant discovery methods might be slow performance when the initiator is communicating with the iSCSI target device.