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.
Parsed from file SNA-NAU-MIB.mib
Module: SNA-NAU-MIB
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.
snaNodeOperLuTermDefault OBJECT-TYPE
SYNTAX INTEGER {
unbind (1),
termself (2),
rshutd (3),
poweroff (4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
View at oid-info.com
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.
Parsed from file rfc1666-SNA-NAU.mib.txt
Company: None
Module: SNA-NAU-MIB
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.
snaNodeOperLuTermDefault OBJECT-TYPE SYNTAX INTEGER { unbind (1), termself (2), rshutd (3), poweroff (4) } MAX-ACCESS read-only STATUS current DESCRIPTION "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." ::= { snaNodeOperEntry 7 }
snaNodeOperLuTermDefault OBJECT-TYPE SYNTAX INTEGER { unbind(1), termself(2), rshutd(3), poweroff(4) } ACCESS read-only STATUS mandatory DESCRIPTION "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." ::= { snaNodeOperEntry 7 }
Automatically extracted from Cisco "SNMP v2 MIBs".
snaNodeOperLuTermDefault OBJECT-TYPE SYNTAX INTEGER { unbind (1), termself (2), rshutd (3), poweroff (4) } MAX-ACCESS read-only STATUS current DESCRIPTION "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." ::= { snaNodeOperEntry 7 }
snaNodeOperLuTermDefault OBJECT-TYPE SYNTAX INTEGER { unbind (1), termself (2), rshutd (3), poweroff (4) } MAX-ACCESS read-only STATUS current DESCRIPTION "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." ::= { snaNodeOperEntry 7 }
Internet Assigned Numbers Authority
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
1.3.6.1.2.1.34.1.1.3.1.1 | snaNodeOperName | 0 | 0 | The value identifies the current name of the Node. In Type 2.1 networks, this is a fully-qualified name, meaning that the Node na… |
1.3.6.1.2.1.34.1.1.3.1.2 | snaNodeOperType | 0 | 0 | The value identifies the current type of the Node. |
1.3.6.1.2.1.34.1.1.3.1.3 | snaNodeOperXidFormat | 0 | 0 | The value identifies the type of XID format currently used for this Node. Note that there is no format type 2. |
1.3.6.1.2.1.34.1.1.3.1.4 | snaNodeOperBlockNum | 0 | 0 | The value identifies the block number for this Node instance. It is the first 3 hexadecimal digits of the SNA Node id. |
1.3.6.1.2.1.34.1.1.3.1.5 | snaNodeOperIdNum | 0 | 0 | The value identifies the ID number for this Node instance. This is the last 5 hexadecimal digits of the SNA Node id. |
1.3.6.1.2.1.34.1.1.3.1.6 | snaNodeOperEnablingMethod | 0 | 0 | The value indicates how the Node is activated for the first time. The values have the following meanings: other (1) - not at boo… |
1.3.6.1.2.1.34.1.1.3.1.8 | snaNodeOperMaxLu | 0 | 0 | This value identifies the current, maximum number of LUs that are activated for this Node. For PU2.1, this object refers to the n… |
1.3.6.1.2.1.34.1.1.3.1.9 | snaNodeOperHostDescription | 0 | 0 | This value identifies the remote host currently associated with this Node. Since SSCP Id's may not be unique across hosts, the hos… |
1.3.6.1.2.1.34.1.1.3.1.10 | snaNodeOperStopMethod | 0 | 0 | This value identifies the current Node shutdown method to be used by the Agent to stop the Node. When the Agent changes the Node'… |
1.3.6.1.2.1.34.1.1.3.1.11 | snaNodeOperState | 0 | 0 | The current state of the Node. The values have the following meanings: inactive (1), a row representing the Node has been created … |
1.3.6.1.2.1.34.1.1.3.1.12 | snaNodeOperHostSscpId | 0 | 0 | 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 … |
1.3.6.1.2.1.34.1.1.3.1.13 | snaNodeOperStartTime | 0 | 0 | The timestamp (e.g, the Agent's sysUpTime value) at the Node activation. |
1.3.6.1.2.1.34.1.1.3.1.14 | snaNodeOperLastStateChange | 0 | 0 | The timestamp (e.g., the Agent's sysUpTime value) at the last state change of the Node. |
1.3.6.1.2.1.34.1.1.3.1.15 | snaNodeOperActFailures | 0 | 0 | This value identifies the number of failed Node activation attempts. |
1.3.6.1.2.1.34.1.1.3.1.16 | snaNodeOperActFailureReason | 0 | 0 | The value indicates the reason for the activation failure. The value 'other (1)' indicates a reason not listed in the enumeratio… |