Table Of Contents
Release Notes for Cisco Application eXtension Platform (AXP) 1.5.1
Cisco AXP Software Development Files
Upgrading and Downgrading to a New Software Release
Packaging Your application Using 1.5.1 SDK
Clean Installing AXP 1.5.1 Release
Upgrading from Cisco AXP 1.1.x to Cisco AXP 1.5.1
Downgrading from Cisco AXP 1.5.1 to Cisco AXP 1.1.x
Clean Installing Cisco AXP 1.1.x on Cisco AXP 1.5
Determining the Software Version
New Features and Enhancements in Cisco AXP 1.5.1
Cisco AXP 1.5.1 Cisco Software Licensing (CSL)
Basic Safeguards for Securing AXP Router/Blade
Resolved Caveats- Cisco AXP Version 1.5.1
Open Caveats- Cisco AXP Version 1.5.1
New and Modified Commands in Cisco AXP 1.5.1
clear security ssh known-hosts
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for Cisco Application eXtension Platform (AXP) 1.5.1
First Published: October 16, 2009Last Updated: September 14, 2010, OL-14273-01These release notes support the software for the Cisco Application eXtension Platform (Cisco AXP). To see if your software or hardware platforms are affected, view the field notices for Cisco IOS software version 12.4 (T) at http://www.cisco.com/warp/public/tech_tips/index/cfn.html. (You need to have an account on cisco.com to view the field notices.)
Contents
•
New Features and Enhancements in Cisco AXP 1.5.1
•
•
•
•
System Requirements
This section describes the system requirements for Cisco Application eXtension Platform Version 1.5.1 and includes the following sections:
•
•
Cisco IOS Software Release
Cisco AXP 1.5.1 supports routers with the following Cisco IOS releases.
•
–
–
–
–
You can download the Cisco AXP 1.5.1 image from www.cisco.com. Navigate the website as shown in the following steps:
Step 1
Step 2
Supported Hardware
Cisco AXP integrates with the Cisco IOS software crypto images, including the following image packs:
•
•
•
•
Cisco AXP integrates with the following Cisco IOS software images:
•
•
•
Table 1 lists the Cisco routers and service modules supported by different versions of Cisco AXP.
Table 1 Cisco AXP Supported Routers and Modules
Service Module891, 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
2921
—
1.5.x
1.5.x
—
1.5.x
2951
—
1.5.x
1.5.x
1.5.x
1.5.x
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
3945
—
1.5.x
1.5.x
1.5.x
1.5.x
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.
Files in Cisco AXP 1.5.1
Files in Cisco AXP 1.5.1 are explained in the following sections:
•
Cisco AXP Product Files
Cisco AXP product files are described in the following sections:
•
•
Cisco AXP Product Files for NME and AIM2 Service Modules
Compressed archive axp-k9.nme.1.5.1.tar.gz contains all package files associated with Cisco AXP on NME and AIM2 service modules. AIM2 service modules use the same package files as NME service modules. The package files are shown in Table 3.
Cisco AXP Product Files for ISM SRE Service Modules
Compressed archive axp-k9.sme.1.5.1.tar.gz contains all package files associated with Cisco AXP on ISM SRE service modules. The package files are shown in Table 4.
Cisco AXP Software Development Files
This section describes the Cisco AXP software development files:
•
•
Cisco AXP Software Development Kit (SDK)
Compressed archive axp-sdk.1.5.1.tar.gz contains the Cisco AXP SDK tool for building third-party applications.
Cisco AXP Software Development Files for VMware
Compressed archive axp-k9.vmw.1.5.1.tar.gz contains the Cisco AXP Software Development Files for VMware. The package files are shown in Table 5.
Table 5 Cisco AXP 1.5.1 Base Package for VMware: axp-k9.vmw.1.5.0.tar.gz
axp-k9.vmw.1.5.1.vmdk
Cisco AXP VMware image file.
axp-k9.vm.vmw.1.5.1.vmx
Cisco AXP VMware header file.
Upgrading and Downgrading to a New Software Release
For more information see the "Installing and Upgrading Software" chapter of the Cisco Application eXtension Platform 1.5 User Guide.
•
•
•
•
•
Packaging Your application Using 1.5.1 SDK
Applications that are not packaged using 1.5 SDK will not run on AXP 1.5.
During packaging with 1.5 SDK, make sure you use the same UUID for your application as before and give a different version number to your application. This will make sure the application is identified and upgraded correctly when upgrade CLI commands are used.
Clean Installing AXP 1.5.1 Release
There are two options to clean install AXP 1.5 that include your application created using the AXP 1.5 SDK.
Note
Option 1
Step 1
Make sure axp-k9.xxx.1.5.1.prt1, axp-installer-k9.xxx.1.5.1.prt1 and axp-timezone.xxx.1.5.1.prt1 are also in the same ftp directory as axp-k9.xxx.1.5.1.pkg.
software install clean url ftp://<ftpserver>/axp-k9.xxx.1.5.1.pkgWait for system to reboot.
Step 2
software install package url ftp://<ftpserver>/application.pkgWait for system to reboot.
Option 2
Step 1
Step 2
software install clean url ftp://<ftpserver>/bundle.pkgWait for system to reboot.
Upgrading from Cisco AXP 1.1.x to Cisco AXP 1.5.1
There are two methods to upgrade from AXP 1.1.x to AXP 1.5 and your application created by 1.5 SDK (applications that are not packaged using 1.5 SDK will not run on AXP 1.5):
Option1
Step 1
(Make sure axp-k9.xxx.1.5.1.prt1, axp-installer-k9.xxx.1.5.1.prt1 and axp-timezone.xxx.1.5.1.prt1 are also in the same ftp directory as axp-k9.xxx.1.5.1.pkg)
software install upgrade url ftp://<ftpserver>/axp-k9.xxx.1.5.1.pkgWait for system to reboot. This will upgrade Cisco AXP from 1.1.x to 1.5.
Step 2
software install package url ftp://<ftpserver>/application.pkgWait 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
Step 2
software install upgrade url ftp://<ftpserver>/bundle.pkgWait for system to reboot.
Downgrading from Cisco AXP 1.5.1 to Cisco AXP 1.1.x
Downgrade of AXP and/or your application from AXP 1.5.1 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 these steps:
Step 1
software install clean url ftp://<ftpserver>/axp-k9.xxx.1.1.x.pkgWait for system to reboot.
Step 2
software install add url ftp://<ftpserver>/application.pkgWait 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.51.
Determining the Software Version
To determine the version of Cisco AXP software currently running on your Cisco AXP service module, log into the service module, and enter the show software version EXEC command.
The following sample output from the show software version command indicates the version number on the first output line.
Application eXtension Platform (AXP) version (1.5.1)Technical Support: http://www.cisco.com/techsupport/ Copyright (c) 1986-2009 by Cisco Systems, Inc.New Features and Enhancements in Cisco AXP 1.5.1
Table 6 lists the main feature changes for Cisco AXP 1.5.1.
Table 6 New Features in Cisco AXP 1.5
New Platforms
AIM2-APPRE-104-K9 (600 MHz, 512 MB eUSB)
ISM-SRE-300-K9 (1.066 GHz, 512MB, 4G eUSB)
Permanent license SKU: FL-AXP-ISM-GPServices Ready Engine (SRE)
SRE enables Pay-As-You-Grow model by decoupling HW-Application. Customers can order HW without any Applications installed and can purchase Cisco Software License (CSL) enabled Applications later and install them.
Cisco Software Licensing (CSL)
AXP 1.5 enables Cisco Software Licensing (CSL) to manage feature entitlements for SRE enabled Platform SKUs (ISM-SRE-xxx)
Cisco AXP 1.5 software has a General Purpose license (AXP-GP-LIC) which is required for hosted applications to run. There is a 60 day evaluation license bundled with the 1.5 SRE image which can be utilized to evaluate the 1.5 AXP hosting environment. This evaluation license can be replaced with a permanent license (purchased) within the 60 day trial period.
The AXP CSL framework also supports custom Cisco or third party licenses via dynamic license policies.
•
•
•
•
Enables application auto-startup when required licenses are enabled/activated.
Kernel
Linux 2.6.22.10 kernel is supported
Guest OS/
AXP Reference OS - AXPOS
AXP User Defined Linux Environment- AXPUDL•
•
•
–
–
•
Optional features
•
•
•
Resource Limitation
When the built-in API functionality is activated via package dependency, the system will reserve additional resources for the AXP host due to added resource usage requirements.
API support
•
•
Timezone support
•
•
•
•
•
•
Show Tech Support enhancements
•
•
Customizable CLI support
Third party customizable CLI output support
Installation
•
•
Packaging Tool Options
•
–
–
–
–
user-defined-linux: If enabled, AXPOS is not provided within the virtual instance. Instead, the application should provide it's own operating system (see the feature highlights for AXP OS - AXPOS User Defined Linux - AXPUDL)
•
–
SDK
The Cisco AXP SDK contains all of the 1.5 AXPOS RPM's installed in the VI. Developers can extract these RPM's into a directory using the rpm_extractor.sh tool or the Linux RPM command. By extracting these RPMs into a single directory, the developer can create a "chroot" environment which is equivalent to the Linux environment an application gets when installed on AXP. This environment can be used to test whether all libraries required by the application are present.
Table 7 lists the optional features supported by Cisco AXP 1.5.1.
Table 7 Optional Features
IOS CLI API
8cec8ee5-54c3-4667-b62e-d4a31805d44
AXP CLI API
-
Basic service—You can use this API without having to package your application with a dependency.
CLI Plugin
b4b0ee92-cf8e-472b-8434-e8e7412ec71a
If you are using a CLI plug-in developed at a lower version than Cisco AXP 1.5, you must re-compile and re-link the CLI plug-in. Refer to the "CLI Plug-in Distribution Service" section of the Cisco Application eXtension Platform 1.5 Developer Guide.
Remote Serial Device
7a013f0e-07cb-4c25-8122-4a0af7704c3b
Application Development
5d9267f0-f9c2-11db-8f0d-001635a94464
This is the only optional feature currently requiring a separate package to be downloaded, for example: axp-app-dev.nme.1.5.0.pkg. Refer to the "Application Development Package" section of the Cisco Application eXtension Platform 1.5 Developer Guide.
Perl
-
In lower versions of Cisco AXP than 1.5, Perl was an add-on package. From Cisco AXP 1.5, add Perl as an RPM package.
Tomcat server
-
In lower versions of Cisco AXP than 1.5, Tomcat was an add-on package. From Cisco AXP 1.5, add Tomcat as an RPM package.
SSH
-
SSH server that runs in a virtual instance. In lower versions of Cisco AXP than 1.5, ssh was an add-on package. From Cisco AXP 1.5, add ssh as an RPM package.
AXP SysInfo API
-
Basic service—You can use this API without having to package your application with a dependency on the package.
AXP SysOp API
-
Basic service—You can use this API without having to package your application with a dependency.
Time Zone
-
Basic service—Timezone sharing is enabled by default. You can disable timezone sharing by specifying --share-timezones=OFF when you package the application.
Java
-
Add Java as an RPM package. Download the
JRE 6 .rpm.bin from the software download website at sun.com.
Cisco AXP 1.5.1 Cisco Software Licensing (CSL)
Cisco AXP 1.5.1 enables Cisco Software Licensing (CSL) to manage feature entitlements for SRE enabled Platform SKUs (ISM-SRE-xxx)
Cisco AXP 1.5.1 software has a General Purpose license (AXP-GP-LIC) which is required for hosted applications to run. The General Purpose license SKU for ISM platforms is FL-AXP-ISM-GP. There is a 60 day evaluation license bundled with the 1.5 SRE image which can be utilized to evaluate the Cisco AXP 1.5 hosting environment. This evaluation license can be replaced with a permanent license (purchased) within the 60 day trial period.
The Cisco AXP CSL framework also supports custom Cisco or third party licenses via dynamic license policies.
•
•
•
•
Enables application auto-startup when required licenses are enabled/activated.
Limitations and Restrictions
Disable CDP
For Cisco AXP 1.5.1, we recommend that you disable cdp. For further information refer to the thread:
AXP 1.5.1 users should disable CDP on the AXP Product Announcements forum at http://developer.cisco.com/web/axp.do command
For Cisco AXP 1.5.1 and previous versions, issuing the do command through the Cisco AXP IOS Service API, always returns "OK". If the do command works or fails, the return value is always the same—"OK".
However, issuing the do command through a Cisco IOS CLI console session returns the correct error messages when the do command fails.
Basic Safeguards for Securing AXP Router/Blade
In order to improve the security of your system, we suggest the following actions:
•
•
Following this safeguard ensures that users attempting a privileged CLI operation need to go through #enable mode and password authorization.
•
Caveats for Cisco AXP 1.5.1
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
•
•
Resolved Caveats- Cisco AXP Version 1.5.1
•
•
•
•
•
•
•
•
•
•
Open Caveats- Cisco AXP Version 1.5.1
•
•
•
•
•
•
•
•
•
•
•
•
•
CSCtb23878 "Show int" command causes the AXP platform on VMWare to hangSymptom CLI hang
Conditions
Workaround
CSCtb24429 VMware Blade: CDP not workingSymptom # show cdp
show cdp^% Invalid input detected at '^' marker.Conditions
Workaround
•
This feature provides an interface for Cisco IOS event Registration and notification and was supported in AXP release 1.1.5. EEM support will be enabled in a subsequent AXP release.
The user is notified via one of the following:
–
******************************************************* Upgrade Aborted ** EEM Event Notification API is currently installed ** but is not supported in AXP 1.5.1, ** Please uninstall EEM API before upgrading *******************************************************User may uninstall EEM and proceed with the upgrade.
–
UUID 6aee7d85-980a-4e20-b15a-c8ac882a968d (1.1.5 EEM)
UUID 545c3671-c4bc-43b8-bce4-690123ab9d4d (1.5.1 EEM)
will yield the following error message:
pkg_build.sh: ERROR: UUID: 545c3671-c4bc-43b8-bce4-690123ab9d4d is reservedpkg_build.sh: for the IOS Event API feature. This feature is notpkg_build.sh: supported in the current AXP release and cannot bepkg_build.sh: specified as a dependency.pkg_build.sh:pkg_build.sh: Invalid value specified for depsRemove the dependency on EEM for packaging to succeed.
CSCtb89345 Found axpcsld core while running regression on tech-support suite
CSCtb90314 Found ipcDaemon core while running regression on RPM test suiteSymptom "show cores" will list:
SIZE LAST_MODIFIED_TIME NAMExxxxxx Tue Sep 15 05:49:03 GMT 2009 cores.prev.ipcDaemon.xxxxxxxxx Tue Sep 15 05:49:03 GMT 2009 cores.prev.axpcsld.xxxThe timestamp should be around the time the blade was reloaded.
Conditions
Workaround
"clear core name <coreFileName>" can be used to remove an individual core file.
"clear cores" can be used to remove all core files.
CSCtb95982 AXP 1.1.x EEM add-on may corrupt AXP when installed on AXP 1.5Symptom The application will be listed as offline due to a missing dependency.
Conditions
Workaround
CSCtb96110 Graceful Shutdown button on Service Module does not workSymptom The less-than-one-second graceful shutdown press action is ignored by the system.
Conditions
Workaround
CSCtb98215 cserial8250 UART intermittently locks upSymptom The following error is seen:
# Clear trace fileserial8250: too much work for irq4Conditions
Workaround
CSCtb27120 IOS API supports a maximum of 600 config commands on AIM2Symptom The following error message is seen if attempting to run more than 600 iosapi commands on AIM2
ERROR: RESPONSE=ERROR: IOS connect failedConditions
Workaround
CSCtb43204 IOS API call rate stress test for 1.5Symptom With 1.5.1 release, sustained IOSAPI stress testing yields a call rate of 2 calls/sec. Users may experience variation in this benchmark from prior AXP releases.
Conditions
Workaround
CSCtb59000 Application does not go to shut state after configuring the shut commandSymptom When the application is configured to shutdown state and within few milliseconds if "show state" command is executed in the exec mode of the application the output of the show command will show initially as "offline-pending" for few seconds and then "online-pending" and then comes online.
Conditions
Workaround
CSCtb45758 Executing commands with sudo access throws errors with AXP 1.5Symptom Configure sudo access with /etc/sudoers with no password execution. i.e.:
user ALL=(ALL) NOPASSWD: ALL
Then do sudo from that account and you see the following error:$ sudo touch /foobaraudit_log_user_command(): Connection refused$Conditions
Workaround
1.
2.
CSCtc00988 "Update pkg_bundle.sh LD_LIBRARY_PATH to include <sdk>/lib/pkg/lib"Symptom While bundling, the following error message may be displayed:
grep: error while loading shared libraries: libpcre.so: cannot open shared object file: No such file or directoryConditions
Workaround
1.
This will create a symlink /lib/libpcre.so -> /lib/libpcre.so.0
2.
a.
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:<axp-sdk>/lib/pkg/lib<axp-sdk>/tools/pkg_bundle.sh ...b.
setenv LD_LIBRARY_PATH "${LD_LIBRARY_PATH}:/<axp-sdk>/lib/pkg/lib"<axp-sdk>/tools/pkg_bundle.sh ...CSCtc35907 Message "ERROR sysdb fixtab ..." appears frequently on console and logSymptom Messages of the form begin appearing frequently (approximately once per minute) on the console:
ERROR sysdb fixtab ref (Invalid argument) from nonpositive refcount (-32767) attr=/sw/dns/host/name, pid=2292'/bin/cdpd'ERROR sysdb fixtab deref (Invalid argument) yields negative refcount (-32767) attr=/sw/dns/host/name, pid=2292'/bin/cdpdand messages of the following form begin appearing frequently (also about once every minute) in messages.log:
Sep 16 11:05:15 localhost superthread: 2009 Sep 16 11:05:15 GMT +0000: superthread: INFO superthread server output ERROR sysdb fixtab ref (Invalid argument) from nonpositive refcount (--32767) attr=/sw/dns/host/name, pid=2477'/opt/IBM-ME-2.3.1/jre/bin/j9 -jcl:foun11 ... /bin/superthread.dat'Over time the refcount in the message will increase.
Conditions
Workaround
CSCta22121 syslog server does not capture the log messages from vserverSymptom Syslog server does not capture any log messages from Virtual Instance.
Conditions
Workaround
2) Bind the new virtual interface to the Virtual Instance
3) Unbind the default interface that is shared between AXP Host and the Virtual Instance
4) Restart Virtual InstanceThe Syslog software in Cent-OS blocks remote logging to any address that resovles to the sender itself. This is done to prevent logging in a loop, which can waste CPU cycles and use up disk space.
New and Modified Commands in Cisco AXP 1.5.1
The following commands are new or have been modified in Cisco AXP 1.5.1.
•
•
broadcast message
To broadcast a message to local and remote network locations, use the broadcast message command in Cisco AXP application service EXEC mode. To disable the broadcast message, use the no form of this command.
broadcast message message
Syntax Description
Command Default
None
Command Modes
Cisco AXP application service EXEC
Cisco AXP EXEC
Command History
Examples
In the following example, the message "test message" is broadcast:
se-Module# broadcast message "test message"clear security ssh known-hosts
To clear known hosts and their server keys from the known hosts table, use the clear security ssh known-hosts command in Cisco AXP application service EXEC mode.
clear security ssh known-hosts host
Syntax Description
Command Default
None
Command Modes
Cisco AXP application service EXEC
Command History
Usage Guidelines
If an SSH server changes its public key, use the clear security ssh known-hosts command to remove the old public key from the known hosts table. Use the show security ssh known-hosts command to display the host name or IP address for a known host in the known hosts table, then use that host name or IP address as the host argument in the clear security ssh known-hosts command to remove the host from the table.
Examples
In the following example, the SSH server with IP address 192.1.147 and its server key is cleared from the known hosts table:
se-Module> clear security ssh known-hosts 192.168.1.47Related Commands
copy log
To copy an application log file to a remote URL, use the copy log command in Cisco AXP application service EXEC mode.
To copy a Cisco AXP host operating system log file to a remote URL, use the copy log command in Cisco AXP EXEC mode.
copy log log-name url ftp/http url
Syntax Description
Command Default
None.
Command Modes
Cisco AXP application service EXEC
Cisco AXP EXEC
Command History
1.0
This command was introduced.
1.5.1
Application files and host files can be referenced from Cisco AXP EXEC mode.
Usage Guidelines
Use this command, in Cisco AXP application service EXEC mode, to copy syslog, trace and custom application log files for a specific application to a remote URL. The standard ftp URL format is supported:
ftp://[user-id:ftp-password@]ftp-server-address[/directory]
The log filename (in both command modes) may contain wildcards * allowing the copying of more than one log file at a time. The matching log files are concatenated.
In Cisco AXP 1.5.1 and higher versions, use this command in Cisco AXP EXEC mode to access both application files and host files. Application files are prefixed with the name of the application and a slash, for example, myapp1/messages.log.
Examples
In the following example, the copy log command copies log file install.log from application "mping" to a remote server:
se-Module(exec-mping)> copy log install.log url ftp://admin:mpg@10.10.67.163/lnstallinfoRelated Commands
copy tech-support
To copy diagnostic information about the host environment from a Cisco AXP host operating system to a remote URL, use the copy tech-support command in Cisco AXP EXEC mode.
copy tech-support url location
Syntax Description
Command Default
None
Command Modes
Cisco AXP EXEC
Command History
Usage Guidelines
The output of this command is a compressed (gzip) tarball (tar) that is uploaded to the specified destination. The tarball includes the running-config, state, resource limits, kernel capabilities, and statistics about the host environment The order in which data is collected remains the same as for the show tech-support command.
In the tarball, the pathnames for the show command output consist of the directory show followed by the name of the show command.
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://myftpserver.example.com/uploads/ts.tar.gzse-Module> copy tech-support url ftp://myusername:mypassword@myftpserver.example.com/uploads/tech.tgzRelated Commands
ip forward
To enable IP forwarding, use the ip forward command in Cisco AXP configuration mode. To disable IP forwarding, use the no form of this command.
ip forward
no ip forward
Syntax Description
This command has no arguments or keywords.
Defaults
IP forwarding is disabled.
Command Default
None.
Command Modes
Cisco AXP configuration
Command History
Usage Guidelines
Use this command to enable IP forwarding so that if Cisco AXP receives a packet that was not destined for it, it forwards the packet to the Cisco Integrated Services Router. If IP forwarding is disabled, and Cisco AXP receives a packet that was not destined for it, it drops the packet.
Examples
In the following example, IP forwarding is enabled:
se-Module (config)> ip forwardip route
To configure a static IP route, use the ip route command in Cisco AXP configuration mode.
To remove the static IP route configuration, use the no form of this command.
ip route {dest-prefix dest-mask forwarding-address [interface interface-name]| table dest-prefix dest-mask forwarding-address}
no ip route {dest-prefix dest-mask forwarding-address | table table-num dest-prefix dest-mask forwarding-address}
Syntax Description
Defaults
None.
Command Default
None.
Command Modes
Cisco AXP configuration
Command History
1.0
This command was introduced.
1.5.1
The interface interface-name keyword and argument were added.
Usage Guidelines
Use this command to configure a static IP route or table for a connected route. If an application is bound to multiple subinterfaces and you want to specify an interface other than the default interface, use the interface keyword.
Examples
In the following example, the static IP route is configured using the destination prefix 10.0.0.0, destination prefix mask 255.255.255.0, and the forwarding router's address 172.16.0.0:
se-Module (config)> ip route 10.0.0.0 255.255.255.0 172.16.0.0In the following example, the static IP route is configured using the destination prefix 10.0.0.0, destination prefix mask 255.255.255.0, the forwarding router's address 172.16.0.0, and the interface ether1:
se-Module (config)> ip route 10.0.0.0 255.255.255.0 172.16.0.0 interface ether1Related Commands
show security ssh known-hosts
To display the known hosts and their server keys, use the show security ssh known-hosts command in Cisco AXP application service EXEC mode.
show security ssh known-hosts
Syntax Description
This command has no arguments or keywords.
Command Default
None
Command Modes
Cisco AXP application service EXEC
Command History
Usage Guidelines
Use this command to display the host name, key type and fingerprint of Secure Shell (SSH) servers in the known hosts table. The possible key types are ssh-rsa and ssh-dsa.
Examples
The following example displays the contents of the known hosts table:
se-Module> show security ssh known-hostshost key-type fingerprint192.168.1.47 ssh-rsa 68:ce:05:7b:58:18:f8:0a:ec:f1:72:fc:70:c9:95:3f192.168.24.30 ssh-rsa 98:03:93:dd:1f:b8:e9:c3:57:7d:93:e9:93:49:c1:e1Related Commands
software install clean
To install a new version of Cisco AXP software, use the software install clean command in Cisco AXP EXEC mode.
software install clean url ftp://ftp-server-ip-address/package-filename}
Syntax Description
url ftp://ftp-server-ip-address/
URL of the FTP server.
package-filename
Name of the package file for the new software.
Command Modes
Cisco AXP EXEC
Command History
1.0
This command was introduced.
1.5.1
The URL of the FTP server was made mandatory.
Usage Guidelines
Use this command to download files for a new installation.
This command cleans the disk. All configuration and voice messages are lost after this step. For future upgrades and installations, verify that a backup has been done. If it has not, abort and do a backup first.
Examples
The following is an example of installing a new version of Cisco AXP software where the FTP server information is included in the command line.
The system enters interactive mode, prompting you for information.
se-Module> software install clean url ftp://10.16.0.1/axp-abc.2.0.pkgRelated Commands
techsupport support shell
To enter the tech-support diagnostic shell, use the techsupport support shell command in Cisco AXP EXEC mode.
techsupport support shell
Syntax Description
This command has no arguments or keywords.
Command Default
None
Command Modes
Cisco AXP EXEC
Command History
Usage Guidelines
Use this command to enter a shell that provides a set of diagnostic utilities you can use to troubleshoot an AXP system and provides read-only access to the /var/log directory. When in the shell, type help to list the utilities provided. Type exit to exit the shell.
Examples
The following example shows what is displayed when a user enters the tech-support shell.
se-Module> techsupport support shellSaving session script in: techshell_session.logThis is a restricted shell environment with a limited set of commandsuseful to technical support personnel for diagnosing the system.Type "help" or ? to find out the list of TechSupport commands.Type "exit" or Cntrl-D to exit.techsupport>This example shows the use of help to display the list of utilities and viewable directories.
se-192-1-1-137> techsupport support shellSaving session script in: techshell_session.logThis is a restricted shell environment with a limited set of commandsuseful to technical support personnel for diagnosing the system.Type "help" or ? to find out the list of TechSupport commands.Type "exit" or Cntrl-D to exit.techsupport> helpTechSupport commands available:awk df free head ls mpstat pidstat sort top vmstatcat du grep iostat more netstat ps tail traceroute wcTechSupport directories viewable:/var/logtechsupport>This example shows the use of more to display messages.log.
techsupport> more /var/log/messages.log08/08/10 15:56:42 system_startup: rsrc_file:/etc/aim_rsrc_file08/08/10 15:56:42 system_startup: Populating resource values from /etc/aim_rsrc_file08/08/10 15:56:43 system_startup: rsrc_file:/etc/default_rsrc_file08/08/10 15:56:43 system_startup: Populating resource values from /etc/default_rsrc_file08/08/10 15:56:44 system_startup: rsrc_file:/etc/products/apphosting/aim_rsrc_file--More--For help using any of the given utilities, please type the name of the utility followed by --help.Related Commands
show tech-support
Displays a summary of the diagnostic information for the application.
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 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
The following documentation is specific to the 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.
•
•
•
•
•
Platform-Specific Documents
Hardware installation guides, configuration and command reference guides, and additional documents specific to the Cisco ISR routers are available at:
•
•
•
•
•
•
•
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation. This guide lists all new and revised Cisco technical documentation. You can also subscribe to the guide using an RSS feed.
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.
2.
3.
4.
5.
6.
"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.
2.
3.
"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.
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.
© 2009, Cisco Systems, Inc. All rights reserved.
