As per Relevance of the word indicate, we have this rfc below:
Network Working Group Z.
Request for Comments: 1665 Eicon Technology
Category: Standards Track D.
Bell Communications
K.
July 1994
Definitions of Managed
for SNA NAUs using SMIv
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
Table of
1. Introduction ................................................ 2
2. The SNMPv2 Network Management Framework ..................... 2
2.1 Object Definitions ......................................... 2
3. Overview .................................................... 3
3.1 Applying MIB II to managing SNA NAUs ....................... 4
3.2 SNANAU MIB Structure ....................................... 4
3.2.1 snaNode group ............................................ 5
3.2.2 snaLu group .............................................. 6
3.2.3 snaMgtTools group ........................................ 7
3.2.4 Conformance statement .................................... 7
3.3 SNANAU MIB special feature ................................. 7
3.3.1 Row Creation mechanism ................................... 8
3.3.2 State Diagrams ........................................... 8
4. Object Definitions .......................................... 9
5. Acknowledgments ............................................. 66
6. References .................................................. 66
7. Security Considerations ..................................... 67
8. Authors' Addresses .......................................... 67
Kielczewski, Kostick & Shih [Page 1]
RFC 1665 SNANAU MIB July 1994
1.
This memo defines a portion of the Management Information Base (MIB
for use with network management protocols in the Internet community
In particular, it defines objects for managing the configuration
monitoring and control of Physical Units (PUs) and Logical
(LUs) in an SNA environment. PUs and LUs are two types of
Addressable Units (NAUs) in the logical structure of an SNA network
NAUs are the origination or destination points for SNA data streams
This memo identifies managed objects for PU Type 1.0, 2.0 and
2.1 and LU Type 0, 1, 2, 3, 4, 7. The generic objects defined
can also be used to manage LU 6.2 and any LU-LU session. The
terms and overall architecture are documented in [1].
2. The SNMPv2 Network Management
The SNMPv2 Network Management Framework consists of four
components. They are
o RFC 1442 [2] which defines the SMI, the mechanisms used
describing and naming objects for the purpose of management
o STD 17, RFC 1213 [3] defines MIB-II, the core set of
objects for the Internet suite of protocols
o RFC 1445 [4] which defines the administrative and
architectural aspects of the framework
o RFC 1448 [5] which defines the protocol used for
access to managed objects
The Framework permits new objects to be defined for the purpose
experimentation and evaluation
2.1. Object
Managed objects are accessed via a virtual information store,
the Management Information Base or MIB. Objects in the MIB
defined using the subset of Abstract Syntax Notation One (ASN.1)
defined in the SMI (RFC 1442 [2]). In particular, each object
is named by an OBJECT IDENTIFIER, an administratively assigned name
The object type together with an object instance serves to
identify a specific instantiation of the object. For
convenience, we often use a textual string, termed the descriptor,
refer to the object type
Kielczewski, Kostick & Shih [Page 2]
RFC 1665 SNANAU MIB July 1994
3.
This document identifies the proposed set of objects for managing
configuration, monitoring and control of Physical Units (PUs)
Logical Units (LUs) in an SNA environment. In this document, the
"Node" is used to describe SNA Node Type 1.0, 2.0 and Type 2.1
the name "LU" is used to describe Logical Unit of Type 0, 1, 2, 3, 4,
7 and 6.2. Note however that only objects common to all PU and
types are covered here and LU 6.2 specific objects are not
in this MIB module
Highlights of the management functions supported by the SNANAU
module include the following
o Creation/deletion of Nodes and LUs via the RowStatus
in the snaNodeAdminTable and in the snaLuAdminTable
o Creation/deletion of table entries associating Node
with link instances via the RowStatus object in
o Activation/Deactivation of Nodes via the AdminState object
the
o Deactivation of sessions via the AdminState object in
o Monitoring and modification of parameters related to Nodes, LUs
and Node/link
o Monitoring of session operational
o PU2.0 operational
o Session operational
o RTM
o Traps for
+ Node state
+ Node activation
+ LU state
+ LU session BIND
Kielczewski, Kostick & Shih [Page 3]
RFC 1665 SNANAU MIB July 1994
This MIB module does not support
o creation of links - the SNA DLC MIB [6] supports
capabilities for links
o activation or deactivation of LUs,
o activation of sessions
3.1. Applying MIB II to managing SNA
This section identifies how MIB II objects, specifically the MIB
system group will be used in SNMP-based management of SNA NAUs.
MIB II system group applies to the SNMP Agent. The following
is from the MIB II system group
sysUpTime: clock in the SNMP Agent/proxy-Agent; expressed
TimeTicks (1/100s of a seconds).
This MIB module uses the TimeStamp TEXTUAL-CONVENTION which
defined in the SNMPv2 Textual Conventions (RFC 1443 [7]) as "
value of MIB II's sysUpTime object when a specific
happens." The specific occurrences related to SNA NAU management
defined in this MIB module
3.2. SNANAU MIB
The SNANAU MIB module contains three groups of objects
o snaNode - objects related to Node configuration, monitoring
control
o snaLu - objects related to LU definition, monitoring
control
o snaMgtTools - objects related to specific management tools
known in SNA environment
These groups are described below in more detail
The objects related to PUs and LUs are organized into two types
tables: the Admin and Oper tables
The "Admin" table contains parameters which are used by a
Station to affect the operation of the SNA service. Some
are used to initialize and configure the SNA service at the
startup, while others can take effect immediately. A
Station can dynamically define SNA resources (PUs, LUs) by
Kielczewski, Kostick & Shih [Page 4]
RFC 1665 SNANAU MIB July 1994
new entries in the Admin table. It uses a special object, AdminState
to control the desired state of a defined PU or LU Session resource
Note that this MIB does not allow the manipulation of an LU'
operational state
The "Oper" table is an extension (augment) of the corresponding
table. It contains objects which correspond to the values
parameters currently used by the SNA system
3.2.1. snaNode
The snaNode group consists of the following tables
1) snaNodeAdminTable This table contains objects which
the configuration parameters of an SNA Node. Link-
configuration objects are contained in a separate MIB
(e.g., the SNA DLC MIB module) corresponding to link type
Entries in this table can be created, modified and deleted
either an Agent or a Management Station. The
object describes the status of an entry and is used to change
status of that entry
The snaNodeAdminState object describes the desired
state of a Node and is used to change the operational state of
Node
How an Agent or a Management Station obtains the initial value
each object at creation time is an implementation specific
not addressed in this memo
For each entry in the snaNodeAdminTable, there is a
entry in the snaNodeOperTable. While the objects in this
describe the desired or configured operational values of the
Node, the actual runtime values are contained in snaNodeOperTable
2) snaNodeOperTable - Each row contains runtime and
state variables for a Node. It is an extension
snaNodeAdminTable and as such uses the same index. The rows
this table are created by an Agent as soon as the entry in
Admin Table become 'active'. The entries in this table cannot
modified by a Management Station
3) snaPu20StatsTable - Each row contains statistics
(counters) for a PU 2.0. The entries in this table are indexed
snaNodeAdminIndex. The rows in this table are created by an
as soon as the corresponding entry in the
becomes 'active'.
Kielczewski, Kostick & Shih [Page 5]
RFC 1665 SNANAU MIB July 1994
4) snaNodeLinkAdminTable - This table contains all references
link- specific tables. If a Node is configured with
links, then it will have multiple entries in this table.
entries in this table can be generated initially, after startup
SNA service, by the Agent which uses information from
configuration file. Subsequent modifications of parameters
creation of new Node link entries and deletion of entries
possible. The modifications to this table can be saved in the
configuration file for the next startup (i.e., restart or
initialization) of SNA service, but the mechanism for
function is not defined in this memo. Each entry contains
configuration information that associates a Node instance to
link instance. The entries are indexed by snaNodeAdminIndex
snaNodeLinkAdminIndex
5) snaNodeLinkOperTable - This table contains all references
link- specific tables for operational parameters. If the Node
configured for multiple links, then it will have multiple
in this table. This table augments the snaNodeLinkAdminTable
6) snaNodeTraps - Two traps are defined for Nodes.
snaNodeStateChangeTrap indicates that the operational state of
Node has changed. The snaNodeActFailTrap indicates the failure
ACTPU received from host
3.2.2. snaLu
The snaLu group consists of the following tables
1) snaLuAdminTable - Table containing LU
information. The rows in this table can be created and deleted
a Management Station. Only objects which are common to all
of LUs are included in this table. The entries are indexed by
and LU indices
2) snaLuOperTable - Table containing dynamic runtime
and control variables relating to LUs. Only objects which
common to all types of LUs are included in this table. This
augments the snaLuAdminTable
3) snaLuSessnTable - This is a table containing objects
describe the operational state of LU-LU sessions. Only
which are common to all types of LU-LU sessions are included
this table. When a session enters the state 'pending-bind (2)',
the corresponding entry in the session table is created by
Agent. When the session state becomes 'unbound (1)', then
session will be removed from the session table by the Agent
Entries are indexed by Node, Link, LU and session indices
Kielczewski, Kostick & Shih [Page 6]
RFC 1665 SNANAU MIB July 1994
4) snaLuSessnStatsTable - Table containing dynamic
information relating to LU-LU sessions. The entries in this
augment the entries in the snaLuSessnTable and cannot be
by a Management Station
5) snaLuTraps - Two traps are defined for LUs.
snaLuStateChangeTrap indicates that the operational state of an
has changed. The snaLuSessnBindFailTrap indicates the failure
a BIND request
3.2.3. snaMgtTools
This is an optional group. The snaMgtTools group consists of
following table
1) snaLuRtmTable Each row contains Response Time Monitor (RTM
variables for an LU. The table is indexed by Node and LU indices
Entries correspond to LU 2 entries in the snaLuAdminTable.
Management Station can read collection of RTM statistics for
given LU
3.2.4. Conformance
Compliance of the SNMPv2 management entity to the SNANAU MIB
defined in terms of following conformance units called groups
Unconditionally mandatory groups: snaNodeGroup, snaLuGroup
snaSessionGroup
Conditionally mandatory groups: snaPu20Group - mandatory only
those entities which implement PU type 2.0. The
- mandatory only for those entities which implement LU type 2
RTM
Refinement of requirements for objects access: an Agent which
not implement row creation for
snaNodeLinkAdminTable and snaLuAdminTable must at least
object modification requests (i.e., read-write access instead
read-create).
3.3. SNANAU MIB special
This section describes the mechanism used for row creation in
Admin tables and also presents critical state transitions for PUs
LUs and Sessions
Kielczewski, Kostick & Shih [Page 7]
RFC 1665 SNANAU MIB July 1994
3.3.1. Row Creation
The row creation mechanism for the Admin tables in this MIB module
based on the use of the RowStatus object. Restriction of
operations for specific tables are described in each table.
particular, before accepting the 'destroy' value for an entry,
Agent has to verify the operational state of the corresponding
in the Oper table
3.3.2. State
The following state diagram models the state transitions for Nodes
When a row is created by a Management Station, an Agent creates
Oper table entry for that Node with the OperState equal
'inactive'. An Agent cannot accept any operations for that
until the RowStatus is set to 'active'.
OperState -> inactive active waiting
--------------I--------------I--------------I-------------I---------
AdminState: I I I
active I active I active I waiting I
I I I
inactive I inactive I stopping I inactive I
I or inactive
The following state diagram models state transitions for Sessions
When a session goes to the 'unbound' state [1], the
entry will be removed from the Session table by the Agent
OperState -> unbound pending-bind bound pending-
--------------I--------------I--------------I---------I--------------
AdminState: I I I
bound I no I no I no I
I I I
unbound I unbound I unbound I unbound I
Kielczewski, Kostick & Shih [Page 8]
RFC 1665 SNANAU MIB July 1994
4. Object
SNA-NAU-MIB DEFINITIONS ::=
-- This MIB module contains objects
-- for management of the following SNA devices: PU types 1.0, 2.0, 2.1
-- and LU types 0, 1, 2, 3, 4, 7. It also contains generic
-- which can be used to manage LU 6.2.
-- Naming conventions in this document
-- The following names are used in object descriptors according
-- SNA conventions
-- The name 'PU' or 'Node' is used to describe Node type 1.0, 2.0
-- 2.1.
-- The name 'LU' is used to describe Logical Unit of type 0,1,2,3,
-- 4,7 or 6.2.
DisplayString, RowStatus, TimeStamp,
FROM SNMPv2-
Counter32, Gauge32, Integer32,
OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-
FROM SNMPv2-
MODULE-COMPLIANCE, OBJECT-
FROM SNMPv2-CONF
snanauMIB MODULE-
LAST-UPDATED "9402041800Z
ORGANIZATION "IETF SNA NAU MIB Working Group
CONTACT-
" Zbigniew
Eicon Technology Inc
2196 32nd
Lachine, Que H8T 3H
Tel: 1 514 631 2592
E-mail: zbig@eicon.qc.
Deirdre
Bell Communications
Red Bank, NJ 07701
Tel: 1 908 758 2642
Kielczewski, Kostick & Shih [Page 9]
RFC 1665 SNANAU MIB July 1994
E-mail: dck2@mail.bellcore.
Kitty Shih (editor
890 Ross
Sunnyvale, CA 94089
Tel: 1 408 747 4305
E-mail: kmshih@novell.com
"This is the MIB module for objects used
manage SNA devices."
::= { mib-2 34 }
-- The SNANAU MIB module contains an objects part and a conformance part
-- Objects are organized into the following groups
-- (1)snaNode group
-- (2)snaLU group
-- (3)snaMgtTools group
snanauObjects OBJECT IDENTIFIER ::= { snanauMIB 1 }
snaNode OBJECT IDENTIFIER ::= { snanauObjects 1 }
snaLu OBJECT IDENTIFIER ::= { snanauObjects 2 }
snaMgtTools OBJECT IDENTIFIER ::= { snanauObjects 3}
-- ***************************************************************
-- snaNode
--
-- It contains Managed Objects related to any type of Node
-- some specific objects for Node Type 2.0.
-- ***************************************************************
-- ***************************************************************
-- The following table contains generic Node
-- parameters
-- ***************************************************************
snaNodeAdminTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"This table contains objects which describe
configuration parameters for an SNA Node.
specific configuration objects are contained
a separate MIB module (e.g., SNA DLC MIB
Kielczewski, Kostick & Shih [Page 10]
RFC 1665 SNANAU MIB July 1994
corresponding to the link type
The table snaNodeAdminLinkTable contains
which identify the relationship between node
and link instances
The entries (i.e., rows) in this table can be
by either an Agent or a Management Station
The Management Station can do this through
the appropriate value in the snaNodeAdminRowStatus
The snaNodeAdminRowStatus object describes
status of an entry and is used to change the
of an entry. The entry is deleted by an Agent
on the value of the snaNodeAdminRowStatus
The snaNodeAdminState object describes the
operational state of a Node and is used to change
operational state of a Node. For example,
information may be obtained from a configuration file
How an Agent or a Management Station obtains
initial value of each object at creation time is
implementation specific issue
For each entry in this table, there is a
entry in the snaNodeOperTable
While the objects in this table describe the
or configured operational values of the SNA Node,
actual runtime values are contained
snaNodeOperTable."
::= { snaNode 1 }
snaNodeAdminEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"An entry contains the configuration parameters
one SNA Node instance. The objects in the
have read-create access
An entry can be created, modified or deleted.
object snaNodeAdminRowStatus is used (i.e., set)
create or delete a row entry."
INDEX { snaNodeAdminIndex }
::= { snaNodeAdminTable 1 }
SnaNodeAdminEntry ::= SEQUENCE {
Kielczewski, Kostick & Shih [Page 11]
RFC 1665 SNANAU MIB July 1994
Integer32,
DisplayString
INTEGER
INTEGER
DisplayString
DisplayString
INTEGER
INTEGER
Integer32,
DisplayString
INTEGER
INTEGER
}
snaNodeAdminIndex OBJECT-
SYNTAX Integer32
MAX-ACCESS not-
STATUS
"Index used to uniquely identify each Node instance
If an Agent creates the entry, then it will
this number otherwise a Management
generates a random number when it reserves
entry for creation."
::= { snaNodeAdminEntry 1 }
snaNodeAdminName OBJECT-
SYNTAX DisplayString (SIZE(0..17))
MAX-ACCESS read-
STATUS
"The value indicates the desired name of
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 (
Kielczewski, Kostick & Shih [Page 12]
RFC 1665 SNANAU MIB July 1994
present) with a period as the delimiter
A write operation to this object
not change the operational value
in snaNodeOperName until the Node
been re-activated (e.g., after the next
of the SNA services)."
::= { snaNodeAdminEntry 2 }
snaNodeAdminType OBJECT-
SYNTAX INTEGER {
other(1),
pu10(2),
pu20(3),
t21len(4),
endNode(5),
networkNode(6)
}
MAX-ACCESS read-
STATUS
"The value indicates the type of SNA Node
A write operation to this object
not change the operational value
in snaNodeOperType until the Node
been re-activated (e.g., after the next
of the SNA services)."
::= { snaNodeAdminEntry 3 }
snaNodeAdminXidFormat OBJECT-
SYNTAX INTEGER {
format0(1),
format1(2),
format3(3)
}
MAX-ACCESS read-
STATUS
"The value indicates the type of XID format used
this Node
Note that there is no format type 2.
A write operation to this object
not change the operational value
in snaNodeOperAdminXidFormat until the Node
been re-activated (e.g., after the next
of the SNA services)."
Kielczewski, Kostick & Shih [Page 13]
RFC 1665 SNANAU MIB July 1994
::= { snaNodeAdminEntry 4 }
snaNodeAdminBlockNum OBJECT-
SYNTAX DisplayString (SIZE(3))
MAX-ACCESS read-
STATUS
"The value indicates the block number for this
instance. It is the first 3 hexadecimal digits of
SNA Node id
A write operation to this object
not change the operational value
in snaNodeOperBlockNum until the Node
been re-activated (e.g., after the next
of the SNA services)."
::= { snaNodeAdminEntry 5 }
snaNodeAdminIdNum OBJECT-
SYNTAX DisplayString (SIZE(5))
MAX-ACCESS read-
STATUS
"The value indicates the ID number for this
instance. This is the last 5 hexadecimal digits
the SNA Node id
A write operation to this object
not change the operational value
in snaNodeOperIdNum until the Node
been re-activated (e.g., after the next
of the SNA services)."
::= { snaNodeAdminEntry 6 }
snaNodeAdminEnablingMethod OBJECT-
SYNTAX INTEGER {
other (1),
startup (2),
demand (3),
onlyMS (4)
}
MAX-ACCESS read-
STATUS
"The value indicates how the Node should
activated for the first time
The values have the following meanings
Kielczewski, Kostick & Shih [Page 14]
RFC 1665 SNANAU MIB July 1994
other (1) - may be used for proprietary
not listed in this enumeration
startup (2) - at SNA services' initialization
(this is the default),
demand (3) - only when LU is requested by application
onlyMS (4) - by a Management Station only
A write operation to this object may
change the operational value
in snaNodeOperEnablingMethod
on the Agent implementation. If the
implementation accepts immediate changes, then
behavior of the Node changes immediately and not
after the next system startup of the SNA services
An immediate change may only apply when
current value `demand (3)' is changed to `onlyMS (4)'
and vice versa."
::= { snaNodeAdminEntry 7 }
snaNodeAdminLuTermDefault OBJECT-
SYNTAX INTEGER {
unbind (1),
termself (2),
rshutd (3),
poweroff(4)
}
MAX-ACCESS read-
STATUS
"The value indicates the desired default
used to deactivate LUs for this
For LU6.2s, `unbind(1)' is the only valid value
unbind(1) - terminate the LU-LU session by
an SNA UNBIND request
termself(2) - terminate the LU-LU session by
an SNA TERM-SELF (Terminate Self) request
the SSCP-LU session. The SSCP will inform
remote session LU partner to send an
request to terminate the session
rshutd(3) - terminate the LU-LU session by
an SNA RSHUTD (Request ShutDown) request
the remote session LU partner. The remote
will then send an UNBIND request to
the session
poweroff(4) - terminate the LU-LU session by
either an SNA LUSTAT (LU Status) request
Kielczewski, Kostick & Shih [Page 15]
RFC 1665 SNANAU MIB July 1994
the LU-LU session or an SNA NOTIFY request
the SSCP-LU session indicating that the LU
been powered off. Sending both is
acceptable. The result should be that
remote session LU partner will send an
to terminate the session
The default behavior indicated by the value of
object may be overridden for an LU instance.
override is performed by setting the
object instance in the snaLuAdminTable to the
value
A write operation to this object may
change the operational value
in snaNodeOperLuTermDefault
on the Agent implementation."
::= { snaNodeAdminEntry 8 }
snaNodeAdminMaxLu OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"The maximum number of LUs that may
activated for this Node. For PU2.1, this
refers to the number of dependent LUs
A write operation to this object
not change the operational value
in snaNodeOperMaxLu until the Node
been re-activated (e.g., after the next
of the SNA services)."
::= { snaNodeAdminEntry 9 }
snaNodeAdminHostDescription OBJECT-
SYNTAX DisplayString (SIZE(0..128))
MAX-ACCESS read-
STATUS
"The value identifies the remote host
with this Node. Since SSCP Id's may not be
across hosts, the host
is required to uniquely identify the SSCP
This object is only applicable to PU2.0
Nodes. If the remote host is unknown, then
value is the null string
Kielczewski, Kostick & Shih [Page 16]
RFC 1665 SNANAU MIB July 1994
A write operation to this object may
change the operational value
in snaNodeOperHostDescription
on the Agent implementation."
::= { snaNodeAdminEntry 10 }
snaNodeAdminStopMethod OBJECT-
SYNTAX INTEGER {
other (1),
normal (2),
immed (3),
force (4)
}
MAX-ACCESS read-
STATUS
"The value indicates the desired method to be
by the Agent to stop a Node (i.e., change the Node'
operational state to inactive(1) ).
The values have the following meaning
other (1) - used for
methods not listed in this enumeration
normal(2) - deactivate only when there is no
activity on this Node (i.e., all data
have been completed and all
have been terminated).
immed(3) - deactivate immediately regardless
current activities on this Node. Wait
deactivation responses (from remote Node
before changing the Node state to inactive
force(4) - deactivate immediately regardless
current activities on this Node. Do not
for deactivation responses (from remote Node
before changing the Node state to inactive
A write operation to this object may
change the operational value
in snaNodeOperStopMethod
on the Agent implementation."
::= { snaNodeAdminEntry 11 }
snaNodeAdminState OBJECT-
SYNTAX INTEGER {
inactive (1),
active (2)
}
Kielczewski, Kostick & Shih [Page 17]
RFC 1665 SNANAU MIB July 1994
MAX-ACCESS read-
STATUS
"The value indicates the desired
state of the SNA Node. This object is
by the Management Station
activate or deactivate the Node
If the current value in snaNodeOperState
`active (2)', then setting this object
`inactive (1)' will initiate the Node
process using the method
by snaNodeOperStopMethod
If the current value in snaNodeOperState
`inactive (1)', then setting this object
`active (2)' will initiate
Node's activation
A Management Station can always set this object
`active (2)' irrespective of the value in
snaOperEnablingMethod."
::= { snaNodeAdminEntry 12 }
snaNodeAdminRowStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"This object is used by a Management Station
create or delete the row entry in
snaNodeAdminTable
the RowStatus textual convention
Upon successful creation
the row, an Agent automatically creates
corresponding entry in the snaNodeOperTable
snaNodeOperState equal to `inactive (1)'.
Row deletion can be Management Station or
initiated
(a) The Management Station can set the value
`destroy (6)' only when the value
snaNodeOperState of this Node instance
`inactive (1)'. The Agent will then delete the
corresponding to this Node instance from
snaNodeAdminTable and the snaNodeOperTable
(b) The Agent detects that a row is in
Kielczewski, Kostick & Shih [Page 18]
RFC 1665 SNANAU MIB July 1994
`notReady (3)' state for greater than
default period of 5 minutes
(c) All rows with the snaNodeAdminRowStatus object'
value of `notReady (3)' will be removed upon
next initialization of the SNA services."
::= { snaNodeAdminEntry 13 }
-- ***************************************************************
-- The following object is updated when there is a change
-- the value of any object in the snaNodeAdminTable
-- ***************************************************************
snaNodeAdminTableLastChange OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value indicates the
(e.g., the Agent's sysUpTime value) of the
change made to any object in the snaNodeAdminTable
including row deletions/additions (e.g., changes
snaNodeAdminRowStatus values).
This object can be used to reduce
retrievals of the snaNodeAdminTable by a
Station. It is expected that a Management
will periodically poll this object and compare
current value with the previous one. A
indicates that some Node configuration
has been changed. Only then will the
Station retrieve the entire table."
::= { snaNode 2 }
-- ***************************************************************
-- The following table contains Node operational parameters
-- ***************************************************************
snaNodeOperTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"This table contains the dynamic parameters
have read-only access. These objects reflect
actual status of the Node. The entries in
table cannot be created or modified by
Kielczewski, Kostick & Shih [Page 19]
RFC 1665 SNANAU MIB July 1994
Management Station
This table augments the snaNodeAdminTable."
::= { snaNode 3 }
snaNodeOperEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"The entry contains parameters which describe
state of one Node. The entries are created by
Agent. They have read-only access."
AUGMENTS { snaNodeAdminEntry }
::= { snaNodeOperTable 1 }
SnaNodeOperEntry ::= SEQUENCE {
DisplayString
INTEGER
INTEGER
DisplayString
DisplayString
INTEGER
INTEGER
Integer32,
DisplayString
INTEGER
INTEGER
OCTET STRING
TimeStamp
TimeStamp
Counter32,
Kielczewski, Kostick & Shih [Page 20]
RFC 1665 SNANAU MIB July 1994
}
snaNodeOperName OBJECT-
SYNTAX DisplayString (SIZE(0..17))
MAX-ACCESS read-
STATUS
"The value identifies the current name of the Node
In Type 2.1 networks,
is a fully-qualified name, meaning that the Node
is preceded by the NetId (if present) with a
as the delimiter."
::= { snaNodeOperEntry 1 }
snaNodeOperType OBJECT-
SYNTAX INTEGER {
other(1),
pu10(2),
pu20(3),
t21LEN(4),
endNode(5),
networkNode(6)
}
MAX-ACCESS read-
STATUS
"The value identifies the current type of the Node."
::= { snaNodeOperEntry 2 }
snaNodeOperXidFormat OBJECT-
SYNTAX INTEGER {
format0 (1),
format1 (2),
format3 (3)
}
MAX-ACCESS read-
STATUS
"The value identifies the type of XID format
used for this Node
Note that there is no format type 2."
::= { snaNodeOperEntry 3 }
snaNodeOperBlockNum OBJECT-
SYNTAX DisplayString (SIZE(3))
MAX-ACCESS read-
STATUS
Kielczewski, Kostick & Shih [Page 21]
RFC 1665 SNANAU MIB July 1994
"The value identifies the block number for this
instance. It is the first 3 hexadecimal
of the SNA Node id."
::= { snaNodeOperEntry 4 }
snaNodeOperIdNum OBJECT-
SYNTAX DisplayString (SIZE(5))
MAX-ACCESS read-
STATUS
"The value identifies the ID number for this
instance. This is the last 5 hexadecimal digits
the SNA Node id."
::= { snaNodeOperEntry 5 }
snaNodeOperEnablingMethod OBJECT-
SYNTAX INTEGER {
other (1),
startup (2),
demand (3),
onlyMS (4)
}
MAX-ACCESS read-
STATUS
"The value indicates how the Node is activated
the first time
The values have the following meanings
other (1) - not at boot time, LU
or by a Management Station
startup (2) - at SNA services'
time (this is the default),
demand (3) - only when LU is requested
application
onlyMS (4) - by a network Management
only."
::= { snaNodeOperEntry 6 }
snaNodeOperLuTermDefault OBJECT-
SYNTAX INTEGER {
unbind (1),
termself (2),
rshutd (3),
poweroff (4)
}
MAX-ACCESS read-
STATUS
Kielczewski, Kostick & Shih [Page 22]
RFC 1665 SNANAU MIB July 1994
"The value identifies the default method used
deactivate LUs for this Node
For LU6.2s, 'unbind(1)' is the only valid value
unbind(1) - terminate the LU-LU session by
an SNA UNBIND request
termself(2) - terminate the LU-LU session by
an SNA TERM-SELF (Terminate Self) request
the SSCP-LU session. The SSCP will inform
remote session LU partner to send an
request to terminate the session
rshutd(3) - terminate the LU-LU session by
an SNA RSHUTD (Request ShutDown) request
the remote session LU partner. The remote
will then send an UNBIND request to
the session
poweroff(4) - terminate the LU-LU session by
either an SNA LUSTAT (LU Status) request
the LU-LU session or an SNA NOTIFY request
the SSCP-LU session indicating that the LU
been powered off. Sending both is
acceptable. The result should be that
remote session LU partner will send an
to terminate the session
This object describes the default behavior for this Node
however, it is possible that for a specific LU
behavior indicated by the snaLuOperTerm object
different."
::= { snaNodeOperEntry 7 }
snaNodeOperMaxLu OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"This value identifies the current, maximum
of LUs that are activated for this Node. For PU2.1,
this object refers to the number of dependent LUs."
::= { snaNodeOperEntry 8 }
snaNodeOperHostDescription OBJECT-
SYNTAX DisplayString (SIZE(0..128))
MAX-ACCESS read-
STATUS
Kielczewski, Kostick & Shih [Page 23]
RFC 1665 SNANAU MIB July 1994
"This value identifies the remote host
associated with this Node
Since SSCP Id's may not be
across hosts, the host
is required to uniquely identify the SSCP."
::= { snaNodeOperEntry 9 }
snaNodeOperStopMethod OBJECT-
SYNTAX INTEGER {
other (1),
normal (2),
immed (3),
force (4)
}
MAX-ACCESS read-
STATUS
"This value identifies the current Node
method to be used by the Agent to stop the Node
When the Agent changes the Node's state to '
(1)', the Agent must use the shutdown
indicated by this object
The values have the following meaning
other (1) - proprietary method not listed in
normal(2) - deactivate only when there is no
activity on this Node (i.e., all data
have been completed and all sessions
been terminated).
immed(3) - deactivate immediately regardless
current activities on this Node. Wait
deactivation responses (from remote Node
before changing the Node state to inactive
force(4) - deactivate immediately regardless
current activities on this Node. Do not
for deactivation responses (from remote Node
before changing the Node state to inactive
Note that a write operation
snaNodeAdminOperStopMethod may immediately
the value of snaNodeOperStopMethod depending
the Agent implementation."
::= { snaNodeOperEntry 10 }
snaNodeOperState OBJECT-
SYNTAX INTEGER {
Kielczewski, Kostick & Shih [Page 24]
RFC 1665 SNANAU MIB July 1994
inactive (1),
active (2),
waiting (3),
stopping (4)
}
MAX-ACCESS read-
STATUS
"The current state of the Node
The values have the following meanings
inactive (1), a row representing the Node
been created in the
and, the Node is ready for activation -or
an active Node has been stopped -or
a waiting Node has returned to the
state
waiting (3), a request to have the Node
has been issued, and the Node is
activation
active (2), the Node is ready and operating
stopping (4), the request to stop the Node
been issued while the StopMethod
or immediate is used."
::= { snaNodeOperEntry 11 }
snaNodeOperHostSscpId OBJECT-
SYNTAX OCTET STRING (SIZE(0..6))
MAX-ACCESS read-
STATUS
"This value identifies the current SSCP
associated with the Node. This object is
applicable to PU 2.0s. If the
is not a PU 2.0 type, then this object contains
zero length string."
::= { snaNodeOperEntry 12 }
snaNodeOperStartTime OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The timestamp (e.g, the Agent's sysUpTime value
at the Node activation."
::= { snaNodeOperEntry 13 }
snaNodeOperLastStateChange OBJECT-
SYNTAX
Kielczewski, Kostick & Shih [Page 25]
RFC 1665 SNANAU MIB July 1994
MAX-ACCESS read-
STATUS
"The timestamp (e.g., the Agent's sysUpTime value
at the last state change of the Node."
::= { snaNodeOperEntry 14 }
snaNodeOperActFailures OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"This value identifies the number of failed
activation attempts."
::= { snaNodeOperEntry 15 }
snaNodeOperActFailureReason OBJECT-
SYNTAX INTEGER {
other (1),
linkFailure (2),
noResources (3),
badConfiguration (4),
internalError (5)
}
MAX-ACCESS read-
STATUS
"The value indicates the reason for the
failure. The value `other (1)' indicates a
not listed in the enumeration. This
will be sent in the trap snaNodeActFailTrap."
::= { snaNodeOperEntry 16 }
-- ***************************************************************
-- The following object is updated when there is a change
-- the value of snaNodeOperState in any row or a row
-- added/deleted from the snaNodeOperTable via the snaNodeAdminTable
-- ***************************************************************
snaNodeOperTableLastChange OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The timestamp (e.g., the Agent's sysUpTime value
at the last change made to any object in
Kielczewski, Kostick & Shih [Page 26]
RFC 1665 SNANAU MIB July 1994
snaNodeOperTable, including row deletions/
made as a result of changes to
snaNodeAdminRowStatus object
This object can be used to reduce
retrievals of the snaNodeOperTable by a
Station. It is expected that a Management
will periodically poll this object and compare
current value with the previous one. A
indicates that some Node operational
has been changed. Only then will the
Station retrieve the entire table."
::= { snaNode 4 }
-- ***************************************************************
-- The following table contains PU 2.0 statistics dynamic parameters
-- ***************************************************************
snaPu20StatsTable OBJECT-
SYNTAX SEQUENCE OF SnaPu20
MAX-ACCESS not-
STATUS
"This table contains the dynamic parameters
have read-only access. The entries in this
correspond to PU 2.0 entries in the
and cannot be created by a Management Station."
::= { snaNode 5 }
snaPu20StatsEntry OBJECT-
SYNTAX SnaPu20
MAX-ACCESS not-
STATUS
"The entry contains parameters which describe
statistics for one PU 2.0. They have read-
access
The counters represent traffic for all
of sessions: LU-LU, SSCP-PU, SSCP-LU
Each Node of PU Type 2.0 from the
has one entry in this table and the index
here has the same value as snaNodeAdminIndex
that PU. The entry is created by the Agent."
INDEX { snaNodeAdminIndex }
::= { snaPu20StatsTable 1 }
Kielczewski, Kostick & Shih [Page 27]
RFC 1665 SNANAU MIB July 1994
SnaPu20StatsEntry ::= SEQUENCE {
snaPu20
Counter32,
snaPu20
Counter32,
snaPu20
Counter32,
snaPu20
Counter32,
snaPu20
Counter32,
snaPu20
Counter32,
snaPu20
Gauge32,
snaPu20
Gauge32,
snaPu20
Gauge32
}
snaPu20StatsSentBytes OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of bytes sent by this Node."
::= { snaPu20StatsEntry 1 }
snaPu20StatsReceivedBytes OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of bytes received by this Node."
::= { snaPu20StatsEntry 2 }
snaPu20StatsSentPius OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of PIUs sent by this Node."
::= { snaPu20StatsEntry 3 }
snaPu20StatsReceivedPius OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
Kielczewski, Kostick & Shih [Page 28]
RFC 1665 SNANAU MIB July 1994
STATUS
"The number of PIUs received by this Node."
::= { snaPu20StatsEntry 4 }
snaPu20StatsSentNegativeResps OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of negative responses
by this Node."
::= { snaPu20StatsEntry 5 }
snaPu20StatsReceivedNegativeResps OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of negative responses
by this Node."
::= { snaPu20StatsEntry 6 }
snaPu20StatsActLus OBJECT-
SYNTAX Gauge32
MAX-ACCESS read-
STATUS
"The number of LUs on this PU which
received and responded to ACTLU from the host."
::= { snaPu20StatsEntry 7 }
snaPu20StatsInActLus OBJECT-
SYNTAX Gauge32
MAX-ACCESS read-
STATUS
"The number of LUs on this PU which
not received an ACTLU from the host. This
possible if the number of configured LUs
that on the host."
::= { snaPu20StatsEntry 8 }
snaPu20StatsBindLus OBJECT-
SYNTAX Gauge32
MAX-ACCESS read-
STATUS
Kielczewski, Kostick & Shih [Page 29]
RFC 1665 SNANAU MIB July 1994
"The number of LUs on this PU which
received and acknowledged a BIND request from
host."
::= { snaPu20StatsEntry 9 }
-- ***************************************************************
-- The following table contains the association between Nodes
-- link identifiers
-- It is used for configuration purposes
-- ***************************************************************
snaNodeLinkAdminTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"This table contains the references to
specific tables. If a Node is configured
multiple links, then the Node will
multiple entries in this table
The entries in this table can be
initially, after initialization of SNA service
by the Agent which uses information
Node configuration file
Subsequent modifications of parameters
creation of new Nodes link entries and
of entries is possible
The modification to this table can
saved in the Node configuration file for
next initialization of SNA service, but the
for this function is not defined here."
::= { snaNode 6 }
snaNodeLinkAdminEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Entry contains the configuration information
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
later, after the entry has been created."
INDEX { snaNodeAdminIndex
Kielczewski, Kostick & Shih [Page 30]
RFC 1665 SNANAU MIB July 1994
snaNodeLinkAdminIndex }
::= { snaNodeLinkAdminTable 1 }
SnaNodeLinkAdminEntry ::= SEQUENCE {
Integer32,
InstancePointer
Integer32,
}
snaNodeLinkAdminIndex OBJECT-
SYNTAX Integer32
MAX-ACCESS not-
STATUS
"This value is used to index the instances of objects
If an Agent creates the entry, then it will
this number otherwise a Management
generates a random number when it reserves
entry for creation."
::= { snaNodeLinkAdminEntry 1 }
snaNodeLinkAdminSpecific OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"This value points to the ifIndex
instance (in the sdlcLSAdminTable
the SNA DLC MIB module) that corresponds to the link
SDLC link-specific information is provided in
SNA DLC MIB."
::= { snaNodeLinkAdminEntry 2 }
snaNodeLinkAdminMaxPiu OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"This value identifies the maximum number of
that can be exchanged by this Node in
Path Information Unit (PIU)."
::= { snaNodeLinkAdminEntry 3 }
Kielczewski, Kostick & Shih [Page 31]
RFC 1665 SNANAU MIB July 1994
snaNodeLinkAdminRowStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"This object is used by a Management Station
create or delete the row entry in
snaNodeLinkAdminTable
To activate a row, a Management Station sets the
to 'active (1)' or 'notReady (3)'. Upon
creation of the row, the Agent automatically
a corresponding entry in the snaNodeLinkOperTable
Row deletion can be Management Station or
initiated
(a) The Management Station can set the value
`destroy (6)' only when the value
snaNodeLinkOperState of this
instance is `inactive (1)'. The Agent will
delete the row corresponding to this
instance from snaNodeLinkOperTable
from snaNodeLinkAdminTable
(b) The Agent detects that a row is in
`notReady (3)' state for greater than
default period of 5 minutes
(c) The Agent will not include a row with RowStatus
`notReady (3)', after SNA system re-
(e.g., reboot)."
::= { snaNodeLinkAdminEntry 4 }
-- ***************************************************************
-- The following object is updated when there is a change
-- the value of any object in the snaNodeLinkAdminTable
-- ***************************************************************
snaNodeLinkAdminTableLastChange OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The timestamp (e.g., the Agent's sysUpTime value
at the
change made to any object in the snaNodeLinkAdminTable
including row deletions/additions (i.e.,
to the snaNodeLinkAdminRowStatus object).
Kielczewski, Kostick & Shih [Page 32]
RFC 1665 SNANAU MIB July 1994
This object can be used to reduce
retrievals of the snaNodeLinkAdminTable by
Management Station. It is expected that
Management Station will periodically poll
object and compare its current value with
previous one
A difference indicates that some Node
information has been changed. Only then will
Management Station retrieve the entire table."
::= { snaNode 7 }
-- ***************************************************************
-- The following table contains the association
-- Nodes and link identifiers
-- It provides the current status
-- ***************************************************************
snaNodeLinkOperTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"This table contains all references to
specific tables for operational parameters
If a Node is configured for multiple links
then the Node will have multiple entries
this table. This table augments
snaNodeLinkAdminTable."
::= { snaNode 8 }
snaNodeLinkOperEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Entry contains all current parameters for
Node link. The objects in the entry
read-only access."
AUGMENTS { snaNodeLinkAdminEntry }
::= { snaNodeLinkOperTable 1 }
SnaNodeLinkOperEntry ::= SEQUENCE {
InstancePointer
Integer32
}
Kielczewski, Kostick & Shih [Page 33]
RFC 1665 SNANAU MIB July 1994
snaNodeLinkOperSpecific OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"This is the object identifier
the instance of the ifIndex object
the sdlcLSOperTable (of the SNA DLC MIB module).
The associated sdlcLSOperTable
will contain information on the link instance."
::= { snaNodeLinkOperEntry 1 }
snaNodeLinkOperMaxPiu OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"Maximum number of octets that
be exchanged by this Node in one
Information Unit (PIU)."
::= { snaNodeLinkOperEntry 2 }
-- ***************************************************************
-- The following object is updated when a row is added/
-- from the snaNodeLinkOperTable
-- ***************************************************************
snaNodeLinkOperTableLastChange OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The timestamp of the
change made to any object in the snaNodeLinkOperTable
including row deletions/additions
This object can be used to reduce
retrievals of the snaNodeLinkOperTable by
Management Station. It is expected that
Management Station will periodically poll
object and compare its current value with
previous one
A difference indicates that some Node
information has been changed. Only then will
Management Station retrieve the entire table."
::= { snaNode 9 }
Kielczewski, Kostick & Shih [Page 34]
RFC 1665 SNANAU MIB July 1994
-- ***************************************************************
--
-- ***************************************************************
snaNodeTraps OBJECT IDENTIFIER ::= { snaNode 10 }
snaNodeStateChangeTrap NOTIFICATION-
OBJECTS { snaNodeOperName
snaNodeOperState }
STATUS
"This trap indicates that the operational
(i.e., value of the snaNodeOperState object) of a
has changed. The following variables are returned
snaNodeOperName - current name of the Node
with the instance identifying the Node; and
snaNodeOperState - current state
the change."
::= { snaNodeTraps 1 }
snaNodeActFailTrap NOTIFICATION-
OBJECTS { snaNodeOperName
snaNodeOperState
snaNodeOperActFailureReason }
STATUS
"This trap indicates a Node activation failure
The value of snaNodeOperState indicates the
state after the activation attempt
The value of snaNodeOperActFailureReason
the failure reason."
::= { snaNodeTraps 2 }
-- ***************************************************************
-- snaLu
--
-- It contains Managed Objects related to LUs in general and
-- specific for LUs of type 0, 1, 2, 3.
-- ***************************************************************
-- ***************************************************************
-- The following table contains LU configuration parameters
-- ***************************************************************
Kielczewski, Kostick & Shih [Page 35]
RFC 1665 SNANAU MIB July 1994
snaLuAdminTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"This table contains LU configuration information
The rows in this table can be created and
by a Management Station
Only objects which are common to all types of
are included in this table."
::= { snaLu 1 }
snaLuAdminEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Contains configuration variables for an LU."
INDEX { snaNodeAdminIndex, snaLuAdminLuIndex }
::= { snaLuAdminTable 1 }
SnaLuAdminEntry ::= SEQUENCE {
Integer32,
DisplayString
DisplayString
INTEGER
INTEGER
OCTET STRING
INTEGER
INTEGER
}
snaLuAdminLuIndex OBJECT-
SYNTAX Integer32
MAX-ACCESS not-
STATUS
"This value identifies the unique index for
Kielczewski, Kostick & Shih [Page 36]
RFC 1665 SNANAU MIB July 1994
LU instance within a Node."
::= { snaLuAdminEntry 1 }
snaLuAdminName OBJECT-
SYNTAX DisplayString (SIZE(0..48))
MAX-ACCESS read-
STATUS
"This value identifies the user
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
not change the operational value
in snaLuOperName until the Node
been re-activated (e.g., after the
initialization of the SNA services)."
::= { snaLuAdminEntry 2 }
snaLuAdminSnaName OBJECT-
SYNTAX DisplayString (SIZE(1..17))
MAX-ACCESS read-
STATUS
"This value identifies the SNA LU
used in exchange of SNA data
A write operation to this object
not change the operational value
in snaLuOperSnaName until the Node
been re-activated (e.g., after the
initialization of the SNA services)."
::= { snaLuAdminEntry 3 }
snaLuAdminType OBJECT-
SYNTAX INTEGER {
other(1),
lu0(2),
lu1(3),
lu2(4),
lu3(5),
lu4(6),
lu62(7),
lu7(8)
}
MAX-ACCESS read-
STATUS
Kielczewski, Kostick & Shih [Page 37]
RFC 1665 SNANAU MIB July 1994
"This value identifies the LU type
A write operation to this object
not change the operational value
in snaLuOperAdminType until the Node
been re-activated (e.g., after the
initialization of the SNA services)."
::= { snaLuAdminEntry 4 }
snaLuAdminDepType OBJECT-
SYNTAX INTEGER {
dependent(1),
independent(2)
}
MAX-ACCESS read-
STATUS
"This value identifies whether the LU
dependent or independent
A write operation to this object
not change the operational value
in snaLuOperDepType until the Node
been re-activated (e.g., after the
initialization of the SNA services)."
::= { snaLuAdminEntry 5 }
snaLuAdminLocalAddress OBJECT-
SYNTAX OCTET STRING (SIZE(1))
MAX-ACCESS read-
STATUS
"The local address for this LU is a byte with a
ranging from 0 to 254.For dependent LUs, this
ranges from 1 to 254 and for independent LUs
value is always 0.
A write operation to this object will not change
operational value reflected in
until the Node has been re-activated (e.g., after
next initialization of the SNA services)."
::= { snaLuAdminEntry 6 }
snaLuAdminDisplayModel OBJECT-
SYNTAX INTEGER {
invalid(1),
model2A(2),
model2B(3),
Kielczewski, Kostick & Shih [Page 38]
RFC 1665 SNANAU MIB July 1994
model3A(4),
model3B(5),
model4A(6),
model4B(7),
model5A(8),
model5B(9),
dynamic(10)
}
MAX-ACCESS read-
STATUS
"The value of this object identifies the model
and screen size of the terminal connected to the host
This is only valid for LU Type 2. The values
the following meaning
model2A(2) - Model 2 (24 rows x 80 cols) with
model2B(3) - Model 2 (24 rows x 80 cols)
extended
model3A(4) - Model 3 (32 rows x 80 cols) with
model3B(5) - Model 3 (32 rows x 80 cols) with
model4A(6) - Model 4 (43 rows x 80 cols) with
model4B(7) - Model 4 (43 rows x 80 cols) with
model5A(8) - Model 5 (27 rows x 132 cols) with
model5B(9) - Model 5 (27 rows x 132 cols)
extended
dynamic(10) - Screen size determine with BIND and
Partition Query
In case this LU is not Type 2, then this
should contain the invalid(1) value."
::= { snaLuAdminEntry 7 }
snaLuAdminTerm OBJECT-
SYNTAX INTEGER {
unbind (1),
termself (2),
rshutd (3),
poweroff (4)
}
MAX-ACCESS read-
STATUS
Kielczewski, Kostick & Shih [Page 39]
RFC 1665 SNANAU MIB July 1994
"This value identifies the desired method
deactivation of this LU. This value overrides
default method (snaNodeOperLuTermDefault) for
Node. For LU 6.2, only the value 'unbind (1)'
applies
unbind(1) - terminate the LU-LU session by
an SNA UNBIND request
termself(2) - terminate the LU-LU session by
an SNA TERM-SELF (Terminate Self) request
the SSCP-LU session. The SSCP will inform
remote session LU partner to send an
request to terminate the session
rshutd(3) - terminate the LU-LU session by
an SNA RSHUTD (Request ShutDown) request
the remote session LU partner. The remote
will then send an UNBIND request to
the session
poweroff(4) - terminate the LU-LU session by
either an SNA LUSTAT (LU Status) request
the LU-LU session or an SNA NOTIFY request
the SSCP-LU session indicating that the LU
been powered off. Sending both is
acceptable. The result should be that
remote session LU partner will send an
to terminate the session
A write operation to this object may
change the operational value
in snaLuOperTerm
on the Agent implementation."
::= { snaLuAdminEntry 8 }
snaLuAdminRowStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"This object is used by a Management Station
create or delete the row entry in
snaLuAdminTable
To activate a row, the Management Station sets
value to 'active (1)' or 'notReady (3)'.
Upon successful creation of the row, the
automatically creates a corresponding entry in
snaLuOperTable with snaLuOperState equal
'inactive (1)'.
Kielczewski, Kostick & Shih [Page 40]
RFC 1665 SNANAU MIB July 1994
Row deletion can be Management Station or
initiated
(a) The Management Station can set the value
'destroy (6)' only when the value of
of this LU instance is 'inactive (1)'. The Agent
then delete the row corresponding to this
instance from snaLuAdminTable
from snaLuOperTable
(b) The Agent detects that a row is in
'notReady (3)' state for greater than
default period of 5 minutes
(c) The Agent will not create a row with
equal to 'notReady (3)', after SNA
re-initialization (e.g., reboot)."
::= { snaLuAdminEntry 9 }
-- ***************************************************************
-- The following table contains LU state dynamic parameters
-- ***************************************************************
snaLuOperTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"This table contains dynamic runtime information
control variables relating to LUs
Only objects which are common to all types of LUs
included in this table. This table augments
snaLuAdminTable."
::= { snaLu 2 }
snaLuOperEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Contains objects reflecting current
for an LU
Each entry is created by the Agent. All
have read-only access."
AUGMENTS { snaLuAdminEntry }
::= { snaLuOperTable 1 }
SnaLuOperEntry ::= SEQUENCE {
DisplayString
Kielczewski, Kostick & Shih [Page 41]
RFC 1665 SNANAU MIB July 1994
DisplayString
INTEGER
INTEGER
OCTET STRING
INTEGER
INTEGER
INTEGER
Gauge32
}
snaLuOperName OBJECT-
SYNTAX DisplayString (SIZE(0..48))
MAX-ACCESS read-
STATUS
"User configurable name for this LU. If a
is not assigned, then this object contains
zero length string."
::= { snaLuOperEntry 1 }
snaLuOperSnaName OBJECT-
SYNTAX DisplayString (SIZE(1..17))
MAX-ACCESS read-
STATUS
"The value identifies the current SNA LU name."
::= { snaLuOperEntry 2 }
snaLuOperType OBJECT-
SYNTAX INTEGER {
other(1),
lu0(2),
lu1(3),
lu2(4),
lu3(5),
lu4(6),
lu62(7),
lu7(8)
}
MAX-ACCESS read-
Kielczewski, Kostick & Shih [Page 42]
RFC 1665 SNANAU MIB July 1994
STATUS
"The value identifies the current LU type."
::= { snaLuOperEntry 3 }
snaLuOperDepType OBJECT-
SYNTAX INTEGER {
dependent(1),
independent(2)
}
MAX-ACCESS read-
STATUS
"The 