From 77b74a0638819f4d776971cebfb2fbb7f3014efd Mon Sep 17 00:00:00 2001 From: Amy Zhou Date: Tue, 16 Aug 2022 16:45:41 -0700 Subject: [PATCH 1/3] new table of contents and files for public preview --- windows/deployment/do/TOC.yml | 45 ++++++++++++++++++- .../do/mcc-isp-cache-node-configuration.md | 0 .../deployment/do/mcc-isp-client-routing.md | 0 .../deployment/do/mcc-isp-common-issues.md | 0 .../do/mcc-isp-configure-routing.md | 0 windows/deployment/do/mcc-isp-create.md | 0 .../do/mcc-isp-device-provisioning.md | 0 windows/deployment/do/mcc-isp-faq.md | 0 windows/deployment/do/mcc-isp-monitor.md | 0 .../deployment/do/mcc-isp-provision-deploy.md | 0 windows/deployment/do/mcc-isp-signup.md | 0 windows/deployment/do/mcc-isp-support.md | 0 windows/deployment/do/mcc-isp-uninstall.md | 0 windows/deployment/do/mcc-isp-update.md | 0 .../do/mcc-isp-verify-cache-node.md | 0 .../deployment/do/mcc-isp-vm-performance.md | 0 16 files changed, 44 insertions(+), 1 deletion(-) create mode 100644 windows/deployment/do/mcc-isp-cache-node-configuration.md create mode 100644 windows/deployment/do/mcc-isp-client-routing.md create mode 100644 windows/deployment/do/mcc-isp-common-issues.md create mode 100644 windows/deployment/do/mcc-isp-configure-routing.md create mode 100644 windows/deployment/do/mcc-isp-create.md create mode 100644 windows/deployment/do/mcc-isp-device-provisioning.md create mode 100644 windows/deployment/do/mcc-isp-faq.md create mode 100644 windows/deployment/do/mcc-isp-monitor.md create mode 100644 windows/deployment/do/mcc-isp-provision-deploy.md create mode 100644 windows/deployment/do/mcc-isp-signup.md create mode 100644 windows/deployment/do/mcc-isp-support.md create mode 100644 windows/deployment/do/mcc-isp-uninstall.md create mode 100644 windows/deployment/do/mcc-isp-update.md create mode 100644 windows/deployment/do/mcc-isp-verify-cache-node.md create mode 100644 windows/deployment/do/mcc-isp-vm-performance.md diff --git a/windows/deployment/do/TOC.yml b/windows/deployment/do/TOC.yml index ba824d08fb..7c3e61afa3 100644 --- a/windows/deployment/do/TOC.yml +++ b/windows/deployment/do/TOC.yml @@ -28,7 +28,50 @@ - name: MCC for Enterprise and Education href: mcc-enterprise.md - name: MCC for ISPs - href: mcc-isp.md + items: + - name: MCC for ISPs Overview + href: mcc-isp.md + - name: Concepts + items: + - name: Device Provisioning + href: mcc-isp-device-provisioning.md + - name: Client Routing + href: mcc-isp-client-routing.md + - name: Cache Node Configuration + href: mcc-isp-cache-node-configuration.md + - name: How-to guides + items: + - name: Operator sign up and service onboarding + href: mcc-isp-signup.md + - name: Create the MCC in Azure portal + href: mcc-isp-create.md + - name: Provision and deploy cache node to your server + href: mcc-isp-provision-deploy.md + - name: Configure client routing for cache node + href: mcc-isp-configure-routing.md + - name: Verify cache node functionality + href: mcc-isp-verify-cache-node.md + - name: Update your cache node + href: mcc-isp-update.md + - name: Monitor cache node health and performance + href: mcc-isp-monitor.md + - name: Uninstall your cache node + href: mcc-isp-uninstall.md + - name: Resources + items: + - name: MCC for ISP Community Forum + href: link-to-come + - name: FAQs + href: mcc-isp-faq.md + - name: Common Issues + href: mcc-isp-common-issues.md + - name: Enhancing VM performance + href: mcc-isp-vm-performance.md + - name: Support + href: mcc-isp-support.md + + + - name: Resources items: diff --git a/windows/deployment/do/mcc-isp-cache-node-configuration.md b/windows/deployment/do/mcc-isp-cache-node-configuration.md new file mode 100644 index 0000000000..e69de29bb2 diff --git a/windows/deployment/do/mcc-isp-client-routing.md b/windows/deployment/do/mcc-isp-client-routing.md new file mode 100644 index 0000000000..e69de29bb2 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-configure-routing.md b/windows/deployment/do/mcc-isp-configure-routing.md new file mode 100644 index 0000000000..e69de29bb2 diff --git a/windows/deployment/do/mcc-isp-create.md b/windows/deployment/do/mcc-isp-create.md new file mode 100644 index 0000000000..e69de29bb2 diff --git a/windows/deployment/do/mcc-isp-device-provisioning.md b/windows/deployment/do/mcc-isp-device-provisioning.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 new file mode 100644 index 0000000000..e69de29bb2 diff --git a/windows/deployment/do/mcc-isp-monitor.md b/windows/deployment/do/mcc-isp-monitor.md new file mode 100644 index 0000000000..e69de29bb2 diff --git a/windows/deployment/do/mcc-isp-provision-deploy.md b/windows/deployment/do/mcc-isp-provision-deploy.md new file mode 100644 index 0000000000..e69de29bb2 diff --git a/windows/deployment/do/mcc-isp-signup.md b/windows/deployment/do/mcc-isp-signup.md new file mode 100644 index 0000000000..e69de29bb2 diff --git a/windows/deployment/do/mcc-isp-support.md b/windows/deployment/do/mcc-isp-support.md new file mode 100644 index 0000000000..e69de29bb2 diff --git a/windows/deployment/do/mcc-isp-uninstall.md b/windows/deployment/do/mcc-isp-uninstall.md new file mode 100644 index 0000000000..e69de29bb2 diff --git a/windows/deployment/do/mcc-isp-update.md b/windows/deployment/do/mcc-isp-update.md new file mode 100644 index 0000000000..e69de29bb2 diff --git a/windows/deployment/do/mcc-isp-verify-cache-node.md b/windows/deployment/do/mcc-isp-verify-cache-node.md new file mode 100644 index 0000000000..e69de29bb2 diff --git a/windows/deployment/do/mcc-isp-vm-performance.md b/windows/deployment/do/mcc-isp-vm-performance.md new file mode 100644 index 0000000000..e69de29bb2 From e710acf76916f12cbe422b87c906eea563d82357 Mon Sep 17 00:00:00 2001 From: Amy Zhou Date: Thu, 25 Aug 2022 22:22:51 -0700 Subject: [PATCH 2/3] first round of changes --- windows/deployment/do/mcc-isp-monitor.md | 23 +++++++++ windows/deployment/do/mcc-isp-uninstall.md | 32 ++++++++++++ windows/deployment/do/mcc-isp-update.md | 7 +++ .../do/mcc-isp-verify-cache-node.md | 49 +++++++++++++++++++ .../deployment/do/mcc-isp-vm-performance.md | 13 +++++ 5 files changed, 124 insertions(+) diff --git a/windows/deployment/do/mcc-isp-monitor.md b/windows/deployment/do/mcc-isp-monitor.md index e69de29bb2..0fbf21f6bb 100644 --- a/windows/deployment/do/mcc-isp-monitor.md +++ b/windows/deployment/do/mcc-isp-monitor.md @@ -0,0 +1,23 @@ +# Monitor cache node health and performance + +## Metrics +Within Azure portal, there are a number of metrics that are available to monitor cache node health and performance. + +### Available Metrics + - **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 + +### Viewing your metrics +To view the metrics associated with your cache nodes, navigate to the **Overview** tab within Azure portal. + +[[ include screenshot of an example view]] + +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. diff --git a/windows/deployment/do/mcc-isp-uninstall.md b/windows/deployment/do/mcc-isp-uninstall.md index e69de29bb2..9aeb0a7462 100644 --- a/windows/deployment/do/mcc-isp-uninstall.md +++ b/windows/deployment/do/mcc-isp-uninstall.md @@ -0,0 +1,32 @@ +# Uninstall your cache node + +There are two main steps required to uninstall your cache node: +1. Delete your cache node from the Azure portal +1. Run the uninstall script to cleanly remove MCC from your server + + +## Delete your cache node from the Azure portal +Navigate to your Overview page. On the top bar, click on **Delete**. + + +## 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. Before you run this script, contact the MCC team. Only run it if you're facing issues with MCC installation. + +> [!WARNING] +> Be cautious before running this script. It will also erase existing IoT workflows in this VM. + +The **uninstallmcc.sh** script removes the following components: + +- IoT Edge +- Edge Agent +- Edge Hub +- MCC +- Moby CLI +- Moby engine + +To run the script, use the following commands: + +```bash +sudo chmod +x uninstallmcc.sh +sudo ./uninstallmcc.sh +``` \ No newline at end of file diff --git a/windows/deployment/do/mcc-isp-update.md b/windows/deployment/do/mcc-isp-update.md index e69de29bb2..02a1de7874 100644 --- a/windows/deployment/do/mcc-isp-update.md +++ b/windows/deployment/do/mcc-isp-update.md @@ -0,0 +1,7 @@ +# Update your cache node + +Microsoft will release updates for MCC periodically to improve performance, functionality, and security. Updates will not require any action from the customer. Instead, when an update is available, your cache node will automatically update during low traffic hours with minimal to no impact to your end customers. + +To view which version your cache nodes are currently on, [[*********]]. + +To view update release notes, visit our Tech Community page. \ No newline at end of file diff --git a/windows/deployment/do/mcc-isp-verify-cache-node.md b/windows/deployment/do/mcc-isp-verify-cache-node.md index e69de29bb2..78593909c6 100644 --- a/windows/deployment/do/mcc-isp-verify-cache-node.md +++ b/windows/deployment/do/mcc-isp-verify-cache-node.md @@ -0,0 +1,49 @@ +# Verify cache node functionality + +### Verify client side + +Sign in to the Connected Cache server or use SSH. Run the following command from a terminal to see the running modules (containers): + +```bash +sudo iotedge list +``` + +If the cache server is running properly, you will see the containers **edgeAgent**, **edgeHub**, and **[Your Cache Node name]** listed, all with the status **running**. + +If it lists the **edgeAgent** and **edgeHub** containers, but doesn't include **MCC**, view the status of the IoT Edge security manager using the command: + +```bash +sudo journalctl -u iotedge -f +``` + +This command provides the current status of the starting and stopping of a container or the container pull and start. + +### Verify server side + +It can take a few minutes for the container to deploy. + +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 +wget http:///mscomtest/wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com +``` + +If successful, you will see a terminal output similar to the following: + +```bash +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 MCC."::: + +Similarly, enter the following URL into a web browser on any device on the network: + +```http +http:///mscomtest/wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com +``` + +If the test fails, for more information, see the [common issues](#common-issues) section. \ No newline at end of file diff --git a/windows/deployment/do/mcc-isp-vm-performance.md b/windows/deployment/do/mcc-isp-vm-performance.md index e69de29bb2..36a3908fcb 100644 --- a/windows/deployment/do/mcc-isp-vm-performance.md +++ b/windows/deployment/do/mcc-isp-vm-performance.md @@ -0,0 +1,13 @@ +# Enhancing VM Performance + +In virtual environments, the cache server egress peaks at around 1.1 Gbps. If you want to maximize the egress in virtual environments, it's critical to change the following two settings: + +1. Enable **SR-IOV** in the following three locations: + + - The BIOS of the MCC VM + - The MCC VM's network card properties + - The hypervisor for the MCC VM + + Microsoft has found these settings to double egress when using a Microsoft Hyper-V deployment. + +2. Enable "high performance" in the BIOS instead of energy savings. Microsoft has found this setting to also nearly double egress in a Microsoft Hyper-V deployment. \ No newline at end of file From 0a7e2d637a12db1bfdd133b98f257437657d6a9e Mon Sep 17 00:00:00 2001 From: doshnid <77081571+doshnid@users.noreply.github.com> Date: Mon, 12 Sep 2022 14:49:33 -0700 Subject: [PATCH 3/3] new faq --- windows/deployment/do/mcc-isp-faq.md | 131 +++++++++++++++++++++++++++ 1 file changed, 131 insertions(+) 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)