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
(48 bit) field represented in IEEE 802.5 format where
the first bit transmitted is the most significant bit.
The destination MAC must also be an 'Individual'
address. Therefore valid addresses are between
000000000001 and 7FFFFFFFFFFF (an address of all
zeroes is not supported).
The Ethernet format for this field is a 6 octet
(48 bit) field represented in IEEE 802.3 format where
the first bit transmitted is the least significant bit.
The destination MAC must also be an 'Individual'
address. Therefore valid addresses must start
with the least significant bit equal to 0. In other
words, the first two digits must be in the set
of 0x00, 0x02, 0x04, ... 0xFE (an address of all
12 digits equal to zeroes is not supported).
This field is not applicable to all cases. If not it
returns a dummy value.
Parsed from file 3Com-linkconv.mib.txt
Company: None
Module: SYNC-RESEARCH-MIB
This field is obsolete.
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
(48 bit) field represented in IEEE 802.5 format where
the first bit transmitted is the most significant bit.
The destination MAC must also be an 'Individual'
address. Therefore valid addresses are between
000000000001 and 7FFFFFFFFFFF (an address of all
zeroes is not supported).
The Ethernet format for this field is a 6 octet
(48 bit) field represented in IEEE 802.3 format where
the first bit transmitted is the least significant bit.
The destination MAC must also be an 'Individual'
address. Therefore valid addresses must start
with the least significant bit equal to 0. In other
words, the first two digits must be in the set
of 0x00, 0x02, 0x04, ... 0xFE (an address of all
12 digits equal to zeroes is not supported).
This field is not applicable to all cases. If not it
returns a dummy value.
Parsed from file SYNC-RESEARCH-MIB.mib
Module: SYNC-RESEARCH-MIB
Vendor: Sync Research, Inc.
Module: SYNC-RESEARCH-MIB
[Automatically extracted from oidview.com]
mappingPuDestinationMAC OBJECT-TYPE SYNTAX PhysAddress ACCESS read-only STATUS mandatory DESCRIPTION "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 (48 bit) field represented in IEEE 802.5 format where the first bit transmitted is the most significant bit. The destination MAC must also be an 'Individual' address. Therefore valid addresses are between 000000000001 and 7FFFFFFFFFFF (an address of all zeroes is not supported). The Ethernet format for this field is a 6 octet (48 bit) field represented in IEEE 802.3 format where the first bit transmitted is the least significant bit. The destination MAC must also be an 'Individual' address. Therefore valid addresses must start with the least significant bit equal to 0. In other words, the first two digits must be in the set of 0x00, 0x02, 0x04, ... 0xFE (an address of all 12 digits equal to zeroes is not supported). This field is not applicable to all cases. If not it returns a dummy value." ::= { mappingPuConfigEntry 5 }
mappingPuDestinationMAC OBJECT-TYPE SYNTAX PhysAddress ACCESS read-only STATUS mandatory DESCRIPTION "This field is obsolete. 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 (48 bit) field represented in IEEE 802.5 format where the first bit transmitted is the most significant bit. The destination MAC must also be an 'Individual' address. Therefore valid addresses are between 000000000001 and 7FFFFFFFFFFF (an address of all zeroes is not supported). The Ethernet format for this field is a 6 octet (48 bit) field represented in IEEE 802.3 format where the first bit transmitted is the least significant bit. The destination MAC must also be an 'Individual' address. Therefore valid addresses must start with the least significant bit equal to 0. In other words, the first two digits must be in the set of 0x00, 0x02, 0x04, ... 0xFE (an address of all 12 digits equal to zeroes is not supported). This field is not applicable to all cases. If not it returns a dummy value." ::= { mappingPuConfigEntry 5 }
| 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.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.17 | mappingPuPartnerLastClearCode | 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.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… |