System Image and Configuration File Management

This chapter describes how to:

• Manage the disk space on your Avici router
  
  
• Load system images and configuration files
  
  
• Perform ROM-burn and Post-burn
  
  
• Recover from a lost password
  
  

System images contain IPriori, the server operating system. The Avici router comes pre-loaded with two system images: the currently operational system image and a fallback image. If the current version of the system image is damaged, you can reload using the fallback version for the system.

Configuration files contain commands to define the operation of the router. By default, the configuration file named startup.cfg is loaded when the system is started.

The Avici router supports up to two disk systems.

System images, configuration files, and logging files can be stored in directories on either disk. The default directory for the startup configuration file is disk a:. When you boot the Avici router, IPriori searches for the configuration file named startup.cfg first on disk a:, then on disk b:.

IPriori creates logging files in the opposite direction. To create a logging file, IPriori tries to create logging files on disk b:. If disk b: is not installed, IPriori creates the logging files on disk a:.

Managing Files

If your disk system becomes overcrowded, you can delete any outdated files. You can recover deleted files until you use the squeeze command. The squeeze command permanently removes the file from the file system.

NOTE If you are out of disk space, use the squeeze command first to remove already deleted files, as these files take up usable space.

Deleting Files

PROCEDURE: Use the following steps to delete a file:

Step 1 Use the cd command to change the current directory.

Step 2 Use the delete or erase command to move a specified file to the trash directory. For example:

router#cd c: router#delete config.tst

or

router#cd a: router#erase startup-config

Step 3 Use the squeeze command to delete all files in the trash directory of the current disk. The following prompt is displayed:

Is this what you want to do (yes/no)?

Enter the full word response "yes" or "no". If you enter only "y", no deletions occur.

In the following example:

• the cd commands set the current device and directory to the trash directory on disk A:
  
  
• the dir command displays the contents of the trash directory
  
  
• the squeeze command deletes any files in the trash directory
  
  
• the dir command re-displays the contents of the trash directory
  
  

router#cd a: router#cd trash router#dir size date time name -------- ------ ------ -------- 512 JUN-02-2001 20:55:42 . <DIR> 512 JUN-02-2001 20:55:42 .. <DIR> 695 JUN-23-2001 20:55:14 DELETE2 2140504064 bytes free router#squeeze WARNING - This will delete all files in the TRASH. Is this what you want to do (yes/no)? yes router#dir size date time name -------- ------ ------ -------- 512 JUN-02-2001 20:55:42 . <DIR> 512 JUN-02-2001 20:55:42 .. <DIR> 2140504749 bytes free

Recovering Deleted Files

To recover any deleted file (until you use the squeeze command):

Use the undelete or unerase command to recover the file:

:

router#undelete config.tst

or

router#unerase config.tst

You can not recover a file from the trash directory if there is another file with the same file name already in your directory. To recover a file with the same file name as an existing (not marked for deletion) file, you must first either delete or rename the existing file.

Updating System Image Files

You must burn system image files into flash memory using the boot command before you start the system.

The Avici router comes loaded with the latest release of software. By default, the Avici router uses the software image specified by the last boot command. You can stop the booting process and change the boot defaults.

You can retrieve system image files from a remote network server or from the disk system on the Avici router's server.

You can change the boot image on all, or any combination of, servers, modules, or bay controllers with the upgrade-all command.

PROCEDURE: To install an updated system image from local disk, perform the following steps:

Step 1 Use the boot command to burn the new image file into flash memory.

In the following example the system image file newimage.cmp resides on the local disk. The boot command burns the new image into location 1 (of 2) in flash memory:

:

router(config)#boot newimage.cmp 1

The image that occupied the first position in flash memory is overwritten with the new file.

Step 2 Use the show flash command to verify that the new image loaded successfully. For example:

router#show flash -------------- Flash Directory ------------------ -------------- (Version: 1.2) ------------------- Number of Images: 2 Post: No Image Current Operational Image: 2 Image 1 Name: newimage.cmp Size: 1400773 bytes Image 2 Name: wood1_5.cmp Size: 1458572 bytes Boot Flags: 0x00000004 Checksum Is Valid ---------------- Obituary Log ------------------- ------------------------------------------------- Base Address of Obit Log: 0xc00f0000 Size of Obit Log: 00031752 Address of Oldest Obit Entry: 0xc00f0000 Address of Current Obit Entry: 0xc00f0094 ------------------- RAM Log --------------------- ------------------------------------------------- Address of RAM Log 0 Header: 0x00003450 Max size of each RAM Log: 65536 Crash Dump Flags: 0xeeee State Flags: 0 TSR ID: 0

