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/operator-nexus/troubleshoot-bmm-node-reboot.md
+11-11Lines changed: 11 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,15 +1,15 @@
1
1
---
2
-
title: Troubleshoot Post BMM Cordon & Restart, VMs show up as error on Portal. Power & Restart doesn’t work anymore for Azure Operator Nexus
3
-
description: Troubleshoot Post BMM Cordon & restart, VMs show up as error on Portal. Power & Restart doesn’t work anymore.
2
+
title: Troubleshoot Post Bare Metal machine(BMM) Cordon and Restart, VMs show up as error on Portal. Power and Restart doesn’t work anymore for Azure Operator Nexus
3
+
description: Troubleshoot Post Bare Metal machine(BMM) Cordon and restart, VMs show up as error on Portal. Power & Restart doesn’t work anymore.
4
4
ms.service: azure-operator-nexus
5
5
ms.custom: troubleshooting
6
6
ms.topic: troubleshooting
7
7
ms.date: 06/13/2023
8
8
ms.author: v-sathysubra
9
9
author: Sathyadevi-S
10
10
---
11
-
# Troubleshoot post BMM cordon & restart, VMs show up as error on portal. Power & Restart doesn’t work anymore
12
-
Follow this troubleshooting guide for BMM Cordon & Restart:
11
+
# Troubleshoot post Bare Metal machine(BMM) cordon and restart, VMs show up as error on portal. Power and Restart doesn’t work anymore
12
+
Follow this troubleshooting guide for Bare Metal machine(BMM) Cordon and Restart:
13
13
- If you encounter VMs showing up as "ERROR" on the portal after an upgrade.
14
14
- Traditional methods such as powering off and restarting the VMs doesn't work
15
15
@@ -24,23 +24,23 @@ Follow this troubleshooting guide for BMM Cordon & Restart:
24
24
25
25
## Symptoms
26
26
27
-
- During BMM restart/upgrade testing, the VM is currently in an error state.
28
-
- After the BMM reboot CORDONED -> POWERED OFF -> POWERED ON -> UNCORDONED
27
+
- During Bare Metal machine(BMM) restart or upgrade testing, the VM is currently in an error state.
28
+
- After the Bare Metal machine(BMM) reboot CORDONED -> POWERED OFF -> POWERED ON -> UNCORDONED
29
29
- Although the VNF successfully came up, established its BGP sessions, and started routing traffic, the VM status in the portal consistently shows an error. Despite this discrepancy, the application remains healthy and continues to function properly.
30
-
- The Portal actions & AZ CLI APIs for the NC VM resource itself were no longer achieving the intent. Example:
30
+
- The Portal actions and AZ CLI APIs for the NC VM resource itself were no longer achieving the intent. Example:
31
31
- Clicking the Power Off (or AZ CLI) actually Power Off the VM anymore
32
32
- Clicking the Restart (or AZ CLI) doesn't actually Restart the VM anymore
33
33
- The platform has lost capability to manage this VM Resource
34
34
35
-
:::image type="content" source="media\troubleshoot-bmm-server\bmm-errorstatus.png" alt-text="Screenshot of Sample VM in Error status." lightbox="media\troubleshoot-bmm-server\bmm-errorstatus.png":::
35
+
:::image type="content" source="media\troubleshoot-bmm-server\bmm-error-status.png" alt-text="Screenshot of Sample VM in Error status." lightbox="media\troubleshoot-bmm-server\bmm-error-status.png":::
36
36
37
37
## Troubleshooting
38
38
39
39
- Gather the VM details and Validate the VM status in the portal.
40
40
41
41
- VM isn't connected and powered off
42
-
- Validate the status of the virtual machine before and after restart/upgrade
43
-
- Check the BGP session and traffic flow before and after restart/upgrade of the VNF
42
+
- Validate the status of the virtual machine before and after restart or upgrade
43
+
- Check the BGP session and traffic flow before and after restart or upgrade of the VNF
44
44
- For more troubleshooting, see [troubleshoot-reboot-reimage-replace](troubleshoot-reboot-reimage-replace.md)
45
45
46
46
## Procedure
@@ -55,4 +55,4 @@ Perform the following CLI update on any affected VMs with some dummy tag values
55
55
56
56
This process facilitates the restoration of the VM to an online state.
57
57
58
-
:::image type="content" source="media\troubleshoot-bmm-server\BMM-runningstatus.png" alt-text="Screenshot of Sample VM in running status." lightbox="media\troubleshoot-bmm-server\BMM-runningstatus.png":::
58
+
:::image type="content" source="media\troubleshoot-bmm-server\BMM-running-status.png" alt-text="Screenshot of Sample VM in running status." lightbox="media\troubleshoot-bmm-server\BMM-running-status.png":::
0 commit comments