Cisco Cisco Application Extension Platform for SRE

To show the remote syslog server status:

blade# show syslog-server 

Syslog Server

Status:                 RUNNING

To configure the number of files for rotation and the file size:

blade# config terminal

(config)# syslog-server limit file-rotation 2 file-size 500

file-rotation 

has a value from 1 to 40, with a default of 10.

file-size 

has a value from 1 to 1000 MB, with a default of 20 MB. 

This section explains how to use the packaging tool to package your applications before installing the 
packages on the application service module. 

This tool requires that the third party application has development authorization from Cisco and can 
access private keys for signing the application. Specify parameters to the packaging tool in single 
command line mode (batch file) or in interactive mode.

Before running the packaging tool, check that your PATH environment variable has the system paths 
listed at the beginning of the string. To determine the value of your path environment variable, enter:

>echo $PATH 

For example, a path similar to the following path value is displayed:

>/bin:/sbin:/usr/bin:/usr/local/sbin:/usr/sbin

Call the packaging tool command (pkg_build.sh) using one of the following two modes:

Single Command Line Mode: Enter the command pkg_build.sh <list of arguments>.

Interactive Mode: Enter command pkg_build.sh and then enter each argument separately (one 
argument on each line).

If you are packaging bash scripts, the packaging tool expects the bash scripts to be version 3.0 or above.

The values supplied to the packaging tool determine the resources allocated to the packaged application 
when the package is installed. The only way to change the resource allocation is by re-packaging.

When you are upgrading an application, there are three arguments/parameters of the packaging tool to 
consider:

uuid: identifies the package when it was first created. To recall the uuid, enter the command “show 
software versions detail”. (See the “Verifying and Troubleshooting System Status” section in the 

name: name of the package using the same name that was used when the package was originally 
created.