The cause of the creation of this conceptual row.
It could be one of the three methods: (1) user
configured, including via management protocol
set operations, configuration file, command line
or equivalent methods; (2) learned from the
partner DLSw Capabilities Exchange messages;
and (3) dynamic, e.g., learned from ICanReach
messages, or LAN explorer frames. Since only
individual MAC addresses can be dynamically learned,
dynamic entries will all have a mask of all FFs.
The public versus private distinction for user-
configured resources applies only to local resources
(UC remote resources are private), and indicates
whether that resource should be advertised in
capabilities exchange messages sent by this node.
Parsed from file DLSW-MIB.mib
Module: DLSW-MIB
The cause of the creation of this conceptual row.
It could be one of the three methods: (1) user
configured, including via management protocol
set operations, configuration file, command line
or equivalent methods; (2) learned from the
partner DLSw Capabilities Exchange messages;
and (3) dynamic, e.g., learned from ICanReach
messages, or LAN explorer frames. Since only
individual MAC addresses can be dynamically learned,
dynamic entries will all have a mask of all FFs.
The public versus private distinction for user-
configured resources applies only to local resources
(UC remote resources are private), and indicates
whether that resource should be advertised in
capabilities exchange messages sent by this node.
dlswDirMacEntryType OBJECT-TYPE
SYNTAX INTEGER {
other(1),
userConfiguredPublic(2),
userConfiguredPrivate(3),
partnerCapExMsg(4),
dynamic(5)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The cause of the creation of this conceptual row.
It could be one of the three methods: (1) user
configured, including via management protocol
set operations, configuration file, command line
or equivalent methods; (2) learned from the
partner DLSw Capabilities Exchange messages;
and (3) dynamic, e.g., learned from ICanReach
messages, or LAN explorer frames. Since only
individual MAC addresses can be dynamically learned,
dynamic entries will all have a mask of all FFs.
The public versus private distinction for user-
configured resources applies only to local resources
(UC remote resources are private), and indicates
whether that resource should be advertised in
capabilities exchange messages sent by this node."
DEFVAL { userConfiguredPublic }
View at oid-info.com
The cause of the creation of this conceptual row.
It could be one of the three methods: (1) user
configured, including via management protocol
set operations, configuration file, command line
or equivalent methods; (2) learned from the
partner DLSw Capabilities Exchange messages;
and (3) dynamic, e.g., learned from ICanReach
messages, or LAN explorer frames. Since only
individual MAC addresses can be dynamically learned,
dynamic entries will all have a mask of all FFs.
The public versus private distinction for user-
configured resources applies only to local resources
(UC remote resources are private), and indicates
whether that resource should be advertised in
capabilities exchange messages sent by this node.
Parsed from file rfc2024-Data-Link-Switches.mib.txt
Company: None
Module: DLSW-MIB
The cause of the creation of this conceptual row.
It could be one of the three methods: (1) user
configured, including via management protocol
set operations, configuration file, command line
or equivalent methods; (2) learned from the
partner DLSw Capabilities Exchange messages;
and (3) dynamic, e.g., learned from ICanReach
messages, or LAN explorer frames. Since only
individual MAC addresses can be dynamically learned,
dynamic entries will all have a mask of all FFs.
The public versus private distinction for user-
configured resources applies only to local resources
(UC remote resources are private), and indicates
whether that resource should be advertised in
capabilities exchange messages sent by this node.
dlswDirMacEntryType OBJECT-TYPE SYNTAX INTEGER { other (1), userConfiguredPublic (2), userConfiguredPrivate (3), partnerCapExMsg (4), dynamic (5) } MAX-ACCESS read-create STATUS current DESCRIPTION "The cause of the creation of this conceptual row. It could be one of the three methods: (1) user configured, including via management protocol set operations, configuration file, command line or equivalent methods; (2) learned from the partner DLSw Capabilities Exchange messages; and (3) dynamic, e.g., learned from ICanReach messages, or LAN explorer frames. Since only individual MAC addresses can be dynamically learned, dynamic entries will all have a mask of all FFs. The public versus private distinction for user- configured resources applies only to local resources (UC remote resources are private), and indicates whether that resource should be advertised in capabilities exchange messages sent by this node." DEFVAL { userConfiguredPublic } ::= { dlswDirMacEntry 4 }
dlswDirMacEntryType OBJECT-TYPE SYNTAX INTEGER { other(1), userConfiguredPublic(2), userConfiguredPrivate(3), partnerCapExMsg(4), dynamic(5) } ACCESS read-write STATUS mandatory DESCRIPTION "The cause of the creation of this conceptual row. It could be one of the three methods: (1) user configured, including via management protocol set operations, configuration file, command line or equivalent methods; (2) learned from the partner DLSw Capabilities Exchange messages; and (3) dynamic, e.g., learned from ICanReach messages, or LAN explorer frames. Since only individual MAC addresses can be dynamically learned, dynamic entries will all have a mask of all FFs. The public versus private distinction for user- configured resources applies only to local resources (UC remote resources are private), and indicates whether that resource should be advertised in capabilities exchange messages sent by this node." DEFVAL { userConfiguredPublic } ::= { dlswDirMacEntry 4 }
Automatically extracted from Cisco SNMP v1 MIBs
dlswDirMacEntryType OBJECT-TYPE SYNTAX INTEGER { other (1), userConfiguredPublic (2), userConfiguredPrivate (3), partnerCapExMsg (4), dynamic (5) } MAX-ACCESS read-create STATUS current DESCRIPTION "The cause of the creation of this conceptual row. It could be one of the three methods: (1) user configured, including via management protocol set operations, configuration file, command line or equivalent methods; (2) learned from the partner DLSw Capabilities Exchange messages; and (3) dynamic, e.g., learned from ICanReach messages, or LAN explorer frames. Since only individual MAC addresses can be dynamically learned, dynamic entries will all have a mask of all FFs. The public versus private distinction for user- configured resources applies only to local resources (UC remote resources are private), and indicates whether that resource should be advertised in capabilities exchange messages sent by this node." DEFVAL { userConfiguredPublic } ::= { dlswDirMacEntry 4 }
dlswDirMacEntryType OBJECT-TYPE SYNTAX INTEGER { other (1), userConfiguredPublic (2), userConfiguredPrivate (3), partnerCapExMsg (4), dynamic (5) } MAX-ACCESS read-create STATUS current DESCRIPTION "The cause of the creation of this conceptual row. It could be one of the three methods: (1) user configured, including via management protocol set operations, configuration file, command line or equivalent methods; (2) learned from the partner DLSw Capabilities Exchange messages; and (3) dynamic, e.g., learned from ICanReach messages, or LAN explorer frames. Since only individual MAC addresses can be dynamically learned, dynamic entries will all have a mask of all FFs. The public versus private distinction for user- configured resources applies only to local resources (UC remote resources are private), and indicates whether that resource should be advertised in capabilities exchange messages sent by this node." DEFVAL { userConfiguredPublic } ::= { dlswDirMacEntry 4 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.46.1.4.2.1.1.1 | dlswDirMacIndex | 0 | 0 | Uniquely identifies a conceptual row of this table. |
| 1.3.6.1.2.1.46.1.4.2.1.1.2 | dlswDirMacMac | 0 | 0 | The MAC address, together with the dlswDirMacMask, specifies a set of MAC addresses that are defined or discovered through an int… |
| 1.3.6.1.2.1.46.1.4.2.1.1.3 | dlswDirMacMask | 0 | 0 | The MAC address mask, together with the dlswDirMacMac, specifies a set of MAC addresses that are defined or discovered through an… |
| 1.3.6.1.2.1.46.1.4.2.1.1.5 | dlswDirMacLocationType | 0 | 0 | The location of the resource (or a collection of resources using a mask) of this conceptual row is either (1) local - the resourc… |
| 1.3.6.1.2.1.46.1.4.2.1.1.6 | dlswDirMacLocation | 0 | 0 | Points to either the ifEntry, dlswTConnConfigEntry, dlswTConnOperEntry, 0.0, or something that is implementation specific. It id… |
| 1.3.6.1.2.1.46.1.4.2.1.1.7 | dlswDirMacStatus | 0 | 0 | This object specifies whether DLSw currently believes the MAC address to be accessible at the specified location. The value `notR… |
| 1.3.6.1.2.1.46.1.4.2.1.1.8 | dlswDirMacLFSize | 0 | 0 | The largest size of the MAC INFO field (LLC header and data) that a circuit to the MAC address can carry through this path. |
| 1.3.6.1.2.1.46.1.4.2.1.1.9 | dlswDirMacRowStatus | 0 | 0 | This object is used by the manager to create or delete the row entry in the dlswDirMacTable following the RowStatus textual conve… |