To change the default name of the network configuration file from which to load configuration commands, use the boot network global configuration command. Use the no form of this command to restore the network configuration filename to the default.
boot network remote-url
no boot network remote-url
remote-url Configures the router to boot the configuration file specified by the FTP, rcp, or TFTP URL:
- ftp: [[[// [username[: password]@ ]location]/ directory]/ filename]
- rcp: [[[// [username@ ]location]/ directory]/ filename]
- tftp: [[[// location]/ directory]/ filename]
The default filename is network-config.
Global configuration
| Release | Modification | 10.0 | This command was introduced. |
|---|
When booting from a network server, routers ignore routing information, static IP routes, and bridging information. As a result, intermediate routers are responsible for handling FTP, rcp, or TFTP requests. Before booting from a network server, verify that a server is available by using the ping command.
Use the service config command to enable the loading of the specified configuration file at reboot time. Without this command, the router ignores the boot network command and uses the configuration information in NVRAM. If the configuration information in NVRAM is invalid or missing, the serviceconfig command is enabled automatically.
The network server will attempt to load two configuration files from remote hosts. The first is the network configuration file containing commands that apply to all network servers on a network. Use the boot network command to identify the network configuration file. The second is the host configuration file containing commands that apply to one network server in particular. Use the boot hostcommand to identify the host configuration file.
The rcp software requires that a client send the remote username on each rcp request to the network server. If the server has a directory structure (such as UNIX systems), the rcp implementation searches for the configuration files starting in the directory associated with the remote username.
When you load a configuration file from a server using rcp, the Cisco IOS software sends the first valid username in the following list:
An account for the username must be defined on the destination server. If the network administrator of the destination server did not establish an account for the username, this command will not execute successfully.
The FTP protocol requires a client to send a remote username and password on each FTP request to a server. The username and password must be associated with an account on the FTP server. If the server has a directory structure, the configuration file or image copied from the directory associated with the username on the server. Refer to the documentation for your FTP server for more details.
When you load a configuration file from a server using FTP, the Cisco IOS software sends the first valid username in the following list:
The router send the first valid password in the following list:
The following example changes the network configuration filename to bridge_9.1 and uses the default broadcast address:
boot network tftp:bridge_9.1 service config
The following example changes the network configuration filename to bridge_9.1, specifies that rcp is to be used as the transport mechanism, and gives 172.16.1.111 as the IP address of the server on which the network configuration file resides:
boot network rcp://172.16.1.111/bridge_9.1 service config
| Command | Description |
|---|---|
| boot host | Changes the default name of the host configuration filename from which to load configuration commands. |
| service config | Enables autoloading of configuration files from a network server, use the service config global configuration command. |
Printed for apswan@ctr.ap.nic.in on Wed Mar 5 22:32:57 PST 2003
All material in this document copyright 2000 Cisco Systems, Inc. All rights reserved. No material may be reproduced or distributed without written permission of Cisco Systems, Inc.