Unsolved

This post is more than 5 years old

17 Posts

7596

May 2nd, 2006 16:00

ax100, iSCSI, bizarre connectivity issues

hey all,

It seems I can either communicate with the ax100 through the iSCSI initiator OR have access to the rest of the network but not both. When I connect the ax100 through a switch I can get to the device through the webservice but not through the iSCSI initiator. If I connect the SP directly to the server then I have access to the device through the initiator but I can't get to ANYTHING ELSE.

What am I missing here?

6 Operator

 • 

9.3K Posts

May 2nd, 2006 20:00

It sounds like you set up conflicting IP addresses, or have assigned IP addresses in the same subnet.

The 2 management ports should be in the same subnet as the rest of your systems (servers). The iSCSI ports are best off being assigned IP addresses in a completely different subnet.

Effectively if you have a dual storage processor unit, you would end up needing 4 different IP addresses for the AX100i.

17 Posts

May 3rd, 2006 11:00

That certainly sounds like a good plan. You did nail it, my config isn't like what you discribed. Lemme see what I can do about this.

96 Posts

May 15th, 2006 21:00

The management IP addresses are typically on the same subnet, so you would typically have 3 different subnets, not 4.  But, that is when you have at least 3 NICs in the server (1-public, 2-iSCSI traffic)  The management ports would be pluged into the public NIC, while each NIC for iSCSI traffic would be on different subnets.  If you only have 2 NICs in the server, you would use 1 NIC for public traffic and 1 for iSCSI traffic, in that case, both iSCSI ports on the array would be on the same subnet (but different from the management ports)
 
I recommend referencing figure 7 of the printed planning guide that shipped with the system. 
 
The planning guide has different sample configs with example subnets.
 
There are also interactive install and plannig guides located at http://www.emc.com/dell-ax100support
 
The key thing to remember all NICs on the server must be on different subnets, unless teamed.  Teaming is not supported for iSCSI traffic.
 

Message Edited by JTGlenn on 05-15-200605:26 PM

0 events found

No Events found!

Top