| dlswVersion |
.1.3.6.1.4.1.43.2.24.1.1 |
|
This value identifies the particular version of the
DLSw standard supported by this DLSw. The first hexdecimal
value represents the DLSw standard Version number of
this DLSw, the second hexdecimal value represents the
DLSw standard Release number. This information
is exchanged in DLSw Capabilities Exchange.
|
| dlswVendorID |
.1.3.6.1.4.1.43.2.24.1.2 |
|
The value identifies the manufacturer-s IEEE assigned
organizationally Unique Identifier (OUI) of this DLSw.
This information is exchanged in DLSw Capabilities
Exchange.
|
| dlswVersionString |
.1.3.6.1.4.1.43.2.24.1.3 |
|
This value identifies the particular version number
of this DLSw. The format of the actual version
string is vendor-specific. This flows in Capabilities
Exchange messages.
|
| dlswStdPacingSupport |
.1.3.6.1.4.1.43.2.24.1.4 |
|
Adaptive pacing defined in the DLSw Standard allows the
receiving end of the DLSw node to control the amount of
data that can flow over the DLSw cloud. none (1) means
this DLSw node does not support the adaptive pacing
scheme as defined in the DLSw Standard, possibly a
proprietary pacing scheme is used. adaptiveRcvWindow
(2) means this DLSw node supports the DLSw Standard
pacing scheme. This DLSw node must be capable to
adjust its sending window size as instructed by the
partner DLSw and also will adjust its receive window
size accordingly to its resource situation. However,
implementation may choose not to adjust the receive window
size. That is, the only Flow Control Operator will
be sent by this node is the Repeat Window Operator.
fixedRcvWindow (3) indicates this capability.
|
| dlswStatus |
.1.3.6.1.4.1.43.2.24.1.5 |
|
The status of DLSw part of the system. Changing the
value from active to inactive causes DLSw to take
the following actions: (1) disconnect all circuits
through all DLSw partners, (2) disconnect all
transport connections to all DLSw partners, (3)
disconnect all local DLC connections, and (4) stop
processing all DLC connection set-up traffic.
Since these are destructive actions, the user should
query the circuit and transport connection tables in
advance to understand the effect this action will have.
Changing the value from inactive to active causes DLSw
to come up in its initial state, i.e., transport
connection established and ready to bring up circuits.
|
| dlswUpTime |
.1.3.6.1.4.1.43.2.24.1.6 |
|
The time (in hundredths of a second) since the DLSw
portion of the system was last re-initialized.
That is, if dlswState is in the active state,
the time the dlswState entered the active state.
It will remain zero, if the dlswState is in the
inactive state.
|
| dlswVirtualSegmentLFSize |
.1.3.6.1.4.1.43.2.24.1.7 |
|
The largest size of the INFO field (LLC and above)
that virtual segment can send/receive. It does
not include any MAC level (framing) octets.
This value will affect the LF size of circuits
in creation. LF size of an existing circuit
can be found in RIF (Routing Information Field).
|
| dlswResourceNBExclusivity |
.1.3.6.1.4.1.43.2.24.1.8 |
|
The value of true identifies the NETBIOS Names that
are configured in the dlswDirNBTable are the only
ones accessible via this DLSw. Changes to this object
take effect for runtime Capabilities Exchange messages
is implementation choice.
|
| dlswResourceMacExclusivity |
.1.3.6.1.4.1.43.2.24.1.9 |
|
The value of true identifies the MAC addresses that
are configured in the dlswDirMacTable are the only
ones accessible via this DLSw. Changes to this object
take effect for runtime Capabilities Exchange messages
is implementation choice.
|
| dlswTConnStatActiveConnections |
.1.3.6.1.4.1.43.2.24.2.1.1 |
|
The number of transport connections are not in
-disconnected- state.
|
| dlswTConnStatCloseIdles |
.1.3.6.1.4.1.43.2.24.2.1.2 |
|
The number of DLSw connections exited connected state
with all circuits disconnected gracefully. That is,
the transport connection was brought down, by either
this DLSw node or its partner DLSw node, with no
active circuits.
|
| dlswTConnStatCloseBusys |
.1.3.6.1.4.1.43.2.24.2.1.3 |
|
The number of DLSw connections exited connected state
without all circuits disconnected gracefully. That is,
the transport connection was brought down, by either
this DLSw node or its partner DLSw node, with some
active circuits. For instance, transport connection,
e.g, TCP connection, failed.
|
| dlswTConnConfigEntry |
.1.3.6.1.4.1.43.2.24.2.2.1 |
|
Each conceptual row defines a collection of
transport connections.
|
| dlswTConnOperEntry |
.1.3.6.1.4.1.43.2.24.2.3.1 |
| dlswDirMacEntries |
.1.3.6.1.4.1.43.2.24.4.1.1 |
|
The current total number of entries in the dlswDirMacTable.
|
| dlswDirNBEntries |
.1.3.6.1.4.1.43.2.24.4.1.4 |
|
The current total number of entries in the dlswDirNBTable.
|
| dlswDirMacEntry |
.1.3.6.1.4.1.43.2.24.4.2.1.1 |
|
Indexed by dlswDirMacIndex.
|
| dlswDirNBEntry |
.1.3.6.1.4.1.43.2.24.4.2.2.1 |
|
Indexed by dlswDirNBIndex.
|
| dlswActiveCircuits |
.1.3.6.1.4.1.43.2.24.5.1.1 |
|
The number of entries in dlswCircuitTable which are
not in the disconnected state.
|
| dlswCircuitCreates |
.1.3.6.1.4.1.43.2.24.5.1.2 |
|
The total number of entries ever added to dlswCircuitTable,
or reactivated upon exiting -disconnected- state.
|
| dlswCircuitEntry |
.1.3.6.1.4.1.43.2.24.5.2.1 |
| dlswTrapCntlTConn |
.1.3.6.1.4.1.43.2.24.1.10.3 |
|
Indicates whether the DLSw is permitted to emit transport
connection up and down traps. With the value of `enabled'
the DLSw will emit traps when connections enter `connected'
and `disconnected' states. With the value of `disabled'
the DLSw will not emit traps when connections enter of
`connected' and `disconnected' states. With the value
of `partial' the DLSw will only emits transport connection
down traps when the connection is closed with busy.
The changes take effect immediately.
|
| dlswTrapCntlCircuit |
.1.3.6.1.4.1.43.2.24.1.10.4 |
|
Indicates whether the DLSw is permitted to generate
circuit up and down traps. With the value of `enabled'
the DLSw will emit traps when circuits enter `connected'
and `disconnected' states. With the value of `disabled'
the DLSw will not emit traps when circuits enter of
`connected' and `disconnected' states. With the value
of `partial' the DLSw will emit traps only for those
circuits that are initiated by this DLSw, e.g.,
originating the CUR_CS message. The changes take effect
immediately.
|
| dlswTConnConfigIndex |
.1.3.6.1.4.1.43.2.24.2.2.1.1 |
|
The index to the conceptual row of the table.
Non-positive numbers are not allowed. There
are objects defined that point to conceptual
rows of this table with this index value.
Zero is used to denote that no corresponding
row exists.
Index values are assigned by the managed station,
and should not be reused but should continue to
increase in value until they wrap.
|
| dlswTConnConfigTDomain |
.1.3.6.1.4.1.43.2.24.2.2.1.2 |
|
The object identifier which indicates the transport
domain of this conceptual row.
|
| dlswTConnConfigLocalTAddr |
.1.3.6.1.4.1.43.2.24.2.2.1.3 |
|
The local transport address for this conceptual row
of the transport connection definition.
|
| dlswTConnConfigRemoteTAddr |
.1.3.6.1.4.1.43.2.24.2.2.1.4 |
|
The remote transport address. Together with the
dlswTConnConfigRemoteTAddrMask, the object instance
of this conceptual row identifies a collection of
the transport connections that will be either
initiated by this DLSw or initiated by partner
DLSw and accepted by this DLSw.
|
| dlswTConnConfigLastModifyTime |
.1.3.6.1.4.1.43.2.24.2.2.1.5 |
|
The value of dlswUpTime when the value of any object in
this conceptual row was last changed. This value may
be compared to dlswTConnOperConnectTime to determine
whether values in this row are completely valid for a
tranport connection created using this row definition.
|
| dlswTConnConfigEntryType |
.1.3.6.1.4.1.43.2.24.2.2.1.6 |
|
The object instance signifies the type of entry in the
associated conceptual row. The value of -individual-
means that the entry applies to a specific partner DLSw
node as identified by dlswTConnConfigRemoteTAddr and
dlswTConnConfigTDomain. The value of -global-
means that the entry applies to all partner DLSw nodes
of the TDomain. The value of -group' means that the entry
applies to a specific set of DLSw nodes in the TDomain.
Any group definitions are enterprise-specific and are pointed
to by dlswTConnConfigGroupDefinition. In the cases of
-global- and `group', the value in dlswTConnConfigRemoteTAddr
may not have any significance.
|
| dlswTConnConfigGroupDefinition |
.1.3.6.1.4.1.43.2.24.2.2.1.7 |
|
For conceptual rows of -individual- and `global' as
specified in dlswTConnConfigEntryType, the instance
of this object is -0.0-. For conceptual rows of
-group-, the instance points to the specific
group definition.
|
| dlswTConnConfigSetupType |
.1.3.6.1.4.1.43.2.24.2.2.1.8 |
|
This value of the instance of a conceptual row
identifies the behavior of the collection of
transport connections that this conceptual row
defines. The value of activePersistent, activeOnDemand
and passive means this DLSw will accept any transport
connections, initiated by partner DLSw nodes, which
are defined by this conceptual row. The value of
activePersistent means this DLSw will also initiate
the transport connections of this conceptual row and
retry periodically if necessary. The value of
activeOnDemand means this DLSw will initiate a
transport connection of this conceptual row, if
there is a directory cache hits. The value of
other is implementation specific. The value of exclude
means that the specified node is not allowed to be
a partner to this DLSw node. To take a certain
conceptual row definition out of service, a value of
notInService for dlswTConnConfigRowStatus should be
used.
|
| dlswTConnConfigSapList |
.1.3.6.1.4.1.43.2.24.2.2.1.9 |
|
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.
It is up to the implementation exactly when to start the
run-time capabilities exchange.
|
| dlswTConnConfigAdvertiseMacNB |
.1.3.6.1.4.1.43.2.24.2.2.1.10 |
|
The value of true indicates that defined local MAC
addresses and NetBIOS names will be advertised to a
partner node via initial and (if supported) run-time
capabilities exchange messages.
|
| dlswTConnConfigInitCirRecvWndw |
.1.3.6.1.4.1.43.2.24.2.2.1.11 |
|
The initial circuit receive pacing window size, in the unit
of SSP messages, to be used for future transport connections
activated using this table row. The managed node sends this
value as its initial receive pacing window in its initial
capabilities exchange message. Changing this value does not
affect the initial circuit receive pacing window size of
currently active transport connections. If the standard window
pacing scheme is not supported, the value is zero.
A larger receive window value may be appropriate for partners
that are reachable only via physical paths that have longer
network delays.
|
| dlswTConnConfigOpens |
.1.3.6.1.4.1.43.2.24.2.2.1.12 |
|
Number of times transport connections entered
connected state according to the definition of
this conceptual row.
|
| dlswTConnConfigRowStatus |
.1.3.6.1.4.1.43.2.24.2.2.1.13 |
|
This object is used by a Management Station to create
or delete the row entry in the dlswTConnConfigTable
following the RowStatus textual convention. The value
of notInService will be used to take a conceptual
row definition out of use.
|
| dlswTConnOperTDomain |
.1.3.6.1.4.1.43.2.24.2.3.1.1 |
|
The object identifier indicates the transport domain
of this transport connection.
|
| dlswTConnOperRemoteTAddr |
.1.3.6.1.4.1.43.2.24.2.3.1.3 |
|
The remote transport address of this transport connection.
|
| dlswTConnOperLocalTAddr |
.1.3.6.1.4.1.43.2.24.2.3.1.2 |
|
The local transport address for this transport connection.
This value could be different from dlswTConnConfigLocalAddr,
if the value of the latter were changed after this transport
connection was established.
|
| dlswTConnOperEntryTime |
.1.3.6.1.4.1.43.2.24.2.3.1.4 |
|
The value of dlswUpTime when this transport connection
conceptual row was created.
|
| dlswTConnOperConnectTime |
.1.3.6.1.4.1.43.2.24.2.3.1.5 |
|
The value of dlswUpTime when this transport connection
last entered the -connected- state. A value of zero means
this transport connection has never been established.
|
| dlswTConnOperState |
.1.3.6.1.4.1.43.2.24.2.3.1.6 |
|
The state of this transport connection. The transport
connection enters -connecting- state when DLSw makes
a connection request to the transport layer. Once initial
Capabilities Exchange is sent, the transport connection enters
enters -initCapExchange- state. When partner capabilities have been
determined and the transport connection is ready for sending
CanUReach (CUR) messages, it moves to the -connected- state.
When DLSw is in the process of bringing down the connection,
it is in the -disconnecting- state. When the transport layer
indicates one of its connections is disconnected, the transport
connection moves to the -disconnected- state.
Whereas all of the values will be returned in response to a
management protocol retrieval operation, only two values may
be specified in a management protocol set operation, -quiescing-
and -disconnecting-. Changing the value to -quiescing- prevents
new circuits from being established, and will cause a transport
disconnect when the last circuit on the connection goes away.
Changing the value to -disconnecting- will force off all circuits
immediately and bring the connection to -disconnected- state.
|
| dlswTConnOperConfigIndex |
.1.3.6.1.4.1.43.2.24.2.3.1.7 |
|
The value of dlswTConnConfigIndex of the dlswTConnConfigEntry
that governs the configuration information used by this
dlswTConnOperEntry. A management station can therefore
normally examine both configured and operational information
for this transport connection.
This value is zero if the corresponding dlswTConnConfigEntry
was deleted after the creation of this dlswTConnOperEntry.
If some fields in the former were changed but the conceptual
row was not deleted, some configuration information may not
be valid for this operational transport connection. A network
management application can compare dlswTConnOperConnectTime and
dlswTConnConfigLastModifyTime to determine if this condition
exists.
|
| dlswTConnOperFlowCntlMode |
.1.3.6.1.4.1.43.2.24.2.3.1.8 |
|
The flow control mechanism in use on this transport connection.
This value is undetermined (1) before the mode of flow control
can be established on a new tranport connection (i.e., after
CapEx is sent but before Capex or other SSP control messages
have been received). Pacing (2) indicates that the standard
RFC 1795 pacing mechanism is in use. Other (3) may be either
the RFC 1434+ xBusy mechanism operating to a back-level DLSw,
or a vendor-specific flow control method. Whether it is xBusy
or not can be inferred from dlswTConnOperPartnerVersion.
|
| dlswTConnOperPartnerVersion |
.1.3.6.1.4.1.43.2.24.2.3.1.9 |
|
This value identifies which version (first octet) and release
(second octect) of the DLSw standard is supported by this
partner DLSw. This information is obtained from a DLSw
capabilities exchange message received from the partner DLSw.
A string of zero length is returned before a Capabilities
Exchange message is received, or if one is never received.
A conceptual row with a dlswTConnOperState of -connected- but
a zero length partner version indicates that the partner is
a non-standard DLSw partner.
If an implementation chooses to keep dlswTConnOperEntrys in
the -disconnected- state, this value should remain unchanged.
|
| dlswTConnOperPartnerVendorID |
.1.3.6.1.4.1.43.2.24.2.3.1.10 |
|
This value identifies the IEEE-assigned organizationally
Unique Identifier (OUI) of the maker of this partner
DLSw. This information is obtained from a DLSw
capabilities exchange message received from the partner DLSw.
A string of zero length is returned before a Capabilities
Exchange message is received, or if one is never received.
If an implementation chooses to keep dlswTConnOperEntrys in
the -disconnected- state, this value should remain unchanged.
|
| dlswTConnOperPartnerVersionStr |
.1.3.6.1.4.1.43.2.24.2.3.1.11 |
|
This value identifies the particular product version (e.g.,
product name, code level, fix level) of this partner DLSw.
The format of the actual version string is vendor-specific.
This information is obtained from a DLSw capabilities exchange
message received from the partner DLSw.
A string of zero length is returned before a Capabilities
Exchange message is received, if one is never received, or
if one is received but it does not contain a version string.
If an implementation chooses to keep dlswTConnOperEntrys in
the -disconnected- state, this value should remain unchanged.
|
| dlswTConnOperPartnerInitPacingWndw |
.1.3.6.1.4.1.43.2.24.2.3.1.12 |
|
The value of the partner initial receive pacing window. This
is our initial send pacing window for all new circuits on this
transport connection, as modified and granted by the first flow
control indication the partner sends on each circuit.
This information is obtained from a DLSw capabilities exchange
message received from the partner DLSw.
A value of zero is returned before a Capabilities
Exchange message is received, or if one is never received.
If an implementation chooses to keep dlswTConnOperEntrys in
the -disconnected- state, this value should remain unchanged.
|
| dlswTConnOperPartnerSapList |
.1.3.6.1.4.1.43.2.24.2.3.1.13 |
|
The Supported SAP List received in the capabilities
exchange message from the partner DLSw. This list has
the same format described for dlswTConnConfigSapList.
A string of zero length is returned before a Capabilities
Exchange message is received, or if one is never received.
If an implementation chooses to keep dlswTConnOperEntrys in
the -disconnected- state, this value should remain unchanged.
|
| dlswTConnOperPartnerNBExcl |
.1.3.6.1.4.1.43.2.24.2.3.1.14 |
|
The value of true signifies that the NetBIOS names received
from this partner in the NetBIOS name list in its capabilities
exchange message are the only NetBIOS names reachable by
that partner. -False- indicates that other NetBIOS names may
be reachable. -False- should be returned before a Capabilities
Exchange message is received, if one is never received, or if
one is received without a NB Name Exclusivity CV.
If an implementation chooses to keep dlswTConnOperEntrys in
the -disconnected- state, this value should remain unchanged.
|
| dlswTConnOperPartnerMacExcl |
.1.3.6.1.4.1.43.2.24.2.3.1.15 |
|
The value of true signifies that the MAC addresses received
from this partner in the MAC address list in its capabilities
exchange message are the only MAC addresses reachable by
that partner. -False- indicates that other MAC addresses may
be reachable. -False- should be returned before a Capabilities
Exchange message is received, if one is never received, or if
one is received without a MAC Address Exclusivity CV.
If an implementation chooses to keep dlswTConnOperEntrys in
the -disconnected- state, this value should remain unchanged.
|
| dlswTConnOperPartnerNBInfo |
.1.3.6.1.4.1.43.2.24.2.3.1.16 |
|
It is up to this DSLw whether to keep either none, some,
or all of the NetBIOS name list that was received in
the capabilities exchange message sent by this partner DLSw.
This object identifies how much information was kept by
this DLSw. These names are stored as userConfigured
remote entries in dlswDirNBTable.
A value of (4), notApplicable, should be returned before
a Capabilities Exchange message is received, or if one is
never received.
If an implementation chooses to keep dlswTConnOperEntrys in
the -disconnected- state, this value should remain unchanged.
|
| dlswTConnOperPartnerMacInfo |
.1.3.6.1.4.1.43.2.24.2.3.1.17 |
|
It is up to this DLSw whether to keep either none, some,
or all of the MAC address list that was received in the
capabilities exchange message sent by this partner DLSw.
This object identifies how much information was kept by
this DLSw. These names are stored as userConfigured
remote entries in dlswDirMACTable.
A value of (4), notApplicable, should be returned before
a Capabilities Exchange message is received, or if one is
never received.
If an implementation chooses to keep dlswTConnOperEntrys in
the -disconnected- state, this value should remain unchanged.
|
| dlswTConnOperDiscTime |
.1.3.6.1.4.1.43.2.24.2.3.1.18 |
|
The value of dlswUpTime when dlswTConnOperState last
entered -disconnected- state.
|
| dlswTConnOperDiscReason |
.1.3.6.1.4.1.43.2.24.2.3.1.19 |
|
This object signifies the reason that either prevented the
transport connection from entering the connected state, or
caused the transport connection to enter the disconnected state.
|
| dlswTConnOperDiscActiveCir |
.1.3.6.1.4.1.43.2.24.2.3.1.20 |
|
The number of circuits active (not in DISCONNECTED state)
at the time the transport connection was last disconnected.
This value is zero if the transport connection has never
been connected.
|
| dlswTConnOperInDataPkts |
.1.3.6.1.4.1.43.2.24.2.3.1.21 |
|
The number of Switch-to-Switch Protocol (SSP) messages of
type DGRMFRAME, DATAFRAME, or INFOFRAME received on this
transport connection.
|
| dlswTConnOperOutDataPkts |
.1.3.6.1.4.1.43.2.24.2.3.1.22 |
|
The number of Switch-to-Switch Protocol (SSP) messages of
type DGRMFRAME, DATAFRAME, or INFOFRAME transmitted on this
transport connection.
|
| dlswTConnOperInDataOctets |
.1.3.6.1.4.1.43.2.24.2.3.1.23 |
|
The number octets in Switch-to-Switch Protocol (SSP) messages
of type DGRMFRAME, DATAFRAME, or INFOFRAME received on this
transport connection. Each message is counted starting with
the first octet following the SSP message header.
|
| dlswTConnOperOutDataOctets |
.1.3.6.1.4.1.43.2.24.2.3.1.24 |
|
The number octets in Switch-to-Switch Protocol (SSP) messages
of type DGRMFRAME, DATAFRAME, or INFOFRAME transmitted on this
transport connection. Each message is counted starting with
the first octet following the SSP message header.
|
| dlswTConnOperInCntlPkts |
.1.3.6.1.4.1.43.2.24.2.3.1.25 |
|
The number of Switch-to-Switch Protocol (SSP) messages
received on this transport connection which were not of
type DGRMFRAME, DATAFRAME, or INFOFRAME.
|
| dlswTConnOperOutCntlPkts |
.1.3.6.1.4.1.43.2.24.2.3.1.26 |
|
The number of Switch-to-Switch Protocol (SSP) messages of
transmitted on this transport connection which were not of
type DGRMFRAME, DATAFRAME, or INFOFRAME.
|
| dlswTConnOperCURexSents |
.1.3.6.1.4.1.43.2.24.2.3.1.27 |
|
The number of CanUReach_ex messages sent on this transport
connection.
|
| dlswTConnOperICRexRcvds |
.1.3.6.1.4.1.43.2.24.2.3.1.28 |
|
The number of ICanReach_ex messages received on this transport
connection.
|
| dlswTConnOperCURexRcvds |
.1.3.6.1.4.1.43.2.24.2.3.1.29 |
|
The number of CanUReach_ex messages received on this transport
connection.
|
| dlswTConnOperICRexSents |
.1.3.6.1.4.1.43.2.24.2.3.1.30 |
|
The number of ICanReach_ex messages sent on this transport
connection.
|
| dlswTConnOperNQexSents |
.1.3.6.1.4.1.43.2.24.2.3.1.31 |
|
The number of NetBIOS_NQ_ex (NetBIOS Name Query-explorer) messages
sent on this transport connection.
|
| dlswTConnOperNRexRcvds |
.1.3.6.1.4.1.43.2.24.2.3.1.32 |
|
The number of NETBIOS_NR_ex (NetBIOS Name Recognized-explorer)
messages received on this transport connection.
|
| dlswTConnOperNQexRcvds |
.1.3.6.1.4.1.43.2.24.2.3.1.33 |
|
The number of NETBIOS_NQ_ex messages received on this
transport connection.
|
| dlswTConnOperNRexSents |
.1.3.6.1.4.1.43.2.24.2.3.1.34 |
|
The number of NETBIOS_NR_ex messages sent on this transport
connection.
|
| dlswTConnOperCirCreates |
.1.3.6.1.4.1.43.2.24.2.3.1.35 |
|
The number of times that circuits entered -circuit_established-
state (not counting transitions from -circuit_restart-).
|
| dlswTConnOperCircuits |
.1.3.6.1.4.1.43.2.24.2.3.1.36 |
|
The number of currently active circuits on this transport
connection, where -active- means not in -disconnected- state.
|
| dlswDirMacIndex |
.1.3.6.1.4.1.43.2.24.4.2.1.1.1 |
|
Uniquely identifies a conceptual row of this table.
|
| dlswDirMacMac |
.1.3.6.1.4.1.43.2.24.4.2.1.1.2 |
|
The MAC address, together with the dlswDirMacMask,
specifies a set of MAC addresses that are defined or
discovered through an interface or partner DLSw nodes.
|
| dlswDirMacMask |
.1.3.6.1.4.1.43.2.24.4.2.1.1.3 |
|
The MAC address mask, together with the dlswDirMacMac,
specifies a set of MAC addresses that are defined or
discovered through an interface or partner DLSw nodes.
|
| dlswDirMacEntryType |
.1.3.6.1.4.1.43.2.24.4.2.1.1.4 |
|
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.
|
| dlswDirMacLocationType |
.1.3.6.1.4.1.43.2.24.4.2.1.1.5 |
|
The location of the resource (or a collection of
resources using a mask) of this conceptual row
is either (1) local - the resource is reachable
via an interface, or (2) remote - the resource
is reachable via a partner DLSw node (or a set
of partner DLSw nodes).
|
| dlswDirMacLocation |
.1.3.6.1.4.1.43.2.24.4.2.1.1.6 |
|
Points to either the ifEntry, dlswTConnConfigEntry,
dlswTConnOperEntry, 0.0, or something that is implementation
specific. It identifies the location of the MAC address
(or the collection of MAC addresses.)
|
| dlswDirMacStatus |
.1.3.6.1.4.1.43.2.24.4.2.1.1.7 |
|
This object specifies whether DLSw currently believes
the MAC address to be accessible at the specified location.
The value `notReachable' allows a configured resource
definition to be taken out of service when a search to
that resource fails (avoiding a repeat of the search).
|
| dlswDirMacLFSize |
.1.3.6.1.4.1.43.2.24.4.2.1.1.8 |
|
The largest size of the MAC INFO field (LLC header and data)
that a circuit to the MAC address can carry through this path.
|
| dlswDirMacRowStatus |
.1.3.6.1.4.1.43.2.24.4.2.1.1.9 |
|
This object is used by a Management Station to create
or delete the row entry in the dlswDirMacTable
following the RowStatus textual convention.
|
| dlswDirNBIndex |
.1.3.6.1.4.1.43.2.24.4.2.2.1.1 |
|
Uniquely identifies a conceptual row of this table.
|
| dlswDirNBName |
.1.3.6.1.4.1.43.2.24.4.2.2.1.2 |
|
The NetBIOS name (including `any char' and `wildcard' characters)
specifies a set of NetBIOS names that are defined or discovered
through an interface or partner DLSw nodes.
|
| dlswDirNBNameType |
.1.3.6.1.4.1.43.2.24.4.2.2.1.3 |
|
Whether dlswDirNBName represents an (or a set of) individual
or group NetBIOS name(s).
|
| dlswDirNBEntryType |
.1.3.6.1.4.1.43.2.24.4.2.2.1.4 |
|
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.
|
| dlswDirNBLocationType |
.1.3.6.1.4.1.43.2.24.4.2.2.1.5 |
|
The location of the resource (or a collection of resources
using any char/wildcard characters) of this conceptual row
is either (1) local - the resource is reachable via an
interface, or (2) remote - the resource is reachable via a
a partner DLSw node (or a set of partner DLSw nodes).
|
| dlswDirNBLocation |
.1.3.6.1.4.1.43.2.24.4.2.2.1.6 |
|
Points to either the ifEntry, dlswTConnConfigEntry,
dlswTConnOperEntry, 0.0, or something that is implementation
specific. It identifies the location of the NetBIOS name
or the set of NetBIOS names.
|
| dlswDirNBStatus |
.1.3.6.1.4.1.43.2.24.4.2.2.1.7 |
|
This object specifies whether DLSw currently believes
the NetBIOS name to be accessible at the specified location.
The value `notReachable' allows a configured resource
definition to be taken out of service when a search to
that resource fails (avoiding a repeat of the search).
|
| dlswDirNBLFSize |
.1.3.6.1.4.1.43.2.24.4.2.2.1.8 |
|
The largest size of the MAC INFO field (LLC header and data)
that a circuit to the NB name can carry through this path.
|
| dlswDirNBRowStatus |
.1.3.6.1.4.1.43.2.24.4.2.2.1.9 |
|
This object is used by a Management Station to create
or delete the row entry in the dlswDirNBTable
following the RowStatus textual convention.
|
| dlswCircuitS1Mac |
.1.3.6.1.4.1.43.2.24.5.2.1.1 |
|
The MAC Address of End Station 1 (S1) used for this circuit.
|
| dlswCircuitS1Sap |
.1.3.6.1.4.1.43.2.24.5.2.1.2 |
|
The SAP at End Station 1 (S1) used for this circuit.
|
| dlswCircuitS2Mac |
.1.3.6.1.4.1.43.2.24.5.2.1.8 |
|
The MAC Address of End Station 2 (S2) used for this circuit.
|
| dlswCircuitS2Sap |
.1.3.6.1.4.1.43.2.24.5.2.1.9 |
|
The SAP at End Station 2 (S2) used for this circuit.
|
| dlswCircuitS1IfIndex |
.1.3.6.1.4.1.43.2.24.5.2.1.3 |
|
The IfEntry index of the local interface through which S1
can be reached.
|
| dlswCircuitS1DlcType |
.1.3.6.1.4.1.43.2.24.5.2.1.4 |
|
The DLC protocol in use between the DLSw node and S1.
|
| dlswCircuitS1RouteInfo |
.1.3.6.1.4.1.43.2.24.5.2.1.5 |
|
If source-route bridging is in use between the DLSw
node and S1, this is the routing information field
describing the path between the two devices.
Otherwise the value will be an OCTET STRING of
zero length.
|
| dlswCircuitS1CircuitId |
.1.3.6.1.4.1.43.2.24.5.2.1.6 |
|
The Circuit ID assigned by this DLSw node to this circuit.
The first four octets are the DLC port Id, and
the second four octets are the Data Link Correlator.
If the DLSw SSP was not used to establish this circuit,
the value will be a string of zero length.
|
| dlswCircuitS1Dlc |
.1.3.6.1.4.1.43.2.24.5.2.1.7 |
|
Points to a conceptual row of the underlying DLC MIB,
which could either be the standard SDLC or LLC MIBs, or an
enterprise-specific DLC MIB.
|
| dlswCircuitS2Location |
.1.3.6.1.4.1.43.2.24.5.2.1.10 |
|
The location of End Station 2 (S2).
If the location of End Station 2 is local, the
interface information will be available in the
conceptual row whose S1 and S2 are the S2 and
the S1 of this conceptual row, respectively.
|
| dlswCircuitS2TDomain |
.1.3.6.1.4.1.43.2.24.5.2.1.11 |
|
If the location of End Station 2 is remote,
this value is the transport domain of the
transport protocol the circuit is running
over. Otherwise, the value is 0.0.
|
| dlswCircuitS2TAddress |
.1.3.6.1.4.1.43.2.24.5.2.1.12 |
|
If the location of End Station 2 is remote,
this object contains the address of the partner
DLSw, else it will be an OCTET STRING of zero length.
|
| dlswCircuitS2CircuitId |
.1.3.6.1.4.1.43.2.24.5.2.1.13 |
|
The Circuit ID assigned to this circuit by the partner
DLSw node. The first four octets are the DLC port Id, and
the second four octets are the Data Link Correlator.
If the DLSw SSP was not used to establish this circuit,
the value will be a string of zero length.
|
| dlswCircuitOrigin |
.1.3.6.1.4.1.43.2.24.5.2.1.14 |
|
This object specifies which of the two end stations
initiated the establishment of this circuit.
|
| dlswCircuitEntryTime |
.1.3.6.1.4.1.43.2.24.5.2.1.15 |
|
The value of dlswUpTime when this circuit table
conceptual row was created.
|
| dlswCircuitStateTime |
.1.3.6.1.4.1.43.2.24.5.2.1.16 |
|
The value of dlswUpTime when this circuit entered the
current state.
|
| dlswCircuitState |
.1.3.6.1.4.1.43.2.24.5.2.1.17 |
|
The current state of this circuit. The implementation
may choose to keep entries for some period of time after
circuit disconnect, so the network management station can
gather the time and cause of disconnection.
While all of the specified values may be returned from a GET
operation, the only SETable value is -disconnectPending-.
When this value is set, DLSw should perform the appropriate
action given its previous state (e.g., send HALT_DL if the
state was -connected-) to bring the circuit down to the
-disconnected- state. Both the partner DLSw and local end
station(s) should be notified as appropriate.
This MIB provides no facility to re-establish a disconnected
circuit, because in DLSw this should be an end station-driven
function.
|
| dlswCircuitPriority |
.1.3.6.1.4.1.43.2.24.5.2.1.18 |
|
The transmission priority of this circuit as understood by
this DLSw node. This value is determined by the two DLSw
nodes at circuit startup time. If this DLSw node does not
support DLSw circuit priority, the value -unsupported- should
be returned.
|
| dlswCircuitFCSendGrantedUnits |
.1.3.6.1.4.1.43.2.24.5.2.1.19 |
|
The number of paced SSP messages that this DLSw is currently
authorized to send on this circuit before it must stop and
wait for an additional flow control indication from the
partner DLSw.
The value zero should be returned if this circuit is not
running the DLSw pacing protocol.
|
| dlswCircuitFCSendCurrentWndw |
.1.3.6.1.4.1.43.2.24.5.2.1.20 |
|
The current window size that this DLSw is using in its role
as a data sender. This is the value by which this DLSw would
increase the number of messages it is authorized to send, if
it were to receive a flow control indication with the bits
specifying -repeat window-.
The value zero should be returned if this circuit is not
running the DLSw pacing protocol.
|
| dlswCircuitFCRecvGrantedUnits |
.1.3.6.1.4.1.43.2.24.5.2.1.21 |
|
The current number of paced SSP messages that this DLSw has
authorized the partner DLSw to send on this circuit before
the partner DLSw must stop and wait for an additional flow
control indication from this DLSw.
The value zero should be returned if this circuit is not
running the DLSw pacing protocol.
|
| dlswCircuitFCRecvCurrentWndw |
.1.3.6.1.4.1.43.2.24.5.2.1.22 |
|
The current window size that this DLSw is using in its role
as a data receiver. This is the number of additional paced
SSP messages that this DLSw would be authorizing its DLSw
partner to send, if this DLSw were to send a flow control
indication with the bits specifying -repeat window-.
The value zero should be returned if this circuit is not
running the DLSw pacing protocol.
|
| dlswCircuitFCLargestRecvGranted |
.1.3.6.1.4.1.43.2.24.5.2.1.23 |
|
The largest receive window size granted by this DLSw during
the current activation of this circuit. This is not the
largest number of messages granted at any time, but the
largest window size as represented by FCIND operator bits.
The value zero should be returned if this circuit is not
running the DLSw pacing protocol.
|
| dlswCircuitFCLargestSendGranted |
.1.3.6.1.4.1.43.2.24.5.2.1.24 |
|
The largest send (with respect to this DLSw) window size
granted by the partner DLSw during the current activation of
this circuit.
The value zero should be returned if this circuit is not
running the DLSw pacing protocol.
|
| dlswCircuitFCHalveWndwSents |
.1.3.6.1.4.1.43.2.24.5.2.1.25 |
|
The number of Halve Window operations this DLSw has sent on
this circuit, in its role as a data receiver.
The value zero should be returned if this circuit is not
running the DLSw pacing protocol.
|
| dlswCircuitFCResetOpSents |
.1.3.6.1.4.1.43.2.24.5.2.1.26 |
|
The number of Reset Window operations this DLSw has sent on
this circuit, in its role as a data receiver.
The value zero should be returned if this circuit is not
running the DLSw pacing protocol.
|
| dlswCircuitFCHalveWndwRcvds |
.1.3.6.1.4.1.43.2.24.5.2.1.27 |
|
The number of Halve Window operations this DLSw has received on
this circuit, in its role as a data sender.
The value zero should be returned if this circuit is not
running the DLSw pacing protocol.
|
| dlswCircuitFCResetOpRcvds |
.1.3.6.1.4.1.43.2.24.5.2.1.28 |
|
The number of Reset Window operations this DLSw has received on
this circuit, in its role as a data sender.
The value zero should be returned if this circuit is not
running the DLSw pacing protocol.
|
| dlswCircuitDiscReasonLocal |
.1.3.6.1.4.1.43.2.24.5.2.1.29 |
|
The reason why this circuit was last disconnected, as seen
by this DLSw node.
This object is present only if the implementation keeps circuit
table entries around for some period after circuit disconnect.
|
| dlswCircuitDiscReasonRemote |
.1.3.6.1.4.1.43.2.24.5.2.1.30 |
|
The generic reason code why this circuit was last disconnected,
as reported by the DLSw partner in a HALT_DL or HALT_DL_NOACK.
If the partner does not send a reason code in these messages, or
the DLSw implementation does not report receiving one, the value
-unknown- is returned.
This object is present only if the implementation keeps circuit
table entries around for some period after circuit disconnect.
|
| dlswCircuitDiscReasonRemoteData |
.1.3.6.1.4.1.43.2.24.5.2.1.31 |
|
Implementation-specific data reported by the DLSw partner in a
HALT_DL or HALT_DL_NOACK, to help specify how and why this
circuit was last disconnected. If the partner does not send
this data in these messages, or the DLSw implementation does
not report receiving it, a string of zero length is returned.
This object is present only if the implementation keeps circuit
table entries around for some period after circuit disconnect.
|
