IP Datagram Error Statistics Report

IP Datagram Error Statistics Report (Detecting Routing Loops)

Introduction

Management solutions and applications available in the market today tends to overlook the need for network administrators of both enterprises and service providers to track Error statistics of many mission critical network device services and device resources where network users are heavily dependant. One such Service/resource is the network’s core router device’s IP Datagram handler processes.

Such critical service as the IP Datagram handler process on router devices should be monitored adequately for information on IP Datagrams Error statistics measurements. The importance of such measurements stems from the fact that it provides the administrators with a clearer picture of how well behaved the particular running service/resource is with its environment.

Knowledge of the extent of IP Datagram processes fault and error values combined with knowledge of times and the duration of the occurrence of those errors will enable administrators to evaluate and plan current and future growth needs leading to better technical and better business decisions.

No NMS application available in the market today and indeed known to us measures and displays the IP Datagram related process Error statistics over a time scale or indeed keeps a history of such statistics.

Solution Overview

This management solution focuses on detecting ONLY those devices that are designated as network Gateways and are indeed an IP Datagram forwarding devices.

The solution defines a module name and description, then initiates the polling process under which the Devices (or in a specified AMZ) are fed into the polling SNMP engine, where the Gateway status of the device is determined through polling the value of the ipForwarding MIB Object. A variable handler is then defined to store the value which is then tested with an IF conditional statement; if the status for the particular device is ‘Forwarding’ then the counters for the IP Datagrams Errors are collected. The particular errors reported in this management process are:

The number of IP Datagrams discarded because no route could be found to transmit them to their destination.

The number of IP Datagrams discarded due to lack of buffer resources.

The number of input Datagrams discarded because the IP address in their IP header's destination field was not a valid address to be received.

The number of input Datagrams discarded due to errors in their IP headers particularly Time-To-Live counter expiration.

The number of locally-addressed IP Datagrams received successfully but discarded because of an unknown or unsupported protocol.

SOSL Based Management Process Script Configuration

MODULE IpErrorStats1 ();

DESCRIPTION "Device IP Group Error Statistics Process Process";

BEGIN

ALL-DEV BY DEV

{

DEFINE ipForwarding DB INT;

ipForwarding = POLL (ipForwarding);

IF (ipForwarding == 1)

THEN

POLL ( ipDefaultTTL;

ipOutNoRoutes;

ipOutDiscards;

ipInAddrErrors

ipInUnknownProtos;

ipInHdrErrors );

ENDIF;

};

END

MODULE IpErrorStats2 ();

DESCRIPTION "Device IP Group Error Statistics Process Process";

BEGIN

ALL-DEV BY DEV

{

DEFINE ipForwarding DB INT;

ipForwarding = POLL (ipForwarding);

IF (ipForwarding == 1)

THEN

DEFINE ipOutNoRoutesT1 MAP INT;

DEFINE ipOutDiscardsT1 MAP INT;

DEFINE ipInAddrErrorsT1 MAP INT;

DEFINE ipInUnknownProtosT1 MAP INT;

DEFINE ipInHdrErrorsT1 MAP INT;

DEFINE ipOutNoRoutes DB INT;

DEFINE ipOutDiscards DB INT;

DEFINE ipInAddrErrors DB INT;

DEFINE ipInUnknownProtosT1 DB INT;

DEFINE ipInHdrErrorsT1 DB INT;

ipOutNoRoutesT1 = ipOutNoRoutes;

ipOutDiscardsT1 = ipOutDiscards;

ipInAddrErrorsT1 = ipInAddrErrors;

ipInUnknownProtosT1 = ipInUnknownProtos;

ipInHdrErrorsT1 = ipInHdrErrors;

RMV ( ipDefaultTTL;

ipOutNoRoutes;

ipOutDiscards;

ipInAddrErrors

ipInUnknownProtos;

ipInHdrErrors );

POLL ( ipDefaultTTL;

ipOutNoRoutes;

ipOutDiscards;

ipInAddrErrors

ipInUnknownProtos;

ipInHdrErrors );

DEFINE ipOutNoRoutesT2 MAP INT;

DEFINE ipOutDiscardsT2 MAP INT;

DEFINE ipInAddrErrorsT2 MAP INT;

DEFINE ipInUnknownProtosT2 MAP INT;

DEFINE ipInHdrErrorsT2 MAP INT;

ipOutNoRoutesT2 = ipOutNoRoutes;

ipOutDiscardsT2 = ipOutDiscards;

ipInAddrErrorsT2 = ipInAddrErrors;

ipInUnknownProtosT2= ipInUnknownProtos;

ipInHdrErrorsT2 = ipInHdrErrors;

CounterData (ipOutNoRoutes,

ipOutNoRoutesT1,

ipOutNoRoutesT2);

CounterData (ipOutDiscards,

ipOutDiscardsT1,

ipOutDiscardsT2);

CounterData (ipInAddrErrors,

ipInAddrErrorsT1,

ipInAddrErrorsT2);

CounterData (ipInUnknownProtos,

ipInUnknownProtosT1,

ipInUnknownProtosT2);

CounterData (ipInAddrErrors,

ipInAddrErrorsT1,

ipInAddrErrorsT2);

POLL ( ipDefaultTTL;

ipOutNoRoutes;

ipOutDiscards;

ipInAddrErrors

ipInUnknownProtos;

ipInHdrErrors );

ENDIF;

};

END

[SOSL Case Studies], [Management Concepts], [NMS Technology R&D]

[Home], [About], [Solutions Center], [NMS Market], [Products & Services],
[Management Technology], [Technical Support], [Contact us], [Site Map]