How to Monitor the Disk Utilization of the CA API Gateway Partitions via SNMP

Document ID : KB000010795
Last Modified Date : 14/02/2018
Show Technical Document Details

SNMP is a protocol for monitoring and managing devices or components within a network. SNMP supports three primary monitoring methods: getting, walking, and trapping. An SNMPGET allows a remote monitor or manager to fetch a particular monitored element. An SNMPWALK allows a remote monitor or manager to fetch a range of values within a class. An SNMP trap allows a monitored entity to generate a notification that is sent to a remote monitor based on certain conditions. This article will focus on configuring the Gateway appliance to allow remote monitors to be queried via getting and walking.

The following document should be executed in order to enable generalized access for SNMP monitoring on the API Gateway: Enabling SNMP monitoring in the CA API Gateway. This document configures the API Gateway to allow remote hosts to access the SNMP daemon running on the API Gateway. This document serves as a supplement to the aforementioned document to permit a specific type of monitoring.



  1. Open the SNMP daemon configuration file: vi /etc/snmp/snmpd.conf
  2. Append one or more lines to the end of the file as follows: disk <partition path> <size in KiB>
  3. Save the file and exit.
  4. Restart the SNMP daemon: service snmpd restart
  5. Query the system for monitored partitions: snmpwalk -v 2c -c <community> <hostname> .
There are several values in this procedure that should be substituted from the provided placeholder values: The value will vary based upon the hostname of the Gateway being monitored. The value of ca should be substituted with the appropriate community name. The value of community should reflect the appropriate community name. The value of hostname should reflect the fully qualified domain name of the monitored Gateway.

The output of step #5 will print out all of the monitorable properties of each monitored partition. This includes but is not limited to:

  • Partition path
  • Partition device name
  • Total partition space
  • Available partition space
  • Used partition space

An example output is illustrated below:

UCD-SNMP-MIB::dskIndex.1 = INTEGER: 1
UCD-SNMP-MIB::dskIndex.2 = INTEGER: 2
UCD-SNMP-MIB::dskPath.1 = STRING: /
UCD-SNMP-MIB::dskPath.2 = STRING: /var/lib/mysql
UCD-SNMP-MIB::dskDevice.1 = STRING: /dev/mapper/vg00-lv_root
UCD-SNMP-MIB::dskDevice.2 = STRING: /dev/mapper/vg00-lv_db
UCD-SNMP-MIB::dskMinimum.1 = INTEGER: 10000
UCD-SNMP-MIB::dskMinimum.2 = INTEGER: 2097152
UCD-SNMP-MIB::dskMinPercent.1 = INTEGER: -1
UCD-SNMP-MIB::dskMinPercent.2 = INTEGER: -1
UCD-SNMP-MIB::dskTotal.1 = INTEGER: 8256952
UCD-SNMP-MIB::dskTotal.2 = INTEGER: 21641788
UCD-SNMP-MIB::dskAvail.1 = INTEGER: 6566464
UCD-SNMP-MIB::dskAvail.2 = INTEGER: 20227964