This article presents options for monitoring an APM hard drive.
Here are several different ways to monitor the APM HDD:
1. The SNMP on the CPM monitors for hard drive errors using alarm name diskDriveError within the CBS-HARDWARE-MIB. So, if a HDD fails on an APM, the alarm would be generated. If you have SNMP traps enabled in the XOS configuration, then a trap would be sent out as well. Please review 'Crossbeam SNMP MIB Reference' in the XOS Configuration Guide for more details about XOS SNMP MIBs.
2. The HDD on the APM is primarily used by certain applications that require local HDD, such as Sourcefire, McAfee, and Imperva. More details of what is stored on local drive by each application is available in KB article 000019436.
3. XOS SNMP is configured and run on the CPM. The application SNMP is configured and run on the APMs. Contact the support team at Sourcefire, McAfee, or Imperva for more details about running SNMP on the VAPs and to find out if it includes OIDs for monitoring disk space. KB article 000020181 provides the location of the Sourcefire MIBs on the VAP (APM).
4. To determine the disk utilization manually on the chassis, you can run the following CLI command:
CBS# show statistics table disk-utilization
The above command will show the disk utilization by all modules. To filter for a specific module, add the source <module> attribute. For example:
CBS# show statistics table disk-utilization source ap7
The above command will show disk utilization for the APM in slot 9.