Deployment of Cisco SDWAN vBond VM from custom image stuck in creating state

Mohneesh Soni 5 Reputation points
2023-08-27T12:18:49.55+00:00

We are trying to deploy Cisco SDWAN vbond VM from custom image. We observed 3 out of 5 times it stuck in creating status for more than 40-50min.

We are deploying other Cisco SDWAN controllers as well e.g. vManage, vSmart without any issue.

But issue occurs only with vBond image. We already tried different Azure regions and separate image versions. The pattern remain same. A few time vBond VM got created immediately and some time it take more than expected time. VM status is creating.PNG

Please review the attaching Activity logs. Microsoft_Azure_ResourceHealth_EMS-AZU-UKS-VBO01_1693135831000.pdf

Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
9,051 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Prrudram-MSFT 28,366 Reputation points Microsoft Employee Moderator
    2023-09-05T04:41:46.63+00:00

    Hi @Mohneesh Soni ,

    Based on the information you provided, the issue is specific to the vBond image and not related to the Azure region or image version.

    To troubleshoot the issue, we need to collect the logs from the VM while it is in the "Creating" state. The logs will help us identify the root cause of the issue.

    You can collect the logs using the Azure Serial Console. To do this, follow these steps:

    1. Go to the Azure portal and navigate to the VM that is stuck in the "Creating" state.
    2. Click on the "Serial Console" button in the top menu bar.
    3. In the Serial Console window, click on the "Send Ctrl-Alt-Del" button to reboot the VM.
    4. Wait for the VM to reboot and then press any key to enter the boot menu.
    5. Select "Boot Diagnostics" from the boot menu and press Enter.
    6. Wait for the VM to boot into the diagnostics console.
    7. In the diagnostics console, click on the "Serial log" tab to view the logs.

    The logs will provide more information about what is happening during the VM creation process. Look for any error messages or warnings that might indicate the root cause of the issue.

    If you are unable to identify the issue from the logs, you can try creating a new VM from the same vBond image and see if the issue persists. If the issue persists, you can contact Cisco support for further assistance.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.