Performing Initial Configuration with the CLI
Infiniband Upgrade Procedures for Q3.2010
Configuration Rules and Guidelines
Associating a LUN with an FC initiator group
Associating a LUN with an FC initiator group
Scripting Aliases for Initiators and Initiator Groups
Supported InfiniBand Client-Side Data Protocols
Supported Fiber Channel Initiators
Configuring FC Client Multipathing
Configuring Solaris Initiators
Configuring Windows Initiators
Windows Tunables - Microsoft DSM Details
Configuring VMware ESX Initiators
Solaris iSCSI/iSER and MPxIO Considerations
Creating an Analytics Worksheet
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 initiator group
Storage Array Type Plugin (satp)
Configuration Changes in a Clustered Environment
Clustering Considerations for Storage
Clustering Considerations for Networking
Clustering Considerations for Infiniband
Preventing 'Split-Brain' Conditions
The SAN configuration screen allows you to connect your appliance to your SAN (Storage Area Network). A SAN is made up of three basic components:
A client which will access the storage on the network
A storage appliance which will provide the storage on the network
A network to link the client to the storage
These three components remain the same regardless of which protocol is used on the network. In some cases, the network may even be a cable between the initiator and the target, but in most cases, there is some type of switching involved.
To configure the appliance to operate on a SAN, it is essential to understand some basic terms:
|
Additionally, it is important to be aware of SCSI transport protocols:
|
Refer to the documentation of IP-based Protocol Support and Initiator Support for details.
Targets and initiators are configured by protocol. Refer to the documentation on a particular protocol (FC, iSCSI or SRP) for details.
Target and initiators groups define sets of targets and initiators that can be associated with LUNs. A LUN that is associated with a target group can only be seen via the targets in the group. If a LUN is not explicitly associated with a target group, it is in the default target group and will be accessible via all targets, regardless of protocol. Similarly, a LUN that is associated with an initiator group can only be seen by the initiators in the group. If a LUN is not explicitly associated with an initiator group, it is in the default initiator group and can be accessed by all initiators. While using the default initiator group can be useful for evaluation purposes, its use is discouraged since it may result in exposure of the LUN to unwanted or conflicting initiators.
The following screenshot shows the Configuration > SAN screen. Use the Target and Initiator links to navigate. Then, click the Fibre Channel Ports, iSCSI Targets, or SRP Targets links to operate on targets by protocol type.
The above screenshot demonstrates creating a new FC target group by moving a discovered target to the Fibre Channel target list.
The following screenshot shows the Shares > Shares > Protocols screen. Use the Target Group or Initiator Group menus to associate a LUN.
Use the configuration san context of the CLI to operate on targets and initiators by protocol type. Then, use the shares CLI context to create LUNs and associate them with target and initiator groups.