- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2025 12:26 PM
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2025 06:36 AM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2025 12:33 PM
Make sure they are equal in applications ,ip ranges and capabilities.. thats what its checking for
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2025 06:36 AM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-11-2025 07:22 AM - edited 08-11-2025 07:34 AM
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.