[monrog2]

Summary

• fetch all immediate children for the bounded vnsLIfCtx queries instead of requesting a remote redirect class unavailable on APIC 5.2
• preserve local and remote redirect-policy evaluation in the existing client-side logic
• classify APIC code 12 Unknown class responses as unsupported classes

Fixes #486

Evidence

On calo-a APIC 5.2(8i), the Check 105 subtree selector returns code 12: Unknown class vnsRsLIfCtxToRemoteSvcRedirectPol. The same parent query succeeds when the subtree-class projection is omitted.

Testing

• focused unit tests: 43 passed
• full unit suite: 1467 passed

[monrog2]

Focused integration-test results

• Tested commit 1ff8f0e with only Check 105 (service_ep_flag_bd_check) selected.
• All seven integration scenarios invoked the intended focused check.
• The original APIC error, Unknown class vnsRsLIfCtxToRemoteSvcRedirectPol, did not recur.
• The primary validation fabric completed the actual-version Check 105 run with PASS: 1 and ERROR: 0.
• One version-override scenario received a whitespace-only response from the initial vlanCktEp query after approximately 46 seconds, causing a JSON-decoding error. This was unrelated to the subtree-class change and is tracked separately in Handle empty icurl responses before JSON decoding #492.
• The overall integration pipeline remained red because of unrelated required-fabric authentication, timeout, and Python-environment failures. Optional-fabric connection failures were reported as warnings.
• Python 2.7 and Python 3.8 unit-test jobs passed.

Conclusion: The live focused integration run validates this PR's compatibility fix; the issue #486 failure was not reproduced.