Guest

Cisco Application Extension Platform

Release Notes for Cisco Application eXtension Platform (AXP) 1.5.2

  • Viewing Options

  • PDF (389.0 KB)
  • Feedback
Release Notes for Cisco Application eXtension Platform (AXP) 1.5.2

Table Of Contents

Release Notes for Cisco Application eXtension Platform (AXP) 1.5.2

Contents

System Requirements

Cisco IOS Software Release

Supported Hardware

Files in Cisco AXP 1.5.2

Cisco AXP Product Files for SM SRE Service Modules

Cisco AXP Software Development Kit (SDK)

Upgrading and Downgrading to a New Software Release

Packaging Your application Using 1.5.2 SDK

Clean Installing AXP 1.5.2 Release

Upgrading from Cisco AXP 1.5.1 to Cisco AXP 1.5.2

Upgrading from Cisco AXP 1.1.x to Cisco AXP 1.5.2

No Downgrading from Cisco AXP 1.5.2 to Cisco AXP 1.1.x

Clean Installing Cisco AXP 1.1.x on Cisco AXP 1.5

Verifying the MAC address of a Network Module (for Cisco AXP 1.5.1 and 1.5.2)

Determining the Cisco AXP Software Version

New Features and Enhancements in Cisco AXP 1.5.2

Basic Safeguards for Securing AXP Router/Blade

Open Caveats for Cisco AXP 1.5.2

New Commands and Modified Command Documentation in Cisco AXP 1.5.2

clear cores

clear cores (Cisco AXP application service EXEC)

copy core

copy tech-support

log trace local enable

show memory

show software

show swap usage

show tech-support

Related Documentation

Software Documents

Platform-Specific Documents

Obtaining Documentation, Obtaining Support, and Security Guidelines

Notices

OpenSSL/Open SSL Project

License Issues


Release Notes for Cisco Application eXtension Platform (AXP) 1.5.2


First Published: January 13, 2010
Last Updated: October 12, 2010, OL-14273-01

These release notes support the software for the Cisco Application eXtension Platform (Cisco AXP). To determine if your Cisco IOS software or Cisco hardware platforms are affected, see the Cisco IOS Software Releases 15.0 Release Notes at http://www.cisco.com/en/US/products/ps10591/prod_release_notes_list.html.

Contents

System Requirements

New Features and Enhancements in Cisco AXP 1.5.2

Basic Safeguards for Securing AXP Router/Blade

Open Caveats for Cisco AXP 1.5.2

New Commands and Modified Command Documentation in Cisco AXP 1.5.2

Related Documentation

Obtaining Documentation, Obtaining Support, and Security Guidelines

Notices

System Requirements

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

Cisco IOS Software Release

Supported Hardware

Files in Cisco AXP 1.5.2

Upgrading and Downgrading to a New Software Release

Verifying the MAC address of a Network Module (for Cisco AXP 1.5.1 and 1.5.2)

Determining the Cisco AXP Software Version

Cisco IOS Software Release

Using Cisco IOS Release 12.4(24)T2 or 15.0(1)M1 and higher is recommended, depending on the type of router—refer to the "Supported Hardware" section.

Cisco AXP 1.5.2 supports routers with the following types of IP-based, crypto images:

Universal (c3900-universalk9-mz.SPA.151-1.XB)

IP-Base (not for applications that require the Event API)

IP-Voice

Adv-Security

Adv-Enterprise

You can download the Cisco AXP 1.5.2 image from www.cisco.com. Navigate the website as shown in the following steps:


Step 1 Choose Products and Routers > Routers > All Products tab.

Step 2 Choose Cisco Application Extension Platform > Download Software > Cisco Application Extension Platform Version 1.5.


Netconf provides the interface for the Cisco IOS CLI API. Depending on the underlying transport protocol (BEEP or SSH), different versions of the Cisco IOS software are supported. For further information, refer to the "Netconf" section of Appendix G, in the Cisco Application eXtension Platform 1.5 Developer Guide.

Supported Hardware

Cisco ISR and Cisco ISR G2 routers are supported by Cisco AXP.

For Cisco Integrated Services Routers, we recommend using Cisco IOS Release 12.4(24)T2 and higher.

For Cisco Integrated Services (Generation 2) Routers, we recommend using Cisco IOS Release 15.0(1)M1 and higher.


Note For Cisco ISR G2 routers 3925E and 3945E, Cisco IOS release 15.1(1)T and higher is required.


The AIM2 service module requires Cisco IOS Release 15.0(1)M1 and higher. Cisco AXP integrates with the Cisco IOS software crypto images given in the "Cisco IOS Software Release" section.


Note The NME-APPRE-522-K9 service module is not supported on Cisco ISR G2 router 2911 and 2921. It is supported on Cisco ISR G2 router 2951 and higher.


For Cisco AXP 1.5.2, new service modules SM-SRE-700-K9 and SM-SRE-900-K9 are supported, along with Cisco ISR G2 routers 2911, 2921, 2951, 3925, 3925E, 3945, and 3945E.

Table 1 lists the Cisco routers and service modules supported by different versions of Cisco AXP.

Table 1 Cisco AXP Supported Hardware

Cisco Router/
Service Module
AIM2-104
NME-302
NME-502
NME-522
ISM-300
SM-700
SM-900

891, 892

1.5.x1

1841

1.5.x

1941

1.5.x

2801

1.5.x

2811

1.5.x

1.0, 1.1, 1.5.x

1.1, 1.5.x

2821

1.5.x

1.0, 1.1, 1.5.x

1,1, 1.5.x

2851

1.5.x

1.0, 1.1, 1.5.x

1.1, 1.5.x

2901

1.5.x

2911

1.5.x

1.5.x

1.5.x

1.5.2

1.5.2

2921

1.5.x

1.5.x

1.5.x

1.5.2

1.5.2

2951

1.5.x

1.5.x

1.5.x

1.5.x

1.5.2

1.5.2

3825

1.5.x

1.0, 1.1, 1.5.x

1.1, 1.5.x

1.0, 1.1, 1.5.x

3845

1.5.x

1.0, 1.1, 1.5.x

1,1, 1.5.x

1.0, 1.1, 1.5.x

3925

1.5.x

1.5.x

1.5.x

1.5.x

1.5.2

1.5.2

3925E

1.5.2

1.5.2

1.5.2

1.5.2

1.5.2

3945

1.5.x

1.5.x

1.5.x

1.5.x

1.5.2

1.5.2

3945E

1.5.2

