![multicast ping tool multicast ping tool](https://networklessons.com/wp-content/uploads/2018/02/multicast-tunnel-rpf-failure-topology-example.png)
In some cases, Linux distributions do not have multicast enabled by default and the /etc/hosts file does not include the IP address associated with the server's hostname. It will save some CPU activity performed continuously. If you can't have multicast enabled within your network you should disable it on the client side and on the service grid side. The GSC count should be added to the commands above above as usual. Machines not running the lookup service should have their agent started using: gs-agent You should use only local lookup service configuration with the agent with the machines running the lookup service: gs-agent -lus=1 -gsm=1 When multicast is disabled global lookup service should not be use. Client locators should have the same list used. This means if the lookup service fails (very low probably to happen) you will be able to start it only on the machines listed on the GS_LOOKUP_LOCATORS list. Disabling multicast discovery means you are loosing dynamicy for the lookup service location. Multicast is not used with replication, notification, monitoring or any client activity against the space. Both are turned on by default on the client side and on the service grid side (GSM,GSC,LUS). It is used as a secondary mechanism for lookup service discovery. Multicast is not a mandatory with GigaSpaces.
#Multicast ping tool how to
You should use multicast replication when having more than 10 clients acting as replica spaces per target space.įor information on how to disable the Jini Lookup Service Multicast announcements, see the Multicast Settings section of the Lookup Service Configuration page. Space cluster replication uses unicast by default.
![multicast ping tool multicast ping tool](https://hackstips.files.wordpress.com/2011/12/untitled13.png)