Guest

Cisco Application Extension Platform

Release Notes for Application Extension Platform (AXP) 1.5.3

Hierarchical Navigation

Downloads

Table Of Contents

Release Notes for Cisco Application Extension Platform (AXP) 1.5.3

Contents

System Requirements

Cisco IOS Software Release

Supported Hardware

Files in Cisco AXP 1.5.3

Cisco AXP Product Files for Cisco SM SRE Service Modules

Cisco AXP Software Development Kit

Upgrading and Downgrading to a New Software Release

Packaging Your application Using 1.5.3 SDK

Clean Installing Cisco AXP 1.5.3

Upgrading from Cisco AXP 1.5.x to Cisco AXP 1.5.3

Upgrading from Cisco AXP 1.1.x to Cisco AXP 1.5.3

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

Clean Installing Cisco AXP 1.1.x on Cisco AXP 1.5

Determining the Cisco AXP Software Version

New and Changed Information

New Software Features in Cisco AXP 1.5.3

NFS Client

Virtual Frame Buffer

Basic Safeguards for Securing the Cisco AXP Router/Blade

Limitations and Restrictions

Possible Failure of the eventapid Process

Caveats

Open Caveats for Cisco AXP 1.5.3

Closed Caveats for Cisco AXP 1.5.3

New and Modified Commands in Cisco AXP 1.5.3

bind filesystem

show mounts

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

Last Updated: May 16, 2011, 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 hardware platforms are affected, refer to the relevant Cisco IOS software release notes.

Start at the products page http://www.cisco.com/cisco/web/psa/default.html.

Navigate to the page for the Cisco IOS software that you are using; for example:

Products > Cisco IOS and NX-OS Software > Cisco IOS > Cisco IOS Software Release 15 Family > Cisco IOS Software Releases 15.1

Contents

•System Requirements

•New Software Features in Cisco AXP 1.5.3

•Basic Safeguards for Securing the Cisco AXP Router/Blade

•Limitations and Restrictions

•Caveats

•New and Modified Commands in Cisco AXP 1.5.3

•Related Documentation

•Obtaining Documentation, Obtaining Support, and Security Guidelines

System Requirements

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

•Cisco IOS Software Release

•Supported Hardware

•Files in Cisco AXP 1.5.3

•Upgrading and Downgrading to a New Software Release

•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.3 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

Note To use Cisco EEM events, you need to have one of the following feature licenses:
DATA, UC, or SEC.

You can download the Cisco AXP 1.5.3 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.

Cisco AXP uses the netconf protocol to provide the programmatic interface for the Cisco IOS CLI API. Netconf is supported over two transport protocols: BEEP and SSH.

Using netconf/SSH is strongly recommended. Netconf/SSH requires a crypto (K9) Cisco IOS software image. Netconf/SSH offers security on the Cisco IOS side. Credentials such as username/password must be supplied on the Cisco AXP side for the connection to be established.

For further information, refer to the "Netconf" section in the Appendix of the Cisco Application eXtension Platform 1.5 Developer Guide.

Supported Hardware

Cisco Integrated Services Router (ISR) and Cisco ISR G2s are supported by Cisco AXP.

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

For Cisco ISR G2s, we recommend using Cisco IOS Release 15.0(1)M1 and higher.

Note For the following Cisco ISR G2s: 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.

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

1.5.2, 1.5.3

2921

—

1.5.x

1.5.x

—

1.5.x

1.5.2, 1.5.3

1.5.2, 1.5.3

2951

—

1.5.x

1.5.x

1.5.x

1.5.x

1.5.2, 1.5.3

1.5.2, 1.5.3

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

1.5.2, 1.5.3

3925E

—

1.5.2, 1.5.3

1.5.2, 1.5.3

1.5.2, 1.5.3

—

1.5.2, 1.5.3

1.5.2, 1.5.3

3945

—

1.5.x

1.5.x

1.5.x

1.5.x

1.5.2, 1.5.3

1.5.2, 1.5.3

3945E

—

1.5.2, 1.5.3

1.5.2, 1.5.3

1.5.2, 1.5.3

—

1.5.2, 1.5.3

1.5.2, 1.5.3

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.066 GHz, 512MB, 4GB eUSB

SM-700

SM-SRE-700-K9

1.066 GHz, 512MB, 4GB eUSB

SM-900

SM-SRE-900-K9

1.86GHz dual core CPU, 4 GB


Files in Cisco AXP 1.5.3

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

•Cisco AXP Product Files for Cisco SM SRE Service Modules

•Cisco AXP Software Development Kit

Cisco AXP Product Files for Cisco SM SRE Service Modules

