Table of Contents

VIP-4R/4T Installation and Configuration

Product Number VIP-4R/4T(=)

This configuration note is a standalone publication that provides instructions for installing, configuring, and maintaining the Versatile Interface Processor (VIP) in your Cisco 7000 series and Cisco 7500 series routers.

The VIP operates with the CxBus in the Cisco 7000 series and CyBus in the Cisco 7500 series, and requires that the host Cisco 7000 series and Cisco 7500 series router is running Cisco Internetwork Operating System (Cisco IOS) Release 11.1(1) or later, or a Cisco-approved beta version of Cisco IOS Release 11.1.

Included are steps for VIP hardware installation and basic VIP configuration steps and examples for configuring the individual interfaces on a new VIP. Also included are maintenance procedures for upgrading user-configurable VIP components.

This publication has two main sections:

• Versatile Interface Processor Functions—this section discusses general VIP features, maintenance considerations, and overall functions
  
  
• VIP Port Adapter Functions—this section contains subsections that discuss each port adapter and its specific features, configuration and connection requirements, and functions
  
  

You need only refer to the information that is specific to your VIP port adapter configuration or that applies to specific VIP functionality. A table of contents is included on page 2 so you can more easily find what you need.

Table of Contents

This configuration note includes the following sections:

• If You Need More Configuration Information
  
  
• Versatile Interface Processor Functions
  
  
• • What is the VIP?
    
    

• VIP Software Prerequisites
  
  
• VIP Hardware Prerequisites
  
  
• What is the Cisco 7000 Family?
  
  
• VIP Port Adapter Hardware Configuration Overview
  
  
• VIP Microcode Overview
  
  
• VIP Installation Prerequisites
  
  
• VIP Installation
  
  
• Checking the Installation and Verifying VIP Status
  
  
• Upgrading VIP Microcode
  
  
• Upgrading and Replacing DRAM SIMMs
  
  

• VIP Port Adapter Functions
  
  
• • 4R Port Adapter
    
    
  • 4T Port Adapter
    
    
• Cisco Information Online
  
  

If You Need More Configuration Information

The Cisco Internetwork Operating System (Cisco IOS) software running the router contains extensive features and functionality. The effective use of many of many of these features is easier if you have more information at hand.

To obtain general information about documentation, call Customer Service at 800 553-6387 or 408 526-7208. Customer Service hours are 5:00 a.m. to 6:00 p.m. Pacific time, Monday through Friday (excluding company holidays). You can also send e-mail to cs-rep@cisco.com. You can also refer to the Cisco Information Packet that shipped with your router.

For additional information on configuring the Cisco 7000 series or Cisco 7500 series router, the following documentation resources are available to you:

• UniverCD
  
  

  This publication and all other Cisco Systems publications are available on UniverCD, which is Cisco's online library of product information. UniverCD is updated and shipped monthly, so it might be more up to date than printed documentation. To order UniverCD, contact a Cisco Sales or Customer Service representative.

• For systems with Cisco IOS Release 11.1(1), a Cisco-approved 11.1 beta software version, or a later Cisco IOS release, refer to the following modular configuration and modular command reference publications, as appropriate for your configuration:
  
  
• • Configuration Fundamentals Configuration Guide
    
    
  • Configuration Fundamentals Command Reference
    
    
  • Wide-Area Networking Configuration Guide
    
    
  • Wide-Area Networking Command Reference
    
    
  • Network Protocols Configuration Guide
    
    
  • Network Protocols Command Reference
    
    
  • Network Protocols Configuration Guide
    
    
  • Network Protocols Command Reference
    
    
  • Bridging and IBM Networking Configuration Guide
    
    
  • Bridging and IBM Networking Command Reference
    
    
  • Configuration Builder Getting Started Guide
    
    
  • Troubleshooting Internetworking Systems
    
    

Versatile Interface Processor Functions

The following sections describe the Versatile Interface Processor (VIP) and discuss VIP-specific features and functions, such as installing and removing the VIP, installing and removing port adapters, using and configuring common VIP interface functions.

What is the VIP?

The VIP is a new interface processor for use with the Cisco 7000 series and Cisco 7500 series routers, and it installs in the interface processor slots in your Cisco 7000 series or 7500 series router. The VIP uses a single motherboard with up to two port adapters. The VIP port adapters provide the individual LAN, WAN, or LAN/WAN interface ports. The VIP can be removed from a chassis while power is on and the system is operating.

Caution The VIP supports online insertion and removal (OIR), which allows you to remove and replace a VIP without first shutting down the system. Online insertion and removal maximizes router availability by letting you add or remove VIPs during system operation; however, the system may indicate a hardware failure if you fail to follow proper procedures. To help avoid problems with the installation, review the functional description in the section "Online Insertion and RemovalAn Overview" on page 13, and follow the VIP installation steps carefully.

The VIP uses a Reduced Instructions Set Computing (RISC), Mips 4600 processor for high performance, and has an internal operating frequency of 100 megahertz (MHz) and a 50-MHz system bus interface. The VIP has 8 megabytes (MB) of dynamic random access memory (DRAM) as the default DRAM configuration.

Figure 1 shows a VIP-4R/4T. The VIP firmware (microcode), which contains card-specific software instructions, resides in a Flash memory device in socket location U17. Single in-line memory modules contain the DRAM. For connector pinouts, refer to the section "4R Port Adapter Receptacles, Cables, and Pinouts" on page 34, or to the section "4T Port Adapter Receptacles, Cables, and Pinouts" on page 51. You can install VIPs in any available interface processor slots.

VIP Software Prerequisites

The VIP requires that the host Cisco 7000 series and Cisco 7500 series router is running Cisco Internetwork Operating System (Cisco IOS) Release 11.1(1) or later, or a Cisco-approved beta version of Cisco IOS Release 11.1.

VIP Hardware Prerequisites