1.5.2

1.5.2

1.5.2

1.5.2

1 1.5.x = Cisco AXP 1.5.1 or higher


The abbreviated service module names used in Table 1 are expanded in Table 2.

Table 2 Cisco AXP Service Modules

Abbreviated Name
Full Name
Description

AIM2-104

AIM2-APPRE-104-K9

600MHz CPU, 512 MB

NME-302

NME-APPRE-302-K9

1GHz CPU, 512MB

NME-502

NME-APPRE-502-K9

1GHz CPU, 1GB

NME-522

NME-APPRE-522-K9

1.4GHz CPU, 2GB

ISM-300

ISM-SRE-300-K9

1.066GHz, 512MB, 4GB eUSB

SM-700

SM-SRE-700-K9

1.066GHz, 512MB, 4GB eUSB

SM-900

SM-SRE-900-K9

1.86GHz dual core CPU, 4 GB


Files in Cisco AXP 1.5.2

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

Cisco AXP Product Files for SM SRE Service Modules

Cisco AXP Software Development Kit (SDK)

Cisco AXP Product Files for SM SRE Service Modules

Compressed archive axp-k9.sme.1.5.2.tar.gz contains all package files associated with Cisco AXP on SM SRE service modules. The package files are shown in Table 3.

Table 3 Cisco AXP 1.5.2 Base Package for SM SRE: axp-k9.sme.1.5.2.tar.gz

Filename
Purpose

axp-helper-k9.sme.1.5.2

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

axp-k9.sme.1.5.2.pkg

Main package for installing the Cisco AXP on Cisco SM SRE service modules.

axp-k9.sme.1.5.2.prt1

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

axp-installer-k9.sme.1.5.2.prt1

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

axp-k9.sme.1.5.2.pkg.install.sre

Installer TCL script.

axp-k9.sme.1.5.2.pkg.install.sre.header

Installer TCL script header.

axp-k9.sme.1.5.2.key

SRE keyfile.

axp-timezone.sme.1.5.2.pkg

AXP Timezone package file.

axp-timezone.sme.1.5.2.prt1

AXP Timezone payload file. Contains required time zone definitions.

axp-app-dev.sme.1.5.2.pkg

Application Development add-on package file.

axp-app-dev.sme.1.5.2.prt1

Application Development add-on payload file.


Cisco AXP Software Development Kit (SDK)

Compressed archive axp-sdk.1.5.2.tar.gz contains the Cisco AXP SDK tool for building third-party applications.

Upgrading and Downgrading to a New Software Release

For more information see the "Installing and Upgrading Software" section of the
"Cisco AXP Software Management" chapter of the Cisco Application eXtension Platform 1.5 User Guide.

Packaging Your application Using 1.5.2 SDK

Clean Installing AXP 1.5.2 Release

Upgrading from Cisco AXP 1.5.1 to Cisco AXP 1.5.2

Upgrading from Cisco AXP 1.1.x to Cisco AXP 1.5.2

No Downgrading from Cisco AXP 1.5.2 to Cisco AXP 1.1.x

Clean Installing Cisco AXP 1.1.x on Cisco AXP 1.5

Packaging Your application Using 1.5.2 SDK

Applications that are not packaged using 1.5 SDK will not run on AXP 1.5.2.

Clean Installing AXP 1.5.2 Release

There are three options to clean install AXP 1.5.2 that include your application created using the AXP 1.5 SDK.


Note Applications that are not packaged using the AXP 1.5 SDK will not run on AXP 1.5.2.


Option 1


Step 1 Install AXP 1.5.2 through the Cisco IOS command line interface (CLI):

For Service Modules only, make sure that all AXP 1.5.2 install files are located in the same ftp directory.

From the Cisco IOS command prompt enter the command:

service-module SM <slot>/0 install url ftp://<ftp server ip address>/<ftp server 
directory>/axp-k9.sme.1.5.2.pkg

You may be prompted to delete the existing AXP application that is already installed. Enter "yes" as the response:

Delete the installed Application eXtension Platform (AXP) and proceed with new 
installation? [no]: yes

If you are installing on an SM-SRE-900-K9 module you will be asked to select the Redundant Array of Inexpensive Hard Disks (RAID) type. Currently two RAID modes are supported: RAID-1 and linear:

Please select disk configuration (1 = RAID-1, 2 = linear):

Step 2 Install your application separately:

software install package url ftp://<ftpserver>/application.pkg

Wait for system to reboot.



Option 2


Step 1 Clean install AXP 1.5.2:

Make sure axp-k9.xxx.1.5.2.prt1, axp-installer-k9.xxx.1.5.2.prt1 and axp-timezone.xxx.1.5.2.prt1 are also in the same ftp directory as axp-k9.xxx.1.5.2.pkg.

software install clean url ftp://<ftpserver>/axp-k9.xxx.1.5.2.pkg

Wait for system to reboot.

Step 2 Install your application separately:

software install package url ftp://<ftpserver>/application.pkg

Wait for system to reboot.


Option 3


Step 1 Bundle your application with AXP 1.5.2.

Step 2 Clean install the resulting bundle package:

software install clean url ftp://<ftpserver>/bundle.pkg

You can also use this command to install the bundle package:

software install package url ftp://<ftpserver>/bundle.pkg

Wait for system to reboot.


Upgrading from Cisco AXP 1.5.1 to Cisco AXP 1.5.2

This procedure assumes you are upgrading from (AXP 1.5.1 + application) to (AXP 1.5.2 + same application).


Step 1 Bundle your application with AXP 1.5.

Step 2 Upgrade to the bundle package:

software install package url ftp://<ftpserver>/axp.k9.xxx.1.5.2.pkg

Wait for system to reboot.


Upgrading from Cisco AXP 1.1.x to Cisco AXP 1.5.2

There are two methods to upgrade from AXP 1.1.x to AXP 1.5.2 and your application created by 1.5 SDK (applications that are not packaged using 1.5 SDK will not run on AXP 1.5.2):

Option1


Step 1 Upgrade AXP from 1.1.x to 1.5:

(Make sure axp-k9.xxx.1.5.2.prt1, axp-installer-k9.xxx.1.5.2.prt1 and axp-timezone.xxx.1.5.2.prt1 are also in the same ftp directory as axp-k9.xxx.1.5.2.pkg)

software install package url ftp://<ftpserver>/axp-k9.xxx.1.5.2.pkg

Wait for system to reboot. This will upgrade Cisco AXP from 1.1.x to 1.5.

Step 2 Install your application separately:

software install package url ftp://<ftpserver>/application.pkg

Wait for system to reboot. If the older version of the application exists on the system, this will upgrade the application to newer version. Otherwise, the application will be newly installed.


Option 2

This option assumes you are upgrading from (AXP 1.1.x + application) to (AXP 1.5 + same application).


Step 1 Bundle your application with AXP 1.5.

Step 2 Upgrade to the bundle package:

software install package url ftp://<ftpserver>/bundle.pkg

Wait for system to reboot.


No Downgrading from Cisco AXP 1.5.2 to Cisco AXP 1.1.x

Downgrade of AXP and/or your application from AXP 1.5.2 to AXP 1.1.x is not allowed. You must clean install AXP 1.1.x.

Clean Installing Cisco AXP 1.1.x on Cisco AXP 1.5

Before performing these steps, make sure the axp-k9.xxx.1.1.x.prt1 file is in the same ftp directory as the axp-k9.xxx.1.1.x.pkg file. To clean install Cisco AXP 1.1.x and your application created by 1.1.x SDK, perform the following steps:


Step 1 Clean install Cisco AXP 1.1.x:

software install clean url ftp://<ftpserver>/axp-k9.xxx.1.1.x.pkg

Wait for system to reboot.

Step 2 Install your application separately:

software install add url ftp://<ftpserver>/application.pkg

Wait for system to reboot.


One-step clean installation of a Cisco AXP 1.1.x bundle containing Cisco AXP 1.1.x and your application is not supported in Cisco AXP 1.5.2.

Verifying the MAC address of a Network Module (for Cisco AXP 1.5.1 and 1.5.2)

An issue existed where the MAC address of a network module (NME) changed after upgrading to Cisco AXP 1.5.1/1.5.2. (For example, see CSCte83939.) This issue has now been resolved.

After you install (or upgrade to) Cisco AXP version 1.5.2, verify the MAC address of the network module by performing the following steps.


Step 1 Verify that the latest Cisco AXP 1.5.2 image is installed by showing the version of the bootloader.

show software version detail | inc Secondary

The version of the bootloader should be 2.1.25.0.

If the version of the bootloader is not 2.1.25.0 contact Cisco Developer Services to help resolve the problem.

Example

se-10-10-2-163# show software version detail  | inc Secondary
 Name: Bootloader (Secondary) (2.1.25.0)
 

Step 2 Verify that the MAC Address is valid on the network module (NME), after the latest Cisco AXP 1.5.2 image has been installed.

Router# show arp Integrated-Service-Engine 1/0

The interface number matches the network module.

The MAC Address should not be 0004.9a49.3c70

If the MAC address is 0004.9a49.3c70 , contact Cisco Developer Services to help resolve the problem.

Example

In this example the MAC address on the network module is shown as 0016.9d39.5045.

This is not equal to 0004.9a49.3c70, which is the desired result. No further action is required.

Router# show arp Integrated-Service-Engine 1/0
Protocol Address          Age (min) Hardware Addr   Type   Interface
Internet 10.10.2.163       7        0016.9d39.5045  ARPA   Integrated-Service-Engine1/0

Determining the Cisco AXP 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.5.2)
Technical Support: http://www.cisco.com/techsupport/ Copyright (c) 1986-2009 by Cisco 
Systems, Inc.

New Features and Enhancements in Cisco AXP 1.5.2

Table 4 lists the main feature changes for Cisco AXP 1.5.2.

Table 4 New Features in Cisco AXP 1.5.2 

Category
Cisco AXP 1.5 Features

New Platforms

SM-SRE-700-K9 (1.86 GHz, 4 GB RAM, 500 GB HDD)

SM-SRE-900-K9 (1.86 GHz dual core, 4 GB RAM, 2x500 GB HDD w/ RAID support)

MGF Interface

The internal interface (mgf) for inter-blade (i.e., AXP to AXP) communication within the same router can now be configured on the module. Traffic that goes out on this is switched between modules in the router that are configured for the same layer-2 subnet.

RAID Support

RAID support is available on the SM-SRE-900-K9. Raid-1 and linear raid can be selected as options at install time.


Table 5 lists the optional features supported by Cisco AXP 1.5.2.

Table 5 Cisco AXP 1.5.2 Optional Features

Service
UUID
1.1 AXPOS
1.5 AXPOS
1.5 AXP UDL

Cisco IOS CLI API
(optional service)

8cec8ee5-54c3-4667-b62e-d4a31805d44a

axp-iosapi.nme.1.1.0.pkg

built-in

built-in

Cisco AXP CLI API
(standard service)

built-in

built-in

built-in

built-in

CLI Plugin
(optional service)

b4b0ee92-cf8e-472b-8434-e8e7412ec71a

axp-cli-plugin.nme.1.1.0.pkg

built-in

built-in

Cisco IOS Event API (optional service) (different UUID from 1.1)

545c3671-c4bc-43b8-bce4-690123ab9d4d

axp-eemapi.nme.1.1.0.pkg

built-in

built-in

Remote Serial Device
(optional service)

7a013f0e-07cb-4c25 -8122-4a0af7704c3b

axp-vserial.nme.1.1.0.pkg

built-in

built-in

Application Development Package
(optional service)

5d9267f0-f9c2-11db-8f0d-001635a94464

axp-app-dev.nme.1.1.0.pkg

axp-app-dev.nme.1.5.0.pkg

axp-app-dev.nme.1.5.0.pkg

AXP SysInfo API (standard service)

-

-

built-in

built-in

AXP SysOp API
(standard service)

-

-

built-in

built-in


Basic Safeguards for Securing AXP Router/Blade

In order to improve the security of your system, we suggest the following actions:

Telneting to router IP addresses must always be protected via username and password. Common pairs such as cisco, cisco should be avoided.

Users that are allowed access to routers should be classified further by assigning privilege levels (0-15) that allow for limiting actions that can be performed. Privilege level 0 is most restrictive, and level 15 is least restrictive.

Following this safeguard ensures that users attempting a privileged CLI operation need to go through #enable mode and password authorization.

Remote access to Service Modules via SSH is disabled by default. When enabling SSH access via the ip ssh server command ensure that the username sysadmin password command is also configured. There are provisions to encrypt this password as well. See the "Secure Shell Access to the Service Module" section of the "Configuring the Application Service Environment" chapter of the Cisco Application eXtension Platform 1.5 User Guide for more information.

Open Caveats for Cisco AXP 1.5.2

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


CSCtb98215: cserial8250 uart intermittently locks up

CSCtc06120: SM: Admin should be notified when disk goes bad on SM-SRE-900-K9 (RAID-1)

CSCtd02362: syslog srvr can't be configured if app with disk wildcard on is on blade

CSCtd04933: ip route to SM1/1 (backplane) is lost after shut/no shut of SM1/1

CSCtd11052: show interface output accounting uses wrong interface data

CSCtd11694: eventapid generates core when events are triggered at more than 1 event/sec

CSCtd11724: Events stop flowing with IPC UDP error given when it fails to get psk msg

CSCtd19442: SNAP: Call to underlying OS function(pthread_cancel) failed

CSCtd31701: Redefine of timezones using the "date" option does not work

CSCtd67367: show run and /etc/resolv.conf in Guest env is not in sync

CSCtb98215: cserial8250 uart intermittently locks up

Symptom    The following messages appear on the console and when this problem occurs the CLI for the module gets stuck:

cserial8250: too much work for irq4
serial8250: too much work for irq4

Conditions   This condition is very intermittent and seems to be more frequent when CLIs which produce significant console output are executed.

Workaround   There is no known workaround for this issue. The module can be recovered by resetting the module from the Cisco IOS CLI when it gets into this condition.

CSCtc06120: SM: Admin should be notified when disk goes bad on SM-SRE-900-K9 (RAID-1)

Symptom    When/if a disk becomes bad, the administrator does not get actively notified.

Conditions   One of the disks becomes bad.

Workaround   The administrator should run the show disk stats command once in a while to verify that the disks are functioning properly.

CSCtd02362: syslog srvr can't be configured if app with disk wildcard on is on blade

Symptom    The syslog-server configured on AXP runs out of disk space even though its log files take up less than the disk allocated for syslog-server. An application runs out of disk space even though it is within its disk limit.

Conditions   The amount of disk spaced used by AXP's syslog-server is not accounted for when an application is installed. For example, take the following AXP system:

Application that uses all but 200 MB of AXP's available disk space

Syslog-server configured to use the remaining 200 MB for log files

Since syslog-server disk usage is not accounted for, it is possible to install an application that uses 200 MB of disk space or less.

Similarly, if an application has the disk wildcard enabled, the application's disk allocation will include the disk space configured for syslog-server. The syslog-server will compete for disk space with the application.

Workaround   When the syslog-server is configured on AXP, application's disk usage should be manually accounted for. In other words, application's disk limits should be set so that the syslog-server has sufficient disk space for its log files. Wildcards should also be avoided to ensure that the syslog-server has enough disk space for its log files.

If it is not important that the syslog-server prematurely runs out of space for its log files, than wildcards can be used and disk limits can be set without regard to the syslog-server's disk usage.

CSCtd04933: ip route to SM1/1 (backplane) is lost after shut/no shut of SM1/1

Symptom    Ping to ISM or SM backplane interface is lost after shut/no shut of the ISM or SM backplane interface.

Conditions   This happens when the ISM/SM backplane interface is configured with the ip unnumbered command so that it does not have an explicit IP address, then a shutdown/no shutdown is issued on the interface.

Workaround   Reconfigure the lost route manually.

CSCtd11052: show interface output accounting uses wrong interface data

Symptom    The output statistics for the show interface command show "0" for input/output packets but actual numbers are not.

Conditions   show interface (for eth0)

Workaround   None.

CSCtd11694: eventapid generates core when events are triggered at more than 1 event/sec

Symptom    Under a stress condition with event notifications higher than one event per second, the eventapid daemon process may crash. This issue is not a specific issue on any particular platform. It can occur on any platforms such as NME, AIM2, ISM, and SM.

The following are indications that the eventapid daemon has crashed:

Core file can be seen by executing the show cores command.

The following messages will be logged to messages.log.

Dec  9 19:49:59 localhost err_handler: 2009 Dec  9 19:49:59 GMT +0000: err_handler:    
INFO AXP_eventapi eventapid_startup.sh startup "eventapid starting"
Dec  9 19:49:59 localhost err_handler: 2009 Dec  9 19:49:59 GMT +0000: err_handler:    
INFO AXP_eventapi eventapid_startup.sh startup "eventapid started"
Dec  9 19:49:59 localhost err_handler: 2009 Dec  9 19:49:59 GMT +0000: err_handler:   
ERROR AXP_startup host_status_monitor monitor eventapid[3217] is dead, restart [0] 
attempted

A list of AXP processes can be seen by issuing the show processes CLI command. The eventapid daemon process will be showing "dead" momentarily until the system automatically restarts the eventapid daemon. Once the eventapid daemon is successfully restarted, the health status for this daemon will change from "dead" to "alive" when the show processes CLI command is reissued.

The guest application will get a connection handler callback method invocation.

Conditions   eventapid daemon may crash under a stress condition with event notifications flowing from Cisco IOS software to the module at a rate higher than 1 event notification per second.

Workaround   The eventapid daemon will get restarted automatically by the system. The application should reregister the events. This reregistration of events can be done in a connection handler callback method.

This involves creating a callback procedure in the application program that would get invoked when the eventapid gets restarted. Check for a status of 1 which indicates that the eventapid daemon just became alive. A status value of 0 will indicate that the eventapid daemon just died. Within this callback procedure, use the register API to reregister the events. Use the set connection handler API to set up the connection monitor to use this callback procedure. See the "Java Example" section in the "IOS CLI API" chapter of the Cisco Application eXtension Platform 1.5 Developer Guide.

CSCtd11724: Events stop flowing with IPC UDP error given when it fails to get psk msg

Symptom    The eventapid daemon may experience a deadlock under a stress condition with events getting triggered at a rate higher than 1 event notification per second. When a deadlock occurs, the application will stop receiving event notification and appear to be hanging or stuck in one of the event API method.

The following messages are seen from the Cisco IOS software console messages and will appear multiple times:

IPC posix UDP Error: get pak failed
IPC Error: Get psk msg failed ; Error - 1
Nov  9 11:52:58.696 PDT: %HA_EM-7-FMS_POLICY_MAX_ENTRIES: fh_schedule_callback:Class 
default: Maximum number of 25 axp publish entries exceeded; some events have been 
discarded. 

This issue is not a specific issue on any particular platform. It can occur on any platforms such as NME, AIM2, ISM, and SM.

Conditions   Deadlock may occur under a stress condition with events getting triggered at a rate higher than 1 per second.

