Kategorien

HP – Switch Bootimage umstellen

Link: http://h30507.www3.hp.com/t5/HP-Networking/HP-ProCurve-using-multiple-config-files/ba-p/42024#.VXfov3kcTuo

 

-Make a backup of the config before implementing a big change;
-Make a fallback configuration;
-Make a backup of the config after project has been accepted;
-Etc.
The procedure to create the multiple config files is:
A: prepare multiple config files:
Sh config files
Write mem
Copy config config1 config config2
Startup-default secondary config config2
Configuration files:
 id | act pri sec | name
 ---+-------------+------------------------------------------------
  1 |  *   *      | config1
  2 |          *  | config2
This allows each flash to use its own configuration file. This ensures a save backup version of the config file, even when a software upgrade changes commands in the config file of the new software release.
The disadvantage is that for each software upgrade, a manual sync of these config files with the copy command must be done to ensure that the latest config version is used for the new software upgrade.
B: Upgrade procedure for single management module switch (e.g. 5400zl)
Procedure assumes primary is active, secondary will be used for new version, check with sh flash / sh ver.
1.Update the config file of secondary to latest version:
write mem                                save current running to start 
copy config config1 config config2       save current start to secondary config
2.Update the secondary flash with the new version:
copy tftp flash x.x.x.x K_13_XX.swi secondary
3.Change the boot default:
boot set-default flash secondary
4.Schedule the reload of the systems:
reload          in/at x for schedule     “no reload” to cancel
3+4 can be combined with boot system flash secondary, but no schedule is
available then
5.Verify if upgrade success. If success, procedure ends with backup of the config
6.If upgrade no success, revert to previous version:

boot system flash primary
or
boot set-default flash primary and reload
This will revert to the previous version and use the original, unmodified configuration file
C: Upgrade procedure for dual management module switch (e.g. 8212zl)
Procedure assumes primary is active, secondary will be used for new version, check with sh flash / sh ver
1.Update the config file of secondary to latest verion:
write mem                             save current running to start
copy config config1 config config2    save current start to secondary config

2.
Update the secondary flash with the new version:
copy tftp flash x.x.x.x K_13_XX.swi secondary

3.
Change the boot default to the new flash:
boot set-default flash secondary

4.
Reload the standby management module:
boot standby

5
.Wait for the standby management module to be active:
sh redundancy              wait until the standby module is booted 
                           in the new release, with status “Standby” repeat
6.Configure the boot default to the old flash, to allow fast fall-back: When the active module releases control to the standby module, it is reloaded. This command will ensure that this reload is done again in the old version, so this module will be “Standby” in the original flash version and config
boot set-default flash primary
7.Perform the actual failover to the standby module:
redundancy switchover
8.If upgrade success(take time to validate new software):
a.Configure standby module to be standby in new release:
boot set-default secondary
b.Reload the standby module with the new version:
boot standby
c.Take a backup of the new configuration file.
9.If upgrade no success:
a.Revert to the standby module, which is still booted in the previous release and configuration file:
redundancy switchover
b.When issues is resolved or new firmware is available, repeat procedure from
start.