The Incorrect Messages Counter reflects any sort of incorrect
information in a message. This includes:
? RELEASE, RELEASE COMPLETE, ADD PARTY REJECT, and
STATUS messages transmitted or received, that contain any of
the Cause values listed below.
? Ignored messages. These messages are dropped because the
message was so damaged that it could not be further processed.
A list of dropped messages is compiled below:
Message with invalid protocol discriminator
Message with errors in the call reference I.E.
? Bits 5-8 of the first octet not equal to '0000'
? Bits 1-4 of the first octet indicating a length other than
3 octets
? RELEASE COMPLETE message received with a call
reference that does not relate to a call active or in progress
? SETUP message received with call reference flag incorrectly
set to 1
? SETUP message received with a call reference for a call that is
already active or in progress.
Message too short
The following cause values are monitored by this counter
(Note: These cause values apply to both UNI3.0 and UNI3.1 unless
otherwise stated)
Cause Value Meaning
10 VPCI/VCI unacceptable (UNI3.0 only)
36 VPCI/VCI assignment failure (UNI3.1 only)
81 invalid call reference value
82 identified channel does not exist
89 invalid endpoint reference
96 mandatory information element is missing
97 message type non-existent or not
implemented
99 information element non-existent or not
implemented
100 invalid information element contents
101 message not compatible with call state
104 incorrect message length
111 protocol error, unspecified
NOTE: For this counter, RELEASE COMPLETE messages that are a
reply to a previous RELEASE message and contain the same cause
value, are redundant (for counting purposes) and should not be
counted.
Parsed from file agilent-wanstats.mib.txt
Company: None
Module: WANSTATS-MIB
The Incorrect Messages Counter reflects any sort of incorrect
information in a message. This includes:
? RELEASE, RELEASE COMPLETE, ADD PARTY REJECT, and
STATUS messages transmitted or received, that contain any of
the Cause values listed below.
? Ignored messages. These messages are dropped because the
message was so damaged that it could not be further processed.
A list of dropped messages is compiled below:
Message with invalid protocol discriminator
Message with errors in the call reference I.E.
? Bits 5-8 of the first octet not equal to '0000'
? Bits 1-4 of the first octet indicating a length other than
3 octets
? RELEASE COMPLETE message received with a call
reference that does not relate to a call active or in progress
? SETUP message received with call reference flag incorrectly
set to 1
? SETUP message received with a call reference for a call that is
already active or in progress.
Message too short
The following cause values are monitored by this counter
(Note: These cause values apply to both UNI3.0 and UNI3.1 unless
otherwise stated)
Cause Value Meaning
10 VPCI/VCI unacceptable (UNI3.0 only)
36 VPCI/VCI assignment failure (UNI3.1 only)
81 invalid call reference value
82 identified channel does not exist
89 invalid endpoint reference
96 mandatory information element is missing
97 message type non-existent or not
implemented
99 information element non-existent or not
implemented
100 invalid information element contents
101 message not compatible with call state
104 incorrect message length
111 protocol error, unspecified
NOTE: For this counter, RELEASE COMPLETE messages that are a
reply to a previous RELEASE message and contain the same cause
value, are redundant (for counting purposes) and should not be
counted.
Parsed from file WANSTATS-MIB.mib
Module: WANSTATS-MIB
Vendor: Hewlett-Packard
Module: WANSTATS-MIB
[Automatically extracted from oidview.com]
wanAtmStatsInIncorrectMsgs OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The Incorrect Messages Counter reflects any sort of incorrect information in a message. This includes: ? RELEASE, RELEASE COMPLETE, ADD PARTY REJECT, and STATUS messages transmitted or received, that contain any of the Cause values listed below. ? Ignored messages. These messages are dropped because the message was so damaged that it could not be further processed. A list of dropped messages is compiled below: Message with invalid protocol discriminator Message with errors in the call reference I.E. ? Bits 5-8 of the first octet not equal to '0000' ? Bits 1-4 of the first octet indicating a length other than 3 octets ? RELEASE COMPLETE message received with a call reference that does not relate to a call active or in progress ? SETUP message received with call reference flag incorrectly set to 1 ? SETUP message received with a call reference for a call that is already active or in progress. Message too short The following cause values are monitored by this counter (Note: These cause values apply to both UNI3.0 and UNI3.1 unless otherwise stated) Cause Value Meaning 10 VPCI/VCI unacceptable (UNI3.0 only) 36 VPCI/VCI assignment failure (UNI3.1 only) 81 invalid call reference value 82 identified channel does not exist 89 invalid endpoint reference 96 mandatory information element is missing 97 message type non-existent or not implemented 99 information element non-existent or not implemented 100 invalid information element contents 101 message not compatible with call state 104 incorrect message length 111 protocol error, unspecified NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted." ::= { wanAtmStatsEntry 17 }
wanAtmStatsInIncorrectMsgs OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The Incorrect Messages Counter reflects any sort of incorrect information in a message. This includes: ? RELEASE, RELEASE COMPLETE, ADD PARTY REJECT, and STATUS messages transmitted or received, that contain any of the Cause values listed below. ? Ignored messages. These messages are dropped because the message was so damaged that it could not be further processed. A list of dropped messages is compiled below: Message with invalid protocol discriminator Message with errors in the call reference I.E. ? Bits 5-8 of the first octet not equal to '0000' ? Bits 1-4 of the first octet indicating a length other than 3 octets ? RELEASE COMPLETE message received with a call reference that does not relate to a call active or in progress ? SETUP message received with call reference flag incorrectly set to 1 ? SETUP message received with a call reference for a call that is already active or in progress. Message too short The following cause values are monitored by this counter (Note: These cause values apply to both UNI3.0 and UNI3.1 unless otherwise stated) Cause Value Meaning 10 VPCI/VCI unacceptable (UNI3.0 only) 36 VPCI/VCI assignment failure (UNI3.1 only) 81 invalid call reference value 82 identified channel does not exist 89 invalid endpoint reference 96 mandatory information element is missing 97 message type non-existent or not implemented 99 information element non-existent or not implemented 100 invalid information element contents 101 message not compatible with call state 104 incorrect message length 111 protocol error, unspecified NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted." ::= { wanAtmStatsEntry 17 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.1 | wanAtmStatsIndex | 0 | 0 | The value of this object uniquely identifies this wanAtmStatsTable entry. |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.2 | wanAtmStatsDataSource | 0 | 0 | This object identifies the source of the data that this wanAtmStatsEntry analyzes. This source can be any interface on this devi… |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.3 | wanAtmStatsDropEvents | 0 | 0 | The total number of events in which frames were dropped by the probe due to lack of resources. Note that this number is not nece… |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.4 | wanAtmStatsInCells | 0 | 0 | The total number of cells seen coming from the far end of the link including errored cells. |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.5 | wanAtmStatsOutCells | 0 | 0 | The total number of cells seen coming from the near end of the link including errored cells. |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.6 | wanAtmStatsInCLP1 | 0 | 0 | The total number of cells with the CLP bit set seen coming from the far end of the link. |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.7 | wanAtmStatsOutCLP1 | 0 | 0 | The total number of cells with the CLP bit set seen coming from the near end of the link. |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.8 | wanAtmStatsConnectionEvents | 0 | 0 | This counter counts the sum of the following errors: 1) SSCOP Connection Disconnect Counter The abnormal occurrence of this event… |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.9 | wanAtmStatsErroredPDUs | 0 | 0 | This counter counts the sum of the following errors: 1) Invalid PDUs. These are defined in SSCOP and consist of PDUs with incorrec… |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.10 | wanAtmStatsSetupAttempts | 0 | 0 | This counter counts the number of call setup attempts (both successful and unsuccessful) detected on this interface. |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.11 | wanAtmStatsInRoutesUnavailable | 0 | 0 | This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE mesg for the same call), ADD PA… |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.12 | wanAtmStatsOutRoutesUnavailable | 0 | 0 | This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE mesg for the same call), ADD PA… |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.13 | wanAtmStatsInResourcesUnavailable | 0 | 0 | This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE mesg for the same call), ADD PA… |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.14 | wanAtmStatsOutResourcesUnavailable | 0 | 0 | This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE mesg for the same call), ADD PA… |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.15 | wanAtmStatsInUnsuccessfulCalls | 0 | 0 | This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE mesg for the same call), ADD PA… |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.16 | wanAtmStatsOutUnsuccessfulCalls | 0 | 0 | This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE mesg for the same call), ADD PA… |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.18 | wanAtmStatsOutIncorrectMsgs | 0 | 0 | The Incorrect Messages Counter reflects any sort of incorrect information in a message. This includes: ? RELEASE, RELEASE COMPLE… |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.19 | wanAtmStatsInPartyEvents | 0 | 0 | This counter monitors error events that occur due to the originating user doing something wrong. This counter is incremented when… |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.20 | wanAtmStatsOutPartyEvents | 0 | 0 | This counter monitors error events that occur due to the originating user doing something wrong. This counter is incremented when… |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.21 | wanAtmStatsInExpiries | 0 | 0 | The Timer Expiries Counter provides a count of network timer expiries, and to some extent, host or switch timer expiries. The con… |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.22 | wanAtmStatsOutExpiries | 0 | 0 | The Timer Expiries Counter provides a count of network timer expiries, and to some extent, host or switch timer expiries. The con… |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.23 | wanAtmStatsInRestartErrors | 0 | 0 | The Restart Activity Counter provides a count of host, switch, or network restart activity. This counter is incremented when rece… |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.24 | wanAtmStatsOutRestartErrors | 0 | 0 | The Restart Activity Counter provides a count of host, switch, or network restart activity. This counter is incremented when tran… |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.25 | wanAtmStatsInSVCs | 0 | 0 | SVC VCCs established at this signaling entity for incoming connections. |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.26 | wanAtmStatsOutSVCs | 0 | 0 | SVC VCCs established at this signaling entity for outgoing connections. |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.27 | wanAtmStatsInOCDs | 0 | 0 | An out of cell delineation from far end of the link. |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.28 | wanAtmStatsOutOCDs | 0 | 0 | An out of cell delineation from near end of the link. |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.29 | wanAtmStatsInLOCs | 0 | 0 | A loss of cell delineation error from far end of the link. This is a persistent OCD condition. |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.30 | wanAtmStatsOutLOCs | 0 | 0 | A loss of cell delineation error from near end of link. This is a persistent OCD condition. |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.31 | wanAtmStatsInLOFs | 0 | 0 | A loss of frame error from far end of link. |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.32 | wanAtmStatsOutLOFs | 0 | 0 | A loss of frame error from near end of link. |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.33 | wanAtmStatsInLOPs | 0 | 0 | A loss of pointer error from far end of link. |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.34 | wanAtmStatsOutLOPs | 0 | 0 | A loss of pointer error from near end of link. |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.35 | wanAtmStatsInLOSs | 0 | 0 | A loss of signal error from far end of link. |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.36 | wanAtmStatsOutLOSs | 0 | 0 | A loss of signal error from near end of link. |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.37 | wanAtmStatsOwner | 0 | 0 | The entity that configured this entry. |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.5.1.38 | wanAtmStatsStatus | 0 | 0 | The status of this wanAtmStatsTable entry. |