edits and image renames

This commit is contained in:
Meghan Stewart 2022-10-17 15:43:51 -07:00
parent d322bd63f9
commit c765d63c74
5 changed files with 12 additions and 9 deletions

View File

Before

Width:  |  Height:  |  Size: 40 KiB

After

Width:  |  Height:  |  Size: 40 KiB

View File

Before

Width:  |  Height:  |  Size: 54 KiB

After

Width:  |  Height:  |  Size: 54 KiB

View File

@ -29,7 +29,7 @@ sections:
- question: What will Microsoft Connected Cache do for me? How will it impact our customers?
answer: As an ISP, your network can benefit from reduced load on your backbone and improve customer download experience for supported Microsoft static content. It will also help you save on CDN costs.
- question: Is there a non-disclosure agreement to sign?
answer: No non-disclosure agreement is required.
answer: No, a non-disclosure agreement isn't required.
- question: What are the prerequisites and hardware requirements?
answer: |
- Azure subscription
@ -46,7 +46,7 @@ sections:
- question: Can we use hard drives instead of SSDs?
answer: We highly recommend using SSDs as Microsoft Connected Cache is a read intensive application. We also recommend using multiple drives to improve performance.
- question: Will I need to manually enter the CIDR blocks? If I have multiple cache nodes, should I configure a subset of CIDR blocks to each cache node?
answer: You can choose route your traffic using manual CIDR blocks or BGP. If you have multiple Microsoft Connected Cache(s), you can allocate subsets of CIDR blocks to each cache node if you wish. However, since Microsoft Connected Cache has automatic load balancing, we recommend adding all of your traffic to all of your cache nodes.
answer: You can choose to route your traffic using manual CIDR blocks or BGP. If you have multiple Microsoft Connected Cache(s), you can allocate subsets of CIDR blocks to each cache node if you wish. However, since Microsoft Connected Cache has automatic load balancing, we recommend adding all of your traffic to all of your cache nodes.
- question: Should I add any load balancing mechanism?
answer: You don't need to add any load balancing. Our service will take care of routing traffic if you have multiple cache nodes serving the same CIDR blocks based on the reported health of the cache node.
- question: How many Microsoft Connected Cache instances will I need? How do we set up if we support multiple countries?
@ -70,8 +70,11 @@ sections:
- question: What CDNs will Microsoft Connected Cache pull content from?
answer: |
Microsoft relies on a dynamic mix of 1st and 3rd party CDN providers to ensure enough capacity, redundancy, and performance for the delivery of Microsoft served content. Though we don't provide lists of the CDN vendors we utilize as they can change without notice, our endpoints are public knowledge. If someone were to perform a series of DNS lookups against our endpoints (tlu.dl.delivery.mp.microsoft.com for example), they would be able to determine which CDN or CDNs were in rotation at a given point in time:
$ dig +noall +answer tlu.dl.delivery.mp.microsoft.com | grep -P "IN\tA"
c-0001.c-msedge.net. 20 IN A 13.107.4.50
$ whois 13.107.4.50|grep "Organization:"
Organization: Microsoft Corporation (MSFT)

View File

@ -36,7 +36,7 @@ You must complete both steps to ensure a clean uninstall of your cache node.
### Remove your cache node from Azure portal
Within [Azure portal](https://www.portal.azure.com), navigate to **Cache Nodes**, then select the cache node you wish to delete. Once selected, select **Delete** on the top bar to remove this cache node from your account.
Within the [Azure portal](https://www.portal.azure.com), navigate to **Cache Nodes**, then select the cache node you wish to delete. Once selected, select **Delete** on the top bar to remove this cache node from your account.
### Run the uninstall script to cleanly remove Microsoft Connected Cache from your server

View File

@ -15,11 +15,11 @@ ms.topic: 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
This article details how to verify that your cache node(s) are functioning properly and serving traffic. This article also details how to monitor your cache nodes.
## Verify functionality on Azure portal
Log into [Azure portal](https://www.portal.azure.com) 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.
Sign into the [Azure portal](https://www.portal.azure.com) 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
@ -31,7 +31,7 @@ To validate a properly functioning MCC, run the following command in the termina
wget http://<CacheServerIP>/mscomtest/wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com
```
If successful, you'll see a terminal output similar to the following:
If successful, you'll see a terminal output similar to the following output:
```bash
HTTP request sent, awaiting response... 200 OK
@ -41,7 +41,7 @@ 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.":::
:::image type="content" source="images/mcc-isp-wget.png" alt-text="Terminal output of successful test result with wget command to validate a Microsoft Connected Cache node." lightbox="./images/mcc-isp-wget.png":::
Similarly, enter the following URL into a web browser on any device on the network:
@ -60,7 +60,7 @@ Within Azure portal, there are many charts and graphs that are available to moni
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|