Auto deployment relies on DHCP options and the current DHCP auto-configuration function. Auto deployment is platform independent, avoiding the J-number validation of the downloaded configuration file when downloaded using DHCP option 66/67. The downloaded configuration file has an IGNORE
tag immediately after the J-number in its header.
An option to add an add-ignore-tag
to an existing copy command will insert an ignore
tag into the configuration header. This insertion happens while transferring the configurations, (startup configuration files
and running configuration files
) from the switch to a configuration file setup on a remote server. The process uses TFTP/SFTP or can be accomplished with a serially connected workstation using XMODEM.
The add-ignore-tag
option is used in conjunction with the copy
command to transfer the startup configuration
or running configuration
files from the switch to a remote server with IGNORE
tag inserted into it.
The IGNORE
tag is inserted into the first line of the configuration file directly after the J-number.
Configuration file
; J9782A IGNORE Configuration Editor; Created on release #YB.15.14.0000x ; Ver #04:63.ff.37.27:88 hostname "HP-2530-24" snmp-server community "public" unrestricted vlan 1 name "DEFAULT_VLAN" no untagged 2,20-25 untagged 1,3-19,26-28 ip address dhcp-bootp
|
|
NOTE: The J-number validation is ignored only when configuration file that contains the |
|
|
There is no change to the current switch configuration when executing the copy command with the add-ignore-tag
option. The IGNORE
tag is only added to the configuration
file being exported to the external server. The configuration
file stored on an external server is then downloaded to the switch using DHCP option 66 during bootup. If the IGNORE
tag is available in the downloaded configuration
file then the switch will avoid the J-number validation of the configuration
file. The downloaded configuration
file will then go through a line by line validation. Once the configuration
file passes this validation, it gets updated in the flash. Once the configuration
file has been updated, the switch will reboot automatically.
|
|
NOTE: The J-number in the downloaded |
|
|
Copy with add-ignore-tag
HPN Switch(config)# copy startup-config tftp <ip-addr> <filename> add-ignore-tag HPN Switch(config)# copy running-config tftp <ip-addr> <filename> add-ignore-tag HPN Switch(config)# copy startup-config sftp <ip-addr> <filename> add-ignore-tag HPN Switch(config)# copy running-config sftp <ip-addr> <filename> add-ignore-tag HPN Switch(config)# copy startup-config xmodem add-ignore-tag HPN Switch(config)# copy running-config xmodem add-ignore-tag
Configuration files can be transferred to the switch from a server using the following copy
commands:
Copy commands
copy tftp < startup-config | running-config > < ip-address > < remote-file >[ pc | unix ] copy xmodem startup-config < pc | unix > copy sftp < startup-config | running-config > < ip-address > < remote-file >
Configuration
files that are downloaded using the copy
commands as described in the example will be accepted by the switch if they pass J-number validations and line by line validations after download. The downloaded configuration file will be discarded by the switch if the validations fail. If the validations fail, the switch will work with it’s previous configuration.
The show logging
command is used to locate errors during a configuration validation process. The event log catalogs entries with the ID#00158 and updates for each invalid entry found in the configuration
file.
Show logging
-- Reverse event Log listing: Events Since Boot ---- W 01/07/14 00:29:31 00158 update: line 13. Module command missing for port or invalid port: 36 I 01/07/14 00:29:30 00131 tftp: Transfer completed I 01/07/14 00:29:29 00090 dhcp: Trying to download Config File (using TFTP) received in DHCP from 192.168.1.1
|
|
NOTE: Downloading manually edited configuration file is not encouraged. |
|
|