Reference record for OID 1.3.6.1.4.1.485.3.6.4.1.1.3



parent
1.3.6.1.4.1.485.3.6.4.1.1 (mappingPuConfigEntry)
node code
3
node name
mappingPuSourceSAP
dot oid
1.3.6.1.4.1.485.3.6.4.1.1.3
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) sync(485) srNodeGroup(3) nodePUGroup(6) puMappingGroup(4) mappingPuConfigTable(1) mappingPuConfigEntry(1) mappingPuSourceSAP(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) syncResearch(485) srNodeGroup(3) nodePUGroup(6) puMappingGroup(4) mappingPuConfigTable(1) mappingPuConfigEntry(1) mappingPuSourceSAP(3)}
  • ...skipped...
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) sync(485) srNodeGroup(3) nodePUGroup(6) puMappingGroup(4) mappingPuConfigTable(1) mappingPuConfigEntry(1) mappingPuSourceSAP(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) syncResearch(485) srNodeGroup(3) nodePUGroup(6) puMappingGroup(4) mappingPuConfigTable(1) mappingPuConfigEntry(1) mappingPuSourceSAP(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) sync(485) srNodeGroup(3) nodePUGroup(6) puMappingGroup(4) mappingPuConfigTable(1) mappingPuConfigEntry(1) mappingPuSourceSAP(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) syncResearch(485) srNodeGroup(3) nodePUGroup(6) puMappingGroup(4) mappingPuConfigTable(1) mappingPuConfigEntry(1) mappingPuSourceSAP(3)}
  • ...skipped...
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) sync(485) srNodeGroup(3) nodePUGroup(6) puMappingGroup(4) mappingPuConfigTable(1) mappingPuConfigEntry(1) mappingPuSourceSAP(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) syncResearch(485) srNodeGroup(3) nodePUGroup(6) puMappingGroup(4) mappingPuConfigTable(1) mappingPuConfigEntry(1) mappingPuSourceSAP(3)}
  • iri oid
  • /iso/identified-organization/dod/internet/private/enterprise/sync/srNodeGroup/nodePUGroup/puMappingGroup/mappingPuConfigTable/mappingPuConfigEntry/mappingPuSourceSAP
  • /iso/identified-organization/dod/internet/private/enterprise/syncResearch/srNodeGroup/nodePUGroup/puMappingGroup/mappingPuConfigTable/mappingPuConfigEntry/mappingPuSourceSAP
  • ...skipped...
  • /iso/org/dod/internet/private/enterprise/sync/srNodeGroup/nodePUGroup/puMappingGroup/mappingPuConfigTable/mappingPuConfigEntry/mappingPuSourceSAP
  • /iso/org/dod/internet/private/enterprise/syncResearch/srNodeGroup/nodePUGroup/puMappingGroup/mappingPuConfigTable/mappingPuConfigEntry/mappingPuSourceSAP
  • /iso/org/dod/internet/private/enterprises/sync/srNodeGroup/nodePUGroup/puMappingGroup/mappingPuConfigTable/mappingPuConfigEntry/mappingPuSourceSAP
  • /iso/org/dod/internet/private/enterprises/syncResearch/srNodeGroup/nodePUGroup/puMappingGroup/mappingPuConfigTable/mappingPuConfigEntry/mappingPuSourceSAP
  • ...skipped...
  • /iso/iso-identified-organization/dod/internet/private/enterprises/sync/srNodeGroup/nodePUGroup/puMappingGroup/mappingPuConfigTable/mappingPuConfigEntry/mappingPuSourceSAP
  • /iso/iso-identified-organization/dod/internet/private/enterprises/syncResearch/srNodeGroup/nodePUGroup/puMappingGroup/mappingPuConfigTable/mappingPuConfigEntry/mappingPuSourceSAP
  • iri by oid_info
    /ISO/Identified-Organization/6/1/4/1/485/3/6/4/1/1/3

    Description by mibdepot

    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 products are
    configured to always call the same remote
    Token-Ring Host or Gateway for all connections
    configured. This means that all the Destination
    SAP (usually set to 4) and Destination MAC addresses
    are the same, so the Source SAP field must be set
    to a unique value in order to uniquely identify
    the LLC connection to the Host. (SNA does not allow
    multiplexing of PUs on one LLC connection. Each
    PU must have its own LLC Type 2 connection.)
    This field must be set to a range between 04 and
    E8 hexadecimal and it must be evenly divisible by
    4 (802.2 LLC rules for user assigned SAPs).

    This field is not applicable in all cases, if not it
    returns a dummy value.

    This parameter defaults to a value of 4.

    Parsed from file 3Com-linkconv.mib.txt
    Company: None
    Module: SYNC-RESEARCH-MIB

    Description by circitor

    This field is obsolete.
    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 products are
    configured to always call the same remote
    Token-Ring Host or Gateway for all connections
    configured. This means that all the Destination
    SAP (usually set to 4) and Destination MAC addresses
    are the same, so the Source SAP field must be set
    to a unique value in order to uniquely identify
    the LLC connection to the Host. (SNA does not allow
    multiplexing of PUs on one LLC connection. Each
    PU must have its own LLC Type 2 connection.)
    This field must be set to a range between 04 and
    E8 hexadecimal and it must be evenly divisible by
    4 (802.2 LLC rules for user assigned SAPs).

    This field is not applicable in all cases, if not it
    returns a dummy value.

    This parameter defaults to a value of 4.

    Parsed from file SYNC-RESEARCH-MIB.mib
    Module: SYNC-RESEARCH-MIB

    Information by oid_info

    Vendor: Sync Research, Inc.
    Module: SYNC-RESEARCH-MIB

    [Automatically extracted from oidview.com]

    Information by mibdepot

    mappingPuSourceSAP OBJECT-TYPE SYNTAX OCTET STRING (SIZE(1)) ACCESS read-only STATUS mandatory DESCRIPTION "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 products are configured to always call the same remote Token-Ring Host or Gateway for all connections configured. This means that all the Destination SAP (usually set to 4) and Destination MAC addresses are the same, so the Source SAP field must be set to a unique value in order to uniquely identify the LLC connection to the Host. (SNA does not allow multiplexing of PUs on one LLC connection. Each PU must have its own LLC Type 2 connection.) This field must be set to a range between 04 and E8 hexadecimal and it must be evenly divisible by 4 (802.2 LLC rules for user assigned SAPs). This field is not applicable in all cases, if not it returns a dummy value. This parameter defaults to a value of 4." ::= { mappingPuConfigEntry 3 }

    Information by circitor

    mappingPuSourceSAP OBJECT-TYPE SYNTAX OCTET STRING (SIZE(1)) ACCESS read-only STATUS mandatory DESCRIPTION "This field is obsolete. 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 products are configured to always call the same remote Token-Ring Host or Gateway for all connections configured. This means that all the Destination SAP (usually set to 4) and Destination MAC addresses are the same, so the Source SAP field must be set to a unique value in order to uniquely identify the LLC connection to the Host. (SNA does not allow multiplexing of PUs on one LLC connection. Each PU must have its own LLC Type 2 connection.) This field must be set to a range between 04 and E8 hexadecimal and it must be evenly divisible by 4 (802.2 LLC rules for user assigned SAPs). This field is not applicable in all cases, if not it returns a dummy value. This parameter defaults to a value of 4." ::= { mappingPuConfigEntry 3 }

    First Registration Authority (recovered by parent 1.3.6.1.4.1.485)

    Bartky Alan

    Brothers (17)

    OIDNameSub childrenSub Nodes TotalDescription
    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.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.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…