Central Servers: Master and Node addresses (Standard Edition)
The persistent outbound connection mechanism connects over HTTPS to one of three global region servers depending upon the N-sight RMM (Dashboard) territory, designated Australia, Europe and the United States.
Type |
Address |
---|---|
Master Format |
region-master.rbm.system-monitor.com |
Node Format |
region-node-Version-NodeNumber.rbm.system-monitor.com |
Node Example |
us-node-1-4-33.rbm.system-monitor.com |
Region |
APAC |
Territory |
Asia, Australia |
Master |
anz-master.rbm.system-monitor.com |
Nodes |
anz-node-Version-NodeNumber.rbm.system-monitor.com |
Region |
Europe |
Territory |
Europe, France, France1, Germany, Ireland, Poland, United Kingdom |
Master |
emea-master.rbm.system-monitor.com |
Nodes |
emea-node-Version-NodeNumber.rbm.system-monitor.com |
Region |
United States, Americas |
Territory |
United States, Americas |
Master |
us-master.rbm.system-monitor.com |
Nodes |
us-node-Version-NodeNumber.rbm.system-monitor.com |
In the majority of cases the Agent will connect to the servers without problem, but where firewall rules are in place restricting outbound HTTPS connections it may be necessary to permit access to the URL: *.rbm.system-monitor.com
Connection Troubleshooting
Where the Agent cannot connect to the master server this is reported in debugrbm.log found in the Advanced Monitoring Agent installation folder (by default C:\Program Files (x86)\Advanced Monitoring Agent). For example:
dd-mm-yyyy hh:mm:ss: winagent(3564): CRBMConnectionManager::queryMasterServerForNodeServerDetails: error getting RBM Node Server details from master server
dd-mm-yyyy hh:mm:ss: winagent(3564): CRBMConnectionManager::runConnectorLoop: unable to retrieve node details from master server
To verify this error.
- Log into the computer using the same user account as the Advanced Monitoring Agent Service
- Open a browser
- Attempt to navigate to the master server URL references in debugrbm.log
- Success: the browser returns a blank page
- Failure: the browser returns an error message
What do you want to do?
- View Remote Background Manager's System Requirements
- Review Standard and Advanced Edition features
- Identify devices running Remote Background Manager
- Enable Remote Background Manager on the target devices