In order to perform crucial networking and security tasks, the MX Security Appliance must allocate resources to a large number of computational tasks. This is required for a wide range of packet processing functions, such as routing packets, performing deep packet inspection for identification and blocking of malicious traffic, and performing packet analysis for traffic classification.
Device load is an important tool to answer short and long term troubleshooting and planning questions. Periods of very high sustained load may result in an overall delay in the MX's ability to perform key packet processing tasks. Subsequently, load monitoring can be an important tool when troubleshooting network performance issues. For long-term network planning, understanding the device's load over time can help to project and identify when a device upgrade may be required for growing sites.
The feature discussed in this article is only available in beta. If you are interested in participating in this beta, please contact your Cisco Meraki sales rep or the Cisco Meraki Support team.
The MX's load is reported through the Cisco Meraki Dashboard API. The load value is returned in numeric value ranging from 1 through 100. A lower value indicates a lower load, where a higher value indicates a more intense workload. Currently, the load value is calculated based upon the CPU utilization of the MX and it's traffic load.
The API call for the "performance score" is as follows:
Return the performance score for a single device. Only primary MX devices supported. If no data is available, error code 204 is returned.
An example request and response is included below:
curl -L -H 'X-Cisco-Meraki-API-Key: -----' -X GET -H'Content-Type: application/json' 'https://Dashboard.meraki.com/api/v0/networks/L_-----/devices/Q2QN-XXXX-XXXX/performance'
Example of results over time: