This publication contains instructions for installing and upgrading the Performance Routing Engine 3
(PRE3) in a Cisco 10008 router.
Finding Feature Information in This Module
Your Cisco IOS software release may not support all of the features documented in this module. To reach
links to specific feature documentation in this module and to see a list of the releases in which each feature is
supported, use the “Feature Information for Installing a PRE3” section on page 34.
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image
support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on
Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at
the login dialog box and follow the instructions that appear.
Contents
The following sections are included in this installation document:
• Product Overview, page 3
• Prerequisites and Preparation, page 7
• Safety Guidelines, page 7
• Software Compatibility, page 8
• Installation Guidelines, page 8
• Installing or Replacing a PRE3, page 11
• Forcing Failover in a Redundant Pair, page 16
• Managing System Boot Parameters, page 16
• Upgrading Software, page 18
Corporate Headquarters:
Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA
The Performance Routing Engine 3 (PRE3) is the fourth generation Parallel Express Forwarding (PXF)
packet processing and scheduling engine for the Cisco 10008 router. Figure 1 shows the front of the
Cisco 10008 router.
Figure 1Cisco 10008 Router Chassis—Front View
2
3
MISWIRE
MISWIRE
Product Overview
1
FANS
FAN
OK
MULTI-
FAILURE
FAN
FAILURE
CAU
TIO
W
hen hot swapping this fan tray,
N
rem
oval and replacem
be don
e in u
en
t must
nder two m
system
shutdown will occur.
1
2
C
IS
C
O
C
ISC
1
0
0
O
0
0
10000
FAIL
F
A
IL
C
A
R
A
R
I
E
R
0
1
POWER
FAULT
POWER
FAULT
2
3
LINK
C
A
R
TX
A
RX
R
L
L
A
IE
O
R
R
O
M
P
4
5
GIGABIT ETHERNET
CH OC-12-DSO SM-IR
inutes or
3
4
0A
PR
O
C
0B
ESS
OR
O
N
C
ISC
O
C10000
C
ISC
10000
O
FAIL
1000
6CT3
0
FAIL
FA
IL
C
L
L
A
A
O
R
R
A
O
M
L
R
L
P
A
I
O
E
R
O
R
M
P
MR
A
A
L
C
A
0
O
PORT0
L
1
PORT1
PORT2
2
PORT3
3
PORT4
4
PORT5
5
6XCT3–DS0
LY
5
C
IS
CO
100
00
CONSOLE
AUX
PO
ACTIVITY
ETHERNET
LINK
A
L
C
IN
T
I
K
V
I
T
Y
ALARMS
C
R
I
T
IC
M
A
A
L
J
O
R
M
I
N
O
R
A
C
O
S
L
O
T
0
S
T
A
T
U
F
S
A
I
L
B
I
T
S
PERFORMANCE ROUTING ENGINE
6XCT3–DS0
P/N
ESR-PRE3
P
RO
C
ESSO
R O
6
7
C
IS
CO
10000
C10000
CISC
O
10000
6CT3
FAIL
FAIL
CONSOLE
AUX
C
A
ACTIVITY
R
A
L
R
L
A
IE
O
R
O
R
M
ETHERNET
P
M
R
P
A
A
L
O
C
A
0
O
PORT0
LINK
L
A
L
C
I
T
N
IV
K
IT
Y
1
PORT1
ALARMS
C
R
I
T
PO
2
RT2
IC
M
A
A
L
J
O
R
M
IN
O
R
PORT3
A
3
C
O
PORT4
4
PORT5
5
S
L
O
T
0
S
T
A
T
U
F
S
A
I
L
B
IT
S
PERFORMANCE ROUTING ENGINE
6XCT3–DS0
P/N
ESR-PRE3
8
C10000
CIS
C
O
C10000
CIS
10000
6CT3
CO
FA
C
10000
IS
6CT3
C
O
IL
FAIL
10000
F
AIL
FAIL
FAIL
C
A
R
A
L
R
C
L
A
IE
A
O
R
R
A
O
R
M
L
R
P
L
A
I
M
O
E
R
R
P
A
A
O
R
L
O
M
C
A
0
O
P
PORT0
L
MR
P
A
A
L
O
C
A
0
O
PO
L
RT0
1
PORT1
1
PO
RT1
PO
2
RT2
PORT2
2
PORT3
3
PORT3
3
C
A
R
R
PORT4
IE
4
T
R
R
X
X
PO
RT4
4
PO
RT5
5
PORT5
5
OC–12/STM–4 POS SM–IR
6XCT3–DS0
6XCT3–DS0
NLY
OL-8544-01
4
5
6
7
132515
1Blower module5PRE3—slot 0A
2Primary Power Entry Module (PEM)6PRE3—slot 0B
3Redundant PEM7Line card slots 5 to 8
4Line card slots 1 to 4
The PRE3 performs all Layer 2 and Layer 3 packet manipulation related to routing and forwarding
through the Cisco 10008 router. Its advanced application-specific integrated circuit (ASIC) technology
supports very high performance throughput with IP services enabled on each port.
The PRE3 consists of two main logical and physical cards:
• The fast packet (FP) card—Performs fast path forwarding and output scheduling.
• The route processor (RP) card—Contains the configuration, management route processing engine,
and backplane interconnect. The FP card plugs into the RP card.
The PRE3 runs Cisco IOS Release 12.2(31)SB2 and later releases. Benefits of the PRE3 include:
• 800-MHz dual processor
• Four PXF network processors arranged as 8 columns and 8 rows
• 128 Mbytes of configuration memory (per column) with Error-Correcting Code (ECC)
• 2 GB SDRAM with single error correction/double error detect ECC
• Two separate CompactFlash slots. The internal CompactFlash slot stores images to bootflash. The
• 256 MB packet buffer and 64 MB control memory ECC
• A 1000/100 Mbit Interprocess Ethernet interface for communications between redundant PRE3s
• A Hierarchical Queueing Framework (HQF) that provides a three level hierarchy for class, logic,
By centralizing packet processing in the PRE3, the Cisco 10008 router architecture frees up space on
line cards, enabling high interface density, yet retaining the compact Network Equipment Business
Systems (NEBS) transmission equipment form factor.
Redundant PRE3s
external CompactFlash slot is Disk0.
and physical levels
You can configure two PRE3s in a single chassis for redundancy. If the active PRE3 fails, the standby
PRE3 automatically takes over operation of the router. Because all the line cards are physically
connected to both the active and standby PRE3s, the failure of a single PRE3 does not require user
intervention. If a failure occurs, all line cards automatically reset to the redundant PRE3. Startup and
running configurations of the standby PRE3 are synchronized with the active PRE3, ensuring the fastest
possible cut-over time if the active PRE3 fails.
PRE3 Front Panel
This section describes the PRE3 front panel (see Figure 2).
PRE3 Connectors
The front panel on the PRE3 contains three ports with RJ-45 connectors (see Figure 2).
• Console port (CONSOLE)—This asynchronous serial port is used to connect a terminal to the PRE3
• Auxiliary port (AUX)—This asynchronous serial port is used to connect a modem to the PRE3 for
• Network Management Ethernet (NME) Port (ETHERNET)—This Ethernet port is used to connect
for local administrative access.
remote administrative access.
the PRE3 to a Fast Ethernet port.
CompactFlash Card Slot
The internal CompactFlash card slot can store the Cisco IOS image or a system configuration file on a
flash memory card. The system can also boot from the software stored on the flash memory card.
ACTIVITYGreenPackets are being transmitted and received.
OffNo activity.
LINKGreenCarrier detected, the port is able to pass traffic.
OffNo carrier detected, the port is not able to pass traffic.
Push-button resetn/aResets the PRE3.
CRITICAL, MAJOR,
and MINOR LEDs
OffNo alarm.
NoteAlarm relay contacts can be used to connect the router
to an external visual or audio alarm system. This feature
enables any CRITICAL, MAJOR, or MINOR alarms
generated by the router to activate the visual or audible
alarms. Shutting off an audible alarm does not disable
the alarm LEDs.
YellowIndicates an alarm condition.
ACO (Alarm cut–off)
n/aPressing this button disables an audible alarm.
Table 1PRE3 LED Status and Button Descriptions (continued)
LEDs and ButtonStatusDescription
CompactFlash Disk0GreenDisk0 is active.
STATUSFlashing
FAILYellowA major failure has disabled the PRE3.
BITSn/aNot supported.
Alphanumeric Display
The alphanumeric display on the front panel provides information on the state of the PRE3. The display
consists of two four-character LED panels. Table 2 describes the most common messages. If you report
a problem to Cisco, it is helpful to include the message on the PRE3 alphanumeric display in your
problem report.
System is booting.
Yellow
GreenPRE3 is active.
Flashing
PRE3 is standby.
Green
OffNo power to PRE3.
OffThe PRE3 is operating correctly.
Table 2Messages on PRE3 Alphanumeric Display
MessagePRE3 Status
1111, 2222, 3333, 4444, 5555, 6666,
7777
The PRE3 has just been powered on and is running its
power-on self-test.
ROM DONEThe PRE3 has loaded the ROM monitor. This message
appears briefly if the system is configured to boot a Cisco
IOS software image. If the system is not configured to
boot Cisco IOS, this message remains on the display and
the rommon> prompt appears on the terminal window.
AUTO BOOT The ROM monitor is preparing to boot a Cisco IOS image.
Before you begin the PRE3 installation procedure, review the safety guidelines in this section to avoid
injuring yourself or damaging the equipment. Before you install, configure, or perform maintenance on
the router, you should also review the safety warnings listed in the Regulatory Compliance and Safety
Information for Cisco 10000 Series Routers document.
Safety Warnings
Safety warnings appear throughout this publication in procedures that, if performed incorrectly, may
harm you. A warning symbol precedes each warning statement. The following warning is an example of
a safety warning. It identifies the warning symbol and associates it with a bodily injury hazard.
Warning
IMPORTANT SAFETY INSTRUCTIONS
This warning symbol means danger. You are in a situation that could cause bodily injury. Before you
work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar
with standard practices for preventing accidents. Use the statement number provided at the end of
each warning to locate its translation in the translated safety warnings that accompanied this device.
Statement 1071
SAVE THESE INSTRUCTIONS
OL-8544-01
NoteIf you need translations of the safety warning, see the Regulatory Compliance and Safety Information
Use the show version command to display the system software version that is currently loaded and
running.
If the output of the show version command indicates that the Cisco IOS software is a version earlier than
the version identified as the minimum Cisco IOS software release in Tab le 3, check the contents of the
CompactFlash memory to determine if the required images are available on your system.
The output of the show flash command provides a list of all files stored in the CompactFlash memory.
If the correct software version is not installed, contact Cisco Customer Service (see the “Obtaining
Technical Assistance” section on page 37).
Installation Guidelines
This section contains guidelines for the following:
• A new installation
• A replacement installation
• The required tools and equipment
The PRE3 is hot-swappable, which means you can remove and replace a PRE3 while the system is
operating—if you have a standby (redundant) PRE3 installed in the chassis. This feature allows you to
add, remove, or replace a PRE3 while the system maintains all routing information and ensures session
preservation.
CautionReplacing the active PRE3 in a non-redundant chassis (no standby PRE3) causes a system shutdown and
stops all traffic. If possible, alert all subscribers that the system will not be functioning during the
replacement.
CautionTo prevent electrostatic discharge (ESD) damage, handle the PRE3 by the faceplate or the card carrier
edges only. Avoid touching the printed circuit board and its components, or any connector pins.
New Installation Guidelines
If you are replacing the PRE3 in a non-redundant system, you must configure the PRE3 using the
configure command. For configuration information, refer to the “Configuring a PRE3” section on
If the PRE3 is replaced in a redundant system containing two PRE3s, the standby (or newly installed)
PRE3 automatically assumes the configuration of the active PRE3; do not configure the new PRE3.
Required Tools and Equipment
You need the following tools and equipment to install the PRE3:
• A 3/16-inch flat-blade screwdriver
• An ESD-preventive wrist or ankle strap with connection cord
• A terminal console to connect to the PRE3 after it is installed
Powering Off the System
If you are installing or replacing a single PRE3, power down the system using the following procedure:
Installation Guidelines
CautionIf you have redundant Power Entry Modules (PEMs), set both power switches to the off (0) position. See
Figure 3 for the DC PEM power switch and Figure 4 for the AC PEM power switch.
Step 1Attach an antistatic strap to your wrist or ankle and to an ESD socket on the chassis, or to a bare metal
surface on the chassis or frame.
Step 2Set the power switch to the off (0) position.
Step 3Go to the Installing or Replacing a PRE3, page 11.
This section describes how to install or replace the PRE3 in the Cisco 10008 chassis. It contains the
following information:
• Installing a PRE3, page 11
• Configuring a PRE3, page 14
• Removing a PRE3, page 14
• Troubleshooting the Installation, page 15
Installing a PRE3
Use the following procedure to install the PRE3 into slot 0A or slot 0B in the Cisco 10008 chassis.
Step 1Attach an antistatic strap to your wrist or ankle and to an ESD socket (see Figure 5) on the chassis, or to
a bare metal surface on the chassis or frame.
Step 2Grasp the faceplate (see Figure 6) of the PRE3 with one hand and place your other hand under the frame
of the PRE3 to support the weight of the PRE3. Position the PRE3 in front of the chassis slot.
Installing or Replacing a PRE3
Step 3Carefully align the upper and lower edges (see Figure 6) of the PRE3 with the upper and lower guides
in the chassis, and slide the PRE3 into the slot until you can feel it begin to seat in the backplane
connectors.
Step 4Simultaneously pivot both ejector levers (see Figure 7) toward each other, until they are parallel to the
faceplate, to firmly seat the PRE3 in the backplane.
The PRE3 cycles through its power-on self-test. The FAIL LED stays on briefly (10 to 15 seconds) and
then shuts off.
Step 5Tighten the top and bottom captive screws (see Figure 8) to secure the PRE3 to the chassis.
CautionTo ensure that there is adequate space for additional line cards, always tighten the captive
screws on each newly installed PRE3 before you insert a standby PRE3 or any additional line
cards. The captive screws prevent accidental removal and provide proper grounding for EMI
shielding.
Step 6Refer to the “Configuring a PRE3” section on page 14 for information about configuring the PRE3.
After the PRE3 is successfully installed, you can configure it for network use. For information about
configuring the PRE3, see “Managing the Router Using the Network Management Ethernet Port” section
on page 24.
NoteYou do not need to configure a redundant (secondary) PRE3. The standby PRE3 automatically assumes
the configuration of the active PRE3.
Removing a PRE3
Use the following procedure to remove a PRE3 from the chassis:
Step 1Attach an antistatic strap to your wrist or ankle and to an ESD socket (see Figure 5) on the chassis, or to
Step 2Loosen the top and bottom captive screws (see Figure 8) on the PRE3.
NoteThe top and bottom captive screws must be loosened prior to pivoting the ejector levers in Step 3.
Step 3Simultaneously pivot both ejector levers (see Figure 7) away from each other to disengage the PRE3
from the backplane.
Step 4Slide the PRE3 out of the slot (see Figure 6) and place it on an antistatic surface, or in an antistatic bag.
Step 5See the “Installing or Replacing a PRE3” section on page 11 for instructions on how to install a new
PRE3.
NoteIf you are not installing a replacement PRE3, install a blank faceplate in the slot.
Warning
Step 6Power on the system if you have powered it off.
Do not operate the system unless all slots contain a PRE3, line card, or a blank faceplate. Blank
faceplates are necessary in empty slots to prevent exposure to hazardous voltages, to reduce
electromagnetic interference (EMI) that may disrupt other equipment, and to direct the flow of cooling
air through the chassis.
Troubleshooting the Installation
Refer to Figure 2 and Table 1 for descriptions of the LEDs on the PRE3. Follow the instructions in
Table 4 to troubleshoot the installation.
Table 4PRE3 Installation Troubleshooting
SymptomPossible CauseCorrective Action
PEMs, fans, and other line cards
do not operate
1. Disconnected power cord.
2. Power switch is in the Off
position.
3. The PRE3 fuses are blown.
1. Check that all power cords
are properly connected to
both the chassis and at the
power connection end.
The FAIL LED does not light
during the power-on self-test
PRE3 does not operate properly
If these troubleshooting procedures do not correct the problem, refer to the Cisco 10000 Series Router
Troubleshooting Guide for additional information.
1. The PRE3 is not properly
seated.
2. Bad PRE3 slot or backplane
connector.
1. Bad PRE3 slot or backplane
connector.
2. Bad PRE3.
1. Be sure the ejector levers
are fully closed and that
the captive screws have
been tightened.
2. Remove the PRE3 and
install it in another PRE3
slot.
1. Remove the PRE3 and
install it in another PRE3
slot.
2. Replace the PRE3.
Forcing Failover in a Redundant Pair
To manually force the active and standby devices in a redundant pair to failover, use the redundancy
force-failover command. Manually force the active and standby PRE3s to reverse roles if you need to
replace the active one. You can then replace the PRE3 while causing only minimal disruption of traffic.
The following example shows how to set the standby PRE3 to be active:
Router# redundancy force-failover main-cpu
This command does not generate an alarm.
Managing System Boot Parameters
During the boot process, the system reads a software configuration register that defines certain system
parameters. The software configuration register is a 16-bit register in NVRAM used to define such
characteristics as:
• The source of the Cisco IOS software image required to run the router
• Whether the system software should ignore the contents of NVRAM
• The behavior of the Break function
By modifying the boot parameters, you can customize your Cisco 10008 router. For example, a common
configuration register setting in some lab environments is 0x2100. Using this setting, the system boots
to the ROM monitor (ROMmon) prompt, where a technician can load a specific image by entering the
boot command at the ROMmon prompt.
Changing the Software Configuration Register Settings
The factory default value for the software configuration register is 0x2102. This value is a combination
of the following: binary bit 8 = 0x0100, bits 00 through 03 = 0x0002, and bit 13 = 2000.
To change the software configuration register settings while you are running system software, perform
the following steps:
Step 1From global configuration mode, enter the config-register value command to set the contents of the
software configuration-register; value is a hexadecimal number preceded by 0x, for example:
Router(config)# config-register 0x2100
Consult the hexadecimal column in Table 5 on page 18 for the possible settings to enter as the 4-bit value
parameter.
Step 2Exit global configuration mode by pressing Ctrl-Z.
Router(config)# Ctrl-Z
Router#
Step 3To display the new software configuration register setting, issue the show version command.
Router# show version
.
.
.
#Configuration register is 0x141 (will be 0x2100 at next reload)
Managing System Boot Parameters
Step 4Save the configuration file to preserve the new software configuration register settings.
Router# copy running-config startup-config
Step 5Reboot the router.
The router reboots using the new register settings. The software configuration register setting takes
affect only after you reload the system. This happens when you issue the reload command from the
console or reboot the router.
Table 5Definition of Bits in the Software Configuration Register
Bit No.Hex Value Meaning/Function
00 to 03 0x0000 to 0x000F Defines the source of a default Cisco IOS software image required to run the router:
• 00—At power-on, the system remains at the ROM monitor prompt (rommon>),
awaiting a user command to boot the system manually by means of the ROMmon
boot command.
• 01—At power-on, the system automatically boots the first system image found on
the PRE3.
• 02 to 0F—At power-on, the system automatically boots from a default Cisco IOS
software image stored on a TFTP server in the network. For this setting, the
Fast Ethernet port on the PRE3 must be configured and operational. This setting
also enables boot system commands that override the default filename.
06 0x0040 Causes system software to ignore the contents of NVRAM.
07 0x0080 Enables the original equipment manufacturer (OEM) bit.
08 0x0100 The Break function is disabled after 30 seconds.
09 0x0200 Not used.
10 0x0400 Broadcast based on 0.0.0.0 IP address.
11 and 12 0x0800 to 0x1000 Defines the console baud rate (the default setting is 9600 baud).
13 0x2000 Boots an image from Disk0.
14 0x4000 Broadcast using the subnet broadcast address.
15 0x8000 Enables diagnostic messages and ignores the contents of NVRAM.
Upgrading Software
This section describes the following methods for upgrading Cisco IOS images on the Cisco 10008
router:
• Upgrading Software from a PRE2 to a PRE3, page 18
• Upgrading Software on a Single PRE3, page 21
• Upgrading Software on Redundant PRE3s, page 22
Upgrading Software from a PRE2 to a PRE3
This section describes the procedures for upgrading the Performance Routing Engine from a PRE2 to a
PRE3. Procedures for downgrading from a PRE3 to a PRE2 are also described.
• Prerequisites, page 19
• Upgrade Considerations, page 19
• Procedure to Upgrade a PRE2 to a PRE3, page 19
NoteWhen upgrading from a PRE2, all references to boot commands pointing to disk1 should be removed.
For all of the software features supported by your current PRE2 (c10k2-p11-mz) image to function
correctly, they must be supported by the PRE3 image. Check with the Cisco Technical Assistance Center
(TAC) to verify the correct upgrade path before initiating the upgrade.
The upgrade should be performed by a qualified engineer. This person must be familiar with the Cisco
router console interface and be able to perform basic router operations, such as configuration loading
and router reload functions.
CautionDo not perform this upgrade if your current PRE2 software image supports new features not yet
supported by the PRE3 software image. Performing this upgrade will cause these features to fail.
Upgrade Considerations
• This is a service impacting hardware upgrade. The router will not be available for user traffic during
the upgrade, and traffic cannot resume until the upgrade is complete.
• All new PRE3s are shipped with an eboot image (c10k3-eboot-mz) stored in bootflash.
Upgrading Software
Procedure to Upgrade a PRE2 to a PRE3
Follow this procedure to upgrade a single PRE2 in a Cisco 10008 chassis that does not have a redundant,
standby PRE2.
Step 1Connect a terminal to the active PRE2.
Step 2Save the startup and running configuration to a location on a TFTP server.
CautionWhen the PRE2 is removed from the chassis, any local configuration will be lost. You must
save your configuration to a TFTP server.
Step 3Power down the router. All the traffic on the router is stopped.
NotePRE2s can be hot-swapped. However, because removing a PRE2 stops all traffic, we recommend
that you power down the router to ensure a successful installation.
Step 4Attach an antistatic strap to your wrist or ankle and to an ESD socket on the chassis, or to a bare metal
surface on the chassis or frame.
Step 5Remove the PRE2 from the chassis using the procedure in the “Removing a PRE3” section on page 14.
Step 6Insert the PRE3 into slot 0A of the chassis by following the procedure in the “Installing a PRE3” section
on page 11.
OL-8544-01
a. If you do not have a second, redundant PRE3 to install, a blank card must be used to fill the unused
slot 0B.
NoteAlthough a PRE3 can be installed in slot 0B, we recommend that you install a single,
non-redundant PRE3 in slot 0A to ensure proper operation.
Step 7Power up the router. The router boots in read-only memory (ROM) monitor mode.
Step 8From the console in ROM monitor mode, enter the appropriate boot command.
Booting from a TFTP Server
If you saved the PRE2 image on a TFTP server that is reachable from the router (for example, if the
router and server are on the same LAN or there is a default proxy server), boot the router from the TFTP
server.
In the following example, the router boots the PRE3 image from a network server with the IP address
172.16.15.112:
> boot tftp://172.16.15.112/c10k3-p11-mz
The configuration dialog appears.
You can now proceed to step 9.
Booting from Disk0
If the image was saved to Disk0, boot that image.
The following boot command loads the PRE3 image from Disk0:
> boot disk0:c10k3-p11-mz
The configuration dialog appears.
You can now proceed to step 9.
Booting from the eboot Image
If you did not save the PRE3 image to a TFTP server, boot the eboot (c10k3-eboot-mz) image stored in
bootflash.
In the following example, the router boots from the eboot image:
> boot bootflash:c10k3-eboot-mz
The configuration dialog appears.
Proceed to the “Did Not Save the Configuration” section on page 21.
Step 9Restore the startup and running configuration of the router.
Saved the Configuration on a CompactFlash Card
If you booted the PRE3 image and saved the previous configuration to a CompactFlash card:
a. Exit the configuration dialog and restore the previously saved startup and running configuration
from the CompactFlash card.
b. Update any boot commands to use the new PRE3 image.
The router is available for normal operations and the upgrade is complete.
If you booted the PRE3 image, and you saved the previous configuration to a TFTP server:
a. Enter the initial configuration dialog, and enter all required information to allow access to the TFTP
server.
b. Assign the correct IP address for the Fast Ethernet interface to become active and for the TFTP
server to become reachable. This may require adding an IP route for the server even after the initial
dialog completes.
c. Restore the previous configuration from the TFTP server to the startup and running configuration
on the router.
d. Restore the startup and running configuration and update any boot commands to use the new PRE3
image.
The router is available for normal operations and the upgrade is complete.
Did Not Save the Configuration
If you did not save the PRE2 image to a TFTP server and you booted the PRE3 image:
a. Enter the initial configuration dialog, and enter all required information. Be sure to assign the
correct IP address for the Fast Ethernet interface to become active and for the TFTP server to become
reachable.
b. The TFTP server should be reachable. If you wish to boot the PRE3 image from a local
CompactFlash card, download the PRE3 IOS image from the TFTP server to the bootflash memory.
If you wish to boot directly from the TFTP server, you can skip the image download.
c. Restore the previously saved configuration by downloading it from the TFTP server. Update any
boot commands from the previous configuration to point to the new PRE3 image. Otherwise, update
the boot command to point to the desired PRE3 image.
d. Reload the router. After reload, the router is available to resume normal operations and the upgrade
is complete.
Upgrading Software on a Single PRE3
To upgrade software for a single PRE3, follow these steps:
Step 1Copy the Cisco IOS image from a TFTP server to Disk0.
Router# copy tftp disk0:
Address or name of remote host []? 223.255.254.254
Source filename []? pre3/images/c10k3-p11-mz
Destination filename [c10k3-p11-mz]?
Accessing tftp://223.255.254.254/pre3/images/c10k3-p11-mz...
Loading pre3/images/c10k3-p11-mz from 223.255.254.254 (via FastEthernet0/0/0):
.
.
.
.
[OK - 25251732 bytes]
25251732 bytes copied in 50.356 secs (501464 bytes/sec)
Router#
OL-8544-01
Step 2Tell the Cisco 10008 router the location in which the new boot image resides. In the following example,
the system is told that the image “c10k3-p11-mz” is located in Disk0.
Router(config)# boot system flash disk0:c10k3-p11-mz
1 -rw- 25750196 Mar 4 2000 00:14:56 +00:00 c10k3-p11-mz
257544192 bytes total (231792640 bytes free)
Step 5Display the system image on bootflash.
Router# show run | i boot
boot-start-marker
boot system flash disk0:c10k3-p11-mz.mce_rp_isp-20060127
boot-end-marker
exception crashinfo file bootflash:crashinfo
Step 6Enter global configuration mode.
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#
Step 7Remove the current image from bootflash in Disk0.
Router(config)# no boot system flash disk0:c10k3-p11-mz.mce_rp_isp-20060127
Upgrading Software
Step 8Add the new image to bootflash in Disk0.
Router(config)# boot system flash disk0:c10k3-p11-mz
Step 9Set the contents of the software configuration register to 0x2100. This new register setting will take
affect after the system reload in Step 13.
Router(config)# config-register 0x2100
Step 10Return to privileged EXEC mode.
Router(config)# exit
Router#
Step 11Copy the running configuration to the startup configuration.
Router# copy running-config startup-config
Destination filename [startup-config]?
Building configuration...
[OK]
Step 12Verify the running configuration is copied to the startup configuration on both PRE3s.
Router# show bootvar
BOOT variable = disk0:c10k3-p11-mz,1;
CONFIG_FILE variable =
BOOTLDR variable =
Configuration register is 0x0
Managing the Router Using the Network Management Ethernet Port
Resetting .......
.
.
.
Both PRE3s are now using the new Cisco IOS image with the new register settings.
Managing the Router Using the Network Management Ethernet
Port
The network management Ethernet (NME) port on the PRE3 is used to manage the Cisco 10008 router.
The duplex mode and speed of the NME port are configurable.
The following sections describe how to configure the duplex mode and speed of the NME port for the
PRE3.
Configuring the NME Port on the PRE3
The NME port for PRE3 supports the following operational modes:
• Autonegotiation (the default)
• Full-duplex
• Half-duplex
Default configurations do not appear in the router’s configuration file.
We recommend that you allow the NME port to autonegotiate the duplex mode. When autonegotiation
mode is enabled, the NME port responds only to IEEE 802.3x pause frames from another device.
If the negotiation of duplex mode fails and a duplex mode mismatch occurs, manually set the duplex
mode for full-duplex or half-duplex operation. Setting duplex mode disables autonegotiation mode.
When you manually set duplex mode, the NME port does not support IEEE 802.3x flow control.
When you manually configure duplex mode, the NME port can experience problems. If this occurs,
disable duplex mode by entering the no full-duplex or no half-duplex command. When you enter the no duplex command, the operational mode reverts to autonegotiation mode.
To configure the NME port, perform the following optional configuration tasks:
• Manually Setting the Duplex Mode for the NME Port for the PRE3, page 24
• Manually Setting the Speed for the NME Port for the PRE3, page 25
Manually Setting the Duplex Mode for the NME Port for the PRE3
24
NoteWe recommend that you allow the NME port to autonegotiate (default setting) duplex mode.
To manually set the duplex operational mode of the NME port for the PRE3, enter either of the following
commands in interface configuration mode:
Configures the NME port for full-duplex operational mode.
For PRE3, the full-duplex command appears in the router’s
configuration file. If the configuration file does not specify a
duplex mode, half-duplex mode is implied.
NoteTo return the system to its default duplex mode
(autonegotiation), enter the no duplex command.
Router(config-if)# half-duplex
Configures the NME port for half-duplex operational mode.
For PRE3, the half-duplex command does not appear in the
router’s configuration file, but it is implied.
NoteTo return the system to its default duplex mode
(autonegotiation), enter the no duplex command.
Manually Setting the Speed for the NME Port for the PRE3
To manually set the speed of the NME port for PRE3, enter the following command in interface
configuration mode. The default speed of the NME port is 100 Mbps.
Analyzing and Troubleshooting Packets
CommandPurpose
Router(config-if)# speed {10 | 100
| auto}
Configures the speed of the NME port.
10—Sets the speed for 10 Mbps.
100— Sets the speed for 100 Mbps (the default).
auto—Enables the NME port to autonegotiate the speed.
To return the system to its default speed (100 Mbps), enter the
no speed command.
Analyzing and Troubleshooting Packets
The PXF engine of the PRE3 is responsible for processing and forwarding packets. As processing
occurs, PXF counters increment to reflect the internal behavior of the PRE. The router collects this
statistical information from the counters and appropriately displays it when you enter specific
show pxf cpu commands. The output from these commands is useful in analyzing and troubleshooting
denied and logged packets.
To correctly interpret packet statistics, it is important that you understand the behavior of the router
during packet and access list processing, and the counters that provide the statistical data. This section
briefly describes access list processing, some PXF counters and their behavior, and some of the
commands you can use to display statistical information. This section is based on PRE3 with differences
noted for other PREs.
The Cisco 10008 router provides traffic filtering capabilities using Access Control Lists (ACLs). Access
lists filter network traffic by controlling whether routed packets are forwarded or blocked at the router's
interfaces. Using ACLs, you can do such things as restrict the contents of routing updates, provide traffic
flow control, and provide security for your network.
The Cisco 10008 router supports the following ACL types and features:
• Standard and extended ACLs
• Named and numbered ACLs
• Per-user ACLs
• Time-based ACLs
The access-list command is used to configure an ACL. For example, the following configuration creates
ACL 108:
access-list 108 permit udp any host 10.68.1.10 range 0 5000 log
access-list 108 permit udp host 10.1.1.10 range 0 5000 any log
After creating an ACL, it is applied to an interface using the ip access-group command. The router
executes the ACL from top to bottom, denying or permitting packets as directed by the access-list entries
(ACEs). When the log keyword is specified in an ACE, the router sends packet information to the
console.
The last line of an ACL is an implicit deny statement that appears to the router as:
deny any any
This statement causes the router to deny any packets remaining after processing the ACEs of the access
list. The implicit deny statement does not include the log keyword; therefore, the router does not send
packet information to the console for those packets denied by the implicit deny statement.
For example, the router processes the following ACL from top to bottom as follows:
access-list 108 permit udp any host 10.68.1.10 range 0 5000 log
access-list 108 permit udp host 10.1.1.10 range 0 5000 any log
• Statement 1—Allows any UDP packet to access host 10.68.1.10 if the UDP destination port of the
packet is between 0 and 5000. The router logs packet information to the console if a match is made.
• Statement 2—Allows any UDP packet from host 10.1.1.10 with a source port between 0 and 5000
to be permitted. The router logs packet information to the console if a match is made.
• Implicit Deny—Denies all remaining packets and does not log the packet information to the console.
Packet Statistics and PXF Counters
The Cisco 10008 router PRE3 provides high performance Layer 3 processing using its PXF engine and
Route Processor (RP). As the PXF engine processes packets, counters such as the following reflect the
internal operation of the PRE3:
The statistical information that the PXF counters provide is useful in analyzing and troubleshooting
denied and logged packets. Because the internal operation of the PRE3 differs for ACLs, the PXF
counters are inconsistent between the PREs. However, system-wide router behavior is consistent for
PREs despite the differences in counters.
The following sections describe the PXF counters and the way in which they increment.
IP Forwarding Counter
A Forwarding Information Base (FIB) lookup is one of the initial steps in forwarding a packet. When
the router forwarding processor needs information to forward a packet, it performs a lookup operation
on the FIB table. The IP forwarding counter reflects the state of that lookup operation. It does not reflect
whether or not the packet was forwarded. This counter increments each time an FIB lookup successfully
occurs.
ICMP Created Counters
Some FIB lookup operations can cause Internet Control Message Protocol (ICMP) messages to be
generated. For example, if a packet’s time-to-live (TTL) expires, an address is unreachable, or an
ACL-denied packet is dropped, an ICMP message is generated. The ICMP created counters reflect the
number of ICMP packets created. The counters increment each time an FIB lookup results in the
generation of an ICMP message.
Analyzing and Troubleshooting Packets
Feedback Counter
Sometimes the PXF engine cannot complete the processing of a packet before the packet completes a
single pass through the PXF; the packet requires additional processing. As a result, the packet is fed back
through the PXF and processing continues. This is referred to as a feedback operation.
The following are examples of packets that can cause feedbacks to occur:
• Packets that are forwarded and logged to the console
• ICMP packets that are sent
• Packets that require both input and output quality of service (QoS)
The feedback counter reflects the total number of feedbacks through the PXF by all packets. The counter
increments one time for each additional pass a packet makes.
When a packet is denied because of an ACL deny statement, the router drops the packet. Dropped packets
do not need further processing and, therefore, are not fed back through the PXF. In this case, the feedback
counter does not increment.
Displaying Packet Statistics
The Cisco 10008 router supports show pxf cpu commands that allow you to determine the following
information:
• Forwarding engine traffic load
• Forwarding engine actions on the traffic
OL-8544-01
• Traffic load from the PXF to the RP
• Status of output packet buffers for the queuing system
The Cisco 10008 router supports PXF–accelerated IPv6 packet forwarding over Multiprotocol Label
Switching (MPLS) on the PRE3. This feature is enabled by default.
Table 6 lists common IPv6 over MPLS commands. For detailed information about configuring IPv6,
refer to the Cisco 10000 Series Router Broadband Aggregation, Leased-Line, and MPLS Configuration
Guide.
Table 6IPv6 Forwarding over MPLS Commands
Command ModePurpose
Router(config)# ipv6
unicast-routing
Router(config)# ipv6 cef
Router(config)# ipv6 cef
distributed
Router(config-if)# ipv6
enable
Router(config-if)# ipv6
address
Router# show pxf cpu ipv6
Analyzing and Troubleshooting Packets
Displays PXF CPU statistics for a bridged
subinterface (encapsulation type).
Displays VCCI to interface mapping
information on the PXF CPU.
Global configuration Enables the forwarding of IPv6
packets.
Global configurationEnables Cisco Express
Forwarding for IPv6 (CEFv6).
Global configurationEnables distributed CEFv6
(dCEFv6) to process IPv6
packets from the Route
Processor (RP) to the line
cards.
Interface configurationEnables IPv6 processing on an
interface that has not been
configured with an explicit
IPv6 address.
Interface configurationConfigures an IPv6 address
based on an IPv6 general prefix
and enables IPv6 processing on
an interface,
Privileged EXECDisplays PXF IPv6 statistics.
Sample Case Study
For the purposes of this case study, assume that the following ACL is configured on the router’s
outbound serial 1/0/0 interface:
access-list 108 permit udp any host 10.68.1.10 range 0 5000 log
access-list 108 permit udp host 10.1.1.l0 range 0 5000 any log
A traffic simulator is used to send 100 UDP packets to the Cisco 10008 router with the source and
destination ports of the packets set to 6000. Packets arrive on the Gigabit Ethernet 2/0/0 interface and
are supposed to leave the router through the serial 1/0/0 interface.
After processing the 100 UDP packets, the show pxf cpu commands are entered to display statistical
information about the packets.
Hardware and Software Components
Table 7 lists the hardware and software components used in the case study.
Table 7Hardware and Software Components
Cisco IOS ReleaseProcessorImage
12.2(31)SB2ESR-PRE3c10k3-p11-mz
Displaying Packet Statistics for ACLs
The show pxf cpu statistics security command provides statistical information about the packets
denied, permitted, and logged by ACLs. The router collects statistics for mini-compiled ACLs, but not
for turbo-compiled ACLs.
The following example output provides packet information before sending the 100 packets. Notice that
the Packets Denied field indicates that no packets have been denied by ACL 108. The Denied and Log
field indicates that no denied packets have been logged.
Router# show pxf cpu statistics security
ACLPktsPktsDeniedPermit
Name DeniedPermitted & Log& Log
1080000
The following example output results after sending the 100 packets. Notice that the Packets Denied field
now indicates that 100 packets have been denied. Recall that the router denied the packets because they
matched the implicit deny statement. This statement does not include a log keyword, which causes
information to be sent to the console. Therefore, no logging occurs and the Denied and Log fields
indicate this.
Router# show pxf cpu statistics security
ACLPktsPktsDeniedPermit
Name DeniedPermitted & Log& Log
108100000
Displaying IP Forwarding Statistics
The show pxf cpu statistics ip command provides statistical information about IP forwarding. The
following example output indicates the count of the IP forwarding counter before sending the 100
packets. Notice that the count is 402.
Router# show pxf cpu statistics ip
FP ip statistics
The following example output results after sending the 100 packets. Notice that the IP forwarding
counter is now 502
Router# show pxf cpu statistics ip
FP ip statistics
dropped0
forwarded502/*incremented by 100*/
punted540
input_packets 942
icmps_created0
noadjacency0
.
.
.
Displaying Queueing Statistics
The show pxf cpu queue command provides queueing statistics for one interface, all interfaces, or a
queue identifier (QID). The following example displays PXF queuing statistics for QID 267.
Router# show pxf cpu queue 267
ID : 267
Priority : Lo
CIR (in-use/configured) : 0/65535
EIR (in-use/configured) : 0/0
MIR (in-use/configured) : 0/65535
Maximum Utilization configured : no
Link : 2
Flowbit (period/offset) : 32768/32768
Burst Size : 1024 bytes
Bandwidth : 133920 Kbps
Channel : 0
Packet Descriptor Base : 0x00000100
ML Index : 0
Length/Average/Alloc : 0/0/32
Enqueues (packets/octets) : 293352/9280610
Dequeues (packets/octets) : 293352/9280610
Drops (tail/random/max_threshold) : 0/0/0
Drops (no_pkt_handle/buffer_low) : 0/0
WRED (weight/avg_smaller) : 0/0
WRED (next qid/drop factor) : 0/0
WRED (min_threshold/max_threshold/scale/slope):
precedence 0 : 0/0/0/0
precedence 1 : 0/0/0/0
precedence 2 : 0/0/0/0
precedence 3 : 0/0/0/0
.
.
.
Analyzing and Troubleshooting Packets
Displaying Drop Statistics
The show pxf cpu statistics drop command provides information about dropped packets and ICMP
packets. The following example output indicates the count of the icmp_unrch_interval counter before
sending the 100 packets. Notice that the count is zero.
Router# show pxf cpu statistics drop
FP drop statistics
The following example output indicates the count of the icmp_unrch_interval counter after sending the
100 packets. Notice that the icmp_unrch_interval count now indicates 100 due to the dropped packets.
Router# show pxf cpu statistics drop
FP drop statistics
The show pxf cpu context command provides the current and historical loads on the PXF. The following
example shows how busy the PXF forwarding process (FP) is with the current traffic load. The FP
context statistics section displays the number of contexts of each type that have entered the PXF engine
since it was last reloaded. If counters are idle, the PXF pipeline is hung.
Router# show pxf cpu context
FP context statistics count rate (since last time command was run)
The show pxf cpu feedback command provides the total number of feedbacks through the PXF by all
packets.
Router# show pxf cpu feedback
Load for five secs: 5%/0%; one minute: 6%; five minutes: 2%
Time source is hardware calendar, *21:13:02.615 UTC Tue Nov 29 2005
Table 8 lists the release history for this feature.
Not all commands may be available in your Cisco IOS software release. For release information about a
specific command, see the command reference documentation.
Cisco IOS software images are specific to a Cisco IOS software release, a feature set, and a platform.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image
support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on
Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at
the login dialog box and follow the instructions that appear.
NoteTable 8 lists only the Cisco IOS software release that introduced support for a given feature in a given
Cisco IOS software release train. Unless noted otherwise, subsequent releases of that Cisco IOS
software release train also support that feature.
Table 8Feature Information for Installing a PRE3
Feature NameReleasesFeature Information
PRE312.2(31)SB2 The PRE3 is the fourth generation PXF packet processing
and scheduling engine for the Cisco 10008 router.
Obtaining Documentation
Cisco documentation and additional literature are available on Cisco.com. This section explains the
product documentation resources that Cisco offers.
Cisco.com
You can access the most current Cisco documentation at this URL:
http://www.cisco.com/techsupport
You can access the Cisco website at this URL:
http://www.cisco.com
You can access international Cisco websites at this URL:
The Product Documentation DVD is a library of technical product documentation on a portable medium.
The DVD enables you to access installation, configuration, and command guides for Cisco hardware and
software products. With the DVD, you have access to the HTML documentation and some of the
PDF files found on the Cisco website at this URL:
http://www.cisco.com/univercd/home/home.htm
The Product Documentation DVD is created and released regularly. DVDs are available singly or by
subscription. Registered Cisco.com users can order a Product Documentation DVD (product number
DOC-DOCDVD= or DOC-DOCDVD=SUB) from Cisco Marketplace at the Product Documentation
Store at this URL:
http://www.cisco.com/go/marketplace/docstore
Ordering Documentation
You must be a registered Cisco.com user to access Cisco Marketplace. Registered users may order Cisco
documentation at the Product Documentation Store at this URL:
Documentation Feedback
http://www.cisco.com/go/marketplace/docstore
If you do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Documentation Feedback
You can provide feedback about Cisco technical documentation on the Cisco Support site area by
entering your comments in the feedback form available in every online document.
Cisco Product Security Overview
Cisco provides a free online Security Vulnerability Policy portal at this URL:
From this site, you will find information about how to do the following:
• Report security vulnerabilities in Cisco products
• Obtain assistance with security incidents that involve Cisco products
• Register to receive security information from Cisco
A current list of security advisories, security notices, and security responses for Cisco products is
available at this URL:
OL-8544-01
http://www.cisco.com/go/psirt
To see security advisories, security notices, and security responses as they are updated in real time, you
can subscribe to the Product Security Incident Response Team Really Simple Syndication (PSIRT RSS)
feed. Information about how to subscribe to the PSIRT RSS feed is found at this URL:
Cisco is committed to delivering secure products. We test our products internally before we release them,
and we strive to correct all vulnerabilities quickly. If you think that you have identified a vulnerability
in a Cisco product, contact PSIRT:
• For emergencies only—security-alert@cisco.com
An emergency is either a condition in which a system is under active attack or a condition for which
a severe and urgent security vulnerability should be reported. All other conditions are considered
nonemergencies.
• For nonemergencies —psirt@cisco.com
In an emergency, you can also reach PSIRT by telephone:
• 1 877 228-7302
• 1 408 525-6532
TipWe encourage you to use Pretty Good Privacy (PGP) or a compatible product (for example, GnuPG) to
encrypt any sensitive information that you send to Cisco. PSI RT can wo r k with information that has been
encrypted with PGP versions 2.x through 9.x.
Never use a revoked encryption key or an expired encryption key. The correct public key to use in your
correspondence with PSIRT is the one linked in the Contact Summary section of the Security
Vulnerability Policy page at this URL:
The link on this page has the current PGP key ID in use.
If you do not have or use PGP, contact PSIRT to find other means of encrypting the data before sending
any sensitive material.
Product Alerts and Field Notices
Modifications to or updates about Cisco products are announced in Cisco Product Alerts and Cisco Field
Notices. You can receive these announcements by using the Product Alert Tool on Cisco.com. This tool
enables you to create a profile and choose those products for which you want to receive information.
To access the Product Alert Tool, you must be a registered Cisco.com user. Registered users can access
the tool at this URL:
Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The
Cisco Support website on Cisco.com features extensive online support resources. In addition, if you
have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide
telephone support. If you do not have a valid Cisco service contract, contact your reseller.
Cisco Support Website
The Cisco Support website provides online documents and tools for troubleshooting and resolving
technical issues with Cisco products and technologies. The website is available 24 hours a day at
this URL:
http://www.cisco.com/en/US/support/index.html
Access to all tools on the Cisco Support website requires a Cisco.com user ID and password. If you have
a valid service contract but do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Obtaining Technical Assistance
NoteBefore you submit a request for service online or by phone, use the Cisco Product Identification Tool
to locate your product serial number. You can access this tool from the Cisco Support website
by clicking the Get Tools & Resources link, clicking the All Tools (A-Z) tab, and then choosing Cisco Product Identification Tool from the alphabetical list. This tool offers three search options:
by product ID or model name; by tree view; or, for certain products, by copying and pasting show
command output. Search results show an illustration of your product with the serial number label
location highlighted. Locate the serial number label on your product and record the information
before placing a service call.
TipDisplaying and Searching on Cisco.com
If you suspect that the browser is not refreshing a web page, force the browser to update the web page
by holding down the Ctrl key while pressing F5.
To find technical information, narrow your search to look in technical documentation, not the
entire Cisco.com website. After using the Search box on the Cisco.com home page, click the
Advanced Search link next to the Search box on the resulting page and then click the
Technical Support & Documentation radio button.
To provide feedback about the Cisco.com website or a particular technical document, click
Contacts & Feedback at the top of any Cisco.com web page.
Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and
S4 service requests are those in which your network is minimally impaired or for which you require
product information.) After you describe your situation, the TAC Service Request Tool provides
recommended solutions. If your issue is not resolved using the recommended resources, your service
request is assigned to a Cisco engineer. The TAC Service Request Tool is located at this URL:
http://www.cisco.com/techsupport/servicerequest
For S1 or S2 service requests, or if you do not have Internet access, contact the Cisco TAC by telephone.
(S1 or S2 service requests are those in which your production network is down or severely degraded.)
Cisco engineers are assigned immediately to S1 and S2 service requests to help keep your business
operations running smoothly.
To open a service request by telephone, use one of the following numbers:
For a complete list of Cisco TAC contacts, go to this URL:
http://www.cisco.com/techsupport/contacts
Definitions of Service Request Severity
To ensure that all service requests are reported in a standard format, Cisco has established severity
definitions.
Severity 1 (S1)—An existing network is “down” or there is a critical impact to your business operations.
You and Cisco will commit all necessary resources around the clock to resolve the situation.
Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your
business operations are negatively affected by inadequate performance of Cisco products. You and Cisco
will commit full-time resources during normal business hours to resolve the situation.
Severity 3 (S3)—Operational performance of the network is impaired while most business operations
remain functional. You and Cisco will commit resources during normal business hours to restore service
to satisfactory levels.
Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or
configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online
and printed sources.
• The Cisco Online Subscription Center is the website where you can sign up for a variety of Cisco
e-mail newsletters and other communications. Create a profile and then select the subscriptions that
you would like to receive. To visit the Cisco Online Subscription Center, go to this URL: