[Top] [Prev] [Next] [Bottom]

Configuring Booting and Dumping

This document describes the Boot CONFIG process. It includes the following sections:

What is Boot CONFIG?

How BOOTP Forwarding Works

Using the Trivial File Transfer Protocol (TFTP)

Validating a Configuration Load

Configuring Dumping

Boot CONFIG Commands

What is Boot CONFIG?

The router's memory contains the information that tells the router how to boot and dump. The Boot CONFIG commands allow you to modify this information.

Using Boot CONFIG commands, you can do the following:

Changes made to system and protocol parameters through Boot CONFIG take effect when you restart the router or when you reload the router software.

Configuring Booting

Boot files are the same as load files. A boot file contains the software to run the router and can reside on a diskette, host server, or IBD. The host server can be any PC, router, or workstation that is running the IP protocol and TFTP. The boot configuration database can contain an entry for each boot file, configured using the add command. Each entry contains the address of the host server, the next hop router, the timeout, path, and filenames for the boot files.

You can configure more than one boot file in the boot configuration database by specifying the path and name of each boot file (using the add command). This gives you multiple servers. If you have more than one host server, you can use a different host server to boot the router when another host server cannot be reached over the network or when a server times out.

To configure booting,

1. Enter config. 

* config

Config>
2. At the Config> prompt, enter boot. 

Config>boot
TFTP Boot/dump configuration

Boot config>
3. Add an address record, with the add address command, specifying from which interface you want the router to boot and the new address. 

Boot config>add address
Which interface is this address for [0]?1 
New address [0.0.0.0]?128.185.123.51
4. Add a boot record, specifying the host address, next hop router, if necessary, and the path and filename on the host. 

Boot config>add boot-entry
remote host or IBD load name [0.0.0.0]test.ldc
To exit Boot CONFIG and return to the * prompt,

1. Enter exit at the Boot config> prompt. 

Boot config>exit
Config>
2. Press Ctrl P. 

*

How BOOTP Forwarding Works

 A router uses BOOTP (Bootstrap Protocol) to learn its IP address, the location of its boot file, and the boot server name. The router can act as a BOOTP relay agent or as a BOOTP client for another device. The following sections describe these two processes.

Note: If your server is running UNIX and you want to see how the BOOTP protocol handshaking works, your system administrator can run the bootpd daemon in a verbose manner by typing bootpd -d. The details of all the handshaking, such as the broadcasts and replies between a BOOTP client and BOOTP server appear on the screen.

The Router as a BOOTP Client

 The router acts as a BOOTP client in two circumstances:

1. The router's boot PROM configuration record indicates that the router can act as a BOOTP client.

2. During booting, the router does not have a valid pathname and filename to the location of the boot file and server.

When either of these two circumstances exists, the router chooses the first of its LAN interfaces to complete its self-test (usually Ethernet) and broadcasts a UDP packet over it to the BOOTP server containing the pathname of the boot file and server.

The following describes the BOOTP client forwarding process:

1. The BOOTP client copies its MAC address (Ethernet) into a BOOTP packet (UDP packet) and broadcasts it onto the local LAN. BOOTP runs on top of UDP.

2. The BOOTP server receives the request and looks up the client's MAC address in its database. If it finds the client's MAC address, it formats a BOOTP reply containing the client's IP address, the location of its boot file, and the boot server name. The server sends this information back over the LAN to the BOOTP client.

Note: If multiple hops are required before reaching the BOOTP server, a BOOTP relay agent receives the packet. See The Router as a BOOTP Relay Agent.

3. The router receives the BOOTP reply packet and uses the information in it to initiate a TFTP request to the BOOTP server.

Configuring a BOOTP Server

 The BOOTP server is either a UNIX host with a bootpd daemon or a DOS host running software available from FTP Software, Inc. The BOOTP server contains a file (maintained by the network administrator) that lists

When the BOOTP server receives a BOOTP request, it matches the MAC address of the client with the MAC address in its BOOTP file. If these addresses match, the server constructs a BOOTP reply and adds the client's IP address, the location of its boot file, and the boot server name. If they do not match, the server drops the packet.

To add a BOOTP server to the router's configuration, enter add bootp-server followed by the IP address of the server at the IP config> prompt:

Config>protocol ip
IP config>add bootp-server 128.185.123.56
You can configure multiple servers. Also, if you only know the network number of the server, or if multiple servers reside on the same network segment, you can configure a broadcast address for the server.

To configure a broadcast address for the server, enter enable directed-broadcast at the IP config> prompt. 

IP config>enable directed-broadcast

Enabling/Disabling BOOTP Forwarding

 To enable BOOTP forwarding on the router, enter enable bootp at the IP config> prompt. 

IP config>enable bootp
Maximum number of forwarding hops [4]? 
Minimum seconds before forwarding [0]?
Maximum number of forwarding hops

 Maximum number of BOOTP relay agents that can forward the packet, not the maximum number of IP hops to the BOOTP server. A typical value for this parameter is 4.

Minimum number of seconds before forwarding

 Time in which new requests from a client are dropped. This parameter is not commonly used. A typical value for this parameter is 0.

After accepting a BOOTP request, the router forwards the BOOTP request to each BOOTP server. If there are multiple servers configured for BOOTP, the transmitting server replicates the packet.

To disable BOOTP forwarding, enter disable bootp at the IP config> prompt. 

IP config>disable bootp

The Router as a BOOTP Relay Agent

 The router acts as a BOOTP relay agent when a BOOTP request requires multiple hops before reaching the BOOTP server. The BOOTP relay agent routes the packet via IP to all BOOTP servers that have been configured.

The following describes the BOOTP relay agent forwarding process:

1. The router, acting as the local BOOTP relay agent, receives the BOOTP request packet from the BOOTP client. The BOOTP relay agent updates the request with needed information and forwards it to all configured servers.

2. The BOOTP server receives the request and looks up the client's MAC address in its database. If the address is found, it formats a BOOTP reply containing the client's IP address, subnet mask, and BOOTP server name. The reply is then sent to the BOOTP relay agent.

3. The BOOTP relay agent receives the reply and makes an entry in its ARP table for the client and then forwards the reply to the BOOTP client.

4. The BOOTP client then continues to boot using the information that is contained in the BOOTP reply packet to initiate a TFTP request to the BOOTP server.

Using the Trivial File Transfer Protocol (TFTP)

 TFTP is a file transfer protocol that runs over the Internet UDP protocol. This implementation provides multiple, simultaneous TFTP file transfers between a router's non-volatile configuration memory and remote hosts.

TFTP allows you to

TFTP transfers involve a client node and a server node. The client node sends a TFTP request onto the network. The router acts as a client node when you enter copy at the Boot config> prompt.

Note: The tftp command and the copy command have the same functionality, but the syntax is different.

The client can transfer a copy of the configuration file stored in configuration memory to a TFTP server. Flash is a non-volatile memory storage location for boot PROM updates.

The server is any device, that is a PC, router, or workstation that receives and services TFTP requests. When the router acts as a server, transfers are transparent. Use the ELS subsystem TFTP message log to view the transfer in progress.

A file server or a router is not allowed to copy any file into another router's configuration memory.

To write to the router, use the copy command at the destination local Boot config> prompt.

Using Configuration Files From a Remote Host or Router

To access configuration files from a remote host or router, enter copy at the Boot config> prompt:

Boot config>copy 
Enter source filename?128.185.210.125:loads/configs/vl-28.cfg
Enter destination filename? CONFIG             
COPYing from "128.185.210.125:loads/configs/vl-28.cfg" to "CONFIG"
COPY succeeded
source filename?

 Specify the remote IP address and the pathname. This is the TFTP host or another router with the file on its IBD or disk.

destination filename?

 Accept the default or specify an IP address.

Names for IBD Files

Each file stored on the IBD must have a unique filename. The filename for the IBD can contain the complete pathname in addition to the filename. For example:

test.cfg
or
/usr/loads/test.ldc
The router accepts any printable ASCII character as part of the filename, with two exceptions:

