You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-vmware/includes/hcx-network-segments.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,19 +11,19 @@ There are varying ways to configure VMware HCX network segments on-premises. The
11
11
12
12
In preparation for the VMware HCX deployment to support the pilot or small production use case, identify the following:
13
13
14
-
-**Management network:** When deploying VMware HCX on-premises, you'll need to define a management network. Typically, it's the same management network used by your on-premises VMware cluster. At a minimum, identify **two** IPs on this network segment for VMware HCX. You might need larger numbers, depending on the scale of your deployment beyond the pilot or small use case.
14
+
-**Management network:** When deploying VMware HCX on-premises, you'll need to identify a management network for VMware HCX. Typically, it's the same management network used by your on-premises VMware cluster. At a minimum, identify **two** IPs on this network segment for VMware HCX. You might need larger numbers, depending on the scale of your deployment beyond the pilot or small use case.
15
15
16
-
> [!NOTE]
17
-
> The recommended method is to create a /26 network because you can use up to 10 service meshes and 60 network extenders (-1 per service mesh). You can stretch **eight** networks per network extender by using Azure VMware Solution private clouds.
18
-
>
19
-
20
-
-**vMotion network:** When deploying VMware HCX on-premises, you'll need to define a vMotion network. Typically, it's the same network used for vMotion by your on-premises VMware cluster. At a minimum, identify **two** IPs on this network segment for VMware HCX. You might need larger numbers, depending on the scale of your deployment beyond the pilot or small use case.
16
+
> [!NOTE]
17
+
> Preparing for large environments, instead of using the management network used for the on-premises VMware cluster, create a new /26 network and present that network as a port group to your on-premises VMware cluster. You can then create up to 10 service meshes and 60 network extenders (-1 per service mesh). You can stretch **eight** networks per network extender by using Azure VMware Solution private clouds.
18
+
>
19
+
20
+
-**Uplink network:** When deploying VMware HCX on-premises, you'll need to identify a Uplink network for VMware HCX. Use the same network which you will be using for the Management network.
21
+
22
+
-**vMotion network:** When deploying VMware HCX on-premises, you'll need to identify a vMotion network for VMware HCX. Typically, it's the same network used for vMotion by your on-premises VMware cluster. At a minimum, identify **two** IPs on this network segment for VMware HCX. You might need larger numbers, depending on the scale of your deployment beyond the pilot or small use case.
21
23
22
24
The vMotion network must be exposed on a distributed virtual switch or vSwitch0. If it's not, modify the environment to accommodate.
23
25
24
26
> [!NOTE]
25
27
> Many VMware environments use non-routed network segments for vMotion, which poses no problems.
26
-
27
-
-**Uplink network:** When deploying VMware HCX on-premises, you'll need to define an Uplink network. Use the management network defined as your uplink network.
28
-
29
-
-**Replication network:** When deploying VMware HCX on-premises, you'll need to define a replication network. Use the management network defined as your replication network. If the on-premises cluster hosts use a dedicated Replication VMkernel network, reserve **two** IP addresses in this network segment and use the Replication VMkernel network for the replication network.
28
+
29
+
-**Replication network:** When deploying VMware HCX on-premises, you'll need to define a replication network. Use the same network as you are using for your Management and Uplink networks. If the on-premises cluster hosts use a dedicated Replication VMkernel network, reserve **two** IP addresses in this network segment and use the Replication VMkernel network for the replication network.
// Measure the performance (Request Units) of writes
@@ -256,4 +256,4 @@ The request charge (that is, the request-processing cost) of a specified operati
256
256
## Next steps
257
257
Forasampleapplicationthat's used to evaluate Azure Cosmos DB for high-performance scenarios on a few client machines, see [Performance and scale testing with Azure Cosmos DB](performance-testing.md).
258
258
259
-
Tolearnmoreaboutdesigningyourapplicationforscaleandhighperformance, see [PartitioningandscalinginAzureCosmosDB](partitioning-overview.md).
259
+
Tolearnmoreaboutdesigningyourapplicationforscaleandhighperformance, see [PartitioningandscalinginAzureCosmosDB](partitioning-overview.md).
Copy file name to clipboardExpand all lines: includes/api-management-service-limits.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ ms.custom: include file
26
26
| Maximum number of subscriptions per service instance<sup>8</sup> | 500 |
27
27
| Maximum number of client certificates per service instance<sup>8</sup> | 50 |
28
28
| Maximum number of APIs per service instance<sup>8</sup> | 50 |
29
-
| Maximum number of API operations per service instance<sup>8</sup> | 1,000 |
29
+
| Maximum number of API management operations per service instance<sup>8</sup> | 1,000 |
30
30
| Maximum total request duration<sup>8</sup> | 30 seconds |
31
31
| Maximum buffered payload size<sup>8</sup> | 2 MiB |
32
32
| Maximum request URL size<sup>9</sup> | 4096 bytes |
@@ -45,4 +45,4 @@ ms.custom: include file
45
45
<sup>8</sup>This limit applies to the Consumption tier only. There are no limits in these categories for other tiers.<br/>
46
46
<sup>9</sup>Applies to the Consumption tier only. Includes an up to 2048 bytes long query string.<br/>
47
47
<sup>10</sup> To increase this limit, please contact [support](https://azure.microsoft.com/support/options/).<br/>
48
-
<sup>11</sup>Self-hosted gateways are supported in the Developer and Premium tiers only. The limit applies to the number of [self-hosted gateway resources](/rest/api/apimanagement/2019-12-01/gateway). To raise this limit please contact [support](https://azure.microsoft.com/support/options/). Note, that the number of nodes (or replicas) associated with a self-hosted gateway resource is unlimited in the Premium tier and capped at a single node in the Developer tier.
48
+
<sup>11</sup>Self-hosted gateways are supported in the Developer and Premium tiers only. The limit applies to the number of [self-hosted gateway resources](/rest/api/apimanagement/2019-12-01/gateway). To raise this limit please contact [support](https://azure.microsoft.com/support/options/). Note, that the number of nodes (or replicas) associated with a self-hosted gateway resource is unlimited in the Premium tier and capped at a single node in the Developer tier.
0 commit comments