windows-itpro-docs/windows/deployment/do/mcc-isp-create-provision-deploy.md

title, manager, description, keywords, ms.prod, ms.mktglfcycl, audience, author, ms.localizationpriority, ms.author, ms.collection, ms.topic

title	manager	description	keywords	ms.prod	ms.mktglfcycl	audience	author	ms.localizationpriority	ms.author	ms.collection	ms.topic
Create, provision, and deploy the cache node in Azure portal	aaroncz	Instructions for creating, provisioning, and deploying Microsoft Connected Cache for ISP on Azure portal	updates, downloads, network, bandwidth	w10	deploy	itpro	nidos	medium	nidos	M365-modern-desktop	article

Create, provision, and deploy the cache node in Azure portal

Applies to

• Windows 10
• Windows 11

This article outlines how to create, provision, and deploy your Microsoft Connected Cache nodes. The creation and provisioning of your cache node takes place in Azure portal. The deployment of your cache node will require downloading an installer script that will be run on your cache server.

Important

Before you can create your Microsoft Connected Cache, you will need to complete the sign up process. You cannot proceed without signing up for our service.

Create cache node

1. Open Azure portal and navigate to the Microsoft Connected Cache resource.

2. Navigate to Settings > Cache nodes and select Create Cache Node.

   :::image type="content" source="images/mcc-isp-create-cache-node.png" alt-text="Screenshot of the cache node page in the Azure portal":::

3. Provide a name for your cache node and select Create to create your cache node.

   :::image type="content" source="images/mcc-isp-cache-node-name.png" alt-text="Screenshot of the create cache node page in the Azure portal, with the cache node name input field.":::

Provision cache node

During the provisioning of your cache node, there are many fields for you to configure your cache node. To learn more about the definitions of each field, review the Configuration fields at the bottom of this 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. Navigate to Settings > Cache nodes. Select the cache node you wish to provision.

   :::image type="content" source="images/mcc-isp-provision-cache-node-numbered.png" alt-text="Screenshot of the Azure portal depicting the cache node configuration page of a cache node. This screenshot shows all of the fields you can choose to configure the cache node.":::

2. Enter the max allowable egress that your hardware can support.

3. Under Cache storage, specify the location of the cache drives to store content along with the size of the cache drives in Gigabytes.
   Note: Up to nine cache drives are supported.

4. Under Routing information, select the routing method you would like to use. For more information, see Client routing.

   • If you choose Manual routing, enter your address range/CIDR blocks.
   • If you choose BGP routing, enter the ASN and IP addresses of the neighborship.

   Note

   Prefix count and IP Space will stop displaying 0 when BGP is successfully established.

Deploy cache node

Once the user executes the deployment script, resources are created behind the scenes resulting in the successful cache node installation. The 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 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.
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.

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.

:::image type="content" source="images/mcc-isp-deploy-cache-node-numbered.png" alt-text="Screenshot of the server provisioning tab within cache node configuration in Azure portal.":::

1. After completing cache node provisioning, navigate to the Server provisioning tab. Select Download provisioning package to download the installation package to your server.

2. Open a terminal window in the directory where you would like to deploy your cache node and run the following command to change the access permission to the Bash script:

   sudo chmod +x installmcc.sh
   

3. Run the deployment script that is shown for your cache node in Azure portal by copying and pasting the script in your terminal. The script may take a few minutes to run. If there were no errors, you have set up your cache node successfully. To verify the server is set up correctly, follow the verification steps.

General configuration fields

Field Name	Expected Value	Description
Cache node name	Alphanumeric string that contains no spaces	The name of the cache node. You may choose names based on location like Seattle-1. This name must be unique and can't be changed later.
Server IP address	IPv4 address	IP address of your MCC server. This address is used to route end-user devices in your network to the server for Microsoft content downloads. The IP address must be publicly accessible.
Max allowable egress (Mbps)	Integer in Mbps	The maximum egress (Mbps) of your MCC based on the specifications of your hardware. For example, 10,000 Mbps.
Enable cache node	Enable or Disable	You can choose to enable or disable a cache node at any time.

Storage fields

Field Name	Expected Value	Description
Cache drive	File path string	Up to 9 drives can be configured for each cache node to configure cache storage. Enter the file path to each drive. For example: /dev/folder/
Cache drive size in gigabytes	Integer in GB	Set the size of each drive configured for the cache node.

Client routing fields

Field Name	Expected Value	Description
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.