2.3.4.138 has helped a lot!

[woodsy]

But! I have in the process of updating the system i have replaced 2 hubs.
Restored the original databases, rebooted.
Having a hard time getting them to back online with hubmesh.
Hub IP's are appropriate on the settings/hubmesh pages.
Worse than that, i have done this several times, and have apparently forgotten the trick.
I know there is a way, just cannot remember it.
Darn system runs dependably enough, i dont get enough practice...

Thanks.

[thebearmay]

Generally if you give HubMesh a few minutes to exchange data everything will come back online. Do note that all hubs will need to be on .138 due to recent changes.

[woodsy]

Yes to both points, @thebearmay.
24 hours had passed.
The .138 release notes i did read and heed.
In the process i changed 2xC4 to 2xC7.
Restored .123 databases.
These are the 2 that are not "meshing".
I have done similar in the past.
All are on .138.

AND: thank you for hubinfo. Many thank you's.

[danabw]

Tagging @support_team....

[gopher.ny]

Are the hubs on the same /24 network, with only last IP address different?
There's a way to "seed" hub mesh manually in .138, too. Use this endpoint to tell the hub where other hubs are:
http://hubs.ip.address.here/hub/advanced/setInitialHubMeshPeers?192.168.1.2,192.168.1.2

To reset, use:
http://hubs.ip.address.here/hub/advanced/setInitialHubMeshPeers?none

[woodsy]

Yes, same switch/net.

I will try your suggestion this evening.

Where you have 192.168.1.2 twice, do i put all the hub IPs there?

Thanks!

[gopher.ny]

@woodsy

Where you have 192.168.1.2 twice, do i put all the hub IPs there?

Yes, comma separated.
They will also share information about other nodes they "know" about, e.g. if hub A sees hub B, and hub B seees hub C, B should share the location of C to A.