Debian Codegraph @

rfc4939.html

raw
1 <pre>Network Working Group K. Gibbons
2 Request for Comments: 4939 2Wire, Inc.
3 Category: Standards Track G. Ramkumar
4 SnapTell, Inc.
5 S. Kipp
6 Brocade, Inc.
7 July 2007
8
9
10 <span class="h1">Definitions of Managed Objects for iSNS</span>
11 <span class="h1">(Internet Storage Name Service)</span>
12
13 Status of This Memo
14
15 This document specifies an Internet standards track protocol for the
16 Internet community, and requests discussion and suggestions for
17 improvements. Please refer to the current edition of the "Internet
18 Official Protocol Standards" (STD 1) for the standardization state
19 and status of this protocol. Distribution of this memo is unlimited.
20
21 Copyright Notice
22
23 Copyright (C) The IETF Trust (2007).
24
25 Abstract
26
27 The iSNS (Internet Storage Name Service) protocol provides storage
28 name service functionality on an IP network that is being used for
29 iSCSI (Internet Small Computer System Interface) or iFCP (Internet
30 Fibre Channel Protocol) storage. This document provides a mechanism
31 to monitor multiple iSNS Servers, including information about
32 registered objects in an iSNS Server.
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Gibbons, et al. Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
55
56
57 Table of Contents
58
59 <a href="#section-1">1</a>. The Internet-Standard Management Framework ......................<a href="#page-3">3</a>
60 <a href="#section-2">2</a>. Introduction ....................................................<a href="#page-3">3</a>
61 <a href="#section-2.1">2.1</a>. Requirement Levels .........................................<a href="#page-3">3</a>
62 <a href="#section-3">3</a>. Technical Description ...........................................<a href="#page-4">4</a>
63 <a href="#section-3.1">3.1</a>. iSNS Registered Objects ....................................<a href="#page-4">4</a>
64 <a href="#section-3.2">3.2</a>. iSNS MIB Structure .........................................<a href="#page-5">5</a>
65 <a href="#section-3.3">3.3</a>. iSNS Server Info ...........................................<a href="#page-5">5</a>
66 <a href="#section-3.3.1">3.3.1</a>. Control Node Information ............................<a href="#page-6">6</a>
67 <a href="#section-3.3.2">3.3.2</a>. Discovery Domain Set (DDS) ..........................<a href="#page-6">6</a>
68 <a href="#section-3.3.3">3.3.3</a>. Discovery Domain (DD) ...............................<a href="#page-6">6</a>
69 <a href="#section-3.3.4">3.3.4</a>. Registered Storage Objects ..........................<a href="#page-6">6</a>
70 <a href="#section-3.3.4.1">3.3.4.1</a>. Registered Entities ........................<a href="#page-6">6</a>
71 <a href="#section-3.3.4.2">3.3.4.2</a>. Registered Portals .........................<a href="#page-6">6</a>
72 <a href="#section-3.3.4.3">3.3.4.3</a>. Registered Portal Groups ...................<a href="#page-7">7</a>
73 <a href="#section-3.3.4.4">3.3.4.4</a>. Registered iSCSI Nodes .....................<a href="#page-7">7</a>
74 <a href="#section-3.3.4.5">3.3.4.5</a>. Registered FC Ports ........................<a href="#page-7">7</a>
75 <a href="#section-3.3.4.6">3.3.4.6</a>. Registered FC Nodes ........................<a href="#page-7">7</a>
76 <a href="#section-3.4">3.4</a>. Multiple Server Instances ..................................<a href="#page-7">7</a>
77 <a href="#section-3.5">3.5</a>. iSNS Notifications .........................................<a href="#page-7">7</a>
78 <a href="#section-4">4</a>. MIB References ..................................................<a href="#page-7">7</a>
79 <a href="#section-5">5</a>. MIB Module ......................................................<a href="#page-8">8</a>
80 <a href="#section-6">6</a>. IANA Considerations ............................................<a href="#page-75">75</a>
81 <a href="#section-7">7</a>. Security Considerations ........................................<a href="#page-76">76</a>
82 <a href="#section-8">8</a>. Normative References ...........................................<a href="#page-77">77</a>
83 <a href="#section-9">9</a>. Informative References .........................................<a href="#page-78">78</a>
84 <a href="#section-10">10</a>. Acknowledgements ..............................................<a href="#page-78">78</a>
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108 <span class="grey">Gibbons, et al. Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
111
112
113 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. The Internet-Standard Management Framework</span>
114
115 For a detailed overview of the documents that describe the current
116 Internet-Standard Management Framework, please refer to <a href="./rfc3410#section-7">section&nbsp;7 of
117 RFC 3410</a> [<a href="./rfc3410" title="&quot;Introduction and Applicability Statements for Internet- Standard Management Framework&quot;">RFC3410</a>].
118
119 Managed objects are accessed via a virtual information store, termed
120 the Management Information Base or MIB. MIB objects are generally
121 accessed through the Simple Network Management Protocol (SNMP).
122 Objects in the MIB are defined using the mechanisms defined in the
123 Structure of Management Information (SMI). This memo specifies a MIB
124 module that is compliant to the SMIv2, which is described in STD 58,
125 <a href="./rfc2578">RFC 2578</a> [<a href="./rfc2578" title="&quot;Structure of Management Information Version 2 (SMIv2)&quot;">RFC2578</a>], STD 58, <a href="./rfc2579">RFC 2579</a> [<a href="./rfc2579" title="&quot;Textual Conventions for SMIv2&quot;">RFC2579</a>] and STD 58, <a href="./rfc2580">RFC 2580</a>
126 [<a href="./rfc2580" title="&quot;Conformance Statements for SMIv2&quot;">RFC2580</a>].
127
128 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Introduction</span>
129
130 The iSNS protocol, as described in <a href="./rfc4171">RFC 4171</a> [<a href="./rfc4171" title="&quot;Internet Storage Name Service (iSNS)&quot;">RFC4171</a>], can be used by
131 IP-based storage devices for dynamic registration and discovery of
132 other storage devices in the network. It has the capability to group
133 devices into storage Discovery Domains, and Discovery Domains into
134 Discovery Domain Sets. The iSNS MIB is designed to allow Simple
135 Network Management Protocol (SNMP) to be used to monitor iSNS servers
136 supporting iSCSI [<a href="./rfc3720" title="&quot;Internet Small Computer Systems Interface (iSCSI)&quot;">RFC3720</a>] and iFCP [<a href="./rfc4172" title="&quot;iFCP - A Protocol for Internet Fibre Channel Storage Networking&quot;">RFC4172</a>].
137
138 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Requirement Levels</span>
139
140 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
141 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
142 document are to be interpreted as described in [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164 <span class="grey">Gibbons, et al. Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
167
168
169 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Technical Description</span>
170
171 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. iSNS Registered Objects</span>
172
173 The following entity relationship figure indicates the objects that
174 can be registered in the iSNS, and their relationship to each other.
175
176 +--------------+ +-----------+
177 | NETWORK |1 *| |
178 | ENTITY |----| PORTAL |
179 | | | |
180 +--------------+ +-----------+
181 |1 |1 |*
182 | | |
183 | |* |
184 | +----------+ |
185 | | PORTAL | |
186 | | GROUP | |
187 | +----------+ |
188 | |* |
189 | | |
190 |* |1 |*
191 +----------+ +-------------+ +----------+ +-----------+
192 | FC |1 *| STORAGE |* *| DISCOVERY|* *| DISCOVERY |
193 | DEVICE |----| NODE |----| DOMAIN |----| DOMAIN |
194 | | | | | | | SET |
195 +----------+ +-------------+ +----------+ +-----------+
196
197 * represents 0 to many possible relationships
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220 <span class="grey">Gibbons, et al. Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
223
224
225 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. iSNS MIB Structure</span>
226
227 The MIB is divided into sections for iSNS server information, iSNS
228 server registered objects information, and iSNS notifications.
229
230 +--------------+ +--------------+
231 | MANAGED iSNS |1 *| CONTROL NODE |
232 | SERVER |----| INFO |
233 | INFO | +--------------+
234 +--------------+
235 |1 |1
236 | | +--------------+
237 | | *| DDS AND DD |
238 | +------| INFO |
239 | | |
240 | +--------------+
241 |
242 | +-------------+
243 | *| REGISTERED |
244 +------------| ENTITIES |
245 | INFO |
246 +-------------+
247 +-----------------+
248 | iSNS |
249 | NOTIFICATION |
250 | INFO |
251 +-----------------+
252
253 The sections that are required to implement are for iSNS Server
254 management and notification.
255
256 <span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. iSNS Server Info</span>
257
258 The isnsServerInfo section provides the ability to monitor multiple
259 iSNS Server instances. The isnsServerTable table provides
260 information on each server instance. This table is indexed by the
261 variable isnsServerIndex. The table indicates current settings for
262 each iSNS server being managed. The network address, TCP and UDP
263 ports being used by a server for iSNSP registrations and queries can
264 be determined from this table.
265
266 The count of objects registered in each iSNS server instance is shown
267 in the table isnsNumObjectsTable. The provides a summary of the
268 number Discovery Domain Sets, Discovery Domains, Entities, Portals,
269 Portal Groups, iSCSI Nodes, and iFCP FC Nodes and Ports.
270
271
272
273
274
275
276 <span class="grey">Gibbons, et al. Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
279
280
281 <span class="h4"><a class="selflink" id="section-3.3.1" href="#section-3.3.1">3.3.1</a>. Control Node Information</span>
282
283 As defined in the iSNS specification, Control Nodes are objects that
284 have been registered with the server and are allowed to manage the
285 iSNS server. These Control Nodes are identified by their iSCSI Node
286 Name or iFCP FC Port Name. The isnsControlNodeInfo section of the
287 MIB provides the ability to view the currently registered set of
288 iSCSI and iFCP control nodes.
289
290 <span class="h4"><a class="selflink" id="section-3.3.2" href="#section-3.3.2">3.3.2</a>. Discovery Domain Set (DDS)</span>
291
292 The isnsDdsInfo section provides information on each registered DDS,
293 the Discovery Domain members of each DDS, for each iSNS Server
294 instance being managed. DDSs provide a method to group multiple
295 Discovery Domains for easier control. As described in the iSNS
296 Specification [<a href="./rfc4171" title="&quot;Internet Storage Name Service (iSNS)&quot;">RFC4171</a>], a DDS can be enabled or disabled, which in
297 turn enables or disables the member Discovery Domains. Discovery
298 Domains that are contained in an enabled DDS are then enforced by an
299 iSNS Server.
300
301 <span class="h4"><a class="selflink" id="section-3.3.3" href="#section-3.3.3">3.3.3</a>. Discovery Domain (DD)</span>
302
303 The isnsDdInfo section provides information on each registered DD,
304 and the DD members, for each iSNS Server instance being managed. DDs
305 are collections of storage nodes and portals that are allowed to
306 discover one another. DD members can be iSCSI nodes, Entity Portals,
307 or iFCP nodes.
308
309 <span class="h4"><a class="selflink" id="section-3.3.4" href="#section-3.3.4">3.3.4</a>. Registered Storage Objects</span>
310
311 The isnsReg section provides information on the registered storage
312 objects for a specific iSNS Server instance. This section is divided
313 into subsections for Entities, Portals, and iSCSI Nodes, as well as
314 iFCP Port and Node information.
315
316 <span class="h5"><a class="selflink" id="section-3.3.4.1" href="#section-3.3.4.1">3.3.4.1</a>. Registered Entities</span>
317
318 The isnsRegEntityInfo section provides information on the registered
319 entities. Entities are collections of storage nodes and portals.
320
321 <span class="h5"><a class="selflink" id="section-3.3.4.2" href="#section-3.3.4.2">3.3.4.2</a>. Registered Portals</span>
322
323 The isnsRegPortalInfo section provides information on the registered
324 portals for a specific iSNS Server instance. Portals are logical
325 IP-Address, TCP/UDP Port pairs that provide access to storage nodes
326 contained in the associated Entity.
327
328
329
330
331
332 <span class="grey">Gibbons, et al. Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
335
336
337 <span class="h5"><a class="selflink" id="section-3.3.4.3" href="#section-3.3.4.3">3.3.4.3</a>. Registered Portal Groups</span>
338
339 The isnsRegPortalGroupInfo section provides information on the
340 registered portal groups for a specific iSNS Server instance. As
341 described in iSCSI [<a href="./rfc3720" title="&quot;Internet Small Computer Systems Interface (iSCSI)&quot;">RFC3720</a>], Portal Groups provide a mapping between
342 Portals and iSCSI Storage Nodes contained in an Entity.
343
344 <span class="h5"><a class="selflink" id="section-3.3.4.4" href="#section-3.3.4.4">3.3.4.4</a>. Registered iSCSI Nodes</span>
345
346 The isnsRegIscsiNodeInfo section provides information on the
347 registered iSCSI Nodes for a specific iSNS Server instance. The
348 iSCSI nodes are individual storage targets or initiators.
349
350 <span class="h5"><a class="selflink" id="section-3.3.4.5" href="#section-3.3.4.5">3.3.4.5</a>. Registered FC Ports</span>
351
352 The isnsRegFcPortInfo section provides information on the registered
353 FC Ports for a specific iSNS Server instance. The FC Ports are ports
354 associated with an iFCP gateway.
355
356 <span class="h5"><a class="selflink" id="section-3.3.4.6" href="#section-3.3.4.6">3.3.4.6</a>. Registered FC Nodes</span>
357
358 The isnsRegFcNodeInfo section provides information on the registered
359 FC Nodes for a specific iSNS Server instance. The FC nodes are
360 individual storage devices associated with an iFCP gateway.
361
362 <span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Multiple Server Instances</span>
363
364 The management of multiple instances of iSNS servers by the agent is
365 supported. As described in <a href="#section-3.3">Section 3.3</a>, each managed iSNS server
366 instance has an entry in the table isnsServerTable.
367
368 <span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>. iSNS Notifications</span>
369
370 The isnsNotification section provides SNMP notifications for iSNS
371 Server state changes.
372
373 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. MIB References</span>
374
375 The following MIB module has IMPORTS from [<a href="./rfc2578" title="&quot;Structure of Management Information Version 2 (SMIv2)&quot;">RFC2578</a>], [<a href="./rfc2579" title="&quot;Textual Conventions for SMIv2&quot;">RFC2579</a>],
376 [<a href="./rfc2580" title="&quot;Conformance Statements for SMIv2&quot;">RFC2580</a>], [<a href="./rfc3411" title="&quot;An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks&quot;">RFC3411</a>], [<a href="./rfc4001" title="&quot;Textual Conventions for Internet Network Addresses&quot;">RFC4001</a>], [<a href="./rfc4044" title="&quot;Fibre Channel Management MIB&quot;">RFC4044</a>], and [<a href="./rfc4133" title="&quot;Entity MIB (Version 3)&quot;">RFC4133</a>]. In
377 REFERENCE clauses, it also refers to [<a href="./rfc3720" title="&quot;Internet Small Computer Systems Interface (iSCSI)&quot;">RFC3720</a>], [<a href="./rfc4171" title="&quot;Internet Storage Name Service (iSNS)&quot;">RFC4171</a>], and
378 [<a href="./rfc4172" title="&quot;iFCP - A Protocol for Internet Fibre Channel Storage Networking&quot;">RFC4172</a>].
379
380
381
382
383
384
385
386
387
388 <span class="grey">Gibbons, et al. Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
391
392
393 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. MIB Module</span>
394
395 ISNS-MIB DEFINITIONS ::= BEGIN
396 IMPORTS
397 -- From <a href="./rfc2578">RFC 2578</a>
398 MODULE-IDENTITY,
399 OBJECT-TYPE,
400 NOTIFICATION-TYPE,
401 Integer32,
402 Unsigned32,
403 Gauge32,
404 mib-2
405 FROM SNMPv2-SMI
406
407 -- From <a href="./rfc2579">RFC 2579</a>
408 TEXTUAL-CONVENTION,
409 TimeStamp,
410 TruthValue
411 FROM SNMPv2-TC
412
413 -- From <a href="./rfc2580">RFC 2580</a>
414 OBJECT-GROUP,
415 MODULE-COMPLIANCE,
416 NOTIFICATION-GROUP
417 FROM SNMPv2-CONF
418
419 -- From <a href="./rfc3411">RFC 3411</a>
420 SnmpAdminString
421 FROM SNMP-FRAMEWORK-MIB
422
423 -- From <a href="./rfc4001">RFC 4001</a>
424 InetAddressType,
425 InetAddress,
426 InetPortNumber
427 FROM INET-ADDRESS-MIB
428
429 -- From <a href="./rfc4044">RFC 4044</a>
430 FcNameIdOrZero,
431 FcAddressIdOrZero
432 FROM FC-MGMT-MIB
433
434 -- From <a href="./rfc4133">RFC 4133</a>
435 PhysicalIndex
436 FROM ENTITY-MIB
437 ;
438
439 isnsMIB MODULE-IDENTITY
440 LAST-UPDATED "200707110000Z"
441
442
443
444 <span class="grey">Gibbons, et al. Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
447
448
449 ORGANIZATION "IETF IPS Working Group"
450 CONTACT-INFO "
451 Attn: Kevin Gibbons
452 2Wire, Inc.
453 1704 Automation Parkway
454 San Jose, CA 95131
455 USA
456 Tel: +1 408-895-1387
457 Fax: +1 408-428-9590
458 Email: [email protected]
459
460 G.D. Ramkumar
461 SnapTell, Inc.
462 2741 Middlefield Rd, Suite 200
463 Palo Alto, CA 94306
464 USA
465 Tel: +1 650-326-7627
466 Fax: +1 650-326-7620
467 Email: [email protected]
468
469 Scott Kipp
470 Brocade
471 4 McDATA Pkwy
472 Broomfield, CO 80021
473 USA
474 Tel: +1 720-558-3452
475 Fax: +1 720-558-8999
476 Email: [email protected]
477 "
478
479 DESCRIPTION
480 "This module defines management information
481 specific to internet Storage Name Service
482 (iSNS) management.
483
484 Copyright (C) The IETF Trust (2007).
485 This version of this MIB module is part
486 of <a href="./rfc4939">RFC 4939</a>; see the RFC itself for full
487 legal notices."
488
489 REVISION "200707110000Z"
490
491 DESCRIPTION
492 "Initial version of iSNS Management Module.
493 This MIB published as <a href="./rfc4939">RFC 4939</a>."
494 ::= { mib-2 163 }
495
496
497
498
499
500 <span class="grey">Gibbons, et al. Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
503
504
505 --
506 -- Textual Conventions
507 --
508
509 IsnsDiscoveryDomainSetId ::= TEXTUAL-CONVENTION
510 DISPLAY-HINT "d"
511 STATUS current
512 DESCRIPTION
513 "The unique Discovery Domain Set Identifier associated with a
514 Discovery Domain Set (DDS)."
515 REFERENCE "<a href="./rfc4171#section-6.11.1.1">RFC 4171, Section&nbsp;6.11.1.1</a>"
516 SYNTAX Unsigned32 ( 1 .. 4294967295 )
517
518 IsnsDdsStatusType ::= TEXTUAL-CONVENTION
519 STATUS current
520 DESCRIPTION
521 "The status of a Discovery Domain Set (DDS) registered in the
522 iSNS. The initially assigned values are below:
523 Bit Status
524 --------- ---------
525 31 DDS Enabled
526 All others RESERVED
527
528 Setting a bit to 1 indicates the feature is enabled.
529 Otherwise, it is disabled. The future assignment of any of
530 the reserved values will be documented in a revision of
531 <a href="./rfc4171">RFC 4171</a>."
532 REFERENCE "<a href="./rfc4171#section-6.11.1.3">RFC 4171, Section&nbsp;6.11.1.3</a>"
533 SYNTAX BITS {
534 reserved0(0), reserved1(1), reserved2(2),
535 reserved3(3), reserved4(4), reserved5(5),
536 reserved6(6), reserved7(7), reserved8(8),
537 reserved9(9), reserved10(10), reserved11(11),
538 reserved12(12), reserved13(13), reserved14(14),
539 reserved15(15), reserved16(16), reserved17(17),
540 reserved18(18), reserved19(19), reserved20(20),
541 reserved21(21), reserved22(22), reserved23(23),
542 reserved24(24), reserved25(25), reserved26(26),
543 reserved27(27), reserved28(28), reserved29(29),
544 reserved30(30),
545 ddsEnabled (31)
546 }
547
548 IsnsDiscoveryDomainId ::= TEXTUAL-CONVENTION
549 DISPLAY-HINT "d"
550 STATUS current
551 DESCRIPTION
552 "The unique Discovery Domain Identifier (DD_ID) associated
553
554
555
556 <span class="grey">Gibbons, et al. Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
559
560
561 with each Discovery Domain (DD). This is used to
562 uniquely index and reference a DD."
563 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
564 SYNTAX Unsigned32 ( 1 .. 4294967295 )
565
566 IsnsDdFeatureType ::= TEXTUAL-CONVENTION
567 STATUS current
568 DESCRIPTION
569 "This type defines the features that each Discovery Domain
570 (DD) has.
571 Bit Status
572 --------- ---------
573 31 Boot List
574 All others RESERVED
575
576 Boot List: this feature indicates that the targets
577 in this DD provide boot capabilities for the member
578 initiators.
579
580 Setting a bit to 1 indicates the feature is enabled.
581 Otherwise, it is disabled. The future assignment of any of
582 the reserved values will be documented in a revision of
583 <a href="./rfc4171">RFC 4171</a>."
584 REFERENCE "<a href="./rfc4171#section-6.11.2.9">RFC 4171, Section&nbsp;6.11.2.9</a>"
585 SYNTAX BITS {
586 reserved0(0), reserved1(1), reserved2(2),
587 reserved3(3), reserved4(4), reserved5(5),
588 reserved6(6), reserved7(7), reserved8(8),
589 reserved9(9), reserved10(10), reserved11(11),
590 reserved12(12), reserved13(13), reserved14(14),
591 reserved15(15), reserved16(16), reserved17(17),
592 reserved18(18), reserved19(19), reserved20(20),
593 reserved21(21), reserved22(22), reserved23(23),
594 reserved24(24), reserved25(25), reserved26(26),
595 reserved27(27), reserved28(28), reserved29(29),
596 reserved30(30),
597 bootlist(31)
598 }
599
600 IsnsDdDdsModificationType ::= TEXTUAL-CONVENTION
601 STATUS current
602 DESCRIPTION
603 "The methods that can be used to modify the Discovery
604 Domain and Discovery Domain Sets in an iSNS Server
605 instance.
606 Bit Flag Description
607 --------- ------------------------------------
608 0 Control Nodes are allowed
609
610
611
612 <span class="grey">Gibbons, et al. Standards Track [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
615
616
617 1 Target iSCSI Nodes are allowed
618 2 Initiator iSCSI Nodes are allowed
619 3 Target iFCP Ports are allowed
620 4 Initiator iFCP Ports are allowed
621
622 Setting a bit to 1 indicates the feature is
623 enabled. Otherwise, it is disabled."
624 REFERENCE "<a href="./rfc4171#section-2.4">RFC 4171, Section&nbsp;2.4</a>"
625 SYNTAX BITS {
626 controlNode(0),
627 targetIscsiNode(1),
628 initiatorIscsiNode(2),
629 targetIfcpNode(3),
630 initiatorIfcpNode(4)
631 }
632
633 IsnsEntityIndexIdOrZero ::= TEXTUAL-CONVENTION
634 DISPLAY-HINT "d"
635 STATUS current
636 DESCRIPTION
637 "The identifier for the unique integer Entity Index
638 associated with an iSNS registered Entity object, and the
639 value zero. The value zero is object-specific and MUST
640 therefore be defined as part of the description of any
641 object that uses this syntax. Examples of the usage of
642 zero might include situations where the Entity is unknown,
643 or not yet registered in the iSNS server. If a value of
644 zero is not valid for an object, then that MUST be
645 indicated."
646 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
647 SYNTAX Unsigned32 ( 0 .. 4294967295 )
648
649 IsnsPortalGroupIndexId ::= TEXTUAL-CONVENTION
650 DISPLAY-HINT "d"
651 STATUS current
652 DESCRIPTION
653 "The identifier for the unique integer Portal Group Index
654 associated with an iSNS registered Portal Group object."
655 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
656 SYNTAX Unsigned32 ( 1 .. 4294967295 )
657
658 IsnsPortalIndexId ::= TEXTUAL-CONVENTION
659 DISPLAY-HINT "d"
660 STATUS current
661 DESCRIPTION
662 "The identifier for the unique integer Portal Index
663 associated with an iSNS registered Portal object. The
664 index is created by the iSNS Server for mapping between
665
666
667
668 <span class="grey">Gibbons, et al. Standards Track [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
671
672
673 registered objects. The Portal Index used for a specific
674 portal IP-address and port number pair is only persistent
675 across reboots for portals that have been explicitly added
676 to a Discovery Domain (DD). If a portal is not explicitly
677 registered in any DD, then the index used for a portal can
678 change after a server reinitialization."
679 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
680 SYNTAX Unsigned32 ( 1 .. 4294967295 )
681
682 IsnsPortalPortTypeId ::= TEXTUAL-CONVENTION
683 STATUS current
684 DESCRIPTION
685 "The UDP or TCP port type being used by a Portal for an
686 Entity."
687 REFERENCE "<a href="./rfc4171#section-6.3.2">RFC 4171, Section&nbsp;6.3.2</a>"
688 SYNTAX INTEGER { udp(1), tcp(2) }
689
690 IsnsPortalGroupTagIdOrNull ::= TEXTUAL-CONVENTION
691 DISPLAY-HINT "d"
692 STATUS current
693 DESCRIPTION
694 "The Portal Group Tag (PGT) represents an association
695 between a Portal and iSCSI Node using the value range
696 0 to 65535. A PGT with no association is a NULL
697 value. The value of -1 indicates a NULL value."
698 REFERENCE "<a href="./rfc4171#section-6.5.4">RFC 4171, Section&nbsp;6.5.4</a>, and <a href="./rfc3720">RFC 3720</a>"
699 SYNTAX Integer32 ( -1 .. 65535 )
700
701 IsnsPortalSecurityType ::= TEXTUAL-CONVENTION
702 STATUS current
703 DESCRIPTION
704 "Indicates security attribute settings for a Portal that is
705 registered in the iSNS server. The bitmapVALID field must
706 be set in order for the contents to be considered valid
707 information. The definitions of the bit fields are based
708 on <a href="./rfc4171">RFC 4171</a>. The initial representation of each bit setting
709 (0 or 1) is indicated below.
710 Bit Flag Description
711 --------- ------------------------------------
712 25 1 = Tunnel Mode Preferred; 0 = No Preference
713 26 1 = Transport Mode Preferred; 0 = No
714 Preference
715 27 1 = PFS Enabled; 0 = PFS Disabled
716 28 1 = Aggressive Mode Enabled; 0 = Disabled
717 29 1 = Main Mode Enabled; 0 = MM Disabled
718 30 1 = IKE/IPsec Enabled; 0 = IKE/IPsec
719 Disabled
720 31 1 = Bitmap VALID; 0 = INVALID
721
722
723
724 <span class="grey">Gibbons, et al. Standards Track [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
727
728
729 All others RESERVED
730
731 The future assignment of any of the reserved values will be
732 documented in a revision of <a href="./rfc4171">RFC 4171</a>."
733 REFERENCE "<a href="./rfc4171#section-6.3.9">RFC 4171, Section&nbsp;6.3.9</a>"
734 SYNTAX BITS {
735 reserved0(0), reserved1(1), reserved2(2),
736 reserved3(3), reserved4(4), reserved5(5),
737 reserved6(6), reserved7(7), reserved8(8),
738 reserved9(9), reserved10(10), reserved11(11),
739 reserved12(12), reserved13(13), reserved14(14),
740 reserved15(15), reserved16(16), reserved17(17),
741 reserved18(18), reserved19(19), reserved20(20),
742 reserved21(21), reserved22(22), reserved23(23),
743 reserved24(24),
744 tunnelModePreferred(25),
745 transportModePreferred(26),
746 pfsEnabled(27),
747 agressiveModeEnabled(28),
748 mainModeEnabled(29),
749 ikeIPsecEnabled(30),
750 bitmapVALID(31)
751 }
752
753 IsnsNodeIndexId ::= TEXTUAL-CONVENTION
754 DISPLAY-HINT "d"
755 STATUS current
756 DESCRIPTION
757 "The identifier for the unique integer Node Index associated
758 with a storage node. This index provides a 1-to-1 mapping
759 to an iSCSI node name. The iSCSI node name maximum length
760 is too long to be used for an index directly. The iSCSI
761 node index used for a specific iSCSI node name is identical
762 in all DDs, and is persistent across server
763 reinitializations when the iSCSI node is a member of a
764 Discovery Domain (DD) or is registered as a Control Node.
765 Furthermore, index values for recently deregistered objects
766 SHOULD NOT be reused in the short term."
767 REFERENCE "<a href="./rfc4171#section-6.4.5">RFC 4171, Section&nbsp;6.4.5</a>"
768 SYNTAX Unsigned32 ( 1 .. 4294967295 )
769
770 IsnsIscsiNodeType ::= TEXTUAL-CONVENTION
771 STATUS current
772 DESCRIPTION
773 "The iSCSI Node Type defines the functions of the registered
774 object. The definitions of each setting are defined in
775 <a href="./rfc4171">RFC 4171</a>.
776 Bit Node Type
777
778
779
780 <span class="grey">Gibbons, et al. Standards Track [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
783
784
785 --------- ---------
786 29 Control
787 30 Initiator
788 31 Target
789 All others RESERVED
790
791 Setting a bit to 1 indicates the node has the corresponding
792 characteristics. The future assignment of any of the
793 reserved values will be documented in a revision of
794 <a href="./rfc4171">RFC 4171</a>."
795 REFERENCE "<a href="./rfc4171#section-6.4.2">RFC 4171, Section&nbsp;6.4.2</a>"
796 SYNTAX BITS {
797 reserved0(0), reserved1(1), reserved2(2),
798 reserved3(3), reserved4(4), reserved5(5),
799 reserved6(6), reserved7(7), reserved8(8),
800 reserved9(9), reserved10(10), reserved11(11),
801 reserved12(12), reserved13(13), reserved14(14),
802 reserved15(15), reserved16(16), reserved17(17),
803 reserved18(18), reserved19(19), reserved20(20),
804 reserved21(21), reserved22(22), reserved23(23),
805 reserved24(24), reserved25(25), reserved26(26),
806 reserved27(27), reserved28(28),
807 control(29),
808 initiator(30),
809 target(31)
810 }
811
812 IsnsFcClassOfServiceType ::= TEXTUAL-CONVENTION
813 STATUS current
814 DESCRIPTION
815 "This defines the Fibre Channel Class of Service types
816 that are supported by the registered port. The
817 definitions are as defined in <a href="./rfc4171">RFC 4171</a>.
818 Bit FC COS Type
819 --------- ----------------
820 28 Fibre Channel Class 3 Supported
821 29 Fibre Channel Class 2 Supported
822 All others RESERVED
823
824 Setting a bit to 1 indicates the class of service is
825 supported. The future assignment of any of the
826 reserved values will be documented in a revision of
827 <a href="./rfc4171">RFC 4171</a>."
828 REFERENCE "<a href="./rfc4171#section-6.6.8">RFC 4171, Section&nbsp;6.6.8</a>"
829 SYNTAX BITS {
830 reserved0(0), reserved1(1), reserved2(2),
831 reserved3(3), reserved4(4), reserved5(5),
832 reserved6(6), reserved7(7), reserved8(8),
833
834
835
836 <span class="grey">Gibbons, et al. Standards Track [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
839
840
841 reserved9(9), reserved10(10), reserved11(11),
842 reserved12(12), reserved13(13), reserved14(14),
843 reserved15(15), reserved16(16), reserved17(17),
844 reserved18(18), reserved19(19), reserved20(20),
845 reserved21(21), reserved22(22), reserved23(23),
846 reserved24(24), reserved25(25), reserved26(26),
847 reserved27(27),
848 class3(28),
849 class2(29)
850 }
851
852 IsnsIscsiScnType ::= TEXTUAL-CONVENTION
853 STATUS current
854 DESCRIPTION
855 "The iSCSI Node State Change Notification (SCN) values
856 for a node as defined in <a href="./rfc4171">RFC 4171</a>.
857 Bit Description
858 ------------ ----------------
859 24 Initiator and self information only
860 25 Target and self information only
861 26 Management registration/SCN
862 27 Object removed
863 28 Object added
864 29 Object updated
865 30 DD or DDS member removed (Mgmt
866 Reg/SCN only)
867 31 (Lsb) DD or DDS member added (Mgmt
868 Reg/SCN only)
869 All others Reserved
870
871 Setting a bit to 1 indicates that type of SCN is enabled.
872 The future assignment of any of the reserved values will be
873 documented in a revision of <a href="./rfc4171">RFC 4171</a>."
874 REFERENCE "<a href="./rfc4171#section-6.4.4">RFC 4171, Section&nbsp;6.4.4</a>"
875 SYNTAX BITS {
876 reserved0(0), reserved1(1), reserved2(2),
877 reserved3(3), reserved4(4), reserved5(5),
878 reserved6(6), reserved7(7), reserved8(8),
879 reserved9(9), reserved10(10), reserved11(11),
880 reserved12(12), reserved13(13), reserved14(14),
881 reserved15(15), reserved16(16), reserved17(17),
882 reserved18(18), reserved19(19), reserved20(20),
883 reserved21(21), reserved22(22), reserved23(23),
884 initiatorAndSelfOnly(24),
885 targetAndSelfOnly(25),
886 managementRegistrationScn(26),
887 objectRemoved(27),
888 objectAdded(28),
889
890
891
892 <span class="grey">Gibbons, et al. Standards Track [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
895
896
897 objectUpdated(29),
898 ddOrDdsMemberRemoved(30),
899 ddOrDdsMemberAdded(31)
900 }
901
902 IsnsIfcpScnType ::= TEXTUAL-CONVENTION
903 STATUS current
904 DESCRIPTION
905 "The iFCP State Change Notification (SCN) values for an iFCP
906 object as defined in <a href="./rfc4171">RFC 4171</a>.
907 Bit Description
908 ------------ ----------------
909 24 Initiator and self information only
910 25 Target and self information only
911 26 Management registration/SCN
912 27 Object removed
913 28 Object added
914 29 Object updated
915 30 DD or DDS member removed (Mgmt
916 Reg/SCN only)
917 31 (Lsb) DD or DDS member added (Mgmt
918 Reg/SCN only)
919 All others Reserved
920
921 Setting a bit to 1 indicates that type of SCN is enabled.
922 The future assignment of any of the reserved values will be
923 documented in a revision of <a href="./rfc4171">RFC 4171</a>."
924 REFERENCE "<a href="./rfc4171#section-6.6.12">RFC 4171, Section&nbsp;6.6.12</a>"
925 SYNTAX BITS {
926 reserved0(0), reserved1(1), reserved2(2),
927 reserved3(3), reserved4(4), reserved5(5),
928 reserved6(6), reserved7(7), reserved8(8),
929 reserved9(9), reserved10(10), reserved11(11),
930 reserved12(12), reserved13(13), reserved14(14),
931 reserved15(15), reserved16(16), reserved17(17),
932 reserved18(18), reserved19(19), reserved20(20),
933 reserved21(21), reserved22(22), reserved23(23),
934 initiatorAndSelfOnly(24),
935 targetAndSelfOnly(25),
936 managementRegistrationScn(26),
937 objectRemoved(27),
938 objectAdded(28),
939 objectUpdated(29),
940 ddOrDdsMemberRemoved(30),
941 ddOrDdsMemberAdded(31)
942 }
943
944 IsnsFcPortRoleType ::= TEXTUAL-CONVENTION
945
946
947
948 <span class="grey">Gibbons, et al. Standards Track [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
951
952
953 STATUS current
954 DESCRIPTION
955 "The FC Port Role defines the functions of the registered
956 object. The definitions of each setting are defined in
957 <a href="./rfc4171">RFC 4171</a>.
958 Bit Port Role
959 --------- ---------
960 29 Control
961 30 FCP Initiator
962 31 FCP Target
963 All others RESERVED
964
965 Setting a bit to 1 indicates the port has the corresponding
966 characteristics. The future assignment of any of the
967 reserved values will be documented in a revision of
968 <a href="./rfc4171">RFC 4171</a>."
969 REFERENCE "<a href="./rfc4171#section-6.6.13">RFC 4171, Section&nbsp;6.6.13</a>"
970 SYNTAX BITS {
971 reserved0(0), reserved1(1), reserved2(2),
972 reserved3(3), reserved4(4), reserved5(5),
973 reserved6(6), reserved7(7), reserved8(8),
974 reserved9(9), reserved10(10), reserved11(11),
975 reserved12(12), reserved13(13), reserved14(14),
976 reserved15(15), reserved16(16), reserved17(17),
977 reserved18(18), reserved19(19), reserved20(20),
978 reserved21(21), reserved22(22), reserved23(23),
979 reserved24(24), reserved25(25), reserved26(26),
980 reserved27(27), reserved28(28),
981 control(29),
982 initiator(30),
983 target(31)
984 }
985
986 IsnsSrvrDiscoveryMethodsType ::= TEXTUAL-CONVENTION
987 STATUS current
988 DESCRIPTION
989 "The types of iSNS Server discovery methods that are enabled
990 on an iSNS Server. The options are DHCP, Service Location
991 Protocol (SLP), multicast group iSNS heartbeat, broadcast
992 group iSNS heartbeat, configured server list, and other.
993 The iSNS Server may support additional discovery methods
994 not indicated."
995 REFERENCE "<a href="./rfc4171#section-2.5">RFC 4171, Section&nbsp;2.5</a>"
996 SYNTAX BITS {
997 dhcp(0),
998 slp(1),
999 multicastGroupHb(2),
1000 broadcastHb(3),
1001
1002
1003
1004 <span class="grey">Gibbons, et al. Standards Track [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
1007
1008
1009 cfgdServerList(4),
1010 other(5)
1011 }
1012
1013 --
1014 -- Internet Storage Name Service Management
1015 --
1016
1017
1018 isnsNotifications OBJECT IDENTIFIER ::=
1019 { isnsMIB 0 }
1020 isnsObjects OBJECT IDENTIFIER ::=
1021 { isnsMIB 1 }
1022 isnsConformance OBJECT IDENTIFIER ::=
1023 { isnsMIB 2 }
1024
1025 --
1026 -- iSNS Server instance managed objects --------------------
1027 --
1028
1029 isnsServerInfo OBJECT IDENTIFIER ::= { isnsObjects 1 }
1030
1031 isnsServerTable OBJECT-TYPE
1032 SYNTAX SEQUENCE OF IsnsServerEntry
1033 MAX-ACCESS not-accessible
1034 STATUS current
1035 DESCRIPTION
1036 "This table provides a list of the iSNS Server instances
1037 that are managed through the same SNMP context."
1038 ::= { isnsServerInfo 1 }
1039
1040 isnsServerEntry OBJECT-TYPE
1041 SYNTAX IsnsServerEntry
1042 MAX-ACCESS not-accessible
1043 STATUS current
1044 DESCRIPTION
1045 "This is a row in the iSNS Server instance table. The number
1046 of rows is dependent on the number of iSNS Server instances
1047 that are being managed through the same SNMP context."
1048 INDEX { isnsServerIndex }
1049 ::= { isnsServerTable 1 }
1050
1051 IsnsServerEntry ::=
1052 SEQUENCE {
1053 isnsServerIndex Unsigned32,
1054 isnsServerName SnmpAdminString,
1055 isnsServerIsnsVersion Unsigned32,
1056 isnsServerVendorInfo SnmpAdminString,
1057
1058
1059
1060 <span class="grey">Gibbons, et al. Standards Track [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
1063
1064
1065 isnsServerPhysicalIndex PhysicalIndex,
1066 isnsServerTcpPort InetPortNumber,
1067 isnsServerUdpPort InetPortNumber,
1068 isnsServerDiscontinuityTime
1069 TimeStamp,
1070 isnsServerRole INTEGER,
1071 isnsServerDiscoveryMethodsEnabled
1072 IsnsSrvrDiscoveryMethodsType,
1073 isnsServerDiscoveryMcGroupType
1074 InetAddressType,
1075 isnsServerDiscoveryMcGroupAddress
1076 InetAddress,
1077 isnsServerEsiNonResponseThreshold
1078 Unsigned32,
1079 isnsServerEnableControlNodeMgtScn
1080 TruthValue,
1081 isnsServerDefaultDdDdsStatus
1082 INTEGER,
1083 isnsServerUpdateDdDdsSupported
1084 IsnsDdDdsModificationType,
1085 isnsServerUpdateDdDdsEnabled
1086 IsnsDdDdsModificationType
1087 }
1088
1089 isnsServerIndex OBJECT-TYPE
1090 SYNTAX Unsigned32 ( 1 .. 4294967295 )
1091 MAX-ACCESS not-accessible
1092 STATUS current
1093 DESCRIPTION
1094 "This object uniquely identifies the iSNS Server being
1095 managed by the SNMP context and is the key for this table.
1096 This is an instance index for each iSNS Server being
1097 managed. The value of this object is used elsewhere in
1098 the MIB to reference specific iSNS Servers."
1099 ::= { isnsServerEntry 1 }
1100
1101 isnsServerName OBJECT-TYPE
1102 SYNTAX SnmpAdminString
1103 MAX-ACCESS read-only
1104 STATUS current
1105 DESCRIPTION
1106 "A non-unique name that can be assigned to the iSNS Server
1107 instance. If not configured, then the string SHALL be
1108 zero-length."
1109 ::= { isnsServerEntry 2 }
1110
1111 isnsServerIsnsVersion OBJECT-TYPE
1112 SYNTAX Unsigned32 ( 0 .. 65535 )
1113
1114
1115
1116 <span class="grey">Gibbons, et al. Standards Track [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
1119
1120
1121 MAX-ACCESS read-only
1122 STATUS current
1123 DESCRIPTION
1124 "The iSNS version value as contained in messages received
1125 from the current primary server. The header of each iSNSP
1126 message contains the iSNS version of the sender. If
1127 unknown, the reported value is 0."
1128 REFERENCE "<a href="./rfc4171">RFC 4171</a>"
1129 DEFVAL { 1 }
1130 ::= { isnsServerEntry 3 }
1131
1132 isnsServerVendorInfo OBJECT-TYPE
1133 SYNTAX SnmpAdminString
1134 MAX-ACCESS read-only
1135 STATUS current
1136 DESCRIPTION
1137 "If this server instance is utilizing the product of a
1138 particular 'vendor', then this managed object contains
1139 that vendor's name and version. Otherwise, the
1140 string SHALL be zero-length. The format of the string
1141 is as follows: Vendor Name, Vendor Version, Vendor
1142 Defined Information.
1143
1144 Field Description
1145 --------- ----------------
1146 Vendor Name The name of the vendor (if one exists)
1147 Vendor Version The version of the vendor product
1148 Vendor Defined This follows the second comma in the
1149 string, if one exists, and is vendor
1150 defined
1151 "
1152 ::= { isnsServerEntry 4 }
1153
1154 isnsServerPhysicalIndex OBJECT-TYPE
1155 SYNTAX PhysicalIndex
1156 MAX-ACCESS read-only
1157 STATUS current
1158 DESCRIPTION
1159 "An index identifying the network interface for this iSNS
1160 Server within a network entity. This index maps to the
1161 entPhysicalIndex of entPhysicalTable table in <a href="./rfc4133">RFC 4133</a>. The
1162 entPhysicalClass value for the table row must be 'port', as
1163 the interface must be able to send and receive data."
1164 REFERENCE "<a href="./rfc4133">RFC 4133</a>, <a href="./rfc4171#section-2.5">RFC 4171, Section&nbsp;2.5</a> - 2.8"
1165 ::= { isnsServerEntry 5 }
1166
1167 isnsServerTcpPort OBJECT-TYPE
1168 SYNTAX InetPortNumber
1169
1170
1171
1172 <span class="grey">Gibbons, et al. Standards Track [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
1175
1176
1177 MAX-ACCESS read-only
1178 STATUS current
1179 DESCRIPTION
1180 "Indicates the TCP port this iSNS instance is accepting
1181 iSNSP messages on, generally the iSNS well-known port.
1182 The well-known TCP port for iSNSP is 3205. If TCP is
1183 not supported by this server instance, then the value
1184 is 0."
1185 ::= { isnsServerEntry 6 }
1186
1187 isnsServerUdpPort OBJECT-TYPE
1188 SYNTAX InetPortNumber
1189 MAX-ACCESS read-only
1190 STATUS current
1191 DESCRIPTION
1192 "Indicates the UDP port this iSNS instance is accepting
1193 iSNSP messages on; generally, the iSNS well-known port.
1194 The well-known UDP port for iSNSP is 3205. If UDP is
1195 not supported by this server instance, then the value
1196 is 0."
1197 ::= { isnsServerEntry 7 }
1198
1199 isnsServerDiscontinuityTime OBJECT-TYPE
1200 SYNTAX TimeStamp
1201 MAX-ACCESS read-only
1202 STATUS current
1203 DESCRIPTION
1204 "The value of sysUpTime on the most recent occasion that
1205 this iSNS server became active or suffered a
1206 discontinuity."
1207 ::= { isnsServerEntry 8 }
1208
1209 isnsServerRole OBJECT-TYPE
1210 SYNTAX INTEGER { notSet(1),
1211 server(2),
1212 backupServer(3) }
1213 MAX-ACCESS read-only
1214 STATUS current
1215 DESCRIPTION
1216 "The current operational mode of this iSNS Server instance.
1217
1218 Value Description
1219 --------- ----------------
1220 notSet The iSNS Server role is not
1221 configured.
1222 server The iSNS Server instance is
1223 an operational iSNS Server.
1224 backupServer The iSNS Server instance is
1225
1226
1227
1228 <span class="grey">Gibbons, et al. Standards Track [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
1231
1232
1233 currently acting as a backup."
1234 REFERENCE "<a href="./rfc4171#section-2.7">RFC 4171, Section&nbsp;2.7</a> - 2.8"
1235 ::= { isnsServerEntry 9 }
1236
1237 isnsServerDiscoveryMethodsEnabled OBJECT-TYPE
1238 SYNTAX IsnsSrvrDiscoveryMethodsType
1239 MAX-ACCESS read-only
1240 STATUS current
1241 DESCRIPTION
1242 "Indicates the discovery methods currently enabled for
1243 this iSNS Server instance. This allows a client to
1244 determine what discovery methods can be used for
1245 this iSNS Server. Additional methods of discovery may
1246 also be supported."
1247 ::= { isnsServerEntry 10 }
1248
1249 isnsServerDiscoveryMcGroupType OBJECT-TYPE
1250 SYNTAX InetAddressType
1251 MAX-ACCESS read-only
1252 STATUS current
1253 DESCRIPTION
1254 "The type of Internet address in
1255 isnsServerDiscoveryMcGroupAddress. If the address is
1256 specified, then it must be a valid multicast address and the
1257 value of this object must be ipv4(1), ipv6(2), ipv4z(3), or
1258 ipv6z(4); otherwise, the value of this object is
1259 unknown(0), and the value of
1260 isnsServerDiscoveryMcGroupAddress is the zero-length string."
1261 ::= { isnsServerEntry 11 }
1262
1263 isnsServerDiscoveryMcGroupAddress OBJECT-TYPE
1264 SYNTAX InetAddress
1265 MAX-ACCESS read-only
1266 STATUS current
1267 DESCRIPTION
1268 "The multicast group that iSNS Heartbeat messages are
1269 sent to if multicast-based discovery has been enabled
1270 for this server instance. If not configured, then the
1271 string SHALL be zero-length. The format of this
1272 object is specified by isnsServerDiscoveryMcGroupType."
1273 ::= { isnsServerEntry 12 }
1274
1275 isnsServerEsiNonResponseThreshold OBJECT-TYPE
1276 SYNTAX Unsigned32 ( 0 .. 65535 )
1277 MAX-ACCESS read-only
1278 STATUS current
1279 DESCRIPTION
1280 "Entity Status Inquiry (ESI) Non-Response Threshold -
1281
1282
1283
1284 <span class="grey">Gibbons, et al. Standards Track [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
1287
1288
1289 the number of ESI messages that will be sent without
1290 receiving a response before an entity is deregistered
1291 from the iSNS database. A value of 0 indicates
1292 Entities will never be deregistered due to non-receipt
1293 of ESI messages."
1294 REFERENCE "<a href="./rfc4171#section-2.4">RFC 4171, Section&nbsp;2.4</a>"
1295 DEFVAL { 3 }
1296 ::= { isnsServerEntry 13 }
1297
1298 isnsServerEnableControlNodeMgtScn OBJECT-TYPE
1299 SYNTAX TruthValue
1300 MAX-ACCESS read-only
1301 STATUS current
1302 DESCRIPTION
1303 "Indicates if the iSNS Server administrative option to send
1304 Management SCNs to Control Nodes is enabled. Management
1305 SCNs are used by Control Nodes to monitor and control an
1306 iSNS Server. If enabled, Control Nodes can register to
1307 receive Management SCNs."
1308 REFERENCE "<a href="./rfc4171#section-2.2.3">RFC 4171, Section&nbsp;2.2.3</a>, 2.4"
1309 DEFVAL { true }
1310 ::= { isnsServerEntry 14 }
1311
1312 isnsServerDefaultDdDdsStatus OBJECT-TYPE
1313 SYNTAX INTEGER { inNoDomain(1),
1314 inDefaultDdAndDds(2) }
1315 MAX-ACCESS read-only
1316 STATUS current
1317 DESCRIPTION
1318 "This indicates the Discovery Domain (DD) and Discovery
1319 Domain Set (DDS) membership status for a new device
1320 when registered in the iSNS Server instance. Either the
1321 new device will not be in a DD/DDS, or will be placed
1322 into a default DD and default DDS. The default setting
1323 is inNoDomain."
1324 REFERENCE "<a href="./rfc4171#section-2.4">RFC 4171, Section&nbsp;2.4</a>"
1325 DEFVAL { inNoDomain }
1326 ::= { isnsServerEntry 15 }
1327
1328 isnsServerUpdateDdDdsSupported OBJECT-TYPE
1329 SYNTAX IsnsDdDdsModificationType
1330 MAX-ACCESS read-only
1331 STATUS current
1332 DESCRIPTION
1333 "The methods that this iSNS Server instance supports
1334 to modify Discovery Domains and Discovery Domain Sets."
1335 REFERENCE "<a href="./rfc4171#section-2.4">RFC 4171, Section&nbsp;2.4</a>"
1336 ::= { isnsServerEntry 16 }
1337
1338
1339
1340 <span class="grey">Gibbons, et al. Standards Track [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
1343
1344
1345
1346 isnsServerUpdateDdDdsEnabled OBJECT-TYPE
1347 SYNTAX IsnsDdDdsModificationType
1348 MAX-ACCESS read-only
1349 STATUS current
1350 DESCRIPTION
1351 "This indicates the methods this server instance currently
1352 allows for modifying Discovery Domains and Discovery
1353 Domain Sets."
1354 REFERENCE "<a href="./rfc4171">RFC 4171</a>, Sec 2.2.2 and 2.4"
1355 ::= { isnsServerEntry 17 }
1356
1357 --
1358 -- Count of objects currently registered in a server instance
1359 --
1360
1361 isnsNumObjectsTable OBJECT-TYPE
1362 SYNTAX SEQUENCE OF
1363 IsnsNumObjectsEntry
1364 MAX-ACCESS not-accessible
1365 STATUS current
1366 DESCRIPTION
1367 "Table providing the number of registered objects of each
1368 type in the iSNS Server instance. The number of entries is
1369 dependent upon the number of iSNS Server instances being
1370 managed."
1371 ::= { isnsServerInfo 2 }
1372
1373 isnsNumObjectsEntry OBJECT-TYPE
1374 SYNTAX IsnsNumObjectsEntry
1375 MAX-ACCESS not-accessible
1376 STATUS current
1377 DESCRIPTION
1378 "Entry of an iSNS Server instance."
1379 AUGMENTS { isnsServerEntry }
1380 ::= { isnsNumObjectsTable 1 }
1381
1382 IsnsNumObjectsEntry ::= SEQUENCE {
1383 isnsNumDds Gauge32,
1384 isnsNumDd Gauge32,
1385 isnsNumEntities Gauge32,
1386 isnsNumPortals Gauge32,
1387 isnsNumPortalGroups Gauge32,
1388 isnsNumIscsiNodes Gauge32,
1389 isnsNumFcPorts Gauge32,
1390 isnsNumFcNodes Gauge32
1391 }
1392
1393
1394
1395
1396 <span class="grey">Gibbons, et al. Standards Track [Page 25]</span></pre>
1397 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
1398 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
1399
1400
1401 isnsNumDds OBJECT-TYPE
1402 SYNTAX Gauge32 ( 0 .. 4294967295 )
1403 MAX-ACCESS read-only
1404 STATUS current
1405 DESCRIPTION
1406 "The current total number of Discovery Domain Sets
1407 in this iSNS instance. This is the number of rows
1408 in the isnsDdsTable."
1409 ::= { isnsNumObjectsEntry 1 }
1410
1411 isnsNumDd OBJECT-TYPE
1412 SYNTAX Gauge32 ( 0 .. 4294967295 )
1413 MAX-ACCESS read-only
1414 STATUS current
1415 DESCRIPTION
1416 "The current total number of Discovery Domains
1417 in this iSNS instance. This is the number of rows in the
1418 isnsDdTable."
1419 ::= { isnsNumObjectsEntry 2 }
1420
1421 isnsNumEntities OBJECT-TYPE
1422 SYNTAX Gauge32 ( 0 .. 4294967295 )
1423 MAX-ACCESS read-only
1424 STATUS current
1425 DESCRIPTION
1426 "The current number of Entities registered in this
1427 iSNS Server instance. This is the number of rows in
1428 the isnsRegEntityTable for this instance."
1429 ::= { isnsNumObjectsEntry 3 }
1430
1431 isnsNumPortals OBJECT-TYPE
1432 SYNTAX Gauge32 ( 0 .. 4294967295 )
1433 MAX-ACCESS read-only
1434 STATUS current
1435 DESCRIPTION
1436 "The current total number of Portals registered in iSNS.
1437 This is the number of rows in isnsRegPortalTable."
1438 ::= { isnsNumObjectsEntry 4 }
1439
1440 isnsNumPortalGroups OBJECT-TYPE
1441 SYNTAX Gauge32 ( 0 .. 4294967295 )
1442 MAX-ACCESS read-only
1443 STATUS current
1444 DESCRIPTION
1445 "The current total number of Portal Groups registered in
1446 iSNS. This is the number of rows in isnsRegPgTable."
1447 ::= { isnsNumObjectsEntry 5 }
1448
1449
1450
1451
1452 <span class="grey">Gibbons, et al. Standards Track [Page 26]</span></pre>
1453 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
1454 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
1455
1456
1457 isnsNumIscsiNodes OBJECT-TYPE
1458 SYNTAX Gauge32 ( 0 .. 4294967295 )
1459 MAX-ACCESS read-only
1460 STATUS current
1461 DESCRIPTION
1462 "The current total number of iSCSI node entries registered
1463 in the iSNS. This is the number rows in
1464 isnsRegIscsiNodeTable."
1465 ::= { isnsNumObjectsEntry 6 }
1466
1467 isnsNumFcPorts OBJECT-TYPE
1468 SYNTAX Gauge32 ( 0 .. 4294967295 )
1469 MAX-ACCESS read-only
1470 STATUS current
1471 DESCRIPTION
1472 "The current total number of FC Port entries registered
1473 in the iSNS. This is the number of rows in
1474 isnsRegFcPortTable."
1475 ::= { isnsNumObjectsEntry 7 }
1476
1477 isnsNumFcNodes OBJECT-TYPE
1478 SYNTAX Gauge32 ( 0 .. 4294967295 )
1479 MAX-ACCESS read-only
1480 STATUS current
1481 DESCRIPTION
1482 "The current total number of FC node entries registered
1483 in the iSNS. This is the number of rows in
1484 isnsRegFcNodeTable."
1485 ::= { isnsNumObjectsEntry 8 }
1486
1487 --
1488 -- Control node information
1489 --
1490
1491 isnsControlNodeInfo OBJECT IDENTIFIER ::=
1492 { isnsServerInfo 3 }
1493
1494 --
1495 -- Specific iSCSI Nodes authorized to register as Control
1496 -- Nodes
1497 --
1498
1499 isnsControlNodeIscsiTable OBJECT-TYPE
1500 SYNTAX SEQUENCE OF
1501 IsnsControlNodeIscsiEntry
1502 MAX-ACCESS not-accessible
1503 STATUS current
1504 DESCRIPTION
1505
1506
1507
1508 <span class="grey">Gibbons, et al. Standards Track [Page 27]</span></pre>
1509 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
1510 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
1511
1512
1513 "Specified iSCSI Nodes that can register or are registered
1514 as control nodes. The number of rows is dependent on the
1515 number of iSCSI Control Nodes."
1516 ::= { isnsControlNodeInfo 1 }
1517
1518 isnsControlNodeIscsiEntry OBJECT-TYPE
1519 SYNTAX IsnsControlNodeIscsiEntry
1520 MAX-ACCESS not-accessible
1521 STATUS current
1522 DESCRIPTION
1523 "This is an iSCSI Control Node entry for a specific iSNS
1524 server instance."
1525 INDEX { isnsServerIndex,
1526 isnsControlNodeIscsiNodeIndex }
1527 ::= { isnsControlNodeIscsiTable 1 }
1528
1529 IsnsControlNodeIscsiEntry ::= SEQUENCE {
1530 isnsControlNodeIscsiNodeIndex IsnsNodeIndexId,
1531 isnsControlNodeIscsiNodeName SnmpAdminString,
1532 isnsControlNodeIscsiIsRegistered TruthValue,
1533 isnsControlNodeIscsiRcvMgtSCN TruthValue
1534 }
1535
1536 isnsControlNodeIscsiNodeIndex OBJECT-TYPE
1537 SYNTAX IsnsNodeIndexId
1538 MAX-ACCESS not-accessible
1539 STATUS current
1540 DESCRIPTION
1541 "The index for the iSCSI storage node authorized to act
1542 as a control node."
1543 ::= { isnsControlNodeIscsiEntry 1 }
1544
1545 isnsControlNodeIscsiNodeName OBJECT-TYPE
1546 SYNTAX SnmpAdminString
1547 MAX-ACCESS read-only
1548 STATUS current
1549 DESCRIPTION
1550 "The iSCSI Name of the initiator or target associated with
1551 the storage node. The iSCSI Name cannot be longer than
1552 223 bytes. The iSNS Server internal maximum size is 224
1553 bytes to provide NULL termination. This is the iSCSI Node
1554 Name for the storage node authorized and/or acting as a
1555 control node."
1556 ::= { isnsControlNodeIscsiEntry 2 }
1557
1558 isnsControlNodeIscsiIsRegistered OBJECT-TYPE
1559 SYNTAX TruthValue
1560 MAX-ACCESS read-only
1561
1562
1563
1564 <span class="grey">Gibbons, et al. Standards Track [Page 28]</span></pre>
1565 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
1566 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
1567
1568
1569 STATUS current
1570 DESCRIPTION
1571 "Indicates whether the control node is currently
1572 registered in the iSNS Server instance."
1573 ::= { isnsControlNodeIscsiEntry 3 }
1574
1575 isnsControlNodeIscsiRcvMgtSCN OBJECT-TYPE
1576 SYNTAX TruthValue
1577 MAX-ACCESS read-only
1578 STATUS current
1579 DESCRIPTION
1580 "Indicates whether the Control Node has registered to
1581 receive Management SCNs. Management SCNs are sent to
1582 a Control Node if they are enabled, as indicated by
1583 isnsServerEnableControlNodeMgtScn, and the Control
1584 Node has registered for them."
1585 REFERENCE "<a href="./rfc4171#section-2.2.3">RFC 4171, Section&nbsp;2.2.3</a>, 2.4"
1586 ::= { isnsControlNodeIscsiEntry 4 }
1587
1588 --
1589 -- Specific FC Ports authorized to register as Control
1590 -- Nodes
1591 --
1592
1593 isnsControlNodeFcPortTable OBJECT-TYPE
1594 SYNTAX SEQUENCE OF
1595 IsnsControlNodeFcPortEntry
1596 MAX-ACCESS not-accessible
1597 STATUS current
1598 DESCRIPTION
1599 "Specified FC Ports that can register or are registered as
1600 control nodes. The number of rows is dependent on the
1601 number of FC Port Control Nodes."
1602 ::= { isnsControlNodeInfo 2 }
1603
1604 isnsControlNodeFcPortEntry OBJECT-TYPE
1605 SYNTAX IsnsControlNodeFcPortEntry
1606 MAX-ACCESS not-accessible
1607 STATUS current
1608 DESCRIPTION
1609 "FC Port control node entry."
1610 INDEX { isnsServerIndex,
1611 isnsControlNodeFcPortWwpn }
1612 ::= { isnsControlNodeFcPortTable 1 }
1613
1614 IsnsControlNodeFcPortEntry ::= SEQUENCE {
1615 isnsControlNodeFcPortWwpn FcNameIdOrZero,
1616 isnsControlNodeFcPortIsRegistered TruthValue,
1617
1618
1619
1620 <span class="grey">Gibbons, et al. Standards Track [Page 29]</span></pre>
1621 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
1622 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
1623
1624
1625 isnsControlNodeFcPortRcvMgtSCN TruthValue
1626 }
1627
1628 isnsControlNodeFcPortWwpn OBJECT-TYPE
1629 SYNTAX FcNameIdOrZero (SIZE(8))
1630 MAX-ACCESS not-accessible
1631 STATUS current
1632 DESCRIPTION
1633 "The FC Port World Wide Port Name that can and/or is acting
1634 as a Control Node for the specified iSNS Server. A zero-
1635 length string is not valid for this managed object.
1636 This managed object, combined with the isnsServerIndex, is
1637 the key for this table."
1638 ::= { isnsControlNodeFcPortEntry 1 }
1639
1640 isnsControlNodeFcPortIsRegistered OBJECT-TYPE
1641 SYNTAX TruthValue
1642 MAX-ACCESS read-only
1643 STATUS current
1644 DESCRIPTION
1645 "Indicates whether the control node is currently
1646 registered in the iSNS Server instance."
1647 ::= { isnsControlNodeFcPortEntry 2 }
1648
1649 isnsControlNodeFcPortRcvMgtSCN OBJECT-TYPE
1650 SYNTAX TruthValue
1651 MAX-ACCESS read-only
1652 STATUS current
1653 DESCRIPTION
1654 "Indicates whether the Control Node has registered to
1655 receive Management SCNs. Management SCNs are sent to
1656 a Control Node if they are enabled, as indicated by
1657 isnsServerEnableControlNodeMgtScn, and the Control
1658 Node has registered for them."
1659 REFERENCE "<a href="./rfc4171#section-2.2.3">RFC 4171, Section&nbsp;2.2.3</a>, 2.4"
1660 ::= { isnsControlNodeFcPortEntry 3 }
1661
1662 --
1663 -- Discovery Domain Set information
1664 --
1665
1666 isnsDdsInfo OBJECT IDENTIFIER ::= { isnsServerInfo 4 }
1667
1668 --
1669 -- Discovery Domain Set Registrations -----------------
1670 --
1671
1672 isnsDdsTable OBJECT-TYPE
1673
1674
1675
1676 <span class="grey">Gibbons, et al. Standards Track [Page 30]</span></pre>
1677 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span>
1678 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
1679
1680
1681 SYNTAX SEQUENCE OF IsnsDdsEntry
1682 MAX-ACCESS not-accessible
1683 STATUS current
1684 DESCRIPTION
1685 "A table containing configuration information for each
1686 Discovery Domain Set (DDS) registered in the iSNS Server
1687 instance. The number of rows in the table is dependent
1688 on the number of DDSs registered in the specified iSNS
1689 server instance."
1690 ::= { isnsDdsInfo 1 }
1691
1692 isnsDdsEntry OBJECT-TYPE
1693 SYNTAX IsnsDdsEntry
1694 MAX-ACCESS not-accessible
1695 STATUS current
1696 DESCRIPTION
1697 "Information on one Discovery Domain Set (DDS) registered
1698 in the iSNS Server instance."
1699 INDEX { isnsServerIndex, isnsDdsId}
1700 ::= { isnsDdsTable 1 }
1701
1702 IsnsDdsEntry ::=
1703 SEQUENCE {
1704 isnsDdsId IsnsDiscoveryDomainSetId,
1705 isnsDdsSymbolicName SnmpAdminString,
1706 isnsDdsStatus IsnsDdsStatusType
1707 }
1708
1709 isnsDdsId OBJECT-TYPE
1710 SYNTAX IsnsDiscoveryDomainSetId
1711 MAX-ACCESS not-accessible
1712 STATUS current
1713 DESCRIPTION
1714 "The ID that refers to this Discovery Domain Set and
1715 index to the table."
1716 ::= { isnsDdsEntry 1 }
1717
1718 isnsDdsSymbolicName OBJECT-TYPE
1719 SYNTAX SnmpAdminString
1720 MAX-ACCESS read-only
1721 STATUS current
1722 DESCRIPTION
1723 "The Discovery Domain Set Symbolic Name field contains
1724 a unique variable-length description (up to 255 bytes)
1725 that is associated with the DDS. If a Symbolic Name is
1726 not provided, then one will be generated by the iSNS
1727 server."
1728 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
1729
1730
1731
1732 <span class="grey">Gibbons, et al. Standards Track [Page 31]</span></pre>
1733 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span>
1734 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
1735
1736
1737 ::= { isnsDdsEntry 2 }
1738
1739 isnsDdsStatus OBJECT-TYPE
1740 SYNTAX IsnsDdsStatusType
1741 MAX-ACCESS read-only
1742 STATUS current
1743 DESCRIPTION
1744 "The status of this Discovery Domain Set (DDS)."
1745 REFERENCE "<a href="./rfc4171#section-6.11.1.3">RFC 4171, Section&nbsp;6.11.1.3</a>"
1746 ::= { isnsDdsEntry 3 }
1747
1748 --
1749 -- Discovery Domain Set Members --------------------
1750 --
1751
1752 --
1753 -- DDS Membership Assignment
1754 --
1755
1756 isnsDdsMemberTable OBJECT-TYPE
1757 SYNTAX SEQUENCE OF IsnsDdsMemberEntry
1758 MAX-ACCESS not-accessible
1759 STATUS current
1760 DESCRIPTION
1761 "A table containing Discovery Domains (DDs) that have
1762 been assigned to specific Discovery Domain Sets (DDSs).
1763 The number of rows in the table is dependent on the
1764 number of DD to DDS relationships in the iSNS instance."
1765 ::= { isnsDdsInfo 2 }
1766
1767
1768 isnsDdsMemberEntry OBJECT-TYPE
1769 SYNTAX IsnsDdsMemberEntry
1770 MAX-ACCESS not-accessible
1771 STATUS current
1772 DESCRIPTION
1773 "The mapping of one Discovery Domain (DD) to a Discovery
1774 Domain Set (DDS). This indicates the DD is a member of
1775 the DDS."
1776 INDEX { isnsServerIndex,
1777 isnsDdsId,
1778 isnsDdsMemberDdId }
1779 ::= { isnsDdsMemberTable 1 }
1780
1781 IsnsDdsMemberEntry ::=
1782 SEQUENCE {
1783 isnsDdsMemberDdId IsnsDiscoveryDomainId,
1784 isnsDdsMemberSymbolicName SnmpAdminString
1785
1786
1787
1788 <span class="grey">Gibbons, et al. Standards Track [Page 32]</span></pre>
1789 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span>
1790 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
1791
1792
1793 }
1794
1795 isnsDdsMemberDdId OBJECT-TYPE
1796 SYNTAX IsnsDiscoveryDomainId
1797 MAX-ACCESS not-accessible
1798 STATUS current
1799 DESCRIPTION
1800 "The ID that identifies the Discovery Domain
1801 that is a member of the Discovery Domain Set."
1802 ::= { isnsDdsMemberEntry 1 }
1803
1804 isnsDdsMemberSymbolicName OBJECT-TYPE
1805 SYNTAX SnmpAdminString
1806 MAX-ACCESS read-only
1807 STATUS current
1808 DESCRIPTION
1809 "The Symbolic Name of the Discovery Domain that is a member
1810 of this DDS. This value SHALL be identical to the object
1811 isnsDdSymbolicName for the associated DD ID."
1812 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
1813 ::= { isnsDdsMemberEntry 2 }
1814
1815 --
1816 -- Discovery Domain information
1817 --
1818
1819 isnsDdInfo OBJECT IDENTIFIER ::= { isnsServerInfo 5 }
1820
1821 --
1822 -- Discovery Domain Registrations ------------------------
1823 --
1824
1825 isnsDdTable OBJECT-TYPE
1826 SYNTAX SEQUENCE OF IsnsDdEntry
1827 MAX-ACCESS not-accessible
1828 STATUS current
1829 DESCRIPTION
1830 "A table containing configuration information for each
1831 Discovery Domain (DD) registered in the iSNS. The number
1832 of rows in the table is dependent on the number of DDs
1833 registered in the iSNS instance."
1834 ::= { isnsDdInfo 1 }
1835
1836 isnsDdEntry OBJECT-TYPE
1837 SYNTAX IsnsDdEntry
1838 MAX-ACCESS not-accessible
1839 STATUS current
1840 DESCRIPTION
1841
1842
1843
1844 <span class="grey">Gibbons, et al. Standards Track [Page 33]</span></pre>
1845 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span>
1846 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
1847
1848
1849 "Information on a Discovery Domain (DD) registered in
1850 the iSNS Server instance."
1851 INDEX { isnsServerIndex, isnsDdId}
1852 ::= { isnsDdTable 1 }
1853
1854 IsnsDdEntry::=
1855 SEQUENCE {
1856 isnsDdId IsnsDiscoveryDomainId,
1857 isnsDdSymbolicName SnmpAdminString,
1858 isnsDdFeatures IsnsDdFeatureType
1859 }
1860
1861 isnsDdId OBJECT-TYPE
1862 SYNTAX IsnsDiscoveryDomainId
1863 MAX-ACCESS not-accessible
1864 STATUS current
1865 DESCRIPTION
1866 "The ID that refers to this Discovery Domain, and the
1867 index to the table."
1868 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
1869 ::= { isnsDdEntry 1 }
1870
1871 isnsDdSymbolicName OBJECT-TYPE
1872 SYNTAX SnmpAdminString
1873 MAX-ACCESS read-only
1874 STATUS current
1875 DESCRIPTION
1876 "The Discovery Domain Symbolic Name field contains a
1877 unique variable-length description (up to 255 bytes)
1878 that is associated with the DD."
1879 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
1880 ::= { isnsDdEntry 2 }
1881
1882 isnsDdFeatures OBJECT-TYPE
1883 SYNTAX IsnsDdFeatureType
1884 MAX-ACCESS read-only
1885 STATUS current
1886 DESCRIPTION
1887 "This defines the features the Discovery Domain has."
1888 REFERENCE "<a href="./rfc4171#section-6.11.2.9">RFC 4171, Section&nbsp;6.11.2.9</a>"
1889 ::= { isnsDdEntry 3 }
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900 <span class="grey">Gibbons, et al. Standards Track [Page 34]</span></pre>
1901 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span>
1902 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
1903
1904
1905 --
1906 -- Discovery Domain Members --------------------
1907 --
1908
1909 --
1910 -- DD iSCSI Node Membership Assignment
1911 --
1912
1913 isnsDdIscsiMemberTable OBJECT-TYPE
1914 SYNTAX SEQUENCE OF
1915 IsnsDdIscsiMemberEntry
1916 MAX-ACCESS not-accessible
1917 STATUS current
1918 DESCRIPTION
1919 "A table containing iSCSI node indexes that have been
1920 assigned to specific DDs in this iSNS Server instance. The
1921 number of rows in the table is dependent on the number of
1922 relationships between iSCSI Nodes and DDs registered in the
1923 iSNS instance."
1924 ::= { isnsDdInfo 2 }
1925
1926 isnsDdIscsiMemberEntry OBJECT-TYPE
1927 SYNTAX IsnsDdIscsiMemberEntry
1928 MAX-ACCESS not-accessible
1929 STATUS current
1930 DESCRIPTION
1931 "The mapping of one iSCSI Node to a Discovery Domain to
1932 indicate membership in the DD. The indexes are the iSNS
1933 server instance, the DD ID of the Discovery Domain, and
1934 the iSCSI Node Index of the iSCSI Node."
1935 INDEX { isnsServerIndex,
1936 isnsDdId,
1937 isnsDdIscsiMemberIndex }
1938 ::= { isnsDdIscsiMemberTable 1 }
1939
1940 IsnsDdIscsiMemberEntry::=
1941 SEQUENCE {
1942 isnsDdIscsiMemberIndex IsnsNodeIndexId,
1943 isnsDdIscsiMemberName SnmpAdminString,
1944 isnsDdIscsiMemberIsRegistered TruthValue
1945 }
1946
1947 isnsDdIscsiMemberIndex OBJECT-TYPE
1948 SYNTAX IsnsNodeIndexId
1949 MAX-ACCESS not-accessible
1950 STATUS current
1951 DESCRIPTION
1952 "The index for this member iSCSI node entry."
1953
1954
1955
1956 <span class="grey">Gibbons, et al. Standards Track [Page 35]</span></pre>
1957 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span>
1958 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
1959
1960
1961 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
1962 ::= { isnsDdIscsiMemberEntry 1 }
1963
1964 isnsDdIscsiMemberName OBJECT-TYPE
1965 SYNTAX SnmpAdminString (SIZE (0..223))
1966 MAX-ACCESS read-only
1967 STATUS current
1968 DESCRIPTION
1969 "The iSCSI Name associated with the storage node. The
1970 iSCSI Name cannot be longer than 223 bytes. The iSNS
1971 server internal maximum size is 224 bytes to provide
1972 NULL termination. This is the iSCSI Name for the storage
1973 node that is a member of the DD. This value maps 1 to 1
1974 to the isnsDdIscsiMemberIndex node index. The iSCSI Name
1975 field is too long to be easily used for an index directly.
1976 The node index used for a specific node name is only
1977 persistent across iSNS Server reinitializations for nodes
1978 that are in a Discovery Domain (DD) or are registered
1979 control nodes. This value is only required during row
1980 creation if the storage node is not yet registered in the
1981 iSNS Server instance. If the storage node is not yet
1982 registered, then the iSCSI Name MUST be provided with the
1983 iSCSI node index during row creation in order to create the
1984 1-to-1 mapping."
1985 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
1986 ::= { isnsDdIscsiMemberEntry 2 }
1987
1988 isnsDdIscsiMemberIsRegistered OBJECT-TYPE
1989 SYNTAX TruthValue
1990 MAX-ACCESS read-only
1991 STATUS current
1992 DESCRIPTION
1993 "This indicates whether this member of the DD is currently
1994 registered in the iSNS Server instance. iSCSI Storage
1995 Node members do not need to be currently registered in
1996 order for their iSCSI Name and Index to be added to
1997 a DD."
1998 REFERENCE "<a href="./rfc4171#section-6.11">RFC 4171, Section&nbsp;6.11</a>"
1999 ::= { isnsDdIscsiMemberEntry 3 }
2000
2001 --
2002 -- DD Portal Membership Assignment
2003 --
2004
2005 isnsDdPortalMemberTable OBJECT-TYPE
2006 SYNTAX SEQUENCE OF
2007 IsnsDdPortalMemberEntry
2008 MAX-ACCESS not-accessible
2009
2010
2011
2012 <span class="grey">Gibbons, et al. Standards Track [Page 36]</span></pre>
2013 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span>
2014 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
2015
2016
2017 STATUS current
2018 DESCRIPTION
2019 "A table containing currently registered and unregistered
2020 portal objects that have been explicitly assigned to
2021 specific DDs. Explicit assignment of a portal to a DD
2022 is only done when a specific set of portals are preferred
2023 for use within a DD. Otherwise, for iSCSI, the Portal
2024 Group Object should be used for identifying which portals
2025 provide access to which storage nodes. The number of rows
2026 in the table is dependent on the number of explicit
2027 relationships between portals and DDs registered in the
2028 iSNS."
2029 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
2030 ::= { isnsDdInfo 3 }
2031
2032 isnsDdPortalMemberEntry OBJECT-TYPE
2033 SYNTAX IsnsDdPortalMemberEntry
2034 MAX-ACCESS not-accessible
2035 STATUS current
2036 DESCRIPTION
2037 "Each entry indicates an explicit addition of a portal to a
2038 discovery domain. The explicit addition of an entity portal
2039 to a discovery domain indicates the portal is preferred for
2040 access to nodes of the entity for this discovery domain.
2041 Registered Portal Group objects are used in iSCSI to
2042 indicate mapping of portals to nodes across all discovery
2043 domains. Portals that have been explicitly mapped to a
2044 discovery domain will be returned as part of a query that
2045 is scoped to that discovery domain. If no portal of an
2046 entity has been explicitly mapped to a discovery domain,
2047 then all portals of the entity that provide access to a
2048 storage node are returned as part of a query. The table
2049 indexes are the server instance, the DD ID of the Discovery
2050 Domain, and the Portal Index of the portal."
2051 INDEX { isnsServerIndex,
2052 isnsDdId,
2053 isnsDdPortalMemberIndex }
2054 ::= { isnsDdPortalMemberTable 1 }
2055
2056 IsnsDdPortalMemberEntry ::=
2057 SEQUENCE {
2058 isnsDdPortalMemberIndex IsnsPortalIndexId,
2059 isnsDdPortalMemberAddressType InetAddressType,
2060 isnsDdPortalMemberAddress InetAddress,
2061 isnsDdPortalMemberPortType IsnsPortalPortTypeId,
2062 isnsDdPortalMemberPort InetPortNumber,
2063 isnsDdPortalMemberIsRegistered TruthValue
2064 }
2065
2066
2067
2068 <span class="grey">Gibbons, et al. Standards Track [Page 37]</span></pre>
2069 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span>
2070 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
2071
2072
2073
2074 isnsDdPortalMemberIndex OBJECT-TYPE
2075 SYNTAX IsnsPortalIndexId
2076 MAX-ACCESS not-accessible
2077 STATUS current
2078 DESCRIPTION
2079 "The index for a portal explicitly contained in the discovery
2080 domain. This managed object, combined with isnsServerIndex
2081 and isnsDdId, is the key for this table."
2082 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
2083 ::= { isnsDdPortalMemberEntry 1 }
2084
2085 isnsDdPortalMemberAddressType OBJECT-TYPE
2086 SYNTAX InetAddressType
2087 MAX-ACCESS read-only
2088 STATUS current
2089 DESCRIPTION
2090 "The type of Inet address in isnsDdPortalMemberAddress. If
2091 the address is specified, then it must be a valid unicast
2092 address and the value of this object must be ipv4(1),
2093 ipv6(2), ipv4z(3), or ipv6z(4); otherwise, the value
2094 of this object is unknown(0), and the value of
2095 isnsDdPortalMemberAddress is the zero-length string."
2096 ::= { isnsDdPortalMemberEntry 2 }
2097
2098 isnsDdPortalMemberAddress OBJECT-TYPE
2099 SYNTAX InetAddress
2100 MAX-ACCESS read-only
2101 STATUS current
2102 DESCRIPTION
2103 "The Inet Address for the portal. The format of this
2104 object is specified by isnsDdPortalMemberAddressType."
2105 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
2106 ::= { isnsDdPortalMemberEntry 3 }
2107
2108 isnsDdPortalMemberPortType OBJECT-TYPE
2109 SYNTAX IsnsPortalPortTypeId
2110 MAX-ACCESS read-only
2111 STATUS current
2112 DESCRIPTION
2113 "The port type for the portal, either UDP or TCP."
2114 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
2115 ::= { isnsDdPortalMemberEntry 4 }
2116
2117 isnsDdPortalMemberPort OBJECT-TYPE
2118 SYNTAX InetPortNumber ( 1 .. 65535 )
2119 MAX-ACCESS read-only
2120 STATUS current
2121
2122
2123
2124 <span class="grey">Gibbons, et al. Standards Track [Page 38]</span></pre>
2125 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span>
2126 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
2127
2128
2129 DESCRIPTION
2130 "The port number for the portal. Whether the portal
2131 type is TCP or UDP is indicated by
2132 isnsDdPortalMemberPortType."
2133 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
2134 ::= { isnsDdPortalMemberEntry 5 }
2135
2136 isnsDdPortalMemberIsRegistered OBJECT-TYPE
2137 SYNTAX TruthValue
2138 MAX-ACCESS read-only
2139 STATUS current
2140 DESCRIPTION
2141 "This indicates whether this member of the DD is currently
2142 registered in the iSNS Server instance. Portals that are
2143 DD members do not need to be currently registered in
2144 order for them to be added to a DD."
2145 REFERENCE "<a href="./rfc4171#section-6.11">RFC 4171, Section&nbsp;6.11</a>"
2146 ::= { isnsDdPortalMemberEntry 6 }
2147
2148 --
2149 -- DD FC Port Membership Assignment
2150 --
2151
2152 isnsDdFcPortMemberTable OBJECT-TYPE
2153 SYNTAX SEQUENCE OF
2154 IsnsDdFcPortMemberEntry
2155 MAX-ACCESS not-accessible
2156 STATUS current
2157 DESCRIPTION
2158 "A table containing FC Port World Wide Names (WWN) that
2159 have been assigned to specific DDs. The number of rows
2160 in the table is dependent on the number of relationships
2161 between FC Ports and DDs registered in the iSNS."
2162 ::= { isnsDdInfo 4 }
2163
2164 isnsDdFcPortMemberEntry OBJECT-TYPE
2165 SYNTAX IsnsDdFcPortMemberEntry
2166 MAX-ACCESS not-accessible
2167 STATUS current
2168 DESCRIPTION
2169 "The association of one FC Port with a Discovery Domain.
2170 Membership of an FC Port in a Discovery Domain is
2171 indicated by creating a row for the appropriate DD ID
2172 and FC Port WWN."
2173 INDEX { isnsServerIndex,
2174 isnsDdId,
2175 isnsDdFcPortMemberPortName }
2176 ::= { isnsDdFcPortMemberTable 1 }
2177
2178
2179
2180 <span class="grey">Gibbons, et al. Standards Track [Page 39]</span></pre>
2181 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span>
2182 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
2183
2184
2185
2186 IsnsDdFcPortMemberEntry ::=
2187 SEQUENCE {
2188 isnsDdFcPortMemberPortName FcNameIdOrZero,
2189 isnsDdFcPortMemberIsRegistered TruthValue
2190 }
2191
2192 isnsDdFcPortMemberPortName OBJECT-TYPE
2193 SYNTAX FcNameIdOrZero (SIZE(8))
2194 MAX-ACCESS not-accessible
2195 STATUS current
2196 DESCRIPTION
2197 "The Port WWN of the FC Port that is a member of the DD. The
2198 value MUST be a valid FC WWN, as per the FC-GS (Fibre Channel -
2199 Generic Services) standard. This managed object, combined
2200 with the isnsServerIndex and isnsDdId are the key for this
2201 table. A zero-length string is not a valid value for this
2202 managed object."
2203 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
2204 ::= { isnsDdFcPortMemberEntry 1 }
2205
2206 isnsDdFcPortMemberIsRegistered OBJECT-TYPE
2207 SYNTAX TruthValue
2208 MAX-ACCESS read-only
2209 STATUS current
2210 DESCRIPTION
2211 "This indicates whether this member of the DD is currently
2212 registered in the iSNS Server instance."
2213 REFERENCE "<a href="./rfc4171#section-6.11">RFC 4171, Section&nbsp;6.11</a>"
2214 ::= { isnsDdFcPortMemberEntry 2 }
2215
2216 --
2217 -- Registered Device Information
2218 --
2219
2220 isnsReg OBJECT IDENTIFIER ::= { isnsServerInfo 6 }
2221
2222 isnsRegEntityInfo OBJECT IDENTIFIER
2223 ::= { isnsReg 1 }
2224
2225 --
2226 -- iSNS Registered Entities Table
2227 --
2228
2229 isnsRegEntityTable OBJECT-TYPE
2230 SYNTAX SEQUENCE OF IsnsRegEntityEntry
2231 MAX-ACCESS not-accessible
2232 STATUS current
2233
2234
2235
2236 <span class="grey">Gibbons, et al. Standards Track [Page 40]</span></pre>
2237 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span>
2238 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
2239
2240
2241 DESCRIPTION
2242 "A table containing registered Entity objects in each iSNS
2243 server instance. The number of entries in the table is
2244 dependent on the number of Entity objects registered in the
2245 iSNS Server instances. All Entity objects are registered in
2246 the iSNS using the iSNS protocol."
2247 ::= { isnsRegEntityInfo 1 }
2248
2249 isnsRegEntityEntry OBJECT-TYPE
2250 SYNTAX IsnsRegEntityEntry
2251 MAX-ACCESS not-accessible
2252 STATUS current
2253 DESCRIPTION
2254 "Information on one registered Entity object in an iSNS
2255 server instance."
2256 INDEX { isnsServerIndex,
2257 isnsRegEntityIndex }
2258 ::= { isnsRegEntityTable 1 }
2259
2260 IsnsRegEntityEntry ::=
2261 SEQUENCE {
2262 isnsRegEntityIndex IsnsEntityIndexIdOrZero,
2263 isnsRegEntityEID SnmpAdminString,
2264 isnsRegEntityProtocol Unsigned32,
2265 isnsRegEntityManagementAddressType
2266 InetAddressType,
2267 isnsRegEntityManagementAddress
2268 InetAddress,
2269 isnsRegEntityTimestamp TimeStamp,
2270 isnsRegEntityVersionMin Unsigned32,
2271 isnsRegEntityVersionMax Unsigned32,
2272 isnsRegEntityRegistrationPeriod
2273 Unsigned32
2274 }
2275
2276 isnsRegEntityIndex OBJECT-TYPE
2277 SYNTAX IsnsEntityIndexIdOrZero
2278 ( 1 .. 4294967295 )
2279 MAX-ACCESS not-accessible
2280 STATUS current
2281 DESCRIPTION
2282 "The Entity Index for this entity. This index is assigned
2283 by the iSNS Server when an Entity is initially registered.
2284 The Entity Index can be used to represent a registered
2285 Entity object in situations where the Entity EID would
2286 be too long/unwieldy. Zero is not a valid value for this
2287 object."
2288 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
2289
2290
2291
2292 <span class="grey">Gibbons, et al. Standards Track [Page 41]</span></pre>
2293 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span>
2294 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
2295
2296
2297 ::= { isnsRegEntityEntry 1 }
2298
2299 isnsRegEntityEID OBJECT-TYPE
2300 SYNTAX SnmpAdminString
2301 MAX-ACCESS read-only
2302 STATUS current
2303 DESCRIPTION
2304 "The EID is a unique registered Entity object identifier, as
2305 specified in the iSNS Specification. This is the iSNS
2306 Entity Identifier for the registered Entity object."
2307 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
2308 ::= { isnsRegEntityEntry 2 }
2309
2310 isnsRegEntityProtocol OBJECT-TYPE
2311 SYNTAX Unsigned32 ( 1 .. 4294967295 )
2312 MAX-ACCESS read-only
2313 STATUS current
2314 DESCRIPTION
2315 "The block storage protocol supported by this entity, as
2316 defined in the iSNS Specification, <a href="#section-6.2.2">Section 6.2.2</a>. The
2317 following values are initially assigned.
2318
2319 Type Value Entity Type
2320 ---------- -----------
2321 1 No Protocol
2322 2 iSCSI
2323 3 iFCP
2324 All Others As assigned by IANA
2325
2326 The full set of current Block Storage Protocols are
2327 specified in the IANA-maintained registry of assigned
2328 iSNS parameters. Please refer to <a href="./rfc4171">RFC 4171</a> and the iSNS
2329 parameters maintained at IANA."
2330 REFERENCE "<a href="./rfc4171#section-6.2.2">RFC 4171, Section&nbsp;6.2.2</a>, and IANA Assignments"
2331 ::= { isnsRegEntityEntry 3 }
2332
2333 isnsRegEntityManagementAddressType OBJECT-TYPE
2334 SYNTAX InetAddressType
2335 MAX-ACCESS read-only
2336 STATUS current
2337 DESCRIPTION
2338 "The type of Inet address in isnsRegEntityManagementAddress.
2339 If the address is specified, then it must be a valid unicast
2340 address and the value of this object must be ipv4(1),
2341 ipv6(2), ipv4z(3), or ipv6z(4); otherwise, the value of
2342 this object is unknown(0), and the value of
2343 isnsRegEntityManagementAddress is the zero-length string."
2344 ::= { isnsRegEntityEntry 4 }
2345
2346
2347
2348 <span class="grey">Gibbons, et al. Standards Track [Page 42]</span></pre>
2349 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span>
2350 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
2351
2352
2353
2354 isnsRegEntityManagementAddress OBJECT-TYPE
2355 SYNTAX InetAddress
2356 MAX-ACCESS read-only
2357 STATUS current
2358 DESCRIPTION
2359 "The iSNS Management IP Address for the registered Entity
2360 object. The format of this object is specified by
2361 isnsRegEntityManagementAddressType."
2362 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
2363 ::= { isnsRegEntityEntry 5 }
2364
2365 isnsRegEntityTimestamp OBJECT-TYPE
2366 SYNTAX TimeStamp
2367 MAX-ACCESS read-only
2368 STATUS current
2369 DESCRIPTION
2370 "The iSNS Entity Registration Timestamp for the registered
2371 Entity object. This is the most recent date and time that
2372 the registered Entity object, and associated registered
2373 objects contained in the Entity, were registered or
2374 updated."
2375 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
2376 ::= { isnsRegEntityEntry 6 }
2377
2378 isnsRegEntityVersionMin OBJECT-TYPE
2379 SYNTAX Unsigned32 ( 0 .. 254 | 255 )
2380 MAX-ACCESS read-only
2381 STATUS current
2382 DESCRIPTION
2383 "The minimum version supported for the block storage protocol
2384 specified by isnsRegEntityProtocol. The protocol version
2385 specified can be from 1 to 254. A value of 255 is a wildcard
2386 value, indicating no minimum version value has been specified
2387 for this Entity. Entity registrations with an
2388 isnsRegEntityProtocol of 'No Protocol' SHALL have an
2389 isnsRegEntityVersionMin value of 0."
2390 REFERENCE "<a href="./rfc4171#section-6.2.5">RFC 4171, Section&nbsp;6.2.5</a>"
2391 ::= { isnsRegEntityEntry 7 }
2392
2393 isnsRegEntityVersionMax OBJECT-TYPE
2394 SYNTAX Unsigned32 ( 0 .. 254 | 255 )
2395 MAX-ACCESS read-only
2396 STATUS current
2397 DESCRIPTION
2398 "The maximum version supported for the block storage protocol
2399 specified by isnsRegEntityProtocol. The protocol version
2400 specified can be from 1 to 254. A value of 255 is a wildcard
2401
2402
2403
2404 <span class="grey">Gibbons, et al. Standards Track [Page 43]</span></pre>
2405 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-44" ></span>
2406 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
2407
2408
2409 value, indicating no maximum version value has been specified
2410 for this Entity. Entity registrations with an
2411 isnsRegEntityProtocol of 'No Protocol' SHALL have an
2412 isnsRegEntityVersionMax value of 0."
2413 REFERENCE "<a href="./rfc4171#section-6.2.5">RFC 4171, Section&nbsp;6.2.5</a>"
2414 ::= { isnsRegEntityEntry 8 }
2415
2416 isnsRegEntityRegistrationPeriod OBJECT-TYPE
2417 SYNTAX Unsigned32 ( 0 .. 4294967295 )
2418 UNITS "seconds"
2419 MAX-ACCESS read-only
2420 STATUS current
2421 DESCRIPTION
2422 "The iSNS Entity Status Inquiry (ESI) registration period,
2423 which indicates the maximum time, in seconds, that the
2424 registration will be maintained without receipt of an iSNSP
2425 message from the entity. If the Registration Period is set
2426 to 0, then the Entity SHALL NOT be deregistered due to no
2427 contact with the entity."
2428 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
2429 ::= { isnsRegEntityEntry 9 }
2430
2431 --
2432 -- Registered Objects Associated With an Entity Information
2433 --
2434
2435 isnsRegEntityNumObjectsTable OBJECT-TYPE
2436 SYNTAX SEQUENCE OF
2437 IsnsRegEntityNumObjectsEntry
2438 MAX-ACCESS not-accessible
2439 STATUS current
2440 DESCRIPTION
2441 "A table containing information on the number of registered
2442 objects associated with a registered Entity in the iSNS
2443 server instance. The number of entries in the table is
2444 dependent on the number of registered Entity objects in the
2445 iSNS."
2446 ::= { isnsRegEntityInfo 2 }
2447
2448 isnsRegEntityNumObjectsEntry OBJECT-TYPE
2449 SYNTAX IsnsRegEntityNumObjectsEntry
2450 MAX-ACCESS not-accessible
2451 STATUS current
2452 DESCRIPTION
2453 "Information on the number of registered objects associated
2454 with a registered Entity object in an iSNS Server instance."
2455 INDEX { isnsServerIndex,
2456 isnsRegEntityIndex }
2457
2458
2459
2460 <span class="grey">Gibbons, et al. Standards Track [Page 44]</span></pre>
2461 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-45" ></span>
2462 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
2463
2464
2465 ::= { isnsRegEntityNumObjectsTable 1 }
2466
2467 IsnsRegEntityNumObjectsEntry ::=
2468 SEQUENCE {
2469 isnsRegEntityInfoNumPortals Gauge32,
2470 isnsRegEntityInfoNumPortalGroups Gauge32,
2471 isnsRegEntityInfoNumIscsiNodes Gauge32,
2472 isnsRegEntityInfoNumFcPorts Gauge32,
2473 isnsRegEntityInfoNumFcNodes Gauge32
2474 }
2475
2476 isnsRegEntityInfoNumPortals OBJECT-TYPE
2477 SYNTAX Gauge32 ( 0 .. 4294967295 )
2478 MAX-ACCESS read-only
2479 STATUS current
2480 DESCRIPTION
2481 "The number of Portals associated with this Entity."
2482 ::= { isnsRegEntityNumObjectsEntry 1 }
2483
2484 isnsRegEntityInfoNumPortalGroups OBJECT-TYPE
2485 SYNTAX Gauge32 ( 0 .. 4294967295 )
2486 MAX-ACCESS read-only
2487 STATUS current
2488 DESCRIPTION
2489 "The number of Portal Groups associated with this Entity."
2490 ::= { isnsRegEntityNumObjectsEntry 2 }
2491
2492 isnsRegEntityInfoNumIscsiNodes OBJECT-TYPE
2493 SYNTAX Gauge32 ( 0 .. 4294967295 )
2494 MAX-ACCESS read-only
2495 STATUS current
2496 DESCRIPTION
2497 "The number of iSCSI Storage Nodes associated with this
2498 Entity."
2499 ::= { isnsRegEntityNumObjectsEntry 3 }
2500
2501 isnsRegEntityInfoNumFcPorts OBJECT-TYPE
2502 SYNTAX Gauge32 ( 0 .. 4294967295 )
2503 MAX-ACCESS read-only
2504 STATUS current
2505 DESCRIPTION
2506 "The number of FC Ports associated with this Entity."
2507 ::= { isnsRegEntityNumObjectsEntry 4 }
2508
2509 isnsRegEntityInfoNumFcNodes OBJECT-TYPE
2510 SYNTAX Gauge32 ( 0 .. 4294967295 )
2511 MAX-ACCESS read-only
2512 STATUS current
2513
2514
2515
2516 <span class="grey">Gibbons, et al. Standards Track [Page 45]</span></pre>
2517 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-46" ></span>
2518 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
2519
2520
2521 DESCRIPTION
2522 "The number of FC Nodes associated with this Entity."
2523 ::= { isnsRegEntityNumObjectsEntry 5 }
2524
2525 --
2526 -- iSNS Registered Portal Information
2527 --
2528
2529 isnsRegPortalInfo OBJECT IDENTIFIER
2530 ::= { isnsReg 2 }
2531
2532 --
2533 -- iSNS Registered Portal Table
2534 --
2535
2536 isnsRegPortalTable OBJECT-TYPE
2537 SYNTAX SEQUENCE OF IsnsRegPortalEntry
2538 MAX-ACCESS not-accessible
2539 STATUS current
2540 DESCRIPTION
2541 "A table containing the registered Portals in the iSNS.
2542 The number of entries is dependent on the number of
2543 Portals registered in the iSNS."
2544 ::= { isnsRegPortalInfo 1 }
2545
2546 isnsRegPortalEntry OBJECT-TYPE
2547 SYNTAX IsnsRegPortalEntry
2548 MAX-ACCESS not-accessible
2549 STATUS current
2550 DESCRIPTION
2551 "Information on one registered Entity Portal in the iSNS.
2552 The Entity Index is part of the table index to quickly
2553 find Portals that support a specific Entity."
2554 INDEX { isnsServerIndex,
2555 isnsRegEntityIndex,
2556 isnsRegPortalPortalIndex }
2557 ::= { isnsRegPortalTable 1 }
2558
2559 IsnsRegPortalEntry ::=
2560 SEQUENCE {
2561 isnsRegPortalPortalIndex IsnsPortalIndexId,
2562 isnsRegPortalAddressType InetAddressType,
2563 isnsRegPortalAddress InetAddress,
2564 isnsRegPortalPortType IsnsPortalPortTypeId,
2565 isnsRegPortalPort InetPortNumber,
2566 isnsRegPortalSymbolicName SnmpAdminString,
2567 isnsRegPortalEsiInterval Unsigned32,
2568 isnsRegPortalEsiPortType IsnsPortalPortTypeId,
2569
2570
2571
2572 <span class="grey">Gibbons, et al. Standards Track [Page 46]</span></pre>
2573 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-47" ></span>
2574 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
2575
2576
2577 isnsRegPortalEsiPort InetPortNumber,
2578 isnsRegPortalScnPortType IsnsPortalPortTypeId,
2579 isnsRegPortalScnPort InetPortNumber,
2580 isnsRegPortalSecurityInfo IsnsPortalSecurityType
2581 }
2582
2583 isnsRegPortalPortalIndex OBJECT-TYPE
2584 SYNTAX IsnsPortalIndexId
2585 MAX-ACCESS not-accessible
2586 STATUS current
2587 DESCRIPTION
2588 "The index for this Entity Portal."
2589 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
2590 ::= { isnsRegPortalEntry 1 }
2591
2592 isnsRegPortalAddressType OBJECT-TYPE
2593 SYNTAX InetAddressType
2594 MAX-ACCESS read-only
2595 STATUS current
2596 DESCRIPTION
2597 "The type of Inet address in isnsRegPortalAddress. If the
2598 address is specified, then it must be a valid unicast
2599 address and the value of this object must be ipv4(1),
2600 ipv6(2), ipv4z(3), or ipv6z(4); otherwise, the value
2601 of this object is unknown(0), and the value of
2602 isnsRegPortalAddress is the zero-length string."
2603 ::= { isnsRegPortalEntry 2 }
2604
2605 isnsRegPortalAddress OBJECT-TYPE
2606 SYNTAX InetAddress
2607 MAX-ACCESS read-only
2608 STATUS current
2609 DESCRIPTION
2610 "The Inet Address for this Portal as defined in the iSNS
2611 Specification, <a href="./rfc4171">RFC 4171</a>. The format of this object is
2612 specified by isnsRegPortalAddressType."
2613 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
2614 ::= { isnsRegPortalEntry 3 }
2615
2616 isnsRegPortalPortType OBJECT-TYPE
2617 SYNTAX IsnsPortalPortTypeId
2618 MAX-ACCESS read-only
2619 STATUS current
2620 DESCRIPTION
2621 "The port type for this Portal, either UDP or TCP, as
2622 defined in the iSNS Specification, <a href="./rfc4171">RFC 4171</a>."
2623 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
2624 ::= { isnsRegPortalEntry 4 }
2625
2626
2627
2628 <span class="grey">Gibbons, et al. Standards Track [Page 47]</span></pre>
2629 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-48" ></span>
2630 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
2631
2632
2633
2634 isnsRegPortalPort OBJECT-TYPE
2635 SYNTAX InetPortNumber ( 1 .. 65535 )
2636 MAX-ACCESS read-only
2637 STATUS current
2638 DESCRIPTION
2639 "The port number for this Portal as defined in the
2640 iSNS Specification, <a href="./rfc4171">RFC 4171</a>. Whether the Portal type
2641 is TCP or UDP is indicated by isnsRegPortalPortType."
2642 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
2643 ::= { isnsRegPortalEntry 5 }
2644
2645 isnsRegPortalSymbolicName OBJECT-TYPE
2646 SYNTAX SnmpAdminString
2647 MAX-ACCESS read-only
2648 STATUS current
2649 DESCRIPTION
2650 "The Symbolic Name for this Portal as defined in the iSNS
2651 Specification, <a href="./rfc4171">RFC 4171</a>. If not provided, then the string
2652 SHALL be zero-length."
2653 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
2654 ::= { isnsRegPortalEntry 6 }
2655
2656 isnsRegPortalEsiInterval OBJECT-TYPE
2657 SYNTAX Unsigned32 ( 0 .. 65535 )
2658 UNITS "seconds"
2659 MAX-ACCESS read-only
2660 STATUS current
2661 DESCRIPTION
2662 "The Entity Status Inquiry (ESI) Interval for this Portal
2663 as defined in the iSNS Specification, <a href="./rfc4171">RFC 4171</a>. A value of
2664 0 indicates that ESI monitoring has not been configured for
2665 this Portal."
2666 REFERENCE "<a href="./rfc4171#section-6.3.4">RFC 4171, Section&nbsp;6.3.4</a>"
2667 ::= { isnsRegPortalEntry 7 }
2668
2669 isnsRegPortalEsiPortType OBJECT-TYPE
2670 SYNTAX IsnsPortalPortTypeId
2671 MAX-ACCESS read-only
2672 STATUS current
2673 DESCRIPTION
2674 "The port type for the ESI Port, either UDP or TCP, as
2675 defined in the iSNS Specification, <a href="./rfc4171">RFC 4171</a>."
2676 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
2677 ::= { isnsRegPortalEntry 8 }
2678
2679 isnsRegPortalEsiPort OBJECT-TYPE
2680 SYNTAX InetPortNumber
2681
2682
2683
2684 <span class="grey">Gibbons, et al. Standards Track [Page 48]</span></pre>
2685 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-49" ></span>
2686 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
2687
2688
2689 MAX-ACCESS read-only
2690 STATUS current
2691 DESCRIPTION
2692 "The TCP or UDP port number used for ESI monitoring. Whether
2693 the port type is TCP or UDP is indicated by
2694 isnsRegPortalEsiPortType. A value of 0 indicates that ESI
2695 monitoring is not enabled for this Portal."
2696 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
2697 ::= { isnsRegPortalEntry 9 }
2698
2699 isnsRegPortalScnPortType OBJECT-TYPE
2700 SYNTAX IsnsPortalPortTypeId
2701 MAX-ACCESS read-only
2702 STATUS current
2703 DESCRIPTION
2704 "The port type for the SCN Port, either UDP or TCP, as
2705 defined in the iSNS Specification, <a href="./rfc4171">RFC 4171</a>."
2706 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
2707 ::= { isnsRegPortalEntry 10 }
2708
2709 isnsRegPortalScnPort OBJECT-TYPE
2710 SYNTAX InetPortNumber
2711 MAX-ACCESS read-only
2712 STATUS current
2713 DESCRIPTION
2714 "The TCP or UDP port used to receive SCN messages from the
2715 iSNS Server. Whether the port type is TCP or UDP is
2716 indicated by isnsRegPortalScnPortType. A value of 0
2717 indicates that SCN message receipt is not enabled for this
2718 Portal."
2719 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
2720 ::= { isnsRegPortalEntry 11 }
2721
2722 isnsRegPortalSecurityInfo OBJECT-TYPE
2723 SYNTAX IsnsPortalSecurityType
2724 MAX-ACCESS read-only
2725 STATUS current
2726 DESCRIPTION
2727 "Indicates security attribute settings for the Portal as
2728 registered in the iSNS server. The bit for bitmapVALID must
2729 be set in order for this attribute to contain valid
2730 information. Setting a bit to 1 indicates the
2731 feature is enabled."
2732 REFERENCE "<a href="./rfc4171#section-6.3.9">RFC 4171, Section&nbsp;6.3.9</a>"
2733 ::= { isnsRegPortalEntry 12 }
2734
2735
2736
2737
2738
2739
2740 <span class="grey">Gibbons, et al. Standards Track [Page 49]</span></pre>
2741 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-50" ></span>
2742 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
2743
2744
2745 --
2746 -- iSNS Registered Portal Group Information
2747 --
2748
2749 isnsRegPortalGroupInfo OBJECT IDENTIFIER
2750 ::= { isnsReg 3 }
2751
2752 --
2753 -- iSNS Registered Portal Group (PG) Table
2754 --
2755
2756 isnsRegPgTable OBJECT-TYPE
2757 SYNTAX SEQUENCE OF IsnsRegPgEntry
2758 MAX-ACCESS not-accessible
2759 STATUS current
2760 DESCRIPTION
2761 "A table containing the registered Portal Groups (PGs) in
2762 the iSNS Server instance. The number of entries is
2763 dependent on the number of Portal Groups registered in
2764 the iSNS."
2765 ::= { isnsRegPortalGroupInfo 1 }
2766
2767 isnsRegPgEntry OBJECT-TYPE
2768 SYNTAX IsnsRegPgEntry
2769 MAX-ACCESS not-accessible
2770 STATUS current
2771 DESCRIPTION
2772 "Information on one registered Portal Group in the iSNS
2773 server instance. The Entity Index is part of the table
2774 index to quickly find Portal Groups that support Portals
2775 and iSCSI Storage Nodes in a specific Entity."
2776 INDEX { isnsServerIndex,
2777 isnsRegEntityIndex,
2778 isnsRegPgIndex }
2779 ::= { isnsRegPgTable 1 }
2780
2781 IsnsRegPgEntry ::=
2782 SEQUENCE {
2783 isnsRegPgIndex IsnsPortalGroupIndexId,
2784 isnsRegPgIscsiNodeIndex IsnsNodeIndexId,
2785 isnsRegPgIscsiName SnmpAdminString,
2786 isnsRegPgPortalPortalIndex IsnsPortalIndexId,
2787 isnsRegPgPortalAddressType InetAddressType,
2788 isnsRegPgPortalAddress InetAddress,
2789 isnsRegPgPortalPortType IsnsPortalPortTypeId,
2790 isnsRegPgPortalPort InetPortNumber,
2791 isnsRegPgPGT IsnsPortalGroupTagIdOrNull
2792 }
2793
2794
2795
2796 <span class="grey">Gibbons, et al. Standards Track [Page 50]</span></pre>
2797 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-51" ></span>
2798 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
2799
2800
2801
2802 isnsRegPgIndex OBJECT-TYPE
2803 SYNTAX IsnsPortalGroupIndexId
2804 MAX-ACCESS not-accessible
2805 STATUS current
2806 DESCRIPTION
2807 "The PG Index for this node. The index is created by the
2808 iSNS Server instance for uniquely identifying registered
2809 objects. The PG object is registered at the same time a
2810 Portal or Storage Node is registered using the iSNS
2811 protocol."
2812 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
2813 ::= { isnsRegPgEntry 1 }
2814
2815 isnsRegPgIscsiNodeIndex OBJECT-TYPE
2816 SYNTAX IsnsNodeIndexId
2817 MAX-ACCESS read-only
2818 STATUS current
2819 DESCRIPTION
2820 "The index for the iSCSI Node associated with this PG.
2821 This index can be used to reference the
2822 isnsRegIscsiNodeTable."
2823 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
2824 ::= { isnsRegPgEntry 2 }
2825
2826 isnsRegPgIscsiName OBJECT-TYPE
2827 SYNTAX SnmpAdminString (SIZE (0..223))
2828 MAX-ACCESS read-only
2829 STATUS current
2830 DESCRIPTION
2831 "The iSCSI Name of the initiator or target associated with
2832 the storage node. The iSCSI Name cannot be longer than
2833 223 bytes. The iSNS Server internal maximum size is 224
2834 bytes to provide NULL termination. This is the PG iSCSI
2835 Name that uniquely identifies the iSCSI Storage Node that
2836 is associated with this PG."
2837 ::= { isnsRegPgEntry 3 }
2838
2839 isnsRegPgPortalPortalIndex OBJECT-TYPE
2840 SYNTAX IsnsPortalIndexId
2841 MAX-ACCESS read-only
2842 STATUS current
2843 DESCRIPTION
2844 "The Portal Index for the Portal associated with this PG.
2845 This index can be used to reference the isnsRegPortalTable."
2846 ::= { isnsRegPgEntry 4 }
2847
2848 isnsRegPgPortalAddressType OBJECT-TYPE
2849
2850
2851
2852 <span class="grey">Gibbons, et al. Standards Track [Page 51]</span></pre>
2853 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-52" ></span>
2854 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
2855
2856
2857 SYNTAX InetAddressType
2858 MAX-ACCESS read-only
2859 STATUS current
2860 DESCRIPTION
2861 "The type of Inet address in isnsRegPgPortalAddress. If
2862 the address is specified, then it must be a valid unicast
2863 address and the value of this object must be ipv4(1),
2864 ipv6(2), ipv4z(3), or ipv6z(4); otherwise, the value
2865 of this object is unknown(0), and the value of
2866 isnsRegPgPortalAddress is the zero-length string."
2867 ::= { isnsRegPgEntry 5 }
2868
2869 isnsRegPgPortalAddress OBJECT-TYPE
2870 SYNTAX InetAddress
2871 MAX-ACCESS read-only
2872 STATUS current
2873 DESCRIPTION
2874 "The Inet Address for the Portal that is associated with
2875 the PG. The format of this object is specified by
2876 isnsRegPgPortalAddressType."
2877 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
2878 ::= { isnsRegPgEntry 6 }
2879
2880 isnsRegPgPortalPortType OBJECT-TYPE
2881 SYNTAX IsnsPortalPortTypeId
2882 MAX-ACCESS read-only
2883 STATUS current
2884 DESCRIPTION
2885 "The port type, either UDP or TCP, for the Portal that
2886 is associated with this registered PG object."
2887 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
2888 ::= { isnsRegPgEntry 7 }
2889
2890 isnsRegPgPortalPort OBJECT-TYPE
2891 SYNTAX InetPortNumber ( 1 .. 65535 )
2892 MAX-ACCESS read-only
2893 STATUS current
2894 DESCRIPTION
2895 "The port number for the Portal that is associated with
2896 this registered PG object. Whether the Portal type is
2897 TCP or UDP is indicated by isnsRegPgPortalPortType."
2898 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
2899 ::= { isnsRegPgEntry 8 }
2900
2901 isnsRegPgPGT OBJECT-TYPE
2902 SYNTAX IsnsPortalGroupTagIdOrNull
2903 MAX-ACCESS read-only
2904 STATUS current
2905
2906
2907
2908 <span class="grey">Gibbons, et al. Standards Track [Page 52]</span></pre>
2909 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-53" ></span>
2910 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
2911
2912
2913 DESCRIPTION
2914 "The Portal Group Tag (PGT) for the registered iSCSI Portal
2915 Group object in an iSNS Server instance. This indicates
2916 the tag value that the Portal uses for access to the iSCSI
2917 Storage Node. The PGT is used for coordinated access
2918 between multiple Portals, as described in the iSCSI
2919 Specification, <a href="./rfc3720">RFC 3720</a>. A PGT with no association is a
2920 NULL value. The value of -1 indicates a NULL value."
2921 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>, and <a href="./rfc3720">RFC 3720</a>"
2922 ::= { isnsRegPgEntry 9 }
2923
2924 --
2925 -- iSNS Registered iSCSI Node Information
2926 --
2927
2928 isnsRegIscsiNodeInfo OBJECT IDENTIFIER ::= { isnsReg 4 }
2929
2930 --
2931 -- iSNS Registered iSCSI Node Table
2932 --
2933
2934 isnsRegIscsiNodeTable OBJECT-TYPE
2935 SYNTAX SEQUENCE OF IsnsRegIscsiNodeEntry
2936 MAX-ACCESS not-accessible
2937 STATUS current
2938 DESCRIPTION
2939 "A table containing the registered iSCSI Nodes in the iSNS
2940 server instance. Storage devices register using the iSNS
2941 protocol. While a device cannot be registered in an iSNS
2942 server using SNMP, an entry can be deleted in order to
2943 remove 'stale' entries. The number of entries is related
2944 to the number of iSCSI nodes registered in the iSNS."
2945 ::= { isnsRegIscsiNodeInfo 1 }
2946
2947 isnsRegIscsiNodeEntry OBJECT-TYPE
2948 SYNTAX IsnsRegIscsiNodeEntry
2949 MAX-ACCESS not-accessible
2950 STATUS current
2951 DESCRIPTION
2952 "Information on one iSCSI node that has been registered in
2953 the iSNS Server instance. New rows cannot be added using
2954 SNMP."
2955 INDEX { isnsServerIndex,
2956 isnsRegEntityIndex,
2957 isnsRegIscsiNodeIndex }
2958 ::= { isnsRegIscsiNodeTable 1 }
2959
2960 IsnsRegIscsiNodeEntry ::= SEQUENCE {
2961
2962
2963
2964 <span class="grey">Gibbons, et al. Standards Track [Page 53]</span></pre>
2965 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-54" ></span>
2966 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
2967
2968
2969 isnsRegIscsiNodeIndex IsnsNodeIndexId,
2970 isnsRegIscsiNodeName SnmpAdminString,
2971 isnsRegIscsiNodeType IsnsIscsiNodeType,
2972 isnsRegIscsiNodeAlias SnmpAdminString,
2973 isnsRegIscsiNodeScnTypes IsnsIscsiScnType,
2974 isnsRegIscsiNodeWwnToken FcNameIdOrZero,
2975 isnsRegIscsiNodeAuthMethod SnmpAdminString
2976 }
2977
2978 isnsRegIscsiNodeIndex OBJECT-TYPE
2979 SYNTAX IsnsNodeIndexId
2980 MAX-ACCESS not-accessible
2981 STATUS current
2982 DESCRIPTION
2983 "The index for this iSCSI node."
2984 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
2985 ::= { isnsRegIscsiNodeEntry 1 }
2986
2987 isnsRegIscsiNodeName OBJECT-TYPE
2988 SYNTAX SnmpAdminString (SIZE (0..223))
2989 MAX-ACCESS read-only
2990 STATUS current
2991 DESCRIPTION
2992 "The iSCSI Name of the initiator or target associated with
2993 the storage node. The iSCSI Name cannot be longer than
2994 223 bytes. The iSNS Server internal maximum size is 224
2995 bytes to provide NULL termination. This is the iSCSI Name
2996 that uniquely identifies the initiator, initiator/target,
2997 target, or control node in the network."
2998 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
2999 ::= { isnsRegIscsiNodeEntry 2 }
3000
3001 isnsRegIscsiNodeType OBJECT-TYPE
3002 SYNTAX IsnsIscsiNodeType
3003 MAX-ACCESS read-only
3004 STATUS current
3005 DESCRIPTION
3006 "The Node Type defining the functions of this iSCSI node."
3007 ::= { isnsRegIscsiNodeEntry 3 }
3008
3009 isnsRegIscsiNodeAlias OBJECT-TYPE
3010 SYNTAX SnmpAdminString
3011 MAX-ACCESS read-only
3012 STATUS current
3013 DESCRIPTION
3014 "The Alias name of the iSCSI node. This is a variable-length
3015 text-based description of up to 255 bytes."
3016 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
3017
3018
3019
3020 <span class="grey">Gibbons, et al. Standards Track [Page 54]</span></pre>
3021 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-55" ></span>
3022 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
3023
3024
3025 ::= { isnsRegIscsiNodeEntry 4 }
3026
3027 isnsRegIscsiNodeScnTypes OBJECT-TYPE
3028 SYNTAX IsnsIscsiScnType
3029 MAX-ACCESS read-only
3030 STATUS current
3031 DESCRIPTION
3032 "The State Change Notification (SCN) types enabled for this
3033 iSCSI node."
3034 REFERENCE "<a href="./rfc4171#section-6.4.4">RFC 4171, Section&nbsp;6.4.4</a>"
3035 ::= { isnsRegIscsiNodeEntry 5 }
3036
3037 isnsRegIscsiNodeWwnToken OBJECT-TYPE
3038 SYNTAX FcNameIdOrZero
3039 MAX-ACCESS read-only
3040 STATUS current
3041 DESCRIPTION
3042 "This contains a globally unique 64-bit integer value that
3043 can be used to represent the World Wide Node Name of the
3044 iSCSI device in a Fibre Channel fabric. This identifier is
3045 used during the device registration process, and MUST
3046 conform to the requirements in <a href="./rfc4171">RFC 4171</a>. A zero-length string
3047 for this managed object indicates that a Node WWN token has
3048 not been assigned."
3049 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
3050 ::= { isnsRegIscsiNodeEntry 6 }
3051
3052 isnsRegIscsiNodeAuthMethod OBJECT-TYPE
3053 SYNTAX SnmpAdminString
3054 MAX-ACCESS read-only
3055 STATUS current
3056 DESCRIPTION
3057 "This attribute contains a null-terminated string containing
3058 UTF-8 text listing the iSCSI authentication methods enabled
3059 for this iSCSI Node, in order of preference. The text
3060 values used to identify iSCSI authentication methods are
3061 embedded in this string attribute and delineated by a
3062 comma. The text values are identical to those found in
3063 <a href="./rfc3720">RFC 3720</a> - iSCSI. Additional vendor-specific text values
3064 are also possible."
3065 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>, and <a href="./rfc3720">RFC 3720</a>"
3066 ::= { isnsRegIscsiNodeEntry 7 }
3067
3068 --
3069 -- iSNS Registered FC Node Information
3070 --
3071
3072 isnsRegFcNodeInfo OBJECT IDENTIFIER ::= { isnsReg 5 }
3073
3074
3075
3076 <span class="grey">Gibbons, et al. Standards Track [Page 55]</span></pre>
3077 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-56" ></span>
3078 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
3079
3080
3081
3082 --
3083 -- iSNS Registered FC Node Table
3084 --
3085
3086 isnsRegFcNodeTable OBJECT-TYPE
3087 SYNTAX SEQUENCE OF IsnsRegFcNodeEntry
3088 MAX-ACCESS not-accessible
3089 STATUS current
3090 DESCRIPTION
3091 "A table containing the registered FC Nodes in the iSNS.
3092 This supports iFCP as defined in <a href="./rfc4172">RFC 4172</a>."
3093 ::= { isnsRegFcNodeInfo 1 }
3094
3095 isnsRegFcNodeEntry OBJECT-TYPE
3096 SYNTAX IsnsRegFcNodeEntry
3097 MAX-ACCESS not-accessible
3098 STATUS current
3099 DESCRIPTION
3100 "Information on one registered FC node that has been
3101 registered in the iSNS."
3102 INDEX { isnsServerIndex,
3103 isnsRegFcNodeWwnn }
3104 ::= { isnsRegFcNodeTable 1 }
3105
3106 IsnsRegFcNodeEntry ::= SEQUENCE {
3107 isnsRegFcNodeWwnn FcNameIdOrZero,
3108 isnsRegFcNodeSymbolicName SnmpAdminString,
3109 isnsRegFcNodeAddressType InetAddressType,
3110 isnsRegFcNodeAddress InetAddress,
3111 isnsRegFcNodeIPA OCTET STRING,
3112 isnsRegFcNodeProxyIscsiName SnmpAdminString,
3113 isnsRegFcNodeNumFcPorts Gauge32
3114 }
3115
3116 isnsRegFcNodeWwnn OBJECT-TYPE
3117 SYNTAX FcNameIdOrZero (SIZE(8))
3118 MAX-ACCESS not-accessible
3119 STATUS current
3120 DESCRIPTION
3121 "The FC Node World Wide Node Name as defined in the iSNS
3122 Specification, <a href="./rfc4171">RFC 4171</a>. A zero-length string is not valid
3123 for this managed object."
3124 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
3125 ::= { isnsRegFcNodeEntry 1 }
3126
3127 isnsRegFcNodeSymbolicName OBJECT-TYPE
3128 SYNTAX SnmpAdminString
3129
3130
3131
3132 <span class="grey">Gibbons, et al. Standards Track [Page 56]</span></pre>
3133 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-57" ></span>
3134 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
3135
3136
3137 MAX-ACCESS read-only
3138 STATUS current
3139 DESCRIPTION
3140 "The FC Node Symbolic Name of the node as defined in the
3141 iSNS Specification, <a href="./rfc4171">RFC 4171</a>. This is a variable-length
3142 text-based description. If not provided, then the string
3143 SHALL be zero-length."
3144 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
3145 ::= { isnsRegFcNodeEntry 2 }
3146
3147 isnsRegFcNodeAddressType OBJECT-TYPE
3148 SYNTAX InetAddressType
3149 MAX-ACCESS read-only
3150 STATUS current
3151 DESCRIPTION
3152 "The type of Inet address in isnsRegFcNodeAddress. If
3153 the address is specified, then it must be a valid unicast
3154 address and the value of this object must be ipv4(1),
3155 ipv6(2), ipv4z(3), or ipv6z(4); otherwise, the value
3156 of this object is unknown(0), and the value of
3157 isnsRegFcNodeAddress is the zero-length string."
3158 ::= { isnsRegFcNodeEntry 3 }
3159
3160 isnsRegFcNodeAddress OBJECT-TYPE
3161 SYNTAX InetAddress
3162 MAX-ACCESS read-only
3163 STATUS current
3164 DESCRIPTION
3165 "The FC Node Inet address of the node as defined in the
3166 iSNS Specification, <a href="./rfc4171">RFC 4171</a>. The format of this object is
3167 specified by isnsRegFcNodeAddressType."
3168 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
3169 ::= { isnsRegFcNodeEntry 4 }
3170
3171 isnsRegFcNodeIPA OBJECT-TYPE
3172 SYNTAX OCTET STRING (SIZE(8))
3173 MAX-ACCESS read-only
3174 STATUS current
3175 DESCRIPTION
3176 "This managed object identifies the FC Initial Process
3177 Associator of the node as defined in the iSNS
3178 Specification, <a href="./rfc4171">RFC 4171</a>."
3179 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
3180 ::= { isnsRegFcNodeEntry 5 }
3181
3182 isnsRegFcNodeProxyIscsiName OBJECT-TYPE
3183 SYNTAX SnmpAdminString (SIZE (0..223))
3184 MAX-ACCESS read-only
3185
3186
3187
3188 <span class="grey">Gibbons, et al. Standards Track [Page 57]</span></pre>
3189 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-58" ></span>
3190 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
3191
3192
3193 STATUS current
3194 DESCRIPTION
3195 "The iSCSI Name used to represent the FC Node in the IP
3196 network. It is used as a pointer to the matching iSCSI Name
3197 entry in the iSNS Server. Its value is usually registered
3198 by an FC-iSCSI gateway connecting the IP network to the
3199 fabric containing the FC device."
3200 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
3201 ::= { isnsRegFcNodeEntry 6 }
3202
3203 isnsRegFcNodeNumFcPorts OBJECT-TYPE
3204 SYNTAX Gauge32 ( 0 .. 4294967295 )
3205 MAX-ACCESS read-only
3206 STATUS current
3207 DESCRIPTION
3208 "The number of FC Ports associated with this FC Node."
3209 ::= { isnsRegFcNodeEntry 7 }
3210
3211 --
3212 -- iSNS Registered FC Port Table
3213 --
3214
3215 isnsRegFcPortTable OBJECT-TYPE
3216 SYNTAX SEQUENCE OF IsnsRegFcPortEntry
3217 MAX-ACCESS not-accessible
3218 STATUS current
3219 DESCRIPTION
3220 "Information on registered FC N_Ports in the iSNS. FC Ports
3221 are associated with registered FC Nodes. This supports
3222 iFCP as defined in <a href="./rfc4172">RFC 4172</a>."
3223 REFERENCE "<a href="./rfc4172#section-4">RFC 4172, Section&nbsp;4</a>"
3224 ::= { isnsRegFcNodeInfo 2 }
3225
3226 isnsRegFcPortEntry OBJECT-TYPE
3227 SYNTAX IsnsRegFcPortEntry
3228 MAX-ACCESS not-accessible
3229 STATUS current
3230 DESCRIPTION
3231 "Information on one FC Port that has been registered in
3232 iSNS."
3233 REFERENCE "<a href="./rfc4172#section-4">RFC 4172, Section&nbsp;4</a>"
3234 INDEX { isnsServerIndex,
3235 isnsRegEntityIndex,
3236 isnsRegFcPortWwpn }
3237 ::= { isnsRegFcPortTable 1 }
3238
3239 IsnsRegFcPortEntry ::= SEQUENCE {
3240 isnsRegFcPortWwpn FcNameIdOrZero,
3241
3242
3243
3244 <span class="grey">Gibbons, et al. Standards Track [Page 58]</span></pre>
3245 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-59" ></span>
3246 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
3247
3248
3249 isnsRegFcPortID FcAddressIdOrZero,
3250 isnsRegFcPortType Unsigned32,
3251 isnsRegFcPortSymbolicName SnmpAdminString,
3252 isnsRegFcPortFabricPortWwn FcNameIdOrZero,
3253 isnsRegFcPortHA FcAddressIdOrZero,
3254 isnsRegFcPortAddressType InetAddressType,
3255 isnsRegFcPortAddress InetAddress,
3256 isnsRegFcPortFcCos IsnsFcClassOfServiceType,
3257 isnsRegFcPortFc4Types OCTET STRING,
3258 isnsRegFcPortFc4Descr SnmpAdminString,
3259 isnsRegFcPortFc4Features OCTET STRING,
3260 isnsRegFcPortScnTypes IsnsIfcpScnType,
3261 isnsRegFcPortRole IsnsFcPortRoleType,
3262 isnsRegFcPortFcNodeWwnn FcNameIdOrZero,
3263 isnsRegFcPortPpnWwn FcNameIdOrZero
3264 }
3265
3266 isnsRegFcPortWwpn OBJECT-TYPE
3267 SYNTAX FcNameIdOrZero (SIZE(8))
3268 MAX-ACCESS not-accessible
3269 STATUS current
3270 DESCRIPTION
3271 "The FC Port's World Wide Port Name as defined in the iSNS
3272 Specification, <a href="./rfc4171">RFC 4171</a>. A zero-length string is not valid
3273 for this managed object."
3274 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
3275 ::= { isnsRegFcPortEntry 1 }
3276
3277 isnsRegFcPortID OBJECT-TYPE
3278 SYNTAX FcAddressIdOrZero
3279 MAX-ACCESS read-only
3280 STATUS current
3281 DESCRIPTION
3282 "The FC Port's Port ID as defined in the iSNS Specification,
3283 <a href="./rfc4171">RFC 4171</a>."
3284 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
3285 ::= { isnsRegFcPortEntry 2 }
3286
3287 isnsRegFcPortType OBJECT-TYPE
3288 SYNTAX Unsigned32 ( 0 .. 65535 )
3289 MAX-ACCESS read-only
3290 STATUS current
3291 DESCRIPTION
3292 "The FC Port Type as defined in the iSNS Specification,
3293 <a href="./rfc4171">RFC 4171</a>, and the Fibre Channel Generic Services
3294 Specification. Current values are as shown below:
3295 unknown (0),
3296 nPort (1),
3297
3298
3299
3300 <span class="grey">Gibbons, et al. Standards Track [Page 59]</span></pre>
3301 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-60" ></span>
3302 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
3303
3304
3305 nlPort (2),
3306 fNlPort (3),
3307 fPort (129), -- x'81'
3308 flPort (130), -- x'82'
3309 ePort (132), -- x'84'
3310 bPort (133), -- x'85'
3311 mFcpPort (65297), -- x'FF11'
3312 iFcpPort (65298), -- x'FF12'
3313 unknownEnd (65535)
3314 The future assignment of any additional values will be
3315 documented in a revision of <a href="./rfc4171">RFC 4171</a>."
3316 REFERENCE "<a href="./rfc4171#section-6.6.3">RFC 4171, Section&nbsp;6.6.3</a>"
3317 ::= { isnsRegFcPortEntry 3 }
3318
3319 isnsRegFcPortSymbolicName OBJECT-TYPE
3320 SYNTAX SnmpAdminString
3321 MAX-ACCESS read-only
3322 STATUS current
3323 DESCRIPTION
3324 "The FC Port Symbolic Name as defined in the iSNS
3325 Specification, <a href="./rfc4171">RFC 4171</a>. If not provided, then the
3326 string SHALL be zero-length."
3327 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
3328 ::= { isnsRegFcPortEntry 4 }
3329
3330 isnsRegFcPortFabricPortWwn OBJECT-TYPE
3331 SYNTAX FcNameIdOrZero
3332 MAX-ACCESS read-only
3333 STATUS current
3334 DESCRIPTION
3335 "The Fabric Port WWN for this entry as defined in the iSNS
3336 Specification, <a href="./rfc4171">RFC 4171</a>. A zero-length string for this
3337 managed object indicates that the Fabric Port WWN is not
3338 known, or has not yet been registered with the iSNS Server."
3339 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
3340 ::= { isnsRegFcPortEntry 5 }
3341
3342 isnsRegFcPortHA OBJECT-TYPE
3343 SYNTAX FcAddressIdOrZero
3344 MAX-ACCESS read-only
3345 STATUS current
3346 DESCRIPTION
3347 "The FC Port Hard Address as defined in the iSNS
3348 Specification, <a href="./rfc4171">RFC 4171</a>."
3349 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
3350 ::= { isnsRegFcPortEntry 6 }
3351
3352 isnsRegFcPortAddressType OBJECT-TYPE
3353
3354
3355
3356 <span class="grey">Gibbons, et al. Standards Track [Page 60]</span></pre>
3357 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-61" ></span>
3358 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
3359
3360
3361 SYNTAX InetAddressType
3362 MAX-ACCESS read-only
3363 STATUS current
3364 DESCRIPTION
3365 "The type of Inet address in isnsRegFcPortAddress. If
3366 the address is specified, then it must be a valid unicast
3367 address and the value of this object must be ipv4(1),
3368 ipv6(2), ipv4z(3), or ipv6z(4); otherwise, the value
3369 of this object is unknown(0), and the value of
3370 isnsRegFcPortAddress is the zero-length string."
3371 ::= { isnsRegFcPortEntry 7 }
3372
3373 isnsRegFcPortAddress OBJECT-TYPE
3374 SYNTAX InetAddress
3375 MAX-ACCESS read-only
3376 STATUS current
3377 DESCRIPTION
3378 "The FC Port Inet Address as defined in the iSNS
3379 Specification, <a href="./rfc4171">RFC 4171</a>. The format of this object is
3380 specified by isnsRegFcPortAddressType."
3381 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
3382 ::= { isnsRegFcPortEntry 8 }
3383
3384 isnsRegFcPortFcCos OBJECT-TYPE
3385 SYNTAX IsnsFcClassOfServiceType
3386 MAX-ACCESS read-only
3387 STATUS current
3388 DESCRIPTION
3389 "The FC Port Class of Service as defined in the iSNS
3390 Specification, <a href="./rfc4171">RFC 4171</a>."
3391 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
3392 ::= { isnsRegFcPortEntry 9 }
3393
3394 isnsRegFcPortFc4Types OBJECT-TYPE
3395 SYNTAX OCTET STRING (SIZE (32))
3396 MAX-ACCESS read-only
3397 STATUS current
3398 DESCRIPTION
3399 "The FC Port FC-4 Types as defined in the iSNS
3400 Specification, <a href="./rfc4171">RFC 4171</a>."
3401 REFERENCE "<a href="./rfc4171#section-6.6.9">RFC 4171, Section&nbsp;6.6.9</a>"
3402 ::= { isnsRegFcPortEntry 10 }
3403
3404 isnsRegFcPortFc4Descr OBJECT-TYPE
3405 SYNTAX SnmpAdminString (SIZE(4..255))
3406 MAX-ACCESS read-only
3407 STATUS current
3408 DESCRIPTION
3409
3410
3411
3412 <span class="grey">Gibbons, et al. Standards Track [Page 61]</span></pre>
3413 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-62" ></span>
3414 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
3415
3416
3417 "The FC Port FC-4 Descriptor as defined in the iSNS
3418 Specification, <a href="./rfc4171">RFC 4171</a>. The FC-4 Descriptor cannot be
3419 longer than 255 bytes. The iSNS Server internal maximum
3420 size is 256 bytes to provide NULL termination."
3421 REFERENCE "<a href="./rfc4171#section-6.6.10">RFC 4171, Section&nbsp;6.6.10</a>"
3422 ::= { isnsRegFcPortEntry 11 }
3423
3424 isnsRegFcPortFc4Features OBJECT-TYPE
3425 SYNTAX OCTET STRING (SIZE (128))
3426 MAX-ACCESS read-only
3427 STATUS current
3428 DESCRIPTION
3429 "The FC Port FC-4 Features as defined in the iSNS
3430 Specification, <a href="./rfc4171">RFC 4171</a>."
3431 REFERENCE "<a href="./rfc4171#section-6.6.11">RFC 4171, Section&nbsp;6.6.11</a>"
3432 ::= { isnsRegFcPortEntry 12 }
3433
3434 isnsRegFcPortScnTypes OBJECT-TYPE
3435 SYNTAX IsnsIfcpScnType
3436 MAX-ACCESS read-only
3437 STATUS current
3438 DESCRIPTION
3439 "The iFCP State Change Notification (SCN) types enabled for
3440 the registered object."
3441 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
3442 ::= { isnsRegFcPortEntry 13 }
3443
3444 isnsRegFcPortRole OBJECT-TYPE
3445 SYNTAX IsnsFcPortRoleType
3446 MAX-ACCESS read-only
3447 STATUS current
3448 DESCRIPTION
3449 "The FC Port Role defines the role of the registered
3450 object."
3451 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
3452 ::= { isnsRegFcPortEntry 14 }
3453
3454 isnsRegFcPortFcNodeWwnn OBJECT-TYPE
3455 SYNTAX FcNameIdOrZero
3456 MAX-ACCESS read-only
3457 STATUS current
3458 DESCRIPTION
3459 "The FC Node World Wide Node Name that is associated with
3460 this FC Port as defined in the iSNS Specification, <a href="./rfc4171">RFC 4171</a>.
3461 This managed object may contain a zero-length string prior
3462 to a device registering this value with the iSNS Server."
3463 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
3464 ::= { isnsRegFcPortEntry 15 }
3465
3466
3467
3468 <span class="grey">Gibbons, et al. Standards Track [Page 62]</span></pre>
3469 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-63" ></span>
3470 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
3471
3472
3473
3474 isnsRegFcPortPpnWwn OBJECT-TYPE
3475 SYNTAX FcNameIdOrZero
3476 MAX-ACCESS read-only
3477 STATUS current
3478 DESCRIPTION
3479 "The Permanent Port Name (PPN) attribute is the FC Port Name WWPN
3480 of the first Storage Node registered in the iSNS Database
3481 that is associated with a particular FC Device (FC Node).
3482 The PPN of all subsequent Storage Node registrations that
3483 are associated with that FC Device (FC Node) SHALL be set
3484 to the FC Port Name WWPN of the first Storage Node, as
3485 defined in the iSNS Specification, <a href="./rfc4171">RFC 4171</a>. This managed
3486 object may contain a zero-length string prior to a device
3487 registering this value with the iSNS Server."
3488 REFERENCE "<a href="./rfc4171#section-6">RFC 4171, Section&nbsp;6</a>"
3489 ::= { isnsRegFcPortEntry 16 }
3490
3491 --
3492 -- Mapping from FC Node to Entity - FC Port
3493 --
3494
3495 isnsRegFcNodePortTable OBJECT-TYPE
3496 SYNTAX SEQUENCE OF
3497 IsnsRegFcNodePortEntry
3498 MAX-ACCESS not-accessible
3499 STATUS current
3500 DESCRIPTION
3501 "A table containing the mapping of a registered FC Node and
3502 associated registered iFCP Port to the supporting registered
3503 Entity object in an iSNS Server instance."
3504 ::= { isnsRegFcNodeInfo 3 }
3505
3506 isnsRegFcNodePortEntry OBJECT-TYPE
3507 SYNTAX IsnsRegFcNodePortEntry
3508 MAX-ACCESS not-accessible
3509 STATUS current
3510 DESCRIPTION
3511 "Information on one mapping from an FC Node and iFCP Port to
3512 an Entity object registered in an iSNS."
3513 INDEX { isnsServerIndex,
3514 isnsRegFcNodeWwnn,
3515 isnsRegFcPortWwpn }
3516 ::= { isnsRegFcNodePortTable 1 }
3517
3518 IsnsRegFcNodePortEntry ::= SEQUENCE {
3519 isnsRegFcNodePortEntityIndex IsnsEntityIndexIdOrZero
3520 }
3521
3522
3523
3524 <span class="grey">Gibbons, et al. Standards Track [Page 63]</span></pre>
3525 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-64" ></span>
3526 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
3527
3528
3529
3530 isnsRegFcNodePortEntityIndex OBJECT-TYPE
3531 SYNTAX IsnsEntityIndexIdOrZero
3532 MAX-ACCESS read-only
3533 STATUS current
3534 DESCRIPTION
3535 "The Entity Index for the registered Entity object
3536 associated with the FC Port and FC Node. This managed
3537 object may contain the value of zero prior to a device
3538 registering this value with the iSNS Server."
3539 ::= { isnsRegFcNodePortEntry 1 }
3540
3541 --
3542 -- iSNS Notifications Information -----------------
3543 --
3544
3545 isnsNotificationsInfo OBJECT IDENTIFIER
3546 ::= { isnsObjects 2 }
3547
3548 isnsInstanceInfo OBJECT-TYPE
3549 SYNTAX SnmpAdminString
3550 MAX-ACCESS accessible-for-notify
3551 STATUS current
3552 DESCRIPTION
3553 "Textual information about the notification event and the
3554 iSNS Server generating the notification. An example is:
3555 iSNS Server Started."
3556 ::= { isnsNotificationsInfo 1 }
3557
3558 isnsAddressNotificationType OBJECT-TYPE
3559 SYNTAX InetAddressType
3560 MAX-ACCESS accessible-for-notify
3561 STATUS current
3562 DESCRIPTION
3563 "The type of Inet address in isnsAddressNotification. If
3564 the address is specified, then it must be a valid unicast
3565 address and the value of this object must be ipv4(1),
3566 ipv6(2), ipv4z(3), or ipv6z(4); otherwise, the value
3567 of this object is unknown(0), and the value of
3568 isnsAddressNotification is the zero-length string."
3569 ::= { isnsNotificationsInfo 2 }
3570
3571 isnsAddressNotification OBJECT-TYPE
3572 SYNTAX InetAddress
3573 MAX-ACCESS accessible-for-notify
3574 STATUS current
3575 DESCRIPTION
3576 "Identifies the IP address of the iSNS Server. The format of
3577
3578
3579
3580 <span class="grey">Gibbons, et al. Standards Track [Page 64]</span></pre>
3581 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-65" ></span>
3582 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
3583
3584
3585 this object is specified by isnsAddressNotificationType.
3586 The IP address will always be specified in the notification
3587 unless an error causes the IP address to not be known."
3588 ::= { isnsNotificationsInfo 3 }
3589
3590 isnsTcpPortNotification OBJECT-TYPE
3591 SYNTAX InetPortNumber
3592 MAX-ACCESS accessible-for-notify
3593 STATUS current
3594 DESCRIPTION
3595 "Indicates the TCP port the iSNS Server is using,
3596 or 0 if TCP-based registrations are not supported."
3597 ::= { isnsNotificationsInfo 4 }
3598
3599 isnsUdpPortNotification OBJECT-TYPE
3600 SYNTAX InetPortNumber
3601 MAX-ACCESS accessible-for-notify
3602 STATUS current
3603 DESCRIPTION
3604 "Indicates the UDP port the iSNS Server is using,
3605 or 0 if UDP-based registrations are not supported."
3606 ::= { isnsNotificationsInfo 5 }
3607
3608 --
3609 -- iSNS Notification Block -----------------
3610 --
3611
3612 isnsServerStart NOTIFICATION-TYPE
3613 OBJECTS {
3614 isnsInstanceInfo,
3615 isnsAddressNotificationType,
3616 isnsAddressNotification,
3617 isnsTcpPortNotification,
3618 isnsUdpPortNotification
3619 }
3620 STATUS current
3621 DESCRIPTION
3622 "This notification is sent when an iSNS Server begins
3623 operation. The notification provides the following:
3624 isnsInstanceInfo : iSNS Server textual information
3625 isnsAddressTypeNotification : iSNS Server address type
3626 isnsAddressNotification : iSNS Server address
3627 isnsTcpPortNotification : iSNS Server TCP Port
3628 isnsUdpPortNotification : iSNS Server UDP Port
3629 "
3630 ::= { isnsNotifications 1 }
3631
3632 isnsServerShutdown NOTIFICATION-TYPE
3633
3634
3635
3636 <span class="grey">Gibbons, et al. Standards Track [Page 65]</span></pre>
3637 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-66" ></span>
3638 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
3639
3640
3641 OBJECTS {
3642 isnsInstanceInfo,
3643 isnsAddressNotificationType,
3644 isnsAddressNotification,
3645 isnsTcpPortNotification,
3646 isnsUdpPortNotification
3647 }
3648 STATUS current
3649 DESCRIPTION
3650 "This notification is sent when an iSNS Server is
3651 shutdown. The notification provides the following:
3652 isnsInstanceInfo : iSNS Server textual information
3653 isnsAddressTypeNotification : iSNS Server address type
3654 isnsAddressNotification : iSNS Server address
3655 isnsTcpPortNotification : iSNS Server TCP Port
3656 isnsUdpPortNotification : iSNS Server UDP Port
3657 "
3658 ::= { isnsNotifications 2 }
3659
3660 ------------------------------------------------------------
3661 --
3662 -- Compliance Information
3663 --
3664
3665 isnsCompliances OBJECT IDENTIFIER ::= { isnsConformance 1 }
3666
3667 isnsIscsiServerCompliance MODULE-COMPLIANCE
3668 STATUS current
3669 DESCRIPTION
3670 "Initial compliance statement for an iSNS Server
3671 providing support to iSCSI clients."
3672 MODULE -- this module
3673 MANDATORY-GROUPS {
3674 isnsServerAttributesGroup,
3675 isnsServerIscsiControlNodeGroup,
3676 isnsServerIscsiDdsDdObjGroup,
3677 isnsServerRegIscsiObjGroup,
3678 isnsServerNumObjectsGroup,
3679 isnsNotificationsObjGroup,
3680 isnsServerNotificationGroup
3681 }
3682 OBJECT isnsServerDiscoveryMcGroupType
3683 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2),
3684 ipv4z(3), ipv6z(4) }
3685 DESCRIPTION
3686 "Only support for unknown, ipv4, ipv6, ipv4z, ipv6z
3687 is required."
3688
3689
3690
3691
3692 <span class="grey">Gibbons, et al. Standards Track [Page 66]</span></pre>
3693 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-67" ></span>
3694 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
3695
3696
3697 OBJECT isnsServerDiscoveryMcGroupAddress
3698 SYNTAX InetAddress (SIZE (0 | 4 | 8 | 16 | 20 ))
3699 DESCRIPTION
3700 "Only addresses for unknown, ipv4, ipv6, ipv4z, ipv6z
3701 and their related SIZE need to be supported."
3702
3703 OBJECT isnsDdPortalMemberAddressType
3704 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2),
3705 ipv4z(3), ipv6z(4) }
3706 DESCRIPTION
3707 "Only support for unknown, ipv4, ipv6, ipv4z, ipv6z
3708 is required."
3709
3710 OBJECT isnsDdPortalMemberAddress
3711 SYNTAX InetAddress (SIZE (0 | 4 | 8 | 16 | 20 ))
3712 DESCRIPTION
3713 "Only addresses for unknown, ipv4, ipv6, ipv4z, ipv6z
3714 and their related SIZE need to be supported."
3715
3716 OBJECT isnsRegEntityManagementAddressType
3717 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2),
3718 ipv4z(3), ipv6z(4) }
3719 DESCRIPTION
3720 "Only support for unknown, ipv4, ipv6, ipv4z, ipv6z
3721 is required."
3722
3723 OBJECT isnsRegEntityManagementAddress
3724 SYNTAX InetAddress (SIZE (0 | 4 | 8 | 16 | 20 ))
3725 DESCRIPTION
3726 "Only addresses for unknown, ipv4, ipv6, ipv4z, ipv6z
3727 and their related SIZE need to be supported."
3728
3729 OBJECT isnsRegPortalAddressType
3730 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2),
3731 ipv4z(3), ipv6z(4) }
3732 DESCRIPTION
3733 "Only support for unknown, ipv4, ipv6, ipv4z, ipv6z
3734 is required."
3735
3736 OBJECT isnsRegPortalAddress
3737 SYNTAX InetAddress (SIZE (0 | 4 | 8 | 16 | 20 ))
3738 DESCRIPTION
3739 "Only addresses for unknown, ipv4, ipv6, ipv4z, ipv6z
3740 and their related SIZE need to be supported."
3741
3742 OBJECT isnsRegPgPortalAddressType
3743 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2),
3744 ipv4z(3), ipv6z(4) }
3745
3746
3747
3748 <span class="grey">Gibbons, et al. Standards Track [Page 67]</span></pre>
3749 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-68" ></span>
3750 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
3751
3752
3753 DESCRIPTION
3754 "Only support for unknown, ipv4, ipv6, ipv4z, ipv6z
3755 is required."
3756
3757 OBJECT isnsRegPgPortalAddress
3758 SYNTAX InetAddress (SIZE (0 | 4 | 8 | 16 | 20 ))
3759 DESCRIPTION
3760 "Only addresses for unknown, ipv4, ipv6, ipv4z, ipv6z
3761 and their related SIZE need to be supported."
3762
3763 OBJECT isnsAddressNotificationType
3764 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2),
3765 ipv4z(3), ipv6z(4) }
3766 DESCRIPTION
3767 "Only support for unknown, ipv4, ipv6, ipv4z, ipv6z
3768 is required."
3769
3770 OBJECT isnsAddressNotification
3771 SYNTAX InetAddress (SIZE (0 | 4 | 8 | 16 | 20 ))
3772 DESCRIPTION
3773 "Only addresses for unknown, ipv4, ipv6, ipv4z, ipv6z
3774 and their related SIZE need to be supported."
3775 ::= { isnsCompliances 1 }
3776
3777 isnsIfcpServerCompliance MODULE-COMPLIANCE
3778 STATUS current
3779 DESCRIPTION
3780 "Initial compliance statement for an iSNS Server
3781 providing support to iFCP Clients."
3782 MODULE -- this module
3783 MANDATORY-GROUPS {
3784 isnsServerAttributesGroup,
3785 isnsServerIfcpPortControlNodeGroup,
3786 isnsServerIfcpDdsDdObjGroup,
3787 isnsServerRegIfcpObjGroup,
3788 isnsServerNumObjectsGroup,
3789 isnsNotificationsObjGroup,
3790 isnsServerNotificationGroup
3791 }
3792 OBJECT isnsServerDiscoveryMcGroupType
3793 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2),
3794 ipv4z(3), ipv6z(4) }
3795 DESCRIPTION
3796 "Only support for unknown, ipv4, ipv6, ipv4z, and ipv6z
3797 is required."
3798
3799 OBJECT isnsServerDiscoveryMcGroupAddress
3800 SYNTAX InetAddress (SIZE (0 | 4 | 8 | 16 | 20 ))
3801
3802
3803
3804 <span class="grey">Gibbons, et al. Standards Track [Page 68]</span></pre>
3805 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-69" ></span>
3806 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
3807
3808
3809 DESCRIPTION
3810 "Only addresses for unknown, ipv4, ipv6, ipv4z, ipv6z,
3811 and their related SIZE need to be supported."
3812
3813 OBJECT isnsDdPortalMemberAddressType
3814 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2),
3815 ipv4z(3), ipv6z(4) }
3816 DESCRIPTION
3817 "Only support for unknown, ipv4, ipv6, ipv4z, and ipv6z
3818 is required."
3819
3820 OBJECT isnsDdPortalMemberAddress
3821 SYNTAX InetAddress (SIZE (0 | 4 | 8 | 16 | 20 ))
3822 DESCRIPTION
3823 "Only addresses for unknown, ipv4, ipv6, ipv4z, ipv6z,
3824 and their related SIZE need to be supported."
3825
3826 OBJECT isnsRegEntityManagementAddressType
3827 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2),
3828 ipv4z(3), ipv6z(4) }
3829 DESCRIPTION
3830 "Only support for unknown, ipv4, ipv6, ipv4z, and ipv6z
3831 is required."
3832
3833 OBJECT isnsRegEntityManagementAddress
3834 SYNTAX InetAddress (SIZE (0 | 4 | 8 | 16 | 20 ))
3835 DESCRIPTION
3836 "Only addresses for unknown, ipv4, ipv6, ipv4z, ipv6z,
3837 and their related SIZE need to be supported."
3838
3839 OBJECT isnsRegPortalAddressType
3840 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2),
3841 ipv4z(3), ipv6z(4) }
3842 DESCRIPTION
3843 "Only support for unknown, ipv4, ipv6, ipv4z, and ipv6z
3844 is required."
3845
3846 OBJECT isnsRegPortalAddress
3847 SYNTAX InetAddress (SIZE (0 | 4 | 8 | 16 | 20 ))
3848 DESCRIPTION
3849 "Only addresses for unknown, ipv4, ipv6, ipv4z, ipv6z,
3850 and their related SIZE need to be supported."
3851
3852 OBJECT isnsRegFcNodeAddressType
3853 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2),
3854 ipv4z(3), ipv6z(4) }
3855 DESCRIPTION
3856 "Only support for unknown, ipv4, ipv6, ipv4z, and ipv6z
3857
3858
3859
3860 <span class="grey">Gibbons, et al. Standards Track [Page 69]</span></pre>
3861 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-70" ></span>
3862 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
3863
3864
3865 is required."
3866
3867 OBJECT isnsRegFcNodeAddress
3868 SYNTAX InetAddress (SIZE (0 | 4 | 8 | 16 | 20 ))
3869 DESCRIPTION
3870 "Only addresses for unknown, ipv4, ipv6, ipv4z, ipv6z,
3871 and their related SIZE need to be supported."
3872
3873 OBJECT isnsRegFcPortAddressType
3874 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2),
3875 ipv4z(3), ipv6z(4) }
3876 DESCRIPTION
3877 "Only support for unknown, ipv4, ipv6, ipv4z, and ipv6z
3878 is required."
3879
3880 OBJECT isnsRegFcPortAddress
3881 SYNTAX InetAddress (SIZE (0 | 4 | 8 | 16 | 20 ))
3882 DESCRIPTION
3883 "Only addresses for unknown, ipv4, ipv6, ipv4z, ipv6z,
3884 and their related SIZE need to be supported."
3885
3886 OBJECT isnsAddressNotificationType
3887 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2),
3888 ipv4z(3), ipv6z(4) }
3889 DESCRIPTION
3890 "Only support for unknown, ipv4, ipv6, ipv4z, and ipv6z
3891 is required."
3892
3893 OBJECT isnsAddressNotification
3894 SYNTAX InetAddress (SIZE (0 | 4 | 8 | 16 | 20 ))
3895 DESCRIPTION
3896 "Only addresses for unknown, ipv4, ipv6, ipv4z, ipv6z,
3897 and their related SIZE need to be supported."
3898 ::= { isnsCompliances 2 }
3899
3900 isnsGroups OBJECT IDENTIFIER ::= { isnsConformance 2 }
3901
3902 isnsServerAttributesGroup OBJECT-GROUP
3903 OBJECTS {
3904 isnsServerName,
3905 isnsServerIsnsVersion,
3906 isnsServerVendorInfo,
3907 isnsServerPhysicalIndex,
3908 isnsServerTcpPort,
3909 isnsServerUdpPort,
3910 isnsServerDiscontinuityTime,
3911 isnsServerRole,
3912 isnsServerDiscoveryMethodsEnabled,
3913
3914
3915
3916 <span class="grey">Gibbons, et al. Standards Track [Page 70]</span></pre>
3917 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-71" ></span>
3918 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
3919
3920
3921 isnsServerDiscoveryMcGroupType,
3922 isnsServerDiscoveryMcGroupAddress,
3923 isnsServerEsiNonResponseThreshold,
3924 isnsServerEnableControlNodeMgtScn,
3925 isnsServerDefaultDdDdsStatus,
3926 isnsServerUpdateDdDdsSupported,
3927 isnsServerUpdateDdDdsEnabled
3928 }
3929 STATUS current
3930 DESCRIPTION
3931 "iSNS Server attributes."
3932 ::= { isnsGroups 1 }
3933
3934 isnsServerNumObjectsGroup OBJECT-GROUP
3935 OBJECTS {
3936 isnsNumDds,
3937 isnsNumDd,
3938 isnsNumEntities,
3939 isnsNumPortals,
3940 isnsNumPortalGroups,
3941 isnsNumIscsiNodes,
3942 isnsNumFcPorts,
3943 isnsNumFcNodes,
3944 isnsRegEntityInfoNumPortals,
3945 isnsRegEntityInfoNumPortalGroups,
3946 isnsRegEntityInfoNumIscsiNodes,
3947 isnsRegEntityInfoNumFcPorts,
3948 isnsRegEntityInfoNumFcNodes
3949 }
3950 STATUS current
3951 DESCRIPTION
3952 "Managed objects indicating the number of registered objects
3953 in an iSNS Server or the number of registered objects
3954 associated with a registered Entity. These managed objects
3955 are optional to implement."
3956 ::= { isnsGroups 2 }
3957
3958 isnsServerIscsiControlNodeGroup OBJECT-GROUP
3959 OBJECTS {
3960 isnsControlNodeIscsiNodeName,
3961 isnsControlNodeIscsiIsRegistered,
3962 isnsControlNodeIscsiRcvMgtSCN
3963 }
3964 STATUS current
3965 DESCRIPTION
3966 "iSNS Server iSCSI control node managed objects."
3967 ::= { isnsGroups 3 }
3968
3969
3970
3971
3972 <span class="grey">Gibbons, et al. Standards Track [Page 71]</span></pre>
3973 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-72" ></span>
3974 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
3975
3976
3977 isnsServerIfcpPortControlNodeGroup OBJECT-GROUP
3978 OBJECTS {
3979 isnsControlNodeFcPortIsRegistered,
3980 isnsControlNodeFcPortRcvMgtSCN
3981 }
3982 STATUS current
3983 DESCRIPTION
3984 "iSNS Server iFCP Port control node managed objects."
3985 ::= { isnsGroups 4 }
3986
3987 isnsServerIscsiDdsDdObjGroup OBJECT-GROUP
3988 OBJECTS {
3989 isnsDdsSymbolicName,
3990 isnsDdsStatus,
3991 isnsDdsMemberSymbolicName,
3992 isnsDdSymbolicName,
3993 isnsDdFeatures,
3994 isnsDdIscsiMemberName,
3995 isnsDdIscsiMemberIsRegistered,
3996 isnsDdPortalMemberAddressType,
3997 isnsDdPortalMemberAddress,
3998 isnsDdPortalMemberPortType,
3999 isnsDdPortalMemberPort,
4000 isnsDdPortalMemberIsRegistered
4001 }
4002 STATUS current
4003 DESCRIPTION
4004 "iSNS Server DDS and DD managed objects for iSCSI."
4005 ::= { isnsGroups 5 }
4006
4007 isnsServerIfcpDdsDdObjGroup OBJECT-GROUP
4008 OBJECTS {
4009 isnsDdsSymbolicName,
4010 isnsDdsStatus,
4011 isnsDdSymbolicName,
4012 isnsDdFeatures,
4013 isnsDdPortalMemberAddressType,
4014 isnsDdPortalMemberAddress,
4015 isnsDdPortalMemberPortType,
4016 isnsDdPortalMemberPort,
4017 isnsDdPortalMemberIsRegistered,
4018 isnsDdFcPortMemberIsRegistered
4019 }
4020 STATUS current
4021 DESCRIPTION
4022 "iSNS Server DDS and DD managed objects for iFCP."
4023 ::= { isnsGroups 6 }
4024
4025
4026
4027
4028 <span class="grey">Gibbons, et al. Standards Track [Page 72]</span></pre>
4029 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-73" ></span>
4030 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
4031
4032
4033 isnsServerRegIscsiObjGroup OBJECT-GROUP
4034 OBJECTS {
4035 isnsRegEntityEID,
4036 isnsRegEntityProtocol,
4037 isnsRegEntityManagementAddressType,
4038 isnsRegEntityManagementAddress,
4039 isnsRegEntityTimestamp,
4040 isnsRegEntityVersionMin,
4041 isnsRegEntityVersionMax,
4042 isnsRegEntityRegistrationPeriod,
4043 isnsRegEntityInfoNumPortals,
4044 isnsRegEntityInfoNumPortalGroups,
4045 isnsRegEntityInfoNumIscsiNodes,
4046 isnsRegEntityInfoNumFcPorts,
4047 isnsRegEntityInfoNumFcNodes,
4048 isnsRegPortalAddressType,
4049 isnsRegPortalAddress,
4050 isnsRegPortalPortType,
4051 isnsRegPortalPort,
4052 isnsRegPortalSymbolicName,
4053 isnsRegPortalEsiInterval,
4054 isnsRegPortalEsiPortType,
4055 isnsRegPortalEsiPort,
4056 isnsRegPortalScnPortType,
4057 isnsRegPortalScnPort,
4058 isnsRegPortalSecurityInfo,
4059 isnsRegPgIscsiNodeIndex,
4060 isnsRegPgIscsiName,
4061 isnsRegPgPortalPortalIndex,
4062 isnsRegPgPortalAddressType,
4063 isnsRegPgPortalAddress,
4064 isnsRegPgPortalPortType,
4065 isnsRegPgPortalPort,
4066 isnsRegPgPGT,
4067 isnsRegIscsiNodeName,
4068 isnsRegIscsiNodeType,
4069 isnsRegIscsiNodeAlias,
4070 isnsRegIscsiNodeScnTypes,
4071 isnsRegIscsiNodeWwnToken,
4072 isnsRegIscsiNodeAuthMethod
4073 }
4074 STATUS current
4075 DESCRIPTION
4076 "iSNS Server registered iSCSI managed objects."
4077 ::= { isnsGroups 7 }
4078
4079 isnsServerRegIfcpObjGroup OBJECT-GROUP
4080 OBJECTS {
4081
4082
4083
4084 <span class="grey">Gibbons, et al. Standards Track [Page 73]</span></pre>
4085 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-74" ></span>
4086 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
4087
4088
4089 isnsRegEntityEID,
4090 isnsRegEntityProtocol,
4091 isnsRegEntityManagementAddressType,
4092 isnsRegEntityManagementAddress,
4093 isnsRegEntityTimestamp,
4094 isnsRegEntityVersionMin,
4095 isnsRegEntityVersionMax,
4096 isnsRegEntityRegistrationPeriod,
4097 isnsRegEntityInfoNumPortals,
4098 isnsRegEntityInfoNumPortalGroups,
4099 isnsRegEntityInfoNumIscsiNodes,
4100 isnsRegEntityInfoNumFcPorts,
4101 isnsRegEntityInfoNumFcNodes,
4102 isnsRegPortalAddressType,
4103 isnsRegPortalAddress,
4104 isnsRegPortalPortType,
4105 isnsRegPortalPort,
4106 isnsRegPortalSymbolicName,
4107 isnsRegPortalEsiInterval,
4108 isnsRegPortalEsiPortType,
4109 isnsRegPortalEsiPort,
4110 isnsRegPortalScnPortType,
4111 isnsRegPortalScnPort,
4112 isnsRegPortalSecurityInfo,
4113 isnsRegFcPortID,
4114 isnsRegFcPortType,
4115 isnsRegFcPortSymbolicName,
4116 isnsRegFcPortFabricPortWwn,
4117 isnsRegFcPortHA,
4118 isnsRegFcPortAddressType,
4119 isnsRegFcPortAddress,
4120 isnsRegFcPortFcCos,
4121 isnsRegFcPortFc4Types,
4122 isnsRegFcPortFc4Descr,
4123 isnsRegFcPortFc4Features,
4124 isnsRegFcPortScnTypes,
4125 isnsRegFcPortRole,
4126 isnsRegFcPortFcNodeWwnn,
4127 isnsRegFcPortPpnWwn,
4128 isnsRegFcNodeSymbolicName,
4129 isnsRegFcNodeAddressType,
4130 isnsRegFcNodeAddress,
4131 isnsRegFcNodeIPA,
4132 isnsRegFcNodeProxyIscsiName,
4133 isnsRegFcNodeNumFcPorts,
4134 isnsRegFcNodePortEntityIndex
4135 }
4136 STATUS current
4137
4138
4139
4140 <span class="grey">Gibbons, et al. Standards Track [Page 74]</span></pre>
4141 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-75" ></span>
4142 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
4143
4144
4145 DESCRIPTION
4146 "iSNS Server registered iFCP managed objects."
4147 ::= { isnsGroups 8 }
4148
4149 isnsNotificationsObjGroup OBJECT-GROUP
4150 OBJECTS {
4151 isnsInstanceInfo,
4152 isnsAddressNotificationType,
4153 isnsAddressNotification,
4154 isnsTcpPortNotification,
4155 isnsUdpPortNotification
4156 }
4157 STATUS current
4158 DESCRIPTION
4159 "iSNS Notification managed objects."
4160 ::= { isnsGroups 9 }
4161
4162 isnsServerNotificationGroup NOTIFICATION-GROUP
4163 NOTIFICATIONS {
4164 isnsServerStart,
4165 isnsServerShutdown
4166 }
4167 STATUS current
4168 DESCRIPTION
4169 "iSNS Server Notification managed objects."
4170 ::= { isnsGroups 10 }
4171 END
4172
4173 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span>
4174
4175 The MIB module in this document uses the following IANA-assigned
4176 OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
4177
4178 Descriptor OBJECT IDENTIFIER value
4179 ---------- -----------------------
4180
4181 isnsMIB { mib-2 163 }
4182
4183 This RFC utilizes the IANA registry of iSNS parameters. This
4184 registry was created for the iSNS Specification [<a href="./rfc4171" title="&quot;Internet Storage Name Service (iSNS)&quot;">RFC4171</a>], and is
4185 located at <a href="http://www.iana.org/assignments/isns-parameters">http://www.iana.org/assignments/isns-parameters</a>.
4186 Specifically, the isnsRegEntityProtocol values used in the MIB module
4187 are the values for the Block Storage Protocols that IANA assigns and
4188 documents in <a href="http://www.iana.org/assignments/isns-parameters">http://www.iana.org/assignments/isns-parameters</a>.
4189
4190
4191
4192
4193
4194
4195
4196 <span class="grey">Gibbons, et al. Standards Track [Page 75]</span></pre>
4197 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-76" ></span>
4198 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
4199
4200
4201 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span>
4202
4203 There are no management objects defined in this MIB module that have
4204 a MAX-ACCESS clause of read-write and/or read-create. So, if this
4205 MIB module is implemented correctly, then there is no risk that an
4206 intruder can alter or create any management objects of this MIB
4207 module via direct SNMP SET operations.
4208
4209 Some of the readable objects in this MIB module (i.e., objects with a
4210 MAX-ACCESS other than not-accessible) may be considered sensitive or
4211 vulnerable in some network environments. It is thus important to
4212 control even GET and/or NOTIFY access to these objects and possibly
4213 to even encrypt the values of these objects when sending them over
4214 the network via SNMP. These are the tables and objects and their
4215 sensitivity/vulnerability:
4216
4217 The isnsDdsMemberTable contains information about which Discovery
4218 Domains may be enabled at the same time.
4219
4220 The isnsDdTable contains information about Discovery Domains,
4221 containing storage nodes with an ability to communicate and exchange
4222 storage data.
4223
4224 The isnsDdIscsiMemberTable indicates which iSCSI nodes are contained
4225 in which Discovery Domains.
4226
4227 The isnsDdPortalMemberTable indicates which iSCSI portals are
4228 contained in which Discovery Domains.
4229
4230 The isnsDdFcPortMemberTable indicates which iFCP FC N_Ports are
4231 contained in which Discovery Domains.
4232
4233 The isnsControlNodeIscsiTable indicates which iSCSI nodes have the
4234 ability to possibly control an iSNS server.
4235
4236 The isnsControlNodeFcPortTable indicates which iFCP FC N_Ports have
4237 the ability to possibly control an iSNS server.
4238
4239 The above object tables provide information about storage objects
4240 sessions, and can indicate to a user who is communicating and
4241 exchanging storage data.
4242
4243 SNMP versions prior to SNMPv3 did not include adequate security.
4244 Even if the network itself is secure (for example by using IPsec),
4245 even then, there is no control as to who on the secure network is
4246 allowed to access and GET/SET (read/change/create/delete) the objects
4247 in this MIB module.
4248
4249
4250
4251
4252 <span class="grey">Gibbons, et al. Standards Track [Page 76]</span></pre>
4253 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-77" ></span>
4254 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
4255
4256
4257 It is RECOMMENDED that implementers consider the security features as
4258 provided by the SNMPv3 framework (see <a href="./rfc3410#section-8">[RFC3410], section&nbsp;8</a>),
4259 including full support for the SNMPv3 cryptographic mechanisms (for
4260 authentication and privacy).
4261
4262 Further, deployment of SNMP versions prior to SNMPv3 is NOT
4263 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
4264 enable cryptographic security. It is then a customer/operator
4265 responsibility to ensure that the SNMP entity giving access to an
4266 instance of this MIB module is properly configured to give access to
4267 the objects only to those principals (users) that have legitimate
4268 rights to indeed GET or SET (change/create/delete) them.
4269
4270 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Normative References</span>
4271
4272 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
4273 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
4274
4275 [<a id="ref-RFC2578">RFC2578</a>] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case J.,
4276 Rose, M., and S. Waldbusser, "Structure of Management
4277 Information Version 2 (SMIv2)", STD 58, <a href="./rfc2578">RFC 2578</a>, April
4278 1999.
4279
4280 [<a id="ref-RFC2579">RFC2579</a>] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
4281 Rose, M., and S. Waldbusser, "Textual Conventions for
4282 SMIv2", STD 58, <a href="./rfc2579">RFC 2579</a>, April 1999.
4283
4284 [<a id="ref-RFC2580">RFC2580</a>] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
4285 Rose, M., and S. Waldbusser, "Conformance Statements for
4286 SMIv2", STD 58, <a href="./rfc2580">RFC 2580</a>, April 1999.
4287
4288 [<a id="ref-RFC3411">RFC3411</a>] Harrington, D., Presuhn, R., and B. Wijnen, "An
4289 Architecture for Describing Simple Network Management
4290 Protocol (SNMP) Management Frameworks", STD 62, <a href="./rfc3411">RFC 3411</a>,
4291 December 2002.
4292
4293 [<a id="ref-RFC3720">RFC3720</a>] Satran, J., Meth, K., Sapuntzakis, C., Chadalapaka, M.,
4294 and E. Zeidner, "Internet Small Computer Systems Interface
4295 (iSCSI)", <a href="./rfc3720">RFC 3720</a>, March 2004.
4296
4297 [<a id="ref-RFC4001">RFC4001</a>] Daniele, M., Haberman, B., Routhier, S., and J.
4298 Schoenwaelder, "Textual Conventions for Internet Network
4299 Addresses", <a href="./rfc4001">RFC 4001</a>, February 2005.
4300
4301 [<a id="ref-RFC4044">RFC4044</a>] McCloghrie, K., "Fibre Channel Management MIB", <a href="./rfc4044">RFC 4044</a>,
4302 May 2005.
4303
4304
4305
4306
4307
4308 <span class="grey">Gibbons, et al. Standards Track [Page 77]</span></pre>
4309 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-78" ></span>
4310 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
4311
4312
4313 [<a id="ref-RFC4133">RFC4133</a>] McCloghrie, K. and A. Bierman, "Entity MIB (Version 3)",
4314 <a href="./rfc4133">RFC 4133</a>, August 2005.
4315
4316 [<a id="ref-RFC4171">RFC4171</a>] Tseng, J., Gibbons, K., Travostino, F., Du Laney, C., and
4317 J. Souza, "Internet Storage Name Service (iSNS)", <a href="./rfc4171">RFC</a>
4318 <a href="./rfc4171">4171</a>, September 2005.
4319
4320 [<a id="ref-RFC4172">RFC4172</a>] Monia, C., Mullendore, R., Travostino, F., Jeong, W., and
4321 M. Edwards, "iFCP - A Protocol for Internet Fibre Channel
4322 Storage Networking", <a href="./rfc4172">RFC 4172</a>, September 2005.
4323
4324 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Informative References</span>
4325
4326 [<a id="ref-RFC3410">RFC3410</a>] Case, J., Mundy, R., Partain, D., and B. Stewart,
4327 "Introduction and Applicability Statements for Internet-
4328 Standard Management Framework", <a href="./rfc3410">RFC 3410</a>, December 2002.
4329
4330 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Acknowledgements</span>
4331
4332 This memo is a product of the IP Storage (IPS) working group within
4333 the Internet Engineering Task Force.
4334
4335 We wish to acknowledge the contributions and comments from the IPS
4336 WG, including the following:
4337
4338 IPS WG Chair: David Black
4339 Former Editors: Josh Tseng and Tom McSweeney
4340 MIB Editors: Keith McCloghrie and Bert Wijnen
4341
4342
4343
4344
4345
4346
4347
4348
4349
4350
4351
4352
4353
4354
4355
4356
4357
4358
4359
4360
4361
4362
4363
4364 <span class="grey">Gibbons, et al. Standards Track [Page 78]</span></pre>
4365 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-79" ></span>
4366 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
4367
4368
4369 Authors' Addresses
4370
4371 Kevin Gibbons
4372 2Wire, Inc.
4373 1704 Automation Parkway
4374 San Jose, CA 95131
4375 USA
4376 Tel: +1 408-895-1387
4377 Fax: +1 408-428-9590
4378 EMail: [email protected]
4379
4380 G.D. Ramkumar
4381 SnapTell, Inc.
4382 2741 Middlefield Rd, Suite 200
4383 Palo Alto, CA 94306
4384 USA
4385 Tel: +1 650-326-7627
4386 Fax: +1 650-326-7620
4387 EMail: [email protected]
4388
4389 Scott Kipp
4390 Brocade
4391 4 McDATA Pkwy
4392 Broomfield, CO 80021
4393 USA
4394 Tel: +1 720-558-3452
4395 Fax: +1 720-558-8999
4396 EMail: [email protected]
4397
4398
4399
4400
4401
4402
4403
4404
4405
4406
4407
4408
4409
4410
4411
4412
4413
4414
4415
4416
4417
4418
4419
4420 <span class="grey">Gibbons, et al. Standards Track [Page 79]</span></pre>
4421 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-80" ></span>
4422 <span class="grey"><a href="./rfc4939">RFC 4939</a> iSNS MIB July 2007</span>
4423
4424
4425 Full Copyright Statement
4426
4427 Copyright (C) The IETF Trust (2007).
4428
4429 This document is subject to the rights, licenses and restrictions
4430 contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
4431 retain all their rights.
4432
4433 This document and the information contained herein are provided on an
4434 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
4435 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
4436 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
4437 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
4438 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
4439 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
4440
4441 Intellectual Property
4442
4443 The IETF takes no position regarding the validity or scope of any
4444 Intellectual Property Rights or other rights that might be claimed to
4445 pertain to the implementation or use of the technology described in
4446 this document or the extent to which any license under such rights
4447 might or might not be available; nor does it represent that it has
4448 made any independent effort to identify any such rights. Information
4449 on the procedures with respect to rights in RFC documents can be
4450 found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
4451
4452 Copies of IPR disclosures made to the IETF Secretariat and any
4453 assurances of licenses to be made available, or the result of an
4454 attempt made to obtain a general license or permission for the use of
4455 such proprietary rights by implementers or users of this
4456 specification can be obtained from the IETF on-line IPR repository at
4457 <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
4458
4459 The IETF invites any interested party to bring to its attention any
4460 copyrights, patents or patent applications, or other proprietary
4461 rights that may cover technology that may be required to implement
4462 this standard. Please address the information to the IETF at
4463 [email protected].
4464
4465 Acknowledgement
4466
4467 Funding for the RFC Editor function is currently provided by the
4468 Internet Society.
4469
4470
4471
4472
4473
4474
4475
4476 Gibbons, et al. Standards Track [Page 80]
4477 </pre>