Application Extension Platform 1.x -- Installing an Application
Revision as of 18:23, 17 November 2010
Note: Make sure that the Cisco Application eXtension Platform (AXP) is ready on the service module before running the automated installer.
Telnet to the Cisco 280x ISR
telnet 192.168.1.39 2800_w_axp> enable
Session into the Service Module
2800_w_axp#service-module Integrated-Service-Engine 1/0 status
Example This example shows typical output from sessioning into the service module.
Service Module is Cisco Integrated-Service-Engine1/0 Service Module supports session via TTY line 66 Service Module is in Steady state Getting status from the Service Module, please wait.. AppRuntimeEnvironment 0.0.6 Online on Bryce
Check the output as shown in the previous example. The Cisco AXP service module should be in Steady State and Online should also appear.
Session into the Cisco AXP Service Module
2800_w_axp# service-module Integrated-Service-Engine 1/0 session se-Module>
Make sure that the Cisco AXP service module has sufficient resources to host your application. To view the resources that are currently assigned to all applications, enter the following command:
se-Module> show resource limits
Note: Carefully consider the existing resources and future requirements for applications that have not yet been loaded. Plan the capacity requirements at appropriate intervals. See the "Dedicated Application Resources" section in the Cisco AXP Developer Guide.
Invoke the Installer Tool
On the service module, enter the following command:
se-Module> software install package url ftp://ip-address/tcpdump.pkg username username password password
After the installer downloads the .pkg and .prt files, a virtual instance is created on the Cisco AXP service. The files are unpacked into / (the root) directory of the virtual instance.
Note: The Cisco AXP service module reboots.
Verify Application is in List
After the reboot, check the application is installed by showing all applications:
se-Module> show software packages
Start the Application
se-Module> app-service application name
To show the status of all applications, enter the following command:
se-Module> show app-service state
Note: After an application starts there may be a delay of several minutes before the command shows the application as being online. Example
In this example the virtual instance of application tcptrace is entered in Cisco AXP application service EXEC mode.
se-Module> app-service tcptrace se-Module(exec-tcptrace)>
The session is now in the virtual instance of the tcptrace application, in Cisco AXP application service EXEC mode. When typing commands you can include the ? character which calls a utility that lists the available commands.
An important command to use during this stage of the installation is the show state command. The output is the same as that seen from the service module context above, but for convenience, you can also view the state of your application from the Cisco AXP application service EXEC mode.
To view the state of your application, enter the following command:
se-Module(exec-tcptrace)> show state
Show Resource Limits
To view the individual resource allocation (set during the packaging step) for the tcptrace application, enter the following command:
se-Module(exec-tcptrace)> show resource limits
This command shows resources for one application, and limited information about overall system resources.
Return to start of Getting Started Guide: Cisco AXP Getting Started Guide