How to create a sync core in Cloud Volumes ONTAP in Azure
- Views:
- 404
- Visibility:
- Public
- Votes:
- 0
- Category:
- cloud-volumes-ontap-cvo
- Specialty:
- microsoft_azure
- Last Updated:
Applies to
- Cloud Volumes ONTAP (CVO)
- Microsoft Azure
Description
This article describes the procedure that must be taken to obtain a sync core from a Cloud Volumes ONTAP instance running on Microsoft Azure.
Procedure
There are two methods for generating a sync core from a node in Azure. Method 1 can be used if the node is responsive, while Method 2 can be used if the node has hung.
| These procedures will cause a panic on the node the procedure is run against. This action can cause a disruption to service. Use these procedures with caution. |
Method 1: Clustershell Command
- Log into the Clustershell via SSH or the Serial console in the Azure console.
- Use the
system node rebootcommand as below, replacing<node_name>with the name of the node you need the core file from.
::> system node reboot -node <node_name> -dump true
- The node will dump a core file and reboot. If the node is in an HA pair, the partner will takeover.
Method 2: Send an NMI from the Azure console
- Log into the Azure console and select the Virtual Machine for the node you need the core file from.
- On the menu under the "Support + troubleshooting" header, select Serial console
- Once the serial console has connected, select the keyboard icon at the top, and click Send Non-Maskable Interrupt (NMI)...
- The node will panic, dump a core file, and reboot. If the node is in an HA pair, the partner will takeover.
Note:
- Once the system has rebooted, you can view the core file by using the
system node coredump showcommand. - You can then upload the core file using the
system node autosupport invoke-core-uploadcommand.
Additional Information
Related Links:
Internal Notes
You must fill out a dynamic sync core template for the core to be reviewed. Consult with your EE for help with the template.