Guest

Cisco Application Extension Platform

Release Notes for Cisco Application eXtension Platform (AXP) 1.1

  • Viewing Options

  • PDF (291.4 KB)
  • Feedback
Release Notes for Cisco Application eXtension Platform (AXP) 1.1.1

Table Of Contents

Release Notes for Cisco Application eXtension Platform (AXP) 1.1.1

Contents

System Requirements

Supported Hardware

Files in Cisco AXP 1.1.1

Cisco AXP Product Files

Cisco AXP Software Development Files

Upgrading to a New Software Release

Upgrading from Cisco AXP 1.0.5/1.0.6 to Cisco AXP 1.1.1

Determining the Software Version

Cisco AXP New Features and Enhancements

Cisco AXP 1.1.1 Perl Add-On File Changes

Cisco AXP 1.1.1 Swap Space of 4 GB

Cisco AXP 1.1.1 Packaging Tool

Caveats for Cisco AXP

Open Caveats- Cisco AXP Version 1.1.1

Resolved Caveats- Cisco AXP Version 1.1.1

Open Caveats- Cisco AXP Version 1.0.6

Resolved Caveats- Cisco AXP Version 1.0.6

Open Caveats- Cisco AXP Version 1.0.5

Resolved Caveats- Cisco AXP Version 1.0.5

Open Caveats- Cisco AXP Version 1.0.4

Resolved Caveats- Cisco AXP Version 1.0.4

Open Caveats - Cisco AXP Version 1.0.3

Resolved Caveats - Cisco AXP Version 1.0.3

Related Documentation

Software Documents

Platform-Specific Documents

Obtaining Documentation, Obtaining Support, and Security Guidelines

Trademarks and Licenses


Release Notes for Cisco Application eXtension Platform (AXP) 1.1.1


Revised: November 9, 2010, OL-14273-01

These release notes support the Cisco Application eXtension Platform (AXP). We recommend that you view the field notices for the version of Cisco IOS software associated with Cisco AXP to see if your software or hardware platforms are affected. If you have an account on Cisco.com, you can find field notices at http://www.cisco.com/warp/customer/tech_tips/index/cfn.html.

Contents

System Requirements

Cisco AXP New Features and Enhancements

Cisco AXP 1.1.1 Perl Add-On File Changes

Cisco AXP 1.1.1 Swap Space of 4 GB

Cisco AXP 1.1.1 Packaging Tool

Caveats for Cisco AXP

Related Documentation

Obtaining Documentation, Obtaining Support, and Security Guidelines

Trademarks and Licenses

System Requirements

This section describes the system requirements for Cisco Application Platform eXtension Version 1.1.1 and includes the following sections:

Supported Hardware

Files in Cisco AXP 1.1.1

Upgrading from Cisco AXP 1.0.5/1.0.6 to Cisco AXP 1.1.1

Determining the Software Version

Supported Hardware

Cisco Platforms
Cisco AXP Service Module SKU
Processor/Memory
Hard Disk
Compact Flash

Cisco 1841

Cisco 2801

Cisco 2811

Cisco 2821

Cisco 2851

Cisco 3825

Cisco 3845

AIM-APPRE-102-K9

300 MHz/256 MB

1 GB

Cisco 2811

Cisco 2821

Cisco 2851

Cisco 3825

Cisco 3845

NME-APPRE-302-K9

1.0 GHz/512 MB

80 GB

Cisco 2811

Cisco 2821

Cisco 2851

Cisco 3825

Cisco 3845

NME-APPRE-502-K9

1.0 GHz/1.0 GB

120 GB

Cisco 3825

Cisco 3845

NME-APPRE-522-K9

1.4 GHz/2.0 GB

160 GB


Files in Cisco AXP 1.1.1

Download Cisco AXP files from Cisco Application Extension Platform Version 1.1.

Files in Cisco AXP 1.1.1 are explained in the following sections:

Cisco AXP Product Files

Cisco AXP Software Development Files

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

Cisco AXP Product Files for AIM Service Modules

Compressed archive axp-k9.aim.1.1.1.tar.gz contains all package files associated with Cisco AXP on AIM service modules. The package files are shown in Table 1.

Table 1

Filename
Purpose

axp-helper-k9.aim.1.1.1

Cisco AXP Rescue Helper image. Aids application installation on AIM service modules when necessary.

axp-k9-aim.1.1.1.pkg

Main package for installing Cisco AXP on AIM service modules.

axp-k9-aim.1.1.1.prt1

Package payload containing all data and executable files for the installer subsystem associated with Cisco AXP on AIM service modules.

axp-installer-k9.aim.1.1.1.prt1

Package payload containing all data and executable files for the installer subsystem associated with Cisco AXP on AIM service modules.


Cisco AXP 1.1.1 Product Files for AIM

Cisco AXP Product Files for NME Service Modules

Compressed archive axp-k9.nme.1.1.1.tar.gz contains all package files associated with Cisco AXP on AIM service module. The package files are shown in Table 2.

Table 2

Filename
Purpose

axp-helper-k9.nme.1.1.1

Cisco AXP rescue helper image. Helps to install the application on Cisco NME service modules when necessary.

axp-k9.nme.1.1.1.pkg

