System Administration

Use the steps described in this chapter to:

• Configure global ARP retries and timeouts
  
  
• Name your system
  
  
• Set the time
  
  
• Configure access control
  
  
• Configure an SNTP server
  
  
• Configure server location
  
  
• Define and configure bays, bay controllers, servers, and router modules
  
  
• Determine the slots where new modules should be installed
  
  
• Remove or replace router modules
  
  
• Configure crashdump behavior
  
  
• Configure global ARP retries and timeouts
  
  
• Display users logged on to the Avici router, bays, servers, router modules, and other system information
  
  

Configuration File Requirements

The first command in a configuration file must be server-id.

If this line is not the first line in a configuration file, a large error banner is displayed and the system will not create the necessary internal interfaces to communicate with the module(s) and bay controller.

A module is defined when you issue the module command. Interface definitions do not take effect unless there is a module already defined containing the corresponding interfaces. Refer to "IPriori Configuration File Organization," in Chapter 1 for more details of configuration file organization and command dependencies.

There are default values for all of the Boot ROM parameters and logging parameters on the bay controller, module, and server. Therefore they need not be defined in the configuration file unless values other than the default are used. However, it is a good idea to define the bootrom and logging parameters for each of the elements in the configuration file to document which bootrom parameters you are actually using even if they are the defaults. Refer to "Updating System Image Files," in Chapter 2 for more information on loading flash memory and setting boot parameters. Refer to Chapter 11 for more details on logging configuration.

Setting the Avici router Host Name

The hostname command identifies the router in output from show commands as well as in the command prompt. If the host name is not set, IPriori uses router as the host name.

Use the hostname command to define the Avici router name.

In the following example, the hostname command changes the router name from the default to cincinnati:

router#config terminal Enter configuration commands, one per line. End with CNTL/Z. router(config)#hostname cincinnati cincinatti(config)#

Setting Time-of-Day

The Avici router server uses an internal clock to mark the time of day. The clock is set at the factory to Eastern Standard Time.

PROCEDURE: Use the following steps for setting time-of-day:

Step 1 Use the clock set command to set the current day, date, and time.

In the following example, the clock set command sets the Avici router clock to 10:05 am on June 7th, 2000, and the show clock command displays the new setting:

router#clock set 10:05:00 7 june 2000 router#show clock 10:05:01.100 Wed Jun 7 2000

The clock time zone denotes the time zone in which you are operating and (optionally) the number of hours relative to Greenwich Mean Time (GMT).

Step 2 Use the clock timezone command to set the time zone to Eastern Daylight Time (EDT).

In the following example, the clock timezone command sets the time zone to EDT, and the show clock command displays the new setting:

router#config terminal Enter configuration commands, one per line. End with CNTL/Z. router(config)#clock timezone edt router (config)#end router#show clock 16:12:16.106 edt Wed Jun 7 2000

Adding User Names

Use the username command to define the names of all users who are allowed access to the Avici router.

You can optionally specify whether the password is encrypted (7) or not (0).

WARNING Never use the "7" option when entering a system password or enable password by hand, unless you are copying verbatim a password that has already been encrypted.

NOTE Even passwords entered into the start up configuration file in clear text will be stored on the running configuration file in encrypted format.

You must enter both a name and password to establish a new user. You can optionally specify whether the password is encrypted (7) or not (0).

In the following example, the username commands create new users, and the show running-config command displays all the configured names:

router#configure terminal Enter configuration commands, one per line. End with CNTL/Z. router(config)#username NOCuser1 0 password ATM1159 router(config)#username NOCuser2 0 password RFCxyz router(config)#username NOCuser3 0 password curtis router(config)#username engineer47 0 password astro router(config)#end router#show running-config . . . ! user admin password 7 S9bQQdb9Sd user NOCuser1 password 7 bbdbed9bzS user NOCuser2 password 7 Sd9S9yRyyc user NOCuser3 password 7 cdrS9yAyNc user engineer47 password 7 SecbyzzyQS !

Configuring an SNTP Server

Simple Network Time Protocol (SNTP) is used to synchronize computer clocks in the Internet.

Use the sntp server command to configure SNTP to request Network Time Protocol (NTP) packets from an NTP server. The SNTP server defined by this command becomes the clock synchronization source.

