Scenario
Integrate Portal on the External Network with ADS M on the Internal Network.
Required Ports
The Portal has a dedicated public IP address. ADS M intranet uses a single public egress IP for external connectivity, and any access to the public network must go through this IP.
To establish a connection between Portal and ADS M, the following ports are required:
| Device | Direction | Device | Port | Service |
| ADSM | –> | Portal | 22 | SSH |
| ADSM | –> | Portal | 873 | rsync |
| Portal | –> | ADSM | 5432 | Database |
| Portal | –> | ADSM | 443 | HTTPS |
To enable data transfer between ADS M Portal and ADS M, the following ports should be opened: 22 and 873 on the Portal side, and 5432 on the ADSM side. Additionally, a DNAT rule must be configured on the gateway to map port 443 of ADSM to the corresponding port on the public IP.
Integration IP
During the deployment of Portal, ADS M automatically writes its IP into the Portal’s configuration file. However, as ADS M and the Portal are not on the same network, the Portal cannot directly access this IP, resulting in no alert messages and inability to query reports. To resolve this, the configuration file needs to be modified in the backend. Follow these steps:
1. Login to the Portal backend as root and view the configuration file.
2. Edit the configuration file using a text editor like nano or vi, for example: “nano /opt/portal/etc/portal.conf” or “vi /opt/portal/etc/portal.conf”.
3. Change the IP after “adsm_address=” to the public IP after ADS M mapping. Save the file by pressing Ctrl-O and exit the editor by pressing Ctrl-X.
- Restart web services.
After completing these steps, the Portal will be integrated normally with ADS M.
