| OID | 1.3.6.1.2.1.46.1.4.2.2.1.4 |
| Module | DLSW-MIB (CISCO) |
| Nom | dlswDirNBEntryType |
| Acces | readwrite |
| 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 test frames. Since only actual
NetBIOS names can be dynamically learned, dynamic
entries will not contain any char or wildcard
characters.
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. |
| Syntaxe | Enumeration (1-other, 2-userConfiguredPublic, 3-userConfiguredPrivate, 4-partnerCapExMsg, 5-dynamic) |
| Module | DLSW-MIB (ietf) |
| Nom | dlswDirNBEntryType |
| Acces | readwrite |
| 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 test frames. Since only actual
NetBIOS names can be dynamically learned, dynamic
entries will not contain any char or wildcard
characters.
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. |
| Syntaxe | Enumeration (1-other, 2-userConfiguredPublic, 3-userConfiguredPrivate, 4-partnerCapExMsg, 5-dynamic) |