cc/td/doc/product/atm/c8510/wa5/12_0
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Release Notes for the
Catalyst 8510 MSR for Cisco IOS Release 12.0(1a)W5(5b)

Release Notes for the
Catalyst 8510 MSR for Cisco IOS Release 12.0(1a)W5(5b)

September 14, 1999

Catalyst 8510 MSR Cisco IOS Release 12.0(1a)W5(5b)

This document describes the features and caveats for Cisco IOS Release 12.0(1a)W5(5b) for the Catalyst 8510 MSR software.

For a list of software caveats that apply to this release, refer to the "Caveats" section.

Contents

This document includes the following sections:

Introduction

The Catalyst 8510 MSR provides switched ATM connections to individual workstations, servers, LAN segments, or other ATM switches and routers using fiber-optic, unshielded twisted-pair (UTP), and coaxial cable.

Note The ATM switch processor and port adapters can be installed in the Catalyst 5500 switch chassis.

System Requirements

This section describes the system requirements for Release 12.0(1a)W5(5b) and includes the following sections:

Memory Requirements

The DRAM memory configuration is 64-MB DRAM (MEM-ASP64M), which is the default for the Catalyst 8510 MSR.

Hardware Supported

Table 1 lists the interfaces supported on the Catalyst 8510 MSR Release 12.0(1a)W5(5b) and their minimum software release.


Table 1: Supported Interfaces and Their Minimum Software Requirements
Part Number Description Minimum Software Requirement

WAI-OC3-4MM

4-port STS-3c/STM-1 multimode fiber port adapters

WAS5-5

WAI-OC3-4SS

4-port STS-3c/STM-1 single-mode fiber port adapters

WAS5-5

WAI-OC3-4U5

4-port STS-3c/STM-1 UTP-5 port adapters

WAS5-5

WAI-OC3-4SSLR

4-port STS-3c/STM-1 SMF long reach port adapters

WAS5-5

WAI-OC3-1S3M

OC-3 mix port adapter module, 1 IR+ port and 3 MM ports

WAS5-5

WAI-OC12-1MM

1-port STS-12c/STM-4c multimode fiber port adapters

WAS5-5

WAI-OC12-1SS

1-port STS-12c/STM-4c SMF port adapters

WAS5-5

WAI-OC12-1SSLR

1-port STS-12c/STM-4c SMF long reach port adapters

WAS5-5

WAI-ATM25-12P

12-port ATM 25 port adapters with 96-pin telco cable

WAS5-5

WAI-T3-2BNC

2-port DS-3 port adapters

WAS5-5

WAI-E3-2BNC

2-port E3 port adapters

WAS5-5

WAI-T3-4BNC

4-port DS-3 port adapters

WAS5-5

WAI-E3-4BNC

4-port E3 port adapters

WAS5-5

WAI-T1-4RJ48

4-port T1 (ATM) with RJ-48 interface port adapters

WAS5-5

WAI-E1-4RJ48

4-port E1 (ATM) with RJ-48 interface port adapters

WAS5-5

WAI-E1-4BNC

4-port E1 (ATM) with BNC interface port adapters

WAS5-5

WAI-T1C-4RJ48

4-port T1 (circuit emulation) with RJ-48 interface port adapters

WAS5-5

WAI-E1C-4RJ48

4-port E1 (circuit emulation) with RJ-48 interface port adapters

WAS5-5

WAI-E1C-4BNC

4-port E1 (circuit emulation) with BNC interface port adapters

WAS5-5

L1010-PWR-DC

Power supply DC

WAS5-5

C8515-MSRP

Hot swappable multiservice switch route processor

WAS5-5

C85MS-4E1-FRRJ48

4-port CE1 with RJ-48c interface Frame Relay port adapters

WAS5-5

WS-X5165

ATM-Fabric Integration Module for the Catalyst 5500

WAS5-5

Determining Your Software Release

To determine the version of Cisco IOS software currently running on the Catalyst 8510 MSR, log into the switch and use the show version EXEC command. The following is sample output from the show version command. The version number is indicated on the second line as shown below:

Cisco Internetwork Operating System Software
IOS (tm) Catalyst 8510 MSR W5-5 Software (CAT8510M-WP-M), Version 12.0(0.19)W5(5.0.2)

Additional command output lines include more information, such as processor revision numbers, memory amounts, hardware IDs, and partition information.

Other Firmware Code