Workaround   There is no viable workaround. If the events stopped flowing due to a deadlock condition or the application hanging situation, the blade must be reloaded.

CSCtd19442: SNAP: Call to underlying OS function(pthread_cancel) failed

Symptom    Occasionally, the following messages may be seen in messages.log from the eventapid process when there are a high volume of event notification.

eventapid:  ERROR AXP_svcapi ios_snap main  Client Error: Call to underlying OS function( 
pthread_cancel ) failed

These pthread cancel failed messages are not specific to any particular platform. It can appear on any platforms such as NME, AIM2, ISM, and SM.

Conditions   These messages may be seen in the messages.log under a stress condition with events higher than 1 per second.

Workaround   N/A. These messages are harmless and do not affect the functionality of the system.

CSCtd31701: Redefine of timezones using the "date" option does not work

Symptom    Redefining a timezone using the "date" option does not produce the intended results. The time remains on Standard Time during the times when it should be Daylight time.

Conditions   The following is an example of a command that will result in this problem.

(config)# clock timezone America/Chicago redefine
(config-timezone)# standard-time CST -6
(config-timezone)# summer-time CDT date March 15 2010 2:00 November 15 2011 2:00
(config-timezone)# exit

This problem applies to Cisco AXP version 1.5.2 release only.

Workaround   The workaround is to use the "recurring" option, rather than the "date" option in the "summer-time" command when redefining timezones.

CSCtd67367: show run and /etc/resolv.conf in Guest env is not in sync

Symptom    Domain name in /etc/resolv.conf and the show run output are not the same.

Conditions   After configuring the ip domain-name and name server and removing them, /etc/resolv.conf will still have the configs.

Workaround   No workaround.

New Commands and Modified Command Documentation in Cisco AXP 1.5.2

The following commands were new or modified for Cisco AXP 1.5.2:

clear cores

clear cores (Cisco AXP application service EXEC)

copy core

copy tech-support

log trace local enable

show memory

show software

show swap usage

show tech-support

clear cores

To delete all host and application core files, use the clear cores command in Cisco AXP EXEC mode.

clear cores

Syntax Description

This command has no arguments or keywords.

Command Default

None

Command Modes

Cisco AXP EXEC

Command History

Cisco AXP Version
Modification

1.0

This command was introduced.

1.5.1

The command was modified to delete application core files as well host core files.


Examples

In the following example, the core files of a Cisco AXP application and the host are deleted:

se-Module(config)> clear cores 

Related Commands

Command
Description

clear core

Clears one specific core file of an application.

show cores

Displays all core files.


clear cores (Cisco AXP application service EXEC)

To delete all of an application's core files, use the clear cores command in Cisco AXP application service EXEC mode.

clear cores

Syntax Description

This command has no arguments or keywords.

Command Default

None

Command Modes

Cisco AXP application service EXEC

Command History

Cisco AXP Version
Modification

1.0

This command was introduced.


Examples

In the following example, the core files of a Cisco AXP application are deleted:

se-Module(exec-helloworld)> clear cores 

Related Commands

Command
Description

show cores

Displays all core files.


copy core

To copy core files to another location, use the copy core command in Cisco AXP EXEC mode or Cisco AXP application service EXEC mode.

copy core core-name url ftp/http url

Syntax Description

core-name

Filename used to identify the core(s).

url

Destination Universal Resource Location (URL).

ftp/http url

FTP or HTTP URL destination location to which the matching core files are to be copied.


Command Default

None

Command Modes

Cisco AXP EXEC
Cisco AXP application service EXEC

Command History

Cisco AXP Version
Modification

1.0

This command was introduced.

1.5.1

The command was modified to accept wildcards in the core filename and copy all matching core files.


Usage Guidelines

The core filename (in both command modes) may contain wildcards * allowing the copying of more than one core file at a time.

Use the show core command to view the core.

The standard FTP URL format is supported:

ftp://[user-id:ftp-password@]ftp-server-address[/directory]

Examples

In the following example, the file mping-test-file2 is copied to remote URL http://example.net.

se-Module(exec-helloworld)> copy core mping-test-file2 http://example.net


Related Commands

Command
Description

show cores

Displays the list of core files.


copy tech-support

To copy diagnostic information about the host and application environment from a Cisco AXP host operating system to a remote location, use the copy tech-support command in Cisco AXP EXEC mode.

copy tech-support location

Syntax Description

location

The URL location is of a form that is accepted by the Linux curl command for uploading files. Forms of this type include prefixes of ftp, and sftp. The user may be prompted to enter credentials if they were not supplied as part of the url or as separate parameters. The format of credentials if they are entered as part of a location is:

prefix://username:password@server

The file: URL location form is support when calling the copy tech-support command using the AXP SYSOP API only.

Note When using the AXP SYSOP API to call the copy tech-support command, do not specify a location beginning with "file:/tmp/" as the file location.


Command Default

None

Command Modes

Cisco AXP EXEC

Command History

Cisco AXP Version
Modification

1.5.1

This command was introduced.


Usage Guidelines

This command copies tech-support data as a tar file to a remote URL provided by the third party application.

Displays the running-config, state, resource limits, and statistics about the application environment.

Displays application specific information if provided by the third-party application.

Displays kernel capabilities.

Displays details on Linux Kernel Module (LKM) support.

Outputs a compressed (gzip) tar file (tar).

The order in which data is collected is the same as the show tech-support command. The output file is uploaded to a specified destination.

The tar file output contains the pathnames for the show command output with the directory "show" followed by the name of the show command. Data files and script output are named according to their labels in the configuration files. For applications running in the AXP Reference OS, the virtual instance name is prefixed as a directory name.

For example, to send a file to an FTP server, enter:

copy tech-support url ftp://myuserid:itspassword@servername/incoming/tech-support.tar.gz.

Examples

In the following example, the copy tech-support command copies tech support data from the host operating system to a remote server:

se-Module> copy tech-support url ftp://admin:mpg@10.10.67.163/lnstallinfo 
se-Module> copy tech-support url ftp://myftpserver.cisco.com/uploads/ts.tar.gz
se-Module> copy tech-support url 
ftp://myusername:mypassword@myftpserver.cisco.com/uploads/tech.tgz

Related Commands

Command
Description

show tech-support

Displays diagnostic information about the host environment.


log trace local enable

To configure tracing messages to a local disk, use the log trace local enable command in Cisco AXP configuration mode. To disable tracing messages to a local disk, use the no form of this command.

log trace local enable

no log trace local enable

Syntax Description

This command has no arguments or keywords.

