Unsolved
This post is more than 5 years old
127 Posts
0
117395
March 4th, 2012 07:00
DCB - any problems out there?
Hi Don, hi group,
yesterday we did a huge upgrade, about 12 array to FW 5.2.1. In parallel, we upgraded our 8024F Systems to the latest FW (4.2.1.3) also. Now the 10 GB EQLs of ours do show DCB active when looking at the network config in EQL Web GUI. Does this have or could have ANY possible negative effect if we DID NOT configure anything on the 8024Fs (we even disabled iSCSI optimization on the 8024, i don´t like the idea that my switch makes decissions regarding MTU, Portfast, etc - i like do these things by myself)?. So to clarify: The 8024Fs are naked, no iSCSI optimization, just LAGs for uplinks to other 8024Fs.
The question would be what the 8024Fs do with Equallogics showing DCB active. As far as my understanding tells, there is no priority flow control if you don´t explicitly configure it at switch level. Is this correct?
And if you don´t configure anything on switch level and DCB shows up active in EQL - is the "normal" flow control of the 8024F used or is NO flow control used at all then? Don´t underestimate this question, i saw some scenarios in the past where stuff like that happened (but it was NO dell ;)).
So the final one: Could it mean ANY harm to my systems if DCB is turned on? And if yes, under which circumstances?
Best regards,
Joerg
0 events found
joergriether
127 Posts
0
March 4th, 2012 09:00
Hi Don,
first of all thank you very much for answering on a sunday - highly appreciated!
I can 100% confirm, a 6510 and 6010 running 5.2.1 connected to a 8024F running 4.2.1.3 SENSES AND ACTIVATES DCB.
I tried to append pics but that doesn´t work ;(
Now to my question: Will disabling DCB on the EQL Group Advanced Settings page does affect my running initiators in any way? Will there be a short disruption? Anything?
Best regards,
joergriether
127 Posts
0
March 4th, 2012 09:00
OK, uploaded it via picture sharing, take a look:
http://tinypic.com/r/ngelix/5
http://tinypic.com/r/j99ell/5
joergriether
127 Posts
0
March 5th, 2012 00:00
Thank you very much, Don.
Awaiting your intel.
Best regards,
Joerg
joergriether
127 Posts
0
March 5th, 2012 06:00
Thanks Don. Please keep me updated.
Best regards,
Joerg
joergriether
127 Posts
0
March 5th, 2012 10:00
ok i just did it - disabled DCB on a replication group - not that ugly if it would have crashed the port.
Now nothing happened - all volumes were NOT reconnected, still there. Permanent Ping did not drop.
And when looking at a port connected to an EQL now, et voila:
http://tinypic.com/r/72anag/5
But this is expected behaviour, am i right? because flow control is always on.
Best regards,
Joerg
joergriether
127 Posts
0
March 5th, 2012 10:00
Hi Don,
ofcourse flow control is on - flow control is the standard config when plugging in a brand new 8024 for the first time - and thus i didn´t change that i assume it is still on.
SO - knowing that - are you telling me i can safely disable DCB?
Best regards,
Joerg
joergriether
127 Posts
0
March 5th, 2012 13:00
aye, it does show DCB disabled.
joergriether
127 Posts
0
March 5th, 2012 13:00
-
joergriether
127 Posts
0
November 9th, 2012 09:00
Ähm....eight months later? I sure could the next weeks but i don´t know what that would bring to light, because neither our switch firmware matches the state of march 2012 nor the eql firmware matches. Besides, DCB is now turned off on all our EQLs.
Actually, we are in the process of doing some testlab work with the 8164F right now ;)
Best regards,
Joerg