Main package for installing the Cisco AXP on Cisco NME service modules.

axp-k9.nme.1.1.1.prt1

Package payload containing all data and executable files for a full installation of the Cisco AXP on Cisco NME service modules.

axp-installer-k9.nme.1.1.1.prt1

Package payload containing all data and executable files for the installer subsystem associated with the Cisco AXP on Cisco NME service modules.


Cisco AXP 1.1.1 Product Files for NME

Cisco AXP Software Development Files

Cisco AXP software development files:

Cisco AXP Software Development Kit (SDK)

Cisco AXP Software Development Files for VMware

Cisco AXP Software Development Files for Add-ons on AIM Service Modules

Cisco AXP Software Development Files for Add-ons on NME Service Modules

Cisco AXP Software Development Kit (SDK)

Compressed archive axp-sdk.1.1.1.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.1.tar.gz contains the Cisco AXP Software Development Files for VMware.

The package files are shown in Table 3.

Table 3

Filename
Purpose

axp-k9.vmw.1.1.1.vmdk

Cisco AXP VMware disk image file.

axp-vm.1.1.1.vmx

Cisco AXP VMware virtual hardware configuration file.


Cisco AXP 1.1.1 Software Development Files for VMware

Cisco AXP Software Development Files for Add-ons on AIM Service Modules

Compressed archive axp-k9.aim.addon.1.1.1.tar.gz contains Cisco AXP software development files for add-ons on AIM service modules. The package files are shown in Table 4.

Table 4 Cisco AXP 1.1.1 Software Development Files for AIM Add-On Software

Filename
Purpose

axp-app-dev.aim.1.1.1.pkg

Package for installing the Application Development add-on associated with Cisco AXP on AIM service modules.

axp-app-dev.aim.1.1.1.prt1

Package payload containing all data and executable files for the Application Development add-on associated with Cisco AXP on AIM service modules.

axp-cli-plugin.aim.1.1.1.pkg

Package for installing the Command Language Interpreter add-on associated with Cisco AXP on AIM service modules.

axp-cli-plugin.aim.1.1.1.prt1

Package payload containing all data and executable files for the Command Language Interpreter add-on associated with Cisco AXP on AIM service modules.

axp-eemapi.aim.1.1.1.pkg

Package for installing Cisco IOS Event Notification add-on associated with Cisco AXP on AIM service modules.

axp-eemapi.aim.1.1.1.prt1

Package payload containing all data and executable files for Cisco IOS Event Notification add-on associated with Cisco AXP on AIM service modules.

axp-iosapi.aim.1.1.1.pkg

Package for installing Cisco IOS Configuration add-on associated with Cisco AXP on AIM service modules.

axp-iosapi.aim.1.1.1.prt1

Package payload containing all data and executable files for Cisco IOS Configuration add-on associated with Cisco AXP on AIM service modules.

axp-vserial.aim.1.1.1.pkg

Package for installing the IOS Serial Device add-on associated with Cisco AXP on AIM service modules.

axp-vserial.aim.1.1.1.prt1

Package payload containing all data and executable files for the IOS Serial Device add-on associated with the Cisco AXP on AIM service modules.

axp-perl-5.8.8.aim.1.1.1.pkg

Package for installing a Perl Language Interpreter add-on associated with the Cisco AXP on AIM service modules.

axp-perl-5.8.8.aim.1.1.1.prt1

Package payload containing all data and executable files for a Perl Language Interpreter add-on associated with the Cisco AXP on AIM service modules.

axp-ssh-4.6p1-k9.aim.1.1.1.pkg

Package for installing a Secure Shell add-on associated with Cisco AXP on AIM service modules.

axp-ssh-4.6p1-k9.aim.1.1.1.prt1

Package payload containing all data and executable files for a Secure Shell add-on associated with the Cisco AXP on AIM service modules.

axp-tomcat5.aim.1.1.1.pkg

Package for installing a Tomcat java-based web server add-on associated with Cisco AXP on AIM service modules.

axp-tomcat5.aim.1.1.1.prt1

Package payload containing all data and executable files for a Tomcat java-based web server add-on associated with the Cisco AXP on AIM service modules.


Cisco AXP Software Development Files for Add-ons on NME Service Modules

Compressed archive axp-k9.nme.addon.1.1.1.tar.gz contains Cisco AXP software development files for add-ons on NME service modules. The package files are shown in Table 5.

Table 5

Filename
Purpose

axp-app-dev.nme.1.1.1.pkg

Package for installing the Application Development add-on associated with the Cisco AXP on Cisco NME service modules.

axp-app-dev.nme.1.1.1.prt1

Package payload containing all data and executable files for the Application Development add-on associated with the6 Cisco AXP on Cisco NME service modules.

axp-cli-plugin.nme.1.1.1.pkg

Package for installing the Command Language Interpreter add-on associated with Cisco AXP on Cisco NME service modules.

axp-cli-plugin.nme.1.1.1.prt1

Package payload containing all data and executable files for the Command Language Interpreter add-on associated with Cisco AXP on Cisco NME service modules.

axp-eemapi.nme.1.1.1.pkg

Package for installing Cisco IOS Event Notification add-on associated with Cisco AXP on Cisco NME service modules.

