This variable indicates the number of traps that have been
lost. A trap is considered to be lost if it is overwritten
in the internal trap table before it is sent to the NMS.
This may occur if the trap table is not large enough (see
sCfgTrapTblSize) to hold all of unsent traps. How quickly
traps are sent to the NMS is governed by the sCfgMaxTrapSec
variable. To prevent trap loss, set these two variables
so that the trap backlog does not overflow the trap table
and so that traps do not flood the network.
Parsed from file NMSYSMGR.MIB.txt
Company: None
Module: COMTEK-VMS-NM-SYSMGR-MIB
This variable indicates the number of traps that have been
lost. A trap is considered to be lost if it is overwritten
in the internal trap table before it is sent to the NMS.
This may occur if the trap table is not large enough (see
sCfgTrapTblSize) to hold all of unsent traps. How quickly
traps are sent to the NMS is governed by the sCfgMaxTrapSec
variable. To prevent trap loss, set these two variables
so that the trap backlog does not overflow the trap table
and so that traps do not flood the network.
Parsed from file COMTEK-VMS-NM-SYSMGR-MIB.mib
Module: COMTEK-VMS-NM-SYSMGR-MIB
Vendor: Comtek Services Inc.
Module: COMTEK-VMS-NM-SYSMGR-MIB
[Automatically extracted from oidview.com]
sTrapLostCount OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "This variable indicates the number of traps that have been lost. A trap is considered to be lost if it is overwritten in the internal trap table before it is sent to the NMS. This may occur if the trap table is not large enough (see sCfgTrapTblSize) to hold all of unsent traps. How quickly traps are sent to the NMS is governed by the sCfgMaxTrapSec variable. To prevent trap loss, set these two variables so that the trap backlog does not overflow the trap table and so that traps do not flood the network." ::= { sTrapInfo 5 }
sTrapLostCount OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "This variable indicates the number of traps that have been lost. A trap is considered to be lost if it is overwritten in the internal trap table before it is sent to the NMS. This may occur if the trap table is not large enough (see sCfgTrapTblSize) to hold all of unsent traps. How quickly traps are sent to the NMS is governed by the sCfgMaxTrapSec variable. To prevent trap loss, set these two variables so that the trap backlog does not overflow the trap table and so that traps do not flood the network." ::= { sTrapInfo 5 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.597.4.3.3.5.0 | sTrapLostCount | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.597.4.3.3.1 | sTrapNextSeqNum | 1 | 1 | The next sequence number in the trap table. When this variable is sent as part of a trap, it identifies the sequence number assi… |
| 1.3.6.1.4.1.597.4.3.3.2 | sTrapTime | 1 | 1 | Subagent up time (sCfgUpTime) when the trap was created. |
| 1.3.6.1.4.1.597.4.3.3.3 | sTrapResendSeqNum | 1 | 1 | Sequence number of a trap message to be resent to the manager. Setting this variable to a trap sequence number causes the specif… |
| 1.3.6.1.4.1.597.4.3.3.4 | sTrapLastSeqNumSent | 1 | 1 | Sequence number of the last trap sent. This value may be compared to sTrapNextSeqNum to determine if a backlog of traps exists. … |
| 1.3.6.1.4.1.597.4.3.3.6 | sTrapTextTbl | 1 | 11 | Table of textual trap messages. |