Skip to content

Commit bd0a0b8

Browse files
committed
Added red rect to diagrams
1 parent a1a03d3 commit bd0a0b8

File tree

4 files changed

+8
-8
lines changed

4 files changed

+8
-8
lines changed
-2.26 KB
Loading
156 Bytes
Loading
-1.79 KB
Loading

articles/azure-vmware/use-hcx-run-commands.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ In this article, you learn how to use HCX run commands. Use run commands to perf
1212

1313
This article describes two HCX commands: **Restart HCX Manager** and **Scale HCX Manager**.
1414

15-
## Restart HCX Manage
15+
## Restart HCX Manager
1616

1717
This Command checks for active HCX migrations and replications. If none are found, it restarts the HCX cloud manager (HCX VM's guest OS).
1818

@@ -24,14 +24,14 @@ This Command checks for active HCX migrations and replications. If none are foun
2424
1. Set parameters and select **Run**.
2525
Optional run command parameters.
2626

27-
If the parameters are used incorrectly, they can halt active migrations, and replications and cause other issues. Brief description of each parameter with an example of when teach should be used.
27+
If the parameters are used incorrectly, they can halt active migrations, and replications and cause other issues. Brief description of each parameter with an example of when it should be used.
2828

2929
**Hard Reboot Parameter** - Restarts the virtual machine instead of the default of a GuestOS Reboot. This command is like pulling the power plug on a machine. We don't want to risk disk corruption so this should only be used if a normal reboot fails, and we have exhausted all other options.
3030

3131
**Force Parameter** - If there are ANY active HCX migrations/replications, this parameter avoids the check for active HCX migrations/replications. If the Virtual machine is in a powered off state, this parameter powers the machine on.
3232

3333
**Scenario 1**: A customer has a migration that has been stuck in an active state for weeks and they need a restart of HCX for a separate issue. Without this parameter, the script will fail due to the detection of the active migration.
34-
Scenario 2: The HCX Manager is powered off and the customer would like to power it back on.
34+
**Scenario 2**: The HCX Manager is powered off and the customer would like to power it back on.
3535

3636
:::image type="content" source="media/hcx-commands/restart-command.png" alt-text="Diagram that shows run command parameters for Restart-HcxManager command." border="false" lightbox="media/hcx-commands/restart-command.png":::
3737

@@ -49,7 +49,7 @@ Use the Scale HCX manager run command to increase the resource allocation of you
4949

5050
1. Select the **Microsoft.AVS.Management** package dropdown menu and select the ``Set-HcxScaledCpuAndMemorySetting`` command.
5151

52-
:::image type="content" source="media/hcx-commands/set-hcx-scale.png" alt-text="Diagram that shows run command parameters for Set-HcxScaledCpuAndMemorySetting Command." border="false" lightbox="media/hcx-commands/set-hcx-scale.png":::
52+
:::image type="content" source="media/hcx-commands/set-hcx-scale.png" alt-text="Diagram that shows run command parameters for Set-HcxScaledCpuAndMemorySetting command." border="false" lightbox="media/hcx-commands/set-hcx-scale.png":::
5353

5454
1. Agree to restart HCX by toggling ``AgreeToRestartHCX`` to **True**.
5555
You must acknowledge that the virtual machine will be restarted.
@@ -58,10 +58,10 @@ Use the Scale HCX manager run command to increase the resource allocation of you
5858
>[!NOTE]
5959
> If this required parameter is set to false that cmdlet execution will fail.
6060
61-
1. Select **Run** to execute.
62-
This process may take between 10-15 minutes.
63-
64-
>[!NOTE]
61+
1. Select **Run** to execute.
62+
This process may take between 10-15 minutes.
63+
64+
>[!NOTE]
6565
> HCX cloud manager will be unavailable during the scaling.
6666
6767
## Next step

0 commit comments

Comments
 (0)