GEM and automatically executed CLI commands


Article ID: 167791


Updated On:




This article informs about CLI commands periodically executed by GEM.This article informs about CLI commands periodically executed by GEM.


The following two processes can be intermittently seen in the process list on the CPM:

/crossbeam/bin/cli --raw -q -i exec -echo continue-on-error /usr/share/tomcat5/webapps/gem/WEB-INF/data/config/cli_commands_health_data_update.txt

/crossbeam/bin/cli --raw -q -i exec -echo continue-on-error /usr/share/tomcat5/webapps/gem/WEB-INF/data/config/cli_commands_chassis_inventory_update.txt


GEM utilizes the CLI to collect some of the chassis operational data. The actual CLI commands are defined in the following two files on the CPM: 

# cat /usr/share/tomcat5/webapps/gem/WEB-INF/data/config/cli_commands_health_data_update.txt
show chassis
show interface detail
show resource-statistics verbose
show npm-originated-flow-stats
show flow distribution
show module status
show apm-resource-protection vap-group-status verbose
show statistics traffic

# cat /usr/share/tomcat5/webapps/gem/WEB-INF/data/config/cli_commands_chassis_inventory_update.txt
show chassis
show operating-mode
show apm-resource-protection admin-status
show apm-resource-protection detected-hosts verbose
show module status
show ap-vap-mapping
show application vap-group
show hostname
show current-release
show cp-redundancy
show environment
show facility-alarm
show vap-group
show netflow
show license-history

The chassis health data are retrieved every 15 seconds, while the inventory data are collected every 30 seconds.