Hello duahimanshu,

Here is a link to the deployment guide for your MD3820i. http://topics-cdn.dell.com/pdf/powervault-md3800i_Deployment%20Guide3_en-us.pdf

For an MD3xxx system you don’t need to have bonded interfaces.

Please let us know if you have any other questions.

thanks for sharing document, i gone through it and i understand it. 

just let me know that you mean to say i no need to do bonding on host server i.e. Dell Power Edge's  10G ports, i just need to assign ip address on both the interfaces. right. ??

Dear sam,

I search ok internet and check the deployment document which u provided me, but still i am not getting my answer.  

I have two dell switches which is stack.

I have one dell power vault san storage with two raid controller.

I have dell power edge 530  with dual 10g ports amd red enterprise subscription.

Now what i did:-

Connectivity between Router and Switches.

1. Configured channel group on router and G0/0 is connected with Dell

Switch Port 1/0/1 and G0/1 is connected with Dell Switch 2/0/1. on the

switch channel group mode is on.

Connectivity Between Switches And Dell Power Edge:-

1. Server1, 10G port 1 to Switch one port 1/0/2

2.Server1 10g Port 2 to switch two port 2/0/2

Connectivity between Switches and SAN VAULT:-

1. Controller 0/Port0 to Switch one port 1/0/3

2. controller 0/Port1 to switch two port 2/0/3

3. Controller1/Port0 to switch one port 1/0/4

4.COntroller1/port1 to switch two  port 1/0/4

IP address of the Server:-

Initially i did bonding but as you said when connecting to san no need bonding:-

Server 10G port 1:- 172.16.18.9

Server 10G port 2:-172.16.18.10

IP address of the SAN VAULT;-

1. Controller 0/Port0=172.16.18.12

2. controller0/Port1=172.16.18.13

3. controller1/port0=172.16.18.14

4.Controller1/port1=172.16.18.15

Now the problem which i am facing is:-

1. while creating session:- we only able to crease session through one

lan. when we try to create session from the second lan it says "

session time out"

2. If i do bonding between both lans still  while creating session it allows through onw lan. The second path it doesnt take . Really dont why its happening or it should work like this????

2. We able to discover the SAN DRIVE unto the red hat server but the

drive are not stable like we mount the drive from

Application\Utility\disk. it shows but when we restart the server it

does not show again. then we have to mount it again??

I'd suggest to read the install guides, as you are definitely doing this setup wrong.

The SAN has 2 management ports. These should have IP addresses on your management network (for some this is just the 'LAN').

The iSCSI traffic needs to be completely isolated from the LAN traffic. This is preferably done via (2) dedicated switches, but can also be achieved with (2) isolated VLANs (w/o any routing in or out of these VLANs). Each VLAN/Switch then uses a unique subnet that isn't in use elsewhere in your whole network.

This should yield you IP addresses similar to this for iSCSI:

Controller 0 iSCSI port 0: 192.168.130.101

Controller 0 iSCSI port 1: 192.168.131.101

Controller 1 iSCSI port 0: 192.168.130.102

Controller 1 iSCSI port 1: 192.168.131.102

These are the factory defaults, but you can swap them with any other subnets, as long as ports 0 on each controller are in one subnet, and ports 1 on each controller are in a different subnet.

A cabling diagram for a PowerVault 10Gbit unit will look like the diagram on page 8 in this PDF.