Multicast not working - Use JDBC Ping as Best Practice
search cancel

Multicast not working - Use JDBC Ping as Best Practice


Article ID: 212647


Updated On:


Clarity PPM On Premise Clarity PPM SaaS


On the environment, multicast is not working, unable to see all the servers listed in the CSA, also notice process delays. 

Possible symptoms:

  • security.logs / CSA / NSA server dropdown does not show all nodes in the cluster, unable to access the logs
  • The command: admin tower does not list all nodes/services
  • Processes not starting or completing, delayed, or launching multiple times
  • There is a problem with the multicast communication and the IT team has been unable to solve it on this environment/ infrastructure 


Release : Any Supported Release


  • Broadcom Support recommends using JDBC Ping as alternative to Multicast
  • JDBC Ping is the new technology, whilst Multicast is the legacy technology
  • As such JDBCPing is recommended and preferred for use as best practice
  • This will work for AWS, DMZ, Azure, different subnets and other environments that do not allow multicast
  • For detailed instruction on how to configure JDBC Ping, check the Broadcom documentation

Additional Information

Ensure the ports are opened as follows: JDBC Ping/Multicast ports used for beacon