Switch Fails to Reboot How to Upload Ios Image

Using Master and Secondary flash image options

The switches covered in this guide feature two flash retentivity locations for storing switch software paradigm 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 epitome.

With the Primary/Secondary flash option yous tin examination a new epitome in your organisation without having to replace a previously existing image. You lot can as well employ the image options for troubleshooting. For example, you tin can copy a problem paradigm into Secondary flash for later assay and place some other, proven image in Chief flash to run your system. The switch can use simply one prototype at a fourth dimension.

The following tasks involve primary/secondary flash options:

• Displaying the electric current flash image information and determining which switch software versions are bachelor

• Switch software downloads

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

• System booting

Displaying the electric current flash image data

Use the commands in this department to:

• Make up one's mind whether at that place 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 wink prototype version. This command identifies the software version on which the switch is currently running, and whether the agile version was booted from the chief or secondary flash paradigm.

Syntax

prove version

For instance, 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 epitome

HP Switch(config)# evidence version  Image stamp:  /su/lawmaking/build/info(s01)               Dec 01 2006 10:l:26               K.12.20               1223 Boot Image:   Primary            

Determining whether the flash images are different versions. If the flash epitome sizes in main and secondary are the aforementioned, then in almost every case, the primary and secondary images are identical. This command provides a comparison of flash image sizes, plus the kick ROM version and from which wink image the switch booted. For example, in the post-obit example, the images are dissimilar versions of the switch software, and the switch is running on the version stored in the secondary flash image:

Different flash image versions

HP Switch(config)# show wink Image            Size(Bytes)   Date   Version -----            ----------  -------- ------------- Primary Image    : 7493854   03/21/10 K.xv.01.0001 Secondary Paradigm  : 7463821   03/23/10 K.15.01.0001  Kicking Rom Version: K.15.08 Default Boot    : Primary            

Determining which flash prototype 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 wink, y'all will see the version number of the software version stored in principal flash, and if the switch booted from secondary flash, yous will come across the version number of the software version stored in secondary flash. Thus, past using show version, then rebooting the switch from the opposite flash image and using show version once again, you lot tin can determine the version(s) of switch software in both flash sources. For instance:

Determining the software version in Master and Secondary flash

HP Switch(config)# bear witness version Management Module i: Agile Image postage stamp:    /sw/lawmaking/build/btm(ec_K_15)                 Aug two 2012 09:06:58                 K.15.12.001                 152 Boot Prototype:     Primary HP Switch(config)# boot system flash secondary Device volition exist rebooted, do you want to continue [y/n]? y   .   .   .  HP Switch(config)# evidence version Management Module 1: Active Paradigm postage stamp:    /sw/code/build/btm(ec_K_15)                 Aug ii 2012 09:06:58                 Grand.fifteen.12.001                 1753 Boot Image:     Secondary            

Switch software downloads

The post-obit table shows the switch'due south options for downloading a software version to flash and booting the switch from flash.

Primary/Secondary memory access

Activeness	Carte du jour	CLI	Web Amanuensis	SNMP
Download to Primary	Yeah	Yeah	Yes	Yes
Download to Secondary	No	Yes	No	Yes
Kicking from Primary	Yes	Yeah	Yes	Yeah
Boot from Secondary	No	Yes	No	Yes

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

Download interruptions. In well-nigh cases, if a power failure or other cause interrupts a wink prototype download, the switch reboots with the paradigm previously stored in primary flash. In the unlikely effect that the primary image is corrupted, equally a outcome of an interruption, the switch will reboot from secondary flash and yous tin can either copy the secondary paradigm into primary or download another prototype to principal from an external source.

Local switch software replacement and removal

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

	NOTE: It is not necessary to erase the content of a flash location before downloading some other software file. The process automatically overwrites the previous file with the new file. If you want to remove an unwanted software version from flash, HP recommends that you lot exercise so past overwriting it with the same software version that y'all are using to operate the switch, or with another acceptable software version. To re-create a software file betwixt the primary and secondary flash locations, Encounter "Copying a switch software paradigm from one flash location to some other", below. The local commands described here are for flash image management within the switch. To download a software prototype file from an external source, come across "File Transfers" in the Management and Configuration Guide for your switch.

