deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 13:27:23 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Merge pull request #7 from amymzhou/amyzhou-mcc

Browse Source 
Amyzhou mcc
This commit is contained in:
Amy Zhou 2022-09-15 22:53:26 -07:00 committed by GitHub
commit 5f68c6e2bd
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
13 changed files with 49 additions and 56 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
windows/deployment/do/TOC.yml
View File

@ -27,14 +27,12 @@
href: delivery-optimization-proxy.md
- name: Microsoft Connected Cache
items:
- name: MCC overview
- name: Microsoft Connected Cache overview
href: waas-microsoft-connected-cache.md
- name: MCC for Enterprise and Education
href: mcc-enterprise.md
- name: MCC for ISPs
items:
- name: Overview
href: mcc-isp-overview.md
- name: Concepts
items:
- name: Device provisioning
@ -49,7 +47,7 @@
items:
- name: Operator sign up and service onboarding
href: mcc-isp-signup.md
- name: Create the MCC in Azure portal
- name: Create the cache node in Azure portal
href: mcc-isp-create.md
- name: Provision and deploy cache node to your server
href: mcc-isp-provision-deploy.md

4
windows/deployment/do/mcc-isp-cache-node-configuration.md
View File

@ -15,7 +15,7 @@ ms.topic: article
# Cache node configuration
All cache node configuration will take place within Azure portal. This article outlines all of the settings that you will be able to configure.
All cache node configuration will take place within Azure portal. This article outlines all of the settings that you'll be able to configure.
## Settings
@ -37,7 +37,7 @@ All cache node configuration will take place within Azure portal. This article o
| Field Name | Expected Value| Description |
| -- | --- | --- |
| **Manual touting - Address range/CIDR blocks** | IPv4 CIDR notation | The IP address range (CIDR blocks) that should be routed to the MCC server as a comma separated list. For example: 2.21.234.0/24, 3.22.235.0/24, 4.23.236.0/24 |
| **Manual routing - Address range/CIDR blocks** | IPv4 CIDR notation | The IP address range (CIDR blocks) that should be routed to the MCC server as a comma separated list. For example: 2.21.234.0/24, 3.22.235.0/24, 4.23.236.0/24 |
| **BGP - Neighbor ASN** | ASN | When configuring BGP, enter the ASN(s) of your neighbors that you want to establish. |
| **BGP - Neighbor IP address** | IPv4 address | When configuring BGP, enter the IP address(es) of neighbors that you want to establish. |

4
windows/deployment/do/mcc-isp-client-routing.md
View File

@ -15,13 +15,13 @@ ms.topic: article
# Client routing
Before serving traffic to your customers, client routing configuration is needed. During the configuration of your cache node in Azure portal, you will be able to route your clients to your cache node.
Before serving traffic to your customers, client routing configuration is needed. During the configuration of your cache node in Azure portal, you'll be able to route your clients to your cache node.
Microsoft Connected Cache offers two ways for you to route your clients to your cache node. The first method of manual entry involves uploading a comma-separated list of CIDR blocks that represents the clients. The second method of setting BGP (Border Gateway Protocol) is more automatic and dynamic, which is set up by establishing neighborships with other ASNs. All routing methods are set up within Azure portal.
Once client routing and other settings are configured, your cache node will be able to download content and serve traffic to your customers.
At this time, only IPv4 addresses are supported. IPv6 addresses are not supported.
At this time, only IPv4 addresses are supported. IPv6 addresses aren't supported.
### Manual routing

14
windows/deployment/do/mcc-isp-configure-routing.md
View File

@ -15,27 +15,27 @@ ms.topic: article
# Configure client routing for cache node
All configuration routing takes place within the Azure Portal. There are two main methods to route clients to your cache node:
All configuration routing takes place within the Azure portal. There are two main methods to route clients to your cache node:
- **Manual Routing**: Providing the CIDR blocks that represent the client IP address space, which should be routed to the MCC node.
- **BGP Routing**: BGP neighborship sessions from the cache node to the router or route server will be initiated automatically based on the portal configuration.
- **Manual routing**: Providing the CIDR blocks that represent the client IP address space, which should be routed to the MCC node.
- **BGP routing**: BGP neighborship sessions from the cache node to the router or route server will be initiated automatically based on the portal configuration.
> [!NOTE]
> Only IPv4 addresses are supported at this time. Entering IPv6 addresses will result in an error.
## Manual Routing
## Manual routing
1. To configure client routing using manually entered CIDR blocks, navigate to **Settings** >> **Routing Information**.
1. Select **Manual prefix entry** as the Prefix Source.
1. Paste in the CIDR blocks, with each IP range separated by a comma.
1. Lastly, press Save to save your changes.
## BGP Routing
## BGP routing
1. To configure client routing using BGP, navigate to **Settings** >> **Routing Information**.
1. Select **BGP** as the Prefix source.
1. Click on **Add neighbor** to add the ASN(s) and IP address(es) of your BGP neighbors.
1. If you'd like to download your BGP routes, click on the **Download Routes** button.
1. Select on **Add neighbor** to add the ASN(s) and IP address(es) of your BGP neighbors.
1. If you'd like to download your BGP routes, select on the **Download Routes** button.
1. Lastly, press Save to save your changes.
1. From your end, establish a neighborship from your router to MCC's host machine. Use the IP address of the host machine that's running the MCC container.

2
windows/deployment/do/mcc-isp-device-provisioning.md
View File