Step 3 Use the reload command to restart the system using the new image file. A preliminary check of memory runs. The test results display on the console terminal screen:

router#reload Do you really want to re-load (y/n)[n]: y Memory has not been cleared.

Press any key to stop auto-boot... 0 auto-booting...

boot device : flash inet on ethernet (e) : 10.5.1.125:ffff0000 flags (f) : 0x0 target name (tn) : regsrv1 TSR ID : 9 Loading image Checksum correct for image Starting at 0x100000...

Auto-configuring SCSI bus...

Adding 10066 symbols for standalone. Copyright (c) 1993-1996 RST Software Industries Ltd. Israel. All rights reserved ver: 2.6 FCS Disk Check In Progress ... Done Checking Disk. Detected a 20054016 Byte Flash Disk No Flash Disk Detected Default disk set to solid-state disk A: Starting SNMP...Done

Avici Systems TSR Copyright 1997-2001 Avici Systems, Inc. CPU: VI Computer POWER4C PPC MACH5 300 MHZ/MPC106v40 OS: IPriori, Version BSP version: 1.1 /2 Creation date: Dec 16 2000, 21:54:54 Build name: Platform: 4cs-d; Label: BU_BL8 Debug: Ready Loading startup configuration... Startup configuration A:\STARTUP.CFG has been loaded. password: router>

If no error messages are displayed, the new version of IPriori has been successfully installed and used to start up the Avici router. If there is a failure during reload, error messages are displayed on the console terminal.

Upgrading All Components With a Single Command

You can perform a system image upgrade on all components of one or more platforms with a single upgrade-all command in configuration mode. The server, module, and bay controller platforms can be upgraded using this command.

Example: In the following example, the upgrade-all command:

• Puts the file tsr.bay into flash location 1 on the bay.
  
  
• Puts the file tsr.mod into flash location 1 on the module.
  
  
• Puts the file tsr.srv into flash location 1 on the server.
  
  

router(config)#upgrade-all bay tsr.bay 1 module tsr.mod 1 server tsr.srv 1 Upgrading BAY image. Burning boot image tsr.bay into location 1 for bay controllers: [1, 1], [1, 2], Done (bay 1, slot 2) Done (bay 1, slot 1) Burn Results: 2 succeeded 0 failed Upgrading MODULE image.

Burning boot image tsr.mod into location 1 for modules: [1, 4], [1, 5], [1, 6], [1, 7], [1, 8], [1,13], [1,14], [1,15], [1,16], [1,17], [1,18], Done (bay 1, slot 4) Done (bay 1, slot 5) Done (bay 1, slot 6) Done (bay 1, slot 7) Done (bay 1, slot 8) Done (bay 1, slot 14) Done (bay 1, slot 16) Done (bay 1, slot 15) Done (bay 1, slot 13) Done (bay 1, slot 17) Done (bay 1, slot 18) Burn Results: 11 succeeded 0 failed Upgrading SERVER image. Preparing to perform flash burn......done Erasing space for image ...........done Writing image to flash .....................................done (config)#

Recovering From A Failure During Boot

CAUTION If there is any failure during the booting process, do not reset the server by using the reload command or cycling the power.

The Avici router's flash memory has room for two copies of the IPriori system image; a current image and a backup image. If a new (current) system image causes the Avici router boot process to fail, you can boot from the backup image.

To change the image file loaded during the boot process, interrupt the boot process and enter boot ROM monitor mode.

The boot process has three phases:

• Phase 1 is before the boot process actually begins. You can interrupt Phase 1 simply by pressing any key within 2 seconds of entering the reload command.
  
  
• Phase 2 begins 2 seconds after you enter the reload command and the boot process is underway.
  
  
• Phase 3 begins when the boot process is complete and the system is up.
  
  

  NOTE You can interrupt Phase 2 or Phase 3 by pressing the Ctrl-X keys or by resetting the server. Once the system is fully up, you must use the reload command to restart the system.

Once in ROM mode, you can specify which image in flash memory is used to boot the Avici router.

Let's assume that you burned a new system image into flash memory and used the reload command to boot the system. An error occurs and the boot process fails.

PROCEDURE: Use the following steps to specify that the Avici router boot using the fallback system image:

Step 1 Use the reload command with no arguments to start the boot process.

Step 2 Interrupt the boot process by pressing any key within 2 seconds during Phase 1 or by pressing Ctrl X during Phase 2 or Phase 3. (See NOTE above.) The boot process stops and the command mode changes to ROM mode.

