|
|
This chapter describes basic system startup and use. Information in this chapter will help you with these tasks:
The setup command facility enables you to start using your Cisco network server quickly and without extensive background knowledge. It does this by prompting you for the information required to perform basic configuration procedures. The setup command facility is available on all Cisco Systems internetworking products with Release 8.2 or later software.
Use the setup command facility both at initial system configuration and for basic changes at any time. In addition, use the facility as a teaching tool to become familiar with the expected command sequence as you step through the process. Because of these unique characteristics, Cisco refers to setup as a command facility rather than simply as a command.
Refer to the Router Products Getting Started publication for detailed information and a step-by-step description of the configuration procedure using the setup command facility.
Use the setup command facility to:
Configure the following protocols with the setup command facility:
For more advanced applications, you need to enter a privileged configuration session, as described in the section "Entering Configuration Mode" later in this chapter.
The setup command facility operates automatically the first time you power-on your network server and when you add new hardware components. To use setup on subsequent occasions, you must invoke it as you would any other command, by typing it at the EXEC prompt (described in the section "Entering Configuration Mode" later in this chapter).
Before you start using the setup command facility, you need to do the following:
Step 1: Attach an RS-232 ASCII terminal to the system console port located at the rear of the network server.
Refer to the Cisco publications, Modular Products Hardware Installation and Reference or the IGS Hardware Installation and Reference, for details about cabling considerations and establishing electrical connections.
Step 2: Configure the terminal to operate at 9600 baud, 8 data bits, no parity, 2 stop bits.
Step 3: Power on the network server and run the setup program.
In addition, you need to know the following before you start:
The streamlined setup command facility gives you an opportunity to continue booting your system even though there may be problems with the configuration file when you are attempting to netboot an image.
The router enters the streamlined setup command facility under the following circumstances:
The setup command facility determines which interfaces are installed and prompts you for configuration information for each one. Once you complete one interface, the facility automatically starts over for the next, continuing until each interface has been configured.
When you first power on your console and network server, a script similar to the following will appear on the screen. The first section of the script displays the banner information, including the software version:
Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
cisco Systems, Inc.
1525 O'Brien Drive
Menlo Park, California 94025
GS Software (GS3-BFX), Version 8.3(1)
Copyright (c) 1986-1991 by cisco Systems, Inc.
Compiled Wed 14-Aug-91 13:31 by block
The next portion of the display is a list of the installed hardware. By reading the installed hardware, the system automatically presents the appropriate interfaces during the configuration process.
CSC3 (68020) processor with 4096K bytes of memory.
X.25 software.
Bridging software.
1 MCI controller.
2 Ethernet/IEEE 802.3 interface.
3 Token Ring/IEEE 802.5 interface.
2 Serial network interface.
16K bytes of multibus memory.
32K bytes of non-volatile configuration memory.
The first two sections of the configuration script (the banner and the installed hardware) appear each time the system is started up.
At the first-time system startup, the System Configuration Dialog automatically appears, offering the prompts for which you'll provide the answers to configure your system.
--- System Configuration Dialog ---
At any point you may enter a question mark '?' for help.
Refer to the 'Getting Started' Guide for additional help.
Default settings are in square brackets '[]'.
Would you like to enter the initial configuration dialog? [yes]:
At this point, you may choose not to continue with the System Configuration Dialog and exit by answering "no" to this prompt.
Answer "yes" to continue with the setup configuration dialog. The remainder of the script is the actual configuration process, with each prompt appearing automatically. Press the Return key to accept the default settings.
There is no default for the final prompt; you must answer either "yes" or "no" as to whether you will use this configuration. Also note that the setup command only asks you to configure the protocols for each interface that you specified on a global basis. For instance, if you said "no" for XNS under the global parameters, the command does not prompt you to configure that protocol under the interface parameters.
Configuring global parameters:
Enter host name [Gateway]: SandBox
Enter enable password: shovel
Enter virtual terminal password: hammer
Configure SNMP Network Management? [yes]:
Configure IP? [yes]:
Configure IGRP routing? [yes]:
Your IGRP autonomous system number [1]: 109
Configure DECnet? [no]: y
Your area number [1]: 55
Your node number [1]: 87
Area (level 2) routing? [no]: y
Configure XNS? [no]: y
Configure Novell? [no]: y
Configure AppleTalk? [no]: y
Extended networks? [yes]:
Configure CLNS? [no]: y
CLNS router tag [area_1]:
CLNS domain [49]:
CLNS area [0001]:
CLNS station id [0000.0C00.0A83]:
Configure Vines? [no]: y
Configure bridging? [no]:
Configure MOP? [no]:
Configuring interface parameters:
Configuring interface TokenRing0:
Is this interface in use? [yes]: no
Configuring interface TokenRing1:
Is this interface in use? [yes]:
Configure IP on this interface? [yes]:
IP address for this interface: 131.108.81.2
Number of bits in subnet field [0]: 8
Class B network is 131.108.0.0, 8 subnet bits; mask is 255.255.255.0
Configure DECnet on this interface? [yes]:
DECnet cost [10]:
Configure XNS on this interface? [yes]:
XNS network number [2]:
Configure Novell on this interface? [yes]:
Novell network number [2]:
Configure AppleTalk on this interface? [yes]:
AppleTalk network number [2]:
appletalk zone name [myzone]:
Configure CLNS on this interface? [yes]: n
Configure Vines on this interface? [yes]:
Configuring interface TokenRing2:
Is this interface in use? [yes]:
Configure IP on this interface? [yes]:
IP address for this interface: 131.108.82.2
Number of bits in subnet field [8]:
Class B network is 131.108.0.0, 8 subnet bits; mask is 255.255.255.0
Configure DECnet on this interface? [yes]: n
Configure XNS on this interface? [yes]: n
Configure Novell on this interface? [yes]: n
Configure AppleTalk on this interface? [yes]: n
Configure CLNS on this interface? [yes]: n
Configure Vines on this interface? [yes]: n
Configuring interface Ethernet0:
Is this interface in use? [yes]:
Configure IP on this interface? [yes]:
IP address for this interface: 131.108.17.2
Number of bits in subnet field [8]:
Class B network is 131.108.0.0, 8 subnet bits; mask is 255.255.255.0
Configure DECnet on this interface? [yes]: n
Configure XNS on this interface? [yes]: n
Configure Novell on this interface? [yes]: n
Configure AppleTalk on this interface? [yes]: n
Configure CLNS on this interface? [yes]: n
Configure Vines on this interface? [yes]: n
Configuring interface Serial0:
Is this interface in use? [yes]: n
Configuring interface Ethernet1:
Is this interface in use? [yes]:
Configure IP on this interface? [yes]:
IP address for this interface: 131.108.80.2
Number of bits in subnet field [8]:
Class B network is 131.108.0.0, 8 subnet bits; mask is 255.255.255.0
Configure DECnet on this interface? [yes]:
DECnet cost [10]:
Configure XNS on this interface? [yes]:
XNS network number [5]:
Configure Novell on this interface? [yes]:
Novell network number [5]:
Configure AppleTalk on this interface? [yes]:
AppleTalk network number [5]:
appletalk zone name [myzone]:
Configure CLNS on this interface? [yes]: n
Configure Vines on this interface? [yes]: n
Configuring interface Serial1:
Is this interface in use? [yes]: n
The following configuration command script was created:
hostname SandBox
enable password shovel
line vty 0 4
password hammer
snmp-server community
!
ip routing
decnet routing 55.87
decnet node-type area
xns routing
novell routing
appletalk routing
clns routing
clns router igrp area_1 net 49.0001.0000.0C00.0A83.00
vines routing
no bridge 1
!
! Turn off all XNS and Novell to prevent network conflicts.
interface TokenRing0
no xns network
no novell network
--More--
interface TokenRing1
no xns network
no novell network
interface TokenRing2
no xns network
no novell network
interface Ethernet0
no xns network
no novell network
interface Serial0
no xns network
no novell network
interface Ethernet1
no xns network
no novell network
interface Serial1
no xns network
no novell network
!
interface TokenRing0
shutdown
no ip address
--More--
!
interface TokenRing1
ip address 131.108.81.2 255.255.255.0
decnet cost 10
xns network 2
novell network 2
appletalk cable-range 2-2
appletalk zone myzone
vines metric
!
interface TokenRing2
ip address 131.108.82.2 255.255.255.0
!
interface Ethernet0
ip address 131.108.17.2 255.255.255.0
!
interface Serial0
shutdown
no ip address
!
--More--
interface Ethernet1
ip address 131.108.80.2 255.255.255.0
decnet cost 10
xns network 5
novell network 5
appletalk cable-range 5-5
appletalk zone myzone
!
interface Serial1
shutdown
no ip address
!
router igrp 109
network 131.108.0.0
!
end
Use this configuration? [yes/no]: yes
[OK]
Use the enabled mode 'configure' command to modify this
configuration.
Press RETURN to get started!
The server displays the system name (SandBox), followed by an angle bracket (>), which is the prompt of the system's command interpreter.
The command interpreter is called the EXEC. The EXEC interprets the commands you type and carries out the corresponding operations.
You can type commands when you see the system prompt, which is the system's host name ending with an angle bracket (>). Although the default system host name is Gateway>, this may have been changed during the initial configuration using the setup command, or with the hostname configuration command. The following sections describe how to use the EXEC.
The EXEC accepts commands typed in uppercase letters, lowercase letters, or both. You may also abbreviate commands and other keywords to the number of characters that cause the command to be a unique abbreviation. For example, you can abbreviate the show command to sh.
If you make a typing mistake, you can erase characters one at a time with the Delete or the Backspace key. Press either key to erase the last character typed. To erase the entire line, type Ctrl-U. (This notation means "Hold down the Ctrl key and press the U key.") The server acts on most commands after you press the Return key.
You can list available EXEC commands by typing a question mark (?). You can also enter a question mark to obtain more information about commands. For example, type terminal ? to obtain a list of terminal commands or show ? to obtain a list of show commands.
Certain EXEC commands produce multiple screens of output. At the end of each screen, the EXEC pauses and displays:
-More-
Type a space to continue the output; type anything else to return to the system command prompt.
For security purposes, the EXEC has two levels of access: user and privileged. The commands available at the user level are a subset of the commands available at the privileged level. Because many of the privileged commands set operating parameters, the privileged level should be password-protected to prevent its unauthorized use. The system prompt for the privileged level ends with a pound sign (#) instead of an angle bracket (>).
The EXEC enable command allows access to the privileged level, prompting for a password if one has been set with the enable-password configuration command. (For more information, see the section "Establishing Passwords and System Security" in the chapter "Configuring the System.")
Type the ? (question mark) command at the user level to see a list of the user-level EXEC commands similar to the following:
Gateway>?
connect <host> Connect to host - same as typing just a host name
disconnect <cn> Break the connection specified by name or number
exit, quit Exit from the EXEC
name-connection Give a connection a logical name
resume Make the named connection be current
show <cmd> Information commands, type "show ?" for list
systat Show terminal lines and users
telnet <host> Connect to host using telnet protocol
terminal Change terminal's parameters, type "terminal ?"
where Show open connections
<cr> To resume connection
Type enable and enter the password to access the privileged command level. Type the ? (question mark) command to see a list of privileged-level EXEC commands similar to this example:
Gateway# ?
clear Reinitialization functions, type "clear ?" for list
configure Configure from terminal or over network
connect <host> Connect to host - same as typing just a host name
debug Enable debugging functions, type "debug ?" for list
disable Turn off privileged commands
disconnect <cn> Break the connection specified by name or number
enable Turn on privileged commands
exit, quit Exit from the EXEC
name-connection Give a connection a logical name
ping Send echo messages
reload Halt and reload system
resume Make the named connection be current
send <line>|* Send message to a terminal line or lines
setup Initialize system configuration
show <cmd> Information commands, type "show ?" for list
systat Show terminal lines and users
telnet <host> Connect to host using telnet protocol
terminal Change terminal's parameters, type "terminal ?"
test Run hardware tests, type "test ?"
trace <address> Trace route to <address>
undebug Disable debugging functions, type "undebug ?" for list
where Show open connections
write Write configuration memory, type "write ?" for list
<cr> To resume connection
To return to the user level prompt, type disable at the EXEC prompt.
The EXEC command configure begins the configuration mode, where you enter the commands to configure your network server for its particular routing or bridging function. The following section describes the use of this command.
Use the privileged EXEC command configure to begin configuration of the network server.
Begin by entering the privileged level of the EXEC. This is done by entering the enable command at the EXEC prompt:
Gateway>enable
The EXEC then prompts you for privileged level password:
Password:
Type in the password. For security purposes, the password will not be displayed. (Also note that the password is case sensitive.) When you enter the correct password, the system displays the privileged mode system prompt:
Gateway#
To begin configuration mode, enter the configure command at the privileged mode prompt:
Gateway#configure
When you enter this command, the EXEC prompts you for the source of the configuration subcommands.
Configuring from terminal, memory, or network [terminal]?
The default is to type in commands from the terminal console. Pressing the Return key begins this configuration method. Each configuration technique--(terminal, memory, and network)--is described in more detail later in this chapter.
The EXEC provides you with a simple editor for entering the configuration commands, and explains the editing functions:
Enter configuration commands, one per line.
Edit with DELETE, CTRL/W, and CTRL/U;end with CTRL/Z
Table 2-1 lists the edit key functions and their meanings.
Key Meaning
Delete or Backspace Erases one character.
Ctrl-W Erases a word.
Ctrl-U Erases a line.
Ctrl-R Redisplays a line.
Return Executes single-line commands.
Ctrl-Z Ends configuration mode and returns to the EXEC.
The configuration subcommands are categorized by these functions:
The descriptions of the commands include the command type and give examples of their use.
As with EXEC commands, you can type configuration subcommands in uppercase letters, lowercase letters, or both. You may also shorten all commands and other keywords to unique abbreviations. You may add comments by preceding the line with an exclamation point (!). Comments do not affect command processing.
If you make a typing mistake, use the Delete or Backspace key to erase a character, Ctrl-W to erase a word, and Ctrl-U to erase a line. To redisplay a line, use Ctrl-R. See Table 2-1 for a list of valid commands.
The network server executes single-line commands when you press the Return key. The network server does not display confirmation messages as it executes the commands. If the network server encounters a problem, it displays an error message on the console terminal. When you type Ctrl-Z, the network server exits the configuration mode.
In most cases, you can negate a configuration subcommand or restore a default by typing no before the subcommand keyword. You can usually omit the arguments of the subcommand when you negate it with no. The command descriptions note any exceptions to these rules.
Following are some examples of configuration files to illustrate how to enter the configuration commands.
Use global configuration commands to enable functions that affect the system rather than a particular line or interface, and can appear any place within the configuration file. An example of this is the global configuration command to define the host name, or the name of the router:
hostname router-1
Commands to enable a particular routing or bridging function are also global configuration commands. The following example illustrates how to enable the Xerox Network System routing protocol:
xns routing 0123.4567.abcd
Once enabled, interface characteristics for XNS routing are specified using the interface command and XNS-specific interface subcommands. Command descriptions in the sections describing configuration will define the command type.
Interface subcommands modify the operation of an interface such as an Ethernet, FDDI, or serial port. Interface subcommands always follow an interface command which defines the interface type.
The following example illustrates how to enable XNS network 1 on interface Ethernet 0:
interface ethernet 0
xns network 1
The following example illustrates how to configure the token rotation timer on interface FDDI 0:
interface FDDI 0
fddi token-rotation-timer 24000
The EXEC accepts commands in uppercase and lowercase letters. Exclamation points are not parsed and serve as comment lines and delimiters between configuration commands.
If you forget to enter the interface command, the system displays the message "must specify a network interface."
Line subcommands modify the operation of a serial terminal line. Line subcommands always follow a line command which defines the line number. If you forget to enter the line command, the system displays the message "must specify a line or range of lines."
The following example illustrates how to set the password on line 5:
line 5
password secretword
Router subcommands are used to configure IP routing protocol characteristics and always follow a router command. The following example illustrates how to set the maximum hop metric for the Cisco IGRP routing protocol:
router igrp
metric maximum-hops 150
If you forget to enter the router command, the system displays the message "must specify a routing protocol."
Remember to type Ctrl-Z to end your configuration sessions, and to use the disable command to leave privileged level mode.
If you used the setup facility's interactive dialog prompts to start your configuration file, it was saved in nonvolatile memory when you finished the prompts. If you chose not to create your configuration file this way, there are several options you may now choose from to create the configuration file.
The network server holds configuration information in two places--in running memory, and in nonvolatile memory. Configuration information in running memory is temporary and will not be stored if power is shut off. Configuration information in nonvolatile memory is always available.
You use the EXEC command write memory to copy current (running) configuration information to nonvolatile memory. This command stores all nondefault configuration information as configuration commands in text format. The command also records a checksum for the information to protect against data corruption.
The EXEC command show configuration displays information stored in nonvolatile memory. You can use this command and the write terminal command to find differences between the current configuration (that in running memory) and that stored in nonvolatile memory. You use the EXEC command write erase to clear the contents of nonvolatile memory.
The write commands create their output by examining the state of the system currently running. The output produced by the write commands is generated by the software, and will not necessarily match the text the user entered to create the current configuration.
The network server also allows you to store the configuration file on a network host. (This allows you to use an editor on the host to edit and create the configuration file.) Use the EXEC command write network to copy the current configuration information to a server host on the network. Use of this command is described later in this section.
To issue configuration commands from the console terminal, enter the EXEC command configure at the privileged-level EXEC prompt and enter configuration mode.
The network server responds with this prompt asking you to specify the terminal, a file, or nonvolatile memory as the source of configuration commands.
Configuring from terminal, memory, or network [terminal]?
To begin configuration, type terminal at the prompt or just press Return (since terminal is the default) to start command collection. (See the section "Entering Configuration Mode" in this chapter for more information.)
During command collection, the network server accepts one configuration command per line. You can enter as many configuration subcommands as you want.
Type Ctrl-Z when you finish entering configuration commands. This returns you to the EXEC where you can test your configuration, or write the configuration commands to memory.
At periodic intervals, you will want to write the configuration information into nonvolatile memory or to a configuration file stored on a remote host. This will make checking, adding information to, and booting the configuration file an easier task. The procedures for writing information to nonvolatile memory are described next.
After you enter the desired configuration information at the console terminal, use the privileged EXEC command write memory to make a copy of the configuration information in the nonvolatile memory. Nonvolatile memory stores the current configuration information in text format as configuration commands, recording only nondefault settings. The memory is checksummed to guard against corrupted data.
As part of its start-up sequence, the network server startup software always checks for configuration information in the nonvolatile memory. Once the nonvolatile memory holds valid configuration commands, the network server executes the commands automatically at startup. If the network server detects a problem with the nonvolatile memory or the configuration information it contains, the network server may enter the setup mode, prompting for configuration information. Problems can include a bad checksum for the information in the nonvolatile memory and the absence of critical information.
To display the configuration information stored in the nonvolatile memory, enter the show configuration EXEC command at the privileged mode EXEC prompt.
To clear the contents of the nonvolatile memory, enter the write erase EXEC command at the privileged level EXEC prompt.
To re-execute the configuration commands stored in nonvolatile memory, enter memory at the configure mode prompt:
Configuring from terminal, memory, or network [terminal]?memory
To store configuration information on a remote host, enter the privileged EXEC command write network. This command sends a copy of the current configuration information to a remote host. The command will prompt you for the destination host's address and a file name, as the following example illustrates.
Tokyo#write network
Remote host [131.108.2.155]?
Name of configuration file to write [tokyo-confg]?
Write file tokyo-confg on host 131.108.2.155? [confirm]y
Writing tokyo-confg...
[OK]
To retrieve and/or add to the configuration information stored on a host file on a device on your network, enter network at the configure mode prompt (see the section "Entering Configuration Mode" in this chapter for more information):
Configuring from terminal, memory, or network [terminal]?network
The system will ask you to select a host or network configuration file, for the address of the host, and for a file name. The following example illustrates this process.
Host or network configuration file [host]?
IP address of remote host [255.255.255.255]? 131.108.2.155
Name of configuration file [tokyo-confg]?
Configure using tokyo-confg from 131.108.2.155? [confirm]y
Booting tokyo-confg from 131.108.2.155: !! [OK - 874/16000 bytes]
The network server may be configured to automatically load additional configuration information from a network host. You may want to keep an up-to-date version of configuration information on another host, where you can change it as necessary, and use the nonvolatile memory as a bootstrap or backup mechanism. You can instruct the network server to load configuration information over the network by entering the service config subcommand and then writing the information to nonvolatile memory using the write memory command. Loading configuration information over the network is the default if nonvolatile memory is not installed. (The service configuration subcommand is described in the section "Tailoring Use of Network Services" in the chapter "Configuring the System.")
After loading configuration information from the nonvolatile memory, the network server will attempt to load two configuration files from remote hosts. The first is the network configuration file, which contains commands that apply to all network servers and terminal servers on a network. The second is the host configuration file, which contains commands that apply to one network server in particular.
The default name of the network configuration file is network-confg. The default name for the host configuration file is taken from the host name. The host name can be specified by the hostname configuration subcommand or can be derived from the Domain Name System (DNS); see the section "Setting the Host Name" in the chapter "Configuring the System" for more information. To form the host configuration file name, the network server converts the host name to lower case, stripped of any DNS information, and appends "-confg." If no host name information is available, the default host configuration file name is gateway-confg. Other names for these configuration files can be set using the boot command, which is described in the section "Setting Configuration File Specifications" in the chapter "Configuring the System."
The network server uses TFTP to load and save configuration files. By default, the network server uses an Internet address of all ones to broadcast TFTP Read Request messages. However, many hosts use an old style of broadcast address consisting of all zeros. You can change operation to accommodate hosts using the old style of broadcast address.
If the network server fails to load a configuration file during startup, it tries again every ten minutes (default setting) until a host provides the requested files. With each failed attempt, the network server displays a message on the console terminal.
If the network server is unable to load the file named network-confg, it displays the message.
Booting network-confg... [timed out]
To end these file load attempts, enter the following configuration command at the console terminal and save it in the nonvolatile memory:
no service config
This command prevents the network server from trying to access nonexistent TFTP servers when it is booted.
As configured at the factory, the operating system software executes instructions in the onboard EPROM. You need not change the system EPROMs with each software update. Instead, you can download the latest software over the network. This process is called
netbooting.
Netbooting works as follows: when you power on your Cisco network server product for the first time, it checks the processor configuration register or the nonvolatile memory for special netbooting instructions. If the system finds no special instructions, it executes the default EPROM software.
If the system finds netbooting instructions, it determines its interface address and then runs a special process to TFTP-load the new software into memory.
You can specify boot loading in two ways. The first way involves setting the low four bits of the processor configuration register; see the Cisco publication Modular Products Hardware Installation and Reference, or IGS Hardware Installation and Reference for details. If no bits are set, you must manually boot the system using the System Bootstrap program. If only the low bit is set, the system runs the default software. The system interprets any other binary bit combination as an octal number for use in forming the boot file name. The system forms the boot file name by starting with the word "cisco" and then appending the octal number, a hyphen, and the processor type name. The System Bootstrap program displays the processor type name at system start up.
For example, if bit one in the four-bit field is set and the processor type is CSC/3, the boot file name formed is cisco3-csc3. Assuming no other information is available, the system would try to TFTP-load the file cisco3-csc3 by first sending a broadcast TFTP read request to determine which server host had the file.
The second way to specify netbooting uses the nonvolatile memory option, which enables you to provide more detailed instructions for software downloading. You can use the boot configuration command to specify both the boot file name and the IP address of the server host. You must, however, still set the bottom four bits of the configuration register to a netbooting value.
For the CSC/2 network server images, it is necessary to use the secondary bootstrap process for netbooting due to memory limitations and the expansion of system software. The secondary bootstrap process requires that there be an image called boot-csc2 on the TFTP server (contact Cisco Customer Service for this). Also, bit 9 of the processor configuration register must be set to enable this process. When booting, the system will request and load boot-csc2. This bootstrap image will then request and load the specified system image. Refer to the hardware configuration and installation manual for your router for more complete information about the processor configuration register.
Use the following EXEC command to halt and restart the network server:
reloadIf the system is set to restart on error, it reboots itself.
|
|