diff --git a/windows/deployment/do/TOC.yml b/windows/deployment/do/TOC.yml index 4ab1afe9dd..f00cde0466 100644 --- a/windows/deployment/do/TOC.yml +++ b/windows/deployment/do/TOC.yml @@ -80,4 +80,5 @@ - name: Content endpoints for Delivery Optimization and Microsoft Connected Cache href: delivery-optimization-endpoints.md + diff --git a/windows/deployment/do/mcc-isp-common-issues.md b/windows/deployment/do/mcc-isp-common-issues.md new file mode 100644 index 0000000000..e69de29bb2 diff --git a/windows/deployment/do/mcc-isp-faq.md b/windows/deployment/do/mcc-isp-faq.md index e69de29bb2..b6edc9fb4c 100644 --- a/windows/deployment/do/mcc-isp-faq.md +++ b/windows/deployment/do/mcc-isp-faq.md @@ -0,0 +1,131 @@ +--- +title: FAQs on Microsoft Connected Cache for ISP +manager: dougeby +description: FAQs on Microsoft Connected Cache (MCC) for ISP +keywords: updates, downloads, network, bandwidth +ms.prod: w10 +ms.mktglfcycl: deploy +audience: itpro +author: nidos +ms.localizationpriority: medium +ms.author: nidos +ms.collection: M365-modern-desktop +ms.topic: article +--- + +# Microsoft Connected Cache for ISP (public preview) + +**Applies to** + +- Windows 10 +- Windows 11 + +
+ + **1. Is this a free service?** +Yes. Microsoft Connected Cache is a free service. + +
+ +**2. What will MCC do for me? How will it impact our customers?** +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. + +
+ +**3. Is there an NDA to sign?** + No NDA is required. + +
+ +**4. What are the prerequisites and hardware requirements?** +- Azure subscription +- Hardware to host MCC - The recommended configuration below will serve approximately 35,000 consumer devices downloading a 2GB payload in 24-hour timeframe at a sustained rate of 6.5 Gbps. +
+ +| Taffic Estimate | Hardware/VM Recommendation | +|-----------|:-----------:| +| <5G Peak | 8 Cores
16 GB Memory
1 SSD Drive 500 GB | +| 10 - 20G Peak | 16 Cores
32 GB Memory
2 - 3 SSD Drives 1 TB | +| 20 - 40G Peak | 32 Cores
64 GB Memory
4 - 6 SSDs 1 TB | + +
+
+ +**5. Will I need to provide hardware BareMetal server or VM?** + Microsoft Connected Cache (MCC) preview is a software-only caching solution and will require you to provide your own server to host the software. + +
+ +**6. Can we use hard drives instead of SSDs?** +We highly recommend using SSDs as MCC is a read intensive application. We also recommend using multiple drives to improve performance. + +
+ +**7. Will I need to manually enter the CIDR blocks? If I have multiple MCCs, should I configure a subset of CIDR blocks to each MCC?** +You have the option to route your traffic using manual CIDR blocks or BGP. If you have multiple MCCs, you can allocate subsets of CIDR blocks to each MCC if you wish. However, since MCC has automatic load balancing, we recommend adding all of your traffic to all of your MCCs. + +
+ +**8. Should I add any load balancing mechanism?** +You need not add any load balancing. Our service will take care of routing traffic if you have multiple MCCs serving the same CIDR blocks based on the reported health of the cache node. + +
+ +**9. How many MCC instances will I need? How do we setup if we support multiple countries?** +As stated in the table above, the recommended configuration will achieve near the maximum possible egress of 20Gbps with a two-port link aggregated NIC and four cache drives. If you provide us with your ASN numbers, we can give a rough estimate of how many MCC instances may be needed. If your ISP spans multiple countries, you can certainly set up separate MCC instances per country. + +
+ +**10. Where should we install MCC?** +You are in control of your hardware and you can pick the location based on your traffic and end customers. You can choose the location where you have your routers or where you have dense traffic or any other parameters. + +
+ +**11. How long would a piece of content live within the MCC? Is content purged from the cache?** +A request for said content is made, and NGINX looks at the cache control headers from the original acquisition, and if that content has expired, NGINX will continue to serve the stale content while it is downloading the new content. We are caching the content for 30 days. The content will be in the hot cache path (open handles and such) for 24 hrs, but will reside on disk for 30 days. +The drive fills up and nginx will start to delete content based on its own algorithm, probably some combination of least recently used. + +
+ +**12. What content is cached by MCC?** +MCC supports Windows and Office content. + +
+ +**13. Does MCC support Xbox or Teams content?** +Currently, MCC does not support Xbox or Teams content. However, supporting Xbox content is of high priority, and we expect this feature in the near future. We'll let you know as soon as it becomes available! + +
+ +**14. Is IPV6 supported?** +No, we do not currently support IPV6. We plan to support it in the future. + +
+ +**15. Is MCC stable and reliable?** +We have already successfully onboarded ISPs in many countries around the world and have received positive feedback! However, you can always start off with a portion of your CIDR blocks to test out the performance of MCC before expanding to more customers. + +
+ +**16.How does MCC populate its content?** +MCC is a cold cache warmed by client requests. The client requests content and that is what fills up the cache. There is no off-peak cache fill necessary. +MCC will reach out to different CDN providers just like a client device would. The traffic flow from MCC will vary depending on how you currently transit to each of these CDN providers. The content can come from 3rd party CDNs or from AFD. + +
+ +**17. What do I do if I need more support and have more questions even after reading this FAQ page?** +You can find more information or post your questions on MCC Community Forum. + + +For further support for your MCC you can find solutions to common problems here. + +
+ +**18. What CDNs will Microsoft Connected Cache pull content from?** + 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 do not 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) diff --git a/windows/deployment/do/mcc-isp-monitor.md b/windows/deployment/do/mcc-isp-monitor.md index 85b3f2bbc1..3d569071a8 100644 --- a/windows/deployment/do/mcc-isp-monitor.md +++ b/windows/deployment/do/mcc-isp-monitor.md @@ -3,14 +3,6 @@ ## Metrics Within Azure portal, there are a number of metrics that are available to monitor cache node health and performance. -### 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-isp-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 are unable to view metrics for your cache node, it may be that your cache node is unhealthy, inactive, or hasn't been fully configured. ### Available Metrics @@ -26,4 +18,4 @@ Within Azure portal, you are able to build your custom metrics using the followi | **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 metrics, visit [Azure Monitor](https://docs.microsoft.com/en-us/azure/azure-monitor/essentials/data-platform-metrics) for details. \ No newline at end of file +To learn more about how to build your custom metrics, visit [Azure Monitor](https://docs.microsoft.com/en-us/azure/azure-monitor/essentials/data-platform-metrics) for details. diff --git a/windows/deployment/do/mcc-isp-uninstall.md b/windows/deployment/do/mcc-isp-uninstall.md index 772887715f..77c5b02e47 100644 --- a/windows/deployment/do/mcc-isp-uninstall.md +++ b/windows/deployment/do/mcc-isp-uninstall.md @@ -1,6 +1,8 @@ # Uninstall your cache node There are two main steps required to uninstall your cache node: + + 1. Remove your cache node from Azure portal 1. Run the uninstall script to cleanly remove MCC from your server @@ -12,6 +14,7 @@ Within Azure portal, navigate to **Cache Nodes**, then select the cache node you ## Run the uninstall script to cleanly remove MCC from your server In the installer zip file, you'll find the file **uninstallmcc.sh**. This script uninstalls MCC and all the related components. Only run it if you're facing issues with MCC installation. + The **uninstallmcc.sh** script removes the following components: - IoT Edge @@ -26,5 +29,7 @@ To run the script, use the following commands: ```bash sudo chmod +x uninstallmcc.sh sudo ./uninstallmcc.sh + ``` + diff --git a/windows/deployment/do/mcc-isp-update.md b/windows/deployment/do/mcc-isp-update.md index 6b2ddaccf3..8029f6348e 100644 --- a/windows/deployment/do/mcc-isp-update.md +++ b/windows/deployment/do/mcc-isp-update.md @@ -4,4 +4,5 @@ Microsoft will release updates for MCC periodically to improve performance, func To view which version your cache nodes are currently on, navigate to the **Cache nodes** tab to view the versions in the list view. -To view update release notes, visit [Version History](mcc-version-history.md). \ No newline at end of file +To view update release notes, visit [Version History](mcc-version-history.md). + diff --git a/windows/deployment/do/mcc-isp-verify-cache-node.md b/windows/deployment/do/mcc-isp-verify-cache-node.md index b855ca73d2..fb166560d8 100644 --- a/windows/deployment/do/mcc-isp-verify-cache-node.md +++ b/windows/deployment/do/mcc-isp-verify-cache-node.md @@ -1,5 +1,6 @@ # Verify cache node functionality + ### 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. @@ -8,6 +9,7 @@ Log into Azure portal and navigate to the Overview page. Select the **Monitoring 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 `` with the IP address of the cache server. ```bash @@ -32,4 +34,6 @@ Similarly, enter the following URL into a web browser on any device on the netwo http:///mscomtest/wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com ``` -If the test fails, for more information, see the [FAQs](#mcc-isp-faq) section. \ No newline at end of file + +If the test fails, for more information, see the [FAQs](#mcc-isp-faq) section. +