snaNodeAdminIndex |
.1.3.6.1.2.1.34.1.1.1.1.1 |
Index used to uniquely identify each Node instance.
If an Agent creates the entry, then it will assign
this number otherwise a Management Station
generates a random number when it reserves the
entry for creation.
|
snaNodeAdminName |
.1.3.6.1.2.1.34.1.1.1.1.2 |
The value indicates the desired name of the
Node for use during Node activation.
In Type 2.1 networks, this is a fully-qualified name,
meaning that the Node name is preceded by the NetId (if
present) with a period as the delimiter.
A write operation to this object will
not change the operational value reflected
in snaNodeOperName until the Node has
been re-activated (e.g., after the next initialization
of the SNA services).
|
snaNodeAdminType |
.1.3.6.1.2.1.34.1.1.1.1.3 |
The value indicates the type of SNA Node.
A write operation to this object will
not change the operational value reflected
in snaNodeOperType until the Node has
been re-activated (e.g., after the next initialization
of the SNA services).
|
snaNodeAdminXidFormat |
.1.3.6.1.2.1.34.1.1.1.1.4 |
The value indicates the type of XID format used for
this Node. Note that there is no format type 2.
A write operation to this object will
not change the operational value reflected
in snaNodeOperAdminXidFormat until the Node has
been re-activated (e.g., after the next initialization
of the SNA services).
|
snaNodeAdminBlockNum |
.1.3.6.1.2.1.34.1.1.1.1.5 |
The value indicates the block number for this Node
instance. It is the first 3 hexadecimal digits of the
SNA Node id.
A write operation to this object will
not change the operational value reflected
in snaNodeOperBlockNum until the Node has
been re-activated (e.g., after the next initialization
of the SNA services).
|
snaNodeAdminIdNum |
.1.3.6.1.2.1.34.1.1.1.1.6 |
The value indicates the ID number for this Node
instance. This is the last 5 hexadecimal digits of
the SNA Node id.
A write operation to this object will
not change the operational value reflected
in snaNodeOperIdNum until the Node has
been re-activated (e.g., after the next initialization
of the SNA services).
|
snaNodeAdminEnablingMethod |
.1.3.6.1.2.1.34.1.1.1.1.7 |
The value indicates how the Node should be
activated for the first time.
The values have the following meanings:
other (1) - may be used for proprietary methods
not listed in this enumeration,
startup (2) - at SNA services' initialization time
(this is the default),
demand (3) - only when LU is requested by application,
or
onlyMS (4) - by a Management Station only.
A write operation to this object may immediately
change the operational value reflected
in snaNodeOperEnablingMethod depending
on the Agent implementation. If the Agent
implementation accepts immediate changes, then the
behavior of the Node changes immediately and not only
after the next system startup of the SNA services.
An immediate change may only apply when the
current value 'demand (3)' is changed to 'onlyMS (4)'
and vice versa.
|
snaNodeAdminLuTermDefault |
.1.3.6.1.2.1.34.1.1.1.1.8 |
The value indicates the desired default method
used to deactivate LUs for this Node
For LU6.2s, 'unbind(1)' is the only valid value.
unbind(1) - terminate the LU-LU session by sending
an SNA UNBIND request.
termself(2) - terminate the LU-LU session by sending
an SNA TERM-SELF (Terminate Self) request on
the SSCP-LU session. The SSCP will inform the
remote session LU partner to send an UNBIND
request to terminate the session.
rshutd(3) - terminate the LU-LU session by sending
an SNA RSHUTD (Request ShutDown) request to
the remote session LU partner. The remote LU
will then send an UNBIND request to terminate
the session.
poweroff(4) - terminate the LU-LU session by sending
either an SNA LUSTAT (LU Status) request on
the LU-LU session or an SNA NOTIFY request on
the SSCP-LU session indicating that the LU has
been powered off. Sending both is also
acceptable. The result should be that the
remote session LU partner will send an UNBIND
to terminate the session.
The default behavior indicated by the value of this
object may be overridden for an LU instance. The
override is performed by setting the snaLuAdminTerm
object instance in the snaLuAdminTable to the desired
value.
A write operation to this object may immediately
change the operational value reflected
in snaNodeOperLuTermDefault depending
on the Agent implementation.
|
snaNodeAdminMaxLu |
.1.3.6.1.2.1.34.1.1.1.1.9 |
The maximum number of LUs that may be
activated for this Node. For PU2.1, this object
refers to the number of dependent LUs.
A write operation to this object will
not change the operational value reflected
in snaNodeOperMaxLu until the Node has
been re-activated (e.g., after the next initialization
of the SNA services).
|
snaNodeAdminHostDescription |
.1.3.6.1.2.1.34.1.1.1.1.10 |
The value identifies the remote host associated
with this Node.
Since SSCP Id's may not be unique
across hosts, the host description
is required to uniquely identify the SSCP.
This object is only applicable to PU2.0 type
Nodes. If the remote host is unknown, then the
value is the null string.
A write operation to this object may immediately
change the operational value reflected
in snaNodeOperHostDescription depending
on the Agent implementation.
|
snaNodeAdminStopMethod |
.1.3.6.1.2.1.34.1.1.1.1.11 |
The value indicates the desired method to be used
by the Agent to stop a Node (i.e., change the Node's
operational state to inactive(1) ).
The values have the following meaning:
other (1) - used for proprietary
methods not listed in this enumeration.
normal(2) - deactivate only when there is no more
activity on this Node (i.e., all data flows
have been completed and all sessions
have been terminated).
immed(3) - deactivate immediately regardless of
current activities on this Node. Wait for
deactivation responses (from remote Node)
before changing the Node state to inactive.
force(4) - deactivate immediately regardless of
current activities on this Node. Do not wait
for deactivation responses (from remote Node)
before changing the Node state to inactive.
A write operation to this object may immediately
change the operational value reflected
in snaNodeOperStopMethod depending
on the Agent implementation.
|
snaNodeAdminState |
.1.3.6.1.2.1.34.1.1.1.1.12 |
The value indicates the desired operational
state of the SNA Node. This object is used
by the Management Station to
activate or deactivate the Node.
If the current value in snaNodeOperState is
'active (2)', then setting this object to
'inactive (1)' will initiate the Node shutdown
process using the method indicated
by snaNodeOperStopMethod.
If the current value in snaNodeOperState is
'inactive (1)', then setting this object to
'active (2)' will initiate the
Node's activation.
A Management Station can always set this object to
'active (2)' irrespective of the value in the
snaOperEnablingMethod.
|
snaNodeAdminRowStatus |
.1.3.6.1.2.1.34.1.1.1.1.13 |
This object is used by a Management Station to
create or delete the row entry in the
snaNodeAdminTable following
the RowStatus textual convention.
Upon successful creation of
the row, an Agent automatically creates a
corresponding entry in the snaNodeOperTable with
snaNodeOperState equal to 'inactive (1)'.
Row deletion can be Management Station or Agent
initiated:
(a) The Management Station can set the value to
'destroy (6)' only when the value of
snaNodeOperState of this Node instance is
'inactive (1)'. The Agent will then delete the rows
corresponding to this Node instance from the
snaNodeAdminTable and the snaNodeOperTable.
(b) The Agent detects that a row is in the
'notReady (3)' state for greater than a
default period of 5 minutes.
(c) All rows with the snaNodeAdminRowStatus object's
value of 'notReady (3)' will be removed upon the
next initialization of the SNA services.
|
snaNodeOperName |
.1.3.6.1.2.1.34.1.1.3.1.1 |
The value identifies the current name of the Node.
In Type 2.1 networks, this
is a fully-qualified name, meaning that the Node name
is preceded by the NetId (if present) with a period
as the delimiter.
|
snaNodeOperType |
.1.3.6.1.2.1.34.1.1.3.1.2 |
The value identifies the current type of the Node.
|
snaNodeOperXidFormat |
.1.3.6.1.2.1.34.1.1.3.1.3 |
The value identifies the type of XID format currently
used for this Node.
Note that there is no format type 2.
|
snaNodeOperBlockNum |
.1.3.6.1.2.1.34.1.1.3.1.4 |
The value identifies the block number for this Node
instance. It is the first 3 hexadecimal digits
of the SNA Node id.
|
snaNodeOperIdNum |
.1.3.6.1.2.1.34.1.1.3.1.5 |
The value identifies the ID number for this Node
instance. This is the last 5 hexadecimal digits of
the SNA Node id.
|
snaNodeOperEnablingMethod |
.1.3.6.1.2.1.34.1.1.3.1.6 |
The value indicates how the Node is activated for
the first time.
The values have the following meanings:
other (1) - not at boot time, LU activation
or by a Management Station;
startup (2) - at SNA services' initialization
time (this is the default),
demand (3) - only when LU is requested by
application,
onlyMS (4) - by a network Management Station
only.
|
snaNodeOperLuTermDefault |
.1.3.6.1.2.1.34.1.1.3.1.7 |
The value identifies the default method used to
deactivate LUs for this Node.
For LU6.2s, 'unbind(1)' is the only valid value.
unbind(1) - terminate the LU-LU session by sending
an SNA UNBIND request.
termself(2) - terminate the LU-LU session by sending
an SNA TERM-SELF (Terminate Self) request on
the SSCP-LU session. The SSCP will inform the
remote session LU partner to send an UNBIND
request to terminate the session.
rshutd(3) - terminate the LU-LU session by sending
an SNA RSHUTD (Request ShutDown) request to
the remote session LU partner. The remote LU
will then send an UNBIND request to terminate
the session.
poweroff(4) - terminate the LU-LU session by sending
either an SNA LUSTAT (LU Status) request on
the LU-LU session or an SNA NOTIFY request on
the SSCP-LU session indicating that the LU has
been powered off. Sending both is also
acceptable. The result should be that the
remote session LU partner will send an UNBIND
to terminate the session.
This object describes the default behavior for this
Node; however, it is possible that for a specific LU
the behavior indicated by the snaLuOperTerm object is
different.
|
snaNodeOperMaxLu |
.1.3.6.1.2.1.34.1.1.3.1.8 |
This value identifies the current, maximum number
of LUs that are activated for this Node. For PU2.1,
this object refers to the number of dependent LUs.
|
snaNodeOperHostDescription |
.1.3.6.1.2.1.34.1.1.3.1.9 |
This value identifies the remote host currently
associated with this Node.
Since SSCP Id's may not be unique
across hosts, the host description
is required to uniquely identify the SSCP.
|
snaNodeOperStopMethod |
.1.3.6.1.2.1.34.1.1.3.1.10 |
This value identifies the current Node shutdown
method to be used by the Agent to stop the Node.
When the Agent changes the Node's state to 'inactive
(1)', the Agent must use the shutdown method
indicated by this object.
The values have the following meaning:
other (1) - proprietary method not listed in this
enumeration
normal(2) - deactivate only when there is no more
activity on this Node (i.e., all data flows
have been completed and all sessions have
been terminated).
immed(3) - deactivate immediately regardless of
current activities on this Node. Wait for
deactivation responses (from remote Node)
before changing the Node state to inactive.
force(4) - deactivate immediately regardless of
current activities on this Node. Do not wait
for deactivation responses (from remote Node)
before changing the Node state to inactive.
Note that a write operation to
snaNodeAdminOperStopMethod may immediately change
the value of snaNodeOperStopMethod depending on
the Agent implementation.
|
snaNodeOperState |
.1.3.6.1.2.1.34.1.1.3.1.11 |
The current state of the Node.
The values have the following meanings:
inactive (1), a row representing the Node has
been created in the AdminTable
and, the Node is ready for activation -or-
an active Node has been stopped -or-
a waiting Node has returned to the inactive
state.
waiting (3), a request to have the Node activated
has been issued, and the Node is pending
activation.
active (2), the Node is ready and operating.
stopping (4), the request to stop the Node has
been issued while the StopMethod normal
or immediate is used.
|
snaNodeOperHostSscpId |
.1.3.6.1.2.1.34.1.1.3.1.12 |
This value identifies the current SSCP Id
associated with the Node. This object is only
applicable to PU 2.0s. If the Node
is not a PU 2.0 type, then this object contains a
zero length string.
|
snaNodeOperStartTime |
.1.3.6.1.2.1.34.1.1.3.1.13 |
The timestamp (e.g, the Agent's sysUpTime value)
at the Node activation.
|
snaNodeOperLastStateChange |
.1.3.6.1.2.1.34.1.1.3.1.14 |
The timestamp (e.g., the Agent's sysUpTime value)
at the last state change of the Node.
|
snaNodeOperActFailures |
.1.3.6.1.2.1.34.1.1.3.1.15 |
This value identifies the number of failed Node
activation attempts.
|
snaNodeOperActFailureReason |
.1.3.6.1.2.1.34.1.1.3.1.16 |
The value indicates the reason for the activation
failure. The value 'other (1)' indicates a reason
not listed in the enumeration. This object
will be sent in the trap snaNodeActFailTrap.
|
snaPu20StatsSentBytes |
.1.3.6.1.2.1.34.1.1.5.1.1 |
The number of bytes sent by this Node.
|
snaPu20StatsReceivedBytes |
.1.3.6.1.2.1.34.1.1.5.1.2 |
The number of bytes received by this Node.
|
snaPu20StatsSentPius |
.1.3.6.1.2.1.34.1.1.5.1.3 |
The number of PIUs sent by this Node.
|
snaPu20StatsReceivedPius |
.1.3.6.1.2.1.34.1.1.5.1.4 |
The number of PIUs received by this Node.
|
snaPu20StatsSentNegativeResps |
.1.3.6.1.2.1.34.1.1.5.1.5 |
The number of negative responses sent
by this Node.
|
snaPu20StatsReceivedNegativeResps |
.1.3.6.1.2.1.34.1.1.5.1.6 |
The number of negative responses received
by this Node.
|
snaPu20StatsActLus |
.1.3.6.1.2.1.34.1.1.5.1.7 |
The number of LUs on this PU which have
received and responded to ACTLU from the host.
|
snaPu20StatsInActLus |
.1.3.6.1.2.1.34.1.1.5.1.8 |
The number of LUs on this PU which have
not received an ACTLU from the host. This is
possible if the number of configured LUs exceeds
that on the host.
|
snaPu20StatsBindLus |
.1.3.6.1.2.1.34.1.1.5.1.9 |
The number of LUs on this PU which have
received and acknowledged a BIND request from the
host.
|
snaNodeLinkAdminIndex |
.1.3.6.1.2.1.34.1.1.6.1.1 |
This value is used to index the instances of objects.
If an Agent creates the entry, then it will assign
this number otherwise a Management Station
generates a random number when it reserves the
entry for creation.
|
snaNodeLinkAdminSpecific |
.1.3.6.1.2.1.34.1.1.6.1.2 |
This value points to the row in the table
containing information on the link instance.
(e.g., the sdlcLSAdminTable of
the SNA DLC MIB module).
|
snaNodeLinkAdminMaxPiu |
.1.3.6.1.2.1.34.1.1.6.1.3 |
This value identifies the maximum number of octets
that can be exchanged by this Node in one
Path Information Unit (PIU).
|
snaNodeLinkAdminRowStatus |
.1.3.6.1.2.1.34.1.1.6.1.4 |
This object is used by a Management Station to
create or delete the row entry in the
snaNodeLinkAdminTable.
To activate a row, a Management Station sets the value
to 'active (1)' or 'notReady (3)'. Upon successful
creation of the row, the Agent automatically creates
a corresponding entry in the snaNodeLinkOperTable.
Row deletion can be Management Station or Agent
initiated:
(a) The Management Station can set the value to
'destroy (6)' only when the value of
snaNodeLinkOperState of this Link
instance is 'inactive (1)'. The Agent will then
delete the row corresponding to this Link
instance from snaNodeLinkOperTable and
from snaNodeLinkAdminTable.
(b) The Agent detects that a row is in the
'notReady (3)' state for greater than a
default period of 5 minutes.
(c) The Agent will not include a row with RowStatus=
'notReady (3)', after SNA system re-initialization
(e.g., reboot).
|
snaNodeLinkOperSpecific |
.1.3.6.1.2.1.34.1.1.8.1.1 |
This value points to the row in the table
containing information on the link instance.
(e.g., the sdlcLSOperTable of
the SNA DLC MIB module).
|
snaNodeLinkOperMaxPiu |
.1.3.6.1.2.1.34.1.1.8.1.2 |
Maximum number of octets that can
be exchanged by this Node in one Path
Information Unit (PIU).
|
snaLuAdminLuIndex |
.1.3.6.1.2.1.34.1.2.1.1.1 |
This value identifies the unique index for an
LU instance within a Node.
|
snaLuAdminName |
.1.3.6.1.2.1.34.1.2.1.1.2 |
This value identifies the user configurable
name for this LU. If a name is not assigned to the LU,
then this object contains a zero length string.
A write operation to this object will
not change the operational value reflected
in snaLuOperName until the Node has
been re-activated (e.g., after the next
initialization of the SNA services).
|
snaLuAdminSnaName |
.1.3.6.1.2.1.34.1.2.1.1.3 |
This value identifies the SNA LU name
used in exchange of SNA data.
A write operation to this object will
not change the operational value reflected
in snaLuOperSnaName until the Node has
been re-activated (e.g., after the next
initialization of the SNA services).
|
snaLuAdminType |
.1.3.6.1.2.1.34.1.2.1.1.4 |
This value identifies the LU type.
A write operation to this object will
not change the operational value reflected
in snaLuOperAdminType until the Node has
been re-activated (e.g., after the next
initialization of the SNA services).
|
snaLuAdminDepType |
.1.3.6.1.2.1.34.1.2.1.1.5 |
This value identifies whether the LU is
dependent or independent.
A write operation to this object will
not change the operational value reflected
in snaLuOperDepType until the Node has
been re-activated (e.g., after the next
initialization of the SNA services).
|
snaLuAdminLocalAddress |
.1.3.6.1.2.1.34.1.2.1.1.6 |
The local address for this LU is a byte with a value
ranging from 0 to 254.For dependent LUs, this value
ranges from 1 to 254 and for independent LUs this
value is always 0.
A write operation to this object will not change the
operational value reflected in snaLuOperLocalAddress
until the Node has been re-activated (e.g., after the
next initialization of the SNA services).
|
snaLuAdminDisplayModel |
.1.3.6.1.2.1.34.1.2.1.1.7 |
The value of this object identifies the model type
and screen size of the terminal connected to the host.
This is only valid for LU Type 2. The values have
the following meaning:
model2A(2) - Model 2 (24 rows x 80 cols) with base
attributes
model2B(3) - Model 2 (24 rows x 80 cols) with
extended attributes
model3A(4) - Model 3 (32 rows x 80 cols) with base
attributes
model3B(5) - Model 3 (32 rows x 80 cols) with extended
attributes
model4A(6) - Model 4 (43 rows x 80 cols) with base
attributes
model4B(7) - Model 4 (43 rows x 80 cols) with extended
attributes
model5A(8) - Model 5 (27 rows x 132 cols) with base
attributes
model5B(9) - Model 5 (27 rows x 132 cols) with
extended attributes
dynamic(10) - Screen size determine with BIND and Read
Partition Query.
In case this LU is not Type 2, then this object
should contain the invalid(1) value.
|
snaLuAdminTerm |
.1.3.6.1.2.1.34.1.2.1.1.8 |
This value identifies the desired method for
deactivation of this LU. This value overrides the
default method (snaNodeOperLuTermDefault) for this
Node. For LU 6.2, only the value 'unbind (1)'
applies.
unbind(1) - terminate the LU-LU session by sending
an SNA UNBIND request.
termself(2) - terminate the LU-LU session by sending
an SNA TERM-SELF (Terminate Self) request on
the SSCP-LU session. The SSCP will inform the
remote session LU partner to send an UNBIND
request to terminate the session.
rshutd(3) - terminate the LU-LU session by sending
an SNA RSHUTD (Request ShutDown) request to
the remote session LU partner. The remote LU
will then send an UNBIND request to terminate
the session.
poweroff(4) - terminate the LU-LU session by sending
either an SNA LUSTAT (LU Status) request on
the LU-LU session or an SNA NOTIFY request on
the SSCP-LU session indicating that the LU has
been powered off. Sending both is also
acceptable. The result should be that the
remote session LU partner will send an UNBIND
to terminate the session.
A write operation to this object may immediately
change the operational value reflected
in snaLuOperTerm depending
on the Agent implementation.
|
snaLuAdminRowStatus |
.1.3.6.1.2.1.34.1.2.1.1.9 |
This object is used by a Management Station to
create or delete the row entry in the
snaLuAdminTable.
To activate a row, the Management Station sets the
value to 'active (1)' or 'notReady (3)'.
Upon successful creation of the row, the Agent
automatically creates a corresponding entry in the
snaLuOperTable with snaLuOperState equal to
'inactive (1)'.
Row deletion can be Management Station or Agent
initiated:
(a) The Management Station can set the value to
'destroy (6)' only when the value of snaLuOperState
of this LU instance is 'inactive (1)'. The Agent will
then delete the row corresponding to this LU
instance from snaLuAdminTable and
from snaLuOperTable.
(b) The Agent detects that a row is in the
'notReady (3)' state for greater than a
default period of 5 minutes.
(c) The Agent will not create a row with RowStatus
equal to 'notReady (3)', after SNA system
re-initialization (e.g., reboot).
|
snaLuOperName |
.1.3.6.1.2.1.34.1.2.2.1.1 |
User configurable name for this LU. If a name
is not assigned, then this object contains a
zero length string.
|
snaLuOperSnaName |
.1.3.6.1.2.1.34.1.2.2.1.2 |
The value identifies the current SNA LU name.
|
snaLuOperType |
.1.3.6.1.2.1.34.1.2.2.1.3 |
The value identifies the current LU type.
|
snaLuOperDepType |
.1.3.6.1.2.1.34.1.2.2.1.4 |
The value identifies whether the LU is currently
dependent or independent.
A write operation to this object will
not change the operational value reflected
in snaLuOperDepType until the Node has
been re-activated (e.g., after the next
initialization of the SNA services).
|
snaLuOperLocalAddress |
.1.3.6.1.2.1.34.1.2.2.1.5 |
The local address for this LU is a byte with a value
ranging from 0 to 254. For dependent LUs, this value
ranges from 1 to 254; for independent LUs this value
is always 0.
A write operation to this object will
not change the operational value reflected
in snaLuOperLocalAddress until the Node has
been re-activated (e.g., after the next
initialization of the SNA services).
|
snaLuOperDisplayModel |
.1.3.6.1.2.1.34.1.2.2.1.6 |
The screen model type of the terminal connected to
the host. If this LU is not Type 2, then this
object should contain the 'invalid(1)' value.
|
snaLuOperTerm |
.1.3.6.1.2.1.34.1.2.2.1.7 |
The value identifies the current method for
deactivation of this LU. This value overrides the
default method (snaNodeOperLuTermDefault) for this
Node. For LU 6.2, only the value 'unbind (1)'
applies.
unbind(1) - terminate the LU-LU session by sending
an SNA UNBIND request.
termself(2) - terminate the LU-LU session by sending
an SNA TERM-SELF (Terminate Self) request on
the SSCP-LU session. The SSCP will inform the
remote session LU partner to send an UNBIND
request to terminate the session.
rshutd(3) - terminate the LU-LU session by sending
an SNA RSHUTD (Request ShutDown) request to
the remote session LU partner. The remote LU
will then send an UNBIND request to terminate
the session.
poweroff(4) - terminate the LU-LU session by sending
either an SNA LUSTAT (LU Status) request on
the LU-LU session or an SNA NOTIFY request on
the SSCP-LU session indicating that the LU has
been powered off. Sending both is also
acceptable. The result should be that the
remote session LU partner will send an UNBIND
to terminate the session.
|
snaLuOperState |
.1.3.6.1.2.1.34.1.2.2.1.8 |
The value identifies the current operational state of
this LU.
It has different meanings for dependent and independent
LUs.
For dependent LUs the values indicate the following:
inactive (1) - LU didn't receive ACTLU, or
it received DACTLU, or received ACTLU and sent
negative response.
active (2) - LU received ACTLU and acknowledged
positively.
For independent LUs the values indicate the following:
active (2) - the LU is defined and is able to send
and receive BIND.
inactive (1) - the LU has a session count equal
to 0.
|
snaLuOperSessnCount |
.1.3.6.1.2.1.34.1.2.2.1.9 |
The number of currently active LU-LU sessions of
this LU.
For the independent LU, if this object has value 0,
it indicates that LU is inactive.
|
snaLuSessnRluIndex |
.1.3.6.1.2.1.34.1.2.3.1.1 |
This value may be used to identify information about
the session partner LU in a table of information about
remote LUs. Such a table is not defined in this
document. If a table of remote LU information is not
implemented, or if the table is implemented but it does
not contain information about the partner LU for a
particular session (as for dependent LU-LU sessions)
then this object will have a value of zero.
|
snaLuSessnIndex |
.1.3.6.1.2.1.34.1.2.3.1.2 |
This value identifies the unique index of the session.
It is recommended that an Agent should not reuse the
index of a deactivated session for a significant
period of time (e.g., one week).
|
snaLuSessnLocalApplName |
.1.3.6.1.2.1.34.1.2.3.1.3 |
The name of the local application using this LU.
If the local application is unknown, then this object
contains a zero length string.
|
snaLuSessnRemoteLuName |
.1.3.6.1.2.1.34.1.2.3.1.4 |
For dependent LUs which are indicated by the
snaLuOperDepType object containing the value
'dependent (1)', this object contains the Primary
LU (PLU) name. For independent LUs,
this object contains the fully-qualified remote LU
name of this 6.2 session.
A fully qualified name is an SNA NAU entity name
preceded by the NetId and a period as the delimiter.
|
snaLuSessnMaxSndRuSize |
.1.3.6.1.2.1.34.1.2.3.1.5 |
The maximum RU size used on this session for sending
RUs.
|
snaLuSessnMaxRcvRuSize |
.1.3.6.1.2.1.34.1.2.3.1.6 |
The maximum RU size used on this session for
receiving RUs.
|
snaLuSessnSndPacingSize |
.1.3.6.1.2.1.34.1.2.3.1.7 |
The size of the send pacing window on this session.
|
snaLuSessnRcvPacingSize |
.1.3.6.1.2.1.34.1.2.3.1.8 |
The size of the receive pacing window on this
session.
|
snaLuSessnActiveTime |
.1.3.6.1.2.1.34.1.2.3.1.9 |
The timestamp (e.g., the Agent's sysUpTime value)
when this session becomes active.
|
snaLuSessnAdminState |
.1.3.6.1.2.1.34.1.2.3.1.10 |
The value indicates the desired operational state of
the session. This object is used to
change the operational state of the session.
A Management Station can only change the operational
state of the session to 'unbound (1)'.
Session deactivation:
If a session is in the operational state
'bound (3)' then setting the value of this
object to 'unbound (1)' will initiate the
session shutdown.
If a session is in the operational state
'pendingBind (2)' then setting the value of this
object to 'unbound (1)' will initiate the session
shutdown.
If a session is in the operational state
'pendingUnbind (4)' for an abnormally long period
of time (e.g., three minutes) then setting the value
of this object to 'unbound (1)' will change the
session operational state to 'unbound (1)'.
Note: for dependent LUs, deactivating the session is
the same as deactivating the LU.
|
snaLuSessnOperState |
.1.3.6.1.2.1.34.1.2.3.1.11 |
The value indicates the current operational state of
the session.
'unbound (1)' - session has been unbound;
in this state it will be removed from the
session table by the Agent.
'pendingBind (2)' - this state has different
meanings for dependent and independent LUs;
for dependent LU - waiting for BIND from
the host, for independent LU - waiting for
BIND response. When a session enters this
state, the corresponding entry in the
session table is created by the Agent.
'bound (3)' - session has been successfully bound.
'pendingUnbind (4)' - session enters this state
when an UNBIND is sent and before the
rsp(UNBIND) is received.
|
snaLuSessnSenseData |
.1.3.6.1.2.1.34.1.2.3.1.12 |
The value identifies the sense code when there is
a BIND failure. It is taken from the negative BIND
response or UNBIND request.
This is displayed as 8 hexadecimal digits.
|
snaLuSessnTerminationRu |
.1.3.6.1.2.1.34.1.2.3.1.13 |
The value identifies the SNA RU that terminated the
session.
If the session is not in the unbound state, this object
has a value of 'other (1)'.
|
snaLuSessnUnbindType |
.1.3.6.1.2.1.34.1.2.3.1.14 |
If the session is in the unbound state, and it was
terminated by an UNBIND, then this object contains
the UNBIND type value (byte 1 of the UNBIND RU);
otherwise the string is null.
|
snaLuSessnLinkIndex |
.1.3.6.1.2.1.34.1.2.3.1.15 |
This value identifies the link over which the session
passes. It is an index into snaNodeLinkAdminTable.
If the index value is not known, the value of this
object shall be zero.
|
snaLuSessnStatsSentBytes |
.1.3.6.1.2.1.34.1.2.4.1.1 |
The number of bytes sent by the local LU.
|
snaLuSessnStatsReceivedBytes |
.1.3.6.1.2.1.34.1.2.4.1.2 |
The number of bytes received by the local LU.
|
snaLuSessnStatsSentRus |
.1.3.6.1.2.1.34.1.2.4.1.3 |
The number of RUs sent by the local LU.
|
snaLuSessnStatsReceivedRus |
.1.3.6.1.2.1.34.1.2.4.1.4 |
The number of RUs received by the local LU.
|
snaLuSessnStatsSentNegativeResps |
.1.3.6.1.2.1.34.1.2.4.1.5 |
The number of negative responses sent by the
local LU.
|
snaLuSessnStatsReceivedNegativeResps |
.1.3.6.1.2.1.34.1.2.4.1.6 |
The number of negative responses received by the
local LU.
|
snaLuRtmPuIndex |
.1.3.6.1.2.1.34.1.3.1.1.1 |
The value identifies the PU 2.0 with which this LU is
associated.
|
snaLuRtmLuIndex |
.1.3.6.1.2.1.34.1.3.1.1.2 |
The value uniquely identifies an LU in a PU 2.0.
|
snaLuRtmState |
.1.3.6.1.2.1.34.1.3.1.1.3 |
The value indicates the current RTM state of an LU.
|
snaLuRtmStateTime |
.1.3.6.1.2.1.34.1.3.1.1.4 |
The timestamp (e.g., the Agent's sysUpTime value)
when this session's RTM state (e.g., snaLuRtmState)
changes value.
|
snaLuRtmDef |
.1.3.6.1.2.1.34.1.3.1.1.5 |
The value indicates the mode of measurement for this
RTM request. The values have following meaning:
firstChar(1) - time to first character on screen
kb(2) - time to keyboard usable by operator
cdeb(3) - time to Change Direction/End Bracket.
|
snaLuRtmBoundary1 |
.1.3.6.1.2.1.34.1.3.1.1.6 |
This object contains the value of the first boundary
in units of 1/10th of a second.
|
snaLuRtmBoundary2 |
.1.3.6.1.2.1.34.1.3.1.1.7 |
This object contains the value of the second boundary
in units of 1/10th of a second.
|
snaLuRtmBoundary3 |
.1.3.6.1.2.1.34.1.3.1.1.8 |
This object contains the value of the third boundary
in units of 1/10th of a second.
|
snaLuRtmBoundary4 |
.1.3.6.1.2.1.34.1.3.1.1.9 |
This object contains the value of the fourth boundary
in units of 1/10th of a second.
|
snaLuRtmCounter1 |
.1.3.6.1.2.1.34.1.3.1.1.10 |
This value indicates the number of transactions which
fall in the range specified by the first boundary.
|
snaLuRtmCounter2 |
.1.3.6.1.2.1.34.1.3.1.1.11 |
This value indicates the number of transactions which
fall in the range specified by the second boundary.
|
snaLuRtmCounter3 |
.1.3.6.1.2.1.34.1.3.1.1.12 |
This value indicates the number of transactions which
fall in the range specified by the third boundary.
|
snaLuRtmCounter4 |
.1.3.6.1.2.1.34.1.3.1.1.13 |
This value indicates the number of transactions which
fall in the range specified by the fourth boundary.
|
snaLuRtmOverFlows |
.1.3.6.1.2.1.34.1.3.1.1.14 |
This value indicates the number of transactions which
exceed the highest range specified by the
boundaries.
|
snaLuRtmObjPercent |
.1.3.6.1.2.1.34.1.3.1.1.15 |
This value indicates the desired percentage of
transactions which should be under a designated
boundary range indicated by snaLuRtmObjRange.
|
snaLuRtmObjRange |
.1.3.6.1.2.1.34.1.3.1.1.16 |
This value indicates the designated boundary range to
which the snaLuRtmObject refers.
The values have the following meanings:
other(1) - not specified
range1(2) - less than boundary 1
range2(3) - between boundary 1 and 2
range3(4) - between boundary 2 and 3
range4(5) - between boundary 3 and 4
range5(6) - greater than boundary 4.
|
snaLuRtmNumTrans |
.1.3.6.1.2.1.34.1.3.1.1.17 |
This value indicates the total number of transactions
executed since the RTM monitoring began (i.e.,
snaLuRtmState changed to 'on(2)') for this LU.
|
snaLuRtmLastRspTime |
.1.3.6.1.2.1.34.1.3.1.1.18 |
This value indicates the response time for the last
transaction in units of 1/10th of a second.
|
snaLuRtmAvgRspTime |
.1.3.6.1.2.1.34.1.3.1.1.19 |
This value indicates the average response time for all
transactions in units of 1/10th of a second.
|