In the following example:

• The sntp server command identifies a system as an SNTP server.
  
  
• The show sntp command displays the configuration:
  
  

router#configure terminal Enter configuration commands, one per line. End with CNTL/Z. router(config)#sntp server 171.69.118.9 router(config)#end router#show sntp SNTP server Stratum Version Last Receive 171.69.118.9 5 3 00:01:02 Synced

Configuring Access Control

The Avici router supports two levels of access control:

• System access - All access to the Avici router is controlled by use of an optional configurable password.
  
  
• Privileged access - A subset of commands are restricted to use by those who know an additional password.
  
  

About Password Encryption

NOTE Passwords entered into the start up configuration file in clear text will be stored on the running configuration file in encrypted format.

Passwords are encrypted to:

• Protect passwords in the running configuration file from detection by unauthorized personnel.
  
  
• Enable the copying of passwords from one configuration file to another without prior knowledge of the password.
  
  

Passwords are stored in the running configuration file in encrypted mode to ensure security. Therefore, the password "tickle" would look as follows in the running configuration file:

system-password 7 Sb9QSxeRee

If you configure the password using the 0 option (no encryption), the password "tickle" would look as follows in the running configuration file:

system-password 7 Sb9QSxeRee

Configuring System Access

Use the system-password command to configure a system password. All users are prompted for this password when they log on to the Avici router.

In the following example:

• The enable command changes the command mode to privileged. The system prompts for the enable password.
  
  
• The system-password command configures the system password as bigrouter:
  
  

router>enable password: router#configure terminal Enter configuration commands, one per line. End with CNTL/Z. router(config)#system-password bigrouter router(config)#end router#

Configuring Privileged Access

Access to the privileged mode Command Line Interface (CLI) for configuring the Avici router is restricted to trusted users. Any user who uses the enable command to enter privileged command mode is prompted for the enable password. Only users who know this password can access the privileged command mode on the Avici router.

Use the enable password command to configure the enable password for the Avici router.

In the following example:

• The first enable command changes the command mode to Privileged. The user is prompted to provide a password.
  
  
• The enable password command changes the password to a new password: tickle.
  
  
• The disable command exits Privileged command mode.
  
  
• The second enable command changes the command mode to Privileged. The user is prompted to provide the new password:
  
  

router>enable password:avici router#configure terminal Enter configuration commands, one per line. End with CNTL/Z. router(config)#enable password 7 tick1e router(config)#end router#disable router>enable password:tick1e router#

Package Files

Package files are a convenient method of packaging compatible operational, FPGA, POST, and boot ROM images for routing modules. You can have multiple package files in the your directory, but only the default package file is used for automatic upgrading of routing modules.

When a routing module with incompatible software is detected, and automatic upgrades are enabled, the module is automatically upgraded using the contents of the default package file.

Use the package-file filename.pkg command to set the default package file for the system to the specified package file.

Alternatively, you can manually download portions of a package file to a specified routing module or all routing modules:

• Use the boot package-file [1 | 2] command to download only the operational image from the specified package file to a specified module or all modules.
  
  
• Use the reboot package-file [1 | 2] command to download only the operational image from the specified package file to a specified module, and restart the module.
  
  
• Use the fpga download package-file [1 | 2] command to download a selected FPGA image to a specified module or all modules that contain the specified FPGA.
  
  

Configuring Automatic Upgrade

When auto-upgrade is enabled and an incompatible operational, FPGA, POST or boot ROM image is detected on a routing module, the image is automatically upgraded from the files contained in the system's default package file.

NOTE By default, automatic upgrading is enabled at the global and per-module level and is not displayed in the output of show running-config.

NOTE If auto-upgrade is globally disabled, it can not be enabled on a module.

If automatic upgrading has been disabled, use the following steps to re-enable it:

Step 1 Verify (show running-config system) that a default package file has been configured.

Step 2 If no package file has been configured, use the package-file filename.pkg command to set the default package file for the system.

Step 3 Use the auto-upgrade command in Configuration command mode to globally enable automatic upgrades of routing modules using the contents of the default package file.

Step 4 Use the auto-upgrade command in Module configuration command mode to enable automatic upgrades on the specified module.

or:

Use the auto-upgrade command in Module-all configuration command mode to enable automatic upgrades on all modules.

