Table of Contents

Introduction
MPLS/Tag Terminology
Equipment and Software Requirements
Configuration Preview
Initial Setup of MPLS Switching

Configuration for BPX switch portions of the BPX 8650 ATM-LSRs

Command Syntax Summary for BPX Portion of MPLS Configuration
Configuration for BPX 1 Portion of ATM-LSR-1
Configuration for BPX 2 portion of ATM-LSR-2

Configuration for LSC 1 and LSC 2 portions of the BPX 8650

Configuration for LSC1 portion of ATM-LSR-1
Configuration for LSC2 portion of ATM-LSR-2

Configuration for Edge Label Switch Routers, LSR-A and LSR-B

Configuration of Cisco 7500 as an Edge Router, Edge LSR-A
Configuration of Cisco 7500 as an Edge Router, Edge LSR-C

Routing Protocol Configures LVCs via MPLS

Testing the MPLS Network Configuration

Useful LSC Commands
Checking the BPX Extended ATM Interfaces

Basic Router Configuration
Accessing the Router Command-Line Interface
Booting the Router for the First Time
Configuring the Router for the First Time
Using the System Configuration Dialog
Configuring Port Adapter Interfaces

Preparing to Configure Port Adapter Interfaces

Identifying Chassis Slot, Port Adapter Slot, and Interface Port Numbers
Cisco 7200 or 7500 Port Adapter Interface Ports

Configuring ATM Interfaces

Other Router Interfaces
Checking the Configuration

Using Show Commands to Verify the New Interface Status
Using Show Commands to Display Interface Information
Using the ping Command

Using Configuration Mode
Cisco IOS Software Basics

Cisco IOS Modes of Operation
Getting Context-Sensitive Help
Saving Configuration Changes

The BPX Switch, 7200, and 7500 Routers for MPLS

This chapter provides basic information for configuring BPX switches and associated label switching controllers along with edge routers for Multiprotocol Label Switching (MPLS) operation. Once MPLS is running in the network, OSPF determines the paths through the network, and MPLS sets up a label along each path. Refer to 9.2 Release Notes for supported features.

For additional information, refer to Chapter 19, Configuration General, MPLS on BPX Switch; for configuring CoS operation, refer to Chapter 21, MPLS CoS with BPX 8650, Configuration; and for information on MPLS VPNs, refer to Chapter 22, MPLS VPNS with BPX 8650, Configuration.

In addition, some basic procedures are provided for initial configuration of a router and its various interfaces, including ATM and Ethernet interfaces.

For further information regarding the Cisco 7200 or 7500 series, detailed software configuration information is provided in the Cisco IOS configuration guide and Cisco IOS command reference publications, which are available on the Cisco Documentation CD-ROM.

The chapter contains the following sections:

• Introduction

• MPLS/Tag Terminology

• Equipment and Software Requirements

• Configuration Preview

• Initial Setup of MPLS Switching

• Testing the MPLS Network Configuration

• Adding to the MPLS Network

• Network Management

• Basic Router Configuration

• Accessing the Router Command-Line Interface

• Booting the Router the First Time

• Configuring the Router for the First Time

• Using the System Configuration Dialog

• Configuring Port Adapter Interfaces

• Other Router Interfaces

• Checking the Configuration

• Using Configuration Mode

• Cisco IOS Software Basics

Introduction

Networks using MPLS, transport IP packets over ATM using label switching, thereby realizing the flexibility and scalability of TCP/IP along with the switching speed and reliability of ATM.

Configuring the MPLS network consists of setting up ATM router/switches for MPLS. This requires configuring the MPLS controller function on the router entity and the controlled (slave) function on the switch entity of each node.

In the example given here for BPX MPLS nodes (BPX 8650 ATM-LSRs), each MPLS node comprises a 7200 or 7500 router and a BPX switch shelf, where a 7200 or 7500 router provides the controlling function to the BPX switch shelf.

When MPLS is running in the network, the routing protocol, e.g., OSPF, determines the paths through the MLPS switch network from every edge label switch router (LSR) to every IP destination. Based on this routing information, MPLS then automatically sets up a Label VC (LVC) along each path. This is done using the Label Distribution Protocol (LDP).