We recommend that you avoid using a space character, because this character is invisible, which can be confusing for other users.

The following chart shows the conventions for filename extensions:

Types of Files Filename Extensions
Configuration

 .cfg

Load

 .exc

Load

 .ldc

Note: When using a router as a boot server for other routers, be sure to include the complete pathname to the load file with the add boot-entry command on the booting router.

To store a file to the IBD, enter copy at the Boot config> prompt.

For example:

Boot config>copy 128.185.210.125:/usr/config/test.cfg ibd/test.cfg

IBD Considerations When Transferring a File

 When transferring a file to a router's IBD, consider the following:

Validating a Configuration Load

 There are two methods the router uses to validate a load before writing the load to the router's configuration memory:

Configuring Dumping

 An important feature of the router is its ability to dump the contents of system memory and the processor's registers to another host during a system reset. It can do this whether the reset results from a software crash, a hardware failure, or pressing the reset switch.

Since dump files are for diagnostic purposes only, you should enable the router's dump and unique-naming capabilities only on the advice of your customer service representative.

If you enable the router's dump and unique-naming capabilities, you must create directories on the destination server to contain the boot and dump files.

The boot and dump functions use TFTP. Your TFTP server may impose additional restrictions.

You can configure the router to append a unique character string to the dump filenames automatically. This prevents an existing dump file from being overwritten by subsequent dumps. Unique naming of dump files can, however, cause the server's disk to become full if there are successive dumps. Unique naming may also be incompatible with the security requirements of some TFTP servers. Some servers require that a file already exist on the server to allow writing the dumps.

To configure dumping, do the following from the Boot config> prompt:

1. Add an address. This can be the same as the boot address used in configuring booting. 

Boot config>add address
Which interface is this address for [0]?1 
New address [0.0.0.0]?128.185.123.51
2. Add a dump entry. Specify the location of the host or server that is going to receive the dump file. The average size of a dump file is 8 Mbytes. 

Boot config>add dump-entry
remote host [0.0.0.0]10.1.153.73 
via gateway (0.0.0.0 if none) [0.0.0.0]? 128.185.160.3
timeout in seconds [10]?
file name []? c:\dump\techpubs.dmp

Note: You should leave the timeout parameter at its default value of 10. Large values (such as 120 seconds) can prevent dumps from completing.
3. Enable dumping with the enable dumping command. Dumping remains enabled until you use the disable dumping command. 

Boot config>enable dumping

Boot CONFIG Commands

This section describes the Boot CONFIG commands.

Press Space twice after you type a command to display the available parameters for each command for your router. Enter help for information about using the command line interface.

Table 1 Boot Config Commands
Command Function
Add Adds a network boot interface, an IP address to a specified interface, a host boot entry, or a host dump entry.

Change Changes the boot interface IP address, network boot entry data, or network dump entry data.

Copy Copies boot files and configuration files to or from remote routers and hosts, or between resources within the router.

Delete Deletes a network boot interface address, host boot entry, or host dump entry.

Describe Displays information about the stored images in the IBD, for load files only.

Disable Disables memory dump or unique naming of dump files.

Enable Enables memory dump or unique naming of dump files.

Erase Erases a stored image on an IBD bank.

List Displays all network boot addresses, all boot and dump configuration data, the contents of the IBD, and BOOTP name settings.

Load Copies a boot file from the IBD to RAM or from a remote host to RAM.

TFTP Initiates TFTP file transfers between router memory or the IBD and remote hosts.

Exit Leaves the Boot CONFIG environment and returns to the CONFIG process.

Add

Adds boot/dump parameters to the router's configuration database.

Syntax: add

address
boot-entry
bp-device
dump-entry

address

 The IP address of the interface over which the router can boot or dump. You must supply the value for the following information, or accept the default:

To see a list of interfaces in the router, enter list interfaces at the Config> prompt.

CAUTION:
You must add an address if you want the router to boot or dump over the network.

Notes:

Example: add address

Which interface is this address for [0]? 
New address [0.0.0.0] ? 128.185.1.2
Net mask for this interface [255.255.255.0]?

