The objects described here can be monitored with the IPHost Network Monitor.
You can start SNMP monitoring using free 30-day trial version of IPHost right now.
OID list for fails statistics
- ACS server If Statistics Receive Fails Big Message
- acsIfStatsReceiveFailsBigMsg 1.3.6.1.4.1.311.1.15.2.1.1.25 (defined in ACSServer-MIB)
This is the total number of RSVP messages which could not be received by this ACS Server because they are too big to fit in the message buffer - ACS server If Statistics Send Fails Big Message
- acsIfStatsSendFailsBigMsg 1.3.6.1.4.1.311.1.15.2.1.1.26 (defined in ACSServer-MIB)
This is the total number of RSVP messages which could not be sent by this ACS Server because they are too big to fit in the message buffer - ACS server If Statistics Receive Fails No Memory
- acsIfStatsReceiveFailsNoMemory 1.3.6.1.4.1.311.1.15.2.1.1.27 (defined in ACSServer-MIB)
This is the total number of RSVP messages which could not be sent by this ACS Server because there was no free message buffer - ACS server If Statistics Send Fails No Memory
- acsIfStatsSendFailsNoMemory 1.3.6.1.4.1.311.1.15.2.1.1.28 (defined in ACSServer-MIB)
This is the total number of RSVP messages which could not be sent by this ACS Server because there was no free message buffer - ipv6 If Statistics Out fragment Fails
- ipv6IfStatsOutFragFails 1.3.6.1.2.1.55.1.6.1.14 (defined in IPV6-MIB)
The number of IPv6 datagrams that have been discarded because they needed to be fragmented at this output interface but could not be. - ipv6 If Statistics reassembly Fails
- ipv6IfStatsReasmFails 1.3.6.1.2.1.55.1.6.1.18 (defined in IPV6-MIB)
The number of failures detected by the IPv6 re- assembly algorithm (for whatever reason: timed out, errors, etc.). Note that this is not necessarily a count of discarded IPv6 fragments since some algorithms (notably the algorithm in RFC 815) can lose track of the number of fragments by combining them as they are received. This counter is incremented at the interface to which these fragments were addressed which might not be necessarily the input interface for some of the fragments. - ALTIGA Sync Statistics Rx Replen Fails
- alSyncStatsRxReplenFails 1.3.6.1.4.1.3076.2.1.2.32.2.1.9 (defined in ALTIGA-SYNC-STATS-MIB)
The number of times receive buffers could not be allocated on this HDLC interface. - ip System Statistics reassembly Fails
- ipSystemStatsReasmFails 1.3.6.1.2.1.4.31.1.1.16 (defined in IP-MIB)
The number of failures detected by the IP re-assembly algorithm (for whatever reason: timed out, errors, etc.). Note that this is not necessarily a count of discarded IP fragments since some algorithms (notably the algorithm in RFC 815) can lose track of the number of fragments by combining them as they are received. When tracking interface statistics, the counter of the interface to which these fragments were addressed is incremented. This interface might not be the same as the input interface for some of the fragments. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime. - ip System Statistics Out fragment Fails
- ipSystemStatsOutFragFails 1.3.6.1.2.1.4.31.1.1.28 (defined in IP-MIB)
The number of IP datagrams that have been discarded because they needed to be fragmented but could not be. This includes IPv4 packets that have the DF bit set and IPv6 packets that are being forwarded and exceed the outgoing link MTU. When tracking interface statistics, the counter of the outgoing interface is incremented for an unsuccessfully fragmented datagram. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime. - ip If Statistics reassembly Fails
- ipIfStatsReasmFails 1.3.6.1.2.1.4.31.3.1.16 (defined in IP-MIB)
The number of failures detected by the IP re-assembly algorithm (for whatever reason: timed out, errors, etc.). Note that this is not necessarily a count of discarded IP fragments since some algorithms (notably the algorithm in RFC 815) can lose track of the number of fragments by combining them as they are received. When tracking interface statistics, the counter of the interface to which these fragments were addressed is incremented. This interface might not be the same as the input interface for some of the fragments. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime. - ip If Statistics Out fragment Fails
- ipIfStatsOutFragFails 1.3.6.1.2.1.4.31.3.1.28 (defined in IP-MIB)
The number of IP datagrams that have been discarded because they needed to be fragmented but could not be. This includes IPv4 packets that have the DF bit set and IPv6 packets that are being forwarded and exceed the outgoing link MTU. When tracking interface statistics, the counter of the outgoing interface is incremented for an unsuccessfully fragmented datagram. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
