This procedure assumes that you are logged in to the local system The consequence of using redundant discovery methods mightīe slow performance when the initiator is communicating with the iSCSI target device. Note - Do not configure an iSCSI target to be discovered by both static andĭynamic device discovery methods. You can determine the static target address from the array's management tool. 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: The iSNS discovery service provides an administrative model to discover all targets in a network. For more information about iSNS, see RFC 4171: The default port for the iSNS server is 3205. 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. It also provides state change notification to notify the iSCSI initiator when changes in the operational state of storage nodes occur. ISNS - iSNS (Internet Storage Name Service) allows the iSCSI initiator to discover the targets to which it has access using as little configuration information as possible. 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. Two dynamic device discovery methods are available: Or use static iSCSI initiator targets to perform device discovery.ĭynamic device discovery – If an iSCSI node exposes many 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 device discovery. Static – Static target addressing is configured.ĭetermine whether you want to configure one of the dynamic device discovery methods SendTargets – Potential targets are discovered by using a discovery-address. Internet Storage Name Service (iSNS) – Potential targets are discovered by interacting with one or more iSNS servers. Copying UFS Files and File Systems (Tasks) UFS Backup and Restore Commands (Reference)Ģ8. Restoring UFS Files and File Systems (Tasks)Ģ7.
Backing Up UFS Files and File Systems (Tasks)Ģ6. Backing Up and Restoring UFS File Systems (Overview)Ģ4. Checking UFS File System Consistency (Tasks)Ģ3. Configuring Additional Swap Space (Tasks)Ģ1. Mounting and Unmounting File Systems (Tasks)ġ9. Creating ZFS, UFS, TMPFS, and LOFS File Systems (Tasks)ġ8. Use LUN Masking When Using the iSNS Discovery Methodġ7.
Globalsan iscsi initiator setup how to#
How to Troubleshoot iSCSI Device or Disk Unavailability ISCSI Device or Disk Is Not Available on the Local System How to Troubleshoot iSCSI Connection Problems No Connections to the iSCSI Target From the Local System Troubleshooting iSCSI Configuration Problems How to Enable Multiple iSCSI Sessions for a Target Setting Up Solaris iSCSI Multipathed Devices How to Modify iSCSI Initiator and Target Parameters Modifying iSCSI Initiator and Target Parameters Solaris iSCSI and RADIUS Server Error Messages How to Configure RADIUS for Your iSCSI Configuration Using a Third-Party RADIUS Server to Simplify CHAP Management in Your iSCSI Configuration How to Configure CHAP Authentication for Your iSCSI Target How to Configure CHAP Authentication for Your iSCSI Initiator How to Configure iSNS Discovery for the Solaris iSCSI TargetĬonfiguring Authentication in Your iSCSI-Based Storage Network Setting Up Your Solaris iSCSI Target Devices
How to Prepare for a Solaris iSCSI Configuration Setting Up Solaris iSCSI Targets and Initiators (Task Map)Ĭonfiguring Solaris iSCSI Targets and InitiatorsĬonfiguring Dynamic or Static Target Discovery
0 kommentar(er)
