Admin - Add-On Packages and Features
- No explicit support here, 3rd party can add their own collector
AXP runs a syslog server that can receive log messages from remote hosts. To use this functionality, the following needs to be done:
1. Write code that uses syslog to log messages, or able to direct logs to syslog when running the program
2. Direct log messages to remote syslog
3. Setup AXP to run remote syslog server
See this online resource for using the syslog API:
Example of using syslog API:
For java programs, developers can use the log4j module, see the following online resource:
Example of using Java log4j API:
By default, C programs using the syslog API should be directed to the local syslog server. In order to direct log messages from local syslog server to remote syslog server, users need to configure the syslog server config file, usually at /etc/syslog.conf, or /etc/syslog-ng.conf if local syslog server is syslog-ng.
For example, append the following line to the config file to redirect all log messages of facility "local1" and priority "info" and higher to "myblade"
Using the log4j, user can configure the syslog behavior by editing the log4j.properties file.
- mySyslog config
log4j.appender.mySyslog.layout.ConversionPattern=%p %t %c - %m%n
Use the CLI to enable the remote syslog server
blade# config terminal
There are CLI to show remote syslog server status
Also, there are CLIs 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
The range for file-rotation is from 1 to 40. The range for file-size is from 1 to 1000 (in MB). By default, file-rotation is 10 and file-size is 20.
The OSGi specification defines how Java applications or components (bundles in OSGi term) can be remotely installed, started, stopped, updated and uninstalled without requiring a reboot and post no impact to the operation of the device.
AXP has chosen and partnered with ProSyst, the leading commercial OSGi software provider, to provide the OSGI framework to the customers.
- OSGi support by Cisco is provided via the optional infrastructure add-on package, prosyst_mbs6.pkg, without any license key embedded.
- The current supported osgi package is ProSyst Embedded Server mBS6.0 Framework package 6.0.02
- If customers choose not to use Cisco provided prosyst_osgi.pkg (i.e. version is not compatible with their product etc.). Customers will purchase the Cisco signed OSGI bundle directly from Prosyst and packaged in their application packages for installation and used as per their requirements.
1. In general, customers who require OSGI support and would like to leverage Cisco prosyst_osgi.pkg, need to purchase the license from ProSyst directly.
2. Application developer needs to place the license key file (domain.crp) in the AXP designated path, /opt (i.e. /opt/domain.crp ), in their project tree. The key file will then be packaged inside the Application add-on package.
3. The startup script for prosys_osgi.pkg will first copy the license key file before it starts up the mBeddedServer.
- AXP provides add-on CLI, connect osgi, to manage the OSGI framework.
o > connect osgi
- This command will cross connect to the text console of the Prosyst OSGI framework and allows administration to manage the OSGI framework by means of Prosyst text commands (CLI) from there.
- This command is only available when prosys_mbs6.pkg infrastructure add_on package is installed.