- Welcome BMC Customer Support Site Guest User
Knowledge Article
Client Management: Improve Internet / DMZ / VPN communication and limit "Queue Full" on Relays
DMZ Relay can be overloaded by Client connections. As a result, they do not accept any more connections and log files are full of "Queue Full" messages.
BMC Client Management
Client Management
BMC Client Management (BCM) <= 12.9
Communications between the DMZ Relay(s) and its children is unstable. DMZ Relay(s) ../log/mtxagent.log are full of "Queue Full" messages, how can it be resolved ? What is causing the issue ? How to set the DMZ Relay to manage communications with its children better? How to set Client to manage communications with the DMZ Relay(s) better? |
Connections in the WAN are usually less stable than in the LAN and the default communication timeout settings are not optimized for this as an Out Of the Box
The following has to be updated on DMZ Relays because communication in the WAN are less stable. It would most likely not apply to a Master or a Relay that have children in the LAN only. The reason is that it sets bigger timeouts to communication, implying that if a communication stops during a remote control as an example the disconnection will not be available for retry for a longer duration. This could have a negative impact in the LAN even if there are little chances it does. Parameters have to be modified both on the DMZ Relay and its children. 1- Manual settings: These are recommended parameters : 1.1 On the relay: Go to ../client/config on a Windows Server relay, or to ../client/etc for linux and edit the following files: - Relay.ini set:
ParentResyncCount=5
ParentResyncInterval=120 - mtxagent.ini set: DefaultTimeout=30
DefaultConnectTimeout=30 (Recommended value for WAN connection) ConnectionQueueMaxSize=50 TunnelTimeout=120 - HttpProtocoHandler.ini set: MaxThreads=150 (This is a maximum value)
- In Console.ini set: MaxThreads=200
1.2 On Clients: - Make sure the relevant Relay selection mechanisms have been set on the client configurations and on the rollout configurations used to deploy the clients - This is done in the files ../client/config/Relay.ini (Windows) / ../client/etc/Relay.ini (Linux) and in Agent Configuration > Communication - Go to ../client/config on a Windows Server Relay, or to ../client/etc for Linux and edit the following files: - Relay.ini set:
ParentTunnel=1 (Not mandatory in case of temporary connection to DMZ Relay)
ParentResyncCount=5 ParentResyncInterval=120 ParentCheckInterval=3600 ParentReselectInterval=3600 (Mandatory as soon as more than one mechanism is set to find out Relay) ParentSelectInterval=3600 - mtxagent.ini set: DefaultTimeout=30
DefaultConnectTimeout=30 (Recommended value for WAN connection) TunnelTimeout=120 2- Deploy the new configurations in mass: Operational rules exports are attached to this Knowledge Article (KA). To import them, follow this KA: https://community.bmc.com/s/article/Client-Management-How-to-export-and-import-objects-in-the-console The operational rule "Relay parameters for DMZ or Low speed connections" must be assigned to relays: The operational rule "Client parameters for DMZ or Low speed connections" must be assigned to clients: Note: There might be queue full messages in the logs because the relay has too many children: Client Management: Check if the parent does not have too many children (queue full) |