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

more content in bulk manage cli

Browse Source
This commit is contained in:
Nidhi Doshi 2024-09-20 14:26:42 -07:00
parent 0bfa6993dc
commit 5461a583c5
1 changed files with 67 additions and 36 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

103
windows/deployment/do/mcc-ent-manage-cache-using-CLI.md
View File

@ -16,18 +16,27 @@ appliesto:
ms.date: 06/03/2024 ms.date: 06/03/2024
--- ---
This article outlines how to create, configure and provision your Microsoft Connected Cache for Enterprise cache nodes using Azure CLI. # Manage cache nodes using CLI
<br>
This article outlines how to create, configure and provision your Microsoft Connected Cache for Enterprise cache nodes using Azure CLI.
Please ensure that you have: ## Prerequisites:
· How to install the Azure CLI | Microsoft Learn 1. **Install Azure CLI**: How to install the Azure CLI | Microsoft Learn
· Installed the MCC extension. 2. **Install MCC extension**: Install the MCC extension.
### 1. Create a Resource group
The first step is to create a resource group if you don't already have one. The first step is to create a resource group if you don't already have one.
An Azure resource group is a logical container into which Azure resources are deployed and managed.
Create a Resource group
An Azure resource group is a logical container into which Azure resources are deployed and managed.
To create a resource group, use az group create. To create a resource group, use az group create.
<br>
```azurecli-interactive ```azurecli-interactive
az group create --name myrg --location westus az group create --name myrg --location westus
@ -36,7 +45,7 @@ az group create --name myrg --location westus
Once the resource group is created, you will need to create a Microsoft Connected Cache for Enterprise resource. Once the resource group is created, you will need to create a Microsoft Connected Cache for Enterprise resource.
Create a MCC resource ### 2. Create a MCC resource
A MCC resource is a resource under which cache nodes can be created. A MCC resource is a resource under which cache nodes can be created.
To create a mcc resource, use az mcc ent resource create To create a mcc resource, use az mcc ent resource create
@ -45,35 +54,45 @@ To create a mcc resource, use az mcc ent resource create
az mcc ent resource create --mcc-resource-name mymccresource --resource-group myrg az mcc ent resource create --mcc-resource-name mymccresource --resource-group myrg
``` ```
In the output, look for operationStatus. operationStatus = Succeeded indicates that our services have successfully started creating MCC resource. <br>
[!IMPORTANT]
In the output, look for operationStatus. **operationStatus = Succeeded** indicates that our services have successfully started creating MCC resource.
The next step is to create a cache node under this resource. The next step is to create a cache node under this resource.
Create a cache node ### 3. Create a cache node
To create a cache node, use az mcc ent node create To create a cache node, use az mcc ent node create
```azurecli-interactive ```azurecli-interactive
az mcc ent node create --cache-node-name mycachenode --mcc-resource-name mymccresource --resource-group myrg --host-os linux az mcc ent node create --cache-node-name mycachenode --mcc-resource-name mymccresource --resource-group myrg --host-os linux
``` ```
In the output, look for operationStatus. operationStatus = Succeeded indicates that our services have successfully started creating cache node. <br>
[!IMPORTANT]
In the output, look for operationStatus. **operationStatus = Succeeded** indicates that our services have successfully started creating cache node.
Confirm cache node creation ### 4. Confirm cache node creation
Before you can start configuring your cache node, you need to confirm that cache node creation has been successful. Before you can start configuring your cache node, you need to confirm that cache node creation has been successful.
To confirm cache node creation, use az mcc ent node show To confirm cache node creation, use az mcc ent node show
<br>
```azurecli-interactive ```azurecli-interactive
az mcc ent node show --cache-node-name mycachenode --mcc-resource-name mymccresource --resource-group myrg az mcc ent node show --cache-node-name mycachenode --mcc-resource-name mymccresource --resource-group myrg
``` ```
In the output look for cacheNodeState. If cacheNodeState = Not Configured, you can continue with cache node configuration. [!IMPORTANT]
If cacheNodeState = Registration in Progress, then the cache node is still in process of being created. Please wait for a minute or two more and run the command again. In the output look for cacheNodeState. If **cacheNodeState = Not Configured**, you can continue with cache node configuration.
If **cacheNodeState = Registration in Progress**, then the cache node is still in process of being created. Please wait for a minute or two more and run the command again.
Once the cache node has been created successfully, you can now configure the cache node. Once the cache node has been created successfully, you can now configure the cache node.
Configure cache node ### 5. Configure cache node
To configure your cache node, use az mcc ent node update To configure your cache node, use az mcc ent node update
Ex: configure linux cache node, proxy, slow Ex: configure linux cache node, proxy, slow
@ -83,14 +102,18 @@ az mcc ent node update --cache-node-name mycachenode --mcc-resource-name mymccre
--cache-drive "[{physical-path:/cachenode/drive1,size-in-gb:50},{physical-path:/cachenode/drive2,size-in-gb:51}]" --proxy enabled --proxy-host "abc.xyz" --proxy-port 80 --auto-update-day 2 --auto-update-time 15:33 --auto-update-week 3 --auto-update-ring slow --cache-drive "[{physical-path:/cachenode/drive1,size-in-gb:50},{physical-path:/cachenode/drive2,size-in-gb:51}]" --proxy enabled --proxy-host "abc.xyz" --proxy-port 80 --auto-update-day 2 --auto-update-time 15:33 --auto-update-week 3 --auto-update-ring slow
``` ```
Note: If your cache node is a Windows cache node, the physical path of the cache drive must be “C:\mccwsl01”. [!IMPORTANT]
In the output, look for operationStatus. operationStatus = Succeeded indicates that our services have successfully updated the cache node. If your cache node is a Windows cache node, the physical path of the cache drive must be **“C:\mccwsl01”**.
In the output, look for operationStatus. **operationStatus = Succeeded** indicates that our services have successfully updated the cache node.
[!IMPORTANT]
Please save values for physicalPath, sizeInGb, proxyPort, proxyHostName as these values will be needed to create the provisioning script. Please save values for physicalPath, sizeInGb, proxyPort, proxyHostName as these values will be needed to create the provisioning script.
Note: proxy info changes, required to provision cache node. [!NOTE]
Proxy info changes, required to provision cache node.
Get provisioning details for the cache node ### 6. Get provisioning details for the cache node
Now that you have configured the cache node, the next step is to provision the cache node on the server. To provision the cache node, you will need to create a provisioning script with relevant information. Now that you have configured the cache node, the next step is to provision the cache node on the server. To provision the cache node, you will need to create a provisioning script with relevant information.
To get the relevant information for provisioning script, use az mcc ent node get-provisioning-details To get the relevant information for provisioning script, use az mcc ent node get-provisioning-details
@ -100,31 +123,36 @@ az mcc ent node get-provisioning-details --cache-node-name mycachenode --mcc-res
In the output, please save the values for cacheNodeId, customerKey, mccResourceId, registrationKey. These values are needed to create the provisioning script. In the output, please save the values for cacheNodeId, customerKey, mccResourceId, registrationKey. These values are needed to create the provisioning script.
Provisioning cache node ### 7. Provisioning cache node
Now
Provisioning cache node on Linux host os: #### Provisioning cache node on Linux host os:
Before you provision your cache node on Linux machine, please make sure you have completed the requisites listed here: Host machine requirements Before you provision your cache node on Linux machine, please make sure you have completed the requisites listed here: Host machine requirements
Use the link below to download and unzip the provisioning package on the server and run the below script to provision your cache node. Use the link below to download and unzip the provisioning package on the server and run the below script to provision your cache node.
Important https://aka.ms/MCC-Ent-InstallScript-Linux
Note: before you execute the script, please make sure you change access permissions by running sudo chmod +x provisionmcc.sh
Note: Please replace the sample values with the values that you saved in the above steps. [!IMPORTANT]
Note: before you execute the script, please make sure you change access permissions by running
Important ```azurepowershell-interactive
sudo chmod +x provisionmcc.sh
```
[!NOTE]
Please replace the sample values in the script below with the values that you saved in the step 5 and 6.
[!IMPORTANT]
'shoulduseproxy' parameter is required, whether or not your network uses proxy to access internet. 'shoulduseproxy' parameter is required, whether or not your network uses proxy to access internet.
https://aka.ms/MCC-Ent-InstallScript-Linux
Provisioning script: Provisioning script:
```powershell-interactive
sudo ./provisionmcc.sh customerid="enter mccResourceId here" cachenodeid=" enter cacheNodeId here " customerkey=" enter customerKey here " registrationkey="enter registrationKey here" drivepathandsizeingb="enter physicalPath value,enter sizeInGb value here" shoulduseproxy="true" proxyurl=http://enter proxy hostname:enter port sudo ./provisionmcc.sh customerid="enter mccResourceId here" cachenodeid=" enter cacheNodeId here " customerkey=" enter customerKey here " registrationkey="enter registrationKey here" drivepathandsizeingb="enter physicalPath value,enter sizeInGb value here" shoulduseproxy="true" proxyurl=http://enter proxy hostname:enter port
```
#### Provisioning cache node on Windows host os:
Provisioning cache node on Windows host os:
Before you provision your cache node on Windows, please make sure you have completed the requisites listed here: Host machine requirements Before you provision your cache node on Windows, please make sure you have completed the requisites listed here: Host machine requirements
@ -137,15 +165,18 @@ Important
https://aka.ms/MCC-Ent-InstallScript-WSL https://aka.ms/MCC-Ent-InstallScript-WSL
If you are using a gmsa account: If you are using a **gmsa** account:
```powershell-interactive
./provisionmcconwsl.ps1 -installationFolder c:\mccwsl01 -customerid enter mccResourceId here -cachenodeid enter cacheNodeId here -customerkey enter customerKey here -registrationkey enter registration key -cacheDrives "/var/mcc,enter drive size" -shouldUseProxy $true -proxyurl " http://enter proxy host name:enter port" -mccRunTimeAccount $User ./provisionmcconwsl.ps1 -installationFolder c:\mccwsl01 -customerid enter mccResourceId here -cachenodeid enter cacheNodeId here -customerkey enter customerKey here -registrationkey enter registration key -cacheDrives "/var/mcc,enter drive size" -shouldUseProxy $true -proxyurl " http://enter proxy host name:enter port" -mccRunTimeAccount $User
```
<br>
If you are using **local user account** or **domain user account**:
If you are using local user account or domain user account: ```powershell-interactive
./provisionmcconwsl.ps1 -installationFolder c:\mccwsl01 -customerid enter mccResourceId here -cachenodeid enter cacheNodeId here -customerkey enter customerKey here -registrationkey enter registration key -cacheDrives "/var/mcc,enter drive size" -shouldUseProxy $true -proxyurl " http://enter proxy host name:enter port" -mccRunTimeAccount $User -mccLocalAccountCredential $myLocalAccountCredential ./provisionmcconwsl.ps1 -installationFolder c:\mccwsl01 -customerid enter mccResourceId here -cachenodeid enter cacheNodeId here -customerkey enter customerKey here -registrationkey enter registration key -cacheDrives "/var/mcc,enter drive size" -shouldUseProxy $true -proxyurl " http://enter proxy host name:enter port" -mccRunTimeAccount $User -mccLocalAccountCredential $myLocalAccountCredential
```
To verify cache node functionality, please see: Verify cache node functionality To verify cache node functionality, please see: Verify cache node functionality