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: AzureAvSetBasicPublicIPUpgrade/README.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ Because the Public IP allocation is set to 'Static' before detaching from the VM
8
8
even in the event of a script failure. For added peace of mind, the module double-checks that the Public IP allocation method is 'Static'
9
9
prior to detaching the Public IP from the VMs.
10
10
11
-
The module logs all upgrade activity to a file named `PublicIPUpgrade.log`, created in the same location where the module was executed (by default).
11
+
The module logs all upgrade activity to a file named `AvSetPublicIPUpgrade.log`, created in the same location where the module was executed (by default).
12
12
13
13
## Unsupported Scenarios
14
14
@@ -64,14 +64,14 @@ The Azure Powershell module must be installed. See [Install the latest Az PowerS
64
64
65
65
### Recovering from a Failed Migration
66
66
67
-
When a migration fails due to a transient issue, such as a network outage or client system crash, the migration can be re-run to configure the Availability Set VMs and Public IPs in the goal state. At execution, the script outputs a recovery log file which is used to ensure the Av Set is properly reconfigured. Review the log file `PublicIPUpgrade.log` created in the location where the script was executed.
67
+
When a migration fails due to a transient issue, such as a network outage or client system crash, the migration can be re-run to configure the Availability Set VMs and Public IPs in the goal state. At execution, the script outputs a recovery log file which is used to ensure the Av Set is properly reconfigured. Review the log file `AvSetPublicIPUpgrade.log` created in the location where the script was executed.
68
68
69
-
To recover from a failed upgrade, pass the recovery log file path to the script with the `-recoverFromFile` parameter and identify the VM to recover with the `-AvailabilitySetName` and `-ResourceGroup` or `-AvailabilitySetResourceID` parameters.
69
+
To recover from a failed upgrade, pass the recovery log file path to the script with the `-recoverFromFile` parameter and identify the Availability Set to recover with the `-AvailabilitySetName` and `-ResourceGroup` or `-AvailabilitySetResourceID` parameters.
70
70
71
71
**EXAMPLE: Recover from a failed migration, passing the name and resource group of the VM to recover, along with the recovery log file**
@@ -84,10 +84,10 @@ The time it takes to upgrade an Availability Set's VM's Public IPs will depend o
84
84
85
85
It is not possible to downgrade a Public IP address from Standard to Basic, so our recommendation is to fail-forward and address the issue with the Standard SKU IPs.
86
86
87
-
### Can I test a migration before executing?
87
+
### Can I test a migration before executing?
88
88
89
89
There is no way to evaluate upgrading a Public IP without completing the action. This script includes a `-whatif` parameter, which checks that your Availability Set will support the upgrade and walks through the steps without taking action.
90
90
91
-
### Does this script support Zonal Basic SKU Public IPs?
91
+
### Does this script support Zonal Basic SKU Public IPs?
92
92
93
93
Yes, the process of upgrading a Zonal Basic SKU Public IP to a Zonal Standard SKU Public IP is the same as a Regional Public IP.
0 commit comments