The VIP operates with the CxBus in the Cisco 7000 series and CyBus in the Cisco 7500 series, and operates with the optional RSP7000 and RSP7000CI RSP-based processor modules in the Cisco 7000 series routers: Cisco 7000 and Cisco 7010. The VIP will also operate with the Route Processor (RP) and Switch Processor (SP) in the Cisco 7000 series routers. The VIP operates with all RSP-based processor modules currently shipping in the Cisco 7000 series and Cisco 7500 series routers: Cisco 7505, Cisco 7507, and Cisco 7513.

What is the Cisco 7000 Family?

For the Cisco 7000 family of routers, which includes the Cisco 7000 series and Cisco 7500 series routers, network interfaces reside on modular interface processors, including the VIP, which provide a direct connection between external networks and the high-speed CxBus in the Cisco 7000 series and the high-speed CyBus in the Cisco 7500 series.

In all systems, the remaining slots support any combination of network interface types: Ethernet attachment unit interface (AUI), Ethernet 10BASE-T, Fast Ethernet 100BASE-TX, Asynchronous Transfer Mode (ATM), Token Ring, multichannel applications, Fiber Distributed Data Interface (FDDI), channel attachment, serial, or High-Speed Serial Interface (HSSI), and all VIP-based interfaces.

Cisco 7000 Series

Figure 2 and Figure 3 show the rear of the Cisco 7000 series routers: the seven-slot Cisco 7000 and the five-slot Cisco 7010, respectively. In the Cisco 7000 series, two slots are reserved for the SP (or SSP) and RP, or for the 7000 Series Route Switch Processor (RSP7000) and the 7000 Series Chassis Interface (RSP7000CI). The remaining slots are for interface processors: slots 0 through 4 in the Cisco 7000, and slots 0 through 2 in the Cisco 7010.

Cisco 7500 Series

Figure 4, Figure 5, and Figure 6 show the rear of the Cisco 7500 series routers: the five-slot Cisco 7505, the seven-slot Cisco 7507, and the thirteen-slot Cisco 7513, respectively.

In the Cisco 7505, one slot (4) is reserved for the Route Switch Processor (RSP1), which contains the system processor and performs packet switching functions. Slots 0 through 3 are for interface processors.

Figure 5 shows the rear of the seven-slot Cisco 7507 router. In the Cisco 7507, up to two slots (2 and 3) are reserved for the Route Switch Processor (RSP2), which contains the system processor and performs packet switching functions. Slots 0 and 1 and 4 through 6 are for interface processors.

Figure 6 shows the rear of the Cisco 7513 with two AC-input power supplies installed. Two slots (6 and 7) are reserved for the second generation Route Switch Processor (RSP2), which contains the system processor and performs packet switching functions. Slots 0 through 5 and 8 through 12 are for interface processors.

VIP Port Adapter Hardware Configuration Overview

The port adapters attach to the VIP motherboard. (See Figure 7.) Each port adapter contains the physical connections for the VIP interface types to connect to your network.

Following are the VIP port adapters by interface type:

• Ethernet 10BASE-T—4E
  
  
• Fast Ethernet 100BASE-TX—FE-TX
  
  
• Synchronous serial—4T
  
  
• Token Ring—4R
  
  

Following are the supported electrical interfaces:

• 4E port adapter—10BASE-T Ethernet, using RJ-45
  
  
• FE-TX port adapter—IEEE 802.3u Fast Ethernet 100BASE-TX, using Media Independent Interface (MII) or RJ-45
  
  
• 4T port adapter—synchronous serial (EIA/TIA-232, EIA-TIA-449, EIA-530, V.35, and X.21; determined by the cable), using DB-60, 60-pin mini-D-sub connectors
  
  
• 4R port adapter—IEEE 802.5 Token Ring, using DB-9, 9-pin D-sub connectors
  
  

	Caution To prevent system problems, do not remove port adapters from the VIP motherboard or attempt to install other port adapters on the VIP motherboard.

VIP Microcode Overview

The VIP microcode (firmware) is an image that provides card-specific software instructions. A Flash memory device in socket U17 of the VIP contains the default microcode boot image. The router supports downloadable microcode, which enables you to upgrade microcode versions by downloading new microcode images, storing them in system Flash memory, and instructing the system to load its image from Flash instead of the default VIP image. (The RP in the Cisco 7000 and 7010 loads software from ROM or Flash memory; the RSP loads software from Flash only.) You can store multiple images for an interface type and, with a configuration command, instruct the system to load any one of them or the default ROM image. All interfaces of the same type (VIP, and so on) will load the same microcode image, either from the default ROM image or from a single image stored in system Flash. Although multiple microcode versions for a specific interface type can be stored concurrently in Flash, only one image can load at startup. The show controllers cbus command displays the currently loaded and running microcode version for the SP or SSP (in the Cisco 7000 series routers), each interface processor, and VIP. The show startup-config EXEC command shows the current system instructions for loading microcode at startup.

Software and interface processor microcode images are carefully optimized and bundled to work together. Overriding the bundle can result in system incompatibilities. We recommend that you use the microcode included in the software bundle. For a complete description of microcode and downloading procedures, refer to the section "Upgrading VIP Microcode" on page 23.

VIP Installation Prerequisites

This section provides a list of parts and tools you will need to perform the VIP installation, and it also includes safety and ESD-prevention guidelines to help you avoid injury and damage to the equipment. This section also provides a detailed description of the OIR function to help you perform online installation successfully and avoid error message and system restarts. If you are installing a new VIP, be sure to review the equipment descriptions and distance limitations in the port adapter sections "Serial Distance Limitations" and "Token Ring Distance Limitations" when preparing your site and planning network connections.

List of Parts and Tools

You need the following tools and parts to install or upgrade a VIP. If you need additional equipment, contact a service representative for ordering information.

• Cables appropriate for the port adapter interfaces on your VIP
  
  
• Number 1 Phillips and a 3/16-inch, flat-blade screwdriver
  
  
• Your own ESD-prevention equipment or the disposable grounding wrist strap included with all upgrade kits, FRUs, and spares
  
  

Safety Guidelines

Following are safety guidelines that you should follow when working with any equipment that connects to electrical power or telephone wiring.

Electrical Equipment Guidelines

Follow these basic guidelines when working with any electrical equipment:

• Before beginning any procedures requiring access to the chassis interior, locate the emergency power-off switch for the room in which you are working.
  
  
• Disconnect all power and external cables before moving a chassis.
  
  
• Do not work alone when potentially hazardous conditions exist.
  
  
• Never assume that power has been disconnected from a circuit; always check.
  
  
• Do not perform any action that creates a potential hazard to people or makes the equipment unsafe.
  
  
• Carefully examine your work area for possible hazards such as moist floors, ungrounded power extension cables, and missing safety grounds; correct all hazardous conditions.
  
  

Telephone Wiring Guidelines

Use the following guidelines when working with any equipment that is connected to telephone wiring or to other network cabling:

• Never install telephone wiring during a lightning storm.
  
  
• Never install telephone jacks in wet locations unless the jack is specifically designed for wet locations.
  
  
• Never touch uninsulated telephone wires or terminals unless the telephone line has been disconnected at the network interface.
  
  
• Use caution when installing or modifying telephone lines.
  
  

Preventing Electrostatic Discharge Damage

Electrostatic discharge (ESD) damage, which can occur when electronic cards or components are improperly handled, results in complete or intermittent failures. A processor module comprises a printed circuit board that is fixed in a metal carrier. Electromagnetic interference (EMI) shielding, connectors, and a handle are integral components of the carrier. Although the metal carrier helps to protect the board from ESD, use a preventive antistatic strap whenever handling a processor module.

Following are guidelines for preventing ESD damage:

• Always use an ESD wrist or ankle strap and ensure that it makes good skin contact.
  
  
• Connect the equipment end of the strap to a captive installation screw on an installed power supply.
  
  
• When installing a processor module, use the ejector levers to properly seat the bus connectors in the backplane, then tighten both captive installation screws. (See Figure 8.) These screws prevent accidental removal, provide proper grounding for the system, and help to ensure that the bus connectors are seated in the backplane.
  
  
• When removing a processor module, use the ejector levers to release the bus connectors from the backplane. Use the handle to pull the processor module out slowly while keeping your other hand underneath the carrier to guide it straight out of the slot.
  
  
• Handle carriers by the handles and carrier edges only; avoid touching the board or connectors.
  
  
• Place a removed processor module board-side-up on an antistatic surface or in a static shielding bag. If you plan to return the component to the factory, immediately place it in a static shielding bag.
  
  
• Avoid contact between the processor module and clothing. The wrist strap only protects the board from ESD voltages on the body; ESD voltages on clothing can still cause damage.
  
  
• Never attempt to remove the printed circuit board from the metal interface processor carrier.
  
  

	Caution For safety, periodically check the resistance value of the antistatic strap. The measurement should be between 1 and 10 megohms.

Online Insertion and Removal—An Overview

The OIR feature allows you to remove and replace a VIP board while the system is operating; you do not need to notify the software or shut down the system power.

This section describes mechanical functions of system components, emphasizes the importance of following correct procedures to avoid unnecessary board failures, and is for background only; specific VIP procedures follow in the section "VIP Installation" on page 16.

Each interface processor contains a receptacle with which it connects to the system backplane. Each backplane connector comprises a set of tiered pins, in three lengths. The pins send specific signals to the system as they make contact with the card. The system assesses the signals it receives and the order in which it receives them to determine what event is occurring and what task it needs to perform, such as reinitializing new interfaces or shutting down removed ones.

For example, when inserting an interface processor, the longest pins make contact with the backplane first, and the shortest pins make contact last. The system recognizes the signals and the sequence in which it receives them. The system expects to receive signals from the individual pins in this logical sequence, and the ejector levers help to ensure that the pins mate in this sequence.

When you remove or insert an interface processor, the backplane pins send signals to notify the system, which then performs as follows:

The system brings on line only interfaces that match the current configuration and were previously configured as up; all others require that you configure them with the configure command. OIR functionality enables you to add, remove, or replace interface processors with the system online, which provides a method that is seamless to end users on the network, maintains all routing information, and ensures session preservation.

The function of the ejector levers (see Figure 8) is to align and seat the card connectors in the backplane. Failure to use the ejector levers and insert the interface processor properly can disrupt the order in which the pins make contact with the card or interface processor. Follow the VIP installation and removal instructions carefully, and review the following examples of incorrect insertion practices and their results:

• Using the handle to force the interface processor all the way into the slot can pop the ejector levers out of their springs. If you then try to use the ejector levers to seat the interface processor, the first layer of pins (which are already mated to the card or interface processor) can disconnect and then remate with the backplane, which the system interprets as a board failure.
  
  
• Using the handle to force or slam the interface processor all the way into the slot can damage the pins on the board connectors if they are not aligned properly with the backplane.
  
  
• When using the handle (rather than the ejector levers) to seat the interface processor in the backplane, you might need to pull the interface processor back out and push it in again to align it properly. Even if the backplane pins are not damaged, the pins mating with and disconnecting from the card or interface processor will cause the system to interpret a board failure. Using the ejector levers ensures that the board connector mates with the backplane in one continuous movement.
  
  
• Using the handle to insert or remove an interface processor, or failing to push the ejector levers fully against the interface processor, can leave some (not all) of the connector pins mated to the card or interface processor, a state which will hang the system. Using the ejector levers and making sure that they are pushed fully into position ensures that all three layers of pins are mated with (or free from) the backplane.
  
  

It is also important to use the ejector levers when removing an interface processor to ensure that the backplane connector pins disconnect from the card or interface processor in the logical sequence expected by the system. Any interface processor that is only partially connected to the backplane can hang the bus. Detailed steps for correctly performing OIR are included with the following procedures for installing and removing the VIP.

VIP Installation

The following sections describe the procedures for removing or installing a VIP in the Cisco 7000 series and Cisco 7500 series routers. The functionality is the same for each router model; therefore, the term the chassis will be used except where specific model issues arise. The OIR function allows you to install and remove a VIP without first shutting down the system; however, you must follow the instructions carefully. Failure to insert the VIP properly can cause system error messages indicating a board failure. For a complete description of OIR, refer to the section "Online Insertion and RemovalAn Overview" on page 13.

Each unused interface processor slot contains an interface processor filler (which is an interface processor carrier without an interface board) to keep dust out of the chassis and to maintain proper air flow through the interface processor compartment. If you are installing a new VIP that is not a replacement, you must first remove the interface processor filler from an unused slot; proceed to the next section "Removing an Interface Processor Filler." If you are replacing a VIP or upgrading the microcode Flash EPROM on a VIP, proceed to the section "Removing a VIP."

	Caution If you use the VIP with a single port adapter, the port adapter must be in slot 0 for the VIP to function properly. A single port adapter in slot 1 will not be recognized by the system.

Removing an Interface Processor Filler

Select an unused interface processor slot for the new VIP and remove the interface processor filler as follows:

Step 1   Choose an available slot for the VIP and make a note of it.

Step 1   Use a screwdriver to loosen the captive installation screws on the interface processor filler. (See Figure 8.)

Step 2   Place your thumbs on both ejector levers and simultaneously pull them both outward to release the VIP from the backplane connector (in the opposite direction from that shown in Figure 8c).

Step 3   Grasp the handle with one hand and pull the filler straight out of the slot, keeping your other hand under the carrier to guide it. (See Figure 9.) Keep the carrier parallel to the backplane.

Step 4   Store the interface processor filler for future use.

To help prevent dust and contaminants from entering the chassis, do not leave the interface processor slot open. Immediately proceed to the section "Installing a VIP" on page 18.

Removing a VIP

Remember, the VIP supports OIR; therefore, you need not shut down the interface or the system power when removing a VIP. If you are replacing a failed VIP, remove the existing board first, then replace the new VIP in the same slot.

Figure 9 shows proper handling of an interface processor during installation.

To remove a VIP, follow these steps:

Step 1   If you are replacing a failed VIP, disconnect all cables from the VIP ports; however, if you are only moving a VIP to another slot, this step is not necessary.

Step 2   Use a screwdriver to loosen the captive installation screws at both ends of the VIP. (See Figure 8.)

	Caution Always use the ejector levers to remove or install the VIP. Failure to do so can cause erroneous system error messages indicating a board failure.

Step 3   Place your thumbs on the ejector levers and simultaneously pull both of the ejectors outward (in the opposite direction from that show in Figure 8c) to release the VIP from the backplane connector.

Step 4   Use the VIP handle to carefully pull the VIP straight out of the slot, keeping your other hand under the carrier to guide it. (See Figure 9.) Keep the VIP parallel to the backplane.

Step 5   Place the removed VIP on an antistatic mat or foam pad, or place it in an antistatic bag if you plan to return it to the factory.

Step 6   If the interface processor slot is to remain empty, install a filler (MAS7K-BLANK) to keep dust out of the chassis and to maintain proper air flow inside the chassis. Do not leave the interface processor slot open. Immediately proceed to the section "Installing a VIP."

Installing a VIP

The VIP slides into the open interface processor slot and connects directly to the backplane. The interface processors are keyed to guide pins on the backplane, so the VIP can be installed only in an interface processor slot. Figure 8 shows the functional details of inserting an interface processor and using the ejector levers. Figure 9 shows proper handling of an interface processor during installation.

	Caution Remove or insert only one interface processor at a time. Allow at least 15 seconds for the system to complete its discovery and initialization before removing or inserting another interface processor. Disrupting the sequence before the system has completed verification can cause the system to interpret hardware failures.

Follow these steps to install a VIP:

Step 1   Ensure that a console terminal is connected to the console port (on the RP or RSP) and that your console is turned ON.

Step 2   Hold the VIP handle with one hand and place your other hand under the carrier to support the VIP and guide it into the slot. (See Figure 9.) Avoid touching the card or any connector pins.

	Caution To prevent ESD damage, handle interface processors by the handles and carrier edges only.

Step 3   Place the back of the VIP in the slot and align the notch on the carrier with the groove in the slot. (See Figure 8.)

Step 4   While keeping the VIP parallel to the backplane, carefully slide it into the slot until the back of the faceplate makes contact with the ejector levers, then stop. (See Figure 8b.)

	Caution Always use the ejector levers when installing or removing processor modules. A module that is partially seated in the backplane will cause the system to hang and subsequently crash, and shoving or slamming the interface processor into the slot can damage the backplane pins and board.

Step 5   Using your thumbs, simultaneously push both ejector levers inward until the VIP is pushed entirely into its slot. (See Figure 8c.)

Step 6   Tighten both of the captive installation screws.

Checking the Installation and Verifying VIP Status

You can use the configure command to configure a VIP interface. To use the configure command, enter the privileged level of the EXEC command interpreter with the enable command. The system will prompt you for a password if one has been set.

