-
1. Re: Enable MESH feature in Tuner
Which version of BBCA are you having in production? You need to enable these properties only on workstations that are to be MESH enabled. The bcast.addr property is not needed as it would be included by default. I don't think that the system would perform peer download of patches, as patch management uses an altogether different mechanism of deployment, in contrast to package deployment.
-
2. Re: Enable MESH feature in Tuner
Hi Adil,
I have BBCA 8.2.00 installed.
So does you mean only below properties to be applied to workstations that are only part of MESH enabled tuner ?
marimba.tuner.p2p.enabled=true
update.vary=true
update.vary.max=30
and remaining machines will contact MESH enabled tuner to receive package before thay contact master/mirror tx ?
-
3. Re: Enable MESH feature in Tuner
The workstations on which these properties are enabled would be able to request and fetch MESH peer to peer downloads. The rest of the workstations would not participate in MESH.
-
4. Re: Enable MESH feature in Tuner
you should enable mesh in the area that affected only from my view. The site you enable mesh would contact the local clients before contact the repeater or Master.
-
5. Re: Enable MESH feature in Tuner
Agree...I have more than 100+ low bandwidth locations with 10-15 endpoints. So seems I should enable MESH on all Tuners.
Tuners with MESH would contact local clients and remaining clients will contact master or repeater for update even after MESH enabled on those locations ?
-
6. Re: Enable MESH feature in Tuner
Tuner with MESH would first check the peer workstations, and in case the peer workstations do not have the content, then they will go to the master transmitter which would redirect them to the assigned repeater...