Forum Discussion
Weight Vs Score for Topology Records
The terms "weight" and "score" are synonymous. "Weight" is used in the Configuration utility (GUI) and "score" is used in TMSH. But they refer to the same thing.
During name resolution, the weight/score is a value that is given to the destination object in the topology record when the request source matches. (See below for more on the matching process). In the event of multiple matches, BIG-IP DNS uses the destination object with the greatest weight/score to load balance the query to.
Keep in mind that, when using topology load balancing at either the wide IP or pool level, BIG-IP DNS only searches those topology records that are applicable to that wide IP or pool. Also, you have to take into consideration whether Longest Match is enabled or not. (It is by default.) In most cases, a set of topology records define mutually exclusive LDNS sets (request sources) so that the decision is clear. But when the set of topology records contains overlapping DNS, it is important to know the details of the systems' matching process. (I won't go into that here...)
The net takeaway though is this: In the event the matching process produces more than one topology record match, the destination object with the highest weight/score is the object the query will be load balanced to.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
