hubinfo_update messages show high proximity values in hub log
Article ID: 424377
Updated On:
Products
Issue/Introduction
In the hub.log there are messages which contain "proximity" values that seem very high.
The proximity value reflects how many "hops" away the hubs are from each other (or how many "middleman" hubs the traffic would pass through when traversing between two hubs).
This value should never be higher than the total number of "levels" of hubs, for example:
Primary hub->Tunnel Server->Tunnel Client
Between the primary hub and tunnel client there is one "middleman" hub (the tunnel server), so the proximity between Tunnel Client and Primary Hub is 1.
However some messages are seen which reflect values that seem exceptionally high, for example:
hubinfo_update - for /Domain/Hubname/robotname/hub from (ip address)/(port) proximity 174 higher than current 125, ignore update
Environment
DX UIM - 23.4.3 or earlier
Cause
unknown
Resolution
This condition has been seen very rarely, but ordinarily if it does occur, it should resolve itself within minutes as the hub will accept updates to the route from other hubs which have a shorter proximity and ignore updates with the same or higher proximity, so this message can be ignored.
Over time, the hub will eventually settle on the shortest possible route between any two given hubs, as each time a lower proximity route is discovered, it will overwrite a higher proximity route.
The amount of time this takes depends on the number of "tiers" of hub tunnels; it will take up to 10 minutes per "tier" for the hub routes to update. So on a 4-tier environment (e.g. Primary hub->Tunnel Server->Tunnel Client->Sub-Client) allow 40 minutes for the route to be corrected.
If a lower proximity route is not discovered over time this may indicate that the hub with the high proximity is not properly communicating with the hub(s) above it - for example a tunnel client that is having trouble connecting to the tunnel server. Once the hub is able to communicate, the routes will be updated appropriately.
Therefore, if this issue is seen, the first thing to investigate will be whether or not the hub in question (the one showing the high proximity value) is appropriately communicating with its nearest hub. For example, if the hub is a tunnel client, check whether it is connecting successfully to the tunnel server, and look for communication errors/hubup failures/tunnel disconnections which may indicate a communication problem with the tunnel server.
Additional Information
Feedback
