Cisco IOS Software Releases 11.0

Table Of Contents

Router Products Release Notes for Cisco IOS Release 11.0

Introduction

Documentation

Platform Support

Cisco IOS Packaging

Memory Requirements

New Features in Release 11.0(11) and Later 11.0 Releases

New Features in Release 11.0(10)

New Feature Sets for CIP2

New Features in Release 11.0(9)

New Features in Release 11.0(8)

New Feature Sets for Cisco 1005

UDP Turbo Flooding for Cisco 7500

New Features in Release 11.0(7)

Support for the Cisco 4700-M Router

New Features in Release 11.0(6)

Channel Service Unit/Data Service Unit (CSU/DSU) Management Information Base (MIB)

Support for the Cisco RSP7000

New Configuration Tool - ClickStart

New Features in Release 11.0(5)

AAL3/4 E3/DS3 for Cisco 4500 and Cisco 4700 ATM NIM

Support for the Cisco 2520, Cisco 2521, Cisco 2522, and Cisco 2523

Support for the Cisco 2524 and Cisco 2525

LAN Frame Relay Access Device (FRAD) Feature Set

Leased Line via ISDN BRI

New Features in Release 11.0(4)

Support for the Cisco 1005

New Feature Sets for Cisco 1003 and Cisco 1004 ISDN Routers

Payload Compression for Frame Relay

Standard Serial Interface Processor and Service Provider MultiChannel Interface Processor on the Cisco 7000 Series

New Features in Release 11.0(3)

Support for the Channel Interface Processor (CIP) on the Cisco 7500 Series

Dynamic Address Mapping for IPX over SMDS

IP Address Pooling Changes

ISDN B-Channel Setup and Teardown

Multilink PPP

Multivendor Flash SIMM Support

PPP Callback

SSE Switching of Input Access Lists

Support for the Cisco 1004 ISDN Router

New Features in Release 11.0(2)

Support for the Fast Ethernet Interface Processor on the Cisco 7000 Series and Cisco 7500 Series

Support for the Cisco 1003 ISDN Router

QLLC and Bisync

New Features in Release 11.0(1)

General Features

Backbone Protocol Routing Features

TCP/IP Features

Transparent Bridging Features

Desktop Protocol Features

AppleTalk Features

Banyan VINES Features

Novell Features

Wide-Area Networking Features

ISDN/DDR Enhancements

X.25 Enhancements

Frame Relay

ATM Enhancements

Core Enhancements

IBM Functionality Features

New Features

New MIB Support

Access Server Features Supported on the Router

Important Notes

BSC and SDLC Commands in Releases 11.0(5) and 11.0(6)

X.25 Problem in 11.0(2)

Upgrading to a New Software Release

Emulated LAN Interoperability

Payload Compression for Frame Relay Support

Multiring FDDI Support

SRB over FDDI

Fast Switching of SRB over FDDI on Cisco 4000 Series

Cisco 1000 Series Support

Enabling IPX Routing

Using AIP Cards

Booting Cisco 4000 Routers

Using LAN Emulation (LANE)

Forwarding of Locally Sourced AppleTalk Packets

Using Source-Route Transparent Bridging (SRT) and Source-Route Bridging (SRB) on Cisco 2500 and Cisco 4000 Routers

Release 11.0(10a) Fixes Caveat CSCdi66673

Release 11.0(12a) Fixes Caveat CSCdi71609

Release 11.0(13a) Fixes Caveat CSCdi92818

Release 11.0(14a) Fixes Caveat CSCdj05366

Caveats for Release 11.0(1) through 11.0(22a)

Caveats for Release 11.0(1) through 11.0(22)

Basic System Services

DECnet

IBM Connectivity

Interfaces and Bridging

IP Routing Protocols

ISO CLNS

Wide-Area Networking

Miscellaneous

Caveats for Release 11.0(1) through 11.0(21)

Basic System Services

Interfaces and Bridging

IP Routing Protocols

Caveats for Release 11.0(1) through 11.0(20)

IBM Connectivity

Miscellaneous

Caveats for Releases 11.0(1) through 11.0(19)

IBM Connectivity

Interfaces and Bridging

IP Routing Protocols

Miscellaneous

Wide-Area Networking

Caveats for Releases 11.0(1) through 11.0(18)

IBM Connectivity

Interfaces and Bridging

IP Routing Protocols

TCP/IP Host-Mode Services

Wide-Area Networking

Caveats for Releases 11.0(1) through 11.0(17)

Basic System Services

IBM Connectivity

Interfaces and Bridging

IP Routing Protocols

LAT

Novell IPX, XNS, and Apollo Domain

TCP/IP Host-Mode Services

VINES

Wide-Area Networking

Caveats for Releases 11.0(1) through 11.0(16)

Basic System Services

IBM Connectivity

Interfaces and Bridging

IP Routing Protocols

LAT

Novell IPX, XNS, and Apollo Domain

TCP/IP Host-Mode Services

VINES

Wide-Area Networking

Caveats for Releases 11.0(1) through 11.0(15)

Basic System Services

IBM Connectivity

Interfaces and Bridging

IP Routing Protocols

TCP/IP Host-Mode Services

Wide-Area Networking

Caveats for Releases 11.0(1) through 11.0(14)

Basic System Services

EXEC and Configuration Parser

IBM Connectivity

Interfaces and Bridging

IP Routing Protocols

Novell IPX, XNS, and Apollo Domain

TCP/IP Host-Mode Services

Wide-Area Networking

Caveats for Releases 11.0(1) through 11.0(13)

Basic System Services

EXEC and Configuration Parser

IBM Connectivity

Interfaces and Bridging

IP Routing Protocols

ISO CLNS

Novell IPX, XNS, and Apollo Domain

TCP/IP Host-Mode Services

VINES

Wide-Area Networking

Caveats for Releases 11.0(1) through 11.0(12)

Basic System Services

EXEC and Configuration Parser

IBM Connectivity

Interfaces and Bridging

IP Routing Protocols

ISO CLNS

Novell IPX, XNS, and Apollo Domain

TCP/IP Host-Mode Services

Wide-Area Networking

Caveats for Releases 11.0(1) through 11.0(11)

AppleTalk

Basic System Services

DECnet

IBM Connectivity

Interfaces and Bridging

IP Routing Protocols

Novell IPX, XNS, and Apollo Domain

TCP/IP Host-Mode Services

Wide-Area Networking

Caveats for Releases 11.0(1) through 11.0(10)

AppleTalk

Basic System Services

IBM Connectivity

Interfaces and Bridging

IP Routing Protocols

Novell IPX, XNS, and Apollo Domain

VINES

Wide-Area Networking

Caveats for Releases 11.0(1) through 11.0(9)

AppleTalk

Basic System Services

DECnet

IBM Connectivity

Interfaces and Bridging

IP Routing Protocols

ISO CLNS

Novell IPX, XNS, and Apollo Domain

VINES

Wide-Area Networking

Caveats for Releases 11.0(1) through 11.0(8)

Basic System Services

DECnet

EXEC and Configuration Parser

IBM Connectivity

Interfaces and Bridging

IP Routing Protocols

ISO CLNS

Novell IPX, XNS, and Apollo Domain

Protocol Translation

Wide-Area Networking

Caveats for Releases 11.0(1) through 11.0(7)

AppleTalk

Basic System Services

IBM Connectivity

Interfaces and Bridging

IP Routing Protocols

ISO CLNS

Novell IPX, XNS, and Apollo Domain

VINES

Wide-Area Networking

Caveats for Releases 11.0(1) through 11.0(5)

Basic System Services

DECnet

IBM Connectivity

Interfaces and Bridging

IP Routing Protocols

Novell IPX, XNS, and Apollo Domain

TCP/IP Host-Mode Services

VINES

Wide-Area Networking

Caveats for Releases 11.0(1) through 11.0(4)

AppleTalk

Basic System Services

DECnet

EXEC and Configuration Parser

IBM Connectivity

Interfaces and Bridging

IP Routing Protocols

ISO CLNS

Novell IPX, XNS, and Apollo Domain

Protocol Translation

TCP/IP Host-Mode Services

Wide-Area Networking

Caveats for Releases 11.0(1) through 11.0(3)

AppleTalk

Basic System Services

IBM Connectivity

Interfaces and Bridging

IP Routing Protocols

ISO CLNS

VINES

Wide-Area Networking

Caveats for Releases 11.0(1) through 11.0(2)

AppleTalk

Basic System Services

IBM Connectivity

Interfaces and Bridging

IP Routing Protocols

ISO CLNS

Novell IPX, XNS, and Apollo Domain

Protocol Translation

TCP/IP Host-Mode Services

VINES

Wide-Area Networking

Release 11.0(1) Caveats

AppleTalk

Basic System Services

DECnet

EXEC and Configuration Parser

IBM Connectivity

Interfaces and Bridging

IP Routing Protocols

Protocol Translation

TCP/IP Host-Mode Services

TN3270

VINES

Wide-Area Networking

Microcode Software

Microcode Revision History (for Cisco 7000 Series Platforms)

ATM Interface Processor (AIP) Microcode Revision Summary

AIP Microcode Version 10.9

AIP Microcode Version 10.10

AIP Microcode Version 10.11

AIP Microcode Version 10.12

AIP Microcode Version 10.13

AIP Microcode Version 10.14

AIP Microcode Version 10.15

AIP Microcode Version 10.16

AIP Microcode Version 10.17

Channel Interface Processor (CIP) Microcode Revision Summary

CIP Microcode Version 11.1

CIP Microcode Version 11.2

CIP Microcode Version 11.3

CIP Microcode Version 11.4

CIP Microcode Version 21.3

Second-Generation Channel Interface Processor (CIP2) Microcode Revision Summary

Fast Ethernet Interface Processor (FEIP) Microcode Revision Summary

FEIP Microcode Version 10.1

FEIP Microcode Version 10.2

FEIP Microcode Version 10.3

FEIP Microcode Version 10.4

FEIP Microcode Version 10.5

FEIP Microcode Version 10.6

FEIP Microcode Version 10.7

Fast Serial Interface Processor (FSIP) Microcode Revision Summary

FSIP Microcode Version 10.11

FSIP Microcode Version 10.12

FSIP Microcode Version 10.13

FSIP Microcode Version 10.14

FSIP Microcode Version 10.15

FSIP Microcode Version 10.16

FSIP Microcode Version 10.17

FSIP Microcode Version 10.18

MultiChannel Interface Processor (MIP) Microcode Revision Summary

MIP Microcode Version 11.3

MIP Microcode Version 11.4

MIP Microcode Version 11.5

Switch Processor (SP) Microcode Revision Summary

SP Microcode Version 10.13

SP Microcode Version 10.14

SP Microcode Version 10.15

Silicon Switch Processor (SSP) Microcode Revision Summary

SSP Microcode Version 10.13

SSP Microcode Version 10.14

SSP Microcode Version 10.15

Token Ring Interface Processor (TRIP) Microcode Revision Summary

TRIP Microcode Version 10.3

TRIP Microcode Version 10.4

Route Switch Processor (RSP) Microcode Revision History

ATM Interface Processor (AIP) Microcode Revision Summary

AIP Microcode Version 20.2

AIP Microcode Version 20.3

AIP Microcode Version 20.4

AIP Microcode Version 20.5

AIP Microcode Version 20.6

AIP Microcode Version 20.7

AIP Microcode Version 20.8

AIP Microcode Version 20.9

AIP Microcode Version 20.10

Channel Interface Processor (CIP) Microcode Revision Summary

CIP Microcode Version 21.2

CIP Microcode Version 21.3

CIP Microcode Version 21.4

CIP Microcode Version 21.5

CIP Microcode Version 21.6

CIP Microcode Version 21.7

CIP Microcode Version 21.8

CIP Microcode Version 21.9

CIP Microcode Version 21.11

CIP Microcode Version 21.12

CIP Microcode Version 21.13

CIP Microcode Version 21.14

CIP Microcode Version 21.15

CIP Microcode Version 21.16

CIP Microcode Version 21.17

CIP Microcode Version 21.18

CIP Microcode Version 21.19

CIP Microcode Version 21.20

CIP Microcode Version 21.21

CIP Microcode Version 21.22

Second-Generation Channel Interface Processor (CIP2) Microcode Revision Summary

Ethernet Interface Processor (EIP) Microcode Revision Summary

EIP Microcode Version 20.1

EIP Microcode Version 20.2

EIP Microcode Version 20.3

Fast Ethernet Interface Processor (FEIP) Microcode Revision Summary

FEIP Microcode Version 20.2

FEIP Microcode Version 20.3

FEIP Microcode Version 20.4

FEIP Microcode Version 20.5

FEIP Microcode Version 20.6

Fast Serial Interface Processor (FSIP) Microcode Revision Summary

FSIP Microcode Version 20.2

FSIP Microcode Version 20.3

FSIP Microcode Version 20.4

FSIP Microcode Version 20.5

FSIP Microcode Version 20.6

FSIP Microcode Version 20.7

HSSI Interface Processor (HIP) Microcode Revision Summary

HIP Microcode Version 20.2

MultiChannel Interface Processor (MIP) Microcode Revision Summary

MIP Microcode Version 20.3

MIP Microcode Version 20.4

Token Ring Interface Processor (TRIP) Microcode Revision Summary

TRIP Microcode Version 20.1

Cisco Connection Online

Documentation CD-ROM

Router Products Release Notes for Cisco IOS Release 11.0

---

March 19, 2001

---

Note   Cisco IOS Release 11.0 is scheduled to go End of Engineering (EOE) July 2000. End of Engineering refers to the date of the last scheduled maintenance release (TAC support is still available after End of Engineering). Cisco IOS Release 11.0 will be supported through January 2001 for any Y2K issues. These release notes will be the last release notes published for Cisco IOS Release 11.0.

---

These release notes describe the features and caveats for Cisco IOS Release 11.0 up to and including Release 11.0(22a). They include all routing and protocol translation features.

Cisco IOS Release 11.0(11) and all subsequent 11.0 releases are deemed "Generally Deployable." Cisco believes Release 11.0 is suitable for deployment anywhere in the network where the features and functionality of the release are required.

Introduction

These release notes discuss the following topics:

•Documentation

•Platform Support

•Cisco IOS Packaging

•Memory Requirements

•New Features in Release 11.0(11) and Later 11.0 Releases

•New Features in Release 11.0(10)

•New Features in Release 11.0(9)

•New Features in Release 11.0(8)

•New Features in Release 11.0(7)

•New Features in Release 11.0(6)

•New Features in Release 11.0(5)

•New Features in Release 11.0(4)

•New Features in Release 11.0(3)

•New Features in Release 11.0(2)

•New Features in Release 11.0(1)

•Important Notes

•Caveats for Release 11.0(1) through 11.0(22a)

•Caveats for Release 11.0(1) through 11.0(22)

•Caveats for Release 11.0(1) through 11.0(21)

•Caveats for Release 11.0(1) through 11.0(20)

•Caveats for Releases 11.0(1) through 11.0(19)

•Caveats for Releases 11.0(1) through 11.0(18)

•Caveats for Releases 11.0(1) through 11.0(17)

•Caveats for Releases 11.0(1) through 11.0(16)

•Caveats for Releases 11.0(1) through 11.0(15)

•Caveats for Releases 11.0(1) through 11.0(14)

•Caveats for Releases 11.0(1) through 11.0(13)

•Caveats for Releases 11.0(1) through 11.0(12)

•Caveats for Releases 11.0(1) through 11.0(11)

•Caveats for Releases 11.0(1) through 11.0(10)

•Caveats for Releases 11.0(1) through 11.0(9)

•Caveats for Releases 11.0(1) through 11.0(8)

•Caveats for Releases 11.0(1) through 11.0(7)

•Caveats for Releases 11.0(1) through 11.0(5)

•Caveats for Releases 11.0(1) through 11.0(4)

•Caveats for Releases 11.0(1) through 11.0(3)

•Caveats for Releases 11.0(1) through 11.0(2)

•Release 11.0(1) Caveats

•Microcode Software

•Microcode Revision History (for Cisco 7000 Series Platforms)

•Route Switch Processor (RSP) Microcode Revision History

•Cisco Connection Online

•Documentation CD-ROM

Documentation

Cisco IOS Release 11.0 router software functionality and configuration information is documented in three publications. (Release 11.0 access server software is documented separately.) Refer to these publications for complete information about using and configuring Release 11.0 software:

•Router Products Configuration Guide

•Router Products Command Reference

•Protocol Translation Configuration Guide and Command Reference

There are also five supporting documents:

•Router Products Command Summary

•Cisco Management Information Base (MIB) User Quick Reference

•System Error Messages

•Debug Command Reference

•Cisco Access Connection Guide

All these documents are available both as printed manuals and as electronic documents. The most up-to-date Cisco IOS documentation can be found on the latest Documentation CD-ROM and on the Web. The electronic documents contain updates and modifications made after the paper documents were printed.

You can access the electronic documents either on the Cisco Documentation CD-ROM, or at Cisco Connection Online (CCO) on the World Wide Web.

On the CD-ROM, within the Cisco IOS Software Configuration database, select Cisco IOS Release 11.0.

CCO is on the World Wide Web at http://www.cisco.com, http://www-europe.cisco.com, or http://www-china.cisco.com. From CCO, go to the Documentation page to find the Cisco IOS Software Configuration database. Then, select Cisco IOS Release 11.0.

Additional information about CCO and the Documentation CD-ROM is in the sections "Cisco Connection Online" and "Documentation CD-ROM" at the end of these release notes.

Platform Support

You can run all Cisco IOS 11.0 Releases on these Cisco platforms, except as noted:

•Cisco 7500 series

•Cisco 7000 series

•Cisco 4000 series (Cisco 4000, 4000-M, 4500, 4500-M, 4700, and 4700-M)
(you cannot run Cisco IOS Release 11.0(1) on Cisco 4700 platforms, and
you cannot run Cisco IOS Releases 11.0(1) through 11.0(6) on Cisco 4700-M platforms)

•Cisco 3000 series (except the Cisco 3202)

•Cisco 2500 series (you cannot run Cisco IOS Releases 11.0(1) through 11.0(4) on the Cisco 2520 through 2525 platforms)

•Cisco 1003 ISDN router (you cannot run Cisco IOS Release 11.0(1) on this platform)

•Cisco 1004 ISDN router (you cannot run Cisco IOS Releases 11.0(1) or 11.0(2) on this platform)

•Cisco 1005 router (you cannot run Cisco IOS Releases 11.0(1) through 11.0(3) on this platform)

•AGS+ (with a CSC/4 processor board)

•MGS (with a CSC/4 processor board)

•CGS (with a CSC/4 processor board)

---

Note   To use Release 11.0 features, AGS+, MGS, and CGS routers must have CSC/4 processor cards and 9.1(8)-level (or later) system ROMs for netbooting.

---

---

Note   Cisco IOS Release 11.0 is the last release supported on the Gateway Server Product Line, specifically the AGS+/4, AGS/4, MGS/4, and CGS/4 platforms. Later releases will not run on these platforms.

---

For each of the supported platforms, Release 11.0 enables your Cisco device to use certain LAN and WAN interfaces and data rates.

For a list of interfaces supported by Release 11.0 for each platform, see Table 1 and Table 2.

Table 1 summarizes the LAN interfaces supported on each platform.

Table 2 summarizes the WAN data rates and interfaces supported on each platform.

For each platform, you can use any of the interfaces or data rates labeled "Yes" in the table. Release 11.0 does not support interfaces or data rates that are not labeled "Yes."

 

Table 1 LAN Interfaces Supported by Router Platforms 

Interface	Cisco 7500 Series	Cisco 7000 Series	Cisco 4000 Series	Cisco 3000 Series1	Cisco 2500 Series	Cisco 1000 Series	AGS+	MGS	CGS
Ethernet (AUI)	Yes	Yes	Yes	Yes	Yes	—	Yes	Yes	Yes
Ethernet (10BaseT)	Yes	Yes2	Yes	—	Yes (some platforms3 )	Yes	Yes	—	—
Fast Ethernet (100BaseTX)	Yes	Yes	—	—	—	—	—	—	—
4-Mbps Token Ring	Yes	Yes	Yes	Yes	Yes	—	Yes	Yes	Yes
16-Mbps Token Ring	Yes	Yes	Yes	Yes	Yes	—	Yes	Yes	Yes
FDDI DAS	Yes	Yes	Yes	—	—	—	Yes	—	—
FDDI SAS	Yes	Yes	Yes	—	—	—	Yes	—	—
FDDI multimode	Yes	Yes	Yes (DAS/SAS)	—	—	—	Yes	—	—
FDDI single-mode	Yes	Yes	Yes	—	—	—	Yes	—	—
ATM Interface	Yes	Yes	Yes	—	—	—	—	—	—
Channel Interface Processor (CIP)	Yes	Yes	—	—	—	—	—	—	—
Second-generation Channel Interface Processor (CIP2)4	Yes	Yes		—	—	—	—	—	—
Channelized E1/T1	Yes	Yes	Yes	—	—	—	—	—	—

1 Except the Cisco 3202. 2 Requires an RSP7000 card. 3 The Cisco 2516, 2518, 2520, 2522, and 2524 platforms support Ethernet 10BaseT. The other Cisco 2500 series platforms do not support Ethernet 10BaseT. 4 The second-generation Channel Interface Processor (CIP2) support was introduced in Release 11.0(10).

 

Table 2 WAN Data Rates and Interfaces Supported by Router Platforms 

	Cisco 7500 Series	Cisco 7000 Series	Cisco 4000 Series	Cisco 3000 Series1	Cisco 2500 Series	Cisco 1003/ 1004	Cisco 1005	AGS+	MGS	CGS
Data Rate
48/56/64 kbps	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
1.544/2.048 Mbps	Yes	Yes	Yes	Yes	Yes	—	Yes	Yes	Yes	Yes
34/45/52 Mbps	Yes	Yes	Yes	—	—	—	—	Yes	—	—
Interface
EIA/TIA-232	Yes	Yes	Yes	Yes	Yes	—	Yes	Yes	-	-
X.21	Yes	Yes	Yes	Yes	Yes	—	Yes	Yes	-	-
V.35	Yes	Yes	Yes	Yes	Yes	—	Yes	Yes	-	-
EIA/TIA-449	Yes	Yes	Yes	Yes	Yes	—	Yes	Yes	-	-
EIA-530	Yes	Yes	Yes	Yes	Yes	—	Yes	—	-	-
EIA/TIA-613 (HSSI)	Yes	Yes	—	—	—	—	—	Yes	-	-
ISDN BRI	—	—	Yes	Yes	Yes	Yes	—	—	-	-
ISDN PRI	Yes	Yes	Yes	—	—	—	—	—	-	-
G.703/G.704	Yes	Yes	Yes	—	—	—	—	Yes	-	-

1 Except the Cisco 3202.

Cisco IOS Packaging

The Cisco IOS software is packaged into "feature sets" (also called "software images"). There are many different feature sets available, and each feature set contains a specific subset of Cisco IOS features. Not all feature sets are available with all platforms. Also, some feature sets support different features when run on different platforms.

To learn what features are available with each feature set, see tables through (following). These tables summarize what features you can use when running a specific feature set on a specific platform. A "Yes" in the table indicates that the feature is available in the feature set.

summarizes the feature sets and optional licenses for the Cisco 7500 series platforms.

Table 4Table 5 Table 4summarizes the feature sets and optional licenses for the Cisco 7000 series, AGS+, MGS, and CGS platforms.

summarizes the feature sets for the Cisco 2500 series platforms.

lists the features sets for the Cisco 4000 series platforms.

summarizes the software for the Cisco 3000 series platforms.

summarizes the software for the Cisco 1003 and Cisco 1004 ISDN routers.

summarizes the software for the Cisco 1005 router.

Table 3 Cisco 7500 Series Software Feature Sets 

Feature	Feature Set
	Enterprise	Enterprise/ APPN	Enterprise/CIP2	Enterprise/ APPN/CIP2
SNMP	Yes	Yes	Yes	Yes
Asynchronous support (SLIP)	Yes	Yes	Yes	Yes
Frame Relay	Yes	Yes	Yes	Yes
SMDS	Yes	Yes	Yes	Yes
X.25	Yes	Yes	Yes	Yes
ISDN	Yes	Yes	Yes	Yes
PPP	Yes	Yes	Yes	Yes
HDLC	Yes	Yes	Yes	Yes
IP	Yes	Yes	Yes	Yes
RIP	Yes	Yes	Yes	Yes
IGRP	Yes	Yes	Yes	Yes
Enhanced IGRP	Yes	Yes	Yes	Yes
OSPF	Yes	Yes	Yes	Yes
BGP	Yes	Yes	Yes	Yes
EGP	Yes	Yes	Yes	Yes
PIM	Yes	Yes	Yes	Yes
NHRP	Yes	Yes	Yes	Yes
ES-IS	Yes	Yes	Yes	Yes
IS-IS	Yes	Yes	Yes	Yes
Snapshot routing	Yes	Yes	Yes	Yes
NTP	Yes	Yes	Yes	Yes
Transparent bridging	Yes	Yes	Yes	Yes
Translational bridging	Yes	Yes	Yes	Yes
Multiring	Yes	Yes	Yes	Yes
LAN extension host	Yes	Yes	Yes	Yes
IPX	Yes	Yes	Yes	Yes
NLSP	Yes	Yes	Yes	Yes
IPXWAN 2.0	Yes	Yes	Yes	Yes
AppleTalk Versions 1 and 2	Yes	Yes	Yes	Yes
AURP	Yes	Yes	Yes	Yes
DECnet IV, V	Yes	Yes	Yes	Yes
Apollo Domain	Yes	Yes	Yes	Yes
Banyan VINES	Yes	Yes	Yes	Yes
ISO CLNS	Yes	Yes	Yes	Yes
XNS	Yes	Yes	Yes	Yes
SRB	Yes	Yes	Yes	Yes
RSRB	Yes	Yes	Yes	Yes
APPN	—	Yes	—	Yes
DLSw (RFC 1795)	Yes	Yes	Yes	Yes
DLSw+	Yes	Yes	Yes	Yes
SDLC	Yes	Yes	Yes	Yes
SDLLC	Yes	Yes	Yes	Yes
STUN	Yes	Yes	Yes	Yes
TG/COS	Yes	Yes	Yes	Yes
QLLC	Yes	Yes	Yes	Yes
DSPU	Yes	Yes	Yes	Yes
Telnet	Yes	Yes	Yes	Yes
AutoInstall	Yes	Yes	Yes	Yes
DHCP	Yes	Yes	Yes	Yes
Router monitoring	Yes	Yes	Yes	Yes
CIP	Yes	Yes	—	—
CIP2	—	—	Yes	Yes

 

Table 4 Cisco 7000 Series, AGS+, MGS, and CGS Software Feature Sets 

Feature	Feature Set
	Enterprise	Source-Route Switch1	Enterprise/ APPN2	Enterprise/ CIP2	Enterprise/ APPN/CIP22
SNMP	Yes	Yes	Yes	Yes	Yes
Asynchronous support (SLIP)	Yes	—	Yes	Yes	Yes
Frame Relay	Yes	—	Yes	Yes	Yes
SMDS	Yes	—	Yes	Yes	Yes
X.25	Yes	—	Yes	Yes	Yes
ISDN	Yes	—	Yes	Yes	Yes
PPP	Yes	—	Yes	Yes	Yes
HDLC	Yes	—	Yes	Yes	Yes
IP	Yes	Yes (host only)	Yes	Yes	Yes
RIP	Yes	—	Yes	Yes	Yes
IGRP	Yes	—	Yes	Yes	Yes
Enhanced IGRP	Yes	—	Yes	Yes	Yes
OSPF	Yes	—	Yes	Yes	Yes
BGP	Yes	—	Yes	Yes	Yes
EGP	Yes	—	Yes	Yes	Yes
PIM	Yes	—	Yes	Yes	Yes
NHRP	Yes	—	Yes	Yes	Yes
ES-IS	Yes	—	Yes	Yes	Yes
IS-IS	Yes	—	Yes	Yes	Yes
Snapshot routing	Yes	—	Yes	Yes	Yes
NTP	Yes	—	Yes	Yes	Yes
Transparent bridging	Yes	Yes	Yes	Yes	Yes
Translational bridging	Yes	—	Yes	Yes	Yes
Multiring	Yes	—	Yes	Yes	Yes
LAN extension host	Yes	—	Yes	Yes	Yes
IPX	Yes	—	Yes	Yes	Yes
NLSP	Yes	—	Yes	Yes	Yes
IPXWAN 2.0	Yes	—	Yes	Yes	Yes
AppleTalk Versions 1 and 2	Yes	—	Yes	Yes	Yes
AURP	Yes	—	Yes	Yes	Yes
DECnet IV, V	Yes	—	Yes	Yes	Yes
Apollo Domain	Yes	—	Yes	Yes	Yes
Banyan VINES	Yes	—	Yes	Yes	Yes
ISO CLNS	Yes	—	Yes	Yes	Yes
XNS	Yes	—	Yes	Yes	Yes
SRB	Yes	Yes	Yes	Yes	Yes
RSRB	Yes	—	Yes	Yes	Yes
APPN	—	—	Yes	—	Yes
DLSw (RFC 1795)	Yes	—	Yes	Yes	Yes
DLSw+	Yes	—	Yes	Yes	Yes
SDLC	Yes	—	Yes	Yes	Yes
SDLLC	Yes	—	Yes	Yes	Yes
STUN	Yes	—	Yes	Yes	Yes
TG/COS	Yes	—	Yes	Yes	Yes
QLLC	Yes	—	Yes	Yes	Yes
DSPU	Yes	—	Yes	Yes	Yes
Telnet	Yes	—	Yes	Yes	Yes
AutoInstall	Yes	—	Yes	Yes	Yes
DHCP	Yes	—	Yes	Yes	Yes
Router monitoring	Yes	Yes	Yes	Yes	Yes
CIP	Yes	Yes	Yes	—	—
CIP2	—	—	—	Yes	Yes

1 The Source-Route Switch feature set applies to the Cisco 7000 and Cisco 7010 only, not to the AGS+, MGS, or CGS. 2 The Enterprise/APPN and Enterprise/APPN/CIP2 applies to the Cisco 7000, Cisco 7010, and AGS+ only.

 

Table 5 Cisco 2500 Series Software Feature Sets 

Feature	Feature Set
	IP	IP/IBM Base	IP/IPX	IP/IPX/ IBM Base	IP/IPX/ IBM/ APPN	Desk- top	Desktop/ IBM Base	Enter- prise	Enter- prise/ APPN	CFRAD	ISDN	LAN FRAD
SNMP	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Asynchronous support (SLIP)	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
CSLIP	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
ARAP	—	—	—	—	—	Yes	Yes	Yes	Yes	—	—	—
Frame Relay (RFC 1490)	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	—	Yes
SMDS	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	—	—	—
X.25	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	—	—	—
ISDN	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	—	Yes	—
PPP	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
CPPP	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
HDLC	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	—	—	Yes
IP	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
RIP	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
IGRP	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Enhanced IGRP	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
OSPF	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	—	Yes	Yes
BGP	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	—	Yes	—
EGP	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	—	Yes	—
PIM	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	—	Yes	—
NHRP	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	—	Yes	—
ES-IS	—	—	—	—	—	—	—	Yes	Yes	—	—	—
IS-IS	—	—	—	—	—	—	—	Yes	Yes	—	—	—
Snapshot routing	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	—	Yes	—
NTP	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	—	—	—
Bridging (transparent and translational)	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	—	Yes	Yes
Multiring	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	—	Yes	Yes
LAN extension host	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	—	—	—
IPX	—	—	Yes	Yes	Yes	Yes	Yes	Yes	Yes	—	Yes	Yes
NLSP	—	—	Yes	Yes	Yes	Yes	Yes	Yes	Yes	—	—	—
IPXWAN 2.0	—	—	Yes	Yes	Yes	Yes	Yes	Yes	Yes	—	—	Yes
RTMP	—	—	—	—	—	Yes	Yes	Yes	Yes	—	—	—
SMRP	—	—	—	—	—	Yes	Yes	Yes	Yes	—	—	—
SRTP	—	—	—	—	—	—	—	Yes	Yes	—	—	—
AppleTalk Versions 1 and 2	—	—	—	—	—	Yes	Yes	Yes	Yes	—	Yes	—
AURP	—	—	—	—	—	Yes	Yes	Yes	Yes	—	Yes	—
DECnet IV	—	—	—	—	—	Yes	Yes	Yes	Yes	—	—	—
DECnet V	—	—	—	—	—	—	—	Yes	Yes	—	—	—
Apollo Domain	—	—	—	—	—	—	—	Yes	Yes	—	—	—
Banyan VINES	—	—	—	—	—	—	—	Yes	Yes	—	—	—
ISO CLNS	—	—	—	—	—	—	—	Yes	Yes	—	—	—
XNS	—	—	—	—	—	—	—	Yes	Yes	—	—	—
SRB	—	Yes	—	Yes	Yes	—	Yes	Yes	Yes	—	—	Yes
RSRB	—	Yes	—	Yes	Yes	—	Yes	Yes	Yes	Yes	—	Yes
APPN	—	—	—	—	Yes	—	—	—	Yes	—	—	—
DLSw (RFC 1795)	—	Yes	—	Yes	Yes	—	Yes	Yes	Yes	Yes	—	Yes
DLSw+	—	Yes	—	Yes	Yes	—	Yes	Yes	Yes	—	—	—
SDLC	—	Yes	—	Yes	Yes	—	Yes	Yes	Yes	Yes	—	Yes
SDLLC	—	Yes	—	Yes	Yes	—	Yes	Yes	Yes	Yes	—	Yes
STUN	—	Yes	—	Yes	Yes	—	Yes	Yes	Yes	Yes	—	Yes
TG/COS	—	—	—	—	—	—	—	Yes	Yes	—	—	—
QLLC	—	Yes	—	Yes	Yes	—	Yes	Yes	Yes	—	—	—
Bisync	—	Yes	—	Yes	Yes	—	Yes	Yes	Yes	Yes	—	Yes
DSPU	—	—	—	—	—	—	—	Yes	Yes	—	—	—
Protocol translation	—	—	—	—	—	—	—	Yes	Yes	—	—	—
TN3270	—	—	—	—	—	—	—	Yes	Yes	—	—	—
LAT	—	—	—	—	—	—	—	Yes	Yes	—	—	—
XRemote	—	—	—	—	—	—	—	Yes	Yes	—	—	—
Telnet	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
AutoInstall	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	—	Yes
DHCP	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	—	Yes	—
Router monitoring	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes

Table 6 Cisco 4000 Series Software Feature Sets 

Feature	Feature Set
	IP	IP/IBM Base	IP/IPX	IP/IPX/ IBM Base	IP/IPX/ IBM/ APPN	Desktop	Desktop/ IBM Base	Enterprise	Enterprise/APPN
SNMP	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Asynchronous support (SLIP)	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
ARAP	—	—	—	—	—	—	—	—	—
Frame Relay (RFC 1490)	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
SMDS	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
X.25	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
ISDN	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
PPP	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
HDLC	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
IP	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
RIP	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
IGRP	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Enhanced IGRP	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
OSPF	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
BGP	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
EGP	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
PIM	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
NHRP	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
ES-IS	—	—	—	—	—	—	—	Yes	Yes
IS-IS	—	—	—	—	—	—	—	Yes	Yes
Snapshot routing	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
NTP	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Bridging (transparent and translational)	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Multiring	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
LAN extension host	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
IPX	—	—	Yes	Yes	Yes	Yes	Yes	Yes	Yes
NLSP	—	—	Yes	Yes	Yes	Yes	Yes	Yes	Yes
RTMP	—	—	—	—	—	Yes	Yes	Yes	Yes
SMRP	—	—	—	—	—	Yes	Yes	Yes	Yes
SRTP	—	—	—	—	—	—	—	Yes	Yes
IPXWAN 2.0	—	—	Yes	Yes	Yes	Yes	Yes	Yes	Yes
AppleTalk Versions 1 and 2	—	—	—	—	—	Yes	Yes	Yes	Yes
AURP	—	—	—	—	—	Yes	Yes	Yes	Yes
DECnet IV	—	—	—	—	—	Yes	Yes	Yes	Yes
DECnet V	—	—	—	—	—	—	—	Yes	Yes
Apollo Domain	—	—	—	—	—	—	—	Yes	Yes
Banyan VINES	—	—	—	—	—	—	—	Yes	Yes
ISO CLNS	—	—	—	—	—	—	—	Yes	Yes
XNS	—	—	—	—	—	—	—	Yes	Yes
SRB	—	Yes	—	Yes	Yes	—	Yes	Yes	Yes
RSRB	—	Yes	—	Yes	Yes	—	Yes	Yes	Yes
APPN	—	—	—	—	Yes	—	—	—	Yes
DLSw (RFC 1795)	—	Yes	—	Yes	Yes	—	Yes	Yes	Yes
DLSw+	—	Yes	—	Yes	Yes	—	Yes	Yes	Yes
SDLC	—	Yes	—	Yes	Yes	—	Yes	Yes	Yes
SDLLC	—	Yes	—	Yes	Yes	—	Yes	Yes	Yes
STUN	—	Yes	—	Yes	Yes	—	Yes	Yes	Yes
TG/COS	—	—	—	—	—	—	—	Yes	Yes
QLLC	—	Yes	—	Yes	Yes	—	Yes	Yes	Yes
Bisync	—	Yes	—	Yes	Yes	—	Yes	Yes	Yes
DSPU	—	—	—	—	—	—	—	Yes	Yes
Protocol translation	—	—	—	—	—	—	—	Yes	Yes
TN3270	—	—	—	—	—	—	—	Yes	Yes
LAT	—	—	—	—	—	—	—	Yes	Yes
XRemote	—	—	—	—	—	—	—	Yes	Yes
Telnet	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
AutoInstall	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
DHCP	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Router monitoring	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes

Table 7 Cisco 3000 Series Software Feature Set 

Feature	Feature Set
	Enterprise
SNMP	Yes
Asynchronous support (SLIP)	Yes
ARAP	Yes
Frame Relay	Yes
SMDS	Yes
X.25	Yes
ISDN	Yes
PPP	Yes
HDLC	Yes
IP	Yes
RIP	Yes
IGRP	Yes
Enhanced IGRP	Yes
OSPF	Yes
BGP	Yes
EGP	Yes
PIM	Yes
NHRP	Yes
ES-IS	Yes
IS-IS	Yes
Snapshot routing	Yes
NTP	Yes
Transparent bridging	Yes
Translational bridging	Yes
Multiring	Yes
LAN extension host	Yes
IPX	Yes
NLSP	Yes
IPXWAN 2.0	Yes
AppleTalk Versions 1 and 2	Yes
AURP	Yes
DECnet	Yes
Apollo Domain	Yes
Banyan VINES	Yes
ISO CLNS	Yes
XNS	Yes
SRB	Yes
RSRB	Yes
APPN	—
DLSw (RFC 1795)	Yes
DLSw+	Yes
SDLC	Yes
SDLLC	Yes
STUN	Yes
TG/COS	Yes
QLLC	Yes
Bisync	Yes
DSPU	Yes
AutoInstall	Yes
Telnet	Yes
Protocol translation	Yes
TN3270	Yes
LAT	Yes
XRemote	Yes
DHCP	Yes
Router monitoring	Yes

Table 8 Cisco 1003 and Cisco 1004 ISDN Routers Software Feature Sets 

Feature	Feature Set
	IP	IP/IPX/AT	IP/AT	IP/IPX
SNMP	Yes	Yes	Yes	Yes
Asynchronous support (SLIP)	—	—	—	—
ARAP	—	—	—	—
Frame Relay (RFC 1490)	—	—	—	—
SMDS	—	—	—	—
X.25	—	—	—	—
ISDN	Yes	Yes	Yes	Yes
PPP	Yes	Yes	Yes	Yes
HDLC	Yes	Yes	Yes	Yes
IP	Yes	Yes	Yes	Yes
RIP	Yes	Yes	Yes	Yes
IGRP	Yes	Yes	Yes	Yes
Enhanced IGRP	Yes	Yes	Yes	Yes
OSPF	—	—	—	—
BGP	—	—	—	—
EGP	—	—	—	—
PIM	—	—	—	—
NHRP	—	—	—	—
ES-IS	—	—	—	—
IS-IS	—	—	—	—
Snapshot routing	Yes	Yes	Yes	Yes
NTP	—	—	—	—
Bridging (transparent)	Yes	Yes	Yes	Yes
Multiring	—	—	—	—
LAN extension host	—	—	—	—
IPX	—	Yes	—	Yes
NLSP	—	—	—	—
IPXWAN 2.0	—	Yes	—	Yes
AppleTalk Versions 1 and 2	—	Yes	Yes	—
AURP	—	—	—	—
DECnet IV	—	—	—	—
DECnet V	—	—	—	—
Apollo Domain	—	—	—	—
Banyan VINES	—	—	—	—
ISO CLNS	—	—	—	—
XNS	—	—	—	—
SRB	—	—	—	—
RSRB	—	—	—	—
DLSw (RFC 1795)	—	—	—	—
DLSw+	—	—	—	—
SDLC	—	—	—	—
SDLLC	—	—	—	—
STUN	—	—	—	—
TG/COS	—	—	—	—
QLLC	—	—	—	—
DSPU	—	—	—	—
Protocol translation	—	—	—	—
TN3270	—	—	—	—
LAT	—	—	—	—
XRemote	—	—	—	—
Telnet	Yes	Yes	Yes	Yes
AutoInstall	—	—	—	—
ClickStart	Yes	Yes	Yes	Yes
Router monitoring	Yes	Yes	Yes	Yes
DHCP	—	—	—	—

Table 9 Cisco 1005 Router Software Feature Sets 

Feature	Feature Set
	IP	IP/IPX	IP/IPX/ X25	IP/AT	IP/AT/ X25	IP/IPX/ AT	IP/IPX/ AT/X25	IP/OSPF/ PIM	IP/IPX/ Async	IP/ Async
SNMP	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Asynchronous support (SLIP)	—	—	—	—	—	—	—	—	Yes	Yes
ARAP	—	—	—	—	—	—	—	—	—	—
Frame Relay (RFC 1490)	Yes	Yes	—	Yes	—	Yes	—	Yes	—	—
SMDS	Yes	Yes	—	Yes	—	Yes	—	Yes	—	—
X.25	Yes	—	Yes	—	Yes	—	Yes	Yes	—	—
ISDN	—	—	—	—	—	—	—	—	—	—
PPP	Yes	Yes	—	Yes	—	Yes	—	Yes	Yes	Yes
HDLC	Yes	Yes	—	Yes	—	Yes	—	Yes	—	—
IP	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
RIP	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
IGRP	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Enhanced IGRP	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
OSPF	—	—	—	—	—	—	—	Yes	—	—
BGP	—	—	—	—	—	—	—	—	—	—
EGP	—	—	—	—	—	—	—	—	—	—
PIM	—	—	—	—	—	—	—	Yes	—	—
NHRP	—	—	—	—	—	—	—	—	—	—
ES-IS	—	—	—	—	—	—	—	—	—	—
IS-IS	—	—	—	—	—	—	—	—	—	—
Snapshot routing	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
NTP	—	—	—	—	—	—	—	—	—	—
Bridging (transparent)	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	—	—
Multiring	—	—	—	—	—	—	—	—	—	—
LAN extension host	—	—	—	—	—	—	—	—	—	—
IPX	—	Yes	Yes	Yes	—	Yes	Yes	—	Yes	—
NLSP	—	—	—	—	—	—	—	—	—	—
IPXWAN 2.0	—	Yes	Yes	Yes	—	Yes	Yes	—	Yes	—
AppleTalk Versions 1 and 2	—	—	—	Yes	Yes	Yes	Yes	—	—	—
AURP	—	—	—	—	—	—	—	—	—	—
DECnet IV	—	—	—	—	—	—	—	—	—	—
DECnet V	—	—	—	—	—	—	—	—	—	—
Apollo Domain	—	—	—	—	—	—	—	—	—	—
Banyan VINES	—	—	—	—	—	—	—	—	—	—
ISO CLNS	—	—	—	—	—	—	—	—	—	—
XNS	—	—	—	—	—	—	—	—	—	—
Source-route bridging/ remote source-route bridging	—	—	—	—	—	—	—	—	—	—
DLSw (RFC 1795)	—	—	—	—	—	—	—	—	—	—
DLSw+	—	—	—	—	—	—	—	—	—	—
SDLC	—	—	—	—	—	—	—	—	—	—
SDLLC	—	—	—	—	—	—	—	—	—	—
STUN	—	—	—	—	—	—	—	—	—	—
TG/COS	—	—	—	—	—	—	—	—	—	—
QLLC	—	—	—	—	—	—	—	—	—	—
DSPU	—	—	—	—	—	—	—	—	—	—
Protocol translation	—	—	—	—	—	—	—	—	—	—
TN3270	—	—	—	—	—	—	—	—	—	—
LAT	—	—	—	—	—	—	—	—	—	—
XRemote	—	—	—	—	—	—	—	—	—	—
Telnet	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
AutoInstall	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	—	—
ClickStart	—	—	—	—	—	—	—	—	—	—
DHCP	—	—	—	—	—	—	—	—	—	—
Router monitoring	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes

Memory Requirements

Beginning with Cisco IOS Release 10.3, some software image (feature set) sizes exceed 4 MB and, when compressed, exceed 2 MB. Also, some systems now require more than 1 MB of main system memory for data structure tables.

For Cisco routers to take advantage of the Release 11.0 features, you need to have the code or main system memory as listed in Table 10. If you do not, you must upgrade your memory. Some platforms have specific chip or architecture requirements that affect what can be upgraded and in what increments.

The memory requirements listed in are minimum requirements. Your specific hardware configuration and the software features you chose to deploy could require you to have more memory.

Notes:

•To use Release 11.0 features, AGS+, MGS, and CGS routers must have CSC/4 processor cards and 9.1(8)-level (or later) system ROMs for netbooting.

•The AGS+ platform running the Enterprise/APPN feature set cannot be booted from Flash memory; an upgrade to 8 MB boot ROMs is required.

•For the Cisco 7000 and 7010 routers to recognize Flash memory cards, 11.0 boot ROMs (or later) are required.

Table 10 Release 11.0 Memory Requirements 

Hardware Platform	Minimum Required Code Memory	Required Main Memory		Release 11.0Runs from
Cisco 1003 and Cisco 1004 ISDN Routers
IP Set	2/4/8 MB optional Flash	4 MB RAM		RAM
IP/IPX/AT Set	2/4/8 MB optional Flash	8 MB RAM		RAM
IP/AT Set	2/4/8 MB optional Flash	4 MB RAM		RAM
IP/IPX Set	2/4/8 MB optional Flash	4 MB RAM		RAM
Cisco 1005 Router
IP Set	2/4/8 MB optional Flash	4 MB RAM		RAM
IP/IPX Set	2/4/8 MB optional Flash	4 MB RAM		RAM
IP/IPX/X25 Set	2/4/8 MB optional Flash	4 MB RAM		RAM
IP/AT Set	2/4/8 MB optional Flash	4 MB RAM		RAM
IP/AT/X25 Set	2/4/8 MB optional Flash	4 MB RAM		RAM
IP/IPX/AT Set	2/4/8 MB optional Flash	8 MB RAM		RAM
IP/IPX/AT/X25 Set	2/4/8 MB optional Flash	8 MB RAM		RAM
IP/OSPF/PIM Set	2/4/8 MB optional Flash	4 MB RAM		RAM
IP/IPX/Async Set	2/4/8 MB optional Flash	4 MB RAM		RAM
IP/Async Set	2/4/8 MB optional Flash	4 MB RAM		RAM
Cisco 2500 Series
IP Set	4 MB Flash	2 MB RAM1		Flash
IP/IBM Set	8 MB Flash	4 MB RAM		Flash
IP/IPX Set	4 MB Flash	4 MB RAM		Flash
IP/IPX/IBM Set	8 MB Flash	4 MB RAM		Flash
IP/IPX/IBM/APPN Set	8 MB Flash	8 MB RAM		Flash
Desktop Set	8 MB Flash	4 MB RAM		Flash
Desktop/IBM Set	8 MB Flash	4 MB RAM		Flash
Enterprise Set	8 MB Flash	6 MB RAM		Flash
Enterprise/APPN Set	8 MB Flash	8 MB RAM		Flash
Cisco Frame Relay Access Device (CFRAD) Set	4 MB Flash	2 MB RAM		Flash
ISDN Set	4 MB Flash	4 MB RAM		Flash
LAN FRAD Set	8 MB Flash	4 MB RAM		Flash
Cisco 2501CF, Cisco 2502CF, Cisco 2520CF, Cisco 2521CF
CFRAD Set	4 MB Flash	2 MB RAM		Flash
Cisco 2522CF, Cisco 2523CF
CFRAD Set	4 MB Flash	4 MB RAM		Flash
Cisco 3101, Cisco 3102, Cisco 3103 Enterprise Set	8 MB Flash	4 MB RAM		Flash
	4 MB Flash	16 MB RAM		RAM
Cisco 3104, Cisco 3204 Enterprise Set	8 MB Flash	4 MB RAM		Flash
	4 MB Flash	8 MB RAM		RAM
Cisco 4000, Cisco 4000-M		Cisco 4000	Cisco 4000-M
IP Set	4 MB Flash	16 MB RAM	8 MB RAM	RAM
IP/IBM Set	4 MB Flash	16 MB RAM	8 MB RAM	RAM
IP/IPX Set	4 MB Flash	16 MB RAM	8 MB RAM	RAM
IP/IPX/IBM Set	4 MB Flash	16 MB RAM	8 MB RAM	RAM
IP/IPX/IBM/APPN Set	4 MB Flash	16 MB RAM	16 MB RAM	RAM
Desktop Set	4 MB Flash	16 MB RAM	8 MB RAM	RAM
Desktop/IBM Set	4 MB Flash	16 MB RAM	8 MB RAM	RAM
Enterprise Set	4 MB Flash	16 MB RAM	16 MB RAM	RAM
Enterprise/APPN Set	4 MB Flash	16 MB RAM	16 MB RAM	RAM
Cisco 4500, Cisco 4500-M		Cisco 4500	Cisco 4500-M
IP Set	4 MB Flash	8 MB RAM	8 MB RAM2	RAM
IP/IBM Set	4 MB Flash	32 MB RAM	16 MB RAM	RAM
IP/IPX Set	4 MB Flash	8 MB RAM	8 MB RAM2	RAM
IP/IPX/IBM Set	4 MB Flash	32 MB RAM	16 MB RAM	RAM
IP/IPX/IBM/APPN Set	4 MB Flash	32 MB RAM	16 MB RAM	RAM
Desktop Set	4 MB Flash	32 MB RAM	16 MB RAM	RAM
Desktop/IBM Set	4 MB Flash	32 MB RAM	16 MB RAM	RAM
Enterprise Set	4 MB Flash	32 MB RAM	16 MB RAM	RAM
Enterprise/APPN Set	4 MB Flash	32 MB RAM	16 MB RAM	RAM
Cisco 4700, Cisco 4700-M
IP Set	4 MB Flash	16 MB RAM		RAM
IP/IBM Set	4 MB Flash	16 MB RAM		RAM
IP/IPX Set	4 MB Flash	16 MB RAM		RAM
IP/IPX/IBM Set	4 MB Flash	16 MB RAM		RAM
IP/IPX/IBM/APPN Set	4 MB Flash	16 MB RAM		RAM
Desktop Set	4 MB Flash	16 MB RAM		RAM
Desktop/IBM Set	4 MB Flash	16 MB RAM		RAM
Enterprise Set	4 MB Flash	16 MB RAM		RAM
Enterprise/APPN Set	4 MB Flash	16 MB RAM		RAM
Cisco 7000, Cisco 7010
IP Set	8 MB Flash	16 MB RAM		RAM
IP/IPX/IBM Set	8 MB Flash	16 MB RAM		RAM
IP/IPX/IBM/APPN Set	8 MB Flash	16 MB RAM		RAM
Desktop/IBM Set	8 MB Flash	16 MB RAM		RAM
Enterprise Set	8 MB Flash memory card	16 MB RAM		RAM
Enterprise/APPN Set	8 MB Flash	16 MB RAM		RAM
Enterprise/CIP2 Set	8 MB Flash memory card	16 MB RAM		RAM
Enterprise/APPN/CIP2 Set	8 MB Flash	16 MB RAM		RAM
Source Route Switch	4 MB Flash	16 MB RAM		RAM
AGS+, MGS, CGS
Enterprise Set (AGS+)	4 MB Flash (optional)	16 MB RAM		RAM
Enterprise/APPN Set (AGS+)	—	16 MB RAM		RAM
Enterprise/CIP2 Set (AGS+)	4 MB Flash (optional)	16 MB RAM		RAM
Enterprise/APPN/CIP2 Set (AGS+)	—	16 MB RAM		RAM
Cisco 7500 series, RSP7000
IP Set	8 MB Flash	16 MB RAM		RAM
IP/IPX/IBM Set	8 MB Flash	16 MB RAM		RAM
IP/IPX/IBM/APPN Set	8 MB Flash	16 MB RAM		RAM
Desktop/IBM Set	8 MB Flash	16 MB RAM		RAM
Enterprise Set	8 MB Flash memory card	16 MB RAM3		RAM
Enterprise/APPN Set	8 MB Flash memory card	16 MB RAM3		RAM
Enterprise/CIP2 Set	8 MB Flash memory card	16 MB RAM3		RAM
Enterprise/APPN/CIP2 Set	8 MB Flash memory card	16 MB RAM3		RAM
Cisco 7505
Enterprise Set	8 MB Flash memory card	16 MB RAM3		RAM
Enterprise/APPN Set	8 MB Flash memory card	16 MB RAM3		RAM
Enterprise/CIP2 Set	8 MB Flash memory card	16 MB RAM3		RAM
Enterprise/APPN/CIP2 Set	8 MB Flash memory card	16 MB RAM3		RAM

1 For Cisco 2500 access servers (Cisco 2509-2512) and for Cisco 2520-2523 platforms, 4 MB DRAM is the minimum recommended. 2 The Cisco 4500-M requires 16 MB DRAM when an MBRI, NP-CT1, or NP-CE1 Network Processor Module is installed in the chassis. 3 The minimum recommended main memory is 24 MB for most applications.

New Features in Release 11.0(11) and Later 11.0 Releases

There are no new features added in Release 11.0(11) or in later 11.0 releases. Cisco IOS Release 11.0(11) and later 11.0 releases are considered Generally Deployable (GD). To maintain the stability required in a GD release, no new features are added.

New Features in Release 11.0(10)

---

Note   The first few maintenance releases of each new Cisco IOS software release may deliver additional new features. When deciding whether to deploy a new release, you should weigh the importance you place on maximizing product capability versus maximizing operational stability. An early release of software should always be tried in a test network before being deployed in a production network.

---

The following enhancements were added to Release 11.0(10):

New Feature Sets for CIP2

Cisco IOS Release 11.0(10) supports four new feature sets— two for the Cisco 7000 series and two for the Cisco 7500 series routers. The new feature sets include support for the second-generation Channel Interface Processor (CIP2). All other feature sets that do not include "CIP2" in their names (refer to Table 3 and Table 3 Table 4) support the original CIP card. The new feature sets on both platforms are

•Enterprise/CIP2

•Enterprise/APPN/CIP2

The CIP2 card is the follow-on product to the original CIP card. The CIP2 card provides increases in performance, capacity, reliability, and serviceability.

The CIP2 card includes the following improvements over the original CIP:

•A secondary processor cache (providing a 50% performance increase)

•Increased memory options (CIP2 memory configurations come in 32 MB, 64 MB, and 128 MB)

•An on-board boot Flash, which is software upgradable (allowing upgrades to the boot microcode without physical replacement of parts)

The CIP2 card operates with the CxBus in the Cisco 7000 series routers with either of the following processor types:

•Route Processor (RP) and Switch Processor (SP) (or Silicon Switch Processor [SSP]) combination

•Cisco 7000 Series Route Switch Processor (RSP7000) and Cisco 7000 Series Chassis Interface (RSP7000CI) combination

The Enterprise/CIP2 image or Enterprise/APPN/CIP2 image is required if you will be using the CIP2 card.

---

Note   Second-generation Channel Interface Processor (CIP2) microcode was introduced in Release 11.0(10).

---

New Features in Release 11.0(9)

No new features were added in Release 11.0(9).

New Features in Release 11.0(8)

The following enhancements were added to Release 11.0(8):

New Feature Sets for Cisco 1005

Cisco IOS Release 11.0(8) supports three new Cisco 1005 feature sets:

•IP/OSPF/PIM

•IP/Async

•IP/IPX/Async

Refer to for a list of features included in each of these sets.

UDP Turbo Flooding for Cisco 7500

User Datagram Protocol (UDP) datagram "turbo" flooding can be used on RSP systems (Cisco 7500 series and RSP7000). Previously, this feature was only supported on Cisco 7000 series routers.

New Features in Release 11.0(7)

The following enhancement was added to Release 11.0(7):

Support for the Cisco 4700-M Router

Release 11.0 now includes support for the Cisco 4700-M router. You can run Release 11.0(7) and later 11.0 releases on the Cisco 4700-M router.

New Features in Release 11.0(6)

---

Note   Cisco IOS Release 11.0(6) consists of software feature-set images for the Cisco 1003, Cisco 1004, and Cisco 1005 platforms only. All feature-set images for these routers are available. A complete set of images for all platforms supported by Release 11.0 is available in Cisco IOS Release 11.0(7) and later.

---

The following enhancements were added to Release 11.0(6):

Channel Service Unit/Data Service Unit (CSU/DSU) Management Information Base (MIB)

A new Cisco-proprietary MIB for integrated CSU/DSU is available in Release 11.0(6) and later. This MIB is available for use with the Cisco 2524 and Cisco 2525 products, and is for T1 and switched 56-kbps interfaces. It enables network managers to retrieve line statistics and CSU/DSU configuration data.

Support for the Cisco RSP7000

The RSP7000 provides an upgrade in the Cisco 7000 series routers to an integrated Route Switch Processor (RSP), which was previously only available with Cisco 7500 series routers. RSP combines the switched routing and high-speed switching functions of the separate Route Processor (RP) and Switch Processor (SP), making obsolete the need for two separate processor units.

RSP7000 functionality is similar to a Cisco 7505 with RSP1, except that CyBus is not supported. CIP, FEIP, and VIP (CyBus interface processors) operate in CxBus mode.

New Configuration Tool - ClickStart

ClickStart allows you to use a standard web browser, such as Netscape or Mosaic, to configure and monitor a Cisco router. You can use ClickStart to configure a Cisco 1003 or Cisco 1004 router that has one Ethernet and one BRI (ISDN) interface. You configure the router to dial your Internet service provider, and your Internet service provider supplies an ISDN connection to the Internet. You can also use ClickStart to monitor any Cisco router that is running Cisco IOS Release 11.0(6) or later.

If you have a Cisco 1003 or Cisco 1004 router, you can automatically use ClickStart to monitor your router.

If you have any other Cisco router, you must enable ClickStart before you can use it to monitor your router. To do this, follow this procedure:

1 To enable ClickStart, use the ip http server global configuration command.

2 By default, ClickStart uses port 80 to communicate with the router. If you want to configure a different port, use the ip http port number global configuration command. number is the number of the port you want to use for ClickStart.

New Features in Release 11.0(5)

The following enhancements were added to Release 11.0(5):

AAL3/4 E3/DS3 for Cisco 4500 and Cisco 4700 ATM NIM

Asynchronous Transfer Mode (ATM) is supported on the Cisco 4500 and Cisco 4700 routers, using the Cisco ATM Network Interface Module (NIM) cards. The ATM adaptation layer 3/4 (AAL3/4), and additional NIM variants for use with E3/DS3 services are supported in Release 11.0(5). ATM on the Cisco 4500 and Cisco 4700 routers is configured differently from that on the Cisco 7000 routers. Refer to the Router Products Configuration Guide for configuration information.

Support for the Cisco 2520, Cisco 2521, Cisco 2522, and Cisco 2523

The Cisco 2520 through Cisco 2523 models merge router and communication server features to serve access and telecommuting requirements in a single platform. WAN aggregation, telecommuting, branch office, and IBM protocol applications are well-suited to these new Cisco devices.

The interfaces available in each model are shown as follows:

Cisco 2520	1 Ethernet, 2 high-speed synchronous serial, 2 low-speed synchronous/asynchronous serial, 1 ISDN BRI
Cisco 2521	1 Token Ring, 2 high-speed synchronous serial, 2 low-speed synchronous/asynchronous serial, 1 ISDN BRI
Cisco 2522	1 Ethernet, 2 high-speed synchronous serial, 8 low-speed synchronous/asynchronous serial, 1 ISDN BRI
Cisco 2523	1 Token Ring, 2 high-speed synchronous serial, 8 low-speed synchronous/asynchronous serial, 1 ISDN BRI

The low-speed serial interfaces (maximum speed 115.2 kbps) are capable of supporting both synchronous and asynchronous protocols.

Support for the Cisco 2524 and Cisco 2525

The Cisco 2524 and Cisco 2525 routers eliminate the need for a separate terminal adapter on the ISDN line, or separate channel service unit/data service units (CSU/DSUs) on the synchronous serial WAN interfaces.

These platforms support a removable BRI or BRI with integrated NT1 interface, a LAN interface (either Ethernet or Token Ring), and two WAN interface slots.

New commands have been added to the Cisco IOS software to support the Cisco 2423 and Cisco 2525.

The Cisco 2524 and Cisco 2525 support RFC 1406, Definitions of Managed Objects for the DS1 and E1 Interface Types.

Cisco IOS Release 11.0(5) also supports the Cisco 2524 and Cisco 2525 routers.

---

Note   The Cisco 2524 and Cisco 2525 require a minimum 11.0(5)-level boot ROM.

---

LAN Frame Relay Access Device (FRAD) Feature Set

The LAN FRAD feature set is supported on the Cisco 2501, Cisco 2502, Cisco 2520, Cisco 2521, Cisco 2522, and Cisco 2523.

Leased Line via ISDN BRI

An ISDN Basic Rate Interface (BRI) can be used as an alternate method of accessing leased lines provided by digital communication service providers. The interface can provide any combination of one 16K (D channel) or two 64K (B channel) leased lines. No signaling or call setup is required.

In some locations, data communications service providers offer leased-line service over the ISDN physical connection. With this service, there is no call setup or teardown required. Data is placed on the ISDN interface in much the same way a leased line connected to a serial port is used.

The leased-line interface supports all commands that a normal serial leased-line interface supports, with the exception of the commands affecting the physical layer. To use this feature, your Cisco router must contain a minimum of one BRI. The command isdn leased-line is added.

New Features in Release 11.0(4)

The following enhancements were added to Release 11.0(4):

Support for the Cisco 1005

The Cisco 1005 synchronous serial router connects small, remote Ethernet LANs to WANs over leased lines, Frame Relay, Switched Multimegabit Data Service (SMDS), Switched-56, and X.25.

New Feature Sets for Cisco 1003 and Cisco 1004 ISDN Routers

Two new feature sets are available:

•IP/AppleTalk (IP/AT)

•IP/IPX

Payload Compression for Frame Relay

This feature allows payload compression of data within Frame Relay packets. Compression is performed on a packet-by-packet basis, yielding a compression ratio of approximately 1.5 to 1, depending on the packet and data characteristics. The command frame-relay payload-compress packet-by-packet is added.

Standard Serial Interface Processor and Service Provider MultiChannel Interface Processor on the Cisco 7000 Series

The Cisco 7000 series now supports the Standard Serial Interface Processor (SSIP) and Service Provider MultiChannel Interface Processor (SMIP).

New Features in Release 11.0(3)

The following enhancements were added to Release 11.0(3):

Support for the Channel Interface Processor (CIP) on the Cisco 7500 Series

Support for IBM channel attach is provided on the Cisco 7500 series routers by the Cisco Channel Interface Processor (CIP) and an appropriate interface adapter card. With a CIP and the ESCON Channel Adapter (ECA) or bus-and-tag Parallel Channel Adapter (PCA), a Cisco 7500 series router can be directly connected to a mainframe. This direct connection replaces the function of an IBM 3172 interconnect controller with no loss in LAN-to-channel connectivity, thus enabling mainframe application and peripheral access from LAN-based workstations. Cisco IOS software supports TCP/IP mainframe protocol environments for the IBM MVS and VM operating systems, including the TCP/IP-based applications Telnet, FTP, SMTP, and NFS.

Dynamic Address Mapping for IPX over SMDS

The new smds glean command dynamically creates SMDS address to higher-level protocol address mappings from incoming packets. Therefore the need for static map configuration for the IPX protocol is optional rather than mandatory. However, static map configurations will override the dynamic maps configurations.

IP Address Pooling Changes

IP address pooling provides a pool of IP addresses from which an incoming interface can provide an IP address to a remote node through the IP Control Protocol (IPCP) address negotiation process. In Cisco IOS Release 11.0(3), the IP address pooling feature is enhanced to allow configuration of a global default address pooling mechanism, a per-interface configuration of the mechanism to use, and a per-interface configuration of a specific address or pool name to use. Cisco IOS Release 11.0(3) also enhances the flexibility of configuration by allowing multiple types of pooling to be active simultaneously.

ISDN B-Channel Setup and Teardown

Previously, an idle timeout was used to determine when to tear down (drop) an ISDN B channel. If there was no traffic on a B channel for the idle timeout period, the B channel would be dropped. Various methods, including "round robin" or "shortest queue" methods, were used to determine when to set up a B channel (depending on the hardware platform in use).

ISDN B channels are now set up or torn down based on the amount of aggregate traffic loading across all active B channels. A new B channel will be set up if the aggregate load exceeds a maximum value for a timeout period. A B channel will be disconnected if the aggregate load drops below a minimum value for a timeout period.

The maximum load value is equal to 64K*N*(load-threshold/255), and the minimum load value is equal to 64K*(N-1)*(load-threshold/255), where N is the number of currently open B channels, and load-threshold is a configurable value.

Multilink PPP

Cisco IOS Release 11.0(3) supports Multilink Point-to-Point Protocol over single or multiple ISDN interfaces. This feature provides load balancing functionality over multiple WAN links, while also providing multivendor interoperability, packet fragmentation and proper sequencing, and load calculation on both inbound and outbound traffic. This feature allows users to specify a load threshold for a link to a given IP address. When the traffic load surpasses that threshold, additional point-to-point links come up. Packets are then sent over all of the links. Cisco's implementation of Multilink PPP supports the fragmentation and packet sequencing specifications in RFC 1717.

Multivendor Flash SIMM Support

With Release 11.0(3), you can use Flash SIMMs from multiple vendors, as long as the total size of each SIMM is equal (if both slots are used, where available), and the SIMMs are installed in one of the combinations shown in (for Cisco 2500 series, Cisco 4000-M, Cisco 4500, and Cisco 4700 platforms) or (for the AccessPro PC card and Cisco 2517 router).

Multivendor Flash support is restricted to platforms that use Rxboot Version 10.2(7a) or later, and Cisco IOS Release 10.2(8), 10.3(6), or 11.0(3) or later. Currently, the Cisco 3000 series and Cisco 4000 series platforms do not support the multivendor Flash feature.

Cisco 2500 series routers (non AccessPro) and the Cisco 4500 and Cisco 4700 routers have two slots for Flash SIMMs. provides the supported SIMM configurations.

Table 11 Flash SIMM Support for the Cisco 2500 Series Platforms, and the Cisco 4000-M, Cisco 4500, and Cisco 4700 

SIMM Size	Vendor	Flash Bank	Considerations
4 MB	Intel (1Mbx8)	Single	None
4 MB/4 MB	Intel/Intel (1Mbx8)	Dual	None
4 MB/4 MB	Intel/AMD (1Mbx8)	Dual	This configuration requires Rxboot Version 10.2(7a) or later. It also requires one of the following Cisco IOS releases: •11.0(3) or later •10.3(6) or later •10.2(8) or later
8 MB	Intel (2Mbx8)	Single	This configuration requires Rxboot Version 10.2(7a) or later. It also requires one of the following Cisco IOS releases: •11.0(1) or later •10.3(1) or later •10.2(2) or later •10.0(6) or later
8 MB/8 MB	Intel/Intel (2Mbx8)	Dual	This configuration requires Rxboot Version 10.2(7a) or later. It also requires one of the following Cisco IOS releases: •11.0(1) or later •10.3(1) or later •10.2(2) or later •10.0(6) or later
8 MB/8 MB	Intel/AMD (2Mbx8)	Dual	This configuration requires Rxboot Version 10.2(7a) or later. It also requires one of the following Cisco IOS releases: •11.0(3) or later •10.3(6) or later •10.2(8) or later
4 MB	AMD (1Mbx8)	Single	This configuration requires Rxboot Version 10.2(7a) or later. It also requires one of the following Cisco IOS releases: •10.0(11) or later •10.2(7) or later •10.3(4) or later
4 MB/4 MB	AMD/AMD (1Mbx8)	Dual	This configuration requires Rxboot Version 10.2(7a) or later. It also requires one of the following Cisco IOS releases: •10.0(11) or later •10.2(7) or later •10.3(4) or later
8 MB	AMD (2Mbx8)	Single	This configuration requires Rxboot Version 10.2(7a) or later. It also requires one of the following Cisco IOS releases: •10.0(11) or later •10.2(7) or later •10.3(4) or later
8 MB/8 MB	AMD/AMD (2Mbx8)	Dual	This configuration requires Rxboot Version 10.2(7a) or later. It also requires one of the following Cisco IOS releases: •10.0(11) or later •10.2(7) or later •10.3(4) or later

The AccessPro PC card has one slot for a Flash SIMM. provides the supported SIMM configurations.

Table 12 AccessPro PC Card and Cisco 2517 Flash SIMM Support 

SIMM Size	Vendor	Flash Bank	Considerations
4 MB	Intel (1Mbx8)	Single	None
8 MB	Intel (2Mbx8)	Single	This configuration requires Rxboot Version 10.2(7a) or later. It also requires one of the following Cisco IOS releases: •11.0(1) or later •10.3(1) or later •10.2(2) or later •10.0(6) or later
8 MB	Intel (1Mbx8)	Dual	None
16 MB	Intel (2Mbx8)	Dual	This configuration requires Rxboot Version 10.2(7a) or later. It also requires one of the following Cisco IOS releases: •11.0(1) or later •10.3(1) or later •10.2(2) or later •10.0(6) or later
4 MB	AMD (1Mbx8)	Single	This configuration requires Rxboot Version 10.2(7a) or later. It also requires one of the following Cisco IOS releases: •10.0(11) or later •10.2(7) or later •10.3(4) or later
8 MB	AMD (2Mbx8)	Single	This configuration requires Rxboot Version 10.2(7a) or later. It also requires one of the following Cisco IOS releases: •10.0(11) or later •10.2(7) or later •10.3(4) or later

PPP Callback

Cisco IOS Release 11.0(3) supports PPP callback, which provides a client-server relationship between the end points of a point-to-point serial connection. PPP callback allows a router to request that a dial-up peer router call back. The callback feature can be used to control access and toll costs between the routers. This feature is a partial implementation of the PPP Callback specifications in RFC 1570.

SSE Switching of Input Access Lists

Beginning with Cisco IOS Release 11.0(3), input access lists are supported under silicon switching.

Support for the Cisco 1004 ISDN Router

The Cisco 1004 is an ISDN router similar to the Cisco 1003. The Cisco 1003 has a B interface that is connected to an NT1, which is connected to the phone company's ISDN line. The Cisco 1004 has a built-in NT1. The Cisco 1004 has one console port, one Ethernet 10BaseT port, one Basic Rate Interface (BRI) port, and one PCMCIA card slot. The BRI port is the interface between the NT1 and the phone company's ISDN line.

New Features in Release 11.0(2)

The following enhancements were added to Release 11.0(2):

Support for the Fast Ethernet Interface Processor on the Cisco 7000 Series and Cisco 7500 Series

The Cisco 7000 series and the Cisco 7500 series routers support the Fast Ethernet Interface Processor (FEIP) card, which allows communications speeds of 100 megabits per second (Mbps).

Support for the Cisco 1003 ISDN Router

Release 11.0 now includes support for the Cisco 1003 ISDN router.

QLLC and Bisync

The QLLC and Bisync features are included to the following feature sets for the Cisco 2500 series and Cisco 4000 series routers:

•IP/IPX/IBM Base

•IP/IPX/IBM/APPN

•Desktop/IBM Base

The Bisync feature is included in the following feature set for the Cisco 2500 series routers:

•CFRAD

New Features in Release 11.0(1)

This section describes new features and enhancements in the initial Cisco IOS Release 11.0 of the router products software.

General Features

This section describes general features that are new in the initial release of Cisco IOS Release 11.0.

•Weighted fair queuing—Weighted fair queuing is a sophisticated traffic priority management algorithm that identifies conversations (traffic streams) and then breaks up the trains of packets belonging to each conversation to ensure that the capacity is shared fairly between individual conversations. Fair queuing provides an automated way to stabilize network behavior during congestion and results in increased performance and reduced retransmission. The algorithm automatically sorts among conversations without requiring the user to define access lists. Instead, by examining sufficient fields in the packet header, the algorithm can identify unique conversations.

Conversations are sorted into two categories—those that are attempting to use a lot of bandwidth with respect to the interface capacity (for example, FTP) and those that need less (for example, interactive traffic). For streams that use less bandwidth, the queuing algorithm always attempts to provide access with little or no queuing and shares the remaining bandwidth between the other conversations.

•Custom and priority queuing enhancements—The number of queues that can be used for custom queuing and priority queuing has been increased to 16.

•Custom and priority queuing Management Information Base (MIB)—This MIB provides detailed access to custom and priority queuing information. This information was previously available only via the show queue EXEC command.

Backbone Protocol Routing Features

This section describes the backbone protocol routing features that are new in the initial release of Cisco IOS Release 11.0.

TCP/IP Features

The following features have been added to the Cisco IOS TCP/IP software:

•Routing security enhancements with Message Digest 5 (MD5)—MD5 authentication is now available for Open Shortest Path First (OSPF) and also for TCP connections between Border Gateway Protocol (BGP) peers. MD5 authentication provides a standards-based method to greatly enhance the probability that the Cisco IOS software will detect and ignore hostile or erroneous routing messages.

•IP multicast fast switching—Fast switching of IP multicast packets is now available. Previously, IP multicast packets were only process switched.

•Rate limiting of IP multicast traffic—Using access lists, you can control how fast a sender can transmit to a multicast group.

•Protocol Independent Multicast (PIM) Nonbroadcast, Multiaccess (NBMA) mode—PIM NBMA mode allows the router to replicate packets for each neighbor on the NBMA network.

•Multicast static routes—IP multicast static routes allow you to have multicast paths diverge from unicast paths. The most common reason for using separate unicast and multicast paths is tunneling. The multicast packets can use the tunnel without having unicast packets use the tunnel.

•Session directory (SD) listener support—The multicast backbone is widely used for multimedia conferencing. The session directory tool helps announce multimedia conference sessions and provide setup information to potential participants. A session directory client multicasts announcement packets on a well-known multicast address and port. You can enable the router to listen for such announcements.

•Interactive input when tracing a branch of a multicast tree—When you use the mbranch or mrbranch commands to trace a branch of a multicast tree, you can now enter information interactively.

•Policy routing—You can now implement IP routing policies based on source or destination IP addresses or packet lengths. Policy routing provides a more flexible method for routing packets than destination routing.

•IP access list logging—The router can now send a logging message to the console when a packet passes or fails an extended access list. The message includes the access list number, whether the packet was permitted or denied, the protocol, whether it was TCP, UDP, ICMP, or a number, and, if appropriate, the source and destination addresses and source and destination port numbers.

•Open Shortest Path First (OSPF) point-to-multipoint—Support for point-to-multipoint media types is added, allowing the Cisco IOS software to more optimally support Frame Relay-type networks using the OSPF routing protocol.

•Border Gateway Protocol (BGP) peer groups—You can group neighbors with the same update policies into BGP peer groups to simplify configuration and make updating more efficient.

Transparent Bridging Features

The following feature has been added to Cisco's transparent bridging software:

•Concurrent routing and bridging (CRB)—This feature allows a given routable protocol to be routed on some interfaces and bridged on other interfaces within the same router. System managers can consolidate multiple IP subnet assignments into one IP subnet by bridging IP hosts on multiple data-link segments into one network segment. For networks that rely on packet absorption, CRB provides a bridge-group command that causes packets in a given protocol to be "absorbed" rather than bridged within the bridge group.

---

Note   CRB is not a source-route bridging (SRB) feature.

---

Desktop Protocol Features

This section describes the desktop protocol features that are new in the initial release of Cisco IOS Release 11.0.

AppleTalk Features

The following features have been added to Cisco's AppleTalk software:

•AppleTalk Name Binding Protocol (NBP) filters—NBP provides directory services in AppleTalk. AppleTalk NBP filtering allows network administrators to use Cisco routers to build firewalls, dial-on-demand triggers, and queuing options based on any designed NBP type or object.

Benefits of using NBP filters include:

•Reducing switched circuit costs by using dial-on-demand triggers

•Controlling access to specific AppleTalk resources on the network (printers, file servers, and so on) with NBP access firewalls

•Reducing WAN costs using NBP-based traffic firewalls to prevent unnecessary NBP packets from traversing cost-per-packet network services, such as X.25, Switched Multimegabit Data Service (SMDS), and Frame Relay

•Minimizing NBP traffic overhead by using NBP queuing

•Increased AppleTalk management granularity by combining AppleTalk NBP filters with network and zone filters in a single access list

•AppleTalk Update-Based Routing Protocol (AURP) options—Optional features of AURP, network number mapping, loop detection, and hop count reduction have been added.

•AppleTalk floating static routes—Previously available for TCP/IP and Novell/IPX environments, the floating static routes feature is now available for AppleTalk internetworking environments. Static routes are traditionally implemented so that they always take precedence over any dynamically learned routes to the same destination network. A floating static route is a statically configured route that can be overridden by dynamically learned routing information. Thus, a floating static route can help create a path of last resort that is used only when no dynamic information is available. Floating static routes can be used to provide backup routes in topologies where dial-on-demand routing (DDR) is used.

•AppleTalk Simple Multicast Routing Protocol (SMRP)—SMRP provides multicast routing functions for AppleTalk traffic. SMRP routes AppleTalk packets to all members of a multipoint group so that packets are not replicated on a link. Applications produced by Apple Corporation, Inc., such as QuickTime Conferencing (QTC) will require support by SMRP.

Banyan VINES Features

The following feature has been added to Cisco's Banyan VINES software:

•VINES floating static routes—Previously available for TCP/IP and Novell/IPX environments, the floating static routes feature is now available for Banyan/VINES internetworking environments. Static routes are traditionally implemented so that they always take precedence over any dynamically learned routes to the same destination network. A floating static route is a statically configured route that can be overridden by dynamically learned routing information. Thus, a floating static route can help create a path of last resort that is used only when no dynamic information is available. Floating static routes can be used to provide backup routes in topologies where dial-on-demand routing (DDR) is used.

Novell Features

The following feature has been added to Cisco's Novell software:

•Sequence Packet Exchange (SPX) spoofing—Some SPX-based services in a Novell environment use SPX watchdog packets to verify the integrity of end-to-end communications when guaranteed and sequenced packet transmission is required. SPX spoofing implemented in the Cisco IOS software will receive, recognize, and successfully acknowledge these watchdog packets both at the server end and at the client end of the wide-area link. Requests for the transmission of legitimate information will trigger the dial-up connection. SPX spoofing can drastically reduce communications costs associated with dial-on-demand circuits.

Wide-Area Networking Features

This section describes the wide-area networking features that are new in the initial release of Cisco IOS Release 11.0.

ISDN/DDR Enhancements

The following feature has been added to Cisco's ISDN and DDR software:

•ISDN fast switching—This feature has been added to offset some of the performance limitations of process switched ISDN WAN connectivity introduced by Multiport Basic Rate Interfaces (MBRIs) and Primary Rate Interfaces (PRIs).

X.25 Enhancements

The following feature has been added to Cisco's X.25 software:

•Transparent bridging over multiprotocol Link Accessed Procedure, Balanced (LAPB)—This feature provides encapsulation of transparent bridging packets over a multiprotocol LAPB connection.

Frame Relay

The following features have been added to Cisco's Frame Relay software:

•Fast-switched Frame Relay bridging—This feature allows Frame Relay bridging traffic (transparent bridging, source-route bridging (SRB), and remote SRB (RSRB)) to be fast-switched.

•Data-link connection identifier (DLCI) prioritization—This feature allows up to four DLCIs to be created between any two sites so that each DLCI has a different priority level. These DLCIs can be used to send different types of traffic such as File Transfer Protocol (FTP), Telnet, or Systems Network Architecture (SNA) on different circuits. Congestion problems that result from mixing batch and interactive traffic over a common DLCI can be alleviated for process-switched packets, and greater granularity for performance management can be attained.

•Payload compression for Frame Relay—This feature allows for payload compression of data within Frame Relay packets. Compression is performed on a packet-by-packet basis, yielding a compression ratio of approximately 1.5 to 1, depending on the packet and data characteristics.

ATM Enhancements

The following features have been added to Cisco's Asynchronous Transfer Mode (ATM) software:

•ATM Point-to-Multipoint signaling—Point-to-multipoint signaling on ATM enables the creation of ATM switched virtual circuits (SVCs) that efficiently support "one-to-many" ATM connections. Point-to-multipoint signaling allows the establishment of unidirectional point-to-multipoint SVCs in addition to the existing support for bi-directional and unidirectional point-to-point SVCs.

•ATM Interim Local Management Interface (ILMI)—ILMI supports standards-based ATM network configuration and ATM address acquisition and registration. ATM network configuration parameters include identification of the User-Network Interface (UNI) version supported or Network-Node Interface (NNI) versus UNI interface identification.

•RFC 1577 Classical IP and ARP over ATM—RFC 1577 defines an application of classical IP and ARP in an ATM environment configured as a logical IP subnetwork (LIS). It also describes the functions of an ATM ARP server and ATM ARP clients in requesting and providing destination IP addresses and ATM addresses in situations when one or both are unknown. Cisco routers can be configured to act as an ARP Client, or to act as a combined ARP Client and ARP Server.

Cisco's implementation of the ATM ARP server functionality provides a robust environment in which network changes can be made more easily and more quickly than in a pure ATM environment. Cisco's ATM ARP client works with any ARP server that is fully compliant with RFC 1577.

•Generation of operation and maintenance (OAM) cells—OAM cells are transmitted over ATM virtual path connections (VPCs) and virtual channel connections (VCCs). This new feature enables the router ATM interface to initiate loopback OAM cells. Previously, ATM interfaces could only echo a loopback OAM cell to the initiator as required.

•SVC idle disconnect—This feature allows the router ATM interfaces to tear down SVCs after a user-definable (or default) period of inactivity on a given connection. SVC teardown provides more efficient use of the finite number of connections available per ATM interface.

•LAN Emulation (client/server)—The LAN Emulation (LANE) feature emulates an Ethernet segment over ATM that allows higher-layer protocols and their applications to operate without modification. LAN Emulation features service components (LANE configuration server, LANE server, and broadcast-and-unknown server) as well as a client component called the LANE client. LAN Emulation includes a connectionless broadcast service not otherwise available in ATM networks that can support important protocol mechanisms such as Address Resolution Protocol (ARP). In LAN Emulation, ARP requests resolve MAC addresses to ATM addresses. The LANE configuration server, LANE server, broadcast-and-unknown server, and LANE client are supported on the router ATM interfaces.

Core Enhancements

The following feature has been added to the Cisco 7000 router:

•Flash memory card for the Cisco 7000 route processor—Support for Personal Computer Memory Card International Association (PCMCIA) Flash memory cards for the Cisco 7000 product family is added with Release 11.0. Available in either 8 MB or 16 MB sizes, the Flash card serves as an extension of Flash memory or nonvolatile random-access memory (NVRAM). The Flash card enables you to boot images over 4 MB in size from Flash memory. Multiple images and configuration files can be stored in Flash memory, and the Flash card can serve as either a boot server or TFTP server.

IBM Functionality Features

This section describes the IBM networks software features and support that are new in the initial release of Cisco IOS Release 11.0.

New Features

The following new IBM software features are available:

•Data-link switching plus (DLSw+) over QLLC/Frame Relay—DLSw+ has been enhanced to support both Qualified Logical Link Control (QLLC) and direct encapsulation in Frame Relay. QLLC support allows DLSw+ to communicate with SNA resources over an X.25 network. Direct encapsulation in Frame Relay allows DLSw+ routers to transfer SNA or NetBIOS data across a Frame Relay cloud without requiring encapsulation in TCP/IP. DLSw+ frames are encapsulated directly in Frame Relay according to RFC 1490. This encapsulation scheme minimizes the overhead and improves performance when these protocols are transmitted over a Frame Relay network.

•SDLC improvements—Synchronous Data Link Control (SDLC) support in the Cisco IOS software has been enhanced to include the following:

•Individual control for devices on a multidrop SDLC line, including the ability to view, shut down, bring up, and add physical units

•Ability to ping physical units on an SDLC line to verify reachability

•More granular debugging with both hexadecimal and EBCDIC readouts

•Dial backup support for SNA Frame Relay Access Support (FRAS)—Cisco's SNA FRAS feature has been enhanced to support dial backup. With this feature, if the primary Frame Relay link to a front-end processor is lost, the Cisco IOS software automatically finds a backup path and uses DLSw+ to reroute around the failed link.

•Downstream physical unit (DSPU) concentration enhancements—The integrated DSPU concentration feature of the Cisco IOS software has been enhanced to support Ethernet and SDLC connections. DSPU concentration is now supported over the following connections: Token Ring, remote source-route bridging (RSRB), Ethernet, and SDLC. Any of these links can be used to connect the DSPU router to downstream SNA devices as well as to upstream SNA hosts. All combinations of upstream and downstream connections are supported.

DSPU concentration provides scalability benefits in integrated SNA and multiprotocol networks, reduces mainframe configuration requirements, limits WAN overhead, and speeds recovery of SNA sessions following network failures or restarts. In many environments, DSPU concentration eliminates the need for SNA gateways. Support for Ethernet and SDLC connections provides additional flexibility in connecting DSPUs and upstream mainframes to Cisco routers offering DSPU concentration.

•Advanced Peer-to-Peer Networking (APPN)/intermediate session routing (ISR) with dependent LU requester (DLUR)—APPN is second-generation SNA from IBM. APPN provides dynamic resource and route discovery without mainframe intervention. Release 11.0 provides APPN network node support, which lets you route SNA natively in a single or multiprotocol environment. ISR is the routing algorithm used in the first release of APPN. With DLUR functionality, an APPN network can concurrently carry legacy SNA traffic, enabling native routing of both APPN and legacy traffic.

•APPN over RSRB—This feature provides for encapsulation of APPN traffic in TCP/IP.

•APPN MIB—In support of APPN, the APPN MIB (based on informational RFC 1593) is implemented in this release. For mainframe NetView users, alerts are issued from APPN code points.

•NetView native service point—The native service point feature lets you view the router from a NetView host. The router appears as a PU 2 to virtual telecommunications access method (VTAM). When run commands are issued from the host to the router, responses are sent in the form of NetView network management vector transports (NMVTs).

•SNA support over Cisco's Channel Interface Processor (CIP)—The Cisco CIP now supports direct mainframe channel connectivity to VTAM. By appearing to be an IBM 3172 with SNA support to VTAM, and by appearing to be a virtual LAN to the Cisco 7000, the CIP can now pass SNA traffic between VTAM and an SNA physical unit (PU). Session traffic for VTAM to VTAM, VTAM to Network Control Program (NCP), and VTAM to a PU T2 or PU 2.1 is supported. In addition, SNA traffic that is transported using Cisco's RSRB, DLSw+, Frame Relay, or SDLLC can use the CIP for IBM mainframe access.

•TCP/IP offload on CIP—The Cisco CIP offers additional support for mainframes running TCP/IP applications by offloading the TCP/IP-level processing from the mainframe. With TCP/IP offload, a TCP/IP stack is resident on the CIP, removing checksum processing, packet retransmission, and the task of creating or removing TCP/IP headers from the mainframe. TCP/IP offload is only supported by IBM's TCP/IP for Multiple Virtual Storage (MVS) and TCP/IP for virtual machine (VM) mainframe applications.

With the addition of TCP/IP offload, the CIP now offers two methods for communicating with mainframes running a TCP/IP stack: traditional gateway connections, which offer the highest level of performance, or offload, which offers high performance as well as mainframe cycle savings. Typically, 30 percent of the mainframe cycles that were dedicated to full TCP/IP processing can be saved by implementing TCP/IP offload.

---

Note   For the TCP/IP offload feature and the SNA support over CIP feature, contact your local sales representative for an update on the prerequisite microcode. Target microcode availability is anticipated in early October 1995 in Cisco IOS Release 11.0(2).

---

New MIB Support

The following new MIBs are available:

•TCP/IP offload MIB—This MIB manages configuration of the TCP offload feature. It is made up of one table entry that shows configuration information such as path, device, host name, router name, application programming interface (API) host application, and API router application.

•CIP CSNA MIB—This MIB provides information on the configuration of the Channel Interface Processor (CIP) Systems Network Architecture (SNA) feature. In eight tables, three pieces of information are provided: configuration of I/O device addresses of communication controllers, information regarding VTAM to internal adapter connections, and the number of sessions allowed between the VTAM and internal adapter.

•CIP/LAN MIB—This MIB provides configuration information on the internal (virtual) LAN and internal (virtual) adapter components of the CIP CSNA feature.Within the LAN configuration are entries for the type of LAN and the bridging protocol. Within the adapter configuration are entries for the media access control (MAC) address and the SNA name used for alerts.

•RSRB MIB—This MIB provides information about the attributes of the local-remote RSRB peer relationship. The following three entities are managed: virtual rings, remote peers, and associated Token Rings.

•STUN MIB—This MIB provides configuration and operational information on Cisco's serial tunnel (STUN) implementation. The following four entities are managed: global STUN information, STUN groups, STUN ports, and STUN routes.

•SDLLC MIB—This MIB provides read-only configuration and operational information on Cisco's implementation of SDLC-to-logical link control 2 (LLC2) media translation. The SDLLC MIB provides a table entry for each serial interface and SDLC address pair, and includes information such as front-end processor (FEP) MAC addresses, SDLC station addresses, and Token Ring numbers on LLC2 stations.

•SNADLC/LLC MIB—This MIB manages the LLC2 stack that runs on a CIP card. The CIP card provides the SNA gateway to an IBM mainframe via a channel connection from the router.

•QLLC MIB—This MIB provides information on QLLC stations in three tables—administrative, operational, and statistical—with an entry in each for every QLLC station. The station is indexed by connection index and by the virtual circuit number for the logical channel identifier or PVC number, depending on the type of circuit on the interface.

•SNADLC/CONV MIB—This MIB provides information for accessing the QLLC MIB objects. It supplies both administrative and operational objects for a connection object that is indexed on a virtual MAC (in 802.3/802.5 format) and displays the index into the QLLC objects. The following three conversion types are supported: QLLC to SDLC, QLLC to LLC, and QLLC to local acknowledgment.

•SDLC MIB—This MIB provides configuration and operational information about SDLC ports and stations. This MIB follows RFC 1213 format, and provides administrative and operational tables for both ports and stations.

•BSTUN MIB—This MIB provides configuration and operational information about Cisco's blocked serial tunnel (BSTUN) implementation. The following four entities are managed: BSTUN global entry, BSTUN group table, BSTUN port table, and BSTUN route table.

•BSC MIB—This MIB provides configuration and operational information for Cisco's Binary Synchronous Communications (BSC) implementation. The following two entities are managed: BSC ports (serial interfaces), and BSC control units (stations on a port).

•CIP/TCPIP MIB—This MIB is used to manage the TCP/IP protocol stack running on the Channel Interface Processor (CIP) card. In Release 11.0, only the TCP/IP offload feature makes use of this MIB. The read-only values allow statistics and status for every instance of IP, TCP, UDP, and Internet Control Message Protocol (ICMP) protocol stacks to be viewed.

Access Server Features Supported on the Router

This section describes the access server features that are new in the initial release of Cisco IOS Release 11.0.

•Asynchronous callback—This feature allows an access server to establish a connection on a supported interface, recognize that a callback is required, terminate the current connection, and initiate the callback to the caller. Callback can be initiated by an EXEC command, by a Point-to-Point Protocol (PPP) Link Control Protocol (LCP) callback request, by an AppleTalk Remote Access (ARA) callback request, or by Terminal Access Controller Access Control System Plus (TACACS+) once authentication has identified a user as requesting callback services. Cisco's implementation supports roaming callback, whereby a user can specify the phone number for callback.

•Asynchronous master interfaces—The asynchronous master interfaces feature reduces the time and complexity of configuring Cisco access servers by allowing you to create a single master interface and associate many subinterfaces to it. This many-to-one relationship allows you to configure the master interface and have the configuration apply to all associated interfaces.

•AAA/TACACS+ Phase II—This upgrade to Authentication, Authorization, and Accounting (AAA)/TACACS+ adds accounting to the existing facilities in TACACS+.

•Local IP pooling—Local IP pooling maintains a pool of IP addresses available to asynchronous interfaces that are dynamically assigned and reused upon disconnection. Pooling reduces the number of IP addresses required to support IP dial-in—via Serial Line Internet Protocol (SLIP) or PPP—on multiple interfaces.

Important Notes

This section describes warnings and cautions about using the Cisco IOS Release 11.0 software. This section discusses these topics:

•BSC and SDLC Commands in Releases 11.0(5) and 11.0(6)

•X.25 Problem in 11.0(2)

•Upgrading to a New Software Release

•Emulated LAN Interoperability

•Payload Compression for Frame Relay Support

•Multiring FDDI Support

•SRB over FDDI

•Fast Switching of SRB over FDDI on Cisco 4000 Series

•Cisco 1000 Series Support

•Enabling IPX Routing

•Using AIP Cards

•Booting Cisco 4000 Routers

•Using LAN Emulation (LANE)

•Forwarding of Locally Sourced AppleTalk Packets

•Using Source-Route Transparent Bridging (SRT) and Source-Route Bridging (SRB) on Cisco 2500 and Cisco 4000 Routers

•Release 11.0(10a) Fixes Caveat CSCdi66673

•Release 11.0(12a) Fixes Caveat CSCdi71609

•Release 11.0(13a) Fixes Caveat CSCdi92818

•Release 11.0(14a) Fixes Caveat CSCdj05366

BSC and SDLC Commands in Releases 11.0(5) and 11.0(6)

In Release 11.0(5), the bsc fdx and sdlc hdx commands were deprecated and replaced by new versions of the media-type command. Also, the sdlc cts-delay and sdlc rts-timeout commands were deprecated and replaced by the half-duplex timer command.

In Release 11.0(6), the half-duplex and full-duplex keywords of the media-type commands were removed and replaced by the half-duplex and full-duplex commands, respectively.

All of the deprecated commands continue to be supported in Release 11.0(6) and later.

X.25 Problem in 11.0(2)

Cisco IOS Release 11.0(2) contains a software defect, affecting all platforms, that involves an unexpected router reload when X.25 is configured. This defect, CSCdi40956, is not present in Release 11.0(1) and is fixed by Release 11.0(3).

Upgrading to a New Software Release

If you are upgrading to Cisco IOS Release 11.0 from an earlier Cisco IOS software release, you should save your current configuration file before installing Release 11.0 software on your router.

Emulated LAN Interoperability

Cisco IOS Release 11.0(6), Release 11.1(2), and Catalyst 5000 ATM software Release 2.1 and later contain a fix for an emulated LAN defect. This fix is incompatible with earlier releases of Cisco IOS Release 11.0, Release 11.1, and Catalyst 5000 ATM software Release 1.1.

If you use emulated LAN bridging features in your network, and you upgrade any device to Cisco IOS Release 11.0(6), Release 11.1(2), or Catalyst 5000 ATM software Release 2.1 or later, you must upgrade all devices in the emulated LAN that run Cisco IOS software to a release level that contains the emulated LAN fix. Failure to upgrade all devices in a particular emulated LAN will result in interoperability problems between Cisco devices.

If you choose to continue to use Cisco IOS Release 11.0(5), Release 11.1(1) or earlier releases, the Catalyst 5000 requires ATM software Release 1.1.

Payload Compression for Frame Relay Support

The payload compression for the Frame Relay feature is not supported in Cisco IOS Release 11.0(1), Release 11.0(2), or Release 11.0(3). This feature is supported in Release 11.0(4).

Multiring FDDI Support

Multiring FDDI features are not supported in Cisco IOS Release 11.0(1), Release 11.0(2), Release 11.0(3), Release 11.0(4), Release 11.0(5), Release 11.0(6), or Release 11.0(7).

SRB over FDDI

This feature supports forwarding of source-route bridged traffic between Token Ring and FDDI interfaces on the Cisco 7000, Cisco 7010, and AGS+ routers. Previously, the only way to transport SNA and NetBIOS over FDDI was with remote source-route bridging (RSRB), which is either fast switched (direct or Fast-Sequence Transport (FST) encapsulation) or process-switched (TCP encapsulation). With SRB over FDDI, traffic can be autonomously switched, greatly improving performance for SRB traffic that uses FDDI as a backbone. This feature eliminates the need for RSRB peer definitions to connect Token Ring networks over the FDDI backbone.

---

Note   SRB over FDDI does not support RSRB traffic forwarded to RSRB peers. Routers that have connections to local Token Ring networks as well as RSRB connections to remote networks cannot use this feature. The work around is to move the RSRB connections to routers that are not connected to the FDDI backbone.

---

Fast Switching of SRB over FDDI on Cisco 4000 Series

Earlier Cisco IOS Release 11.0 release notes inadvertently indicated that fast switching of SRB over FDDI was supported on the Cisco 4000 series. SRB over FDDI for the Cisco 4000 series routers is not supported in any release of Cisco IOS Release 11.0.

Cisco 1000 Series Support

The Cisco 1000 series, including the Cisco 1003 ISDN router is not supported in Cisco IOS Release 11.0(1). The Cisco 1003 router is supported in Release 11.0(2). The Cisco 1004 router is supported in Release 11.0(3). The Cisco 1005 is supported in Release 11.0(4). Note that the size of the Cisco 1003 and Cisco 1004 feature set images released in Release 11.0(3) prevent those routers from running if large routing tables are present. Those images are now obsolete, and new images are available in Release 11.0(4) and later.

Enabling IPX Routing

The Token Ring interface is reset whenever IPX routing is enabled on that interface.

Using AIP Cards

Cisco 7000 series ATM Interface Processor (AIP) cards that support E3, DS3, or Transport Asynchronous Transmitter/Receiver Interface (TAXI) connections and that were shipped after February 22, 1995, require Cisco IOS Release 10.0(9), 10.2(5), 10.3(1), or later.

Booting Cisco 4000 Routers

You must use the Release 9.14 rxboot image for Cisco 4000 routers because the Release 11.0 rxboot image is too large to fit in the ROMs. (Note that rxboot image size is not a problem for Cisco 4500 routers.) However, because the Release 9.14 rxboot image does not recognize new network processor modules, such as the Multiport Basic Rate Interface (MBRI), its use causes two problems:

•You cannot boot from a network server over BRI lines. Instead, you can boot either from a network server over other media or use the copy tftp flash command to copy images over BRI or other media to Flash memory. If you use the copy tftp flash command over a BRI interface, you must be running the full system image.

•If you use the rxboot image on a Cisco 4000 router that is already configured, the following error messages are displayed, with one pair of messages for each BRI interface configured:

Bad interface specification

No interface specified - IP address

Bad interface specification

No interface specified - IP address

Using LAN Emulation (LANE)

Note the following information regarding the LAN Emulation (LANE) feature:

•LANE is available for use with the Cisco 7000 series routers connected to an LS100 or LS1010 switch. LANE requires at least version 3.1(2) of the LS100 software, which requires a CPU upgrade if you are currently running software prior to version 2.5.

•The LS2020 cannot be used for LANE because it does not support UNI 3.0 and point-to-multipoint SVCs.

•Routing of IP, IPX, and AppleTalk is supported. Refer to the switching matrix in the "Switching" appendix of the Router Products Command Reference publication to determine what runs at process, fast, autonomous, and silicon levels.

•LANE does not support:

•DECnet, CLNS, VINES, and XNS

•LANE over PVCs

•HSRP

•AppleTalk Phase 1 cannot be routed to AppleTalk Phase 2 via LANE.

Forwarding of Locally Sourced AppleTalk Packets

Our implementation of AppleTalk does not forward packets with local source and destination network addresses. This behavior does not conform to the definition of AppleTalk in Apple Computer's Inside AppleTalk publication. However, this behavior is designed to prevent any possible corruption of the AppleTalk Address Resolution Protocol (AARP) table in any AppleTalk node that is performing MAC-address gleaning.

Using Source-Route Transparent Bridging (SRT) and Source-Route Bridging (SRB) on Cisco 2500 and Cisco 4000 Routers

Certain products containing the Texas Instruments TMS380C26 Token Ring controller do not support SRT. SRT is the concurrent operation of SRB and transparent bridging on the same interface. The affected products, shipped between March 30, 1994, and January 16, 1995, are the Cisco 4000 NP-1R, Cisco 4000 NP-2R, Cisco 2502, Cisco 2504, Cisco 2510, Cisco 2512, Cisco 2513, and Cisco 2515.

Units shipped before March 30, 1994, or after January 16, 1995, are not affected. They use the Texas Instruments TMS380C16 Token Ring controller, which supports SRT.

SRT support is necessary in two situations. In one, Token Ring networks are configured to source-route bridging (SRB) protocols such as SNA and NetBIOS, and transparently bridge other protocols, such as IPX. In the other situation, SNA or NetBIOS uses SRB and Windows NT is configured to use NetBIOS over IP. Certain other configuration alternatives do not require SRT (contact the Technical Assistance Center).

As of Release 10.3(1), SRB in the following Cisco IOS features sets is no longer supported: IP, IP/IPX, and Desktop. To use SRB, you need one of the following feature sets: IP/IBM base, IP/IPX/IBM base, IP/IPX/IBM/APPN, Desktop/IBM base, Enterprise, or Enterprise/APPN. In most non-IBM Token Ring environments, the multiring feature in IP, IP/IPX, and Desktop eliminates the need for IP/IBM base, IP/IPX/IBM base, IP/IPX/IBM/APPN, Desktop/IBM base, Enterprise, or Enterprise/APPN.

Release 11.0(10a) Fixes Caveat CSCdi66673

After the release of Cisco IOS Release 11.0(10), a caveat was discovered within the rsp- Cisco IOS images. It was determined that this caveat was significant enough to merit a rebuild of the rsp- images. The rebuild includes the caveat fix and is renumbered to 11.0(10a).

This defect is bug CSCdi66673 and is described as follows:

When Ethernet runt packets are received by Cisco 7500 series router processors (RSP1, RSP2, or RSP7000), a Reserved Exception crash or a QAERROR error will occur. When either of these problems happens, a switching complex restart is forced. The Reserved Exception crash has the following output:

Queued messages:

Aug 14 10:44:16: %RSP-3-ERROR: memd write exception, addr 08000000

Aug 14 10:44:16: %RSP-3-ERROR:   RSP alignment error on write to QA, addr 080000

00

*** System received a reserved exception ***

signal= 0x9, code= 0x0, context= 0x60c72fd0

PC = 0x60107514, Cause = 0x2020, Status Reg = 0x34008702

DCL Masked Interrupt Register = 0x000000ff

DCL Interrupt Value Register = 0x00000000

MEMD Int 6 Status Register = 0x00000000

The QAERROR error has the following output:

Jun 17 10:50:23.329: %RSP-2-QAERROR: reused or zero link error, write at addr 03

08 (QA)

  log 260308C0, data A816FFFF 00000000

Release 11.0(10a) and all subsequent releases of Cisco IOS software, including Release 11.0(11), include the fix for this caveat.

Release 11.0(12a) Fixes Caveat CSCdi71609

After the release of Cisco IOS Release 11.0(12), a caveat was discovered within the rsp- Cisco IOS images. It was determined that this caveat was significant enough to merit a rebuild of the rsp- images. The rebuild includes the caveat fix and is renumbered to 11.0(12a). Release 11.0(12a) includes 11.0(12) images plus the rebuilt rsp- images.

This defect is bug CSCdi71609 and is described as follows:

A serious bug has been found within various Cisco IOS software releases. In extremely rare conditions, a failure condition can occur when Backing-Store or Fair Queuing are enabled. To avoid these problems, the rsp- Cisco IOS images in affected releases are no longer available.

This problem can be avoided by disabling both Backing-Store and Fair Queuing on existing Cisco IOS software releases with rsp- images.

Release 11.0(12a) and all subsequent releases of Cisco IOS software, including Release 11.0(13), include the fix for this caveat.

Release 11.0(13a) Fixes Caveat CSCdi92818

