HP 5500 Ei 5500 Si Switch Series Configuration Guide
Have a look at the manual HP 5500 Ei 5500 Si Switch Series Configuration Guide online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 1114 HP manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
![Page 108
96
Step Command
1. Enter system view. system-view
2. Perform configuration rollback.
configuration replace file filename
The configuration rollback function might fail to reco nfigure some commands in the running configuration
for one of the following reasons:
• A command cannot be undone because the undo form designed for the command does not include
a keyword or argument configured in the command. For example, if the undo form designed for the
A [B ] C command is undo A C , the...](http://img.usermanuals.tech/thumb/36/58909/w64_hp-5500-ei-5500-si-switch-series-configuration-guide-107.png "Page 108
96
Step Command
1. Enter system view. system-view
2. Perform configuration rollback.
configuration replace file filename
The configuration rollback function might fail to reco nfigure some commands in the running configuration
for one of the following reasons:
• A command cannot be undone because the undo form designed for the command does not include
a keyword or argument configured in the command. For example, if the undo form designed for the
A [B ] C command is undo A C , the...")
![Page 109
97
Step Command Remarks
2. Back up the next-startup
configuration file to a TFTP
server in user view. backup startup-configuration to
dest-addr [dest-filename ] N/A
Deleting the next-startup configuration file
CAUTION:
This task permanently deletes the next-startup conf
iguration file from all member devices. Before
performing this task, back up the file as needed.
You can delete the main, the backup, or both. If the device has only one next-startup configuration file,
the...](http://img.usermanuals.tech/thumb/36/58909/w64_hp-5500-ei-5500-si-switch-series-configuration-guide-108.png "Page 109
97
Step Command Remarks
2. Back up the next-startup
configuration file to a TFTP
server in user view. backup startup-configuration to
dest-addr [dest-filename ] N/A
Deleting the next-startup configuration file
CAUTION:
This task permanently deletes the next-startup conf
iguration file from all member devices. Before
performing this task, back up the file as needed.
You can delete the main, the backup, or both. If the device has only one next-startup configuration file,
the...")
![Page 110
98
Displaying and maintaining a configuration file
Task Command Remarks
Display information about
configuration rollback. display archive configuration [ |
{ begin | exclude | include }
regular-expression ] Available in any view.
Display the running configuration. display current-configuration
[ [ configuration [ configuration
] |
interface [ interface-type ]
[ interface-number ] | exclude
modules ] [ by-linenum ] [ | { begin
| exclude | include }
regular-expression ] ]...](http://img.usermanuals.tech/thumb/36/58909/w64_hp-5500-ei-5500-si-switch-series-configuration-guide-109.png "Page 110
98
Displaying and maintaining a configuration file
Task Command Remarks
Display information about
configuration rollback. display archive configuration [ |
{ begin | exclude | include }
regular-expression ] Available in any view.
Display the running configuration. display current-configuration
[ [ configuration [ configuration
] |
interface [ interface-type ]
[ interface-number ] | exclude
modules ] [ by-linenum ] [ | { begin
| exclude | include }
regular-expression ] ]...")
99 Upgrading software Upgrading software includes upgrading the Boot ROM and system software. Each time the switch is powered on, it runs the Boot ROM image to initialize hardware and display hardware information, and t h e n r u n s t h e sys t e m s o f t wa re i m a g e ( a l s o c a l l e d t h e b o o t fi l e ) s o yo u c a n a c c e s s t h e s o f t wa re f e a t u re s , as shown in Figure 42. Figure 42 Relationship betw een the Boot ROM and the system software images Software upgrade methods You can upgrade both Boot ROM and system software at the Boot menu or at the CLI. The following sections describe the CLI approach. For instructions about how to upgrade them at the Boot menu, see the release notes of your switch. The CLI approach provides the following upgrading methods: Upgrade method Upgrade object Description Upgrading software through a system reboot Boot ROM and system software A switch reboot is required during the upgrade, causing service interruption. Upgrading software by installing hotfixes System software Hotfixes repair software defects without rebooting the switch and interrupting the running services of the switch. The patch files must match the switch model and software version. Otherwise, the hotfixing operation fails. Start Boot ROM runs Press Ctrl+B Run system software image Enter Boot menu to upgrade Boot ROM or system software Yes No Select the Reboot option to reboot the device Enter CLI Finish
100 Upgrade method Upgrade object Description In-Service Software Upgrade (ISSU) System software ISSU enables software upgrade and ensures continues packet forwarding. For more information, see Performing ISSU. The ISSU feature is available only on the HP 5500-EI switch. Upgrading software through a system reboot Upgrading software by rebooting the switch interrupts the ongoing services. If any other method is possible, do not use this method. Upgrading Boot ROM through a system reboot 1. Transfer the Boot ROM image to the root directory of the switchs storage media, for example, by using FTP or TFTP. IMPORTANT: • To successfully upgrade the Boot ROM of a member switch, make sure the Boot ROM image is stored in the root directory of the member switchs storage media. 2. Upgrade the Boot ROM from the CLI, as follows: Step Command Remarks 1. Enter system view. system-view N/A 2. Enable Boot ROM image validity check. bootrom-update security-check enable Optional By default, the validity check function is enabled. This feature examines the upgrade Boot ROM image for version and hardware incompatibility to ensure a successful upgrade. 3. Return to user view. quit N/A 4. Upgrade Boot ROM on member switches. bootrom update file file-url slot slot-number-list Available in user view. 3. Reboot the switch. Upgrading system software through system reboot (method 1) 1. Transfer the system software image to the root di rectory of the master switchs storage media, for example, by using FTP or TFTP. IMPORTANT: The image file must be saved in the r oot directory for a successful upgrade. 2. Copy the new system software image to the root directory of each subordinate switchs storage media.
101
IMPORTANT:
You can assign different names to the image files for different member switches, but must make sure the
image versions are the same.
3.
Use the boot-loader file file -url slot { all | slot-number } { main | backup } command in user view
to specify the system software image to be used at the next startup for each member switch.
4. Reboot all member switches.
Upgrading system software through system reboot (method 2)
This method simplifies the software upgrade procedure described in Upgrading system software
thr
ough system reboot (method 1) for a multiple-MPU context by using one command to complete
copying a system software image to an MPU and specifying the file as the system software image to be
used at the next startup.
To use this method to upgrade system software:
1. Transfer the system software image to the root di rectory of the master switchs storage media, for
example, by using FTP or TFTP.
2. Use the boot-loader update file file-url slot { slot-number | all } { main | backup } command in user
view to specify the system software image as the file to be used at the next startup for each member
switch.
3. Reboot all member switches.
Upgrading software by installing hotfixes
Hotfixes can repair software defects without rebooting the switch.
Basic concepts
• Patch and patch file
A patch fixes certain software defects. Patches might be released as patch files. A patch file might
contain one or more patches. Af ter being loaded from the storage media to the memory patch
area, each patch is assigned a unique number , which starts from 1, for identification,
management and operation. For example, if a patch file has three patches, they are numbered as
1, 2, and 3.
• Incremental patch
Incremental patches are dependent on previous patches and cannot separately run. For example,
if a patch file has three patches, patch 3 can be running only after patch 1 and 2 take effect. You
cannot run patch 3 separately.
Patches that have been released are all incremental patches.
• Common patch and temporary patch
There are common and temporary patches:
{ Common patches are formally released through the version release flow.
{ Temporary patches are not formally released through the version release flow, but temporarily
provided to solve the emergent problems.
102 Common patches always include the functions of the previous temporary patches. The patch type only affects the patch loading proc ess. The system deletes all of the temporary patches before it loads the common patch. • Patch package file A patch package file typically contains multiple pat ch files. A patch package file enables you to fix bugs for multiple components by executing a single command. Using patch files is more troublesome. Patch file names are strictly defined and cannot be changed. To fix software bugs for a component, you must download the specific patch file, and rename the file to that pre-defined for the hardware. If the file name is unqualified, the upgrade fails. If there are multiple components, repeat this operation multiple times. Patch state Each patch has a state, which can be switched only by commands. The relationship between patch state changes and command actions is shown in Figure 43. T he patch can be in IDLE, DEACTIVE, ACTIVE, or RUNNING state. Load, run temporarily, confirm running , stop running, delete, install, and uninstall are operations and they correspond to the following commands: patch load, patch active, patch run, patch deactive, patch delete, patch install, and undo patch install . For example, if you execute the patch active command for the patches in DEACTIVE state, the patches switch to the ACTIVE state. IMPORTANT: Patch state information is saved in Flash memory in the file patchstate. To make sure that the switch can correctly find the patches, do not edit, delete, move the file, or change the file name. Figure 43 Relationship between patch state changes and command actions
103 IDLE state Patches in IDLE state are not loaded. You cannot install or run the patches, as shown in Figure 44. In this example, the memory patch area can load up to eight patches. Figure 44 Patches are not loaded to the memory patch area The memory patch area supports up to 200 patches. DEACTIVE state Patches in DEACTIVE state have been loaded to the memory patch area but have not yet run in the system. Suppose that there are seven patches in the patch file to be loaded. After the seven patches successfully pass the version check and CRC check, they are loaded to the memory patch area and are in DEACTIVE state. At this time, the patch stat es in the system are as shown in Figure 45. Figure 45 A patch file is loaded to the memory patc h area ACTIVE state Patches in ACTIVE state have run temporarily in th e system and become DEACTIVE after system reboot. For the seven patches in Figure 45, if y ou activate the first five patches, their states change from DEACTIVE to ACTIVE. The patch states in the system are as shown in Figure 46. T he patches that are in ACTIVE state are in DEACTIVE state after system reboot.
104 Figure 46 Patches are activated RUNNING state After you confirm the ACTIVE patches are running, the state of the patches changes to RUNNING and the patches are in RUNNING state after system reboot . If you confirm the first three patches are running, for the five patches in Figure 46, the ir states change from ACTIVE to RUNNING. The patch states of the system are shown in Figure 47 . T he patches that are in RUNNING state are still in RUNNING state after system reboot. Figure 47 Patches are running Hotfix configuration task list Task Remarks Installing patches: • Installing a patch in one step • Installing a patch step-by-step Use either approach. The step-by-step patch installation allows you to control the patch status. Uninstalling a patch step-by-step Optional.
105
Installation prerequisites
Patches are released per switch model. To ensure a successful hotfix operation and normal switch
operation after the hotfix operation:
• Make sure each patch file you are installing matches the switch model and software version.
• The loading and installation are performed on all member switches of an IRF fabric. Before these
operations, save the same patch files to the storag e media’s root directory of each member switch.
• Name a patch file properly. Otherwise, the syst em cannot locate the patch file and the hotfixing
operation fails. The name is in the format of patch_ PATC H - F L AG s u f f ix.bin. The PATCH-FLAG is
pre-defined. The value of the version field (using the display patch information command)
represents the PATCH-FLAG suffix. The system se arches the root directory of the storage media
(Flash by default) for patch files based on the PATCH-FLAG. If there is a match, the system loads
patches to or install them on the memory patch area. The default name of a patch file is
patch_xxx.bin.
Installing a patch in one step
To install patches in one step, use the patch install command and specify either the directory where the
patch file locates or the filename of the patch package.
After you execute the command, the system displays the message Do you want to continue running
patches after reboot? [Y/N]:
• Entering y or Y: All the specified patches are installed, and turn to RUNNING state from IDLE. This
equals executing commands patch location, patch load , patch active, and patch run. The patches
remain RUNNING after system reboot.
• Entering n or N: All the specified patches are installed an d turn to ACTIVE state from IDLE. This
equals executing commands patch location, patch load and patch active. The patches turn to
DEACTIVE state after system reboot.
To install the patches in one step:
Step Command Remarks
1. Enter system view. system-view N/A
2. Install the patches in one step. patch install
{ patch-location | file
patch-package }
• patch-location : Specifies the
directory where the patch file
locates. Provide this argument
when you install a patch file
which is not packaged in a
patch package file.
• file patch-location : Specifies
the name of the patch package
file. Provide this option when
you install a patch package file.
If you execute the patch install patch-location command, the directory specified for the patch-location
argument will replace the directory specified with the patch location command after the upgrade is
complete.
If you execute the patch install file patch-package command, the directory specified with the patch
location command does not change.
106 To uninstall all patches in one operation, use the undo patch install command, which is the same as performing Uninstalling a patch step-by-step . Installing a patch step-by-step Step-by-step patch installation enables you to cont rol the patch status during the patch installation process. Step-by-step patch installation task list Task Remarks Configuring the patch file location Optional. To install a patch package, skip this step. Loading a patch file Required. Activating patches Required. Confirming running patches Optional. Configuring the patch file location HP recommends that you save the patch file to the root directory of the Flash. If you save the patch files to a storage medium other than the Flash, you must specify the directory that saves patch files so the system can locate them. Make sure the specified directory exist on each member switch in the IRF fabric. If the switch has only one storage medium, you do not need to perform this task. To configure the patch file location: Step Command Remarks 1. Enter system view. system-view N/A 2. Configure the patch file location. patch location patch-location Optional. flash: by default. NOTE: After you execute the patch install patch-location command, the directory specified for the patch-location argument will replace the directory specified with the patch location command after the upgrade is complete. Loading a patch file Loading the correct patch files is th e basis of other hotfix operations. If you install a patch from a patch file, the system loads a patch file from the Flash by default. If you install a patch from a patch package, the system finds the correc t patch file in the patch package file and loads the patch file. IMPORTANT: Set the file transfer mode to binary mode before using FTP or TFTP to upload or download patch files to or from the Flash of the switch. Otherwise, patch file cannot be parsed properly.
107 To load a patch file: Step Command 1. Enter system view. system-view 2. Load the patch file on from the storage media (the Flash) to the specified memory patch area. patch load slot slot-number [ file patch-package ] Activating patches After you activate a patch, the patch takes effect and is in the test-run stage. After the switch is reset or rebooted, the patch becomes invalid. I f yo u fi n d t h a t a n AC T I V E p a t c h c a u s e s a n e r ro r, re b o ot the switch to deactivate the patch, so as to avoid a series of running faults resulting from patch error. To activate patches: Step Command 1. Enter system view. system-view 2. Activate patches. patch active [ patch-number ] slot slot-number Confirming running patches This operation is applicable only to patches in ACTIVE state. After you confirm that the installed patch is runni ng, the patch state changes to RUNNING, and the patch is in the normal running stage. After the switch is reset or rebooted, the patch is still valid. To confirm the running of patches: Step Command 1. Enter system view. system-view 2. Confirm the running of patches. patch run [ patch-number ] [ slot slot-number ] Uninstalling a patch step-by-step This section describes the procedure of uninstalling patches. Step-by-step patch uninstallation task list Task Remarks Stopping running patches Required Deleting patches Required Stopping running patches When you stop running a patch, the patch state becomes DEACTIVE, and the system runs the way it did before it was installed with the patch. To stop running patches:
108
Step Command
1. Enter system view. system-view
2. Stop running patches.
patch deactive [ patch-number ] slot slot-number
Deleting patches
Deleting patches only removes the patches from the memory patch area, and does not delete them from
the storage media. The patches turn to IDLE state after this operation. Af ter a patch is deleted, the system
runs the way it did before it was installed with the patch.
In an IRF fabric, HP recommends that you uninstall all patches by using the undo patch install command
in one operation.
To delete patches:
Step Command
1. Enter system view. system-view
2. Delete patches from the memory patch area.
patch delete [ patch-number ] slot slot-number
Displaying and maintaining software upgrade
Task Command Remarks
Display information about system
software display boot-loader
[ slot slot-number ]
[ | { begin | exclude | include }
regular-expression ] Available in any view
Display information about the
patch package. display patch
[ | { begin | exclude |
include } regular-expression ] Available in any view
Display the patch information. display patch information
[ | { begin |
exclude | include } regular-expression ] Available in any view
Software upgrade examples
Immediate upgrade configuration example
Network requirement
The IRF fabric in Figure 48 comprises two member switches, the master use the member ID 1 and the
subordinate switch uses the member ID 2. The current software version of the IRF fabric is soft-version1.
The latest system software image soft-version2.bin and the latest configuration file new-config.cfg are
both saved on the TFTP server. The TFTP server and IRF fabric can reach each other.
Upgrade the software version of the IRF fabric to soft-version2 and the configuration file to new-config.