Thanks so much for all your hard work on this project. It's greatly appreciated.As usual if you find any typos or have suggestions let me know. Beyond that I think I'm officially done with this project and I'm glad so many people got use out of it, it's been fun working with so many people.
Maybe there just aren't that many users out there - this thread is now the first hit on Google for "delta 7024" And most of the rest are about Delta airlines. I do see a single Delta 7024 on UK eBay, but just one, and at more than twice the price I paid for the LB6M. Though still significantly cheaper than the 8024, so definitely would worth doing for someone who had one.I did figure out how to do the same procedure on a Delta 7024 to turn it into a Dell 8024, but I still haven't found someone willing to try it
Oh wait, here is something interesting.Yes to both
See Configuring port flap dampening on a trunk
Was port 1 in your lacp by chance? I'm going through the brocade release notes to see if this was ever fixed, there's the v7 codetrain that has less features but seemingly more bugfixes (last v7 release for the turboiron was 7.4 in April of 2016, versus 2015 for the v8 image in this guide)
I'll post a link to the v7 image if you want to try it and make it flap, to see if it also locks up
interface ethernet 25 ethernet 26 ethernet 27 ethernet 28 link-aggregate conf key 10000 link-aggregate conf timeout short link-aggregate active show link-aggregate
I would really appreciate such a write-up for the S5800.Hope that works out with the Dell firmware! That would make these right up up there with current enterprise class switch offerings! Would also make it pair up even better with the H3C S5800 that I just got and converted to the latest HP A5800 software. If you are looking for a top shelf 48 port copper gigabit switch with 4 10Gbe SFP+ ports, find one. ... Edit to add, if anyone is interested I'll document all the steps and make an easy guide like we now have for the LB6M. Will make things a lot faster and easier if the steps were actually documented with some quick config tips and whatnot. Only gotcha is if some prior owner actually configured a bootloader password. No need to really but if that is set and not known then its pretty much over before you start. Any other passwords for the CLI or anything else can be removed easily as long as you can get into the bootloader on one.
Not sure how I missed this. If you can roughly match the format of the LB6M guide website I can throw your guide up on there as well (with credits to you of course). Check the github repo for the markdown source if you want a template to work off of. StackEdit is nice site if you want a simple way to write up markdown and see a preview as you workWould also make it pair up even better with the H3C S5800 that I just got and converted to the latest HP A5800 software.
the dampening feature doesn't solve the core problem that's making it flap, it just disables a port altogether (or for a specified amount of time) if it sees it go up and down a certain number of times. This prevents the flapping from carrying on forever and filling up your logs (and crashing in some cases too apparently). Still a very useful feature to enable. check this short guide, for a LACP group, just run these commands on every port member -Could this dampening commands mitigate the flapping with out-of-the-box settings ?
Not sure how I missed this. If you can roughly match the format of the LB6M guide website I can throw your guide up on there as well (with credits to you of course). Check the github repo for the markdown source if you want a template to work off of. StackEdit is nice site if you want a simple way to write up markdown and see a preview as you work
Do you happen to know what management CPU the HP/H3C uses? It looks like there's a slim chance it could match the LB4M, and new firmware for that would make a lot of people happy. Did you need to extract the bootloader out of the HP firmware BIN? I see a u-boot header, but no ending load instruction at the end of the u-boot section, at least not one that matches the jump at the end of our u-boot. I guess it could just be jumping to a different memory address
SW: Version 07.3.00sT203 Copyright (c) 1996-2013 Brocade Communications Systems, Inc. Compiled on Sep 29 2016 at 23:42:25 labeled as TIR07300s (6643818 bytes) from Primary TIR07300s.bin Compressed Boot-Monitor Image size = 369366, Version:07.3.00T205 (trz07300) HW: Stackable TurboIron-X24 ========================================================================== Serial #: 00000000000 P-ASIC 0: type B820, rev 11 subrev 00 ========================================================================== 825 MHz Power PC processor MPC8541E (version 8020/0020) 330 MHz bus 512 KB boot flash memory 31744 KB code flash memory 512 MB DRAM The system uptime is 1 minutes 36 seconds The system started at 19:15:19 GMT+00 Wed Feb 28 2018 The system : started=warm start reloaded=by "reload"
Compressed Pri Code size = 6643818, Version:07.3.00T203 (TIR07300s.bin) Compressed Sec Code size = 6845067, Version:08.0.01T203 (TIR08001e.bin) Compressed Boot-Monitor Image size = 369366, Version:07.3.00T205 (trz07300) Code Flash Free Space = 18219008
I have a feeling they just changed the fallback defaults for LACP from "short" in v7 to "long" in v8. Since your other end gear defaulted to "short", the v8 image default of "long" didn't match and caused flapping, but the "short" default in v7 matched. I don't think there's a right or wrong choice, the "short" default in v7 that works for your switches will break the other 50% of switches that default to long - this is why it's nice when gear auto negotiates timings like it should so it doesn't have to use default guesses in the first placeWell, I have flashed the V7 image now and the LACP channel doesn't flap anymore. I could not get it to flap. So now I have a V7 image in my primary flash and a V8 image in the secondary flash. Booting to the secondary (V8) flash with the same configuration makes the ports flap again and crash. Booting the primary (V7) image just works fine.
Long timeout: 120, default: 120 Short timeout: 3, default: 3 Port [Sys P] [Port P] [ Key ] [Act][Tio][Agg][Syn][Col][Dis][Def][Exp][Ope] 5 1 1 10000 Yes S Agg Syn Col Dis No No Ope 6 1 1 10000 Yes S Agg Syn Col Dis No No Ope
Interesting! I even remember a paragraph in the v8 manual that said something similar to this, it said something like "unplug or disable the ports on the other device while configuring a new LACP group or flapping may occur while the other device attempts to negotiate the LACP group before it has been fully defined on all interfaces"I also noticed that I can get the V8 LACP to work if I only enable one interface. Once the LACP connection is established I can enable the second interface and it links up too and works fine. However when I enable both links at the same time it flaps. V7 image works fine even if I enable both links at the same time.