For example if the animus is pinging a rudder to see if it's up or down and a response doesn't come
back the inner mess doesn't really know whether that device is down.
All it knows is that the response didn't come back.
The device could be down but there could also be a routing problem or an intermediate device could be
done or a device between the enemies and the rudder could be done.
So some device along the path could be down or traffic could be blocked by an ACL or a firewall rule.
All the animus knows is that it can't reach the device that it's pinging.
It's an AP On the other hand is different with S&P.
The animus is querying a device and the device is telling the enemies via S&P the state of an interface.
So if a device indicates that interface Fost Ethan at 0 0 as an example is down the enemy's nose 100
percent that that information is accurate because it received that information via an MP from the device
that it was querying.
Now in the event that the actual device is down rather than an interface on the device you'll get an
unknown state.
That's a different type of signifier than if the interface is down on a device that's up and running
in terms of performance monitoring ICMP or ping is used for availability calculations and latency response
time as S&P is used for almost all the other statistics including you memory buffers interface traffic
and errors and many many other statistics.
In some cases for Windows systems the enemies might leverage w where my or Windows management instrumentation
to check for performance Karner type of values.