Network Domain
Last updated: 2025-04-18 10:43:27
Overview
Installing the bh-gateway-client in different network environments enables unified management of IDC private network assets, other cloud platform private network assets, and public network assets.
Directions
Network Domain Purchase
After the successful deployment of the BH instance, a default network domain is created. The default network domain corresponds to the VPC where the instance is deployed.
If additional networks are required, users should first purchase a network domain expansion package.
1. Log in to the BH console.
2. In the left sidebar, choose Activate Package > Service List.
3. On the Service List page, locate the instance for which you need to adjust the network domain. Click More > Adjust Network Domain on the right-hand side of the instance.
4. In the Adjust Network Domain popup, purchase the required number of network domains based on your needs.
Network Domain Configuration
1. Log in to the BH console.
2. In the left sidebar, choose Activate Package > Network Domain.
3. On the Network Domain page, click Create, to enter a popup for creating a network domain.
4. In the New Network Domain popup, configure the required parameters, and then click OK.
Parameter Name | Details |
Access BH resource ID | The BH instance to which this network domain belongs. When assets are bound to this BH instance and network domain, the BH will initiate connections through the client of this network domain. |
Network domain name | The name displayed in the network domain and asset sections. It is recommended to use a descriptive name that reflects the environment of this network domain. |
IP | The public IP allowlist that permits the network domain client (bh-gateway-client) to connect to the BH instance. You can configure a single IP or CIDR range, with one entry per line. Multiple IPs should belong to the same network (either within the same VPC or local area network). |
Client Installation
After configuring the network domain, it will initially be in a disconnected status. You need to download the installation script and deploy it within the target network domain on one or more servers that can access the BH's public IP.
Note
The client of a network domain can be installed on one or more servers within the same network domain to provide services. It is recommended to configure at least two servers to ensure high availability. Ensure that the client is not installed across different network domains, which could lead to some servers being accessible and others not.
The client script should be installed on a Linux machine.
1. Log in to the BH console.
2. In the left sidebar, choose Activate Package > Network Domain.
3. Select the network domain for which you want to perform the installation, and click Download Installation Script in the operation column.
4. Upload the installation script to the server, and execute the script.
5. Check whether the client starts normally by running
ps aux | grep bh_gateway_client.
6. View the
/var/log/tsecbh/bh_gateway.log log file to determine if the client is successfully connected to the BH instance.
7. Refresh the Network Domain page in the console. The status of the network domain should now display as Enabled.
Asset Configuration
Note
When binding assets to a BH instance, you should specify the associated network domain. If the asset and the BH instance are in the same VPC, select the default network domain of the asset.
For assets in other network domains, configure the network domain based on actual conditions.
1. Log in to the BH console.
2. In the left sidebar, choose Asset Mgmt > Servers.
3. On the Servers page, select the host asset requiring a network domain configuration and click Host Assets.
4. In the Host Assets popup, configure the network domain as needed, and click OK.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback