I am adding a 3810 to an existing stack. The stack is running 16.06.0006. I updated the switch being added to that version but the boot ROM version on the new switch is showing as 16.01..0009. Do I need the bootrom version to match between stack members?
BootROM updates are performed automatically during the boot process on ArubaOS-Switch when they are required, which is typically during the first boot using a switch software update that includes a BootROM revision. One thing to note is that the BootROM version number is not necessarily the same as the switch software version (in fact, they are almost always different, as they are entirely separate components).
Is there a document that details bootrom revision numbers. Based on the release notes I have reviewed I have not seen 16.01.0009 referenced anywhere but I do see 16.01.0008 in many.
Interesting; BootROM 16.01.0008 is the version included in the latest released builds of all current major software versions for the 3810 from KB.16.02 through KB.16.08. Which model of 3810 included the 16.01.0009 BootROM, and was it recently purchased?
In any case, as long as the switch software versions match between stack members, they should operate normally.
3810M / JL074A. This is an RMA sent to us from a support a case.
Would be interesting if you post the output of:
Here it is.
Aruba-3810M-48G-PoEP-1-slot# show flashImage Size (bytes) Date Version----------------- ------------ -------- --------------Primary Image : 33733822 06/22/18 KB.16.06.0006Secondary Image : 33733822 06/22/18 KB.16.06.0006
Boot ROM Version----------------Primary Boot ROM Version : KB.16.01.0009Secondary Boot ROM Version : KB.16.01.0009
Default Boot Image : PrimaryDefault Boot ROM : Primary
Aruba-3810M-48G-PoEP-1-slot# show ver
Image stamp:/ws/swbuildm/rel_washington_qaoff/code/build/bom(swbuildm_rel_washington_qaoff_rel_washington)Jun 22 2018 12:34:17KB.16.06.0006923Boot Image: Primary
Boot ROM Version: KB.16.01.0009Active Boot ROM: Primary
That's good to know! It looks like newly-manufactured switches are getting preloaded with a newer BootROM build at the factory; this should have no effect on switch operation.
The newer bootroms are also be loaded for 2930F switches - this is creating issues forming VSF stacks when the bootroms are different between chassis.
2930F normal bootrom for firmware 16.08 is bootrom WC.16.01.0004, however many are currently shipping with WC.16.01.0005
Would be a good future feature to be able to force a manual bootrom updrade/downgrade rather than only as part of a firmware update (which only updates the bootroom if the version requires a new minimum release, and never downgrades).
Also relevant Release Notes (e.g. Aruba 2930F) should be updated accordingly: if we look at very latest Aruba 2930F WC.16.08.0001 Release Note of January, 2nd 2019 (which is the 2nd Edition) there is no mention of any BootROM version change (and possible impact of that change in VSF scenarios).
Have you observed actual failures in forming a VSF stack between switches running different BootROM versions, even when they are running the same switch software? If so, could you post any relevant (sanitized) event log entries and 'show vsf' output?
Thanks Matt. Yes we have see VSF stack failures.
I dont have access to this environment any longer however here are two screenshots showing the incompatibleOS failure caused by the bootrom.
bootrom releasesVSF failure - IncompatibleOs
How did you fixed this issue? I will make a VSF stack today with 2* 2930F switches and they have also different boot versions (16.01.0005 and 16.01.0004) but the same software: 16.06.0006.
I did not make the VSF link yet, the newer switch (with boot ROM 16.01.0005) is at factory defaults (I downgraded it from 16.07.0003 to 16.06.0006 because that's the current firmware on the switch that's already in production). Can I downgarde his boot ROM?
I'm not totally sure...but downgrading the BootROM looks not possible (swi file embeds BootROM)...downgrading is seldom a recommendable procedure...my take is that you should update your System Software on running Aruba 2930F (in order to have your BootROM updated too [*]) and then deploy the VSF.
[*] consider that WC.16.09.0001 software release uses BootROM WC.16.01.0006 or BootROM WC.16.01.0007 (JL692A only) when running on Aruba 2930F...so your BootROMs 16.01.0005 and 16.01.0004 will be both updated if you perform the system software update to WC.16.09.0001 (that's an example, other recent WC software branches software version should produce the same result).
Indeed, I also thought downgrading was no option, so I upgraded to 16.09 so both existing boot ROM versions upgraded. Then I made my stack and everything works fine now.
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2021 Hewlett Packard Enterprise Development LPAll Rights Reserved.