axp-eemapi.nme.1.1.1.prt1

Package payload containing all data and executable files for the IOS Event Notification add-on associated with Cisco AXP on Cisco NME service modules.

axp-iosapi.nme.1.1.1.pkg

Package for installing Cisco IOS Configuration add-on associated with Cisco AXP on Cisco NME service modules.

axp-iosapi.nme.1.1.1.prt1

Package payload containing all data and executable files for the IOS Configuration add-on associated with Cisco AXP on Cisco NME service modules.

axp-vserial.nme.1.1.1.pkg

Package for installing Cisco IOS Serial Device add-on associated with the Cisco AXP on Cisco NME service modules.

axp-vserial.nme.1.1.1.prt1

Package payload containing all data and executable files for Cisco IOS Serial Device add-on associated with the Cisco AXP on Cisco NME service modules.

axp-perl-5.8.8.nme.1.1.1.pkg

Package for installing a Perl Language Interpreter add-on associated with Cisco AXP on Cisco NME service modules.

axp-perl-5.8.8.nme.1.1.1.prt1

Package payload containing all data and executable files for a Perl Language Interpreter add-on associated with Cisco AXP on Cisco NME service modules.

axp-ssh-4.6p1-k9.nme.1.1.1.pkg

Package for installing a Secure Shell add-on associated with Cisco AXP on Cisco NME service modules.

axp-ssh-4.6p1-k9.nme.1.1.1.prt1

Package payload containing all data and executable files for a Secure Shell add-on associated with Cisco AXP on Cisco NME service modules.

axp-tomcat5.nme.1.1.1.pkg

Package for installing a Tomcat Java-based Web Server add-on associated with Cisco AXP on Cisco NME service modules.

axp-tomcat5.nme.1.1.1.prt1

Package payload containing all data and executable files for a Tomcat Java-based Web Server add-on associated with Cisco AXP on Cisco NME service modules.


Files included in Cisco AXP 1.1.1 Cisco NME Add-On Packages

Upgrading to a New Software Release

Upgrading from Cisco AXP 1.0.5/1.0.6 to Cisco AXP 1.1.1

To upgrade from Cisco AXP 1.0.5/1.0.6 to Cisco AXP 1.1.1:

a. Copy the installer payload file (axp-installer.k9.<nme/aim.1.1.1>.prt1) to the same FTP directory as the Cisco AXP package. The FTP directory contains a package file such as axp-k9.nme/aim.1.1.1.pkg and a corresponding payload file axp-k9.nme/aim.1.1.1.prt1 with other add-on packages.

b. Install the Cisco AXP package using the software install upgrade command. For upgrading and downgrading various software versions on Cisco AXP, refer to the Cisco AXP User Guide. For more information on this command, see the Cisco AXP Command Reference.


NoteTo upgrade from Cisco AXP 1.0.5/1.0.6 to Cisco AXP 1.1.1, use the Cisco AXP 1.1.1 Software Development Authorization Certificate to package/bundle your application.

After upgrading to Cisco AXP 1.1.1, verify that the system is running on Cisco AXP 1.1.1.

After the system is upgraded to 1.1.1, for your next installation use the Cisco AXP 1.1.1 Software Development Authorization Certificate to package/bundle an application.


To downgrade to an earlier version of Cisco AXP:

Use the software install upgrade command. The software install downgrade command is not currently supported. For more information, see the Cisco Application eXtension Platform Command Reference and the Cisco Application eXtension Platform User Guide.

Determining the Software Version

To determine which version of the Cisco AXP software is currently running on your Cisco ISR router, log into the router, and enter the show version EXEC command. The following sample output from the show version command indicates the version number on the second output line.

Application eXtension Platform (AXP) version (1.1.1)
Technical Support: http://www.cisco.com/techsupport/ Copyright (c) 1986-2008 by Cisco 
Systems, Inc.

Cisco AXP New Features and Enhancements

For a list of new features and enhancements in the latest Cisco AXP release, refer to the document Cisco Application eXtension Platform Feature and Release History.

Cisco AXP 1.1.1 Perl Add-On File Changes

The Perl add-on package, for Cisco AXP version 1.1.1 and higher, contains path file names that include "i586" instead of "i686".

Example (Cisco AXP 1.1.1)

In this example, the perl files for Cisco AXP 1.1.1 have path names that include "i586". The files in the @INC directory are:

@INC:
/usr/local/lib/perl5/5.8.8/i586-linux-thread-multi
/usr/local/lib/perl5/5.8.8
/usr/local/lib/perl5/site_perl/5.8.8/i586-linux-thread-multi/
/usr/local/lib/perl5/site_perl/5.8.8
/usr/local/lib/perl5/site_perl

Example (Cisco AXP 1.0.6)

In this example, the perl files for Cisco AXP 1.0.6 have path names that include "i686". The files in the @INC directory are:

@INC:
    /usr/local/lib/perl5/5.8.8/i686-linux-thread-multi
    /usr/local/lib/perl5/5.8.8
    /usr/local/lib/perl5/site_perl/5.8.8/i686-linux-thread-multi
    /usr/local/lib/perl5/site_perl/5.8.8
    /usr/local/lib/perl5/site_perl

Cisco AXP 1.1.1 Swap Space of 4 GB

The boot helper must be installed if an application requires 4 GB swap space.


Note It is not necessary to install a boot helper on a new factory preloaded application service module with Cisco AXP 1.1 host OS.


The difference in available memory using 2 GB or 4 GB is shown in Table 6 and Table 7 below.

To set 4 GB swap space available for the application:

Install the Cisco AXP 1.1 host OS using the boot helper. See the "Installing Software using a Helper Image" section in the Cisco Application eXtension Platform User Guide.

To set 2 GB of swap space available for the application, use the software install clean or software install upgrade command to install the Cisco AXP 1.1 host OS. See the "Installing and Upgrading" section in the Cisco Application eXtension Platform User Guide.

Table 6 Available Virtual Memory (2 GB Swap Space)

Service Module Platform
Available Virtual Memory (MB)
Virtual Memory (MB)
Physical Memory (MB)
Host OS Memory (MB)

AIM-APPRE-102-K9

176

0

256

80

NME-APPRE-302-K9

2332

2412

512

80

NME-APPRE-502-K9

2844

2924

1024

80

NME-APPRE-522-K9

3868

3948

2048

80


Table 7 Available Virtual Memory (4 GB Swap Space)

Service Module Platform
Available Virtual Memory (MB)
Virtual Memory (MB)
Physical Memory (MB)
Host OS Memory (MB)

AIM-APPRE-102-K9

176

0

256

80

NME-APPRE-302-K9

4232

4312

512

80

NME-APPRE-502-K9

4744

4824

1024

80

NME-APPRE-522-K9

5768

5848

2048

80


Cisco AXP 1.1.1 Packaging Tool

The packaging tool script pkg_build.sh appears to freeze when packaged with the Cisco AXP 1.1.1 SDK.

Symptom

Script pkg_build.sh appears to freeze.

Conditions

The log file core.log displays a message similar to the one shown below:

".../axp-sdk.1.1.1/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:"

Workaround


1. During packaging, exit from the package build script after the following warning message appears:

Do you wish to continue packaging without these files(y,n)? 

a. Enter n.

2. The grep command is required. If it is not installed on your development system, install the appropriate RPM that supports the grep command.

3. Go into the root user for your system and create the following symbolic link, either as the root user or by using the sudo command:

ln -s /lib/libpcre.so.0 /usr/lib/libpcre.so

4. Retry packaging using the pkg_build.sh script.


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/cgi-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.)  


Open Caveats- Cisco AXP Version 1.1.1

Resolved Caveats- Cisco AXP Version 1.1.1

Open Caveats- Cisco AXP Version 1.0.6

Resolved Caveats- Cisco AXP Version 1.0.6

Open Caveats- Cisco AXP Version 1.0.5

Resolved Caveats- Cisco AXP Version 1.0.5

Open Caveats- Cisco AXP Version 1.0.4

Resolved Caveats- Cisco AXP Version 1.0.4

Open Caveats - Cisco AXP Version 1.0.3

Resolved Caveats - Cisco AXP Version 1.0.3

Resolved Caveats - Cisco AXP Version 1.0.3

Open Caveats- Cisco AXP Version 1.1.1

CSCsr87787 File ownership changes in guest environment when upgrading the 
application.

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.

Workaround   In the startup script change the file ownership to a desired value. Changing file ownership in the startup script is only required when the users are different from root, and the user changes the file ownership.

CSCsu21866 Upgrade expects the wrong installer file and fails 

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.

Workaround   Repackage the bundle using the pkg_bundle.sh tool, and specify the Cisco AXP host OS package as the last entry in the sequence of packages to be bundled.

CSCsu09203 Application fails to appear online after an upgrade 

Symptom    After upgrading an application to a newer version, the application does not appear online. The show software version command does not show the application as installed.

Conditions   Occurs for some application upgrades when the upgraded application does not contain a file that was present in a previous version of the application.

Workaround   When a new version of an application does not contain a file that was in a previous version of the application, add a dummy file in the new version of the application. The dummy file has the same name as the file name used in the previous version of the application.

Resolved Caveats- Cisco AXP Version 1.1.1

There are no resolved caveats for this version.

Open Caveats- Cisco AXP Version 1.0.6

There are no open caveats for this version.

Resolved Caveats- Cisco AXP Version 1.0.6

CSCso45164 /dev/rtc device disappears in vserver after addition of second vserver

Symptom    The /dev/rtc device disappears from the guest environment

Conditions   Problem was seen happening after a second application was installed on the system. The /dev/rtc device of the first application disappeared and the second application can see its /dev/rtc device.

Workaround   None.

Further Problem Description:

Installing more applications may cause previously installed application's /dev/rtc device to disappear.

CSCso48376 Removal of ios_config event has no effect if username is not configured.

Symptom    Remove, change, or add an ios_config type event from CLI has no effect.

Workaround   Configure username/password with proper previledge(15) and configure the name and password in Service module as well.

CSCso56053 Incorrect error message when trying to install an add-on using upgrade C

Symptom    When the user tries to install an add-on package on the system using "software install upgrade" instead of the correct CLI "software install add", the system prints an incorrect error message instead of a more meaningful message indicating that this action is not permitted. Following is the error message that the user will see:

TypeError: raise: arg 3 must be a traceback or None

Conditions   This happens only when the user tries to install an application using a wrong CLI.

Workaround   Use the correct CLI, "software install add".

CSCso59201 Resource manager cannot handle corrupt filenames.

Symptom    When the packaged application contains files with corrupted filenames, the resource manager fails to install any new add-ons or upgrades.

Conditions   This happens when the package contains files with corrupted filenames, such as filenames containing escape characters, white spaces, or control characters.

Workaround   Remove all white spaces, escape characters, or control character from the filenames.

CSCso74355 Log level errors CLI do not work.

Symptom    When user configures the application log level to be "error", logging fails.

Conditions   The user makes the configuration by using the following command (with an "s" in the word error):

> configure terminal

conf> app-service <app>

conf-app> log level errors

Workaround   The user should use the following command without an "s" in the word "error":

conf-app> log level errors

CSCso15624 CLI plugin activation causes user to be kicked out to the router prompt.

Symptom    When user issues a plug-in CLI command, the CLI console is being kicked out to the router prompt.

Conditions   This issue is caused when the plug-in CLI is activated in either one of the following two possible error conditions:

1. The CLI action shared library loading problem.

2. The CLI action has seg fault.

These conditions should be checked and verified by the plug-in CLI developers.

Workaround   Check the CLI action to ensure the two conditions above are causing the problem and fix them.

CSCso36155 Upgrade does not work for manifest only changes.

Symptom    Customer changes the resource limits of an application but does not change any content, re-packages the application with different version number and upgrades the application using "software install upgrade". After reboot "show resource limits" still shows old resource values.

Workaround   Touch a dummy file and then repackage the application with new resource limits. If at least one file is different from the old version, upgrade will update the manifest file and after reboot "show resource limits" will have correct values for the application.

CSCso43978 `no shutdown' on vserver not working

Symptom    A given vserver for an installed application will not start if this vserver is "down". Typically, the vserver will not start after the system reboots after the installation. The following message can be seen in messages.log:

<14>Feb 29 15:37:50 localhost [App1]: invalid parameters: 'space_used' is larger than 
'space_total'

Conditions   The developer specified a value for the --disk-limit parameter at the time of application packaging which is syntactically correct but specifies a limit that is actually less than the amount of data to be packaged.

When this occurs with an SDK that does not have a fix for this problem, the following errors take place:

1. The packaging tool accepts the erroneous value for --disk-limit and creates the package.

2. The developer installs the package on the blade and the installer goes through.

3. After the installation, the vserver attempts to start and the vserver logic prevents the vserver from starting due to the configured limit (--disk-limit) being exceeded by the size of the data present in the vserver.

Workaround   To prevent the erroneous behavior, the developer must provide a disk-limit greater than the data to be packaged. Use the linux "du" command to figure out how much space is required.

CSCsl01618 Always clear `vserver run' file if `vserver start' returns error.

Symptom    If application startup fails, the log message may still show application started success. The CLI may report that the application is online when it is really not.

Conditions   Application startup fails due to bad startup script or system error.

Workaround   No work around for the incorrect log message. If CLI is displaying the application as online when it is not, one can try connect console to the application. This will update the state shown on the CLI.

CSCso91674 Syslog and timer events fail. EEM Errors in /var/log/messages.log

Symptom    EEM events are not registered properly sometimes. EEM events are not received after reload and an additional reset is required.

Conditions   Application names contain "_" (underscore) character.

Workaround   Repackage applications using names that do not contain "_" (underscore) character. Additional reset is needed to restart the EEM event delivery service.

CSCsq37639 Connect console fails when link using absolute path.

Symptom    Command connect console fails though proper link to files were created in post install script.

Conditions   Absolute links to files created in the post-install.sh file fail. For example: `ln -s /bin/login.sh /bin/console'

Workaround   Create relative links to the files. Use the following link:

`ln -s login.sh /bin/console'

CSCsq52222 java.lang.InterruptedException on show tech-support with Ctrl+C

Symptom    When `show tech-support' CLI is used with Ctrl+C keys, the CLI output throws java.lang.InterruptedException.

Conditions   Hit Ctrl+C keys after entering the CLI `show tech-support' on app-services. Software: Application eXtension Platform (AXP) version (1.0.4).

Workaround   None.

CSCsq56199 Copy log CLI fails to throw error.

Symptom    The copy log CLI does not provide a failure message when the user attempts to copy a log file that does not exist.

Conditions   This defect affects AXP version 1.0.4 and earlier versions. The defect occurs when the user specifies a log file that does not exist on the copy log CLI.

Workaround   None.

CSCsq88119 Installing a second wildcard application makes the first application 
loose its configured value.

Symptom    CLI configs for other applications disappear when installing or uninstalling third party applications.

Conditions   After a new application is installed, previously configured CLI changes for other applications are lost. This behavior is also observed when an application is uninstalled. The old configs can be located in startup-config, but they are missing from the running-config.

None.

CSCso35807 Service using domain socket must validate socket path size.

Symptom    Application with the application name containing 20 to 32 characters will not have working CLI plug-in capability

