What happened to the PowerConnect 62xx v3.0 firmware?
What happened to the PowerConnect 62xx v3.0 firmware? It was there a couple of weeks ago, but it's gone now. I just got a new PowerConnect 6224 and was going to upgrade it, but the firmware is gone. :emotion-3:
I just got off the phone with Dell Support and found out they pulled the v3.0.0.8 firmware because it causes the stack to fail. After we upgraded we have seen the switch go down about every two weeks. It stops layer 3 routing and you can't access any of the interfaces on the switch. They only thing you can do is a hard reboot by cutting the power to the switch. After it boots back up everything runs fine for the next two weeks then with no warning it just stops. When I called Dell they knew exactly what is was and told me to back down to 2.2.0.3 but to leave the newer June 30, 2009 boot code alone.
I don't know how long the image was on the FTP site before it was pulled, but I would guess at least a couple of months. When I spoke to Dell, they said that they were planning on releasing he 3.0 code as v3.0.0.13. However, that was probably at least two or three months ago. So, who knows...
That kind of sucks. I still have the v3 firmware downloaded, and was planning to install it soon. I dont have any 6200's in a stack just stand-alone, but I still dont want to install it if Dell pulled it from the download site.
We are using a stacked pair of 6224 switches for our iSCSI SAN (equallogic PS3900XV). We were told to upgrade to 3.0.0.8 because of iSCSI performance fixes. Can we downgrade back to 2.2.0.3 and still run iSCSI? If not, do we stay with 3.0.0.8 even though it was pulled?
It's hard to tell. We do see iSCSI timeouts, especially during backups when large amounts of data are transferred. Is this due to 3.0.0.8 or some other cause? How would we know?
deRahier
4 Posts
793
0
Posted September 29th, 2009 03:00
This is indeed a good question, I just saw that 3.0.0.8 has been removed for download.
I have no information why, unless it is related to the igmp-related migration problems that I mentioned 2 months ago...
Hope to have some official statement (do I need to roll back to v2.1 ??