This field is obsolete.
A two octet field indicating the Last Clearing
Cause and Diagnostic Field of the last failed
connection attempt (a.k.a. call attempt) or
active connection (a.k.a. session) for the partner PU .
For LLC type 2 connections the first octet (cause)
is always 0. The second octet (diagnostic)
indicates the reason for the last connection failure.
The second octet is set to 0 when a sucessful
call has been placed, or if no call has ever been
placed, or the clear is initiated by the partner for
which mappingPuLastClearCode has the clear code.
If the second octet is non-zero then it indicates
the reason for the connection attempt failure.
See User's Guide for information
Parsed from file SYNC-RESEARCH-MIB.mib
Module: SYNC-RESEARCH-MIB
Vendor: Sync Research, Inc.
Module: SYNC-RESEARCH-MIB
[Automatically extracted from oidview.com]
mappingPuPartnerLastClearCode OBJECT-TYPE SYNTAX OCTET STRING (SIZE(2)) ACCESS read-only STATUS mandatory DESCRIPTION "This field is obsolete. A two octet field indicating the Last Clearing Cause and Diagnostic Field of the last failed connection attempt (a.k.a. call attempt) or active connection (a.k.a. session) for the partner PU . For LLC type 2 connections the first octet (cause) is always 0. The second octet (diagnostic) indicates the reason for the last connection failure. The second octet is set to 0 when a sucessful call has been placed, or if no call has ever been placed, or the clear is initiated by the partner for which mappingPuLastClearCode has the clear code. If the second octet is non-zero then it indicates the reason for the connection attempt failure. See User's Guide for information" ::= { mappingPuConfigEntry 17 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.485.3.6.4.1.1.1 | mappingPuConfigLineIndex | 0 | 0 | The port number for which PU is associated with. Port number 99 is a special value which is used to indicate NetView PU. |
| 1.3.6.1.4.1.485.3.6.4.1.1.2 | mappingPuConfigAddress | 0 | 0 | The PU address in the range of 0x01 to 0xfe. |
| 1.3.6.1.4.1.485.3.6.4.1.1.3 | mappingPuSourceSAP | 0 | 0 | The LLC source SAP value for this PU. Typically the source SAP will vary for each PU. This is due to the fact that most Sync prod… |
| 1.3.6.1.4.1.485.3.6.4.1.1.4 | mappingPuDestinationSAP | 0 | 0 | The LLC Destination SAP value for this PU. For SNA typically the destination is almost always SAP 4. However both Host Front End… |
| 1.3.6.1.4.1.485.3.6.4.1.1.5 | mappingPuDestinationMAC | 0 | 0 | The LAN Destination MAC address used in the LLC Type 2 connection for this PU. The Token-Ring format for this field is a 6 octet (… |
| 1.3.6.1.4.1.485.3.6.4.1.1.6 | mappingPuPartnerConfigLineIndex | 0 | 0 | The port number for the partner PU associated with source PU. Port number 99 is a special value which is used to indicate NetVie… |
| 1.3.6.1.4.1.485.3.6.4.1.1.7 | mappingPuPartnerConfigAddress | 0 | 0 | The PU address of the partner PU in the range of 0x01 to 0xfe. |
| 1.3.6.1.4.1.485.3.6.4.1.1.8 | mappingPuPartnerSourceSAP | 0 | 0 | The LLC source SAP value for a partner PU. Typically the source SAP will vary for each PU. This is due to the fact that most Sync… |
| 1.3.6.1.4.1.485.3.6.4.1.1.9 | mappingPuPartnerDestSAP | 0 | 0 | The LLC Destination SAP value for the partner PU. For SNA typically the destination is almost always SAP 4. However both Host Fr… |
| 1.3.6.1.4.1.485.3.6.4.1.1.10 | mappingPuPartnerDestMAC | 0 | 0 | The LAN Destination MAC address used in the LLC Type 2 connection for the partner PU. The Token-Ring format for this field is a 6… |
| 1.3.6.1.4.1.485.3.6.4.1.1.11 | mappingPuNAU | 0 | 0 | The NAU Name. The NAU name is same for both the source PU and the partner PU. It represents one physical PU in a network. |
| 1.3.6.1.4.1.485.3.6.4.1.1.12 | mappingPuConnectID | 0 | 0 | The connection ID. This must match a connection ID of an access line PU or another mapping PU Connection ID. The connnection ID is… |
| 1.3.6.1.4.1.485.3.6.4.1.1.13 | mappingPuXID | 0 | 0 | The XID value for this PU. The XID is used to identify the PU during the LLC connection process to the remote Host or Gateway. For… |
| 1.3.6.1.4.1.485.3.6.4.1.1.14 | mappingPuDirectDLCI | 0 | 0 | The Frame Relay DLCI used in the LLC Type 2 connection for this PU. The Frame Relay format for this field is a 2 octet (16 bit) fi… |
| 1.3.6.1.4.1.485.3.6.4.1.1.15 | mappingPuLastClearCode | 0 | 0 | This field is obsolete. A two octet field indicating the Last Clearing Cause and Diagnostic Field of the last failed connection at… |
| 1.3.6.1.4.1.485.3.6.4.1.1.16 | mappingPuConnAttemptCnt | 0 | 0 | This field is obsolete. The number of connection attempts performed for this PU. This count is set to zero at startup, and after e… |
| 1.3.6.1.4.1.485.3.6.4.1.1.18 | mappingPuPartnerConnAttemptCnt | 0 | 0 | This field is obsolete. The number of connection attempts performed for the partner PU. This count is set to zero at startup, and… |