Conditions   CLI plug-in fails, if an application name contains 20 to 32 characters.

Workaround   Change the application name with a new name containing less than or equal to 19 characters.

CSCsq39715 app-service exec and config missing command when two add-on packages 
have same name.

Conditions   This happens when two add-on packages have the same name and the names are in upper case for one package and lower case for the other, for example: APP2 and App2. As a result of same package names:

show runn fails with no output.

config under app-server fails to prompt with default configuration commands (for example, bind, hostname,ip limit)

Workaround   Do not package same name add-on package.

Open Caveats- Cisco AXP Version 1.0.5

CSCso91674 Syslog and timer events fail. EEM errors in /var/log/messages.log

Symptom    EEM events are not registered properly sometimes. EEM events are not received after reload and an additional reset is required.

Conditions   This happens if the application names contain "_" (underscore) character.

Workaround   Repackage applications using names that do not contain "_" (underscore) character. Additional reset is needed to restart the EEM event delivery service.

Resolved Caveats- Cisco AXP Version 1.0.5

CSCsq49465 - ntp sync takes 20 minutes on router/service module full power down/up 

Symptom    If the router and service module are physically powered down, and left to sit over a period of hours, the ntp sync time between the router and the service module can take up to 20 minutes or longer on powering back the router and service module.

Conditions   The service module has the ISR as its ntp master, and the ISR syncs to an external ntp master. This happens when both the ISR and service module are physically powered down and then powered up.

Workaround   None.

CSCsq49482 iosapi daemon crashes and fails to restart

Conditions   This happens when application that depends upon axp-iosapi add-on package, has a name containing more than 15 characters. As a result, the memory storage holding the application name does not have enough memory space allocated. Hence, data corruption occurs.

Workaround   Use shorter application name with less than 15 characters when building the application package that depends upon axp-iosapi add-on package.

CSCsq25612 Unable to display run config after installing an addon package with 
long name

Symptom    Running configuration is not displayed when installing add-on package with application name containing 32 characters.

Conditions   This happens when using the software install add command to install a package with a long application name containing more than 15 characters. As a result, the "show run" command does not display the running configuration.

Workaround   Use shorter application name with less than 15 characters when building the add on package.

CSCso43087 ip_forward turned off by default

Symptom    IP packet forwarded to the blade can be routed back to the router.

Conditions   When using packet replication technologies from IOS, NAM or RITE packet, the IP address of these packets are not the same as the blade's IP address. Application/driver does not read the packet and IP routing sends the packet back to the IOS router. This should not affect operation just consuming CPU processing and bandwidth of the interface between Cisco IOS and blade.

Workaround   None.

Open Caveats- Cisco AXP Version 1.0.4

CSCso45164 The "/dev/rtc" device disappears in vserver after addition of second 
vserver.

Symptom    The /dev/rtc device disappears from the guest environment.

Conditions   This problem happens after the installation of a second application on the system. The /dev/rtc device of the first application disappeared, but the second application can see its /dev/rtc device.

Workaround   There is no known workaround for this issue.

Further Problem Description: Installing more applications may cause previously installed application's /dev/rtc device to disappear.

CSCso36155 Upgrade does not work for manifest ONLY changes.

Symptom    Customer changes the resource limits of an application but does not change any content, re-packages the application with different version number and upgrades the application using "software install upgrade". After reboot "show resource limits" still shows old resource values.

Workaround   The workaround is for the customer to touch a dummy file and then repackage the application with the new resource limits. If at least one file is different from the old version upgrade will update the manifest file and so after reboot "show resource limits" will have correct values for the application.

Resolved Caveats- Cisco AXP Version 1.0.4

CSCsm67655 EEM Apps takes a long time to come online.

Symptom    There is a sequential delay if eemapi add-on package is installed. When the installation of an application depends on Cisco axp-eemapi add-on package, that application takes about 10 to 11 minutes to come online. Installing a second application takes about 20 plus minutes to come online.

Conditions   This happens when a Cisco IOS router prompts confirmation "erase flash: [confirm]" when "erase flash:" CLI command is issued. The 1.0.3 eemapi add-on package during startup, it does not expect the confirmation prompt, hence, it times out after 10 minutes.

Workaround   axp-eemapi..1.0.3 add-on package will not be released for version 1.0.3. User should use version 1.0.1.

CSCsl02585 Bundle script throw errors and exits when there is no disk space

Symptom    The bundle package is packed and signed correctly but the installation will fail because the disk space on the development environment is full.

Conditions   This happens when disk space is out and the payload is missing in the bundled package. This error shows up, If during packaging of one of the many add-on packages, the packaging fails to copy due to full disk space on the development environment.

Workaround   Make sure there is at least twice the total disk space needed by all add-on packages before running packaging tool.

CSCsm47140 Javalin: CLI: ip ssh server does not bring it up to RUNNING state

Symptom    The config CLI "ip ssh server" under an application's ape-service mode, does not take effect in random times. That results in the application SSH server not starting, even though the config CLI is registered and seen in "show running-config". This case arises when the application container is running into high CPU usage.

Conditions   To turn on the application SSH server, in the CLI console:

CLI> config terminal

CLI(config)> app-service myapp

