| |
|
|
IPrioriTM includes an industry standard Command-Line Interface (CLI). The commands are grouped into commands modes. When a user logs in to IPriori they are in Executive mode.
Moving Between Command Modes
To modify the system configuration, use the enable command to enter Privileged mode:
Figure 1-1. Enable Command
Use the exit command to move up one level in command modes:
Figure 1-2. The Exit Command
Use the end command to Privileged command mode from any command mode:
Figure 1-3. The End Command
Use the ? to display the available commands in each command mode. For example:
router(config)#router bgp 1
router(config-router)#bgp ?
always-compare-med Allow comparing MED from different neighbors
client-to-client Configure client to client route reflection
cluster-id Configure Route-Reflector Cluster-id
confederation AS confederation parameters
dampening Enable route-flap dampening
default Configure BGP defaults
router-id Override configured router identifier
router(config-router)#bgp
CLI Features
The Avici router CLI supports the following features:
- Command Abbreviation - The CLI recognizes abbreviated keywords. Type the minimum number of unique characters to enter a keyword.
- Command-Line Error Detection - When the CLI detects an error, it indicates the error location with the caret (^) symbol on the following line.
- Command Prompt - The command prompt on the Avici router changes as you navigate through command modes. Refer to Table 1-1 for more information on the CLI command modes.
Command Mode Prompts
Each command mode available on the Avici router provides its own prompt so that you can easily identify what mode you are in.
The "parent" command mode is the mode from which you enter a command mode.
The following table lists the command modes, their parent command modes, the prompt displayed by the command mode, and the command used to enter the command mode:
Using the "Show" Commands
IPriori has been enhanced to support redirection of the output of show commands and selected display of output using redirection and three new sub-commands:
- Begin string - Display output starting with lines that match the specified regular expression.
- Include string - Display only those lines of output that include the specified regular expression.
- Exclude string - Display only those lines of output that exclude the specified regular expression.
Example 1: In the following example:
- The | redirects output of the show ip route command
- The include string command selects for display only those lines that include the string "12.12":
router#show ip route | include 12.12
S 12.12.9.0/24 via 127.0.0.1 [w:1 m:0]
S 12.12.10.0/24 via 127.0.0.1 [w:1 m:0]
S 12.12.11.0/24 via 127.0.0.1 [w:1 m:0]
S 12.12.12.0/24 via 127.0.0.1 [w:1 m:0]
S 12.12.13.0/24 via 127.0.0.1 [w:1 m:0]
.
.
.
Example 2: In the following example:
- The | redirects output of the show ip route command
- The exclude string command selects for display only those lines that do not include the string "12.12":
router#show ip route | exclude 12.12
Codes: C - connected O - OSPF i - IS-IS
S - static IA - inter area L1 - level-1
B - BGP E1 - external type 1 L2 - level-2
M - MPLS E2 - external type 2
* - candidate default
m - route's metric
w - route's weight
S * 0.0.0.0/0 via 10.22.0.1 [w:1 m:0]
C 10.22.0.0/16 directly connected to Ethernet 0
C 10.50.0.1/32 directly connected to Loopback 0
C 10.50.1.0/24 directly connected to composite-link 12
.
.
.
Example 3: In the following example:
- The | redirects output of the show ip route command
- The begin string command displays the output starting with the line that includes the string "12.12.20":
router##sho ip route | begin 12.12.20
S 12.12.20.0/24 via 127.0.0.1 [w:1 m:0]
S 127.0.0.0/8 via 127.0.0.1 [w:0 m:0]
C 127.0.0.1/32 directly connected to Null 0 .
.
.
.
Modifying the Console and VTY Line Defaults
Use the steps described in this section to modify the default settings for console and telnet sessions into the Avici router. The values and their defaults are as follows:
Modifying the Exec-Timeout
Exec-timeout automatically terminates the session if there is no keyboard activity or output displayed to the screen for the specified amount of time.
Use the exec-timeout command to configure the number of minutes without keyboard activity before the session is automatically ended.
Use the command in Privileged command mode to set the timeout for this session only. Use the command in Line configuration command mode to set the timeout for this and future sessions.
Example: In the following example:
- The line console command specifies the console and changes the command mode to Line configuration.
- The exec-timeout command configures the console to automatically logout if there is no command line activity for 15 minutes.
- The show running-config command displays the setting:
NOTE The setting will be saved for future VTY sessions.
router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
router(config)#line console 0
router(config-line)#exec-timeout 15
router(config-line)#end
router#sho run
.
.
.
!
line console 0
exec-timeout 15 0
Modifying History and History Size
Command line history allows the user to view command lines entered during this session.
Use the history command in Privileged command mode to enable/disable history for this session only.
Use the command in Line configuration command mode to enable/disable history for this and future sessions
Use the history size command to configure the number of command lines stored in the history buffer. Use the command in Privileged command mode to set the history size for this session only. Use the command in Line configuration command mode to set the history for this and future sessions
Use the show history command to display the command-line history buffer for commands issued in Executive/Privileged and Configuration command modes.
Example: In the following example,
- The line console 0 command specifies the console and changes the command mode to Line configuration.
- The history command enables the re-display of commands entered.
- The history size 10 command sets the number of lines displayed by the show history command to 10.
- The the show history command displays the last 10 commands issued in both Executive/Privileged command modes and all Configuration command modes:
router(config)#line console 0
router(config-line)#history
router(config-line)#history size 10
router(config-line)#end
router#show hist
CLI command history:ADMIN/PRIV mode
sho int pos 1/5/1
sho int pos 1/6/1
con t
sho int pos 1/6/1
con t
sho int pos 1/6/1
con t
sho int pos 1/6/1
con t
sho line
CLI command history:CONFIG mode
sonet path-trace test message
end
int pos 1/6/1
no sonet path-trace
end
line console 0
history
history size 10
end
show history
Modifying Netmask Display
You can select how IP netmasks are displayed in show commands using the ip netmask-format command.
Use the command in Privileged command mode to set the netmask format for this session only. Use the command in Line configuration command mode to set the netmask format for this and future sessions.
Use the ip netmask-format decimal command to configure the line to display IP netmasks using dotted decimal format.
Use the ip netmask-format hexadecimal command to configure the line to display IP netmasks using hexadecimal notation.
Use the ip netmask-format bit-count command to configure the line to display IP netmasks using prefix length format.
Example: In the following example,
- The line vty 0 4 command specifies VTY lines and changes the command mode to Line configuration.
- The ip netmask-format command configures the VTY lines to display the IP netmask in prefix length format.
- The show interface pos n/n/n displays an interface with the IP netmask in prefix length format:
NOTE The setting will be saved for future VTY sessions.
router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
router(config)#line vty 0 4
router(config-line)ip netmask-format bit-count
router(config-line)#end
router#sho int pos 1/5/1
POS 1/5/1 interface status is up, line protocol is up
Internet address is 10.100.53.2/24
Modifying Length and Width
Use the length num-lines command to define the number of lines displayed on your video terminal. Long output will pause after the specified number of lines are displayed.
Use the width num-lines command to define the number of characters per line displayed on your video terminal. Output that is wider than the specified number of lines "wraps" to the next line.
Use the commands in Privileged command mode to set the terminal length for this session only. Use the commands in Line configuration command mode to set the terminal length for this and future sessions.
Example: In the following example,
- The line vty 0 4 command specifies the VTY lines and changes the command mode to Line configuration.
- The length command configures the console to display the 30 lines per screen.
- The width command configures the console to display 90 characters per line.
- The show line displays the setting:
NOTE The setting will be saved for future VTY sessions.
router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
router(config)#line vty 0 4
router(config-line)#length 30
router(config-line)#width 90
router(config-line)#end
router#show line
.
.
.
Line vty 3 (*)
Length: 30 lines, Width: 90 columns
History is ENABLED, history size is 10.
Configuration Change Methodology
Before installing a configuration file on a live Avici router operating in the Internet, it is best to try your configuration in a test bed situation. Once you are certain that the configuration file contains no typographical or logical defects, it can be loaded onto an operational router.
Likewise, changes to a configuration running in an operational network should also be made with great care. Although you can change parameters on the fly in your test bed, this is rarely a good idea in a live network. Instead, test all configuration file changes on a test bed network, and then load the new configuration file onto your customer network.
IPriori Configuration File Organization
Organize your IPriori configuration file so that other users can easily read and understand your intent.
Comments
Comments begin with the pound sign(#). Comments terminate with the new line character.
It is a good idea to begin all IPriori configuration files with a comment block, including:
- Describe the network and its areas
- What the file does
- When it was created
- The name of the contact responsible for maintaining the file.
- The date the file was deployed.
To make your configuration files easier to maintain, do not use command abbreviations. Enter the entire command name and the complete name of each keyword or parameter.
PROCEDURE: Use the following steps to create a configuration file:
Step 1 Define the server identifier and location.
Step 2 Define and configure logging.
Step 3 Define the contents of each module slot.
Step 4 Identify interfaces and their IP addresses.
Step 6 Define your routing policies.
Step 7 Configure your interior gateway protocol (OSPF or IS-IS).
Step 8 Configure MPLS, RSVP and LDP
Step 9 Configure traffic engineering tunnels
Interface Definitions
When configuring routing protocols on a router, many components of the operation of that protocol are interface dependant and therefore are configured per interface. There are two schools of organization for configuration files:
- All interface commands should be collocated in the configuration file.
- All protocol configuration commands should be collocated in the configuration file.
The first method uses fewer total configuration commands. The second keeps all protocol-related configuration in a single location.
The module statement for each module must be entered before defining any interfaces on that module. Module commands can be entered in one of two ways:
- Collocated in one area of the configuration file, separate from the corresponding interface commands
- Located with the corresponding interfaces commands.
In a large configurations with many multiple-interface modules, collocating the module commands with the corresponding interface commands improves readability.
Example 1: In the following sample configuration file, the interface commands are collocated:
server-id 1
.
.
.
module 1/1 4xoc12
interface pos 1/1/1
ip address 13.1.3.1 255.255.255.0
ip router isis boston
isis password bigp0p level-1
interface pos 1/1/2
ip address 13.1.5.2 255.255.255.0
ip router isis boston
isis password bigp0p level-1
interface pos 1/1/3
ip address 13.1.1.50 255.255.255.0
ip router isis boston
isis password bigp0p level-1
module 1/2 4xoc12
interface pos 1/2/1
ip address 13.2.7.1 255.255.255.0
ip router isis boston
isis password bigp0p level-1
interface pos 1/2/2
ip address 13.2.110.3 255.255.255.0
ip router isis boston
isis password bigp0p level-1
interface pos 1/2/3
ip address 13.2.13.22 255.255.255.0
ip router isis boston
isis password bigp0p level-1
module 1/3 1xoc48
interface pos 1/3/1
ip address 13.4.12.25 255.255.255.0
ip router isis boston
isis password bigp0p level-2
router isis boston
net 49.0001.0000.0000.0020.00
net 49.0004.0000.0000.0020.00
net 49.0005.0000.0000.0020.00
domain-password moulder
area-password tick1e
Example 2: In the following sample configuration file, the routing commands are collocated:
module 1/1 4xoc12
module 1/2 4xoc12
module 1/3 1xoc48
interface pos 1/1/1
ip address 13.1.0.1 255.255.0.0
interface pos 1/1/2
ip address 13.6.0.2 255.255.0.0
interface pos 1/1/3
ip address 13.5.0.50 255.255.0.0
interface pos 1/2/1
ip address 13.2.0.1 255.255.0.0
interface pos 1/2/2
ip address 13.7.0.3 255.255.0.0
interface pos 1/2/3
ip address 13.9.0.22 255.255.0.0
interface pos 1/3/1
ip address 13.4.0.25 255.255.0.0
.
.
.
router isis boston
net 49.0001.0000.0000.0020.00
net 49.0004.0000.0000.0020.00
net 49.0005.0000.0000.0020.00
domain-password moulder
area-password tick1e
interface pos 1/1/1
ip router isis boston
isis password bigp0p level-1
interface pos 1/1/2
ip router isis boston
isis password bigp0p level-1
interface pos 1/1/3
ip router isis boston
isis password bigp0p level-1
interface pos 1/2/1
ip router isis boston
isis password bigp0p level-1
interface pos 1/2/2
ip router isis boston
isis password bigp0p level-1
interface pos 1/2/3
ip router isis boston
isis password bigp0p level-1
interface pos 1/3/1
ip router isis boston
isis password bigp0p level-2
Porting Files from Other Routers
IPriori's industry-standard CLI eases the transition from other routers. There are a few differences in the CLI to support the unique architecture of the Avici router:
- On the Avici router, all interfaces must be explicitly enabled. For each interface entry in a configuration file, include a no shutdown command to enable the interface unless you want to explicitly enable the interface from the CLI at a later time.
- SONET interfaces support Layer 3 IP traffic. POS interfaces are identified by bay#/slot#/port#. Refer to Chapter 4 for more information about interface identifiers on the Avici router.
- The first command in the configuration file must be server-id server-id {upper|lower|full} where the options are as follows:
server-id
Sets the server ID for the server.
upper
Specifies the server is located in the upper half of a split bay.
lower
Specifies the server is located in the lower half of a split bay.
full
Specifies the server is in a full bay.
- Each module must be explicitly configured. Interfaces configured before the configuration of the associated module are not recognized by the Avici router.
| |
|
|
Source
File Name: usingCLI.fm
HTML File Name: usingCLI.html
Last Updated: 05/30/02 at 13:53:38
Please email suggestions and comments to: doc@avici.com