|
|
Table Of Contents
Release Notes for Cisco ONS 15540 ESPx
for Cisco IOS Release 12.2(24)SV1Determining the Software Version
New Features in Release 12.2(24)SV
New Features in Release 12.2(23)SV
New Features in Release 12.2(22)SV
New Features in Release 12.2(18)SV2
New Features in Release 12.2(18)SV1
New Features in Release 12.2(18)SV
Resolved Caveats in Release 12.2(24)SV1
Open Caveats in Release 12.2(24)SV
Resolved Caveats in Release 12.2(24)SV
Resolved Caveats in Release 12.2(23)SV
Resolved Caveats in Release 12.2(22)SV
Resolved Caveats in Release 12.2(18)SV2
Resolved Caveats in Release 12.2(18)SV1
Resolved Caveats for Release 12.2(18)SV
Obtaining Technical Assistance
Obtaining Additional Publications and Information
Release Notes for Cisco ONS 15540 ESPx
for Cisco IOS Release 12.2(24)SV1
This document describes caveats for Cisco IOS Release 12.2(24)SV1 for the Cisco ONS 15540 ESPx.
Date: July 29, 2005
Text Part Number: OL-4893-06 E0
Contents
This document includes the following information:
•
Caveats
•
•
•
Introduction
The Cisco ONS 15540 ESPx is an optical transport platform that employs DWDM (dense wavelength division multiplexing) technology. With the Cisco ONS 15540 ESPx, users can take advantage of the availability of dark fiber to build a common infrastructure that supports data, SAN (storage area networking), and TDM (time-division multiplexing) traffic. The system uses an enhanced chassis with front fiber optic cable access for optical interconnections between transponder modules and optical mux/demux modules. For more information about DWDM technology and applications, refer to the Introduction to DWDM Technology publication and the Cisco ONS 15540 ESPx Planning Guide.
System Requirements
This section describes the system requirements for the Cisco ONS 15540 ESPx and includes the following sections:
•
Memory Requirements
The DRAM memory configuration is 128 MB, which is the default for the Cisco ONS 15540 ESPx.
Hardware Supported
Table 1 lists the hardware components supported on the Cisco ONS 15540 ESPx and the minimum software version required. See the "Determining the Software Version" section.
Determining the Software Version
Note
To determine the version of Cisco IOS software currently running on a Cisco ONS 15540 ESPx system, log in to the system and enter the show version EXEC command. The following sample output is from the show version command. The software version number is shown on the second line of the sample output.
Switch# show versionCisco Internetwork Operating System SoftwareIOS (tm) ONS-15540 Software (ONS15540-I-M), Version 12.2(24)SV <Information deleted>Upgrading the System Image
To ensure proper system functioning, follow the system image upgrading procedure described in the Cisco ONS 15540 ESPx Software Upgrade Guide.
Note
Caution
Feature Set Table
The Cisco IOS Release software is packaged in feature sets (also called software images) depending on the platform. Each feature set contains a specific set of Cisco IOS software features. Table 2 lists the Cisco IOS software feature sets available for the Cisco ONS 15540 ESPx.
This section lists new features that appear in this and previous releases of Cisco IOS Release 12.2. The new features are sorted by release number.
Table 2 Feature Sets Supported by the Cisco ONS 15540 ESPx
Gigabit Ethernet
12.1(10)EV
Fast Ethernet
12.1(10)EV
Ethernet
12.1(10)EV
ATM OC-3/STM-1, OC-12/STM-4, and OC-48/STM-16
12.1(10)EV
12.1(10)EV
POS3
12.1(10)EV
Fibre Channel (1 Gbps)
12.1(10)EV
Fibre Channel (2 Gbps)
12.1(10)EV
FDDI4
12.1(10)EV
ESCON5 SM (200 Mbps)
12.1(10)EV
FICON6 (800 Mbps)
12.1(10)EV
FICON (1 Gbps)
12.2(18)SV
Token Ring
12.1(10)EV
SNMP
12.1(10)EV
CiscoView
12.1(10)EV
Cisco Transport Manager
12.1(10)EV
CDP7
12.1(10)EV
IP packets
12.1(10)EV
OSCP8
12.1(10)EV
APS9 protocol packets
12.1(10)EV
Point-to-point
12.1(10)EV
Hubbed ring
12.1(10)EV
Meshed ring
12.1(10)EV
12.1(10)EV1
IBM GDPS 10 coupling link
12.1(10)EV1
Unidirectional path switching
12.1(10)EV
Bidirectional path switching
12.1(10)EV
CDL over 10 GE
12.1(10)EV2
2-Gbps Fibre Channel protocol monitoring on 2.5-Gbps transponder modules
12.2(18)SV
2-Gbps FICON protocol monitoring on 2.5-Gbps transponder modules
12.2(18)SV
Functional image version diagnostics
12.2(18)SV
2-Gbps ISC links peer mode protocol monitoring on 2.5-Gbps transponder modules
12.2(22)SV
1-Gbps ISC links peer mode protocol monitoring on 2.5-Gbps transponder modules
12.2(23)SV
SSHv1 client and server support
12.2(24)SV
SNMPv3 support
12.2(24)SV
Counter preservation on processor card switchovers
12.2(24)SV
1 SONET = Synchronous Optical Networking
2 SDH = Synchronous Digital Hierarchy
3 POS = Packet over SONET
4 FDDI = Fiber Distributed Data Interface
5 ESCON = Enterprise Systems Connection
6 FICON = Fiber Connection
7 CDP = Cisco Discovery Protocol
8 OSCP = Optical Supervisory Channel Protocol
9 APS = Automatic Protection Switching
10 GDPS = Geographically Dispersed Parallel Sysplex
11 ETR/CLO = external timer reference/control link oscillator
New and Changed Information
This section lists new features that appear in this and previous releases of Cisco IOS Release 12.2. The new features are sorted by release number.
New Features in Release 12.2(24)SV
The following new software features are available for the Cisco ONS 15540 ESPx in Cisco IOS Release 12.2(24)SV:
•
•
•
New Features in Release 12.2(23)SV
The following new software feature is available for the Cisco ONS 15540 ESPx in Cisco IOS Release 12.2(23)SV:
•
New Features in Release 12.2(22)SV
The following new software feature is available for the Cisco ONS 15540 ESPx in Cisco IOS Release 12.2(22)SV:
•
Note
release 1.A3 or later.New Features in Release 12.2(18)SV2
No new features are available for this release.
New Features in Release 12.2(18)SV1
No new features are available for this release.
New Features in Release 12.2(18)SV
The following new software features are available for the Cisco ONS 15540 ESPx in Cisco IOS Release 12.2(18)SV:
•
Note
release 1.A3 or later.•
Note
release 1.A3 or later.•
•
Caveats
This section describes open and resolved severity 1 and 2 caveats and certain severity 3 caveats. The "Open Caveats" section lists open caveats that apply to the current release and may apply to previous releases. The "Resolved Caveats" sections list caveats resolved in a particular release, but open in previous releases.
Resolved Caveats in Release 12.2(24)SV1
•
Cisco Internetwork Operating System (IOS) software is vulnerable to a Denial of Service (DoS) and potentially an arbitrary code execution attack from a specifically crafted IPv6 packet. The packet must be sent from a local network segment. Only devices that have been explicitly configured to process IPv6 traffic are affected. Upon successful exploitation, the device may reload or be open to further exploitation.
Cisco has made free software available to address this vulnerability for all affected customers.
More details can be found in the security advisory that is posted at http://www.cisco.com/warp/public/707/cisco-sa-20050729-ipv6.shtml.
Open Caveats in Release 12.2(24)SV
•
Symptom: The patch commands saved on the system are not compatible with CTM (Cisco Transport Manager).
Workaround: Remove the patch commands that show up out of order after the configuration is saved. Then, reset the active processor card or switch to the standby processor card and reenter the patch commands.
•
Symptom: In a point-to-point network with y-cable based APS configured, the protection path does not automatically come up if the working path is down.
Workaround: Configure a loopback on the client side to restore traffic to the protection path.
•
Symptom: The OSC wave interface goes into an invalid state when a PSM is placed in subslot 0 of a line card motherboard. Reloading a shelf with the PSM in subslot 0 causes the OSC wave interface to become inoperative.
Workaround: Install the PSM in subslots 1, 2, or 3 in line card motherboards where the OSC is in use.
•
Symptom: An informational warning is issued instead of a critical alarm when the transponder modules shut down in response to a multiple fan failure event after issuing the environment-monitor shutdown fan command.
Workaround: None.
•
Symptom: During normal operation, an outage may result when trying to connect through the console port. The console port issues error messages. These can be routine messages relating to loss of light on wave ports that were turned on. Interface alarm flapping may cause hardware watchdog timeout, failed to switchover to standby processor card.
Workaround: None
•
Symptom: The GE optical link fails to come up between two Catalyst 65xx 8-port GBIC modules through the Cisco ONS155xx transparent transponders when Forward Laser Control (FLC) is enabled on the system. The link fails to come up irrespective of the type of protection scheme.
Workaround: Use a 16-port GBIC module on the Catalyst 65xx or deactivate FLC on the ONS155xx.
•
Symptom: The GE optical link fails to come up between two Catalyst 65xx 8-port GBIC modules through the Cisco ONS15540 PSM DWDMs when forward laser control (FLC) is enabled.
Workaround: Use a 16-port GBIC module or disable FLC.
Resolved Caveats in Release 12.2(24)SV
•
Symptom: A warning is issued if the card has an unknown functional image. Version compatibility checks need to be performed during system initialization. The hardware version compatibility should identify any mismatch between functional image versions and hardware versions. The software version compatibility should identify any mismatch between FPGA image and software image.
Workaround: None
•
Symptom: If the transparent interface on a multimode transponder module is configured for Sysplex ETR traffic (encap sysplex etr command), the show interfaces transparent command output shows that forward laser control is set to off. Forward laser control is automatically enabled for Sysplex ETR.
Workaround: Add client input traffic and the trunk side laser will function.
•
Symptom: The Prot Switch Byte Failure - In Effect alarm message appears on the console.
Workaround: None.
•
Symptom: The show redundancy command is not valid on specific versions of the Cisco ONS 15530 software but the choice still exists.
Workaround: Use the show redundancy summary command.
•
Certain release trains of Cisco Internetwork Operating System (IOS), when configured to use the Cisco IOS Secure Shell (SSH) server as a means to perform remote management tasks on Cisco IOS devices, may contain two vulnerabilities that can potentially cause Cisco IOS devices to exhaust resources and reload. Repeated exploitation of these vulnerabilities can result in a Denial of Service (DoS) condition. Use of SSH with Remote Authentication Dial In User Service (RADIUS) is not affected by these vulnerabilities.
Cisco has made free software available to address these vulnerabilities for all affected customers. There are workarounds available to mitigate the effects of the vulnerability (see the "Workarounds" section of the full advisory for details.)
This advisory will be posted at http://www.cisco.com/warp/public/707/cisco-sa-20050406-ssh.shtml.
•
Certain release trains of Cisco Internetwork Operating System (IOS), when configured to use the Cisco IOS Secure Shell (SSH) server as a means to perform remote management tasks on Cisco IOS devices, may contain two vulnerabilities that can potentially cause Cisco IOS devices to exhaust resources and reload. Repeated exploitation of these vulnerabilities can result in a Denial of Service (DoS) condition. Use of SSH with Remote Authentication Dial In User Service (RADIUS) is not affected by these vulnerabilities.
Cisco has made free software available to address these vulnerabilities for all affected customers. There are workarounds available to mitigate the effects of the vulnerability (see the "Workarounds" section of the full advisory for details.)
This advisory will be posted at http://www.cisco.com/warp/public/707/cisco-sa-20050406-ssh.shtml.
•
A document that describes how the Internet Control Message Protocol (ICMP) could be used to perform a number of Denial of Service (DoS) attacks against the Transmission Control Protocol (TCP) has been made publicly available. This document has been published through the Internet Engineering Task Force (IETF) Internet Draft process, and is entitled "ICMP Attacks Against TCP" (draft-gont-tcpm-icmp-attacks-03.txt).
These attacks, which only affect sessions terminating or originating on a device itself, can be of three types:
1. Attacks that use ICMP "hard" error messages
2. Attacks that use ICMP "fragmentation needed and Don't Fragment (DF) bit set" messages, also known as Path Maximum Transmission Unit Discovery (PMTUD) attacks
3. Attacks that use ICMP "source quench" messagesSuccessful attacks may cause connection resets or reduction of throughput in existing connections, depending on the attack type.
Multiple Cisco products are affected by the attacks described in this Internet draft.
Cisco has made free software available to address these vulnerabilities. In some cases there are workarounds available to mitigate the effects of the vulnerability.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20050412-icmp.shtml.
The disclosure of these vulnerabilities is being coordinated by the National Infrastructure Security Coordination Centre (NISCC), based in the United Kingdom. NISCC is working with multiple vendors whose products are potentially affected. Its posting can be found at: http://www.niscc.gov.uk/niscc/docs/re-20050412-00303.pdf?lang=en.
•
Symptom: Cisco IOS® devices running branches of Cisco IOS version 12.2S that have Dynamic Host Configuration Protocol (DHCP) server or relay agent enabled, even if not configured, are vulnerable to a denial of service where the input queue becomes blocked when receiving specifically crafted DHCP packets. Cisco is providing free fixed software to address this issue. There are also workarounds to mitigate this vulnerability. This issue was introduced by the fix included in CSCdx46180 and is being tracked by Cisco Bug ID CSCee50294.
This advisory is available at
http://www.cisco.com/warp/public/707/cisco-sa-20041110-dhcp.shtml .
Workaround: None.
•
Symptom: A receive failure might display a message that the laser if shut due to forward laser control.
Workaround: None.
Resolved Caveats in Release 12.2(23)SV
•
Symptom: DWDM links set at a 196.608-Mbps rate, or an uncommon rate close to this, may not work properly on the 2.5-Gbps transponder module. Link initialization failures and bit errors may occur.
Workaround: None.
•
Symptom: APS behavior for the aps clear command is inconsistent with the standard behavior if the following conditions occur:
–
–
Workaround: None.
•
Symptom: The IDPROM values from the high band single-mode SFPs are not readable. The SFPs cannot be configured and cannot be used.
Workaround: None.
•
Symptom: In a splitter configuration with 10-GE transponder modules, switchover eventually fails if continuous back and forth switchovers are performed from working to protection.
Workaround: None.
Resolved Caveats in Release 12.2(22)SV
•
Symptom: The OSC wave interface does not come back up after resolving a trunk fiber break if laser safety control was configured after the trunk fiber break occurred.
Workaround: None.
Resolution: Upgrade the 15540 mux/demux motherboard functional image to release 2.67 or later.
•
Symptom: A y-cable APS bidirectional switchover caused by a trunk Rx failure takes as long as 10 seconds in a configuration with 10-GE transponder modules.
Workaround: None.
•
Symptom: Tracebacks related to processor hog issues are seen when reprogramming the functional image for a 2.5-Gbps transponder module.
Workaround: None.
•
Symptom: If monitoring is disabled, Loss of Light on the local transparent interface results in Loss of Sync on the far side wave interface.
Workaround: Enable monitoring on the transparent interface.
•
Symptom: After configuring a patch between a wavepatch interface and a wdmrelay interface, issuing a show connect intermediate command results in spurious memory access.
Workaround: Do not issue the show connect intermediate command when a patch between a wavepatch interface and a wdmrelay interface is configured.
•
Symptom: If a row is created in cApsChanConfigTable using createAndWait, a set operation on an instance of cApsChanConfigIfIndex might modify another instance of that object.
Workaround: Use createAndGo to create the row.
•
Symptom: An APS switchover from a working interface to a protect interface might not occur for10-GE transponder modules.
This symptom occurs with the following configurations:
–
–
–
•
Symptom: If a one-way patch configuration is removed between a thru interface and a wdm interface, the system hangs for a long time and eventually crashes.
Workaround: Configure two-way patches between the thru and wdm interfaces.
Resolved Caveats in Release 12.2(18)SV2
•
Symptom: In some instances the system crashes when it attempts to parse IP SNMP related commands.
Workaround: None.
•
Symptom: Bidirectional APS fails when the ethernetdcc interface is used as a message channel for trunk based protection if the PSM is connected directly to a wavepatch interface on a transponder module rather than to the wdm interface on a mux/demux module.
Workaround: None.
•
Symptom: Link initialization failure due to Loss of Lock might occur for ESCON traffic on some transponder modules due to a transient failure of the clock recovery unit. Only some transponder modules are susceptible to this failure and not all. This is an initialization failure and not a run-time failure.
Workaround: None.
•
Symptom: The input power level to the wavepatch x/y/1 interface on a 10-GE transponder module falls below the configured optical threshold but the alarm is not raised. The alarm works correctly for wavepatch x/y/0.
Workaround: None.
Resolved Caveats in Release 12.2(18)SV1
•
Symptom: Performing an online removal and insertion on a tengigethernetphy interface or waveethernetphy interface when loopback is configured causes a loss of the loopback information on the hardware. However, the loopback CLI configuration is still present in the software.
Workaround: Remove and reinsert the module, and then issue the loopback command to manually configure loopback.
•
Symptom: Issuing a Ctrl-U when connected to a raw TL1 port causes the system to crash.
Workaround: If a TL1 port is unused, apply an IP ACL to the management Ethernet interface that blocks the incoming TCP connections to that port.
Resolved Caveats for Release 12.2(18)SV
•
A Cisco device running Cisco IOS software and enabled for the Border Gateway Protocol (BGP) is vulnerable to a Denial of Service (DOS) attack from a malformed BGP packet. The BGP is not enabled by default, and must be configured to accept traffic from an explicitly defined peer. Unless the malicious traffic appears to be sourced from a configured, trusted peer, it would be difficult to inject a malformed packet. BGP MD5 is a valid workaround for this problem.
Cisco has made free software available to address this problem. For more details, refer to this advisory, available at http://www.cisco.com/warp/public/707/cisco-sa-20040616-bgp.shtml.
•
A Cisco device running Cisco IOS software and enabled for the Border Gateway Protocol (BGP) is vulnerable to a Denial of Service (DOS) attack from a malformed BGP packet. The BGP is not enabled by default, and must be configured to accept traffic from an explicitly defined peer. Unless the malicious traffic appears to be sourced from a configured, trusted peer, it would be difficult to inject a malformed packet. BGP MD5 is a valid workaround for this problem.
Cisco has made free software available to address this problem. For more details, refer to this advisory, available at http://www.cisco.com/warp/public/707/cisco-sa-20040616-bgp.shtml.
•
Symptom: The system crashes when the user exits from the console after the active processor card has been removed and inserted online and is switched back to being the active processor card.
Workaround: None.
•
Symptom: Client Tx fault alarm is asserted when an SFP optics is inserted or upon a y-cable switchover.
Workaround: Upgrade to Cisco IOS Release 12.1(12c)EV3 and transponder functional image version 1.A2 or higher.
•
Symptom: In a point-to-point network topology setup where bidirectional PSM trunk fiber protection APS is configured, and the CDL (Converged Data Link) is configured for dcc and the controller type of the mux/demux module is 0x1104 (4-channel mux/demux module without OSC), APS cannot track a valid ethernetdcc interface. Therefore the group cannot be associated.
Workaround: Do not configure CDL as dcc for PSM APS if the corresponding mux/demux module does not have OSC ports (controller type 0x1104).
•
Symptom: Continuous optical performance monitoring alarms cause memory leaks that lead to bus error exceptions and an unexpected reload.
Workaround: None.
•
Symptom: When you enter the send break command on the active processor and keep the active processor in the ROM monitor (ROMMON) mode for a long time, the standby processor may reload because of a bus error exception.
Workaround: None.
Limitations and Restrictions
This section provides limitations and restrictions for Cisco ONS 15540 ESPx hardware and software.
Transponder Modules
This section contains limitations and restrictions that apply to transponder modules.
•
•
Data errors or link-down conditions for 2-Gbps Fibre Channel might occur on single-mode transponder modules when used with certain client laser sources. Transmitters in some client GBIC and SFP transceiver units might send large overshoots in optical power with signal bit transitions, causing momentary overload conditions on the transponder module client side receiver. The average transmitted power level from the GBIC does not violate the overload specification of the transponder module client side receiver, so a power meter does not detect the overload.
The workaround is to attenuate the signal from the client equipment to a recommended level of -12 dBm when transmitting 2-Gbps Fibre Channel services.
•
Related Documentation
Refer to the following documents for more information about the Cisco ONS 15540 ESPx:
•
•
•
•
•
•
•
•
•
•
•
•
•
Obtaining Documentation
Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
Cisco.com
You can access the most current Cisco documentation on the World Wide Web at this URL:
http://www.cisco.com/univercd/home/home.htm
You can access the Cisco website at this URL:
International Cisco websites can be accessed from this URL:
http://www.cisco.com/public/countries_languages.shtml
Ordering Documentation
You can find instructions for ordering documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
You can order Cisco documentation in these ways:
•
http://www.cisco.com/en/US/partner/ordering/index.shtml
•
Documentation Feedback
You can submit e-mail comments about technical documentation to bug-doc@cisco.com.
You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Obtaining Technical Assistance
For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, the Cisco Technical Assistance Center (TAC) provides 24-hour-a-day, award-winning technical support services, online and over the phone. Cisco.com features the Cisco TAC website as an online starting point for technical assistance. If you do not hold a valid Cisco service contract, please contact your reseller.
Cisco TAC Website
The Cisco TAC website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The Cisco TAC website is available 24 hours a day, 365 days a year. The Cisco TAC website is located at this URL:
Accessing all the tools on the Cisco TAC website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a login ID or password, register at this URL:
http://tools.cisco.com/RPF/register/register.do
Opening a TAC Case
Using the online TAC Case Open Tool is the fastest way to open P3 and P4 cases. (P3 and P4 cases are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Case Open Tool automatically recommends resources for an immediate solution. If your issue is not resolved using the recommended resources, your case will be assigned to a Cisco TAC engineer. The online TAC Case Open Tool is located at this URL:
http://www.cisco.com/tac/caseopen
For P1 or P2 cases (P1 and P2 cases are those in which your production network is down or severely degraded) or if you do not have Internet access, contact Cisco TAC by telephone. Cisco TAC engineers are assigned immediately to P1 and P2 cases to help keep your business operations running smoothly.
To open a case by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447For a complete listing of Cisco TAC contacts, go to this URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
TAC Case Priority Definitions
To ensure that all cases are reported in a standard format, Cisco has established case priority definitions.
Priority 1 (P1)—Your network is "down" or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Priority 2 (P2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Priority 3 (P3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Priority 4 (P4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•
http://www.cisco.com/go/marketplace/
•
http://cisco.com/univercd/cc/td/doc/pcat/
•
•
•
http://www.cisco.com/go/iqmagazine
•
•
http://www.cisco.com/en/US/learning/index.html
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
CCSP, CCVP, the Cisco Square Bridge logo, Follow Me Browsing, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Access Registrar, Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, StrataView Plus, TeleRouter, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0502R)
Copyright © 2003-2005 Cisco Systems, Inc. All rights reserved.
Posted: Fri Jul 29 23:03:52 PDT 2005
All contents are Copyright © 1992--2005 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