CLI(config-myapp)> ip ssh server

Normally, users should see that the application is running by doing:

CLI> app-service myapp

CLI(exec-myapp)> show ssh-server

Application SSH Server

Status: RUNNING

But in some cases when the application is in high CPU usage, it might report that the application SSH server is "NOT RUNNING"

Workaround   Since this is a random failure, users can issue the same config CLI again until the SSH server reports "RUNNING".

CSCsm71620 Validation Failed: Development authorization not found

Symptom    Installation failure with the following error:

Validation Failed: Development authorization not found

Conditions   When dev authorization file is not named as "dev_authorization.sig".

Workaround   Rename dev authorization file to "dev_authorization.sig".

CSCsm85157 Vserver should only have the CLIs that are applicable to it

Symptom    When customer installs application that depends upon Cisco add-on package. The CLIs associated with that add-on, if any, should only be displayed in that Vserver Instance. However, if customer install another applications that depends on another Cisco add-on which has its own CLIs, those CLIs also shows on the other application which does not depend on it.

Conditions   When multiple Cisco add-on packages are installed and each one has its own set of CLIs, the CLIs are displayed to all the Vserver Instances regardless whether the application has dependency on them or not.

Workaround   Customer needs to ignore the CLIs under app-service that is not applicable to their applications.

CSCsm97701 AXP Service API Hangs when ntp server is set

Symptom    Service API hangs, no returns from the call.

Conditions   This happens when issuing ntp server x.x.x.x prefer CLI through Service API.

Workaround   Implement a timeout that exits the call after a period of waiting. The actual CLI config is already processed and executed on the Blade and it is only the Service API call that fails to return.

CSCsm92964 Session to blade hangs by using CLI

Symptom    When install eemapi application or vserial application, after boot up and console become ready the CLI console freeze

Conditions   This is problem affects all the versions.

Workaround   There is no workaround.

CSCso08068 CLI commands on service module not working properly

Symptom    Slow response of show run, show resource limit and "[no] limit disk utilization" commands

Conditions   This happens when an Virtual Instance is populated with a application image.

Workaround   This is a performance issue that does not have other side effect. Currently there is no work around.

CSCso34815 CLI console hangs upon reboot

Symptom    The CLI console hangs at 3% at the progress bar, upon reboot of a fresh install application.

Conditions   This issue happens if the customer is creating their application package with an application name that is too long (for example, 29 characters).

Workaround   Reduce the application name to a shorter name. Name of 19 characters has been tested and works.

Open Caveats - Cisco AXP Version 1.0.3

CSCsm67655 EEM Apps takes a long time to come online

Symptom    When installing an application depends on Cisco axp-eemapi add-on package, that application takes about 10 to 11 minutes to come online. If installing 2nd applications, it takes about 20+ minutes to come online. There is a sequential delays if eemapi add-on package is installed.

This happens when a Cisco IOS router prompts confirmation "erase flash: [confirm]" when "erase flash:" CLI command is issued. The 1.0.3 eemapi add-on package during startup, it does not expect the confirmation prompt, hence, it times out after 10 min.

Workaround   axp-eemapi.<aim/nme>.1.0.3 add-on package will not be released for version 1.0.3. Customer should stay with existing axp-eemapi.<aim/nme>.1.0.1 package for Cisco IOS Event Notification feature.

Resolved Caveats - Cisco AXP Version 1.0.3

CSCsl75082 ICW Upgrade requires boothelper and configuration change

Symptom    Customer who wishes to do a clean install to an AIM 1.0.1 image from older images may encounter kernel signature mismatch errors during the boot process.

Conditions   Problem is seen with 1.0.1 image in AIM with primary bootloader configured as default bootloader. Images prior to 1.0.1 may also be affected.

Workaround   The workaround is to change the bootloader configuration to use secondary bootloader.

Further Problem Description: The primary bootloader included in 1.0.1 image is defective and unusable.

CSCsl05305 Packaging fails with a source directory name with space 

Symptom    When the directory name of the source value contains a space, the packaging fails.

Conditions   Space in the name of the source directory.

Workaround   Rename the directory without a space as a work around.

CSCs115789 Show history iosapi c can not do auto-complete.

Symptom    No output for show history iosapi if the user uses the auto complete

Conditions   This error occurs when trying to do a show command with partial names for parameters

For example: show history iosapi c instead of show history iosapi config 

Workaround   Use full names for parameters like config instead of c or con or conf. Further, after executing a show command with partial parameter, it could be successfully executed again by using the up arrow to get to the previous command to execute it again. The second time the auto-completion takes effect.

CSCsl14407 Installing vserial ciscoadd-on causes 3rd party app installation to 
fail

Symptom    Cannot install a package due to resource limitation errors.

Conditions   When AXP VSerial Add-on package is installed and the following command has been executed: show serial devices

Workaround   There is no workaround.

CSCsl80156 Non CLI entries to /etc/passwd and /etc/group not persisted after 
reload 

Symptom    When customer has its own post-install.sh to add user and password or runtime add users as well. These new users are not persisted.

Conditions   Since post-install.sh only execute once, there is no way for it to add user again

