forked from docs/enterprise-router
first uplo Reviewed-by: Sarda, Priya <prsarda@noreply.gitea.eco.tsi-dev.otc-service.com> Co-authored-by: proposalbot <proposalbot@otc-service.com> Co-committed-by: proposalbot <proposalbot@otc-service.com>
52 lines
1.9 KiB
ReStructuredText
52 lines
1.9 KiB
ReStructuredText
:original_name: er_01_0099.html
|
|
|
|
.. _er_01_0099:
|
|
|
|
Accepting an Attachment Request
|
|
===============================
|
|
|
|
Scenarios
|
|
---------
|
|
|
|
This section describes how to accept a request from another user for creating an attachment to your enterprise router.
|
|
|
|
.. note::
|
|
|
|
- If **Auto Accept Shared Attachments** is disabled on your enterprise router, you can choose to accept the attachment request or not.
|
|
- If **Auto Accept Shared Attachments** is enabled on your enterprise router, the attachment will be automatically accepted without your approval.
|
|
|
|
Procedure
|
|
---------
|
|
|
|
#. Log in to the management console.
|
|
|
|
#. Click |image1| 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:: /_static/images/en-us_image_0000001674900098.png
|
|
:alt: **Figure 1** Searching for an enterprise router
|
|
|
|
**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**.
|
|
|
|
#. In the attachment list, locate the attachment you want to accept and click **Accept** in the **Operation** column.
|
|
|
|
The owner accepts the attachment request. The attachment status changes from **Pending acceptance** to **Creating**.
|
|
|
|
- When the attachment status changes to **Normal**, the attachment is successfully created.
|
|
- When the attachment status changes to **Failed**, the attachment fails to be created. Contact customer service.
|
|
|
|
After an attachment is created, you can perform :ref:`Follow-up Procedure <er_01_0070__section582517444316>`.
|
|
|
|
.. |image1| image:: /_static/images/en-us_image_0000001190483836.png
|