Configuring Cross-CIDR Access
If your client and the replica set instance are deployed in different CIDR blocks and the client CIDR is not 192.168.0.0/16, 172.16.0.0/24, or 10.0.0.0/8 , you can configure cross-CIDR access to enable access.
This section describes how to configure cross-CIDR access for an instance.
Precautions
- Only replica set instances support this function.
- During the configuration of cross-CIDR access, services are running properly without interruption or intermittent disconnection.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click in the upper left corner of the page and choose Databases > Document Database Service.
- On the Instances page, click the instance name.
- In the navigation pane on the left, choose Connections.
- On the Private Connection tab, click Enable to the right of Cross-CIDR Access. You can add or delete the blocks as required.
- Click to add new CIDR blocks.
- Click to delete existing CIDR blocks.
Figure 1 Cross-CIDR Access
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. The CIDR blocks cannot start with 127. The allowed IP mask ranges from 8 to 32.
- View the change results. 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.
Figure 2 Changing a CIDR block
Follow-up Operations
After cross-CIDR access is configured, you can use MongoShell to connect to a replica set instance over a private network. For details, see Connecting to a Cluster Instance Using Mongo Shell.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.