Copying a switch software image from one flash location to another. When y'all copy the flash prototype 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 practise not have to erase the current paradigm at the destination location before copying in a new paradigm.

	Caution: Verify that there is an adequate software version in the source wink location from which you lot are going to re-create. Use the show flash control or, if necessary, the procedure nether Displaying the current flash epitome data to verify an acceptable software version. Attempting to copy from a source image location that has a corrupted flash image overwrites the prototype in the destination wink location. In this case, the switch will not accept a valid flash epitome in either flash location, but will continue running on a temporary wink image in RAM. Do not reboot the switch. Instead, immediately download another valid flash image to primary or secondary wink. Otherwise, if the switch is rebooted without a software epitome in either primary or secondary flash, the temporary flash image in RAM will be cleared and the switch will go down. To recover, see "Restoring a Flash Paradigm" in the Management and Configuration Guide for your switch.

Syntax

copy wink flash <destination flash>

where: destination flash = chief or secondary :

For case, to re-create the epitome in secondary wink to main flash:

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

Indicating two different software versions in Chief and Secondary flash

HP Switch(config)# bear witness wink Image             Size (bytes) Appointment     Version ----------------- ------------ -------- -------------------- Primary Image     : 10167529    10/14/11 K.14.89 Secondary Paradigm   : 15085139    08/17/12 K.15.10.0001  Boot ROM Version : K.fifteen.28 Default Boot     : Principal            

Execute the copy command equally follows:

HP Switch(config)# re-create flash wink primary          

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

	CAUTION: No undo! Before using this command in one wink image location (primary or secondary), ensure that you take a valid software file in the other wink paradigm location (secondary or primary). If the switch has only ane flash prototype loaded (in either master or secondary flash) and you erase that image, then the switch does not have a software image stored in flash. In this case, if y'all practice not reboot or power cycle the switch, yous tin can recover by using xmodem or tftp to download another software epitome.

Syntax

erase wink <primary | secondary>

For example, to erase the software epitome in principal flash, do the post-obit:

1. Offset verify that a usable flash paradigm exists in secondary flash. The virtually reliable way to ensure this is to reboot the switch from the wink image yous want to retain. For instance, if y'all are planning to erase the primary epitome, then first reboot from the secondary image to verify that the secondary image is present and adequate for your system:

   HP Switch# boot arrangement flash secondary                

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

   Erase Flash Prompt

   HP Switch# erase flash primary The Main OS Image volition be deleted, continue [y/n]?                  

3. Type 'y' at the prompt to consummate the flash erase.

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

   Bear witness flash listing after erasing Primary flash

   HP Switch# show wink  Compressed Principal Code size   = 0 Compressed Secondary lawmaking size = 2555802 Boot ROM Version : K.xv.xix Default Boot     : Secondary                  

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

Rebooting the switch

Operating notes about booting

Default kicking source. The switch reboots from primary flash by default unless you specify the secondary flash by inbound either the boot organization flash [primary | secondary] or kicking set-default flash [primary | secondary] control. Both the kick 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 endeavor and displays:

Paradigm does non exist Operation aborted.            

Interaction of Primary and Secondary flash images with the current configuration. The switch has 1 startup-config file (encounter Configuration file management), which it ever 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 prototype and the startup-config file to support identical software features. For case, suppose you have just downloaded a software upgrade that includes new features that are not supported in the software y'all used to create the electric current startup-config file. In this case, the software only assigns manufactory-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 before software version "X" that does not include all of the features plant in "Y", the software only ignores the parameters for whatever features that information technology does not back up.

Scheduled reload. If no parameters are entered later 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 control is effectively cancelled. When entering a reload at or reload after command, a prompt will appear to confirm the command before it can exist processed past the switch. For the reload at control, if mm/dd/yy are left bare, 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 i:00 mm/dd command tin can exist executed (where mm/dd is the engagement the switch is scheduled to reboot).

Kicking and reload command comparison

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

Comparing the boot and reload commands

Actions	Included in Boot?	Included in Reload	Note
Salvage all configuration changes since the last boot or reload	Optional, with prompt	Optional with reload <cr>, when prompt displays. Not saved with reload at/after commands; No prompt is displayed.	Config changes saved to the startup-config file if "y" is selected ( reload command).
Perform all system self-tests	Yes	No	The reload control provides a faster system reboot.
Choice of primary or secondary flash image	Yes	No—Uses the current wink paradigm.
Perform a scheduled reboot	No	Yes	Use the reload command with after/at parameters (see Using reload for details).

Setting the default flash

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, ready the default wink for the next kick to primary or secondary.

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

HP Switch(config)# boot gear up-default flash secondary HP Switch(config)# show flash Image           Size(Bytes)   Date    Version ------          ----------   -------  ------------- Primary Image   : 7476770    03/15/10 K.15.01.0001 Secondary Paradigm : 7476770    03/fifteen/10 Yard.15.01.0001  Boot Rom Version: K.xv.08 Default Boot    : Secondary  HP Switch(config)# kicking This management module will now reboot from secondary and will become the standby module! You will need to  use the other direction module'south console interface. Exercise you lot want to continue [y/n]?              

Booting from the default flash (Primary or Secondary)

The kicking command boots the switch from the wink paradigm 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 organisation flash <primary | secondary> control. This control also executes the complete fix of subsystem self-tests. Yous 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 (principal or secondary). You lot can select which image to boot from during the kicking procedure itself. When using redundant management, the switch will failover to the standby management module.

Notation : This is changed from always booting from primary flash. You are prompted with a message which volition signal the flash being booted from.

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

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

Boot command (default Primary wink) with redundant management

HP Switch(config)# boot This management module will now reboot from principal paradigm and will become the standby module! You will demand to employ the other management module's console interface. Do y'all want to proceed [y/n]? y  Do you want to save current configuration [y/n]? n              

In the above case, typing either a 'y' or 'northward' at the second prompt initiates the reboot performance. (Inbound 'y' saves any configuration changes from the running-config file to the startup-config file; entering 'n' discards them.)

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

HP Switch(config)# show flash Epitome Size(Bytes) Date Version Primary Epitome : 7497114 03/29/x K.15.01.0001 Secondary Image : 7497114 03/29/10 Thousand.xv.01.0001 Kick Rom Version: Yard.15.08 Default Boot : Chief   HP Switch(config)# boot ready-default flash secondary This control changes the location of the default boot. This command volition change the default flash image to kicking from  secondary. Hereafter, 'reload' 'boot' commands will boot from secondary. Do you lot desire to go on [y/northward]? y  HP Switch(config)# boot This management module will now reboot from secondary paradigm and will go the standby module! You will need to use the other management module's console interface. Practice you want to continue [y/north]? n              

Booting from a specified wink

This version of the boot command gives you lot the choice of specifying whether to reboot from primary or secondary flash, and is the required control for rebooting from secondary flash. This option too executes the consummate fix of subsystem self-tests.

Syntax

boot organization flash [ <master ] | [ secondary> ]

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

Boot command with secondary wink option

HP Switch(config)# kicking system flash secondary System will be rebooted from secondary image. Practise yous desire to continue [y/n]?              

In the in a higher place example, typing either a [y] or [n] at the second prompt initiates the reboot functioning.

Using the fastboot feature. The fastboot command allows a kick 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 direction module when the config files are synchronized. Fastboot is used during the next bootup on either management module.

Syntax

[no] fastboot

Enables the fastboot selection

The no option disables the feature.

Syntax

show fastboot

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