Workaround   They can use post-install.sh to add user(s), but it needs to be saved in the /opt/cli_server/original_config/passwd. Here is an example of post-install.sh:

#!/bin/bash
ln -s /bin/bash /bin/console
useradd testuser1 -p $1$encryptedpasswd1

useradd testuser2 -p $1$encryptedpasswd2
user1=`cat /etc/passwd | grep testuser1`

user2=`cat /etc/passwd | grep testuser2`

/bin/unprotect_host  /opt/cli_server/original_config/passwd
echo "$user1" >> /opt/cli_server/original_config/passwd

echo "$user2" >> /opt/cli_server/original_config/passwd

If they are performing useradd after vserver is up and running (i.e. go into Linux shell to do useradd or manually add entry in the /etc/passwd file). They need to first unprotect /opt/cli_server/original_config/passwd file first, then manually copy over the entries into that file. /bin/unprotect /opt/cli_server/original_config/passwd

vi /opt/cli_server/original_config/passwd (then copy entries in)

CSCsm09058 Manifest file becomes corrupt when application upgrade with different 
cert.

Symptom    If an application is upgraded with new development authorization and certificate files the blade becomes unusable. After the upgrade if the user wants to use any of the "software install" commands the CLI fails with an error: Validation Failed: Signature validation failed for file /sw/installed/manifest/<manifest_name>.sig AesopError.AesopInstallerError: Manifest signature validation failed for <manifest_name>.sig

Conditions   This problem happens only when the user changes the application's development authorization and certificate files and upgrades the application using "software install upgrade". If the user uses "software install add" to install the application he will not have this issue. This problem affects 1.0.1 version only.

Workaround   There is no workaround.

CSCsm11276 Router crashed during the IOS EEM configuration

Symptom    Router reload when the NM blade boot up.

Conditions   When install multiple eemapi applications on the blade, occasionally the router will reload itself.

Workaround   Install only single eemapi application.

Further Problem Description: Multiple eemapi applications cause underlying eem startup code try to configure IOS concurrently. This may cause conflict and result in router reload.

CSCsh86692 Static route not in routing table after shut/no shut interface

Symptom    conf t se-100-0-1-2(config)> ip route 4.0.0.0 255.255.255.0 200.0.0.1 se-100-0-1-2(config-interface)> shut se-100-0-1-2(config-interface)> no shut

After shut, and no shut, the ip routing table is disappeared for the entry of 4.0.0.0

Conditions   This problem occurs in version 1.0.1 and can be reproduced.

Workaround   There is no workaround.

CSCsi77373 Failed copy command does not give error message

Symptom    When use CLI copy command, it does not print any error message and just return. This leave customer has no indication that the copy command failed.

Conditions   When the copy command can not be executed successfully due to remote setup etc. but CLI leaves no indication to user that some error has occurs.

Workaround   There is no workaround.

CSCsm18304 CLI allows default route to be removed

Symptom    The Integrated-Service-Engine (ISE) default route setup on the router for the blade via the Cisco IOS command 'service-module ip default gateway' establishes the default route for the eth0 interface. The AXP CLI allows the user to remove this default route via 'no ip route 0.0.0.0 0.0.0.0 <gateway ip>, and then add their own default route. This allowance leads the user to believe the he can change the default route of the blade which is not possible. The removed route is restored when the blade is reloaded since the data is provided by the router.

Conditions   When user do the AXP CLI: >config t >no ip route 0.0.0.0 0.0.0.0 <gateway ip> and then add their own default route. After reload, the original default route (configured in IOS) is restored back.

Workaround   Do not delete default router in AXP. It should be changed in IOS side and reflect in the AXP side.

CSCsm01287 Cannot read upper case hostname using IOSAPI within show run incl

Symptom    When user using JAVA API, that do filter spec with mixed lower and upper case value. The result are "no data found".

Conditions   This only happen in Java API and only happens when the filter spec is included and the value has mixed cases.

Workaround   Use include command not filter to specific value (which has mixed case)

CSCsm22156 Service APIs not working with Single install of OS,addon,and app 

Symptom    Particular CLIs do not show up after a clean installation. For example:

1. "ip ssh ..." CLIs for the app-dev and app-ssh packages

2. Plugin CLIs written by application developer

Conditions   This problem arises if the application developer bundles the AXP OS package, add-on packages and their application in a single install bundle and install.

Workaround   Application developers should first install the AXP OS package, then install the rest of the bundle (add-on and application).

Related Documentation

The following sections describe the documentation available for the Cisco Application eXtension Platform and Cisco ISR routers. 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:

Software Documents

Platform-Specific Documents

Software Documents

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.

Cisco Application eXtension Platform 1.1 Feature and Release History

Cisco Application eXtension Platform 1.1 Developer Guide

Cisco Application eXtension Platform 1.1 User Guide 

Cisco Application eXtension Platform 1.1 Command Reference

Open Source Software Licenses for Cisco AXP 1.1

Platform-Specific Documents

Hardware installation guides, configuration and command reference guides, and additional documents specific to the Cisco ISR routers are available at:

Cisco Integrated Service Routers

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.

Trademarks and Licenses

Cisco Trademarks

Open Source Licenses

For open source license information, see Open Source Software Licenses for Cisco AXP 1.1.