mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-18 20:03:40 +00:00
deleted files that are no longer needed
This commit is contained in:
Amy Zhou
@ -1,45 +0,0 @@
|
|||||||
---
|
|
||||||
title: Update or uninstall Microsoft Connected Cache for Enterprise and Education
|
|
||||||
manager: dougeby
|
|
||||||
description: Details on updating or uninstalling Microsoft Connected Cache (MCC) for Enterprise and Education.
|
|
||||||
ms.prod: w10
|
|
||||||
author: amymzhou
|
|
||||||
ms.localizationpriority: medium
|
|
||||||
ms.author: amyzhou
|
|
||||||
ms.collection: M365-modern-desktop
|
|
||||||
ms.topic: article
|
|
||||||
---
|
|
||||||
# Update or uninstall Microsoft Connected Cache for Enterprise and Education
|
|
||||||
|
|
||||||
|
|
||||||
## Update MCC
|
|
||||||
|
|
||||||
Throughout the preview phase, we'll send you security and feature updates for MCC. Follow these steps to perform the update.
|
|
||||||
|
|
||||||
Run the following command with the **arguments** we provided in the email to update your MCC:
|
|
||||||
|
|
||||||
```powershell
|
|
||||||
# .\updatemcc.ps1 version="**\<VERSION\>**" tenantid="**\<TENANTID\>**" customerid="**\<CUSTOMERID\>**" cachenodeid="**\<CACHENODEID\>**" customerkey="**\<CUSTOMERKEY\>**"
|
|
||||||
```
|
|
||||||
For example:
|
|
||||||
```powershell
|
|
||||||
# .\updatemcc.ps1 version="msconnectedcacheprod.azurecr.io/mcc/linux/iot/mcc-ubuntu-iot-amd64:1.2.1.659" tenantid="799a999aa-99a1-99aa-99aa-9a9aa099db99" customerid="99a999aa-99a1-99aa-99aa-9aaa9aaa0saa" cachenodeid=" aa99aaaa-999a-9aas-99aa99daaa99 " customerkey="a99d999a-aaaa-aa99-0999aaaa99a”
|
|
||||||
```
|
|
||||||
|
|
||||||
## Uninstall MCC
|
|
||||||
|
|
||||||
Please contact the MCC Team before uninstalling to let us know if you're facing
|
|
||||||
issues.
|
|
||||||
|
|
||||||
This script will remove the following:
|
|
||||||
|
|
||||||
1. EFLOW + Linux VM
|
|
||||||
1. IoT Edge
|
|
||||||
1. Edge Agent
|
|
||||||
1. Edge Hub
|
|
||||||
1. MCC
|
|
||||||
1. Moby CLI
|
|
||||||
1. Moby Engine
|
|
||||||
|
|
||||||
To delete MCC, go to Control Panel \> Uninstall a program \> Select Azure IoT
|
|
||||||
Edge LTS \> Uninstall
|
|
||||||
@ -1,545 +0,0 @@
|
|||||||
---
|
|
||||||
title: Microsoft Connected Cache for Enterprise and Education (private preview)
|
|
||||||
manager: dougeby
|
|
||||||
description: Details on Microsoft Connected Cache (MCC) for Enterprise and Education.
|
|
||||||
ms.prod: w10
|
|
||||||
author: carmenf
|
|
||||||
ms.localizationpriority: medium
|
|
||||||
ms.author: carmenf
|
|
||||||
ms.collection: M365-modern-desktop
|
|
||||||
ms.topic: article
|
|
||||||
---
|
|
||||||
|
|
||||||
# Microsoft Connected Cache for Enterprise and Education (private preview)
|
|
||||||
|
|
||||||
**Applies to**
|
|
||||||
|
|
||||||
- Windows 10
|
|
||||||
- Windows 11
|
|
||||||
|
|
||||||
## Overview
|
|
||||||
|
|
||||||
> [!IMPORTANT]
|
|
||||||
> Microsoft Connected Cache is currently a private preview feature. During this phase we invite customers to take part in early access for testing purposes. This phase does not include formal support, and should not be used for production workloads. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
|
|
||||||
|
|
||||||
Microsoft Connected Cache (MCC) preview is a software-only caching solution that delivers Microsoft content within Enterprise networks. MCC can be deployed to as many physical servers or VMs as needed, and is managed from a cloud portal. Cache nodes are created in the cloud portal and are configured by applying a client policy using your management tool, such as [Intune](/mem/intune/).
|
|
||||||
|
|
||||||
MCC is a hybrid (a mix of on-premises and cloud resources) SaaS solution built as an Azure IoT Edge module; it's a Docker compatible Linux container that is deployed to your Windows devices. IoT Edge for Linux on Windows (EFLOW) was chosen because it's a secure, reliable container management infrastructure. EFLOW is a Linux virtual machine, based on Microsoft's first party CBL-Mariner operating system. It’s built with the IoT Edge runtime and validated as a tier 1 supported environment for IoT Edge workloads. MCC will be a Linux IoT Edge module running on the Windows Host OS.
|
|
||||||
|
|
||||||
Even though your MCC scenario isn't related to IoT, Azure IoT Edge is used as a more generic Linux container, deployment, and management infrastructure. The Azure IoT Edge runtime sits on your designated MCC device and performs management and communication operations. The runtime performs the following important functions to manage MCC on your edge device:
|
|
||||||
|
|
||||||
1. Installs and updates MCC on your edge device.
|
|
||||||
2. Maintains Azure IoT Edge security standards on your edge device.
|
|
||||||
3. Ensures that MCC is always running.
|
|
||||||
4. Reports MCC health and usage to the cloud for remote monitoring.
|
|
||||||
|
|
||||||
To deploy a functional MCC to your device, you must obtain the necessary keys that will provision the Connected Cache instance to communicate with Delivery Optimization services and enable the device to cache and deliver content. See [figure 1](#fig1) below for a summary of the architecture of MCC, built using IoT Edge.
|
|
||||||
|
|
||||||
For more information about Azure IoT Edge, see [What is Azure IoT Edge](/azure/iot-edge/about-iot-edge).
|
|
||||||
|
|
||||||
## How MCC works
|
|
||||||
|
|
||||||
The following steps describe how MCC is provisioned and used.
|
|
||||||
|
|
||||||
1. The Azure Management Portal is used to create MCC nodes.
|
|
||||||
2. The MCC container is deployed and provisioned to a server using the installer provided in the portal.
|
|
||||||
3. Client policy is configured in your management solution to point to the IP address or FQDN of the cache server.
|
|
||||||
4. Microsoft end-user devices make range requests for content from the MCC node.
|
|
||||||
5. An MCC node pulls content from the CDN, seeds its local cache stored on disk, and delivers content to the client.
|
|
||||||
6. Subsequent requests from end-user devices for content come from the cache.
|
|
||||||
|
|
||||||
If an MCC node is unavailable, the client will pull content from CDN to ensure uninterrupted service for your subscribers.
|
|
||||||
|
|
||||||
<a id="fig1">
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
</a>Figure 1: **MCC processes**. Each number in the diagram corresponds to the steps described above.
|
|
||||||
|
|
||||||
|
|
||||||
## Enterprise requirements for MCC
|
|
||||||
|
|
||||||
1. **Azure subscription**: MCC management portal is hosted within Azure and is used to create the Connected Cache [Azure resource](/azure/cloud-adoption-framework/govern/resource-consistency/resource-access-management) and IoT Hub resource. Both are free services.
|
|
||||||
|
|
||||||
Your Azure subscription ID is first used to provision MCC services, and enable access to the preview. The MCC server requirement for an Azure subscription will cost you nothing. If you do not have an Azure subscription already, you can create an Azure [Pay-As-You-Go](https://azure.microsoft.com/offers/ms-azr-0003p/) account which requires a credit card for verification purposes. For more information, see the [Azure Free Account FAQ](https://azure.microsoft.com/free/free-account-faq/).
|
|
||||||
|
|
||||||
The resources used for the preview and in the future when this product is ready for production will be completely free to you, like other caching solutions.
|
|
||||||
|
|
||||||
2. **Hardware to host MCC**: The recommended configuration will serve approximately 35000 managed devices, downloading a 2GB payload in 24-hour timeframe at a sustained rate of 6.5 Gbps.
|
|
||||||
|
|
||||||
**EFLOW Requires Hyper-V support**
|
|
||||||
- On Windows client, enable the Hyper-V feature
|
|
||||||
- On Windows Server, install the Hyper-V role and create a default network switch
|
|
||||||
|
|
||||||
Disk recommendations:
|
|
||||||
- Using an SSD is recommended as cache read speed of SSD is superior to HDD
|
|
||||||
|
|
||||||
NIC requirements:
|
|
||||||
- Multiple NICs on a single MCC instance aren't supported.
|
|
||||||
- 1 Gbps NIC is the minimum speed recommended but any NIC is supported.
|
|
||||||
- For best performance, NIC and BIOS should support SR-IOV
|
|
||||||
|
|
||||||
VM networking:
|
|
||||||
- An external virtual switch to support outbound and inbound network communication (created during the installation process)
|
|
||||||
|
|
||||||
### Sizing recommendations
|
|
||||||
|
|
||||||
| Component | Branch Office / Small Enterprise | Large Enterprise |
|
|
||||||
| -- | --- | --- |
|
|
||||||
| OS| Windows Server 2019*/2022 <br> Windows 10*/11 (Pro or Enterprise) with Hyper-V Support <br><br>* Windows 10 and Windows Server 2019 build 17763 or later | Same |
|
|
||||||
|NIC | 1 Gbps | 5 Gbps |
|
|
||||||
|Disk | SSD <br>1 drive <br>50GB each |SSD <br>1 drive <br>200GB each |
|
|
||||||
|Memory | 4GB | 8GB |
|
|
||||||
|Cores | 4 | 8 |
|
|
||||||
|
|
||||||
## Steps to deploy MCC
|
|
||||||
|
|
||||||
To deploy MCC to your server:
|
|
||||||
|
|
||||||
1. [Provide Microsoft with the Azure subscription ID](#provide-microsoft-with-the-azure-subscription-id)
|
|
||||||
2. [Create the MCC Resource in Azure](#create-the-mcc-resource-in-azure)
|
|
||||||
3. [Create an MCC Node](#create-an-mcc-node-in-azure)
|
|
||||||
4. [Edit Cache Node Information](#edit-cache-node-information)
|
|
||||||
5. [Install MCC on a physical server or VM](#install-mcc-on-windows)
|
|
||||||
6. [Verify proper functioning MCC server](#verify-proper-functioning-mcc-server)
|
|
||||||
7. [Review common Issues](#common-issues) if needed.
|
|
||||||
|
|
||||||
For questions regarding these instructions contact [msconnectedcache@microsoft.com](mailto:msconnectedcache@microsoft.com)
|
|
||||||
|
|
||||||
### Provide Microsoft with the Azure Subscription ID
|
|
||||||
|
|
||||||
As part of the MCC preview onboarding process an Azure subscription ID must be provided to Microsoft.
|
|
||||||
|
|
||||||
> [!IMPORTANT]
|
|
||||||
> [Take this survey](https://aka.ms/MSConnectedCacheSignup) and provide your Azure subscription ID and contact information to be added to the allowlist for this preview. You will not be able to proceed if you skip this step.
|
|
||||||
|
|
||||||
For information about creating or locating your subscription ID, see [Steps to obtain an Azure Subscription ID](#steps-to-obtain-an-azure-subscription-id).
|
|
||||||
|
|
||||||
### Create the MCC resource in Azure
|
|
||||||
|
|
||||||
The MCC Azure management portal is used to create and manage MCC nodes. An Azure Subscription ID is used to grant access to the preview and to create the MCC resource in Azure and Cache nodes.
|
|
||||||
|
|
||||||
Once you take the survey above and the MCC team adds your subscription ID to the allowlist, you will be given a link to the Azure portal where you can create the resource described below.
|
|
||||||
|
|
||||||
1. In the Azure portal home page, choose **Create a resource**:
|
|
||||||
:::image type="content" source="./images/ent-mcc-create-azure-resource.png" alt-text="Screenshot of the Azure portal with the create a resource option outlined in red.":::
|
|
||||||
|
|
||||||
2. Type **Microsoft Connected Cache** into the search box, and hit **Enter** to show search results.
|
|
||||||
|
|
||||||
> [!NOTE]
|
|
||||||
> You'll not see Microsoft Connected Cache in the drop-down list. You need to type it and press enter to see the result.
|
|
||||||
|
|
||||||
3. Select **Microsoft Connected Cache Enterprise** and choose **Create** on the next screen to start the process of creating the MCC resource.
|
|
||||||
|
|
||||||
:::image type="content" source="./images/ent-mcc-azure-search-result.png" alt-text="Screenshot of the Azure portal search results for Microsoft Connected Cache.":::
|
|
||||||
:::image type="content" source="./images/ent-mcc-azure-marketplace.png" alt-text="Screenshot of Microsoft Connected Cache within the Azure Marketplace.":::
|
|
||||||
|
|
||||||
4. Fill in the required fields to create the MCC resource.
|
|
||||||
|
|
||||||
- Choose the subscription that you provided to Microsoft.
|
|
||||||
- Azure resource groups are logical groups of resources. Create a new resource group and choose a name for your resource group.
|
|
||||||
- Choose **(US) West US** for the location of the resource. This choice will not impact MCC if the physical location isn't in the West US, it's just a limitation of the preview.
|
|
||||||
|
|
||||||
> [!NOTE]
|
|
||||||
> Your MCC resource will not be created properly if you do not select **(US) West US**
|
|
||||||
|
|
||||||
- Choose a name for the MCC resource.
|
|
||||||
|
|
||||||
> [!NOTE]
|
|
||||||
> Your MCC resource must not contain the word **Microsoft** in it.
|
|
||||||
|
|
||||||
:::image type="content" source="./images/ent-mcc-azure-create-connected-cache.png" alt-text="Screenshot of the Create a Connected Cache page within the Azure Marketplace.":::
|
|
||||||
|
|
||||||
5. Once all the information has been entered, click the **Review + Create** button. Once validation is complete, click the **Create** button to start the
|
|
||||||
resource creation.
|
|
||||||
|
|
||||||
:::image type="content" source="./images/ent-mcc-azure-cache-created.png" alt-text="Screenshot of the completed cache deployment within the Azure.":::
|
|
||||||
|
|
||||||
#### Error: Validation failed
|
|
||||||
|
|
||||||
- If you get a Validation failed error message on your portal, it's likely because you selected the **Location** as **US West 2** or some other location that isn't **(US) West US**.
|
|
||||||
- To resolve this error, go to the previous step and choose **(US) West US**.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### Create an MCC node in Azure
|
|
||||||
|
|
||||||
Creating an MCC node is a multi-step process and the first step is to access the MCC private preview management portal.
|
|
||||||
|
|
||||||
1. After the successful resource creation click on the **Go to resource**.
|
|
||||||
2. Under **Cache Node Management** section on the leftmost panel, click on **Cache Nodes**.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
3. On the **Cache Nodes** blade, click on the **Create Cache Node** button.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
4. Clicking the **Create Cache Node** button will open the **Create Cache Node** page; **Cache Node Name** is the only field required for cache node creation.
|
|
||||||
|
|
||||||
| **Field Name** | **Expected Value** | **Description** |
|
|
||||||
|---------------------|--------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|
|
|
||||||
| **Cache Node Name** | Alphanumeric name that includes no spaces. | The name of the cache node. You may choose names based on location like Seattle-1. This name must be unique and cannot be changed later. |
|
|
||||||
|
|
||||||
5. Enter the information for the **Cache Node** and click the **Create** button.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
If there are errors, the form will provide guidance on how to correct the errors.
|
|
||||||
|
|
||||||
Once the MCC node has been created, the installer instructions will be exposed. More details on the installer instructions will be addressed later in this article, in the [Install Connected Cache](#install-mcc-on-windows) section.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
#### Edit cache node information
|
|
||||||
|
|
||||||
Cache nodes can be deleted here by clicking the check box to the left of a **Cache Node Name** and then clicking the delete toolbar item. Be aware that if a cache node is deleted, there is no way to recover the cache node or any of the information related to the cache node.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### Install MCC on Windows
|
|
||||||
|
|
||||||
Installing MCC on your Windows device is a simple process. A PowerShell script performs the following tasks:
|
|
||||||
|
|
||||||
- Installs the Azure CLI
|
|
||||||
- Downloads, installs, and deploys EFLOW
|
|
||||||
- Enables Microsoft Update so EFLOW can stay up to date
|
|
||||||
- Creates a virtual machine
|
|
||||||
- Enables the firewall and opens ports 80 and 22 for inbound and outbound traffic. Port 80 is used by MCC, and port 22 is used for SSH communications.
|
|
||||||
- Configures Connected Cache tuning settings.
|
|
||||||
- Creates the necessary *FREE* Azure resource - IoT Hub/IoT Edge.
|
|
||||||
- Deploys the MCC container to server.
|
|
||||||
|
|
||||||
#### Run the installer
|
|
||||||
|
|
||||||
1. Download and unzip mccinstaller.zip from the create cache node page or cache node configuration page which contains the necessary installation files.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Files contained in the mccinstaller.zip file:
|
|
||||||
|
|
||||||
- **installmcc.ps1**: Main installer file.
|
|
||||||
- **installEflow.ps1**: Installs the necessary prerequisites such as the Linux VM, IoT Edge runtime, and Docker, and makes necessary host OS settings to optimize caching performance.
|
|
||||||
- **resourceDeploymentForConnectedCache.ps1**: Creates Azure cloud resources required to support MCC control plane.
|
|
||||||
- **mccdeployment.json**: Deployment manifest used by IoT Edge to deploy the MCC container and configure settings on the container, such as cache drive location sizes.
|
|
||||||
- **updatemcc.ps1**: The update script used to upgrade MCC to a particular version.
|
|
||||||
- **mccupdate.json**: Used as part of the update script
|
|
||||||
|
|
||||||
1. Open Windows PowerShell as administrator and navigate to the location of these files.
|
|
||||||
|
|
||||||
> [!NOTE]
|
|
||||||
> Ensure that Hyper-V is enabled on your device.
|
|
||||||
> Do not use PowerShell ISE, PowerShell 6.x, or PowerShell 7.x. Only Windows PowerShell version 5.x is supported.
|
|
||||||
|
|
||||||
**Windows 10:** [Enable Hyper-V on Windows 10](/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v)
|
|
||||||
|
|
||||||
**Windows Server:** [Install the Hyper-V role on Windows Server](/windows-server/virtualization/hyper-v/get-started/install-the-hyper-v-role-on-windows-server)
|
|
||||||
|
|
||||||
#### If you're installing MCC on a local virtual machine:
|
|
||||||
|
|
||||||
1. Enable Nested Virtualization
|
|
||||||
|
|
||||||
```powershell
|
|
||||||
Set -VMProcessor -VMName "VM name" -ExposeVirtualizationExtensions $true
|
|
||||||
```
|
|
||||||
2. Enable Mac Spoofing
|
|
||||||
```powershell
|
|
||||||
Get-VMNetworkAdapter -VMName "VM name" | Set-VMNetworkAdapter -MacAddressSpoofing On
|
|
||||||
```
|
|
||||||
**Virtual machine should be in the OFF state while enabling Nested Virtualization and Mac Spoofing**
|
|
||||||
|
|
||||||
3. Set the execution policy
|
|
||||||
|
|
||||||
```powershell
|
|
||||||
Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope Process
|
|
||||||
```
|
|
||||||
> [!NOTE]
|
|
||||||
> After setting the execution policy, you'll see a warning asking if you wish to change the execution policy. Choose **[A] Yes to All**.
|
|
||||||
|
|
||||||
4. Copy the command from the portal and run it in Windows PowerShell
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
> [!NOTE]
|
|
||||||
> After running the command, and multiple times throughout the installation process, you'll receive the following notice. **Please select [R] Run once to proceed**.
|
|
||||||
> <br>
|
|
||||||
> <br>Security warning
|
|
||||||
> <br>Run only scripts that you trust. While scripts from the internet can be useful, this script can potentially harm your computer. If you trust this script, use the Unblock-File cmdlet to allow the script to run without this warning message. Do you want to run C:\\Users\\mccinstaller\\Eflow\\installmcc.ps1?
|
|
||||||
><br>
|
|
||||||
> <br>[D] Do not run **[R] Run once** [S] Suspend [?] Help (default is "D"):
|
|
||||||
|
|
||||||
3. Choose whether you would like to create a new virtual switch or select an existing one. Name your switch and select the Net Adapter to use for the switch. A computer restart will be required if you're creating a new switch.
|
|
||||||
|
|
||||||
> [!NOTE]
|
|
||||||
> Restarting your computer after creating a switch is recommended. You'll notice network delays during installation if the computer has not been restarted.
|
|
||||||
|
|
||||||
If you restarted your computer after creating a switch, start from Step 2 above and skip step 5.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
4. Re-run the script after the restart. This time, choose **No** when asked to create a new switch. Enter the number corresponding to the switch you previously created.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
5. Decide whether you would like to use dynamic or static address for the Eflow VM
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
> [!NOTE]
|
|
||||||
> Choosing a dynamic IP address might assign a different IP address when the MCC restarts.
|
|
||||||
> <br>A static IP address is recommended so you do not have to change this value in your management solution when MCC restarts.
|
|
||||||
|
|
||||||
6. Choose where you would like to download, install, and store the virtual hard disk for EFLOW. You'll also be asked how much memory, storage, and cores you would like to allocate for the VM. In this example, we chose the default values for all prompts.
|
|
||||||
|
|
||||||
7. Follow the Azure Device Login link and sign into the Azure portal.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
8. If this is your first MCC deployment, please select **n** so that a new IoT Hub can be created. If you have already configured MCC before, choose **y** so that your MCCs are grouped in the same IoT Hub.
|
|
||||||
|
|
||||||
1. You'll be shown a list of existing IoT Hubs in your Azure Subscription; Enter the number corresponding to the IoT Hub to select it. **You'll likely have only 1 IoT Hub in your subscription, in which case you want to enter “1”**
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
9. Your MCC deployment is now complete.
|
|
||||||
|
|
||||||
1. If you do not see any errors, please continue to the next section to validate your MCC deployment.
|
|
||||||
2. After validating your MCC is properly functional, please review your management solution documentation, such as [Intune](/mem/intune/configuration/delivery-optimization-windows), to set the cache host policy to the IP address of your MCC.
|
|
||||||
3. If you had errors during your deployment, see the [Troubleshooting](#troubleshooting) section in this article.
|
|
||||||
|
|
||||||
### Verify proper functioning MCC server
|
|
||||||
|
|
||||||
#### Verify Client Side
|
|
||||||
|
|
||||||
Connect to the EFLOW VM and check if MCC is properly running:
|
|
||||||
|
|
||||||
1. Open PowerShell as an Administrator
|
|
||||||
2. Enter the following commands:
|
|
||||||
|
|
||||||
```powershell
|
|
||||||
Connect-EflowVm
|
|
||||||
sudo -s
|
|
||||||
iotedge list
|
|
||||||
```
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
You should see MCC, edgeAgent, and edgeHub running. If you see edgeAgent or edgeHub but not MCC, please try this command in a few minutes. The MCC container can take a few minutes to deploy
|
|
||||||
|
|
||||||
#### Verify server side
|
|
||||||
|
|
||||||
For a validation of properly functioning MCC, execute the following command in the EFLOW VM or any device in the network. Replace <CacheServerIP\> with the IP address of the cache server.
|
|
||||||
|
|
||||||
```powershell
|
|
||||||
wget [http://<CacheServerIP>/mscomtest/wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com]
|
|
||||||
```
|
|
||||||
|
|
||||||
A successful test result will look like this:
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
OR
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Similarly, enter this URL from a browser in the network:
|
|
||||||
|
|
||||||
[http://YourCacheServerIP/mscomtest/wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com]()
|
|
||||||
|
|
||||||
If the test fails, see the common issues section for more information.
|
|
||||||
|
|
||||||
### Intune (or other management software) configuration for MCC
|
|
||||||
|
|
||||||
For an Intune deployment, create a Configuration Profile and include the Cache Host eFlow IP Address or FQDN:
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### Common Issues
|
|
||||||
|
|
||||||
#### PowerShell issues
|
|
||||||
|
|
||||||
If you're seeing errors similar to this: “The term ‘Get-Something’ isn't recognized as the name of a cmdlet, function, script file, or operable program.”
|
|
||||||
|
|
||||||
1. Ensure you're running Windows PowerShell version 5.x.
|
|
||||||
|
|
||||||
2. Run \$PSVersionTable and ensure you’re running version 5.x and *not version 6 or 7*.
|
|
||||||
|
|
||||||
3. Ensure you have Hyper-V enabled:
|
|
||||||
|
|
||||||
**Windows 10:** [Enable Hyper-V on Windows 10](/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v)
|
|
||||||
|
|
||||||
**Windows Server:** [Install the Hyper-V role on Windows Server](/windows-server/virtualization/hyper-v/get-started/install-the-hyper-v-role-on-windows-server)
|
|
||||||
|
|
||||||
#### Verify Running MCC Container
|
|
||||||
|
|
||||||
Connect to the Connected Cache server and check the list of running IoT Edge modules using the following commands:
|
|
||||||
|
|
||||||
```bash
|
|
||||||
Connect-EflowVm
|
|
||||||
sudo iotedge list
|
|
||||||
```
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
If edgeAgent and edgeHub containers are listed, but not “MCC”, you may view the status of the IoT Edge security manager using the command:
|
|
||||||
|
|
||||||
```bash
|
|
||||||
sudo journalctl -u iotedge -f
|
|
||||||
```
|
|
||||||
|
|
||||||
For example, this command will provide the current status of the starting, stopping of a container, or the container pull and start as is shown in the sample below:
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Use this command to check the IoT Edge Journal
|
|
||||||
|
|
||||||
```bash
|
|
||||||
sudo journalctl -u iotedge –f
|
|
||||||
```
|
|
||||||
|
|
||||||
Please note: You should consult the IoT Edge troubleshooting guide ([Common issues and resolutions for Azure IoT Edge](/azure/iot-edge/troubleshoot)) for any issues you may encounter configuring IoT Edge, but we have listed a few issues below that we hit during our internal validation.
|
|
||||||
|
|
||||||
## Diagnostics Script
|
|
||||||
|
|
||||||
If you're having issues with your MCC, we included a diagnostics script which will collect all your logs and zip them into a single file. You can then send us these logs via email for the MCC team to debug.
|
|
||||||
|
|
||||||
To run this script:
|
|
||||||
|
|
||||||
1. Navigate to the following folder in the MCC installation files:
|
|
||||||
|
|
||||||
mccinstaller > Eflow > Diagnostics
|
|
||||||
|
|
||||||
1. Run the following commands:
|
|
||||||
|
|
||||||
```powershell
|
|
||||||
Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope Process
|
|
||||||
.\collectMccDiagnostics.ps1
|
|
||||||
```
|
|
||||||
|
|
||||||
1. The script stores all the debug files into a folder and then creates a tar file. After the script is finished running, it will output the path of the tar file which you can share with us. The location should be **\<currentpath\>**\mccdiagnostics\support_bundle_\$timestamp.tar.gz
|
|
||||||
|
|
||||||
1. [Email the MCC team](mailto:mccforenterprise@microsoft.com?subject=Debugging%20Help%20Needed%20for%20MCC%20for%20Enterprise) and attach this file asking for debugging support. Screenshots of the error along with any other warnings you saw will be helpful during out debugging process.
|
|
||||||
|
|
||||||
## Update MCC
|
|
||||||
|
|
||||||
Throughout the private preview phase, we will send you security and feature updates for MCC. Please follow these steps to perform the update.
|
|
||||||
|
|
||||||
Run the following command with the **arguments** we provided in the email to update your MCC:
|
|
||||||
|
|
||||||
```powershell
|
|
||||||
# .\updatemcc.ps1 version="**\<VERSION\>**" tenantid="**\<TENANTID\>**" customerid="**\<CUSTOMERID\>**" cachenodeid="**\<CACHENODEID\>**" customerkey="**\<CUSTOMERKEY\>**"
|
|
||||||
```
|
|
||||||
For example:
|
|
||||||
```powershell
|
|
||||||
# .\updatemcc.ps1 version="msconnectedcacheprod.azurecr.io/mcc/linux/iot/mcc-ubuntu-iot-amd64:1.2.1.659" tenantid="799a999aa-99a1-99aa-99aa-9a9aa099db99" customerid="99a999aa-99a1-99aa-99aa-9aaa9aaa0saa" cachenodeid=" aa99aaaa-999a-9aas-99aa99daaa99 " customerkey="a99d999a-aaaa-aa99-0999aaaa99a”
|
|
||||||
```
|
|
||||||
|
|
||||||
## Uninstall MCC
|
|
||||||
|
|
||||||
Please contact the MCC Team before uninstalling to let us know if you're facing
|
|
||||||
issues.
|
|
||||||
|
|
||||||
This script will remove the following:
|
|
||||||
|
|
||||||
1. EFLOW + Linux VM
|
|
||||||
2. IoT Edge
|
|
||||||
3. Edge Agent
|
|
||||||
4. Edge Hub
|
|
||||||
5. MCC
|
|
||||||
6. Moby CLI
|
|
||||||
7. Moby Engine
|
|
||||||
|
|
||||||
To delete MCC, go to Control Panel \> Uninstall a program \> Select Azure IoT
|
|
||||||
Edge LTS \> Uninstall
|
|
||||||
|
|
||||||
## Appendix
|
|
||||||
|
|
||||||
### Steps to obtain an Azure Subscription ID
|
|
||||||
|
|
||||||
1. Sign in to https://portal.azure.com/ and navigate to the Azure services section.
|
|
||||||
2. Click on **Subscriptions**. If you do not see **Subscriptions**, click on the **More Services** arrow and search for **Subscriptions**.
|
|
||||||
3. If you already have an Azure Subscription, skip to step 5. If you do not have an Azure Subscription, select **+ Add** on the top left.
|
|
||||||
4. Select the **Pay-As-You-Go** subscription. You'll be asked to enter credit card information, but you'll not be charged for using the MCC service.
|
|
||||||
5. On the **Subscriptions** blade, you'll find details about your current subscription. Click on the subscription name.
|
|
||||||
6. After you select the subscription name, you'll find the subscription ID in the **Overview** tab. Click on the **Copy to clipboard** icon next to your Subscription ID to copy the value.
|
|
||||||
|
|
||||||
### Troubleshooting
|
|
||||||
|
|
||||||
If you’re not able to sign up for a Microsoft Azure subscription with the error: **Account belongs to a directory that cannot be associated with an Azure subscription. Please sign in with a different account.** See [Can't sign up for a Microsoft Azure subscription](/troubleshoot/azure/general/cannot-sign-up-subscription).
|
|
||||||
|
|
||||||
Also see [Troubleshoot issues when you sign up for a new account in the Azure portal](/azure/cost-management-billing/manage/troubleshoot-azure-sign-up).
|
|
||||||
|
|
||||||
### IoT Edge runtime
|
|
||||||
|
|
||||||
The Azure IoT Edge runtime enables custom and cloud logic on IoT Edge devices.
|
|
||||||
The runtime sits on the IoT Edge device, and performs management and
|
|
||||||
communication operations. The runtime performs several functions:
|
|
||||||
|
|
||||||
- Installs and update workloads (Docker containers) on the device.
|
|
||||||
- Maintains Azure IoT Edge security standards on the device.
|
|
||||||
- Ensures that IoT Edge modules (Docker containers) are always running.
|
|
||||||
- Reports module (Docker containers) health to the cloud for remote monitoring.
|
|
||||||
- Manages communication between an IoT Edge device and the cloud.
|
|
||||||
|
|
||||||
For more information on Azure IoT Edge, please see the [Azure IoT Edge documentation](/azure/iot-edge/about-iot-edge).
|
|
||||||
|
|
||||||
### EFLOW
|
|
||||||
|
|
||||||
- [What is Azure IoT Edge for Linux on Windows](/azure/iot-edge/iot-edge-for-linux-on-windows)
|
|
||||||
- [Install Azure IoT Edge for Linux on Windows](/azure/iot-edge/how-to-provision-single-device-linux-on-windows-symmetric#install-iot-edge)
|
|
||||||
- [PowerShell functions for Azure IoT Edge for Linux on Windows](/azure/iot-edge/reference-iot-edge-for-linux-on-windows-functions)
|
|
||||||
- EFLOW FAQ and Support: [Support · Azure/iotedge-eflow Wiki (github.com)](https://github.com/Azure/iotedge-eflow/wiki/Support#how-can-i-apply-updates-to-eflow)
|
|
||||||
- [Now ready for Production: Linux IoT Edge Modules on Windows - YouTube](https://www.youtube.com/watch?v=pgqVCg6cxVU&ab_channel=MicrosoftIoTDevelopers)
|
|
||||||
|
|
||||||
### Routing local Windows Clients to an MCC
|
|
||||||
|
|
||||||
#### Get the IP address of your MCC using ifconfig
|
|
||||||
|
|
||||||
There are multiple methods that can be used to apply a policy to PCs that should participate in downloading from the MCC.
|
|
||||||
|
|
||||||
##### Registry Key
|
|
||||||
|
|
||||||
You can either set your MCC IP address or FQDN using:
|
|
||||||
|
|
||||||
1. Registry Key (version 1709 and later):
|
|
||||||
`HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization`
|
|
||||||
</br>
|
|
||||||
"DOCacheHost"=" "
|
|
||||||
|
|
||||||
From an elevated command prompt:
|
|
||||||
|
|
||||||
```
|
|
||||||
reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization" /v DOCacheHost /t REG_SZ /d "10.137.187.38" /f
|
|
||||||
```
|
|
||||||
|
|
||||||
1. MDM Path (version 1809 and later):
|
|
||||||
|
|
||||||
`.Vendor/MSFT/Policy/Config/DeliveryOptimization/DOCacheHost`
|
|
||||||
|
|
||||||
1. In Windows (release version 1809 and later), you can apply the policy via Group Policy Editor. The policy to apply is **DOCacheHost**. To configure the clients to pull content from the MCC using Group Policy, go to **Computer Configuration** > **Administrative Templates** > **Windows Components** > **Delivery Optimization**. Set the **Cache Server Hostname** to the IP address of your MCC, such as `10.137.187.38`.
|
|
||||||
|
|
||||||
:::image type="content" source="./images/ent-mcc-group-policy-hostname.png" alt-text="Screenshot of the Group Policy editor showing the Cache Server Hostname Group Policy setting.":::
|
|
||||||
|
|
||||||
**Verify Content using the DO Client**
|
|
||||||
|
|
||||||
To verify that the Delivery Optimization client can download content using MCC, you can use the following steps:
|
|
||||||
|
|
||||||
1. Download a game or application from the Microsoft Store.
|
|
||||||
|
|
||||||
:::image type="content" source="./images/ent-mcc-store-example-download.png" alt-text="Screenshot of the Microsoft Store with the game, Angry Birds 2, selected.":::
|
|
||||||
|
|
||||||
|
|
||||||
1. Verify downloads came from MCC by one of two methods:
|
|
||||||
|
|
||||||
- Using the PowerShell Cmdlet Get-DeliveryOptimizationStatus you should see *BytesFromCacheServer*.
|
|
||||||
|
|
||||||
:::image type="content" source="./images/ent-mcc-get-deliveryoptimizationstatus.png" alt-text="Screenshot of the output of Get-DeliveryOptimization | FT from PowerShell.":::
|
|
||||||
|
|
||||||
- Using the Delivery Optimization Activity Monitor
|
|
||||||
|
|
||||||
:::image type="content" source="./images/ent-mcc-delivery-optimization-activity.png" alt-text="Screenshot of the Delivery Optimization Activity Monitor.":::
|
|
||||||
## Also see
|
|
||||||
|
|
||||||
[Microsoft Connected Cache for ISPs](mcc-isp.md)<br>
|
|
||||||
[Introducing Microsoft Connected Cache](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/introducing-microsoft-connected-cache-microsoft-s-cloud-managed/ba-p/963898)
|
|
||||||
@ -1,33 +0,0 @@
|
|||||||
---
|
|
||||||
title: Client routing
|
|
||||||
manager: dougeby
|
|
||||||
description: How client routing works for Microsoft Connected Cache
|
|
||||||
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
|
|
||||||
---
|
|
||||||
|
|
||||||
# Client routing
|
|
||||||
|
|
||||||
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 aren't supported.
|
|
||||||
|
|
||||||
### Manual routing
|
|
||||||
|
|
||||||
You can manually upload a list of your CIDR blocks in Azure portal to enable manual routing of your customers to your cache node.
|
|
||||||
|
|
||||||
### BGP routing
|
|
||||||
|
|
||||||
BGP (Border Gateway Protocol) routing is another method offered for client routing. BGP dynamically retrieves CIDR ranges by exchanging information with routers to understand reachable networks. For an automatic method of routing traffic, you can choose to configure BGP routing in Azure portal.
|
|
||||||
|
|
||||||
@ -1,50 +0,0 @@
|
|||||||
---
|
|
||||||
title: Configure client routing for cache node
|
|
||||||
manager: dougeby
|
|
||||||
description: How to configure client routing for a cache node
|
|
||||||
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
|
|
||||||
---
|
|
||||||
|
|
||||||
# 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:
|
|
||||||
|
|
||||||
- **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
|
|
||||||
|
|
||||||
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
|
|
||||||
|
|
||||||
1. To configure client routing using BGP, navigate to **Settings** >> **Routing Information**.
|
|
||||||
1. Select **BGP** as the Prefix source.
|
|
||||||
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.
|
|
||||||
|
|
||||||
> [!NOTE]
|
|
||||||
> With the BGP configuration, you're essentially setting up an iBGP neighbor in your public ASN. For example, when you initiate the BGP session from the router to the cache node, you would use your own ASN.
|
|
||||||
|
|
||||||
> [!NOTE]
|
|
||||||
> Make sure there aren't any firewall rules blocking this connection.
|
|
||||||
|
|
||||||
To verify that BGP has been configured properly and that Microsoft Connected Cache services are receiving the route advertisements, wait about five minutes before refreshing cache node settings page and view the BGP routes received.
|
|
||||||
|
|
||||||
If after five minutes, you don't see traffic, navigate to [Support and Troubleshooting](mcc-isp-support.md) for more information.
|
|
||||||
@ -1,47 +0,0 @@
|
|||||||
---
|
|
||||||
title: Device provisioning
|
|
||||||
manager: dougeby
|
|
||||||
description: How device provisioning works for Microsoft Connected Cache
|
|
||||||
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
|
|
||||||
---
|
|
||||||
|
|
||||||
# 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 isn't related to IoT, IoT Central and IoT Edge are installed for management and communication operation purposes.
|
|
||||||
|
|
||||||
### Components installed during provisioning
|
|
||||||
|
|
||||||
#### IoT Central
|
|
||||||
|
|
||||||
IoT Central is the main hub that handles all messaging and requests from IoT Edge devices. To learn more about the interaction between IoT Edge and IoT Central, review the [IoT Central](/azure/iot-central/core/concepts-iot-edge) documentation.
|
|
||||||
|
|
||||||
#### IoT Edge
|
|
||||||
|
|
||||||
IoT Edge performs several functions important to manage MCC on your edge device:
|
|
||||||
|
|
||||||
1. Installs and updates MCC on your edge device.
|
|
||||||
1. Maintains Azure IoT Edge security standards on your edge device.
|
|
||||||
1. Ensures that MCC is always running.
|
|
||||||
1. Reports MCC health and usage to the cloud for remote monitoring.
|
|
||||||
|
|
||||||
### Components of the device provisioning script
|
|
||||||
|
|
||||||
There are five IDs that the device provisioning script takes as input in order to successfully provision and install your cache server. The provisioning script will automatically include these keys, with no input necessary from the user.
|
|
||||||
|
|
||||||
| ID | Description |
|
|
||||||
| -- | --- |
|
|
||||||
| Customer ID | The Azure subscription ID that the cache node is created in. |
|
|
||||||
| Cache node ID | The unique alphanumeric ID of the cache node being provisioned. |
|
|
||||||
| Customer Key | |
|
|
||||||
| Cache node name | The name of the cache node. |
|
|
||||||
| Tenant ID | The unique ID associated with the Azure account. |
|
|
||||||
|
|
||||||
@ -1,46 +0,0 @@
|
|||||||
---
|
|
||||||
title: Monitor cache node health and performance
|
|
||||||
manager: dougeby
|
|
||||||
description: Monitoring and metrics for cache node health and performance on Azure portal
|
|
||||||
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
|
|
||||||
---
|
|
||||||
|
|
||||||
# Monitor cache node health and performance
|
|
||||||
|
|
||||||
## Metrics
|
|
||||||
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'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|
|
|
||||||
| **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|
|
|
||||||
|
|
||||||
To learn more about how to build your custom charts and graphs, visit [Azure Monitor](/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-img-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 at a time 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.
|
|
||||||
|
|
||||||
@ -1,70 +0,0 @@
|
|||||||
---
|
|
||||||
title: Provision and deploy Microsoft Connected Cache for ISP
|
|
||||||
manager: dougeby
|
|
||||||
description: Provision and deploy Microsoft Connected Cache for ISP on Azure portal
|
|
||||||
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
|
|
||||||
---
|
|
||||||
|
|
||||||
|
|
||||||
# Create, provision and deploy Microsoft Connected Cache for ISP
|
|
||||||
|
|
||||||
**Applies to**
|
|
||||||
|
|
||||||
- Windows 10
|
|
||||||
- Windows 11
|
|
||||||
|
|
||||||
> [!IMPORTANT]
|
|
||||||
> Before you can create your Microsoft Connected Cache, you will need to complete the [sign up process](mcc-isp-signup.md).
|
|
||||||
|
|
||||||
## Create a cache node
|
|
||||||
|
|
||||||
1. Navigating to **Cache nodes** under **Settings**.
|
|
||||||
1. Select **Create Cache Node**.
|
|
||||||
1. Provide a name for your cache node
|
|
||||||
1. Select **Create** to create your cache node.
|
|
||||||
|
|
||||||
## Provision your cache node
|
|
||||||
|
|
||||||
1. Select the cache node you want to provision and deploy.
|
|
||||||
|
|
||||||
:::image type="content" source="./images/numberedprovmcc.png" alt-text="Screenshot of the Settings tab in the Cache nodes page.":::
|
|
||||||
|
|
||||||
1. Enter the max allowable egress that your hardware can support.
|
|
||||||
|
|
||||||
1. Under Cache storage, specify the location of the cache drives to store content along with the size of the cache drives in Gigabytes.
|
|
||||||
> [!NOTE]
|
|
||||||
> You can add up to nine cache drives.
|
|
||||||
|
|
||||||
1. Under Routing information, select the routing source you would like to use. For more information, see [client routing](mcc-isp-client-routing.md).
|
|
||||||
|
|
||||||
- If you choose **Manual** routing, enter Address range/CIDR blocks and the number of IP space.
|
|
||||||
- If you choose **BGP** routing, enter the ASN and IP addresses of the neighborship.
|
|
||||||
> [!Note]
|
|
||||||
> **Prefix count** and **IP Space** will stop showing 0 when BGP is successfully established.
|
|
||||||
|
|
||||||
## Deploy your cache node
|
|
||||||
|
|
||||||
:::image type="content" source="./images/numbereddeploymcc.png" alt-text="Screenshot of the Azure portal showing the Server provisioning tab.":::
|
|
||||||
|
|
||||||
|
|
||||||
1. Under **Server provisioning**, download the provisioning package to your server.
|
|
||||||
|
|
||||||
Open a terminal window and run the following command to change the access permission to the Bash script.
|
|
||||||
|
|
||||||
```bash
|
|
||||||
sudo chmod +x installmcc.sh
|
|
||||||
```
|
|
||||||
|
|
||||||
1. Run the provisioning script that is shown in the Azure portal for your cache node.
|
|
||||||
|
|
||||||
|
|
||||||
1. If there were no errors, you've set up your cache node. To verify the server is set up correctly, follow the [verification steps](mcc-isp-verify-cache-node.md).
|
|
||||||
|
|
||||||
@ -1,49 +0,0 @@
|
|||||||
---
|
|
||||||
title: Uninstall your cache node
|
|
||||||
manager: dougeby
|
|
||||||
description: How to uninstall a cache node
|
|
||||||
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
|
|
||||||
---
|
|
||||||
|
|
||||||
# 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.
|
|
||||||
|
|
||||||
|
|
||||||
## 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, 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.
|
|
||||||
|
|
||||||
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
|
|
||||||
|
|
||||||
```
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,53 +0,0 @@
|
|||||||
---
|
|
||||||
title: Traffic estimation
|
|
||||||
manager: dougeby
|
|
||||||
description: Details on how traffic estimates are made and how to enhance cache node performance.
|
|
||||||
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
|
|
||||||
---
|
|
||||||
|
|
||||||
# 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'll use these estimations to recommend hardware or VM configurations. You can view these recommendations within the Azure portal.
|
|
||||||
|
|
||||||
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're maximizing the performance of your cache node, note the following:
|
|
||||||
|
|
||||||
### OS requirements
|
|
||||||
|
|
||||||
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
|
|
||||||
|
|
||||||
- Multiple NICs on a single MCC instance are supported using a _link aggregated_ configuration.
|
|
||||||
- 10 Gbps NIC is the minimum speed recommended, but any NIC is supported.
|
|
||||||
|
|
||||||
### Drive performance
|
|
||||||
|
|
||||||
The maximum number of disks supported is 9. When configuring your drives, we recommend SSD drives as cache read speed of SSD is superior to HDD. In addition, using multiple disks is recommended to improve cache performance.
|
|
||||||
|
|
||||||
RAID disk configurations are discouraged as cache performance will be impacted. If using RAID disk configurations, ensure striping.
|
|
||||||
|
|
||||||
### Hardware configuration example
|
|
||||||
|
|
||||||
There are many hardware configurations that suit Microsoft Connected Cache. As an example, below is the hardware configuration of a customer who is able to egress 40 Gbps of traffic.
|
|
||||||
|
|
||||||
**Dell PowerEdge R330**
|
|
||||||
- 2 x Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40 GHz , total 32 core
|
|
||||||
- 48 GB, Micron Technology 18ASF1G72PDZ-2G1A1, Speed: 2133 MT/s
|
|
||||||
- 4 - Transcend SSD230s 1 TB SATA Drives
|
|
||||||
- Intel Corporation Ethernet 10G 2P X520 Adapter (Link Aggregated)
|
|
||||||
|
|
||||||
### Virtual Machines
|
|
||||||
|
|
||||||
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.
|
|
||||||
Reference in New Issue
Block a user