Example: In the following example, automatic upgrading is re-enabled, both globally and for all routing modules.

• The package-file filename.pkg command sets the specified package file as the default package file for the system.
  
  
• The show running-config system command displays the setting.
  
  
• The auto-upgrade command in Configuration command mode globally enables automatic upgrades.
  
  
• The module all command specifies all modules and changes the command mode to Module-all configuration.
  
  
• The auto-upgrade command enables automatic upgrading of incompatible operational, FPGA, POST, and boot ROM images on all modules.
  
  

router#configure terminal Enter configuration commands, one per line. End with CNTL/Z. router(config)#package-file R0401450.PKG router(config)#end router#show running-config system . . ! package-file A:\R0401450.PKG ! . .

router#configure terminal Enter configuration commands, one per line. End with CNTL/Z. router(config)#auto-upgrade router(config)#module all router(config-module-all)#auto-upgrade router(config-module-all)#end

The Avici router Bay

The Avici router is available in the following configurations:

• Split bay configuration
  
  
• Full bay configuration
  
  
• Multi-bay configurations
  
  

Avici router Split Bay

The Avici router split bay configuration splits a four shelf Avici router into an upper logical router and a lower logical router. These two routers each contain two shelves, each with 10 slots, providing the capability of installing a server and a minimum of four router modules.

The two backplanes providing interconnection between router modules are disconnected creating two physically separate logical routers. These two logical routers do not communicate with each other across the fabric.

The following figure shows a split bay configuration:

Figure 3-1. Avici router Split Bay Configuration

Avici router Full Bay

The Avici router full bay configuration consists of a hardware bay with:

• Four shelves, with ten slots each
  
  
• One or two server modules
  
  
• Two bay controller modules
  
  
• Up to 38 routing modules
  
  

The following figure shows a full bay Avici router:

Figure 3-2. Full Bay Configuration

Multi-Bay Configuration

There are two multi-bay configurations:

• 2-bay configurations
  
  
• 4-bay configuration (bays are arranged in a 2 x 2 cube)
  
  

A fully configured 4 bay configuration supports up to 82 routing modules.

The following figure shows a 2-bay configuration:

Figure 3-3. 2-Bay Configuration

Servers, Bay Controllers and Router Modules

This section describes the Avici router servers, bay controllers and router modules.

Server Modules

The server modules:

• Compute path selection based on your network design criteria
  
  
• Provide convergence in the event of a link failure
  
  
• Compute forwarding tables based on configured route policies and route filtering
  
  

The server modules also communicate with bay controllers, download router tables to attached router modules, and monitor the state of router modules and bay controllers.

Bay Controller Modules

The bay controller monitors system temperature, power, and servers. The bay controller also issues alarms from a connection located at the top of the Avici router bay.

Router Modules

The Avici router supports combinations of Gigabit Ethernet, OC-3c, OC-12c, OC-48c, and OC-192c router modules in a single backplane.

Table 3-1. Module Type and Description

Module Type	Description
4xOC-12c	4-port OC-12c module
4xOC-3c	4-port OC-3c module
1xOC-48c	1-port OC-48c module
1xoc48c-mux	1 port OC48c (mux) module
2xOC-48c	2-port OC-48c module
2x1gbe	2 port Gigabit Ethernet module
1xOC-192c-a	1 port OC192C module (1 of 2 module set)
1xOC-192c-b	1 port OC192C module (2 of 2 module set)

Configuration Command Modes

There are separate configuration modes for the server, bay controller and router modules. Each configuration mode provides the ability to:

• Set boot parameters
  
  
• Set logging parameters
  
  

Server Configuration Mode

Use the server command to enter server configuration command mode.

Valid values for the server-id are integers 1 - 32.

The following commands are supported in server configuration command mode:

Table 3-2. Commands Available in Server Configuration Command Mode  

Command	Description
exit	Exit from server mode.
help	Description of the interactive help system.
logging-max-history max_files	Change the maximum number of log files that are created on the permanent storage for the current system. A number will form the extension to the stored file name and be numbered from 0 to max_file -1. Default is 5. Allowed range is 1 to 100.
logging-filter system level	Specify that the hardware entity does not generate events for the specified system at or below the specified level. Note that critical errors are always generated regardless of filtering. Multiple logging filter statements can be given. Default is to log all level errors (and above) for all systems.
no	Negate a command or set a value to its default.

