SNA-NAU-MIB: View SNMP OID List / Download MIB

This is the MIB module for objects used to manage SNA devices.

This table contains objects which describe the configuration parameters for an SNA Node. Link specific configuration objects are contained in a separate MIB module (e.g., SNA DLC MIB) corresponding to the link type. The table snaNodeAdminLinkTable contains objects which identify the relationship between node instances and link instances. The entries (i.e., rows) in this table can be created by either an Agent or a Management Station. The Management Station can do this through setting the appropriate value in the snaNodeAdminRowStatus. The snaNodeAdminRowStatus object describes the status of an entry and is used to change the status of an entry. The entry is deleted by an Agent based on the value of the snaNodeAdminRowStatus. The snaNodeAdminState object describes the desired operational state of a Node and is used to change the operational state of a Node. For example, such information may be obtained from a configuration file. How an Agent or a Management Station obtains the initial value of each object at creation time is an implementation specific issue. For each entry in this table, there is a corresponding entry in the snaNodeOperTable. While the objects in this table describe the desired or configured operational values of the SNA Node, the actual runtime values are contained in snaNodeOperTable.

An entry contains the configuration parameters for one SNA Node instance. The objects in the entry have read-create access. An entry can be created, modified or deleted. The object snaNodeAdminRowStatus is used (i.e., set) to create or delete a row entry.

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.

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).

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). Enumeration: 'pu20': 3, 'networkNode': 6, 'pu10': 2, 'other': 1, 'endNode': 5, 't21len': 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). Enumeration: 'format0': 1, 'format1': 2, 'format3': 3.

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).

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).

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. Enumeration: 'onlyMS': 4, 'other': 1, 'startup': 2, 'demand': 3.

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. Enumeration: 'unbind': 1, 'termself': 2, 'poweroff': 4, 'rshutd': 3.

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).

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.

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. Enumeration: 'immed': 3, 'other': 1, 'force': 4, 'normal': 2.

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. Enumeration: 'active': 2, 'inactive': 1.

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.

