|
|
LightStream 1010 ATM Cisco IOS Release 12.0(11)
Text Product Number 78-6254-10
This document describes the features and caveats for Cisco IOS Release 12.0(11) for the LightStream 1010 ATM switch software. This software is based on Cisco IOS Release 12.0(10).
This document includes the following sections:
The LightStream 1010 ATM switch 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. |
Table 1 lists the release names, versions, and part numbers used with the LightStream 1010 ATM switch.
This section describes the system requirements for Release 12.0(11) and includes the following sections:
The standard default DRAM memory for the LightStream 1010 ATM switch is 64-MB DRAM (MEM-ASP64M).
Table 2 lists the interfaces supported on the LightStream 1010 ATM switch release 12.0(11), and their minimum software requirements.
| Part Number | Description | Minimum Software Requirement |
|---|---|---|
4-port T1 (circuit emulation) with RJ-48 interface port adapters |
||
4-port E1 (circuit emulation) with RJ-48 interface port adapters |
||
4-port E1 (circuit emulation) with BNC interface port adapters |
||
ASP1 with FC-per-flow Queuing (FC-PFQ3) |
||
| 1ASP = ATM switch processor
2FC-PCQ = feature card per-class queueing 3FC-PFQ = feature card per-flow queueing |
To determine the version of Cisco IOS software currently running on the LightStream 1010 ATM switch, log in to the switch and use the show version EXEC command. The second line in the following sample output from the show version command indicates the version number:
Additional command output lines include more information, such as processor revision numbers, memory amounts, hardware IDs, and partition information.
The Cisco IOS software is packaged in feature sets, or software images, that vary according to the platform. Table 3 lists the Cisco IOS software feature sets available for the LightStream 1010 ATM switch in Cisco IOS Release 12.0(11), along with those features supported in previous releases.
| 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 |
This section contains information about new features that appear in this and previous releases of Cisco IOS Release 12.0 and 11.3.
|
Note See Table 3 for a complete list of features supported by this and previous releases. |
There are no new features in these releases.
The following features have been added to the LightStream 1010 ATM switch software:
This section lists the caveats and corrected caveats for each release. Use Table 4 to determine the status of a particular caveat and its relevancy to your software release. In the table, "Y" indicates a fixed caveat, and "N" indicates an open caveat.
| DDTS Number | 12.0(11) | 12.0(10) | 12.0(9) | 12.0(8) | 12.0(7) | 12.0(6) | 12.0(5) | 12.0(4) | 12.0(2a) | 11.3(3a) WA4(6) |
|---|---|---|---|---|---|---|---|---|---|---|
Symptom: SVC setups fail even when physical connectivity is established.
Workaround: Reload the switch.
Symptom: A bus error exception might occur when adding parties to a root connection.
Symptom: The system will ignore the incoming SSCOP pdu status messages from another system and automatically reset the session after the timers expire.
Symptom: The LightStream 1010 sometimes runs out of shared memory when running LES/BUS services at a high data rate.
Workaround: Move LES/BUS to a platform that is more suitable for this service. Recommended platform is Catalyst 5000 LANE.
Symptom: When resetting a connection to an endstation, the system might crash if using
the static map command.
Symptom: OAM F5 Loopback cells not passing across ATM 25 Mbps port adapter.
Workaround: Enter the no atm oam intercept end-to-end command in global command mode.
Symptom: When using third party equipment and trying to se tup VBR-nrt across UNI 4.0/PNNI interfaces, it might result in an unsupported combination of traffic parameters.
Symptom: Multiple tags for default route with VC merge.
Workaround: Do not assign tags to the default route.
Symptom: VP-associated code point not supported on UNI 4.0.
Symptom: New SVC or sof- PVC calls from a LightStream 1010 ATM switch to a Fore ATM switch across a PNNI interface fail to connect. Connections initiated from the Fore switch do not fail.
Symptom: In software versions 12.0 and greater, the SNMP might fail to show trace using the
VC trace application. This is caused by an incorrect cross identifier return for VCs 0/5 and 0/16.
Symptom: When hundreds of TVCs in bidirectional mode are repeatedly configured and unconfigured in a switch, VC resources might be exhausted.
Symptom: Only 99 percent of the CPU might be available when an ATM-25 is connected to ports 1 to 3 on the 4-port ATM-25 module or ports 1 to 5 and 7 to 11 on the 12-port ATM-25 module.
Symptom: The vc-merge command, activated by default, does not work with 11.3 code. Large amounts of CRCs appear when the vc-merge command is activated.
Symptom: When a call is made over a VP tunnel, the Connection ID information element incorrectly sets the VP bits of all links to 00 (associated signaling). This setting might cause link failures outside the VP tunnel.
Symptom: ILMI keepalives might incorrectly reset the interface on the second retry of a link failure.
Symptom: In some cases constant bit rate VCs get stuck because of excessive errors.
Symptom: After reloading the system, OC-3c and OC-12c connections come up without a problem. When a new module is inserted after the reload, the system recognizes the module. The modules appear in the output from the show hardware command and the show running config command; however, none of the ports send out any information. The input cell count increments, but the output cell count does not.
Symptom: Soft VCs showing incorrect soft VCLs and SVCLs might not connect to certain ports.
Symptom: An interface snoop configuration might crash an FC1 system.
Symptom: Systems with the FC1 card installed might crash intermittently during boot.
Symptom: Systems with customer equipment that require a PVP value of 0 might cause the PVP tunnel to fail on the LightStream 1010 side of the network.
Workaround: Change the PVP value to a non-zero number.
Symptom: If the show atm vc interface command results in a status of NO HW RESOURCE for the interface, a failure might occur in mmc_close_conn.
Symptom: In certain instances SSCOP might ask the remote site to resynchronize its values so that both sides agree on the current status of these values. This request is likely in a redundant hardware failover. The system recognizes the request, but sends back a response message with a UNI 3.0 format rather than a UNI 3.1 format so the remote side cannot recognize the response.
Symptom: When issuing the show debug command on a system which is a PNNI childless uncle, an infinite loop within the pnni_debug_show command might trigger a watchdog timeout.
Symptom: When forwarding a call setup from one VP tunnel to another, dropped information elements which are mandatory when using associated signaling might cause compatibility problems with third-party equipment.
Symptom: Tag switching on the atm trunk works, but if the same link becomes a part of the inverse multiplexing for ATM (IMA) group, tag switching might not work as expected.
Symptom: The PVC Discovery feature on a router that is connected to an ATM interface might fail to discover all the configured PVCs and soft PVCs coming from the interface. This condition occurs only when soft PVCs are present on the configuration.
Symptom: While sending heavy traffic bidirectionally, the modem might go into ring buffer overflow.
Symptom: When data is being converted from bits per second to cells per second, numbers might be rounded down when they should be rounded up.
Symptom: A system running Cisco IOS Release 11.3(5)WA4(5) or WA5(5) might report the following error message:
This message occurs when the system receives an LLC2 broadcast on a LANE subinterface. In some cases, the system crashes after reporting this error message.
Workaround: Use a separate management ELAN or use a built-in Ethernet port to manage the switch.
Symptom: The circuit emulation service might display an interface as up when it is experiencing Loss of Signal (LOS). In addition, alarm indication signals (AIS) might not be generated during the shutdown.
Symptom: When using a 25-Mbps port adapter, the number of leaves in a point-to-multipoint connection cannot exceed 32.
Symptom: PVCs that are terminating on a CPU port over point-to-point subinterfaces might not be accepted.
Workaround: Use multipoint subinterfaces.
Symptom: CES E1 PAM might fail to stop sending REMAIS yellow alarms when OOF appears for a short period.
Symptom: The system issues an acctngFileFull message every 10 seconds if the snmp-server enable trap atm statement is configured.
Workaround: Remove this statement or command from the configuration.
Symptom: The TR-LEC might incorrectly process all registration requests received on its control distribute VC. When working correctly, it processes registration requests only when the LAN emulation client identifier (LECID) in the registration message matches up with its own LECID.
Symptom: When running tag switching, no tag is created for the default route.
Symptom: When using the atm pnni node node command, the peer group leader election (PGLE) might stay in the hung state for a long time.
Symptom: When soft VPs are being created, the VPI value allocated on the switched part of the soft VP path might collide with an existing configured PVP.
Workaround: To get the soft VP back up, either remove the PVP or create a PVP using the same VPI value that is on the peer switch.
Symptom: The system might crash with a bus error exception when attempting the atm ping command on a VC if the VC has been removed through a link failure.
Symptom: A PNNI process is terminated when the associated node is either disabled or removed. Following process termination, PNNI might not clean up and release some of its data structures properly. As a result of not freeing the data structures, the associated memory is lost until the next reload.
Workaround: Reload the system.
Symptom: The SNMP agent might not be able to discover and allow PNNI-related configurations on ATM subinterfaces. An alignment error message is printed when an SNMP walk (or other SNMP get next) request is issued.
Symptom: Connections where end-to-end delay IE is included in the CONNECT message might fail. Examples of these connections include UNI 40, CBR, and UBR-rt.
A LightStream 1010 ATM switch that is an intermediate switch passes a bad CONNECT message from one side to the other. The CONNECT message shows up as a CONNECT packet that is longer than the actual contents, with junk bytes at the end.
Symptom: Due to an infinite loop, a LightStream 1010 ATM switch with eight LAN emulation clients configured on the CPU and 300 point-to-point and 60 point-to-multipoint connections might crash unexpectedly at the find-buddy function.
Symptom: After hot swapping an OC-12 SM port adapter with an OC-12 MM port adapter, the output of the show controller command might incorrectly show the module as OC-12 SM. The module itself works.
Symptom: CES: per-VC queues might fill with cells on 64 Kbps circuits.
With standard CES 64 Kbps circuits, the per-VC queues build up with cells at a rate of about one per second. There is a mismatch between the cell-rate requested and the rate granted. This is caused by signaling a pcr of 170 cells per second, rather than the desired 172 cells per second. Because the CBR FC-PFQ traffic shaping in current software has excellent granularity, roughly a cell every two seconds is queued. After the queue fills, dropping occurs at that rate.
Symptom: Disabling tag switching on an interface that carries tagged VCs (TVCs) might not remove the TVCs. Reenabling tag switching on that interface puts it in the "not TDP ready" state.
Symptom: CES interfaces might not come up upon reload.
The line state stays at XmtAIS LossOfSignal. Sometimes the switch comes up, but the IF status of show ces int command always shows as DOWN and the line state is RcvAIS XmtAIS.
Symptom: Crash with software release 11-3-3aWA4-6.
Data flowing over OC-12 links between two LightStream 1010 ATM switches might cause memory corruption and the software release 11-3-3aWA4-6 might crash. This crash might be caused by badly formed AAL5 packets.
Workaround: Reboot the switch.
Symptom: The snmp get command does not work for the following MIB variables:
Symptom: The power-on diagnostic test might indicate snake-test failures from the ASP-PFQ.
If the snake test fails or the switch is not reset, the red LED on the left side of the processor remains lit. Changing out power supplies and processors does not correct this problem. Consequently, no evidence exists that this alarm indicates a failed processor.
Symptom: Crash in process_handle_watchdog might occur.
This problem is caused by a routing loop, which is caused by metric overflow in metric aggregation.
Symptom: The PNNI agent returns a value of lowestLevelOutsideLink(4) for links between nodes on the same peer group for the pnniLinkType object. The correct value is lowestLevelHorizontalLink(2).
Symptom: PNNI: There might be a crash at compare_avl_nodes.
When using the pnni_election command with a freed pnni_pdb where there are two scripts running pnni commands from different threads, the CLI command creates the pnni node and passes the pnni_pdb in the csb to be processed by the next issued command. In the meantime, SNMP deletes the node from under CLI.
Symptom: After manually configuring all the prefix and ESI addresses for LECS/LES/BUS and clients for all devices on the network and upgrading from 11.2(8.0.1) FWA4(1) to 11.3(3a)WA4.6, the LANE client on the system might not join.
Workaround: Remove the manually configured address; the LANE client comes right up.
Symptom: ADD Party over Tunnel might not work.
On a source node, if you are adding a subsequent leaf to a VP tunnel that is out of bandwidth, PNNI might reject the route request (for the leaf) leading to an eventual rejection of the ADD party by signaling.
Symptom: Left-justified AESA feature can cause the system to crash when enabling and disabling a node with 3000 e164/f69/X121 addresses.
Symptom: The ATM switch might crash if you remove a snooped subinterface by entering the no interface command and then entering the show atm snoop-vc command on the snoop interface.
Symptom: When a LEC/LES/BUS are all on the same switch, a point-to-multipoint connection exists with the CPU as root and with several leaves on the CPU. When the LES sends a packet to all leaves, one packet needs to loop back to the CPU for the LEC. The code that performs loopback initializes hwidb->atm_db->fast_vc_info for the LANE client and eventually calls atm_input to queue the packet. However, another packet could come in on the same CPU port (for example, PNNI). This situation would cause hwidb->atm_db->fast_vc_info to be overwritten because hwidb is shared. When interrupt handling is complete for the new packet, the old packet might be misinterpreted as a totally different kind of packet.
Symptom: When snoop-vc is configured on a port, a switch might give the following internal error message:
The message can be ignored, it does not affect the snooping functionality.
Workaround: Ignore the message. It does not affect the snooping functionality.
Symptom: Per VC Snooping is unconfigurable or broken.
Symptom: When a large amount of data is sent out of the Ethernet interface, the interface might become inundated and start generating the error message:
%SONICT-3-INTERNAL_ERROR: sonic_send: no free tbufs
The interface stops sending data and the transmitter remains stuck until the shut/no shut command sequence is issued on the interface.
Workaround: Issue the shut/no shut command sequence on the interface.
Symptom: One soft VC might not come up because the resources at the destination switch are not available. After retrying the soft VC several times, the system might crash because of memory corruption.
Symptom: You cannot use SNMP to create a soft PVC on the ATM switch.
Symptom: A ring-back tone cannot be heard from the other side of a PBX when on-hook-detect is set.
Symptom: When using more than 13 time slots with cas on-hook, the voice CBR connections might be unstable. Without on-hook-detect configuration, all CBR VCs will be stable.
Symptom: ILMI might not come up upon reload of vp-mux (vuni).
ILMI on the tunnel interface (connected to the far-end peer device through a vp-mux switch and virtual UNI) has trouble staying in "WaitDevType" after reloading the vp-mux switch.
Workaround: Shut down the tunnel interface; disable the ILMI followed by the no shut command on the tunnel interface. After the interface settles down, the ILMI on the tunnel can be reenabled. Shut the interface. Use the atm ilmi-enable command and atm auto-configuration command (if desired), then reenable the tunnel interface with the no shut command.
Symptom: Some LANE clients cannot join an ELAN.
The show lane command indicates that some LANE clients (still in init state as far as the LANE client router is concerned) appear in the LECS table with no information.
The show atm vc interface command indicates that some SVCs are not connected.
If the LANE clients try to join the ELAN, they are rejected.
Symptom: Funnel VCs might jeopardize quality of service (QoS) of guaranteed services.
The current multipoint-to-point funnel implementation might 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: A LightStream 1010 switch installed in the Catalyst 5500 chassis might fail to boot up when using mixed power supplies at high temperatures.
When using power supplies from different vendors on the Catalyst 5500 chassis, make sure that the supplies are powered-up in serial order. If you power up the power supplies simultaneously, the processor on the LightStream 1010 ATM switch might not come out of reset. For example, the processor might hang and not boot.
Symptom: PNNI support of left-justified E.164 AESA addresses is not available in Cisco IOS Release 11.3 (0.8)TWA4(2).
Symptom: Unless it is administratively shut down, the CBR interface on the CES port adapter is always in the up/up state, even when no cable is attached. If the CBR line goes down, the interface stays up/up, and the only error reported is Linestate: LossOfSignal.
Symptom: When the ROM monitor environment variable boot is set to a nonexistent file (using the Cisco IOS boot system flash command) and the configuration register is set to 0x2102 (autoboot), the switch might hang 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: A CES PVC cannot be cross connected to a VP tunnel interface.
Symptom: When hot swapping cards immediately after turning off the interrupts, the system might crash. The crash occurs because the interrupts are disabled and the hot swapping is not seen until the command issue is complete.
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 might 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 DDTs for information on how to convert a requested rate to the actual rate.
Symptom: There is a small divergence in the measured output of the shaped VP tunnels at rates of 90 Mbps and above.
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 the clear ip route command on the switch on the interface that was shutdown, or the 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 the shut/no shut command on the UNI interfaces of the switch on which the physical interface was shut to bring everything back up.
Symptom: The CPU HOG condition might occur while setting up a lot of calls.
Symptom: IP host-routing might not disable when specified.
Workaround: Enable and disable ip routing and then save the configuration to NVRAM.
Symptom: Shutting down an interface with more than 1000 tag switching VCs might cause a CPU HOG occurrence for the EXEC process. The CPU HOG occurrence does not impact the functionality of the ATM switch.
Symptom: Under some rare conditions (not yet identified), some ports might get stuck in the WaitDevType state.
Workaround: Reboot the switch.
Symptom: The ATM switch does not currently support maxvc-number negotiation through ILMI.
Symptom: The following error might occur after copying the running configuration to a TFTP server and then trying to unconfigure all of the interface addresses:
Symptom: If there are multiple parallel paths to the same destination on a LightStream 1010 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 four 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.
Symptom: The system does not support CUGs on soft PVC connections. For example, if you define a set of access policies and a CUG on an interface with the PVC leg of a soft PVC call, the CUG parameters do not apply to those calls.
Symptom: In a LightStream 1010 ATM switch equipped with an FC-PFQ, the maximum number of cells available for use is 64,511. The number of cells in the switch fabric is 65,535.
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.
Symptom: The fail over time for the circuit emulation switch (CES) soft VC on a redundant link might be inconsistent, from less than 1 second up to 15 seconds.
Symptom: Cell loss might occur while hot swapping a power supply.
Symptom: SNMP support of the ciscoAtmIfPhysEntryData table and LED information is not available on the 25-MB port adapter.
Symptom: Supporting ABR VP tunnels requires interaction between VP flow-control and VC marking that neither FC-PCQ nor FC-PFQ hardware can perform. Because of this, the configuration of an ABR VP tunnel subinterface is prevented.
Symptom: The cell count reported on a snooped interface is twice the actual number of cells transmitted.
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 (by way of 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.
Symptom: If you disable Cisco Discovery Protocol (CDP) on the 2/0/0.x interface and it is configured as a LEC, the information is not saved to NVRAM when you enter the copy running-config startup-config command. CDP is disabled in the running configuration, but it is reenabled after a system reload.
Symptom: The call attempt counters for PortSelectGroups might not count the outgoing calls on its NNI interfaces because of switch crankback attempts. This might cause 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.
Symptom: When one of the installed power supplies is powered off, and you are copying an image to bootflash, a power supply failure message might appear.
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:
VBR: sustained cell rate (SCR) + sustained-cell-rate-margin-factor x (PCR - SCR).
ABR, UBR: no bandwidth is allocated.
Symptom: A Lan Emulation Configuration Server (LECS), using Cisco IOS Version 11.2(X), expects all LESs to establish an individual control VC to the LECS 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:
The clients are still allowed to join the ELAN. Disregard the warning message.
Symptom: When a large number of LANE clients come up and down constantly over extended periods of time, the system might 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: The receiver circuitry on DS3 port adapters might 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 LED lights up.
Symptom: Under very heavy traffic conditions the switch might experience temporary queue cell failures.
Workaround: This should clear after the traffic congestion clears.
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:
This message indicates that the release process runs for a long time before returning control to the kernel, which might then schedule other tasks. This process does not affect normal operation of the switch.
Symptom: E3 port adapters are limited to 65,535 cells per second per PVC regardless of the framing type. There is no benefit from G832 framing.
Symptom: When a fault condition occurs on an interface on an intermediate switch, Alarm Indication Signal (AIS) cells are generated. In response, the endpoint sends Remote Identification (RDI) cells. In some cases, these RDI cells are not propagated beyond the intermediate switch. The intermediate switch removes the connection leg entries for both interfaces participating in the connection when the 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.
The following sections describe documentation available for the LightStream 1010 ATM switch. Both printed manuals and electronic documents are available.
The most current documentation can be found on Cisco Connection Online (CCO) under the "Technical Assistance Center" section and on the Documentation CD-ROM. These electronic documents might contain updates and modifications made after the hard-copy documents were printed.
Use these release notes with the documents listed in this section.
Following is a list of the software documentation available for the LightStream 1010 ATM switch:
Following is a list of the hardware documentation available for the LightStream 1010 ATM switch:
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.
For helpful tips on configuring Cisco products, follow this path on CCO:
Service & Support: Technical Assistance Center
"Software Technical 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 556-8409.
In addition to "Software Technical Tips," the following sections are on the Technical Documents page:
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. |
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.
Posted: Thu Jan 23 21:14:42 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.