Tuning Check error: T021-MID cluster configuration should be identical - Discovery Admin Workspace

[HeyMarkWarmack]

Hello Discovery Admins - 

On the Discovery Admin Workspace, I am trying to resolve the T021 tuning check error under the 'Discovery tuning advice' at the bottom.

High - T021-MID cluster configuration should be identical

One of my Clusters, with four of my MID Server instances (on one VM server) are in this error. I reduced it to two servers and checked all the settings.

The error description says to look at Supported applications, ip ranges and capabilities.  I have looked and looked, search Docs and can NOT find any additional information on the T021 error and how to find issue and resolve.

I did have different IP Ranges and I made the two servers with the same list.

The caveat is they are not in the exact order, I tried to re-add and it will not let me add the exact order for each MID.  I have removed and re-added several times and they never end up in the same order.  Don't think it matters but it SEEMS like this is the only difference.

[doug_schulze]

Make sure they are equal in applications ,ip ranges and capabilities.. thats what its checking for

[HeyMarkWarmack]

Doug - I have reduced the cluster to two MIDs and have done a deep compare and they seem same to me.  The only difference is the order of the IP Ranges, but they contain the same set.  See below for example.   

The documentation is good in describing what the cluster is doing but not on this specific error, other than the 3 areas (tabs) to check.

                                    MID1                           MID2

Applications                 ALL (all 18)                ALL (all 18 MIDs)

IP Ranges (examples)  10.1.1.0/24                  10.3.1.0/22

                                     10.2.1.0/24                  10.1.1.0/24

                                     10.3.1.0/22                 10.2.1.0/24

Capabilities                  ALL                             ALL

Any suggestions would be appreciated. 

[HeyMarkWarmack]

UPDATE:  The weekly Tuning Check jobs ran naturally and the T021 Error cleared with just the two MIDs with the corrected IP Ranges that were made the same.   ORDER UNDER IP RANGES DOES NOT IMPACT TUNING CHECK.

That was my root issue, mismatched IP Ranges that were probably OK back in a previous version but now fail the check in Yokohama now.

[HeyMarkWarmack]

Update 11/3/25:  I was able to keep three [3] of the four [4] MID Server instances in the Cluster without throwing the T021 error.  When I add the fourth one it throws the error on the health check; same Supported Applications = ALL, Capabilities = ALL and seven IP Ranges are all the same.

I do not see anything in the logs about the health check that would tell me what the difference is in the fourth MID.

Putting in SN Case.....