Merge pull request #10388 from MicrosoftDocs/main

Publish main to live, Friday 10:30AM PST, 11/08
This commit is contained in:
Stacyrch140 2024-11-08 13:42:42 -05:00 committed by GitHub
commit 2cd530b38c
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 23 additions and 17 deletions

View File

@ -303,16 +303,14 @@ Navigate to the Connected Cache resource to delete, then select the **Delete** o
# [Azure CLI](#tab/cli)
Use the following command to delete the Connected Cache resource.
Use the following command to delete the cache node under the resource.
Replace the following placeholders with your own information:
* *\<resource-group>*: Name of the resource group in your subscription.
* *\<mcc-resource-name>*: Name of your Microsoft Connected Cache for Enterprise resource.
* *\<cache-node-name>*: The name for your Microsoft Connected Cache node.
```azurecli-interactive
az mcc ent node delete --cache-node-name <mycachenode> --mcc-resource-name <mymccresource> --resource-group <myrg>
az mcc ent resource delete --mcc-resource-name <mymccresource> --resource-group <myrg>
```
---
@ -323,16 +321,19 @@ On the left pane, select **Cache Nodes** under **Cache Node Management** to see
# [Azure CLI](#tab/cli)
Use the following command to delete the cache node under the resource.
Use the following command to delete the Connected Cache node.
Replace the following placeholders with your own information:
* *\<resource-group>*: Name of the resource group in your subscription.
* *\<mcc-resource-name>*: Name of your Microsoft Connected Cache for Enterprise resource.
* *\<cache-node-name>*: The name for your Microsoft Connected Cache node.
```azurecli-interactive
az mcc ent node delete --mcc-resource-name <mymccresource> --resource-group <myrg>
az mcc ent node delete --cache-node-name <mycachenode> --mcc-resource-name <mymccresource> --resource-group <myrg>
```
---
<br>
@ -345,4 +346,4 @@ az mcc ent node delete --mcc-resource-name <mymccresource> --resource-group <myr
|Not provisioned| Cache node is ready to be provisioned on host machine|
|Healthy| Cache node phoning home|
|Unhealthy| Cache node has stopped phoning home|
|Never phoned home| Cache node has provisioned but has never phoned home|
|Never phoned home| Cache node has provisioned but has never phoned home|

View File

@ -140,7 +140,21 @@ az mcc ent node get-provisioning-details --cache-node-name mycachenode --mcc-res
>* In the output look for cacheNodeState. If **cacheNodeState = Not Provisioned**, you can continue with cache node provisioning.
>* If **cacheNodeState = Not Configured**, then the cache node has not been configured. Configure the cache node before provisioning.
### Example script:
<br>
## Next step
To deploy the cache node to a **Windows** host machine, see
>[!div class="nextstepaction"]
>[Deploy cache node to Windows](mcc-ent-deploy-to-windows.md)
To deploy the cache node to a **Linux** host machine, see
>[!div class="nextstepaction"]
>[Deploy cache node to Linux](mcc-ent-deploy-to-linux.md)
<br>
### Example script to bulk create and configure multiple cache nodes:
Below is a pseudocode example of how to script bulk creation and configuration of a Connected Cache Azure resource and multiple Connected Cache cache nodes:
@ -199,12 +213,3 @@ for ($cacheNodeNumber = 1; $cacheNodeNumber -le $cacheNodesToCreate; $cacheNodeN
```
---
## Next step
To deploy the cache node to a **Windows** host machine, see
>[!div class="nextstepaction"]
>[Deploy cache node to Windows](mcc-ent-deploy-to-windows.md)
To deploy the cache node to a **Linux** host machine, see
>[!div class="nextstepaction"]
>[Deploy cache node to Linux](mcc-ent-deploy-to-linux.md)