Cisco IOS software release 11.0(13) was deferred due to a severe defect in source-route bridging protocol when used on a Route Switch Processor (RSP)-based platform, including the Cisco 7500 series and RSP7000 routers.

This defect is bug CSCdi92818 and is described as follows:

CSCdi92818 affects any RSP router running Cisco IOS Software Interim 11.0(12.3) through 11.0(13.3) with a CIP and/or a TRIP, and a FDDI. If the CIP or the TRIP are passing RIF data, the FDDI will stop passing traffic. The FDDI will not acknowledge incoming traffic on FDDI interfaces if SRB is in use anywhere in the router. There is no known workaround. SRB needs to be turned off in these configurations.

If you are not running source-route bridging in your network, this defect does not apply to you. If you are running source-route bridging in your network, certain interface types on an RSP-based platform may be specifically affected.

If you believe your network may be impacted by this defect, you can obtain Cisco IOS Release 11.0(13a) from the Cisco Connection Online Software Upgrade Library.

Release 11.0(13a) and all subsequent releases of Cisco IOS software, including Release 11.0(14), include the fix for this caveat.

Release 11.0(14a) Fixes Caveat CSCdj05366

Cisco IOS software release 11.0(14) was deferred due to a severe defect.

This defect is bug CSCdj05366 and is described as follows:

When establishing a second telnet session to a router, vty does not echo characters; the first established session works correctly.

If you believe your network may be impacted by this defect, you can obtain Cisco IOS Release 11.0(14a) from the Cisco Connection Online Software Upgrade Library.

Release 11.0(14a) and all subsequent releases of Cisco IOS software, including Release 11.0(15), include the fix for this caveat.

Caveats for Release 11.0(1) through 11.0(22a)

Cisco IOS Release 11.0(22a) is a rebuild release for Cisco IOS Release 11.0. The caveats in this section are resolved in Cisco IOS Release 11.0(22a) but may be open in previous Cisco IOS releases.

•Cisco IOS software releases based on versions 11.x and 12.0 contain a defect that allows a limited number of SNMP objects to be viewed and modified without authorization using a undocumented ILMI community string. Some of the modifiable objects are confined to the MIB-II system group, such as "sysContact", "sysLocation", and "sysName", that do not affect the device's normal operation but that may cause confusion if modified unexpectedly. The remaining objects are contained in the LAN-EMULATION-CLIENT and PNNI MIBs, and modification of those objects may affect ATM configuration. An affected device might be vulnerable to a denial-of-service attack if it is not protected against unauthorized use of the ILMI community string.

The vulnerability is only present in certain combinations of IOS releases on Cisco routers and switches. ILMI is a necessary component for ATM, and the vulnerability is present in every IOS release that contains the supporting software for ATM and ILMI without regard to the actual presence of an ATM interface or the physical ability of the device to support an ATM connection.

To remove this vulnerability, Cisco is offering free software upgrades for all affected platforms. The defect is documented in DDTS record CSCdp11863.

In lieu of a software upgrade, a workaround can be applied to certain IOS releases by disabling the ILMI community or "*ilmi" view and applying an access list to prevent unauthorized access to SNMP. Any affected system, regardless of software release, may be protected by filtering SNMP traffic at a network perimeter or on individual devices.

This notice will be posted at http://www.cisco.com/warp/public/707/ios-snmp-ilmi-vuln-pub.shtml. [CSCdp11863]

•Cisco IOS software contains a flaw that permits the successful prediction of TCP Initial Sequence Numbers.

This vulnerability is present in all released versions of Cisco IOS software running on Cisco routers and switches. It only affects the security of TCP connections that originate or terminate on the affected Cisco device itself; it does not apply to TCP traffic forwarded through the affected device in transit between two other hosts.

To remove the vulnerability, Cisco is offering free software upgrades for all affected platforms. The defect is described in DDTS record CSCds04747.

Workarounds are available that limit or deny successful exploitation of the vulnerability by filtering traffic containing forged IP source addresses at the perimeter of a network or directly on individual devices.

This notice will be posted at http://www.cisco.com/warp/public/707/ios-tcp-isn-random-pub.shtml. [CSCds04747]

Caveats for Release 11.0(1) through 11.0(22)

This section describes possibly unexpected behavior by Release 11.0(22). Unless otherwise noted, these caveats apply to all 11.0 releases up to and including 11.0(22).

Only serious caveats are described in these release notes. For the complete list of caveats against this release, access CCO or use the Documentation CD-ROM as described in the sections "Cisco Connection Online" and "Documentation CD-ROM" at the end of this document.

Basic System Services

•On a Cisco 7000 series router, if you replace one interface processor (for example, a TRIP or an FSIP) with a different type of interface processor online, the show ip interface brief and show interface commands display information for both the old and new controllers. Rarely, this also results in the continual reinitialization of the newly inserted controller.

The only known workaround is to completely unconfigure the old card before replacing it with the new card. Sometimes, it might even be necessary to issue a write erase command, reboot the router, and then redefine the existing interfaces to completely remove all configuration traces of the old card. Once the information that is displayed by the show commands is self-consistent, the newly inserted card behaves normally. [CSCdi49800]

•When your configuration contains AAA commands, booting from Cisco IOS Release 11.0(10c) bootroms will cause error messages to be displayed. [CSCdk40563]

DECnet

•Under certain conditions, DECnet does not send triggered routing updates after an adjacency comes up. If (periodic) routing updates are sent out frequently (default frequency being 40 seconds), this is not an issue, since an update gets sent out in a short time, and routes are learned. However, if the routing update timer has been configured to be a large value, then routes may not be learned for a long time.The workaround is to configure a smaller value for the routing update timer.[CSCdk62414]

IBM Connectivity

•When you configure Native Service Point (NSP) on a router's Frame Relay interface and set the LSAP value, the value displayed by the show running-configuration command will be 0, even if you specified a different value.

!

sna host NETHOST xid-snd 05d26198 dlci 68 rsap 4 lsap 0 focalpoint

! 

If you change the sna host command to another medium, for example Token Ring, and the sna host command uses an rmac instead of the dlci xx parameter, LSAP will be set to the actual value you specified, for example 20.

router (config)#

sna host NETHOST xid-snd 05d26198 dlci 68 rsap 4 lsap 20 focalpoint 

[CSCdk46001]

Interfaces and Bridging

•If a serial interface is set to loopback via a hardware signal, the interface will remain in loopback until the hardware signal is dropped and a no loopback interface configuration command is issued. [CSCdi47768]

IP Routing Protocols

•An external SPF calculation may be triggered every 35 to 40 seconds if both of the following occur:

(1) An OSPF external LSA contains a forwarding address that OSPF has no route for, and

(2) A static route to the forwarding address is configured, and it points out an interface that OSPF is running on.

To work around this problem, either remove the static route, or prevent the unreachable forwarding address from being included in the external LSA by making sure that any ASBRs redistributed between different OSPF domains has the fix for CSCdi63983. [CSCdk52593]

ISO CLNS

•On platforms which do not use the old MCI controller, fast-switching of CLNS traffic with non-zero N-Selector does not work. [CSCdk36270]

Wide-Area Networking

•When changing the encapsulation of an ISDN or dialer interface from Frame Relay to X.25 or LAPB, the router may reload. To work around this problem, configure HDLC before configuring X.25 on the dialer interface. [CSCdi44646]

•The SSCOP layer sequence number wraparound conditions leads to memory leaks and memory fragmentation problems. The problem occurs when the sscop's send sequence number reaches a maximum value of 16777215. The switch needs to be reset to continue normal functionality.

The problem can also occur in routers. The shut and no shut commands need to be issued on the ATM interface in order to reset the sequence counters. This reset may also be used to free buffer resources in a system that has encountered the SSCOP wrap but not yet crashed. [CSCdj45157]

Miscellaneous

•When running 2523 and 2524 serial ports in asynchronous mode, modem control is supported only when DTE style 5-in-1 cables are used to connect to DCE devices. The DCE 5-in-1 cable will not support modem control for the asynchronous mode. To support DTE deviceswith modem control, you must use the DTE style cables with a null modem adapter. [CSCdi72371]

•This software-forced crash occured once on a Cisco 4500 Series router. The Development Engineers are waiting for the necessary coredump, as well as debug output to pinpoint the cause. The problem has not recurred. [CSCdk56185]

Caveats for Release 11.0(1) through 11.0(21)

This section describes possibly unexpected behavior by Release 11.0(21). Unless otherwise noted, these caveats apply to all 11.0 releases up to and including 11.0(21).

Only serious caveats are described in these release notes. For the complete list of caveats against this release, access CCO or use the Documentation CD-ROM as described in the sections "Cisco Connection Online" and "Documentation CD-ROM" at the end of this document.

All the caveats listed in this section are resolved in Release 11.0(22).

Basic System Services

•From the login prompt, you can recover fragments of lines typed by the previous user of the same physical or virtual terminal line. This recovery may pose a security problem. A complete description and details are at http://www.cisco.com/warp/public/770/ioshist-pub.shtml. [CSCdk43920]

Interfaces and Bridging

•The router became very busy and hung up, seemingly because the token ring did not filter forwarded DECnet multicast frames, if permanent bridging entry and DECnet were configured. There was no workaround. [CSCdk27418]

•When transparent bridging is configured, the token ring protocol state may keep going up and down. There is no workaround.[CSCdk60152]

IP Routing Protocols

•The following platforms may reload with a bus error or segv after issuing the show ip eigrp event, show ipx eigrp event, show appletalk eigrp event commands, or by enabling Enhanced IGRP event logging for any of these protocols:

•Cisco Series1000

•Cisco Series 1250

•Cisco Series 1260

•Cisco Series1380

•Cisco Series1400

•Cisco Series1520

•Cisco Series 7000 (RP/SP)

Other platforms, including the Cisco 3600, 4500, 4700, 5300, 7000 (RSP), 7200, 7500, 8500, and RSM series routers may display the record as a spurious memory access. The Enhanced IGRP event log is invalid on all platforms.

The workaround to this problem is to not display the event log or enable Enhanced IGRP event logging. Additionally, the event log can be disabled by issuing the following commands (as appropriate) from configuration mode on the router:

IP:

router eigrp as eigrp event-log-size 0

IPX:

ipx router eigrp as event-log-size 0

Appletalk:

appletalk eigrp event-log-size 0

[CSCdk33475]

Caveats for Release 11.0(1) through 11.0(20)

This section describes caveats (possibly unexpected behavior) of Cisco IOS Release 11.0(20). These caveats also apply to Releases 11.0(1) through 11.0(19) (unless otherwise noted).

For more caveats of Release 11.0(20) and earlier 11.0 releases, see all the preceding caveats sections.

Only serious caveats are described in these release notes. For the complete list of caveats against this release, access CCO or use the Documentation CD-ROM as described in the sections "Cisco Connection Online" and "Documentation CD-ROM" at the end of this document.

All the caveats listed in this section are resolved in Release 11.0(21).

IBM Connectivity

•When using NetView version 3.1 or greater, the DLUR router may display the following message repeatedly when a runcmd is issued to a DLUR router configured with NSP over DLUR.

%APPN-7-APPNETERROR: MSP04-bAuUEcKTSepupA TRIED TO SEND TO THIS NODE FOR bAuUEcKcbDe

%APPN-7-APPNETERROR: MSP08-MDS_MU RCVD WITH ERROR

%APPN-7-APPNETERROR: 008B13100038131119810801E2C1F5D5C5E30902D4D3E5F0F5F0C1060323F0F1 
%APPN-7-APPNETERROR: F516820801E2C1F5D5C5E30602E3E2C4E5060323F0F1F4059000800000331549 
%APPN-7-APPNETERROR: 16010A01E2C1F5D5C5E340400A02C3D5D4F0F14040400A0423F0F1F540404040 
%APPN-7-APPNETERROR: 0F020000001200620602083B3200E9001C1212001880610C060A50C3D6D5E2D6 
%APPN-7-APPNETERROR: D3C5400831E2C840E5C5D9

%APPN-7-APPNETERROR: MSP08-SENSE_CODE=0x8A80009

%APPN-7-APPNETERROR: MSP08: SENSE_DATA= 0x8A80009

%APPN-7-MSALERT: Alert CPMS002 issued with sense code 0x8A80009 by XXXMSP04 

The workaround is to not use NSP over DLUR. [CSCdk19424]

Miscellaneous

•An error in TTY input processing allows interactive users to enter data that may corrupt internal data structures. This error allows anyone who can get interactive access to the system to crash it, without necessarily being able to log in. More information is available at http://www.cisco.com/warp/public/770/ioslogin-pub.shtml. [CSCdj43337]

Caveats for Releases 11.0(1) through 11.0(19)

This section describes caveats (possibly unexpected behavior) of Cisco IOS Release 11.0(19). These caveats also apply to Releases 11.0(1) through 11.0(18) (unless otherwise noted).

For more caveats of Release 11.0(19) and earlier 11.0 releases, see all the preceding caveats sections.

Only serious caveats are described in these release notes. For the complete list of caveats against this release, access CCO or use the Documentation CD-ROM as described in the sections "Cisco Connection Online" and "Documentation CD-ROM" at the end of this document.

All the caveats listed in this section are resolved in Release 11.0(20).

IBM Connectivity

•Under certain stress conditions where a router's buffer is depleting (when processing DLUR pipe traffic, gds 1500 variables), the router sends an unsolicited reset IPM request to VTAM. VTAM immediately sends a reset IPM acknowledgment. Upon receiving this reset IPM acknowledgment, the router unbinds its cpsvrmgr (DLUR pipe) and cpsvrmg (CP-CP) sessions. [CSCdj44512]

•An upstream APPN node queued all binds destined for an intermediate APPN router because of a BIND pacing. The downstream router did not responded with an IPM (pacing response) to the upstream node. The pacing window was not released by the downstream router because the BIND buffer had been lost after waiting on a send_q to a downstream node that had not responded to a pacing request, and then the link to that node was terminated. Cleanup of the downstream node's link freed the BIND in an inappropriate way. [CSCdj81746]

•An APPN ping to any unknown resource in the network can cause a router reload. This is a regression defect caused by CSCdj73921. [CSCdj84606]

•APPN/DLUR: A router reload can occur when DLUR processes a flow on the DLUS/DLUR connect, which must be responded to negatively because the PU has disconnected. This is a regression defect introduced by CSCdj59639. [CSCdj84659]

•A router may display the following recurring message on its console:

%APPN-7-MSALERT: Alert LU62004 issued with sense code 0x812000D by XXXSMPUN

This sense code indicates that APPN is running out of buffers and therefore unable to allocate new sessions. One solution is not to reserve the unbind buffers in advance during the BIND time. [CSCdj87034]

•The maximum memory access for APPN is adjusted as the maximum memory capacity of Cisco routers increase to 256 M. With this fix, the APPN subsystem can use the full 256 M of main memory for the router. [CSCdk08186]

•A regression was caused by CSCdj87034 which caused sessions to have a single DLUR DLUS pipe. [CSCdk10696]

Interfaces and Bridging

•If a board is pulled out or inserted when FEIP is transferring data, system service may be disrupted because of an internal FEIP hardware bug. The user might see either a Cybus error or a MEMD error when the problem occurs. [CSCdj89682]

IP Routing Protocols

•Under unusual circumstances, a router configured for EIGRP may lose routes from the routing table. Examination of the EIGRP topology entry for the lost route reveals the feasible distance as infinity (4294967295), even though the metric for that route is good.

The loss of the route is due to sporadic line congestion (packet drops) and/or SIA events on the same link as the neighbor occurring while a route is active. On very rare occasions, this can result in a lost acknowledge packet and a retransmission of the reply packet. For the failure to occur the retransmitted reply must have a valid metric.

A known workaround is to issue the clear ip route * command. [CSCdj73617]

•If a Cisco router is attached to a network that includes a Proteon router, free processor memory in the Cisco router can very slowly decline. This is due to a memory leak in the OSPF process. [CSCdj78467]

Miscellaneous

•Online insertion and removal (OIR) of an interface processor in an rsp-based Cisco 7000 or Cisco 7500 router may result in multiple interfaces dropping very large numbers of incoming packets after the OIR. This problem may be seen on interfaces of other boards, as well as the interfaces on the board that was inserted or removed. The problem can be observed by a large and increasing number of packets reported in the "ignore" counter in the output of the show interfaces command. Communication through these interfaces will be severely impacted. This problem is most likely to occur in routers that have many active interfaces, and some interfaces with moderate to high traffic load. The problem is rare in routers that have few active interfaces and lightly loaded interfaces. The workaround is to reload the controller microcode using the microcode reload configuration command after the OIR event or power down the router to remove and insert cards. [CSCdk07259]

Wide-Area Networking

•Under certain conditions when using CHAP authentication, the router may reload unexpectedly. [CSCdj85943]

Caveats for Releases 11.0(1) through 11.0(18)

This section describes caveats (possibly unexpected behavior) of Cisco IOS Release 11.0(18). These caveats also apply to Releases 11.0(1) through 11.0(17) (unless otherwise noted).

For more caveats of Release 11.0(18) and earlier 11.0 releases, see all the preceding caveats sections.

Only serious caveats are described in these release notes. For the complete list of caveats against this release, access CCO or use the Documentation CD-ROM as described in the sections "Cisco Connection Online" and "Documentation CD-ROM" at the end of this document.

All the caveats listed in this section are resolved in Release 11.0(19).

IBM Connectivity

•Timers are not cleaned up properly in LLC2. This may result in crashes when RSRB local acknowledgment is used under a high load. [CSCdj42474]

•Executing a show source command may cause the router to restart unexpectedly if a virtual ring group or remote peer is deconfigured when the source bridge command output is waiting at the -- more -- prompt.

The workaround is to not reconfigure virtual rings or remote peers while executing a show source command. [CSCdj49973]