@ -16,7 +16,7 @@ ms.topic: article
# Device provisioning
Once the user executes the provisioning script, resources are created behind the scenes resulting in the successful cache node installation.
The device provisioning script takes the input of different IDs outlined below to create an IoT Central and an IoT Edge device. even though Microsoft Connected Cache scenario is not related to IoT, IoT Central and IoT Edge are installed for management and communication operation purposes.
The device provisioning script takes the input of different IDs outlined below to create an IoT Central and an IoT Edge device. even though Microsoft Connected Cache scenario isn't related to IoT, IoT Central and IoT Edge are installed for management and communication operation purposes.
### Components installed during provisioning

25
windows/deployment/do/mcc-isp-monitor.md
View File

@ -16,20 +16,11 @@ ms.topic: article
# 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.
### 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.
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 are able to build your custom metrics using the following available metrics:
Within Azure portal, you're able to build your custom charts and graphs using the following available metrics:
| Metric name | Description |
| -- | ---- |
@ -41,4 +32,14 @@ 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.
To learn more about how to build your custom charts and graphs, visit [Azure Monitor](https://docs.microsoft.com/en-us/azure/azure-monitor/essentials/data-platform-metrics) 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-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'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.

14
windows/deployment/do/mcc-isp-overview.md
View File

@ -1,14 +0,0 @@
---
title: Microsoft Connected Cache Overview
manager: dougeby
description: An overview for Microsoft Connected Cache for ISPs
keywords: updates, downloads, network, bandwidth
ms.prod: w10
ms.mktglfcycl: deploy
audience: itpro
author: amyzhou
ms.localizationpriority: medium
ms.author: amyzhou
ms.collection: M365-modern-desktop
ms.topic: article
---

2
windows/deployment/do/mcc-isp-uninstall.md
View File

@ -24,7 +24,7 @@ There are two main steps required to uninstall your cache node:
## Remove your cache node from Azure portal
Within Azure portal, navigate to **Cache Nodes**, then select the cache node you wish to delete. Once selected, click **Delete** on the top bar to remove this cache node from your account.
Within Azure portal, 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 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.

2
windows/deployment/do/mcc-isp-update.md
View File

@ -15,7 +15,7 @@ ms.topic: article
# 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.
Microsoft will release updates for Microsoft Connected Cache periodically to improve performance, functionality, and security. Updates won't 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, navigate to the **Cache nodes** tab to view the versions in the list view.

4
windows/deployment/do/mcc-isp-verify-cache-node.md
View File

@ -29,7 +29,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 will see a terminal output similar to the following:
If successful, you'll see a terminal output similar to the following:
```bash
HTTP request sent, awaiting response... 200 OK
@ -39,7 +39,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 MCC.":::
:::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:

10
windows/deployment/do/mcc-traffic-estimation.md
View File

@ -15,17 +15,17 @@ ms.topic: article
# Traffic estimation
During the sign up process, Microsoft will provide you with a traffic estimation based on your ASN(s). We make estimations based on our predictions on historical data about Microsoft content download volume. We will use these estimations to recommend hardware or VM configurations. You can view these recommendations within the Azure portal.
During the sign-up process, Microsoft will provide you with a traffic estimation based on your ASN(s). We make estimations based on our predictions on historical data about Microsoft content download volume. We'll use these estimations to recommend hardware or VM configurations. You can view these recommendations within the Azure portal.
Note that we make these estimations based on the Microsoft content types that Microsoft Connected Cache serves. To learn more about the types of content that are supported, see [Delivery Optimization and Microsoft Connected Cache content endpoints]().
We make these estimations based on the Microsoft content types that Microsoft Connected Cache serves. To learn more about the types of content that are supported, see [Delivery Optimization and Microsoft Connected Cache content endpoints]().
## Cache performance
To make sure you are maximizing the performance of your cache node, please note the following:
To make sure you're maximizing the performance of your cache node, note the following:
### OS requirements
The MCC module is optimized for Ubuntu 20.04 LTS. Install Ubuntu 20.04 LTS on a physical server or VM of your choice.
The Microsoft Connected Cache module is optimized for Ubuntu 20.04 LTS. Install Ubuntu 20.04 LTS on a physical server or VM of your choice.
### NIC requirements
@ -50,4 +50,4 @@ There are many hardware configurations that suit Microsoft Connected Cache. As a
### Virtual Machines
If you are using a virtual machine as your server, please refer to [VM performance](mcc-isp-vm-performance.md) for tips on how to improve your VM performance.
If you're using a virtual machine as your server, refer to [VM performance](mcc-isp-vm-performance.md) for tips on how to improve your VM performance.

8
windows/deployment/do/mcc-version-history.md
View File

@ -12,3 +12,11 @@ ms.author: amyzhou
ms.collection: M365-modern-desktop
ms.topic: article
---
# Current Version
### Version 1332
Released September 15, 2022
Version notes:
- Fix for caching TLU (Time Limited URLs) – There was a problem and some files that were accessed via TLUs were returning 403s
- Core Caching Engine optimizations that will dynamically configure caching settings based on the available system resources.

2
windows/deployment/do/waas-microsoft-connected-cache.md
View File

@ -55,7 +55,7 @@ See the following diagram.
For more information about MCC, see the following articles:
- [Microsoft Connected Cache for Enterprise and Education](mcc-enterprise.md)
- [Microsoft Connected Cache for ISPs](mcc-isp.md)
- [Microsoft Connected Cache for ISPs](mcc-isp-device-provisioning.md)
## Also see