Ghost Peer to Peer multicast imaging randomly fails
Last Updated January 07, 2019
When using the Peer to Peer multicasting built into Ghost (using -mp switch), client machines will randomly drop out of the multicast
GSS 3.x and DS 8.x
Ghost doesn't provide any logs that help to determine what is causing the issue.
By default, the client systems (slave systems) wait one second to receive data from the master system (the one in charge of the multicast session). If a response is not received within that second, the client systems fail-over to unicast.
The issue can be worked around by adding the parameter '-readtimeout' to the command line and giving it a value of '-2'. E.g '-readtimeout=2'. This command tells the client to wait '2' seconds for the master to respond before dropping into a unicast session. This value can be raised further should the issue continue to occur.
Steps to add the switch:
Add '-readtimeout=2' to the imaging jobs command line parameters
Select the Deploy image task
Click on the 'Advanced' Button
Under command line options enter '-readtimeout=2'
Click 'Save Changes'
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe