Dell Equallogic PS6000 setup problem

Storage

Storage
Information and ideas on Dell storage solutions, including DAS, NAS, SAN and backup.

Dell Equallogic PS6000 setup problem

This question is answered

Hi everyone, we're some problems doing the basic configuration of a PS6000. Getting very frustrated!

We have a completely isolated, standalone network set up which consists of two stacked Dell 6224 switches. On the network we have a Windows Server 2008 R2 machine running the Remost Setup Wizard. The server is a basic build, no additonal roles or features added. There is no uplink from the network to any other FW's or networks, it is completely isolated.

We have installed the tools that came with the array, and accepted all the necessary changes to the Server's FW, added all the additional components as requitred and so on. We have connected the PS6000 to the network and are running the Remote Setup Wizard to configure it. The first screen detects the PS6000 correctly via its MAC address, we select it and move to the next screen. We assign it a name, an IP address from the subnet range on this network, an appropriate subnet mask and the default gateway. That all goes fine.

On the next screen we assign the Group name, Group IP address and all the various Group, joining and CHAP passwords. All the passwords are accepted and approved. However on clicking "Next" we get an error that says: "Incomplete Information - Enter the Following: Group IP (address provided already in use by another host)" and we can't progress any further.

This cannot be the case - the IP address is not in use as there are only 3 other devices on this entire network. There is no DHCP or anything else providing addresses and no other hosts to pick them up. We can put any address we like into this field (within the appropriate subnet, of course) and get the same error message. Pick any random address, it's already in use, or so the Wizard claims.

This unit is straight out of the box, never switched on before, never previously configured, brand spanking new. Anyone else experienced this or have any advice?

TIA,

Tim Lovegrove

Verified Answer
  • I'm not sure if this is relevant but I ran into a  similar error today configuring a PS6000 SAN.  After much stuffing around I found that the IP address I tried to configure for the Group IP Address, when pinged, returned a "Destination host unreachable" response as opposed to what you would expect in the form of: "Request Timed Out".  When I tested from other servers I got "Request Timed Out" notifications so I went back to the original server and cleared the routing table by going to the command line and executing a " route -f " with the route utility.  After which pings returned "Request timed out" messages and I could move on through the SAN configuration.

    Not sure if this will help but I thought I would post in case I can spare someone else the time and hassle.

All Replies
  • Tim,

    First, ensure you have a unique IP address for the member IP (the first IP address requested) and the Group IP address (they must be different).  The member IP is the eth0 IP address, where the group IP is a virtual IP that the HOST iSCSI initiator uses to discover the group, and redirect the initiator to a physical IP on the array.

    You didn't indicate the type of interface on the host you are using to run RSW, i.e., NIC, HBA.  You may need to check the properties to ensure they are setup correctly for iSCSI, do a search in the EqualLogic knowledge base for “wizard”.

    Also, (although not usually related to duplicate IP messages, but will effect performance) ensure you have your 6224 switches setup on a unique VLAN for iSCSI, do not use the default VLAN (see the support site KB and search on “default VLAN” for further info why we recommend this).

    Joe

    Follow me on Twitter: @joesatdell

     

  • If there is nothing on the PS6000 yet, then console into it, or ssh, telnet, whatever to the IP address you're trying to use, reset it (wipes the config) and then try again. They'll be much quicker than getting on with support, if it's empty.

    Sr. Virtualization Specialist
    Michael F Kelly Jr.

  • @Joe: Many thanks for the pointers. The Group and Member IP addresses are unique, the only other addresses on the network are the Server and the network switches, so I have plenty to choose from! I will look more into the properties of the server's NIC that I'm using to run the RSW. Your suggestion makes me think it isn't fully or correclty set up for the iSCSI side.

    I'll also get the switches set up on a new VLAN for the iSCSI - I wasn't aware that was the recommended approach so many thanks for htat.

    @mfkelly: thanks also for your suggestion, if I get no joy with Joe's suggestions I'll reset and try again.

  • Tim,

    Another item may be the mac address table on the switch is corrupted, if you can restart the switch.  If you have two switches stacked, check the trunk ports between switches, you may not have spanning tree enabled on them.

    You may also want to try the Remote Setup Command Line utility, it’s discussed in the HIT user guide.

    Finally, if all else fails use the serial interface on the array to setup the member.

    Regards,

    Joe

    Follow me on Twitter: @joesatdell

     

  • " If you have two switches stacked, check the trunk ports between switches, you may not have spanning tree enabled on them."

    If the switches are stacked, there shouldn't be trunk ports between the switches. Trunk ports are only used if you aren't stacking. The stacking connections between the switches don't need any settings as such in an iSCSI setup; they just extend the 'switch' to have more ports more or less.

    Member since 2003

  • Yes, agreed, if using the stacking cable, you don't need to setup spanning tree.  I wasn't clear, I was referring to an ISL between the switches, without a stacking cable.

    Joe

    Follow me on Twitter: @joesatdell

     

  • I'm not sure if this is relevant but I ran into a  similar error today configuring a PS6000 SAN.  After much stuffing around I found that the IP address I tried to configure for the Group IP Address, when pinged, returned a "Destination host unreachable" response as opposed to what you would expect in the form of: "Request Timed Out".  When I tested from other servers I got "Request Timed Out" notifications so I went back to the original server and cleared the routing table by going to the command line and executing a " route -f " with the route utility.  After which pings returned "Request timed out" messages and I could move on through the SAN configuration.

    Not sure if this will help but I thought I would post in case I can spare someone else the time and hassle.

  • Stryder110 - annoying that such a simple thing could resolve the issue! Thank you - that's got me going.

    Thanks to everyone else for their assistence, I've learned a lot about the necessary configurations from this thread.

  • I had to turn the Windows Firewall off in addition the the "route -f".

  • route -f worked for me, thanks for posting