ATM Switch Router Command Reference, 12.0(1a)W5(7b)
B Commands for the ATM Switch
Download this chapter
B Commands for the ATM SwitchB Commands for the ATM Switch
give_us_feedback

Table of Contents

B Commands
 background-routes-enable
 bandwidth
 boot config
 boot system

B Commands

Note      Commands that are identical to those documented in the Cisco IOS software documentation have been removed from this chapter. Refer to Appendix D, "Removed and Changed Commands," of this command reference for a list of removed commands.

background-routes-enable

To enable background route computation and to specify how often the switch polls for a significant change that activates a new computation of the background routes, use the background-routes-enable ATM router PNNI configuration command. To disable background route computation, use the no form of this command.

background-routes-enable [insignificant-threshold number] [poll-interval seconds]
no background-routes-enable
Syntax Description

number

Specifies the number of insignificant changes necessary to trigger a new computation of the background routes, from 1 to 100. The default is 32.

seconds

Specifies the poll interval in seconds, from 1 to 60. The default is 10 seconds.

Default

Disabled

Command Mode

ATM router PNNI configuration

Usage Guidelines

The ATM switch router supports the following two route selection modes:

  • On-demand (no background-routes)—Separate route computation is performed for each SETUP or ADD PARTY message received over a UNI or IISP interface. In this mode, the most recent topology information received by this node is always used for each setup request.
  • Background-routes—Most calls are routed using precomputed routing trees. In this mode, multiple background trees are precomputed for several service categories and QoS metrics. If no route is found in the background trees that satisfies the QoS requirements of a particular setup request, route selection reverts to on-demand route computation.

The background-routes mode should be enabled in large networks, where it could exhibit less stringent processing requirements and better scalability.

The poll-interval is used to throttle background route computation. Route computation is performed at most every poll-interval seconds, when a significant change in the topology of the network is reported, or when a specified insignificant-threshold number of changes has occurred since the last route computation.

Caution

Decreasing the poll-interval increases the load on the switch processor.

For more information, refer to the Catalyst 8540 MSR ATM Switch Configuration Guide.

Example

The following example shows how to enable background routes with a poll-interval of 15 seconds using the background-routes-enable ATM router PNNI configuration command.

Switch# configure terminal
Switch(config)# atm router pnni
Switch(config-atm-router)# background-routes-enable poll-interval 15
Related Commands

show atm pnni background routes
show atm pnni background status

bandwidth

Note      This command or some of its parameters may not function as expected in the ATM switch router environment.

boot config

To specify the device and filename of the configuration file from which the switch configures itself during initialization, use the boot config global configuration command. To remove this specification, use the no form of the command.

boot config device:filename
no boot config
Syntax Description

device:

Device containing the configuration file. The colon (:) is required. Valid devices are as follows:

  • bootflash: This device is the internal Flash memory.
  • slot0: This device is the PCMCIA slot route processor card.
  • slot1: This device is the second PCMCIA slot on the route processor card.

filename

Name of the configuration file. The configuration file must be an ASCII file. The maximum filename length is 63 characters.

Default

No device and filename is specified.

Command Mode

Global configuration

Usage Guidelines

You set the config_file environment variable in the current running memory when you use the boot config command. This variable specifies the configuration file used for initialization.

Note      When you use this global configuration command, you affect only the running configuration. You must save the environment variable setting to your startup configuration to place the information under ROM monitor control and to have the environment variable function as expected. Use the copy running-config command to save the environment variable from your running configuration to your startup configuration.

boot system

To specify the system image that the switch loads at startup, use one of the following boot system global configuration commands. To remove the startup system image specification, use the no form of this command.

boot system {[device:] filename [hostname] | flash [device:] [filename] |
 mop filename [if-type] [card/subcard/port] | rcp filename [ip-address] |
 rom | tftp [hostname]}
no boot system {[device:] filename [hostname] | flash [[device:] filename] |
 mop filename [if-type] [card/subcard/port] | rcp filename [ip-address] |
 rom | tftp [hostname]}
Syntax Description

device

Device containing the system image to load at startup. A colon (:) is required as part of the device specification. Valid devices are as follows:

  • bootflash: This device is the internal flash memory.
  • slot0: This device is the first PCMCIA slot on the route processor card.
  • slot1: This device is the second PCMCIA slot on the route processor card.

filename

Name of the system image to load at startup. The filename is case sensitive. If you do not specify a filename for flash, the switch loads the first valid file in the specified Flash device, the specified partition of Flash memory, or the default Flash device (if you omit the device: argument).

hostname

Name or IP address of the host that stores the system image.

flash

Boots the switch from internal Flash memory. If you omit all arguments that follow this keyword, the system searches internal Flash for the first bootable image.

This keyword boots the switch from a Flash device, as specified by the device argument. When you omit all arguments that follow this keyword, this system searches the PCMCIA slot 0 for the first bootable image.

mop

Boots the switch from a DecNet MOP server.

if-type

Interface type, specified as atm, atm-p, cbr, ethernet, null, or the MAC layer address of the host to boot from.

card/subcard/port

Interface identifier for the specified interface type.

rcp

Boots the switch from a system image stored on a network server using rcp. If you omit this keyword, the transport mechanism defaults to tftp.

ip-address

IP address of the TFTP server containing the system image file. If omitted, this value defaults to the IP broadcast address of 255.255.255.255.

rom

Boots the switch from the system image stored in ROM.

tftp

Boots the switch from a system image stored on a TFTP server. This is the default when you do not specify any keyword (flash, tftp, or rcp).

Default

If you do not specify a system image file with the boot system command, the switch uses the configuration register settings to determine the default system image filename for booting from a network server. The switch forms the default boot filename by starting with the word cisco and then appending the octal equivalent of the boot field number in the configuration register, followed by a hyphen (-) and the processor type name (cisconn-cpu). See the appropriate hardware installation guide for details on the configuration register and default filename. See also the command config-register. See also the "Syntax Description" section.

If you omit a keyword (flash, rcp, or tftp) from the boot system command, the system defaults to booting from a system image stored on a TFTP server.

Command Mode

Global configuration

Usage Guidelines

For this command to work, the config-register command must be set properly.

Enter several boot system commands to provide a fail-safe method for booting your switch. The switch stores and executes the boot system commands in the order in which you enter them in the configuration file. If you enter multiple boot commands of the same type—for example, if you enter two commands that instruct the switch to boot from different network servers—then the switch tries them in the order in which they appear in the configuration file.

Each time you write a new software image to Flash memory, you must delete the existing filename in the configuration file with the no boot system filename command. Then add a new line in the configuration file with the boot system filename command.

Note      The no boot system global configuration command disables all boot system configuration commands regardless of argument. Specifying the flash device name or the filename argument with the no boot system command disables only the command specified by these arguments.

You can boot the switch from a compressed image on a network server. When a network server boots software, both the image being booted and the running image must fit into memory. Use compressed images to ensure that enough memory is available to boot the switch. You can compress a software image on any UNIX platform using the compress command. Refer to your UNIX platform's documentation for the exact usage of the compress command. (You can also decompress data with the UNIX uncompress command.)

The rcp protocol requires that a client send the remote username in an rcp request to a server. When the switch executes the boot system rcp command, by default the switch software sends the switch host name as both the remote and local usernames. The rcp software searches for the system image to boot from the remote server relative to the directory of the remote username (if the server has a directory structure as UNIX systems do, for example).

The boot system command modifies the BOOT environment variable in the running configuration. The BOOT environment variable specifies a list of bootable images on various devices.