This section describes the firmware code installed on an interface that might be updated in the field.

Table 2 lists the port adapters and the firmware that might be updated in the field.


Table 2: Interfaces Supporting Field upgrade and Version
Interface, Module, or Port Adapter Type Product Name Firmware File Name

Four Port E1

Frame Relay port adapter

fi-c8510-4e1fr.A.2_3

For information describing the firmware update process, refer to the chapter "Managing Configuration Files" and the section "Maintaining Functional Images" in the LightStream 1010 ATM Switch and Catalyst 8510 MSR Software Configuration Guide.

Feature Set Tables

The Cisco IOS software is packaged in feature sets (also called software images) depending on the platform. Each feature set contains a specific set of Cisco IOS features. The following section lists the features set matrix and the features supported by each feature set.

Table 3 lists the Cisco IOS software feature sets available for the Catalyst 8510 MSR in Cisco IOS Release 12.0(1a)W5(5b).


Table 3: Feature Sets Supported by the Catalyst 8510 MSR
Feature Set 12.0(1a)W5(5b)

Left-justified E.164 AFI support

x

SNMP1

x

Asynchronous support

x

PPP2 (SLIP3/PPP)

x

IP4

x

NTP5

x

TACACS+6

x

Telnet

x

Point-to-point and point-to-multipoint permanent VCCs7 and VPCs8

x

Point-to-point and point-to-multipoint switched VCCs and VPCs (UNI 3.0)

x

Point-to-point and point-to-multipoint switched VCCs and VPCs (UNI 3.1)

x

Point-to-point and point-to-multipoint switched VCCs and VPCs (UNI 4.0)

x

Multipoint-to-point UNI signaling

x

Soft VCCs and VPCs

x

VP tunneling

x

VPI/VCI range support in ILMI 4.0

x

PNNI hierarchy

x

ILMI version 4.0

x

IISP9

x

LANE10 client (LEC11) and LANE Services (LES12/BUS13/LECS14) on ASP15

x

Token Ring LANE services

x

ATM ARP16 server on ASP

x

ATM ARP client on ASP

x

ATM tag switch router (TSR)

x

Port snooping

x

OAM17 F4 and F5

x

E.164 address translation

x

E.164 autoconversion

x

Circuit emulation

x

ATM access lists

x

ATM accounting

x

ATM RMON18

x

Multiple, weighted, dynamic thresholds for selective packet marking and discard

x

Shaped VP tunnels for CBR traffic (FC-PFQ only)

x

Substitution of other service categories in shaped VP tunnels (FC-PFQ feature cards only)

x

Dual leaky bucket policing (FC-PFQ feature cards only)

x

Scheduler/Service Class/PVC configuration for FC-PFQ feature cards

x

Logical multicast support (up to 254 leaves per output port, per point-to-multipoint VC) (FC-PFQ feature cards only)

x

Network clocking enhancements for smooth switchover (FC-PFQ feature cards only)

x

Per-VC or per-VP nondisruptive snooping (FC-PFQ feature cards only)

x

Support for non-zero MCR19 on ABR connections (FC-PFQ feature cards only)

x

Access lists on ILMI registration

x

CUGs

x

ATM soft restart

x

ATM accounting enhancements

x

CISCO-SYSLOG-MIB support

x

CISCO-CONFIG-COPY-MIB support

x

Signaling diagnostics and MIB

x

Supplemental AToM MIB

x

E1 Frame Relay Port Adapter

x

Frame Relay to ATM Interworking Features on the Channelized E1 Port Adapter

x

Hierarchical VP Tunnels

x

Remote Logging for Accounting

x

Tag Switching VC-Merge on Non-UBR VP Tunnels and Hierarchical VP Tunnels

x

PNNI Complex Node Representation

x

Support for ATM-Fabric Integration Module in Catalyst 5500

x

1SNMP = Simple Network Management Protocol.
2PPP = Point-to-Point Protocol.
3SLIP = Serial Line Internet Protocol.
4IP = Internet Protocol.
5NTP = Network Time Protocol.
6TACACS+ = Terminal Access Controller Access Control System.
7VCCs = virtual channel connections.
8VPCs = virtual path connections.
9IISP = Interim-Interswitch Signaling Protocol.
10LANE = LAN Emulation.
11LEC = LAN Emulation Client.
12LES = LAN Emulation Server.
13BUS = broadcast and unknown server.
14LECS = LAN Emulation Configuration Server.
15ASP = ATM switch processor.
16ARP = Address Resolution Protocol.
17OAM = Operation, Administration, and Maintenance.
18RMON = Remote Monitoring.
19MCR = minimum cell rate.

