deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-16 02:43:43 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

added version history, added tables and screenshot

Browse Source
This commit is contained in:
Amy Zhou
2022-09-09 13:49:35 -07:00
parent dbfabe19fe
commit fa54063a9a
10 changed files with 62 additions and 47 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
windows/deployment/do/images/mcc-img-metrics.PNG Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 40 KiB

22
windows/deployment/do/mcc-isp-cache-node-configuration.md
View File

@ -2,15 +2,27 @@
All cache node configuration will take place within Azure portal. This article outlines all of the settings that you will be able to configure.
## Settings
| 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. |
| **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. |
| **Cache drive size in gigabytes** | Integer in GB | Set the size of each drive configured for the cache node. |
| **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 |
| **Neighbor ASN** | Integer ASN | When configuring BGP, enter the ASN(s) of your neighbors that you want to establish. |
| **Neighbor IP address** | Ipv4 address | When configuring BGP, enter the IP address(es) of neighbors that you want to establish. |
## Storage
| 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
| Field Name | Expected Value| Description |
| -- | --- | --- |
| **Manual touting - 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. |

6
windows/deployment/do/mcc-isp-client-routing.md
View File

@ -1,4 +1,4 @@
# Client Routing (CIDR, BGP)
# Client Routing
Before serving traffic to your customers, client routing configuration is needed. During the configuration of your cache node in Azure portal, you will be able to route your clients to your cache node.
@ -8,9 +8,9 @@ Once client routing and other settings are configured, your cache node will be a
At this time, only IPv4 addresses are supported. IPv6 addresses are not supported.
### CIDR blocks
### Manual routing
CIDR blocks are comprised of IP prefixes (groups of IP addresses) that represent your customer base. You can manually upload a list of your CIDR blocks in Azure portal.
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

10
windows/deployment/do/mcc-isp-configure-routing.md
View File

@ -27,11 +27,9 @@ All configuration routing takes place within the Azure Portal. There are two mai
> [!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.
a. Make sure there aren't any firewall rules blocking this connection.
b. Verify that the BGP connection has been established and that you're advertising routes to the MCC.
c. Wait five minutes to refresh the cache node page in the Azure portal to see the BGP routes.
> [!NOTE]
> Make sure there aren't any firewall rules blocking this connection.
1. If there are errors:
- Inspect the installer logs, which are in the following path: `/etc/mccresourcecreation/`
- For more information, see [Troubleshoot your IoT Edge device](/azure/iot-edge/troubleshoot).
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.

30
windows/deployment/do/mcc-isp-monitor.md
View File

@ -3,21 +3,27 @@
## Metrics
Within Azure portal, there are a number of metrics that are available to monitor cache node health and performance.
### Available Metrics
- **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
### Viewing your metrics
### Monitoring your metrics
To view the metrics associated with your cache nodes, navigate to the **Overview** >> **Monitoring** tab within Azure portal.
[[ include screenshot of an example view]]
:::image type="content" source="images/mcc-isp-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 by one 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 are unable to view metrics for your cache node, it may be that your cache node is unhealthy, inactive, or hasn't been fully configured.
### Available Metrics
Within Azure portal, you are able to build your custom metrics 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 metrics, visit [Azure Monitor](https://docs.microsoft.com/en-us/azure/azure-monitor/essentials/data-platform-metrics) for details.

3
windows/deployment/do/mcc-isp-uninstall.md
View File

@ -12,9 +12,6 @@ Within Azure portal, navigate to **Cache Nodes**, then select the cache node you
## 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.
> [!WARNING]
> Be cautious before running this script. It will also erase existing IoT workflows in this VM.
The **uninstallmcc.sh** script removes the following components:
- IoT Edge

4
windows/deployment/do/mcc-isp-update.md
View File

@ -2,6 +2,6 @@
Microsoft will release updates for MCC periodically to improve performance, functionality, and security. Updates will not require any action from the customer. Instead, when an update is available, your cache node will automatically update during low traffic hours with minimal to no impact to your end customers.
To view which version your cache nodes are currently on, [[*********]].
To view which version your cache nodes are currently on, navigate to the **Cache nodes** tab to view the versions in the list view.
To view update release notes, visit our Tech Community page.
To view update release notes, visit [Version History](mcc-version-history.md).

4
windows/deployment/do/mcc-isp-verify-cache-node.md
View File

@ -2,11 +2,11 @@
### Verify functionality on Azure portal
Log into Azure portal and navigate to the Overview page. Select the **Monitoring** tab to verify the functionality of your server. If you see **All systems go** for your cache node, your server is successfully deployed and running. If you see **Error detected** for your cache node or other warning messages, select the "Diagnose and Solve" link to troubleshoot and resolve the issue.
Log into Azure portal 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.
### Verify functionality on the server
It can take a few minutes for the container to deploy.
It can take a few minutes for the container to deploy after you've saved the configuration.
To validate a properly functioning MCC, run the following command in the terminal of the cache server or any device in the network. Replace `<CacheServerIP>` with the IP address of the cache server.

30
windows/deployment/do/mcc-traffic-estimation.md
View File

@ -1,6 +1,6 @@
# 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 will use these estimations to recommend the right hardware for you to deploy your cache node on. You can view these recommendations within the Azure portal.
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 will use these estimations to recommend hardware or VM configurations. You can view these recommendations within the Azure portal.
Note that 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]().
@ -8,28 +8,30 @@ Note that we make these estimations based on the Microsoft content types that Mi
To make sure you are maximizing the performance of your cache node, please note the following:
### Drive performance
### OS requirements
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.
The MCC 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.
### Sizing recommendations
### Drive performance
The MCC module is optimized for Ubuntu 20.04 LTS. Install Ubuntu 20.04 LTS on a physical server or VM of your choice. The following recommended configuration can egress at a rate of 9 Gbps with a 10 Gbps NIC.
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.
| Component | Minimum | Recommended |
| -- | --- | --- |
| OS | Ubuntu 20.04 LTS VM or physical server | Ubuntu 20.04 LTS VM or physical server (preferred) |
| NIC | 10 Gbps| at least 10 Gbps |
| Disk | SSD <br>1 drive <br>2 TB each |SSD <br>2-4 drives <br>at least 2 TB each |
| Memory | 8 GB | 32 GB or greater |
| Cores | 4 | 8 or more |
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.40GHz , total 32core
- 48GB, Micron Technology 18ASF1G72PDZ-2G1A1, Speed: 2133 MT/s
- 4 - Transcend SSD230s 1TB SATA Drives
- Intel Corporation Ethernet 10G 2P X520 Adapter (Link Aggregated)
### Virtual Machines

0
windows/deployment/do/mcc-version-history.md Normal file
View File