| 1 |
<pre>Network Working Group Z. Kielczewski |
| 2 |
Request for Comments: 1665 Eicon Technology Corporation |
| 3 |
Category: Standards Track D. Kostick |
| 4 |
Bell Communications Research |
| 5 |
K. Shih |
| 6 |
Novell |
| 7 |
Editors |
| 8 |
July 1994 |
| 9 |
|
| 10 |
|
| 11 |
<span class="h1">Definitions of Managed Objects</span> |
| 12 |
<span class="h1">for SNA NAUs using SMIv2</span> |
| 13 |
|
| 14 |
Status of this Memo |
| 15 |
|
| 16 |
This document specifies an Internet standards track protocol for the |
| 17 |
Internet community, and requests discussion and suggestions for |
| 18 |
improvements. Please refer to the current edition of the "Internet |
| 19 |
Official Protocol Standards" (STD 1) for the standardization state |
| 20 |
and status of this protocol. Distribution of this memo is unlimited. |
| 21 |
|
| 22 |
Table of Contents |
| 23 |
|
| 24 |
<a href="#section-1">1</a>. Introduction ................................................ <a href="#page-2">2</a> |
| 25 |
<a href="#section-2">2</a>. The SNMPv2 Network Management Framework ..................... <a href="#page-2">2</a> |
| 26 |
<a href="#section-2.1">2.1</a> Object Definitions ......................................... <a href="#page-2">2</a> |
| 27 |
<a href="#section-3">3</a>. Overview .................................................... <a href="#page-3">3</a> |
| 28 |
<a href="#section-3.1">3.1</a> Applying MIB II to managing SNA NAUs ....................... <a href="#page-4">4</a> |
| 29 |
<a href="#section-3.2">3.2</a> SNANAU MIB Structure ....................................... <a href="#page-4">4</a> |
| 30 |
<a href="#section-3.2.1">3.2.1</a> snaNode group ............................................ <a href="#page-5">5</a> |
| 31 |
<a href="#section-3.2.2">3.2.2</a> snaLu group .............................................. <a href="#page-6">6</a> |
| 32 |
<a href="#section-3.2.3">3.2.3</a> snaMgtTools group ........................................ <a href="#page-7">7</a> |
| 33 |
<a href="#section-3.2.4">3.2.4</a> Conformance statement .................................... <a href="#page-7">7</a> |
| 34 |
<a href="#section-3.3">3.3</a> SNANAU MIB special feature ................................. <a href="#page-7">7</a> |
| 35 |
<a href="#section-3.3.1">3.3.1</a> Row Creation mechanism ................................... <a href="#page-8">8</a> |
| 36 |
<a href="#section-3.3.2">3.3.2</a> State Diagrams ........................................... <a href="#page-8">8</a> |
| 37 |
<a href="#section-4">4</a>. Object Definitions .......................................... <a href="#page-9">9</a> |
| 38 |
<a href="#section-5">5</a>. Acknowledgments ............................................. <a href="#page-66">66</a> |
| 39 |
<a href="#section-6">6</a>. References .................................................. <a href="#page-66">66</a> |
| 40 |
<a href="#section-7">7</a>. Security Considerations ..................................... <a href="#page-67">67</a> |
| 41 |
<a href="#section-8">8</a>. Authors' Addresses .......................................... <a href="#page-67">67</a> |
| 42 |
|
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Kielczewski, Kostick & Shih [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 55 |
|
| 56 |
|
| 57 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 58 |
|
| 59 |
This memo defines a portion of the Management Information Base (MIB) |
| 60 |
for use with network management protocols in the Internet community. |
| 61 |
In particular, it defines objects for managing the configuration, |
| 62 |
monitoring and control of Physical Units (PUs) and Logical Units |
| 63 |
(LUs) in an SNA environment. PUs and LUs are two types of Network |
| 64 |
Addressable Units (NAUs) in the logical structure of an SNA network. |
| 65 |
NAUs are the origination or destination points for SNA data streams. |
| 66 |
This memo identifies managed objects for PU Type 1.0, 2.0 and Type |
| 67 |
2.1 and LU Type 0, 1, 2, 3, 4, 7. The generic objects defined here |
| 68 |
can also be used to manage LU 6.2 and any LU-LU session. The SNA |
| 69 |
terms and overall architecture are documented in [<a href="#ref-1" title="Systems Network Architecture Technical Overview">1</a>]. |
| 70 |
|
| 71 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. The SNMPv2 Network Management Framework</span> |
| 72 |
|
| 73 |
The SNMPv2 Network Management Framework consists of four major |
| 74 |
components. They are: |
| 75 |
|
| 76 |
o <a href="./rfc1442">RFC 1442</a> [<a href="#ref-2" title=""Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2)"">2</a>] which defines the SMI, the mechanisms used for |
| 77 |
describing and naming objects for the purpose of management. |
| 78 |
|
| 79 |
o STD 17, <a href="./rfc1213">RFC 1213</a> [<a href="#ref-3" title=""Management Information Base for Network Management of TCP/IP-based internets - MIB-II"">3</a>] defines MIB-II, the core set of managed |
| 80 |
objects for the Internet suite of protocols. |
| 81 |
|
| 82 |
o <a href="./rfc1445">RFC 1445</a> [<a href="#ref-4" title=""Administrative Model for version 2 of the Simple Network Management Protocol (SNMPv2)"">4</a>] which defines the administrative and other |
| 83 |
architectural aspects of the framework. |
| 84 |
|
| 85 |
o <a href="./rfc1448">RFC 1448</a> [<a href="#ref-5" title=""Protocol Operations for version 2 of the Simple Network Management Protocol (SNMPv2)"">5</a>] which defines the protocol used for network |
| 86 |
access to managed objects. |
| 87 |
|
| 88 |
The Framework permits new objects to be defined for the purpose of |
| 89 |
experimentation and evaluation. |
| 90 |
|
| 91 |
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Object Definitions</span> |
| 92 |
|
| 93 |
Managed objects are accessed via a virtual information store, termed |
| 94 |
the Management Information Base or MIB. Objects in the MIB are |
| 95 |
defined using the subset of Abstract Syntax Notation One (ASN.1) |
| 96 |
defined in the SMI (<a href="./rfc1442">RFC 1442</a> [<a href="#ref-2" title=""Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2)"">2</a>]). In particular, each object type |
| 97 |
is named by an OBJECT IDENTIFIER, an administratively assigned name. |
| 98 |
The object type together with an object instance serves to uniquely |
| 99 |
identify a specific instantiation of the object. For human |
| 100 |
convenience, we often use a textual string, termed the descriptor, to |
| 101 |
refer to the object type. |
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Kielczewski, Kostick & Shih [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 111 |
|
| 112 |
|
| 113 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Overview</span> |
| 114 |
|
| 115 |
This document identifies the proposed set of objects for managing the |
| 116 |
configuration, monitoring and control of Physical Units (PUs) and |
| 117 |
Logical Units (LUs) in an SNA environment. In this document, the name |
| 118 |
"Node" is used to describe SNA Node Type 1.0, 2.0 and Type 2.1 and |
| 119 |
the name "LU" is used to describe Logical Unit of Type 0, 1, 2, 3, 4, |
| 120 |
7 and 6.2. Note however that only objects common to all PU and LU |
| 121 |
types are covered here and LU 6.2 specific objects are not included |
| 122 |
in this MIB module. |
| 123 |
|
| 124 |
Highlights of the management functions supported by the SNANAU MIB |
| 125 |
module include the following: |
| 126 |
|
| 127 |
|
| 128 |
o Creation/deletion of Nodes and LUs via the RowStatus objects |
| 129 |
in the snaNodeAdminTable and in the snaLuAdminTable. |
| 130 |
|
| 131 |
o Creation/deletion of table entries associating Node instances |
| 132 |
with link instances via the RowStatus object in the |
| 133 |
snaNodeLinkAdminTable |
| 134 |
|
| 135 |
o Activation/Deactivation of Nodes via the AdminState object in |
| 136 |
the snaNodeAdminTable |
| 137 |
|
| 138 |
o Deactivation of sessions via the AdminState object in the |
| 139 |
snaLuSessnTable |
| 140 |
|
| 141 |
o Monitoring and modification of parameters related to Nodes, LUs, |
| 142 |
and Node/link associations |
| 143 |
|
| 144 |
o Monitoring of session operational parameters |
| 145 |
|
| 146 |
o PU2.0 operational statistics |
| 147 |
|
| 148 |
o Session operational statistics |
| 149 |
|
| 150 |
o RTM statistics |
| 151 |
|
| 152 |
o Traps for: |
| 153 |
+ Node state change |
| 154 |
+ Node activation failure |
| 155 |
+ LU state change |
| 156 |
+ LU session BIND failure |
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Kielczewski, Kostick & Shih [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 167 |
|
| 168 |
|
| 169 |
This MIB module does not support: |
| 170 |
|
| 171 |
o creation of links - the SNA DLC MIB [<a href="#ref-6" title=""Definitions of Managed Objects for SNA Data Link Control: SDLC"">6</a>] supports management |
| 172 |
capabilities for links, |
| 173 |
|
| 174 |
o activation or deactivation of LUs, nor |
| 175 |
|
| 176 |
o activation of sessions. |
| 177 |
|
| 178 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Applying MIB II to managing SNA NAUs</span> |
| 179 |
|
| 180 |
This section identifies how MIB II objects, specifically the MIB II |
| 181 |
system group will be used in SNMP-based management of SNA NAUs. The |
| 182 |
MIB II system group applies to the SNMP Agent. The following object |
| 183 |
is from the MIB II system group: |
| 184 |
|
| 185 |
sysUpTime: clock in the SNMP Agent/proxy-Agent; expressed in |
| 186 |
TimeTicks (1/100s of a seconds). |
| 187 |
|
| 188 |
This MIB module uses the TimeStamp TEXTUAL-CONVENTION which is |
| 189 |
defined in the SNMPv2 Textual Conventions (<a href="./rfc1443">RFC 1443</a> [<a href="#ref-7" title=""Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2)"">7</a>]) as "the |
| 190 |
value of MIB II's sysUpTime object when a specific occurrence |
| 191 |
happens." The specific occurrences related to SNA NAU management are |
| 192 |
defined in this MIB module. |
| 193 |
|
| 194 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. SNANAU MIB Structure</span> |
| 195 |
|
| 196 |
The SNANAU MIB module contains three groups of objects: |
| 197 |
|
| 198 |
o snaNode - objects related to Node configuration, monitoring and |
| 199 |
control. |
| 200 |
|
| 201 |
o snaLu - objects related to LU definition, monitoring and |
| 202 |
control. |
| 203 |
|
| 204 |
o snaMgtTools - objects related to specific management tools well |
| 205 |
known in SNA environment. |
| 206 |
|
| 207 |
These groups are described below in more detail. |
| 208 |
|
| 209 |
The objects related to PUs and LUs are organized into two types of |
| 210 |
tables: the Admin and Oper tables. |
| 211 |
|
| 212 |
The "Admin" table contains parameters which are used by a Management |
| 213 |
Station to affect the operation of the SNA service. Some parameters |
| 214 |
are used to initialize and configure the SNA service at the next |
| 215 |
startup, while others can take effect immediately. A Management |
| 216 |
Station can dynamically define SNA resources (PUs, LUs) by creating |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Kielczewski, Kostick & Shih [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 223 |
|
| 224 |
|
| 225 |
new entries in the Admin table. It uses a special object, AdminState, |
| 226 |
to control the desired state of a defined PU or LU Session resource. |
| 227 |
Note that this MIB does not allow the manipulation of an LU's |
| 228 |
operational state. |
| 229 |
|
| 230 |
The "Oper" table is an extension (augment) of the corresponding Admin |
| 231 |
table. It contains objects which correspond to the values of |
| 232 |
parameters currently used by the SNA system. |
| 233 |
|
| 234 |
<span class="h4"><a class="selflink" id="section-3.2.1" href="#section-3.2.1">3.2.1</a>. snaNode group</span> |
| 235 |
|
| 236 |
The snaNode group consists of the following tables: |
| 237 |
|
| 238 |
1) snaNodeAdminTable This table contains objects which describe |
| 239 |
the configuration parameters of an SNA Node. Link-specific |
| 240 |
configuration objects are contained in a separate MIB module |
| 241 |
(e.g., the SNA DLC MIB module) corresponding to link type. |
| 242 |
Entries in this table can be created, modified and deleted by |
| 243 |
either an Agent or a Management Station. The snaNodeAdminRowStatus |
| 244 |
object describes the status of an entry and is used to change the |
| 245 |
status of that entry. |
| 246 |
|
| 247 |
The snaNodeAdminState object describes the desired operational |
| 248 |
state of a Node and is used to change the operational state of a |
| 249 |
Node. |
| 250 |
|
| 251 |
How an Agent or a Management Station obtains the initial value of |
| 252 |
each object at creation time is an implementation specific issue |
| 253 |
not addressed in this memo. |
| 254 |
|
| 255 |
For each entry in the snaNodeAdminTable, there is a corresponding |
| 256 |
entry in the snaNodeOperTable. While the objects in this table |
| 257 |
describe the desired or configured operational values of the SNA |
| 258 |
Node, the actual runtime values are contained in snaNodeOperTable. |
| 259 |
|
| 260 |
2) snaNodeOperTable - Each row contains runtime and operational |
| 261 |
state variables for a Node. It is an extension of |
| 262 |
snaNodeAdminTable and as such uses the same index. The rows in |
| 263 |
this table are created by an Agent as soon as the entry in the |
| 264 |
Admin Table become 'active'. The entries in this table cannot be |
| 265 |
modified by a Management Station. |
| 266 |
|
| 267 |
3) snaPu20StatsTable - Each row contains statistics variables |
| 268 |
(counters) for a PU 2.0. The entries in this table are indexed by |
| 269 |
snaNodeAdminIndex. The rows in this table are created by an Agent |
| 270 |
as soon as the corresponding entry in the snaNodeAdminTable |
| 271 |
becomes 'active'. |
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Kielczewski, Kostick & Shih [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 279 |
|
| 280 |
|
| 281 |
4) snaNodeLinkAdminTable - This table contains all references to |
| 282 |
link- specific tables. If a Node is configured with multiple |
| 283 |
links, then it will have multiple entries in this table. The |
| 284 |
entries in this table can be generated initially, after startup of |
| 285 |
SNA service, by the Agent which uses information from Node |
| 286 |
configuration file. Subsequent modifications of parameters, |
| 287 |
creation of new Node link entries and deletion of entries is |
| 288 |
possible. The modifications to this table can be saved in the Node |
| 289 |
configuration file for the next startup (i.e., restart or next |
| 290 |
initialization) of SNA service, but the mechanism for this |
| 291 |
function is not defined in this memo. Each entry contains the |
| 292 |
configuration information that associates a Node instance to one |
| 293 |
link instance. The entries are indexed by snaNodeAdminIndex and |
| 294 |
snaNodeLinkAdminIndex. |
| 295 |
|
| 296 |
5) snaNodeLinkOperTable - This table contains all references to |
| 297 |
link- specific tables for operational parameters. If the Node is |
| 298 |
configured for multiple links, then it will have multiple entries |
| 299 |
in this table. This table augments the snaNodeLinkAdminTable. |
| 300 |
|
| 301 |
6) snaNodeTraps - Two traps are defined for Nodes. The |
| 302 |
snaNodeStateChangeTrap indicates that the operational state of a |
| 303 |
Node has changed. The snaNodeActFailTrap indicates the failure of |
| 304 |
ACTPU received from host. |
| 305 |
|
| 306 |
<span class="h4"><a class="selflink" id="section-3.2.2" href="#section-3.2.2">3.2.2</a>. snaLu group</span> |
| 307 |
|
| 308 |
The snaLu group consists of the following tables: |
| 309 |
|
| 310 |
1) snaLuAdminTable - Table containing LU configuration |
| 311 |
information. The rows in this table can be created and deleted by |
| 312 |
a Management Station. Only objects which are common to all types |
| 313 |
of LUs are included in this table. The entries are indexed by Node |
| 314 |
and LU indices. |
| 315 |
|
| 316 |
2) snaLuOperTable - Table containing dynamic runtime information |
| 317 |
and control variables relating to LUs. Only objects which are |
| 318 |
common to all types of LUs are included in this table. This table |
| 319 |
augments the snaLuAdminTable. |
| 320 |
|
| 321 |
3) snaLuSessnTable - This is a table containing objects which |
| 322 |
describe the operational state of LU-LU sessions. Only objects |
| 323 |
which are common to all types of LU-LU sessions are included in |
| 324 |
this table. When a session enters the state 'pending-bind (2)', |
| 325 |
the corresponding entry in the session table is created by the |
| 326 |
Agent. When the session state becomes 'unbound (1)', then the |
| 327 |
session will be removed from the session table by the Agent. |
| 328 |
Entries are indexed by Node, Link, LU and session indices. |
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Kielczewski, Kostick & Shih [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 335 |
|
| 336 |
|
| 337 |
4) snaLuSessnStatsTable - Table containing dynamic statistics |
| 338 |
information relating to LU-LU sessions. The entries in this table |
| 339 |
augment the entries in the snaLuSessnTable and cannot be created |
| 340 |
by a Management Station. |
| 341 |
|
| 342 |
5) snaLuTraps - Two traps are defined for LUs. The |
| 343 |
snaLuStateChangeTrap indicates that the operational state of an LU |
| 344 |
has changed. The snaLuSessnBindFailTrap indicates the failure of |
| 345 |
a BIND request. |
| 346 |
|
| 347 |
<span class="h4"><a class="selflink" id="section-3.2.3" href="#section-3.2.3">3.2.3</a>. snaMgtTools group</span> |
| 348 |
|
| 349 |
This is an optional group. The snaMgtTools group consists of the |
| 350 |
following table: |
| 351 |
|
| 352 |
1) snaLuRtmTable Each row contains Response Time Monitor (RTM) |
| 353 |
variables for an LU. The table is indexed by Node and LU indices. |
| 354 |
Entries correspond to LU 2 entries in the snaLuAdminTable. A |
| 355 |
Management Station can read collection of RTM statistics for a |
| 356 |
given LU. |
| 357 |
|
| 358 |
<span class="h4"><a class="selflink" id="section-3.2.4" href="#section-3.2.4">3.2.4</a>. Conformance statement</span> |
| 359 |
|
| 360 |
Compliance of the SNMPv2 management entity to the SNANAU MIB is |
| 361 |
defined in terms of following conformance units called groups. |
| 362 |
|
| 363 |
Unconditionally mandatory groups: snaNodeGroup, snaLuGroup, |
| 364 |
snaSessionGroup. |
| 365 |
|
| 366 |
Conditionally mandatory groups: snaPu20Group - mandatory only for |
| 367 |
those entities which implement PU type 2.0. The snaMgtToolsRtmGroup |
| 368 |
- mandatory only for those entities which implement LU type 2 and |
| 369 |
RTM. |
| 370 |
|
| 371 |
Refinement of requirements for objects access: an Agent which does |
| 372 |
not implement row creation for snaNodeAdminTable |
| 373 |
snaNodeLinkAdminTable and snaLuAdminTable must at least support |
| 374 |
object modification requests (i.e., read-write access instead of |
| 375 |
read-create). |
| 376 |
|
| 377 |
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. SNANAU MIB special feature</span> |
| 378 |
|
| 379 |
This section describes the mechanism used for row creation in the |
| 380 |
Admin tables and also presents critical state transitions for PUs, |
| 381 |
LUs and Sessions. |
| 382 |
|
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Kielczewski, Kostick & Shih [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 391 |
|
| 392 |
|
| 393 |
<span class="h4"><a class="selflink" id="section-3.3.1" href="#section-3.3.1">3.3.1</a>. Row Creation mechanism</span> |
| 394 |
|
| 395 |
The row creation mechanism for the Admin tables in this MIB module is |
| 396 |
based on the use of the RowStatus object. Restriction of some |
| 397 |
operations for specific tables are described in each table. In |
| 398 |
particular, before accepting the 'destroy' value for an entry, an |
| 399 |
Agent has to verify the operational state of the corresponding entry |
| 400 |
in the Oper table. |
| 401 |
|
| 402 |
<span class="h4"><a class="selflink" id="section-3.3.2" href="#section-3.3.2">3.3.2</a>. State Diagrams</span> |
| 403 |
|
| 404 |
The following state diagram models the state transitions for Nodes. |
| 405 |
When a row is created by a Management Station, an Agent creates the |
| 406 |
Oper table entry for that Node with the OperState equal to |
| 407 |
'inactive'. An Agent cannot accept any operations for that Node |
| 408 |
until the RowStatus is set to 'active'. |
| 409 |
|
| 410 |
OperState -> inactive active waiting stopping |
| 411 |
--------------I--------------I--------------I-------------I--------- |
| 412 |
AdminState: I I I I |
| 413 |
active I active I active I waiting I no |
| 414 |
I I I I |
| 415 |
inactive I inactive I stopping I inactive I stopping |
| 416 |
I or inactive I |
| 417 |
|
| 418 |
The following state diagram models state transitions for Sessions. |
| 419 |
When a session goes to the 'unbound' state [<a href="#ref-1" title="Systems Network Architecture Technical Overview">1</a>], the corresponding |
| 420 |
entry will be removed from the Session table by the Agent. |
| 421 |
|
| 422 |
OperState -> unbound pending-bind bound pending-unbind |
| 423 |
--------------I--------------I--------------I---------I-------------- |
| 424 |
AdminState: I I I I |
| 425 |
bound I no I no I no I no |
| 426 |
I I I I |
| 427 |
unbound I unbound I unbound I unbound I unbound |
| 428 |
|
| 429 |
|
| 430 |
|
| 431 |
|
| 432 |
|
| 433 |
|
| 434 |
|
| 435 |
|
| 436 |
|
| 437 |
|
| 438 |
|
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Kielczewski, Kostick & Shih [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 447 |
|
| 448 |
|
| 449 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Object Definitions</span> |
| 450 |
|
| 451 |
SNA-NAU-MIB DEFINITIONS ::= BEGIN |
| 452 |
|
| 453 |
-- This MIB module contains objects necessary |
| 454 |
-- for management of the following SNA devices: PU types 1.0, 2.0, 2.1 |
| 455 |
-- and LU types 0, 1, 2, 3, 4, 7. It also contains generic objects |
| 456 |
-- which can be used to manage LU 6.2. |
| 457 |
|
| 458 |
-- Naming conventions in this document: |
| 459 |
-- The following names are used in object descriptors according to |
| 460 |
-- SNA conventions. |
| 461 |
-- The name 'PU' or 'Node' is used to describe Node type 1.0, 2.0 or |
| 462 |
-- 2.1. |
| 463 |
-- The name 'LU' is used to describe Logical Unit of type 0,1,2,3, |
| 464 |
-- 4,7 or 6.2. |
| 465 |
|
| 466 |
|
| 467 |
|
| 468 |
IMPORTS |
| 469 |
DisplayString, RowStatus, TimeStamp, InstancePointer |
| 470 |
FROM SNMPv2-TC |
| 471 |
|
| 472 |
Counter32, Gauge32, Integer32, |
| 473 |
OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE |
| 474 |
FROM SNMPv2-SMI |
| 475 |
|
| 476 |
MODULE-COMPLIANCE, OBJECT-GROUP |
| 477 |
FROM SNMPv2-CONF; |
| 478 |
|
| 479 |
|
| 480 |
snanauMIB MODULE-IDENTITY |
| 481 |
LAST-UPDATED "9402041800Z" |
| 482 |
ORGANIZATION "IETF SNA NAU MIB Working Group" |
| 483 |
CONTACT-INFO |
| 484 |
" Zbigniew Kielczewski |
| 485 |
Eicon Technology Inc. |
| 486 |
2196 32nd Avenue |
| 487 |
Lachine, Que H8T 3H7 |
| 488 |
Canada |
| 489 |
Tel: 1 514 631 2592 |
| 490 |
E-mail: [email protected] |
| 491 |
|
| 492 |
Deirdre Kostick |
| 493 |
Bell Communications Research |
| 494 |
Red Bank, NJ 07701 |
| 495 |
|
| 496 |
Tel: 1 908 758 2642 |
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Kielczewski, Kostick & Shih [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 503 |
|
| 504 |
|
| 505 |
E-mail: [email protected] |
| 506 |
|
| 507 |
Kitty Shih (editor) |
| 508 |
Novell |
| 509 |
890 Ross Drive |
| 510 |
Sunnyvale, CA 94089 |
| 511 |
Tel: 1 408 747 4305 |
| 512 |
E-mail: [email protected]" |
| 513 |
DESCRIPTION |
| 514 |
"This is the MIB module for objects used to |
| 515 |
manage SNA devices." |
| 516 |
::= { mib-2 34 } |
| 517 |
|
| 518 |
-- The SNANAU MIB module contains an objects part and a conformance part. |
| 519 |
-- Objects are organized into the following groups: |
| 520 |
-- (1)snaNode group, |
| 521 |
-- (2)snaLU group, |
| 522 |
-- (3)snaMgtTools group. |
| 523 |
|
| 524 |
snanauObjects OBJECT IDENTIFIER ::= { snanauMIB 1 } |
| 525 |
|
| 526 |
snaNode OBJECT IDENTIFIER ::= { snanauObjects 1 } |
| 527 |
snaLu OBJECT IDENTIFIER ::= { snanauObjects 2 } |
| 528 |
snaMgtTools OBJECT IDENTIFIER ::= { snanauObjects 3} |
| 529 |
|
| 530 |
|
| 531 |
-- *************************************************************** |
| 532 |
-- snaNode group |
| 533 |
-- |
| 534 |
-- It contains Managed Objects related to any type of Node and |
| 535 |
-- some specific objects for Node Type 2.0. |
| 536 |
-- *************************************************************** |
| 537 |
|
| 538 |
|
| 539 |
-- *************************************************************** |
| 540 |
-- The following table contains generic Node configuration |
| 541 |
-- parameters. |
| 542 |
-- *************************************************************** |
| 543 |
|
| 544 |
snaNodeAdminTable OBJECT-TYPE |
| 545 |
SYNTAX SEQUENCE OF SnaNodeAdminEntry |
| 546 |
MAX-ACCESS not-accessible |
| 547 |
STATUS current |
| 548 |
DESCRIPTION |
| 549 |
"This table contains objects which describe the |
| 550 |
configuration parameters for an SNA Node. Link |
| 551 |
specific configuration objects are contained in |
| 552 |
a separate MIB module (e.g., SNA DLC MIB) |
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Kielczewski, Kostick & Shih [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 559 |
|
| 560 |
|
| 561 |
corresponding to the link type. |
| 562 |
The table snaNodeAdminLinkTable contains objects |
| 563 |
which identify the relationship between node instances |
| 564 |
and link instances. |
| 565 |
|
| 566 |
The entries (i.e., rows) in this table can be created |
| 567 |
by either an Agent or a Management Station. |
| 568 |
The Management Station can do this through setting |
| 569 |
the appropriate value in the snaNodeAdminRowStatus. |
| 570 |
|
| 571 |
The snaNodeAdminRowStatus object describes the |
| 572 |
status of an entry and is used to change the status |
| 573 |
of an entry. The entry is deleted by an Agent based |
| 574 |
on the value of the snaNodeAdminRowStatus. |
| 575 |
|
| 576 |
The snaNodeAdminState object describes the desired |
| 577 |
operational state of a Node and is used to change the |
| 578 |
operational state of a Node. For example, such |
| 579 |
information may be obtained from a configuration file. |
| 580 |
|
| 581 |
How an Agent or a Management Station obtains the |
| 582 |
initial value of each object at creation time is an |
| 583 |
implementation specific issue. |
| 584 |
|
| 585 |
For each entry in this table, there is a corresponding |
| 586 |
entry in the snaNodeOperTable. |
| 587 |
While the objects in this table describe the desired |
| 588 |
or configured operational values of the SNA Node, the |
| 589 |
actual runtime values are contained in |
| 590 |
snaNodeOperTable." |
| 591 |
::= { snaNode 1 } |
| 592 |
|
| 593 |
snaNodeAdminEntry OBJECT-TYPE |
| 594 |
SYNTAX SnaNodeAdminEntry |
| 595 |
MAX-ACCESS not-accessible |
| 596 |
STATUS current |
| 597 |
DESCRIPTION |
| 598 |
"An entry contains the configuration parameters for |
| 599 |
one SNA Node instance. The objects in the entry |
| 600 |
have read-create access. |
| 601 |
An entry can be created, modified or deleted. The |
| 602 |
object snaNodeAdminRowStatus is used (i.e., set) to |
| 603 |
create or delete a row entry." |
| 604 |
INDEX { snaNodeAdminIndex } |
| 605 |
::= { snaNodeAdminTable 1 } |
| 606 |
|
| 607 |
SnaNodeAdminEntry ::= SEQUENCE { |
| 608 |
snaNodeAdminIndex |
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Kielczewski, Kostick & Shih [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 615 |
|
| 616 |
|
| 617 |
Integer32, |
| 618 |
snaNodeAdminName |
| 619 |
DisplayString, |
| 620 |
snaNodeAdminType |
| 621 |
INTEGER, |
| 622 |
snaNodeAdminXidFormat |
| 623 |
INTEGER, |
| 624 |
snaNodeAdminBlockNum |
| 625 |
DisplayString, |
| 626 |
snaNodeAdminIdNum |
| 627 |
DisplayString, |
| 628 |
snaNodeAdminEnablingMethod |
| 629 |
INTEGER, |
| 630 |
snaNodeAdminLuTermDefault |
| 631 |
INTEGER, |
| 632 |
snaNodeAdminMaxLu |
| 633 |
Integer32, |
| 634 |
snaNodeAdminHostDescription |
| 635 |
DisplayString, |
| 636 |
snaNodeAdminStopMethod |
| 637 |
INTEGER, |
| 638 |
snaNodeAdminState |
| 639 |
INTEGER, |
| 640 |
snaNodeAdminRowStatus |
| 641 |
RowStatus |
| 642 |
} |
| 643 |
|
| 644 |
snaNodeAdminIndex OBJECT-TYPE |
| 645 |
SYNTAX Integer32 |
| 646 |
MAX-ACCESS not-accessible |
| 647 |
STATUS current |
| 648 |
DESCRIPTION |
| 649 |
"Index used to uniquely identify each Node instance. |
| 650 |
If an Agent creates the entry, then it will assign |
| 651 |
this number otherwise a Management Station |
| 652 |
generates a random number when it reserves the |
| 653 |
entry for creation." |
| 654 |
::= { snaNodeAdminEntry 1 } |
| 655 |
|
| 656 |
snaNodeAdminName OBJECT-TYPE |
| 657 |
SYNTAX DisplayString (SIZE(0..17)) |
| 658 |
MAX-ACCESS read-create |
| 659 |
STATUS current |
| 660 |
DESCRIPTION |
| 661 |
"The value indicates the desired name of the |
| 662 |
Node for use during Node activation. |
| 663 |
In Type 2.1 networks, this is a fully-qualified name, |
| 664 |
meaning that the Node name is preceded by the NetId (if |
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Kielczewski, Kostick & Shih [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 671 |
|
| 672 |
|
| 673 |
present) with a period as the delimiter. |
| 674 |
|
| 675 |
A write operation to this object will |
| 676 |
not change the operational value reflected |
| 677 |
in snaNodeOperName until the Node has |
| 678 |
been re-activated (e.g., after the next initialization |
| 679 |
of the SNA services)." |
| 680 |
::= { snaNodeAdminEntry 2 } |
| 681 |
|
| 682 |
snaNodeAdminType OBJECT-TYPE |
| 683 |
SYNTAX INTEGER { |
| 684 |
other(1), |
| 685 |
pu10(2), |
| 686 |
pu20(3), |
| 687 |
t21len(4), |
| 688 |
endNode(5), |
| 689 |
networkNode(6) |
| 690 |
} |
| 691 |
MAX-ACCESS read-create |
| 692 |
STATUS current |
| 693 |
DESCRIPTION |
| 694 |
"The value indicates the type of SNA Node. |
| 695 |
|
| 696 |
A write operation to this object will |
| 697 |
not change the operational value reflected |
| 698 |
in snaNodeOperType until the Node has |
| 699 |
been re-activated (e.g., after the next initialization |
| 700 |
of the SNA services)." |
| 701 |
::= { snaNodeAdminEntry 3 } |
| 702 |
|
| 703 |
snaNodeAdminXidFormat OBJECT-TYPE |
| 704 |
SYNTAX INTEGER { |
| 705 |
format0(1), |
| 706 |
format1(2), |
| 707 |
format3(3) |
| 708 |
} |
| 709 |
MAX-ACCESS read-create |
| 710 |
STATUS current |
| 711 |
DESCRIPTION |
| 712 |
"The value indicates the type of XID format used for |
| 713 |
this Node. |
| 714 |
Note that there is no format type 2. |
| 715 |
|
| 716 |
A write operation to this object will |
| 717 |
not change the operational value reflected |
| 718 |
in snaNodeOperAdminXidFormat until the Node has |
| 719 |
been re-activated (e.g., after the next initialization |
| 720 |
of the SNA services)." |
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Kielczewski, Kostick & Shih [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 727 |
|
| 728 |
|
| 729 |
::= { snaNodeAdminEntry 4 } |
| 730 |
|
| 731 |
snaNodeAdminBlockNum OBJECT-TYPE |
| 732 |
SYNTAX DisplayString (SIZE(3)) |
| 733 |
MAX-ACCESS read-create |
| 734 |
STATUS current |
| 735 |
DESCRIPTION |
| 736 |
"The value indicates the block number for this Node |
| 737 |
instance. It is the first 3 hexadecimal digits of the |
| 738 |
SNA Node id. |
| 739 |
|
| 740 |
A write operation to this object will |
| 741 |
not change the operational value reflected |
| 742 |
in snaNodeOperBlockNum until the Node has |
| 743 |
been re-activated (e.g., after the next initialization |
| 744 |
of the SNA services)." |
| 745 |
::= { snaNodeAdminEntry 5 } |
| 746 |
|
| 747 |
snaNodeAdminIdNum OBJECT-TYPE |
| 748 |
SYNTAX DisplayString (SIZE(5)) |
| 749 |
MAX-ACCESS read-create |
| 750 |
STATUS current |
| 751 |
DESCRIPTION |
| 752 |
"The value indicates the ID number for this Node |
| 753 |
instance. This is the last 5 hexadecimal digits of |
| 754 |
the SNA Node id. |
| 755 |
|
| 756 |
A write operation to this object will |
| 757 |
not change the operational value reflected |
| 758 |
in snaNodeOperIdNum until the Node has |
| 759 |
been re-activated (e.g., after the next initialization |
| 760 |
of the SNA services)." |
| 761 |
::= { snaNodeAdminEntry 6 } |
| 762 |
|
| 763 |
snaNodeAdminEnablingMethod OBJECT-TYPE |
| 764 |
SYNTAX INTEGER { |
| 765 |
other (1), |
| 766 |
startup (2), |
| 767 |
demand (3), |
| 768 |
onlyMS (4) |
| 769 |
} |
| 770 |
MAX-ACCESS read-create |
| 771 |
STATUS current |
| 772 |
DESCRIPTION |
| 773 |
"The value indicates how the Node should be |
| 774 |
activated for the first time. |
| 775 |
The values have the following meanings: |
| 776 |
|
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Kielczewski, Kostick & Shih [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 783 |
|
| 784 |
|
| 785 |
other (1) - may be used for proprietary methods |
| 786 |
not listed in this enumeration, |
| 787 |
startup (2) - at SNA services' initialization time |
| 788 |
(this is the default), |
| 789 |
demand (3) - only when LU is requested by application, |
| 790 |
or |
| 791 |
onlyMS (4) - by a Management Station only. |
| 792 |
|
| 793 |
A write operation to this object may immediately |
| 794 |
change the operational value reflected |
| 795 |
in snaNodeOperEnablingMethod depending |
| 796 |
on the Agent implementation. If the Agent |
| 797 |
implementation accepts immediate changes, then the |
| 798 |
behavior of the Node changes immediately and not only |
| 799 |
after the next system startup of the SNA services. |
| 800 |
An immediate change may only apply when the |
| 801 |
current value `demand (3)' is changed to `onlyMS (4)' |
| 802 |
and vice versa." |
| 803 |
::= { snaNodeAdminEntry 7 } |
| 804 |
|
| 805 |
snaNodeAdminLuTermDefault OBJECT-TYPE |
| 806 |
SYNTAX INTEGER { |
| 807 |
unbind (1), |
| 808 |
termself (2), |
| 809 |
rshutd (3), |
| 810 |
poweroff(4) |
| 811 |
} |
| 812 |
MAX-ACCESS read-create |
| 813 |
STATUS current |
| 814 |
DESCRIPTION |
| 815 |
"The value indicates the desired default method |
| 816 |
used to deactivate LUs for this Node |
| 817 |
For LU6.2s, `unbind(1)' is the only valid value. |
| 818 |
|
| 819 |
unbind(1) - terminate the LU-LU session by sending |
| 820 |
an SNA UNBIND request. |
| 821 |
termself(2) - terminate the LU-LU session by sending |
| 822 |
an SNA TERM-SELF (Terminate Self) request on |
| 823 |
the SSCP-LU session. The SSCP will inform the |
| 824 |
remote session LU partner to send an UNBIND |
| 825 |
request to terminate the session. |
| 826 |
rshutd(3) - terminate the LU-LU session by sending |
| 827 |
an SNA RSHUTD (Request ShutDown) request to |
| 828 |
the remote session LU partner. The remote LU |
| 829 |
will then send an UNBIND request to terminate |
| 830 |
the session. |
| 831 |
poweroff(4) - terminate the LU-LU session by sending |
| 832 |
either an SNA LUSTAT (LU Status) request on |
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Kielczewski, Kostick & Shih [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 839 |
|
| 840 |
|
| 841 |
the LU-LU session or an SNA NOTIFY request on |
| 842 |
the SSCP-LU session indicating that the LU has |
| 843 |
been powered off. Sending both is also |
| 844 |
acceptable. The result should be that the |
| 845 |
remote session LU partner will send an UNBIND |
| 846 |
to terminate the session. |
| 847 |
|
| 848 |
The default behavior indicated by the value of this |
| 849 |
object may be overridden for an LU instance. The |
| 850 |
override is performed by setting the snaLuAdminTerm |
| 851 |
object instance in the snaLuAdminTable to the desired |
| 852 |
value. |
| 853 |
|
| 854 |
A write operation to this object may immediately |
| 855 |
change the operational value reflected |
| 856 |
in snaNodeOperLuTermDefault depending |
| 857 |
on the Agent implementation." |
| 858 |
::= { snaNodeAdminEntry 8 } |
| 859 |
|
| 860 |
snaNodeAdminMaxLu OBJECT-TYPE |
| 861 |
SYNTAX Integer32 |
| 862 |
MAX-ACCESS read-create |
| 863 |
STATUS current |
| 864 |
DESCRIPTION |
| 865 |
"The maximum number of LUs that may be |
| 866 |
activated for this Node. For PU2.1, this object |
| 867 |
refers to the number of dependent LUs. |
| 868 |
|
| 869 |
A write operation to this object will |
| 870 |
not change the operational value reflected |
| 871 |
in snaNodeOperMaxLu until the Node has |
| 872 |
been re-activated (e.g., after the next initialization |
| 873 |
of the SNA services)." |
| 874 |
::= { snaNodeAdminEntry 9 } |
| 875 |
|
| 876 |
snaNodeAdminHostDescription OBJECT-TYPE |
| 877 |
SYNTAX DisplayString (SIZE(0..128)) |
| 878 |
MAX-ACCESS read-create |
| 879 |
STATUS current |
| 880 |
DESCRIPTION |
| 881 |
"The value identifies the remote host associated |
| 882 |
with this Node. Since SSCP Id's may not be unique |
| 883 |
across hosts, the host description |
| 884 |
is required to uniquely identify the SSCP. |
| 885 |
This object is only applicable to PU2.0 type |
| 886 |
Nodes. If the remote host is unknown, then the |
| 887 |
value is the null string. |
| 888 |
|
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Kielczewski, Kostick & Shih [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 895 |
|
| 896 |
|
| 897 |
A write operation to this object may immediately |
| 898 |
change the operational value reflected |
| 899 |
in snaNodeOperHostDescription depending |
| 900 |
on the Agent implementation." |
| 901 |
::= { snaNodeAdminEntry 10 } |
| 902 |
|
| 903 |
snaNodeAdminStopMethod OBJECT-TYPE |
| 904 |
SYNTAX INTEGER { |
| 905 |
other (1), |
| 906 |
normal (2), |
| 907 |
immed (3), |
| 908 |
force (4) |
| 909 |
} |
| 910 |
MAX-ACCESS read-create |
| 911 |
STATUS current |
| 912 |
DESCRIPTION |
| 913 |
"The value indicates the desired method to be used |
| 914 |
by the Agent to stop a Node (i.e., change the Node's |
| 915 |
operational state to inactive(1) ). |
| 916 |
|
| 917 |
The values have the following meaning: |
| 918 |
|
| 919 |
other (1) - used for proprietary |
| 920 |
methods not listed in this enumeration. |
| 921 |
normal(2) - deactivate only when there is no more |
| 922 |
activity on this Node (i.e., all data flows |
| 923 |
have been completed and all sessions |
| 924 |
have been terminated). |
| 925 |
immed(3) - deactivate immediately regardless of |
| 926 |
current activities on this Node. Wait for |
| 927 |
deactivation responses (from remote Node) |
| 928 |
before changing the Node state to inactive. |
| 929 |
force(4) - deactivate immediately regardless of |
| 930 |
current activities on this Node. Do not wait |
| 931 |
for deactivation responses (from remote Node) |
| 932 |
before changing the Node state to inactive. |
| 933 |
|
| 934 |
A write operation to this object may immediately |
| 935 |
change the operational value reflected |
| 936 |
in snaNodeOperStopMethod depending |
| 937 |
on the Agent implementation." |
| 938 |
::= { snaNodeAdminEntry 11 } |
| 939 |
|
| 940 |
snaNodeAdminState OBJECT-TYPE |
| 941 |
SYNTAX INTEGER { |
| 942 |
inactive (1), |
| 943 |
active (2) |
| 944 |
} |
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">Kielczewski, Kostick & Shih [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 951 |
|
| 952 |
|
| 953 |
MAX-ACCESS read-create |
| 954 |
STATUS current |
| 955 |
DESCRIPTION |
| 956 |
"The value indicates the desired operational |
| 957 |
state of the SNA Node. This object is used |
| 958 |
by the Management Station to |
| 959 |
activate or deactivate the Node. |
| 960 |
|
| 961 |
If the current value in snaNodeOperState is |
| 962 |
`active (2)', then setting this object to |
| 963 |
`inactive (1)' will initiate the Node shutdown |
| 964 |
process using the method indicated |
| 965 |
by snaNodeOperStopMethod. |
| 966 |
|
| 967 |
If the current value in snaNodeOperState is |
| 968 |
`inactive (1)', then setting this object to |
| 969 |
`active (2)' will initiate the |
| 970 |
Node's activation. |
| 971 |
|
| 972 |
A Management Station can always set this object to |
| 973 |
`active (2)' irrespective of the value in the |
| 974 |
snaOperEnablingMethod." |
| 975 |
::= { snaNodeAdminEntry 12 } |
| 976 |
|
| 977 |
snaNodeAdminRowStatus OBJECT-TYPE |
| 978 |
SYNTAX RowStatus |
| 979 |
MAX-ACCESS read-create |
| 980 |
STATUS current |
| 981 |
DESCRIPTION |
| 982 |
"This object is used by a Management Station to |
| 983 |
create or delete the row entry in the |
| 984 |
snaNodeAdminTable following |
| 985 |
the RowStatus textual convention. |
| 986 |
|
| 987 |
Upon successful creation of |
| 988 |
the row, an Agent automatically creates a |
| 989 |
corresponding entry in the snaNodeOperTable with |
| 990 |
snaNodeOperState equal to `inactive (1)'. |
| 991 |
|
| 992 |
Row deletion can be Management Station or Agent |
| 993 |
initiated: |
| 994 |
(a) The Management Station can set the value to |
| 995 |
`destroy (6)' only when the value of |
| 996 |
snaNodeOperState of this Node instance is |
| 997 |
`inactive (1)'. The Agent will then delete the rows |
| 998 |
corresponding to this Node instance from the |
| 999 |
snaNodeAdminTable and the snaNodeOperTable. |
| 1000 |
(b) The Agent detects that a row is in the |
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">Kielczewski, Kostick & Shih [Page 18]</span></pre> |
| 1005 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1006 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
`notReady (3)' state for greater than a |
| 1010 |
default period of 5 minutes. |
| 1011 |
(c) All rows with the snaNodeAdminRowStatus object's |
| 1012 |
value of `notReady (3)' will be removed upon the |
| 1013 |
next initialization of the SNA services." |
| 1014 |
::= { snaNodeAdminEntry 13 } |
| 1015 |
|
| 1016 |
|
| 1017 |
-- *************************************************************** |
| 1018 |
-- The following object is updated when there is a change to |
| 1019 |
-- the value of any object in the snaNodeAdminTable. |
| 1020 |
-- *************************************************************** |
| 1021 |
|
| 1022 |
snaNodeAdminTableLastChange OBJECT-TYPE |
| 1023 |
SYNTAX TimeStamp |
| 1024 |
MAX-ACCESS read-only |
| 1025 |
STATUS current |
| 1026 |
DESCRIPTION |
| 1027 |
"The value indicates the timestamp |
| 1028 |
(e.g., the Agent's sysUpTime value) of the last |
| 1029 |
change made to any object in the snaNodeAdminTable, |
| 1030 |
including row deletions/additions (e.g., changes to |
| 1031 |
snaNodeAdminRowStatus values). |
| 1032 |
|
| 1033 |
This object can be used to reduce frequent |
| 1034 |
retrievals of the snaNodeAdminTable by a Management |
| 1035 |
Station. It is expected that a Management Station |
| 1036 |
will periodically poll this object and compare its |
| 1037 |
current value with the previous one. A difference |
| 1038 |
indicates that some Node configuration information |
| 1039 |
has been changed. Only then will the Management |
| 1040 |
Station retrieve the entire table." |
| 1041 |
::= { snaNode 2 } |
| 1042 |
|
| 1043 |
|
| 1044 |
-- *************************************************************** |
| 1045 |
-- The following table contains Node operational parameters. |
| 1046 |
-- *************************************************************** |
| 1047 |
|
| 1048 |
snaNodeOperTable OBJECT-TYPE |
| 1049 |
SYNTAX SEQUENCE OF SnaNodeOperEntry |
| 1050 |
MAX-ACCESS not-accessible |
| 1051 |
STATUS current |
| 1052 |
DESCRIPTION |
| 1053 |
"This table contains the dynamic parameters which |
| 1054 |
have read-only access. These objects reflect the |
| 1055 |
actual status of the Node. The entries in this |
| 1056 |
table cannot be created or modified by a |
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
<span class="grey">Kielczewski, Kostick & Shih [Page 19]</span></pre> |
| 1061 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1062 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
Management Station. |
| 1066 |
This table augments the snaNodeAdminTable." |
| 1067 |
::= { snaNode 3 } |
| 1068 |
|
| 1069 |
snaNodeOperEntry OBJECT-TYPE |
| 1070 |
SYNTAX SnaNodeOperEntry |
| 1071 |
MAX-ACCESS not-accessible |
| 1072 |
STATUS current |
| 1073 |
DESCRIPTION |
| 1074 |
"The entry contains parameters which describe the |
| 1075 |
state of one Node. The entries are created by the |
| 1076 |
Agent. They have read-only access." |
| 1077 |
AUGMENTS { snaNodeAdminEntry } |
| 1078 |
::= { snaNodeOperTable 1 } |
| 1079 |
|
| 1080 |
SnaNodeOperEntry ::= SEQUENCE { |
| 1081 |
snaNodeOperName |
| 1082 |
DisplayString, |
| 1083 |
snaNodeOperType |
| 1084 |
INTEGER, |
| 1085 |
snaNodeOperXidFormat |
| 1086 |
INTEGER, |
| 1087 |
snaNodeOperBlockNum |
| 1088 |
DisplayString, |
| 1089 |
snaNodeOperIdNum |
| 1090 |
DisplayString, |
| 1091 |
snaNodeOperEnablingMethod |
| 1092 |
INTEGER, |
| 1093 |
snaNodeOperLuTermDefault |
| 1094 |
INTEGER, |
| 1095 |
snaNodeOperMaxLu |
| 1096 |
Integer32, |
| 1097 |
snaNodeOperHostDescription |
| 1098 |
DisplayString, |
| 1099 |
snaNodeOperStopMethod |
| 1100 |
INTEGER, |
| 1101 |
snaNodeOperState |
| 1102 |
INTEGER, |
| 1103 |
snaNodeOperHostSscpId |
| 1104 |
OCTET STRING, |
| 1105 |
snaNodeOperStartTime |
| 1106 |
TimeStamp, |
| 1107 |
snaNodeOperLastStateChange |
| 1108 |
TimeStamp, |
| 1109 |
snaNodeOperActFailures |
| 1110 |
Counter32, |
| 1111 |
snaNodeOperActFailureReason |
| 1112 |
INTEGER |
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
<span class="grey">Kielczewski, Kostick & Shih [Page 20]</span></pre> |
| 1117 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span> |
| 1118 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 1119 |
|
| 1120 |
|
| 1121 |
} |
| 1122 |
|
| 1123 |
snaNodeOperName OBJECT-TYPE |
| 1124 |
SYNTAX DisplayString (SIZE(0..17)) |
| 1125 |
MAX-ACCESS read-only |
| 1126 |
STATUS current |
| 1127 |
DESCRIPTION |
| 1128 |
"The value identifies the current name of the Node. |
| 1129 |
In Type 2.1 networks, this |
| 1130 |
is a fully-qualified name, meaning that the Node name |
| 1131 |
is preceded by the NetId (if present) with a period |
| 1132 |
as the delimiter." |
| 1133 |
::= { snaNodeOperEntry 1 } |
| 1134 |
|
| 1135 |
snaNodeOperType OBJECT-TYPE |
| 1136 |
SYNTAX INTEGER { |
| 1137 |
other(1), |
| 1138 |
pu10(2), |
| 1139 |
pu20(3), |
| 1140 |
t21LEN(4), |
| 1141 |
endNode(5), |
| 1142 |
networkNode(6) |
| 1143 |
} |
| 1144 |
MAX-ACCESS read-only |
| 1145 |
STATUS current |
| 1146 |
DESCRIPTION |
| 1147 |
"The value identifies the current type of the Node." |
| 1148 |
::= { snaNodeOperEntry 2 } |
| 1149 |
|
| 1150 |
snaNodeOperXidFormat OBJECT-TYPE |
| 1151 |
SYNTAX INTEGER { |
| 1152 |
format0 (1), |
| 1153 |
format1 (2), |
| 1154 |
format3 (3) |
| 1155 |
} |
| 1156 |
MAX-ACCESS read-only |
| 1157 |
STATUS current |
| 1158 |
DESCRIPTION |
| 1159 |
"The value identifies the type of XID format currently |
| 1160 |
used for this Node. |
| 1161 |
Note that there is no format type 2." |
| 1162 |
::= { snaNodeOperEntry 3 } |
| 1163 |
|
| 1164 |
snaNodeOperBlockNum OBJECT-TYPE |
| 1165 |
SYNTAX DisplayString (SIZE(3)) |
| 1166 |
MAX-ACCESS read-only |
| 1167 |
STATUS current |
| 1168 |
DESCRIPTION |
| 1169 |
|
| 1170 |
|
| 1171 |
|
| 1172 |
<span class="grey">Kielczewski, Kostick & Shih [Page 21]</span></pre> |
| 1173 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span> |
| 1174 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 1175 |
|
| 1176 |
|
| 1177 |
"The value identifies the block number for this Node |
| 1178 |
instance. It is the first 3 hexadecimal digits |
| 1179 |
of the SNA Node id." |
| 1180 |
::= { snaNodeOperEntry 4 } |
| 1181 |
|
| 1182 |
snaNodeOperIdNum OBJECT-TYPE |
| 1183 |
SYNTAX DisplayString (SIZE(5)) |
| 1184 |
MAX-ACCESS read-only |
| 1185 |
STATUS current |
| 1186 |
DESCRIPTION |
| 1187 |
"The value identifies the ID number for this Node |
| 1188 |
instance. This is the last 5 hexadecimal digits of |
| 1189 |
the SNA Node id." |
| 1190 |
::= { snaNodeOperEntry 5 } |
| 1191 |
|
| 1192 |
|
| 1193 |
snaNodeOperEnablingMethod OBJECT-TYPE |
| 1194 |
SYNTAX INTEGER { |
| 1195 |
other (1), |
| 1196 |
startup (2), |
| 1197 |
demand (3), |
| 1198 |
onlyMS (4) |
| 1199 |
} |
| 1200 |
MAX-ACCESS read-only |
| 1201 |
STATUS current |
| 1202 |
DESCRIPTION |
| 1203 |
"The value indicates how the Node is activated for |
| 1204 |
the first time. |
| 1205 |
The values have the following meanings: |
| 1206 |
other (1) - not at boot time, LU activation |
| 1207 |
or by a Management Station; |
| 1208 |
startup (2) - at SNA services' initialization |
| 1209 |
time (this is the default), |
| 1210 |
demand (3) - only when LU is requested by |
| 1211 |
application, |
| 1212 |
onlyMS (4) - by a network Management Station |
| 1213 |
only." |
| 1214 |
::= { snaNodeOperEntry 6 } |
| 1215 |
|
| 1216 |
snaNodeOperLuTermDefault OBJECT-TYPE |
| 1217 |
SYNTAX INTEGER { |
| 1218 |
unbind (1), |
| 1219 |
termself (2), |
| 1220 |
rshutd (3), |
| 1221 |
poweroff (4) |
| 1222 |
} |
| 1223 |
MAX-ACCESS read-only |
| 1224 |
STATUS current |
| 1225 |
|
| 1226 |
|
| 1227 |
|
| 1228 |
<span class="grey">Kielczewski, Kostick & Shih [Page 22]</span></pre> |
| 1229 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span> |
| 1230 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 1231 |
|
| 1232 |
|
| 1233 |
DESCRIPTION |
| 1234 |
"The value identifies the default method used to |
| 1235 |
deactivate LUs for this Node. |
| 1236 |
|
| 1237 |
For LU6.2s, 'unbind(1)' is the only valid value. |
| 1238 |
|
| 1239 |
unbind(1) - terminate the LU-LU session by sending |
| 1240 |
an SNA UNBIND request. |
| 1241 |
termself(2) - terminate the LU-LU session by sending |
| 1242 |
an SNA TERM-SELF (Terminate Self) request on |
| 1243 |
the SSCP-LU session. The SSCP will inform the |
| 1244 |
remote session LU partner to send an UNBIND |
| 1245 |
request to terminate the session. |
| 1246 |
rshutd(3) - terminate the LU-LU session by sending |
| 1247 |
an SNA RSHUTD (Request ShutDown) request to |
| 1248 |
the remote session LU partner. The remote LU |
| 1249 |
will then send an UNBIND request to terminate |
| 1250 |
the session. |
| 1251 |
poweroff(4) - terminate the LU-LU session by sending |
| 1252 |
either an SNA LUSTAT (LU Status) request on |
| 1253 |
the LU-LU session or an SNA NOTIFY request on |
| 1254 |
the SSCP-LU session indicating that the LU has |
| 1255 |
been powered off. Sending both is also |
| 1256 |
acceptable. The result should be that the |
| 1257 |
remote session LU partner will send an UNBIND |
| 1258 |
to terminate the session. |
| 1259 |
|
| 1260 |
This object describes the default behavior for this Node; |
| 1261 |
however, it is possible that for a specific LU the |
| 1262 |
behavior indicated by the snaLuOperTerm object is |
| 1263 |
different." |
| 1264 |
::= { snaNodeOperEntry 7 } |
| 1265 |
|
| 1266 |
snaNodeOperMaxLu OBJECT-TYPE |
| 1267 |
SYNTAX Integer32 |
| 1268 |
MAX-ACCESS read-only |
| 1269 |
STATUS current |
| 1270 |
DESCRIPTION |
| 1271 |
"This value identifies the current, maximum number |
| 1272 |
of LUs that are activated for this Node. For PU2.1, |
| 1273 |
this object refers to the number of dependent LUs." |
| 1274 |
::= { snaNodeOperEntry 8 } |
| 1275 |
|
| 1276 |
snaNodeOperHostDescription OBJECT-TYPE |
| 1277 |
SYNTAX DisplayString (SIZE(0..128)) |
| 1278 |
MAX-ACCESS read-only |
| 1279 |
STATUS current |
| 1280 |
DESCRIPTION |
| 1281 |
|
| 1282 |
|
| 1283 |
|
| 1284 |
<span class="grey">Kielczewski, Kostick & Shih [Page 23]</span></pre> |
| 1285 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span> |
| 1286 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 1287 |
|
| 1288 |
|
| 1289 |
"This value identifies the remote host currently |
| 1290 |
associated with this Node. |
| 1291 |
Since SSCP Id's may not be unique |
| 1292 |
across hosts, the host description |
| 1293 |
is required to uniquely identify the SSCP." |
| 1294 |
::= { snaNodeOperEntry 9 } |
| 1295 |
|
| 1296 |
snaNodeOperStopMethod OBJECT-TYPE |
| 1297 |
SYNTAX INTEGER { |
| 1298 |
other (1), |
| 1299 |
normal (2), |
| 1300 |
immed (3), |
| 1301 |
force (4) |
| 1302 |
} |
| 1303 |
MAX-ACCESS read-only |
| 1304 |
STATUS current |
| 1305 |
DESCRIPTION |
| 1306 |
"This value identifies the current Node shutdown |
| 1307 |
method to be used by the Agent to stop the Node. |
| 1308 |
When the Agent changes the Node's state to 'inactive |
| 1309 |
(1)', the Agent must use the shutdown method |
| 1310 |
indicated by this object. |
| 1311 |
|
| 1312 |
The values have the following meaning: |
| 1313 |
|
| 1314 |
other (1) - proprietary method not listed in this |
| 1315 |
enumeration |
| 1316 |
normal(2) - deactivate only when there is no more |
| 1317 |
activity on this Node (i.e., all data flows |
| 1318 |
have been completed and all sessions have |
| 1319 |
been terminated). |
| 1320 |
immed(3) - deactivate immediately regardless of |
| 1321 |
current activities on this Node. Wait for |
| 1322 |
deactivation responses (from remote Node) |
| 1323 |
before changing the Node state to inactive. |
| 1324 |
force(4) - deactivate immediately regardless of |
| 1325 |
current activities on this Node. Do not wait |
| 1326 |
for deactivation responses (from remote Node) |
| 1327 |
before changing the Node state to inactive. |
| 1328 |
|
| 1329 |
Note that a write operation to |
| 1330 |
snaNodeAdminOperStopMethod may immediately change |
| 1331 |
the value of snaNodeOperStopMethod depending on |
| 1332 |
the Agent implementation." |
| 1333 |
::= { snaNodeOperEntry 10 } |
| 1334 |
|
| 1335 |
snaNodeOperState OBJECT-TYPE |
| 1336 |
SYNTAX INTEGER { |
| 1337 |
|
| 1338 |
|
| 1339 |
|
| 1340 |
<span class="grey">Kielczewski, Kostick & Shih [Page 24]</span></pre> |
| 1341 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span> |
| 1342 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 1343 |
|
| 1344 |
|
| 1345 |
inactive (1), |
| 1346 |
active (2), |
| 1347 |
waiting (3), |
| 1348 |
stopping (4) |
| 1349 |
} |
| 1350 |
MAX-ACCESS read-only |
| 1351 |
STATUS current |
| 1352 |
DESCRIPTION |
| 1353 |
"The current state of the Node. |
| 1354 |
The values have the following meanings: |
| 1355 |
inactive (1), a row representing the Node has |
| 1356 |
been created in the AdminTable |
| 1357 |
and, the Node is ready for activation -or- |
| 1358 |
an active Node has been stopped -or- |
| 1359 |
a waiting Node has returned to the inactive |
| 1360 |
state. |
| 1361 |
waiting (3), a request to have the Node activated |
| 1362 |
has been issued, and the Node is pending |
| 1363 |
activation. |
| 1364 |
active (2), the Node is ready and operating. |
| 1365 |
stopping (4), the request to stop the Node has |
| 1366 |
been issued while the StopMethod normal |
| 1367 |
or immediate is used." |
| 1368 |
::= { snaNodeOperEntry 11 } |
| 1369 |
|
| 1370 |
snaNodeOperHostSscpId OBJECT-TYPE |
| 1371 |
SYNTAX OCTET STRING (SIZE(0..6)) |
| 1372 |
MAX-ACCESS read-only |
| 1373 |
STATUS current |
| 1374 |
DESCRIPTION |
| 1375 |
"This value identifies the current SSCP Id |
| 1376 |
associated with the Node. This object is only |
| 1377 |
applicable to PU 2.0s. If the Node |
| 1378 |
is not a PU 2.0 type, then this object contains a |
| 1379 |
zero length string." |
| 1380 |
::= { snaNodeOperEntry 12 } |
| 1381 |
|
| 1382 |
snaNodeOperStartTime OBJECT-TYPE |
| 1383 |
SYNTAX TimeStamp |
| 1384 |
MAX-ACCESS read-only |
| 1385 |
STATUS current |
| 1386 |
DESCRIPTION |
| 1387 |
"The timestamp (e.g, the Agent's sysUpTime value) |
| 1388 |
at the Node activation." |
| 1389 |
::= { snaNodeOperEntry 13 } |
| 1390 |
|
| 1391 |
snaNodeOperLastStateChange OBJECT-TYPE |
| 1392 |
SYNTAX TimeStamp |
| 1393 |
|
| 1394 |
|
| 1395 |
|
| 1396 |
<span class="grey">Kielczewski, Kostick & Shih [Page 25]</span></pre> |
| 1397 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span> |
| 1398 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 1399 |
|
| 1400 |
|
| 1401 |
MAX-ACCESS read-only |
| 1402 |
STATUS current |
| 1403 |
DESCRIPTION |
| 1404 |
"The timestamp (e.g., the Agent's sysUpTime value) |
| 1405 |
at the last state change of the Node." |
| 1406 |
::= { snaNodeOperEntry 14 } |
| 1407 |
|
| 1408 |
snaNodeOperActFailures OBJECT-TYPE |
| 1409 |
SYNTAX Counter32 |
| 1410 |
MAX-ACCESS read-only |
| 1411 |
STATUS current |
| 1412 |
DESCRIPTION |
| 1413 |
"This value identifies the number of failed Node |
| 1414 |
activation attempts." |
| 1415 |
::= { snaNodeOperEntry 15 } |
| 1416 |
|
| 1417 |
snaNodeOperActFailureReason OBJECT-TYPE |
| 1418 |
SYNTAX INTEGER { |
| 1419 |
other (1), |
| 1420 |
linkFailure (2), |
| 1421 |
noResources (3), |
| 1422 |
badConfiguration (4), |
| 1423 |
internalError (5) |
| 1424 |
} |
| 1425 |
MAX-ACCESS read-only |
| 1426 |
STATUS current |
| 1427 |
DESCRIPTION |
| 1428 |
"The value indicates the reason for the activation |
| 1429 |
failure. The value `other (1)' indicates a reason |
| 1430 |
not listed in the enumeration. This object |
| 1431 |
will be sent in the trap snaNodeActFailTrap." |
| 1432 |
::= { snaNodeOperEntry 16 } |
| 1433 |
|
| 1434 |
|
| 1435 |
|
| 1436 |
-- *************************************************************** |
| 1437 |
-- The following object is updated when there is a change to |
| 1438 |
-- the value of snaNodeOperState in any row or a row is |
| 1439 |
-- added/deleted from the snaNodeOperTable via the snaNodeAdminTable. |
| 1440 |
-- *************************************************************** |
| 1441 |
|
| 1442 |
snaNodeOperTableLastChange OBJECT-TYPE |
| 1443 |
SYNTAX TimeStamp |
| 1444 |
MAX-ACCESS read-only |
| 1445 |
STATUS current |
| 1446 |
DESCRIPTION |
| 1447 |
"The timestamp (e.g., the Agent's sysUpTime value) |
| 1448 |
at the last change made to any object in the |
| 1449 |
|
| 1450 |
|
| 1451 |
|
| 1452 |
<span class="grey">Kielczewski, Kostick & Shih [Page 26]</span></pre> |
| 1453 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span> |
| 1454 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 1455 |
|
| 1456 |
|
| 1457 |
snaNodeOperTable, including row deletions/additions |
| 1458 |
made as a result of changes to the |
| 1459 |
snaNodeAdminRowStatus object. |
| 1460 |
|
| 1461 |
This object can be used to reduce frequent |
| 1462 |
retrievals of the snaNodeOperTable by a Management |
| 1463 |
Station. It is expected that a Management Station |
| 1464 |
will periodically poll this object and compare its |
| 1465 |
current value with the previous one. A difference |
| 1466 |
indicates that some Node operational information |
| 1467 |
has been changed. Only then will the Management |
| 1468 |
Station retrieve the entire table." |
| 1469 |
::= { snaNode 4 } |
| 1470 |
|
| 1471 |
|
| 1472 |
-- *************************************************************** |
| 1473 |
-- The following table contains PU 2.0 statistics dynamic parameters. |
| 1474 |
-- *************************************************************** |
| 1475 |
|
| 1476 |
snaPu20StatsTable OBJECT-TYPE |
| 1477 |
SYNTAX SEQUENCE OF SnaPu20StatsEntry |
| 1478 |
MAX-ACCESS not-accessible |
| 1479 |
STATUS current |
| 1480 |
DESCRIPTION |
| 1481 |
"This table contains the dynamic parameters which |
| 1482 |
have read-only access. The entries in this table |
| 1483 |
correspond to PU 2.0 entries in the snaNodeOperTable |
| 1484 |
and cannot be created by a Management Station." |
| 1485 |
::= { snaNode 5 } |
| 1486 |
|
| 1487 |
snaPu20StatsEntry OBJECT-TYPE |
| 1488 |
SYNTAX SnaPu20StatsEntry |
| 1489 |
MAX-ACCESS not-accessible |
| 1490 |
STATUS current |
| 1491 |
DESCRIPTION |
| 1492 |
"The entry contains parameters which describe the |
| 1493 |
statistics for one PU 2.0. They have read-only |
| 1494 |
access. |
| 1495 |
The counters represent traffic for all kinds |
| 1496 |
of sessions: LU-LU, SSCP-PU, SSCP-LU. |
| 1497 |
|
| 1498 |
Each Node of PU Type 2.0 from the snaNodeAdminTable |
| 1499 |
has one entry in this table and the index used |
| 1500 |
here has the same value as snaNodeAdminIndex of |
| 1501 |
that PU. The entry is created by the Agent." |
| 1502 |
INDEX { snaNodeAdminIndex } |
| 1503 |
::= { snaPu20StatsTable 1 } |
| 1504 |
|
| 1505 |
|
| 1506 |
|
| 1507 |
|
| 1508 |
<span class="grey">Kielczewski, Kostick & Shih [Page 27]</span></pre> |
| 1509 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span> |
| 1510 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 1511 |
|
| 1512 |
|
| 1513 |
SnaPu20StatsEntry ::= SEQUENCE { |
| 1514 |
snaPu20StatsSentBytes |
| 1515 |
Counter32, |
| 1516 |
snaPu20StatsReceivedBytes |
| 1517 |
Counter32, |
| 1518 |
snaPu20StatsSentPius |
| 1519 |
Counter32, |
| 1520 |
snaPu20StatsReceivedPius |
| 1521 |
Counter32, |
| 1522 |
snaPu20StatsSentNegativeResps |
| 1523 |
Counter32, |
| 1524 |
snaPu20StatsReceivedNegativeResps |
| 1525 |
Counter32, |
| 1526 |
snaPu20StatsActLus |
| 1527 |
Gauge32, |
| 1528 |
snaPu20StatsInActLus |
| 1529 |
Gauge32, |
| 1530 |
snaPu20StatsBindLus |
| 1531 |
Gauge32 |
| 1532 |
} |
| 1533 |
|
| 1534 |
snaPu20StatsSentBytes OBJECT-TYPE |
| 1535 |
SYNTAX Counter32 |
| 1536 |
MAX-ACCESS read-only |
| 1537 |
STATUS current |
| 1538 |
DESCRIPTION |
| 1539 |
"The number of bytes sent by this Node." |
| 1540 |
::= { snaPu20StatsEntry 1 } |
| 1541 |
|
| 1542 |
snaPu20StatsReceivedBytes OBJECT-TYPE |
| 1543 |
SYNTAX Counter32 |
| 1544 |
MAX-ACCESS read-only |
| 1545 |
STATUS current |
| 1546 |
DESCRIPTION |
| 1547 |
"The number of bytes received by this Node." |
| 1548 |
::= { snaPu20StatsEntry 2 } |
| 1549 |
|
| 1550 |
snaPu20StatsSentPius OBJECT-TYPE |
| 1551 |
SYNTAX Counter32 |
| 1552 |
MAX-ACCESS read-only |
| 1553 |
STATUS current |
| 1554 |
DESCRIPTION |
| 1555 |
"The number of PIUs sent by this Node." |
| 1556 |
::= { snaPu20StatsEntry 3 } |
| 1557 |
|
| 1558 |
snaPu20StatsReceivedPius OBJECT-TYPE |
| 1559 |
SYNTAX Counter32 |
| 1560 |
MAX-ACCESS read-only |
| 1561 |
|
| 1562 |
|
| 1563 |
|
| 1564 |
<span class="grey">Kielczewski, Kostick & Shih [Page 28]</span></pre> |
| 1565 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span> |
| 1566 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 1567 |
|
| 1568 |
|
| 1569 |
STATUS current |
| 1570 |
DESCRIPTION |
| 1571 |
"The number of PIUs received by this Node." |
| 1572 |
::= { snaPu20StatsEntry 4 } |
| 1573 |
|
| 1574 |
snaPu20StatsSentNegativeResps OBJECT-TYPE |
| 1575 |
SYNTAX Counter32 |
| 1576 |
MAX-ACCESS read-only |
| 1577 |
STATUS current |
| 1578 |
DESCRIPTION |
| 1579 |
"The number of negative responses sent |
| 1580 |
by this Node." |
| 1581 |
::= { snaPu20StatsEntry 5 } |
| 1582 |
|
| 1583 |
snaPu20StatsReceivedNegativeResps OBJECT-TYPE |
| 1584 |
SYNTAX Counter32 |
| 1585 |
MAX-ACCESS read-only |
| 1586 |
STATUS current |
| 1587 |
DESCRIPTION |
| 1588 |
"The number of negative responses received |
| 1589 |
by this Node." |
| 1590 |
::= { snaPu20StatsEntry 6 } |
| 1591 |
|
| 1592 |
snaPu20StatsActLus OBJECT-TYPE |
| 1593 |
SYNTAX Gauge32 |
| 1594 |
MAX-ACCESS read-only |
| 1595 |
STATUS current |
| 1596 |
DESCRIPTION |
| 1597 |
"The number of LUs on this PU which have |
| 1598 |
received and responded to ACTLU from the host." |
| 1599 |
::= { snaPu20StatsEntry 7 } |
| 1600 |
|
| 1601 |
snaPu20StatsInActLus OBJECT-TYPE |
| 1602 |
SYNTAX Gauge32 |
| 1603 |
MAX-ACCESS read-only |
| 1604 |
STATUS current |
| 1605 |
DESCRIPTION |
| 1606 |
"The number of LUs on this PU which have |
| 1607 |
not received an ACTLU from the host. This is |
| 1608 |
possible if the number of configured LUs exceeds |
| 1609 |
that on the host." |
| 1610 |
::= { snaPu20StatsEntry 8 } |
| 1611 |
|
| 1612 |
snaPu20StatsBindLus OBJECT-TYPE |
| 1613 |
SYNTAX Gauge32 |
| 1614 |
MAX-ACCESS read-only |
| 1615 |
STATUS current |
| 1616 |
DESCRIPTION |
| 1617 |
|
| 1618 |
|
| 1619 |
|
| 1620 |
<span class="grey">Kielczewski, Kostick & Shih [Page 29]</span></pre> |
| 1621 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span> |
| 1622 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 1623 |
|
| 1624 |
|
| 1625 |
"The number of LUs on this PU which have |
| 1626 |
received and acknowledged a BIND request from the |
| 1627 |
host." |
| 1628 |
::= { snaPu20StatsEntry 9 } |
| 1629 |
|
| 1630 |
|
| 1631 |
-- *************************************************************** |
| 1632 |
-- The following table contains the association between Nodes and |
| 1633 |
-- link identifiers. |
| 1634 |
-- It is used for configuration purposes. |
| 1635 |
-- *************************************************************** |
| 1636 |
|
| 1637 |
snaNodeLinkAdminTable OBJECT-TYPE |
| 1638 |
SYNTAX SEQUENCE OF SnaNodeLinkAdminEntry |
| 1639 |
MAX-ACCESS not-accessible |
| 1640 |
STATUS current |
| 1641 |
DESCRIPTION |
| 1642 |
"This table contains the references to link |
| 1643 |
specific tables. If a Node is configured for |
| 1644 |
multiple links, then the Node will have |
| 1645 |
multiple entries in this table. |
| 1646 |
The entries in this table can be generated |
| 1647 |
initially, after initialization of SNA service, |
| 1648 |
by the Agent which uses information from |
| 1649 |
Node configuration file. |
| 1650 |
Subsequent modifications of parameters, |
| 1651 |
creation of new Nodes link entries and deletion |
| 1652 |
of entries is possible. |
| 1653 |
The modification to this table can be |
| 1654 |
saved in the Node configuration file for the |
| 1655 |
next initialization of SNA service, but the mechanism |
| 1656 |
for this function is not defined here." |
| 1657 |
::= { snaNode 6 } |
| 1658 |
|
| 1659 |
snaNodeLinkAdminEntry OBJECT-TYPE |
| 1660 |
SYNTAX SnaNodeLinkAdminEntry |
| 1661 |
MAX-ACCESS not-accessible |
| 1662 |
STATUS current |
| 1663 |
DESCRIPTION |
| 1664 |
"Entry contains the configuration information that |
| 1665 |
associates a Node instance to one link instance. |
| 1666 |
The objects in the entry have read-create access. |
| 1667 |
Entry can be created, modified or deleted. |
| 1668 |
The object snaNodeLinkAdminRowStatus is used (set) |
| 1669 |
to create or delete an entry. |
| 1670 |
The object snaNodeLinkAdminSpecific can be set |
| 1671 |
later, after the entry has been created." |
| 1672 |
INDEX { snaNodeAdminIndex, |
| 1673 |
|
| 1674 |
|
| 1675 |
|
| 1676 |
<span class="grey">Kielczewski, Kostick & Shih [Page 30]</span></pre> |
| 1677 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span> |
| 1678 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 1679 |
|
| 1680 |
|
| 1681 |
snaNodeLinkAdminIndex } |
| 1682 |
::= { snaNodeLinkAdminTable 1 } |
| 1683 |
|
| 1684 |
SnaNodeLinkAdminEntry ::= SEQUENCE { |
| 1685 |
snaNodeLinkAdminIndex |
| 1686 |
Integer32, |
| 1687 |
snaNodeLinkAdminSpecific |
| 1688 |
InstancePointer, |
| 1689 |
snaNodeLinkAdminMaxPiu |
| 1690 |
Integer32, |
| 1691 |
snaNodeLinkAdminRowStatus |
| 1692 |
RowStatus |
| 1693 |
} |
| 1694 |
|
| 1695 |
snaNodeLinkAdminIndex OBJECT-TYPE |
| 1696 |
SYNTAX Integer32 |
| 1697 |
MAX-ACCESS not-accessible |
| 1698 |
STATUS current |
| 1699 |
DESCRIPTION |
| 1700 |
"This value is used to index the instances of objects. |
| 1701 |
If an Agent creates the entry, then it will assign |
| 1702 |
this number otherwise a Management Station |
| 1703 |
generates a random number when it reserves the |
| 1704 |
entry for creation." |
| 1705 |
::= { snaNodeLinkAdminEntry 1 } |
| 1706 |
|
| 1707 |
snaNodeLinkAdminSpecific OBJECT-TYPE |
| 1708 |
SYNTAX InstancePointer |
| 1709 |
MAX-ACCESS read-create |
| 1710 |
STATUS current |
| 1711 |
DESCRIPTION |
| 1712 |
"This value points to the ifIndex value |
| 1713 |
instance (in the sdlcLSAdminTable of |
| 1714 |
the SNA DLC MIB module) that corresponds to the link. |
| 1715 |
SDLC link-specific information is provided in the |
| 1716 |
SNA DLC MIB." |
| 1717 |
::= { snaNodeLinkAdminEntry 2 } |
| 1718 |
|
| 1719 |
snaNodeLinkAdminMaxPiu OBJECT-TYPE |
| 1720 |
SYNTAX Integer32 |
| 1721 |
MAX-ACCESS read-create |
| 1722 |
STATUS current |
| 1723 |
DESCRIPTION |
| 1724 |
"This value identifies the maximum number of octets |
| 1725 |
that can be exchanged by this Node in one |
| 1726 |
Path Information Unit (PIU)." |
| 1727 |
::= { snaNodeLinkAdminEntry 3 } |
| 1728 |
|
| 1729 |
|
| 1730 |
|
| 1731 |
|
| 1732 |
<span class="grey">Kielczewski, Kostick & Shih [Page 31]</span></pre> |
| 1733 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span> |
| 1734 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 1735 |
|
| 1736 |
|
| 1737 |
snaNodeLinkAdminRowStatus OBJECT-TYPE |
| 1738 |
SYNTAX RowStatus |
| 1739 |
MAX-ACCESS read-create |
| 1740 |
STATUS current |
| 1741 |
DESCRIPTION |
| 1742 |
"This object is used by a Management Station to |
| 1743 |
create or delete the row entry in the |
| 1744 |
snaNodeLinkAdminTable. |
| 1745 |
To activate a row, a Management Station sets the value |
| 1746 |
to 'active (1)' or 'notReady (3)'. Upon successful |
| 1747 |
creation of the row, the Agent automatically creates |
| 1748 |
a corresponding entry in the snaNodeLinkOperTable. |
| 1749 |
|
| 1750 |
Row deletion can be Management Station or Agent |
| 1751 |
initiated: |
| 1752 |
(a) The Management Station can set the value to |
| 1753 |
`destroy (6)' only when the value of |
| 1754 |
snaNodeLinkOperState of this Link |
| 1755 |
instance is `inactive (1)'. The Agent will then |
| 1756 |
delete the row corresponding to this Link |
| 1757 |
instance from snaNodeLinkOperTable and |
| 1758 |
from snaNodeLinkAdminTable. |
| 1759 |
(b) The Agent detects that a row is in the |
| 1760 |
`notReady (3)' state for greater than a |
| 1761 |
default period of 5 minutes. |
| 1762 |
(c) The Agent will not include a row with RowStatus= |
| 1763 |
`notReady (3)', after SNA system re-initialization |
| 1764 |
(e.g., reboot)." |
| 1765 |
::= { snaNodeLinkAdminEntry 4 } |
| 1766 |
|
| 1767 |
|
| 1768 |
-- *************************************************************** |
| 1769 |
-- The following object is updated when there is a change to |
| 1770 |
-- the value of any object in the snaNodeLinkAdminTable. |
| 1771 |
-- *************************************************************** |
| 1772 |
|
| 1773 |
|
| 1774 |
snaNodeLinkAdminTableLastChange OBJECT-TYPE |
| 1775 |
SYNTAX TimeStamp |
| 1776 |
MAX-ACCESS read-only |
| 1777 |
STATUS current |
| 1778 |
DESCRIPTION |
| 1779 |
"The timestamp (e.g., the Agent's sysUpTime value) |
| 1780 |
at the last |
| 1781 |
change made to any object in the snaNodeLinkAdminTable, |
| 1782 |
including row deletions/additions (i.e., changes |
| 1783 |
to the snaNodeLinkAdminRowStatus object). |
| 1784 |
|
| 1785 |
|
| 1786 |
|
| 1787 |
|
| 1788 |
<span class="grey">Kielczewski, Kostick & Shih [Page 32]</span></pre> |
| 1789 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span> |
| 1790 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 1791 |
|
| 1792 |
|
| 1793 |
This object can be used to reduce frequent |
| 1794 |
retrievals of the snaNodeLinkAdminTable by a |
| 1795 |
Management Station. It is expected that a |
| 1796 |
Management Station will periodically poll this |
| 1797 |
object and compare its current value with the |
| 1798 |
previous one. |
| 1799 |
A difference indicates that some Node operational |
| 1800 |
information has been changed. Only then will the |
| 1801 |
Management Station retrieve the entire table." |
| 1802 |
::= { snaNode 7 } |
| 1803 |
|
| 1804 |
|
| 1805 |
-- *************************************************************** |
| 1806 |
-- The following table contains the association between |
| 1807 |
-- Nodes and link identifiers. |
| 1808 |
-- It provides the current status. |
| 1809 |
-- *************************************************************** |
| 1810 |
|
| 1811 |
snaNodeLinkOperTable OBJECT-TYPE |
| 1812 |
SYNTAX SEQUENCE OF SnaNodeLinkOperEntry |
| 1813 |
MAX-ACCESS not-accessible |
| 1814 |
STATUS current |
| 1815 |
DESCRIPTION |
| 1816 |
"This table contains all references to link |
| 1817 |
specific tables for operational parameters. |
| 1818 |
If a Node is configured for multiple links, |
| 1819 |
then the Node will have multiple entries in |
| 1820 |
this table. This table augments the |
| 1821 |
snaNodeLinkAdminTable." |
| 1822 |
::= { snaNode 8 } |
| 1823 |
|
| 1824 |
snaNodeLinkOperEntry OBJECT-TYPE |
| 1825 |
SYNTAX SnaNodeLinkOperEntry |
| 1826 |
MAX-ACCESS not-accessible |
| 1827 |
STATUS current |
| 1828 |
DESCRIPTION |
| 1829 |
"Entry contains all current parameters for one |
| 1830 |
Node link. The objects in the entry have |
| 1831 |
read-only access." |
| 1832 |
AUGMENTS { snaNodeLinkAdminEntry } |
| 1833 |
::= { snaNodeLinkOperTable 1 } |
| 1834 |
|
| 1835 |
SnaNodeLinkOperEntry ::= SEQUENCE { |
| 1836 |
snaNodeLinkOperSpecific |
| 1837 |
InstancePointer, |
| 1838 |
snaNodeLinkOperMaxPiu |
| 1839 |
Integer32 |
| 1840 |
} |
| 1841 |
|
| 1842 |
|
| 1843 |
|
| 1844 |
<span class="grey">Kielczewski, Kostick & Shih [Page 33]</span></pre> |
| 1845 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span> |
| 1846 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 1847 |
|
| 1848 |
|
| 1849 |
snaNodeLinkOperSpecific OBJECT-TYPE |
| 1850 |
SYNTAX InstancePointer |
| 1851 |
MAX-ACCESS read-only |
| 1852 |
STATUS current |
| 1853 |
DESCRIPTION |
| 1854 |
"This is the object identifier representing |
| 1855 |
the instance of the ifIndex object in |
| 1856 |
the sdlcLSOperTable (of the SNA DLC MIB module). |
| 1857 |
The associated sdlcLSOperTable row |
| 1858 |
will contain information on the link instance." |
| 1859 |
::= { snaNodeLinkOperEntry 1 } |
| 1860 |
|
| 1861 |
snaNodeLinkOperMaxPiu OBJECT-TYPE |
| 1862 |
SYNTAX Integer32 |
| 1863 |
MAX-ACCESS read-only |
| 1864 |
STATUS current |
| 1865 |
DESCRIPTION |
| 1866 |
"Maximum number of octets that can |
| 1867 |
be exchanged by this Node in one Path |
| 1868 |
Information Unit (PIU)." |
| 1869 |
::= { snaNodeLinkOperEntry 2 } |
| 1870 |
|
| 1871 |
|
| 1872 |
-- *************************************************************** |
| 1873 |
-- The following object is updated when a row is added/deleted |
| 1874 |
-- from the snaNodeLinkOperTable. |
| 1875 |
-- *************************************************************** |
| 1876 |
|
| 1877 |
snaNodeLinkOperTableLastChange OBJECT-TYPE |
| 1878 |
SYNTAX TimeStamp |
| 1879 |
MAX-ACCESS read-only |
| 1880 |
STATUS current |
| 1881 |
DESCRIPTION |
| 1882 |
"The timestamp of the last |
| 1883 |
change made to any object in the snaNodeLinkOperTable, |
| 1884 |
including row deletions/additions. |
| 1885 |
|
| 1886 |
This object can be used to reduce frequent |
| 1887 |
retrievals of the snaNodeLinkOperTable by a |
| 1888 |
Management Station. It is expected that a |
| 1889 |
Management Station will periodically poll this |
| 1890 |
object and compare its current value with the |
| 1891 |
previous one. |
| 1892 |
A difference indicates that some Node operational |
| 1893 |
information has been changed. Only then will the |
| 1894 |
Management Station retrieve the entire table." |
| 1895 |
::= { snaNode 9 } |
| 1896 |
|
| 1897 |
|
| 1898 |
|
| 1899 |
|
| 1900 |
<span class="grey">Kielczewski, Kostick & Shih [Page 34]</span></pre> |
| 1901 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span> |
| 1902 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 1903 |
|
| 1904 |
|
| 1905 |
-- *************************************************************** |
| 1906 |
-- Traps |
| 1907 |
-- *************************************************************** |
| 1908 |
|
| 1909 |
snaNodeTraps OBJECT IDENTIFIER ::= { snaNode 10 } |
| 1910 |
|
| 1911 |
snaNodeStateChangeTrap NOTIFICATION-TYPE |
| 1912 |
OBJECTS { snaNodeOperName, |
| 1913 |
snaNodeOperState } |
| 1914 |
STATUS current |
| 1915 |
DESCRIPTION |
| 1916 |
"This trap indicates that the operational state |
| 1917 |
(i.e., value of the snaNodeOperState object) of a Node |
| 1918 |
has changed. The following variables are returned: |
| 1919 |
snaNodeOperName - current name of the Node, |
| 1920 |
with the instance identifying the Node; and, |
| 1921 |
snaNodeOperState - current state after |
| 1922 |
the change." |
| 1923 |
::= { snaNodeTraps 1 } |
| 1924 |
|
| 1925 |
snaNodeActFailTrap NOTIFICATION-TYPE |
| 1926 |
OBJECTS { snaNodeOperName, |
| 1927 |
snaNodeOperState, |
| 1928 |
snaNodeOperActFailureReason } |
| 1929 |
STATUS current |
| 1930 |
DESCRIPTION |
| 1931 |
"This trap indicates a Node activation failure. |
| 1932 |
The value of snaNodeOperState indicates the current |
| 1933 |
state after the activation attempt. |
| 1934 |
The value of snaNodeOperActFailureReason indicates |
| 1935 |
the failure reason." |
| 1936 |
::= { snaNodeTraps 2 } |
| 1937 |
|
| 1938 |
|
| 1939 |
|
| 1940 |
-- *************************************************************** |
| 1941 |
-- snaLu group |
| 1942 |
-- |
| 1943 |
-- It contains Managed Objects related to LUs in general and some |
| 1944 |
-- specific for LUs of type 0, 1, 2, 3. |
| 1945 |
-- *************************************************************** |
| 1946 |
|
| 1947 |
|
| 1948 |
-- *************************************************************** |
| 1949 |
-- The following table contains LU configuration parameters. |
| 1950 |
-- *************************************************************** |
| 1951 |
|
| 1952 |
|
| 1953 |
|
| 1954 |
|
| 1955 |
|
| 1956 |
<span class="grey">Kielczewski, Kostick & Shih [Page 35]</span></pre> |
| 1957 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span> |
| 1958 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 1959 |
|
| 1960 |
|
| 1961 |
snaLuAdminTable OBJECT-TYPE |
| 1962 |
SYNTAX SEQUENCE OF SnaLuAdminEntry |
| 1963 |
MAX-ACCESS not-accessible |
| 1964 |
STATUS current |
| 1965 |
DESCRIPTION |
| 1966 |
"This table contains LU configuration information. |
| 1967 |
The rows in this table can be created and deleted |
| 1968 |
by a Management Station. |
| 1969 |
Only objects which are common to all types of LUs |
| 1970 |
are included in this table." |
| 1971 |
::= { snaLu 1 } |
| 1972 |
|
| 1973 |
snaLuAdminEntry OBJECT-TYPE |
| 1974 |
SYNTAX SnaLuAdminEntry |
| 1975 |
MAX-ACCESS not-accessible |
| 1976 |
STATUS current |
| 1977 |
DESCRIPTION |
| 1978 |
"Contains configuration variables for an LU." |
| 1979 |
INDEX { snaNodeAdminIndex, snaLuAdminLuIndex } |
| 1980 |
::= { snaLuAdminTable 1 } |
| 1981 |
|
| 1982 |
SnaLuAdminEntry ::= SEQUENCE { |
| 1983 |
snaLuAdminLuIndex |
| 1984 |
Integer32, |
| 1985 |
snaLuAdminName |
| 1986 |
DisplayString, |
| 1987 |
snaLuAdminSnaName |
| 1988 |
DisplayString, |
| 1989 |
snaLuAdminType |
| 1990 |
INTEGER, |
| 1991 |
snaLuAdminDepType |
| 1992 |
INTEGER, |
| 1993 |
snaLuAdminLocalAddress |
| 1994 |
OCTET STRING, |
| 1995 |
snaLuAdminDisplayModel |
| 1996 |
INTEGER, |
| 1997 |
snaLuAdminTerm |
| 1998 |
INTEGER, |
| 1999 |
snaLuAdminRowStatus |
| 2000 |
RowStatus |
| 2001 |
} |
| 2002 |
|
| 2003 |
snaLuAdminLuIndex OBJECT-TYPE |
| 2004 |
SYNTAX Integer32 |
| 2005 |
MAX-ACCESS not-accessible |
| 2006 |
STATUS current |
| 2007 |
DESCRIPTION |
| 2008 |
"This value identifies the unique index for an |
| 2009 |
|
| 2010 |
|
| 2011 |
|
| 2012 |
<span class="grey">Kielczewski, Kostick & Shih [Page 36]</span></pre> |
| 2013 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span> |
| 2014 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 2015 |
|
| 2016 |
|
| 2017 |
LU instance within a Node." |
| 2018 |
::= { snaLuAdminEntry 1 } |
| 2019 |
|
| 2020 |
snaLuAdminName OBJECT-TYPE |
| 2021 |
SYNTAX DisplayString (SIZE(0..48)) |
| 2022 |
MAX-ACCESS read-create |
| 2023 |
STATUS current |
| 2024 |
DESCRIPTION |
| 2025 |
"This value identifies the user configurable |
| 2026 |
name for this LU. If a name is not assigned to the LU, |
| 2027 |
then this object contains a zero length string. |
| 2028 |
|
| 2029 |
A write operation to this object will |
| 2030 |
not change the operational value reflected |
| 2031 |
in snaLuOperName until the Node has |
| 2032 |
been re-activated (e.g., after the next |
| 2033 |
initialization of the SNA services)." |
| 2034 |
::= { snaLuAdminEntry 2 } |
| 2035 |
|
| 2036 |
snaLuAdminSnaName OBJECT-TYPE |
| 2037 |
SYNTAX DisplayString (SIZE(1..17)) |
| 2038 |
MAX-ACCESS read-create |
| 2039 |
STATUS current |
| 2040 |
DESCRIPTION |
| 2041 |
"This value identifies the SNA LU name |
| 2042 |
used in exchange of SNA data. |
| 2043 |
|
| 2044 |
A write operation to this object will |
| 2045 |
not change the operational value reflected |
| 2046 |
in snaLuOperSnaName until the Node has |
| 2047 |
been re-activated (e.g., after the next |
| 2048 |
initialization of the SNA services)." |
| 2049 |
::= { snaLuAdminEntry 3 } |
| 2050 |
|
| 2051 |
snaLuAdminType OBJECT-TYPE |
| 2052 |
SYNTAX INTEGER { |
| 2053 |
other(1), |
| 2054 |
lu0(2), |
| 2055 |
lu1(3), |
| 2056 |
lu2(4), |
| 2057 |
lu3(5), |
| 2058 |
lu4(6), |
| 2059 |
lu62(7), |
| 2060 |
lu7(8) |
| 2061 |
} |
| 2062 |
MAX-ACCESS read-create |
| 2063 |
STATUS current |
| 2064 |
DESCRIPTION |
| 2065 |
|
| 2066 |
|
| 2067 |
|
| 2068 |
<span class="grey">Kielczewski, Kostick & Shih [Page 37]</span></pre> |
| 2069 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span> |
| 2070 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 2071 |
|
| 2072 |
|
| 2073 |
"This value identifies the LU type. |
| 2074 |
|
| 2075 |
A write operation to this object will |
| 2076 |
not change the operational value reflected |
| 2077 |
in snaLuOperAdminType until the Node has |
| 2078 |
been re-activated (e.g., after the next |
| 2079 |
initialization of the SNA services)." |
| 2080 |
::= { snaLuAdminEntry 4 } |
| 2081 |
|
| 2082 |
snaLuAdminDepType OBJECT-TYPE |
| 2083 |
SYNTAX INTEGER { |
| 2084 |
dependent(1), |
| 2085 |
independent(2) |
| 2086 |
} |
| 2087 |
MAX-ACCESS read-create |
| 2088 |
STATUS current |
| 2089 |
DESCRIPTION |
| 2090 |
"This value identifies whether the LU is |
| 2091 |
dependent or independent. |
| 2092 |
|
| 2093 |
A write operation to this object will |
| 2094 |
not change the operational value reflected |
| 2095 |
in snaLuOperDepType until the Node has |
| 2096 |
been re-activated (e.g., after the next |
| 2097 |
initialization of the SNA services)." |
| 2098 |
::= { snaLuAdminEntry 5 } |
| 2099 |
|
| 2100 |
snaLuAdminLocalAddress OBJECT-TYPE |
| 2101 |
SYNTAX OCTET STRING (SIZE(1)) |
| 2102 |
MAX-ACCESS read-create |
| 2103 |
STATUS current |
| 2104 |
DESCRIPTION |
| 2105 |
"The local address for this LU is a byte with a value |
| 2106 |
ranging from 0 to 254.For dependent LUs, this value |
| 2107 |
ranges from 1 to 254 and for independent LUs this |
| 2108 |
value is always 0. |
| 2109 |
|
| 2110 |
A write operation to this object will not change the |
| 2111 |
operational value reflected in snaLuOperLocalAddress |
| 2112 |
until the Node has been re-activated (e.g., after the |
| 2113 |
next initialization of the SNA services)." |
| 2114 |
::= { snaLuAdminEntry 6 } |
| 2115 |
|
| 2116 |
snaLuAdminDisplayModel OBJECT-TYPE |
| 2117 |
SYNTAX INTEGER { |
| 2118 |
invalid(1), |
| 2119 |
model2A(2), |
| 2120 |
model2B(3), |
| 2121 |
|
| 2122 |
|
| 2123 |
|
| 2124 |
<span class="grey">Kielczewski, Kostick & Shih [Page 38]</span></pre> |
| 2125 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span> |
| 2126 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 2127 |
|
| 2128 |
|
| 2129 |
model3A(4), |
| 2130 |
model3B(5), |
| 2131 |
model4A(6), |
| 2132 |
model4B(7), |
| 2133 |
model5A(8), |
| 2134 |
model5B(9), |
| 2135 |
dynamic(10) |
| 2136 |
} |
| 2137 |
MAX-ACCESS read-create |
| 2138 |
STATUS current |
| 2139 |
DESCRIPTION |
| 2140 |
"The value of this object identifies the model type |
| 2141 |
and screen size of the terminal connected to the host. |
| 2142 |
This is only valid for LU Type 2. The values have |
| 2143 |
the following meaning: |
| 2144 |
|
| 2145 |
model2A(2) - Model 2 (24 rows x 80 cols) with base |
| 2146 |
attributes |
| 2147 |
model2B(3) - Model 2 (24 rows x 80 cols) with |
| 2148 |
extended attributes |
| 2149 |
model3A(4) - Model 3 (32 rows x 80 cols) with base |
| 2150 |
attributes |
| 2151 |
model3B(5) - Model 3 (32 rows x 80 cols) with extended |
| 2152 |
attributes |
| 2153 |
model4A(6) - Model 4 (43 rows x 80 cols) with base |
| 2154 |
attributes |
| 2155 |
model4B(7) - Model 4 (43 rows x 80 cols) with extended |
| 2156 |
attributes |
| 2157 |
model5A(8) - Model 5 (27 rows x 132 cols) with base |
| 2158 |
attributes |
| 2159 |
model5B(9) - Model 5 (27 rows x 132 cols) with |
| 2160 |
extended attributes |
| 2161 |
dynamic(10) - Screen size determine with BIND and Read |
| 2162 |
Partition Query. |
| 2163 |
|
| 2164 |
In case this LU is not Type 2, then this object |
| 2165 |
should contain the invalid(1) value." |
| 2166 |
::= { snaLuAdminEntry 7 } |
| 2167 |
|
| 2168 |
snaLuAdminTerm OBJECT-TYPE |
| 2169 |
SYNTAX INTEGER { |
| 2170 |
unbind (1), |
| 2171 |
termself (2), |
| 2172 |
rshutd (3), |
| 2173 |
poweroff (4) |
| 2174 |
} |
| 2175 |
MAX-ACCESS read-create |
| 2176 |
STATUS current |
| 2177 |
|
| 2178 |
|
| 2179 |
|
| 2180 |
<span class="grey">Kielczewski, Kostick & Shih [Page 39]</span></pre> |
| 2181 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span> |
| 2182 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 2183 |
|
| 2184 |
|
| 2185 |
DESCRIPTION |
| 2186 |
"This value identifies the desired method for |
| 2187 |
deactivation of this LU. This value overrides the |
| 2188 |
default method (snaNodeOperLuTermDefault) for this |
| 2189 |
Node. For LU 6.2, only the value 'unbind (1)' |
| 2190 |
applies. |
| 2191 |
|
| 2192 |
unbind(1) - terminate the LU-LU session by sending |
| 2193 |
an SNA UNBIND request. |
| 2194 |
termself(2) - terminate the LU-LU session by sending |
| 2195 |
an SNA TERM-SELF (Terminate Self) request on |
| 2196 |
the SSCP-LU session. The SSCP will inform the |
| 2197 |
remote session LU partner to send an UNBIND |
| 2198 |
request to terminate the session. |
| 2199 |
rshutd(3) - terminate the LU-LU session by sending |
| 2200 |
an SNA RSHUTD (Request ShutDown) request to |
| 2201 |
the remote session LU partner. The remote LU |
| 2202 |
will then send an UNBIND request to terminate |
| 2203 |
the session. |
| 2204 |
poweroff(4) - terminate the LU-LU session by sending |
| 2205 |
either an SNA LUSTAT (LU Status) request on |
| 2206 |
the LU-LU session or an SNA NOTIFY request on |
| 2207 |
the SSCP-LU session indicating that the LU has |
| 2208 |
been powered off. Sending both is also |
| 2209 |
acceptable. The result should be that the |
| 2210 |
remote session LU partner will send an UNBIND |
| 2211 |
to terminate the session. |
| 2212 |
|
| 2213 |
A write operation to this object may immediately |
| 2214 |
change the operational value reflected |
| 2215 |
in snaLuOperTerm depending |
| 2216 |
on the Agent implementation." |
| 2217 |
::= { snaLuAdminEntry 8 } |
| 2218 |
|
| 2219 |
snaLuAdminRowStatus OBJECT-TYPE |
| 2220 |
SYNTAX RowStatus |
| 2221 |
MAX-ACCESS read-create |
| 2222 |
STATUS current |
| 2223 |
DESCRIPTION |
| 2224 |
"This object is used by a Management Station to |
| 2225 |
create or delete the row entry in the |
| 2226 |
snaLuAdminTable. |
| 2227 |
To activate a row, the Management Station sets the |
| 2228 |
value to 'active (1)' or 'notReady (3)'. |
| 2229 |
Upon successful creation of the row, the Agent |
| 2230 |
automatically creates a corresponding entry in the |
| 2231 |
snaLuOperTable with snaLuOperState equal to |
| 2232 |
'inactive (1)'. |
| 2233 |
|
| 2234 |
|
| 2235 |
|
| 2236 |
<span class="grey">Kielczewski, Kostick & Shih [Page 40]</span></pre> |
| 2237 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span> |
| 2238 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 2239 |
|
| 2240 |
|
| 2241 |
Row deletion can be Management Station or Agent |
| 2242 |
initiated: |
| 2243 |
(a) The Management Station can set the value to |
| 2244 |
'destroy (6)' only when the value of snaLuOperState |
| 2245 |
of this LU instance is 'inactive (1)'. The Agent will |
| 2246 |
then delete the row corresponding to this LU |
| 2247 |
instance from snaLuAdminTable and |
| 2248 |
from snaLuOperTable. |
| 2249 |
(b) The Agent detects that a row is in the |
| 2250 |
'notReady (3)' state for greater than a |
| 2251 |
default period of 5 minutes. |
| 2252 |
(c) The Agent will not create a row with RowStatus |
| 2253 |
equal to 'notReady (3)', after SNA system |
| 2254 |
re-initialization (e.g., reboot)." |
| 2255 |
::= { snaLuAdminEntry 9 } |
| 2256 |
|
| 2257 |
|
| 2258 |
-- *************************************************************** |
| 2259 |
-- The following table contains LU state dynamic parameters. |
| 2260 |
-- *************************************************************** |
| 2261 |
|
| 2262 |
snaLuOperTable OBJECT-TYPE |
| 2263 |
SYNTAX SEQUENCE OF SnaLuOperEntry |
| 2264 |
MAX-ACCESS not-accessible |
| 2265 |
STATUS current |
| 2266 |
DESCRIPTION |
| 2267 |
"This table contains dynamic runtime information and |
| 2268 |
control variables relating to LUs. |
| 2269 |
Only objects which are common to all types of LUs are |
| 2270 |
included in this table. This table augments the |
| 2271 |
snaLuAdminTable." |
| 2272 |
::= { snaLu 2 } |
| 2273 |
|
| 2274 |
snaLuOperEntry OBJECT-TYPE |
| 2275 |
SYNTAX SnaLuOperEntry |
| 2276 |
MAX-ACCESS not-accessible |
| 2277 |
STATUS current |
| 2278 |
DESCRIPTION |
| 2279 |
"Contains objects reflecting current information |
| 2280 |
for an LU. |
| 2281 |
Each entry is created by the Agent. All entries |
| 2282 |
have read-only access." |
| 2283 |
AUGMENTS { snaLuAdminEntry } |
| 2284 |
::= { snaLuOperTable 1 } |
| 2285 |
|
| 2286 |
SnaLuOperEntry ::= SEQUENCE { |
| 2287 |
snaLuOperName |
| 2288 |
DisplayString, |
| 2289 |
|
| 2290 |
|
| 2291 |
|
| 2292 |
<span class="grey">Kielczewski, Kostick & Shih [Page 41]</span></pre> |
| 2293 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span> |
| 2294 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 2295 |
|
| 2296 |
|
| 2297 |
snaLuOperSnaName |
| 2298 |
DisplayString, |
| 2299 |
snaLuOperType |
| 2300 |
INTEGER, |
| 2301 |
snaLuOperDepType |
| 2302 |
INTEGER, |
| 2303 |
snaLuOperLocalAddress |
| 2304 |
OCTET STRING, |
| 2305 |
snaLuOperDisplayModel |
| 2306 |
INTEGER, |
| 2307 |
snaLuOperTerm |
| 2308 |
INTEGER, |
| 2309 |
snaLuOperState |
| 2310 |
INTEGER, |
| 2311 |
snaLuOperSessnCount |
| 2312 |
Gauge32 |
| 2313 |
} |
| 2314 |
|
| 2315 |
snaLuOperName OBJECT-TYPE |
| 2316 |
SYNTAX DisplayString (SIZE(0..48)) |
| 2317 |
MAX-ACCESS read-only |
| 2318 |
STATUS current |
| 2319 |
DESCRIPTION |
| 2320 |
"User configurable name for this LU. If a name |
| 2321 |
is not assigned, then this object contains a |
| 2322 |
zero length string." |
| 2323 |
::= { snaLuOperEntry 1 } |
| 2324 |
|
| 2325 |
snaLuOperSnaName OBJECT-TYPE |
| 2326 |
SYNTAX DisplayString (SIZE(1..17)) |
| 2327 |
MAX-ACCESS read-only |
| 2328 |
STATUS current |
| 2329 |
DESCRIPTION |
| 2330 |
"The value identifies the current SNA LU name." |
| 2331 |
::= { snaLuOperEntry 2 } |
| 2332 |
|
| 2333 |
snaLuOperType OBJECT-TYPE |
| 2334 |
SYNTAX INTEGER { |
| 2335 |
other(1), |
| 2336 |
lu0(2), |
| 2337 |
lu1(3), |
| 2338 |
lu2(4), |
| 2339 |
lu3(5), |
| 2340 |
lu4(6), |
| 2341 |
lu62(7), |
| 2342 |
lu7(8) |
| 2343 |
} |
| 2344 |
MAX-ACCESS read-only |
| 2345 |
|
| 2346 |
|
| 2347 |
|
| 2348 |
<span class="grey">Kielczewski, Kostick & Shih [Page 42]</span></pre> |
| 2349 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span> |
| 2350 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 2351 |
|
| 2352 |
|
| 2353 |
STATUS current |
| 2354 |
DESCRIPTION |
| 2355 |
"The value identifies the current LU type." |
| 2356 |
::= { snaLuOperEntry 3 } |
| 2357 |
|
| 2358 |
snaLuOperDepType OBJECT-TYPE |
| 2359 |
SYNTAX INTEGER { |
| 2360 |
dependent(1), |
| 2361 |
independent(2) |
| 2362 |
} |
| 2363 |
MAX-ACCESS read-only |
| 2364 |
STATUS current |
| 2365 |
DESCRIPTION |
| 2366 |
"The value identifies whether the LU is currently |
| 2367 |
dependent or independent. |
| 2368 |
|
| 2369 |
A write operation to this object will |
| 2370 |
not change the operational value reflected |
| 2371 |
in snaLuOperDepType until the Node has |
| 2372 |
been re-activated (e.g., after the next |
| 2373 |
initialization of the SNA services)." |
| 2374 |
::= { snaLuOperEntry 4 } |
| 2375 |
|
| 2376 |
snaLuOperLocalAddress OBJECT-TYPE |
| 2377 |
SYNTAX OCTET STRING (SIZE(1)) |
| 2378 |
MAX-ACCESS read-only |
| 2379 |
STATUS current |
| 2380 |
DESCRIPTION |
| 2381 |
"The local address for this LU is a byte with a value |
| 2382 |
ranging from 0 to 254. For dependent LUs, this value |
| 2383 |
ranges from 1 to 254; for independent LUs this value |
| 2384 |
is always 0. |
| 2385 |
|
| 2386 |
A write operation to this object will |
| 2387 |
not change the operational value reflected |
| 2388 |
in snaLuOperLocalAddress until the Node has |
| 2389 |
been re-activated (e.g., after the next |
| 2390 |
initialization of the SNA services)." |
| 2391 |
::= { snaLuOperEntry 5 } |
| 2392 |
|
| 2393 |
snaLuOperDisplayModel OBJECT-TYPE |
| 2394 |
SYNTAX INTEGER { |
| 2395 |
invalid(1), |
| 2396 |
model2A(2), |
| 2397 |
model2B(3), |
| 2398 |
model3A(4), |
| 2399 |
model3B(5), |
| 2400 |
model4A(6), |
| 2401 |
|
| 2402 |
|
| 2403 |
|
| 2404 |
<span class="grey">Kielczewski, Kostick & Shih [Page 43]</span></pre> |
| 2405 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-44" ></span> |
| 2406 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 2407 |
|
| 2408 |
|
| 2409 |
model4B(7), |
| 2410 |
model5A(8), |
| 2411 |
model5B(9), |
| 2412 |
dynamic(10) |
| 2413 |
} |
| 2414 |
MAX-ACCESS read-only |
| 2415 |
STATUS current |
| 2416 |
DESCRIPTION |
| 2417 |
"The screen model type of the terminal connected to |
| 2418 |
the host. If this LU is not Type 2, then this |
| 2419 |
object should contain the `invalid(1)' value." |
| 2420 |
::= { snaLuOperEntry 6 } |
| 2421 |
|
| 2422 |
snaLuOperTerm OBJECT-TYPE |
| 2423 |
SYNTAX INTEGER { |
| 2424 |
unbind (1), |
| 2425 |
termself (2), |
| 2426 |
rshutd (3), |
| 2427 |
poweroff (4) |
| 2428 |
} |
| 2429 |
MAX-ACCESS read-only |
| 2430 |
STATUS current |
| 2431 |
DESCRIPTION |
| 2432 |
"The value identifies the current method for |
| 2433 |
deactivation of this LU. This value overrides the |
| 2434 |
default method (snaNodeOperLuTermDefault) for this |
| 2435 |
Node. For LU 6.2, only the value 'unbind (1)' |
| 2436 |
applies. |
| 2437 |
|
| 2438 |
unbind(1) - terminate the LU-LU session by sending |
| 2439 |
an SNA UNBIND request. |
| 2440 |
termself(2) - terminate the LU-LU session by sending |
| 2441 |
an SNA TERM-SELF (Terminate Self) request on |
| 2442 |
the SSCP-LU session. The SSCP will inform the |
| 2443 |
remote session LU partner to send an UNBIND |
| 2444 |
request to terminate the session. |
| 2445 |
rshutd(3) - terminate the LU-LU session by sending |
| 2446 |
an SNA RSHUTD (Request ShutDown) request to |
| 2447 |
the remote session LU partner. The remote LU |
| 2448 |
will then send an UNBIND request to terminate |
| 2449 |
the session. |
| 2450 |
poweroff(4) - terminate the LU-LU session by sending |
| 2451 |
either an SNA LUSTAT (LU Status) request on |
| 2452 |
the LU-LU session or an SNA NOTIFY request on |
| 2453 |
the SSCP-LU session indicating that the LU has |
| 2454 |
been powered off. Sending both is also |
| 2455 |
acceptable. The result should be that the |
| 2456 |
remote session LU partner will send an UNBIND |
| 2457 |
|
| 2458 |
|
| 2459 |
|
| 2460 |
<span class="grey">Kielczewski, Kostick & Shih [Page 44]</span></pre> |
| 2461 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-45" ></span> |
| 2462 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 2463 |
|
| 2464 |
|
| 2465 |
to terminate the session." |
| 2466 |
::= { snaLuOperEntry 7 } |
| 2467 |
|
| 2468 |
snaLuOperState OBJECT-TYPE |
| 2469 |
SYNTAX INTEGER { |
| 2470 |
inactive (1), |
| 2471 |
active (2) |
| 2472 |
} |
| 2473 |
MAX-ACCESS read-only |
| 2474 |
STATUS current |
| 2475 |
DESCRIPTION |
| 2476 |
"The value identifies the current operational state of |
| 2477 |
this LU. It has different meanings for dependent and |
| 2478 |
independent LUs. |
| 2479 |
For dependent LUs the values indicate the following: |
| 2480 |
inactive (1) - LU didn't receive ACTLU, or |
| 2481 |
it received DACTLU, or received ACTLU and sent |
| 2482 |
negative response. |
| 2483 |
active (2) - LU received ACTLU and acknowledged |
| 2484 |
positively. |
| 2485 |
|
| 2486 |
For independent LUs the values indicate the following: |
| 2487 |
active (2) - the LU is defined and is able to send |
| 2488 |
and receive BIND. |
| 2489 |
inactive (1) - the LU has a session count equal |
| 2490 |
to 0." |
| 2491 |
::= { snaLuOperEntry 8 } |
| 2492 |
|
| 2493 |
snaLuOperSessnCount OBJECT-TYPE |
| 2494 |
SYNTAX Gauge32 |
| 2495 |
MAX-ACCESS read-only |
| 2496 |
STATUS current |
| 2497 |
DESCRIPTION |
| 2498 |
"The number of currently active LU-LU sessions of |
| 2499 |
this LU. |
| 2500 |
For the independent LU, if this object has value 0, |
| 2501 |
it indicates that LU is inactive." |
| 2502 |
::= { snaLuOperEntry 9 } |
| 2503 |
|
| 2504 |
|
| 2505 |
-- *************************************************************** |
| 2506 |
-- The following table contains LU-LU session status parameters. |
| 2507 |
-- *************************************************************** |
| 2508 |
|
| 2509 |
snaLuSessnTable OBJECT-TYPE |
| 2510 |
SYNTAX SEQUENCE OF SnaLuSessnEntry |
| 2511 |
MAX-ACCESS not-accessible |
| 2512 |
STATUS current |
| 2513 |
|
| 2514 |
|
| 2515 |
|
| 2516 |
<span class="grey">Kielczewski, Kostick & Shih [Page 45]</span></pre> |
| 2517 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-46" ></span> |
| 2518 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 2519 |
|
| 2520 |
|
| 2521 |
DESCRIPTION |
| 2522 |
"This is a table containing objects which describe the |
| 2523 |
operational state of LU-LU sessions. Only objects which |
| 2524 |
are common to all types of LU sessions are included |
| 2525 |
in this table. |
| 2526 |
|
| 2527 |
When a session's snaLuSessnOperState value changes to |
| 2528 |
'pending-bind (2)', then the corresponding entry |
| 2529 |
in the session table is created by the Agent. |
| 2530 |
|
| 2531 |
When the session's snaLuSessnOperState value changes to |
| 2532 |
'unbound (1)', then the session will be removed from |
| 2533 |
the session table by the Agent." |
| 2534 |
::= { snaLu 3 } |
| 2535 |
|
| 2536 |
snaLuSessnEntry OBJECT-TYPE |
| 2537 |
SYNTAX SnaLuSessnEntry |
| 2538 |
MAX-ACCESS not-accessible |
| 2539 |
STATUS current |
| 2540 |
DESCRIPTION |
| 2541 |
"An entry contains dynamic parameters for an LU-LU |
| 2542 |
session. The indices identify the Node, link and LU |
| 2543 |
on which this session has been established." |
| 2544 |
INDEX { snaNodeAdminIndex, |
| 2545 |
snaNodeLinkAdminIndex, |
| 2546 |
snaLuAdminLuIndex, |
| 2547 |
snaLuSessnIndex } |
| 2548 |
::= { snaLuSessnTable 1 } |
| 2549 |
|
| 2550 |
SnaLuSessnEntry ::= SEQUENCE { |
| 2551 |
snaLuSessnIndex |
| 2552 |
Integer32, |
| 2553 |
snaLuSessnLocalApplName |
| 2554 |
DisplayString, |
| 2555 |
snaLuSessnRemoteLuName |
| 2556 |
DisplayString, |
| 2557 |
snaLuSessnMaxSndRuSize |
| 2558 |
INTEGER, |
| 2559 |
snaLuSessnMaxRcvRuSize |
| 2560 |
INTEGER, |
| 2561 |
snaLuSessnSndPacingSize |
| 2562 |
INTEGER, |
| 2563 |
snaLuSessnRcvPacingSize |
| 2564 |
INTEGER, |
| 2565 |
snaLuSessnActiveTime |
| 2566 |
TimeStamp, |
| 2567 |
snaLuSessnAdminState |
| 2568 |
INTEGER, |
| 2569 |
|
| 2570 |
|
| 2571 |
|
| 2572 |
<span class="grey">Kielczewski, Kostick & Shih [Page 46]</span></pre> |
| 2573 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-47" ></span> |
| 2574 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 2575 |
|
| 2576 |
|
| 2577 |
snaLuSessnOperState |
| 2578 |
INTEGER, |
| 2579 |
snaLuSessnSenseData |
| 2580 |
OCTET STRING, |
| 2581 |
snaLuSessnTerminationRu |
| 2582 |
INTEGER, |
| 2583 |
snaLuSessnUnbindType |
| 2584 |
OCTET STRING |
| 2585 |
} |
| 2586 |
|
| 2587 |
snaLuSessnIndex OBJECT-TYPE |
| 2588 |
SYNTAX Integer32 |
| 2589 |
MAX-ACCESS read-only |
| 2590 |
STATUS current |
| 2591 |
DESCRIPTION |
| 2592 |
"This value identifies the unique index of the session. |
| 2593 |
It is recommended that an Agent should not reuse the |
| 2594 |
index of a deactivated session for a significant |
| 2595 |
period of time (e.g., one week)." |
| 2596 |
::= { snaLuSessnEntry 1 } |
| 2597 |
|
| 2598 |
snaLuSessnLocalApplName OBJECT-TYPE |
| 2599 |
SYNTAX DisplayString (SIZE(0..48)) |
| 2600 |
MAX-ACCESS read-only |
| 2601 |
STATUS current |
| 2602 |
DESCRIPTION |
| 2603 |
"The name of the local application using this LU. |
| 2604 |
If the local application is unknown, then this object |
| 2605 |
contains a zero length string." |
| 2606 |
::= { snaLuSessnEntry 2 } |
| 2607 |
|
| 2608 |
snaLuSessnRemoteLuName OBJECT-TYPE |
| 2609 |
SYNTAX DisplayString (SIZE(0..17)) |
| 2610 |
MAX-ACCESS read-only |
| 2611 |
STATUS current |
| 2612 |
DESCRIPTION |
| 2613 |
"For dependent LUs which are indicated by the |
| 2614 |
snaLuOperDepType object containing the value |
| 2615 |
'dependent (1)', this object contains the Primary |
| 2616 |
LU (PLU) name. For independent LUs, |
| 2617 |
this object contains the fully-qualified remote LU |
| 2618 |
name of this 6.2 session. |
| 2619 |
A fully qualified name is an SNA NAU entity name |
| 2620 |
preceded by the NetId and a period as the delimiter." |
| 2621 |
::= { snaLuSessnEntry 3 } |
| 2622 |
|
| 2623 |
snaLuSessnMaxSndRuSize OBJECT-TYPE |
| 2624 |
SYNTAX INTEGER (1..8192) |
| 2625 |
|
| 2626 |
|
| 2627 |
|
| 2628 |
<span class="grey">Kielczewski, Kostick & Shih [Page 47]</span></pre> |
| 2629 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-48" ></span> |
| 2630 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 2631 |
|
| 2632 |
|
| 2633 |
MAX-ACCESS read-only |
| 2634 |
STATUS current |
| 2635 |
DESCRIPTION |
| 2636 |
"The maximum RU size used on this session for sending |
| 2637 |
RUs." |
| 2638 |
::= { snaLuSessnEntry 4 } |
| 2639 |
|
| 2640 |
snaLuSessnMaxRcvRuSize OBJECT-TYPE |
| 2641 |
SYNTAX INTEGER (1..8192) |
| 2642 |
MAX-ACCESS read-only |
| 2643 |
STATUS current |
| 2644 |
DESCRIPTION |
| 2645 |
"The maximum RU size used on this session for |
| 2646 |
receiving RUs." |
| 2647 |
::= { snaLuSessnEntry 5 } |
| 2648 |
|
| 2649 |
snaLuSessnSndPacingSize OBJECT-TYPE |
| 2650 |
SYNTAX INTEGER (1..63) |
| 2651 |
MAX-ACCESS read-only |
| 2652 |
STATUS current |
| 2653 |
DESCRIPTION |
| 2654 |
"The size of the send pacing window on this session." |
| 2655 |
::= { snaLuSessnEntry 6 } |
| 2656 |
|
| 2657 |
snaLuSessnRcvPacingSize OBJECT-TYPE |
| 2658 |
SYNTAX INTEGER (1..63) |
| 2659 |
MAX-ACCESS read-only |
| 2660 |
STATUS current |
| 2661 |
DESCRIPTION |
| 2662 |
"The size of the receive pacing window on this |
| 2663 |
session." |
| 2664 |
::= { snaLuSessnEntry 7 } |
| 2665 |
|
| 2666 |
snaLuSessnActiveTime OBJECT-TYPE |
| 2667 |
SYNTAX TimeStamp |
| 2668 |
MAX-ACCESS read-only |
| 2669 |
STATUS current |
| 2670 |
DESCRIPTION |
| 2671 |
"The timestamp (e.g., the Agent's sysUpTime value) |
| 2672 |
when this session becomes active." |
| 2673 |
::= { snaLuSessnEntry 8 } |
| 2674 |
|
| 2675 |
snaLuSessnAdminState OBJECT-TYPE |
| 2676 |
SYNTAX INTEGER { |
| 2677 |
unbound (1), |
| 2678 |
bound (3) |
| 2679 |
} |
| 2680 |
MAX-ACCESS read-write |
| 2681 |
|
| 2682 |
|
| 2683 |
|
| 2684 |
<span class="grey">Kielczewski, Kostick & Shih [Page 48]</span></pre> |
| 2685 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-49" ></span> |
| 2686 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 2687 |
|
| 2688 |
|
| 2689 |
STATUS current |
| 2690 |
DESCRIPTION |
| 2691 |
"The value indicates the desired operational state of |
| 2692 |
the session. This object is used to |
| 2693 |
change the operational state of the session. |
| 2694 |
A Management Station can only change the operational |
| 2695 |
state of the session to `unbound (1)'. |
| 2696 |
|
| 2697 |
Session deactivation: |
| 2698 |
If a session is in the operational state |
| 2699 |
`bound (3)' then setting the value of this |
| 2700 |
object to 'unbound (1)' will initiate the |
| 2701 |
session shutdown. |
| 2702 |
If a session is in the operational state |
| 2703 |
`pending-bind (2)' then setting the value of this |
| 2704 |
object to 'unbound (1)' will initiate the session |
| 2705 |
shutdown. |
| 2706 |
If a session is in the operational state |
| 2707 |
`pending-unbind (4)' for an abnormally long period |
| 2708 |
of time (e.g., three minutes) then setting the value |
| 2709 |
of this object to 'unbound (1)' will change the |
| 2710 |
session operational state to 'unbound (1)'. |
| 2711 |
|
| 2712 |
Note: for dependent LUs, deactivating the session is |
| 2713 |
the same as deactivating the LU." |
| 2714 |
::= { snaLuSessnEntry 9 } |
| 2715 |
|
| 2716 |
snaLuSessnOperState OBJECT-TYPE |
| 2717 |
SYNTAX INTEGER { |
| 2718 |
unbound (1), |
| 2719 |
pending-bind (2), |
| 2720 |
bound (3), |
| 2721 |
pending-unbind (4) |
| 2722 |
} |
| 2723 |
MAX-ACCESS read-only |
| 2724 |
STATUS current |
| 2725 |
DESCRIPTION |
| 2726 |
"The value indicates the current operational state of |
| 2727 |
the session. |
| 2728 |
|
| 2729 |
'unbound (1)' - session has been unbound; |
| 2730 |
in this state it will be removed from the |
| 2731 |
session table by the Agent. |
| 2732 |
|
| 2733 |
'pending-bind (2)' - this state has different |
| 2734 |
meanings for dependent and independent LUs; |
| 2735 |
for dependent LU - waiting for BIND from |
| 2736 |
the host, for independent LU - waiting for |
| 2737 |
|
| 2738 |
|
| 2739 |
|
| 2740 |
<span class="grey">Kielczewski, Kostick & Shih [Page 49]</span></pre> |
| 2741 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-50" ></span> |
| 2742 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 2743 |
|
| 2744 |
|
| 2745 |
BIND response. When a session enters this |
| 2746 |
state, the corresponding entry in the |
| 2747 |
session table is created by the Agent. |
| 2748 |
|
| 2749 |
'bound (3)' - session has been successfully bound. |
| 2750 |
|
| 2751 |
'pending-unbind (4)' - session enters this state |
| 2752 |
when an UNBIND is sent and before the |
| 2753 |
rsp(UNBIND) is received." |
| 2754 |
::= { snaLuSessnEntry 10 } |
| 2755 |
|
| 2756 |
snaLuSessnSenseData OBJECT-TYPE |
| 2757 |
SYNTAX OCTET STRING (SIZE(0..8)) |
| 2758 |
MAX-ACCESS read-only |
| 2759 |
STATUS current |
| 2760 |
DESCRIPTION |
| 2761 |
"The value identifies the sense code when there is |
| 2762 |
a BIND failure. It is taken from the negative BIND |
| 2763 |
response or UNBIND request. |
| 2764 |
This is displayed as 8 hexadecimal digits." |
| 2765 |
::= { snaLuSessnEntry 11 } |
| 2766 |
|
| 2767 |
snaLuSessnTerminationRu OBJECT-TYPE |
| 2768 |
SYNTAX INTEGER { |
| 2769 |
other (1), |
| 2770 |
bind-failure (2), |
| 2771 |
unbind (3) |
| 2772 |
} |
| 2773 |
MAX-ACCESS read-only |
| 2774 |
STATUS current |
| 2775 |
DESCRIPTION |
| 2776 |
"The value identifies the SNA RU that terminated the |
| 2777 |
session. If the session is not in the unbound state, |
| 2778 |
this object has a value of 'other (1)'." |
| 2779 |
::= { snaLuSessnEntry 12 } |
| 2780 |
|
| 2781 |
snaLuSessnUnbindType OBJECT-TYPE |
| 2782 |
SYNTAX OCTET STRING (SIZE(0..1)) |
| 2783 |
MAX-ACCESS read-only |
| 2784 |
STATUS current |
| 2785 |
DESCRIPTION |
| 2786 |
"If the session is in the unbound state, and it was |
| 2787 |
terminated by an UNBIND, then this object contains |
| 2788 |
the UNBIND type value (byte 1 of the UNBIND RU); |
| 2789 |
otherwise the string is null." |
| 2790 |
::= { snaLuSessnEntry 13 } |
| 2791 |
|
| 2792 |
|
| 2793 |
|
| 2794 |
|
| 2795 |
|
| 2796 |
<span class="grey">Kielczewski, Kostick & Shih [Page 50]</span></pre> |
| 2797 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-51" ></span> |
| 2798 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 2799 |
|
| 2800 |
|
| 2801 |
-- *************************************************************** |
| 2802 |
-- The following table contains LU sessions statistics dynamic |
| 2803 |
-- parameters. |
| 2804 |
-- *************************************************************** |
| 2805 |
|
| 2806 |
snaLuSessnStatsTable OBJECT-TYPE |
| 2807 |
SYNTAX SEQUENCE OF SnaLuSessnStatsEntry |
| 2808 |
MAX-ACCESS not-accessible |
| 2809 |
STATUS current |
| 2810 |
DESCRIPTION |
| 2811 |
"This table contains dynamic statistics information |
| 2812 |
relating to LU sessions. |
| 2813 |
The entries in this table augment the entries in |
| 2814 |
the snaLuSessnTable and cannot be created by |
| 2815 |
a Management Station." |
| 2816 |
::= { snaLu 4 } |
| 2817 |
|
| 2818 |
snaLuSessnStatsEntry OBJECT-TYPE |
| 2819 |
SYNTAX SnaLuSessnStatsEntry |
| 2820 |
MAX-ACCESS not-accessible |
| 2821 |
STATUS current |
| 2822 |
DESCRIPTION |
| 2823 |
"Contains statistics information for an LU session. |
| 2824 |
Each entry is created by the Agent. |
| 2825 |
Objects in this table have read-only access. |
| 2826 |
Each session from snaLuSessnTable |
| 2827 |
has one entry in this table." |
| 2828 |
AUGMENTS { snaLuSessnEntry } |
| 2829 |
::= { snaLuSessnStatsTable 1 } |
| 2830 |
|
| 2831 |
SnaLuSessnStatsEntry ::= SEQUENCE { |
| 2832 |
snaLuSessnStatsSentBytes |
| 2833 |
Counter32, |
| 2834 |
snaLuSessnStatsReceivedBytes |
| 2835 |
Counter32, |
| 2836 |
snaLuSessnStatsSentRus |
| 2837 |
Counter32, |
| 2838 |
snaLuSessnStatsReceivedRus |
| 2839 |
Counter32, |
| 2840 |
snaLuSessnStatsSentNegativeResps |
| 2841 |
Counter32, |
| 2842 |
snaLuSessnStatsReceivedNegativeResps |
| 2843 |
Counter32 |
| 2844 |
} |
| 2845 |
|
| 2846 |
snaLuSessnStatsSentBytes OBJECT-TYPE |
| 2847 |
SYNTAX Counter32 |
| 2848 |
MAX-ACCESS read-only |
| 2849 |
|
| 2850 |
|
| 2851 |
|
| 2852 |
<span class="grey">Kielczewski, Kostick & Shih [Page 51]</span></pre> |
| 2853 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-52" ></span> |
| 2854 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 2855 |
|
| 2856 |
|
| 2857 |
STATUS current |
| 2858 |
DESCRIPTION |
| 2859 |
"The number of bytes sent by the local LU." |
| 2860 |
::= { snaLuSessnStatsEntry 1 } |
| 2861 |
|
| 2862 |
snaLuSessnStatsReceivedBytes OBJECT-TYPE |
| 2863 |
SYNTAX Counter32 |
| 2864 |
MAX-ACCESS read-only |
| 2865 |
STATUS current |
| 2866 |
DESCRIPTION |
| 2867 |
"The number of bytes received by the local LU." |
| 2868 |
::= { snaLuSessnStatsEntry 2 } |
| 2869 |
|
| 2870 |
snaLuSessnStatsSentRus OBJECT-TYPE |
| 2871 |
SYNTAX Counter32 |
| 2872 |
MAX-ACCESS read-only |
| 2873 |
STATUS current |
| 2874 |
DESCRIPTION |
| 2875 |
"The number of RUs sent by the local LU." |
| 2876 |
::= { snaLuSessnStatsEntry 3 } |
| 2877 |
|
| 2878 |
snaLuSessnStatsReceivedRus OBJECT-TYPE |
| 2879 |
SYNTAX Counter32 |
| 2880 |
MAX-ACCESS read-only |
| 2881 |
STATUS current |
| 2882 |
DESCRIPTION |
| 2883 |
"The number of RUs received by the local LU." |
| 2884 |
::= { snaLuSessnStatsEntry 4 } |
| 2885 |
|
| 2886 |
snaLuSessnStatsSentNegativeResps OBJECT-TYPE |
| 2887 |
SYNTAX Counter32 |
| 2888 |
MAX-ACCESS read-only |
| 2889 |
STATUS current |
| 2890 |
DESCRIPTION |
| 2891 |
"The number of negative responses sent by the |
| 2892 |
local LU." |
| 2893 |
::= { snaLuSessnStatsEntry 5 } |
| 2894 |
|
| 2895 |
snaLuSessnStatsReceivedNegativeResps OBJECT-TYPE |
| 2896 |
SYNTAX Counter32 |
| 2897 |
MAX-ACCESS read-only |
| 2898 |
STATUS current |
| 2899 |
DESCRIPTION |
| 2900 |
"The number of negative responses received by the |
| 2901 |
local LU." |
| 2902 |
::= { snaLuSessnStatsEntry 6 } |
| 2903 |
|
| 2904 |
|
| 2905 |
|
| 2906 |
|
| 2907 |
|
| 2908 |
<span class="grey">Kielczewski, Kostick & Shih [Page 52]</span></pre> |
| 2909 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-53" ></span> |
| 2910 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 2911 |
|
| 2912 |
|
| 2913 |
-- *************************************************************** |
| 2914 |
-- Traps |
| 2915 |
-- *************************************************************** |
| 2916 |
|
| 2917 |
snaLuTraps OBJECT IDENTIFIER ::= { snaLu 5 } |
| 2918 |
|
| 2919 |
snaLuStateChangeTrap NOTIFICATION-TYPE |
| 2920 |
OBJECTS { snaLuOperName, |
| 2921 |
snaLuOperSnaName, |
| 2922 |
snaLuOperState } |
| 2923 |
STATUS current |
| 2924 |
DESCRIPTION |
| 2925 |
"This trap indicates that the operational state |
| 2926 |
(i.e., snaLuOperState value) of the LU has changed. |
| 2927 |
The value of snaLuOperName indicates the name of the LU. |
| 2928 |
The value of snaLuOperSnaName indicates the SNA name |
| 2929 |
of LU. The value of snaLuOperState indicates the |
| 2930 |
current state after change." |
| 2931 |
::= { snaLuTraps 1 } |
| 2932 |
|
| 2933 |
snaLuSessnBindFailTrap NOTIFICATION-TYPE |
| 2934 |
OBJECTS { snaLuSessnLocalApplName, |
| 2935 |
snaLuSessnRemoteLuName, |
| 2936 |
snaLuSessnOperState, |
| 2937 |
snaLuSessnSenseData } |
| 2938 |
STATUS current |
| 2939 |
DESCRIPTION |
| 2940 |
"This trap indicates the failure of a BIND. |
| 2941 |
The value of snaLuSessnLocalApplName indicates the local |
| 2942 |
application name. |
| 2943 |
The value of snaLuSessnPartnerName indicates the partner |
| 2944 |
name. |
| 2945 |
The value of snaLuSessnOperState indicates the current |
| 2946 |
state after change. |
| 2947 |
The value of snaLuSessnBindFailureReason |
| 2948 |
indicates the failure reason. |
| 2949 |
The Agent should not generate more than 1 trap of this |
| 2950 |
type per minute to minimize the level of management |
| 2951 |
traffic on the network." |
| 2952 |
::= { snaLuTraps 2 } |
| 2953 |
|
| 2954 |
|
| 2955 |
-- *************************************************************** |
| 2956 |
-- snaMgtTools group |
| 2957 |
-- |
| 2958 |
-- Currently this group contains only one table. |
| 2959 |
-- *************************************************************** |
| 2960 |
|
| 2961 |
|
| 2962 |
|
| 2963 |
|
| 2964 |
<span class="grey">Kielczewski, Kostick & Shih [Page 53]</span></pre> |
| 2965 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-54" ></span> |
| 2966 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 2967 |
|
| 2968 |
|
| 2969 |
-- *************************************************************** |
| 2970 |
-- The following table contains Response Time Monitoring (RTM) |
| 2971 |
-- configuration information and statistics for LU Type 2s. |
| 2972 |
-- RTM supports the capability to measure and report end-user |
| 2973 |
-- response times for dependent LUs. When the RTM state of an LU |
| 2974 |
-- is 'on', response times for each LU transaction are monitored. |
| 2975 |
-- A set of ranges is defined (e.g., Range 1 includes the number of |
| 2976 |
-- transactions with response times less than 1 second) using the |
| 2977 |
-- "boundary" definitions (e.g., boundary #2 is defined as 3 seconds). |
| 2978 |
-- A set of counters (one per range) identifies |
| 2979 |
-- the number of transactions within each response time range. |
| 2980 |
-- *************************************************************** |
| 2981 |
|
| 2982 |
snaLuRtmTable OBJECT-TYPE |
| 2983 |
SYNTAX SEQUENCE OF SnaLuRtmEntry |
| 2984 |
MAX-ACCESS not-accessible |
| 2985 |
STATUS current |
| 2986 |
DESCRIPTION |
| 2987 |
"This table contains Response Time Monitoring (RTM) |
| 2988 |
information relating to an LU (Type 2). Each entry |
| 2989 |
corresponds to an LU 2 entry in |
| 2990 |
snaLuAdminTable." |
| 2991 |
::= { snaMgtTools 1 } |
| 2992 |
|
| 2993 |
snaLuRtmEntry OBJECT-TYPE |
| 2994 |
SYNTAX SnaLuRtmEntry |
| 2995 |
MAX-ACCESS not-accessible |
| 2996 |
STATUS current |
| 2997 |
DESCRIPTION |
| 2998 |
"Contains RTM information for an LU (Type 2). |
| 2999 |
Each entry is created by the Agent." |
| 3000 |
INDEX { snaLuRtmPuIndex, snaLuRtmLuIndex } |
| 3001 |
::= { snaLuRtmTable 1 } |
| 3002 |
|
| 3003 |
SnaLuRtmEntry ::= SEQUENCE { |
| 3004 |
snaLuRtmPuIndex |
| 3005 |
Integer32, |
| 3006 |
snaLuRtmLuIndex |
| 3007 |
Integer32, |
| 3008 |
snaLuRtmState |
| 3009 |
INTEGER, |
| 3010 |
snaLuRtmStateTime |
| 3011 |
TimeStamp, |
| 3012 |
snaLuRtmDef |
| 3013 |
INTEGER, |
| 3014 |
snaLuRtmBoundary1 |
| 3015 |
Integer32, |
| 3016 |
snaLuRtmBoundary2 |
| 3017 |
|
| 3018 |
|
| 3019 |
|
| 3020 |
<span class="grey">Kielczewski, Kostick & Shih [Page 54]</span></pre> |
| 3021 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-55" ></span> |
| 3022 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 3023 |
|
| 3024 |
|
| 3025 |
Integer32, |
| 3026 |
snaLuRtmBoundary3 |
| 3027 |
Integer32, |
| 3028 |
snaLuRtmBoundary4 |
| 3029 |
Integer32, |
| 3030 |
snaLuRtmCounter1 |
| 3031 |
Counter32, |
| 3032 |
snaLuRtmCounter2 |
| 3033 |
Counter32, |
| 3034 |
snaLuRtmCounter3 |
| 3035 |
Counter32, |
| 3036 |
snaLuRtmCounter4 |
| 3037 |
Counter32, |
| 3038 |
snaLuRtmOverFlows |
| 3039 |
Counter32, |
| 3040 |
snaLuRtmObjPercent |
| 3041 |
Integer32, |
| 3042 |
snaLuRtmObjRange |
| 3043 |
INTEGER, |
| 3044 |
snaLuRtmNumTrans |
| 3045 |
Integer32, |
| 3046 |
snaLuRtmLastRspTime |
| 3047 |
Integer32, |
| 3048 |
snaLuRtmAvgRspTime |
| 3049 |
Integer32 |
| 3050 |
} |
| 3051 |
|
| 3052 |
snaLuRtmPuIndex OBJECT-TYPE |
| 3053 |
SYNTAX Integer32 |
| 3054 |
MAX-ACCESS not-accessible |
| 3055 |
STATUS current |
| 3056 |
DESCRIPTION |
| 3057 |
"The value identifies the PU 2.0 with which this LU is |
| 3058 |
associated." |
| 3059 |
::= { snaLuRtmEntry 1 } |
| 3060 |
|
| 3061 |
snaLuRtmLuIndex OBJECT-TYPE |
| 3062 |
SYNTAX Integer32 |
| 3063 |
MAX-ACCESS not-accessible |
| 3064 |
STATUS current |
| 3065 |
DESCRIPTION |
| 3066 |
"The value uniquely identifies an LU in a PU 2.0." |
| 3067 |
::= { snaLuRtmEntry 2 } |
| 3068 |
|
| 3069 |
snaLuRtmState OBJECT-TYPE |
| 3070 |
SYNTAX INTEGER { |
| 3071 |
off(1), |
| 3072 |
on(2) |
| 3073 |
|
| 3074 |
|
| 3075 |
|
| 3076 |
<span class="grey">Kielczewski, Kostick & Shih [Page 55]</span></pre> |
| 3077 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-56" ></span> |
| 3078 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 3079 |
|
| 3080 |
|
| 3081 |
} |
| 3082 |
MAX-ACCESS read-only |
| 3083 |
STATUS current |
| 3084 |
DESCRIPTION |
| 3085 |
"The value indicates the current RTM state of an LU." |
| 3086 |
::= { snaLuRtmEntry 3 } |
| 3087 |
|
| 3088 |
snaLuRtmStateTime OBJECT-TYPE |
| 3089 |
SYNTAX TimeStamp |
| 3090 |
MAX-ACCESS read-only |
| 3091 |
STATUS current |
| 3092 |
DESCRIPTION |
| 3093 |
"The timestamp (e.g., the Agent's sysUpTime value) |
| 3094 |
when this session's RTM state (e.g., snaLuRtmState) |
| 3095 |
changes value." |
| 3096 |
::= { snaLuRtmEntry 4 } |
| 3097 |
|
| 3098 |
snaLuRtmDef OBJECT-TYPE |
| 3099 |
SYNTAX INTEGER { |
| 3100 |
firstChar(1), |
| 3101 |
kb(2), |
| 3102 |
cdeb(3) |
| 3103 |
} |
| 3104 |
MAX-ACCESS read-only |
| 3105 |
STATUS current |
| 3106 |
DESCRIPTION |
| 3107 |
"The value indicates the mode of measurement for this |
| 3108 |
RTM request. The values have following meaning: |
| 3109 |
firstChar(1) - time to first character on screen |
| 3110 |
kb(2) - time to keyboard usable by operator |
| 3111 |
cdeb(3) - time to Change Direction/End Bracket." |
| 3112 |
::= { snaLuRtmEntry 5 } |
| 3113 |
|
| 3114 |
snaLuRtmBoundary1 OBJECT-TYPE |
| 3115 |
SYNTAX Integer32 |
| 3116 |
MAX-ACCESS read-only |
| 3117 |
STATUS current |
| 3118 |
DESCRIPTION |
| 3119 |
"This object contains the value of the first boundary |
| 3120 |
in units of 1/10th of a second." |
| 3121 |
::= { snaLuRtmEntry 6 } |
| 3122 |
|
| 3123 |
snaLuRtmBoundary2 OBJECT-TYPE |
| 3124 |
SYNTAX Integer32 |
| 3125 |
MAX-ACCESS read-only |
| 3126 |
STATUS current |
| 3127 |
DESCRIPTION |
| 3128 |
"This object contains the value of the second boundary |
| 3129 |
|
| 3130 |
|
| 3131 |
|
| 3132 |
<span class="grey">Kielczewski, Kostick & Shih [Page 56]</span></pre> |
| 3133 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-57" ></span> |
| 3134 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 3135 |
|
| 3136 |
|
| 3137 |
in units of 1/10th of a second." |
| 3138 |
::= { snaLuRtmEntry 7 } |
| 3139 |
|
| 3140 |
snaLuRtmBoundary3 OBJECT-TYPE |
| 3141 |
SYNTAX Integer32 |
| 3142 |
MAX-ACCESS read-only |
| 3143 |
STATUS current |
| 3144 |
DESCRIPTION |
| 3145 |
"This object contains the value of the third boundary |
| 3146 |
in units of 1/10th of a second." |
| 3147 |
::= { snaLuRtmEntry 8 } |
| 3148 |
|
| 3149 |
snaLuRtmBoundary4 OBJECT-TYPE |
| 3150 |
SYNTAX Integer32 |
| 3151 |
MAX-ACCESS read-only |
| 3152 |
STATUS current |
| 3153 |
DESCRIPTION |
| 3154 |
"This object contains the value of the fourth boundary |
| 3155 |
in units of 1/10th of a second." |
| 3156 |
::= { snaLuRtmEntry 9 } |
| 3157 |
|
| 3158 |
snaLuRtmCounter1 OBJECT-TYPE |
| 3159 |
SYNTAX Counter32 |
| 3160 |
MAX-ACCESS read-only |
| 3161 |
STATUS current |
| 3162 |
DESCRIPTION |
| 3163 |
"This value indicates the number of transactions which |
| 3164 |
fall in the range specified by the first boundary." |
| 3165 |
::= { snaLuRtmEntry 10 } |
| 3166 |
|
| 3167 |
snaLuRtmCounter2 OBJECT-TYPE |
| 3168 |
SYNTAX Counter32 |
| 3169 |
MAX-ACCESS read-only |
| 3170 |
STATUS current |
| 3171 |
DESCRIPTION |
| 3172 |
"This value indicates the number of transactions which |
| 3173 |
fall in the range specified by the second boundary." |
| 3174 |
::= { snaLuRtmEntry 11 } |
| 3175 |
|
| 3176 |
snaLuRtmCounter3 OBJECT-TYPE |
| 3177 |
SYNTAX Counter32 |
| 3178 |
MAX-ACCESS read-only |
| 3179 |
STATUS current |
| 3180 |
DESCRIPTION |
| 3181 |
"This value indicates the number of transactions which |
| 3182 |
fall in the range specified by the third boundary." |
| 3183 |
::= { snaLuRtmEntry 12 } |
| 3184 |
|
| 3185 |
|
| 3186 |
|
| 3187 |
|
| 3188 |
<span class="grey">Kielczewski, Kostick & Shih [Page 57]</span></pre> |
| 3189 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-58" ></span> |
| 3190 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 3191 |
|
| 3192 |
|
| 3193 |
snaLuRtmCounter4 OBJECT-TYPE |
| 3194 |
SYNTAX Counter32 |
| 3195 |
MAX-ACCESS read-only |
| 3196 |
STATUS current |
| 3197 |
DESCRIPTION |
| 3198 |
"This value indicates the number of transactions which |
| 3199 |
fall in the range specified by the fourth boundary." |
| 3200 |
::= { snaLuRtmEntry 13 } |
| 3201 |
|
| 3202 |
snaLuRtmOverFlows OBJECT-TYPE |
| 3203 |
SYNTAX Counter32 |
| 3204 |
MAX-ACCESS read-only |
| 3205 |
STATUS current |
| 3206 |
DESCRIPTION |
| 3207 |
"This value indicates the number of transactions which |
| 3208 |
exceed the highest range specified by the |
| 3209 |
boundaries." |
| 3210 |
::= { snaLuRtmEntry 14 } |
| 3211 |
|
| 3212 |
snaLuRtmObjPercent OBJECT-TYPE |
| 3213 |
SYNTAX Integer32 |
| 3214 |
MAX-ACCESS read-only |
| 3215 |
STATUS current |
| 3216 |
DESCRIPTION |
| 3217 |
"This value indicates the desired percentage of |
| 3218 |
transactions which should be under a designated |
| 3219 |
boundary range indicated by snaLuRtmObjRange." |
| 3220 |
::= { snaLuRtmEntry 15 } |
| 3221 |
|
| 3222 |
snaLuRtmObjRange OBJECT-TYPE |
| 3223 |
SYNTAX INTEGER { |
| 3224 |
other(1), |
| 3225 |
range1(2), |
| 3226 |
range2(3), |
| 3227 |
range3(4), |
| 3228 |
range4(5), |
| 3229 |
range5(6) |
| 3230 |
} |
| 3231 |
MAX-ACCESS read-only |
| 3232 |
STATUS current |
| 3233 |
DESCRIPTION |
| 3234 |
"This value indicates the designated boundary range to |
| 3235 |
which the snaLuRtmObject refers. |
| 3236 |
The values have the following meanings: |
| 3237 |
other(1) - not specified |
| 3238 |
range1(2) - less than boundary 1 |
| 3239 |
range2(3) - between boundary 1 and 2 |
| 3240 |
range3(4) - between boundary 2 and 3 |
| 3241 |
|
| 3242 |
|
| 3243 |
|
| 3244 |
<span class="grey">Kielczewski, Kostick & Shih [Page 58]</span></pre> |
| 3245 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-59" ></span> |
| 3246 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 3247 |
|
| 3248 |
|
| 3249 |
range4(5) - between boundary 3 and 4 |
| 3250 |
range5(6) - greater than boundary 4." |
| 3251 |
::= { snaLuRtmEntry 16 } |
| 3252 |
|
| 3253 |
snaLuRtmNumTrans OBJECT-TYPE |
| 3254 |
SYNTAX Integer32 |
| 3255 |
MAX-ACCESS read-only |
| 3256 |
STATUS current |
| 3257 |
DESCRIPTION |
| 3258 |
"This value indicates the total number of transactions |
| 3259 |
executed since the RTM monitoring began (i.e., |
| 3260 |
snaLuRtmState |
| 3261 |
changed to `on(2)') for this LU." |
| 3262 |
::= { snaLuRtmEntry 17 } |
| 3263 |
|
| 3264 |
snaLuRtmLastRspTime OBJECT-TYPE |
| 3265 |
SYNTAX Integer32 |
| 3266 |
MAX-ACCESS read-only |
| 3267 |
STATUS current |
| 3268 |
DESCRIPTION |
| 3269 |
"This value indicates the response time for the last |
| 3270 |
transaction in units of 1/10th of a second." |
| 3271 |
::= { snaLuRtmEntry 18 } |
| 3272 |
|
| 3273 |
snaLuRtmAvgRspTime OBJECT-TYPE |
| 3274 |
SYNTAX Integer32 |
| 3275 |
MAX-ACCESS read-only |
| 3276 |
STATUS current |
| 3277 |
DESCRIPTION |
| 3278 |
"This value indicates the average response time for all |
| 3279 |
transactions in units of 1/10th of a second." |
| 3280 |
::= { snaLuRtmEntry 19 } |
| 3281 |
|
| 3282 |
|
| 3283 |
|
| 3284 |
-- *************************************************************** |
| 3285 |
-- Conformance information |
| 3286 |
-- *************************************************************** |
| 3287 |
|
| 3288 |
snanauConformance OBJECT IDENTIFIER ::= { snanauMIB 2 } |
| 3289 |
|
| 3290 |
snanauCompliances OBJECT IDENTIFIER ::= {snanauConformance 1 } |
| 3291 |
snanauGroups OBJECT IDENTIFIER ::= {snanauConformance 2 } |
| 3292 |
|
| 3293 |
-- Compliance statements |
| 3294 |
snanauCompliance MODULE-COMPLIANCE |
| 3295 |
STATUS current |
| 3296 |
DESCRIPTION |
| 3297 |
|
| 3298 |
|
| 3299 |
|
| 3300 |
<span class="grey">Kielczewski, Kostick & Shih [Page 59]</span></pre> |
| 3301 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-60" ></span> |
| 3302 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 3303 |
|
| 3304 |
|
| 3305 |
"The compliance statement for the SNMPv2 entities |
| 3306 |
which implement the snanau MIB." |
| 3307 |
|
| 3308 |
MODULE -- this module |
| 3309 |
|
| 3310 |
-- Unconditionally mandatory groups |
| 3311 |
MANDATORY-GROUPS { snaNodeGroup, |
| 3312 |
snaLuGroup, |
| 3313 |
snaSessionGroup } |
| 3314 |
|
| 3315 |
-- Conditionally mandatory groups |
| 3316 |
GROUP snaPu20Group |
| 3317 |
DESCRIPTION |
| 3318 |
"The snaPu20Group is mandatory only for those |
| 3319 |
entities which implement PU type 2.0" |
| 3320 |
|
| 3321 |
GROUP snaMgtToolsRtmGroup |
| 3322 |
DESCRIPTION |
| 3323 |
"The snaMgtToolsGroup is mandatory only for |
| 3324 |
those entities which implement LU type 2 |
| 3325 |
and RTM." |
| 3326 |
|
| 3327 |
-- Refinement of requirements for objects access. |
| 3328 |
-- The Agent which does not implement row creation for |
| 3329 |
-- snaNodeAdminTable, snaNodeLinkAdminTable and |
| 3330 |
-- snaLuAdminTable must at least accept |
| 3331 |
-- objects modification (read-write access instead of |
| 3332 |
-- read-create). |
| 3333 |
|
| 3334 |
OBJECT snaNodeAdminName |
| 3335 |
MIN-ACCESS read-write |
| 3336 |
DESCRIPTION |
| 3337 |
"An Agent is required to implement read-write |
| 3338 |
access to this object." |
| 3339 |
|
| 3340 |
OBJECT snaNodeAdminType |
| 3341 |
MIN-ACCESS read-write |
| 3342 |
DESCRIPTION |
| 3343 |
"An Agent is required to implement read-write |
| 3344 |
access to this object." |
| 3345 |
|
| 3346 |
OBJECT snaNodeAdminXidFormat |
| 3347 |
MIN-ACCESS read-write |
| 3348 |
DESCRIPTION |
| 3349 |
"An Agent is required to implement read-write |
| 3350 |
access to this object." |
| 3351 |
|
| 3352 |
OBJECT snaNodeAdminBlockNum |
| 3353 |
|
| 3354 |
|
| 3355 |
|
| 3356 |
<span class="grey">Kielczewski, Kostick & Shih [Page 60]</span></pre> |
| 3357 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-61" ></span> |
| 3358 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 3359 |
|
| 3360 |
|
| 3361 |
MIN-ACCESS read-write |
| 3362 |
DESCRIPTION |
| 3363 |
"An Agent is required to implement read-write |
| 3364 |
access to this object." |
| 3365 |
|
| 3366 |
OBJECT snaNodeAdminIdNum |
| 3367 |
MIN-ACCESS read-write |
| 3368 |
DESCRIPTION |
| 3369 |
"An Agent is required to implement read-write |
| 3370 |
access to this object." |
| 3371 |
|
| 3372 |
OBJECT snaNodeAdminEnablingMethod |
| 3373 |
MIN-ACCESS read-write |
| 3374 |
DESCRIPTION |
| 3375 |
"An Agent is required to implement read-write |
| 3376 |
access to this object." |
| 3377 |
|
| 3378 |
OBJECT snaNodeAdminLuTermDefault |
| 3379 |
MIN-ACCESS read-write |
| 3380 |
DESCRIPTION |
| 3381 |
"An Agent is required to implement read-write |
| 3382 |
access to this object." |
| 3383 |
|
| 3384 |
OBJECT snaNodeAdminMaxLu |
| 3385 |
MIN-ACCESS read-write |
| 3386 |
DESCRIPTION |
| 3387 |
"An Agent is required to implement read-write |
| 3388 |
access to this object." |
| 3389 |
|
| 3390 |
OBJECT snaNodeAdminHostDescription |
| 3391 |
MIN-ACCESS read-write |
| 3392 |
DESCRIPTION |
| 3393 |
"An Agent is required to implement read-write |
| 3394 |
access to this object." |
| 3395 |
|
| 3396 |
OBJECT snaNodeAdminStopMethod |
| 3397 |
MIN-ACCESS read-write |
| 3398 |
DESCRIPTION |
| 3399 |
"An Agent is required to implement read-write |
| 3400 |
access to this object." |
| 3401 |
|
| 3402 |
OBJECT snaNodeAdminState |
| 3403 |
MIN-ACCESS read-write |
| 3404 |
DESCRIPTION |
| 3405 |
"An Agent is required to implement read-write |
| 3406 |
access to this object." |
| 3407 |
|
| 3408 |
OBJECT snaNodeLinkAdminSpecific |
| 3409 |
|
| 3410 |
|
| 3411 |
|
| 3412 |
<span class="grey">Kielczewski, Kostick & Shih [Page 61]</span></pre> |
| 3413 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-62" ></span> |
| 3414 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 3415 |
|
| 3416 |
|
| 3417 |
MIN-ACCESS read-write |
| 3418 |
DESCRIPTION |
| 3419 |
"An Agent is required to implement read-write |
| 3420 |
access to this object." |
| 3421 |
|
| 3422 |
OBJECT snaNodeLinkAdminMaxPiu |
| 3423 |
MIN-ACCESS read-write |
| 3424 |
DESCRIPTION |
| 3425 |
"An Agent is required to implement read-write |
| 3426 |
access to this object." |
| 3427 |
|
| 3428 |
OBJECT snaLuAdminName |
| 3429 |
MIN-ACCESS read-write |
| 3430 |
DESCRIPTION |
| 3431 |
"An Agent is required to implement read-write |
| 3432 |
access to this object." |
| 3433 |
|
| 3434 |
OBJECT snaLuAdminSnaName |
| 3435 |
MIN-ACCESS read-write |
| 3436 |
DESCRIPTION |
| 3437 |
"An Agent is required to implement read-write |
| 3438 |
access to this object." |
| 3439 |
|
| 3440 |
OBJECT snaLuAdminType |
| 3441 |
MIN-ACCESS read-write |
| 3442 |
DESCRIPTION |
| 3443 |
"An Agent is required to implement read-write |
| 3444 |
access to this object." |
| 3445 |
|
| 3446 |
OBJECT snaLuAdminDepType |
| 3447 |
MIN-ACCESS read-write |
| 3448 |
DESCRIPTION |
| 3449 |
"An Agent is required to implement read-write |
| 3450 |
access to this object." |
| 3451 |
|
| 3452 |
OBJECT snaLuAdminLocalAddress |
| 3453 |
MIN-ACCESS read-write |
| 3454 |
DESCRIPTION |
| 3455 |
"An Agent is required to implement read-write |
| 3456 |
access to this object." |
| 3457 |
|
| 3458 |
OBJECT snaLuAdminDisplayModel |
| 3459 |
MIN-ACCESS read-write |
| 3460 |
DESCRIPTION |
| 3461 |
"An Agent is required to implement read-write |
| 3462 |
access to this object." |
| 3463 |
|
| 3464 |
OBJECT snaLuAdminTerm |
| 3465 |
|
| 3466 |
|
| 3467 |
|
| 3468 |
<span class="grey">Kielczewski, Kostick & Shih [Page 62]</span></pre> |
| 3469 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-63" ></span> |
| 3470 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 3471 |
|
| 3472 |
|
| 3473 |
MIN-ACCESS read-write |
| 3474 |
DESCRIPTION |
| 3475 |
"An Agent is required to implement read-write |
| 3476 |
access to this object." |
| 3477 |
|
| 3478 |
::= {snanauCompliances 1 } |
| 3479 |
|
| 3480 |
|
| 3481 |
-- Units of conformance |
| 3482 |
|
| 3483 |
snaNodeGroup OBJECT-GROUP |
| 3484 |
OBJECTS {snaNodeAdminIndex, |
| 3485 |
snaNodeAdminName, |
| 3486 |
snaNodeAdminType, |
| 3487 |
snaNodeAdminXidFormat, |
| 3488 |
snaNodeAdminBlockNum, |
| 3489 |
snaNodeAdminIdNum, |
| 3490 |
snaNodeAdminEnablingMethod, |
| 3491 |
snaNodeAdminLuTermDefault, |
| 3492 |
snaNodeAdminMaxLu, |
| 3493 |
snaNodeAdminHostDescription, |
| 3494 |
snaNodeAdminStopMethod, |
| 3495 |
snaNodeAdminState, |
| 3496 |
snaNodeAdminRowStatus, |
| 3497 |
snaNodeAdminTableLastChange, |
| 3498 |
snaNodeOperName, |
| 3499 |
snaNodeOperType, |
| 3500 |
snaNodeOperXidFormat, |
| 3501 |
snaNodeOperBlockNum, |
| 3502 |
snaNodeOperIdNum, |
| 3503 |
snaNodeOperEnablingMethod, |
| 3504 |
snaNodeOperLuTermDefault, |
| 3505 |
snaNodeOperMaxLu, |
| 3506 |
snaNodeOperHostDescription, |
| 3507 |
snaNodeOperStopMethod, |
| 3508 |
snaNodeOperState, |
| 3509 |
snaNodeOperHostSscpId, |
| 3510 |
snaNodeOperStartTime, |
| 3511 |
snaNodeOperLastStateChange, |
| 3512 |
snaNodeOperActFailures, |
| 3513 |
snaNodeOperActFailureReason, |
| 3514 |
snaNodeOperTableLastChange, |
| 3515 |
snaNodeLinkAdminIndex, |
| 3516 |
snaNodeLinkAdminSpecific, |
| 3517 |
snaNodeLinkAdminMaxPiu, |
| 3518 |
snaNodeLinkAdminRowStatus, |
| 3519 |
snaNodeLinkAdminTableLastChange, |
| 3520 |
snaNodeLinkOperSpecific, |
| 3521 |
|
| 3522 |
|
| 3523 |
|
| 3524 |
<span class="grey">Kielczewski, Kostick & Shih [Page 63]</span></pre> |
| 3525 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-64" ></span> |
| 3526 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 3527 |
|
| 3528 |
|
| 3529 |
snaNodeLinkOperMaxPiu, |
| 3530 |
snaNodeLinkOperTableLastChange } |
| 3531 |
STATUS current |
| 3532 |
DESCRIPTION |
| 3533 |
"A collection of objects providing the |
| 3534 |
instrumentation of SNA nodes." |
| 3535 |
::= { snanauGroups 1 } |
| 3536 |
|
| 3537 |
snaLuGroup OBJECT-GROUP |
| 3538 |
OBJECTS { snaLuAdminLuIndex, |
| 3539 |
snaLuAdminName, |
| 3540 |
snaLuAdminSnaName, |
| 3541 |
snaLuAdminType, |
| 3542 |
snaLuAdminDepType, |
| 3543 |
snaLuAdminLocalAddress, |
| 3544 |
snaLuAdminDisplayModel, |
| 3545 |
snaLuAdminTerm, |
| 3546 |
snaLuAdminRowStatus, |
| 3547 |
snaLuOperName, |
| 3548 |
snaLuOperSnaName, |
| 3549 |
snaLuOperType, |
| 3550 |
snaLuOperDepType, |
| 3551 |
snaLuOperLocalAddress, |
| 3552 |
snaLuOperDisplayModel, |
| 3553 |
snaLuOperTerm, |
| 3554 |
snaLuOperState, |
| 3555 |
snaLuOperSessnCount } |
| 3556 |
STATUS current |
| 3557 |
DESCRIPTION |
| 3558 |
"A collection of objects providing the |
| 3559 |
instrumentation of SNA LUs." |
| 3560 |
::= { snanauGroups 2 } |
| 3561 |
|
| 3562 |
snaSessionGroup OBJECT-GROUP |
| 3563 |
OBJECTS { snaLuSessnIndex, |
| 3564 |
snaLuSessnLocalApplName, |
| 3565 |
snaLuSessnRemoteLuName, |
| 3566 |
snaLuSessnMaxSndRuSize, |
| 3567 |
snaLuSessnMaxRcvRuSize, |
| 3568 |
snaLuSessnSndPacingSize, |
| 3569 |
snaLuSessnRcvPacingSize, |
| 3570 |
snaLuSessnActiveTime, |
| 3571 |
snaLuSessnAdminState, |
| 3572 |
snaLuSessnOperState, |
| 3573 |
snaLuSessnSenseData, |
| 3574 |
snaLuSessnTerminationRu, |
| 3575 |
snaLuSessnUnbindType, |
| 3576 |
snaLuSessnStatsSentBytes, |
| 3577 |
|
| 3578 |
|
| 3579 |
|
| 3580 |
<span class="grey">Kielczewski, Kostick & Shih [Page 64]</span></pre> |
| 3581 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-65" ></span> |
| 3582 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 3583 |
|
| 3584 |
|
| 3585 |
snaLuSessnStatsReceivedBytes, |
| 3586 |
snaLuSessnStatsSentRus, |
| 3587 |
snaLuSessnStatsReceivedRus, |
| 3588 |
snaLuSessnStatsSentNegativeResps, |
| 3589 |
snaLuSessnStatsReceivedNegativeResps } |
| 3590 |
STATUS current |
| 3591 |
DESCRIPTION |
| 3592 |
"A collection of objects providing the |
| 3593 |
instrumentation of SNA sessions." |
| 3594 |
::= { snanauGroups 3 } |
| 3595 |
|
| 3596 |
snaPu20Group OBJECT-GROUP |
| 3597 |
OBJECTS { snaPu20StatsSentBytes, |
| 3598 |
snaPu20StatsReceivedBytes, |
| 3599 |
snaPu20StatsSentPius, |
| 3600 |
snaPu20StatsReceivedPius, |
| 3601 |
snaPu20StatsSentNegativeResps, |
| 3602 |
snaPu20StatsReceivedNegativeResps, |
| 3603 |
snaPu20StatsActLus, |
| 3604 |
snaPu20StatsInActLus, |
| 3605 |
snaPu20StatsBindLus } |
| 3606 |
STATUS current |
| 3607 |
DESCRIPTION |
| 3608 |
"A collection of objects providing the |
| 3609 |
instrumentation of PU 2.0." |
| 3610 |
::= { snanauGroups 4 } |
| 3611 |
|
| 3612 |
snaMgtToolsRtmGroup OBJECT-GROUP |
| 3613 |
OBJECTS { snaLuRtmPuIndex, |
| 3614 |
snaLuRtmLuIndex, |
| 3615 |
snaLuRtmState, |
| 3616 |
snaLuRtmStateTime, |
| 3617 |
snaLuRtmDef, |
| 3618 |
snaLuRtmBoundary1, |
| 3619 |
snaLuRtmBoundary2, |
| 3620 |
snaLuRtmBoundary3, |
| 3621 |
snaLuRtmBoundary4, |
| 3622 |
snaLuRtmCounter1, |
| 3623 |
snaLuRtmCounter2, |
| 3624 |
snaLuRtmCounter3, |
| 3625 |
snaLuRtmCounter4, |
| 3626 |
snaLuRtmOverFlows, |
| 3627 |
snaLuRtmObjPercent, |
| 3628 |
snaLuRtmObjRange, |
| 3629 |
snaLuRtmNumTrans, |
| 3630 |
snaLuRtmLastRspTime, |
| 3631 |
snaLuRtmAvgRspTime } |
| 3632 |
STATUS current |
| 3633 |
|
| 3634 |
|
| 3635 |
|
| 3636 |
<span class="grey">Kielczewski, Kostick & Shih [Page 65]</span></pre> |
| 3637 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-66" ></span> |
| 3638 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 3639 |
|
| 3640 |
|
| 3641 |
DESCRIPTION |
| 3642 |
"A collection of objects providing the |
| 3643 |
instrumentation of RTM for SNA LU 2.0." |
| 3644 |
::= { snanauGroups 5 } |
| 3645 |
|
| 3646 |
-- end of conformance statement |
| 3647 |
|
| 3648 |
|
| 3649 |
END |
| 3650 |
|
| 3651 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgments</span> |
| 3652 |
|
| 3653 |
The following people greatly contributed to the work on this MIB |
| 3654 |
document: Michael Allen, Robin Cheng, Bill Kwan. Special thanks goes |
| 3655 |
to Dave Perkins for his assistance in reviewing this MIB proposal. |
| 3656 |
|
| 3657 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span> |
| 3658 |
|
| 3659 |
[<a id="ref-1">1</a>] IBM, Systems Network Architecture Technical Overview, GC 30- |
| 3660 |
3073-3, March, 1991. |
| 3661 |
|
| 3662 |
[<a id="ref-2">2</a>] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure |
| 3663 |
of Management Information for version 2 of the Simple Network |
| 3664 |
Management Protocol (SNMPv2)", <a href="./rfc1442">RFC 1442</a>, SNMP Research, Inc., |
| 3665 |
Hughes LAN Systems, Dover Beach Consulting, Inc., Carnegie Mellon |
| 3666 |
University, April 1993. |
| 3667 |
|
| 3668 |
[<a id="ref-3">3</a>] McCloghrie, K., and M. Rose, "Management Information Base for |
| 3669 |
Network Management of TCP/IP-based internets - MIB-II", STD 17, |
| 3670 |
<a href="./rfc1213">RFC 1213</a>, Hughes LAN Systems, Performance Systems International, |
| 3671 |
March 1991. |
| 3672 |
|
| 3673 |
[<a id="ref-4">4</a>] Galvin, J., and K. McCloghrie, "Administrative Model for version |
| 3674 |
2 of the Simple Network Management Protocol (SNMPv2)", <a href="./rfc1445">RFC 1445</a>, |
| 3675 |
Trusted Information Systems, Hughes LAN Systems, April 1993. |
| 3676 |
|
| 3677 |
[<a id="ref-5">5</a>] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol |
| 3678 |
Operations for version 2 of the Simple Network Management |
| 3679 |
Protocol (SNMPv2)", <a href="./rfc1448">RFC 1448</a>, SNMP Research, Inc., Hughes LAN |
| 3680 |
Systems, Dover Beach Consulting, Inc., Carnegie Mellon |
| 3681 |
University, April 1993. |
| 3682 |
|
| 3683 |
[<a id="ref-6">6</a>] Hilgeman, J., Nix, S., Bartky, A., Clark, W., "Definitions of |
| 3684 |
Managed Objects for SNA Data Link Control: SDLC", Work in |
| 3685 |
Progress. |
| 3686 |
|
| 3687 |
|
| 3688 |
|
| 3689 |
|
| 3690 |
|
| 3691 |
|
| 3692 |
<span class="grey">Kielczewski, Kostick & Shih [Page 66]</span></pre> |
| 3693 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-67" ></span> |
| 3694 |
<span class="grey"><a href="./rfc1665">RFC 1665</a> SNANAU MIB July 1994</span> |
| 3695 |
|
| 3696 |
|
| 3697 |
[<a id="ref-7">7</a>] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual |
| 3698 |
Conventions for version 2 of the Simple Network Management |
| 3699 |
Protocol (SNMPv2)", <a href="./rfc1443">RFC 1443</a>, SNMP Research, Inc., Hughes LAN |
| 3700 |
Systems, Dover Beach Consulting, Inc., Carnegie Mellon |
| 3701 |
University, April 1993. |
| 3702 |
|
| 3703 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span> |
| 3704 |
|
| 3705 |
Security issues are not discussed in this memo. |
| 3706 |
|
| 3707 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Authors' Addresses</span> |
| 3708 |
|
| 3709 |
Zbigniew Kielczewski |
| 3710 |
Eicon Technology Corporation |
| 3711 |
2196 32nd Avenue |
| 3712 |
Montreal, Quebec, Canada H8T 3H7 |
| 3713 |
|
| 3714 |
Phone: 1 514 631 2592 |
| 3715 |
EMail: [email protected] |
| 3716 |
|
| 3717 |
|
| 3718 |
Deirdre Kostick |
| 3719 |
Bell Communications Research |
| 3720 |
Red Bank, NJ 07701 |
| 3721 |
|
| 3722 |
Phone: 1 908 758 2642 |
| 3723 |
EMail: [email protected] |
| 3724 |
|
| 3725 |
|
| 3726 |
Kitty Shih |
| 3727 |
Novell |
| 3728 |
890 Ross Drive |
| 3729 |
Sunnyvale, CA 94089 |
| 3730 |
|
| 3731 |
Phone: 1 408 747 4305 |
| 3732 |
EMail: [email protected] |
| 3733 |
|
| 3734 |
|
| 3735 |
|
| 3736 |
|
| 3737 |
|
| 3738 |
|
| 3739 |
|
| 3740 |
|
| 3741 |
|
| 3742 |
|
| 3743 |
|
| 3744 |
|
| 3745 |
|
| 3746 |
|
| 3747 |
|
| 3748 |
Kielczewski, Kostick & Shih [Page 67] |
| 3749 |
</pre> |