boot-entry

 Specifies the information the router needs to locate the TFTP host server and retrieve the boot image file. There are several ways that a router can boot:

Example: add boot-entry

remote host or IBD loadname [0.0.0.0]?  128.185.30.0
via gateway (0.0.0.0 if none) [0.0.0.0]?  0.0.0.0
timeout in seconds [3]? 
file name [ ]?  /tftpboot/loads/gt.ldc
remote host or IBD loadname?

 IP address of the remote host or an IBD loadname.

Note: An IBD loadname must start with a letter. Otherwise, the system interprets the string as an IP address.

via gateway?

 IP address of the first hop router, if any. If the TFTP host server is on a directly connected network, answer 0.0.0.0.

timeout in seconds?

 The amount of time the router waits before retransmitting. The default is 3 seconds. You may set this to a longer time over exceptionally slow boot paths.

file name?

 The complete directory path and name of the boot image file on the TFTP host server. (The complete directory path is not necessary on some machines. For example, if the default assumes the path is /tftpboot/, which is invisible to you, then if the path is /tftpboot/loads/name, you only need to enter loads/name.) Remember,

when referencing a file stored on a UNIX-based operating system use a forward slash /. The filename is case-sensitive. If the path requires the leading /, use the colon before the forward slash : /. For example: 128.185.15.1:/tftpboot/loads/name.

When referencing a file stored on a DOS disk use a backward slash \ and the filename is not case-sensitive.

To see a list of the current boot configuration, enter list boot-entries.

Example: list boot-entries

1: "loads/test.ldc" on 128.185.210.125 via 10.1.153.29 for 3 secs
2: IBD load "latest-test1.ldc"

bp-device

 Provides BOOTP booting capability for retrieving the router's software from a BOOTP device.

Notes:

Example: add bp-device 

Which interface number [0]? 1

dump-entry

 Specifies the IP address of the remote host that receives the dump file(s).

To view a list of the dump configurations, enter list dump-entries.

Note: You should leave the timeout parameter at its default value of 10. Large values (such as 120 seconds) can prevent dumps from completing.

Example: add dump-entry 

remote host [0.0.0.0]? 128.185.162.30
via gateway (0.0.0.0 if none) [0.0.0.0]? 128.185.160.3
timeout in seconds [10]?
file name []? c:\dump\techpubs.dmp
remote host?

 IP address of the remote host on which the dump file is stored, usually the same as the boot server.

via gateway?

 If the host is on a remote network (not directly connected to the booting router), specify the IP address of the next hop (router) towards the host. If the host is on a directly connected network, answer 0.0.0.0.

timeout in seconds?

 Specifies the amount of time the router waits before retransmission takes place. The default is 3 seconds. You may need to increase the time over exceptionally slow boot paths.

file name?

 Base dump path and filename (may have unique suffix appended).

Change

Modifies entries in the existing address, boot-entry, BOOTP devices, and dump-entry information.

Syntax: change

address
boot-entry
bp-device
dump-entry

address

 Changes an existing address for a boot interface or device that was previously added. When you enter the change address command, you must supply the following information:

The screen displays some of this information, such as the address entry number, when you enter list at the Boot config> prompt. To obtain the interface number (Ifc#), enter list interfaces at the Config> prompt.

Example: change address 

Change which entry [1]? 1
Which interface is this address for [0]? 1
New address [192.9.1.1]? 128.185.162.1
Net mask for this interface [255.255.255.0]?

boot-entry

 Modifies the configured information about a previously added network boot file. When you enter change boot-entry, you must supply the following information:

The console displays some of this information, such as the boot entry number, when you enter the list boot-entries command at the Boot config> prompt.

Example: change boot-entry

change which entry [1]? 1
remote host [18.123.0.16]?
via gateway (0.0.0.0 if none) [0.0.0.0]? 
timeout in seconds [3]?
file name [user/lib/gw/gwimage.ldb]?

bp-device

 Changes the interface that is the BOOTP device. To obtain the entry number for an interface, use the list boot-entries command.

Example: change bp-device 

Change which entry [1]? 2
Which interface is this entry for [1]?
For more information on the BOOTP protocol and its related processes, see the IP documentation.

dump-entry

Modifies the configured information about a previously added network dump file. When you enter change dump-entry, you must supply the following information:

Enter list dump-entries at the Boot config> prompt to see this information.

Example: change dump-entry

change which entry [1]? 1
remote host [18.123.0.16]?
via gateway (0.0.0.0 if none) [0.0.0.0]?
timeout in seconds [3]?
file name [user/lib/gw/gwimage.ldb]? c:\dump\Ollie.dmp

Copy

 Copies boot files and configuration files to and from remote routers and hosts. To use the copy command, the router must have IP configured and running on at least one interface. The router cannot be in Config-only mode. This command is similar to the tftp command but the syntax is different.

You can do the following when using the copy command:

Ctrl P Display the * prompt.
Ctrl C Cancel the copy command.

Syntax: copy

config
ibd/<file-name>
<host-ip-address>:/<file-name>

Copying From a Remote Router

 Example: copy

Enter source filename?CONFIG
Enter destination filename?IBD/my_gt70.cfg
COPYing from "CONFIG" to "IBD/my_gt70.cfg"
COPY succeeded
config

 Configuration memory.

ibd/filename

 Filename on IBD. Include complete pathname.

IPaddressremote
path and filename

 Remote file on TFTP host. Include the complete pathname.

When copying a file to the IBD, the router puts the file into the largest set of contiguous free banks. If no banks are available, the message COPY error - TFTP Disk Full or IBD full appears on the console.

Copying From a Remote Host

Example: copy

Enter source filename?128.185.110.15:/router/loads/cgt70.cfg
Enter destination filename? ibd/gt70.cfg
The source has a path and filename. The destination is an IBD file that is named gt70.cfg. The colon (:) in the source is the delimiter between the Host IP address and the path/filename.

Copying Within a Router

Example: copy

Enter source filename? config
Enter destination filename? ibd/gt70.cfg
In the example above, the source is the configuration memory. The destination is an IBD.

config

Gets the same result as if you enter copy except that you do not get prompted for the source filename.

Example: copy config

destination filename [IBD/VL_1-71(p28).cfg]?

ibd/<file-name>

 Copies a boot file or configuration file from an IBD. You must include the filename.

Example: copy ibd/vl-28.cfg

destination filename [CONFIG]?

<host-ip-address>:/<file-name>

 Copies a boot file or configuration file from a remote host. You must include the filename.

Example: copy 128.185.110.30:/loads/test.ldc

destination filename [CONFIG]? ibd/test.ldc

Delete

 Removes entries from the interface address, BOOTP interface, and boot and dump configuration databases.

Syntax: delete

address
boot-entry
bp-device
dump-entry

address

 Removes an interface address entry from the boot and dump configuration database.

When you enter delete address, a prompt appears for the entry you want to delete. To see address entry numbers, enter list addresses at the Boot config> prompt.

To verify the deletion, enter list addresses.

Example: delete address

delete which entry [1]? 2

boot-entry

 Removes a boot entry from the boot and dump configuration database. To find your boot entry number, enter list boot-entries at the Boot config> prompt. The boot-entry number is the first number that appears on each line.

Example: delete boot-entry

delete which entry [1]? 2

bp-device

 Removes the specified interface as a BOOTP device.

Example: delete bp-device 

delete which entry [1]? 1
For more information on BOOTP, see the IP documentation.

dump-entry

Removes a dump entry from the boot and dump configuration database. When you enter delete dump-entry, a prompt appears for the entry you want to delete. The dump entry number is the first number that appears on each line when you enter list dump-entries at the Boot config> prompt.

To verify the deletion, enter list all.

Example: delete dump-entry

delete which entry [1]? 1

Describe

 Displays information about a stored image in the IBD.

Syntax: describe loadname

Displays the following information about the specified loadname:

Example: describe gt70.ldc

Copyright Notice:  Copyright 1985, 1986, 1987, 1989 by J. Noel Chiappa
Proprietary Rights Notice: All Right Reserved. This file contains
the valuable properties and trade secrets of J. Noel Chiappa,
embodying substantial creative efforts and confidential information,
ideas, and expressions, no part of which may be reproduced or
transmitted in any form or by any means, electronic, mechanical or
otherwise, including photocopying and recording or in connection with
any information storage and retrieval system without the permission
in writing of J. Noel Chiappa.
Copyright 1986-1996, by PROTEON, Inc.


GlobeTrotter 70/72 Bridging Router   OpenROUTE(tm) 2.3
Fri Mar 15 16:01:30 1996


Packages:


  p5730-g   GlobeTrotter 70 Internet Connectivity
            Internet Protocol - IP
            PPP with Multilink, PAP, CHAP
            ISDN Line

Disable

 Disables network memory dumping and the unique naming of dump files.

Syntax: disable

dumping
unique-naming

dumping

 Suppresses a memory dump to the network when a system failure occurs. Dumping is disabled as the default setting.

Example: disable dumping

unique-naming

Suppresses the automatic unique naming of dump files. After entering this command, enter list all at the Boot config> prompt to verify the unique-naming setting. Unique naming is disabled as the default.

Example: disable unique-naming

Enable

Enables memory dumping and the unique naming of dump files.

Syntax: enable

dumping
unique-naming

dumping

 Enables a memory dump to the network when a system failure occurs. The command turns on the dump operation using the data supplied with add dump-entry. Enable dumping only if the router is experiencing problems of unknown origin. Dump files can be very large and consume large amounts of disk space. Further, it takes considerable time to transfer large dump files to the dump host.

Dumping is enabled until you enter disable dumping.

Example: enable dumping

unique-naming

Enables the automatic unique naming of dump files. Adds a random suffix (hexadecimal) between 1 and 5 characters to the configured dump filename during a dump.

If you need more than one instance of the dump file, enable the unique-naming feature. Avoid filling disk storage space with unneeded dump files. Some UNIX hosts are not capable of accepting this feature.

Dump files include unique names until you enable disable unique-naming.

Example: enable unique-naming

Erase

Erases a stored image or an IBD bank.

Syntax: erase loadname or bank-number

Erases a stored image or an IBD bank. Type the loadname or the bank number (1, 2, 3, or 4) that contains the load. To verify the erasure, enter list ibd. If an erase does not succeed after 10 tries, the router marks the bank as faulty.

Specifying a bank number may result in a partial erasure of the load file if it is large enough to traverse more than one bank.

Example: erase test

Erasing bank 5 ...
Banks 1-4 contain ...
Banks 5-7 have been erased
Example: erase 2

Are you sure you want to erase bank 2? (Yes or [No]): yes
Erasing bank 2 ...
Banks 5-7 have been erased
If the erasure fails, a message indicating the failure appears on the screen along with the banks that failed. Failure information appears in the list command until the router is restarted. The router does not automatically delete any boot records referencing the image in the failed bank(s).

At boot time, if the boot PROM cannot find an image, it displays a message and tries the next boot record.

Exit

Returns to the previous command level. For example, if you are at the Boot config> prompt and enter exit, you go back to the Config> prompt.

Syntax: exit

Example: exit

Config>

List

 Displays the current boot and dump configuration database and the contents of the IBD.

Syntax: list

addresses
all
boot-entries
bp-device
dump-entries
disk
ibd

addresses

 Displays the IP addresses and subnet masks of all of the network boot interfaces set up with add address.

Example: list addresses

Interface addresses:
1: 192.9.1.1 on interface 0, mask 255.255.255.252
2: 192.9.223.39 on interface 5, mask 255.255.255.0

all

 Displays all boot and dump configuration data and the current settings for the dump and unique-naming capabilities.

Example: list all

Interface Addresses:
 1: 128.185.227.23 on interface 0, mask 255.255.255.0


Boot files:
 1: "loads/latest-gen.gt70.ldc" on 128.185.210.125 via 128.185.227.15
	 	for 10 ses
 2: IBD load "gt70.ldc"


BOOTP over interface(s):
Dumping disabled
Unique-naming disabled
Dump to:


Banks 1-9 contain load "gt70.ldc" which uses 545421 bytes
     Loaded using TFTP over IP
     Filename gt70.ldc
     Host 128.185.1.11
Banks 10-14 have been erased

boot-entries

 Displays the boot file configuration setup with add boot-entry.

Example: list boot-entries

1: /usr/lib/gw/this-dn.ldb on 192.9.1.2 via 0.0.0.0 for 3 secs  
2: /usr/lib/gw/this.ldb on 192.9.2.2 via 192.9.1.4 for 3 scs  
3: IBD load "test"

bp-device

 Lists the interfaces added with add bp-device.

Example: list bp-device

BOOTP over interface(s): 0 1

disk

 Lists the contents of the disk drive.

Syntax: list disk

Example: list disk

dump-entries

 Displays the dump file configuration set up with add dump-entry.

Example: list dump-entries

1: "dumps/rbx-51.dmp" on 128.185.210.125 via 128.185.123.28 for 3 secs

ibd

 Displays the contents of the IBD. This is like the information you get when you enter boot information at the + prompt. It displays

Example: list ibd 

Banks 1-9 contain load "gt70.ldc" which uses 545421 bytes
     Loaded using TFTP over IP
     Filename gt70.ldc
     Host 128.185.1.11
Banks 10-14 have been erased

Load

 Copies the boot file into the router's main memory from either a local or remote source. Typing load at the Boot config> prompt is an alternative to typing reload at the * prompt.

Syntax: load

local
remote

local

 Transfers a load file previously stored in the router's IBD to the router's memory. The loadname is case-sensitive and must match one of the loadnames stored in the IBD.

You must have a load file in the IBD to use load local successfully.

Note: If the software does not find the load file, it goes into the boot monitor and does an autoboot or manual boot, depending on the setting of your boot switch.

Example: load local 

Loadname: gt70.ldc
Are you sure you want to reload the gateway (Yes or No): yes
PROM Load/Dump Program *Revision: 1.20*
Copyright 1985 - 1993 Proteon, Inc. All rights reserved
     Host CNX5-29 loading
Loading using IBD Load Image "rbx2-multisna.ldc"
___________________________
Starting at 1040000
Copyright Notices:
Copyright 1984-1996 Proteon, Inc.
Copyright 1984 - 1987, 1989 by J. Noel Chiappa
MOS Operator Control
*

remote

 Loads the boot file from a remote host (TFTP host server) into configuration memory. If the network's local interface is not configured first using the add address command, the router tells you the first hop is unreachable. To perform a remote load:

1. If your router has a boot switch, ensure the boot switch on the router is set to the auto position.

2. Enter load remote at the Boot config> prompt and enter the remote host address, remote pathname, first hop address, and TFTP timeout value after the prompts.

3. A prompt then asks you to confirm the reload. Enter no to cancel the command. Enter yes to load the boot file from the remote host.

Example: load remote

Remote Host Address[0.0.0.0]? 128.185.210.125
Remote Pathname[ ]? /loads/gt70.ldc
First Hop Address[0.0.0.0]? 128.185.208.38
TFTP Timeout Value[3]?
Are you sure you want to reload the gateway(Yes or No): yes
Remote Host Address

 IP address of the host containing the boot file.

Remote Pathname

 Pathname and filename of the boot file you want to load.

First Hop Address

 The address of the first-hop router that routes to other networks. Specify if the remote host address is not on a directly-connected network; if it is, use the 0.0.0.0 default.

TFTP Timeout Value

 The time interval between the TFTP packet retransmissions. You may need values longer than the default value of 3 to boot over or across slow networks or serial lines.

TFTP

Initiates TFTP file transfers between a remote host and the router's non-volatile configuration memory or IBD. Lets you store a file in or retrieve it from a TFTP server or a router with an IBD. This command works like copy but the syntax is different.

The router acts as a TFTP client. The remote host is any device (for example, router, workstation, PC) running IP and acting as a TFTP server node. The router cannot be in Config-only mode.

Typing tftp get and tftp put locks the CONFIG process for the duration of the operation. You can do the following:

Ctrl P Display the * prompt.
Ctrl C Cancel the TFTP operation.

Note: Do not press the reset switch or power off the router while it is performing tftp get. Doing this leaves the destination memory in an inconsistent and invalid state. That is, you get a portion of a configuration or load and it looks like it is valid.

Syntax: tftp

get
put

get

Initiates a request to a TFTP server to transfer a file from the remote host to the router. The server sends individual data packets and the client node acknowledges their receipt until the transfer is complete. 

TFTP transfer complete,  Status: OK
If the TFTP transfer is unsuccessful, a detailed error message appears on the screen. While transferring a file to CONFIG, the following message appears on the screen:

Updating CONFIG:  Do Not Interrupt!
If you are attempting to transfer a file to an IBD and there is no room on the IBD, the following message appears:

No Free IBD Bank
Erase one or more banks to make room.

CAUTION:
Do not reset or power off the router while the updating of the configuration memory is in progress. This can corrupt the data in the configuration memory, forcing you to reconfigure the router.

Syntax: tftp get local filename remote host address path/filename

Example: tftp get

Enter local filename [CONFIG]?
Enter remote host's IP address or name in host table? 128.185.227.58
Enter path/filename of file on remote host []? configs/v1-28.cfg          
TFTP transfer complete, status: OK
Enter local filename?

 The name that you want the transferred file to have on the local router. Specify the complete pathname if you are transferring the file to the IBD. Filenames cannot begin with a digit. The default is CONFIG.

Enter remote host's IP address of name in host table?

 The address of the remote host with the file to transfer. The Magic Number stored in the file is compared to the number in static memory. This prevents cross loading non-volatile memories between types of routers.

Enter path/filename of file on remote host?

 The unique name of the file on the remote host. Specify the complete pathname. It is case-sensitive. The hostname must match the hostname in the archive file. Filenames cannot begin with a digit. The default is the ASCII representation of one of the host's IP addresses in hexadecimal.

put

Transfers a file to the server from the router. The server acknowledges the request and the client transfers the file. This cycle continues until the transfer is complete and the following message appears: 

TFTP transfer complete,  Status: OK
To transfer a file into another router's configuration memory or IBD, log into the destination router and enter tftp get.

To transfer a router's configuration file into the router's configuration memory, enter tftp get or copy commands at the Boot config> prompt.

Syntax: tftp put local filename remote host address path/filename

Example: tftp put

Enter local filename [CONFIG]? IBD/GT70.ldc
Enter remote host's IP address or name in host table? 128.185.227.58
Enter path/filename of file on remote host []? gt70.ldc  
TFTP transfer complete, status: OK
Enter local filename?

 The name of the local file that you are transferring. CONFIG is a filename that refers to the router's non-volatile memory. Filenames cannot begin with a digit.

Enter remote host's IP address or name in host table?

 The IP address of the remote host and filename to be used to store the CONFIG file on the remote host.

Enter path/filename of file on remote host?

 The unique name of the file on the remote host. Specify the complete pathname. It is case-sensitive. The hostname must match the hostname in the archive file. Filenames cannot begin with a digit. The default is the ASCII representation of one of the host's IP addresses in hexadecimal.

If you try to put a configuration file on another router's IBD, the result is an access violation.

To cancel a TFTP transaction, press Ctrl C. Enter yes.

Are you sure (Yes or No):yes

The tftp command generates the following error messages:
Error Message Meaning
Unknown Error

 Protocol failure.

File Not Found

 Specified host file does not exist.

Access Violation

 File protection error.

Disk Full

 File system full during write.

Illegal Operation

 Undefined TFTP operation requested.

Unknown TID

 Unexpected TFTP packet received.

File Already Exists

 File already exists.

No Such User

 TFTP not supported on host.

Bad Magic Number

 Configuration file from a different type of router.


[Top] [Prev] [Next] [Bottom]

docs@openroute.com
Copyright © 1998, OpenROUTE Networks, Inc. All rights reserved.