The system prompt for the privileged level ends with a pound sign (#) instead of an angle bracket (>). At the console terminal, enter the privileged level as follows:

Step 1   At the user-level EXEC prompt, enter the enable command. The EXEC prompts you for a privileged-level password, as follows:

Router> enable

Password:
 

Step 2   Enter the password (the password is case sensitive). For security purposes, the password is not displayed on your console.

Step 3   When you enter the correct password and press Return, the system displays the privileged-mode system prompt (#) as follows:

Router#

Checking the VIP Installation

After you install the VIP and connect cables (using connection procedures in the respective port adapter subsections), verify the installation by observing the LED states and the console display. When the system has reinitialized all interfaces, the enabled LED on the VIP and on all interface processors should go on. One or the other of the MII and RJ-45 LEDs should be on, depending on your connection, and the link LED should be on if the VIP is receiving a carrier signal from the network.

The console screen will also display a message as the system discovers each interface during its reinitialization.

When you remove and replace interface processors, the system provides status messages on the console screen. The messages are for information only.

The following sample display shows the events logged by the system as a serial-equipped VIP was removed from slot 2; the system then reinitialized the remaining interface processors and marked as down the serial interfaces on the VIP that was removed from slot 2. When the VIP is reinserted, the system automatically brings up the interfaces that were up when the VIP was removed.

Router# 
%OIR-6-REMCARD: Card removed from slot 2, interfaces disabled
%LINK-5-CHANGED: Interface Serial2/1/0, changed state to administratively down
%LINK-5-CHANGED: Interface Serial2/1/1, changed state to administratively down
 
Router#
%OIR-6-INSCARD: Card inserted in slot 2, interfaces administratively shut down
%LINK-5-CHANGED: Interface Serial2/1/0, changed state to up
%LINK-5-CHANGED: Interface Serial2/1/1, changed state to up

The following example display shows the events logged by the system as a new VIP is inserted in slot 3. (Serial interfaces are used in the following examples.)

Router#
%OIR-6-INSCARD: Card inserted in slot 3, interfaces administratively shut down
%LINK-5-CHANGED: Interface Serial3/1/0, changed state to administratively down
%LINK-5-CHANGED: Interface Serial3/1/1, changed state to administratively down
 

Verify that the VIP is installed correctly as follows:

Step 1   While the system reinitializes each interface, observe the console display messages and verify that the system discovers the VIP as follows:

• If you installed a new VIP, the system should recognize all new interfaces but leave them configured as down.
  
  
• If you replaced a VIP, the system should recognize each interface and place it in the same state (up or down) each was in when you removed the VIP.
  
  

Step 2   When the reinitialization is complete, verify that the enabled LED on each port adapter goes on and remains on. If it does, proceed to step 5. If it does not, proceed to the next step.

Step 3   If the enabled LED on a port adapter fails to go on, suspect that the VIP board connector is not fully seated in the backplane. Loosen the captive installation screws, then firmly push both ejector levers into place until they are approximately in the same orientation as the VIP faceplate. Tighten the captive installation screws. After the system reinitializes the interfaces, the enabled LED on the port adapter should go on. If it does, proceed to Step 5. If it does not, proceed to Step 4.

Step 4   If the enabled LED still fails to go on, remove the VIP and try installing it in another available interface processor slot.

• If the enabled LED goes on when the VIP is installed in the new slot, suspect a failed backplane port in the original interface processor slot.
  
  
• If the enabled LED still fails to go on, but other LEDs on the VIP go on to indicate activity, proceed to Step 5 to resume the installation checkout and suspect that the enabled LED on the port adapter has failed.
  
  
• If no LEDs on the VIP go on, suspect that the VIP is faulty.
  
  
• If the enabled LED still does not go on, do not proceed with the installation. Contact a service representative to report the problem and obtain further instructions.
  
  

Step 5   If the VIP is new and not a replacement, you have to configure the new interfaces. Proceed to the appropriate configuration section for your port adapter. (This does not have to be done immediately, but new interfaces will not be available until you configure them.)

Step 6   If the VIP is a replacement, use the show interfaces type slot/port adapter/port or show controllers cbus command to verify the status of the interfaces. (Refer to the section "Verifying VIP Status Using show Commands" on page 21.)

If you replaced a VIP with a new VIP with a greater number of ports (for example, if you replaced a one-port VIP with a two-port VIP), the system will recognize the first interface, but will not recognize the additional interface. The new interface will remain in the shutdown state until you configure it.

Step 7   When the interfaces are up, check the activity of each interface by observing the status LEDs, which are described in the appropriate LED section for your port adapter type.

Step 8   In general, if an interface's LED fails to go on and a cable is connected to the port, check the cable connection and make certain it is properly seated in the connector.

If an error message is displayed on the console terminal, refer to the System Error Messages publication for error message definitions. If you experience other problems that you are unable to solve, contact a service representative for assistance.

This completes the VIP installation. If you installed a new VIP or if you installed a replacement VIP with an additional port, you must now configure the new interface as described in the following section.

Verifying VIP Status Using show Commands

The following procedure describes how to use the show commands to verify that the new interfaces are configured correctly:

Step 1   Use the show version or show hardware commands to display the system hardware configuration. Ensure that the list includes the new interfaces.

Step 2   Display all of the current interface processors and their interfaces with the show controllers cbus command. Verify that the new VIP appears in the correct slot.

Step 3   Specify one of the new VIP interfaces with the show interfaces type slot/port adapter/port 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 command show protocols. 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 write terminal (or show running-config) command. Display the configuration stored in NVRAM using the show config (or 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.

The show controllers cbus command displays the internal status of each interface processor, including the slot location, the card hardware version, and the currently-running microcode version. It also lists each interface (port) on each interface processor including the logical interface number, interface type, physical (slot/port adapter/port) address, and hardware (station address) of each interface. The following example shows a VIP, with serial interfaces, installed in interface processor slot 3:

Router# show controller cbus 

 
(display text omitted)
slot3: VIP, hw 2.1, sw 200.09, ccb 5800FF70, cmdq 480000A0, vps 8192
    software loaded from system
    FLASH ROM version 255.255, VPLD version 20.0
    4T HW Revision 121, SW Revision 216, Unresponsive 0
    Serial3/1/0, addr 0000.0ca5.2380 (bia 0000.0ca5.2380)
      gfreeq 48000140, lfreeq 48000238 (1536 bytes), throttled 0
      rxlo 4, rxhi 123, rxcurr 16, maxrxcurr 16
      txq 48000240, txacc 480000EA (value 77), txlimit 77
    Serial3/1/1, addr 0000.0ca5.238e (bia 0000.0ca5.238e)
      gfreeq 48000140, lfreeq 48000238 (1536 bytes), throttled 0
      rxlo 4, rxhi 123, rxcurr 16, maxrxcurr 16
      txq 48000240, txacc 480000EA (value 77), txlimit 77
 
(display text omitted)
 

The show startup-config command displays the contents of the system configuration file stored in NVRAM. This file should reflect all new configuration changes you made and wrote to memory with the show running-config command. (A serial interface is used in this example.)

Router# show startup-config

 
Using 1652 out of 130048 bytes
version 11.1(1)
!
hostname Router
!
enable-password hello
!
microcode VIP flash VIP11-0
microcode reload
!
(display text omitted)
!
interface serial 3/1/0
ip address 1.1.1.1 255.255.255.248
ip route-cache cbus
!
(display text omitted)
 

The show protocols command displays the global (system-wide) and interface-specific status of any configured Level 3 protocol.

Router# show protocols

 
Global values:
  Internet Protocol routing is enabled
Serial3/1/0 is up, line protocol is up

Upgrading VIP Microcode

The Cisco 7000 series and the Cisco 7500 series support downloadable microcode, which enables you to upgrade microcode versions without having to physically replace the microcode Flash memory device on the board. You can download new microcode versions and store multiple versions in Flash memory, and you can boot from them just as you can with the system software images. System software upgrades may also contain upgraded microcode images, which will load automatically when the new software image is loaded (unless the configuration states otherwise).

You can download microcode to Flash memory by copying the TFTP image of a microcode version to Flash memory. When the microcode image is stored in Flash memory you can use the microcode reload command to manually load the new microcode file, and the configure command to instruct the system to load the new image automatically at each system boot.

To compare the size of the microcode image and the amount of Flash memory available, you must know the size of the new microcode image. The image size is specified in the README file that is included on the floppy disk with the new image.

	Caution Before you copy a file to system Flash memory, be sure there is ample space available in Flash memory. Compare the size of the file you want to copy to the amount of available Flash memory shown. If the space available is less than the space required by the file you want to copy, the copy process will continue, but the entire file will not be copied into Flash memory.

Follow these steps to download (copy) a microcode version from a TFTP server to Flash memory.

Step 1   To display the total amount of Flash memory present, its location, any files that currently exist in Flash memory and their size, and the amount of Flash memory remaining, use the show flash command. Following is an example of the output that is displayed:

Router# show flash

 
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1   .. FFFFFFFF B4A18E0B 3F6494  30   4023316  Jun 26 1994 19:44:29 image/file/1
2   .. FFFFFFFF 8075AA5D 4118B4  23   111518   Jun 29 1994 11:05:57 image/file/2
 
12044568 bytes available (8533736 bytes used)
 

Step 2   Compare the amount of available Flash memory (last line in the preceding example) to the size of the new microcode image on the floppy disk. If you attempt to copy in a new image, and the size of the new image exceeds the available space in Flash, only part of the new image will be copied, and the following error message will be displayed:

buffer overflow - xxxx/xxxx
 

where xxxx/xxxx is the number of bytes read in/number of bytes available.

Step 3   After you verify that there is sufficient space available in Flash memory for the new image, use the command copy tftp:filename [ flash | slot0 | slot1 ]:filename to copy an image to Flash memory. (tftp:filename is the file's source, and [ flash | slot0 | slot1 ]:filename is the destination in onboard Flash memory or on either of the Flash memory cards.)

An example of the copy tftp:filename command follows:

Router# copy tftp:vip11-1 slot0:vip11-1

20575008 bytes available on device slot0, proceed? [confirm]
Address or name of remote host [1.1.1.1]?
Loading new.image from 1.1.1.1 (via Ethernet1/0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 7799951/15599616 bytes]
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
Router#
 

Step 4   Use the show flash command to verify that the microcode has been copied to Flash. The output should display the filename of the image you copied to Flash (vip11-1 in the following example):

Router# show flash

 
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1   .. FFFFFFFF B4A18E0B 3F6494  30   4023316 Jun 26 1994 19:44:29 image/file/1
2   .. FFFFFFFF 8075AA5D 4118B4  23   111518   Jun 29 1994 11:05:57 image/file/2
3   .. FFFFFFFF EEA1FEEB 8436E8  22   4398516  Oct 10 1995 19:35:25 vip11-1
 
7646052 bytes available (16179788 bytes used)

Step 5   To ensure that the new microcode is used when you reboot the system, add the appropriate commands to the configuration file. To modify the configuration file, enter the configure terminal command, as follows:

Router# config t

Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)#
 

Step 6   Specify that you are changing the microcode for the VIP (microcode vip), and that it will load from Flash memory (flash). Then add the filename of the new microcode image to be loaded from Flash:

Router(config)# microcode vip flash slot0:vip11-1

 

Step 7   To save the configuration file, press Ctrl-Z.

Step 8   Copy the new configuration to nonvolatile random-access memory (NVRAM):

Router# copy running-config startup-config

 

The microcode reload command is automatically added to your running configuration. The new VIP microcode image will load automatically the next time the system boots or reinitializes.

Step 9   To load the new microcode immediately, you can issue the microcode reload configuration command (you must be in Configuration mode to enter this command):

Router# config t

Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)# microcode reload

 

Immediately after you enter the microcode reload command and press Return, the system reloads all microcode. Configuration mode remains enabled; after the reload is complete, press Ctrl-Z to exit from Configuration mode and return to the system prompt.

Step 10   To verify that the VIP is using the correct microcode, issue the show startup-config or show controllers cbus command, which indicates the currently loaded and running microcode version for each interface processor and the SP or SSP in the Cisco 7000 series routers.

Router# show controllers cbus

 

This completes the procedure for downloading microcode to Flash memory.

Upgrading and Replacing DRAM SIMMs

VIPs are shipped with 8 megabytes (MB) of dynamic random-access memory (DRAM) as the default DRAM configuration. Depending on memory requirements, you might need to upgrade the amount of DRAM by replacing the DRAM SIMMs on the VIP. You also might need to replace a single SIMM in the case of a diagnosed DRAM SIMM failure.

	Caution SIMMs are sensitive components that are susceptible to ESD damage. Handle SIMMs by the edges only; avoid touching the memory modules, pins, or traces (the metal fingers along the connector edge of the SIMM). (See Figure 10.)

Following is the procedure for replacing or upgrading DRAM SIMMs.

Step 1   Attach an ESD-preventive wrist strap between you and an unpainted chassis or VIP surface.

Step 2   Disconnect all cables from the VIP and remove it from the chassis using the procedure in the section "Removing a VIP" on page 16.

Step 3   Place the VIP on a flat surface (preferably an antistatic mat or foam), and turn it so the face plate is away from you and the connector edge is toward you. (approximately opposite of the orientation shown in Figure 11).

Step 4   Locate the DRAM SIMMs in U1 and U2. (See Figure 11.)

Step 5   Remove a SIMM by pulling outward on the connectors to unlatch it, as shown in the enlargement in Figure 12. Be careful not to break the holders on the SIMM connector.

Step 6   Using the SIMM orientation shown in Figure 12, position the new SIMM so that the polarization notch is located at the right end of the SIMM socket.

Step 7   Insert the new SIMM by sliding the end with the metal fingers into the SIMM connector socket at approximately a 45-degree angle to the system card. Gently rock the SIMM back into place until the latch on either side snaps into place. (See Figure 12.)

	Caution Do not use excessive force, or the connector could break. To prevent damage, do not push on the center of the SIMMs. Handle each SIMM with care.

Step 8   As required, repeat Steps 5 through 7 for the second SIMM.

Step 9   Reinstall the VIP in the chassis using the procedure in the section "Installing a VIP" on
page 18.

If error messages relating to memory are displayed once power to the chassis is turned back on, or the VIP card is installed in a chassis that is already on, repeat Steps 1 through 8, taking care to firmly reseat each SIMM in its socket.

This completes the procedure for upgrading or replacing DRAM SIMMs on your VIP.

VIP Port Adapter Functions

The following sections discuss the port adapters used with the VIP:

• 4R Port Adapter
  
  
• 4T Port Adapter
  
  

4R Port Adapter

The following sections discuss the 4R port adapter, which is shown in Figure 13.

• Token Ring Overview
  
  
• Token Ring Specifications and Physical Connections
  
  
• Token Ring Connection Equipment
  
  
• Token Ring Distance Limitations
  
  
• Token Ring Speed Considerations
  
  
• 4R Port Adapter LEDs
  
  
• 4R Port Adapter Receptacles, Cables, and Pinouts
  
  
• Attaching 4R Port Adapter Interface Cables
  
  
• Configuring the 4R Interfaces
  
  

The 4R port adapter (see Figure 13) is currently available on the VIP-4R/4T, which has two port adapter slots: port adapter slot 0 and port adapter slot 1. The 4R port adapter, which is installed in port adapter slot 0, provides up to four IBM Token Ring or IEEE 802.5 Token Ring interfaces. Each Token Ring interface can be set for 4 Mbps or 16 Mbps. All Token Ring ports run at wire speed.

Token Ring Overview

The following sections describe Token Ring specifications, physical connections, connection equipment, and cables and connectors. Figure 14 shows the 4R port adapter installed on the VIP-4R/4T.

Token Ring Specifications and Physical Connections

The term Token Ring refers to both IBM's Token Ring Network, which IBM developed in the 1970s, and to IEEE 802.5 networks. The IEEE 802.5 specification was modeled after, and still closely shadows, IBM's network. The two types are compatible, although the specifications differ slightly.

Token Ring and IEEE 802.5 are token passing networks, which move a small frame, called a token, around the network. Possession of the token grants the right to transmit; a station with information to transmit must wait until it detects a free token passing by.

The IBM Token Ring specifies a star topology, with all end stations connected through a device called a multistation access unit (MSAU). IEEE 802.5 does not specify any topology, although most implementations are based on a star configuration with end stations attached to a device called a media access unit (MAU). Also, IBM Token Ring specifies twisted-pair cabling, whereas IEEE 802.5 does not specify media type. Most Token Ring networks use shielded twisted-pair cabling; however, some networks that operate at 4 Mbps use unshielded twisted-pair cable. Table 1 shows a comparison of the two types.

All 4R port adapter interfaces support both 4- and 16-Mbps operation and early token release. The default for all ports is for 4-Mbps operation and early token release disabled. Both states are enabled with configuration commands in Configuration mode.

To enable 16 Mbps, specify the slot/port address and use the configuration command ring-speed 16; to return to 4 Mbps operation, use the command ring-speed 4. To enable and disable early token release, specify the slot/port address and use the configuration command [no] early token release. For complete descriptions and examples of software commands, refer to the related software configuration documentation.

In the typical Token Ring network shown in Figure 15, lobe cables connect each Token Ring station (4R port adapter interface) to the MSAU (or MAU), and patch cables connect adjacent MSAUs (or MAUs) to form one large ring.

Token Ring Connection Equipment

You will need an 802.5 MAU or an MSAU to provide the interface between the 4R port adapter Token Ring interfaces and the external ring, and a Token Ring lobe cable between each 4R port adapter interface and the MAU or MSAU. Lobe cables connect each Token Ring station (4R port adapter interface) to the MAU or MSAU, and patch cables can connect adjacent MSAUs to form one large ring.

4R port adapter interfaces operate at either 4 or 16 Mbps. The default speed for all 4R port adapter interfaces is 4 Mbps, which you can change to 16 Mbps on any port using the ring-speed n configuration command, where n is the speed (4 or 16) in Mbps. The speed of each Token Ring port must match the speed of the ring to which it is connected. Before you enable the Token Ring interfaces, ensure that each is set for the correct speed, or it can bring down the ring.

	Caution Each 4R port adapter interface must be configured for the same ring speed as the ring to which it is connected, either 4 or 16 Mbps. If the port is set for a different speed, it will cause the ring to beacon, which effectively brings the ring down and makes it inoperable.

Token Ring Distance Limitations

The maximum transmission distance is not defined for IEEE 802.5 (Token Ring) networks. Shielded twisted-pair (STP) cabling is most commonly used for rates of 4 and 16 Mbps. Twisted-pair cabling is more susceptible to interference than other types of cabling; therefore, the network length and repeater spacing should be planned accordingly.

Token Ring Speed Considerations

Before you install the 4R port adapter, determine the ring speed (4 or 16 Mbps) of each ring to be connected to the server. There is no factory default for the interface speed; you must set the speed of each interface (within the setup command facility or with the ring-speed command) before you bring the interface up and insert it into the ring with the no shutdown command.

4R Port Adapter LEDs

The 4R port adapter's enabled LED (shown in Figure 16) goes on to indicate the following status of the 4R port adapter:

• Enabled for operation
  
  
• Correctly connected to the VIP card
  
  
• Receiving power from the VIP card
  
  
• Contains a valid microcode version
  
  

If any of these conditions is not met, or if the initialization fails for other reasons, the port adapter's enabled LED does not go on.

When a Token Ring interface is configured by using software commands, two additional LEDs for each port indicate the following:

• In ring—Goes on when the interface is currently active and inserted into the ring; off when the interface is not active and is not inserted into a ring.
  
  
• 4/16 Mbps—Goes on if the interface is operating at 16 Mbps; off when the interface is operation at 4 Mbps.
  
  

4R Port Adapter Receptacles, Cables, and Pinouts

A network interface cable provides the connection between the 9-pin Token Ring receptacles on the 4R port adapter and a media access unit (MAU). The 9-pin connector at the 4R port adapter end, and the MAU connector at the network end, are described in the section "Token Ring Connection Equipment" on page 32.

4R Port Adapter Receptacles and Cables

The Token Ring ports on the 4R port adapter are DB-9 (PC type) receptacles that require Type 1 or Type 3 lobe cables. Token Ring interface cables are not available from Cisco Systems, but are commercially available through outside cable vendors. Type 1 lobe cables use shielded twisted-pair (STP) cable and terminate at the network end with a large MAU plug. (See Figure 17.) The 4R port adapter end of the cable is a DB-9 plug.

Type 3 lobe cables use either shielded or unshielded twisted-pair (UTP) cable and terminate at the network end with an RJ-11 plug. (See Figure 18.) The 4R port adapter end of the cable is a DB-9 plug.

4R Port Adapter Receptacle Pinout

Table 2 lists the pinout for the DB-9 receptacle used on the 4R port adapter.

Attaching 4R Port Adapter Interface Cables

The Token Ring ports on the 4R port adapter run at either 4- or 16 Mbps. You need one Token Ring interface cable for each 4R port adapter interface you want to use. Token Ring interface cables are not available from Cisco Systems, but are commercially available through outside cable vendors.

Following is the procedure for attaching Token Ring cables to the 4R port adapter:

Step 1   Determine which 4R port adapter ports you want to use.

Step 2   Attach the port adapter end of a Token Ring interface cable, or other connection equipment, to the interface port. (See Figure 19).

	Caution Each 4R port adapter interface must be configured for the same ring speed as the ring to which it is connected; either 4 or 16 Mbps. If the 4R port adapter interface is set for a different speed, it will cause the ring to beacon, which effectively brings the ring down and makes it inoperable.

Step 3   Attach the network end of the Token Ring interface cable to the appropriate Token Ring equipment at your site: a MAU or MSAU.

Configuring the 4R Interfaces

You can modify the startup configuration for Cisco 7000 series and Cisco 7500 series routers through the software command interpreter called EXEC. To configure the interfaces for interface processors, you can use either one of the setup or configure EXEC commands:

The setup command facility can be used after first time startup to make basic changes at any time. The changes you make will affect only the changed elements' current memory values that are stored in nonvolatile memory.

The configure privileged EXEC command enables you to perform advanced configurations such as specifying interfaces. The EXEC interprets the commands you enter and carries out the corresponding operations. You can list available EXEC commands by entering a question mark (?). You also can enter a question mark to obtain more information about commands. For example, enter terminal ? to obtain a list of terminal commands or show ? to obtain a list of show commands.

Using the EXEC Command Interpreter

Before you use the setup or the configure command, you must have privileged access to the EXEC command interpreter. 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.

Follow these steps to enter the privileged level of the EXEC.

Step 1   At the EXEC prompt for a router, enter the enable command:

Router> enable

 

The EXEC prompts you for a privileged level password:

Password:
 

Step 2   Enter the password.

For security purposes, the password is not displayed. (Also note that the password is case sensitive). When you enter the correct password, the system displays the privileged mode system prompt:

Router#
 

To configure Token Ring interfaces using the setup EXEC command facility, follow the instructions in the section "Using the Setup Command." To configure the Token Ring interfaces by using the configure EXEC command, follow the instructions in the section "Using the Configure EXEC Command" on page 39.

Using the Setup Command

The setup command facility identifies all interfaces (including the Token Ring interfaces for the ports on the 4R port adapter) that are installed and prompts you for configuration information for each installed interface. When you finish configuring one interface, the setup command facility prompts you for the next, continuing until each interface has been configured.

When you enter the setup command facility after first time startup, you must run through the entire dialog until you come to the interface you want to change. Note that when you use the setup command after first time startup, the default values indicated within the brackets in the System Configuration Dialog are the values last set using the setup command facility or left as defaults.

After you choose to continue with the setup command (by answering yes to the system configuration dialog prompt), the remainder of the script is the actual configuration process. The dialog prompts you first for global system parameters, then for configuration information for each interface. The existing configuration is displayed as the default, in brackets ([ ]), at the end of each prompt. Press Return to accept the default settings.

Following is the procedure for using the setup facility to configure the 4R Token Ring interfaces:

Step 1   After you access the privileged level of the EXEC, as described in the section "Using the EXEC Command Interpreter" on page 37, enter the setup command to begin the setup facility:

Router# setup 
 

Step 1   The following script is displayed on the screen, with the name of your router as the default in the brackets.

-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 '[]'.

Continue with configuration dialog? [yes]:
(Use Ctrl-c to abort configuration at any prompt)

Configuring global parameters:

Enter host name [Router]: sandbox

 

Step 2   To accept the default and keep the router name, press Return. (If you do want to change the name of the router, enter the new name before pressing Return.)

Step 3   Proceed through the remainder of the global parameter prompts, using the Return key to accept the defaults.

After the global parameters are configured, the system prompts you for interface configuration information, one interface at a time. Following is a partial display of the script for a previously configured interface:

Configuring interface parameters:



	Configuring interface Token Ring0:

		Is this interface in use [yes]:

	Tokenring ring speed (4 or 16) [16]

		Configure IP on this interface? [yes]:

		IP address for this interface: 1.1.1.30

		(remainder of display text omitted)