Bay Controller Configuration Mode

Use the bay command to enter bay controller configuration command mode.

The following commands are available in bay controller command mode:

Table 3-3. Commands Available in Bay Controller Command Mode  

Command	Description
exit	Exit from the mode back to configuration mode.
boot file [flags flag {1|2}]	Modify boot parameters for this bay controller. Each bay controller contains two flash memory locations; Location 1 and location 2. Each flash location can be loaded with a separate boot image for the bay controller. The command without the optional file, sets the default image from which to boot. With the optional file, it burns the file into the selected flash memory location. If no file location is specified, the new file overwrites the older image. The flags parameter is used to set the boot flags to be used when the system is restarted. To add new boot flags to the existing boot flag, perform a logical "OR" on the existing boot flag and the new setting.
help	Description of the interactive help system.
logging-max-history max_files	Change the maximum number of log files that are created on the permanent storage for the current system.
logging-filter system level	Specify that the hardware entity does not generate events for the specified system at or below the specified level. Note that critical errors are always generated regardless of filtering.
post-burn filename	Burn POST on individual or all bay controller(s).
reboot [flags flag {1|2} | file]	Modify boot parameters and reboot all bay controllers.
rom-burn filename	Burn ROM on individual servers.

Module Configuration Mode

Use the module command to enter router module configuration command mode.

Within module mode, the following commands are available:

Table 3-4. Commands in Module Configuration Command Mode  

Command	Description
auto-upgrade	Enable Auto Upgrade of images for the module.
boot [flags flag {1|2} | file | package-file]	Modify boot parameters for this module. Specify an image file or package file to be used at the next module start.
exit	Exit from module mode
fabric link down-event	Configure the amount of down events allowed for this link.
fabric link time-window	Configure the time window to allow the down events to occur in.
fpga activebank	Sets the memory bank from which the FPGA is loaded during the next module boot/reboot.
fpga download	Download an FPGA image to the modules from a file or package file.
help	Description of the interactive help system
logging-filter system level	Specify that the hardware entity does not generate events for the specified system at or below the specified level. Note that critical errors are always generated regardless of filtering. Multiple logging filter statements can be given. Default is to log all levels including and above warning for all systems.
logging-max-history max_files	Change the maximum number of log files that are created on the permanent storage for the current system. A number will form the extension to the stored file name and be numbered from 0 to max_file -1. Default is 5. Allowed range is 1 to 100.
post-burn [filename | package-file]	Burn a POST image from a file or package file onto a specified module or all modules.
reboot [filename | package-file][1 | 2]	Specify the file or package file, and the memory bank to be used when the system starts and restart the system.
rom-burn filename	Burn a boot ROM image from a file or package file onto a specified module or all modules.
shutdown	Disable/enable a module (or module subsystem).

Module-all Configuration Mode

Use the module all command to change the command mode to Module-all command mode. Command issued in Module-all command mode configure all routing configured routing module in the Avici router.

NOTE The reboot command is not available in Module-all command mode.

Configuring the Avici router Server

Use the steps described in this section to:

• Define the server ID
  
  
• Configuring a Warm Server
  
  
• Configure the number of logging files
  
  

Configuring the Server-ID

The server ID is an identifier used for communication inside the Avici router. Servers in the same Avici router bay must not have the same server ID.

CAUTION server-id must be the first command to appear in the configuration file. No Avici router interfaces will come up until the server ID is configured. If you configure a Avici router interface without first configuring the server ID, the interface will display (show interface) as not configured.

Use the server-id command to set the ID for the server.

In the following example:

• The server-id 2 command configures the server ID as 2.
  
  
• The show server command displays the configuration:
  
  

router#configure terminal Enter configuration commands, one per line. End with CNTL/Z. router(config)#server-id 2 router#show server Server ID 2 Server: lower-full - Controls slots 21 - 40 Current Server Access Module: 1/37, on Eth1 Software version: Platform: 4cs-d; Label: BU_BL8, built Dec 16 1999, 21:54:54 Last started on TUE DEC 28 13:03:44 1999 Max number of historical logging files: 5