Consider packets arriving at the edge of the MPLS network with a particular destination IP address. The packets with that IP address will have labels applied at the edge LSR and the resulting ATM cells will be forwarded along the appropriate LVC path through the network using label swapping at each label switch until the far end edge LSR is reached. The far end edge LSR will remove the label, rebuild the frame, and forward the IP packet onto its LAN destination.

MPLS/Tag Terminology

The following lists the change of terminology to reflect the change from "label" to "mpls" terms.

Equipment and Software Requirements

BPX:

• BPX 8650

BCC-3-64, BCC-4-64, BCC-4-128

BXM FW

• --

LSC Router:

• 7200 Series Router with NPE-150, NPE-200, or 7200VXR processor

• 7500 Series Router with RSP-2 or RSP-4 processor

• 32 MB minimum, 64 MB recommended memory

IOS:

• 12.0T(5) or later, IP only release recommended

SWSW:

• 9.2.10 or later

Configuration Preview

Setting up label switching on a node involves is essentially a three-step process:

1. Configuring BPX switch

(a) BPX switch (label switch slaves) configuration

(b) Router (label switch controller) configuration of router extended ATM interfaces on the BPX for tag switching

2. Setting up edge routers (can include setting up policies, etc.)

3. MPLS automatically sets up LVCs across the network.

Figure 17-1 shows an example of a simplified MPLS network. The packets destined for 204.129.33.127 could be real time video, while the packets destined for 204.133.44.129 could be data files which can be transmitted when network bandwidth is available.

Once MPLS has been set up on the nodes shown in Figure 17-1, (ATM-LSR 1 thru ATM-LSR 5, Edge LSR_A, Edge LSR_B, and Edge LSR_C), automatic network discovery is thereby enabled. Then MPLS will automatically set up LVCs across the network. At each ATM LSR (label switch), label swapping is used to transport the cells across the previously set up LVC paths.

At the edge LSRs, labels are added to incoming IP packets, and labels are removed from outgoing packets. Figure 17-1 shows IP packets with host destination 204.129.33.127 being transported as labeled ATM cells across LVC 1, and IP packets with host destination 204.133.44.129 being transported as labeled ATM cells across LVC 2.

Figure 17-2 is a simplified diagram showing the MPLS label swapping that might take place in the transportation of the IP packets in the form of ATM cells across the network on the LVC1 and LVC2 virtual circuits.

For example, an unlabeled IP packet with destination 204.133.44.129 arrives at edge label switching router (LSR-A). Edge LSR-A checks its label forwarding information base (LFIB) and matches the destination with prefix 204.133.44.0/8. LSR-A converts the AAL5 frame to cells and sends the frame out as a sequence of cells on 1/VCI 50. ATM-LSR-1, which is a BPX 8650 label switch router (LSR) controlled by a routing engine (7200 or 7500 router), performs a normal switching operation by checking its LFIB and switching incoming cells on interface 2/VCI 50 to outgoing interface 0/VCI 42.

Continuing on, ATM-LSR-2 checks its LFIB and switches incoming cells on interface 2/VCI 42 to outgoing interface 0/VCI 90. Finally, Edge LSR-C receives the incoming cells on incoming interface 1/VCI 90, checks its LFIB, converts the ATM cells back to an AAL5 frame, then to an IP packet, and then sends the outgoing packet onto its LAN destination 204.133.44.129.

Initial Setup of MPLS Switching

The following provides an example of configuring BPX 8650 MPLS label switches (ATM-LSRs) for MPLS switching of IP packets through an ATM network, along with configuration for 7200/7500 routers for use as Label edge routers (Edge LSRs) at the edges of the network.

