Table Of Contents
Cisco ASA 5500 Series Release Notes Version 8.0(4)
Cisco ASA 5500 Series Adaptive Security Appliance
Operating System and Browser Requirements
Determining the Software Version
Upgrading to a New Software Version
Downgrading to Version 7.2(x) Software
Resolved Caveats - Version 8.0(4)
Obtaining Documentation and Submitting a Service Request
Cisco ASA 5500 Series Release Notes Version 8.0(4)
March 26 2009Contents
This document includes the following sections:
•
Obtaining Documentation and Submitting a Service Request
Introduction
This version supports the following products:
•
Cisco ASA 5500 series adaptive security appliance, Version 8.0(4)
•
ASDM, Version 6.1(3)
Cisco ASA 5500 Series Adaptive Security Appliance
The Cisco ASA 5500 series adaptive security appliances are purpose-built solutions that combine the most effective security and VPN services with the innovative Cisco Adaptive Identification and Mitigation (AIM) architecture.
Designed as a key component of the Cisco Self-Defending Network, the adaptive security appliance provides proactive threat defense that stops attacks before they spread through the network, controls network activity and application traffic, and delivers flexible VPN connectivity. The result is a powerful multifunction network adaptive security appliance family that provides the security breadth and depth for protecting small and medium-sized business and enterprise networks while reducing the overall deployment and operations costs and complexities associated with providing this new level of security.
For more information on all of the new features, see New Features.
Additionally, the adaptive security appliance software supports Cisco Adaptive Security Device Manager (ASDM). ASDM delivers world-class security management and monitoring through an intuitive, easy-to-use web-based management interface. Bundled with the adaptive security appliance, ASDM accelerates adaptive security appliance deployment with intelligent wizards, robust administration tools, and versatile monitoring services that complement the advanced integrated security and networking features offered by the market-leading suite of the adaptive security appliance. Its secure, web-based design enables anytime, anywhere access to adaptive security appliances. For more information on ASDM, see the Cisco ASDM Release Notes Version 6.1(3).
Important Notes
•
ASA Compatible with EIGRP Version 3—EIGRP support was added in Version 8.0(2). However, due to a packet format change, Version 8.0(3) and later are not compatible with Version 8.0(2). Therefore, if you upgrade an adaptive security appliance to Version 8.0(3) or later, and it is peering with another adaptive security appliance running Version 8.0(2), then the peer must also be upgraded, or EIGRP will not operate correctly.
•
Show Active Directory Groups—The DAP Usability feature, used to list active directory groups, is for ASDM only. The show ad-groups command is not intended for CLI use.
•
IPSec VPN packets are dropped when compression is enabled—When you configure the ip-comp enable command under the group-policy, then large packets that are eligible for compression are silently dropped by the security appliance. VPN compression is only useful for very slow Internet connections, so we suggest that you disable compression (ip-comp disable). Alternatively, you can upgrade to interim build 8.0(4.16) or later. (CSCsu26649)
Limitations and Restrictions
Please note the following operational limitations.
•
Stateful Failover with Phone Proxy—When using Stateful Failover with phone proxy, information is not passed to the standby unit; when the active unit goes down, the call fails, media stops flowing, and the call must be re-established.
•
No .NET over Clientless sessions—Clientless sessions do not support .NET framework applications (CSCsv29942).
•
When using Clientless SSL VPN Post-SSO parameters for the Citrix Web interface bookmark, Single-Signon (SSO) works but the Citrix portal is missing the Reconnect and Disconnect buttons. Only the Log Off button shows up. When not using SSO over Clientless, all three buttons show up correctly.
Workaround: Use the Cisco HTTP-POST plugin to provide single signon and correct Citrix portal behavior.
System Requirements
The sections that follow list the system requirements for operating an adaptive security appliance. This section includes the following topics:
•
Operating System and Browser Requirements
•
Determining the Software Version
•
Upgrading to a New Software Version
Memory Requirements
Table 1 lists the DRAM memory requirements for the adaptive security appliance. The memory listed in this table is the default value that ships with each adaptive security appliance.
Table 1 DRAM Memory Requirements
ASA Model Default DRAM Memory (MB)5505
256
5510
256
5520
512
5540
1024
5550
4096
All adaptive security appliances require a minimum of 64 MB of internal CompactFlash, and they all ship with a minimum of 128 MB of internal CompactFlash.
If your adaptive security appliance has only 64 MB of internal CompactFlash, you should not store multiple system images, or multiple images of the new AnyConnect VPN client components, client/server plugins, or Cisco Secure Desktop.
We recommend that you purchase a 256 MB or 512 MB CompactFlash upgrade from Cisco, choosing from the following part numbers:
•
ASA5500-CF-256 MB = ASA 5500 Series CompactFlash, 256 MB
•
ASA5500-CF-512 MB = ASA 5500 Series CompactFlash, 512 MB
You can check the size of internal flash and the amount of free flash memory on the adaptive security appliance by doing the following:
•
ASDM—Click Tools > File Management. The amounts of total and available flash memory appear on the bottom left in the pane.
•
CLI—In Privileged EXEC mode, enter the dir command. The amounts of total and available flash memory appear on the bottom of the output.
For example:
hostname # dirDirectory of disk0:/43 -rwx 14358528 08:46:02 Feb 19 2007 cdisk.bin136 -rwx 12456368 10:25:08 Feb 20 2007 asdmfile58 -rwx 6342320 08:44:54 Feb 19 2007 asdm-600110.bin61 -rwx 416354 11:50:58 Feb 07 2007 sslclient-win-1.1.3.173.pkg62 -rwx 23689 08:48:04 Jan 30 2007 asa1_backup.cfg66 -rwx 425 11:45:52 Dec 05 2006 anyconnect70 -rwx 774 05:57:48 Nov 22 2006 cvcprofile.xml71 -rwx 338 15:48:40 Nov 29 2006 tmpAsdmCustomization43040652672 -rwx 32 09:35:40 Dec 08 2006 LOCAL-CA-SERVER.ser73 -rwx 2205678 07:19:22 Jan 05 2007 vpn-win32-Release-2.0.0156-k9.pkg74 -rwx 3380111 11:39:36 Feb 12 2007 securedesktop_asa_3_2_0_56.pkg62881792 bytes total (3854336 bytes free)hostname #
In a failover configuration, the two units must have the same hardware configuration, must be the same model, must have the same number and types of interfaces, and must have the same amount of RAM. For more information, see the "Configuring Failover" chapter in the Cisco Security Appliance Command Line Configuration Guide.
Note
If you use two units with different flash memory sizes, make sure that the unit with the smaller flash memory has enough space for the software images and configuration files.
Operating System and Browser Requirements
For the latest OS and browser test results, see the Cisco ASA 5500 Series VPN Compatibility Reference.
Determining the Software Version
Use the show version command to verify the software version of your adaptive security appliance. Alternatively, the software version appears on the Cisco ASDM home page.
Upgrading to a New Software Version
To upgrade from Version 7.2.(x) to Version 8.0(4), perform the following steps:
Step 1
Make a backup copy of your current configuration file.
Step 2
Load the new Version 8.0(4) image from the following website:
http://www.cisco.com/public/sw-center/index.shtml
Step 3
Restart the device to load the Version 8.0(4) image.
Step 4
Load the new ASDM 6.1(3) image from the following website:
http://www.cisco.com/public/sw-center/index.shtml
Step 5
Enter the following command to tell the adaptive security appliance where to find the ASDM image:
hostname(config)# asdm image disk0:/asdmfilename (no spaces after the / character, or within the filename itself)
Downgrading to Version 7.2(x) Software
To downgrade from Version 8.0(4) to 7.2(x), perform the following steps:
Step 1
Load the 7.2(x) image from the following website:
http://www.cisco.com/public/sw-center/index.shtml
Step 2
Restart the device to load the 7.2(x) image.
Step 3
Load the ASDM 5.2(x) image from the following website:
http://www.cisco.com/public/sw-center/index.shtml
Step 4
Enter the following command to tell the adaptive security appliance where to find the ASDM image:
hostname(config)# asdm image disk0:/asdmfilename (no spaces after the / character, or within the filename itself)
New Features
Table 2 lists the new features for Version 8.0(4).
Table 2 New Features for ASA and PIX Version 8.0(4)
Feature Description Unified Communications Features1Phone Proxy
Phone Proxy functionality is supported. ASA Phone Proxy provides similar features to those of the Metreos Cisco Unified Phone Proxy with additional support for SIP inspection and enhanced security. The ASA Phone Proxy has the following key features:
•
Secures remote IP phones by forcing the phones to encrypt signaling and media
•
Performs certificate-based authentication with remote IP phones
•
Terminates TLS signaling from IP phones and initiates TCP and TLS to Cisco Unified Mobility Advantage servers
•
Terminates SRTP and initiates RTP/SRTP to the called party
In ASDM, see Configuration > Firewall > Advanced > Encrypted Traffic Inspection > Phone Proxy.
Mobility Proxy
Secure connectivity (mobility proxy) between Cisco Unified Mobility Advantage clients and servers is supported.
Cisco Unified Mobility Advantage solutions include the Cisco Unified Mobile Communicator, an easy-to-use software application for mobile handsets that extends enterprise communications applications and services to mobile phones and smart phones and the Cisco Unified Mobility Advantage server. The mobility solution streamlines the communication experience, enabling real-time collaboration across the enterprise.
The ASA in this solution delivers inspection for the MMP (formerly called OLWP) protocol, the proprietary protocol between Cisco Unified Mobile Communicator and Cisco Unified Mobility Advantage. The ASA also acts as a TLS proxy, terminating and reoriginating the TLS signaling between the Cisco Unified Mobile Communicator and Cisco Unified Mobility Advantage.
In ASDM, see Configuration > Firewall > Advanced > Encrypted Traffic Inspection > TLS Proxy.
Presence Federation Proxy
Secure connectivity (presence federation proxy) between Cisco Unified Presence servers and Cisco/Microsoft Presence servers is supported. With the Presence solution, businesses can securely connect their Cisco Unified Presence clients back to their enterprise networks, or share Presence information between Presence servers in different enterprises.
The ASA delivers functionality to enable Presence for Internet and intra-enterprise communications. An SSL-enabled Cisco Unified Presence client can establish an SSL connection to the Presence Server. The ASA enables SSL connectivity between server to server communication including third-party Presence servers communicating with Cisco Unified Presence servers. Enterprises share Presence information, and can use IM applications. The ASA inspects SIP messages between the servers.
In ASDM, see Configuration > Firewall > Service Policy Rules > Add/Edit Service Policy Rule > Rule Actions > Protocol Inspection or Configuration > Firewall > Advanced > Encrypted Traffic Inspection > TLS Proxy > Add > Client Configuration.
Remote Access FeaturesAuto Sign-On with Smart Tunnels for IE1
This feature lets you enable the replacement of logon credentials for WININET connections. Most Microsoft applications use WININET, including Internet Explorer. Mozilla Firefox does not, so it is not supported by this feature. It also supports HTTP-based authentication, therefore form-based authentication does not work with this feature.
Credentials are statically associated to destination hosts, not services, so if initial credentials are wrong, they cannot be dynamically corrected during runtime. Also, because of the association with destinations hosts, providing support for an auto sign-on enabled host may not be desirable if you want to deny access to some of the services on that host.
To configure a group auto sign-on for smart tunnels, you create a global list of auto sign-on sites, then assign the list to group policies or user names. This feature is not supported with Dynamic Access Policy.
In ASDM, see Firewall > Advanced > ACL Manager.
Entrust Certificate Provisioning1
ASDM includes a link to the Entrust website to apply for temporary (test) or discounted permanent SSL identity certificates for your ASA.
In ASDM, see Configuration > Remote Access VPN > Certificate Management > Identity Certificates. Click Enroll ASA SSL VPN head-end with Entrust.
Extended Time for User Reauthentication on IKE Rekey
You can configure the security appliance to give remote users more time to enter their credentials on a Phase 1 SA rekey. Previously, when reauthenticate-on-rekey was configured for IKE tunnels and a phase 1 rekey occurred, the security appliance prompted the user to authenticate and only gave the user approximately 2 minutes to enter their credentials. If the user did not enter their credentials in that 2 minute window, the tunnel would be terminated. With this new feature enabled, users now have more time to enter credentials before the tunnel drops. The total amount of time is the difference between the new Phase 1 SA being established, when the rekey actually takes place, and the old Phase 1 SA expiring. With default Phase 1 rekey times set, the difference is roughly 3 hours, or about 15% of the rekey interval.
In ASDM, see Configuration > Device Management > Certificate Management > Identity Certificates.
Persistent IPsec Tunneled Flows
With the persistent IPsec tunneled flows feature enabled, the security appliance preserves and resumes stateful (TCP) tunneled flows after the tunnel drops, then recovers. All other flows are dropped when the tunnel drops and must reestablish when a new tunnel comes up. Preserving the TCP flows allows some older or sensitive applications to keep working through a short-lived tunnel drop. This feature supports IPsec LAN-to-LAN tunnels and Network Extension Mode tunnels from a Hardware Client. It does not support IPsec or AnyConnect/SSL VPN remote access tunnels. See the [no] sysopt connection preserve-vpn-flows command. This option is disabled by default.
In ASDM, see Configuration > Remote Access VPN > Network (Client) Access > Advanced > IPsec > System Options. Check the Preserve stateful VPN flows when the tunnel drops for Network Extension Mode (NEM) checkbox to enable persistent IPsec tunneled flows.
Show Active Directory Groups
The CLI command show ad-groups was added to list the active directory groups. ASDM Dynamic Access Policy uses this command to present the administrator with a list of MS AD groups that can be used to define the VPN policy.
In ASDM, see Configuration > Remote Access VPN > Clientless SSL VPN Access > Dynamic Access Policies > Add/Edit DAP > Add/Edit AAA Attribute.
Smart Tunnel over Mac OS1
Smart tunnels now support Mac OS.
In ASDM, see Configuration > Remote Access VPN > Clientless SSL VPN Access > Portal > Smart Tunnels.
Firewall FeaturesQoS Traffic Shaping
If you have a device that transmits packets at a high speed, such as the adaptive security appliance with Fast Ethernet, and it is connected to a low speed device such as a cable modem, then the cable modem is a bottleneck at which packets are frequently dropped. To manage networks with differing line speeds, you can configure the security appliance to transmit packets at a fixed slower rate. See the shape command. See also the crypto ipsec security-association replay command, which lets you configure the IPSec anti-replay window size. One side-effect of priority queueing is packet re-ordering. For IPSec packets, out-of-order packets that are not within the anti-replay window generate warning syslog messages. These warnings become false alarms in the case of priority queueing. This new command avoids possible false alarms.
In ASDM, see Configuration > Firewall > Security Policy > Service Policy Rules > Add/Edit Service Policy Rule > Rule Actions > QoS. Note that the only traffic class supported for traffic shaping is class-default, which matches all traffic.
TCP Normalization Enhancements
You can now configure TCP normalization actions for certain packet types. Previously, the default actions for these kinds of packets was to drop the packet. Now you can set the TCP normalizer to allow the packets.
•
TCP invalid ACK check (the invalid-ack command)
•
TCP packet sequence past window check (the seq-past-window command)
•
TCP SYN-ACK with data check (the synack-data command)
You can also set the TCP out-of-order packet buffer timeout (the queue command timeout keyword). Previously, the timeout was 4 seconds. You can now set the timeout to another value.
The default action for packets that exceed MSS has changed from drop to allow (the exceed-mss command).
The following non-configurable actions have changed from drop to clear for these packet types:
•
Bad option length in TCP
•
TCP Window scale on non-SYN
•
Bad TCP window scale value
•
Bad TCP SACK ALLOW option
In ASDM, see Configuration > Firewall > Objects > TCP Maps.
TCP Intercept statistics
You can enable collection for TCP Intercept statistics using the threat-detection statistics tcp-intercept command, and view them using the show threat-detection statistics command.
In ASDM 6.1(5) and later, see Configuration > Firewall > Threat Detection. This command was not supported in ASDM 6.1(3).
Threat detection shun timeout
You can now configure the shun timeout for threat detection using the threat-detection scanning-threat shun duration command.
In ASDM 6.1(5) and later, see Configuration > Firewall > Threat Detection. This command was not supported in ASDM 6.1(3).
Timeout for SIP Provisional Media
You can now configure the timeout for SIP provisional media using the timeout sip-provisional-media command.
In ASDM, see Configuration > Firewall > Advanced > Global Timeouts.
Platform FeaturesNative VLAN support for the ASA 5505
You can now include the native VLAN in an ASA 5505 trunk port using the switchport trunk native vlan command.
In ASDM, see Configuration > Device Setup > Interfaces > Switch Ports > Edit dialog.
SNMP support for unnamed interfaces
Previously, SNMP only provided information about interfaces that were configured using the nameif command. For example, SNMP only sent traps and performed walks on the IF MIB and IP MIB for interfaces that were named. Because the ASA 5505 has both unnamed switch ports and named VLAN interfaces, SNMP was enhanced to show information about all physical interfaces and logical interfaces; a nameif command is no longer required to display the interfaces using SNMP. These changes affect all models, and not just the ASA 5505.
1 This feature is not supported on the PIX security appliance.
SNMP Changes
This section describes the updated approach used by SNMP to display adaptive security appliance interfaces, and the additional link state traps that are sent for interfaces.
Before Version 8.0(4)/8.1(2), SNMP only provided information about interfaces that were configured using the nameif command. For example, SNMP only sent traps and performed walks on the IF MIB and IP MIB for interfaces that were named. Because the ASA 5505 has both unnamed switch ports and named VLAN interfaces, SNMP was enhanced to show information about all physical interfaces and logical interfaces; a nameif command is no longer required to display the interfaces using SNMP. These changes affect all models, and not just the ASA 5505.
This section includes the following topics:
IF MIB Output Changes
SNMP was enhanced to show information about all physical interfaces and logical interfaces, including internal interfaces; a nameif command is no longer required to display the interfaces using SNMP.
For example, the ifPhysAddr output now includes the MAC addresses of switch ports on the ASA 5505; before, only named VLAN interfaces were shown with a MAC address of 0:0:0:0:0:0.
You might see information about the following internal interfaces:
•
Null0—Not currently in use.
•
Internal-Data or Internal-Control—Internal interfaces for communicating with SSMs or SSCs.
•
_internal_loopback—The loopback interface.
•
Virtual—Used for phone proxy media termination functions.
The following topics show a sample interface configuration on the ASA 5505, and sample ifDescr output:
•
Sample Interface Configuration
Sample Interface Configuration
The following example shows the interface configuration for an ASA 5505; refer to this example when looking at the ipDescr sample output in the "Sample ifDescr Output" section.
interface Vlan1nameif usersecurity-level 40ip address 192.168.4.1 255.255.255.0interface Vlan40no nameifsecurity-level 0no ip addressinterface Vlan41no nameifsecurity-level 100no ip addressinterface Vlan46no nameifsecurity-level 0no ip addressinterface Vlan47no nameifsecurity-level 100no ip addressinterface Vlan100nameif insidesecurity-level 100ip address 10.7.1.80 255.255.255.0interface Vlan112no nameifsecurity-level 10no ip addressinterface Vlan114nameif mgmtsecurity-level 10ip address 10.8.1.80 255.255.255.0interface Vlan200nameif outsidesecurity-level 0ip address 10.9.1.80 255.255.255.0interface Ethernet0/0switchport trunk allowed vlan 100switchport mode trunkinterface Ethernet0/1switchport trunk allowed vlan 1,200switchport mode trunkinterface Ethernet0/2switchport access vlan 114interface Ethernet0/3interface Ethernet0/4interface Ethernet0/5interface Ethernet0/6interface Ethernet0/7Sample ifDescr Output
The following ifDescr output shows the difference before and after the SNMP changes (changes are shown in bold):
Before:
IF-MIB::ifDescr.1 = Adaptive Security Appliance 'user' interfaceIF-MIB::ifDescr.2 = Adaptive Security Appliance 'inside' interfaceIF-MIB::ifDescr.3 = Adaptive Security Appliance 'mgmt' interfaceIF-MIB::ifDescr.4 = Adaptive Security Appliance 'outside' interfaceAfter:
IF-MIB::ifDescr.1 = Adaptive Security Appliance 'Null0' interfaceIF-MIB::ifDescr.2 = Adaptive Security Appliance 'Internal-Data0/0'interfaceIF-MIB::ifDescr.3 = Adaptive Security Appliance 'Ethernet0/0' interfaceIF-MIB::ifDescr.4 = Adaptive Security Appliance 'Ethernet0/1' interfaceIF-MIB::ifDescr.5 = Adaptive Security Appliance 'Ethernet0/2' interfaceIF-MIB::ifDescr.6 = Adaptive Security Appliance 'Ethernet0/3' interfaceIF-MIB::ifDescr.7 = Adaptive Security Appliance 'Ethernet0/4' interfaceIF-MIB::ifDescr.8 = Adaptive Security Appliance 'Ethernet0/5' interfaceIF-MIB::ifDescr.9 = Adaptive Security Appliance 'Ethernet0/6' interfaceIF-MIB::ifDescr.10 = Adaptive Security Appliance 'Ethernet0/7' interfaceIF-MIB::ifDescr.11 = Adaptive Security Appliance 'Internal-Data0/1' interfaceIF-MIB::ifDescr.12 = Adaptive Security Appliance '_internal_loopback' interfaceIF-MIB::ifDescr.13 = Adaptive Security Appliance 'Virtual254' interfaceIF-MIB::ifDescr.14 = Adaptive Security Appliance 'user' interfaceIF-MIB::ifDescr.15 = Adaptive Security Appliance 'Vlan40' interfaceIF-MIB::ifDescr.16 = Adaptive Security Appliance 'Vlan41' interfaceIF-MIB::ifDescr.17 = Adaptive Security Appliance 'Vlan46' interfaceIF-MIB::ifDescr.18 = Adaptive Security Appliance 'Vlan47' interfaceIF-MIB::ifDescr.19 = Adaptive Security Appliance 'inside' interfaceIF-MIB::ifDescr.20 = Adaptive Security Appliance 'Vlan112' interfaceIF-MIB::ifDescr.21 = Adaptive Security Appliance 'mgmt' interfaceIF-MIB::ifDescr.22 = Adaptive Security Appliance 'outside' interfaceIP MIB Output Changes
Walking the IP MIB now shows IP addresses assigned to all interfaces, not just those configured using the nameif command.
SNMP Link State Trap Changes
SNMP now sends traps at bootup, when an interface is shut down, or when an interface is brought up for all physical interfaces and logical interfaces; a nameif command is no longer required to send traps about interfaces. Before this enhancement, traps were sent only for interfaces that had a name configured.
Caveats
The following sections describe the caveats for Version 8.0(4).
•
Open Caveats - Version 8.0(4)
•
Resolved Caveats - Version 8.0(4)
For your convenience in locating caveats in the Cisco Bug Toolkit, the caveat titles listed in this section are drawn directly from the Bug Toolkit database. These caveat titles are not intended to be read as complete sentences because the title field length is limited. In the caveat titles, some truncation of wording or punctuation may be necessary to provide the most complete and concise description. The only modifications made to these titles are as follows:
•
Commands are in boldface type.
•
Product names and acronyms may be standardized.
•
Spelling errors and typos may be corrected.
Note
If you are a registered cisco.com user, view Bug Toolkit on cisco.com at the following website:
http://www.cisco.com/support/bugtools
To become a registered cisco.com user, go to the following website:
http://tools.cisco.com/RPF/register/register.do
Open Caveats - Version 8.0(4)
Resolved Caveats - Version 8.0(4)
Related Documentation
For additional information on the adaptive security appliance, go to:
http://www.cisco.com/en/US/products/ps6120/tsd_products_support_series_home.html
Obtaining Documentation and Submitting a Service Request
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)
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.
© 2007-2008 Cisco Systems, Inc.
All rights reserved.

