forked from docs/virtual-private-cloud
Compare commits
3 Commits
main
...
propose-vp
| Author | SHA1 | Date | |
|---|---|---|---|
| bb9de6c778 | |||
| a67520a9de | |||
| c76420195d |
Binary file not shown.
|
Before Width: | Height: | Size: 16 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 19 KiB |
BIN
umn/source/_static/images/en-us_image_0000001865582789.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001865582789.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 28 KiB |
BIN
umn/source/_static/images/en-us_image_0000001865582793.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001865582793.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 13 KiB |
BIN
umn/source/_static/images/en-us_image_0000001865662813.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001865662813.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 5.4 KiB |
BIN
umn/source/_static/images/en-us_image_0000001865674836.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001865674836.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 79 KiB |
BIN
umn/source/_static/images/en-us_image_0000001865684752.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001865684752.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 29 KiB |
BIN
umn/source/_static/images/en-us_image_0000001865828728.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001865828728.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 86 KiB |
BIN
umn/source/_static/images/en-us_image_0000001865833004.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001865833004.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 80 KiB |
BIN
umn/source/_static/images/en-us_image_0000001865837676.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001865837676.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 93 KiB |
BIN
umn/source/_static/images/en-us_image_0000001865884494.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001865884494.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 96 KiB |
BIN
umn/source/_static/images/en-us_image_0000001865898552.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001865898552.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 143 KiB |
BIN
umn/source/_static/images/en-us_image_0000001866046474.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001866046474.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 12 KiB |
BIN
umn/source/_static/images/en-us_image_0000001866063864.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001866063864.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 64 KiB |
BIN
umn/source/_static/images/en-us_image_0000001911771617.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001911771617.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 64 KiB |
BIN
umn/source/_static/images/en-us_image_0000001911842313.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001911842313.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 33 KiB |
BIN
umn/source/_static/images/en-us_image_0000001911849797.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001911849797.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 125 KiB |
BIN
umn/source/_static/images/en-us_image_0000001911853289.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001911853289.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 32 KiB |
@ -27,5 +27,11 @@ Procedure
|
||||
|
||||
6. On the displayed page, click the **Inbound Rules**, **Outbound Rules**, and **Associated Subnets** tabs one by one to view details about inbound rules, outbound rules, and subnet associations.
|
||||
|
||||
|
||||
.. figure:: /_static/images/en-us_image_0000001865684752.png
|
||||
:alt: **Figure 1** Viewing a firewall
|
||||
|
||||
**Figure 1** Viewing a firewall
|
||||
|
||||
.. |image1| image:: /_static/images/en-us_image_0000001818982734.png
|
||||
.. |image2| image:: /_static/images/en-us_image_0000001865662773.png
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -29,5 +29,11 @@ Procedure
|
||||
|
||||
You can view the security groups associated with the ECS and the inbound and outbound rules.
|
||||
|
||||
|
||||
.. figure:: /_static/images/en-us_image_0000001911842313.png
|
||||
:alt: **Figure 1** View the security group of an ECS
|
||||
|
||||
**Figure 1** View the security group of an ECS
|
||||
|
||||
.. |image1| image:: /_static/images/en-us_image_0000001818982734.png
|
||||
.. |image2| image:: /_static/images/en-us_image_0000001818982866.png
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -13,10 +13,7 @@ If your security group rule is no longer required, you can delete it.
|
||||
Notes and Constraints
|
||||
---------------------
|
||||
|
||||
Security group rules use whitelists. Deleting a security group rule may result in ECS access failures. Security group rules work as follows:
|
||||
|
||||
- Inbound rule: If an inbound request matches the source in an inbound security group rule with **Action** set to **Allow**, the request is allowed.
|
||||
- Outbound rule: If the destination of an outbound security group rule with **Action** set to **Allow** is 0.0.0.0/0, all outbound requests are allowed.
|
||||
Security group rules use whitelists. Deleting a security group rule may result in ECS access failures.
|
||||
|
||||
Procedure
|
||||
---------
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -19,6 +19,8 @@ Notes and Constraints
|
||||
|
||||
- The security group rules to be imported must be configured based on the template. Do not add parameters or change existing parameters. Otherwise, the import will fail.
|
||||
- Duplicate rules are not allowed, you can delete the rule and try again.
|
||||
- If you want to import rules of the security group in one region to another under one account, only rules with both **Source** and **Destination** set to **IP address** can be applied.
|
||||
- If you want to import rules of the security group in one account to the security group in another account, only rules with both **Source** and **Destination** set to **IP address** can be applied.
|
||||
|
||||
Procedure
|
||||
---------
|
||||
@ -51,42 +53,41 @@ Procedure
|
||||
|
||||
.. table:: **Table 1** Template parameters
|
||||
|
||||
+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------+
|
||||
| Parameter | Description | Example Value |
|
||||
+=======================+====================================================================================================================================================================================================================================================================================================================================================================================================================+====================================+
|
||||
| Direction | The direction in which the security group rule takes effect. | Inbound |
|
||||
| | | |
|
||||
| | - **Inbound**: Inbound rules control incoming traffic to instances in the security group. | |
|
||||
| | - **Outbound**: Outbound rules control outgoing traffic from instances in the security group. | |
|
||||
+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------+
|
||||
| Protocol & Port | The network protocol used to match traffic in a security group rule. | TCP |
|
||||
| | | |
|
||||
| | Currently, the value can be **All**, **TCP**, **UDP**, **GRE**, **ICMP**, or more. | |
|
||||
+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------+
|
||||
| | **Port**: The port or port range over which traffic can reach your ECS. The value can be from 1 to 65535. | 22, or 22-30 |
|
||||
+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------+
|
||||
| Type | Source IP address version. You can select: | IPv4 |
|
||||
| | | |
|
||||
| | - IPv4 | |
|
||||
| | - IPv6 | |
|
||||
+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------+
|
||||
| Source | Source of the security group rule. The value can be an IP address, a security group, or an IP address group to allow access from IP addresses or instances in the security group. For example: | sg-test[96a8a93f-XXX-d7872990c314] |
|
||||
| | | |
|
||||
| | - IP address: | |
|
||||
| | | |
|
||||
| | - Single IP address: 192.168.10.10/32 | |
|
||||
| | - All IP addresses: 0.0.0.0/0 | |
|
||||
| | - IP address range: 192.168.1.0/24 | |
|
||||
| | | |
|
||||
| | - **Security group**: The source is from another security group. You can select a security group in the same region under the current account from the drop-down list. Instance A is in security group A and instance B is in security group B. If security group A has an inbound rule with **Action** set to **Allow** and **Source** set to security group B, access from instance B is allowed to instance A. | |
|
||||
| | - **IP address group**: The source is an IP address group. An IP address group is a collection of one or more IP addresses. You can select an available IP address group from the drop-down list. An IP address group can help you manage IP address ranges and IP addresses with same security requirements in a more simple way. | |
|
||||
+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------+
|
||||
| Destination | Destination of the security group rule. The value can be an IP address or a security group to allow access to IP addresses or instances in the security group. For example: | sg-test[96a8a93f-XXX-d7872990c314] |
|
||||
+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------+
|
||||
| Description | (Optional) Supplementary information about the security group rule. | ``-`` |
|
||||
| | | |
|
||||
| | The route description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | |
|
||||
+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------+
|
||||
+-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------+
|
||||
| Parameter | Description | Example Value |
|
||||
+=======================+===============================================================================================================================================================================================================================================================================================================================================================+====================================+
|
||||
| Direction | The direction in which the security group rule takes effect. | Inbound |
|
||||
| | | |
|
||||
| | - **Inbound**: Inbound rules control incoming traffic to instances in the security group. | |
|
||||
| | - **Outbound**: Outbound rules control outgoing traffic from instances in the security group. | |
|
||||
+-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------+
|
||||
| Protocol & Port | The network protocol used to match traffic in a security group rule. | TCP |
|
||||
| | | |
|
||||
| | Currently, the value can be **All**, **TCP**, **UDP**, **GRE**, **ICMP**, or more. | |
|
||||
+-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------+
|
||||
| | **Port**: The port or port range over which traffic can reach your ECS. The value can be from 1 to 65535. | 22, or 22-30 |
|
||||
+-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------+
|
||||
| Type | Source IP address version. You can select: | IPv4 |
|
||||
| | | |
|
||||
| | - IPv4 | |
|
||||
| | - IPv6 | |
|
||||
+-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------+
|
||||
| Source | Source of the security group rule. The value can be an IP address or a security group to allow access from IP addresses or instances in the security group. | sg-test[96a8a93f-XXX-d7872990c314] |
|
||||
| | | |
|
||||
| | - IP address: | |
|
||||
| | | |
|
||||
| | - Single IP address: 192.168.10.10/32 | |
|
||||
| | - All IP addresses: 0.0.0.0/0 | |
|
||||
| | - IP address range: 192.168.1.0/24 | |
|
||||
| | | |
|
||||
| | - **Security group**: The source is from another security group. You can select a security group in the same region from the drop-down list. If there is instance A in security group A and instance B in security group B, and the inbound rule of security group A allows traffic from security group B, traffic is allowed from instance B to instance A. | |
|
||||
+-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------+
|
||||
| Destination | Destination of the security group rule. The value can be an IP address or a security group to allow access to IP addresses or instances in the security group. | sg-test[96a8a93f-XXX-d7872990c314] |
|
||||
+-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------+
|
||||
| Description | (Optional) Supplementary information about the security group rule. | ``-`` |
|
||||
| | | |
|
||||
| | The route description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | |
|
||||
+-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------+
|
||||
|
||||
.. |image1| image:: /_static/images/en-us_image_0000001818982734.png
|
||||
.. |image2| image:: /_static/images/en-us_image_0000001865582585.png
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@ -81,27 +81,27 @@ Assigning an EIP
|
||||
|
||||
.. table:: **Table 2** EIP tag requirements
|
||||
|
||||
+-----------------------+---------------------------------------------------------------------+-----------------------+
|
||||
| Parameter | Requirement | Example Value |
|
||||
+=======================+=====================================================================+=======================+
|
||||
| Key | - Cannot be left blank. | Ipv4_key1 |
|
||||
| | - The key value must be unique for the same EIP. | |
|
||||
| | - Can contain up to 36 characters. | |
|
||||
| | - Can contain only the following character types: | |
|
||||
| | | |
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Special characters, including hyphens (-) and underscores (_) | |
|
||||
+-----------------------+---------------------------------------------------------------------+-----------------------+
|
||||
| Value | - Can contain up to 43 characters. | 3005eip |
|
||||
| | - Can contain only the following character types: | |
|
||||
| | | |
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Special characters, including hyphens (-) and underscores (_) | |
|
||||
+-----------------------+---------------------------------------------------------------------+-----------------------+
|
||||
+-----------------------+------------------------------------------------------------------------+-----------------------+
|
||||
| Parameter | Requirement | Example Value |
|
||||
+=======================+========================================================================+=======================+
|
||||
| Key | - Cannot be left blank. | Ipv4_key1 |
|
||||
| | - The key value must be unique for the same EIP. | |
|
||||
| | - Can contain up to 36 characters. | |
|
||||
| | - Can contain only the following character types: | |
|
||||
| | | |
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Only hyphens (-), underscores (_), and at signs (@) are allowed. | |
|
||||
+-----------------------+------------------------------------------------------------------------+-----------------------+
|
||||
| Value | - Can contain up to 43 characters. | 3005eip |
|
||||
| | - Can contain only the following character types: | |
|
||||
| | | |
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Only underscores (_), hyphens (-), and at signs (@) are allowed. | |
|
||||
+-----------------------+------------------------------------------------------------------------+-----------------------+
|
||||
|
||||
#. Click **Create Now**.
|
||||
|
||||
@ -122,7 +122,7 @@ Binding an EIP
|
||||
|
||||
#. Click **OK**.
|
||||
|
||||
An IPv6 client on the Internet can access the ECS that has an EIP bound in a VPC. For details, see :ref:`How Does an IPv6 Client on the Internet Access the ECS That Has an EIP Bound in a VPC? <vpc_faq_0076>`
|
||||
An IPv6 client on the internet can access the ECS that has an EIP bound in a VPC. For details, see `How Does an IPv6 Client on the Internet Access the ECS That Has an EIP Bound in a VPC? <https://docs.otc.t-systems.com/virtual-private-cloud/umn/faq/connectivity/how_does_an_ipv6_client_on_the_internet_access_the_ecs_that_has_an_eip_bound_in_a_vpc.html#vpc-faq-0076>`__
|
||||
|
||||
Follow-Up Procedure
|
||||
-------------------
|
||||
@ -131,7 +131,7 @@ After an ECS with an EIP bound is created, the system generates a domain name in
|
||||
|
||||
You can use any of the following commands to obtain the domain name of an EIP:
|
||||
|
||||
- ping -a *EIP*
|
||||
- ping -an *EIP*
|
||||
- nslookup [-qt=ptr] *EIP*
|
||||
- dig -x *EIP*
|
||||
|
||||
|
||||
@ -16,27 +16,27 @@ A tag consists of a key and value pair. :ref:`Table 1 <en-us_topic_0068145818__t
|
||||
|
||||
.. table:: **Table 1** EIP tag requirements
|
||||
|
||||
+-----------------------+---------------------------------------------------------------------+-----------------------+
|
||||
| Parameter | Requirement | Example Value |
|
||||
+=======================+=====================================================================+=======================+
|
||||
| Key | - Cannot be left blank. | Ipv4_key1 |
|
||||
| | - Must be unique for each EIP. | |
|
||||
| | - Can contain a maximum of 36 characters. | |
|
||||
| | - Can contain only the following character types: | |
|
||||
| | | |
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Special characters, including hyphens (-) and underscores (_) | |
|
||||
+-----------------------+---------------------------------------------------------------------+-----------------------+
|
||||
| Value | - Can contain a maximum of 43 characters. | 3005eip |
|
||||
| | - Can contain only the following character types: | |
|
||||
| | | |
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Special characters, including hyphens (-) and underscores (_) | |
|
||||
+-----------------------+---------------------------------------------------------------------+-----------------------+
|
||||
+-----------------------+------------------------------------------------------------------------+-----------------------+
|
||||
| Parameter | Requirement | Example Value |
|
||||
+=======================+========================================================================+=======================+
|
||||
| Key | - Cannot be left blank. | Ipv4_key1 |
|
||||
| | - Must be unique for each EIP. | |
|
||||
| | - Can contain a maximum of 36 characters. | |
|
||||
| | - Can contain only the following character types: | |
|
||||
| | | |
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Only hyphens (-), underscores (_), and at signs (@) are allowed. | |
|
||||
+-----------------------+------------------------------------------------------------------------+-----------------------+
|
||||
| Value | - Can contain a maximum of 43 characters. | 3005eip |
|
||||
| | - Can contain only the following character types: | |
|
||||
| | | |
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Only underscores (_), hyphens (-), and at signs (@) are allowed. | |
|
||||
+-----------------------+------------------------------------------------------------------------+-----------------------+
|
||||
|
||||
Procedure
|
||||
---------
|
||||
|
||||
@ -1,8 +0,0 @@
|
||||
:original_name: vpc_faq_0063.html
|
||||
|
||||
.. _vpc_faq_0063:
|
||||
|
||||
How Many Routes Can a Route Table Contain?
|
||||
==========================================
|
||||
|
||||
Currently, a route table can contain 100 routes.
|
||||
@ -0,0 +1,8 @@
|
||||
:original_name: vpc_faq_0063.html
|
||||
|
||||
.. _vpc_faq_0063:
|
||||
|
||||
How Many Routes Can I Add to a Route Table?
|
||||
===========================================
|
||||
|
||||
A maximum of 200 routes can be added to each route table.
|
||||
@ -5,7 +5,7 @@
|
||||
Routing
|
||||
=======
|
||||
|
||||
- :ref:`How Many Routes Can a Route Table Contain? <vpc_faq_0063>`
|
||||
- :ref:`How Many Routes Can I Add to a Route Table? <vpc_faq_0063>`
|
||||
- :ref:`Are There Any Restrictions on Using a Route Table? <vpc_faq_0064>`
|
||||
- :ref:`Do the Same Routing Priorities Apply to Direct Connect Connections and Custom Routes in the Same VPC? <vpc_faq_0066>`
|
||||
- :ref:`Are There Different Routing Priorities of the VPN and Custom Routes in the Same VPC? <vpc_faq_00001>`
|
||||
@ -14,7 +14,7 @@ Routing
|
||||
:maxdepth: 1
|
||||
:hidden:
|
||||
|
||||
how_many_routes_can_a_route_table_contain
|
||||
how_many_routes_can_i_add_to_a_route_table
|
||||
are_there_any_restrictions_on_using_a_route_table
|
||||
do_the_same_routing_priorities_apply_to_direct_connect_connections_and_custom_routes_in_the_same_vpc
|
||||
are_there_different_routing_priorities_of_the_vpn_and_custom_routes_in_the_same_vpc
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -29,6 +29,12 @@ Procedure
|
||||
|
||||
A default subnet will be created together with a VPC and you can also click **Add Subnet** to create more subnets for the VPC.
|
||||
|
||||
|
||||
.. figure:: /_static/images/en-us_image_0000001865837676.png
|
||||
:alt: **Figure 1** Create a VPC and subnet
|
||||
|
||||
**Figure 1** Create a VPC and subnet
|
||||
|
||||
.. table:: **Table 1** VPC parameter descriptions
|
||||
|
||||
+-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
|
||||
@ -108,7 +114,7 @@ Procedure
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Special characters, including hyphens (-) and underscores (_) | |
|
||||
| | - Only hyphens (-), underscores (_), and at signs (@) are allowed. | |
|
||||
+-----------------------+------------------------------------------------------------------------+-----------------------+
|
||||
| Value | - Can contain a maximum of 43 characters. | vpc-01 |
|
||||
| | - Can contain only the following character types: | |
|
||||
@ -116,34 +122,34 @@ Procedure
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Special characters, including hyphens (-) and underscores (_) | |
|
||||
| | - Only underscores (_), hyphens (-), and at signs (@) are allowed. | |
|
||||
+-----------------------+------------------------------------------------------------------------+-----------------------+
|
||||
|
||||
.. _vpc_qs_0009__en-us_topic_0013935842_table6536185812515:
|
||||
|
||||
.. table:: **Table 3** Subnet tag key and value requirements
|
||||
|
||||
+-----------------------+---------------------------------------------------------------------+-----------------------+
|
||||
| Parameter | Requirements | Example Value |
|
||||
+=======================+=====================================================================+=======================+
|
||||
| Key | - Cannot be left blank. | subnet_key1 |
|
||||
| | - Must be unique for each subnet. | |
|
||||
| | - Can contain a maximum of 36 characters. | |
|
||||
| | - Can contain only the following character types: | |
|
||||
| | | |
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Special characters, including hyphens (-) and underscores (_) | |
|
||||
+-----------------------+---------------------------------------------------------------------+-----------------------+
|
||||
| Value | - Can contain a maximum of 43 characters. | subnet-01 |
|
||||
| | - Can contain only the following character types: | |
|
||||
| | | |
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Special characters, including hyphens (-) and underscores (_) | |
|
||||
+-----------------------+---------------------------------------------------------------------+-----------------------+
|
||||
+-----------------------+------------------------------------------------------------------------+-----------------------+
|
||||
| Parameter | Requirements | Example Value |
|
||||
+=======================+========================================================================+=======================+
|
||||
| Key | - Cannot be left blank. | subnet_key1 |
|
||||
| | - Must be unique for each subnet. | |
|
||||
| | - Can contain a maximum of 36 characters. | |
|
||||
| | - Can contain only the following character types: | |
|
||||
| | | |
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Only hyphens (-), underscores (_), and at signs (@) are allowed. | |
|
||||
+-----------------------+------------------------------------------------------------------------+-----------------------+
|
||||
| Value | - Can contain a maximum of 43 characters. | subnet-01 |
|
||||
| | - Can contain only the following character types: | |
|
||||
| | | |
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Only underscores (_), hyphens (-), and at signs (@) are allowed. | |
|
||||
+-----------------------+------------------------------------------------------------------------+-----------------------+
|
||||
|
||||
#. Click **Create Now**.
|
||||
|
||||
|
||||
@ -81,27 +81,27 @@ Procedure
|
||||
|
||||
.. table:: **Table 2** Subnet tag key and value requirements
|
||||
|
||||
+-----------------------+---------------------------------------------------------------------+-----------------------+
|
||||
| Parameter | Requirements | Example Value |
|
||||
+=======================+=====================================================================+=======================+
|
||||
| Key | - Cannot be left blank. | subnet_key1 |
|
||||
| | - Must be unique for each subnet. | |
|
||||
| | - Can contain a maximum of 36 characters. | |
|
||||
| | - Can contain only the following character types: | |
|
||||
| | | |
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Special characters, including hyphens (-) and underscores (_) | |
|
||||
+-----------------------+---------------------------------------------------------------------+-----------------------+
|
||||
| Value | - Can contain a maximum of 43 characters. | subnet-01 |
|
||||
| | - Can contain only the following character types: | |
|
||||
| | | |
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Special characters, including hyphens (-) and underscores (_) | |
|
||||
+-----------------------+---------------------------------------------------------------------+-----------------------+
|
||||
+-----------------------+------------------------------------------------------------------------+-----------------------+
|
||||
| Parameter | Requirements | Example Value |
|
||||
+=======================+========================================================================+=======================+
|
||||
| Key | - Cannot be left blank. | subnet_key1 |
|
||||
| | - Must be unique for each subnet. | |
|
||||
| | - Can contain a maximum of 36 characters. | |
|
||||
| | - Can contain only the following character types: | |
|
||||
| | | |
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Only hyphens (-), underscores (_), and at signs (@) are allowed. | |
|
||||
+-----------------------+------------------------------------------------------------------------+-----------------------+
|
||||
| Value | - Can contain a maximum of 43 characters. | subnet-01 |
|
||||
| | - Can contain only the following character types: | |
|
||||
| | | |
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Only underscores (_), hyphens (-), and at signs (@) are allowed. | |
|
||||
+-----------------------+------------------------------------------------------------------------+-----------------------+
|
||||
|
||||
7. Click **OK**.
|
||||
|
||||
|
||||
@ -81,27 +81,27 @@ Assigning an EIP
|
||||
|
||||
.. table:: **Table 2** EIP tag requirements
|
||||
|
||||
+-----------------------+---------------------------------------------------------------------+-----------------------+
|
||||
| Parameter | Requirement | Example Value |
|
||||
+=======================+=====================================================================+=======================+
|
||||
| Key | - Cannot be left blank. | Ipv4_key1 |
|
||||
| | - The key value must be unique for the same EIP. | |
|
||||
| | - Can contain up to 36 characters. | |
|
||||
| | - Can contain only the following character types: | |
|
||||
| | | |
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Special characters, including hyphens (-) and underscores (_) | |
|
||||
+-----------------------+---------------------------------------------------------------------+-----------------------+
|
||||
| Value | - Can contain up to 43 characters. | 3005eip |
|
||||
| | - Can contain only the following character types: | |
|
||||
| | | |
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Special characters, including hyphens (-) and underscores (_) | |
|
||||
+-----------------------+---------------------------------------------------------------------+-----------------------+
|
||||
+-----------------------+------------------------------------------------------------------------+-----------------------+
|
||||
| Parameter | Requirement | Example Value |
|
||||
+=======================+========================================================================+=======================+
|
||||
| Key | - Cannot be left blank. | Ipv4_key1 |
|
||||
| | - The key value must be unique for the same EIP. | |
|
||||
| | - Can contain up to 36 characters. | |
|
||||
| | - Can contain only the following character types: | |
|
||||
| | | |
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Only hyphens (-), underscores (_), and at signs (@) are allowed. | |
|
||||
+-----------------------+------------------------------------------------------------------------+-----------------------+
|
||||
| Value | - Can contain up to 43 characters. | 3005eip |
|
||||
| | - Can contain only the following character types: | |
|
||||
| | | |
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Only underscores (_), hyphens (-), and at signs (@) are allowed. | |
|
||||
+-----------------------+------------------------------------------------------------------------+-----------------------+
|
||||
|
||||
#. Click **Create Now**.
|
||||
|
||||
@ -122,7 +122,7 @@ Binding an EIP
|
||||
|
||||
#. Click **OK**.
|
||||
|
||||
An IPv6 client on the Internet can access the ECS that has an EIP bound in a VPC. For details, see :ref:`How Does an IPv6 Client on the Internet Access the ECS That Has an EIP Bound in a VPC? <vpc_faq_0076>`
|
||||
An IPv6 client on the internet can access the ECS that has an EIP bound in a VPC. For details, see `How Does an IPv6 Client on the Internet Access the ECS That Has an EIP Bound in a VPC? <https://docs.otc.t-systems.com/virtual-private-cloud/umn/faq/connectivity/how_does_an_ipv6_client_on_the_internet_access_the_ecs_that_has_an_eip_bound_in_a_vpc.html#vpc-faq-0076>`__
|
||||
|
||||
Follow-Up Procedure
|
||||
-------------------
|
||||
@ -131,7 +131,7 @@ After an ECS with an EIP bound is created, the system generates a domain name in
|
||||
|
||||
You can use any of the following commands to obtain the domain name of an EIP:
|
||||
|
||||
- ping -a *EIP*
|
||||
- ping -an *EIP*
|
||||
- nslookup [-qt=ptr] *EIP*
|
||||
- dig -x *EIP*
|
||||
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@ -29,6 +29,12 @@ Procedure
|
||||
|
||||
A default subnet will be created together with a VPC and you can also click **Add Subnet** to create more subnets for the VPC.
|
||||
|
||||
|
||||
.. figure:: /_static/images/en-us_image_0000001865837676.png
|
||||
:alt: **Figure 1** Create a VPC and subnet
|
||||
|
||||
**Figure 1** Create a VPC and subnet
|
||||
|
||||
.. table:: **Table 1** VPC parameter descriptions
|
||||
|
||||
+-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
|
||||
@ -108,7 +114,7 @@ Procedure
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Special characters, including hyphens (-) and underscores (_) | |
|
||||
| | - Only hyphens (-), underscores (_), and at signs (@) are allowed. | |
|
||||
+-----------------------+------------------------------------------------------------------------+-----------------------+
|
||||
| Value | - Can contain a maximum of 43 characters. | vpc-01 |
|
||||
| | - Can contain only the following character types: | |
|
||||
@ -116,34 +122,34 @@ Procedure
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Special characters, including hyphens (-) and underscores (_) | |
|
||||
| | - Only underscores (_), hyphens (-), and at signs (@) are allowed. | |
|
||||
+-----------------------+------------------------------------------------------------------------+-----------------------+
|
||||
|
||||
.. _vpc_qs_0005__en-us_topic_0013935842_table6536185812515:
|
||||
|
||||
.. table:: **Table 3** Subnet tag key and value requirements
|
||||
|
||||
+-----------------------+---------------------------------------------------------------------+-----------------------+
|
||||
| Parameter | Requirements | Example Value |
|
||||
+=======================+=====================================================================+=======================+
|
||||
| Key | - Cannot be left blank. | subnet_key1 |
|
||||
| | - Must be unique for each subnet. | |
|
||||
| | - Can contain a maximum of 36 characters. | |
|
||||
| | - Can contain only the following character types: | |
|
||||
| | | |
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Special characters, including hyphens (-) and underscores (_) | |
|
||||
+-----------------------+---------------------------------------------------------------------+-----------------------+
|
||||
| Value | - Can contain a maximum of 43 characters. | subnet-01 |
|
||||
| | - Can contain only the following character types: | |
|
||||
| | | |
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Special characters, including hyphens (-) and underscores (_) | |
|
||||
+-----------------------+---------------------------------------------------------------------+-----------------------+
|
||||
+-----------------------+------------------------------------------------------------------------+-----------------------+
|
||||
| Parameter | Requirements | Example Value |
|
||||
+=======================+========================================================================+=======================+
|
||||
| Key | - Cannot be left blank. | subnet_key1 |
|
||||
| | - Must be unique for each subnet. | |
|
||||
| | - Can contain a maximum of 36 characters. | |
|
||||
| | - Can contain only the following character types: | |
|
||||
| | | |
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Only hyphens (-), underscores (_), and at signs (@) are allowed. | |
|
||||
+-----------------------+------------------------------------------------------------------------+-----------------------+
|
||||
| Value | - Can contain a maximum of 43 characters. | subnet-01 |
|
||||
| | - Can contain only the following character types: | |
|
||||
| | | |
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Only underscores (_), hyphens (-), and at signs (@) are allowed. | |
|
||||
+-----------------------+------------------------------------------------------------------------+-----------------------+
|
||||
|
||||
#. Click **Create Now**.
|
||||
|
||||
|
||||
@ -81,27 +81,27 @@ Procedure
|
||||
|
||||
.. table:: **Table 2** Subnet tag key and value requirements
|
||||
|
||||
+-----------------------+---------------------------------------------------------------------+-----------------------+
|
||||
| Parameter | Requirements | Example Value |
|
||||
+=======================+=====================================================================+=======================+
|
||||
| Key | - Cannot be left blank. | subnet_key1 |
|
||||
| | - Must be unique for each subnet. | |
|
||||
| | - Can contain a maximum of 36 characters. | |
|
||||
| | - Can contain only the following character types: | |
|
||||
| | | |
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Special characters, including hyphens (-) and underscores (_) | |
|
||||
+-----------------------+---------------------------------------------------------------------+-----------------------+
|
||||
| Value | - Can contain a maximum of 43 characters. | subnet-01 |
|
||||
| | - Can contain only the following character types: | |
|
||||
| | | |
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Special characters, including hyphens (-) and underscores (_) | |
|
||||
+-----------------------+---------------------------------------------------------------------+-----------------------+
|
||||
+-----------------------+------------------------------------------------------------------------+-----------------------+
|
||||
| Parameter | Requirements | Example Value |
|
||||
+=======================+========================================================================+=======================+
|
||||
| Key | - Cannot be left blank. | subnet_key1 |
|
||||
| | - Must be unique for each subnet. | |
|
||||
| | - Can contain a maximum of 36 characters. | |
|
||||
| | - Can contain only the following character types: | |
|
||||
| | | |
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Only hyphens (-), underscores (_), and at signs (@) are allowed. | |
|
||||
+-----------------------+------------------------------------------------------------------------+-----------------------+
|
||||
| Value | - Can contain a maximum of 43 characters. | subnet-01 |
|
||||
| | - Can contain only the following character types: | |
|
||||
| | | |
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Only underscores (_), hyphens (-), and at signs (@) are allowed. | |
|
||||
+-----------------------+------------------------------------------------------------------------+-----------------------+
|
||||
|
||||
7. Click **OK**.
|
||||
|
||||
|
||||
@ -43,39 +43,37 @@ Procedure
|
||||
|
||||
.. table:: **Table 1** Parameter description
|
||||
|
||||
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+
|
||||
| Parameter | Description | Example Value |
|
||||
+=======================+=======================================================================================================================================================================================================================================================================+============================+
|
||||
| Name | Mandatory | sg-AB |
|
||||
| | | |
|
||||
| | Enter the security group name. | |
|
||||
| | | |
|
||||
| | The security group name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | |
|
||||
| | | |
|
||||
| | .. note:: | |
|
||||
| | | |
|
||||
| | You can change the security group name after a security group is created. It is recommended that you give each security group a different name. | |
|
||||
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+
|
||||
| Enterprise Project | Mandatory | default |
|
||||
| | | |
|
||||
| | When creating a security group, you can add the security group to an enabled enterprise project. | |
|
||||
| | | |
|
||||
| | An enterprise project facilitates project-level management and grouping of cloud resources and users. The name of the default project is **default**. | |
|
||||
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+
|
||||
| Template | Mandatory | General-purpose web server |
|
||||
| | | |
|
||||
| | A template comes with default security group rules, helping you quickly create security groups. The following templates are provided: | |
|
||||
| | | |
|
||||
| | - **Custom**: This template allows you to create security groups with custom security group rules. | |
|
||||
| | - **General-purpose web server** (default value): The security group that you create using this template is for general-purpose web servers and includes default rules that allow all inbound ICMP traffic and allow inbound traffic on ports 22, 80, 443, and 3389. | |
|
||||
| | - **All ports open**: The security group that you create using this template includes default rules that allow inbound traffic on any port. Note that allowing inbound traffic on any port poses security risks. | |
|
||||
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+
|
||||
| Description | Optional | N/A |
|
||||
| | | |
|
||||
| | Supplementary information about the security group. This parameter is optional. | |
|
||||
| | | |
|
||||
| | The security group description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | |
|
||||
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+
|
||||
+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+
|
||||
| Parameter | Description | Example Value |
|
||||
+=======================+================================================================================================================================================================================================================================+============================+
|
||||
| Name | Mandatory | sg-AB |
|
||||
| | | |
|
||||
| | Enter the security group name. | |
|
||||
| | | |
|
||||
| | The security group name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | |
|
||||
| | | |
|
||||
| | .. note:: | |
|
||||
| | | |
|
||||
| | You can change the security group name after a security group is created. It is recommended that you give each security group a different name. | |
|
||||
+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+
|
||||
| Enterprise Project | Mandatory | default |
|
||||
| | | |
|
||||
| | When creating a security group, you can add the security group to an enabled enterprise project. | |
|
||||
| | | |
|
||||
| | An enterprise project facilitates project-level management and grouping of cloud resources and users. The name of the default project is **default**. | |
|
||||
+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+
|
||||
| Template | Mandatory | General-purpose web server |
|
||||
| | | |
|
||||
| | The system provides several security group templates for you to create a security group. A security group template has preconfigured inbound and outbound rules. You can select a template based on your service requirements. | |
|
||||
| | | |
|
||||
| | :ref:`Table 1 <en-us_topic_0013748715__table117828131111>` describes the security group templates. | |
|
||||
+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+
|
||||
| Description | Optional | N/A |
|
||||
| | | |
|
||||
| | Supplementary information about the security group. This parameter is optional. | |
|
||||
| | | |
|
||||
| | The security group description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | |
|
||||
+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+
|
||||
|
||||
#. Confirm the inbound and outbound rules of the template and click **OK**.
|
||||
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -23,6 +23,12 @@ Procedure
|
||||
|
||||
5. On the **Alarm Rules** page, click **Create Alarm Rule** and set required parameters, or modify an existing alarm rule.
|
||||
|
||||
|
||||
.. figure:: /_static/images/en-us_image_0000001865898552.png
|
||||
:alt: **Figure 1** Create an alarm rule
|
||||
|
||||
**Figure 1** Create an alarm rule
|
||||
|
||||
6. After the parameters are set, click **Create**.
|
||||
|
||||
After the alarm rule is created, the system automatically notifies you if an alarm is triggered for the VPC service.
|
||||
|
||||
@ -31,7 +31,7 @@ Procedure
|
||||
5. In the upper right corner, click **Create Route Table**. On the displayed page, configure parameters as prompted.
|
||||
|
||||
|
||||
.. figure:: /_static/images/en-us_image_0000001818983038.png
|
||||
.. figure:: /_static/images/en-us_image_0000001865582789.png
|
||||
:alt: **Figure 1** Create Route Table
|
||||
|
||||
**Figure 1** Create Route Table
|
||||
|
||||
@ -32,7 +32,20 @@ Procedure
|
||||
The route table details page is displayed.
|
||||
|
||||
a. On the **Summary** tab page, view the basic information and routes of the route table.
|
||||
|
||||
|
||||
.. figure:: /_static/images/en-us_image_0000001866063864.png
|
||||
:alt: **Figure 1** View the basic information and routes of the route table
|
||||
|
||||
**Figure 1** View the basic information and routes of the route table
|
||||
|
||||
b. On the **Associated Subnets** tab page, view the subnets associated with the route table.
|
||||
|
||||
|
||||
.. figure:: /_static/images/en-us_image_0000001911853289.png
|
||||
:alt: **Figure 2** View the subnets associated with the route table
|
||||
|
||||
**Figure 2** View the subnets associated with the route table
|
||||
|
||||
.. |image1| image:: /_static/images/en-us_image_0000001818982734.png
|
||||
.. |image2| image:: /_static/images/en-us_image_0000001865582825.png
|
||||
|
||||
@ -31,9 +31,21 @@ Procedure
|
||||
|
||||
6. In the right of the subnet details page, view the route table associated with the subnet.
|
||||
|
||||
|
||||
.. figure:: /_static/images/en-us_image_0000001911849797.png
|
||||
:alt: **Figure 1** View the route table associated with a subnet
|
||||
|
||||
**Figure 1** View the route table associated with a subnet
|
||||
|
||||
7. Click the name of the route table.
|
||||
|
||||
The route table details page is displayed. You can further view the route information.
|
||||
|
||||
|
||||
.. figure:: /_static/images/en-us_image_0000001911771617.png
|
||||
:alt: **Figure 2** View the basic information and routes of the route table
|
||||
|
||||
**Figure 2** View the basic information and routes of the route table
|
||||
|
||||
.. |image1| image:: /_static/images/en-us_image_0000001818982734.png
|
||||
.. |image2| image:: /_static/images/en-us_image_0000001865582701.png
|
||||
|
||||
@ -35,7 +35,7 @@ Procedure
|
||||
You can click **+** to add more routes.
|
||||
|
||||
|
||||
.. figure:: /_static/images/en-us_image_0000001818823258.png
|
||||
.. figure:: /_static/images/en-us_image_0000001865582793.png
|
||||
:alt: **Figure 1** Add Route
|
||||
|
||||
**Figure 1** Add Route
|
||||
@ -45,6 +45,12 @@ Procedure
|
||||
+-----------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------+
|
||||
| Parameter | Description | Example Value |
|
||||
+=======================+======================================================================================================================================================================+========================+
|
||||
| Destination Type | Mandatory | IP address |
|
||||
| | | |
|
||||
| | The destination can be: | |
|
||||
| | | |
|
||||
| | - IP address: single IP address or IP address range | |
|
||||
+-----------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------+
|
||||
| Destination | Mandatory | IPv4: 192.168.0.0/16 |
|
||||
| | | |
|
||||
| | Enter the destination of the route. You can enter a single IP address or an IP address range in CIDR notation. | |
|
||||
|
||||
@ -40,7 +40,13 @@ Procedure
|
||||
+-----------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+
|
||||
| Item | Description | Example Value |
|
||||
+=======================+======================================================================================================================================================================+=======================+
|
||||
| Destination | Mandatory | Pv4: 192.168.0.0/16 |
|
||||
| Destination Type | Mandatory | IP address |
|
||||
| | | |
|
||||
| | The destination can be: | |
|
||||
| | | |
|
||||
| | - **IP address**: Select this option if you want to enter an IP address or IP address range. | |
|
||||
+-----------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+
|
||||
| Destination | Mandatory | IPv4: 192.168.0.0/16 |
|
||||
| | | |
|
||||
| | Enter the destination of the route. You can enter a single IP address or an IP address range in CIDR notation. | |
|
||||
| | | |
|
||||
|
||||
@ -27,6 +27,12 @@ Procedure
|
||||
|
||||
#. Click the **IP Addresses** tab and click **Assign Virtual IP Address**.
|
||||
|
||||
|
||||
.. figure:: /_static/images/en-us_image_0000001866046474.png
|
||||
:alt: **Figure 1** Assign a virtual IP address
|
||||
|
||||
**Figure 1** Assign a virtual IP address
|
||||
|
||||
#. Select an IP address type. This parameter is available only in regions supporting IPv6.
|
||||
|
||||
- IPv4
|
||||
|
||||
@ -81,27 +81,27 @@ Procedure
|
||||
|
||||
.. table:: **Table 2** Subnet tag key and value requirements
|
||||
|
||||
+-----------------------+---------------------------------------------------------------------+-----------------------+
|
||||
| Parameter | Requirements | Example Value |
|
||||
+=======================+=====================================================================+=======================+
|
||||
| Key | - Cannot be left blank. | subnet_key1 |
|
||||
| | - Must be unique for each subnet. | |
|
||||
| | - Can contain a maximum of 36 characters. | |
|
||||
| | - Can contain only the following character types: | |
|
||||
| | | |
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Special characters, including hyphens (-) and underscores (_) | |
|
||||
+-----------------------+---------------------------------------------------------------------+-----------------------+
|
||||
| Value | - Can contain a maximum of 43 characters. | subnet-01 |
|
||||
| | - Can contain only the following character types: | |
|
||||
| | | |
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Special characters, including hyphens (-) and underscores (_) | |
|
||||
+-----------------------+---------------------------------------------------------------------+-----------------------+
|
||||
+-----------------------+------------------------------------------------------------------------+-----------------------+
|
||||
| Parameter | Requirements | Example Value |
|
||||
+=======================+========================================================================+=======================+
|
||||
| Key | - Cannot be left blank. | subnet_key1 |
|
||||
| | - Must be unique for each subnet. | |
|
||||
| | - Can contain a maximum of 36 characters. | |
|
||||
| | - Can contain only the following character types: | |
|
||||
| | | |
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Only hyphens (-), underscores (_), and at signs (@) are allowed. | |
|
||||
+-----------------------+------------------------------------------------------------------------+-----------------------+
|
||||
| Value | - Can contain a maximum of 43 characters. | subnet-01 |
|
||||
| | - Can contain only the following character types: | |
|
||||
| | | |
|
||||
| | - Uppercase letters | |
|
||||
| | - Lowercase letters | |
|
||||
| | - Digits | |
|
||||
| | - Only underscores (_), hyphens (-), and at signs (@) are allowed. | |
|
||||
+-----------------------+------------------------------------------------------------------------+-----------------------+
|
||||
|
||||
7. Click **OK**.
|
||||
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user