mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-29 13:47:23 +00:00
add edits to verification of client, some enterprise changes for clarity
This commit is contained in:
Amy Zhou
parent
a924fd0782
commit
8f7c2f5fcd
@ -23,13 +23,20 @@ If you're not able to sign up for a Microsoft Azure subscription with the **Acco
|
||||
- [Can't sign up for a Microsoft Azure subscription](/troubleshoot/azure/general/cannot-sign-up-subscription).
|
||||
- [Troubleshoot issues when you sign up for a new account in the Azure portal](/azure/cost-management-billing/manage/troubleshoot-azure-sign-up).
|
||||
|
||||
## Installing on VMWare
|
||||
## Hardware specifications
|
||||
|
||||
Most customers choose to install their cache node on a Windows Server with a nested Hyper-V VM. If this is not supported in your network, some customers have also opted to install their cache node using VMWare. At this time, a Linux-only solution is not available and Azure VMs do not support the standalone Microsoft Connected Cache.
|
||||
|
||||
### Installing on VMWare
|
||||
|
||||
We've seen that Microsoft Connected Cache for Enterprise and Education can be successfully installed on VMWare. To do so, there are a couple of additional configurations to be made:
|
||||
|
||||
1. Ensure that you're using ESX. In the VM settings, turn on the option **Expose hardware assisted virtualization to the guest OS**.
|
||||
1. Using the HyperV Manager, create an external switch. For the external switch to have internet connection, ensure **"Allow promiscuous mode"**, **"Allow forged transmits"**, and **"Allow MAC changes"** are all switched to **Yes**.
|
||||
|
||||
### Installing on Hyper-V
|
||||
To learn more about how to configure Intel and AMD processors to support nested virtualization, see [Run Hyper-V in a Virtual Machine with Nested Virtualization](/virtualization/hyper-v-on-windows/user-guide/nested-virtualization).
|
||||
|
||||
## Diagnostics Script
|
||||
|
||||
If you're having issues with your MCC, we included a diagnostics script. The script collects all your logs and zips them into a single file. You can then send us these logs via email for the MCC team to debug.
|
||||
@ -95,7 +102,7 @@ You can either set your MCC IP address or FQDN using:
|
||||
:::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." lightbox="./images/ent-mcc-group-policy-hostname.png":::
|
||||
|
||||
|
||||
**Verify Content using the DO Client**
|
||||
## Verify Content using the DO Client
|
||||
|
||||
To verify that the Delivery Optimization client can download content using MCC, you can use the following steps:
|
||||
|
||||
|
||||
@ -24,8 +24,7 @@ ms.topic: article
|
||||
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 don't 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 free to you, like other caching solutions.
|
||||
|
||||
2. **Hardware to host MCC**: The recommended configuration will serve approximately 35000 managed devices, downloading a 2 GB payload in 24-hour timeframe at a sustained rate of 6.5 Gbps.
|
||||
1. **Hardware to host MCC**: The recommended configuration will serve approximately 35000 managed devices, downloading a 2 GB payload in 24-hour timeframe at a sustained rate of 6.5 Gbps.
|
||||
|
||||
> [!NOTE]
|
||||
> Azure VMs are not currently supported. If you'd like to install your cache node on VMWare, see the [Appendix](mcc-enterprise-appendix.md) for a few additional configurations.
|
||||
@ -44,6 +43,7 @@ ms.topic: article
|
||||
|
||||
VM networking:
|
||||
- An external virtual switch to support outbound and inbound network communication (created during the installation process)
|
||||
1. **Content endpoints**: Using a proxy or firewall? Certain endpoints must be allowed through in order for your MCC to cache and serve content. See [Delivery Optimization and Microsoft Connected Cache content type endpoints](delivery-optimization-endpoints.md) for the complete list of endpoints required.
|
||||
|
||||
## Sizing recommendations
|
||||
|
||||
|
||||
@ -68,8 +68,6 @@ sections:
|
||||
answer: We have already successfully onboarded ISPs in many countries around the world and have received positive feedback! However, you can always start off with a portion of your CIDR blocks to test out the performance of MCC before expanding to more customers.
|
||||
- question: How does Microsoft Connected Cache populate its content?
|
||||
answer: Microsoft Connected Cache is a cold cache warmed by client requests. The client requests content and that is what fills up the cache. There's no off-peak cache fill necessary. Microsoft Connected Cache will reach out to different CDN providers just like a client device would. The traffic flow from Microsoft Connected Cache will vary depending on how you currently transit to each of these CDN providers. The content can come from third party CDNs or from AFD.
|
||||
- question: What do I do if I need more support and have more questions even after reading this FAQ page?
|
||||
answer: For further support for Microsoft Connected Cache, visit [Troubleshooting Issues for Microsoft Connected Cache for ISP (public preview)](mcc-isp-support.md).
|
||||
- question: What CDNs will Microsoft Connected Cache pull content from?
|
||||
answer: |
|
||||
Microsoft relies on a dynamic mix of 1st and 3rd party CDN providers to ensure enough capacity, redundancy, and performance for the delivery of Microsoft served content. Though we don't provide lists of the CDN vendors we utilize as they can change without notice, our endpoints are public knowledge. If someone were to perform a series of DNS lookups against our endpoints (tlu.dl.delivery.mp.microsoft.com for example), they would be able to determine which CDN or CDNs were in rotation at a given point in time:
|
||||
@ -81,3 +79,7 @@ sections:
|
||||
$ whois 13.107.4.50|grep "Organization:"
|
||||
|
||||
Organization: Microsoft Corporation (MSFT)
|
||||
- question: I have an active MCC, but I'm noticing I hit the message limit for my IoT Hub each day. Does this affect my MCC performance and should I be concerned?
|
||||
answer: Even when the quota of 8k messages is hit, the MCC functionality will not be affected. Your client devices will continue to download content as normal. You will also not be charged above the 8k message limit, so you don’t need to worry at all about getting a paid plan – MCC will always be a free service. So what is the impact if functionality isn’t? Instead, messages about the configuration or edge deployment would be impacted – this means that if there was a request to update your MCC and the daily quota was reached, your MCC might not update. In that case, you would just need to wait for the next day to update. This is only a limitation of the private preview and is not an issue during public preview.
|
||||
- question: What do I do if I need more support and have more questions even after reading this FAQ page?
|
||||
answer: For further support for Microsoft Connected Cache, visit [Troubleshooting Issues for Microsoft Connected Cache for ISP (public preview)](mcc-isp-support.md).
|
||||
|
||||
@ -17,6 +17,28 @@ ms.topic: article
|
||||
|
||||
This article details how to verify that your cache node(s) are functioning properly and serving traffic. This article also details how to monitor your cache nodes.
|
||||
|
||||
## Verify cache node installation is complete
|
||||
|
||||
Sign in to the Connected Cache server or use SSH. Run the following command from a terminal to see the running modules (containers):
|
||||
|
||||
```bash
|
||||
sudo iotedge list
|
||||
```
|
||||
|
||||
:::image type="content" source="./images/mcc-isp-running-containers.png" alt-text="Screenshot of the terminal output of iotedge list command, showing the running containers." lightbox="./images/mcc-isp-running-containers.png":::
|
||||
|
||||
If it lists the **edgeAgent** and **edgeHub** containers, but doesn't include **MCC**, view the status of the IoT Edge security manager using the command:
|
||||
|
||||
```bash
|
||||
sudo iotedge system logs -- -f
|
||||
```
|
||||
|
||||
For example, this command provides the current status of the starting and stopping of a container, or the container pull and start:
|
||||
|
||||
:::image type="content" source="./images/mcc-isp-edge-journalctl.png" alt-text="Terminal output of journalctl command for iotedge." lightbox="./images/mcc-isp-edge-journalctl.png":::
|
||||
|
||||
You may need to wait several minutes for the MCC container image to complete downloading and to start up.
|
||||
|
||||
## Verify functionality on Azure portal
|
||||
|
||||
Sign into the [Azure portal](https://www.portal.azure.com) and navigate to the **Overview** page. Select the **Monitoring** tab to verify the functionality of your server(s) by validating the number of healthy nodes shown. If you see any **Unhealthy nodes**, select the **Diagnose and Solve** link to troubleshoot and resolve the issue.
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user