Table Of Contents
Release Notes for the Cisco Catalyst Blade Switch 3030, Cisco IOS Release 12.2(25)SEE2 and Later
Device Manager System Requirements
Finding the Software Version and Feature Set
Upgrading a Switch by Using the Device Manager
Upgrading a Switch by Using the CLI
Recovering from a Software Failure
Resolved Caveats in Cisco IOS Release 12.2(25)SEE4
Resolved Caveats in Cisco IOS Release 12.2(25)SEE2
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Obtaining Technical Assistance
Cisco Technical Support & Documentation Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Release Notes for the Cisco Catalyst Blade Switch 3030, Cisco IOS Release 12.2(25)SEE2 and Later
Revised June 10, 2008
Cisco IOS Releases 12.2(25)SEE2 and later run on the Cisco Catalyst Blade Switch 3030.
Unless otherwise noted, the term switch refers to a standalone switch.
These release notes include important information about Cisco IOS Release 12.2(25)SEE and any limitations, restrictions, and caveats that apply to them. 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 Catalyst Blade Switch 3030 documentation and of Cisco EtherSwitch service module 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
Cisco IOS Release 12.2(25)SEE2 is based on Cisco IOS Release 12.2(25)S. Open caveats in Cisco IOS Release 12.2(25)S also affect Cisco IOS Release 12.2(25)SEE, unless they are listed in the Cisco IOS Release 12.2(25)SEE resolved caveats list. The list of open caveats in Cisco IOS Release 12.2(25)S is available at this URL:
/en/US/docs/ios/12_2s/release/notes/122Srn.html#wp2367913
Contents
This information is in the release notes:
•
•
•
•
•
•
•
•
•
System Requirements
The system requirements are described in these sections:
•
Hardware Supported
Table 1 lists the hardware supported on Cisco IOS Release 12.2(25)SEE.
Table 1 Cisco Catalyst Blade Switch 3030 Supported Hardware
Cisco Catalyst Blade Switch 3030
Ten internal 1000BASE-TX ports, two external 10/100/1000 ports, and four SFP1 module slots
Cisco IOS Release 12.2(25)SEE
SFP modules
1000BASE-T and 1000BASE-SX
Cisco IOS Release 12.2(25)SEE
1 SFP = small form-factor pluggable
Device Manager System Requirements
These sections describes the hardware and software requirements for using the device manager:
•
•
Hardware Requirements
Table 2 lists the minimum hardware requirements for running the device manager.
Table 2 Minimum Hardware Requirements
Intel Pentium II1
64 MB2
256
1024 x 768
Small
1 We recommend Intel Pentium 4.
2 We recommend 256-MB DRAM.
Software Requirements
Table 3 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
Table 3 Supported Operating Systems and Browsers
Windows 98
None
5.5 or 6.0
7.1
Windows NT 4.0
Service Pack 6 or later
5.5 or 6.0
7.1
Windows 2000
None
5.5 or 6.0
7.1
Windows XP
None
5.5 or 6.0
7.1
1 Service Pack 1 or higher is required for Internet Explorer 5.5.
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 system board flash device (flash:).
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 4 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/partner/products/sw/iosswrel/ps5187/prod_bulletin0900aecd80281c0e.
HtmlYou can copy the binary software image file (with the .bin suffix) 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:
/en/US/docs/ios/12_2/configfun/command/reference/frf011.html#wp1018426
Upgrading a Switch by Using the Device Manager
You can upgrade switch software by using the device manager. 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.
To download software, follow these steps:
Step 1
Step 2
http://www.cisco.com/pcgi-bin/Software/Iosplanner/Planner-tool/iosplanner.cgi
Click on "Launch the IOS Upgrade Planner," and search for CBS3000 to download the appropriate files:
•
•
Step 3
For more information, see Appendix B in the software configuration guide for this release.
Step 4
Note
See the "Connecting through the DRAC/MC" section of the Cisco Catalyst Blade Switch 3030 Getting Started Guide for instructions on how to connect to the switch by using the DRAC/MC.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/cbs30x0-lanbasek9-tar.122-25.SEE.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.
Step 7
Switch# dir flash:
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
There are no new features in this release.
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 switch:
Configuration
These are the configuration limitations:
•
This problem occurs under these conditions:
–
–
–
The workaround is to reconfigure the static IP address. (CSCea71176 and CSCdz11708)
•
–
–
No workaround is necessary; these are the designed behaviors. (CSCed50819)
•
The workaround is to configure the port for 10 Mbps 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)
Ethernet
These are the Ethernet limitations:
•
If this happens, uneven traffic distribution happens 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
This is the IP limitation:
•
IP Telephony
This is the IP telephony limitation:
•
Multicasting
These are the multicasting limitations:
•
–
–
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)
QoS
These are the quality of service (QoS) limitations:
•
•
SPAN and RSPAN
This is the SPAN and Remote SPAN (RSPAN) limitation.
•
The workaround is to use the monitor session session_number destination {interface interface-id encapsulation replicate} global configuration command for local SPAN. (CSCed24036)
Trunking
These are the trunking limitations:
•
•
•
VLAN
This is the VLAN limitation:
•
The workaround is to reduce the number of VLANs or trunks. (CSCeb31087)
Device Manager Limitations
When you are prompted to accept the security certificate and you click No, you only see a blank screen, and the device manager does not launch.
The workaround is to click Yes when you are prompted to accept the certificate. (CSCef45718)
Device Manager Notes
These notes apply to the device manager:
•
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
This section describes the open caveats with possible unexpected activity in this software release. Unless otherwise noted, these severity 3 Cisco IOS configuration caveats apply to the switch:
•
In both EXEC and privileged EXEC command modes, if the console session displays command output and pauses at the end of a page (the More prompt shows), the console session is not closed by a console redirection. The console redirection occurs, but the current console session remains active.
Close any active console session (log out) before you enter the connect switch-N command to redirect the DRAC/MC console to the switch internal console interface, or the reverse.
There is no workaround.
•
These DELL-VENDOR-MIB (powerConnect3000MIB) objects return incorrect values:
–
–
The MIB objects return these values:
productIdentificationVersion = "CBS30X0-LANBASE-M"productIdentificationBuildNumber = "12.2(25)SEE"The correct values are:
productIdentificationVersion = "12.2(25)SEE"productIdentificationBuildNumber = "1"The workaround is to use the value provided by the productIdentificationBuildNumber object wherever the value provided by the productIdentificationVersion object is required.
•
A QoS service policy with a policy map containing more than 62 policers cannot be added to an interface by using the service-policy interface configuration command.
The workaround is to use policy maps with 62 or fewer policers.
•
MAC address notification traps do not work when port security is enabled on the interface.
The workaround is to disable port security on the interface.
•
The switch does not forward an IEEE802.1x request that has null credentials.
There is no workaround.
•
When a source port for a SPAN session has IEEE 802.1x enabled, Extensible Authentication Protocol over LAN (EAPOL) packets are not visible to the packet sniffing tool.
The workaround is to enable a voice VLAN on the SPAN source port.
•
This error message appears during authentication when a method list is used and one of the methods in the method list is removed:
AAA-3-BADMETHODERROR:Cannot process authentication method 218959117There is no workaround. However, this is only an informational message and does not affect switch functionality.
•
When the switch displays a STORM_CONTROL-3-SHUTDOWN message, and a port status changes to disabled, the cpscEvent (cpscStatus) Trap incorrectly shows that the CPortStormControlStatusType is 2, which means forwarding. (The correct status is 5, which means shutdown.)
There is no workaround.
•
When the radius-server source-ports 1645-1646 global configuration command is removed, the switch sends the RADIUS server requests with incorrect source ports. This causes failed authentication attempts.
The workaround is to reload the switch, which restores the reload radius-server source-ports 1645-1645 global configuration command to the configuration and re-establishes communication with the RADIUS server.
•
The switch might display tracebacks similar to these examples when a large number of IEEE 802.1x supplicants try to repeatedly log in and log out.
Examples:
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 Fa9
Jan 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
Jan 3 19:06:13 L3A3 310: -Traceback= B37A84 18DAB0 3046F4 302C80 303228 8F2B64 8E912C Jan 3 20:41:44 L3A3 315: .Jan 3 20:51:26.249: %SM-4-BADEVENT: Event 'eapSuccess' is invalid for the current state 'auth_restart': dot1x_auth Fa9
Jan 3 20:41:44 L3A3 316: -Traceback= B37A84 18DAB0 304648 302C80 303228 8F2B64 8E912C
There is no workaround.
•
When you remove a voice VLAN from a secure port, this message appears:
PORT_SECURITY-6-VLAN_REMOVED: VLAN xxx is no longer allowed on port ppp. Its port security configuration has been removed.
There is no workaround. This is only a notification; no action is required.
•
If you globally disable IEEE 802.1x authentication by using the no dot1x system-auth-control global configuration command and if the dot1x port-control auto or the dot1x port-control force-unauthorized interface configuration command was previously entered, the dot1x port-control auto or the dot1x port-control force-unauthorized interface configuration command takes effect, and the host cannot access the port.
The workaround is to enter the no dot1x port-control interface configuration command to return to the default setting of force-authorized.
Resolved Caveats
These sections describe caveats that were resolved in these releases:
•
•
Resolved Caveats in Cisco IOS Release 12.2(25)SEE4
These caveats were resolved in Cisco IOS Release 12.2(25)SEE4:
•
Multiple Cisco products contain either of two authentication vulnerabilities in the Simple Network Management Protocol version 3 (SNMPv3) feature. These vulnerabilities can be exploited when processing a malformed SNMPv3 message. These vulnerabilities could allow the disclosure of network information or may enable an attacker to perform configuration changes to vulnerable devices. The SNMP server is an optional service that is disabled by default. Only SNMPv3 is impacted by these vulnerabilities. Workarounds are available for mitigating the impact of the vulnerabilities described in this document.
The United States Computer Emergency Response Team (US-CERT) has assigned Vulnerability Note VU#878044 to these vulnerabilities.
Common Vulnerabilities and Exposures (CVE) identifier CVE-2008-0960 has been assigned to these vulnerabilities.
This advisory will be posted at http://www.cisco.com/warp/public/707/cisco-sa-20080610-snmpv3.shtml
•
The switch no longer incorrectly overwrites the class of service (CoS) packets of internally generated Multicast Listener Discovery (MLD) queries and other control packets.
•
The switch no longer reloads when the write core privileged EXEC command is entered when testing a core dump configuration and FTP is selected as the file transfer protocol.
Resolved Caveats in Cisco IOS Release 12.2(25)SEE2
These caveats were resolved in Cisco IOS Release 12.2(25)SEE2:
•
The Mean Opinion Score (MOS) reported by an IP SLA jitter probe is now correct.
•
It is no longer necessary to detach and then reapply a hierarchical policy map to force changes to a VLAN level class-map to take effect.
•
A switch no longer fails IEEE 802.1x authentication if it downloads an access control list (ACL) that has more than 20 ACL access control entries (ACEs) from a RADIUS server.
•
MAC notifications now work properly when port security is configured.
•
The switch now forwards an IEEE802.1x request that has null credentials.
•
A switch no longer fails or displays illegal memory access messages during the SNMP Timer process.
•
The ENTITY-MIB: entPhysicalVendorType now returns correct information for SFP ports.
•
When the switch displays a STORM_CONTROL-3-SHUTDOWN message and a port status changes to disabled, the cpscEvent (cpscStatus) Trap now correctly shows that the CPortStormControlStatusType is 5, which means shutdown.
In previous releases, the trap showed 2, which means forwarding.
•
A MAC entry no longer changes from static to dynamic on a switch configured with private VLANs.
•
When the radius-server source-ports 1645-1646 global configuration command is removed, the switch no longer sends the RADIUS server requests with incorrect source ports.
•
This error log message no longer randomly appears:
%TCAMMGR-3-HANDLE_ERROR: cam handle [hex] is invalid•
If the dot1x port-control auto/force-unauthorized interface configuration command has been entered while IEEE 802.1x is globally disabled, it is no longer necessary to enter the no dot1x port-control interface configuration command to return to the default setting of force-authorized.
•
A switch no longer fails when a user logs in, the debug radius privileged EXEC command is enabled, and the RADIUS server is sending an unsupported attribute value.
•
When you telnet to a switch and enter the autocommand-options nohangup interface configuration command on VTY lines 0 through 4, you can now successfully log out and telnet back into the switch.
•
A routed port no longer fails when STP is configured on an internal VLAN on that port.
•
When a supplicant authenticates, the switch no longer fails if a value for attribute 11 is configured on the RADIUS server.
•
CBS 3030 switch ports are no longer error-disabled when connected to Dell servers. In previous releases, link flaps occurred on the servers, and the CBS 3030 switch ports were error-disabled when connected to the servers.
Related Documentation
These documents provide complete information about the Cisco Catalyst Blade Switch 3030 and are available at Cisco.com:
http://www.cisco.com/en/US/products/ps6748/tsd_products_support_series_home.html
You can order printed copies of documents with a DOC-xxxxxx= number from the Cisco.com sites and from the telephone numbers listed in the "Obtaining Documentation" section.
These documents provide complete information about the Cisco Catalyst Blade Switch 3030:
•
•
•
•
•
•
•
•
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/techsupport
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
Product Documentation DVD
The Product Documentation DVD is a comprehensive library of technical product documentation on a portable medium. The DVD enables you to access multiple versions of installation, configuration, and command guides for Cisco hardware and software products. With the DVD, you have access to the same HTML documentation that is found on the Cisco website without being connected to the Internet. Certain products also have .PDF versions of the documentation available.
The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD= or DOC-DOCDVD=SUB) from Cisco Marketplace at this URL:
http://www.cisco.com/go/marketplace/
Ordering Documentation
Registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:
http://www.cisco.com/go/marketplace/
Nonregistered Cisco.com users can order technical documentation from 8:00 a.m. to 5:00 p.m. (0800 to 1700) PDT by calling 1 866 463-3487 in the United States and Canada, or elsewhere by calling 011 408 519-5055. You can also order documentation by e-mail at tech-doc-store-mkpl@external.cisco.com or by fax at 1 408 519-5001 in the United States and Canada, or elsewhere at 011 408 519-5001.
Documentation Feedback
You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com.
You can submit comments about Cisco documentation 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.
Cisco Product Security Overview
Cisco provides a free online Security Vulnerability Policy portal at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
From this site, you will find information about how to:
•
•
•
A current list of security advisories, security notices, and security responses for Cisco products is available at this URL:
To see security advisories, security notices, and security responses as they are updated in real time, you can subscribe to the Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed. Information about how to subscribe to the PSIRT RSS feed is found at this URL:
http://www.cisco.com/en/US/products/products_psirt_rss_feed.html
Reporting Security Problems in Cisco Products
Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you have identified a vulnerability in a Cisco product, contact PSIRT:
•
An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.
•
In an emergency, you can also reach PSIRT by telephone:
•
•
Tip
Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
The link on this page has the current PGP key ID in use.
If you do not have or use PGP, contact PSIRT at the aforementioned e-mail addresses or phone numbers before sending any sensitive material to find other means of encrypting the data.
Obtaining Technical Assistance
Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.
Cisco Technical Support & Documentation Website
The Cisco Technical Support & Documentation 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, at this URL:
http://www.cisco.com/techsupport
Access to all tools on the Cisco Technical Support & Documentation 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 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 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)—An existing 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 operations 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 the network is impaired, while 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://www.cisco.com/go/iqmagazine
or view the digital edition at this URL:
http://ciscoiq.texterity.com/ciscoiq/sample/
•
•
http://www.cisco.com/en/US/products/index.html
•
http://www.cisco.com/discuss/networking
•
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.
CCVP, the Cisco logo, and the Cisco Square Bridge logo are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networking Academy, Network Registrar, Packet, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, 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. (0705R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2006-2007 Cisco Systems, Inc. All rights reserved.
Guest
