The SAP list indicates which SAPs are advertised to
the transport connection defined by this conceptual
row. Only SAPs with even numbers are represented,
in the form of the most significant bit of the first
octet representing the SAP 0, the next most significant
bit representing the SAP 2, to the least significant
bit of the last octet representing the SAP 254. Data
link switching is allowed for those SAPs which have
one in its corresponding bit, not allowed otherwise.
The whole SAP list has to be changed together. Changing
the SAP list affects only new circuit establishments
and has no effect on established circuits.
This list can be used to restrict specific partners
from knowing about all the SAPs used by DLSw on all its
interfaces (these are represented in dlswIfSapList for
each interface). For instance, one may want to run NetBIOS
with some partners but not others.
If a node supports sending run-time capabilities exchange
messages, changes to this object should cause that action.
When to start the run-time capabilities exchange is
implementation-specific.
The DEFVAL below indicates support for SAPs 0, 4, 8, and C.
Parsed from file DLSW-MIB.mib
Module: DLSW-MIB
The SAP list indicates which SAPs are advertised to
the transport connection defined by this conceptual
row. Only SAPs with even numbers are represented,
in the form of the most significant bit of the first
octet representing the SAP 0, the next most significant
bit representing the SAP 2, to the least significant
bit of the last octet representing the SAP 254. Data
link switching is allowed for those SAPs which have
one in its corresponding bit, not allowed otherwise.
The whole SAP list has to be changed together. Changing
the SAP list affects only new circuit establishments
and has no effect on established circuits.
This list can be used to restrict specific partners
from knowing about all the SAPs used by DLSw on all its
interfaces (these are represented in dlswIfSapList for
each interface). For instance, one may want to run NetBIOS
with some partners but not others.
If a node supports sending run-time capabilities exchange
messages, changes to this object should cause that action.
When to start the run-time capabilities exchange is
implementation-specific.
The DEFVAL below indicates support for SAPs 0, 4, 8, and C.
dlswTConnConfigSapList OBJECT-TYPE
SYNTAX OCTET STRING(SIZE(16))
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The SAP list indicates which SAPs are advertised to
the transport connection defined by this conceptual
row. Only SAPs with even numbers are represented,
in the form of the most significant bit of the first
octet representing the SAP 0, the next most significant
bit representing the SAP 2, to the least significant
bit of the last octet representing the SAP 254. Data
link switching is allowed for those SAPs which have
one in its corresponding bit, not allowed otherwise.
The whole SAP list has to be changed together. Changing
the SAP list affects only new circuit establishments
and has no effect on established circuits.
This list can be used to restrict specific partners
from knowing about all the SAPs used by DLSw on all its
interfaces (these are represented in dlswIfSapList for
each interface). For instance, one may want to run NetBIOS
with some partners but not others.
If a node supports sending run-time capabilities exchange
messages, changes to this object should cause that action.
When to start the run-time capabilities exchange is
implementation-specific.
The DEFVAL below indicates support for SAPs 0, 4, 8, and C."
DEFVAL { AA000000000000000000000000000000h }
View at oid-info.com
The SAP list indicates which SAPs are advertised to
the transport connection defined by this conceptual
row. Only SAPs with even numbers are represented,
in the form of the most significant bit of the first
octet representing the SAP 0, the next most significant
bit representing the SAP 2, to the least significant
bit of the last octet representing the SAP 254. Data
link switching is allowed for those SAPs which have
one in its corresponding bit, not allowed otherwise.
The whole SAP list has to be changed together. Changing
the SAP list affects only new circuit establishments
and has no effect on established circuits.
This list can be used to restrict specific partners
from knowing about all the SAPs used by DLSw on all its
interfaces (these are represented in dlswIfSapList for
each interface). For instance, one may want to run NetBIOS
with some partners but not others.
If a node supports sending run-time capabilities exchange
messages, changes to this object should cause that action.
When to start the run-time capabilities exchange is
implementation-specific.
The DEFVAL below indicates support for SAPs 0, 4, 8, and C.
Parsed from file rfc2024-Data-Link-Switches.mib.txt
Company: None
Module: DLSW-MIB
The SAP list indicates which SAPs are advertised to
the transport connection defined by this conceptual
row. Only SAPs with even numbers are represented,
in the form of the most significant bit of the first
octet representing the SAP 0, the next most significant
bit representing the SAP 2, to the least significant
bit of the last octet representing the SAP 254. Data
link switching is allowed for those SAPs which have
one in its corresponding bit, not allowed otherwise.
The whole SAP list has to be changed together. Changing
the SAP list affects only new circuit establishments
and has no effect on established circuits.
This list can be used to restrict specific partners
from knowing about all the SAPs used by DLSw on all its
interfaces (these are represented in dlswIfSapList for
each interface). For instance, one may want to run NetBIOS
with some partners but not others.
If a node supports sending run-time capabilities exchange
messages, changes to this object should cause that action.
When to start the run-time capabilities exchange is
implementation-specific.
The DEFVAL below indicates support for SAPs 0, 4, 8, and C.
dlswTConnConfigSapList OBJECT-TYPE SYNTAX OCTET STRING (SIZE(16)) MAX-ACCESS read-create STATUS current DESCRIPTION "The SAP list indicates which SAPs are advertised to the transport connection defined by this conceptual row. Only SAPs with even numbers are represented, in the form of the most significant bit of the first octet representing the SAP 0, the next most significant bit representing the SAP 2, to the least significant bit of the last octet representing the SAP 254. Data link switching is allowed for those SAPs which have one in its corresponding bit, not allowed otherwise. The whole SAP list has to be changed together. Changing the SAP list affects only new circuit establishments and has no effect on established circuits. This list can be used to restrict specific partners from knowing about all the SAPs used by DLSw on all its interfaces (these are represented in dlswIfSapList for each interface). For instance, one may want to run NetBIOS with some partners but not others. If a node supports sending run-time capabilities exchange messages, changes to this object should cause that action. When to start the run-time capabilities exchange is implementation-specific. The DEFVAL below indicates support for SAPs 0, 4, 8, and C." DEFVAL { 'AA000000000000000000000000000000'H } ::= { dlswTConnConfigEntry 9 }
dlswTConnConfigSapList OBJECT-TYPE SYNTAX OCTET STRING(SIZE(16)) ACCESS read-write STATUS mandatory DESCRIPTION "The SAP list indicates which SAPs are advertised to the transport connection defined by this conceptual row. Only SAPs with even numbers are represented, in the form of the most significant bit of the first octet representing the SAP 0, the next most significant bit representing the SAP 2, to the least significant bit of the last octet representing the SAP 254. Data link switching is allowed for those SAPs which have one in its corresponding bit, not allowed otherwise. The whole SAP list has to be changed together. Changing the SAP list affects only new circuit establishments and has no effect on established circuits. This list can be used to restrict specific partners from knowing about all the SAPs used by DLSw on all its interfaces (these are represented in dlswIfSapList for each interface). For instance, one may want to run NetBIOS with some partners but not others. If a node supports sending run-time capabilities exchange messages, changes to this object should cause that action. When to start the run-time capabilities exchange is implementation-specific. The DEFVAL below indicates support for SAPs 0, 4, 8, and C." DEFVAL { 'AA000000000000000000000000000000'h } ::= { dlswTConnConfigEntry 9 }
Automatically extracted from Cisco SNMP v1 MIBs
dlswTConnConfigSapList OBJECT-TYPE SYNTAX OCTET STRING (SIZE(16)) MAX-ACCESS read-create STATUS current DESCRIPTION "The SAP list indicates which SAPs are advertised to the transport connection defined by this conceptual row. Only SAPs with even numbers are represented, in the form of the most significant bit of the first octet representing the SAP 0, the next most significant bit representing the SAP 2, to the least significant bit of the last octet representing the SAP 254. Data link switching is allowed for those SAPs which have one in its corresponding bit, not allowed otherwise. The whole SAP list has to be changed together. Changing the SAP list affects only new circuit establishments and has no effect on established circuits. This list can be used to restrict specific partners from knowing about all the SAPs used by DLSw on all its interfaces (these are represented in dlswIfSapList for each interface). For instance, one may want to run NetBIOS with some partners but not others. If a node supports sending run-time capabilities exchange messages, changes to this object should cause that action. When to start the run-time capabilities exchange is implementation-specific. The DEFVAL below indicates support for SAPs 0, 4, 8, and C." DEFVAL { 'AA000000000000000000000000000000'H } ::= { dlswTConnConfigEntry 9 }
dlswTConnConfigSapList OBJECT-TYPE SYNTAX OCTET STRING (SIZE(16)) MAX-ACCESS read-create STATUS current DESCRIPTION "The SAP list indicates which SAPs are advertised to the transport connection defined by this conceptual row. Only SAPs with even numbers are represented, in the form of the most significant bit of the first octet representing the SAP 0, the next most significant bit representing the SAP 2, to the least significant bit of the last octet representing the SAP 254. Data link switching is allowed for those SAPs which have one in its corresponding bit, not allowed otherwise. The whole SAP list has to be changed together. Changing the SAP list affects only new circuit establishments and has no effect on established circuits. This list can be used to restrict specific partners from knowing about all the SAPs used by DLSw on all its interfaces (these are represented in dlswIfSapList for each interface). For instance, one may want to run NetBIOS with some partners but not others. If a node supports sending run-time capabilities exchange messages, changes to this object should cause that action. When to start the run-time capabilities exchange is implementation-specific. The DEFVAL below indicates support for SAPs 0, 4, 8, and C." DEFVAL { 'AA000000000000000000000000000000'H } ::= { dlswTConnConfigEntry 9 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.46.1.2.2.1.1 | dlswTConnConfigIndex | 0 | 0 | The index to the conceptual row of the table. Negative numbers are not allowed. There are objects defined that point to conceptu… |
| 1.3.6.1.2.1.46.1.2.2.1.2 | dlswTConnConfigTDomain | 0 | 0 | The object identifier which indicates the transport domain of this conceptual row. |
| 1.3.6.1.2.1.46.1.2.2.1.3 | dlswTConnConfigLocalTAddr | 0 | 0 | The local transport address for this conceptual row of the transport connection definition. |
| 1.3.6.1.2.1.46.1.2.2.1.4 | dlswTConnConfigRemoteTAddr | 0 | 0 | The remote transport address. Together with dlswTConnConfigEntryType and dlswTConnConfigGroupDefinition, the object instance of … |
| 1.3.6.1.2.1.46.1.2.2.1.5 | dlswTConnConfigLastModifyTime | 0 | 0 | The time (in hundredths of a second) since the value of any object in this conceptual row except for dlswTConnConfigOpens was las… |
| 1.3.6.1.2.1.46.1.2.2.1.6 | dlswTConnConfigEntryType | 0 | 0 | The object instance signifies the type of entry in the associated conceptual row. The value of `individual' means that the entry… |
| 1.3.6.1.2.1.46.1.2.2.1.7 | dlswTConnConfigGroupDefinition | 0 | 0 | For conceptual rows of `individual' and `global' as specified in dlswTConnConfigEntryType, the instance of this object is `0.0'.… |
| 1.3.6.1.2.1.46.1.2.2.1.8 | dlswTConnConfigSetupType | 0 | 0 | This value of the instance of a conceptual row identifies the behavior of the collection of transport connections that this conce… |
| 1.3.6.1.2.1.46.1.2.2.1.10 | dlswTConnConfigAdvertiseMacNB | 0 | 0 | The value of true indicates that any defined local MAC addresses and NetBIOS names will be advertised to a partner node via initi… |
| 1.3.6.1.2.1.46.1.2.2.1.11 | dlswTConnConfigInitCirRecvWndw | 0 | 0 | The initial circuit receive pacing window size, in the unit of SSP messages, to be used for future transport connections activate… |
| 1.3.6.1.2.1.46.1.2.2.1.12 | dlswTConnConfigOpens | 0 | 0 | Number of times transport connections entered connected state according to the definition of this conceptual row. |
| 1.3.6.1.2.1.46.1.2.2.1.13 | dlswTConnConfigRowStatus | 0 | 0 | This object is used by the manager to create or delete the row entry in the dlswTConnConfigTable following the RowStatus textual … |