Command Default

None

Command Modes

Cisco AXP configuration

Command History

Cisco AXP Release
Modification

1.0

This command was introduced.


Usage Guidelines

Enable local tracing to a disk.

The trace function is the same on Advanced Integration Module 2 (AIM2) and Integrated Service Module (ISM) since they are flash-based systems. The trace function is the same on Service Module (SM) and Network Module (NME). The trace function is different on the AIM2 and the NM as summarized in the following table:

AIM2
NME

The atrace.log file is disabled by default. Issue the log trace local enable command to begin and the no log trace local enable command to stop.

The atrace.log file is enabled by default. Tracing to an external server is also supported.

The maximum size of atrace.log is 10 MB.

The maximum size of atrace.log is 100 MB.

The atrace.log file does not wrap when full.

The atrace.log file wraps when full.


The AIM2 does not store any trace information in flash memory itself by default. Also, the internal storage capacity for trace data, when enabled, is much more limited. This is because the lifespan of the internal compact flash memory card on the AIM2 is related to the number of writes issued to it. Constantly writing traces significantly lowers the lifespan.


Note Enter the no log trace local enable command followed by the log trace local enable command in Cisco AXP configuration mode in order to restart an atrace.log file on an AIM2 that has reached its maximum size. This removes the original atrace.log file and begins a new one.


For the log facility, there are also important differences:

AIM2
NM

Only Fatal messages are logged to the messages.log file by default. Enter the log console info command from Cisco AXP configuration mode to see all messages.

All categories of messages are logged to the messages.log file.


Examples

The following example configures tracing to a local disk:

se-Module(config)> log trace local enable 

Related Commands

Command
Description

log console info

Configures information messages to be displayed on the console

show logging

Displays the types of messages that are displayed on the console.


show memory

To display memory statistics, use the show memory command in Cisco AXP EXEC mode.

show memory [|]

Syntax Description

|

(Optional) Pipe output to another command.

begin

(Optional) Display begins with the line that matches.

exclude

(Optional) Display excludes lines that match.

include

(Optional) Display includes lines that match.

page

(Optional) Displays paginated output (--More--).


Command Default

None

Command Modes

Cisco AXP EXEC

Command History

Cisco AXP Version
Modification

1.0

This command was introduced.


Examples

In the following example, the show memory command displays the memory statistics.

se-Module> show memory 

SDRAM (MByte):                512
Total Memory (kB):            512788
Active Memory (kB):           129232
Inactive Memory (kB):         105632
Other Memory (kB):            21472
MemoryPool (kB):              256452

Table 6 describes the significant fields shown in the display.

Table 6 show memory Field Descriptions 

Field
Description

SDRAM

Total usable RAM (in megabytes), that is, physical memory minus a few reserved bytes and the kernel binary code.

Total Memory

Total usable RAM (in kilobytes).

Active Memory

The total amount of buffer or page cache memory that is active (in kilobytes). This part of the memory is used recently and usually not reclaimed unless absolutely necessary.

Inactive Memory

The total amount of buffer or page cache memory that is free and available (in kilobytes). This is memory that has not been recently used and can be reclaimed for other purposes by the paging algorithm.

Other Memory

Total memory (active plus inactive plus free), where free is the amount of physical RAM left unused by the system.

MemoryPool

Physical RAM left unused by the system (in kilobytes).


Related Commands

Command
Description

show running-config

Displays the current running configuration.


show software

To display the current software information of the module, use the show software command in Cisco AXP EXEC mode.

show software {dependencies | directory download | download server | install history | licenses | packages | versions}

Syntax Description

dependencies

Displays the subsystem software dependencies on the installed packages.

directory download

Displays directory listings information about the download directories.

download server

Displays information about the download server.

install history

Displays information about what software was installed on the module and when.

licenses

Displays installed software license information.

packages

Displays information about the installed software and plug-in packages.

versions

Displays the versions of installed packages.


Command Default

None

Command Modes

Cisco AXP EXEC

Command History

Cisco AXP Version
Modification

1.0

This command was introduced.

1.5.1

The install history keywords were added.


Examples

Examples of the following commands are listed below:

show software directory download: Example

show software download server: Example

show software licenses: Example

show software packages: Example

show software versions: Example

show software versions detail: Example

show software install history: Example

show software directory download: Example

In the following example, the show software directory download command displays download directory information on the screen.

se-Module> show software directory download

KBytes  Directory
27347   /dwnld/pkgdata

Directory listings

Directory: /dwnld/pkgdata

total 27347
drwxrwxr-x    2 root     daemon        136 Oct 18 19:30 .
drwxrwxr-x    4 root     daemon        136 Oct 18 19:30 ..
-rw-rw-r--    1 root     root     27857860 Oct 18 19:31 axp-upgrade.2.1
-rw-rw-r--    1 root     root       113161 Oct 18 19:30 axp.2.1.pkg
se-Module

show software download server: Example

se-Module> show software download server

Download server URL is: ftp://172.16.0.1/ftp

show software licenses: Example


se-Module> show software licenses

Core:
 - application mode: AXP 

show software packages: Example


se-Module> show software packages 

Installed Packages:

 - Installer (Installer application) (1.1.0.150)
 - Bootloader (Primary) (Service Engine Bootloader) (1.0.2)
 - AXP (Virtual Server Development System) (1.1.0)
 - Infrastructure (Service Engine Infrastructure) (2.4.30.6)
 - Global (Global manifest) (1.1.0)
 - guest_os (AXP Guest OS Add-on Package) (1.1.0)
 - Bootloader (Secondary) (Service Engine Bootloader) (1.0.2.150)
 - Core (Service Engine OS Core) (2.4.30.6)
 - GPL Infrastructure (Service Engine GPL Infrastructure) (2.2.30.1)

Installed Plug-ins:

 - showtime (showtime Discus Beta) (1.3)
 - iosapi (ios api Discus app!) (1.0)
 - cli_plugin (CLI Plugin bundle to allow custom CLI plugin) (1.1.0)
 - Tomcat (Apache Foundation Tomcat Servlet Container) (5.5.20)
 - helloworld (hello Discus Beta) (1.0)

show software versions: Example


se-Module# show software versions 

Components: 

 - MyApp version  1.0 
 - app_dev version  1.5.1 

show software versions detail: Example


se-192-1-1-118# show software versions detail