New and Changed Information

This section lists some of the features available for the Catalyst 8510 MSR in Cisco IOS Release 12.0(1a)W5(5b) software.

See the section "Related Documentation" for a list of documents that describe these features.

Important Notes

Table 4 lists the release names, versions, and part numbers used with the Catalyst 8510 MSR.


Table 4:
Release Name Release Version Part Number

WAS1-1

11.1.(4)

SF-WAS1-11.1.4

WAS1-2

11.1.(410)

SF-WAS1-11.1.410

WAS1-3

11.1.(6)

SF-WAS1-11.1.6

WAS1-4

11.1.(8)

SF-WAS1-11.1.8

WAS1-5

11.1.(9)

SF-WAS1-11.1.9

WAS1-6

11.1.(11)

SF-WAS1-11.1.11

WAS2-1

11.1.(410)

SF-WAS2-11.1.410

WAS2-2

11.1.(6)

SF-WAS2-11.1.6

WAS2-3

11.1.(8)

SF-WAS2-11.1.8

WAS2-4

11.1.(9)

SF-WAS2-11.1.9

WAS2-5

11.1.(11)

SF-WAS2-11.1.11

WAS3-1

11.2(2)WA3(1a)

SF-WAS3-11.2.2

WAS3-2

11.2(5)WA3(2b)

SF-WAS3-11.2.5

WAS3-3

11.2(8)WA3(3)

SF-WAS3-11.2.8

WAS3-4

11.2(10)WA3(4)

SF-WAS3-11.2.10

WAS3-5

11.2(12)WA3(5)

SF-WAS3-5

WAS3-6

11.2(15)WA3(6)

SF-WAS3-6

WAS3-7

11.2(15)WA3(7)

SF-WAS3-7

WAS4-1

11.2.0(8.0.1)FWA4(1)

SF-WAS4-11.2.8.1S

WAS4-2

11.3(0.8)TWA4(2)

SF-WAS4-2

WAS4-4

11.3(2a)WA4(4)

SF-WAS4-4

WAS4-6

11.3(3a)WA4(6)

SF-WAS4-6

WAS4-7

12.0(2a)

SF-WAS4-7

WAS5-5

12.0(1a)W5(5b)

SF-WAS5-5

Release Name to Version and Part Number Matrix

Caveats

This section contains listings of the caveats for each release. Use Table 5 to determine if a particular caveat applies to your software release, or if a particular caveat was corrected in your software release. These caveats are described in detail in the section "Open Caveats - Release 12.0(1a)W5(5b)."


Table 5: Release Caveats and Caveats Corrected Reference 
DDTS Number Software Release
12.0(1a)W5(5b)
Corrected Caveat

CSCdi55937

x

CSCdi74229

x

CSCdi75584

x

CSCdi82954

x

CSCdi83275

x

CSCdi92142

x

CSCdj01016

x

CSCdj01757

x

CSCdj10889

x

CSCdj13565

x

CSCdj18430

x

CSCdj18583

x

CSCdj18678

x

CSCdj24272

x

CSCdj25772

x

CSCdj42669

x

CSCdj42967

x

CSCdj54954

x

CSCdj59640

x

CSCdj68412

x

CSCdj71109

x

CSCdj71876

x

CSCdj78305

x

CSCdj80396

x

CSCdj82930

x

CSCdj84344

x

CSCdj84379

x

CSCdj85853

x

CSCdj86073

x

CSCdk03049

x

CSCdk07378

x

CSCdk10398

x

CSCdk25256

x

CSCdk26482

x

CSCdk27725

x

CSCdk41001

x

CSCdk41605

x

CSCdk47516

x

CSCdk49213

x

CSCdk56557

x

CSCdk57536

x

CSCdk63547

x

CSCdk73733

x

Open Caveats - Release 12.0(1a)W5(5b)

This section describes unsupported features and limitations, caveats, and some potentially unexpected behavior by the Catalyst 8510 MSR for Cisco IOS Release 12.0(1a)W5(5b).

The following caveats have been identified for this release of the Catalyst 8510 MSR software:

