Deleting a Virtual Gateway Attachment
Scenarios
This section describes how to delete a virtual gateway attachment from an enterprise router.
Notes and Constraints
- Deleting an attachment will also delete its associations, propagations, and propagated routes in the route table.
- If flow logging is enabled for an attachment, flow logging will be disabled, but collected flow logs will not be deleted.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List and choose Networking > Enterprise Router.
The Enterprise Router homepage is displayed.
- Search for the target enterprise router by name.
Figure 1 Searching for an enterprise router
- Go to the Attachments tab using either of the following methods:
- In the upper right corner of the enterprise router, click Manage Attachment.
- Click the enterprise router name and click Attachments.
A virtual gateway attachment cannot be directly deleted on the Attachments page of the enterprise router.
A virtual gateway attachment will be automatically deleted after you perform the following operations to delete the virtual gateway and its virtual interfaces.
- Locate the target virtual gateway attachment and click the attached resource.
Example: vgw-demo
The virtual gateway attachment details page is displayed.
- On the details page, click the virtual gateway.
The virtual gateway list is displayed.
- Check whether the virtual gateway has virtual interfaces.
- If the virtual gateway has virtual interfaces, delete the virtual interfaces first.
For details, see section "Deleting a Virtual Interface" in the Direct Connect User Guide.
- If the virtual gateway has no virtual interfaces, go to 9.
- If the virtual gateway has virtual interfaces, delete the virtual interfaces first.
- Locate the target virtual gateway and click Delete in the Operation column.
A confirmation dialog box is displayed.
- Click Yes.
A deleted virtual gateway cannot be recovered.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.