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 97
85
Format Description Length Example
drive:/[path]/file-
name Specifies a file in a specific storage
medium on the device.
The
drive argument represents the
storage medium name.
The storage medium on the master
is typically flash.
The storage medium on a
subordinate device is typically
slotX#flash, where X represents the
member ID of the subordinate
device, for example, slot2#flash.
To view the correspondence
between a device and its member
ID, use the display irf command. 1 to...](http://img.usermanuals.tech/thumb/36/58909/w64_hp-5500-ei-5500-si-switch-series-configuration-guide-96.png "Page 97
85
Format Description Length Example
drive:/[path]/file-
name Specifies a file in a specific storage
medium on the device.
The
drive argument represents the
storage medium name.
The storage medium on the master
is typically flash.
The storage medium on a
subordinate device is typically
slotX#flash, where X represents the
member ID of the subordinate
device, for example, slot2#flash.
To view the correspondence
between a device and its member
ID, use the display irf command. 1 to...")
![Page 104
92
Enabling configuration file auto-update
The configuration auto-update function enables all subordinate switches to automatically save the
running configuration as the master does when you execute the save [ safely ] [ backup | main ]
[ force ] command or the save filename all command. If this function is disabled, only the master
saves the configuration.
To ensure configuration consistency, HP recommends enabling the function.
To enable configuration auto-update:
Step Command Remarks...](http://img.usermanuals.tech/thumb/36/58909/w64_hp-5500-ei-5500-si-switch-series-configuration-guide-103.png "Page 104
92
Enabling configuration file auto-update
The configuration auto-update function enables all subordinate switches to automatically save the
running configuration as the master does when you execute the save [ safely ] [ backup | main ]
[ force ] command or the save filename all command. If this function is disabled, only the master
saves the configuration.
To ensure configuration consistency, HP recommends enabling the function.
To enable configuration auto-update:
Step Command Remarks...")
![Page 105
93
Task Command Remarks
Save the running configuration to a
configuration file and specify the
file as the startup configuration file
for the next startup. save [ safely
] [ backup | main ]
[ force ] By default, the running
configuration is saved to the
current startup configuration file.
You can choose to save the
configuration to a different file as
instructed by the system.
If you execute the
save [ safely ]
command without specifying any
other keyword, the command
saves the...](http://img.usermanuals.tech/thumb/36/58909/w64_hp-5500-ei-5500-si-switch-series-configuration-guide-104.png "Page 105
93
Task Command Remarks
Save the running configuration to a
configuration file and specify the
file as the startup configuration file
for the next startup. save [ safely
] [ backup | main ]
[ force ] By default, the running
configuration is saved to the
current startup configuration file.
You can choose to save the
configuration to a different file as
instructed by the system.
If you execute the
save [ safely ]
command without specifying any
other keyword, the command
saves the...")
89 Directory of flash:/ 0 -rw- 13308645 Mar 22 2011 11:34:07 main.bin 1 -rw- 7380 Mar 25 2011 10:47:36 patch-package.bin 2 -rw- 228 Mar 25 2011 10:50:39 patchstate 3 -rw- 3921 Apr 01 2011 17:56:30 startup.cfg 4 -rw- 151 Apr 01 2011 17:56:24 system.xml 15240 KB total (2521 KB free) # Create new folder mytest in the test directory. cd test mkdir mytest %Created dir flash:/test/mytest. # Display the current working directory. pwd flash:/test # Display the files and the subdirectories in the test directory. dir Directory of flash:/test/ 0 drw- - Apr 01 2011 18:28:14 mytest 15240 KB total (2519 KB free) # Return to the upper directory. cd .. # Display the current working directory. pwd flash:
90 Managing configuration files You can manage configuration files at the CLI or by using the Boot menu of the device. This chapter describes the CLI approach. Overview A configuration file saves a configuration as a set of text commands. You can save the running configuration to a configuration file so the configuration takes effect after you reboot the device. You can also back up the configuration file to a host and download the file to the device as needed. Configuration types The device maintains the following types of configurations: factory defaults, startup configuration, and running configuration. Factory defaults The device is shipped with some basic settings called factory defaults. These default settings make sure the device can start up and run normally when it has no configuration file or the configuration file is corrupted. To view the factory defaults, use the display default-configuration command. NOTE: Factory defaults vary with devi ce models and might differ from th e default settings of commands. Startup configuration The device uses startup configuration to configure software features during startup. After the device starts up, you can specify a different configuration file for the next startup. This configuration file is called the next-startup configuration file. If no next-startup configuration file exists, the device boots with the factory defaults. To view the current startup configuration, use either of the following ways: • Execute the display startup command. To view detailed file contents, use the more command. • After the device reboots, execute the display current-configuration command before making any configuration. Running configuration The running configuration includes the startup settings that have not been changed and the new settings you have made. The running configuration is stored in a volatile storage medium. To make the settings you made to survive a reboot, save them to the startup configuration file. To view the running configuration, use the display current-configuration command.
91 Configuration file format and content A configuration file is saved as a text file according to the following rules: • Commands are saved in their complete form. • The commands are listed in sections by view, typically in this order: system view, interface view, protocol views, and user interface view. • Sections are separated with one or more blank lines or comment lines that start with a pound sign (#). • A configuration file ends with a return. Coexistence of multiple configuration files The device can save multiple configuration files on its storage media. You can save the configurations used for different networking environments to different configuration files. When the device moves between networking environments, you can quickly adapt the device to the environments by loading the intended configuration file onto the device. You can specify one main startup configuration file and one backup startup configuration file for the device. At startup, the device first tries to start up with the main startup configuration file. If the main startup configuration file is corrupted or lost, the device tries to start up with the backup startup configuration file. For reliability, do not specify a configuration file as both the main and backup startup configuration files. If a configuration file is not assign ed the main or backup attribute, its file attribute is NULL. You can specify a main or backup startup configuration file directly (see Specifying a configuration file) or w hen saving the running configuration (see Saving the running configuration) . Startup with a configuration file The device selects the configuration file to load at startup, as follows: 1. If the specified main startup configuration file exists , the device starts up with this configuration file. 2. If the specified main startup configuration file does not exist but the backup startup configuration file exists, the device st arts up with the backup startup configuration file. 3. If neither the main nor the backup startup configurat ion file exists, the device starts up with the factory defaults. Saving the running configuration To make configuration changes take effect at the next startup of the device, save the running configuration to the startup configuration file to be used at the next startup before the device reboots. Complete these tasks to save the current configuration: Task Remarks Enabling configuration file auto-update Optional Perform this task to ensure configuration consistency across member devices. Saving running configuration in fast mode or safe mode Required
92 Enabling configuration file auto-update The configuration auto-update function enables all subordinate switches to automatically save the running configuration as the master does when you execute the save [ safely ] [ backup | main ] [ force ] command or the save filename all command. If this function is disabled, only the master saves the configuration. To ensure configuration consistency, HP recommends enabling the function. To enable configuration auto-update: Step Command Remarks 1. Enter system view. system-view N/A 2. Enable configuration file auto-update. slave auto-update config By default, this function is enabled. Saving running configuration in fast mode or safe mode You can save the running configuration to a configuration file in one of the following modes: • Fast mode —Use the save command without the safely keyword. The file is saved more quickly but is likely to be lost if the device reboots or powe r failure occurs during the process. If the startup configuration file for the next startup is lost, the device will use the factory defaults the next time it reboots, and you must re-specify a new startup configuration file for the device (see Specifying a conf iguration file for the next startup). • Safe mode —Use the save command with the safely keyword. The file is saved slowly, but the system retains the configuration file even if the device reboots or a power failure occurs during the process. The fast saving mode is suitable for environments where a reliable power source is used. The safe mode is preferred in environments where the power source is not reliable or remote maintenance is involved. The configuration file name extension must be .cfg. To save the running configuration, perform either of the following tasks in any view: Task Command Remarks Save the running configuration to a configuration file without specifying the file as the startup configuration file for the next startup. save file-url [ all | slot slot-number ] The save command executed with only the file-url argument saves the running configuration only to the specified path, regardless of whether the configuration auto-update function has been enabled.
93 Task Command Remarks Save the running configuration to a configuration file and specify the file as the startup configuration file for the next startup. save [ safely ] [ backup | main ] [ force ] By default, the running configuration is saved to the current startup configuration file. You can choose to save the configuration to a different file as instructed by the system. If you execute the save [ safely ] command without specifying any other keyword, the command saves the configuration to the main startup configuration file. If configuration auto-update is enabled, the save file -url all command and the save [ safely ] [ backup | main ] [ force ] command save the configuration to the master device and all member devices. If the function is disabled, the commands save the configuration only to the master device. Configuring configuration rollback To replace the running configuration with the configuration in a configuration file without rebooting the device, use the configuration rollback function. This function helps you revert to a previous configuration state or adapt the running configuratio n to different network environments. The configuration rollback function compares the running configuration against the specified replacement configuration file and handles configuration differences as follows: • If a command in the running configuration is not in the replacement file, executes its undo form. • If a command in the replacement file is not in the running configuration, adds it to the running configuration. • If a command has different settings in the running configuration and the configuration file, replaces its running configuration with the setting in the configuration file. To facilitate configuration rollback, the configuration archive function is developed. This function enables the system to automatically save the running configurat ion at regular intervals as checkpoint references. Configuration task list Task Remarks Configuring configuration archive parameters Required. • Enabling automatic configuration archiving • Manually archiving running configuration Required. Use either approach. Performing configuration rollback Required. Configuring configuration archive parameters Before archiving the running configuration, either manually or automatically, you must configure a file directory and file name prefix for configuration archives.
94 Configuration archives are saved with the file name format prefix_serial number .cfg, for example, 20080620archive_1.cfg and 20080620archive_2.cfg. The serial number is automatically assigned from 1 to 1000, increasing by 1. After the serial number reaches 1000, it restarts from 1. After you change the file directory or file name prefix , or reboot the device, the old configuration archives are regarded as common configuration files, the configuration archive counter resets, and the display archive configuration command does not display them. The serial number for new configuration archives starts from 1. After the maximum number of configuration archives is reached, the system deletes the oldest archive for the new archive. Configuration guidelines In an IRF fabric, the configuration archive function saves running configuration only on the master device. To make sure the system can archive running configuration after a master/subordinate switchover, create the directory on all IRF members. Configuration procedure To configure configuration archive parameters: Step Command Remarks 1. Create the configuration archive directory. See Managing the file system. In an IRF fabric, create the directory at least on the master. HP recommends creating the directory on all member devices. 2. Enter system view. system-view N/A 3. Configure the directory and file name prefix for archiving the running configuration. archive configuration location directory filename-prefix filename-prefix Do not include member ID information in the directory name. By default, no path or file name prefix is set for configuration archives, and the system does not regularly save configuration. IMPORTANT: The undo form of this command disables both manual and automatic configuration archiving, restores the default settings for the archive configuration interval and archive configuration max commands, and deletes all saved configuration archives. 4. Set the maximum number of configuration archives. archive configuration max file-number Optional. The default number is 10. Change the setting depending on the available storage space.
95 Enabling automatic configuration archiving To avoid decreasing system performance, follow these guidelines when you configure automatic configuration archiving: • If the device configuration does not change freq uently, manually archive the running configuration as needed. • If a low-speed storage media (such as a Flash) is used, archive the running configuration manually, or configure automatic archiving with an inte rval longer than 1440 minutes (24 hours). Make sure you have set an archive path and file name prefix before performing this task. To enable automatic configuration archiving: Step Command Remarks 1. Enter system view. system-view N/A 2. Enable automatic configuration archiving and set the archiving interval. archive configuration interval minutes By default, this function is disabled. To view configuration archive names and their archiving time, use the display archive configuration command. Manually archiving running configuration To save system resources, disable automatic configuration archiving and manually archive configuration if the configuration will not be changed very often. You can also manually archive configuration before performing complicated configuration tasks so you can use the archive for configuration recovery after the configuration attempt fails. Make sure you have set an archive path and file name prefix before performing this task. Perform the following task in user view: Task Command Manually archive the running configuration. archive configuration Performing configuration rollback To avoid rollback failure, follow these guidelines: • Do not reboot member devices while the system is executing the configuration replace file command. Make sure the replacement configuratio n file is created by using the configuration archive function or the save command on the current device. • If the configuration file is not created on the current device, make sure the configuration file content format is fully compatible with the current device. • The replacement configuration file is not encrypted. To perform configuration rollback:
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 configuration rollback function cannot undo the A B C command, because the system does not recognize the undo A B C command. • A command (for example, a hardware-dependent command) cannot be deleted, overwritten, or undone due to system restrictions. • The commands in different views are dependent on each other. • Commands or command settings not supported on the current device cannot be added to the running configuration. Specifying a configuration file for the next startup You can specify a configuration file as the main startup configuration file to be used at the next startup when you use the save command to save the running configuration to it. Alternatively, perform the following task in user view to specify a startup configuration file for the next startup: Task Command Remarks Specify a startup configuration file of all member switches. startup saved-configuration cfgfile [ backup | main ] The configuration file must use the .cfg extension and be saved in the root directory of storage media. Backing up the next-startup configuration file to a TFTP server Before performing this task, make sure the server is reachable and enabled with TFTP service, and you have read and write permissions. This task backs up only the main next-startup configuration file. To back up the startup configuration file to be used at the next startup: Step Command Remarks 1. Ve ri f y t h a t a n ex t - s ta r t u p configuration file has been specified in user view. display startup Optional. If no next-startup configuration file has been specified, the back operation will fail.
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 system sets the attribute of the configuration file to NULL instead of deleting the file. You may need to delete the next-startup configuration file for one of the following reasons: • After you upgrade system software, the file does not match the new system software. • The file has been corrupted or is not fully compatible with the device. After the file is deleted, the device uses factory defaults at the next startup. Perform the following task in user view: Task Command Delete the next-startup configuration file. reset saved-configuration [ backup | main ] Restoring the next-startup configuration file from a TFTP server To download a configuration file from a TFTP server to the root directory of each member storage medium, and specify the file as the configuration file for the next startup, perform the task in this section. This task restores only the main next-startup configuration file. Before restoring the next-startup configuration file, make sure the server is reachable, the server is enabled with TFTP service, and you have read and write permissions. To restore the next-startup configuration file from a TFTP server: Step Command Remarks 1. Restore the main next-startup configuration file from a TFTP server in user view. restore startup-configuration from src-addr src-filename N/A 2. Verify that the specified configuration file has been set as the main next-startup configuration file. display startup Optional
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 ] ] Available in any view.
Display the factory defaults.
display default-configuration
[ |
{ begin | exclude | include }
regular-expression ] Available in any view.
Display the running configuration
file saved on the storage media of
the device. display saved
-configuration
[ by-linenum ] [ | { begin | exclude
| include } regular-expression ] Available in any view.
Display the configuration files used
at this startup and the next startup. display startup
[ | { begin |
exclude | include }
regular-expression ] Available in any view.
Display the valid configuration
under the current view. display this
[ by-linenum ] [ |
{ begin | exclude | include }
regular-expression ] Available in any view.