Aruba & ProVision-based
cancel
Showing results for 
Search instead for 
Did you mean: 

Installing new modules in 5412Rzl2 chassis

SOLVED
Go to solution
SF8
Occasional Visitor

Installing new modules in 5412Rzl2 chassis

I am trying to install new modules into a chassis switch, though they will not come online. The switch is brand new and has not been configured at all. It has the latest firmware (KB.16.01.0006). There were different types of modules previously installed in these slots. I have rebooted the chassis several times, but each time I keep getting error: Slot X Inactive: Module/Configuration mismatch. I can install these modules in other slots on the chassis and they work without any problems, so I know they're compatible. 

I've tried rebooting the switch via CLI using 'reload' command while the modules were completely installed and also while modules have been removed. I have also tried rebooting the switch by removing the power cable and lastly tried reseting the switch by using the reset button on the mgmt console. Any other ideas I can try?

5 REPLIES
parnassus
Honored Contributor
Solution

Re: Installing new modules in 5412Rzl2 chassis

Which "new modules" exactly?

The KB.16.01.0006 isn't the latest version of KB.16.01 branch (that's just to be clear), and KB.16.01 isn't the latest branch too (the KB.16.02 software branch exists too).

What's about using the erase startup-config CLI command in order for the Switch to start from scratch?

SF8
Occasional Visitor

Re: Installing new modules in 5412Rzl2 chassis

Sorry, I read the wrong line, switch has version KB.16.02.0014 (the KB.16.01.0006 is the boot ROM version).

And I'm trying to install a 20 pt + 4 SFP port and a 20 port + 2SFP port modules. Neither of these modules has been installed in this particular switch before, but the slots that I'm installing them in had different kinds of modules in them (I believe they were both 24 port 1g modules).

I didn't think to erase startup-config since it hasn't been configured at all and I thought the reset button on the mgmt console did that. I just tried it and that seemed to do the trick. 

Thanks for your help!

parnassus
Honored Contributor

Re: Installing new modules in 5412Rzl2 chassis

Nice you solved so quickly.


SF8 wrote: Sorry, I read the wrong line, switch has version KB.16.02.0014 (the KB.16.01.0006 is the boot ROM version).

I think that the Aruba 5400R zl2 Flash Image software version KB.16.02.0014 actually uses BootROM version KB.15.01.0001 (do verify it with the show flash and show version commands) so if you saw something like KB.16.01.0006 it could have been the (Flash) secondary image software version...in that case the KB.16.02.0014 your Switch is currently operating from is the (Flash) primary image software version (which is probably the default software image the Switch is also booting from): that said it simply means that you have (Flash) Primary and Secondary images software versions currently "not aligned" (nothing particularly bad).

SF8
Occasional Visitor

Re: Installing new modules in 5412Rzl2 chassis

Show flash command results:

SWITCH# show flash
Image Size (bytes) Date Version
----------------- ------------ -------- --------------
Primary Image : 25487477 10/26/16 KB.16.02.0014
Secondary Image : 18487353 05/06/15 KB.15.17.0005

Boot ROM Version
----------------
Primary Boot ROM Version : KB.16.01.0006
Secondary Boot ROM Version : KB.16.01.0006

Default Boot Image : Primary
Default Boot ROM : Primary

And show version results:

SWITCH# sho ver
Management Module 1: Active
Image stamp:
/ws/swbuildm/rel_spokane_qaoff/code/build/bom(swbuildm_rel_spokane_qaoff_rel_sp
okane)
Oct 26 2016 10:57:51
KB.16.02.0014
373
Boot Image: Primary

Boot ROM Version: KB.16.01.0006
Active Boot ROM: Primary

I usually keep the secondary flash version an older version just in case the new version messes up or doesn't work correctly, etc. That way I have a known working flash that I can always boot into. :)


parnassus
Honored Contributor

Re: Installing new modules in 5412Rzl2 chassis

The output of show flash:

Image Size (bytes) Date Version
----------------- ------------ -------- --------------
Primary Image   : 25487477     10/26/16 KB.16.02.0014
Secondary Image : 18487353     05/06/15 KB.15.17.0005

Boot ROM Version
----------------
Primary Boot ROM Version   : KB.16.01.0006
Secondary Boot ROM Version : KB.16.01.0006

Default Boot Image : Primary
Default Boot ROM   : Primary

is very interesting: I didn't know that BootROM image version could have that value since in Release Notes of any KB.16.02 version (and at least from KB.16.02.0008) I always seen clearly stated that: "KB.16.02.0014 uses BootROM KB.15.01.0001. If your switch has an older version of BootROM, the BootROM will be updated with this version of software." probably that KB.15.01.0001 is a real typo.

I noticed instead that the KB.16.01.0011 Release Notes (and also all previous ones of KB.16.01 branch) reports the BootROM KB.16.01.0006 correctly!

HPE Documentation Team: please correct such typo!

The correct sentence on the latest KB.16.02.0014 Release Notes should be IMHO:

"KB.16.02.0014 uses BootROM KB.16.01.0006. If your switch has an older version of BootROM, the BootROM will be updated with this version of software."

About the double flash behaviour, yep it's a best practice...but I also align them once I see there aren't major issues showing up during the staging phase (I dislike to have two very different software images - one very new and the other one very old - with a configuration file basically binded to the newer one).