The fastboot command is shown below.

HP Switch(config)# fastboot            

Using reload

The reload command reboots the switch from the flash image that you are currently booted on (primary or secondary) or the wink prototype that was set either by the boot set-default command or by the concluding executed boot system flash <primary | secondary> command. Considering reload bypasses some subsystem self-tests, the switch reboots faster than if you lot use either of the kicking command options. If you are using redundant direction 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, yous must reboot the switch in social club to implement the modify. The reload command prompts you lot to save or discard the configuration changes.

Using reload with redundant direction and awaiting configuration changes

HP Switch(config)# max-vlans 12 Command will take effect after saving configuration and reboot.  HP Switch(config)# reload This command will cause a switchover to the other management module which may not be running the aforementioned software paradigm and configurations. Do you want to go along [y/north]? y              

Scheduled reload. Beginning with software release K.11.34, additional parameters take been added to the reload 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 prototype as before the reload.

	CAUTION: When using redundant management, the reload at/after command causes a switchover at the scheduled time to the other direction module, which may non exist running the same software epitome or have the same configurations.

Parameters include:

• afterwards : 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.

The no form 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 i:00 in the morning). Instead, a reload at i:00 mm/dd command can be executed (where mm/dd is the appointment the switch is scheduled to reboot).

Examples of scheduled reload commands:

• To schedule a reload in xv minutes:

  HP Switch# reload after 15                      

• To schedule a reload in three hours:

  HP Switch# reload afterward 03:00                      

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

  HP Switch# reload after 01:00:00                      

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

  HP Switch# reload at 12:05                      

• To schedule a reload for some futurity date:

  HP Switch# reload at 12:05 01/01/2008                      

The reload command with a redundant management system

HP Switch(config)# reload subsequently 04:14:00     Reload scheduled in 4 days, 14 hours, 0 minutes This command will cause a switchover at the scheduled fourth dimension to the other management module which may not be running the same software paradigm and configurations. Exercise you lot desire to keep [y/n]?              

Module reload. The module reload characteristic allows yous to reset a module by initiating a warm reboot of a specified module or modules. This saves time over rebooting the unabridged switch, which can accept 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 the module parameter, 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. The at and after parameters are not immune with the module option. The no version of the command is not valid with the module option.

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

	Note: This feature is not supported for HP One modules.

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

Reloading a specified module

HP Switch(config)# reload module C The 'reload module' command volition shutdown the specified modules. Ports on specified modules will no longer pass traffic. Any management traffic to the switch which passes through the afflicted modules will exist interrupted (e.g. ssh, telnet, snmp). This control may take up to 2 minutes to ability down all specified modules. Delight check  the event log for current status of module power down, power up cycle. Keep [y/n]?              

Displaying reload information. Apply the bear witness reload command to brandish the reload information. This tin 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 at information

HP Switch(config)# reload at 23:45 Reload scheduled at 23:45:47 six/16/2012 (in 0 days, 1 hours, 41 minutes  HP Switch(config)# show reload at Reload scheduled for 23:45:47 06/xvi/2012 (in 0 days, ane hours, 40 minutes)  HP Switch(config)# show reload after Reload scheduled for 23:45:47 vi/16/2012 (in 0 days, 1 hours, twoscore minutes)              

The scheduled reload after information

HP Switch(config)# reload after 35 Reload scheduled in 0 days, 0 hours, 35 minutes  HP Switch(config)# testify reload at Reload scheduled in 0 days, 0 hours, 34 minutes  HP Switch(config)# show reload after Reload scheduled in 0 days, 0 hours, 34 minutes              

The module reload data

HP Switch(config)# show reload module  Module Reload information:  Module | Final reload date -------+---------------------   C      10:fifty:51 01/xiii/2012              

munizwourfact1993.blogspot.com

Source: https://techhub.hpe.com/eginfolib/networking/docs/switches/common/15-18/5998-8158_bog/content/ch04s07.html

Share this post