Applications:

 Name: Installer (1.5.1.50)
 Desc: Installer application
   id: a0fb9f0a-fa5c-4b21-a64c-0cb9d6379573
 Type: (installer)

 Name: AXP (1.5.1)
 Desc: Virtual Server Development System
   id: 2876dec2-dfbe-4d43-9ef6-6dc16062f03b
 Type: (application)

 Name: ios_snap (1.5.1.SNAP_REL_20090915)
 Desc: Structured Network API Support
   id: cc5c39cc-71a3-4487-a7e5-bd197e07a03e
 Type: (application)

 Name: Core (2.5.5.0)
 Desc: Service Engine OS Core
   id: 430f25f9-0fed-48a4-b362-823937138501
 Type: (application)

 Name: Global (1.5.1)
 Desc: Global manifest
   id: edceaf0b-a890-4045-9086-5452fac85eba
 Type: (application)

 Name: iosapi (1.5.1)
 Desc: IOS CLI API
   id: 8cec8ee5-54c3-4667-b62e-d4a31805d44a
 Type: (application)

 Name: axpos (1.5.1)
 Desc: AXP Reference OS
   id: 9a2882e5-c927-4b1a-9e39-eeeda9f01901
 Type: (application)

 Name: GPL Infrastructure (2.3.5.0)
 Desc: Service Engine GPL Infrastructure
   id: 9f112eb1-6f58-4dd4-8faa-8530467af3b9
 Type: (application)

 Name: cli_plugin (1.5.1)
 Desc: CLI Plugin bundle to allow custom CLI plugin
   id: b4b0ee92-cf8e-472b-8434-e8e7412ec71a
 Type: (application)

 Name: ios_eemclient (V124_24_6_PI11V)
 Desc: IOS EEM Client Library
   id: 2d039106-c6a3-4378-9a63-e041351f640e
 Type: (application)

 Name: vserialapi (1.5.1)
 Desc: Remote Serial Device support
   id: 7a013f0e-07cb-4c25-8122-4a0af7704c3b
 Type: (application)

 Name: eventapi (1.5.1)
 Desc: IOS Event API
   id: 545c3671-c4bc-43b8-bce4-690123ab9d4d
 Type: (application)

 Name: Infrastructure (2.5.5.0)
 Desc: Service Engine Infrastructure
   id: a36e1be1-ce8a-4f53-ace7-1844262aa0b9
 Type: (application)

 Name: Guest OS Environment (1.5.1)
 Desc: AXP Guest OS Environment (Legacy)
   id: ca9d624a-1c8f-473a-a0bc-822e648de7fc
 Type: (application)

 Name: Bootloader (Secondary) (2.1.16.70)
 Desc: Service Engine Bootloader
   id: 9d7b26fb-21b2-416e-8b65-425c2f8da5d8
 Type: (bootloader)

 Name: ios_mosipc (1.5.1.OMNI_TAHOE_MOS_20090825)
 Desc: Cisco Multi-OS IPC support
   id: 6842f4ef-5caf-4088-9fab-68a465ca6947
 Type: (application)

 Name: timezone (1.0.2009g.1)
 Desc: Time Zone Definitions
   id: 322c7f55-9971-4df1-8460-e7beaa94c526
 Type: (application)

 Name: axpsystemapi (1.5.1)
 Desc: AXP standard services(AXP SysInfo, SysOp, CLI API)
   id: 53bf57bd-d7bf-4f4a-977d-6f90fb2e74e3
 Type: (application)


Components:

 Name: MyApp (1.0)
 Desc: My Sample Application
   id: 0614b1fb-9105-474d-9787-53f9a589a36e
 Type: (plug-in)

 Name: app_dev (1.5.1)
 Desc: Application Debugging Add-on Package
   id: *5d9267f0-f9c2-11db-8f0d-001635a94464*
 Type: (plug-in)


show software install history: Example

In the following examples, the show software install history command displays information to the screen about what software was installed on the module and when the software was installed.

se-Module> show software install history

Software Installation History:
  Refer to install.log for more details

 2009-12-04 00:00:24  ***Install Command Issued*** Cmd:1 Opt:0, Pkg:bundle_img_cus.pkg Url:ftp://10.0.0.123 
Mode:0 Proto:1 Host:10.0.0.123 Scripts:False
 2009-12-04 00:11:03  ***SOFTWARE CLEANED*** 
 Timestamp            Subsystem                Version          Description                          UID                     
 2009-12-04 00:11:03  AXP                    1.5.1.81        Virtual Server Development System    
2876dec2-dfbe-4d43-9ef6-6dc16062f03b
 2009-12-04 00:11:03  app_cus_3              1.2             Customer                             
6d702d56-cd66-4d4e-b2af-46033aa644fe
 2009-12-04 00:11:03  Core                   2.5.5.0         Service Engine OS Core               
430f25f9-0fed-48a4-b362-823937138501
 2009-12-04 00:11:04  Global                 1.5.1.81        Global manifest                      
edceaf0b-a890-4045-9086-5452fac85eba
 2009-12-04 00:11:04  iosapi                 1.5.1.81        IOS CLI API                          
8cec8ee5-54c3-4667-b62e-d4a31805d44a
 2009-12-04 00:11:04  app_cus_2              1.2             Customer                             
c507de5c-59ea-499c-803b-8fac063f04a2
 2009-12-04 00:11:04  axpos                  1.5.1.81        AXP Reference OS                     
9a2882e5-c927-4b1a-9e39-eeeda9f01901
 2009-12-04 00:11:04  GPL Infrastructure     2.3.5.0         Service Engine GPL Infrastructure    
9f112eb1-6f58-4dd4-8faa-8530467af3b9

Table 7 describes the significant fields shown in the display.

Table 7 show software install history Field Descriptions 

Field
Description

Timestamp

Date and time the package was installed

Subsystem

Package name

Version

Package version

Description

Description of package

UID

Unique identifier of the package


Related Commands

Command
Description

software install

Installs host and add-on packages on the Cisco AXP service module


show swap usage

To view the swap usage of the system and each application, use the show swap usage command in Cisco AXP EXEC mode and Cisco AXP application service EXEC mode.

show swap usage

Syntax Description

This command has no arguments or keywords.

Command Modes

Cisco AXP EXEC
Cisco AXP application service EXEC mode

Command History

Cisco AXP Release
Modification

1.1

This command was introduced.

1.5.2

This command was made available in Cisco AXP application service EXEC mode.


Usage Guidelines

This command is available inside each application's context. The show tech-support command also displays swap usage information.

Examples

The following example shows that the system swap usage is on:

se-10-0-0-10# show swap usage