Symptom: Remote defect identification (RDI) cells sent by an end point in response to alarm indication signal (AIS) cells generated at an intermediate switch with a fault condition on an interface are not propagated beyond the intermediate switch. The intermediate switch removes the connection leg entries for both interfaces participating in the connection when a fault is discovered on one of the interfaces, even though the other interface might still be up. As a result, the RDI cells are dropped at the intermediate switch.
Workaround: None.
Symptom: When more than 1000 SVCs are active on an interface and the shutdown command is entered, all SVCs on that interface are released and the following message appears:
%SYS-3-CPUHOG
This message indicates that the release process runs for a long time before returning control to the kernel, which can then schedule other tasks. This process does not affect normal operation of the switch.
Workaround: None.
Symptom: Under very heavy traffic conditions the switch might experience temporary queue cell failures. This should clear after the traffic congestion clears.
Workaround: None.
Symptom: The receiver circuitry on DS3 port adapters can interpret noise as a valid signal. This signal is framed incorrectly and does not contain real data. The DS3 controller interprets the signal as a bad signal instead of no signal, and the red RX light emitting diode (LED) lights up.
Workaround: None.
Symptom: When a large number of LANE clients come up and down constantly over extended periods of time, the system can run out of AAL5 buffers and the following message appears:
%AAL5-3-INTERNAL_ERROR: No more big aal5 pkts
In most cases, the system continues to function normally, but occasionally the system denies additional calls from end systems.
Workaround: Toggle the interface to reinitialize all connections and restore normal operation.
Symptom: A LECS, using Cisco IOS Version 11.2(X), expects all LESs to establish an individual control VC to the LECS in order to validate clients.
If different Emulated Local Area Networks (ELANs), using Cisco IOS Release 11.1(X), are configured on multiple subinterfaces of the same physical interface, then all LES(s) multiplex the control messages (which validate the clients) into a single VC.
For example, see the following LES router configuration: 
atm1/0.1    sysa_70k_31_a1.1_LAN sysa_70k_31_a1.1_LAN
atm1/0.2    sysa_70k_31_a1.2_LAN sysa_70k_31_a1.2_LAN
atm1/0.3    sysa_70k_31_a1.3_LAN sysa_70k_31_a1.3_LAN
atm1/0.4    sysa_70k_31_a1.4_LAN sysa_70k_31_a1.4_LAN
This configuration of an LECS sends the following warning messages to the console stating that an LES of one ELAN is attempting to obtain information about another ELAN:
%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.1_LAN'
%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.2_LAN'
%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.3_LAN'
The clients are still allowed to join the ELAN. Disregard the warning message.
Workaround: None.
Symptom: You can create variable bit rate (VBR), available bit rate (ABR), and unspecified bit rate (UBR) VCs across the switch with peak cell rate (PCR) values greater than the interface line rate. However, the actual allocated bandwidth continues to be:
Workaround: None.
Symptom: When one of the installed power supplies is powered OFF, and you are copying an image to bootflash, a power supply failure message appears.
Workaround: None.
Symptom: The call attempt counters for PortSelectGroups might not count the outgoing calls on its NNI interfaces because of switch crankback attempts. This might result in a discrepancy between the call attempt counters shown on Portselgroup representing the interface on which the call came in and the counters shown on the PortSelgroup representing the interface over which an attempt was made to forward the call. This problem might occur when a call fails.
Workaround: None.
Symptom: ATM RMON data collection is not supported on subinterfaces or tunnels. The atm rmon collect command is accepted on hardware interfaces only; it is ignored on subinterfaces. SNMP and NVGEN support (via portSelTable) is not possible until the Interfaces MIB (RFC 1573) entries are added for tunnel subinterfaces. ATM RMON counters for a hardware interface do not include any of the traffic through tunnels configured on the interface.
Workaround: None.
Symptom: The cell count reported on a snooped interface is twice the actual number of cells transmitted.
Workaround: None.
Symptom: Supporting ABR VP tunnels require interaction between VP flow-control and VC marking that neither FC-PCQ nor FC-PFQ hardware can perform. The configuration of an ABR VP tunnel subinterface is prevented.
Workaround: None.
Symptom: SNMP support of the ciscoAtmIfPhysEntryData table and LED information is not available on the 25-MB port adapter.
Workaround: None.
Symptom: The system crashes when you enter the no shutdown command on an E3 interface and the port adapter is not installed.
Workaround: None.
Symptom: Cell loss might occur while hot swapping a power supply.
Workaround: None.
Symptom: Spurious memory messages display when trying to create 96 tunnels between two ATM switches on three links.
Workaround: None.
Symptom: When memory is almost or completely exhausted and a soft PVC goes down, it might not come back up, leaving it in a releasing or inactive state.
Workaround: None.
Symptom: In an Catalyst 8510 MSR equipped with an FC-PFQ, the maximum number of cells available for use is 64511. The number of cells in the switch fabric is 65535.
Workaround: None.
Symptom: When running a test between two CES ports, you might see AIS problems when a CES DSX1 loopback payload is activated.
Workaround: None.
Symptom: If there are multiple parallel paths to the same destination on a Catalyst 8510 MSR with a FC-PFQ feature card installed, the tag switching VCs (TVCs) should be load balanced on a per network prefix basis over these parallel paths (up to a maximum of 4 parallel paths) instead of being VC merged. Load balancing does not happen in some cases and the TVCs might be VC merge and go out of the switch as a single VC.
Workaround: None.
Symptom: The ATM switch does not currently support maxvc-number negotiation through ILMI.
Workaround: None.
Symptom: Under some rare conditions (not yet identified), some ports might get stuck in the WaitDevType state.
Workaround: Reboot the switch.
Symptom: IP host-routing does not disable when specified.
Workaround: Enable and disable ip routing and then save the configuration to NVRAM.
Symptom: Open shortest path first (OSPF) does not recognize more than four parallel interfaces. This might cause some tag VCs (TVCs) to not get switched to other interfaces if a tunnel carrying the TVCs is shut down.
Workaround: Enter a clear ip route command on the switch on the interface that was shut, or a clear ip route command on all the switches to bring everything back up most of the time. If the clear ip route command does not work, enter a shut/no shut command on the UNI interfaces on the switch on which the physical interface was shut to bring everything back up.
Symptom: There is a small divergence in the measured output of the shaped VP tunnels at rates of 90 Mbps and above.
Workaround: None.
Symptom: The granularity provided by the FC-PFQ feature card scheduling hardware does not allow an exact match of all requested cell rates. To satisfy the traffic contract guarantee, the next higher available scheduling value is used. A shaped VP tunnel is used frequently to pass data to a WAN VP trunk, and limits the traffic transmitted to the scheduled rate. This can cause cells to be dropped in the WAN. Any dropping must be done prior to multiplexing onto the VP, so that a packet discard can be performed.
Workaround: Refer to the information in the DDTs for information on how to make a conversion of a requested rate to the actual rate.
Symptom: When you set the ROM monitor environment variable boot to a nonexistent file (using the Cisco IOS command boot system flash) and the configuration register is set to 0x2102 (autoboot), the switch hangs during the subsequent reload command issued by the software.
Workaround: Power-cycle the switch; a break character is sent to the switch to force it to the ROM monitor prompt. You can then manually reboot the switch.
Symptom: The following messages might appear on the console:
SYS-3-MGDTIMER Unitialized timer
This message is harmless and no loss of function occurs.
Workaround: None.
Symptom: The show atm vc interface vpi vci command displays incorrect transmit (TX) cell counter values on the VC-merged leg of the connection.
Workaround: None.
Symptom: Funnel VCs can jeopardize quality of service (QoS) for services.
The current multipoint-to-point funnel implementation can compromise the QOS guarantees of other connections (guaranteed services) when the application that created the funnel SVC malfunctions. For example, if the application were to transmit traffic on more than one leg of the funnel SVC simultaneously, the rate scheduler on the output interface will over-subscribe and, potentially, affect the peak cell rate (PCR), sustained cell rate (SCR), and maximum cell rate (MCR) guarantees for other VCs on the interface.
Symptom: Non-zero generic flow control (GFC) field is not reset to zero when passing through the switch.
When cells with a non-zero GFC field are received on a PVC, they are switched on the exit port without changing the GFC field. The switch should reset to zero all GFC bits from cells received with non-zero GFC at the user network interface (UNI).
Workaround: None.
Symptom: The following error message appears when using the show atm interface resource atm card/subcard/port.subport command:
Tunnel:%ATMCORE-3-INTERNAL_ERROR: show_atm_int_rm: Cannot find phylo
This error message appears because the tunnel specified in the CLI has been deleted and the software has released all the structures pertaining to that tunnel.
Workaround: None.
Symptom: Snooping error: %ATMCORE-3-INTERNAL_ERROR:connUpdateFreeVxiMap:bitMapInfo
When snoop-VC is configured on a port the switch returns these internal error messages.
%ATMCORE-3-INTERNAL_ERROR: connUpdateFreeVxiMap: bitMapInfo null ptr
Workaround: These messages can be ignored; they do not affect the snooping functionality.
Symptom: The show controller atm card/subcard/port command displays the incorrect interface type after hot-swapping the port adapter.
Workaround: None.
Symptom: PNNI PVP 18 does not automatically come up on VP tunnels of loopbacked Network-to-Network Interfaces (NNIs).
The following scenario will cause Private Network-Network Interface (PNNI) not to come up on a logical interface because the well-known VC, 0,18 (used for PNNI) is not automatically created:
Workaround: None.
Symptom: Tag switching and Tag Discovery Protocol (TDP): Memory fragmentation
While running tag-switching with a very large number of destinations, continuous toggling of VC Merge (which forces all the TDP sessions to restart) on the switch for a very extended period of time (for example, overnight) causes memory fragmentation in the TDP process.
Workaround: None.
Symptom: Frame Relay soft-VC is not released when line protocol goes down.
When the Local Management Interface (LMI) configured on a Frame Relay interface brings down the line protocol of that interface, the soft-PVCs originating from or terminating on that Frame Relay interface are not torn down.
Workaround: None.
Symptom: Spurious memory access on show ip route when SONICT interface is shutdown.
If you shutdown a 10-Mbps port and then use the show ip route command, spurious memory access appears in the print_route_preamble():
Workaround: None.
Symptom: The following message appears on the neighbor ATM switch after using the reload command:
%SYS-3-CPUHOG: Task ran for 3984 msec (24/11), process = Net Background

Workaround: None.
Symptom: Frame Relay soft-VC configuration is not possible using SNMP.
You can not configure Frame Relay soft-VCs using the casfVcEndptTable in SNMP.
Workaround: None.
Symptom: Power-on diagnostics will display an NVRAM-Config failure following the second power-cycle after you use the write erase command if the write memory command has not be used between power-cycles.
This failure will occur only if you use the write erase command and the power-on diagnostics runs twice without the write memory command being used.
Workaround: After using the write erase command, use the write memory command before power cycling the switch.

Documentation Updates

An Update to the LightStream 1010 ATM Switch and Catalyst 8510 MSR Command Reference document was created to reflect information added after printing the manual.

Related Documentation

The following sections describe the documentation available for the Catalyst 8510 MSR. Typically, these documents consist of hardware installation guides, software installation guides, Cisco IOS configuration and command references, system error messages, and feature modules, which are updates to the Cisco IOS documentation. Documentation is available as printed manuals or electronic documents, except for feature modules, which are available online only.

The most up-to-date documentation can be found on the Web via Cisco Connection Online (CCO) and the Documentation CD-ROM. These electronic documents might contain updates and modifications made after the hard-copy documents were printed.

These release notes should be used in conjunction with the documents listed in these sections.

Platform Documents

Following is a list of the platform specific documentation available for the Catalyst 8510 MSR:

Software Documents

Following is a list of the software documentation available for the Catalyst 8510 MSR:

Service and Support

For service and support for a product purchased from a reseller, contact the reseller. Resellers offer a wide variety of Cisco service and support programs, which are described in the section "Service and Support" in the information packet that shipped with your product.

Note If you purchased your product from a reseller, you can access CCO as a guest. CCO is Cisco Systems' primary real-time support channel. Your reseller offers programs that include direct access to CCO services.

For service and support for a product purchased directly from Cisco, use CCO.

Software Configuration Tips on the Cisco TAC Home Page

For helpful tips on configuring Cisco products, follow this path on CCO:

Software & Support: Technical Tips (button on left margin)

"Hot Tips" are popular tips and hints gathered from Cisco's Technical Assistance Center (TAC). Most of these documents are also available from the TAC's Fax-on-Demand service. To access Fax-on-Demand and receive documents at your fax machine, call 888-50-CISCO (888-502-4726). From international areas, call 650-596-4408.

The following sections are provided from the Technical Tips page:

Cisco Connection Online

Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.

Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.

CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.

You can access CCO in the following ways:

For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.

Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com.

Documentation CD-ROM

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.

If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.





hometocprevnextglossaryfeedbacksearchhelp
Posted: Tue Sep 14 19:08:13 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.