|
Note You can find the most current Cisco IOS documentation on Cisco.com . These electronic documents may contain updates and modifications made after the hardcopy documents were printed. |
These release notes for the Cisco 1700 series routers describe the enhancements provided in Cisco IOS Release 12.1 T. These release notes are updated as needed.
For a list of the software caveats that apply to Cisco IOS Release 12.1 T, see Caveats for Cisco IOS Release 12.1 T that accompanies these release notes. The caveats document is updated for every maintenance release and is located on Cisco.com and the Documentation CD-ROM.
Use these release notes with Cross-Platform Release Notes for Cisco IOS Release 12.1 on Cisco.com and the Documentation CD-ROM.
These release notes describe the following topics:
These release notes describe the Cisco 1700 series routers for Cisco IOS Release 12.1 T, which is an early deployment (ED) release based on Cisco IOS Release 12.1. Early deployment releases contain fixes for software caveats and support for new Cisco hardware and software features.
The following list shows the recent early deployment releases of the Cisco 1720 router:
The following list shows the recent early deployment releases of the Cisco 1750 router:
For more information, see the "Platform-Specific Documents" section about accessing related release note documents.
This section describes the system requirements for Cisco IOS Release 12.1 T:
Platforms | Feature Sets | Image Name | Software Image | Recommended Flash Memory | Recommended DRAM Memory | Runs from |
---|---|---|---|---|---|---|
48 MB1 |
||||||
48 MB1 |
||||||
48 MB1 |
||||||
48 MB1 |
||||||
132 MB in Release 12.1(4)T and earlier releases. |
Cisco IOS Release 12.1 T supports the Cisco 1700 series routers:
For detailed descriptions of the new hardware features, see "New and Changed Information" section.
The 1720 router provides Internet and intranet access and includes the following:
The Cisco 1720 router has the following hardware components:
The Cisco 1720 router supports any combination of one or two of the following WAN interface cards, which are shared with the Cisco 1600, 2600, and 3600 routers:
The voice-and-data capable Cisco 1750 router provides global Internet and company intranet access and includes the following:
The Cisco 1750 router has the following hardware components:
The Cisco 1750 router also supports any combination of one or two of the following WAN interface cards, which are shared with the Cisco 1600, 1720, 2600, and 3600 routers:
The Cisco 1750 router supports any combination of one or two of the following voice interface cards, which are shared with the Cisco 2600 and 3600 routers:
To determine the version of Cisco IOS software running on your Cisco 1700 series router, log in to the router and enter the show version EXEC command:
For general information about upgrading to a new software release, see Software Installation and Upgrade Procedures located at: http://www.cisco.com/warp/public/130/upgrade_index.shtml .
The Cisco IOS software is packaged in feature sets consisting of software imagesdepending on the platform. Each feature set contains a specific set of Cisco IOS features.
Cisco IOS Release 12.1 T supports the same feature sets as Cisco IOS Release 12.1, but Release 12.1 T can include new features supported by the Cisco 1700 series routers.
Caution Cisco IOS images with strong encryption (including, but not limited to 168-bit (3DES) data encryption feature sets) are subject to United States government export controls and have limited distribution. Strong encryption images to be installed outside the United States are likely to require an export license. Customer orders may be denied or subject to delay due to United States government regulations. When applicable, the purchaser/user must obtain local import and use authorizations for all encryption strengths. Please contact your sales representative or distributor for more information, or send an e-mail to export@cisco.com. |
Table 2, Table 3, and Table 4 list the features and feature sets supported by the Cisco 1700 series in Cisco IOS Release 12.1 T. All three tables use the following conventions:
Note These feature set tables contain only the features specific to the T-train. For a more complete list of features, see the feature set tables in the mainline release notes on Cisco.com: http://www.cisco.com/ univercd/cc/td/doc/product/software/ios 121/121relnt/xprn121/ 121 feats.htm. |
The following sections list the new hardware and software features supported by the Cisco 1700 series routers for Release 12.1 T.
The Australian version of the two-port Foreign Exchange Office (FXO) voice/fax interface card for the voice/fax network module (VIC-2FXO-M3) is supported by the Cisco 1750 in Cisco IOS Release 12.1(5)T.
The following new software features are supported by the Cisco 1700 series routers for Release 12.1(5)T:
The AutoInstall Using DHCP for LAN Interfaces feature replaces the use of the Bootstrap Protocol (BOOTP) with the use of the Dynamic Host Configuration Protocol (DHCP) for Cisco IOS AutoInstall over LAN interfaces. AutoInstall is a Cisco IOS software feature which provides for the configuration of a new routing device automatically when the device is initialized. DHCP (defined in RFC 2131) is based on the Bootstrap Protocol, which provides the framework for passing configuration information to hosts on a TCP/IP network. DHCP adds the capability of automatic allocation of reusable network addresses and additional configuration options. In Cisco IOS release 12.1(5)T, the IP address procurement phase of the AutoInstall process is now accomplished using DHCP for Ethernet, Token Ring, and FDDI interfaces. Prior to this release, IP addresses for LAN interfaces were obtained using BOOTP during the AutoInstall process. The AutoInstall Using DHCP for LAN Interfaces feature also allows the routing device to recognize IP address allocation messages coming from regular BOOTP servers, providing a seamless transition for those devices already using BOOTP servers for AutoInstall. Additionally, this feature allows for the uploading of configuration files using unicast TFTP. For further details, please see the following document:
http://www.cisco.com/ univercd/cc/td/doc/product /software/ios121 /121newft/121t/ 121t5/dt_dhcpa.htm
A closed user group (CUG) selection facility is a specific encoding element that allows a destination data terminal equipment (DTE) to identify the CUG to which the source and destination DTEs belong. The Closed User Group Selection Facility Suppress Option feature enables a user to configure an X.25 data communications equipment (DCE) interface or X.25 profile with a DCE station type to remove the CUG selection facility from incoming call packets destined for the preferential CUG only or for all CUGs. You can also remove the selection facility from a CUG with outgoing access (CUG/OA).
This feature extends the functionality of WRED (Weighted Random Early Detection) to enable support for Differentiated Services (DiffServ) and Assured Forwarding (AF) Per Hop Behavior (PHB). This feature enables WRED to be compliant with the DiffServ standard and the AF PHB standard being developed by the Internet Engineering Task Force (IETF). This feature enables customers to implement AF PHB by coloring packets according to DSCP values and then assigning preferential drop probabilities to those packets.This feature adds two new commands, random-detect dscp and dscp. It also adds two new arguments, dscp-based and prec-based, to two existing WRED-related commandsthe random-detect (interface) command and the random-detect-group command.
This feature improves the current real-time fax over Internet Protocol (IP) (known as fax relay) implementation in Cisco gateways so that fax transmissions work reliably over higher packet-loss conditions.
This feature also includes enhanced real-time fax debugging capabilities and statistics. These features give better visibility into the real-time fax operation in the gateway, allowing for improved field diagnostics and troubleshooting.
These improvements include configuration of fax relay ECM (Error Correction Mode) on the voice over IP (VoIP) dial peer. ECM provides for error-free page transmission. This mode is available on fax machines that include memory for storage of the page data (usually high-end fax machines).
Differentiated services (DiffServ) describes a set of end-to-end quality of service (QoS) capabilities. End-to-end QoS means that the network can deliver service required by specific network traffic from one end of the network to another. Cisco IOS QoS software supports three types of service models: best-effort, integrated (IntServ), and differentiated services (DiffServ).
For more information about the best-effort and integrated-service models, see the Cisco IOS Quality of Service Solution Configuration Guide.
Differentiated services is a multiple service model that satisfies different QoS requirements. The network tries to deliver service based on the QoS specified by each packet. This specification can occur in different ways, for example, using the 6-bit Differentiated Services Code Point (DSCP) setting in IP packets or source and destination addresses. The network uses the QoS specification to classify, mark, shape, police traffic, and perform intelligent queueing.
Differentiated services is used for several mission-critical applications and for providing end-to-end QoS. Typically, differentiated services is appropriate for aggregate flows because it performs a relatively coarse level of traffic classification.
Cisco IOS QoS includes the following features that support differentiated services:
For more information about Cisco IOS QoS features, see the Cisco IOS Quality of Service Solutions Guide and the Cisco IOS Quality of Service Command Reference.
Microsoft NetMeeting is a Windows-based application that enables multi-user interaction and collaboration from a users PC over the Internet or an intranet. Support for the NetMeeting Directory (ILS) allows connections by name from the directory built into the NetMeeting application. Destination IP addresses do not need to be known in order for a connection to be made.
The Network Time Protocol (NTP) is used to synchronize timekeeping among a set of distributed time servers and clients. The Cisco NTP MIB enables users to remotely monitor an NTP server using the Simple Network Management Protocol (SNMP), provided the MIB itself is implemented on that server. Use of the NTP MIB to monitor the NTP status of routing devices is accomplished using software on a Network Management System (NMS). There are no new or modified Cisco IOS software commands associated with this feature.
The Cisco implementation of the NTP MIB is based on NTP version 3 (RFC-1305). The MIB objects are all read-only. SNMP requests are processed by reading the corresponding variables from the NTP subsystem and returning them in the response. The NTP MIB defines a set of NTP server system objects, including an NTP server peers table and an NTP server filter register table. For complete details on the Cisco implementation of the NTP MIB, see the MIB file itself ("CISCO-NTP-MIB.my", available through Cisco.com at http://www.cisco.com/public/mibs/v2/).
The Parser Cache feature optimizes the parsing (translation) of Cisco IOS software configuration command lines by remembering how to parse recently encountered command lines. This feature was developed to improve the the scalability of the Cisco IOS software command-line interface (CLI) parser when processing large configuration files. This improvement is especially useful for those cases in which thousands of virtual circuits must be configured for interfaces, or hundreds of access lists (ACLs) are required. The parser chain cache can rapidly recognize and translate configuation lines which differ slightly from previously used configuration lines (for example, pvc 0/100, pvc 0/101, and so on). Testing indicates an improvement to load time of between 30% and 36% for large configuration files when using the parser cache.
The parser cache is enabled by default on all platforms using Cisco IOS 12.1(5)T or later. A new command, [no] parser cache, allows the disabling or re-enabling of this feature.
Queueing manages congestion on a router interface or a virtual circuit (VC). In a Frame Relay environment, the congestion point may not be the interface itself, but it may be the VC because of the committed information rate (CIR). For real-time traffic (voice flows) to be transmitted in a timely manner, the data rate must not exceed the CIR or packets might be dropped causing voice quality issues. Frame Relay traffic shaping (FRTS) is configured on the interfaces to control the outbound traffic rate by preventing the router from exceeding the CIR. This means that fancy queueing such as class-based weighted fair queueing (CBWFQ), low latency queueing (LLQ), and weighted fair queueing (WFQ), can run on the VC to provide the quality of service (QoS) guarantees for the traffic.
Previously, RSVP reservations were not constrained by the CIR of the flow's outbound VC. As a result, oversubscription could occur when the sum of the RSVP traffic and other traffic exceeded the CIR.
The RSVP support for Frame Relay feature allows RSVP to work with per VC (data link connection identifier (DLCI)) queueing for voice-like flows. Traffic shaping must be enabled in a Frame Relay environment for accurate admission control of resources (bandwidth and queues) at the congestion point; that is, the VC itself. Specifically, RSVP can work with VCs defined at the interface and subinterface levels. There is no limit to the number of VCs that can be configured per interface or subinterface.
The SDLC SNRM Timer and Window Size Enhancements feature introduces a new window size setting for SDLC configurations, and a new timeout setting for the SNRM frame. These enhancements change the operation of SDLC processing on a multidrop line.
Prior to this feature, all SDLC addresses on the multidrop had the same window count. Now the window count can be configured on a Physical Unit (PU) or SDLC address level. This enhancement gives a controller a different window size than other devices on the interface, and allows devices attached to the multidrop to be sized individually.
Cisco IOS software SDLC implementation currently utilizes a common response timer (T1) for all outstanding commands. Calculating the maximum frame size and line speed produces a minimum time of 3.5 seconds for receiving acknowledgments; thus, polling stations used for link activation utilize this 3.5-second timer. This is a problem on a multidrop, because stations that do not respond to the SNRM will have 3.5 seconds of downtime-waiting before the next station that is active is polled. This enhancement reduces the time to stations that are waiting idle, as opposed to those that are active.
Most protocols in the Internet assume that links are bidirectional. In particular, routing protocols used by directly connected routers no longer behave properly in the presence of a unidirectional link, such as a satellite link. The Unidirectional Link Routing feature, introduced in Cisco IOS Release 12.0(3)T, enables a router to emulate the behavior of a bidirectional link for operation of IP over unidirectional links.
The unidirectional link routing (UDLR) enhancements introduced in Cisco IOS Release 12.1(5)T include enhancements to the existing UDLR tunnel mechanism and the addition of the Internet Group Management Protocol (IGMP) proxy mechanism.
The VoIP Call Admission Control using the Resource Reservation Protocol (RSVP) feature synchronizes with H.323 Version 2 (Fast Connect) setup procedures to guarantee that the required QoS for VoIP calls is maintained across the IP network. Before Cisco IOS Release 12.1(3)XI, VoIP gateways used H.323 Version 1 (Slow Connect) procedures when initiating calls requiring bandwidth reservation. This feature, which is enabled by default, allows gateways to use H.323 Version 2 (Fast Connect) for all calls, including those requiring RSVP.
The following new software features are supported by the Cisco 1700 series routers for Release 12.1(3)T:
For the Cisco 1750 router, these enhancements provide compliance with all mandatory elements of H.323 Version 2 for the Cisco IOS based Gateway, Gatekeeper, and Proxy products. Along with other selected features, they provide critical new functionality needed for interoperablilty and network deployment. New features include:
Cisco IOS Release 12.1(3)T supports the following features:
To configure these features on Cisco 1700 series routers, see the online document Quality of Service Solutions Configuration Guide. From Cisco.com, click on the path (under the heading Service & Support):
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Configuration Guides and Command References: Configuration Guides and Command References: Quality of Service Solutions Configuration Guide
Secure Shell (SSH) is a protocol that provides a secure remote connection to another router. There are currently two versions of SSH available, SSH Version 1 and SSH Version 2. Only SSH Version 1 is implemented in Cisco IOS software.
The Secure Shell Version 1 Integrated Client feature is an application running over TCP/IP to provide strong authentication and encryption. The SSH client enables a Cisco router to make a secure, encrypted connection to another Cisco router or device running an SSH Version 1 server. This connection provides functionality that is similar to that of an outbound Telnet connection except that the connection is encrypted. With authentication and encryption, the SSH client allows for a secure communication over an insecure network.
The SSH client in Cisco IOS software works with publicly and commercially available SSH servers. The SSH client supports the ciphers of Data Encryption Standard (DES), Triple DES (3DES), and password authentication.
The SSH client functionality is available only when the SSH server is enabled.
The following new software features are supported by the Cisco 1700 series routers for Release 12.1(2)T:
Bidir-PIM is a variant of the Protocol Independent Multicast (PIM) suite of routing protocols for IP multicast. In PIM, packet traffic for a multicast group is routed according to the rules of the mode configured for that multicast group. The Cisco IOS implementation of PIM supports three modes for a multicast group:
A router can simultaneously support all three modes or any combination of them for different multicast groups. In bidirectional mode, traffic is only routed along a bidirectional shared tree that is rooted at the rendezvous point (RP) for the group. In bidir-PIM, the IP address of the RP acts as the key to having all routers establish a loop-free spanning tree topology rooted in that IP address. This IP address does not need to be a router, but can be any unassigned IP address on a network that is reachable throughout the PIM domain. Using this technique is the preferred configuration for establishing a redundant RP configuration for bidir-PIM.
Membership to a bidirectional group is signalled via explicit Join messages. Traffic from sources is unconditionally sent up the shared tree toward the RP and passed down the tree toward the receivers on each branch of the tree.
Bidir-PIM is designed to be used for many-to-many applications within individual PIM domains. Multicast groups in bidirectional mode can scale to an arbitrary number of sources without incurring overhead due to the number of sources.
Bidir-PIM is derived from the mechanisms of PIM sparse mode (PIM SM) and shares many SPT operations. Bidir-PIM also has unconditional forwarding of source traffic toward the RP upstream on the shared tree, but no registering process for sources as in PIM SM. These modifications are necessary and sufficient to allow forwarding of traffic in all routers solely based on the (*, G) multicast routing entries. This feature eliminates any source-specific state and allows scaling capability to an arbitrary number of sources.
The Frame Relay Switching Enhancements feature enables a router in a Frame Relay network to be used as a Frame Relay switch.
This feature includes the following Frame Relay switching enhancements:
Before the Frame Relay Switching Enhancements feature was introduced, routers had limited Frame Relay switching functionality. With this feature, a router acting as a virtual Frame Relay switch can be configured to do the following:
The explosive growth of the Internet has placed the focus on the scalability of Interior Gateway Protocols such as OSPF. The networks using OSPF are becoming larger every day and will continue to expand to accommodate the demand to connect to the Internet.
Internet Service Providers and customers with large networks have regularly complained that OSPF has a traffic overhead, even when the network topology is stable.
By design, OSPF requires link-state advertisements (LSAs) to be refreshed as they expire after 3600 seconds. Some implementations have tried to improve the flooding by reducing the frequency to refresh from 30 min to around 50 min or so.
This solution reduces the amount of refresh traffic but requires at least one refresh before the LSA expires. The OSPF Flooding Reduction feature works by reducing unnecessary refreshing and flooding of already known and unchanged information. To achieve this reduction, the LSAs are now flooded with the higher bit set, thus making them DoNotAge (DNA) LSAs.
The Cisco 1700 series routers, which includes the Cisco 1720 and 1750 models, are modular access routers for small and medium businesses and small branch offices. Cisco 1700 routers deliver routing, firewall, and VPN functions for Internet data and voice applications.
The VPN module, which fits into a slot inside the Cisco 1720 or 1750 chassis, assists the host processor by accelerating layer 3 IP Security (IPSec) data and voice encryption and decryption. The VPN module supports DES and 3DES encryption algorithms, MD5 and SHA-1 hashing, and Diffie-Hellman key generation.
The VPN module encrypts data using DES and 3DES algorithms at speeds suitable for full duplex T1/E1 serial connections (4 megabits per second for 1518-byte packets). Equipped with a VPN module, a Cisco 1700 router supports up to 100 encrypted tunnels for concurrent sessions with mobile users or other sites.
Voice over Frame Relay (VoFR) enables a router to carry voice traffic (for example, telephone calls and faxes) over a Frame Relay network. Configuration information is available in the "Cisco IOS Multiservice Applications Configuration Guide" and "Cisco IOS Multiservice Applications Command Reference" publications.
Before configuring VoFR on a router, you must configure your Frame Relay backbone network. As part of your Frame Relay configuration, you need to configure the map class, and the Local Management Interface (LMI) among other Frame Relay functionality. For more information about Frame Relay configuration, refer to the ''Cisco IOS Wide-Area Networking Configuration Guide.''
The Cisco VoFR implementation allows the following types of VoFR calls:
The following new software features are supported by the Cisco 1700 series routers for Release 12.1(1)T:
Secure Shell (SSH) is a protocol that provides a secure, remote connection to a router. There are currently two versions of SSH available: SSH Version 1 and SSH Version 2. Only SSH Version 1 is implemented in Cisco IOS software.
The SSH server feature enables a SSH client to make a secure, encrypted connection to a Cisco router. This connection provides functionality that is similar to an inbound Telnet connection. The SSH server in Cisco IOS software will work with publicly and commercially available SSH clients.
Cisco H.323 Version 2 Phase 2 enhancements upgrade several optional features of the H.323 Version 2 specification, and facilitate customized extensions to the Cisco Gatekeeper.
H.245 tunneling is backward compatible with H.323 Version 1 configurations.
Note Certain devices are limited in their support of H.450. The Cisco 1700 and ubr820 platforms do not support Interactive Voice Response (IVR). Therefore, these platforms are not able to act as H.450 Transferring endpoints. |
Old Cisco Management Information Bases (MIBs) will be replaced in a future release. Currently, OLD-CISCO-* MIBs are being converted into more scalable MIBswithout affecting existing Cisco IOS products or NMS applications. You can update from deprecated MIBs to the replacement MIBs as shown in Table 5.
Note Cisco Management Information Base (MIB) User Quick Reference is no longer published. If you have an account with Cisco.com, you can find the current list of MIBs supported by Cisco. To reach the Cisco Network Management Toolkit, go to Cisco.com, press Login, and click to Software Center: Network Mgmt Products: Cisco Network Management Toolkit: Cisco MIB. |
The following sections contain important notes about Cisco IOS Release 12.1 T that can apply to the Cisco 1700 series routers.
The last maintenance release of the 12.1 T release train is 12.1(5)T. The migration path for customers who need bug fixes for the 12.1 T features is the 12.2 mainline release. The 12.2 mainline release has the complete feature content of 12.1 T and will eventually reach general deployment (GD).
The last maintenance release was renamed from 12.1(4)T to 12.1(5)T to synchronize with its parent software base, the 12.1(5) mainline release, and to reflect that 12.1(5)T has all the bug fixes of the 12.1(5) mainline release. The 12.1 T release train is a superset of the 12.1 mainline release; hence any defect fixed in the 12.1 mainline is also fixed in 12.1 T. The set of features for 12.1(4)T is the same as that for 12.1(5)T. There was no change in the feature content of the release. The release was renamed so that the releases would be consistent with the Cisco release process.
A defect in multiple releases of Cisco IOS software will cause a Cisco router or switch to halt and reload if the IOS HTTP service is enabled, browsing to http://router-ip/anytext?/ is attempted, and the enable password is supplied when requested. This defect can be exploited to produce a denial of service (DoS) attack.
The vulnerability, identified as Cisco bug ID CSCdr91706, affects virtually all mainstream Cisco routers and switches running Cisco IOS software releases 12.0 through 12.1, inclusive. This is not the same defect as CSCdr36952.
The vulnerability has been corrected and Cisco is making fixed releases available for free to replace all affected IOS releases. Customers are urged to upgrade to releases that are not vulnerable to this defect as shown in detail below.
This vulnerability can only be exploited if the enable password is known or not set.
You are strongly encouraged to read the complete advisory, which is available at http://www.cisco.com/warp/public/707/ioshttpserverquery-pub.shtml .
Booting a Cisco 1700 series router with the commands boot flash or boot system flash results in unpredictable behavior. To work around this problem, be sure to enter a colon (:) following both commands (for example, boot flash: or boot system flash:).
Be advised that the fans in the Cisco 1700 series routers stay off until thermally activated (45°C/115°F).
When using a multipartition flash card, the various flash partitions are referred to as "flash:1:", "flash:2:", etc. If you specify only "flash" in a multipartition flash, the parser assumes "flash:1:." For example, if you enter show flash all the parser defaults to "show flash:1: all" and only the flash information for the first partition displays. To see information for all flash partitions, enter show flash ?. This will list all of the valid partitions. Then enter show flash:xx: all on each valid partition.
Caveats describe unexpected behavior in Cisco IOS software releases. Severity 1 caveats are the most serious caveats; severity 2 caveats are less serious. Severity 3 caveats are moderate caveats, and only select severity 3 caveats are included in the caveats document.
For information on caveats in Cisco IOS Release 12.1 T, see Caveats for Cisco IOS Release 12.1 T.
All caveats in Cisco IOS Release 12.1 are also in Cisco IOS Release 12.1 T.
For information on caveats in Cisco IOS Release 12.0, see Caveats for Cisco IOS Release 12.1, which lists severity 1 and 2 caveats and is located on Cisco.com and the Documentation CD-ROM.
This section describes possibly unexpected behavior by Release12.1(3)T, specific to the Cisco 1750 router only. The following caveats are severity 3.
The Cisco 1750 router is a Residential Gateway (RGW) and supports MGCP on FXS ports only, therefore, do not configure MGCP on FXO or E&M ports.
From the perspective of the Cisco 1750 router command line interface (CLI), the format used to describe the slot and port is <slot>/<port>. However, after executing the command show mgcp endpoint, the Cisco 1750 router might display the output in the format <slot>/<subinterface>/<port>, such as 0/0/1 for port 0/1. The 0 digit for the <slot> does not represent hardware; it is a phantom number added by Cisco 1750 internal code because there is no concept of a subinterface for Cisco 1750 routers. This syntax structure matches that of some other networking equipment requiring unique specifications for all three hardware aspects:the slot number, the sub-unit number, and the port number. On the Cisco 1750 router, the <subinterface> is actually the slot number. The output format of the command show mgcp endpoint thus provides information about how to configure the command call agent.
This section describes possibly unexpected behavior by Release12.1(1)T, specific to the Cisco 1700 series routers. Only severity 1 and 2 caveats are included.
The Australian variant of the two-port Foreign Exchange Office (FXO) voice/fax interface card for the voice/fax network module (VIC-2FXO-M3) is not supported by the Cisco 1750 at this time.
The following sections describe the documentation available for the Cisco 1700 series routers. These documents consist of hardware and software installation guides, Cisco IOS configuration and command references, system error messages, feature modules, and other documents.
Documentation is available as printed manuals or electronic documents, except for feature modules, which are available online on Cisco.com and the Documentation CD-ROM.
Use these release notes with these documents:
The following documents are specific to Cisco IOS Release 12.1 and are located on Cisco.com and the Documentation CD-ROM:
On Cisco.com at:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Release Notes: Cross-Platform Release Notes
See Caveats for Cisco IOS Release 12.1 and Caveats for Cisco IOS Release 12.1 T, which contain caveats applicable to all platforms for all maintenance releases of Cisco IOS Release 12.1 and Release 12.1 T.
On Cisco.com at:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Caveats
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Caveats
These individual and groups of documents are available for the Cisco 1720 router on Cisco.com and the Documentation CD-ROM:
On Cisco.com at:
Technical Documents: Documentation Home Page: Cisco Product Documentation: Access Servers and Access Routers: Modular Access Routers: Cisco 1720 Router
On the Documentation CD-ROM at:
Cisco Product Documentation: Access Servers and Access Routers: Modular Access Routers: Cisco 1720 Router
These individual and groups of documents are available for the Cisco 1750 router on Cisco.com and the Documentation CD-ROM:
On Cisco.com at:
Technical Documents: Documentation Home Page: Cisco Product Documentation: Access Servers and Access Routers: Modular Access Routers: Cisco 1750 Router
On the Documentation CD-ROM at:
Cisco Product Documentation: Access Servers and Access Routers: Modular Access Routers: Cisco 1750 Router
Feature modules describe new features supported by Cisco IOS Release 12.1 T and are updates to the Cisco IOS documentation set. A feature module consists of a brief overview of the feature, benefits, configuration tasks, and a command reference. As updates, the feature modules are available online only. Feature module information is incorporated in the next printing of the Cisco IOS documentation set.
On Cisco.com at:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1: New Feature Documentation
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1: New Feature Documentation
The Cisco IOS software documentation set consists of the Cisco IOS configuration guides, Cisco IOS command references, and several other supporting documents that are shipped with your order in electronic form on the Documentation CD-ROMunless you specifically ordered the printed versions.
Each module in the Cisco IOS documentation set consists of two books: a configuration guide and a corresponding command reference. Chapters in a configuration guide describe protocols, configuration tasks, Cisco IOS software functionality, and contain comprehensive configuration examples. Chapters in a command reference provide complete command syntax information. Use each configuration guide with its corresponding command reference.
On Cisco.com and the Documentation CD-ROM, two master hot-linked documents provide information for the Cisco IOS software documentation set.
On Cisco.com at:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Configuration Guides and Command References
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Configuration Guides and Command References
Table 6 describes the contents of the Cisco IOS Release 12.1 software documentation set, which is available in electronic form and in printed form ordered.
Note You can find the most current Cisco IOS documentation on Cisco.com and the Documentation CD-ROM. These electronic documents may contain updates and modifications made after the hard-copy documents were printed. |
On Cisco.com at:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1
Note Cisco Management Information Base (MIB) User Quick Reference is no longer published. If you have an account with Cisco.com, you can find the current list of MIBs supported by Cisco. To reach the Cisco Network Management Toolkit, go to CC, press Login, and click to Software Center: Network Mgmt Products: Cisco Network Management Toolkit: Cisco MIB. |
You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly. Therefore, it is probably more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Registered Cisco.com users can order the Documentation CD-ROM and other Cisco Product documentation through our online Subscription Services at http://www.cisco.com/cgi-bin/subcat/kaojump.cgi.
Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco's corporate headquarters (California, USA) at 408 526-4000 or, in North America, call 800 553-NETS (6387).
Cisco provides Cisco.com as a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center. All customers can submit technical feedback on Cisco documentation using the web, e-mail, a self-addressed stamped response card included in many printed documents, or by sending mail to Cisco.
Cisco continues to revolutionize how business is done on the Internet. Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
Cisco.com's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through Cisco.com, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users may order products, check on the status of an order and view benefits specific to their relationships with Cisco.
You can access Cisco.com in the following ways:
You can e-mail questions about using Cisco.com to cco-team@cisco.com.
The Cisco Technical Assistance Center (TAC) is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.
To display the TAC web site that includes links to technical support information and software upgrades and for requesting TAC support, use www.cisco.com/techsupport.
To contact by e-mail, use one of the following:
Language | E-mail Address |
---|---|
In North America, TAC can be reached at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following web site: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.
If you have a Cisco.com log-in account, you can access the following URL, which contains links and tips on configuring your Cisco products:
http://www.cisco.com /public/technotes/tech_sw.html
This URL is subject to change without notice. If it changes, point your Web browser to Cisco.com, press Login, and click on this path: Technical Assistance Center: Technical Tips.
The following sections are provided from the Technical Tips page:
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:
Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate and value your comments.
Posted: Thu Jan 16 11:41:28 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.