System Swap Usage:
             total       used       free     shared    buffers     cached
Mem:          2024        118       1906          0         14         53
Swap:         3820          0       3820
Total:        5845        118       5726

The following example shows that the system swap usage is off:

se-10-0-0-10# show swap usage

swap is turned OFF

The following example shows that the application exec-AXP_APP has swap usage on:

se-10-0-0-10(exec-AXP_APP)# show swap usage

swap is turned ON

Host Swap usage
             total       used       free     shared    buffers     cached
Mem:          2024        118       1906          0         14         53
Swap:         3820          0       3820
Total:        5845        118       5726

The following example shows that the application exec-AXP_APP has swap usage off:

se-10-0-0-10(exec-AXP_APP)# show swap usage

swap is turned OFF

Related Commands

Command
Description

show tech-support

Displays diagnostic information for the application.


show tech-support

To display diagnostic information about the host and application environment, use the show tech-support command in Cisco  AXP EXEC and Cisco AXP application service EXEC mode.

show tech-support [page]

Syntax Description

page

Page through output


Command Default

None

Command Modes

Cisco AXP EXEC
Cisco AXP application service EXEC

Command History

Cisco AXP Version
Modification

1.0

This command was introduced.

1.5.1

This command was updated to include application tech-support information when entered in Cisco AXP EXEC mode.


Usage Guidelines

This command:

Dumps information to the screen provided by the third party application

Displays the running-config, state, resource limits, and statistics about the application environment

Executes the /bin/techsupport binary or script file to display application specific information if provided by the third-party application.

Displays kernel capabilities

Displays details on Linux Kernel Module (LKM) support

The output of the show tech-support command includes data files content and the output of scripts in the configuration files.

Only printable characters are displayed in the output.

The show command output appears first, followed by the host configuration file output, and then each configuration file output of each application running in the AXP Reference OS or AXPUDL.

Individual configuration lines are processed in the order of appearance. The labels on each configuration line are used to identify the source of the data. A header line includes data that identifies the virtual instance from which the data originated.

Examples

In the following example, show tech-support displays diagnostic information for the application environment on the screen. This information includes: state, statistics, processes, resource limits, and running configuration.

se-Module(exec-demo)> show tech-support

------------------ show app-service state ------------------
                   APPLICATION                STATE               HEALTH
                    helloworld               online                ALIVE

------------------ show app-service statistics ------------------
CTX   PROC    VSZ    RSS  userTIME   sysTIME    UPTIME NAME
0      122   2.7G 624.3M  59m23s94   1h10m58   4d20h45 root server
2        4   8.6M   2.9M   1m16s66   1m31s31   4d20h43 helloworld


------------------ show process ------------------
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  0.0  0.1   1972   616 ?        S    Nov15   0:00 init [4]
root      3758  0.0  0.1   2244   872 ?        Ss   Nov15   0:00 /usr/bin/syslog_ng
root      3763  0.0  0.2   2500  1096 ?        S    Nov15   0:00 /bin/bash 
/opt/helloworld/hello_world.sh
root     29302  0.0  0.1   1948   532 ?        Ss   12:55   0:00 /bin/logmgr 
/var/log/messages.log 5000000
root     31016  0.0  0.1   2216   532 ?        S    13:02   0:00 sleep 5


-------------------- Swap space Information --------------------

swap is turned ON

Filename  Type      Size     Used   Priority
/dev/sda3 partition 1959920  0     -2


------------------ show resource limits ------------------
    APPLICATION      CPU(INDEX)      MEMORY(MB)   DISK(MB)    LOG(MB)
     helloworld             800              10         20          5

------------------ Application Capabilities------------------
System Capabilities:
                DAC_OVERRIDE
                DAC_READ_SEARCH
                FOWNER
                FSETID
                KILL
                SETGID
                SETUID
                SETPCAP
                NET_ADMIN
Context Capabilities:
                UTSNAME
                RLIMIT
                RAW_ICMP
                SYSLOG
                SECURE_MOUNT
                SECURE_REMOUNT
                BINARY_MOUNT
                QUOTA_CTL
Dev FS:
                /dev/null c 1 4
                /dev/mytest b 20 8
                /dev/loop0 b 7 0
                /dev/loop1 b 7 1
Net Flags:
Proc FS:
                /proc/test blah
                /proc/sys/net/ipv4/ip_forward 0
Kernel Modules:
                cisco_module.ko
                /mymod/capture.ko

The following capabilities have errors when applied:
Proc FS:  /proc/test blah
Kernel Modules:  cisco_module.ko
 
The following capabilities have errors during installation:
System Capabilities: SYS_ADMIN

------------------ show running-config ------------------
Generating running configuration:

app-service helloworld
 bind interface eth0
 hostname se-10-0-0-0
 log level info
 exit

Related Commands

Command
Description

show resource limits

Displays a summary of the resource limits configuration.

show running-config

Displays the running configuration of the application environment.

show state

Displays the status and health of a specific application.

show statistics

Displays statistics for a virtual instance in the application environment.


Related Documentation

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 software 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. These documents can also be obtained from the Support section of the following page: http://www.cisco.com/en/US/products/ps9701/index.html.

Cisco Application Extension Platform 1.5 Developer Guide

Cisco Application Extension Platform 1.5 User Guide

Cisco Application Extension Platform 1.5 Advanced Features Guide

Open Source Software Licenses for Cisco AXP

For further information on commands available in Cisco AXP 1.1, and 1.5.1, refer to the following documents:

Cisco Application Extension Platform 1.1 Command Reference

Release Notes for Cisco AXP 1.5.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 Router Products

Cisco SRE Service Module Configuration and Installation Guide

Cisco 1900 Series Integrated Services Router Hardware Installation

Software Activation on Cisco Integrated Services Routers and Cisco Integrated Service Routers G2

Cisco 2900 and 3900 Series Hardware Installation

Cisco 3900 Series, 2900 Series, and 1900 Series Integrated Services Routers Software Configuration Guide

Cisco 2800 Series Hardware Installation

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.

Notices

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 (eay@cryptsoft.com).

This product includes software written by Tim Hudson (tjh@cryptsoft.com).

License Issues

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 openssl-core@openssl.org.

OpenSSL License:

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 openssl-core@openssl.org.

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 (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).

Original SSLeay License:

Copyright © 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved.

This package is an SSL implementation written by Eric Young (eay@cryptsoft.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 (tjh@cryptsoft.com).

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 (eay@cryptsoft.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 (tjh@cryptsoft.com)".

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].