Table Of Contents
Release Notes for the Cisco IE 3000 Switch, Cisco IOS Release 12.2(46)SE1 and later
Device Manager System Requirements
Finding the Software Version and Feature Set
Upgrading a Switch by Using the Device Manager or Network Assistant
Upgrading a Switch by Using the CLI
Recovering from a Software Failure
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(46)SE2
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(46)SE1
Updates to the Cisco IE 3000 Switch Software Configuration Guide and Command Reference
Updates to the Cisco IE 3000 Switch Getting Started Guide
Updates to the Regulatory Compliance and Safety Information for the Cisco IE 3000 Switch
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for the Cisco IE 3000 Switch, Cisco IOS Release 12.2(46)SE1 and later
Revised September 9, 2009
Cisco IOS Release 12.2(46)SE1 and later runs on all Cisco IE 3000 switches.
These release notes include important information about Cisco IOS Release 12.2(46)SE1 and later, and any limitations, restrictions, and caveats that apply to the releases. Verify that these release notes are correct for your switch:
•
If you are installing a new switch, see the Cisco IOS release label on the rear panel of your switch.
•
•
For the complete list of Cisco IE 3000 switch documentation, see the "Related Documentation" section.
You can download the switch software from this site (registered Cisco.com users with a login password):
http://www.cisco.com/public/sw-center/sw-lan.shtml
This software release is part of a special release of Cisco IOS software that is not released on the same 8-week maintenance cycle that is used for other platforms. As maintenance releases and future software releases become available, they will be posted to Cisco.com in the Cisco IOS software area.
Contents
This information is in the release notes:
•
•
System Requirements
The system requirements are described in these sections:
•
Hardware Supported
This section lists the hardware and SFP modules that the switch supports.
Switches and Modules
Table 1 lists the hardware supported on this release.
.
SFP Modules
These are the SFP modules that the switch supports:
.
Device Manager System Requirements
These sections describes the hardware and software requirements for using the device manager:
Hardware Requirements
Table 3 lists the minimum hardware requirements for running the device manager.
Table 3 Minimum Hardware Requirements
233 MHz minimum1
512 MB2
256
1024 x 768
Small
1 We recommend 1 GHz.
2 We recommend 1 GB DRAM.
Software Requirements
Table 4 lists the supported operating systems and browsers for using the device manager. The device manager verifies the browser version when starting a session to ensure that the browser is supported.
Note
Cluster Compatibility
You cannot create and manage switch clusters through the device manager. To create and manage switch clusters, use the command-line interface (CLI) or the Network Assistant application.
When creating a switch cluster or adding a switch to a cluster, follow these guidelines:
•
•
•
For additional information about clustering, see Getting Started with Cisco Network Assistant and Release Notes for Cisco Network Assistant (not orderable but available on Cisco.com), the software configuration guide, and the command reference.
CNA Compatibility
Cisco IOS 12.2(46)SE1 and later is only compatible with Cisco Network Assistant (CNA) 5.4 and later.
Note
You can download Cisco Network Assistant from this URL:
http://www.cisco.com/pcgi-bin/tablebuild.pl/NetworkAssistant
For more information about Cisco Network Assistant, see the Release Notes for Cisco Network Assistant on Cisco.com.
Upgrading the Switch Software
These are the procedures for downloading software. Before downloading software, read this section for important information:
•
•
•
•
Finding the Software Version and Feature Set
The Cisco IOS image is stored as a bin file in a directory that is named with the Cisco IOS release. A subdirectory contains the files needed for web management. The image is stored on the compact flash memory card.
You can use the show version privileged EXEC command to see the software version that is running on your switch. The second line of the display shows the version.
You can also use the dir filesystem: privileged EXEC command to see the directory names of other software images that you might have stored in flash memory.
Deciding Which Files to Use
The upgrade procedures in these release notes describe how to perform the upgrade by using a combined tar file. This file contains the Cisco IOS image file and the files needed for the embedded device manager. You must use the combined tar file to upgrade the switch through the device manager. To upgrade the switch through the command-line interface (CLI), use the tar file and the archive download-sw privileged EXEC command.
Table 5 lists the filenames for this software release.
Archiving Software Images
Before upgrading your switch software, make sure that you have archived copies of the current Cisco IOS release and the Cisco IOS release to which you are upgrading. You should keep these archived images until you have upgraded all devices in the network to the new Cisco IOS image and until you have verified that the new Cisco IOS image works properly in your network.
Cisco routinely removes old Cisco IOS versions from Cisco.com. See Product Bulletin 2863 for more information:
http://www.cisco.com/en/US/products/sw/iosswrel/ps5187/prod_bulletin0900aecd80281c0e.html
You can copy the bin software image file on the flash memory to the appropriate TFTP directory on a host by using the copy flash: tftp: privileged EXEC command.
Note
You can also configure the switch as a TFTP server to copy files from one switch to another without using an external TFTP server by using the tftp-server global configuration command. For more information about the tftp-server command, see the "Basic File Transfer Services Commands" section of the Cisco IOS Configuration Fundamentals Command Reference, Release 12.2 at this URL:
Upgrading a Switch by Using the Device Manager or Network Assistant
You can upgrade switch software by using the device manager or Network Assistant. For detailed instructions, click Help.
Note
Upgrading a Switch by Using the CLI
This procedure is for copying the combined tar file to the switch. You copy the file to the switch from a TFTP server and extract the files. You can download an image file and replace or keep the current image.
Note
To download software, follow these steps:
Step 1
Step 2
http://www.cisco.com/public/sw-center/sw-lan.shtml
To download the image for a Cisco IE 3000 switch, click Cisco IE 3000 software. To obtain authorization and to download the cryptographic software files, click Cisco IE 3000 3DES Cryptographic Software.
Step 3
For more information, see the Cisco IE 3000 Switch Software Configuration Guide.
Step 4
Step 5
Switch# ping tftp-server-addressFor more information about assigning an IP address and default gateway to the switch, see the software configuration guide for this release.
Step 6
Switch# archive download-sw /overwrite /reload tftp:[[//location]/directory]/image-name.tarThe /overwrite option overwrites the software image in flash memory with the downloaded one.
The /reload option reloads the system after downloading the image unless the configuration has been changed and not saved.
For //location, specify the IP address of the TFTP server.
For /directory/image-name.tar, specify the directory (optional) and the image to download. Directory and image names are case sensitive.
This example shows how to download an image from a TFTP server at 198.30.20.19 and to overwrite the image on the switch:
Switch# archive download-sw /overwrite tftp://198.30.20.19/ies-lanbase-tar.122-46.SE1.tarYou can also download the image file from the TFTP server to the switch and keep the current image by replacing the /overwrite option with the /leave-old-sw option.
Recovering from a Software Failure
For additional recovery procedures, see the "Troubleshooting" chapter in the software configuration guide for this release.
Installation Notes
You can assign IP information to your switch by using these methods:
•
•
•
•
New Features
These sections describe the new supported hardware and the new and updated software features provided in this release:
New Hardware Features
There are no new hardware features for this release. For a list of all supported hardware, see the "Hardware Supported" section.
New Software Features
•
•
•
•
•
–
–
–
Limitations and Restrictions
You should review this section before you begin working with the switch. These are known limitations that will not be fixed, and there is not always a workaround. Some features might not work as documented, and some features could be affected by recent changes to the switch hardware or software.
This section contains these limitations:
Cisco IOS Limitations
These limitations apply to the Cisco IE 3000 switches:
•
•
•
Configuration
•
This problem occurs under these conditions:
–
–
–
The workaround is to reconfigure the static IP address. (CSCea71176 and CSCdz11708)
•
The workaround is to configure the port for 10 Mb/s and half duplex or to connect a hub or a nonaffected device to the switch. (CSCed39091)
•
The workaround is to enter the no switchport block unicast interface configuration command on that specific interface. (CSCee93822)
•
There is no workaround. This is a cosmetic error and does not affect the functionality of the switch. (CSCef59331)
•
High CPU utilization can also occur with other conditions, such as when debug messages are logged at a high rate to the console.
Use one of these workarounds:
–
–
–
•
The workaround is to configure aggressive UDLD. (CSCsh70244).
Ethernet
Traffic on EtherChannel ports is not perfectly load-balanced. Egress traffic on EtherChannel ports are distributed to member ports on load balance configuration and traffic characteristics like MAC or IP address. More than one traffic stream may map to same member ports based on hashing results calculated by the ASIC.
If this happens, uneven traffic distribution will happen on EtherChannel ports.
Changing the load balance distribution method or changing the number of ports in the EtherChannel can resolve this problem. Use any of these workarounds to improve EtherChannel load balancing:
•
•
•
•
For example, with load balance configured as dst-ip with 150 distinct incrementing destination IP addresses, and the number of ports in the EtherChannel set to either 2, 4, or 8, load distribution is optimal.(CSCeh81991)
IP
When the rate of received DHCP requests exceeds 2,000 packets per minute for a long time, the response time might be slow when you are using the console. The workaround is to use rate limiting on DHCP traffic to prevent a denial of service attack from occurring. (CSCeb59166)
Multicasting
•
•
•
–
–
There is no workaround. (CSCec20128)
•
The switchport block multicast interface configuration command is only applicable to non-IP multicast traffic.
There is no workaround. (CSCee16865)
•
–
–
The workaround is to enter the clear ip mroute privileged EXEC command on the interface. (CSCef42436)
After you configure a switch to join a multicast group by entering the ip igmp join-group group-address interface configuration command, the switch does not receive join packets from the client, and the switch port connected to the client is removed from the IGMP snooping forwarding table.
Use one of these workarounds:
–
–
•
The workaround is to enter the shutdown and the no shutdown interface configuration commands on the Fast Ethernet interface of a new IP phone that is attached to the service module port after the internal link is brought up. (CSCeh45465)
QoS
•
•
SPAN and RSPAN
•
Trunking
•
•
•
VLAN
•
The workaround is to reduce the number of VLANs or trunks. (CSCeb31087)
•
The workaround is to enter the switchport access vlan dynamic interface configuration command separately on each port. (CSCsi26392)
Device Manager Limitations
•
The workaround is to click Yes when you are prompted to accept the certificate. (CSCef45718)
•
The workaround is to manually reload the switch. (CSCsj88169)
Important Notes
Device Manager Notes
•
•
From Microsoft Internet Explorer:
1.
2.
3.
4.
5.
•
Beginning in privileged EXEC mode, follow these steps to configure the HTTP server interface:
•
If you change the HTTP port, you must include the new port number when you enter the IP address in the browser Location or Address field (for example, http://10.1.126.45:184 where 184 is the new HTTP port number). You should write down the port number through which you are connected. Use care when changing the switch IP information.
If you are not using the default method of authentication (the enable password), you need to configure the HTTP server interface with the method of authentication used on the switch.
Beginning in privileged EXEC mode, follow these steps to configure the HTTP server interface:
Open Caveats
•
When you enter the boot host retry timeout global configuration command to specify the amount of time that the client should keep trying to download the configuration and you do not enter a timeout value, the default value is zero, which should mean that the client keeps trying indefinitely. However, the client does not keep trying to download the configuration.
The workaround is to always enter a non zero value for the timeout value when you enter the boot host retry timeout timeout-value command.
•
When an unsuccessful forward open request message is returned on the switch, the response does not contain the connection serial number, vendor ID, or vendor serial number information. Only the general and extended error codes are returned.
This problem only applies to unsuccessful forward open response messages.
The workaround is to enable the CIP debug command to determine the cause of the forward open failure.
•
The show cip object tcp/ip interface privileged EXEC command displays an old value for the domain name after it has been unconfigured with the no ip domain-name global configuration command.
The workaround is to ignore the domain name output of the show cip object tcp/ip interface privileged EXEC command.
•
When you configure PTP in forward mode by entering the ptp mode forward global configuration command, the PTP page in device manager breaks due to a parser error.
There is no workaround. No PTP information is displayed when PTP is in forward mode.
•
The device manager Legend incorrectly shows solid green for the Alarm and Setup LEDs in the Off state. The correct color of these LEDs in the Off state is solid black (dark).
There is no workaround.
Resolved Caveats
These are the caveats that have been resolved in these releases:
•
•
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(46)SE2
•
Symptoms: Several features within Cisco IOS software are affected by a crafted UDP packet vulnerability. If any of the affected features are enabled, a successful attack will result in a blocked input queue on the inbound interface. Only crafted UDP packets destined for the device could result in the interface being blocked, transit traffic will not block the interface.
Cisco has released free software updates that address this vulnerability.
Workarounds that mitigate this vulnerability are available in the workarounds section of the advisory. This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090325-udp.shtml
•
A vulnerability in the handling of IP sockets can cause devices to be vulnerable to a denial of service attack when any of several features of Cisco IOS software are enabled. A sequence of specially crafted TCP/IP packets could cause any of the following results:
–
–
–
–
Workarounds that mitigate this vulnerability are available in the "workarounds" section of the advisory. The advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090325-ip.shtml
•
Cisco IOS software contains a vulnerability in multiple features that could allow an attacker to cause a denial of service (DoS) condition on the affected device. A sequence of specially crafted TCP packets can cause the vulnerable device to reload.
Cisco has released free software updates that address this vulnerability.
Several mitigation strategies are outlined in the workarounds section of this advisory.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090325-tcp.shtml
•
Multiple Cisco products are affected by denial of service (DoS) vulnerabilities that manipulate the state of Transmission Control Protocol (TCP) connections. By manipulating the state of a TCP connection, an attacker could force the TCP connection to remain in a long-lived state, possibly indefinitely. If enough TCP connections are forced into a long-lived or indefinite state, resources on a system under attack may be consumed, preventing new TCP connections from being accepted. In some cases, a system reboot may be necessary to recover normal system operation. To exploit these vulnerabilities, an attacker must be able to complete a TCP three-way handshake with a vulnerable system.
In addition to these vulnerabilities, Cisco Nexus 5000 devices contain a TCP DoS vulnerability that may result in a system crash. This additional vulnerability was found as a result of testing the TCP state manipulation vulnerabilities.
Cisco has released free software updates for download from the Cisco website that address these vulnerabilities. Workarounds that mitigate these vulnerabilities are available.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090908-tcp24.shtml.
•
During switch bootup, the switch alarm-relay circuit no longer changes states (from open to closed and back to open again).
•
The server side of the Secure Copy (SCP) implementation in Cisco IOS software contains a vulnerability that could allow authenticated users with an attached command-line interface (CLI) view to transfer files to and from a Cisco IOS device that is configured to be an SCP server, regardless of what users are authorized to do, per the CLI view configuration. This vulnerability could allow valid users to retrieve or write to any file on the device's file system, including the device's saved configuration and Cisco IOS image files, even if the CLI view attached to the user does not allow it. This configuration file may include passwords or other sensitive information.
The Cisco IOS SCP server is an optional service that is disabled by default. CLI views are a fundamental component of the Cisco IOS Role-Based CLI Access feature, which is also disabled by default. Devices that are not specifically configured to enable the Cisco IOS SCP server, or that are configured to use it but do not use role-based CLI access, are not affected by this vulnerability.
This vulnerability does not apply to the Cisco IOS SCP client feature.
Cisco has released free software updates that address this vulnerability.
There are no workarounds available for this vulnerability apart from disabling either the SCP server or the CLI view feature if these services are not required by administrators.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090325-scp.shtml
•
Smartport macros can now be configured using RSLogix Add-on Profile (AOP). In previous releases, some macros were incorrectly applied twice. (AOP cannot configure multiple macros, and an error was reported to the management node.)
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(46)SE1
•
These traceback messages such as these no longer appear when a large number of IEEE 802.1x supplicants repeatedly try to log in and log out.
Jan 3 17:54:32 L3A3 307: Jan 3 18:04:13.459: %SM-4-BADEVENT: Event 'eapReq' is invalid for the current state 'auth_bend_idle': dot1x_auth_bend Fa9Jan 3 17:54:32 L3A3 308: -Traceback= B37A84 18DAB0 2FF6C0 2FF260 8F2B64 8E912C Jan 3 19:06:13 L3A3 309: Jan 3 19:15:54.720: %SM-4-BADEVENT: Event 'eapReq_no_reAuthMax' is invalid for the current ate 'auth_restart': dot1x_auth Fa4•
When IEEE 802.1x is globally disabled on the switch by using the no dot1x system-auth-control global configuration command, interface level IEEE 802.1x configuration commands, including the dot1x timeout and dot1x mac-auth-bypass commands, are now available.
•
The configuration file used for the configuration replacement feature no longer requires the character string end\n at the end of the file.
•
A switch configured for Link Layer Discovery Protocol (LLDP) now correctly reports the enabled switch capabilities in the LLDP type, length, and value (TLV) attributes. System capabilities appear correctly, and the enabled capabilities are now identified if the switch is configured only as a Layer 2 switch.
•
When two IE 3000 switches are connected with both copper and fiber connections on the same port. and a 100FX-FE SFP module is connected to the switch, when you change the media-type from SFP to copper, the copper link now correctly comes up.
•
When configuring a switch management VLAN to be another VLAN during Express Setup, the PC no longer loses the network connection to the switch if it remains connected to the same port.
•
When a diagnostic or port mirroring role is defined on an interface and you change it to another port role, the port role icon in device manager is now correct.
•
If you remove the secure MAC address from an interface through CIP (Common Industrial Protocol), the switchport port-security violation restrict CLI configuration no longer remains on the interface.
•
In a Multi Domain Authentication (MDA) setup with per-virtual port error-disable configured, when authenticated data and voice clients on the member switch port are dynamically assigned to VLANs and a second data client causes a security violation, only the data virtual port is error-disabled. The voice virtual port is no longer error-disabled at the same time.
•
When the switch IP address is successfully changed via CIP, the expected successful CIP response is now returned. When changing the domain name or switch host name, odd-length strings with the required padding are no longer rejected by the switch.
•
When an IEEE 802.1x client is directly connected to an interface configured for 802.1x multi-domain with no IP phone attached, the interface is initially assigned to the guest VLAN. Once the 802.1x supplicant allows access to the guest VLAN and an EAPOL packet is detected, the interface now correctly reverts to an unauthorized state, and IEEE 802.1x authentication restarts.
•
The CIP revision has been incremented to 2.001 in this release.
Documentation Updates
These sections provide updates to the product documentation:
•
•
•
Updates to the Cisco IE 3000 Switch Software Configuration Guide and Command Reference
The default mode for the ptp global configuration command has been changed to e2etransparent.
The ptp mode forward option has been added to the ptp global configuration command.
When PTP mode is forward, all incoming PTP packets pass through all ports on the switch as normal multicast traffic. In this mode, the switch does not generate any PTP packets, and no other PTP configuration is available, including priority or ptp interface configuration commands.
When the switch is in PTP forward mode, if you enter the show ptp clock or show ptp port privileged EXEC commands, you see a message that no information is available in forwarding mode.
See the ptp (global configuration) command on the next page for the correct syntax.
Note that the "Configuring PTP" chapter in the software configuration guide for this release also contains the wrong information for ptp mode default and does not include the ptp forward option.
ptp (global configuration)
Use the ptp global configuration command to set the clock properties for the Precision Time Protocol (PTP). Use the no form of this command to return to the default end-to-end transparent clock mode.
ptp {mode {boundary | e2etransparent | forward} | priority1 value | priority2 value}
no ptp {mode | priority1 | priority2}
Syntax Description
Defaults
The default mode is end-to-end transparent clock mode.
Command Modes
Global configuration
Command History
Usage Guidelines
The ptp priority1 and ptp priority2 commands are only available when the switch is in boundary mode.
When the switch is in PTP forward mode, no PTP configuration is available except configuring PTP mode to another mode. You cannot configure per-port PTP when the switch is in forward mode.
If you enter the show ptp clock or show ptp port privileged EXEC command when the switch is in PTP forward mode, an error message is generated that no information is available.
Examples
This example shows how to configure the clock to end-to-end transparent mode:
Switch(config)# ptp mode e2etransparentThis example shows how to configure the local clock priority1 value to 55 when PTP mode is boundary:
Switch(config)# ptp mode priority1 55Related Commands
Updates to the Cisco IE 3000 Switch Getting Started Guide
Express Setup
In the "Running Express Setup" section of the Cisco IE 3000 Switch Getting Started Guide,
Steps 8 to 10 have changed.Running Express Setup:
To run Express Setup:
Warning Statement 1067
This warning statement has been removed from the Cisco IE 3000 Switch Getting Started Guide on Cisco.com.
Grounding the Switch
Step 6: Use a ratcheting torque screwdriver to tighten the ground screw and ring terminal lug to the switch front panel to 8.5 in-lb, the maximum recommended torque.
Wiring the DC Power Source
Step 6: Use a ratcheting torque flathead screwdriver to torque the power and relay connector captive screws (above the installed wire leads) to 2 in-lb, the maximum recommended torque.
Resetting the Switch
Follow these steps to return your switch to the factory default settings. These are reasons why you might want to reset the switch:
•
•
•
Caution
To reset the password on the switch:
1.
2.
3.
After the switch restarts, continue to run Express Setup.
Updates to the Regulatory Compliance and Safety Information for the Cisco IE 3000 Switch
Warning Statement 1067
Warning statement 1067 has been removed from the Regulatory Compliance and Safety Information for the Cisco IE 3000 Switch on Cisco.com.
Compliance Labels
The compliance labels for the switch are shown in Figure 1 and Figure 2.
Figure 1 Compliance Label for the Cisco IE 3000 Switch
Figure 2 Compliance Label for the Cisco IE 3000 Switch Extension Module
Related Documentation
These documents provide complete information about the Cisco IE 3000 switches and are available at Cisco.com:
http://www.cisco.com/en/US/products/ps9703/tsd_products_support_series_home.html
•
•
•
•
•
For other information about related products, see these documents:
•
•
•
These SFP module installation notes are available from this Cisco.com site:
http://www.cisco.com/en/US/products/hw/modules/ps5455/prod_installation_guides_list.html
•
•
These compatibility matrix documents are available from this Cisco.com site:
http://www.cisco.com/en/US/products/hw/modules/ps5455/products_device_support_tables_list.html
•
•
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
CCDE, CCSI, CCENT, Cisco Eos, Cisco HealthPresence, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Stackpower, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo 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. (0903R)
Guest
