• Hp Procurve Firmware Update
• Hp J4813a Procurve Switch 2524 Firmware Update
• Hp Procurve Switch Firmware Updater

Invest in networking switches. HPE network switches are built to handle today’s network traffic as well as the inevitable future increase in traffic. They are agile, scalable, and secure and can be easily integrated into your existing Aruba infrastructure.

This how-to will go through the process of updating the firmware on an HP switch. To check your current version run #show version from the command line. You will need a TFTP server for this. You can download one from http://www.solarwinds.com/products/freetools/freetftpserver.aspx. HP regularly releases new printer firmware versions with product enhancements or issue fixes. Depending on your printer, apps on the printer control panel might also receive updates. Update firmware and apps on a regular basis to make sure you are getting the most out of your printer. In this video you will see how to update your HP Switch firmware!.SORRY FOR THE VIDEO PROBLEMS! (you still can see the guidelines ).Update(3.1.2019). Invest in networking switches. HPE network switches are built to handle today’s network traffic as well as the inevitable future increase in traffic. They are agile, scalable, and secure and can be easily integrated into your existing Aruba infrastructure.

The switches covered in this guide feature two flash memory locations for storing switch software image files:

• Primary Flash: The default storage for a switch software image.

• Secondary Flash: The additional storage for either a redundant or an alternate switch software image.

With the Primary/Secondary flash option you can test a new image in your system without having to replace a previously existing image. You can also use the image options for troubleshooting. For example, you can copy a problem image into Secondary flash for later analysis and place another, proven image in Primary flash to run your system. The switch can use only one image at a time.

The following tasks involve primary/secondary flash options:

• Displaying the current flash image data and determining which switch software versions are available

• Switch software downloads

• Replacing and removing (erasing) a local switch software version

• System booting

Use the commands in this section to:

• Determine whether there are flash images in both primary and secondary flash

• Determine whether the images in primary and secondary flash are the same

• Identify which switch software version is currently running

Viewing the currently active flash image version. This command identifies the software version on which the switch is currently running, and whether the active version was booted from the primary or secondary flash image.

Syntax

For example, if the switch is using a software version of K.12.XX stored in Primary flash, show version produces the following:

The identity of the current flash image

Determining whether the flash images are different versions. If the flash image sizes in primary and secondary are the same, then in almost every case, the primary and secondary images are identical. This command provides a comparison of flash image sizes, plus the boot ROM version and from which flash image the switch booted. For example, in the following case, the images are different versions of the switch software, and the switch is running on the version stored in the secondary flash image:

Determining which flash image versions are installed. The show version command displays which software version the switch is currently running and whether that version booted from primary or secondary flash. Thus, if the switch booted from primary flash, you will see the version number of the software version stored in primary flash, and if the switch booted from secondary flash, you will see the version number of the software version stored in secondary flash. Thus, by using show version, then rebooting the switch from the opposite flash image and using show version again, you can determine the version(s) of switch software in both flash sources. For example:

Determining the software version in Primary and Secondary flash

The following table shows the switch’s options for downloading a software version to flash and booting the switch from flash.

Primary/Secondary memory access

The different software download options involve different copy commands, plus xmodem, usb, and tftp.

Download interruptions. In most cases, if a power failure or other cause interrupts a flash image download, the switch reboots with the image previously stored in primary flash. In the unlikely event that the primary image is corrupted, as a result of an interruption, the switch will reboot from secondary flash and you can either copy the secondary image into primary or download another image to primary from an external source.

This section describes commands for erasing a software version and copying an existing software version between primary and secondary flash.

Copying a switch software image from one flash location to another. When you copy the flash image from primary to secondary or the reverse, the switch overwrites the file in the destination location with a copy of the file from the source location. This means you do not have to erase the current image at the destination location before copying in a new image.

Syntax

copy flash flash<destination flash>

For example, to copy the image in secondary flash to primary flash:

• Verify that there is a valid flash image in the secondary flash location. The following figure indicates that a software image is present in secondary flash. (If you are unsure whether the image is secondary flash is valid, try booting from it before you proceed by using boot system flash secondary.)

Indicating two different software versions in Primary and Secondary flash

Execute the copy command as follows:

Erasing the contents of Primary or Secondary flash. This command deletes the software image file from the specified flash location.

Syntax

erase flash<primary | secondary>

For example, to erase the software image in primary flash, do the following:

1. First verify that a usable flash image exists in secondary flash. The most reliable way to ensure this is to reboot the switch from the flash image you want to retain. For example, if you are planning to erase the primary image, then first reboot from the secondary image to verify that the secondary image is present and acceptable for your system:

2. Then erase the software image in the selected flash (in this case, primary):

3. Type ‘y’ at the prompt to complete the flash erase.

4. Use show flash to verify erasure of the selected software flash image. The “0” shows that the primary flash has been erased.

   Show flash listing after erasing Primary flash

In redundant management systems, this command will erase the selected flash in both the active and the standby management modules. If redundancy has been disabled or the standby module has failed self-test, this command only affects the active management module.

