4.0 KiB
title, manager, description, keywords, ms.prod, ms.mktglfcycl, audience, author, ms.localizationpriority, ms.author, ms.collection, ms.topic
| title | manager | description | keywords | ms.prod | ms.mktglfcycl | audience | author | ms.localizationpriority | ms.author | ms.collection | ms.topic |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Verify cache node functionality and monitor health and performance | dougeby | How to verify the functionality of a cache node | updates, downloads, network, bandwidth | w10 | deploy | itpro | amyzhou | medium | amyzhou | M365-modern-desktop | article |
Verify cache node functionality and monitor health and performance
This article details how to verify that your cache node(s) are functioning properly and serving traffic. In addition, this article details
Verify functionality on Azure portal
Log into Azure portal and navigate to the Overview page. Select the Monitoring tab to verify the functionality of your server(s) by validating the number of healthy nodes shown. If you see any Unhealthy nodes, select the Diagnose and Solve link to troubleshoot and resolve the issue.
Verify functionality on the server
It can take a few minutes for the container to deploy after you've saved the configuration.
To validate a properly functioning MCC, run the following command in the terminal of the cache server or any device in the network. Replace <CacheServerIP> with the IP address of the cache server.
wget http://<CacheServerIP>/mscomtest/wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com
If successful, you'll see a terminal output similar to the following:
HTTP request sent, awaiting response... 200 OK
Length: 969710 (947K) [image/gif]
Saving to: 'wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com'
wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com 100%[========================]
:::image type="content" source="images/imcc28.png" alt-text="Terminal output of successful test result with wget command to validate a Microsoft Connected Cache node.":::
Similarly, enter the following URL into a web browser on any device on the network:
http://<CacheServerIP>/mscomtest/wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com
If the test fails, for more information, see the FAQs section.
Monitor cache node health and performance
Within Azure portal, there are many charts and graphs that are available to monitor cache node health and performance.
Available Metrics
Within Azure portal, you're able to build your custom charts and graphs using the following available metrics:
| Metric name | Description |
|---|---|
| Cache Efficiency | Cache efficiency is defined as the total cache hit bytes divided by all bytes requested. The higher this value (0 - 100%), the more efficient the cache node is. |
| Healthy nodes | The number of cache nodes that are reporting as healthy |
| Unhealthy nodes | The number of cache nodes that are reporting as unhealthy |
| Maximum in | The maximum egress (in Gbps) of inbound traffic |
| Maximum out | The maximum egress (in Gbps) of outbound traffic |
| Average in | The average egress (in Gbps) of inbound traffic |
| Average out | The average egress (in Gbps) of outbound traffic |
To learn more about how to build your custom charts and graphs, visit Azure Monitor for details.
Monitoring your metrics
To view the metrics associated with your cache nodes, navigate to the Overview >> Monitoring tab within Azure portal.
:::image type="content" source="images/mcc-img-metrics.PNG" alt-text="Screenshot of the Azure portal displaying the metrics view in the Overview tab":::
You can choose to monitor the health and performance of all cache nodes or one by one by using the dropdown menu. The Egress bits per second graph shows your inbound and outbound traffic of your cache nodes over time. You can change the time range (1 hour, 12 hours, 1 day, 7 days, 14 days, and 30 days) by selecting the time range of choice on the top bar.
If you're unable to view metrics for your cache node, it may be that your cache node is unhealthy, inactive, or hasn't been fully configured.