Can you please tell me how the HUBs populate or even decided on the “Source”, see below and does this relate to the “Route” or “Next Hop”?
Your understanding is correct.
If remote HUB is communicated directly, you don't see any value in [source] column.
If remote HUB is communicated through another HUB (like proxying behavior) you see value in the column.
If you similar with Network devices, UIM HUB behavior is similar from neighbors concept point of view.
The HUB information is being shared with the other HUB. The other HUB shares that with another HUB.
If you are in 3 tier HUB installation, the Primary UIM Server connects to location dedicated HUB through proxy role HUB.
In this case, source for the location dedicated HUB is proxy role HUB. You also see the number in it. It represents for how many hops is expected in the communication.
Do you mind if I ask you to review the comment, then mark the question answered (assumed answered) if you are satisfied with the response ?
This is what we thought the entry meant.
What we have noticed is that our remote HUBs next hop seems to always be our “Discovery Servers”. The Discovery Server has the “discovery queues” to each remote HUB and each remote HUB has a Qos & Alarm queue to our Central MGMT Servers. (i.e. Queues out of the remote HUBs in 2 directions) I suspect our environment is confusing the remote HUBs and they are just picking a next hop “out of the air” as they have queues to MGMT & Discovery Servers.
Is there any way to force the “next hop” to be our main MGMT Servers? Or does it even matter?
Retrieving data ...