diff --git a/windows/deployment/do/mcc-isp-overview.md b/windows/deployment/do/mcc-isp-overview.md index 60b248f3ae..e3474b59cb 100644 --- a/windows/deployment/do/mcc-isp-overview.md +++ b/windows/deployment/do/mcc-isp-overview.md @@ -13,7 +13,7 @@ appliesto: - ✅ Windows 11 - ✅ Windows 10 - ✅ Microsoft Connected Cache for ISPs -ms.date: 07/27/2023 +ms.date: 03/21/2024 --- # Microsoft Connected Cache for ISPs overview @@ -37,10 +37,15 @@ Microsoft Connected Cache uses Delivery Optimization as the backbone for Microso - Endpoint protection: Windows Defender definition updates - Xbox: Xbox Game Pass (PC only) -Do you peer with [Microsoft (ASN 8075)](/azure/internet-peering/)? Microsoft Connected Cache complements peering by offloading static content that is served off of multiple CDNs such as Akamai, Lumen, and Edgecast. Microsoft Peering mainly caches dynamic content - by onboarding to Microsoft Connected Cache, you'll cache static content that otherwise would be served from the CDN. - For the full list of content endpoints that Microsoft Connected Cache for ISPs supports, see [Microsoft Connected Cache content and services endpoints](delivery-optimization-endpoints.md). +### Are you already peering with 8075? + +MCC complements peering by offloading static content that is served off of multiple CDNs such as Akamai, Lumen, Edgecast. Static content such as OS updates, Apps, Software installs etc. can't be served via 8075. So, even if you're peering with Microsoft, you can benefit from installing MCC. + +:::image type="content" source="./media/mcc-isp-overview/mcc-isp-peeringvsmcc.png" alt-text="Chart containing Peering vs Cache Content Traffic." lightbox="./media/mcc-isp-overview/mcc-isp-peeringvsmcc.png"::: + + ## How MCC works :::image type="content" source="./images/mcc-isp-diagram.png" alt-text="Data flow diagram of how Microsoft Connected Cache works." lightbox="./images/mcc-isp-diagram.png"::: @@ -71,3 +76,18 @@ The following steps describe how MCC is provisioned and used: 1. Subsequent requests from end-user devices for content will be served from cache. 1. If the MCC node is unavailable, the client gets content from the CDN to ensure uninterrupted service for your subscribers. + +### Hardware recommendation + +The following are recommended hardware configurations based on traffic ranges: + +| Microsoft Connected Cache Machine Class | Scenario |Traffic Range| VM/Hardware Recommendation| +| -------- | -------- | -------- | -------- | +| Edge | For smaller ISPs or remote sites part of a larger network. |< 5 Gbps Peak| **VM**

Up to 8 cores

Up to 16-GB memory

1 500 GB SSD| +| Metro POP | For ISPs, IXs, or Transit Providers serving a moderate amount of traffic in a network that might require one of more cache nodes. |5 to 20 Gbps Peak| **VM or hardware**

16 cores*

32-GB memory

2 - 3 500-GB SSDs each| +|Data Center|For ISPs, IXs, or Transit Providers serving a large amount traffic daily and might require deployment of multiple cache nodes.|20 to 40 Gbps Peak| **Hardware**, see sample spec below:

32 or more cores*

64 or more GB memory

4 - 6 500 - 1-TB SSDs** each | + +*Requires systems (chipset, CPU, motherboard) with PCIe version 3, or higher. + +**Drive speeds are important and to achieve higher egress, we recommend SSD NVMe in m.2 PCIe slot (version 4, or higher). + diff --git a/windows/deployment/do/media/mcc-isp-overview/mcc-isp-peeringvsmcc.png b/windows/deployment/do/media/mcc-isp-overview/mcc-isp-peeringvsmcc.png new file mode 100644 index 0000000000..de0852f52e Binary files /dev/null and b/windows/deployment/do/media/mcc-isp-overview/mcc-isp-peeringvsmcc.png differ