•In a rare timing situation, an APPN/DLUR router may reload due to a bus error/segV exception at ndr_sndtp_encap_mu. [CSCdj59639]

•When an actpu is followed by a dactpu from VTAM and there has been no response from the downstream device to either flow, after a disconnect is received from the downstream device, DLUR will send a -rsp(actpu) upstream instead of the proper flow, a +rsp(dactpu). This can cause the PU from the DLUS perspective to hang in PDACP state. [CSCdj61872]

•It is rare, but possible, for DLUS to send a -rsp(REQDACTPU). When this happens, it indicates that VTAM has already cleaned up the PU in question. When receiving this response, DLUR must clean up the PU to avoid the PU from being stuck in "stopping" state. [CSCdj61879]

•When using APPN/DLUR with a large number of LUs (over 1000), a memory spike can occur during the processing of a downstream PU outage. In extreme cases, this memory spike can be large enough to exhaust memory in the APPN/DLUR router, which can cause a reload. [CSCdj61908]

•If an RSRB session is disconnected by the local LAN side at exactly the same time as a data message is received from a remote host, a situation can occur that will lead to a crash in llc_get_oqueue_status(). There is no workaround. [CSCdj62026]

•Session attempts fail with DLUR generating a sense 08060000 in a rare case where the LU name list gets corrupted. This problem is easily identified by the VTAM LU showing "active" state, while the show appn dlur-lu name display does not show the LU. [CSCdj62172]

•When source-route translational bridging is used, LLC sessions that are initiated from the transparent domain will result in the source-route largest frame to be incorrectly set to 4472 bytes instead of 1500. The result is that SNA and NetBIOS sessions may fail if the source-route station sends a frame with a payload that exceeds the maximum allowable size of 1500 bytes for Ethernet media.

The problem typically occurs when NetBIOS is utilized to allow workstations to communicate between Ethernet and Token Ring. It will also occur when SNA is used.

The workaround is to disable fast-switching by using the command no source-bridge transparent fastswitch or configure the end stations to use frames with a payload of less than or equal to 1500 bytes. [CSCdj62385]

•Any DLUR installation with more than 800 to 1000 downstream PUs may experience a reload with the following backtrace:

[abort(0x601f2c3c)+0x8]
[crashdump(0x601f0b20)+0x94]
[process_handle_watchdog(0x601c2f08)+0xb4]
[signal_receive(0x601b7d58)+0xa8]
[process_forced_here(0x60169424)+0x68]
[locate_node_index(0x607dbcc0)+0x64]
[etext(0x60849e00)+0xcbee04] [CSCdj67966]

•An APPN router may reload in rare situations with the following backtrace:

RA: 0x607E1724[find_matching_row(0x607e16ec)+0x38] RA: 0x607E1B9C[Tfind_next(0x607e1b70)+0x2c] RA: 0x6071182C[DBfind_next_directory_entry(0x60711814)+0x18] RA: 0x6070BAD8[CPdelete_men(0x6070ba90)+0x48] RA: 0x6070BA78[CPupdate_cp_status(0x6070b9c0)+0xb8] RA: 0x6070B40C[CPmain(0x6070b300)+0x10c] RA: 0x6070AC2C[newdss00(0x6070ab60)+0xcc] RA: 0x60183F80[r4k_process_dispatch(0x60183f6c)+0x14] [CSCdj70817]

•APPN leaks memory when directory services process unknown locate replies. [CSCdj70886]

Interfaces and Bridging

•When transparent bridging to a Token Ring interface, it is possible for the interface to read in a frame it has forwarded to the Token Ring interface. This will make the bridge table incorrect.

This problem only affects the midrange and low-end platforms. [CSCdj41666]

IP Routing Protocols

•A router may crash with a "System restarted by bus error at PC 0x60394488, address 0xD0D0D0D" message when running Cisco IOS Release 11.1(9) RSP with a heavy load of Enhanced IGRP and CSNA traffic. [CSCdj29447]

TCP/IP Host-Mode Services

•Somebody has released a program, known as land.c, that can be used to launch denial of service attacks against various TCP implementations. The program sends a TCP SYN packet (a connection initiation), giving the target host's address as both source and destination, and using the same port on the target host as both source and destination.

For in-depth information including workarounds and information on other Cisco product vulnerabilities, please see:

http://www.cisco.com/warp/customer/770/land-pub.shtml [CSCdj61324]

Wide-Area Networking

•When using DLCI prioritization on a point-to-point Frame Relay subinterface and one of the DLCIs fail, the subinterface may bounce once or continually bounce during LMI full status reports, depending on whether LMI reports the DLCI as being DELETED or INACTIVE. This behavior is the same for every DLCI defined in the priority-dlci-group.

During normal behavior, the point-to-point subinterface should go down when the primary DLCI fails. If a secondary DLCI fails, the subinterface stays up, but traffic destined for that DLCI only will fail. [CSCdj11056]

•A remote DLSw peering router may send a DM response just after the LLC2 connection is established if the router is very busy and the PC station responds immediately to the UA with an RR. The client will need to reestablish the connection. [CSCdj47782]

Caveats for Releases 11.0(1) through 11.0(17)

This section describes caveats (possibly unexpected behavior) of Cisco IOS Release 11.0(17). These caveats also apply to Releases 11.0(1) through 11.0(16) (unless otherwise noted).

For more caveats of Release 11.0(17) and earlier 11.0 releases, see all the preceding caveats sections.

Only serious caveats are described in these release notes. For the complete list of caveats against this release, access CCO or use the Documentation CD-ROM as described in the sections "Cisco Connection Online" and "Documentation CD-ROM" at the end of this document.

All the caveats listed in this section are resolved in Release 11.0(18).

Basic System Services

•On Single Flash Bank 2500 devices, when the device is running from the image on Flash (RFF), the SNMP operation of copy to Flash using CISCO-FLASH-MIB does not work.

The work around is to use the command line interface command copy tftp flash. This CLI command invokes the FLH interface and the file is copied successfully to the device. [CSCdj27438]

•When custom or priority queuing is turned off on an interface that does not support fair queuing, the queuing data structures associated with the interface are left in an inconsistent state.

In particular, the enqueue and the dequeue routines are not reset, which causes the box to crash when the routines are invoked the next time. Once the box is rebooted the inconsistency is cleared. [CSCdj29439]

•A crash occurred in the Frame Relay packet classifier function called by the WFQ routine. A workaround for this problem is to disable WFQ on the interface with Frame Relay encapsulation. [CSCdj45516]

•The input queue may be wedged with IP packets if the exception dump command is configured.

The following are known workarounds:

- Increase the input queue to 175. ([75]Original Queue amount+[100] per exception dump x.x.x.x command)

- Remove the exception dump x.x.x.x command.

[CSCdj58035]

IBM Connectivity

•When an LNM queries the router with a report station address, the router answers correctly with a report station address. However, 0.001 seconds later, the router sends a second report station address to the LNM with all zeros in the frame. This causes the LNM to work incorrectly. [CSCdj04559]

•A 1500-byte frame sent to the SR/TLB code is dropped because the SR/TLB MTU is set to 1492 bytes. [CSCdj18838]

•A small window exists in which it is possible after a transmission group reinitialization that only one CP-CP session is established between the router and a neighboring node. In this case, the contention winner session from the perspective of the router is not activated. Once this occurs, the CP-CP contention winner session will only activate if the APPN subsystem is stopped and started.

There is no known workaround. [CSCdj25859]

•An APPN image may restart because of a CPU HOG problem in processing a link failure event by the Directory Service APPN process (xxxdns00). This problem occurs when many locate requests were pending with the node that had a link failure.

There is no alternative workaround when this happens. The router is forced to restart by the system watchdog process (software-forced reload event).

The fix is to give up the CPU by the xxxdns00 process after processing certain number of requests at a time. [CSCdj26423]

•An APPN router may display the following "Unanticipated CP_STATUS" message when the contention loser CP-CP session goes down and comes back up without the contention winner session being deactivated:

%APPN-6-APPNSENDMSG: Ended DLUR connection with DLUS NETA.SJMVS1

%APPN-7-MSALERT: Alert LU62004 issued with sense code 0x8A00008 by XXXSMPUN 

%APPN-6-APPNSENDMSG: Starting DLUR connection with DLUS NETA.SJMVS4 

%APPN-7-APPNETERROR: CP_STATUS FSM: Unanticipated CP_STATUS message received 

Each subsequent broadcast locate received by the router causes the following messages to be displayed and about 1920 bytes of APPN memory to be leaked:

%APPN-7-APPNETERROR: MAP_INPUT_SET_TO_ROW: invalid input value=0x80200080

%APPN-7-APPNETERROR: State Error lcb: 60C05CC0 pcid: DA839C70FB1548CB row: 22 col: 0

This problem occurs when two links are active to the same node and the CP-CP sessions are split between these two links and the link with contention loser is stopped.

The APPN subsystem should be stopped and restarted to clear this problem. If the CP-CP sessions are between the router and the host, terminating either CP-CP session on the host will also clear this problem. [CSCdj33718]

•If the DLUR router received fixed session-level pacing values on the primary stage, it may modify these pacing values before forwarding the bind to the secondary stage. [CSCdj36195]

•The APPN router may crash during an SNMP access to the APPN MIB. This problem only occurs after an unused APPN node is garbage collected. [CSCdj36824]

•An APPN DLUR router may reload with SegV exception in ndr_sndtp_encap_mu in a timing window where the DLUR supported device disconnects before a request_actpu is sent to the DLUS for that device. [CSCdj37172]

•A problem occurs when a LU node-specific node attempts to start a session with a set of invalid Bind parameters. This results in a locate-find (with the bind in the CDINIT) being sent through the Cisco APPN network to the end VTAM CP. The end VTAM CP rejects the locate-find with a 0835003A sense. It then sends this back with a control vector CV35 of minimum length 8 bytes to the originator through the Cisco APPN network node (NN). The APPN NN then rejects the frame with a 08953500 sense and drops the CP-CP session between the Cisco and VTAM CPs. [CSCdj37479]

•APPN enforces the maximum size of a CV10 (product set identifier) on XID to not exceed 60 bytes. Some products include a CV10 that is larger than the 60-byte value. These products will fail XID negotiation with APPN. [CSCdj40144]

•In the event that APPN/DLUR has processed and sent a bind request to a downstream device, and that device has not responded to the bind, issuing a vary,inact command on the host for the LU name that the bind is destined for will not completely clean up the session as it should. [CSCdj40147]

•Memory leaks occur when APPN TPsend_search is sending locate search requests to adjacent nodes when a link failure occurs. [CSCdj40915]

•When RSRB with TCP encapsulation is configured and remwait/dead peers exist, an explorer packet may continuously try to open the remwait/dead peer. After several tries, the router may crash with memory corruption.

A workaround is to remove any remwait/dead peer statements. [CSCdj42427]

•An APPN router may crash with a bus error if a race condition is experienced during cleanup processing. The stacktrace shows the crash occurred in Qfind_front while executing a psp00 function. An example stacktrace for this problem is shown below.

System was restarted by bus error at PC 0x3784864, address 0xF0110208 PC 0x3784864[_Qfind_front(0x3040a04+0x743e44)+0x1c] RA: 0x36C1F2E[_queue_find_front(0x3040a04+0x68151c)+0xe] RA: 0x36CC554[_psbmfrm(0x3040a04+0x68bb30)+0x20] RA: 0x36CDAF6[_psp00(0x3040a04+0x68cfd4)+0x11e] RA: 0x314BD78[_process_hari_kari(0x3040a04+0x10b374)+0x0] [CSCdj44198]

•APPN crashed when it received a CV35 without the Termination Procedure Origin Name (TPON) field. [CSCdj44661]

•DLUR bind processing may cause stack corruption, resulting in a reload with PC 0x0. This problem is caused by attempting to parse the user data subfields beyond the location where the subfields exist. The reload will only occur if the byte two bytes beyond the end of the user data area is 0x3 or 0x4. This is a very rare occurrence. [CSCdj45676]

•In recent 11.0 releases, problems were experienced when APPN CP/CP sessions are split across multiple transmission groups (TG). A workaround is to force the CP/CP session to use a single TG. [CSCdj46413]

•The message "%APPN-0-APPNEMERG: Mfreeing bad storage, addr = 60BB7188, header = 60BB6B20, 00000218 -Process= "ndrmain", ipl= 0, pid= 62" may be issued when a DLUR served PU disconnects. [CSCdj46783]

•Some 68K-based routers, such as the Cisco 7000, Cisco 4000, and Cisco 2500 routers, may crash while running APPN. This memory corruption may occur after a rare combination of APPN detail displays, followed by a show appn stat display.

[CSCdj47941]

•An APPN router may fail the ACT_ROUTE if using parallel Transmission Groups (TG). This problem may occur when an APPN router has two parallel links defined with the adjacent node. If the adjacent node activated a link to the network node (NN) requesting a TG number that had previously been used for a different defined link activation, the NN may fail the ACTIVATE_ROUTE. The APPN router sometimes tried to incorrectly activate the route using the other inactive link which still had the same TG number. [CSCdj49814]

•Normal non-extended unbind (0x3201) was extended with corrupted information, which caused rejection by the host. As far as the host is concerned, the session is still active. A user cannot clean up this session without bringing down the link. [CSCdj50581]

Interfaces and Bridging

•The auto-enable feature for packet-by-packet Frame Relay compression is removed and this form of compression is allowed to be manually enabled. [CSCdi85183]

•PPP compression and custom queuing are incompatible features and may cause the router to crash. To work around this problem, turn off all fancy queuing. [CSCdj25503]

IP Routing Protocols

•A router crashes after receiving multicast packets with the illegal source address 0.0.0.0. The workaround is to configure the access list to filter out packets with a source IP address of 0.0.0.0. [CSCdj32995]

•On a Cisco 4700, RIP cannot handle more than 1800 routes received back to back without inter-frame gap. [CSCdj40042]

•If the OSPF summary host route is overwritten by a route from another routing process that has a lower administrative distance, it is possible that the OSPF summary host route will not be reinstalled after the latter route is removed. In particular, it only happens if the host route address is also the router ID of some ASBR. [CSCdj49161]

LAT

•The following message may be erroneously displayed:

%LAT-3-BADDATA: Tty124, Data pointer does not correspond to current packet

When many LAT sessions are active, and a received data slot starts in the last 14 bytes of a full Ethernet frame, data for that slot is discarded. [CSCdi82343]

Novell IPX, XNS, and Apollo Domain

•Using the xns flooding command may cause the router to reload in certain environments. [CSCdj23479]

•If a route goes away due to aging (180 seconds) and the default route is known, a cache entry may be installed for the network using the default route path. If the network comes back within the next 60 seconds, a new cache entry pointing to the now valid path may not be installed and the cache will still point to the default route path for the network. A workaround is to issue the clear ipx route and clear ipx cache commands, or run without using the default route. [CSCdj47705]

TCP/IP Host-Mode Services

•Memory allocated for a new TCP connection will not be freed after receiving an ICMP unreachable if the new connection has its own listeners for processing of incoming connections. [CSCdj07761]

VINES

•A router may unexpectedly reload when VINES SRTP routing is configured. The workaround is to remove the vines srtp-enabled command. [CSCdj37888]

Wide-Area Networking

•PPP IPCP negotiation will be changed after Cisco IOS Release 11.0(11).

In Cisco IOS Release 11.0(11) the software accepts the remote peer's "Her" proposed address regardless, and the "Her" address is subsequently added to the IP routing table as a host route.

With Cisco IOS releases later than 11.0(11) the software will check the "Her" address against the corresponding dialer map and if the address is different than the IP address detailed within the dialer map, a NAK will be sent and the dialer map IP address will be added as a host route in the IP routing table.

It is possible to revert to the previous operation using the hidden interface command ppp ipcp accept-address. When enabled, the peer IP address will be accepted but is still subject to AAA verification. It will have precedence over any local address pool, however. [CSCdj04128]

•On a Cisco 4500 running Cisco IOS Release 11.0(11) and RSRB, there may be a crash in the "llc2_timer" routine causing a system reload. [CSCdj13175]

•The patch prevents the use of an invalid pak-info_start pointer when doing payload compression on RSP platforms, thus avoiding a crash. [CSCdj43332]

•A boot image without a subsystem containing IPCP will restart the router. There is no workaround. [CSCdj48085]

Caveats for Releases 11.0(1) through 11.0(16)

This section describes caveats (possibly unexpected behavior) of Cisco IOS Release 11.0(16). These caveats also apply to Releases 11.0(1) through 11.0(15) (unless otherwise noted).

For more caveats of Release 11.0(16) and earlier 11.0 releases, see all the preceding caveats sections.

Only serious caveats are described in these release notes. For the complete list of caveats against this release, access CCO or use the Documentation CD-ROM as described in the sections "Cisco Connection Online" and "Documentation CD-ROM" at the end of this document.

All the caveats listed in this section are resolved in Release 11.0(17).

Basic System Services

•When using AAA, it is not possible to duplicate the precise sequence of prompts that dialup users have become accustomed to from using XTACACS. This makes moving from XTACACS to AAA problematic for users who do not wish to rewrite their dial-in scripts. [CSCdi42842]

•The router may reload inadvertently if you respond improperly to extended ping dialog prompts. [CSCdi88443]

•An ARAP session attempt causes NAS to reload when running AAA accounting with ARAP. [CSCdj21751]

IBM Connectivity

•Issuing the show lnm station command may cause the routers to reload, especially when the stations are getting in and out of the ring. [CSCdj09905]

•Continuously issuing the appn ping command causes the router to hang indefinitely. [CSCdj19525]

•Using the dlsw ring-list or dlsw port-list configuration commands can cause a SegV exception when executing the show dlsw reachability command. [CSCdj21894]