|
|
Table Of Contents
Release Notes for Cisco ONS 15540 ESP
for Cisco IOS Release 12.2(26)SVDetermining the Software Version
New Features in Release 12.2(26)SV
New Features in Release 12.2(25)SV
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
Open Caveats in Release 12.2(26)SV
Resolved Caveats in Release 12.2(26)SV
Resolved Caveats in Release 12.2(25)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
Cisco Technical Support Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Release Notes for Cisco ONS 15540 ESP
for Cisco IOS Release 12.2(26)SV
This document describes caveats for Cisco IOS Release 12.2(26)SV for the Cisco ONS 15540 ESP (Extended Services Platform).
Date: May 17, 2005
Text Part Number OL-4892-08
Contents
This document includes the following information:
•
Caveats
•
•
•
Introduction
The Cisco ONS 15540 ESP is an optical transport platform that employs DWDM (dense wavelength division multiplexing) technology. With the Cisco ONS 15540 ESP, 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. For more information about DWDM technology and applications, refer to the Introduction to DWDM Technology publication and the
Cisco ONS 15540 ESP Planning Guide.System Requirements
This section describes the system requirements for the Cisco ONS 15540 ESP and includes the following sections:
•
Memory Requirements
The DRAM memory configuration is 128 MB, which is the default for the Cisco ONS 15540 ESP.
Hardware Supported
Table 1 lists the hardware components supported on the Cisco ONS 15540 ESP 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 ESP 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(26)SV <Information deleted>Upgrading the System Image
To ensure proper system functioning, follow the system image upgrading procedure described in the Cisco ONS 15540 ESP 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 features. Table 2 lists the Cisco IOS software feature sets available for the Cisco ONS 15540 ESP.
Table 2 Feature Sets Supported by the Cisco ONS 15540 ESP
Gigabit Ethernet
12.1(7a)EY2
Fast Ethernet
12.1(7a)EY2
Ethernet
12.1(7a)EY2
ATM OC-3/STM-1, OC-12/STM-4, and OC-48/STM-16
12.1(7a)EY2
12.1(7a)EY2
POS3
12.1(7a)EY2
Coupling link
12.1(7a)EY2
Fibre Channel (1 Gbps)
12.1(7a)EY2
Fibre Channel (2 Gbps)
12.1(7a)EY2
FDDI4
12.1(7a)EY2
ESCON5 SM (200 Mbps)
12.1(7a)EY2
FICON6 (800 Mbps)
12.1(7a)EY2
FICON (1 Gbps)
12.1(12c)EV3
Token Ring
12.1(7a)EY2
SNMP
12.1(7a)EY2
CiscoView
12.1(7a)EY2
Cisco Transport Manager
12.1(7a)EY2
IP packets
12.1(7a)EY2
OSCP7
12.1(7a)EY2
APS8 protocol packets
12.1(7a)EY2
Point-to-point
12.1(7a)EY2
Hubbed ring
12.1(7a)EY2
Meshed ring
12.1(7a)EY2
12.1(7a)EY2
IBM GDPS 9 coupling link
12.1(7a)EY2
2-Gbps Fibre Channel protocol monitoring on transponder modules
12.2(18)SV
2-Gbps FICON protocol monitoring on 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 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 OSCP = Optical Supervisory Channel Protocol
8 APS = Automatic Protection Switching
9 GDPS = Geographically Dispersed Parallel Sysplex
10 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(26)SV
There are no new features for this release.
New Features in Release 12.2(25)SV
There are no new features for this release.
New Features in Release 12.2(24)SV
The following new software features are available for the Cisco ONS 15540 ESP 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 ESP 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 ESP 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 ESP 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.
Open Caveats in Release 12.2(26)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: Put a loopback on the client side to restore traffic to the protection path.
•
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 enabled. Interface alarm flapping may cause a hardware watchdog timeout that failed to switchover to the 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 Cisco ONS 15540 .
•
Symptom: The Cisco ONS 15540 might not allow you to connect to the standby processor card due to an authentication failure. This occurs when AAA or a local database is used for user authentication as this information (AAA or local database) is not replicated from the active to the standby processor card.
Workaround: None.
•
Symptom: During a processor card switchover, an extended range transponder might experience a temporary traffic interruption until the switchover is completed. The issue is intermittent and not all transponders in a given chassis may be affected. This interruption may potentially happen for the following types of protocol encapsulations:
–
–
–
–
–
–
Workaround: None.
•
Symptom: The system does not detect individual cards and requires a reboot to restart communication to the cards.
Workaround: None.
•
Symptoms: During a processor card switchover, an extended range transponder might experience a temporary traffic interruption may occur. When the switchover is complete, traffic resumes. This symptom is intermittent and may not affect all transponders in a chassis.
The traffic interruption may occur for the following types of encapsulation:
- ETR/CLO
- 100-Mbps Fast Ethernet / FDDI
- ESCON/SBCON
- 1-Gbps FC/FICON
- 1-Gbps ISC (ISC-1, ISC-3 peer mode, 1-Gbps)
- 2-Gbps FC/FICON
- 2-Gbps ISC (ISC-3 peer mode, 2 Gbps)
Workaround: None.
•
Symptom: A temporary traffic interruption in 2.5G transparent transponders during ONS 15540 and 15530 CPU switchover. This depends on the software versions of the Active CPU before and after the switchover.
Conditions: This can occur when switching from a CPU that is running on IOS software without the fix for CSCec64326, to a CPU running on IOS software with the fix for CSCec64326. The fix for CSCec64326 involves changes to hardware settings, causing the temporary datahit.
Workaround: None. The problem will be fixed in a future release of IOS software.
•
Symptom: The client Laser on the ten gig interface goes down for around 4 to 5 seconds, when the FLC is configured on the waveethernetphy interface and PSM APS switchover happens on an ONS 15540 setup with a combination of 10GE transponder and PSM APS.
Workaround: Disable FLC on Waveethernetphy interface.
Resolved Caveats in Release 12.2(26)SV
•
Symptom: When a CPU switchover is performed on an ONS 15540 or ONS 15530 system, the memory utilization on the new primary increases by 10MB. In such a case, the memory utilization may go up to 85%. This problem is seen only with 12.2 based images.
Workaround: None.
•
Symptom: In ONS 15530 and 15540 systems, the reading shown by the temperature sensor device attached to CPU cards may get stuck and do not change. Large differences between the temperature readings of the active and standby CPUs , or more than 10degree C difference between the readings of Inlet and Outlet sensors on the same CPU, are indicative of this stuck state on one or more sensors.
Condition: ONS 15530 and 15540 CPU cards manufactured upto March 2005 may have the older version sensor part and are potentially affected. Some cards produced before this affected date do have new sensor parts and are therefore not affected.
Date of manufacture of the CPU card can be displayed using the show hardware detail command from IOS.
For cards manufactured upto the fixed date, it is not possible to identify affected CPU boards based on version or serial number. It can only be checked by running a software utility (Please see resolution section below).
The failure is rarely found. The CPU temperature sensor may function normally after power up, and thereafter enter the stuck state at a later point during runtime.
Workaround: None. Removing and reinserting the CPU card or power-cycling the chassis may help recover from this error.
Resolution: This issue has been fixed in a later version of the temperature sensor device, and hence a CPU replacement is needed for a permanent fix. At this time the necessary logistics are being worked out to:
–
–
Impact: The command show environment will return incorrect temperature values. Minor, Major and Critical alarms that are based on temperature will not function.
•
Symptom: PSM APS switchover may rarely occur on an ONS 15540 system due to false low alarms reported for the wdmsplit interfaces.
Condition: This occurs rarely when spurious low alarms are seen for the PSM wdm split interfaces.
Workaround: None.
•
Symptom: Traffic is disrupted for one to two seconds on ONS 155xx transponders configured with Forward Laser Control, when a protection switchover occurs on a trunk Protection Switch Module (PSM). This exceeds the specification of 50ms maximum failover time for the optical transport layer.
Workaround: Disable FLC on trunk-to-client direction of transponder, if feasible for the service. This workaround does not apply for ISC, ETR or CLO services.
Resolution: This will be fixed in the future release of IOS software on ONS15530 and ONS15540, with a caveat that the following configuration will not be supported on the platform:
–
–
–
•
Symptom: On an ONS 15540/15530 system with Protection Switch Module, if a CPU switch occurs with the APS state such that protect interface is active and working interface is standby, then after the new CPU comes up there will be an extra APS switch to working. This is seen with all ONS15540 and ONS15530 software based on 12.1 and 12.2.
Workaround: None.
Resolved Caveats in Release 12.2(25)SV
•
Symptom: The optical link fails to come up between two 8-port GBIC modules through the ONS15540 PSM DWDMs when forward laser control (FLC) is enabled.
Workaround: Use a 16-port GBIC module or deactivate FLC.
•
Symptom: If a failed subcard is replaced by a new one, the show diag online output continues to indicate that there was a 'previous failure' for this subcard. This should have been cleared when the new card was inserted. This is specific to subcards, for motherboards the older failures are cleared when a new card is inserted.
Workaround: None.
•
Symptom: The system crashes when the functional image reprogramming is in progress for any of the line cards and the command show upgrade-information functional-image is issued at the same time through vty lines.
Workaround: None.
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 the functional 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 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.
•
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: 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 Cisco ONS 15540.
•
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: 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: 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.
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 Cisco ONS 15540 mux/demux motherboard functional image to release 2.67 or later.
•
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: 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: 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.
Resolved Caveats in Release 12.2(18)SV1
•
Symptom: Tracebacks related to processor hog issues are seen when reprogramming the 2.5-Gbps transponder module functional image.
Workaround: None.
•
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 to 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: Unable to disable APS group through SNMP. The console or Telnet session hangs indefinitely after configuration mode is entered using the SNMP set command.
Workaround: Do not disable the APS group through SNMP.
•
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 ESP 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 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 client side receiver. The average transmitted power level from the GBIC does not violate the overload specification of the transponder 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 ESP:
•
•
•
•
•
•
•
•
•
•
•
•
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 at this URL:
http://www.cisco.com/univercd/home/home.htm
You can access the Cisco website at this URL:
You can access international Cisco websites at 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 send 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, Cisco Technical Support provides 24-hour-a-day, award-winning technical assistance. The Cisco Technical Support Website on Cisco.com features extensive online support resources. In addition, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not hold a valid Cisco service contract, contact your reseller.
Cisco Technical Support Website
The Cisco Technical Support Website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, 365 days a year, at this URL:
http://www.cisco.com/techsupport
Access to all tools on the Cisco Technical Support Website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Note
Submitting a Service Request
Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco TAC engineer. The TAC Service Request Tool is located at this URL:
http://www.cisco.com/techsupport/servicerequest
For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco TAC engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.
To open a service request 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 list of Cisco TAC contacts, go to this URL:
http://www.cisco.com/techsupport/contacts
Definitions of Service Request Severity
To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.
Severity 1 (S1)—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.
Severity 2 (S2)—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.
Severity 3 (S3)—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.
Severity 4 (S4)—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, 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, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO 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. (0411R)
Copyright © 2003-2004 Cisco Systems, Inc. All rights reserved.
Posted: Mon Aug 8 01:12:15 PDT 2005
All contents are Copyright © 1992--2005 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
