Changes to ccn_umn from docs/doc-exports#1450 (CCN UMN 20250121 version)
Reviewed-by: Hajba, László Antal <laszlo-antal.hajba@t-systems.com> Co-authored-by: OpenTelekomCloud Proposal Bot <proposalbot@otc-service.com> Co-committed-by: OpenTelekomCloud Proposal Bot <proposalbot@otc-service.com>
BIN
umn/source/_static/images/en-us_image_0000001190483836.png
Normal file
|
After Width: | Height: | Size: 1004 B |
BIN
umn/source/_static/images/en-us_image_0000002082069408.png
Normal file
|
After Width: | Height: | Size: 289 B |
BIN
umn/source/_static/images/en-us_image_0000002082224192.png
Normal file
|
After Width: | Height: | Size: 289 B |
BIN
umn/source/_static/images/en-us_image_0000002089104748.png
Normal file
|
After Width: | Height: | Size: 1004 B |
BIN
umn/source/_static/images/en-us_image_0000002089104752.png
Normal file
|
After Width: | Height: | Size: 1004 B |
BIN
umn/source/_static/images/en-us_image_0000002089264608.png
Normal file
|
After Width: | Height: | Size: 1004 B |
BIN
umn/source/_static/images/en-us_image_0000002089264612.png
Normal file
|
After Width: | Height: | Size: 1004 B |
BIN
umn/source/_static/images/en-us_image_0000002089584348.png
Normal file
|
After Width: | Height: | Size: 1004 B |
BIN
umn/source/_static/images/en-us_image_0000002089584360.png
Normal file
|
After Width: | Height: | Size: 1004 B |
BIN
umn/source/_static/images/en-us_image_0000002089584372.png
Normal file
|
After Width: | Height: | Size: 1004 B |
BIN
umn/source/_static/images/en-us_image_0000002089584376.png
Normal file
|
After Width: | Height: | Size: 1004 B |
BIN
umn/source/_static/images/en-us_image_0000002090740630.png
Normal file
|
After Width: | Height: | Size: 5.8 KiB |
BIN
umn/source/_static/images/en-us_image_0000002121850428.png
Normal file
|
After Width: | Height: | Size: 128 B |
BIN
umn/source/_static/images/en-us_image_0000002122008564.png
Normal file
|
After Width: | Height: | Size: 27 KiB |
BIN
umn/source/_static/images/en-us_image_0000002125143773.png
Normal file
|
After Width: | Height: | Size: 1004 B |
BIN
umn/source/_static/images/en-us_image_0000002125143777.png
Normal file
|
After Width: | Height: | Size: 1004 B |
BIN
umn/source/_static/images/en-us_image_0000002125143785.png
Normal file
|
After Width: | Height: | Size: 1004 B |
BIN
umn/source/_static/images/en-us_image_0000002125143789.png
Normal file
|
After Width: | Height: | Size: 1004 B |
BIN
umn/source/_static/images/en-us_image_0000002157370221.png
Normal file
|
After Width: | Height: | Size: 1004 B |
BIN
umn/source/_static/images/en-us_image_0000002178551392.png
Normal file
|
After Width: | Height: | Size: 146 KiB |
BIN
umn/source/_static/images/en-us_image_0000002445232846.png
Normal file
|
After Width: | Height: | Size: 88 KiB |
BIN
umn/source/_static/images/en-us_image_0000002445430860.png
Normal file
|
After Width: | Height: | Size: 56 KiB |
BIN
umn/source/_static/images/en-us_image_0000002446287918.png
Normal file
|
After Width: | Height: | Size: 20 KiB |
BIN
umn/source/_static/images/en-us_image_0000002446606818.png
Normal file
|
After Width: | Height: | Size: 27 KiB |
BIN
umn/source/_static/images/en-us_image_0000002446788280.png
Normal file
|
After Width: | Height: | Size: 26 KiB |
BIN
umn/source/_static/images/en-us_image_0000002446790368.png
Normal file
|
After Width: | Height: | Size: 71 KiB |
BIN
umn/source/_static/images/en-us_image_0000002449787866.png
Normal file
|
After Width: | Height: | Size: 10 KiB |
BIN
umn/source/_static/images/en-us_image_0000002449789746.png
Normal file
|
After Width: | Height: | Size: 19 KiB |
BIN
umn/source/_static/images/en-us_image_0000002449948666.png
Normal file
|
After Width: | Height: | Size: 46 KiB |
BIN
umn/source/_static/images/en-us_image_0000002449949814.png
Normal file
|
After Width: | Height: | Size: 16 KiB |
BIN
umn/source/_static/images/en-us_image_0000002461583304.png
Normal file
|
After Width: | Height: | Size: 51 KiB |
BIN
umn/source/_static/images/en-us_image_0000002461680909.png
Normal file
|
After Width: | Height: | Size: 91 KiB |
BIN
umn/source/_static/images/en-us_image_0000002461833813.png
Normal file
|
After Width: | Height: | Size: 1004 B |
BIN
umn/source/_static/images/en-us_image_0000002478587813.png
Normal file
|
After Width: | Height: | Size: 7.8 KiB |
BIN
umn/source/_static/images/en-us_image_0000002479757549.png
Normal file
|
After Width: | Height: | Size: 32 KiB |
BIN
umn/source/_static/images/en-us_image_0000002480095461.png
Normal file
|
After Width: | Height: | Size: 31 KiB |
BIN
umn/source/_static/images/en-us_image_0000002482863093.png
Normal file
|
After Width: | Height: | Size: 101 KiB |
BIN
umn/source/_static/images/en-us_image_0000002483026245.png
Normal file
|
After Width: | Height: | Size: 18 KiB |
@ -0,0 +1,20 @@
|
||||
:original_name: cc_gcn_0000.html
|
||||
|
||||
.. _cc_gcn_0000:
|
||||
|
||||
Central Networks
|
||||
================
|
||||
|
||||
- :ref:`Overview <cc_03_1010>`
|
||||
- :ref:`Central Networks <cc_03_1020>`
|
||||
- :ref:`Policies <cc_03_1030>`
|
||||
- :ref:`Cross-Site Connection Bandwidths <cc_03_1050>`
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
:hidden:
|
||||
|
||||
overview
|
||||
central_networks
|
||||
policies
|
||||
cross-site_connection_bandwidths
|
||||
@ -0,0 +1,69 @@
|
||||
:original_name: cc_03_1010.html
|
||||
|
||||
.. _cc_03_1010:
|
||||
|
||||
Overview
|
||||
========
|
||||
|
||||
Central Network
|
||||
---------------
|
||||
|
||||
Relying on the cloud backbone network, a central network allows you to easily set up a reliable, intelligent enterprise-grade network and manage global network resources on premises and on the cloud. By setting up a central network, you can enable communication between enterprise routers, in the same region or different regions.
|
||||
|
||||
Application Scenarios
|
||||
---------------------
|
||||
|
||||
- Cross-region communication on the cloud: Enterprise routers in different regions are added to a central network as attachments so that resources in these regions can communicate with each other over one network.
|
||||
|
||||
|
||||
.. figure:: /_static/images/en-us_image_0000002445430860.png
|
||||
:alt: **Figure 1** Cross-region communication between enterprise routers
|
||||
|
||||
**Figure 1** Cross-region communication between enterprise routers
|
||||
|
||||
- Global network: By flexibly changing the central network policies, you can build a global network more conveniently.
|
||||
|
||||
Central Network Constraints
|
||||
---------------------------
|
||||
|
||||
- To use a central network, the following resources must have been created:
|
||||
|
||||
- Enterprise router: used to set up a central network
|
||||
|
||||
.. note::
|
||||
|
||||
If you are not the owner of an enterprise router, you cannot use the enterprise router to set up a central network.
|
||||
|
||||
- Policy management
|
||||
|
||||
- A central network can only have one policy. If you apply another policy for this central network, the policy that was previously applied will be automatically cancelled.
|
||||
- In each policy, only one enterprise router can be added for a region. All added enterprise routers can communicate with each other by default.
|
||||
- A policy that is being applied or cancelled cannot be deleted.
|
||||
|
||||
- Cross-site connection bandwidth management
|
||||
|
||||
- A cross-site connection bandwidth cannot be changed or deleted when it is being created, updated, deleted, frozen, unfrozen, or is recovering.
|
||||
- The total of cross-site connection bandwidths cannot exceed the global connection bandwidth.
|
||||
- If a cross-site connection bandwidth is deleted, you will still be billed for the global connection bandwidth.
|
||||
|
||||
Configuration Process
|
||||
---------------------
|
||||
|
||||
:ref:`Figure 2 <cc_03_1010__fig1846518181211>` shows the process of configuring a central network to manage global network resources.
|
||||
|
||||
.. _cc_03_1010__fig1846518181211:
|
||||
|
||||
.. figure:: /_static/images/en-us_image_0000002478587813.png
|
||||
:alt: **Figure 2** Central network configuration process
|
||||
|
||||
**Figure 2** Central network configuration process
|
||||
|
||||
.. table:: **Table 1** Steps for configuring a central network
|
||||
|
||||
+-----+-----------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------+
|
||||
| No. | Step | Description | Reference |
|
||||
+=====+=========================================+=================================================================================================================================================================================================================================================================================+=======================================================================================+
|
||||
| 1 | Create a central network. | After an enterprise router is created, you can create a central network and add the enterprise router to a policy of the central network. In this way, resources can communicate with each other across regions, and network resources in each region can be managed centrally. | :ref:`Creating a Central Network <cc_03_1020__section2954341203415>` |
|
||||
+-----+-----------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------+
|
||||
| 2 | Assign cross-site connection bandwidth. | After adding enterprise routers in different regions to the same policy, purchase a global connection bandwidth and assign a bandwidth for cross-site connections. | :ref:`Assigning a Cross-Site Connection Bandwidth <cc_03_1050__section6858346105817>` |
|
||||
+-----+-----------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------+
|
||||
@ -0,0 +1,97 @@
|
||||
:original_name: cc_03_1030.html
|
||||
|
||||
.. _cc_03_1030:
|
||||
|
||||
Policies
|
||||
========
|
||||
|
||||
Scenarios
|
||||
---------
|
||||
|
||||
Policies record the enterprises routers that have been added to a central network to allow you to better manage your network. You can apply policies of any version.
|
||||
|
||||
Constraints
|
||||
-----------
|
||||
|
||||
- A central network can only have one policy. If you apply another policy for this central network, the policy that was previously applied will be automatically cancelled.
|
||||
- In each policy, only one enterprise router can be added for a region. All added enterprise routers can communicate with each other by default.
|
||||
- A policy that is being applied or cancelled cannot be deleted.
|
||||
|
||||
Creating a Policy
|
||||
-----------------
|
||||
|
||||
#. Log in to the management console.
|
||||
|
||||
#. Click |image1| in the upper left corner to select a region and a project.
|
||||
|
||||
#. In the service list, choose **Network** > **Cloud Connect**.
|
||||
|
||||
#. In the navigation pane on the left, choose **Cloud Connect** > **Central Networks**.
|
||||
|
||||
#. Locate the central network and click its name.
|
||||
|
||||
#. On the **Policies** tab, click **Add Policy**.
|
||||
|
||||
#. Select the target region and enterprise router in that region.
|
||||
|
||||
You can click **Add Enterprise Router** to add an enterprise router in another region.
|
||||
|
||||
|
||||
.. figure:: /_static/images/en-us_image_0000002446287918.png
|
||||
:alt: **Figure 1** Creating a policy
|
||||
|
||||
**Figure 1** Creating a policy
|
||||
|
||||
#. Click **OK**.
|
||||
|
||||
Applying a Policy
|
||||
-----------------
|
||||
|
||||
#. Log in to the management console.
|
||||
|
||||
#. Click |image2| in the upper left corner to select a region and a project.
|
||||
|
||||
#. In the service list, choose **Network** > **Cloud Connect**.
|
||||
|
||||
#. In the navigation pane on the left, choose **Cloud Connect** > **Central Networks**.
|
||||
|
||||
#. Locate the central network and click its name.
|
||||
|
||||
#. On the **Policies** tab, locate the policy you want to apply and click **Apply** on the right.
|
||||
|
||||
|
||||
.. figure:: /_static/images/en-us_image_0000002483026245.png
|
||||
:alt: **Figure 2** Applying a policy
|
||||
|
||||
**Figure 2** Applying a policy
|
||||
|
||||
#. In the **Policy Changes** area on the right, check the change of the enterprise router in the policy.
|
||||
|
||||
#. Click **OK**.
|
||||
|
||||
Deleting a Policy
|
||||
-----------------
|
||||
|
||||
#. Log in to the management console.
|
||||
|
||||
#. Click |image3| in the upper left corner to select a region and a project.
|
||||
|
||||
#. In the service list, choose **Network** > **Cloud Connect**.
|
||||
|
||||
#. In the navigation pane on the left, choose **Cloud Connect** > **Central Networks**.
|
||||
|
||||
#. Locate the central network and click its name.
|
||||
|
||||
#. On the **Policies** tab, locate the policy you want to delete and click **Delete** on the right.
|
||||
|
||||
|
||||
.. figure:: /_static/images/en-us_image_0000002449787866.png
|
||||
:alt: **Figure 3** Deleting a policy
|
||||
|
||||
**Figure 3** Deleting a policy
|
||||
|
||||
#. In the displayed dialog box, click **OK**.
|
||||
|
||||
.. |image1| image:: /_static/images/en-us_image_0000002089584376.png
|
||||
.. |image2| image:: /_static/images/en-us_image_0000002125143785.png
|
||||
.. |image3| image:: /_static/images/en-us_image_0000002089584372.png
|
||||
@ -0,0 +1,39 @@
|
||||
:original_name: cc_03_1103.html
|
||||
|
||||
.. _cc_03_1103:
|
||||
|
||||
Adding Instances to a Global Connection Bandwidth
|
||||
=================================================
|
||||
|
||||
Scenarios
|
||||
---------
|
||||
|
||||
Central networks can use global connection bandwidths for communication.
|
||||
|
||||
Constraints
|
||||
-----------
|
||||
|
||||
- Instances that can be added to a global connection bandwidth must be from the same region as the bandwidth.
|
||||
- A global connection bandwidth can only be used by instances of the same type. If you want another type of instances to use a global connection bandwidth that already has instances, you need to remove the instances first.
|
||||
|
||||
- You can bind one global connection bandwidth to or unbind it from a central network at a time.
|
||||
|
||||
- To use a global connection bandwidth on a central network, you need to configure cross-site connections by referring to the following:
|
||||
|
||||
- :ref:`Central Networks <cc_03_1020>`
|
||||
- :ref:`Policies <cc_03_1030>`
|
||||
|
||||
Using a Global Connection Bandwidth on a Central Network
|
||||
--------------------------------------------------------
|
||||
|
||||
#. Log in to the management console.
|
||||
#. Click |image1| in the upper left corner to select a region and a project.
|
||||
#. In the service list, choose **Network** > **Cloud Connect**.
|
||||
#. In the navigation pane on the left, choose **Cloud Connect** > **Central Networks**.
|
||||
#. In the central network list, click the name of the target central network.
|
||||
#. Click the **Cross-Site Connection Bandwidths** tab.
|
||||
#. Locate the cross-site connection and click **Assign now** in the **Global Connection Bandwidth** column.
|
||||
#. On the **Assign Bandwidth** page, select the global connection bandwidth.
|
||||
#. Specify the bandwidth and click **OK**.
|
||||
|
||||
.. |image1| image:: /_static/images/en-us_image_0000002089104752.png
|
||||
@ -0,0 +1,82 @@
|
||||
:original_name: cc_03_1102.html
|
||||
|
||||
.. _cc_03_1102:
|
||||
|
||||
Creating a Global Connection Bandwidth
|
||||
======================================
|
||||
|
||||
Scenarios
|
||||
---------
|
||||
|
||||
This section describes how to create a global connection bandwidth for communication over the backbone network.
|
||||
|
||||
Procedure
|
||||
---------
|
||||
|
||||
#. Log in to the management console.
|
||||
|
||||
#. Click |image1| in the upper left corner to select a region and a project.
|
||||
|
||||
#. In the service list, choose **Network** > **Cloud Connect**.
|
||||
|
||||
#. In the navigation pane on the left, choose **Intra-Cloud** > **Global Connection Bandwidths**.
|
||||
|
||||
#. Click **Create Global Connection Bandwidth**.
|
||||
|
||||
#. Configure the parameters based on :ref:`Table 1 <cc_03_1102__table9908161616>`.
|
||||
|
||||
|
||||
.. figure:: /_static/images/en-us_image_0000002480095461.png
|
||||
:alt: **Figure 1** Creating a global connection bandwidth
|
||||
|
||||
**Figure 1** Creating a global connection bandwidth
|
||||
|
||||
.. _cc_03_1102__table9908161616:
|
||||
|
||||
.. table:: **Table 1** Parameters required for creating a global connection bandwidth
|
||||
|
||||
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| Parameter | Description |
|
||||
+===================================+===========================================================================================================================================================+
|
||||
| Bandwidth Type | Mandatory |
|
||||
| | |
|
||||
| | Only geographic-region bandwidths are supported. You need to select a geographic region and specify the regions that need to communicate with each other. |
|
||||
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| Geographic Region | Only **Europe** is supported if **Geographic-region** is selected for **Bandwidth Type**. |
|
||||
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| Connect Regions | Regions that need to communicate with each other in a geographic region. |
|
||||
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| Billed By | Mandatory |
|
||||
| | |
|
||||
| | The price of a global connection bandwidth varies by its size. |
|
||||
| | |
|
||||
| | - After a bandwidth is purchased, the billing starts immediately regardless of whether the bandwidth is used. |
|
||||
| | - If a bandwidth is no longer required, delete it in a timely manner to avoid unnecessary fees. |
|
||||
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| Bandwidth | Mandatory |
|
||||
| | |
|
||||
| | Select the bandwidth, in Mbit/s. |
|
||||
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| Bandwidth Name | Mandatory |
|
||||
| | |
|
||||
| | Enter the name of the bandwidth. The name: |
|
||||
| | |
|
||||
| | - Must contain 1 to 64 characters. |
|
||||
| | - Can contain letters, digits, underscores (_), hyphens (-), and periods (.). |
|
||||
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| Enterprise Project | Mandatory |
|
||||
| | |
|
||||
| | Provides a cloud resource management mode, in which cloud resources and members are centrally managed by project. |
|
||||
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
|
||||
#. Click **Next**.
|
||||
|
||||
#. Confirm the configurations and click **Submit**.
|
||||
|
||||
The global connection bandwidth list page is displayed.
|
||||
|
||||
#. In the global connection bandwidth list, view the status of the bandwidth.
|
||||
|
||||
If the bandwidth status becomes **Normal**, the creation is successful.
|
||||
|
||||
.. |image1| image:: /_static/images/en-us_image_0000002089264608.png
|
||||
@ -0,0 +1,28 @@
|
||||
:original_name: cc_03_1106.html
|
||||
|
||||
.. _cc_03_1106:
|
||||
|
||||
Deleting a Global Connection Bandwidth
|
||||
======================================
|
||||
|
||||
Scenarios
|
||||
---------
|
||||
|
||||
If a pay-per-use global connection bandwidth is no longer needed, delete the bandwidth in a timely manner to avoid extra expenditures.
|
||||
|
||||
Constraints
|
||||
-----------
|
||||
|
||||
If a global connection bandwidth is in use by instances, it cannot be deleted. Remove the instances from the global connection bandwidth first.
|
||||
|
||||
Procedure
|
||||
---------
|
||||
|
||||
#. Log in to the management console.
|
||||
#. Click |image1| in the upper left corner to select a region and a project.
|
||||
#. In the service list, choose **Network** > **Cloud Connect**.
|
||||
#. In the navigation pane on the left, choose **Intra-Cloud** > **Global Connection Bandwidths**.
|
||||
#. Locate the global connection bandwidth you want to delete and click **Delete** in the **Operation** column.
|
||||
#. In the displayed dialog box, click **OK**.
|
||||
|
||||
.. |image1| image:: /_static/images/en-us_image_0000002461833813.png
|
||||
@ -0,0 +1,24 @@
|
||||
:original_name: cc_gpb_0000.html
|
||||
|
||||
.. _cc_gpb_0000:
|
||||
|
||||
Global Connection Bandwidths
|
||||
============================
|
||||
|
||||
- :ref:`Overview <cc_03_1101>`
|
||||
- :ref:`Creating a Global Connection Bandwidth <cc_03_1102>`
|
||||
- :ref:`Adding Instances to a Global Connection Bandwidth <cc_03_1103>`
|
||||
- :ref:`Removing Instances from a Global Connection Bandwidth <cc_03_1104>`
|
||||
- :ref:`Modifying a Global Connection Bandwidth <cc_03_1105>`
|
||||
- :ref:`Deleting a Global Connection Bandwidth <cc_03_1106>`
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
:hidden:
|
||||
|
||||
overview
|
||||
creating_a_global_connection_bandwidth
|
||||
adding_instances_to_a_global_connection_bandwidth
|
||||
removing_instances_from_a_global_connection_bandwidth
|
||||
modifying_a_global_connection_bandwidth
|
||||
deleting_a_global_connection_bandwidth
|
||||
@ -0,0 +1,27 @@
|
||||
:original_name: cc_03_1105.html
|
||||
|
||||
.. _cc_03_1105:
|
||||
|
||||
Modifying a Global Connection Bandwidth
|
||||
=======================================
|
||||
|
||||
Scenarios
|
||||
---------
|
||||
|
||||
This section describes how to modify a global connection bandwidth.
|
||||
|
||||
You can only modify the bandwidth name and bandwidth. If you modify the bandwidth, the new bandwidth takes effect immediately.
|
||||
|
||||
|
||||
Modifying a Global Connection Bandwidth
|
||||
---------------------------------------
|
||||
|
||||
#. Log in to the management console.
|
||||
#. Click |image1| in the upper left corner to select a region and a project.
|
||||
#. In the service list, choose **Network** > **Cloud Connect**.
|
||||
#. In the navigation pane on the left, choose **Intra-Cloud** > **Global Connection Bandwidths**.
|
||||
#. Locate the global connection bandwidth and click **Modify Bandwidth** in the **Operation** column.
|
||||
#. On the **Modify Global Connection Bandwidth** page, modify the bandwidth name and bandwidth and click **Next**.
|
||||
#. Confirm the information and click **Submit**.
|
||||
|
||||
.. |image1| image:: /_static/images/en-us_image_0000002089264612.png
|
||||
@ -0,0 +1,46 @@
|
||||
:original_name: cc_03_1101.html
|
||||
|
||||
.. _cc_03_1101:
|
||||
|
||||
Overview
|
||||
========
|
||||
|
||||
Global Connection Bandwidth
|
||||
---------------------------
|
||||
|
||||
A global connection bandwidth is used by instances to allow communication over the backbone network.
|
||||
|
||||
.. table:: **Table 1** Global connection bandwidth types
|
||||
|
||||
+-------------------+-----------------+-------------------------------------------------------------------------------------+--------------------------------------------------------------------------------+
|
||||
| Bandwidth Type | Instance Type | Description | Scenario |
|
||||
+===================+=================+=====================================================================================+================================================================================+
|
||||
| Geographic-region | Central network | Select this type of bandwidth if you need communication within a geographic region. | Enterprise routers on a central network must be in the same geographic region. |
|
||||
+-------------------+-----------------+-------------------------------------------------------------------------------------+--------------------------------------------------------------------------------+
|
||||
|
||||
Constraints on Global Connection Bandwidths
|
||||
-------------------------------------------
|
||||
|
||||
- Instances that can be added to a global connection bandwidth must be in the same region as the bandwidth.
|
||||
- A global connection bandwidth can only be used by instances of the same type. If you want another type of instances to use a global connection bandwidth that already has instances, you need to remove the instances first.
|
||||
- To use a global connection bandwidth on a central network, you need to configure cross-site connections by referring to the following:
|
||||
|
||||
- :ref:`Central Networks <cc_03_1020>`
|
||||
- :ref:`Policies <cc_03_1030>`
|
||||
|
||||
- Before an instance is removed from a global connection bandwidth, ensure the instance is not used to run workloads or establish network connectivity, or the workloads will be unavailable or the network will be interrupted.
|
||||
- If a global connection bandwidth has been used to assign cross-site connection bandwidths for a central network, the global connection bandwidth cannot be unbound from the central network. You need to delete the cross-site connection bandwidths first.
|
||||
- If a global connection bandwidth is in use by instances, it cannot be deleted.
|
||||
|
||||
Geographic-Region Bandwidth Application Scenario (Central Network)
|
||||
------------------------------------------------------------------
|
||||
|
||||
In this example, enterprise routers are connected over a central network.
|
||||
|
||||
Enterprise router ER-A in Germany and enterprise router ER-B in Netherlands are from the same geographic region, so a geographic-region bandwidth can be used for communication between the two enterprise routers.
|
||||
|
||||
|
||||
.. figure:: /_static/images/en-us_image_0000002482863093.png
|
||||
:alt: **Figure 1** Cross-region communication between enterprise routers
|
||||
|
||||
**Figure 1** Cross-region communication between enterprise routers
|
||||
@ -0,0 +1,32 @@
|
||||
:original_name: cc_03_1104.html
|
||||
|
||||
.. _cc_03_1104:
|
||||
|
||||
Removing Instances from a Global Connection Bandwidth
|
||||
=====================================================
|
||||
|
||||
Scenarios
|
||||
---------
|
||||
|
||||
You can unbind a global connection bandwidth from a central network.
|
||||
|
||||
Constraints
|
||||
-----------
|
||||
|
||||
- Before an instance is removed from a global connection bandwidth, the instance is not used to run workloads or establish network connectivity, or the workloads will be unavailable or the network will be interrupted.
|
||||
- A global connection bandwidth can only be used by one type of instances. If you want to change the instance type, remove all the instances from the global connection bandwidth and then add instances of another type by referring to :ref:`Adding Instances to a Global Connection Bandwidth <cc_03_1103>`.
|
||||
- If a global connection bandwidth has been used to assign cross-site connection bandwidths for a central network, the global connection bandwidth cannot be unbound from the central network. You need to delete the cross-site connection bandwidths first.
|
||||
|
||||
Deleting Cross-Site Connection Bandwidth
|
||||
----------------------------------------
|
||||
|
||||
#. Log in to the management console.
|
||||
#. Click |image1| in the upper left corner to select a region and a project.
|
||||
#. In the service list, choose **Network** > **Cloud Connect**.
|
||||
#. In the navigation pane on the left, choose **Cloud Connect** > **Central Networks**.
|
||||
#. In the central network list, click the name of the target central network.
|
||||
#. Click the **Cross-Site Connection Bandwidths** tab.
|
||||
#. Locate the cross-site connection and click **Delete Bandwidth** in the **Operation** column.
|
||||
#. In the displayed dialog box, click **OK**.
|
||||
|
||||
.. |image1| image:: /_static/images/en-us_image_0000002089104748.png
|
||||