Default boot source.The switch reboots from primary flash by default unless you specify the secondary flash by entering either the boot system flash [primary | secondary] or boot set-default flash [primary | secondary] command. Both the boot command and the reload command will reboot based on how these options have been selected.

Boot attempts from an empty flash location. In this case, the switch aborts the attempt and displays:

Interaction of Primary and Secondary flash images with the current configuration. The switch has one startup-config file (see Configuration file management), which it always uses for reboots, regardless of whether the reboot is from primary or secondary flash. Also, for rebooting purposes, it is not necessary for the software image and the startup-config file to support identical software features. For example, suppose you have just downloaded a software upgrade that includes new features that are not supported in the software you used to create the current startup-config file. In this case, the software simply assigns factory-default values to the parameters controlling the new features. Similarly, If you create a startup-config file while using a version 'Y' of the switch software, and then reboot the switch with an earlier software version 'X' that does not include all of the features found in 'Y', the software simply ignores the parameters for any features that it does not support.

Scheduled reload.If no parameters are entered after the reload command, an immediate reboot is executed. The reload at and reload after command information is not saved across reboots. If the switch is rebooted before a scheduled reload command is executed, the command is effectively cancelled. When entering a reload at or reload after command, a prompt will appear to confirm the command before it can be processed by the switch. For the reload at command, if mm/dd/yy are left blank, the current day is assumed.

The scheduled reload feature removes the requirement to physically reboot the switch at inconvenient times (for example, at 1:00 in the morning). Instead, a reload at 1:00 mm/dd command can be executed (where mm/dd is the date the switch is scheduled to reboot).

The switch offers reboot options through the boot and reload commands, plus the options inherent in a dual-flash image system. Generally, using boot provides more comprehensive self-testing; using reload gives you a faster reboot time.

Comparing the boot and reload commands

You can specify the default flash to boot from on the next boot by entering the boot set-default flash command.

Syntax

boot set-default flash [ primary | secondary ]

Upon booting, set the default flash for the next boot to primary or secondary.

Boot set-default command with default flash set to Secondary (with a redundant management module present)

The boot command boots the switch from the flash image that you are currently booted on, or the flash image that was set either by the boot set-default command or by the last executed boot system flash <primary | secondary> command. This command also executes the complete set of subsystem self-tests. You have the option of specifying a configuration file.

Syntax

boot [system[flash | <primary | secondary> ]] [config FILENAME]

Reboots the switch from the flash that you are currently booted on (primary or secondary). You can select which image to boot from during the boot process itself. When using redundant management, the switch will failover to the standby management module.

Note: This is changed from always booting from primary flash. You are prompted with a message which will indicate the flash being booted from.

system: Boots the switch. You can specify the flash image to boot from. When using redundant management, boots both the active and standby management modules.

config: You can optionally select a configuration file from which to boot.

Boot command (default Primary flash) with redundant management

In the above example, typing either a ‘y’ or ‘n’ at the second prompt initiates the reboot operation. (Entering ‘y’ saves any configuration changes from the running-config file to the startup-config file; entering ‘n’ discards them.)

Boot command booting from a different flash than the current flash (with redundant management module present)

This version of the boot command gives you the option of specifying whether to reboot from primary or secondary flash, and is the required command for rebooting from secondary flash. This option also executes the complete set of subsystem self-tests.

Syntax

boot system flash [<primary] | [secondary>]

For example, to reboot the switch from secondary flash when there are no pending configuration changes in the running-config file:

In the above example, typing either a [y] or [n] at the second prompt initiates the reboot operation.

Using the fastboot feature.The fastboot command allows a boot sequence that skips the internal power-on self-tests, resulting in a faster boot time. When using redundant management and fastboot is enabled, it is saved to the standby management module when the config files are synchronized. Fastboot is used during the next bootup on either management module.

Syntax

[no] fastboot

Enables the fastboot option

Syntax

show fastboot

Shows the status of the fastboot feature, either enabled or disabled.

The fastboot command is shown below.

Thereload command reboots the switch from the flash image that you are currently booted on (primary or secondary) or the flash image that was set either by the boot set-default command or by the last executed boot system flash <primary | secondary> command. Because reload bypasses some subsystem self-tests, the switch reboots faster than if you use either of the boot command options. If you are using redundant management and redundancy is enabled, the switch will failover to the other management module.

Syntax

reload

For example, if you change the number of VLANs the switch supports, you must reboot the switch in order to implement the change. Thereload command prompts you to save or discard the configuration changes.

Using reload with redundant management and pending configuration changes

Scheduled reload.Beginning with software release K.11.34, additional parameters have been added to thereload command to allow for a scheduled reboot of the switch via the CLI.

Syntax

[no] reload [after <[dd:]hh:] [mm>] | [at <hh:mm[:ss]>] [<mm/dd[/[yy]yy]>]

Enables a scheduled warm reboot of the switch. The switch boots up with the same startup config file and using the same flash image as before the reload.

Parameters include:

• after: Schedules a warm reboot of the switch after a given amount of time has passed.

• at: Schedules a warm reboot of the switch at a given time.

Thenoform of the command removes a pending reboot request.

