What is your port MTU size set to? I'd recommend setting it to 9216 (PowerConnect 6248's maximum). If you set it to 9000, this has a high likelyhood of being part of the problem.

Hello Torito,

For your MD 3000i are you using all 4 nic’s on both Controllers or are you using less than that?  Also what is the current firmware of your MD3000i as well as you didn’t list that in your original post.    I would also do as Dev manger stated that if not set your MTU size to 9216 then try that & retest to see if you are getting the same issue.  

Please let us know if you have any other questions.

Dear Sam,

Yes, the current value in Powerconnect is 9216 (VSwitch and Controllers 9000 max. configuration value) and we have 2 controllers using 8 ports (192.168.130.X and 192.168.131.X networks)

Dell support made a Storage maintenance a week ago.

The md3000i  firmware data:

PowerVault MD Storage Manager

    AMW Version: 10.84.G6.44

    Report Date: Tue Jan 28 12:31:42 EST 2014

Storage Array

    Storage Array Name: BTPPMVMWISCSI01

    Current Package Version: 07.84.53.60

    Current NVSRAM Version: N26X0-784890-004

    Staged Package Version: None

    Staged NVSRAM Version: None

RAID Controller Modules

    Location: Enclosure 0, Slot 0

    Current Package Version: 07.84.53.60

    Current NVSRAM Version: N26X0-784890-004

    Board ID: 2660

    Sub-Model ID: 143

I have a big doubt, The MD3000i has frecuently in MD warnings as the next detail is shown:

Virtual Disk Not On Preferred Path

Storage array:  BTPPMVMWISCSI01

Preferred owner: RAID Controller Module in slot 1

Current owner: RAID Controller Module in slot 0

Affected disk group: GENERAL02_R10   

Virtual Disk:  GENERALE02_R10

Affected disk group:  GENERALS03_R5   

Virtual Disk:  GENERALS03_R5

Why can be happening it?

Thanks in advance

Hello Torito, You stated in your original post that you have a MD3000i but the firmware that is listed is the latest for an MD32xx or MD36xx, & I wanted to make sure which unit that you had. The Latest firmware for the MD3000i is 07.35.39.64 so I wanted to make sure that the correct firmware was installed for the correct unit. Please let us know if you have any other questions.

Dear Sam,

You are right! The model is MD3200i

Thanks in advance

Hello Torito,

Can I get you to gather a support bundle so that I can review to confirm that all updates took & make sure that there is no issues with the MD3200i.  I will send you a private message that you can reply with the logs.  

Please let us know if you have any other questions.

Hello Torito,

I tried to send you an email from the email that is listed to your profile but it comes back as undeliverable.  Can you check it to make sure that it is correct so i can send you this email.  

Please let us know if you have any other questions.

To answer if it's ok we need to know the current load on the devices: server, switch and storage itself. In normal situation you don't need to think about icmp. The metric you should warry about is delay to datastore which you can find in vsphere client (performance on datastore).

If it's 30ms or less you are ok.

There is one more thing you should know about this storage. There are design and hardware from last centure under the hood. Don't expect good performance or reliability. You can trust me I have two of these :) The only way we could work on these babies is qos on switches + a lot testing and load validation before implementation. Thanks god we've migrated to emc vnx with fcoe.

Dear eek ru,

I am checking the values in MD3200i

Thanks

Dear Sam,

I'm collecting data storage (support bundle).

Please, send me a private message again.

Thanks

Dear Sam,

I fixed email. Could you try again?

thanks so much

Hello Torito,

I just sent you the email.  

Please let us know if you have any other questions.

Thank you!

Fusion # 28015847 Hello Torito,

I have reviewed the support bundle that you sent, thanks for that.  I am not seeing any errors on the MD3200i. What I did notice is that out of your 12 VD that you have running on the MD3200i that 7 of them are not on their preferred owner, & when the report was created all 12 VD were running off controller 0.  Now this could be the reason why you are seeing pinging response times.  What I would recommend is that you redistribute the VD to the correct owner.  Here is the process for doing so & I will also send you another private message with the VD that needs to be switched to their preferred owner.  

The alert on the system is due to a virtual disk not being on the preferred path. When virtual disks are created, they are assigned to one of the two controllers as a preferred communication path. If that path is not available – due to a network issue, controller reset, etc. – the array will communicate via the alternate controller. In some cases the communication does not shift back to the primary path when it becomes available again.  To correct this you just need to manually redistribute the virtual disks back to their preferred paths.

To redistribute virtual disks:

1.            Open Modular Disk Storage Manager (MDSM)

2.            Click on the Support tab

3.            Select Manage Raid Controller Modules

4.            Click on Redistribute Virtual Disks

•             You will get an alert telling you that this will disrupt communications if you do not have the multipath drivers installed. You can ignore this message and proceed. If you still have access to the virtual disk that is not on preferred path, you have multipath drivers installed

Please let us know if you have any other questions.