The value indicates the timestamp (e.g., the Agent's sysUpTime value) of the last change made to any object in the snaNodeAdminTable, including row deletions/additions (e.g., changes to snaNodeAdminRowStatus values). This object can be used to reduce frequent retrievals of the snaNodeAdminTable by a Management Station. It is expected that a Management Station will periodically poll this object and compare its current value with the previous one. A difference indicates that some Node configuration information has been changed. Only then will the Management Station retrieve the entire table.

This table contains the dynamic parameters which have read-only access. These objects reflect the actual status of the Node. The entries in this table cannot be created or modified by a Management Station. This table augments the snaNodeAdminTable.

The entry contains parameters which describe the state of one Node. The entries are created by the Agent. They have read-only access.

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.

The value identifies the current type of the Node. Enumeration: 'pu20': 3, 'networkNode': 6, 'pu10': 2, 'other': 1, 'endNode': 5, 't21LEN': 4.

The value identifies the type of XID format currently used for this Node. Note that there is no format type 2. Enumeration: 'format0': 1, 'format1': 2, 'format3': 3.

The value identifies the block number for this Node instance. It is the first 3 hexadecimal digits of the SNA Node id.

The value identifies the ID number for this Node instance. This is the last 5 hexadecimal digits of the SNA Node id.

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. Enumeration: 'onlyMS': 4, 'other': 1, 'startup': 2, 'demand': 3.

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. Enumeration: 'unbind': 1, 'termself': 2, 'poweroff': 4, 'rshutd': 3.

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.

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.

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. Enumeration: 'immed': 3, 'other': 1, 'force': 4, 'normal': 2.

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. Enumeration: 'active': 2, 'stopping': 4, 'waiting': 3, 'inactive': 1.

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.

The timestamp (e.g, the Agent's sysUpTime value) at the Node activation.

The timestamp (e.g., the Agent's sysUpTime value) at the last state change of the Node.

This value identifies the number of failed Node activation attempts.

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. Enumeration: 'badConfiguration': 4, 'internalError': 5, 'other': 1, 'noResources': 3, 'linkFailure': 2.

The timestamp (e.g., the Agent's sysUpTime value) at the last change made to any object in the snaNodeOperTable, including row deletions/additions made as a result of changes to the snaNodeAdminRowStatus object. This object can be used to reduce frequent retrievals of the snaNodeOperTable by a Management Station. It is expected that a Management Station will periodically poll this object and compare its current value with the previous one. A difference indicates that some Node operational information has been changed. Only then will the Management Station retrieve the entire table.

This table contains the dynamic parameters which have read-only access. The entries in this table correspond to PU 2.0 entries in the snaNodeOperTable and cannot be created by a Management Station.

The entry contains parameters which describe the statistics for one PU 2.0. They have read-only access. The counters represent traffic for all kinds of sessions: LU-LU, SSCP-PU, SSCP-LU. Each Node of PU Type 2.0 from the snaNodeAdminTable has one entry in this table and the index used here has the same value as snaNodeAdminIndex of that PU. The entry is created by the Agent.

The number of bytes sent by this Node.

The number of bytes received by this Node.

The number of PIUs sent by this Node.

The number of PIUs received by this Node.

The number of negative responses sent by this Node.

The number of negative responses received by this Node.

The number of LUs on this PU which have received and responded to ACTLU from the host.

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.

The number of LUs on this PU which have received and acknowledged a BIND request from the host.

This table contains the references to link specific tables. If a Node is configured for multiple links, then the Node will have multiple entries in this table. The entries in this table can be generated initially, after initialization of SNA service, by the Agent which uses information from Node configuration file. Subsequent modifications of parameters, creation of new Nodes link entries and deletion of entries is possible. The modification to this table can be saved in the Node configuration file for the next initialization of SNA service, but the mechanism for this function is not defined here.

Entry contains the configuration information that associates a Node instance to one link instance. The objects in the entry have read-create access. Entry can be created, modified or deleted. The object snaNodeLinkAdminRowStatus is used (set) to create or delete an entry. The object snaNodeLinkAdminSpecific can be set later, after the entry has been created.

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.

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).

This value identifies the maximum number of octets that can be exchanged by this Node in one Path Information Unit (PIU).

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).

The timestamp (e.g., the Agent's sysUpTime value) at the last change made to any object in the snaNodeLinkAdminTable, including row deletions/additions (i.e., changes to the snaNodeLinkAdminRowStatus object). This object can be used to reduce frequent retrievals of the snaNodeLinkAdminTable by a Management Station. It is expected that a Management Station will periodically poll this object and compare its current value with the previous one. A difference indicates that some Node operational information has been changed. Only then will the Management Station retrieve the entire table.

This table contains all references to link specific tables for operational parameters. If a Node is configured for multiple links, then the Node will have multiple entries in this table. This table augments the snaNodeLinkAdminTable.

Entry contains all current parameters for one Node link. The objects in the entry have read-only access.

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).

Maximum number of octets that can be exchanged by this Node in one Path Information Unit (PIU).

The timestamp of the last change made to any object in the snaNodeLinkOperTable, including row deletions/additions. This object can be used to reduce frequent retrievals of the snaNodeLinkOperTable by a Management Station. It is expected that a Management Station will periodically poll this object and compare its current value with the previous one. A difference indicates that some Node operational information has been changed. Only then will the Management Station retrieve the entire table.

This trap indicates that the operational state (i.e., value of the snaNodeOperState object) of a Node has changed. The following variables are returned: snaNodeOperName - current name of the Node, with the instance identifying the Node; and, snaNodeOperState - current state after the change.

This trap indicates a Node activation failure. The value of snaNodeOperState indicates the current state after the activation attempt. The value of snaNodeOperActFailureReason indicates the failure reason.

This table contains LU configuration information. The rows in this table can be created and deleted by a Management Station. Only objects which are common to all types of LUs are included in this table.

Contains configuration variables for an LU.

This value identifies the unique index for an LU instance within a Node.

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).

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).

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). Enumeration: 'lu0': 2, 'lu1': 3, 'lu2': 4, 'lu3': 5, 'lu4': 6, 'lu7': 8, 'other': 1, 'lu62': 7.

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). Enumeration: 'dependent': 1, 'independent': 2.

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).

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. Enumeration: 'model2B': 3, 'dynamic': 10, 'model2A': 2, 'model3A': 4, 'invalid': 1, 'model3B': 5, 'model5B': 9, 'model5A': 8, 'model4A': 6, 'model4B': 7.

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. Enumeration: 'unbind': 1, 'termself': 2, 'poweroff': 4, 'rshutd': 3.

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).

This table contains dynamic runtime information and control variables relating to LUs. Only objects which are common to all types of LUs are included in this table. This table augments the snaLuAdminTable.

Contains objects reflecting current information for an LU. Each entry is created by the Agent. All entries have read-only access.

User configurable name for this LU. If a name is not assigned, then this object contains a zero length string.

The value identifies the current SNA LU name.

The value identifies the current LU type. Enumeration: 'lu0': 2, 'lu1': 3, 'lu2': 4, 'lu3': 5, 'lu4': 6, 'lu7': 8, 'other': 1, 'lu62': 7.

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). Enumeration: 'dependent': 1, 'independent': 2.

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).

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. Enumeration: 'model2B': 3, 'dynamic': 10, 'model2A': 2, 'model3A': 4, 'invalid': 1, 'model3B': 5, 'model5B': 9, 'model5A': 8, 'model4A': 6, 'model4B': 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. Enumeration: 'unbind': 1, 'termself': 2, 'poweroff': 4, 'rshutd': 3.

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. Enumeration: 'active': 2, 'inactive': 1.

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.