For more details and examples, see below.

The scheduled reload feature removes the requirement to physically reboot the switch at inconvenient times (for example, at 1:00 in the morning). Instead, a reload at 1:00 mm/dd command can be executed (where mm/dd is the date the switch is scheduled to reboot).

Examples of scheduled reload commands:

• To schedule a reload in 15 minutes:

• To schedule a reload in 3 hours:

• To schedule a reload for the same time the following day:

• To schedule a reload for the same day at 12:05:

• To schedule a reload for some future date:

The reload command with a redundant management system

Module reload.The module reload feature allows you to reset a module by initiating a warm reboot of a specified module or modules. This saves time over rebooting the entire switch, which can take several minutes to complete and disrupts all users on the switch. The specified module has its power turned off, and then turned on again. This causes the module to reset to a known good state and reload its software.

Syntax

[no] reload [[after <[[DD:]HH:]MM>] | [[at HH:MM[:SS] [MM/DD[/[YY]YY]]]] | [[module<slot-id-range>]]]

When specified with themoduleparameter, initiates a reload of the module in the specified slot or slots by turning the slot power off, then on again. A valid slot or range of slots must be specified. Theatandafterparameters are not allowed with themoduleoption. Thenoversion of the command is not valid with themoduleoption.

When thereloadcommand is executed without any parameters, an immediate switch reload occurs.

module: Powers the module on or off, forcing a software reload of the specified module or modules.

Reloading a specified module

Displaying reload information. Use theshow reload command to display the reload information. This can include:

• A scheduled, pending reload of the entire switch

• A statement that no reload is scheduled

• The time of the last reload of each module on the system

The scheduled reload after information

Whilst learning about updating our HP Pro-curve switches, I found many contradicting pieces of information on how to do this. This is my method for updating via the web interface (Focusing on a 2910-24G-PoE+ al Switch). Please bear in mind that not all of the HP pro-curve switches support the web interface. I'm going to assume you don't necessarily know the model of your switch, so i'll explain how to find it. Before any thing else, it is massively important to ensure that no-one will be disrupted whilst you are working on the switch. In my case, I was able to update our switches during the Christmas break period. Very few users were on site, so it was a good opportunity to do so.

11 Steps total

Step 1: Ensure you know correct IP address

The IP address is used to connect your machine to the switch to do the update. You should have a record of these IP addresses available to you.

Step 2: Find the model of the switch you are updating

It is important to ensure you know the model of your switch, as the software is different for each model. I've placed the IP address of my switch into an internet browser (Note: some older HP switches require java support in browser), and you can see the model is a 2910-24G-PoE+ al Switch (J9146A)

Step 3: Obtain copy of new software from HP

Using the 'HP networking support tool', find the appropriate switch's links. Navigate to the software downloads page.

Step 4: Navigate to the software downloads page

Upon the page loading, you should find all of the available software for your switch. Ensure you know which version you are currently on (can be found via the web interface), and find the latest version. Also, it's always beneficial to read the release notes, both to check compatibility and to find which new features have been added/which bugs have been fixed.

Step 5: Download software

Once you've found the version you require, click on the marked button to continue to the download page.

Step 6: Open the web interface

Enter the IP address of your switch into a web browser. Log in with the 'manager' account and navigate to 'uploads/downloads' under the 'system' heading.

Step 7: Download configuration file

Important: HP always recommend backing up your switch's configuration file BEFORE updating software. Click on the listed configuration file and select download. This will download the configuration file to your local PC.

Step 8: Upload the software to the switch

Click on 'update' under the primary image. It will then ask you to choose a file. As default, the file for uploading uses the version of software as its title. In this case, W_15_14_0012.swi is the file required.

Hp Procurve Firmware Update

Step 9: Begin the upload/flash process

The switch will now prompt you to being the upload/flash. This may take a few minutes and the web interface should refresh when completed. DO NOT interrupt the power to the switch during this process, as it could easily cause irreparable damage to your hardware.

Step 10: Verify the switch has successfully written the new software

The page will re-load. The 'Primary' software image will now show the new version of software. The upload/flash was successful.

Step 11: Reboot the switch

Assuming that no one will be disrupted, reboot the switch from the web interface (using the link 'reboot'). Upon reboot, the switch will display the new software version on the home page. Check that all of your port configurations are still in place. If not, you can re-upload the configuration file (step 7, upload instead of download)

You've successfully updated you HP switch software. Remember, this guide only covers updating via the web interface and there are other methods of updating if this isn't suitable for you. The most common of these is via a TELNET session, which is covered in a 'how-to' by 'Gitclaus' found here: http://community.spiceworks.com/how_to/82205-how-to-update-hp-switch-firmware

Hp J4813a Procurve Switch 2524 Firmware Update

1 Comment

Hp Procurve Switch Firmware Updater

• Datil
  Pictuelle Dec 22, 2015 at 12:45pm

  Cool, this is pretty much true of any firmware updates,
  Insure correct model,
  Get the correct firmware,
  Disconnect (isolate) so there are no interruptions,
  Update,
  Reboot
  Log in and check the settings/set-up accordingly