Open for Voting

Feature Request - Support for HP switches .swi filename for firmware repository

When adding .swi firmware files (associated to HP Procurve/Aruba) switches to the repository, they do not "scan" thus are not available to push via NCM.

Would like support of HP/Aruba switches as we use them extensively at our location.  Lots of them.  Would be swell if we could upgrade them in bulk.

Parents
  • Are there other modifications you would like to see, in NCMs Firmware Upgrade, for your HP Procurve/Aruba devices? Beyond extending file support to .swi.

  • As someone who is newish to SolarWinds, have run NCM for a while purely for switch backups, and as a customer who has just purchased NPM, traffic analyser and IPAM, it seems to me that SolarWinds is very Cisco-entric. We have over 300 Aruba switches, with more incoming which will be running Aruba-CX. Im not interested in SW managing or monitoring my wireless, but for my wired LAN, support seems poor and for a newbie, the documentation seems even less for how to do anything when you are running a HPE/Aruba network.

    Being able to upgrade multiple switches using NCM would be a good start.

    Good documentation on templating configs and best practice for monitoring Aruba switches would be even better...If I've missed good documentation I apologise in advance

  • You can always reach out directly or post your question - the community as well many of us here at SolarWinds are always happy to help. Feel free to reach out to me with any specific questions you may have.

  • What you can do is rename your Aruba Firmware from .swi to .bin. NCM will then recognize it and you can install it via tftp command. I have not found a hp switch that insists on the firmware being .swi when uploading and installing.

  • Do you have an (HP) template that we see?

Comment Children
No Data