Configuring the Server ID for a Avici router Split Bay

When specifying a server ID in a split bay configuration, each server is uniquely identified by both a number and the upper and lower keywords.

Some rules to consider when configuring split bay:

• Servers must reside in slots 11 and 31.
  
  
• The server IDs must be unique within a bay.
  
  
• Slot numbering for a full bay and for split bay are the same. Specifically, the top left-most slot is number 1. Slot numbers increase from left to right and from top shelf to bottom shelf. Therefore, the upper server supports slot numbers 1 through 10 and 12 through 20. The lower server supports slots 21 through 30 and 32 through 40.
  
  

In the following example:

• The server-id 1 ? command displays the options for configuring a server ID.
  
  
• The server-id 1 upper command configures the server as part of the upper router on a Avici router split bay.
  
  
• The show server command displays the configuration:
  
  

router#configure terminal Enter configuration commands, one per line. End with CNTL/Z. router(config)#server-id 1 ? full entire bay (all 4 shelves) lower lower 1/2 of split bay (shelves 3 & 4) upper upper 1/2 of split bay (shelves 1 & 2) router(config)#server-id 1 upper router#show server

Server ID 1 Server: upper - Controls slots 1 - 20 Location (bay/slot): 1/11 Current Server Access Module: 1/5, on Eth2 Backup Server Access Module: 1/15, on Eth1 Warm Stand-by State: ACTIVE Warm Stand-by Partner id: NONE IPriori release version: 4.1.54.0   Operational image version: Platform: 4cs-d; Label: R4.1_REL.54, built Oct 20 2001, 17:37:06 ROM Version: IPriori Bootrom Release 5.10 built Oct 11 2001, 19:30:42 . . .

Configuring a Warm-Standby Server

The Avici router supports a warm-standby (secondary) server that becomes the active server in the event that the primary server becomes inoperative. The warm-standby server is the second server installed in a Avici router full bay configuration. If warm-standby is disabled, the system will only support a single server.

The startup config is parsed twice during system initialization. The first parse happens before the server has any state information, and processes server-specific information (e.g. server-id, domain, location, eth0 address). The second parse happens only after the server has assumed a status of "active" and processes non-server specific commands.

The warm-standby server in secondary mode has limited functionality and supports a limited CLI command set; its primary function is to mirror the configuration of the primary server and monitor its status. Should the secondary server become active because of a failure of the primary server, it must relearn all configuration information (e.g., tunnels, routers etc.) based on the startup.cfg.

The CLI is not active until the server has assumed a final state: Active, Backup, or Inactive.

The startup configuration file resident on the active server is copied to the backup server only upon initial partnership of the backup/active servers and when the write command is used.

The warm-standby command enables users to enable/disable warm standby functionality. Warm-standby is enabled by default.

NOTE When a backup server is not installed, and warm-standby is enabled, the time during initialization when the CLI is not active is extended by 1 minute. When only one server is present, you can disable warm-standby and reduce the time for system initialization to complete, with the no warm-standby command.

Use the show server command to display warm-standby status.

WARNING The warm-standby and no warm-standby commands do not take effect until the configuration file has been saved (using the write command), and the server is re-booted.

If warm server functionality has been disabled, the installation of a second server is not supported.

Example: In the following example:

• The warm-standby command enables the secondary server functionality:
  
  
• The write command saves the changes in the running configuration file to the startup configuration file.
  
  
• The reboot command restarts the server using the updated configuration file.
  
  
• The show server command displays the setting:
  
  

router(config)#warm-standby WARNING: - Changes to warm-standby require a write and reboot to take effect! router(config)#end router#write router#reboot . . . Avici Systems TSR Copyright 1997-2000 Avici Systems, Inc. CPU:VI Computer POWER4C PPC 604E 300 MHZ/MPC106v40 OS:IPriori, Beta Version BSP version:1.1 /2 Creation date:Jan 29 2001, 18:57:19 Build name:Platform:4cs-d; Label:R3.3_REL.21 Debug:No Support Loading server-specific info from startup configuration... Server specific info has been loaded from A:\STARTUP.CFG. Determining Server State.........Done Server state is:ACTIVE. Loading non-server specific info from startup configuration... Non-server specific info has been loaded from A:\STARTUP.CFG. Password: . . . router#show server Server ID 1 Server: upper - Controls slots 1 - 20 Location (bay/slot): 1/11 Current Server Access Module: 1/5, on Eth2 Backup Server Access Module: 1/15, on Eth1 Warm Stand-by State: ACTIVE Warm Stand-by Partner id: NONE IPriori release version: 4.1.54.0   Operational image version: Platform: 4cs-d; Label: R4.1_REL.54, built Oct 20 2001, 17:37:06 ROM Version: IPriori Bootrom Release 5.10 built Oct 11 2001, 19:30:42 . . . Max number of historical logging files:5

