A lot of my devices are set to use the relay list server mechanism. Because of this the port 1610 is overloaded sometimes. How can I resolve this?

A new port could be dedicated to the relay list server, before going further make sure the port 1614 (or the port number you chose to use) make sure the port 1614 is opened on the network, else the following configuration will not work.

1- Set a new port to listen to:
On the master and/or on any device that is set as an active Relay List Server in Global Settings > Relay Lists:
- Go into the BCM agent installation folder then to ../config for a Windows device or ../etc for a linux device
- Duplicate the file HttpProtocolHandler.ini file
- Rename the duplicated file as RelayList.ini.
- Edit the file HttpProtocolHandler.ini and add ",RelayList" in the "VirtualHosts=" parameter. If it is set to the default, it should look like this: "VirtualHosts=Console,AdvertisedUsers,RelayList"
- Edit the new file RelayList.ini file and update the following parameters values (or use another port): - Restart the BCM service (BMC Client Management Agent)
From now the BCM agent of the relay list server is also listening on the port 1614.

2- Modify the rollout configurations:
Modify your current Rollout configurations in order to set the new "1614" port for the Relay List server(s), so the next BCM agents use it:



3- Update the configuration of the existing devices:
Modify the configuration of the existing BCM agents, in order to have them using the new port for the Relay List server requests:
- Create an operational rule and add the steps:

3.1 Update INI File:



Replace <Relay List server IP> by the IP or the hostname of the Relay List server that is to be added to the targets Relay.ini before going next.

3.2: "Restart BCM agent"
If this step is not added then the new setting will only be set at the next restart of the agent.

3.3: Assign the operational rule
Assign it to a couple of devices first, make sure it works well, then assign it to a wider scale.