Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

Article Number: 000147737

How to configure an iSCSI network on Compellent

Summary: Our charter is to deliver solutions that simplify IT by providing database solutions, custom development, dynamic datacenters, flexible computing.

This article may have been automatically translated. If you have any feedback regarding its quality, please let us know using the form at the bottom of this page.

Article Content

Symptoms

Applies to: 

Storage Platform(s) – Dell Compellent Series 40 and Dell Compellent Series 30 storage systems with Storage Center 5.4 and greater 


Author:

Ramamohan Reddy K


Problem:

How to configure iSCSI network on Compellent?

Solution:

Front end cabling and Fault Domain configuration of iSCSI network is same as the FC.Follow the wiki for front end cabling and domain configuration.But in iSCSI there will be a control port configured for each Fault Domain.
This control port redirects the iSCSI traffic to corresponding virtual ports.

 
SLN310492_en_US__1icon NOTE: Create separate and unique subnets for each Fault Domain network. Different fault domains with the same subnet can confuse a server trying to determine the proper connection path.
Example: Suppose if you want to configure two Fault Domains in the iSCSI network you can configure below:

Fault Domain1

Controller A Port1 IP address 192.168.1.1
subdomain 255.255.255.0

Controller B port1 IP address 192.168.1.2
subdomain 255.255.255.0

Control port IP address 192.168.1.3

subdomain 255.255.255.0

Fault Domain 2

Controller A Port 2 IP address 192.168.2.1
subdomain 255.255.255.0

Controller B port 2 IP address 192.168.2.2

subdomain 255.255.255.0

Control port IP address 192.168.2.3

subdomain 255.255.255.0

In FC network, connection will be established immediately between all the ports which are zoned together. Whereas, iSCSI network is not zoned and you need to initiate all connections from servers.
 

Discovering compellent targets:

Discover the iqn of the compellent ports using faultdomain control port. 

iscsiadm -m discovery -t sendtargets -p <faultdomain_ip_address> 

Where, faultdomain _ip_address is the control port IP address of the fault domain in the Compellent storage.

For example, the following command discovers the iqn of the compellent ports which are associated to Fault Domain 1.

# iscsiadm -m discovery -t sendtargets -p 192.168.1.3

192.168.1.3:3260,0 iqn.2002-03.com.compellent:5000d31000295251

192.168.1.3:3260,0 iqn.2002-03.com.compellent:5000d31000295253

And the following command discovers the iqn of the compellent ports which are associated to Fault Domain 2.

# iscsiadm -m discovery -t sendtargets -p 192.168.2.3

192.168.2.3:3260,0 iqn.2002-03.com.compellent:5000d31000295252

192.168.2.3:3260,0 iqn.2002-03.com.compellent:5000d31000295254


Logging compellent targets:

Once you have discovered your compellent targets, you can log in the target as follows:

# iscsiadm -m node --login

Logging in to [iface: default, target:
iqn.2002-03.com.compellent: 5000d31000295251, portal: 192.168.1.3, 3260]

Logging in to [iface: default, target:
iqn.2002-03.com.compellent: 5000d31000295253, portal: 192.168.1.3, 3260]

Login to [iface: default, target:
iqn.2002-03.com.compellent: 5000d31000295252, portal: 192.168.2.3, 3260]:successful

Login to [iface: default, target:
iqn.2002-03.com.compellent: 5000d31000295254, portal: 192.168.2.3, 3260]:successful

Once login to compellent targets succeeded, server object can be created on the Compellent Storage Center. Once the servers created in the Compellent Storage Center use the wiki article to give host
access to Compellent volumes.

Article Properties

Last Published Date

10 Apr 2021

Version

3

Article Type

Solution

Back to Top