This is a table containing objects which describe the operational state of LU sessions. Only objects which are common to all types of LU sessions are included in this table. When a session's snaLuSessnOperState value changes to 'pendingBind (2)', then the corresponding entry in the session table is created by the Agent. When the session's snaLuSessnOperState value changes to 'unbound (1)', then the session will be removed from the session table by the Agent.

An entry contains dynamic parameters for an LU-LU session. The indices identify the Node, local LU, and remote LU for this session.

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.

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).

The name of the local application using this LU. If the local application is unknown, then this object contains a zero length string.

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.

The maximum RU size used on this session for sending RUs.

The maximum RU size used on this session for receiving RUs.

The size of the send pacing window on this session.

The size of the receive pacing window on this session.

The timestamp (e.g., the Agent's sysUpTime value) when this session becomes active.

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. Enumeration: 'unbound': 1, 'bound': 3.

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. Enumeration: 'pendingUnbind': 4, 'unbound': 1, 'bound': 3, 'pendingBind': 2.

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.

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)'. Enumeration: 'unbind': 3, 'other': 1, 'bindFailure': 2.

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.

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.

This table contains dynamic statistics information relating to LU sessions. The entries in this table augment the entries in the snaLuSessnTable and cannot be created by a Management Station.

Contains statistics information for an LU session. Each entry is created by the Agent. Objects in this table have read-only access. Each session from snaLuSessnTable has one entry in this table.

The number of bytes sent by the local LU.

The number of bytes received by the local LU.

The number of RUs sent by the local LU.

The number of RUs received by the local LU.

The number of negative responses sent by the local LU.

The number of negative responses received by the local LU.

This trap indicates that the operational state (i.e., snaLuOperState value) of the LU has changed. The value of snaLuOperName indicates the name of the LU. The value of snaLuOperSnaName indicates the SNA name of LU. The value of snaLuOperState indicates the current state after change.

This trap indicates the failure of a BIND. The value of snaLuSessnLocalApplName indicates the local application name. The value of snaLuSessnPartnerName indicates the partner name. The value of snaLuSessnOperState indicates the current state after change. The value of snaLuSessnBindFailureReason indicates the failure reason. The Agent should not generate more than 1 trap of this type per minute to minimize the level of management traffic on the network.

This table contains Response Time Monitoring (RTM) information relating to an LU (Type 2). Each entry corresponds to an LU 2 entry in snaLuAdminTable.

Contains RTM information for an LU (Type 2). Each entry is created by the Agent.

The value identifies the PU 2.0 with which this LU is associated.

The value uniquely identifies an LU in a PU 2.0.

The value indicates the current RTM state of an LU. Enumeration: 'on': 2, 'off': 1.

The timestamp (e.g., the Agent's sysUpTime value) when this session's RTM state (e.g., snaLuRtmState) changes value.

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. Enumeration: 'cdeb': 3, 'kb': 2, 'firstChar': 1.

This object contains the value of the first boundary in units of 1/10th of a second.

This object contains the value of the second boundary in units of 1/10th of a second.

This object contains the value of the third boundary in units of 1/10th of a second.

This object contains the value of the fourth boundary in units of 1/10th of a second.

This value indicates the number of transactions which fall in the range specified by the first boundary.

This value indicates the number of transactions which fall in the range specified by the second boundary.

This value indicates the number of transactions which fall in the range specified by the third boundary.

This value indicates the number of transactions which fall in the range specified by the fourth boundary.

This value indicates the number of transactions which exceed the highest range specified by the boundaries.

This value indicates the desired percentage of transactions which should be under a designated boundary range indicated by snaLuRtmObjRange.

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. Enumeration: 'range3': 4, 'range2': 3, 'range1': 2, 'other': 1, 'range5': 6, 'range4': 5.

This value indicates the total number of transactions executed since the RTM monitoring began (i.e., snaLuRtmState changed to 'on(2)') for this LU.

This value indicates the response time for the last transaction in units of 1/10th of a second.

This value indicates the average response time for all transactions in units of 1/10th of a second.

The compliance statement for the SNMPv2 entities which implement the snanau MIB.

A collection of objects providing the instrumentation of SNA nodes.

A collection of objects providing the instrumentation of SNA LUs.

A collection of objects providing the instrumentation of SNA sessions.

A collection of objects providing the instrumentation of PU 2.0.

A collection of objects providing the instrumentation of RTM for SNA LU 2.0.