NetworkDevice_IPSubsystem is calculating excessive packet errors. (NETIQKB48672)

NetworkDevice_IPSubsystem is calculating excessive packet errors.

The IPSubsystem_Util KS retrieves these values from the standard IP MIB in MIB-2:

 "ip.ipInReceives.0" 

 "ip.ipInHdrErrors.0"

 "ip.ipInAddrErrors.0"

 "ip.ipForwDatagrams.0"

 "ip.ipInUnknownProtos.0"

 "ip.ipInDiscards.0'

 "ip.ipReasmFails.0"

 "ip.ipOutRequests.0"

 "ip.ipOutDiscards.0"

 "ip.ipOutNoRoutes.0"

 "ip.ipFragFails.0"

For each counter, a delta (how much the counter increased) is calculated at each script iteration. So the % packet errors can be considered an average over the script interval time.

The standard IP MIB used by IPSubsystem_Util is designed to monitor both Layer2/Layer3 devices. The IpForwarding attribute is set to true if the devices is routing, and false if not.

For the problem counter here is "ipInAddrErrors" the number of input datagrams discarded because the IP address in the IP header's destination field was not a valid address to be received at this entity. This count includes invalid addresses (e.g. , 0.0.0.0) and addresses from unsupported Classes (e.g. , Class E). For entities which are not IP routers and therefore do not forward datagrams, this counter includes datagrams discarded because the destination address was not a local address.

Formerly known as NETIQKB48672

The MIB description specifies how the value is to be determined when the device is or is not routing.
AppManager calculates % Packet Errors using the formula below:

(ip.ipInHdrErrors.0+ip.ipInAddrErrors.0+ip.ipInUnknownProtos.0+ip.ipInDiscards.0+ip.ipReasmFails.0+ip.ipOutDiscards.0+ip.ipOutNoRoutes.0+ip.ipFragFails.0)/ip.ipInReceives.0)*100