Configuring Server Thresholds

Thresholds for CPU usage and memory availability may be configured on servers. These thresholds allow an SNMP trap to generate if CPU usage or memory available exceeds the value point set in the threshold. In addition, the frequency at which the thresholds are checked may also be set.

CPU usage is measured in percentages. When CPU usage rises above the rising threshold percentage point, a trap generates. When the CPU usage falls below the falling threshold percentage point, the trap clears and resets. Monitoring of threshold value points is done by using the interval keyword. Refer to Table 3-5 "Server Threshold Defaults & Value Ranges" for default and threshold value ranges.

One or all of the keywords may be used to set the threshold values.

Table 3-5. Server Threshold Defaults & Value Ranges

Default Threshold Values	Threshold Value Range
CPU usage: Rising: 95%, Falling 93%	75% to 100%
Memory: Rising: 7MB, Falling 5MB	0 to 100 MB
Interval: 15 seconds	5 to 40 seconds

PROCEDURE: Use the following steps to configure the CPU usage threshold and interval:

Step 1 Use the server 1 command in configuration mode to identify the server.

Step 2 Use the CPU threshold {falling | rising | interval} command to set the threshold value points.

Step 3 Use the end command to exit server configuration mode.

Step 4 Use the show rmon alarms command to view the configured settings.

Example: In the following example:

• The server 1 command identifies the server. This value must match the value in the running configuration.
  
  
• The CPU threshold falling 85 rising 93 interval 10 command sets the threshold value points.
  
  
• The end command returns user to configuration mode.
  
  
• The show rmon alarms command displays the information regarding the configuration.
  
  

router(config)#server 1 router(config-server): CPU threshold falling 85 rising 93 interval 10 router(config-server): end router# show rmon alarms router# Alarm 65536 is active, owned by jason Monitors aviciCPUTotal5sec.196609 every 15 seconds Taking absolute samples, last value was 5 Rising threshold is 93, assigned to event 65536 Falling threshold is 85, assigned to event 65537 Interval is 10, assigned to 65538 On startup enable rising alarm Alarm 65537 is active, owned by config

PROCEDURE: Use the following steps to configure the CPU usage threshold and interval:

Step 5 Use the server 1 command in configuration mode to identify the server.

Step 6 Use the memory threshold falling rising interval command to set the threshold value points.

Step 7 Use the end command to exit server configuration mode.

Step 8 Use the show rmon alarms command to view the configured settings.

Example: In the following example:

• The server 1 command identifies the server.
  
  
• The memory threshold falling 7 rising 10 interval 30 command sets the threshold value points.
  
  
• The end command returns user to configuration mode.
  
  
• The show rmon alarms command displays the configuration settings.
  
  

router(config)#server 1 router(config-server): memory threshold falling 7 rising 10 interval 30 router(config-server): end router# show rmon alarms router# Alarm 65536 is active, owned by jason Monitors aviciPlatformMemoryFree.196609 every 15 seconds Taking absolute samples, last value was 521547720 Rising threshold is 10, assigned to event 65539 Falling threshold is 7, assigned to event 65540 Interval is 30, assigned to 65541 On startup enable falling alarm

Configuring Server Logging

PROCEDURE: Use the following steps to configure logging for the server:

Step 1 Use the server 1 command to change the command mode to server configuration command mode.

Step 2 Use the logging-filter command to configure message filtering by severity level.

Step 3 Use the logging-max-history command to configure the number of stored log files.

In the following example:

• The server 1 command specifies the server to be configured and changes the command mode to server configuration.
  
  
• The logging-filter command sets filtering for server 1 to discard all Border Gateway Protocol (BGP) system event messages at severity levels warning and below.
  
  
• The logging-max-history command sets the maximum number of log files on server 1 to 3:
  
  

router#configure terminal Enter configuration commands, one per line. End with CNTL/Z. router(config)#server 1 router(config-server)#logging-filter bgp-events warning router(config-server)#logging-max-history 3

Configuring Server Location

Servers must be installed in the following slots:

In a full bay configuration:

• Servers are restricted to slots 11 and 20. When only one server is installed, it must be in slot 11.
  
  

In a split bay configuration:

• Upper Logical Router - the server module is restricted to slot 11.
  
  
• Lower Logical Router - the server module is restricted to slot 31.
  
  

PROCEDURE: Use the following steps to add descriptive text to the running configuration file and the output of the show server command specifying the slot in which the server is installed:

NOTE The information created by the server-location command is for display only. If you enter the server location for a full bay configuration incorrectly, this mis-information is accepted and displayed by the show running-config and show server commands.

Step 1 Use the server command to specify the server, and to change the command mode to Server Configuration Mode.

Step 2 Use the server-location command to specify the slot in which the server is installed:

outer#configure terminal Enter configuration commands, one per line. End with CNTL/Z. router(config)#server-location 1/11 router(server-location)#end router#show server Server ID 1 Server: upper - Controls slots 1 - 20 Location (bay/slot):1/11

Current Server Access Module: 1/17, on Eth1 Software version: Platform: 4cs-d; Label: BU_BL8, built Dec 16 1999, 21:54:54 Last started on TUE DEC 28 13:03:44 1999 Max number of historical logging files: 5 Immediate logging is on Non-default logging filters: os minor bgp information

Configuring a Banner

Use the banner command to configure a unique warning banner which displays at system start-up and when new users log in. Banners may contain up to 70 characters of text per line and up to 50 lines of text. Banner warnings may include a company name, address, pertinent warnings, and descriptions. The show banner command displays the banner.

Example 1: The following example shows a banner configuration:

• The config terminal command puts the system into configuration mode.
  
  
• The banner lines 3 sets the lines of the banner at 3.
  
  
• User enters the banner text number command to enter the text for each line of the banner. Use the banner text number  and hit enter to enter a blank line in the banner. User completes this process for each line of text.
  
  
• The end command exits configuration mode.
  
  
• The show banner command displays the newly created banner. The show banner command can be used to view the banner for possible editing.
  
  

router#config terminal

Enter configuration commands, on per line. End with CNTL/Z.

router(config)banner ?

lines   Configure the number of lines of text in the banner (1-50)

text    Enter the text on a particular line

router(config)banner lines 3

router(config)banner text 1 Avici Systems, Inc.

router(config)banner text 2 101 Billerica Avenue

router(config)banner text 3 Billerica, MA 01862

router(config)end

router#show banner

router#Line Text 1 * Avici Systems, Inc. * 2 * 101 Billerica Avenue * 3 * Billerica, MA 01982 * 4 * * 5 * *

Example 2: The following example shows editing of a banner configuration:

• The config terminal command puts the system into configuration mode.
  
  
• User enters the banner text number command to enter the text for the line number of the banner to edit. User completes this process for each line of text to be edited.
  
  
• The end command exits configuration mode.
  
  
• The show banner command displays the newly created banner.
  
  

router#config terminal

Enter configuration commands, on per line. End with CNTL/Z.

router(config)banner ?

lines   Configure the number of lines of text in the banner (1-50)

text    Enter the text on a particular line

router(config)banner lines 3

router(config)banner text 1 Avici Systems, Inc.

router(config)banner text 2 101 Billerica Avenue

router(config)banner text 3 Billerica, MA 01862

router(config)end

router#show banner

router#Line Text 1 * Avici Systems, Inc. * 2 * 101 Billerica Avenue * 3 * Billerica, Massachusetts 01862  4*  5*

Configuring the Bay Controller

The Avici router has two bay controllers per chassis. One bay controller operates in passive mode, the other in active mode. The selection of which bay controller is active is done automatically, and you can not configure this attribute.

Bay controllers are identified by the following commands:

bay 1/1	Specifies the bay controller installed on the left side of the bay.
bay 1/2	Specifies the bay controller installed on the right side of the bay.