In the following example, the boot process is interrupted by pressing any key within 2 seconds, and the ? displays the commands available in boot ROM mode:

router#reload <press any key within 2 seconds> [IPriori Boot]: ? ? - print this list boot - boot (load and go) print - print boot params

change - change boot params load - load boot file go adrs - go to adrs dump adrs[,nbytes][,width] - dump memory at adrs, [for nbytes], [by width] modify adrs - modify memory starting at adrs (interactive) fill adrs, nbytes, value - fill memory at adrs, for nbytes with value transfer fadrs, dadrs, nbytes - copy memory from fadrs, to dadrs, nbytes

exception - print last fatal exception network netif - print network interface device address aflash - Display the flash directory aclear [#] - Clear all (or specified) NVRAM address settings anvram value - Change the NVRAM boot flags (value in Hex!) apost - Execute the Avici Post Executive adefault - Set default operational image aload [#] - Load a Flash image (default = 0) ago [#] - Load and run a Flash image (default = 0)

aramlog # - Display the RAM log (starting at '#') aobit # - Display the Obit log (starting at '#') aClear - Clear the Obit log Boot flags: 0x04 - don't autoboot 0x08 - quick autoboot (no countdown) 0x80 - use tftp to get boot image Available boot devices:net, flash

Step 3 Use the aflash command to display the current and fallback system images currently burned into flash memory:

[IPriori Boot]:aflash -------------- Flash Directory ------------------ -------------- (Version: 1.2) ------------------- Number of Images: 2 Post: No Image Current Operational Image: 1 Image 1 Name: newimage.cmp Size: 1343478 bytes Image 2 Name: backup.cmp Size: 1302500 bytes Boot Flags: 0x00000000 Checksum Is Valid TSR ID: 0

Step 4 Identify the number of the fallback system image. Valid values are 1 or 2.

Step 5 Use the adefault command to change the default system image to the selected image. For example, if the fallback image is image 2:

[IPriori Boot]:adefault 2

This specifies that the Avici router will, by default, boot from the fallback image.

Step 6 Use the boot command to restart the boot process. The Avici router boots using the fallback system image.

In general, you do not reload and retry an image that has failed.

Updating System Images from Remote Server

You can install and load system image files from remote servers using either of two methods:

• Use the copy ftp command to retrieve a new system image from a remote server, burn the new image into flash memory and restart the system.
  
  
• Use the network option of the copy command to burn a system image directly from a remote server into flash memory and restart the system.
  
  

Copying System Image From A Remote Server

PROCEDURE: To copy a system image from a remote server, perform the following steps:

Step 1 Use the copy ftp filename command to retrieve the system image from a remote server. You are prompted to enter the following information:

Table 2-1. copy ftp Command Prompts

Field	Description
Source filename	Enter the name of the file to copy. File names may be up to 8 characters long with a 3 character extension. For example: newnodes.cfg.
Destination filename	Enter the name for the file on the destination system.
Host directory	Enter the name of the directory on the remote system where the source file is located (for copying from a remote host).
Host name or address	Enter the name or IP address of the remote system where the source file is located (for copying from a remote host).
Username	Enter your user name on the remote host.
Password	Enter your password on the remote host. The text is not displayed as you type.

For example:

router#copy ftp newimage.cmp Enter source filename:new.cmp Enter host directory: C:/ Enter hostname or address: 10.5.1.13 Username: userid Password: Remote Copy Succeeded!

This procedure copies a new system image named new.cmp from drive C on remote system 10.5.1.13 to a file named newimage.cmp on the local server using the file transfer protocol.

Step 2 Use the boot command to burn the new image file into flash memory.

In the following example, the boot command burns newimage.cmp into flash memory. Because no location argument is supplied with the boot command, the new image overwrites the existing image designated as the current operational image:

router(config)#boot newimage.cmp

Step 3 Use the show flash command to verify that the new image loaded successfully:

router#show flash -------------- Flash Directory ------------------ -------------- (Version: 1.2) ------------------- Number of Images: 2 Post: No Image Current Operational Image: 2 Image 1 Name: svr1.cmp Size: 1400773 bytes Image 2 Name: wood1_5.cmp Size: 1458572 bytes Boot Flags: 0x00000004 Checksum Is Valid

---------------- Obituary Log ------------------- ------------------------------------------------- Base Address of Obit Log: 0xc00f0000 Size of Obit Log: 00031752 Address of Oldest Obit Entry: 0xc00f0000 Address of Current Obit Entry: 0xc00f0094

------------------- RAM Log --------------------- ------------------------------------------------- Address of RAM Log 0 Header: 0x00003450 Max size of each RAM Log: 65536 Crash Dump Flags: 0xeeee State Flags: 0 TSR ID: 0

Step 4 Use the reload command to restart the system using the new image file:

router#reload Press any key to stop auto-boot... 0 auto-booting... >> boot device : flash flags (f) : 0x0 target name (tn) : testbed24 Loading from 0xff000000... Checksum correct for image Starting at 0x100000...

Avici Systems TSR Copyright 1997-2001 Avici Systems, Inc. CPU: VI Computer POWER4C PPC MACH5 300 MHZ/MPC106v40 OS: IPriori, Alpha Version BSP version: 1.1 /2 Creation date: Feb 9 2001, 14:50:01 Build name: Platform: 4cs; Unauthorized, untested image Debug: Ready

Loading startup configuration... Startup configuration has been loaded. User Verification Password:

CAUTION If there is any failure during the booting process, DO NOT reset the server by using the reload command or cycling the power.

See "Recovering From A Failure During Boot for more information.

Netloading System Image From A Remote Server

WARNING Loading a system image file directly from a remote server is a procedure meant to provide diagnosis of network problems. ONLY trained service personnel should perform this task.

PROCEDURE: To boot the Avici router directly from a system file on a remote server, perform the following steps:

Step 1 Use the reload command to start the boot process.

Step 2 Interrupt the boot process by pressing any key within 2 seconds. The boot process stops and the command mode changes to ROM mode.

Step 3 Once in ROM mode, use the change command to change the boot device to net. To leave a field unchanged, and move to the next field, press RETURN.

Step 4 Enter the new parameters.:

[IPriori Boot]:change boot device : net host name : swsrv1 file name : /home/wdstck/IPriori.net inet on ethernet (e) : 10.5.1.202:ffff0000 host inet (h) : 10.1.2.80 gateway inet (g) : 10.5.0.1 user (u) : userid ftp password (pw) : *********** flags (f) : 0x0 target name (tn) : router TSR ID : 0

The parameters and their meaning are described in the following table:

Table 2-2. Change Command Parameters 

Field	Description
boot device	Specifies what entity to boot from. Valid values are net (boots from a system image file on a remote server) or flash (boots from a system image in local flash memory.
host name	Host name of the remote server where the system image resides. If the host name can not be resolved, enter the IP address of the remote server.
file name	Path to the system image on the remote server.
inet on ethernet (e)	IP address and subnet mask of interface Ethernet 0.
host inet (h)	IP address of server identified in the host name field.
gateway inet (g)	IP address of the local gateway router.
user (u)	User ID for FTP or RSH.
ftp password (pw)	FTP password. Blank if using RSH.
flags (f)	0x00 - (delayed autoboot) Allows 8 seconds to interrupt boot process. 0x08 - (quick autoboot) Allows you 2 seconds to interrupt boot process. 0x80 - (tftp) Sets the default file transfer protocol to tftp. Overrides RSH/FTP.
target name (tn)	The name displayed at system start up before entering Privileged mode and setting the system name.
startup script (s)	This field is left blank.
TSR ID	The value of the Avici router ID is always 0.

Step 5 Use the boot command to load the specified system image and restart the Avici router. In the following example, the boot parameters set in Step 3 are used to restart the system:

[IPriori Boot]:boot ********************** netload *************************************** boot device : net host name : swsrv1 file name : /home/wdstck/IPriori.net inet on ethernet (e) : 10.5.1.202:ffff0000 host inet (h) : 10.1.2.80 gateway inet (g) : 10.5.0.1 user (u) : userid

ftp password (pw) : *********** flags (f) : 0x00 target name (tn) : svr-10 TSR ID : 0

Attached TCP/IP interface to eth0 Loading... 4331864 Starting at 0x100000... Log system up Auto-configuring SCSI bus...

ID LUN VendorID ProductID Rev. Type Blocks BlkSize pScsiPhysDev -- --- -------- ---------------- ---- ---- -------- ------- ------------ 6 0 QUANTUM FIREBALL SE4.3S PJ0A 0 8418816 512 0x137da208 Date: 02-09-2001 Time: 15:36:22 The Intel 28F016SA/28F160B3T flash parts start at 0xff000000 The AMD AM29F040 flash part start at 0xfff00000

Attaching network interface eth0...Done Attaching network interface eth1...Done Attaching network interface eth2...Done Attaching network interface eth3...Done Attaching network interface eth4...Done Attaching network interface Null0... done.

Adding 8208 symbols for standalone. S_dosFsLib_VOLUME_NOT_AVAILABLE Adding Default Logfile os_log Starting SNMP...Done

Avici Systems TSR Copyright 1997-2001 Avici Systems, Inc. CPU: VI Computer POWER4C PPC MACH5 300 MHZ/MPC106v40 OS: IPriori, Alpha Version BSP version: 1.1 /2 Creation date: Feb 9 2001, 14:50:01 Build name: Platform: 4cs; Unauthorized, untested image Debug: Ready

Loading startup configuration... Startup configuration has been loaded. User Verification Password:

Updating a ROM Image

You can perform a ROM-burn on any or all module(s) or bay(s) with a single command line. You can perform a ROM-burn on one server at a time. Whether a given CLI entry updates a single platform component (i.e. a single module or bay) or all platform components depends upon the command mode as follows:

• Configuration command mode for the desired server to burn a server ROM
  
  
• Module command mode to burn a specific module ROM
  
  
• Module-all command mode to burn the same image on to all module ROMs
  
  
• Bay command mode to burn a specific bay ROM
  
  
• Bay-all command mode to burn the same image on to all bays.
  
  

Within the appropriate command mode, the rom-burn image-name command is used to burn the updated ROM image. The new ROM image is not the active image until you reboot the upgraded platform. Once you have rebooted the upgraded platform, use the show version command to display the active image.

WARNING If a rom-burn fails, you must successfully reburn ROM prior to reboot. Attempting to perform a rom-burn on a failed ROM after a reboot may require that the module be replaced.

Example: The following example enters the module-all configuration mode and performs a ROM-burn on all modules for this Avici router:

router#configure terminal Enter configuration commands, one per line. End with CNTL/Z. router(config)#module-all router(config-module-all)#rom-burn bootcpm.rom Burning boot image bootcpm.rom into location 0 for modules: [1, 4], [1, 5], [1, 6], [1, 7], [1, 8], [1,13], [1,14], [1,15], [1,16], [1,17], [1,18], Done (bay 1, slot 4) Done (bay 1, slot 5) Done (bay 1, slot 6) Done (bay 1, slot 7) Done (bay 1, slot 8) Done (bay 1, slot 14) Done (bay 1, slot 16) Done (bay 1, slot 15) Done (bay 1, slot 13) Done (bay 1, slot 17) Done (bay 1, slot 18) Burn Results: 11 succeeded 0 failed router(config-module-all)#end router#

Updating a POST Image

You can perform a POST-burn on any or all module(s) or bay(s) with a single command line.Whether a given CLI entry updates a single platform component (i.e. a single module or bay) or all platform components depends upon the command mode as follows:

• Module command mode to burn a specific module POST
  
  
• Module-all command mode to burn the same image on to all module POSTs
  
  
• Bay command mode to burn a specific bay POST
  
  
• Bay-all command mode to burn the same image on to all bays.
  
  

Within the appropriate command mode, the post-burn image-name command is used to burn the updated POST image. Use the show flash command, specifying the appropriate platform, to verify the updated image.

WARNING If a post-burn fails, you must successfully reburn POST prior to reboot. Attempting to perform a post-burn on a failed post after a reboot may require that the module be replaced.

Example: The following example enters the module configuration mode and performs a POST-burn on a single module:

router#configure terminal Enter configuration commands, one per line. End with CNTL/Z. router(config)#module 1/18 router(config-module)#post-burn postcpm.rom Burning boot image postcpm.rom into location 0 for modules: [1,18], Done (bay 1, slot 18) Burn Results: 1 succeeded 0 failed router(config-module)#end router#

Updating Configuration Files

Configuration files contain the commands that define how the Avici router operates. The configuration file named startup.cfg is always loaded from the local disk system as the operational configuration when the Avici router is started.

You can maintain multiple configuration files on either the local disk or a server, but only startup.cfg on the local disk is used at system startup.

PROCEDURE: The following steps are typical to update the configuration file:

Step 1 Retrieve a new configuration file from a network server.

Step 2 Use the boot config filename command to copy the specified file to startup.cfg and save the current file as startup.bkp.

Step 3 Use the reload command to start the system using the new configuration file.

Step 4 Use the enable command to enter privileged mode.

Step 5 Use the configure terminal command to enter configuration mode.

Step 6 Optionally, modify the configuration file using the CLI.

Step 7 Save the changes to the configuration file using the write command.

Updating from Local Disk

PROCEDURE: To install a configuration file from local disk, perform the following steps:

Step 1 Starting in configuration mode, use the reboot config filename command to replace the contents of the startup configuration file startup.cfg with the contents of the specified file and restart the system.

In the following example, reboot overwrites the configuration file (startup.cfg) with the contents of a file named test.cfg and restarts the system:

router(config)#reboot config test.cfg

The PROM diagnostics run a preliminary check on memory and verify that the loader is present in the file system. The test results are displayed on the console screen.

Step 2 When the boot process is complete, use the show startup-config command to display the contents of the startup configuration file (startup.cfg).

Step 3 Verify that the new configuration file is operational.

Step 4 Optionally, use the CLI commands to modify the startup configuration file. Refer to the IPriori Command-Line Interface Reference for information about the CLI commands.

Step 5 Use the write command with no arguments to save the modified file as startup.cfg on the local disk:

router#write Saving configuration... router#

The previous step saves the modified configuration file as startup.cfg on the local disk.

or:

Use the write file filename command to save the modified file on local disk with the specified filename:

router#write file test44.cfg Saving configuration... router#

This procedure saves the modified configuration file as test44.cfg on the local disk.

or:

Use the write network [filename] command to save the modified file on a remote host. You are prompted to enter the following information:

Table 2-3. write network Command Prompts

Field	Description
Host name or address	Enter the name or IP address of the remote system where the source file is located (for copying from a remote host).
Destination filename	Enter the file name as it should appear on the remote system.
Write file filename to host IP address?	Enter yes to confirm the information and complete the copy operation. Enter no to cancel the copy operation.

For example:

router#write network Host Address [255.255.255.255]:10.5.1.190 Destination filename: test.cfg Write file test.cfg to host 10.5.1.190 [yes|no] ? yes Saving configuration... router#

This process saves the modified configuration file with the file name test.cfg on a remote host with an IP address of 10.5.1.190.

See write in the "System Image and Configuration File Management" chapter of the IPriori Command-Line Interface Reference.

Updating from Remote Server

PROCEDURE: To install a configuration file from the network, perform the following steps:

Step 1 Use the copy {tftp | ftp} destination command to copy a configuration file from a remote system to the local disk system.

NOTE The startup configuration file must reside on the local disk system. The startup configuration file must be named startup.cfg. You may have multiple start up configuration files stored on your local disk, but only the file named startup.cfg is loaded at system start.

In the following example, FTP is used to copy the startup configuration file (startup.cfg) from a remote system to a file named test.cfg on the default device of the local system:

router#copy ftp startup-config Enter destination filename: test.cfg Enter host directory: C:\ Enter hostname or address: 10.5.1.190 Username: userid Password: Remote Copy Succeeded!

Step 2 Use the reboot config filename command to replace the contents of the configuration file startup.cfg with the specified file and restart the system.

In the following example, reboot config filename command is used to overwrite the configuration file (startup.cfg) with the contents of a file named test.cfg and restart the system:

router(config)#reboot config test.cfg

The existing configuration file is saved as startup.bck

Step 3 Use the show startup-config command to display the contents of the startup configuration file (startup.cfg).

Step 4 Use the CLI commands to modify the startup configuration file.

Step 5 Use the write command with no arguments to save the modified file as startup.cfg on the local disk:

router#write Saving configuration... router#

The previous step saves the modified configuration file as startup.cfg on the local disk.

or:

Use the write file [ filename] command to save the modified file with the specified file name on local disk:

router#write file test.cfg Saving configuration...

This command saves the modified configuration file with the name test.cfg on the local disk.

or:

Use the write network [filename] command to save the modified file on a remote host:

router#write network Host Address [255.255.255.255]:10.5.1.190 Destination filename: testfile.cfg Write file testfile.cfg to host 10.5.1.190 [yes|no] ? yes Saving configuration...

This command saves the modified configuration file with the file name test.cfg on a remote host with an IP address of 10.5.1.190.

See the write command in the "Configuration and File Management Commands" chapter of the IPriori Command-Line Interface Reference.

Copyright © 2002 Avici Systems Inc.
Avici® and TSR® are registered trademarks of Avici Systems Inc.
IPriori™ and SSR™ are trademarks of Avici Systems Inc.

   Source File Name: FileMgmt.fm
    HTML File Name: FileMgmt.html
    Last Updated: 05/30/02 at 13:53:51

Please email suggestions and comments to: doc@avici.com