The compressed archive axp-k9.sme.1.5.3.tar.gz contains all package files associated with Cisco AXP for service modules such as SM-SRE-700-K9, SM-SRE-900-K9 (SM SRE service modules). The package files are shown in Table 3.

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

Filename
Purpose

axp-helper-k9.sme.1.5.3

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

axp-k9.sme.1.5.3.pkg

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

axp-k9.sme.1.5.3.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.3.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.3.pkg.install.sre

Installer Tcl1 script.

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

Installer Tcl script header.

axp-k9.sme.1.5.3.key

SRE keyfile.

axp-timezone.sme.1.5.3.pkg

AXP Timezone package file.

axp-timezone.sme.1.5.3.prt1

AXP Timezone payload file. Contains required time zone definitions.

axp-app-dev.sme.1.5.3.pkg

Application Development add-on package file.

axp-app-dev.sme.1.5.3.prt1

Application Development add-on payload file.

1 Tcl = Tool Command Language


Cisco AXP Software Development Kit

Compressed archive axp-sdk.1.5.3.tar.gz contains the Cisco AXP Software Development Kit (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 Cisco Application eXtension Platform 1.5 User Guide.

•Packaging Your application Using 1.5.3 SDK

•Clean Installing Cisco AXP 1.5.3

•Upgrading from Cisco AXP 1.5.x to Cisco AXP 1.5.3

•Upgrading from Cisco AXP 1.1.x to Cisco AXP 1.5.3

•No Downgrading from Cisco AXP 1.5.3 to Cisco AXP 1.1.x

•Clean Installing Cisco AXP 1.1.x on Cisco AXP 1.5

Packaging Your application Using 1.5.3 SDK

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

Clean Installing Cisco AXP 1.5.3

There are three options to clean install Cisco AXP 1.5.3 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.3.

Option 1

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

For service modules only, make sure that all AXP 1.5.3 install files are located in the same FTP directory. Check that the files in Table 3 are present.

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.3.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 the system to reboot.


Option 2

Step 1 Clean install Cisco AXP 1.5.3:

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

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

Wait for the system to reboot.

Step 2 Install your application separately: 

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

Wait for the system to reboot.

Option 3

Step 1 Bundle your application with Cisco AXP 1.5.3.

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 the system to reboot.

Upgrading from Cisco AXP 1.5.x to Cisco AXP 1.5.3

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

Step 1 Bundle your application with Cisco AXP 1.5.

Step 2 Upgrade to the bundle package: 

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

Wait for the system to reboot.

Upgrading from Cisco AXP 1.1.x to Cisco AXP 1.5.3

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

Option1

Step 1 Upgrade AXP from 1.1.x to 1.5:

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

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

Wait for the 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 the 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 Cisco AXP 1.5.

Step 2 Upgrade to the bundle package: 

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

Wait for the system to reboot.

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

Downgrade of Cisco AXP or your application from Cisco AXP 1.5.3 to Cisco AXP 1.1.x is not allowed. You must clean install Cisco 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 these 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 the system to reboot.

Step 2 Install your application separately: 

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

Wait for the 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.3.

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

Technical Support: http://www.cisco.com/techsupport/ Copyright (c) 1986-2009 by Cisco 
Systems, Inc.

New and Changed Information

New Software Features in Cisco AXP 1.5.3

The following software features are new for Cisco AXP 1.5.3:

•NFS Client

•Virtual Frame Buffer

NFS Client

The NFS client is a new feature that can be used to access an NFS server from a Cisco AXP service module.

For further details of NFS client, refer to:

•"NFS Client" in the Cisco AXP Optional Features section of the Cisco Application eXtension Platform 1.5 Developer Guide.

•"Displaying Mount Points for an NFS Server" in the
Cisco Application eXtension Platform 1.5 User Guide

•New and Modified Commands in Cisco AXP 1.5.3

Virtual Frame Buffer

The virtual frame buffer is a feature in Cisco AXP that supports a virtual graphical user interface and desktop clients such as VNC.

A virtual graphical user interface is supported by Cisco AXP on the following platforms:

•VMWare—a VMWare VM already has a virtual hardware frame buffer, by default. Therefore, the application itself does not need to enable a virtual frame buffer. For an example, refer to the "Gnome on AXP Demo" on the documentation page of the Cisco AXP Cisco Developer Network.

•NME and SME platforms—the application needs to install linux virtual frame buffer kernel modules.

Installing Virtual Frame Buffer Kernel Modules

To enable the virtual frame buffer, for applications running on NME, SME platforms, the application must be packaged with an authorization bundle that has kernel module capability.

To install the virtual frame buffer kernel modules, the application also requires the following entries in its capability configuration file: 

@MODULES=


fb.ko


fb_sys_fops.ko


sysfillrect.ko


syscopyarea.ko


sysimgblt.ko


vfb.ko vfb_enable=1

For more information on the capabilities configuration file, refer to the Cisco AXP Advanced Features Guide.

After the virtual frame buffer kernel modules are loaded, an application can use a standard linux OS install method, such as the YUM package manager, to install a graphical subsystem and create a virtual graphical user interface.

Basic Safeguards for Securing the Cisco AXP Router/Blade

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 also provisions to encrypt this password. For more information, 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.

Limitations and Restrictions

Possible Failure of the eventapid Process

The eventapid daemon process may crash. After an eventapid failure, the system automatically restarts the eventapid daemon process.

The failure of the eventapid process is more likely to occur when the event notifications are higher than one event per second. The failure can occur on any hardware platform used with Cisco AXP, such as NME, AIM2, ISM, and SM. Evidence of the failure is shown in the messages.log.

The show cores command displays the core files on the screen.

The show log message.log command shows messages such as the following: 

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

The show processes command gives a list of AXP processes. If the command is issued shortly before the system automatically restarts the eventapid daemon, then the eventapid daemon process is shown as "dead". If the command is issued after the eventapid daemon has restarted, the health status for the daemon is shown as "alive".

Workaround

After the eventapid process crashes, previously registered events become inactive. When the eventapid process restarts the application must reregister the events.

To reregister the events after the eventapid restarts, use a connection handler callback procedure in the application.

A status of 1 indicates that the eventapid daemon is alive. A status of 0 indicates that the eventapid daemon is dead.

Within the 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 "Java Example 2" in the "Event API" section of the Cisco Application eXtension Platform 1.5 Developer Guide.

Caveats

Open caveats for Cisco AXP 1.5.3 are described in the "Open Caveats for Cisco AXP 1.5.3" section. Selected closed caveats are described in the "Closed Caveats for Cisco AXP 1.5.3" section.

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.

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 for Cisco AXP 1.5.3

The open caveats in Cisco AXP 1.5.3 are as follows:

•CSCte99057: Installation of rpm file fails with a 'bad magic' error

•CSCtf63209 Installation of AXP onto SRE via router intermittently fails

•CSCtg15475 ciscoipc crash

CSCte99057: Installation of rpm file fails with a 'bad magic' error

Symptom    Installation of rpm file fails with a "bad magic" error.

Conditions   Occurs when attempting to install an rpm file created using a later version of rpmbuild than the version supported by Cisco AXP.

Workaround   Replace the rpm binaries and libraries in the guest OS with a later version of rpm from the CentOS linux distribution. Manually invoke this new rpm; for example, using a command such as:
rpm -i <rpm file>. The same command can be used in a post install script.

Note After replacing the rpm binaries and libraries in the guest OS, do not use the automated method for installing rpm files that places rpms in the third_party_rpms_repository. This method does not work because the rpm uses older binary files in the host OS.

CSCtf63209 Installation of AXP onto SRE via router intermittently fails

Symptom    Installation of Cisco AXP via router fails with error message "netboot image corrupted".

Conditions   Installation of Cisco AXP onto SRE hardware.

Workaround   Retry installation.

CSCtg15475 ciscoipc crash

Symptom    The ciscoipc process may crash under a stress condition. The failure of the process is more likely to occur when the event notifications are higher than one event per second. This issue is not a specific to any particular platform. It can occur on any platforms such as NME, AIM2, ISM and SM.

This issue affects only EEM related events.

As a result of the failure, the application is no longer able to receive EEM events and it is not able to register for a new event.

After a new event registration attempt, the application receives the error message "INIT_FMP_NULL".

/var/log/ciscoipc.log may include the following:

INFO: This application received signal.

INFO: Calling abort to dump the core.

The show serviceapi ios-event connection command shows "no ios-event connections".

The show cores command displays the core files on the screen.

The show processes command gives a list of AXP processes and the ciscoipc process is shown as "dead".

Conditions   The ciscoipc process may crash under a stress condition.

Workaround   Reload the service module.

Closed Caveats for Cisco AXP 1.5.3

The closed caveats in Cisco AXP 1.5.3 are as follows:

•CSCtf25557 Speed on the Cisco IOS side Remains Unchanged

•CSCtc79779 Bind Interface vc_net_add() Error

CSCtf25557 Speed on the Cisco IOS side Remains Unchanged

Symptom    From the virtual instance, when an application sets the speed for a serial device, the speed is not set on the corresponding line on Cisco IOS side.

Conditions   If the application tries to set the speed to 19200 for a serial device, on the Cisco IOS side the default speed of 9600 remains unchanged.

Workaround   None.

CSCtc79779 Bind Interface vc_net_add() Error

Symptom    After trying to bind to any interface such as physical interfaces eth1, or mgf0, or to virtual interfaces such as vlan, or sub, an error occurs: naddress: vc_net_add()

Conditions   Occurs only if the application has the CISCO_ADVANCED_NET_ADMIN capability turned on.

Workaround   None. The CISCO_ADVANCED_NET_ADMIN capability gives the application access to all interfaces on the host including creating/changing/removing interfaces. There is no point in using bind interface for an application that can already access all interfaces on the system. The application can create or modify any networking configurations in the guest OS when the CISCO_ADVANCED_NET_ADMIN capability is enabled.

New and Modified Commands in Cisco AXP 1.5.3

The following commands were introduced for Cisco AXP 1.5.3:

•bind filesystem

•show mounts

bind filesystem

To bind (or mount) a local subdirectory of /mnt/filesystem to the NFS server, use the bind filesystem command in Cisco AXP application service configuration mode.

bind filesystem nfs_server remote_path [bind_point]

To unmount the subdirectory, use the no form of the command:

no bind filesystem nfs_server remote_path [bind_point]

Note If the /mnt/filesystem/ directory contains no subdirectories, the bind filesystem command fails with the error: "ERROR: There must be at least one subdirectory listed in /mnt/filesystem/ to mount to".

Syntax Description

nfs_server

IP address of NFS server

remote_path

Destination path of NFS server

bind_point

Name of sub-directory of /mnt/filesystem—bind_point is only required when there is more than one subdirectory of /mnt/filesystem


Command Default

None

Command Modes

Cisco AXP application service configuration mode.

Command History

Cisco AXP Version
Modification

1.5.3

This command was introduced.


Examples

Bind to NFS Server from the Service Module: Example

In this example, remote location 192.168.24.4:/local/nfs is mounted in the guest OS. The command specifies the nfs_server (192.168.24.4), remote_path (/local/nfs). The bind_point is not specified. When the bind_point is not specified there must be only one subdirectory of /mnt/filesystem. This unnamed subdirectory of /mnt/filesystem is bound to the remote location. 

axp# config t

axp(config)# app-service App

axp(config-App)# bind filesystem 192.168.24.4 /local/nfs

Bind to NFS Server from an Application using the AXP CLI API: Example

If an application requires the use of a mount to the NFS server, it can run the command using the
AXP CLI API. The following line of code calls the bind filesystem command from a bash script: 

bash-3.2# appreapi --mode config "app-service App,bind filesystem 192.168.24.4 
/local/nfs/discus"

The AXP CLI API can be used from programs written in the following languages: C/C++, Java, Perl, Python, and Bash. Refer to the "AXP CLI API" section of the Cisco Application Extension Platform 1.5 Developer Guide.

Related Commands

Command
Description

show mounts

Lists the local mount points that are bound to the NFS server.


show mounts

To list the local mount points, use the show mounts command in Cisco AXP application service configuration mode.

If no mount points are present, the message "There are no active mounts" appears.

show mounts

Syntax Description

This command has no arguments or keywords.

Command Default

None.

Command Modes

Cisco AXP EXEC mode.

Command History

Cisco AXP Version
Modification

1.5.3

This command was introduced.


Examples

In this example, the show mounts command shows the following information:

APP NAME

LOCAL MOUNT POINT—the local mount point is /mnt/filesystem/my_mount2 (where the mount is accessible from within the guest OS).

SERVER—the NFS server is displayed: 192.168.24.11:/media0

PINGABLE?—the server is "pingable", so True is displayed—the server is pingable if it can be pinged using the ping command.

NFS ACCESSIBLE?—the server is "NFS accessible", so True is displayed—the server is determined as being accessible if an ls command can be successfully performed on the bind point. 

se-Module# show mounts

APP NAME:  iss_test_cat3

    LOCAL MOUNT POINT:  /mnt/filesystem/my_mount2

    SERVER:  192.168.24.11:/media0

	BOUND IN APPLICATION?:  True

    PINGABLE?:  True

	NFS ACCESSIBLE?:  True


Related Commands

Command
Description

bind filesystem

Binds (or mounts) a local subdirectory of /mnt/filesystem to the NFS server.


Related Documentation

The following sections describe the documentation available for the Cisco AXP and Cisco ISR's. 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 the Cisco AXP. 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

Commands in Cisco AXP 1.1, 1.5.1, and 1.5.2, are described in the following documents:

•Cisco Application Extension Platform 1.1 Command Reference

•Release Notes for Cisco AXP 1.5.1

•Release Notes for Cisco AXP 1.5.2

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

•Cisco 2800 Series Hardware Installation

•Cisco 3900 Series and Cisco 2900 Series Hardware Installation Guide

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

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

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

Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

© 2010, Cisco Systems, Inc. All rights reserved.