Workshop diagnostic laptop sometimes gets a ping reply, but the FR10 status collection times out. Another laptop worked, with incomplete network notes. I want the endpoint, selected route and service evidence separated before we blame settings or code.
Capture the configured target, selected interface and route during the failed read. For the other laptop, establish the exact operation that worked; a remembered ping result would not be an equivalent comparison
Other operator remembers seeing a status value, not which program returned it. I've asked for a read-only comparison with the environment recorded, so that memory isn't our baseline.
Have the network owner review the selected path if it differs. Avoid changing several adapters or weakening protections at once; that would lose the comparison and introduce another problem
The comparison found our script loaded a target from an old copied configuration, while the other laptop used the intended controller address. Maintainer corrected the config selection; the documented read now returns the expected identity on mine.