 Feedback
|
Table Of Contents
Cisco Application eXtension Platform 1.0 Command Reference
Entering and Exiting the Command Environment
Entering the Command Environment
Exiting the Command Environment
copy syslog-server logs bundle
show app-service status-monitor
syslog-server limit file-rotation
Cisco Application eXtension Platform 1.0 Command Reference
Revised: 8/19/08, OL-15872-01
This guide contains the following sections:
•
Entering and Exiting the Command Environment
Entering and Exiting the Command Environment
This section describes the procedures for entering and exiting the command environment where
Cisco AXP configuration commands are executed, and consists of the following sections:•
•
EXEC and Configuration Modes
The Cisco AXP EXEC and Cisco AXP configuration command modes are similar to the EXEC and configuration modes for Cisco IOS CLI commands.
•
se-Module>•
se-Module> app-service application-nameExample:
se-Module> app-service helloworldse-Module(exec-helloworld)>•
se-Module> configure terminalse-Module(config)>•
Example:
se-Module(config)> app-service helloworldse-Module(config-helloworld)>•
Example:
se-100-0-5-2(config)> app SYSLOG_APP1se-100-0-5-2(config-SYSLOG_APP1)>•
Example:
se-Module (config-interface)> ip route table 10Entering the Command Environment
After the Cisco AXP is installed and active, use this procedure to enter the command environment.
Prerequisites
The following information is required to enter the command environment:
•
•
•
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Exiting the Command Environment
To leave the Cisco AXP command environment and return to the Cisco ISR 2800 command environment, use the exit command.
Example:
se-Module> exitRouter#Cisco AXP 1.0 Commands
•
•
•
•
app-service
To configure the Cisco AXP application hosting environment for a specific application, use the app-service command in Cisco AXP configuration mode.
app-service app-name
Syntax Description
Defaults
No default behavior or values.
Command Default
None.
Command Modes
Cisco AXP Configuration Mode.
Command History
Examples
In the following example, the configuration mode for application "helloworld" is entered.
se-Module(config)> app-service helloworldse-Module(config-helloworld)>Related Commands
bind interface
To attach a networking device to the application environment, use the bind interface command in Cisco AXP application service configuration mode. To detach a networking device from the application environment, use the no form of this command.
bind interface network-interface-name
no bind interface network-interface-name
Syntax Description
Defaults
No default behavior or values.
Command Default
None.
Command Modes
Cisco AXP application service configuration.
Command History
Usage Guidelines
This command attaches or detaches a networking device to or from the application environment. The network-interface-name is the interface name defined in the host, for example, the Ethernet device-name defined in the interface command.
The interface is immediately available to the virtual instance with the execution of a new bind command.
Removing an interface binding with the no prefix displays the following warning messages:
WARNING!!! Reset the hosting environment
WARNING!!! For binding to be removed
Note
ipaddr in the /etc/hosts file is modified when you enter the bind interface command (eth0 is the default).
Examples
In the following example, the Cisco AXP application service EXEC mode for application "helloworld" is entered, then the bind command attaches pre-defined interface eth0 to the application.
se-Module(config)> app-service helloworldse-Module (config-helloworld)> bind interface eth0Related Commands
bind serial
To attach or bind the serial device to the application environment, use the bind serial command in Cisco AXP application service configuration mode. To unattach the serial device to the application environment, use the no form of the command.
bind serial device-id [device-id on hosting environment]
no bind serial device-id [device-id on hosting environment]
Syntax Description
Defaults
No default behavior or values.
Command Default
None.
Command Modes
Cisco AXP application service configuration.
Command History
Usage Guidelines
This command typically follows the app-service <application name> command.The application being a serial application.
Examples
In the following example, the Cisco AXP application service configuration mode for the serial device "serialapp" is entered. Then the serial device is bound to a Cisco IOS side device id of "vtty000".
se-Module(config)> app-service serialappse-Module(config-serialapp)> bind serial vtty000 modemRelated Commands
app-service
Enters Cisco AXP application hosting environment for a specific application.
show device serial
Displays the device ID.
clear cores
To clear 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.
Defaults
No default behavior or values.
Command Default
None.
Command Modes
Cisco AXP application service EXEC.
Command History
Examples
In the following example, clear the core files of a Cisco AXP application in Cisco AXP application service EXEC mode:
se-Module(exec-helloworld)> clear coresRelated Commands
clear core
To clear one specific core file of an application, use the clear core command in Cisco AXP application service EXEC mode.
clear core name core-name
Syntax Description
Defaults
No default behavior or values.
Command Default
None.
Command Modes
Cisco AXP application service EXEC.
Command History
Examples
In the following example, the helloworld-test-core-file is cleared from the application:
se-Module(exec-helloworld)> clear core name helloworld-test-core-fileRelated Commands
clear logs
In Cisco AXP application service EXEC mode, use the clear logs command to clear the content of all log files of the application.
In Cisco AXP EXEC mode, use the clear logs command to clear the content of all host log files.
clear logs
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Default
None.
Command Modes
Cisco AXP application service EXEC.
Cisco AXP EXEC.
Command History
Usage Guidelines
Depending on the mode, the command either clears the contents of all host log files (Cisco AXP EXEC mode) or clears the contents of the application log files (Cisco AXP application service EXEC mode).
Note
Examples
In the following example, the log files are cleared in Cisco AXP application service EXEC mode:
se-Module(exec-helloworld)> clear logsIn the following example, the log files are cleared in Cisco AXP EXEC mode:
se-Module> clear logsRelated Commands
clear log
In Cisco AXP application service EXEC mode, use the clear log command to clear the content of a specific log file of the application.
In Cisco AXP EXEC mode, use the clear log command to clear the content of a specific host log file.
clear log name log-name
Syntax Description
Defaults
No default behavior or values.
Command Default
None.
Command Modes
Cisco AXP application service EXEC.
Cisco AXP EXEC.
Command History
Usage Guidelines
Depending on the mode, use this command to either clear the contents of a specific host log file (Cisco AXP EXEC mode) or clear the contents of a specific application log file (Cisco AXP application service EXEC mode).
Note
Examples
In the following example, the log file messages.log is cleared in Cisco AXP application service EXEC mode:
se-Module(exec-helloworld)> clear log name messages.logIn the following example, the log file sshd.log is cleared in Cisco AXP EXEC mode:
se-Module> clear log name sshd.logRelated Commands
clear syslog-server logs
To clear the content of all syslog files in the /var/remote directory, use the clear syslog-server logs command in Cisco AXP EXEC mode.
clear syslog-server logs
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Default
None.
Command Modes
Cisco AXP EXEC.
Command History
Examples
In the following example, the content of all syslog files in the /var/remote directory is cleared:
se-Module> clear syslog-server logsRelated Commands
clear syslog-server log-name
To clear the contents of a specific syslog server file, use the clear syslog-server log-name command in Cisco AXP EXEC mode.
clear syslog-server log name log-name
Syntax Description
Defaults
No default behavior or values.
Command Default
None.
Command Modes
Cisco AXP EXEC.
Command History
Examples
In the following example, the contents of a specific syslog server file are cleared:
se-Module> clear syslog-server log name remote_messages.logRelated Commands
clock timezone
To set the time zone for the Cisco AXP service module, use the clock timezone command in Cisco AXP configuration mode.
clock timezone [time-zone]
Syntax Description
Command Modes
Cisco AXP configuration.
Command History
Usage Guidelines
The configured NTP server provides the date-stamp system and application functions. The clock timezone command specifies the local time zone where Cisco AXP is installed.
If you know the phrase for the time-zone, enter it for the time-zone value. If you do not know the time zone phrase, leave the time-zone value blank and a series of menus appear to guide you through the time zone selection process.
Examples
In the following example, the United States Pacific Time is selected from the timezone menu:
se-10-0-0-0>config tse-10-0-0-0(config)> clock timezonePlease identify a location so that time zone rules can be set correctly.Please select a continent or ocean.1) Africa 4) Arctic Ocean 7) Australia 10) Pacific Ocean2) Americas 5) Asia 8) Europe3) Antarctica 6) Atlantic Ocean 9) Indian Ocean>? 2Please select a country.1) Anguilla 18) Ecuador 35) Paraguay2) Antigua & Barbuda 19) El Salvador 36) Peru3) Argentina 20) French Guiana 37) Puerto Rico4) Aruba 21) Greenland 38) St Kitts & Nevis5) Bahamas 22) Grenada 39) St Lucia6) Barbados 23) Guadeloupe 40) St Pierre & Miquelon7) Belize 24) Guatemala 41) St Vincent8) Bolivia 25) Guyana 42) Suriname9) Brazil 26) Haiti 43) Trinidad & Tobago10) Canada 27) Honduras 44) Turks & Caicos Is11) Cayman Islands 28) Jamaica 45) United States12) Chile 29) Martinique 46) Uruguay13) Colombia 30) Mexico 47) Venezuela14) Costa Rica 31) Montserrat 48) Virgin Islands (UK)15) Cuba 32) Netherlands Antilles 49) Virgin Islands (US)16) Dominica 33) Nicaragua17) Dominican Republic 34) Panama>? 45Please select one of the following time zone regions.1) Eastern Time2) Eastern Time - Michigan - most locations3) Eastern Time - Kentucky - Louisville area4) Eastern Standard Time - Indiana - most locations5) Central Time6) Central Time - Michigan - Wisconsin border7) Mountain Time8) Mountain Time - south Idaho & east Oregon9) Mountain Time - Navajo10) Mountain Standard Time - Arizona11) Pacific Time12) Alaska Time13) Alaska Time - Alaska panhandle14) Alaska Time - Alaska panhandle neck15) Alaska Time - west Alaska16) Aleutian Islands17) Hawaii>? 11The following information has been given:United StatesPacific TimeTherefore TZ='America/Los_Angeles' will be used.Local time is now: Fri Dec 24 10:41:28 PST 2004.Universal Time is now: Fri Dec 24 18:41:28 UTC 2004.Is the above information OK?1) Yes2) No>? 1se-10-0-0(config)>To select United States Pacific Time using the timezone using the timezone name:
se-10-0-0-0> config tse-10-0-0-0(config)> clock timezone Americas/Los_AngelesRelated Commands
ntp server
Specifies the NTP server.
show clock detail
Displays the clock details.
connect console
To allow third-party applications to integrate their commands to the console shell, use the
connect console command in Cisco AXP application service EXEC mode.connect console
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Default
None.
Command Modes
Cisco AXP application service EXEC.
Command History
Usage Guidelines
This command allows a third party to integrate their own application commands to the console shell. On initiating the command, /bin/console is executed. The third party application must provide its own console file in binary or a script (telnet to their CLI), to cross connect to its CLI shell.
If the application does not provide a console file, the following message appears:
Unable to start console
Examples
In the following example, the shell of an application's virtual instance is entered:
se-Module(exec-tcptrace)> connect console <enter>bash-2.05b#Related Commands
copy syslog-server logs bundle
To bundle all the syslog server log files into a gzip file and copy them to a remote URL, use the
copy syslog-server logs bundle command in Cisco AXP EXEC mode.copy syslog-server logs bundle destination-filename.gz url ftp/http url
Syntax Description
Defaults
No default behavior or values.
Command Default
None.
Command Modes
Cisco AXP EXEC.
Command History
Examples
In the following example, the syslog server log files are bundled into a gzip file and copied to a remote URL:
se-Module> copy syslog-server logs bundle myappslogs.gz url http://testfiles.company.comRelated Commands
copy syslog-server log name
To copy a specific syslog server log file, use the copy syslog-server log name command in
Cisco AXP EXEC mode.copy syslog-server log name log-name url ftp/http url
Syntax Description
Defaults
No default behavior or values.
Command Default
None.
Command Modes
Cisco AXP EXEC.
Command History
Usage Guidelines
The standard FTP URL format is supported:
ftp://[user-id:ftp-password@]ftp-server-address[/directory]
A wildcard * may be used to copy more than one log file at a time.
Related Commands
copy core
To copy a core file to a remote URL, use the copy core command in Cisco AXP application service EXEC mode.
copy core core-name url ftp/http url
Syntax Description
Defaults
No default behavior or values.
Command Default
None.
Command Modes
Cisco AXP application service EXEC.
Command History
Usage Guidelines
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.netRelated 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
Defaults
No default behavior or values.
Command Default
None.
Command Modes
Cisco AXP application service EXEC.
Cisco AXP EXEC.
Command History
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.
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 logs bundle
To copy a tar file containing syslog files and custom application log files on the guest operating system to a remote URL, use the copy logs bundle command in Cisco AXP application service EXEC mode.
To copy a tar file containing syslog files and custom application log files on the guest and host operating systems to a remote URL, use the copy logs bundle command in Cisco AXP EXEC mode.
copy logs bundle destfilename.tar url url
Syntax Description
Defaults
No default behavior or values.
Command Default
None.
Command Modes
Cisco AXP application service EXEC.
Cisco AXP EXEC.
Command History
Usage Guidelines
If you are in In Cisco AXP EXEC mode, this command does not copy remote syslog server log files.
Examples
In the following example, a tar file is copied to a remote server:
se-Module(exec-mping)> copy logs bundle mpg.tar url http://lab:mpg@10.10.67.163/appinfoRelated Commands
hostname
To configure a hostname for the application that is different from the name used for the host, use the hostname command in Cisco AXP application service configuration mode.
To disable the hostname for the application, use the no form of this command.
hostname name
no hostname name
Syntax Description
Defaults
Hostname configured on the host side.
Command Default
None.
Command Modes
Cisco AXP application service configuration.
Command History
Usage Guidelines
This command configures the hostname for the application, if it is different from the hostname configured for the Cisco AXP host. The hostname is limited to 32 characters.
If more than 32 characters are entered, the following error message appears:
hostname size greater than 32
This command modifies configuration directives in file /etc/hosts. The command updates the hostname of the hostname: IP mapping entry.
If the file does not exist, the command creates the /etc/hosts file, and adds an entry to the file.
If the file exists, (for example, if an application package has already bundled its own /etc/hosts file), the new entries are appended to the existing entries and the original entries remain intact.
Examples
In the following example, the initial contents of file etc/hosts are:
etc/hosts:127.0.0.1 localhost.localdomain localhost ## added by cliipaddr hostname.domain hostname ## added by cliFor example, the following commands set the hostname to "myhostname". The original hostname is the hostname of the host (after installing the application, the hostname for the vserver is the same as for the host.)
configure terminalapp-service myapphostname myhostnameThe hostname in the second line of the /etc/hosts file above, (ipaddr hostname.domain hostname) is changed to myhostname.
The /etc/hosts file is created by Cisco AXP if it is not packaged by the user. An /etc/hosts file that is created by the user must contain the first line shown above (starting with "127.0.0.1"). Lines following the first line of the file are created by Cisco AXP.
The IP address, ipaddr in the /etc/hosts file is modified using the bind interface command.
The first binding of the interface provides ipaddr, which is normally eth0. The interface eth0 is bound to each virtual instance by default. Use the bind interface command for multiple bindings.
Related Commands
interface
To configure external network interfaces and enter interface configuration mode, use the interface command in Cisco AXP configuration mode.
interface device-name
Syntax Description
Defaults
None.
Command Default
None.
Command Modes
Cisco AXP configuration.
Command History
Usage Guidelines
The device name can be eth0 or eth1 for a built-in physical interface, eth0:1 for a virtual interface, or eth0.1 for a VLAN interface.
The virtual or VLAN interfaces can be configured only if these interfaces are not bound to the virtual hosting environment. If the interfaces are bound, an error message with the specific device name appears.
For example, for eth0.1 the error message will display:
Error Message eth0.1 still bound to hosting environment(s), unbind first.Do not remove a built-in physical interface. On removal, an error message appears:
Error Message Can not remove the built-in interface eth0/1.Examples
In the following example, the command interface eth0 configures the external network interface eth0, by entering interface configuration mode.
se-Module (config)> interface eth0
se-Module(config-interface)>
Related Commands
bind interface
Attaches or detaches a networking device to or from the application environment.
ip address
To configure the IP address for a network interface, use the ip address command in Cisco AXP interface configuration mode.
ip address ip-address network-mask
Syntax Description
Defaults
None.
Command Default
None.
Command Modes
Cisco AXP interface configuration.
Command History
Usage Guidelines
Use this command to configure the IP address and network mask for the specified network interface. Changing the IP address for a bound interface results in a message warning the user that the application is bound to the interface. To remove the old IP configuration, reset the virtual instance.
Examples
In the following example, the IP address of an interface in Cisco AXP interface configuration mode is specified:
se-Module (config-interface)> ip address 209.165.201.1 255.255.255.224
Related Commands
ip route table
To configure the route table for a connected route, use the ip route table command in Cisco AXP interface configuration mode.
ip route table table-num
Syntax Description
Defaults
None.
Command Default
None.
Command Modes
Cisco AXP interface configuration.
Command History
Usage Guidelines
Use this command to configure the route table for a connected route for source-based routing.
Examples
In the following example, the route table number 10 is configured:
se-Module (config-interface)> ip route table 10
Related Commands
interface
Configures the interface device.
ip address
Configures the IP address for the specified network interface.
ip ssh server
To enable the IP SSH service, use the ip ssh server command in Cisco AXP syslog application configuration mode. To disable the service, use the no form of this command.
ip ssh server [port-num]
no ip ssh server
Syntax Description
Defaults
Port number 22.
Command Default
Enabled.
Command Modes
Cisco AXP syslog application service configuration.
Command History
Usage Guidelines
Use this command to start or stop the SSH server that is located on the specified port number. The range of port numbers that may be used is 1-65535 and the default is 22.
Error messages: Table
Examples
In the following example, the IP SSH server is enabled on port 5000 for application SYSLOG_APP1.
se-100-0-5-2(config)> app SYSLOG_APP1
se-100-0-5-2(config-SYSLOG_APP1)> ip ssh server port 5000
Related Commands
ip ssh interface
Interface on which the sshd daemon listens for an incoming connection.
ip ssh server interface
To enable the interface on which the sshd daemon listens for an incoming connection, use the
ip ssh server interface command in Cisco AXP configuration mode.ip ssh server interface interface
Syntax Description
Defaults
None.
Command Default
None.
Command Modes
Cisco AXP configuration.
Command History
Usage Guidelines
This command specifies the interface on which the sshd process listens for an incoming connection.
If you do not specify this command, the sshd process listens on all interfaces.Related Commands
ip ssh username
To specify an unencrypted or hidden password for SSH tunneling, use the ip ssh username command in Cisco AXP syslog application configuration mode.
To disable tunneling, use the no form of the command.
ip ssh username [tunnel_root | tunnel_user] password clear-password-string
no ip ssh username [tunnel_root | tunnel_user] password clear-password-string
Syntax Description
Defaults
None.
Command Default
None.
Command Modes
Cisco AXP syslog application service configuration.
Command History
Usage Guidelines
For a tunnel user, the startup script decides on the level of access a user can have to perform specific operations.
Related Commands
ip ssh interface
Specifies the interface on which the sshd daemon listens for an incoming connection.
ip local policy route-map
To configure a route map for policy routing, use the ip local policy route-map command in Cisco AXP configuration mode.
ip local policy route-map map-tag
Syntax Description
Defaults
None.
Command Default
None.
Command Modes
Cisco AXP configuration.
Command History
Usage Guidelines
The route map name must match the map-tag in the route-map command.
Examples
In the following example, the route map is configured for policy routing with map-tag=10:
se-100-0-5-2(config)> ip local policy route-map 10
Related Commands
ip access-list standard
To configure a standard access list for the application, use the ip access-list standard command in Cisco AXP configuration mode.
ip access-list standard {acl-name | acl-num}
Syntax Description
Defaults
None.
Command Default
None.
Command Modes
Cisco AXP configuration.
Command History
Usage Guidelines
Use this command to create an access list for source-based route configurations.
To create an entry that specifies the type of packets that you want for further processing, use the permit command in standard ACL subcommand mode (config-std-nacl) to specify the type of packets that must be accepted for further processing.
Include at least one permit entry to create a valid access list.
Cisco AXP 1.0 allows only a single IP address in the access list to be specified.
Examples
In the following example, an access list is created for source-based route configuration.
se-Module (config)> ip access-list standard test
Related Commands
permit
Adds a line to a standard access list specifying the type of packets to be accepted for further processing.
ip domain-name
To configure the domain name for the application, use the ip domain-name command in Cisco AXP application configuration mode. To disable the domain name, use the no form of this command.
ip domain-name dns-server-domain-name
no ip domain-name dns-server-domain-name
Syntax Description
Defaults
No domain name is configured.
Command Default
None.
Command Modes
Cisco AXP application service configuration.
Command History
Usage Guidelines
The domain-name is limited to 64 characters.
If you enter more than 64 characters, the following error message appears:
Error Message domain size greater than 64This command modifies configuration directives in /etc/hosts and /etc/resolv.conf files where the domain name is relevant, and also modifies the search list for hostname lookup and domain directives for local domain name in the /etc/resolv.conf file.
For the /etc/hosts file, this command updates the domain name of the hostname-ip mapping entry.
Example:
/etc/resolv.conf:search cisco.com ## added by clidomain cisco.com ## added by clinameserver x.x.x.x ## added by cli/etc/hosts:10.100.50.10 appre.cisco.com appreUse this command with the ip name-server command to configure the DNS server. The host commands
ip domain-name and ip name-server populate the /etc/resolv.conf file in each installed virtual instance. Changing the configuration results in the updating of host results in the /etc/resolv.conf file.When these commands are used to configure a new name-server and domain-name for a virtual instance (in app-service mode), the /etc/resolv.conf file in that virtual instance is overridden with the new server name and domain name.
The /etc/resolv.conf file in that virtual instance reverts to the host configuration whenever the virtual instance does not have a name-server or domain-name configured.
Configuring the name-server and domain-server in a virtual instance always takes precedence over configuration in the host.
Examples
In the following example, the domain name of the application is changed from mping to mycompany.com:
SE-Module> config tse-10-0-0-0(config-mping)> ip domain-name mycompany.comse-10-0-0-0(config-mping)> ip name-server 10.0.61.1Related Commands
ip name-server
To configure the IP address of the domain name server (DNS) of the application, use the ip name-server command in Cisco AXP application service configuration mode.
To disable the name server, use the no form of this command.
ip name-server ip-address
no ip name-server ip-address
Syntax Description
Defaults
No name server is configured.
Command Default
None.
Command Modes
Cisco AXP application service configuration.
Command History
Usage Guidelines
Use this command with the ip domain-name command to configure the DNS server. A maximum of two DNS servers can be defined. In a Linux environment, the /etc/resolv.conf file typically contains the IP addresses of name servers (DNS name resolvers) that attempt to translate names into addresses for any node available on the network.
The ip domain-name and ip name-server commands in the host populate the /etc/resolv.conf file in each installed virtual instance. Using this command to change the configuration in the host results in the /etc/resolv.conf file being updated.
When these commands are used to configure a new name-server and domain-name for a virtual instance (in app-service mode), the /etc/resolv.conf file in that virtual instance is overridden with the new server name and domain name.
The /etc/resolv.conf file in that virtual instance reverts back to the host configuration whenever the virtual instance does not have a name-server or domain-name configured. Configuring the name-server and domain-server in a virtual instance always takes precedence over configuration in the host.
If an application package has already bundled its own /etc/resolv.conf file, the new entries will be appended to the existing ones and will leave the original ones intact.
Example:
search localdomain ## added by clidomain localdomain ## added by clinameserver x.x.x.x ## added by cliExamples
In the following example, the IP name server of the application is changed from mping to 10.10.61.16:
se-Module> config tse-Module(config-mping)> ip name-server 10.10.61.16se-Module(config-mping)> ip domain-name mycompany.comRelated Commands
limit log-file size
To configure the log file size, use the limit log-file size command in Cisco AXP application service configuration mode.
To disable log file size configuration, use the no form of this command.
limit log-file size size
no limit log-file size size
Syntax Description
Defaults
Default value is 5 MB.
Command Default
None.
Command Modes
Cisco AXP application service configuration.
Command History
Usage Guidelines
This command sets the maximum size of the log file /var/log/messages.log. Each virtual instance writes a syslog to its own file /var/log/messages.log. When this file reaches the limit specified by this command, its contents are moved to a backup log file messages.log.prev and a new messages.log file is started. The range is 0-40 MB with a default size of 5 MB for two files.
megabytes: The range of the log file size from 0-40 MB.
When the value is out of range, the following message appears:
%Invalid input detected at `^' markerIf the log file size configuration is disabled (no limit log-file size), the maximum size of the log file reverts to the default value of 5 MB.
If the maximum size of the log file is set to 0 MB, the minimum file size is 10 KB.
Examples
In the following example, the size of the log file is changed to 10 MB.
se-Module(config-helloworld)> limit log-file size 10Related Commands
show logs
Lists logs in the application environment that reside in the /var/log directory.
limit cpu utilization
To configure the CPU resource usage limits, use the limit cpu utilization command in Cisco AXP application service configuration mode.
To disable setting CPU utilization limits, use the no form of this command.
limit cpu utilization index
no limit cpu utilization index
Syntax Description
Defaults
No default behavior or values.
Command Default
None.
Command Modes
Cisco AXP application service configuration.
Command History
Usage Guidelines
This command modifies the CPU utilization limit when the application is installed. It becomes effective when the application instance restarts.
The CPU utilization range varies between the minimum and maximum limits specified by the package. The specified CPU utilization maximum for a Cisco AXP service module is based on a platform CPU index.
The platform CPU index is specified relative to a value of 10000 assigned to the following configuration:
1.0 GHz Celeron M CPU on the application runtime engine of an NME_APPRE_302-K9 network module. For example, the CPU utilization limit for the AIM_APPRE 102 blade is 3000.Examples
In the following example, the CPU utilization limit is set to 3000, (typical for an AIM_APPRE 102 blade):
se-Module(config-helloworld)> limit cpu utilization 3000Related Commands
show resource limits
Displays the resource limits configured for the application.
limit disk utilization
To modify the disk utilization setup during installation, use the limit disk utilization command in Cisco AXP application service configuration mode.
To disable setting of disk utilization limits, use the no form of the command.
limit disk utilization amount
no limit disk utilization amount
Syntax Description
Defaults
No default behavior or values.
Command Default
None.
Command Modes
Cisco AXP application service configuration.
Command History
Usage Guidelines
This command limits the disk space utilization in a virtual instance. The disk utilization range varies between the minimum limit specified by the package to the maximum limit available to the system.
Examples
In the following example, the disk utilization is set to 100 MB during installation:
se-Module(config-myapp1)> limit disk utilization 100Related Commands
show resource limits
Displays the resource limits configured for the application.
log console
To configure the types of messages to be displayed on the console, use the log console command in Cisco AXP configuration mode. To stop messages from displaying, use the no form of this command.
log console {errors | info | notice | warning}
no log console {errors | info | notice | warning}
Caution
Syntax Description
Defaults
Only fatal error messages are displayed.
Command Modes
CiscoAXP configuration
Command History
Usage Guidelines
The messages on the console display are also saved in the messages.log file. These messages can be used for debugging purposes.
Examples
The following example configures error messages to be displayed on the console:
se-10-0-0-0> config tse-10-0-0-0(config)> log console errorsse-10-0-0-0(config)> exitRelated Commands
log console monitor
To display system messages on the console, use the log console monitor command in Cisco AXP EXEC mode. To stop messages from displaying, use the no form of this command.
log console monitor {module | entity | activity}
no log console monitor {module | entity | activity}
Caution
Syntax Description
Defaults
Only fatal error messages are displayed.
Command Modes
Cisco AXP EXEC
Command History
Usage Guidelines
The messages on the console monitor are also saved in the messages.log file. These messages can be used for debugging purposes.
Examples
The following example displays messages for results of the database entity in the networking module:
se-10-0-0-0> log console monitor networking database resultsRelated Commands
log trace boot
To save the trace configuration upon rebooting, use the log trace boot command in Cisco AXP EXEC mode.
log trace boot
Syntax Description
This command has no arguments or keywords.
Command Modes
Cisco AXP EXEC
Command History
Usage Guidelines
To ensure that the current trace configuration is saved when the Cisco AXP service module is rebooted, use the log trace boot command.
Examples
The following example illustrates the log trace boot command:
se-10-0-0-0>log trace bootRelated Commands
log trace buffer save
To save the current trace information, use the log trace buffer save command in Cisco AXP EXEC mode. To turnoff the log trace, use the no form of this command.
log trace buffer save
no log trace buffer
Syntax Description
This command has no arguments or keywords.
Command Modes
Cisco AXP EXEC
Command History
Usage Guidelines
Current trace information stored in the memory buffer can be saved to a file.
Examples
The following example illustrates the log trace buffer save command:
se-10-0-0-0>log trace buffer saveRelated Commands
show logs
Displays a list of the trace logs.
show trace buffer
Displays the modules and entities being traced.
log trace local enable
To configure tracing messages to a local disk, use the log trace local enable command in Cisco AXP configuration mode.
log trace local enable
Syntax Description
There is no syntax description for this command.
Defaults
None
Command Modes
Cisco AXP configuration
Command History
Usage Guidelines
Enable local tracing to a disk.
Examples
The following example configures tracing toto a local disk:
se-10-0-0-0> config tse-10-0-0-0(config)> log trace local enablese-10-0-0-0(config)> exitRelated Commands
log trace server
To configure tracing messages for remote storage , use the log trace server command in Cisco AXP configuration mode.
log trace server {enable | url url}
Syntax Description
enable
Enables tracing to the FTP server.
url
Designates remote storage directory.
url
FTP URL address.
Defaults
None
Command Modes
Cisco AXP configuration
Command History
Usage Guidelines
Configures tracing messages for remote storage.
Examples
The following example configures tracing remotely:
se-10-0-0-0> config tse-10-0-0-0(config)> log trace server url ftp urlse-10-0-0-0(config)> exitRelated Commands
log server address
To configure the remote logging server, use the log server address command in Cisco AXP application service configuration mode.
To disable the remote logging server, use the no form of this command.
log server address {ip-address | hostname}
no log server address {ip-address | hostname}
Syntax Description
Defaults
No external log server is configured.
Command Modes
Cisco AXP application service configuration.
Command History
Usage Guidelines
This command enables and disables remote logging, and configures the remote logging server. Application syslog messages are sent to the specified log server. The hostname can be an IP address or a name.
When an invalid IP address format such as 0.0.0.0 is entered, the following error message appears:
Error Message 0.0.0.0 is an invalid Host IP addressThis is used to stream out the application logs to the remote syslog server.
Examples
In the following example, IP address 10.1.61.16 is assigned as the external log server:
se-10-0-0-0(config-mping)> log server address 10.1.61.16se-10-0-0-0(config-mping)> exitRelated Commands
show hosts
Displays all configured hosts.
show log
Displays a specific log.
show logs
Displays all logs.
show running-config
Displays the log server as part of the configuration.
log level
To configure the different system log levels, use the log level command in Cisco AXP application service configuration mode.
To disable log levels, use the no form of this command.
log level levels
no log level levels
Syntax Description
Defaults
warn is the default value.
Command Default
None.
Command Modes
Cisco AXP application service configuration.
Command History
Examples
The following example shows the log level being set so that events with LOG_INFO or higher severity are logged:
se-Module(config-myapp)> log level infoUsage Guidelines
log level info logs events with LOG_INFO or higher severity.
In the following example, events within the stdout of a CLI plug-in and the output from System.out.println calls made by the application MyAppMain, are redirected to syslog if they have a log level of LOG_INFO or above.
# java -cp ./app_bin/myApp.jar:/cli_comm/:/usr/lib/java/localsocket.jar:/usr/lib/java/cli_distributio n_vm.jar com.myApp.MyAppMain | /bin/logger -p infoRelated Commands
ntp server
To synchronize the Cisco AXP application system clock with a remote Network Time Protocol (NTP) server, use the ntp server command in Cisco AXP configuration mode.
To disable the Cisco AXP application system clock from being synchronized with an NTP server, use the no form of this command.
ntp server {hostname | ip-address} [prefer]
no ntp server {hostname | ip-address}
Syntax Description
hostname
Hostname of the NTP server.
ip-address
IP address of the NTP server.
prefer
(Optional) Marks the server as preferred.
Defaults
The default is the IP address of the server.
Command Default
None.
Command Modes
Cisco AXP configuration.
Command History
Usage Guidelines
Use this command in conjunction with the clock time command to set the timing functions for Cisco AXP systems and applications.
The prefer option indicates that the specified server is chosen for synchronization from among a set of correctly operating hosts.
Caution
Examples
The following example assigns the server with address 192.168.1.100 as the preferred NTP server:
se-10-0-0-0(config)> ntp server 192.168.1.100 preferThe following example assigns the server with hostname main_ntp as the NTP server:
se-10-0-0-0(config)> ntp server main_ntpRelated Commands
clock timezone
Configures the local time zone.
show clock detail
Displays current clock statistics.
show ntp source
Displays current NTP server statistics.
status-monitor
To configure the status monitor and recovery threshold, use the status-monitor command in Cisco AXP application service configuration mode.
status-monitor monitor_interval Interval-Num recovery_threshold Threshold-Num
Syntax Description
Defaults
Default value for monitor interval is 12 and recovery threshold is 5.
Command Default
None.
Command Modes
Cisco AXP application service configuration.
Command History
Usage Guidelines
Cisco AXP allows third party applications to plug in their status monitoring and allows recovery from a malfunctioned state.
An application must provide one or more watchdog scripts or executable files bundled in their package to use the Cisco AXP application monitoring feature. The number of scripts or executables is dependent on the application, resulting in a unique way of determining the status of the application. For example, it can be based on Process Identifier (PID), or a response to an application ping. Cisco AXP supports Shell scripts and C language executables for application status monitoring.
For more information on watchdog scripts and executables, see the Cisco AXP Developer Guide.
The application status monitor has a heartbeat of 5 seconds, which is the minimum interval used for monitoring. For example, if the monitor interval is set at 12, monitoring of each virtual instance takes place every 12 heartbeat intervals, which is every one minute. You can configure the monitoring interval for a virtual instance through the status-monitor monitor interval command.
The scripts or executables return a status code where zero indicates that the application is healthy and alive. A non zero status code indicates that the application is not functional. When a watchdog script or executable returns a non zero status code, relevant information such as the name of the watchdog script, return status, and time of failure is logged.
A recovery counter counts the number of times the failure takes place, and acts as a delay mechanism for further action. A recovery count of three means that the application monitor has run for three iterations and is receiving either a non zero return status, or the watchdog script has been running for over 3 monitoring intervals and is not returning a value.
You can use the status-monitor monitor interval command for configuring the recovery threshold that decides on the number of recovery counters before taking the next action. When the recovery threshold is reached, the virtual instance restarts and the application monitor continues to run, repeating the monitoring cycle. A virtual instance can restart any number of times.
If you are developing a third party application, you can provide default configuration parameters using a configuration file that is packaged together with the application.
Examples
The following example sets the threshold value for the monitor interval to 10 (monitoring occurs every 50 seconds) and the threshold value for recovery attempts to 10.
se-Module(config-mping)> status-monitor monitor_interval 10 recovery_threshold 10Related Commands
show app-service state
To display the state and health of all installed virtual instances and applications, use the
show app-service state command in Cisco AXP EXEC mode.show app-service state
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Default
None.
Command Modes
Cisco AXP EXEC.
Command History
Usage Guidelines
Use this command frequently on the application service module to determine whether your applications are up and running.
Examples
In the following example, for each of three running applications, the application's name, state, and health are displayed on the screen.
se-100.0.4.2> show app-service stateAPPLICATION STATE HEALTHhelloworld online ALIVEsimpleFC4CPlusApp online ---x11_app online ---Related Commands
show state
Displays the status and health of a specific application in Cisco AXP application service EXEC mode.
show app-service statistics
To display the memory and processing time information of an installed virtual instance, use the show app-service statistics command in Cisco AXP EXEC mode.
show app-service statistics
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Default
None.
Command Modes
Cisco AXP EXEC.
Command History
Examples
In the following example, the statistics for all installed virtual instances are displayed on the screen.
se-100.0.4.2> show app-service statisticsCTX PROC VSZ RSS userTIME sysTIME UPTIME NAME0 122 2.7G 626.9M 1h23m20 1h39m08 6d18h56 root server2 4 8.6M 2.9M 1m46s57 2m07s88 6d18h54 helloworldCTX = context number for the virtual instancePROC = quantity of processes in the contextVSZ = number of pages of virtual memoryRSS = Resident set size limits for memoryuserTime = utime User-mode CPU time accumulatedsysTime = ctime Kernel-mode CPU time accumulatedupTime = uptimeRelated Commands
show statistics app
Allows third party applications to integrate their own application statistics for display.
show app-service status-monitor
To display status monitor information for all installed applications, use the show app-service status-monitor command in Cisco AXP EXEC mode.
show app-service status-monitor
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Default
None.
Command Modes
Cisco AXP EXEC.
Command History
Examples
In the following example, the monitoring information for helloworld is displayed on the screen. (helloworld is the only installed application.)
se-100.0.4.2> show app-service status-monitorApplication: helloworldMonitor status: PASSEDMonitor in progress: YesLast executed watchdog: W00template.shLast executed date: Wed Sep 5 14:09:58 PDT 2007Last failed watchdog: ---Last failed return code: -Last failed date: ---Last restarted date: ---Recovery threshold: 4Monitor interval: 3Related Commands
show clock detail
To display clock statistics, use the show clock detail command in Cisco AXP EXEC mode.
show clock detail
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Default
None.
Command Modes
Cisco AXP EXEC.
Command History
Examples
In the following example, the clock statistics are displayed on the screen.
se-100.0.4.2> show clock detailse-10-1-1-20> show clock detail15:22:08.375 PST Thu Nov 29 2007time zone: America/Los_Angelesclock state: unsyncdelta from reference (microsec): 0estimated error (microsec): 16time resolution (microsec): 1clock interrupt period (microsec): 10000time of day (sec): 1196378528time of day (microsec): 378926Related Commands
clock timezone
Configures the local timezone.
ntp server
Configures the NTP server for time synchronization
show device serial
To display the serial device ID, use the show device serial command in Cisco AXP EXEC mode.
show device serial
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Default
None
Command Modes
Cisco AXP EXEC.
Command History
Examples
In the following example, all the serial devices are displayed on the screen.
se-Module> show device serialDevice Name TTY No. Line No. Line Type Intf Name Assigned Tovaux1 1 1 AUX - -vtty000 0/0/0 2 TTY Se0/0/0 serialappvtty001 0/0/1 3 TTY Se0/0/1 -Related Commands
show interfaces
To display all the configured interfaces, including virtual and VLAN interfaces, use the show interfaces command in Cisco AXP EXEC mode.
show interfaces [ | |GigabitEthernet|ide]
Syntax Description
|
Pipes output to another command.
GigabitEthernet
Gigabit Ethernet device.
ide
Integrated Drive Electronics (hard disk)
Defaults
No default behavior or values.
Command Default
None.
Command Modes
Cisco AXP EXEC.
Command History
Examples
In the following example, the show interfaces command displays all configured interfaces on the screen: a GigabitEthernet interface and an IDE (hard disk) interface.
se-100.0.4.2> show interfacesGigabitEthernet 0 is up, line protocol is upInternet address is 10.10.1.20 mask 255.255.255.0 (configured on router)25629 packets input, 1688582 bytes0 input errors, 0 dropped, 0 overrun, 0 frame errors25634 packets output, 1785015 bytes0 output errors, 0 dropped, 0 overrun, 0 collision errors0 output carrier detect errorsIDE hd0 is up, line protocol is up2060 reads, 32704512 bytes0 read errors489797 write, 2520530944 bytes0 write errorsRelated Commands
show logs
The show logs command can be used in either of the following two modes:
•
•
show logs
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Default
None.
Command Modes
Cisco AXP application service EXEC.
Cisco AXP EXEC.
Command History
Usage Guidelines
In Cisco AXP application service EXEC mode, this command displays all the log files under the /var/log directory of the virtual instance.
Examples
In the following example, the show logs command, executed in Cisco AXP application service EXEC mode, shows the log files under the /var/log directory of the virtual instance.
se-Module(exec-mping)> show logsSIZE LAST_MODIFIED_TIME NAME108 Mon Nov 05 19:50:33 PST 2007 messages.logIn the following example, the show logs command, executed in Cisco AXP EXEC mode, shows the log files on the Cisco AXP service module.
se-Module> show logsSIZE LAST_MODIFIED_TIME NAME43452 Tue Nov 06 10:46:44 PST 2007 linux_session.log7630 Thu Nov 15 16:18:22 PST 2007 install.log8508 Thu Nov 15 16:18:00 PST 2007 dmesg0 Thu Nov 01 18:12:34 PDT 2007 eem.log4614755 Thu Nov 15 16:16:50 PST 2007 messages.log.prevRelated Commands
log level
Configures the severity of messages to be logged.
log trace
Configures trace logging options.
show log name
To display a specific log file in the application environment , use the show log name command in Cisco AXP application service EXEC mode.
To display system level logging data for a specific log file, use the show log name command in Cisco AXP EXEC mode.
show log name log-name {containing expression | paged | interactive | {|begin | |exclude | | include | |page} | tail}
Syntax Description
Defaults
No default behavior or values.
Command Default
None.
Command Modes
Cisco AXP application service EXEC.
Cisco AXP EXEC.
Command History
Examples
In the following example, the show log command, in Cisco AXP EXEC mode, displays selected system level logging data from file messages.log where the logging data includes the text "iosapi audit".
se-100-0-3-2> show log name messages.log|include "iosapi audit"<197>Sep 21 17:28:46 localhost iosapid: INFO iosapi audit history [IOSAPI]:[EXEC]:[SUCCESS]:[show version]Related Commands
show ntp associations
To display the association identifier and status for all Network Time Protocol (NTP) servers, use the show ntp associations command in Cisco AXP EXEC mode.
show ntp associations [assocID association-id]
Syntax Description
Command Modes
Cisco AXP EXEC.
Command History
Usage Guidelines
The show ntp associations command displays the association identifier and status for all the NTP servers configured for Cisco AXP and does not provide details about the servers. The show ntp associations assocID association-id command provides details on the status of a specified NTP server.
Use the status field to determine the configuration and status of all the NTP servers. This field consists of 4 hexadecimal digits:
•
•
Table 1 shows common status codes and their descriptions. The first digit specifies the configuration, reachability, and authentication status for the specified server. The second digit records how well the specified server passed through the clock selection algorithm.
Table 2 lists the event codes. The third digit indicates the number of events that have occurred since the last time an error was returned to the console by NTP or by one of the show ntp commands. This value does not wrap and stops incrementing at 15 (or hex F).
For a properly running server, the value should be xx1x, unless one of the show ntp commands has queried the server since startup. In that case, the value should be xx0x. If the third digit is any other value, check for the event causing errors.
The fourth digit in the field indicates the last event that occurred. For properly running servers, the event should be the server becoming reachable.
The flash field indicates the status of the packets while a series of 12 diagnostic tests are performed on them. The tests are performed in a specified sequence to gain maximum information while protecting against accidental or malicious errors.
The flash variable is set to zero as each packet is received. If any bits are set as a result of the tests, the packet is discarded.
The tests look for the following information:
•
•
•
•
•
Table 3 lists the flash bits for each test.
Examples
The following example show the output that appears after using the basic show ntp associations command:
se-10-0-0-0> show ntp associationsind assID status conf reach auth condition last_event cnt===========================================================1 50101 8000 yes yes none sys.peer reachable 2Table 4 describes the significant fields shown in the display.
Table 4 show ntp associations Field Descriptions
ind
Index number of the association.
assID
Peer identifier returned by the server.
status
Hexadecimal value of the server status. See Table 1 and Table 2 for a description of these field codes.
conf
Indicates whether the server is configured or not. Valid values are yes and no.
reach
Indicates whether the peer is reachable or not. Valid values are yes and no.
auth
Status of the server authentication. Valid values are:
•
•
•
•
condition
Type of association in the clock selection process. Valid values are:
•
•
•
•
•
•
•
•
last_event
Last event that occurred in the system. Valid values are:
•
•
•
•
•
•
See Table 2 for descriptions of these values.
cnt
Number of events that occurred since the last time an error was returned to the console by the NTP. This value does not wrap and stops incrementing at 15 (or hex F). For a properly functioning server, this value should be 1 or 0.
The following example shows the ntp associations for a particular assocID, using the show ntp associations assocID command:
se-10-0-0-0> show ntp associations assocID 50101status=8000 unreach, conf, no events,srcadr=10.1.10.2, srcport=123, dstadr=10.1.1.20, dstport=123, leap=11,stratum=16, precision=-17, rootdelay=0.000, rootdispersion=0.000,refid=0.0.0.0, reach=000, unreach=16, hmode=3, pmode=0, hpoll=10,ppoll=10, flash=00 ok, keyid=0, offset=0.000, delay=0.000,dispersion=0.000, jitter=4000.000,reftime=00000000.00000000 Wed, Feb 6 2036 22:28:16.000,org=00000000.00000000 Wed, Feb 6 2036 22:28:16.000,rec=00000000.00000000 Wed, Feb 6 2036 22:28:16.000,xmt=cafae952.b5de7a74 Fri, Nov 30 2007 11:56:02.710,filtdelay= 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00,filtoffset= 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00,filtdisp= 16000.0 16000.0 16000.0 16000.0 16000.0 16000.0 16000.0 16000.0Table 5 describes the significant fields shown in the display.
Table 5 show ntp associations assoc-id Field Descriptions
status
Status of the peer. See Table 1, Table 2, and Table 4 for descriptions of the values in this line.
srcadr
IP address of the host server.
srcport
Port address of the host server.
dstadr
IP address of the destination server.
dstport
Port address of the destination server.
leap
Two-bit coded warning of an impending leap second to be inserted in the NTP timescale. Valid values are:
•
•
•
•
stratum
Server hop count to the primary clock source. Valid values are:
•
•
•
If the stratum value is 15, the server is probably unsynchronized and its clock needs to be reset.
precision
Precision of the clock, in seconds to the power of two.
rootdelay
Total round-trip delay, in seconds, to the primary reference source at the root of the synchronization subnet.
rootdispersion
Maximum error, in seconds, relative to the primary reference source at the root of the synchronization subnet.
refid
IP address of the peer selected for synchronization.
reach
Peer reachability status history, in octal. Each bit is set to 1 if the server is reached during a polling period and is set to 0 otherwise. The value 377 indicates that the last 8 attempts were good.
unreach
Number of poll intervals since the last valid packet was received.
hmode
Association mode of the host server. Valid values are:
•
•
•
•
•
•
•
•
pmode
Association mode of the peer server. Valid values are:
•
•
•
•
•
•
•
•
hpoll
Minimum interval, in seconds as a power of two, between transmitted messages from the host.
ppoll
Minimum interval, in seconds as a power of two, between transmitted messages to the peer.
flash
Status of the packet after a series of diagnostic tests are performed on the packet. See the description of the flash field values in Table 3.
keyid
ID of the cryptographic key used to generate the message-authentication code.
offset
Time difference between the client and the server, in milliseconds.
delay
Round-trip delay of the packet, in milliseconds.
dispersion
Measure, in milliseconds, of how scattered the time offsets have been from a specific time server.
jitter
Estimated time error, in milliseconds, of the Cisco AXP clock measured as an exponential average of RMS time differences.
reftime
Local time, in time-stamp format, when the local clock was last updated. If the local clock has never been synchronized, the value is zero.
org
Local time, in time-stamp format, at the peer when its latest NTP message was sent. If the peer becomes unreachable, the value is zero.
rec
Local time, in time-stamp format, when the latest NTP message from the peer arrived. If the peer becomes unreachable, the value is zero.
xmt
Local time, in time-stamp format, at which the NTP message departed the sender.
filtdelay
Round-trip delay, in seconds, between the peer clock and the local clock over the network between them.
filtoffset
Offset, in seconds, of the peer clock relative to the local clock.
filtdisp
Maximum error, in seconds, of the peer clock relative to the local clock over the network between them. Only values greater than zero are possible.
Related Commands
show ntp servers
Displays a list of NTP servers and their current states.
show ntp source
Displays the primary time source for an NTP server.
show ntp servers
To display a list of Network Time Protocol (NTP) servers, their current states, and a summary of the remote peers associated with each server, use the show ntp servers command in Cisco AXP EXEC mode.
show ntp servers
Syntax Description
This command has no keywords or arguments.
Command Modes
Cisco AXP EXEC.
Command History
Usage Guidelines
Use the show ntp servers command after changing the ntp server configuration.
Examples
The following example shows sample output for the show ntp servers command:
se-10-1-1-20> show ntp serversremote refid st t when poll reach delay offset jitter==============================================================================10.1.10.2 0.0.0.0 16 u - 1024 0 0.000 0.000 4000.00space reject, x falsetick, . excess, - outlyer+ candidate, # selected, * sys.peer, o pps.peerTable 6 describes the significant fields shown in the display.
Related Commands
show ntp source
To display the time source for a Network Time Protocol (NTP) server, use the show ntp source command in Cisco AXP EXEC mode. The display extends back to the primary time source, starting from the localhost.
show ntp source [detail]
Syntax Description
detail
(Optional) Additional NTP server details including: precision, leap, refid, delay, dispersion, rootdelay, rootdispersion, reference time, originate timestamp, and transmit timestamp.
Command Modes
Cisco AXP EXEC.
Command History
Examples
The following example shows the sample output for the show ntp source command:
se-10-0-0-0> show ntp source127.0.0.1: stratum 9, offset 0.000015, synch distance 0.0304710.100.10.65: stratum 8, offset -0.001124, synch distance 0.00003Table 7 describes the significant fields shown in the display.
The following example shows the sample output for the show ntp source detail command:
se-1-100-5-2> show ntp source detailserver 10.0.0.1, port 123stratum 9, precision -17, leap 00refid [10.10.10.65] delay 0.00012, dispersion 0.00000 offset 0.000011rootdelay 0.00058, rootdispersion 0.03111, synch dist 0.03140reference time: af4a3ff7.926698bb Thu, Feb 30 2007 14:47:19.571originate timestamp: af4a4041.bf991bc5 Thu, Nov 30 2007 14:48:33.748transmit timestamp: af4a4041.bf90a782 Thu, Nov 30 2007 14:48:33.748server 10.10.10.65, port 123stratum 8, precision -18, leap 00refid [172.16.7.1] delay 0.00024, dispersion 0.00000 offset -0.001130rootdelay 0.00000, rootdispersion 0.00003, synch dist 0.00003reference time: af4a402e.f46eaea6 Thu, Nov 30 2007 14:48:14.954originate timestamp: af4a4041.bf6fb4d4 Thu, Nov 30 2007 14:48:33.747transmit timestamp: af4a4041.bfb0d51f Thu, Nov 30 2007 14:48:33.748Table 8 describes the significant fields shown in the display.
Related Commands
show ntp associations
Displays a list of association identifiers and peer status for an NTP server.
show ntp servers
Displays a list of NTP servers and their current states.
show ntp status
To display statistics for the Network Time Protocol (NTP) server, use the show ntp status command in Cisco AXP EXEC mode.
show ntp status
Syntax Description
This command has no arguments or keywords.
Command Modes
Cisco AXP EXEC.
Command History
Examples
The following shows sample output for the show ntp status command:
se-10-0-0-0> show ntp statusNTP reference server 1: 10.100.6.9Status: sys.peerTime difference (secs): 3.268110005008586E8Time jitter (secs): 0.17168384790420532Table 9 describes the significant fields shown in the display.
Related Commands
clock timezone
Sets the local time zone.
ntp server
Specifies the NTP server for Cisco AXP.
show clock detail
Displays clock statistics.
show process
To display all processes in the application environment, use the show process command in Cisco AXP application service EXEC mode.
show process [all | memory | pid id | running}
Syntax Description
Defaults
No default behavior or values.
Command Default
None.
Command Modes
Cisco AXP application service EXEC.
Command History
Usage Guidelines
This command displays all processes in the virtual application environment and sorted by process ID in ascending order.
Examples
In the following example, show process displays summary and process information on the screen.
se-Module(exec-mping)> show processUSER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMANDroot 1 0.0 0.1 1972 612 ? S Nov05 0:00 init [4]root 8522 0.0 0.1 2244 800 ? Ss Nov05 0:00 /cisco/bin/syslog_ngroot 8523 0.0 0.1 1952 536 ? Ss Nov05 0:00 /bin/logmgr/var/log/messages.log 5000000Related Commands
show tech-support
Displays a summary of the diagnostic information for the application.
show processes
To display processes running on the Cisco AXP service module, use the show processes command in Cisco AXP EXEC mode.
show processes [cpu | memory]
Syntax Description
Defaults
No default behavior or values.
Command Default
None.
Command Modes
Cisco AXP EXEC.
Command History
Examples
In the following example, show processes displays all the running processes. For each process the name of the process (in the CMD column), the health of the process, and the state of the process are displayed on the screen.
se-Module(exec-mping)> show processesse-10-0-0-0> show processesSTATE HEALTH CMDonline alive syslog-ngonline alive platform_configonline alive traceonline alive rbcponline alive ntponline alive downloaderonline alive superthreadonline alive dnsonline alive backuprestoreonline alive cliservice alive sshdIn the following example, show processes memory displays the Random Access Memory (RAM) utilization of the ten running processes on the screen.
se-10-0-0-0> show processes memoryVSZ RSS SHR PVT RD RW EXE DAT STK %PVT CMD12680 1360 968 392 0 0 96 4800 0 0.1 syslog-ng22704 1336 1076 260 0 0 64 14840 0 0.1 platform_config10384 1072 900 172 0 0 28 2552 0 0.0 rbcp14272 2568 1260 1308 0 0 16 4620 0 0.3 trace2560 772 568 204 0 0 572 464 0 0.0 monitor23504 3808 1456 2352 0 0 20 13848 0 0.5 downloader18832 1364 1120 244 0 0 212 10812 0 0.0 ntp63660 17780 2324 15456 0 0 40 53424 0 3.0 superthread63660 17780 2324 15456 0 0 40 53424 0 3.0 cli1972 616 524 92 0 0 28 496 0 0.0 sshd--------------------------------------------Process Memory Information for helloworld--------------------------------------------VSZ RSS SHR PVT RD RW EXE DAT STK CMD1972 616 524 92 0 0 28 496 0 init2244 872 704 168 0 0 92 572 0 syslog_ng2500 1096 948 148 0 0 572 404 0 hello_world.sh1948 532 456 76 0 0 8 492 0 logmgr0 0 0 0 0 0 0 0 0In the following example, show processes cpu displays the CPU utilization of the the combined running processes on the screen.
se-10-0-0-0> show processes cpuUptime (secs): 1122639.02User time (secs): 9834.87Kernel time (secs): 11647.49Idle time (secs): 1100952.01se-10-0-0-0>Related Commands
show tech-support
Displays a summary of the diagnostic information for the application.
show resource limits
To display a summary of the resource limits configuration, use the show resource limits command in Cisco AXP application service EXEC mode.
show resource limits
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Default
None.
Command Modes
Cisco AXP application service EXEC.
Command History
Examples
In the following example, show resource limits shows that for application mping, the CPU index value is set to 1000, memory limit is 10 MB, disk limit is 10 MB, and log size limit is 5 MB.
se-Module(exec-mping)> show resource limitsAPPLICATION CPU(INDEX) MEMORY(MB) DISK(MB) LOG(MB)mping 1000 10 10 5Related Commands
show running-config
To display the running configuration of the application environment, use the show running-config command in Cisco AXP application service EXEC mode.
show running-config
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Default
None.
Command Modes
Cisco AXP application service EXEC.
Command History
Examples
In the following example, show running-config displays the running configuration for the application mping on the screen.
se-Module(exec-mping)> show running-configapp-service mpingbind interface eth0hostname se-10-0-0-0exitRelated Commands
show tech-support
Displays a summary of the diagnostic information for the application.
show ssh-server
To display the current status of the SSH server for a virtual instance, use the show ssh-server command in Cisco AXP application service EXEC mode.
show ssh-server
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Default
None.
Command Modes
Cisco AXP application service EXEC.
Command History
Usage Guidelines
Use this command to display the status of the SSH server—either RUNNING or NOT RUNNING.
Examples
In the following example, the status of the SSH server for the virtual instance of the application SYSLOG_APP1 is displayed on the screen. In this case the SSH server is RUNNING.
se-100-0-5-2> app-service SYSLOG_APP1se-100-0-5-2(exec-SYSLOG_APP1)> show ssh-serverApplication SSH ServerStatus: RUNNINGse-100-0-5-2(exec-SYSLOG_APP1)>Related Commands
ip ssh-server
Configures the SSH server.
ip ssh username
Configures SSH tunneling.
show state
To display the status and health of a specific application, use the show state command in Cisco AXP application service EXEC mode.
show state
Syntax Description
There are no arguments or keywords for this command.
Defaults
No default behavior or values.
Command Default
None.
Command Modes
Cisco AXP application service EXEC.
Command History
Usage Guidelines
The show state command displays the state and health as:
•
•
Examples
In the following example, show state displays the state and health status of the application helloworld on the screen.
se-Module(exec-helloworld)> show stateAPPLICATION STATE HEALTHhelloworld online ALIVERelated Commands
show statistics
To display statistics for a virtual instance in the application environment, use the show statistics command in Cisco AXP application service EXEC mode.
show statistics
Command Default
None.
Command Modes
Cisco AXP application service EXEC.
Command History
Usage Guidelines
The show statistics command displays statistics such as CPU utilization and memory for a virtual instance in the application environment.
The show statistics app command displays statistics of third party applications integrated into the application environment.
When this command is initiated, /bin/appstats is executed. The third party application must provide the appstats file, in binary or script format, to plug in for its statistics.
Examples
In the following example, show statistics displays statistics for the environment of application "mping" on the screen.
se-Module(exec-mping)> show statisticsCTX PROC VSZ RSS userTIME sysTIME UPTIME NAME2 3 6.6M 2.5M 0m00s12 0m00s40 3h04m08 mpingCTX = context number for the virtual instancePROC = quantity of processes in the contextVSZ = number of pages of virtual memoryRSS = Resident set size limits for memoryuserTime = utime User-mode CPU time accumulatedsysTIME = ctime Kernel-mode CPU time accumulatedUPTIME = uptimeNAME = application nameRelated Commands
show statistics app
Allows third party applications to integrate their own application statistics for display.
show statistics app
To allow third party applications to integrate their own application statistics for display, use the
show statistics app command in Cisco AXP application service EXEC mode.show statistics app
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Default
None.
Command Modes
Cisco AXP application service EXEC.
Command History
Usage Guidelines
When this command is initiated, /bin/appstats is executed which plugs in statistics that must be provided by the third party application using file appstats (in binary or script format).
Related Commands
show statistics
Displays statistics for a virtual instance in the application environment.
show status-monitor
To display parameters of the status monitor, use the show status-monitor command in Cisco AXP application service EXEC mode.
show status-monitor
Syntax Description
This command has no arguments or keywords.
Command Default
None.
Command Modes
Cisco AXP application service EXEC.
Command History
Examples
In the following example, the show status-monitor command displays the status of the status-monitor for the helloworld application.
se-Module(exec-helloworld)> show status-monitorApplication: helloworldMonitor status: PASSEDMonitor in progress: YesLast executed watchdog: W00template.shLast executed date: Wed Sep 5 14:09:58 PDT 2007Last failed watchdog: ---Last failed return code: -Last failed date: ---Last restarted date: ---Recovery threshold: 4Monitor interval: 3
Related Commands
show syslog-server logs
To display syslog server log files in the /var/remote log directory, use the show syslog-server logs command in Cisco AXP EXEC mode.
show syslog-server logs
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Default
None.
Command Modes
Cisco AXP EXEC.
Command History
Usage Guidelines
This command displays all the syslog files under /var/remote log directory.
Examples
The following example illustrates the show syslog-server logs command that displays the size last modified date and time for each of the syslog files under the /var/remote log directory. In this case, there is only one syslog file: remote_messages.log.
se-Module> show syslog-server logsSIZE LAST_MODIFIED_TIME NAME62 Thu Oct 18 16:37:22 PDT 2007 remote_messages.logRelated Commands
log level
Configures the severity of messages to be logged.
log trace
Configures trace logging options.
show syslog-server log name
To display system level logging data for a specific log file, use the show log name command in Cisco AXP EXEC mode.
show syslog-server log name log-name { paged | | |}
Syntax Description
log-name
Log name. See the show logs command for log names.
paged
Displays in page mode.
|
Pipes output to another command.
Defaults
No default behavior or values.
Command Default
None.
Command Modes
Cisco AXP EXEC.
Command History
Examples
In the following example, show syslog-server log name displays system level logging data for log file remote_messages.log.
se-10-0-0-0> show syslog-server log name remote_messages.logPress <CTRL-C> to exit...#!/bin/cat16:37:22 logmgr: BEGIN FILE16:37:22 logmgr: STARTRelated Commands
show logs
Displays log files in the application environment or on the Cisco AXP service module.
show syslog-server logs
Displays all the syslog files.
show tech-support
To display diagnostic information about the application environment, use the show tech-support command in Cisco AXP application service EXEC mode.
show tech-support
Syntax Description
This command has no arguments or keywords.
Command Default
None.
Command Modes
Cisco AXP application service EXEC.
Command History
Usage Guidelines
This command:
•
•
•
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-10-0-0-0(exec-helloworld)> show tech-support------------------ show app-service state ------------------APPLICATION STATE HEALTHhelloworld online ALIVE------------------ show app-service statistics ------------------CTX PROC VSZ RSS userTIME sysTIME UPTIME NAME0 122 2.7G 624.3M 59m23s94 1h10m58 4d20h45 root server2 4 8.6M 2.9M 1m16s66 1m31s31 4d20h43 helloworld------------------ show process ------------------USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMANDroot 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_ngroot 3763 0.0 0.2 2500 1096 ? S Nov15 0:00 /bin/bash /opt/helloworld/hello_world.shroot 29302 0.0 0.1 1948 532 ? Ss 12:55 0:00 /bin/logmgr /var/log/messages.log 5000000root 31016 0.0 0.1 2216 532 ? S 13:02 0:00 sleep 5------------------ show resource limits ------------------APPLICATION CPU(INDEX) MEMORY(MB) DISK(MB) LOG(MB)helloworld 800 10 20 5------------------ show running-config ------------------Generating running configuration:app-service helloworldbind interface eth0hostname se-10-0-0-0log level infoexitRelated Commands
show software
To display characteristics of the installed software, use the show software command in Cisco AXP EXEC mode.
show software {directory | download server | licenses | packages | versions}
Syntax Description
Command Modes
Cisco AXP EXEC.
Command History
Examples
The following is sample output of the show software command:
se-10-0-0-0> show software download serverDownload server URL is: ftp://172.16.0.1/ftpse-10-0-0-0> show software licensesCore:- application mode: AXPse-10-0-0-0> show software packagesInstalled Packages:- Core (Integrated Voice Services - Core)- Boot Loader (Service Engine Bootloader)se-10-50-10-125> show software versionsInstalled Packages:Software Version: 3.0.1- Installer 3.0.1.0- Thirdparty 2.3.1.0- Bootloader (Primary) 2.1.14- Infrastructure 2.3.2.0Related Commands
show software directory
To display directory information for software download and downgrade files, use the show software directory command in Cisco AXP EXEC mode.
show software directory {download | downgrade}
Syntax Description
downgrade
Displays downgrade directory information.
download
Displays download directory information.
Command Modes
Cisco AXP EXEC.
Command History
Examples
In the following example, the show software directory download command shows download directory information to the screen.
se-10-10-0-0> show software directory downloadKBytes Directory27347 /dwnld/pkgdataDirectory listingsDirectory: /dwnld/pkgdatatotal 27347drwxrwxr-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.pkgse-10-0-0-0>In the following example, the show software directory downgrade command displays downgrade directory information to the screen.se-172-16-0-0> show software directory downgradeKBytes Directory6154 /dwnld/dwngradeDirectory listingsDirectory: /dwnld/dwngradetotal 6154drwxrwxrwx 3 root daemon 184 Nov 3 17:22 .drwxrwxr-x 4 root daemon 360 Nov 3 17:22 ..-rw-rw-r-- 1 root daemon 227 Oct 28 18:42 .uninstall_work_order-rw-rw-r-- 1 root daemon 6286628 Oct 28 18:42 add_files.fhdrdrwxrwxr-x 2 root daemon 48 Nov 3 17:22 tmpse-10-0-0-0>Related Commands
show app-service
Displays statistics for installed applications.
show tech-support
Displays a summary of the diagnostic information for the application.
show startup-config
To display the current startup configuration, use the show startup-config command in Cisco AXP EXEC mode.
show startup-config [paged]
Syntax Description
Command Modes
Cisco AXP EXEC.
Command History
Usage Guidelines
This command displays the startup configuration stored in flash memory.
Examples
The following example example output from the show startup-config command shows the stored configuration on the screen.
se-10-0-0-0> show startup-config! This adds all the platform CLI commands!! hostnamehostname se-10-0-0-0! Domain Nameip domain-name localdomain! DNS Serversip name-server 10.100.10.130! Timezone Settingsclock timezone America/Los_AngelesendRelated Commands
show system language
To display which language the system is configured to use and/or a list of the languages available, use the show system language command in Cisco AXP EXEC mode.
show system language {preferred | installed}
Syntax Description
Command Modes
Cisco AXP EXEC.
Command History
Usage Guidelines
Use this command to either see the current language used by the system or the languages available to be used by the system.
Examples
The following example shows that English is the system language preferred.
se-10-0-0-0> show system language preferred Preferred Language: en_USRelated Commands
show trace buffer
To display a list of events in memory, use the show trace buffer command in Cisco AXP EXEC mode.
show trace buffer [containing string [long | short] | long [paged] | short [paged] | tail [number [long | short]]]
Syntax Description
Command Modes
Cisco AXP EXEC.
Command History
Usage Guidelines
Use this command to monitor trace events set for debugging. Stop the output by pressing Ctrl-C.
Examples
The following example shows partial output from the show trace buffer command:
se-10-0-0-0> show trace bufferPress <CTRL-C> to exit...238 09/19 23:23:11.041 TRAC TIMZ 0 UTC UTC 0238 09/19 23:23:11.043 TRAC TIMZ 0 UTC UTC 0800 09/19 23:28:04.152 WFSP MISC 0 WFSysdbLimits::WFSysdbLimits hwModuleType=NM800 09/19 23:28:04.171 WFSP MISC 0 WFSysdbProp::getProp800 09/19 23:28:04.171 WFSP MISC 0 keyName = limitsDirstr = /sw/apps/wf/ccnapps/limits800 09/19 23:28:04.197 WFSP MISC 0 WFSysdbProp::getNodeXml800 09/19 23:28:04.197 WFSP MISC 0 WFSysdbProp::getProp800 09/19 23:28:04.198 WFSP MISC 0 keyName = limitsstr = <?xml version="1.0" encoding="ISO-8859-1" standalone="yes"?> <attrList> <attrDecl purpose="CONFIG" type="INT32" maxsize="4"> <node>limits</node> <attr>max_scripts</attr> <desc>maximum number of scripts</desc> <value>0</value> </attrDecl> <attrDecl purpose="CONFIG" type="INT32" maxsize="4"> <node>limits</node> <attr>max_prompts</attr> <desc>maximum number of prompts</desc> <value>0</value> </attrDecl> </attrList>800 09/19 23:28:04.199 WFSP MISC 0 WFSysdbProp::getNodeXml(str, str)800 09/19 23:28:04.200 WFSP MISC 0 WFSysdbProp::getProp800 09/19 23:28:04.200 WFSP MISC 0 keyName = appRelated Commands
show trace store
To display a list of events from the atrace.log file, use the show trace store command in Cisco AXP EXEC mode.
show trace store [containing string [long | short] | long [paged] | short [paged] | tail [number [long | short]]]
Syntax Description
Command Modes
Cisco AXP EXEC.
Command History
Usage Guidelines
Use this command to monitor trace events set for debugging.
Examples
The following example shows partial output from the show trace store command:
se-10-0-0-0> show trace storePress <CTRL-C> to exit...238 09/19 23:23:11.043 TRAC TIMZ 0 UTC UTC 0800 09/19 23:28:04.152 WFSP MISC 0 WFSysdbLimits::WFSysdbLimits hwModuleType=NM800 09/19 23:28:04.171 WFSP MISC 0 WFSysdbProp::getProp800 09/19 23:28:04.171 WFSP MISC 0 keyName = limitsDirstr = /sw/apps/wf/ccnapps/limits800 09/19 23:28:04.197 WFSP MISC 0 WFSysdbProp::getNodeXml800 09/19 23:28:04.197 WFSP MISC 0 WFSysdbProp::getProp800 09/19 23:28:04.198 WFSP MISC 0 keyName = limitsstr = <?xml version="1.0" encoding="ISO-8859-1" standalone="yes"?> <attrList> <attrDecl purpose="CONFIG" type="INT32" maxsize="4"> <node>limits</node> <attr>max_scripts</attr> <desc>maximum number of scripts</desc> <value>0</value> </attrDecl> <attrDecl purpose="CONFIG" type="INT32" maxsize="4"> <node>limits</node> <attr>max_prompts</attr> <desc>maximum number of prompts</desc> <value>0</value> </attrDecl> </attrList>800 09/19 23:28:04.199 WFSP MISC 0 WFSysdbProp::getNodeXml(str, str)800 09/19 23:28:04.200 WFSP MISC 0 WFSysdbProp::getProp800 09/19 23:28:04.200 WFSP MISC 0 keyName = appRelated Commands
show trace store-prev
To display a list of events from the atrace.log.prev file, use the show trace store-prev command in Cisco AXP EXEC mode.
show trace store-prev [containing string [long | short] | long [paged] | short [paged] | tail [number [long | short]]]
Syntax Description
Command Modes
Cisco AXP EXEC.
Command History
Usage Guidelines
Use this command to monitor trace events set for debugging.
Examples
The following example shows partial output from the show trace store-prev command:
se-10-0-0-0> show trace store-prevPress <CTRL-C> to exit...238 09/19 23:23:11.041 TRAC TIMZ 0 UTC UTC 0238 09/19 23:23:11.043 TRAC TIMZ 0 UTC UTC 0800 09/19 23:28:04.152 WFSP MISC 0 WFSysdbLimits::WFSysdbLimits hwModuleType=NM800 09/19 23:28:04.171 WFSP MISC 0 WFSysdbProp::getProp800 09/19 23:28:04.171 WFSP MISC 0 keyName = limitsDirstr = /sw/apps/wf/ccnapps/limits800 09/19 23:28:04.197 WFSP MISC 0 WFSysdbProp::getNodeXml800 09/19 23:28:04.197 WFSP MISC 0 WFSysdbProp::getProp800 09/19 23:28:04.198 WFSP MISC 0 keyName = limitsstr = <?xml version="1.0" encoding="ISO-8859-1" standalone="yes"?> <attrList> <attrDecl purpose="CONFIG" type="INT32" maxsize="4"> <node>limits</node> <attr>max_scripts</attr> <desc>maximum number of scripts</desc> <value>0</value> </attrDecl> <attrDecl purpose="CONFIG" type="INT32" maxsize="4"> <node>limits</node> <attr>max_prompts</attr> <desc>maximum number of prompts</desc> <value>0</value> </attrDecl> </attrList>800 09/19 23:28:04.199 WFSP MISC 0 WFSysdbProp::getNodeXml(str, str)800 09/19 23:28:04.200 WFSP MISC 0 WFSysdbProp::getProp800 09/19 23:28:04.200 WFSP MISC 0 keyName = appRelated Commands
show logs
Displays a list of the log files.
show trace store
Displays a list of events from the atrace.log file.
show version
To display versions of Cisco AXP components, use the show version command in Cisco AXP EXEC mode.
show version
Syntax Description
This command has no arguments or keywords.
Command Modes
Cisco AXP EXEC.
Command History
Usage Guidelines
This command displays a list of the installed Cisco AXP hardware components with their versions and serial numbers.
Examples
The following example shows the displayed details from the show version command, containing Cisco AXP network module details.
se-10-1-1-20> show versionse-10-1-1-20 uptime is 0 weeks, 0 days, 20 hours, 0 minutesCPU Model: Intel(R) Celeron(R) M processor 1.00GHzCPU Speed (MHz): 1000.192CPU Cache (KByte): 512BogoMIPS: 2002.02SKU: NME-APPRE-302-K9Chassis Type: C2821Chassis Serial: FHK0945F1TAModule Type: NMEModule Serial: FOC10480BFMUDI Name: Not AvailableUDI Description: Not AvailableIDE Drive: 64MBSATA Drive: 80.0GBSDRAM (MByte): 512Table 11 describes the significant fields shown in the display.
Related Commands
show software
Displays the version numbers of the installed Cisco AXP software components.
software download abort
To abort a download that is in progress, use the software download abort command in Cisco AXP EXEC mode.
software download abort
Syntax Description
This command has no arguments or keywords.
Command Modes
Cisco AXP EXEC.
Command History
Examples
The following is an example of downloading a software package to install later where the FTP server information is included on the command line.
se-10-0-0-0> software download abortDownload request aborted.Related Commands
software download clean
To download software packages for installing later, use the software download clean command in Cisco AXP EXEC mode.
software download clean {package-file-name | url ftp://ftp-server-ip-address/package-file-name}
Syntax Description
package-file-name
Name of the package file for the new software.
url ftp://ftp-server-ip-address
URL of the FTP server.
Command Modes
Cisco AXP EXEC.
Command History
Examples
The following is an example of downloading a software package to install later where the FTP server information has been set in the configuration.
se-172-16-0-0> software download clean axp-abc.2.0.1.pkgThe following is an example of downloading a software package to install later where the FTP server information is included on the command line.
se-10-16-0-0> software download clean url ftp://10.16.0.2/axp-abc.2.0.1.pkgWARNING:: This command will download the necessary software toWARNING:: complete a clean install. It is recommended that a backup be doneWARNING:: before installing software.Would you like to continue? [n] yDownloading axp-abc.2.0.1.pkgBytes downloaded : 63648Validating package signature ... done> x[17488 refs]se-10-0-0-0>The following is an example of using the software download status command to check on the download progress.
se-172-16-0-0> software download statusDownload request in progress.downloading file : axp-abc.2.0.prt1bytes downloaded : 5536224Related Commands
software download server
To configure the FTP server address on the Cisco AXP service module, use the software download server command in Cisco AXP configuration mode.
software download server url ftp://server-ip-address[/dir] [username username
password password | credentials hidden credentials]Syntax Description
Command Modes
Cisco AXP configuration.
Command History
Examples
The following is an example of setting the server information with just a root directory.
se-10-16-0-0(config)> software download server url ftp://10.19.0.0/The following is an example of setting the server information with a directory different than the root directory.
se-10-16-0-0(config)> software download server url ftp://10.19.0.0/ftp_dirThe following is an example of setting the server information with a username and password.
se-10-16-0-0(config)> software download server url ftp://10.19.0.0/ftp_dir username ftpuser password ftppasswordRelated Commands
software download status
To display the progress of a software download, use the software download status command in Cisco AXP EXEC mode.
software download status
Syntax Description
This command has no arguments or keywords.
Command Modes
Cisco AXP EXEC.
Command History
Examples
The following is an example of a download in progress:
se-10-0-0-0> software download statusDownload request in progress.downloading file : axp-abc.2.0.1.prt1bytes downloaded : 5536224The following is an example of a download that has completed:
se-10-0-0-0> software download statusDownload request completed successfully.Related Commands
software download upgrade
To download software for a later upgrade, use the software download upgrade command in Cisco AXP EXEC mode.
software download upgrade {package-filename | url ftp://ftp-server-ip-address[/dir]/package-filename} [username username password password]
Syntax Description
Command Modes
Cisco AXP EXEC.
Command History
Usage Guidelines
Use this command to download files for a future upgrade.
Examples
The following is an example of downloading a software package to upgrade later where the FTP server information has been set up.
se-10-0-0-0> software download upgrade axp-abc.2.1.pkgThe following is an example of downloading a software package to upgrade later where the FTP server information is included on the command line. The username and password could also be included in this command.
se-10-0-0-0> software download upgrade url ftp://10.16.0.1/axp-abc.2.1.pkgWARNING:: This command will download the necessary software toWARNING:: complete an upgrade. It is recommended that a backup be doneWARNING:: before installing software.Would you like to continue? [n] yurl_host :10.16.0.1url_user :nullurl_uname :anonymousurl_psword :anonymousurl_proto :ftpurl_path :/url_fname :axp-abc.2.0.0.12.pkgurl_url :ftp://10.16.0.1/Downloading axp-abc.2.1.pkgBytes downloaded : 63648Validating package signature ... doneValidating installed manifests ..........complete.[17497 refs]
Note
The following is an example of using the software download status command to check on the download progress.
se-10-0-0-0> software download statusDownload request in progress.downloading file : axp-abc.2.1.prt1bytes downloaded : 5536224se-10-0-0-0> software download statusDownload request completed successfully.The following is an example of using the show software directory download to determine if a download has been successful:
se-10-10-0-0> show software directory downloadKBytes Directory0 /dwnld/pkgdataDirectory listingsDirectory: /dwnld/pkgdatatotal 0drwxrwxr-x 2 root daemon 48 Sep 15 2007 .drwxrwxr-x 4 root daemon 200 Sep 15 2007 ..Related Commands
software install add
To install add-on packageson the Cisco AXP service module, use the software install add command in Cisco AXP EXEC mode.
software install add {package-filename | url ftp://ftp-server-ip-address/package-filename}
Syntax Description
package-filename
Name of the add-on package file.
url ftp://ftp-server-ip-address/
URL address of the FTP server where the package is located.
Command Modes
Cisco AXP EXEC.
Command History
Usage Guidelines
Use this command to install add-on packages.
For a list of software add-on packages, see the latest Cisco AXP release notes by clicking General Information in the support area of the Cisco AXP documentation page.
Examples
The following is an example of the command to install a new version of Cisco AXP software where the FTP server information was set in the configuration.
se-10-16-0-0> software install add axp-eemapi.aim.1.0.5.pkgThe 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-10-16-0-0> software install add url ftp://10.16.0.1/ axp-eemapi.aim.1.0.5.pkgRelated 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 {package-filename | url ftp://ftp-server-ip-address/package-filename}
Syntax Description
package-filename
Name of the package file for the new software.
url ftp://ftp-server-ip-address/
URL of the FTP server.
Command Modes
Cisco AXP EXEC.
Command History
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 the command to install a new version of Cisco AXP software where the FTP server information was set in the configuration.
se-10-16-0-0> software install clean axp-abc.2.0.pkgThe 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-10-16-0-0> software install clean url ftp://10.16.0.1/axp-abc.2.0.pkgRelated Commands
software install downgrade
The software install downgrade command is not supported, although it is visible upto maintenance release 1.0.6.
To downgrade Cisco AXP software to a lower release, use the same command for upgrading:
software install upgrade
To upgrade to a newer version of Cisco AXP software, use the software install upgrade command in Cisco AXP EXEC mode.
software install upgrade {pkg axp-package.pkg | url ftp://ftp-server-ip-address/axp-package.pkg}
Syntax Description
pkg axp-package.pkg
Specifies a package name.
url ftp://ftp-server-ip-address/axp-package.pkg
Specifies the FTP server information.
Command Modes
Cisco AXP EXEC.
Command History
Usage Guidelines
Use this command to upgrade to a newer version of Cisco AXP software.
Copy the installer payload file axp-installer-k9.<platform>.<version>.prt1 to the same FTP directory as the Cisco AXP package.
When a new release image is installed over an existing one, the old installer from the previous release is first upgraded via the package, axp-installer-k9.<platform>.<version>.prt1, and then the new image is installed.
Examples
The following is an example of the command to upgrade to a newer version of Cisco AXP software.
se-10-16-0-0> software install upgrade url ftp://10.16.0.1/axp-abc.2.0.2.pkgThe following is an example of the command to upgrade to a newer version of Cisco AXP software if the FTP server is configured or the software files were downloaded previously with the software download upgrade command:
se-10-16-0-0> software install upgrade pkg axp-abc.2.0.2.pkgRelated Commands
software remove
To remove software installed during a download or upgrade, use the software remove command in Cisco AXP EXEC mode.
software remove {all | downgradefiles | downloadfiles}
Syntax Description
all
Removes both the downgrade and the download files.
downgradefiles
Removes the downgrade files.
downloadfiles
Removes the download files.
Command Modes
Cisco AXP EXEC.
Command History
Examples
The following is an example of the software remove all command:
se-172-19-0-0> software remove allDownload files removedDowngrade files removedThe following is an example of the software remove downgradefiles command:se-172-19-0-0> software remove downgradefilesDowngrade files removedThe following is an example of the software remove downloadfiles command:se-172-19-0-0> software remove downloadfilesDownload files removedRelated Commands
show software directory
Displays the disk usage for the download and downgrade directories.
syslog-server
To enable the syslog server, use the syslog-server command in Cisco AXP configuration mode.
syslog-server
Syntax Description
This command has no arguments or keywords.
Command Default
Disabled.
Command Modes
Cisco AXP configuration.
Command History
Usage Guidelines
This command enables or disables syslog server. The syslog server is disabled by default.
If the server is enabled, the Cisco AXP service module is used as a syslog server to receive all the log files from external devices.
The error message below arises if the system has less than 80G disk storage, or available disk space does not satisfy the current limits set by file size, and the number of files.
ERROR - system does not have enough disk spaceThis error is resolved by either unloading applications to free disk space, or by changing limits. If this error occurs, the syslog server is disabled.
Related Commands
syslog-server limit file-rotation
To set the syslog server file rotation limits, use the syslog-server limit file-rotation command in Cisco AXP configuration mode.
syslog-server limit file-rotation size [file-size num]
Syntax Description
num
Defines the number of log files to be rotated. The range is 1-40 and the default is 10.
size
Defines the maximum size (in MB) of each log file. The range is 1-1000 MB and the default is 20 MB.
Command Default
None.
Command Modes
Cisco AXP configuration.
Command History
Usage Guidelines
Setting the file rotation configuration lower than the current settings causes extra log files to be deleted.
Examples
In the following example, the original current file rotation size is 5 (number of files). The syslog-server limit file-rotation command sets the new file rotation size to 2. This has the effect of deleting log files 3, 4, and 5.
syslog-server limit file-rotation 10 file-size 2The message below indicates that the new file rotation value is lower than the current file rotation value.
WARNING - setting the new file-rotation value to 2 from the old value of 5 caused extra log files to be removedIn the following example, the syslog-server limit file-rotation command sets the file size to 100 MB.
syslog-server limit file-rotation 100 file-size 2The message below results from the available system disk space being insufficient for newly configured limits.
System does not have enough disk space.In the following example, the syslog-server limit file-rotation command exceeds the limits for both file size and rotation. This causes the new configuration to be rejected and the original file size limit and rotation limit remain the same.
syslog-server limit file-rotation 1001 file-size 1001syslog-server limit file-size 1001^Invalid input detected at '^' markersyslog-server limit file-rotation 20 file-size 1001^Invalid input detected at '^' marker.Related Commands
syslog-server limit file-size
To set the syslog server file size limits, use the syslog-server limit file-size command in Cisco AXP configuration mode.
syslog-server limit file-size size [file-rotation num]
Syntax Description
num
Defines the number of log files to be rotated The range is 1-40 and the default is 10.
size
Defines the maximum size (in MB) of each log file. The range is 1-1000 MB and the default is 20 MB.
Command Default
None.
Command Modes
Cisco AXP configuration.
Command History
Usage Guidelines
syslog-server limit file-size size [file-rotation num] works in a similar way to
syslog-server limit file-rotation num [file-size size].
See the "syslog-server limit file-rotation" section for usage.
Examples
See the "syslog-server limit file-rotation" section for examples.
Related Commands
write
To erase, copy, or display the running configuration, use the write command in Cisco AXP EXEC mode.
write [erase | memory | terminal]
Syntax Description
erase
Erases the running configuration.
memory
Writes the running configuration to the startup configuration. This is the default.
terminal
Displays the running configuration.
Defaults
No default behavior or values.
Command Default
None.
Command Modes
Cisco AXP EXEC.
Command History
Usage Guidelines
Use the write or write memory command as a shortcut for the copy running-config startup-config command.
Related Commands
copy running-config startup-config
Writes the running configuration to the startup configuration.
erase startup-config
Deletes the current start up configuration.
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].
CCDE, CCENT, Cisco Eos, Cisco HealthPresence, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website 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. (0812R)
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.
© 2008 Cisco Systems, Inc. All rights reserved.
