Table Of Contents
Release Notes for Cisco Application eXtension Platform (AXP) 1.1.5
September 24, 2009Revised: April 6, 2010, OL-14273-01
These release notes support the software for the Cisco Application eXtension Platform (AXP). To see if your software or hardware platforms are affected, view the field notices for Cisco IOS software version 12.4 (T) at http://www.cisco.com/warp/public/tech_tips/index/cfn.html. (You need to have an account on cisco.com to view the field notices.)
This section describes the system requirements for Cisco Application eXtension Platform Version 1.1.5 and includes the following sections:
Cisco IOS Software Release
Cisco AXP 1.1.5 supports routers with the following Cisco IOS releases.
•12.4(15)T3 or higher: IP-based crypto images including the following image packs:
Download the image from:
Files in Cisco AXP 1.1.5
Download Cisco AXP files from the following location:
Files in Cisco AXP 1.1.5 are explained in the following sections:
Cisco AXP Product Files
Cisco AXP product files for AIM and NME service modules:
Cisco AXP Product Files for AIM Service Modules
Cisco AXP Product Files for NME Service Modules
Compressed archive axp-k9.nme.1.1.5.tar.gz contains all package files associated with Cisco AXP on NME service module. The package files are shown in Table 1.
Cisco AXP Software Development Files
Cisco AXP software development files:
Cisco AXP Software Development Kit (SDK)
Compressed archive axp-sdk.1.1.5.tar.gz contains the Cisco AXP Software Development Kit (SDK) for all service modules.
Cisco AXP Software Development Files for VMware
Compressed archive axp-k9.vmw.1.1.5.tar.gz contains the Cisco AXP Software Development Files for VMware.
The package files are shown in Table 2.
Table 3 Cisco AXP 1.1.5 Software Development Files for VMware
Cisco AXP VMware disk image file.
Cisco AXP VMware virtual hardware configuration file.
Cisco AXP Software Development Files for Add-ons on AIM Service Modules
Compressed archive axp-k9.aim.addon.1.1.5.tar.gz contains Cisco AXP software development files for add-ons on AIM service modules. The package files are shown in Table 3.
Cisco AXP Software Development Files for Add-ons on NME Service Modules
Compressed archive axp-k9.nme.addon.1.1.5.tar.gz contains Cisco AXP software development files for add-ons on NME service modules. The package files are shown in Table 4.
Upgrading and Downgrading to a New Software Release
Upgrading from Cisco AXP 1.1.1 to Cisco AXP 1.1.5
To upgrade from Cisco AXP 1.1.1 and higher versions to Cisco AXP 1.1.5 with applications packaged with the 1.1.1/1.1.5 SDK:
a. Copy the installer payload file (axp-installer.k9.nme.1.1.5.prt1 or axp-installer.k9.aim.1.1.5.prt1) to the same FTP directory as the Cisco AXP package.
The FTP directory contains a package file such as (axp-k9.nme.1.1.5.pkg or axp-installer.k9.aim.1.1.5.prt1) and
a corresponding payload file (axp-k9.nme.1.1.5.prt1 or axp-k9.aim.1.1.5.prt1) with other add-on packages.
b. Install the Cisco AXP package using the software install upgrade command.
Note If you are using a URL to obtain a copy of the Cisco AXP package use an ftp or ftps server location. Do not use an sftp server location. Using an sftp server results in the error described in the caveat: "CSCsy53185 TypeError occurs during installation or upgrade of Cisco AXP." section.
For upgrading and downgrading various software versions on Cisco AXP, refer to the Cisco Application eXtension Platform 1.1 Command Reference and the Cisco Application eXtension Platform 1.1 User Guide.
After upgrading to Cisco AXP 1.1.5, verify that the system is running on Cisco AXP 1.1.5.
Downgrading from Cisco AXP 1.1.5
To downgrade to Cisco AXP 1.1.1 with applications packaged with the 1.1.1 SDK:
–Use the software install upgrade command. The software install downgrade command is not currently supported. For more information, see the Cisco Application eXtension Platform 1.1 Command Reference and the Cisco Application eXtension Platform 1.1 User Guide.
Note If you downgrade the service module to Cisco AXP 1.1.1 and use applications packaged with the Cisco AXP 1.1.5 SDK, the applications may not work. To avoid this, first repackage the applications with the Cisco AXP 1.1.1 SDK, downgrade the service module to Cisco AXP 1.1.1, and run the applications packaged with the Cisco AXP 1.1.1 SDK.
Determining the Software Version
To determine the version of Cisco AXP software currently running on your Cisco AXP service module, log into the service module, and enter the show software version EXEC command.
The following sample output from the show software version command indicates the version number on the first output line.Application eXtension Platform (AXP) version (1.1.5)Technical Support: http://www.cisco.com/techsupport/ Copyright (c) 1986-2009 by Cisco Systems, Inc.
Limitations and Restrictions
For Cisco AXP 1.1.5 and lower versions, issuing the do command through the Cisco AXP IOS Service API, always returns "OK". If the do command works or fails, the return value is always the same—"OK".
However, issuing the do command through a Cisco IOS CLI console session returns the correct error messages when the do command fails.
Caveats for Cisco AXP
Caveats describe unexpected behavior or defects in Cisco software releases. Severity 1 caveats are the most serious caveats, severity 2 caveats are less serious, and severity 3 caveats are the least serious of these three severity levels.
Note To reach the Bug Toolkit, log in to Cisco.com and go to: http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. (If the defect that you have requested cannot be displayed, this may be due to one or more of the following reasons: the defect number does not exist, the defect does not have a customer-visible description yet, or the defect has been marked Cisco Confidential.)
Resolved Caveats- Cisco AXP Version 1.1.5
Symptom Cannot bind to port 53.
Conditions J9 on the service module binds to the well known port.
Symptom Boot up of the service module displays the message:Bootup of service module gives message '/sw/info/ps: -5: event handler is dead
Conditions Service module configuration contains more than eight interfaces/subinterfaces.
Symptom The bind serial command is not displayed in the running configuration after reloading the service module.
Conditions .The bind serial command is configured inside the application context and saved to the startup configuration using the write memory command. The service module is reloaded using the reload command.
Symptom Guest application running IOSAPI command freezes when the command is run.
Conditions NETCONF over BEEP is configured on the router and service module. Rebooting only the router and then running the IOSAPI application causes the application to consistently hang. Rebooting only the service module and then running the IOSAPI application causes the application to randomly hang.
Symptom The virtual instance disappears when the OS is upgraded.
Conditions Cisco AXP initially installed with a single bundle image using the boot helper.
Symptom Service API freezes
Conditions CLI to install or upgrade an application fails
Symptom Excessive delay in NETCONF responding to a failed connection of an unreachable device.
Conditions Any connection attempt to a non-responsive server.
Symptom Application fails to start after an upgrade.
Conditions The application fails to start when the file ownership changes to root/daemon during the upgrade process.
Symptom Installing a Cisco AXP 1.1 host OS with a bundle containing one or more Cisco AXP 1.0 add-on packages, or upgrading from Cisco AXP 1.0 host OS with the same bundle results in an upgrade failure. This happens when using either software install upgrade command or software install clean command.
The system expects the Cisco AXP 1.0 installer file. Copying that file to the same FTP package directory results in a successful download of the 1.0 installer file, but does not install the bundle.
Conditions .Packages are bundled with a Cisco AXP 1.1 SDK, where the bundle includes the Cisco AXP 1.1 host OS package and one or more Cisco AXP 1.0 add-on packages. The system installs this bundle from a Cisco AXP 1.0 system.
Symptom Function GetRouterIP is unavailable.
Conditions The virtual instance does not link to ipcutilservice. AXP 1.1 release will encounter this issueCSCsu65855 When upgrading from Cisco AXP 1.0.6 to 1.1.1, the /etc/rc.d/rc3.d/<files> might be corrupted.
Symptom When upgrading Cisco AXP, the /etc/rc.d/rc3.d/<files> might be corrupted. For example, if applications App1 and App2 in the bundle contain a file of the same name e.g /etc/rc.d/rc3.d/S98_app_cus, then the contents of the S98_app_cus file for App1 are replaced by the contents of the S98_app_cus file for App2.
Conditions Upgrading Cisco AXP 1.0.6 to 1.1.1 using a bundle containing two or more applications and the Cisco AXP 1.1.1 base OS image.
Symptom In /proc/meminfo the "Swap Free" value is a very low number, the allocated address space.
Conditions In Cisco AXP 1.1.1, when swap is turned on, the swap free value shown in /proc/meminfo in the guest OS is the allocated address space, not the unused swap space. (The swap free value in /proc/meminfo in the host OS is the unused swap space, which is correct.)CSCsu93803 The packaging tool pkg_build.sh does not package files with a file name containing spaces.
Symptom File names with spaces do not appear in a packaged application.
Conditions Packaging an application with a file name containing spaces fails and the file is not packaged.
Symptom A bridge utility command such as brctl addbr br0 gives an error.
Conditions Enabling Openvpn in tap (bridge) server mode.
Symptom Interface attribute missing in the ping command.
Conditions .Using a different interface to ping ICMP packets through the interface attribute in the ping command.CSCsw88604 Packaging tool pkg_build.sh fails to build package due to an error in create_manifest.sh.
Symptom Using packaging tool pkg_build.sh, a create_manifest.sh error occurs, and a package is not built.
Conditions The packaging tool pkg_build.sh is not provided with GREP_CMD as a parameter.
Symptom The "show resource limit" command underestimates the memory available to an application.
Conditions When an application is packaged to use swap space for memory.
Symptom Using the rpm_extractor.sh tool on an RPM, gives a .deps file that might not include all of the required libraries (dependencies) for the binary files in an RPM.
Conditions If a dependency was not listed in the RPM's original .spec file, it is not listed in the .deps file created by the rpm_extractor.sh tool.
Symptom Setting a new timezone on the Cisco AXP service module might not take effect and the timezone remains set to the old timezone.
Conditions After a new timezone is set, the timezone is not propagated to virtual instances after saving the configuration and reloading the service module. The show clock detail command shows the time according to the new timezone. However, the show clock command shows the time according to the old timezone. The following timezones show this problem:
•ZuluCSCsv16106 Running a command in the Cisco AXP IOS Service API that contains embedded quotes, results in an error.
Symptom Failure to successfully run a command using the IOS Service API, where the command contains embedded quotes.
Conditions The show class map \"brett class\" command returns the error message "operation failed".
Symptom When the AIM module boots up, the following error message is output:Enter '###' to start safe mode: System start in Normal modeexpr: syntax error/etc/rc.d/rc.aesop: line 764: [: -lt: unary operator expected/etc/rc.d/rc.aesop: line 766: [: -lt: unary operator expectedINIT: Entering runlevel: 2
Conditions The error message occurs when the AIM module reboots.CSCsr89533 The "show swap usage" command displays the incorrect amount of memory used by an application.
Symptom An incorrect value is displayed for the amount of memory used by an application running in a virtual instance.
Conditions None.CSCsy05334 After upgrading a bundle of applications having different versions command show software version fails to show one of the bundle applications in a list.
Symptom After upgrading an application does not appear after command show software version. However, the application does appear after command show app state.
Conditions Upgrading an application in a bundle, when applications in the bundle were compiled with different versions of Cisco AXP tools.
Symptom The IP address is unavailable. The following messages are displayed after executing the no shutdown CLI:SIOCSIFFLAGS: Cannot assign requested addressSIOCSIFNETMASK: Cannot assign requested addressSIOCSIFFLAGS: Cannot assign requested address
Conditions A shutdown/no shutdown CLI sequence on subinterface eth1:1 .
Symptom Delay of up to ten minutes before the Cisco AXP host OS comes online.
Conditions After the service module is restarted several times, see the messages log.
Symptom CLI session hangs after entering ctrl-c
Conditions A CLI session with a long response time hangs when Ctrl-C is used to terminate that session.
Symptom An error message of the following type:!!Downloading ftp built_in_installerDownload errorCan not download built_in_installererror code 550 : error type 'Can not find package file'
Conditions Upgrading a bundle containing the Cisco AXP base OS image, a Cisco add-on package, and an application package. The installer file is placed in the same FTP directory as the bundle.
Open Caveats- Cisco AXP Version 1.1.5CSCsu25459 The script pkg_build.sh freezes when application is packaged with a dependency on a Cisco add-on application.
Symptom The commands fgrep, egrep, and mkencryptedsig.sh do not have their supported libraries available in axp-sdk.1.0.6/lib/pkg/bin. The pkg_build.sh script freezes and the core.log file displays the following type of message:Checking for installed files that are not in packaging file list...The following files/directories in the install directory are missing from packaging file list./source/javalin/tools/1.0.6/axp-sdk.1.0.6/lib/pkg/bin/fgrep: error while loading shared libraries: libpcre.so: cannot open shared object file: No such file or directory.Do you wish to continue packaging without these files(y,n)? Please answer y to continue, no to exit: Processing manifest templates within /source/javalin/apps/remoteSerialDev_app/package/templates.
Conditions Packaging the application with a dependency on a Cisco add-on application using Cisco AXP 1.0.6 or 1.1.1.
Workaround Perform one of the following workarounds after the packaging tool script freezes:
Press Ctrl-C to continue, or
Obtain the pcre library (RPM) and install it on the development workstation. Then repackage your application.CSCsr40087 Application online state not displayed after installing a third party application bundle.
Symptom The show app-service state command does not display the online state of the bundle after installation.
Conditions Install a bundle containing a third party application and the Cisco AXP host OS.
Workaround Install the third party application and the Cisco AXP host OS separately without bundling them.CSCsv57204 Disk-wildcard parameter on AIM module uses available resources and affects system performance.
Symptom Performance suffers and disk capacity is displayed as being nearly full. When used disk space approaches 50 MB, the application cannot write logs. Rebooting the system results in the appearance of messages such as the following:WARNING: The system storage usage has exceeded 95% of its capacity.WARNING: Starting disk cleanup operation ....trace: INFO trace daemon output id: cannot find name for user ID 0/bin/disk_cleanup.sh: line 6: cannot create temp file for here document: No space left on deviceRemoving unnecessary filestrace: INFO trace daemon output Unable to locate media-typeDisk is 100% full, with 48k bytes available
Conditions Use the disk-wildcard parameter and fill the allocated space by writing to file.
Workaround Keep the file size less than 50 MB of the maximum allocated size.
Symptom The following message appears after starting to install the Cisco AXP base OS:
"insmod: error inserting '/lib/modules/aesop_flash/aesop_flash.ko':".
Conditions Compact flash from Unigen is used.
Workaround Use Cisco-supported compact flash.CSCsw91323 During reload of the Cisco AXP AIM module, the boot fails with messages: Unable to load image, Unable to boot image.
Symptom During reload of the Cisco AXP AIM module, the boot fails and the following message appears: "Unable to load image Unable to boot image".
Conditions Rare occurrence during reload.
Workaround Do a filesystem check using the file check fsck command, before reloading the Cisco AXP AIM module. The check shows that everything is correct, and the module boots up properly.CSCsw92182 Pinging a sub interface using the name of the sub interface causes the source IP address of the interface to be used.
Symptom Pinging the sub interface name results in the IP address of the interface to be shown in the debug output of the Cisco ISR.
Conditions Pinging the subinterface, for example "ping 172.19.161.148 repeat 5 interface eth0:7" pings the source IP address of eth0 interface, instead of eth0:7.
Workaround Ping the IP address of the sub interface. Do not ping the name of the sub interface.CSCsx02536 In the guest OS, the routing table is populated using the "ip route" command. This command does not have the option of specifying the source IP of devices.
Symptom The routing table is only populated by Cisco AXP command "ip route". In this command the source IP of a device cannot be specified.
Conditions If an application is bound with multiple IP addresses (sub interfaces) then only the default interface is chosen for the routing table. This is different from the Linux version of command "ip route".
Workaround Increase the permissions in the development authorization file. To obtain a development authorization file, contact your Cisco Marketing representative. Package the application with the command route add in the startup script.CSCsx33477 An error message "Authorization document not found" occurs when uninstalling an application.
Symptom Error message "Authorization document not found" occurs during uninstallation.
Conditions An application is dependent upon another application or is itself a dependency for another application. Attempting to uninstall any of these applications fails. For example, the following steps result in an error:
1. Install application A.
2. Package application B and specify dependency on application A.
3. Install application B.
4. Package application C and specify dependency on application B.
5. Install application C.
6. Try to uninstall any of the applications A, B, or C.
Workaround Install a new version of Cisco AXP by issuing the software install clean command. This command clears the disk and removes all configurations.CSCsx39232 Specifying port 80 in a command, when Apache web server is running, causes the network module to hang.
Symptom Commands such as the following cause the network module to hang:
"copy log messages.log url ftp://<reachableip>:80/messages.log" —the command hangs and cannot be terminated using Ctrl+C.
Conditions The copy log command hangs when copying the log to a machine that has ftp and Apache running and the specified port is 80.
Workaround Do not use port number 80 in the URL within the command.
Symptom When multiple application packages use different authorization files, one application does not run. Uninstalling one of the packages causes a manifest signature verification error.
Conditions Two application packages are installed. Application package A using authorization file A. Application package B uses authorization file B. B is dependent on A. Application package A does not run. Trying to uninstall either package A or package B fails with a manifest signature verification error.
Workaround Reinstall Cisco AXP base OS using the boothelper. Package applications using one authorization file.CSCsm85157 Virtual instance contains show commands for Cisco add-on applications on which the application is not dependent.
Symptom A query of commands for an application in app-service mode displays show commands for Cisco add-on packages on which the application does not have a dependency.
For example, the show history iosapi command may be displayed for an application that is not dependent on the Cisco IOS API add-on package axp-iosapi.<platform>.<version>.pkg.
Conditions Multiple Cisco add-on packages installed with different dependencies.
Workaround .Ignore show commands that are not associated with an application. Executing these show commands displays nothing.
Symptom The error "TypeError: cannot concatenate 'str' and 'instance' objects" occurs during install/upgrade.
Conditions Using the sftp protocol to obtain a remote Cisco AXP package during a clean install or upgrade.
Workaround Use either the ftp or ftps protocol. For example: software install upgrade url ftp://ftp-server-ip-address/axp-package.pkg
The following sections describe the documentation available for the Cisco Application eXtension Platform and Cisco ISRs. Typically, these documents consist of hardware and software installation guides, Cisco IOS configuration and command references, system error messages, feature modules, and other documents for Cisco IOS Release.
Use these release notes with the documents listed in the following sections:
The following documents are specific to Cisco Application eXtension Platform. They are also listed in the Support section at: http://www.cisco.com/en/US/products/ps9701/index.html.
Hardware installation guides, configuration and command reference guides, and additional documents specific to the Cisco ISR routers are available at:
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. This guide lists all new and revised Cisco technical documentation. You can also subscribe to the guide using an RSS feed.
The following notices pertain to this software license.
OpenSSL/Open SSL Project
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).
This product includes cryptographic software written by Eric Young (firstname.lastname@example.org).
This product includes software written by Tim Hudson (email@example.com).
The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact firstname.lastname@example.org.
Copyright © 1998-2007 The OpenSSL Project. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)".
4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact email@example.com.
5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project.
6. Redistributions of any form whatsoever must retain the following acknowledgment:
"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)".
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT "AS IS"' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This product includes cryptographic software written by Eric Young (firstname.lastname@example.org). This product includes software written by Tim Hudson (email@example.com).
Original SSLeay License:
Copyright © 1995-1998 Eric Young (firstname.lastname@example.org). All rights reserved.
This package is an SSL implementation written by Eric Young (email@example.com).
The implementation was written so as to conform with Netscapes SSL.
This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (firstname.lastname@example.org).
Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgement:
"This product includes cryptographic software written by Eric Young (email@example.com)".
The word `cryptographic' can be left out if the routines from the library being used are not cryptography-related.
4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: "This product includes software written by Tim Hudson (firstname.lastname@example.org)".
THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The license and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license [including the GNU Public License].
CCDE, CCENT, CCSI, Cisco Eos, Cisco Explorer, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco TrustSec, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, 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 Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco 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. (1002R)
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.
© 2008-2009, Cisco Systems, Inc. All rights reserved.