See Figure 17-3 for a simplified example of the network. The following configuration example describes the configuration of Edge LSR-A (7500 router), Edge LSR-C (7500 router), ATM LSR-1 (BPX 8650 switch and controller), and ATM LSR-2 (BPX 8650 switch and controller) shown in Figure 17-3. The configuration of ATM LSR-3, ATM LSR-4, and ATM LSR-5, is not detailed, but would be performed in a similar manner to that for ATM LSR-1 and ATM LSR-2. Also, the configuration of Edge LSR-B (7500 router) would be similar to that for Edge LSR-A and LSR-C.

The configuration of a BPX 8650 ATM-LSR, consists of two parts, configuring the BPX switch and configuring the associated label switch controller (7200 or 7500 router).

Configuration for BPX switch portions of the BPX 8650 ATM-LSRs

The BPX nodes need to be set up and configured in the ATM network, including links to other nodes, etc. Following this, they may be configured for MPLS Operation. In configuring the BPX nodes for operation, a virtual interface and associated partition is set up with the cnfrsrc command. The 7200 or 7500 router is linked to the BPX with the addshelf command to allow the router's label switch controller function to control the MPLS operation of a node. The resources of the partition may be distributed between the associated ports. These are items such as bandwidth, vpi range, and number of logical connection spaces (LCNs). The VPIs are of local significance, so they do not have to be the same for each port in a node, but it is generally convenient from a tracking standpoint to keep them the same for a given BPX node. In this example, it is assumed that a single external controller per node is supported, so that the partition chosen is always 1.

Proceed as follows to configure the BPX 8650 label switch routers, ATM-LSR-1 and ATM-LSR-2:

Command Syntax Summary for BPX Portion of MPLS Configuration

This chapter provides an example for configuring the BPX 8650 for basic MPLS operation. For additional detail about configuring MPLS on the BPX: for general information, refer to Chapter 19, Configuration General, MPLS on BPX Switch; for configuring CoS operation, refer to Chapter 21, MPLS CoS with BPX 8650, Configuration; and for information on MPLS VPNs, refer to Chapter 22, MPLS VPNS with BPX 8650, Configuration.

Syntax for associated commands, cnfrsrc, cnfqbin, addshelf are as follows:

cnfrsrc slot.port.{virtual trk} maxpvclcns maxpvcbw [Edit parms ? y/n] partitionID e/d minvsilcns maxvsilcns vsistartvpi vsiendvpi vsiminbw vsimaxbw {if you enter "y", to Edit parms?

cnfrsrc slot.port.{virtual trk} maxpvclcns maxpvcbw [Edit parms ? y/n] {accepts defaults if you enter "n" to Edit parms

cnfqbin <slot.port> <Qbin_#> <e/d> y/n <Qbin discard_thr> <Low EPD threshold> <CLPhi> <EFCI_thr> {If you enter "n" to not accept template values

cnfqbin <slot.port.[virtual trk}> <Qbin_#> <e/d> y/n {If you enter "y" to accept template values.

addshelf <slot.port [virtual trk]> <device-type> <control ID> <control partition ID>

Configuration for BPX 1 Portion of ATM-LSR-1

Proceed with configuration as follows:.

Configuration for BPX 2 portion of ATM-LSR-2

Proceed with configuration as follows:.

Configuration for LSC 1 and LSC 2 portions of the BPX 8650

Before configuring the routers for the label switch (MPLS) controlling function, it is necessary to perform the initial router configuration if this has not been done.

As part of this configuration, it is necessary to enable and configure the ATM Adapter interface as described in "Configuring ATM Interfaces" section.

Then the extended ATM interface can be set up for Label Switching, and the BPX ports configured by the router as extended ATM ports of the router physical ATM interface according to the following procedures for LSC1 and LSC2.

Configuration for LSC1 portion of ATM-LSR-1

Configuration for LSC2 portion of ATM-LSR-2

Configuration for Edge Label Switch Routers, LSR-A and LSR-B

Before configuring the routers for the label switch (MPLS) controlling function, it is necessary to perform the initial router configuration if this has not been done.

As part of this configuration, it is necessary to enable and configure the ATM Adapter interface as described in "Configuring ATM Interfaces" section.

Then the extended ATM interface can be set up for Label Switching, and the BPX ports configured by the router as extended ATM ports of the router physical ATM interface according to the following procedures for LSR-A and LSR-C. Configuration of the 7500 routers performing as label edge routers is provided in the following:

Configuration of Cisco 7500 as an Edge Router, Edge LSR-A

Configuration of Cisco 7500 as an Edge Router, Edge LSR-C

Routing Protocol Configures LVCs via MPLS

After the initial configuration procedures for the BPX 8650 and Edge Routers has been performed as described in the previous paragraphs, the routing protocol, e.g., OSPF, sets up the LVCs via MPLS as shown in Figure 17-4.

Testing the MPLS Network Configuration

Preliminary testing of the MPLS network starts with checking VSI status, the MPLS interfaces, and MPLS discovery process.

Useful LSC Commands

The following are some of the useful LSC (also referred to as TSC) commands for monitoring and troubleshooting an MPLS network:

  show controllers VSI descriptor [descriptor]

  show tag int

  show tag tdp disc

For a complete description of these LSC commands refer to the related IOS MPLS documentation. For Release 9.1, these are Cisco IOS 11.1 CT documents:

• Tag Switching on Cisco 7000 Family

• Tag Switch Controller

Checking the BPX Extended ATM Interfaces

Use the following procedure as a quick checkout of the tag switching configuration and operation with respect to the BPX switch, for example ATM-LSR-1.

The example output for ATM-LSC-1 (BPX 8650 shelf) is:

-------

Step 2   If there are no interfaces present, first check that card 1 is up,

with, on the BPX switch:

   dspcds

and, if the card is not up, in this example BXM in slot 1 of the BPX shelf:

   resetcd 1 h

and/or remove the card to get it to reset if necessary.

---

Note This example assumes that the controller is connected to card 1 on the switch. Substitute a different card number, as applicable.

---

Step 3   Check the trunk status with the following command:

   dsptrks

The dsptrks screen for ATM-LSR-1 should show the 1.1, 1.3 and 2.2 MPLS interfaces, with the "Other End" of 1.1 reading "VSI (VSI)". A typical dsptrks screen example follows:

Sample Display

Step 4   Enter the dspnode command.

   dspnode

The resulting screens should show trunk 1.1 (link to LSC on ATM-LSR-1) as type VSI. A typical dspnode screen follows:

Example of dspnode screen.

Step 5   Enter the dsprsrc command as follows:

   dsprsrc 1.1 1

The resulting screen should show the settings shown in the following example:

Sample Display:

Step 6   Enter the dspqbin command as follows:

   dspqbin 1.1 10

The resulting screen should show the settings shown in the following example:

Sample Display:

Step 7   If interfaces 1.3 and 2.2 are present, but not enabled, perform the previous debugging steps for interfaces 1.3 and 2.2 instead of 1.1, except for the dspnode command which does not show anything useful pertaining to ports 1.3 and 2.2.

Step 8   Try a ping on the tag switch connections. If the ping doesn't work, but all the tag switching and routing configuration looks correct, check that the TSC has found the VSI interfaces correctly by entering the following command at the TSC:

If the interfaces are not shown, re-check the configuration of port 1.1 on the BPX switch as described in the previous steps.

Step 9   If the VSI interfaces are shown, but are down, check whether the LSRs connected to the BPX switch show that the lines are up. If not, check such items as cabling and connections.

Step 10   If the LSCs and BPX switches show the interfaces are up, but the LSC doesn't show this, enter the following command on the LSC:

Router LSC1# reload


If the "show tag int" command shows that the interfaces are up, but the ping doesn't work, enter the follow command at the LSC:

Router LSC1# tag tdp disc


The resulting display should show something similar to the following:

Step 11   If the interfaces on the display show "xmit" and not "xmit/recv", then the LSC is sending LDP messages, but not getting responses. Enter the following command on the neighboring LSRs.

Router LSC1# tag tdp disc


If resulting displays also show "xmit" and not "xmit/recv", then one of two things is likely:

(a) The LSC is not able to set up VSI connections

(b) The LSC is able to set up VSI connections, but cells won't be transferred because they can't get into a queue

Step 12   Check the VSI configuration on the switch again, for interfaces 1.1, 1.3, and 2.2, paying particular attention to:

(a) maximum bandwidths at least a few thousands cells/sec

(b) qbins enabled

(c) all qbin thresholds non-zero

Basic Router Configuration

The following paragraphs in this chapter provide basic configuration information for the Cisco 7200 or 7500 routers used as the Label Switch Controller for the BPX 8650. The following topics are included:

• Accessing the Router Command-Line Interface

• Booting the Router for the First Time

• Configuring the Router for the First Time

Accessing the Router Command-Line Interface

To configure a router, you must access its command-line interface (CLI).

If you will be configuring the router on site, connect a console terminal (an ASCII terminal or a PC running terminal emulation software) to the console port on the router.

For remote access, connect a modem to the auxiliary port on the router.

Booting the Router for the First Time

Each time you turn on power to the router, it goes through the following boot sequence:

The first time you boot the router, you need to configure the router interfaces and then save the configuration to a file in NVRAM. Proceed to the next section, "Configuring the Router for the First Time," for configuration instructions.

Configuring the Router for the First Time

You can configure the Cisco router using one of the following procedures, which are described in this section:

1. Using the System Configuration Dialog—Recommended if you are not familiar with Cisco IOS commands.

2. Using Configuration Mode—Recommended if you are familiar with Cisco IOS commands.

3. Using Auto Install—Recommended for automatic installation if another router running Cisco IOS software is installed on the network. This configuration method must be set up by someone with experience using Cisco IOS software.

TimeSaver Obtain the correct network addresses from your system administrator or consult your network plan to determine correct addresses before you begin to configure the router.

Use the procedure that best meets the needs of your network configuration and level of experience using Cisco IOS software. If you use configuration mode or Auto Install to configure the router and you would like a quick review of the Cisco IOS software, refer to the section "Cisco IOS Software Basics" later in this chapter. Otherwise, proceed to the next section, "Using the System Configuration Dialog."

Using the System Configuration Dialog

If your router does not have a configuration (setup) file and you are not using AutoInstall, the router will automatically start the setup command facility. An interactive dialog called the System Configuration Dialog appears on the console screen. This dialog helps you navigate through the configuration process by prompting you for the configuration information necessary for the Cisco router to operate.

This section gives an example configuration using the System Configuration Dialog. When you are configuring your router, respond as appropriate for your network.

At any time during the System Configuration Dialog, you can request help by entering a question mark (?) at a prompt.

Before proceeding with the System Configuration Dialog, obtain from your system administrator the node addresses and the number of bits in the subnet field (if applicable) of the Ethernet and synchronous serial ports.

Take the following steps to configure the router using the System Configuration Dialog:

Step 2   Press Return or enter yes to begin the configuration process.

Step 3   When the System Configuration Dialog asks whether you want to view the current interface summary, press Return or enter yes:

Step 4   Configure the global parameters. A typical configuration follows:

Step 5   Next, you are prompted to enter an enable secret password. There are two types of privileged-level passwords:

• Enable secret password (a secure, encrypted password).

• Enable password (a less secure, nonencrypted password).

The enable password is used when the enable secret password does not exist. For maximum security, be sure the passwords are different. If you enter the same password for both, the Cisco router will accept your entry, but will display a warning message indicating that you should enter a different password.

Step 6   Enter an enable secret password:

Step 7   Enter the enable and virtual terminal passwords:

Step 8   Press Return to accept Simple Network Management Protocol management, or enter no to refuse it:

Step 9   In the following example, the Cisco router is configured for AppleTalk, IP, MPLS, and Internetwork Packet Exchange. Configure the appropriate protocols for your router:

Configuring Port Adapter Interfaces

Once port adapter cable connections have been made, and basic configuration on the router is completed, the applicable port adapter interfaces on the router, Ethernet, Fast Ethernet, ATM, FDDI, etc., must be configured, followed by configuration of the router for MPLS operation, and addition of permanent virtual circuits (PVCs), as applicable.

Preparing to Configure Port Adapter Interfaces

If you want to configure interfaces in a new Cisco 7200 or 7500 Series router, or if you want to change the configuration of an existing interface, be prepared with the information you will need, such as the following:

• Protocols you plan to route on each new interface.

• Internet protocol (IP) addresses if you plan to configure the interfaces for IP routing.

• The types of interfaces that will be used.

The configure command requires privileged-level access to the EXEC command interpreter, which usually requires a password. Contact your system administrator if necessary to obtain EXEC-level access.

Identifying Chassis Slot, Port Adapter Slot, and Interface Port Numbers

The following section describes how to identify chassis slot, port adapter slot, and interface port numbers on the 7200 or 7500 Series routers for all port adapter interface types.

Cisco 7200 or 7500 Port Adapter Interface Ports

Physical port addresses specify the actual physical location of each interface port, regardless of the type.

You can also identify port adapter interface ports by physically checking the slot/interface port location on the 7200 or 7500 Series routers, or by using show commands to display information about a specific interface or all interfaces.

Configuring ATM Interfaces

This section provides the procedure for a basic interface configuration.

Press the Return key after each step unless otherwise noted. At any time you can exit the privileged level and return to the user level by entering disable at the prompt as follows:

Use the following procedure to perform a basic configuration:

Step 2   At the prompt, enter the subcommand interface to specify the interface to be configured, then atm to specify port adapter type, then slot/port (port adapter slot number and interface port number). The example that follows is the 1/0 interface of the atm port adapter in a 7200 Series router:

Step 3   If IP routing is enabled on the system, you can assign an IP address and subnet mask to the interface with the ip address configuration subcommand, as in the following example:

Step 4   Add any additional configuration subcommands required to enable routing protocols and set the interface characteristics.

Step 5   Change the shutdown state to up and enable the interface as follows:

Step 6   Repeat Step 2 through Step 5 to configure additional interfaces as required.

Step 7   When you have completed the configuration, press Ctrl-Z to exit configuration mode.

Step 8   Write the new configuration to nonvolatile memory as follows:

---

Note If you are going to unattach/reconfigure the ATM interface cable, use the shutdown command prior to this action. After re-attaching the ATM interface cable, use the no shutdown command to bring the ATM interface into an up state.

---

Other Router Interfaces

The router has other interfaces for carrying IP traffic. Refer to the Cisco 7200 or 7500 Series Router documentation, as applicable.

Checking the Configuration

After configuring the new interface, use the show commands to display the status of the new interface or all interfaces and the ping command to check connectivity.

Using Show Commands to Verify the New Interface Status

The following steps use show commands to verify that the new interfaces are configured and operating correctly.

Step 2   Display all the current port adapters and their interfaces with the show controllers command. Verify that the new port adapter appears in the correct slot.

Step 3   Specify one of the new interfaces with the show interfaces port adapter type slot/interface command and verify that the first line of the display specifies the interface with the correct slot number. Also verify that the interface and line protocol are in the correct state: up or down.

Step 4   Display the protocols configured for the entire system and specific interfaces with the show protocols command. If necessary, return to configuration mode to add or remove protocol routing on the system or specific interfaces.

Step 5   Display the running configuration file with the show running-config command. Display the configuration stored in NVRAM using the show startup-config command. Verify that the configuration is accurate for the system and each interface.

If the interface is down and you configured it as up, or if the displays indicate that the hardware is not functioning properly, ensure that the network interface is properly connected and terminated. If you still have problems bringing the interface up, contact a service representative for assistance.

Using Show Commands to Display Interface Information

To display information about a specific interface, use the show interfaces command with the interface type and port address in the format show interfaces [type slot/port] for the Cisco router.

Cisco Show Interfaces Command

Following is an example of how the show interfaces [type slot/port] command displays status information (including the physical slot and port address) for the interfaces you specify.(Interfaces are administratively shut down until you enable them.)

With the show interfaces type slot/port command, use arguments such as the interface type (ethernet, and so forth) slot, and the port number (slot/port) to display information about a specific Ethernet 10BASE-T interface only.

The show version (or show hardware) command displays the configuration of the system hardware (the number of each port adapter type installed), the software version, the names and sources of configuration files, and the boot images. Following is an example of the show version command:

To determine which typew of port adapter are installed in your system, use the show diag command. Specific port adapter information is displayed, as shown in the following example: o:

Proceed to the "Using the ping Command" section to verify that each interface port is functioning properly.

Using the ping Command

The packet internet groper (ping) command allows you to verify that an interface port is functioning properly and to check the path between a specific port and connected devices at various locations on the network. This section provides brief descriptions of the ping command. After you verify that the system has booted successfully and is operational, you can use this command to verify the status of interface ports.

The ping command sends an echo request out to a remote device at an IP address that you specify. After sending a series of signals, the command waits a specified time for the remote device to echo the signals. Each returned signal is displayed as an exclamation point (!) on the console terminal; each signal that is not returned before the specified time-out is displayed as a period (.). A series of exclamation points (!!!!!) indicates a good connection; a series of periods (.....) or the messages [timed out] or [failed] indicate that the connection failed.

Following is an example of a successful ping command to a remote server with the address 1.1.1.10:

If the connection fails, verify that you have the correct IP address for the server and that the server is active (powered on), and repeat the ping command.

Using Configuration Mode

You can configure the 7200 Router manually if you prefer not to use AutoInstall or the prompt-driven System Configuration Dialog.

Take the following steps to configure the Cisco 7200 router manually:

Step 2   When you are prompted to enter the initial dialog, enter no to go into the normal operating mode of the Cisco 7200 router:

Step 3   After a few seconds you will see the user EXEC prompt (Router>). By default, the host name is Router, but the prompt will match the current host name. In the following examples, the host name is aries Enter the enable command to enter enable mode. You can only make configuration changes in enable mode:

Step 4   Enter the configure terminal command at the enable prompt to enter configuration mode:

Step 6   To save the configuration changes to NVRAM, enter the copy running-config startup-config command at the privileged EXEC prompt:

Cisco IOS Software Basics

The section provides you with some basic information about the Cisco IOS software and includes the following sections:

• Cisco IOS Modes of Operation

• Getting Context-Sensitive Help

Cisco IOS Modes of Operation

Cisco IOS software provides access to several different command modes. Each command mode provides a different group of related commands.

For security purposes, Cisco IOS software provides two levels of access to commands: user and privileged. The unprivileged user mode is called user EXEC mode. The privileged mode is called privileged EXEC mode and requires a password. The commands available in user EXEC mode are a subset of the commands available in privileged EXEC mode.

Table 17-1 describes some of the most commonly used modes, how to enter the modes, and the resulting prompts. The prompt helps you identify which mode you are in and, therefore, which commands are available to you.

Getting Context-Sensitive Help

In any command mode, you can get a list of available commands by entering a question mark (?).

To obtain a list of commands that begin with a particular character sequence, type in those characters followed immediately by the question mark (?). Do not include a space. This form of help is called word help, because it completes a word for you.

To list keywords or arguments, enter a question mark in place of a keyword or argument. Include a space before the question mark. This form of help is called command syntax help, because it reminds you which keywords or arguments are applicable based on the command, keywords, and arguments you have already entered.

You can also abbreviate commands and keywords by entering just enough characters to make the command unique from other commands. For example, you can abbreviate the show command to sh.

Saving Configuration Changes

Whenever you make changes to the Cisco 7200 Router configuration, you must save the changes to memory so they will not be lost if there is a system reload or power outage. There are two types of configuration files: the running (current operating) configuration and the startup configuration. The running configuration is stored in RAM; the startup configuration is stored in NVRAM.

To display the current running configuration, enter the show running-config command. Enter the copy running-config startup-config command to save the current running configuration to the startup configuration file in NVRAM.

You can also abbreviate commands and keywords by entering just enough characters to make the command unique from other commands. For example, you can abbreviate the show command to sh.

Posted: Sun Jan 14 18:38:56 PST 2001
All contents are Copyright © 1992--2001 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.