Configure Bay Controller Logging

PROCEDURE: Use the following steps to configure logging for the two bay controllers:

Step 1 Use the bay 1/1 command to identify the left bay controller and change the command mode to bay controller configuration command mode.

Step 2 Use the logging-filter command to configure message filtering by severity level.

Step 3 Use the logging-max-history command to configure the number of stored log files.

Step 4 Repeat steps 1 - 3 using the bay 1/2 command to configure logging for the right bay controller.

In the following example:

• The bay 1/1 command specifies the left bay controller and changes the command mode to bay controller configuration.
  
  
• The logging-filter command sets filtering for the left bay controller to discard all BGP system messages at severity levels warning and below.
  
  
• The logging-max-history command sets the maximum number of log files on the left bay controller to 3:
  
  

router#configure terminal Enter configuration commands, one per line. End with CNTL/Z. router(config)bay 1/1 router(config-bay)#logging-filter bgp warning router(config-bay)#logging-max-history 3

Configuring Router Modules

Use the steps described in this section to:

• Determine which slot new modules should be installed
  
  
• Identify the type of module installed in a specific slot.
  
  
• Activate the module using the no shutdown command.
  
  

Determining Slots for New Modules

The Avici router fabric consists of a passive backplane and an active routing mechanism on the routing modules. It is crucial that routing modules be installed into the Avici router bay in pairs, using the Avici module population rules.

Use the show population command to display where new modules should be inserted into the Avici router.

Unmatched slots (modules not inserted in pairs) already installed in the Avici router are noted with the following error message:

Incorrect module placement detected at slot nn.

The following example shows where a new module pair should be inserted in the top half of a Avici router 2+2 bay:

router#show population Incorrect module placement detected at slot 17. New Module Placement Bay 1: 1 2 3 4 5 6 7 8 9 10 =========================== Shelf 1 || E N E I I | I I I N E || --------------------------- Shelf 2 || S I E E I | I I I I E || =========================== (E=Empty, I=Identified, N=New Module Location, O=Occupied, S=Server, U=Unknown)

The new module pair must be inserted into slots 2 and 9.

Identifying Type of Module

The Avici router supports the following types of router modules:

Table 3-6. Router Module Types and Speeds  

Module Type	Description	Transmission Rate per Port	Available Bandwidth per Port
4xOC-3c	4 port OC-3c module	155 Mb/sec	150 Mb/sec
16xOC-3c	16 port OC-3c module	155 Mb/sec	150 Mb/sec
4xOC-12c	4 port OC-12c module	622 Mb/sec	601.34 Mb/sec
1xOC-48c	1 port OC-48c module	2488 Mb/sec	2405.38 Mb/sec
1xOC-48c-mux	1 port OC-48c mux module	2488 Mb/sec	2405.38 Mb/sec
2xOC-48c	2 port OC-48c module	2488 Mb/set	2405.38 Mb/sec
1xOC-192c	1 port, dual slot OC-192c module	9958 Mb/sec	9620 Mb/sec
2x1gbe	2 port Gigabit Ethernet module	1000 Mb/sec	1000 Mb/sec

Use the show modules brief command to display the type of module installed in each slot.

router#show modules brief Module Discovered Configured Starts Last Started Status    1/4 2x1GbE 2x1GbE 1 TUE MAY 29 12:27:11 2001 Up 1/5 2x1GbE 2x1GbE 1 TUE MAY 29 12:27:11 2001 Up 1/6 2x1GbE 2x1GbE 1 TUE MAY 29 12:27:11 2001 Up 1/7 4xOC3c 4xOC3c 1 TUE MAY 29 12:27:12 2001 Up 1/8 4xOC12c 4xOC12c 1 TUE MAY 29 12:27:12 2001 Up S 1/15 4xOC12c 4xOC12c 1 TUE MAY 29 12:27:03 2001 Up 1/16 1xOC48c 1xOC48c 1 TUE MAY 29 12:27:12 2001 Up 1/17 1xOC48c 2xOC48c 0 never Misconfigured 1/18 None 1xOC48c 0 never  Unknown   1/25     1xOC48c       0                                 never IncompatibleSW Module 1/25 requires a software upgrade to Release 4.0.1 image.   1/26      1xOC48c      4xOC3c 0                    n