lboka/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
doc-exports/docs/dds/umn/dds_03_0100.html
Wang , Deng Ke ba65944bfd Added version 4.2. 
Reviewed-by: Boka, Ladislav <ladislav.boka@t-systems.com>
Co-authored-by: Wang , Deng Ke <wangdengke2@huawei.com>
Co-committed-by: Wang , Deng Ke <wangdengke2@huawei.com>
2023-07-11 13:21:20 +00:00

3.6 KiB
Raw Blame History

Configuring Cross-CIDR Access for Replica Set Instances

If a client and a replica set instance are deployed in different CIDR blocks and the client is not in 192.168.0.0/16, 172.16.0.0/24, or 10.0.0.0/8, configure Cross-CIDR Access for the instance to communicate with the client.

Precautions

  • During the configuration of cross-CIDR access, services are running properly without interruption or intermittent disconnection.
  • If the client and replica set instance are in different VPCs and CIDR blocks, configure a VPC peering connection by referring to VPC Peering Connection in Virtual Private Cloud User Guide.

Procedure

  1. Log in to the DDS console.
  2. On the Instance Management page, click the target replica set instance.
  3. In the navigation pane on the left, choose Connections.
  4. On the Address area, click Enable to the right of Cross-CIDR Access and specify the client CIDR block details.

    Up to 30 CIDR blocks can be configured, and each of them can overlap but they cannot be the same. That is, the source CIDR blocks can overlap but cannot be the same.

  5. After cross-CIDR access is enabled, Enabled is displayed to the right of Cross-CIDR Access.

    If you need to change the client CIDR block, click Change to the right of Cross-CIDR Access.

    • To ensure the ECS and the DB instance can communicate with each other, configure the connection by referring to section "VPC Peering Connection Overview" in the Virtual Private Cloud User Guide.

Parent topic: Connection Management