idnits 2.17.1 draft-ietf-ips-scsi-mib-09.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 22. -- Found old boilerplate from RFC 3978, Section 5.5 on line 4147. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 4124. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 4131. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 4137. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 3 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 3640 has weird spacing: '...sEnable tru...' == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (January 30, 2006) is 6653 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'X3T10' is defined on line 4004, but no explicit reference was found in the text == Unused Reference: 'FCP2' is defined on line 4010, but no explicit reference was found in the text == Unused Reference: 'RFC4022' is defined on line 4029, but no explicit reference was found in the text == Unused Reference: 'SCC2' is defined on line 4048, but no explicit reference was found in the text == Unused Reference: 'SPI4' is defined on line 4055, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'SAM2' -- Possible downref: Non-RFC (?) normative reference: ref. 'SPC2' -- Possible downref: Non-RFC (?) normative reference: ref. 'X3T10' -- Obsolete informational reference (is this intentional?): RFC 3720 (Obsoleted by RFC 7143) Summary: 3 errors (**), 0 flaws (~~), 10 warnings (==), 11 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Hallak-Stamler 3 Internet-Draft Sanrad Intelligent Storage 4 Expires: August 3, 2006 M. Bakke 5 Cisco Systems, Inc. 6 Y. Lederman 7 Siliquent Technologies 8 M. Krueger 9 Hewlett-Packard 10 K. McCloghrie 11 Cisco Systems, Inc. 12 January 30, 2006 14 Definition of Managed Objects for SCSI Entities 15 draft-ietf-ips-scsi-mib-09 17 Status of this Memo 19 By submitting this Internet-Draft, each author represents that any 20 applicable patent or other IPR claims of which he or she is aware 21 have been or will be disclosed, and any of which he or she becomes 22 aware will be disclosed, in accordance with Section 6 of BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF), its areas, and its working groups. Note that 26 other groups may also distribute working documents as Internet- 27 Drafts. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 The list of current Internet-Drafts can be accessed at 35 http://www.ietf.org/ietf/1id-abstracts.txt. 37 The list of Internet-Draft Shadow Directories can be accessed at 38 http://www.ietf.org/shadow.html. 40 This Internet-Draft will expire on August 3, 2006. 42 Copyright Notice 44 Copyright (C) The Internet Society (2006). 46 Abstract 48 This memo defines a portion of the Management Information Base (MIB), 49 for use with network management protocols in the Internet community. 50 In particular it describes managed objects for Small Computer System 51 Interface (SCSI) entities, independently of the interconnect 52 subsystem layer. 54 Table of Contents 56 1. The Internet-Standard Management Framework . . . . . . . . . . 4 57 2. Requirements notation . . . . . . . . . . . . . . . . . . . . 5 58 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 59 3.1. Introduction . . . . . . . . . . . . . . . . . . . . . . 6 60 3.2. SCSI Terminology . . . . . . . . . . . . . . . . . . . . 8 61 3.2.1. SCSI Application Layer . . . . . . . . . . . . . . . . 8 62 3.2.2. SCSI Device . . . . . . . . . . . . . . . . . . . . . 8 63 3.2.3. SCSI Port . . . . . . . . . . . . . . . . . . . . . . 8 64 3.2.4. SCSI Initiator Device . . . . . . . . . . . . . . . . 9 65 3.2.5. SCSI Initiator Port . . . . . . . . . . . . . . . . . 9 66 3.2.6. SCSI Target Device . . . . . . . . . . . . . . . . . . 9 67 3.2.7. SCSI Target Port . . . . . . . . . . . . . . . . . . . 9 68 3.2.8. Logical Units . . . . . . . . . . . . . . . . . . . . 9 69 3.2.9. Logical Unit Number . . . . . . . . . . . . . . . . . 9 70 3.2.10. Interconnect Subsystem . . . . . . . . . . . . . . . . 9 71 3.2.11. Device Server . . . . . . . . . . . . . . . . . . . . 10 72 3.2.12. Task Manager . . . . . . . . . . . . . . . . . . . . . 10 73 3.2.13. SCSI Instance . . . . . . . . . . . . . . . . . . . . 10 74 3.3. SCSI MIB Module Implementation . . . . . . . . . . . . . 10 75 3.4. Bridging and Virtualization . . . . . . . . . . . . . . . 12 76 3.5. SCSI Command MIB Module . . . . . . . . . . . . . . . . . 13 77 4. Structure of the MIB . . . . . . . . . . . . . . . . . . . . . 14 78 4.1. The SCSI Device Group . . . . . . . . . . . . . . . . . . 14 79 4.2. The Initiator Group . . . . . . . . . . . . . . . . . . . 14 80 4.3. The Target Group . . . . . . . . . . . . . . . . . . . . 14 81 4.4. The Discovery Group . . . . . . . . . . . . . . . . . . . 14 82 4.5. The LUN Map Group . . . . . . . . . . . . . . . . . . . . 14 83 4.6. The Target Statistic Group . . . . . . . . . . . . . . . 15 84 4.7. The Target High Speed Statistic Group . . . . . . . . . . 15 85 4.8. The LUN Map Statistics Group . . . . . . . . . . . . . . 15 86 4.9. The LUN Map Statistics High Speed Group . . . . . . . . . 15 87 4.10. The Initiator Statistics Group . . . . . . . . . . . . . 16 88 4.11. The Initiator High Speed Statistic Group . . . . . . . . 16 89 4.12. The Discovery Statistics Group . . . . . . . . . . . . . 16 90 4.13. The Discovery Statistics High Speed Group . . . . . . . . 16 91 4.14. The Device Statistics Group . . . . . . . . . . . . . . . 16 92 5. Relationships in this MIB . . . . . . . . . . . . . . . . . . 17 93 6. Relationship to Other MIBs . . . . . . . . . . . . . . . . . . 19 94 6.1. Host Resource MIB . . . . . . . . . . . . . . . . . . . . 19 95 6.2. iSCSI MIB Module . . . . . . . . . . . . . . . . . . . . 19 97 7. Miscellaneous Details . . . . . . . . . . . . . . . . . . . . 20 98 7.1. Names and Identifiers . . . . . . . . . . . . . . . . . . 20 99 7.2. Logical Unit Number . . . . . . . . . . . . . . . . . . . 20 100 7.3. Notifications . . . . . . . . . . . . . . . . . . . . . . 20 101 7.4. SCSI Domains . . . . . . . . . . . . . . . . . . . . . . 20 102 7.5. Counters: 32 bits and 64 bits . . . . . . . . . . . . . . 20 103 7.6. Local versus Remote Entities . . . . . . . . . . . . . . 21 104 8. Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . 22 105 9. Object Definitions . . . . . . . . . . . . . . . . . . . . . . 23 106 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 81 107 11. Object Population Example: SCSI Target and Initiator 108 devices on a pSCSI bus . . . . . . . . . . . . . . . . . . . . 82 109 11.1. scsiInstance Table: . . . . . . . . . . . . . . . . . . . 83 110 11.2. scsiDevice Table: . . . . . . . . . . . . . . . . . . . . 83 111 11.3. scsiPort Table: . . . . . . . . . . . . . . . . . . . . . 83 112 11.4. scsiTransport Table: . . . . . . . . . . . . . . . . . . 83 113 11.5. scsiIntrDev Table: . . . . . . . . . . . . . . . . . . . 84 114 11.6. scsiInitiatorPort Table: . . . . . . . . . . . . . . . . 84 115 11.7. scsiDscTgt Table: . . . . . . . . . . . . . . . . . . . . 84 116 11.8. scsiDscLUN: . . . . . . . . . . . . . . . . . . . . . . . 84 117 11.9. scsiDscLUNIdentifier: . . . . . . . . . . . . . . . . . . 85 118 11.10. scsiAttTgtPort Table: . . . . . . . . . . . . . . . . . . 85 119 11.11. scsiTgtDev Table: . . . . . . . . . . . . . . . . . . . . 85 120 11.12. scsiTgtPort Table: . . . . . . . . . . . . . . . . . . . 86 121 11.13. scsiLU Table: . . . . . . . . . . . . . . . . . . . . . . 86 122 11.14. scsiLuId Table: . . . . . . . . . . . . . . . . . . . . . 86 123 11.15. scsiLunMap Table: . . . . . . . . . . . . . . . . . . . . 87 124 11.16. scsiAuthorizedIntr Table: . . . . . . . . . . . . . . . . 87 125 11.17. scsiAttIntrPort Table: . . . . . . . . . . . . . . . . . 87 126 12. Security Considerations . . . . . . . . . . . . . . . . . . . 88 127 13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 91 128 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 92 129 14.1. Normative References . . . . . . . . . . . . . . . . . . 92 130 14.2. Informative References . . . . . . . . . . . . . . . . . 93 131 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 95 132 Intellectual Property and Copyright Statements . . . . . . . . . . 97 134 1. The Internet-Standard Management Framework 136 For a detailed overview of the documents that describe the current 137 Internet-Standard Management Framework, please refer to section 7 of 138 RFC 3410 [RFC3410]. 140 Managed objects are accessed via a virtual information store, termed 141 the Management Information Base or MIB. MIB objects are generally 142 accessed through the Simple Network Management Protocol (SNMP). 143 Objects in the MIB are defined using the mechanisms defined in the 144 Structure of Management Information (SMI). This memo specifies a MIB 145 module that is compliant to the SMIv2, which is described in STD 58, 146 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 147 [RFC2580]. 149 2. Requirements notation 151 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 152 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 153 document are to be interpreted as described in [RFC2119]. 155 3. Overview 157 This memo defines a portion of the Management Information Base (MIB) 158 for use with network management protocols in the Internet community. 159 In particular, it describes a set of managed objects to configure and 160 monitor Small Computer System Interface entities (SCSI entities), 161 i.e. SCSI Target Devices and SCSI Initiator Devices and SCSI Ports. 163 SCSI is a client-server protocol in which application clients within 164 a SCSI initiator device (client) issue service requests to logical 165 units contained in a SCSI target device(server). 167 This MIB module is based on documents defined by the ANSI T10 168 Technical Committee, specifically the SCSI Architecture Model - 2 169 [SAM2] and SCSI Primary Commands - 2 [SPC2]. 171 The [SAM2] standard is the primary source for the SCSI architecture 172 discussion in this document and the terminology used in this MIB 173 module. 175 3.1. Introduction 177 In the late 1970s a firm called Shugart Associates started to have 178 some considerable success with a peripheral interface definition in 179 what became the PC marketplace, and this interface was adopted and 180 extended by an open standards committee to form the Small Computer 181 Systems Interface (SCSI). SCSI defines an 8 bit wide multi-drop 182 "bus" structure which could interconnect a total of eight peripherals 183 and computer systems. 185 It's important to realize that all SCSI initially standardized was 186 the "physical connection" i.e. the connectors, cables and interface 187 signals. Thus even though a peripheral could be connected to 188 multiple systems, the information that flowed across the interface 189 was different in each case. This was addressed some five years later 190 by the definition of a Common Command Set, and with this definition 191 in place it was possible for the first time to develop a peripheral 192 with both a common interface and common operating firmware for 193 connection to multiple systems. 195 The physical interface of SCSI continued to be developed throughout 196 the 1980s with the addition of fast (up to 10 megabytes/s) and wide 197 (16 bits) variants, but the distance supported remained a maximum of 198 25 meters (from one end of the bus to another), and indeed some of 199 the faster variants supported much less than that distance. The 200 command set development continued, with special commands for tapes, 201 printers, and even processors being added to the original disk- 202 oriented set. So successful was SCSI in the 1980s that the majority 203 of the available Operating Systems incorporated support for the SCSI 204 command set as standard. 206 However at the end of the 1980s the distance, speed and number of 207 devices supported by SCSI were starting to become significant 208 impediments to systems design, and while the "information explosion" 209 had not yet started in earnest, it was already being anticipated. At 210 the same time, the serial interface technologies developed for Local 211 Area Networks such as Ethernet, and the fibre optics technologies 212 that were first deployed in telecommunications applications, were 213 starting to appear sufficiently rugged & low-cost for use in 214 peripheral interface applications. Thus a standards project was 215 begun in 1988 to develop a new serial, fibre-optic interface to carry 216 the SCSI command sets and other peripheral protocols. This interface 217 eventually became known as Fibre Channel (FC), and it is based on an 218 architecture centered around an abstractly defined "fabric", which 219 may be a switch or a loop connection. MIB modules for various FC 220 equipments are already in existence. 222 In order to support the new interfaces, it was necessary to 223 completely reorganize the SCSI standards and definitions. The 224 command sets were separated from the physical interface definitions, 225 and a SCSI Architectural Model (SAM) was created to define the 226 interaction between the various standards. It is a key to 227 understanding SAM to realize that it was first created approximately 228 10 years AFTER the first SCSI products were shipped!! 230 The most recent development in this saga occurred in 2000 when an 231 IETF Working Group was formed to address, amongst other things, a 232 definition for transporting the SCSI command sets directly over a 233 TCP/IP infrastructure. This effort is known as iSCSI [RFC3720], and 234 an iSCSI MIB module is already under development [I-D.ietf-ips-iscsi- 235 mib]. 237 Most of the projects are in T10, except Fibre Channel that is defined 238 by T11 and IEEE defines 1394. 240 The SCSI MIB module represents the SCSI protocol layer common to all 241 SCSI command sets and transports. It does not represent the command 242 sets and transports themselves. These should appear in other MIB 243 modules specific to the transport or command set. The following 244 drawing shows the relationships between the various actual and 245 possible SCSI- related MIB modules. 247 +---------------------------------+ 248 SCSI Command | Higher-level MIBs, specific to | 249 Sets | command sets, disk, tape, etc. | 250 +---------------------------------+ 251 SCSI | SCSI MIB | 252 +-------+---------+-------+-------+ 253 SCSI | iSCSI | FCP | SPI | Other | 254 Transport | MIB | MIB | MIB | MIBs | 255 Protocols | | | | | 256 +-------+---------+-------+-------+ 257 SCSI | TCP | Fibre | Other | 258 Interconnect | MIB | Channel | Interconnect | 259 | | MIBs | MIBs | 260 +-------+---------+---------------+ 262 An iSCSI MIB module [I-D.ietf-ips-iscsi-mib], and a Fibre Channel 263 interconnect MIB Module [RFC4044] are currently being developed. No 264 development is currently planned for standard command-set-specific or 265 device- specific MIBs. 267 The TCP-MIB [RFC4022]is already a proposed standard RFC 4022. 269 3.2. SCSI Terminology 271 The following sections explain some of the SCSI terminology, which is 272 used later in defining the MIB module. For the authoritative 273 definitions of these terms, see SAM-2 [SAM2]. 275 3.2.1. SCSI Application Layer 277 The protocols and procedures that implement or invoke SCSI commands 278 and task management functions by using services provided by a SCSI 279 transport protocol layer. 281 3.2.2. SCSI Device 283 A SCSI device is an entity that contains one or more SCSI ports that 284 are connected to a service delivery subsystem and supports a SCSI 285 application protocol. 287 3.2.3. SCSI Port 289 A SCSI port is a device-resident entity that connects the application 290 client, device server or task manager to the service delivery 291 subsystem through which requests and responses are routed. A SCSI 292 port is synonymous with port and either a SCSI initiator port or a 293 SCSI target port. 295 3.2.4. SCSI Initiator Device 297 A SCSI initiator device contains application clients and SCSI 298 initiator ports that originate device service and task management 299 requests to be processed by a SCSI target device. When used this 300 term refers to SCSI initiator devices or SCSI target/initiator 301 devices that are using the SCSI target/initiator port as a SCSI 302 initiator port. 304 3.2.5. SCSI Initiator Port 306 A SCSI initiator port acts as the connection between application 307 clients and the service delivery subsystem through which requests and 308 responses are routed. In all cases when this term is used it refers 309 to an initiator port or a SCSI target/initiator port operating as a 310 SCSI initiator port. 312 3.2.6. SCSI Target Device 314 A SCSI target device contains logical units and SCSI target ports 315 that receive device service and task management requests for 316 processing. When used this term refers to SCSI target devices or 317 SCSI target/initiator devices that are using the SCSI target/ 318 initiator port as a SCSI target port. 320 3.2.7. SCSI Target Port 322 A SCSI target port contains a task router and acts as the connection 323 between device servers and task managers and the service delivery 324 subsystem through which requests and responses are routed. When this 325 term is used it refers to a SCSI target port or a SCSI target/ 326 initiator port operating as a SCSI target port. 328 3.2.8. Logical Units 330 A logical unit is an entity residing in the SCSI target device that 331 implements a device model and processes SCSI commands sent by an 332 application client. 334 3.2.9. Logical Unit Number 336 A Logical Unit Number or LUN is a 64-bit identifier for a logical 337 unit. 339 3.2.10. Interconnect Subsystem 341 An interconnect subsystem is one or more interconnects that appear as 342 a single path for the transfer of information between SCSI devices. 344 3.2.11. Device Server 346 A device server is an object within the logical unit that processes 347 SCSI tasks according to the rules for task management. 349 3.2.12. Task Manager 351 A task manager is a server within the SCSI target device that 352 processes task management functions. 354 3.2.13. SCSI Instance 356 A "SCSI instance" is a distinct SCSI entity within a managed system. 357 While most implementations will have just one SCSI instance, the MIB 358 module allows for multiple (virtual) instances, such that a large 359 system can be "partitioned" into multiple, distinct virtual systems. 361 For example, in a host, it allows multiple vendors' implementations 362 of the MIB module to co-exist under a single SNMP agent through each 363 vendor's implementation being a different SCSI instance. It also 364 allows a single SNMP agent to represent multiple subsystems each of 365 which have their own SCSI instance. 367 3.3. SCSI MIB Module Implementation 369 The SCSI MIB module is a basic building block to use in the various 370 SCSI management scenarios. This module is intended to be implemented 371 in every SCSI entity in a managed system. A SCSI entity can be a 372 SCSI Initiator device, SCSI Target device or SCSI Initiator and 373 Target device. Since SCSI (storage) networking devices may contain 374 more than one SCSI entity, it is possible that more than one SCSI 375 instance will reside in a single device. 377 In small-scale environments a single network management station 378 (NMS)may have SNMP access to both SCSI initiator devices and SCSI 379 target devices. However if the SCSI target devices, or virtualized 380 target devices, are being provided as a service, it is more likely 381 that the provider of the service owns and manages the SCSI target 382 devices, and that the consumer of the service owns and manages the 383 SCSI initiator devices. In this case, the service provider NMS and 384 the consumer NMS may have only allowed SNMP access to the SCSI target 385 devices and the SCSI initiator devices respectively. 387 The figures in this chapter describe the location of the SCSI MIB 388 module implementations in the various SCSI management scenarios. The 389 locations of the SCSI SNMP agent implementing the SCSI MIB module, 390 are denoted with '*. 392 +----------+ +---------+ 393 |SCSI | SCSI Transport |SCSI | 394 |Initiator +---------------------------------------+Target | 395 |Device | |Device | 396 | * | | * | 397 +----------+ +---------+ 398 | | 399 | | 400 | | 401 | | 402 | | 403 | SNMP +----------+ SNMP | 404 +------------------|SCSI |-------------------+ 405 |Management| 406 | (NMS) | 407 +----------+ 408 Figure 1. Single SCSI Initiator device and Single SCSI Target device 410 Figure 1 describes a simple SCSI management scenario of a SCSI 411 Initiator device, a SCSI Target device and a Management station. In 412 this scenario there are two SNMP agents, each containing its SCSI 413 instance and its respective objects. As the SCSI Target and SCSI 414 Initiator device are interconnected, their Target and Initiator port 415 objects will be complementary. 417 +-----------+ 418 | +--------+-+ SCSI Transport +---------+ 419 | | SCSI |---------------------------------------+ SCSI | 420 |* | Initiator+---------------------------------------+ Target | 421 +--| Device | SCSI Transport | Device | 422 | | * | | * | 423 | +----------+ +---------+ 424 | | | 425 | | | 426 | | | 427 | | | 428 | | | 429 |SNMP | SNMP +----------+ SNMP | 430 +-------+------------------|SCSI |-------------------+ 431 |Management| 432 | (NMS) | 433 +----------+ 434 Figure 2. Multiple Hosts and a Single Target device 436 Figure 2 adds another SCSI Initiator device, to the SCSI network, 437 which connects to the same SCSI target device. The additional SCSI 438 Initiator device also has an SNMP agent implementing the SCSI MIB 439 module. In this case, the SCSI Target device's MIB module will show 440 that two SCSI Initiator devices are attached to it. 442 +-----------+ +----------+ 443 | +----------+ +---------------+ +-+-------+ | 444 | |SCSI |--------------| Virtualization| | SCSI | | 445 |* |Initiator +--------------| Device +-------+ Target | | 446 +--|Device | SCSI | | | Device | *| 447 | | * | | * | | * |--+ 448 | +----------+ Transport +------------+--+ +---------+ | 449 | | | | | 450 | | | | | 451 | | | | | 452 | | | | | 453 | | | | | 454 | | SNMP +-----------+ | SNMP | | 455 +-------+------------------+ SCSI + +-+------------+-------+ 456 | Management| 457 | (NMS) | 458 +-----------+ 459 Figure 3. Multiple Hosts, Virtualization device and multiple 460 SCSI Target devices 462 Figure 3 adds an in-band virtualization device which encapsulates, 463 and possibly modifies, the SCSI Target devices representation to the 464 SCSI Initiator devices. It is common practice for an in-band 465 virtualization device, to include both SCSI Target and Initiator 466 device functionality. Therefore, its SCSI MIB module implementation 467 includes both the SCSI Target and Initiator device objects. It 468 should be noted that the Virtualization device might implement 469 additional proprietary MIB modules, as the SCSI MIB module does not 470 distinguish between physical and virtual SCSI entities. 472 3.4. Bridging and Virtualization 474 Storage virtualization is a concept that abstracts storage resources 475 in such a way that, storage entities are provided as pool of logical 476 entities. 478 Usually the virtualization process is transparent to the storage 479 users (i.e. Hosts). Virtualization normally affects the SCSI 480 entities represented to SCSI Initiator devices. However, the SCSI 481 MIB module enables the representation of SCSI entities and their 482 respective status, including error and performance-monitoring 483 statistics. It should be possible to perform a limited number of 484 configuration modification and diagnostic actions. 486 The SCSI entities embodied in the bridging and virtualization devices 487 can be represented by the SCSI MIB module. However, Bridging and 488 Virtualization devices configuration is beyond the above-described 489 scope and therefore should be provided through other MIB modules. 491 3.5. SCSI Command MIB Module 493 The management of SCSI commands is beyond the scope of this MIB 494 module. Future SCSI Command MIB module can link to this MIB module, 495 through the use of OIDs or INDEX values of appropriate tables. 497 4. Structure of the MIB 499 This MIB module contains fourteen conformance groups: 501 4.1. The SCSI Device Group 503 The scsiDeviceGroup group contains the objects general to each SCSI 504 instance: instance, device and port objects. It contains also the 505 objects referring to the transport(s) used by those SCSI instances. 506 This group is mandatory for all SCSI managed system. 508 Alias objects are provided for SCSI instances and SCSI devices to 509 enable administrators to identify them. These objects contain human 510 readable administrative text strings, and hence use the 511 SnmpAdminString textual convention from [RFC3411]. 513 4.2. The Initiator Group 515 The scsiInitiatorDeviceGroup contains all the managed information 516 related to a local SCSI initiator device and port. In addition, it 517 contains the managed objects referring to the monitored attached SCSI 518 target devices. Any managed system acting, as a SCSI initiator or 519 target/initiator device and port must support this group. 521 4.3. The Target Group 523 The scsiTargetDeviceGroup contains all the managed objects related to 524 a local SCSI target device, a local SCSI target port, monitored 525 attached initiator ports, logical units and logical unit identifiers. 527 Managed systems acting, as a SCSI target or target/initiator device 528 and port must support this group. 530 4.4. The Discovery Group 532 The scsiDiscoveryGroup group is a collection of managed objects 533 referring to remote SCSI target devices, remote SCSI target ports, 534 remote logical units and remote logical unit identifiers discovered 535 by or configured to a managed system acting as a SCSI initiator 536 device. 538 Managed systems acting as SCSI initiator device and port and 539 supporting remote SCSI target devices or ports configuration or 540 discovery should implement this group. 542 4.5. The LUN Map Group 544 The scsiLunMapGroup group is a collection of managed objects allowing 545 mapping between SCSI target devices, logical units and logical unit 546 numbers in one side to remote authorized SCSI initiator devices or 547 ports in another side. 549 Managed systems supporting this mapping should implement the 550 scsiLunMapGroup. 552 4.6. The Target Statistic Group 554 The scsiTargetDevStatsGroup group is a collection of managed objects 555 representing various statistics referring to a SCSI target device or 556 port. Managed systems acting as a SCSI target device and port 557 supporting statistics should implement this group. 559 4.7. The Target High Speed Statistic Group 561 The scsiTargetDevHSStatsGroup group is a collection of managed 562 objects representing various statistics referring to a SCSI target 563 device or port. It provides support for systems, which can quickly 564 generate countable information because they run at high speed. 566 Managed systems acting, as a SCSI target device and port and running 567 at high speed supporting should implement this group. 569 4.8. The LUN Map Statistics Group 571 The scsiLunMapStatsGroup group is a collection of managed objects 572 representing various statistics referring to remote authorized SCSI 573 initiator devices or ports. 575 Managed systems acting as a SCSI target device and port and able to 576 gather statistics on remote SCSI initiator devices or ports should 577 implement this group. 579 4.9. The LUN Map Statistics High Speed Group 581 The scsiLunMapHSStatsGroup group is a collection of managed objects 582 representing various statistics referring to remote authorized SSCI 583 initiator devices or ports. It provides support for systems, which 584 can quickly generate countable information because they run at high 585 speed. 587 Managed systems acting as a SCSI target device and port and able to 588 gather statistics on remote SCSI initiator devices or ports and 589 running at high speed should implement this group. 591 4.10. The Initiator Statistics Group 593 The scsiInitiatorDevStatsGroup group is a collection of managed 594 objects representing various statistics referring to a SCSI initiator 595 device or port. 597 Managed systems acting as a SCSI initiator device and port supporting 598 statistics should implement this group. 600 4.11. The Initiator High Speed Statistic Group 602 The scsiInitiatorDevHSStatsGroup group is a collection of managed 603 objects representing various statistics referring to a SCSI initiator 604 device or port. It provides support for systems, which can quickly 605 generate countable information because they run at high speed. 607 Managed systems acting as a SCSI initiator device and port and 608 running at high speed supporting should implement this group. 610 4.12. The Discovery Statistics Group 612 The scsiDiscoveryStatsGroup group is a collection of managed objects 613 representing various statistics referring to remote discovered or 614 configured SCSI target devices or ports. 616 Managed systems acting as a SCSI initiator device and port and able 617 to gather statistics on remote SCSI target devices or ports should 618 implement this group. 620 4.13. The Discovery Statistics High Speed Group 622 The scsiDiscoveryHSStatsGroup group is a collection of managed 623 objects representing various statistics referring to remote 624 discovered or configured SCSI target devices or ports. It provides 625 support for systems, which can quickly generate countable information 626 because they run at high speed. 628 Managed systems acting as a SCSI initiator device and port and able 629 to gather statistics on remote SCSI target devices or ports and 630 running at high speed should implement this group. 632 4.14. The Device Statistics Group 634 The scsiDeviceStatGroup group is a collection of managed objects 635 representing various statistics referring to a SCSI device. 637 Managed systems able to gather device statistics should implement 638 this group. 640 5. Relationships in this MIB 642 This chapter outlines the functionality and the dependency between 643 the MIB tables providing the required management functionality for 644 SCSI initiator and target devices. For specific usage of these 645 tables, the reader should refer to the description of the tables and 646 their respective table entries and attributes. 648 Following is a list of required SCSI initiator related features, and 649 the respective tables facilitating this functionality: 651 o List all the SCSI initiator ports, which should be managed through 652 this MIB module. The table scsiIntrPortTable maintains all the 653 SCSI initiator ports for the SCSI initiator devices in the MIB 654 module. 656 o Provide a list of all SCSI target ports or SCSI target devices to 657 which a SCSI initiator port can attach. This should prevent a 658 SCSI initiator device or port from attaching to SCSI target 659 devices that should be either invisible or inaccessible to it. 660 The entries in this list can be either created manually or by 661 automatic discovery mechanisms (e.g. SLP, iSNS). 662 The ScsiDscTgtTable provides this information. The entries in 663 this table point to SCSI initiator port, and indicate that the 664 SCSI initiator port can only attach to SCSI target ports or SCSI 665 target devices provided in the respective entries of the 666 ScsiDscTgtTable. This MIB module permits, but does not require 667 this table to be written via SNMP. There are significant security 668 considerations in allowing writes to this table, see Section 12. 670 o The information, for the aforementioned SCSI target ports or SCSI 671 target devices, about the LUs and their respective LUN Ids should 672 be provided. The scsiDscLunTable and scsiDscLunIdTable maintain 673 this information. 675 o The scsiAttTgtPortTable provides the information information about 676 the SCSI target ports each SCSI initiator port is currently 677 communicating with. This table should be dynamically updated to 678 reflect those connections. 680 Following is a list of required SCSI target device related features, 681 and the respective tables facilitating this functionality: 683 o List all the SCSI target ports, which should be managed through 684 this MIB module. The table scsiTgtPortTable maintains all the 685 SCSI target ports for the SCSI target devices in the MIB module. 687 o Provide a list of valid SCSI initiator ports or SCSI initiator 688 devices authorized to attach to a SCSI target port. This list 689 should feature the concept of "access lists", which are common in 690 IP routers and switches. The ScsiAuthorizedIntr table provides 691 this information. 692 This MIB module permits, but does not require this table to be 693 written via SNMP. There are significant security considerations 694 in allowing writes to this table, see Section 12. 696 o It should be possible to specify the list of LUNs exposed to each 697 SCSI initiator port or device, when it attached to the SCSI target 698 device. SCSI target devices must provide a default list of LUNs. 699 This list of LUNs can be either a unique list for each SCSI 700 initiator device, or be the default list. For each entry in the 701 ScsiAuthorizedIntr table a pointer, named scsiAuthIntrLunMapIndex, 702 indexing the ScsiLunMapTable facilitates this feature. 704 o Provide means to monitor all the SCSI initiator ports currently 705 attached to this SCSI target port. The scsiAttIntrPortTable 706 provides this information. This table should be dynamically 707 updated to reflect those connections. 709 6. Relationship to Other MIBs 711 6.1. Host Resource MIB 713 The SCSI MIB module extends objects defined in the host resource MIB 714 module to SCSI specific entities but does not contain information on 715 software modules such as device drivers. If MIB objects are required 716 for installed packages of SCSI software, then the hrSWInstalledGroup 717 of the HOST-RESOURCES-MIB [RFC2790] are the standard MIB objects to 718 use. 720 6.2. iSCSI MIB Module 722 The SCSI MIB module defines managed objects for SCSI protocol layer. 723 The SCSI layer can run on the top of several transport layers; iSCSI 724 is one of them. The ISCSI-MIB [I-D.ietf-ips-iscsi-mib] is the MIB 725 portion defining the managed objects for the transport called iSCSI. 726 In the same way, a fibre channel or parallel SCSI MIB module would 727 define managed objects for a transport called respectively fibre 728 channel or parallel SCSI. 730 The relationship between the SCSI MIB module and any valid transport 731 MIB module is determined via the SCSI port managed table that has an 732 object pointing to the corresponding row, if any, of the relevant 733 table in a transport MIB module. 735 7. Miscellaneous Details 737 7.1. Names and Identifiers 739 The names and the identifiers of the SCSI devices, ports and logical 740 units depend on the underlying transport protocols; their format and 741 length vary accordingly. Please refer to SAM-2 [SAM2] in order to 742 get more details. 744 7.2. Logical Unit Number 746 The logical unit number is a 64-bit integer. This type does not 747 exist in SMI and therefore, this MIB contains a textual convention 748 defining LUN as an OCTET STRING. 750 7.3. Notifications 752 Separate SNMP notifications may be enabled/disabled to notify of a 753 change in any of the SCSI device status variables. A notification 754 will be generated theoretically for each occurrence (see restriction 755 below) of the abnormal status (e.g., if the SCSI device's current 756 status is abnormal and another logical unit changes its status from 757 available to abnormal another notification will occur). 759 To avoid sending an excessive number of notifications due to multiple 760 errors counted, an SNMP agent implementing the SCSI MIB module should 761 not send more than three SCSI notifications in any 10-second period. 763 The 3-in-10 rule was chosen because one notification every three 764 seconds was deemed often enough, but if and when two or three 765 different notifications happen at the same time, it would not be 766 desirable to suppress them. Three notifications in ten seconds is a 767 happy medium, where a short burst of notifications is allowed, 768 without inundating the network and/or destination host with a large 769 number of notifications. 771 The ultimate control on sending of notifications is in command of the 772 notification generator module specified in [RFC3413]. 774 7.4. SCSI Domains 776 SAM-2 [SAM2]specifies that devices belong to a domain. However, it 777 is not usually possible to determine this from within a system, so 778 domains are not represented within this MIB module. 780 7.5. Counters: 32 bits and 64 bits 782 Some counters, in (newer) high-performance systems, can increase at a 783 fast enough rate such that their representation as Counter32's, can 784 cause them to "wrap" in less than an hour. The SMIv2 provides 785 Counter64 as the syntax for such counters. However, (older) SNMPv1 786 implementations cannot support Counter64's. Thus, this MIB module 787 defines such counters as both Counter32's and Counter64's. 789 The counters in this MIB module which count data, are defined in 790 terms of megabytes (i.e., as the number of megabytes of data), such 791 that Counter64's are not required. 793 However, the counters in this MIB module, which count commands, when 794 in use at 5 GBit/second with 512-byte read/write operations, could 795 wrap within an hour. Therefore, each of these counters will be 796 defined as both a Counter32 and a Counter64, with the latter being 797 mandatory, for system speeds of 4 Gbit/second or higher. 799 A possible (but not required) implementation strategy is to have the 800 value of each Counter32 be the same value as the low order 32 bits of 801 the corresponding Counter64. 803 7.6. Local versus Remote Entities 805 This MIB module qualifies often SCSI entities as local or remote. 806 The local entities are the ones for which the agent is reporting. 807 The remote entities are the ones, which the local entities are in 808 communication with via the SCSI protocol. 810 8. Abbreviations 812 This MIB module will use the following abbreviations: 814 Inst = Instance 816 Dev = SCSI Device 818 Tgt = SCSI Target Device 820 Intr = SCSI Initiator Device 822 Att = Attached 824 Id = Identifier 826 Dsc = Discovered 828 pSCSI = Parallel SCSI 830 9. Object Definitions 832 SCSI-MIB DEFINITIONS ::= BEGIN 834 IMPORTS 835 MODULE-IDENTITY, OBJECT-IDENTITY, OBJECT-TYPE, 836 NOTIFICATION-TYPE, Integer32, Unsigned32, Counter32, 837 Counter64, Gauge32, 838 mib-2 FROM SNMPv2-SMI 839 TEXTUAL-CONVENTION, TimeStamp, TruthValue, 840 RowStatus, RowPointer, AutonomousType, 841 StorageType FROM SNMPv2-TC 842 MODULE-COMPLIANCE, OBJECT-GROUP, 843 NOTIFICATION-GROUP FROM SNMPv2-CONF 844 SnmpAdminString FROM SNMP-FRAMEWORK-MIB; 846 scsiMIB MODULE-IDENTITY 847 LAST-UPDATED "200601240000Z" -- 24th January 2006 848 ORGANIZATION "IETF" 849 CONTACT-INFO " 850 Michele Hallak-Stamler 851 Sanrad Intelligent Network 852 32 Habarzel Street 853 Tel Aviv, Israel 854 Phone: +972 3 7674809 855 E-mail: michele@sanrad.com 857 Yaron Lederman 858 Siliquent Technologies Ltd. 859 21 Etzel Street 860 Ramat Gan, Israel 861 Phone: +972 3 6777375 862 E-mail: yaronled@bezeqint.net 864 Mark Bakke 865 Postal: Cisco Systems, Inc 866 6450 Wedgwood Road, Suite 130 867 Maple Grove, MN 868 USA 55311 869 Phone: +1 763-398-1000 870 Fax: +1 763-398-1001 871 E-mail: mbakke@cisco.com 873 Marjorie Krueger 874 Postal: Hewlett-Packard 875 Networked Storage Architecture 876 Networked Storage Solutions Org. 877 8000 Foothills Blvd. 878 Roseville, CA 95747 879 Phone: +1 916-785-2656 880 Phone: +1 916-785-0391 881 E-mail: marjorie_krueger@hp.com 883 Keith McCloghrie 884 Cisco Systems, Inc. 885 Postal: 170 West Tasman Drive 886 San Jose, CA USA 95134 887 Phone: +1 408 526-5260 888 E-mail: kzm@cisco.com 890 " 891 DESCRIPTION 892 "The SCSI MIB Module. 893 Copyright (C) The Internet Society (2006). This version of 894 this MIB module is part of RFC yyyy; see the RFC 895 itself for full legal notices." 896 -- RFC Ed.: replace yyyy with actual RFC number & remove this note 898 -- Revision History 900 REVISION "200601240000Z" 901 DESCRIPTION " Initial version published as RFC yyyy." 902 -- RFC Ed.: replace yyyy with actual RFC number & remove this note 903 ::= { mib-2 xxx} -- must be changed in the future 904 -- RFC Ed.: replace xxx with IANA-assigned number & remove this note 905 --******************** Textual Conventions ************************* 906 ScsiLUN ::= TEXTUAL-CONVENTION 907 STATUS current 908 DESCRIPTION 909 "This textual convention represents a SCSI Logical Unit 910 Number. The format of a LUN is documented in Tables A.2 911 and A.3 of SAM-2[SAM2]." 912 REFERENCE 913 "SCSI Architecture Model-2 (SAM-2), ANSI INCITS 366-2003, 914 T10 Project 1157-D, 12 September 2002 - Annex A [SAM2]" 915 SYNTAX OCTET STRING (SIZE ( 2 | 8)) 917 ScsiIndexValue ::= TEXTUAL-CONVENTION 918 DISPLAY-HINT "d" 919 STATUS current 920 DESCRIPTION 921 " An arbitrary integer value, greater than zero, for use 922 as a unique index value." 923 SYNTAX Unsigned32 (1..4294967295) 925 ScsiPortIndexValueOrZero ::= TEXTUAL-CONVENTION 926 DISPLAY-HINT "d" 927 STATUS current 928 DESCRIPTION 929 "This textual convention is an extension of the ScsiIndexValue 930 convention. The latter defines a greater than zero value used 931 to identify an index. This extension permits the additional 932 value of zero and is applicable only to indices of SCSI port. 933 Usage of the zero is object-specific and must therefore be 934 defined as part of the description of any object, which uses 935 this syntax. Examples of the usage of zero might include 936 situations where index was unknown, or when none or all 937 indices need to be referenced." 938 SYNTAX Unsigned32 (0..4294967295) 940 ScsiIndexValueOrZero ::= TEXTUAL-CONVENTION 941 DISPLAY-HINT "d" 942 STATUS current 943 DESCRIPTION 944 "This textual convention is an extension of the ScsiIndexValue 945 convention. The latter defines a greater than zero value used 946 to identify an index. This extension permits the additional 947 value of zero. Usage of the zero is object-specific and must 948 therefore be defined as part of the description of any object 949 which uses this syntax. Examples of the usage of zero might 950 include situations where index was unknown, or when none or 951 all indices need to be referenced." 952 SYNTAX Unsigned32 (0..4294967295) 954 ScsiIdentifier ::= TEXTUAL-CONVENTION 955 STATUS current 956 DESCRIPTION 957 "This textual convention represents a generic SCSI port 958 identifier. 959 The format depends on the transport used and is documented 960 in Tables A.2 and A.3 of SAM-2[SAM2]." 961 REFERENCE 962 "SCSI Architecture Model-2 (SAM-2), ANSI INCITS 366-2003, 963 T10 Project 1157-D, 12 September 2002 - Annex A [SAM2]" 964 SYNTAX OCTET STRING (SIZE (0..262)) 966 ScsiName ::= TEXTUAL-CONVENTION 967 STATUS current 968 DESCRIPTION 969 " This Textual Convention represents the name of a SCSI 970 Initiator Device, a SCSI Target Device, a SCSI Initiator Port 971 or a SCSI Target Port. 972 The format depends on the transport used and is documented 973 in Tables A.4 and A.5 of SAM-2[SAM2]. 974 Every object defined using this syntax must define whether it 975 is: 976 a) Always used for a port, 977 b) Always used for a device, or 978 c) The circumstances under which it is used for a port or 979 device." 980 REFERENCE 981 "SCSI Architecture Model-2 (SAM-2), ANSI INCITS 366-2003, 982 T10 Project 1157-D, 12 September 2002 - Annex A [SAM2]" 983 SYNTAX OCTET STRING (SIZE (0..262)) 985 ScsiLuNameOrZero ::= TEXTUAL-CONVENTION 986 STATUS current 987 DESCRIPTION 988 "This Textual Convention represents either the name of a SCSI 989 Logical Unit or a zero-length string. Objects defined with 990 this syntax must specify the meaning of the zero-length 991 string. 992 The format of the name of a LU is defined : 993 - a zero-length octet string or 994 - a string of eight bytes." 995 REFERENCE 996 "SCSI Architecture Model-2 (SAM-2), ANSI INCITS 366-2003, 997 T10 Project 1157-D, 12 September 2002 - Annex A [SAM2]" 998 SYNTAX OCTET STRING (SIZE (0 | 8)) 1000 ScsiDeviceOrPort ::= TEXTUAL-CONVENTION 1001 STATUS current 1002 DESCRIPTION 1003 "This type specifies whether a particular configuration is 1004 applicable to a port or to a device." 1005 SYNTAX INTEGER { 1006 device(1), 1007 port(2), 1008 other(3) 1009 } 1011 ScsiIdCodeSet ::= TEXTUAL-CONVENTION 1012 DISPLAY-HINT "d" 1013 STATUS current 1014 DESCRIPTION 1015 "This Textual Convention specifies the code set for the 1016 identifier contained in an Identification Descriptor returned 1017 in a Logical Unit's Device Identification Page, and is 1018 formatted as defined in T10 SPC-2 (see REFERENCE) table 172 - 1019 Code Set" 1020 REFERENCE 1021 "ANSI - SCSI Primary Commands - 2 (SPC-2), 1022 ANSI INCITS 351-2001, 11 July 2001 Chapter 8: section 8.4.4, 1023 Vital Product Data Parameters [SPC2]" 1024 SYNTAX Unsigned32 (0..15) 1026 ScsiIdAssociation ::= TEXTUAL-CONVENTION 1027 DISPLAY-HINT "d" 1028 STATUS current 1029 DESCRIPTION 1030 "This Textual Convention specifies what the identifier is 1031 associated with (e.g, with the addressed physical/logical 1032 device or with a particular port) for the identifier 1033 contained in an Identification Descriptor returned in a 1034 Logical Unit's Device Identification Page, and is 1035 formatted as defined in T10 SPC-2 (see REFERENCE) 1036 table 173 - Association." 1037 REFERENCE 1038 "ANSI - SCSI Primary Commands - 2 (SPC-2), 1039 ANSI INCITS 351-2001, 11 July 2001 Chapter 8: section 8.4.4, 1040 Vital Product Data Parameters [SPC2]" 1041 SYNTAX Unsigned32 (0..3) 1043 ScsiIdType ::= TEXTUAL-CONVENTION 1044 DISPLAY-HINT "d" 1045 STATUS current 1046 DESCRIPTION 1047 "This Textual Convention specifies the type for the identifier 1048 contained in an Identification Descriptor returned in a 1049 Logical Unit's Device Identification Page, and is formatted 1050 as defined in T10 SPC-2 (see REFERENCE) table 174 -Identifier 1051 Type." 1052 REFERENCE 1053 "ANSI - SCSI Primary Commands - 2 (SPC-2), 1054 ANSI INCITS 351-2001, 11 July 2001 Chapter 8: section 8.4.4, 1055 Vital Product Data Parameters [SPC2]" 1056 SYNTAX Unsigned32 (0..15) 1058 ScsiIdValue ::= TEXTUAL-CONVENTION 1059 STATUS current 1060 DESCRIPTION 1061 "This Textual Convention represents an identifier. The objects 1062 of type ScsiIdCodeSet, ScsiIdAssociation, ScsiIdType, define 1063 together the format. 1064 The format is the same as contained in an Identification 1065 Descriptor returned in a Logical Unit's Device Identification 1066 Page, and is formatted as defined in T10 SPC-2 1067 (see REFERENCE)." 1068 REFERENCE 1069 "ANSI - SCSI Primary Commands - 2 (SPC-2), 1070 ANSI INCITS 351-2001, 11 July 2001 Chapter 8: section 8.4.4, 1071 Vital Product Data Parameters [SPC2]" 1072 SYNTAX OCTET STRING (SIZE (0..255)) 1074 ScsiHrSWInstalledIndexOrZero ::= TEXTUAL-CONVENTION 1075 DISPLAY-HINT "d" 1076 STATUS current 1077 DESCRIPTION 1078 "The index value for a software module's row in the Host 1079 Resources MIBs hrSWInstalledTable. A zero value indicates 1080 that no row in the hrSWInstalledTable is applicable." 1081 REFERENCE 1082 "hrSWInstalledTable is defined in the Host Resources MIB, 1083 [RFC2790]." 1084 SYNTAX Integer32 (0..2147483647) 1086 --****************** Structure of the MIB ************************** 1087 scsiNotifications OBJECT IDENTIFIER ::= { scsiMIB 0 } 1088 scsiAdmin OBJECT IDENTIFIER ::= { scsiMIB 1 } 1089 scsiObjects OBJECT IDENTIFIER ::= { scsiMIB 2 } 1090 scsiConformance OBJECT IDENTIFIER ::= { scsiMIB 3 } 1092 scsiTransportTypes OBJECT IDENTIFIER ::= { scsiAdmin 1 } 1093 scsiGeneral OBJECT IDENTIFIER ::= { scsiObjects 1 } 1094 scsiInitiatorDevice OBJECT IDENTIFIER ::= { scsiObjects 2 } 1095 scsiTargetDevice OBJECT IDENTIFIER ::= { scsiObjects 3 } 1096 scsiLogicalUnit OBJECT IDENTIFIER ::= { scsiObjects 4 } 1098 --****************** Transport Types ******************************* 1099 -- The following object identifiers allow determining the different 1100 -- transports (service delivery subsystems) in use under the SCSI 1101 -- layer. 1103 scsiTransportOther OBJECT-IDENTITY 1104 STATUS current 1105 DESCRIPTION 1106 "This identity identifies a transport that has no identity; it 1107 might happen because the transport is unknown or might not 1108 have been defined when this MIB module was created." 1109 ::= { scsiTransportTypes 1 } 1110 scsiTransportSPI OBJECT-IDENTITY 1111 STATUS current 1112 DESCRIPTION 1113 "This identity identifies a parallel SCSI transport." 1114 REFERENCE 1115 "T10 - SCSI Parallel Interface - 4 (SPI-4) 1116 - ANSI INCITS 362-2002 [SPI4]" 1117 ::= { scsiTransportTypes 2 } 1119 scsiTransportFCP OBJECT-IDENTITY 1120 STATUS current 1121 DESCRIPTION 1122 "This identity identifies a Fibre Channel Protocol for SCSI, 1123 Second Version." 1124 REFERENCE 1125 "T10 - SCSI Fibre Channel Protocol - 2 (FCP-2) 1126 - ANSI INCITS 350-2003 [FCP2]" 1127 ::= { scsiTransportTypes 3 } 1129 scsiTransportSRP OBJECT-IDENTITY 1130 STATUS current 1131 DESCRIPTION 1132 "This identity identifies a protocol for transporting SCSI over 1133 RDMA interfaces, e.g., InfiniBand (tm)." 1134 REFERENCE 1135 "T10 - SCSI RDMA Protocol (SRP) 1136 - ANSI INCITS 365-2002 [SRP]." 1137 ::= { scsiTransportTypes 4 } 1139 scsiTransportISCSI OBJECT-IDENTITY 1140 STATUS current 1141 DESCRIPTION 1142 "This identity identifies an ISCSI transport." 1143 REFERENCE 1144 "IETF IPS WG - Internet Small Computer Systems Interface 1145 (iSCSI) [RFC3720] " 1146 ::= { scsiTransportTypes 5 } 1148 scsiTransportSBP OBJECT-IDENTITY 1149 STATUS current 1150 DESCRIPTION 1151 "This identity identifies the Serial Bus Protocol 3." 1152 REFERENCE 1153 "T10 - Serial Bus Protocol 3 (SBP-3) 1154 - ANSI INCITS 375-2004 [SBP3]." 1155 ::= { scsiTransportTypes 6 } 1157 scsiTransportSAS OBJECT-IDENTITY 1158 STATUS current 1159 DESCRIPTION 1160 "This identity identifies the Serial Attach SCSI Protocol." 1161 REFERENCE 1162 "T10 - Serial Attached SCSI - 1.1 (SAS - 1.1) 1163 - #1601-D Rev-10 [SAS-1.1]." 1164 ::= { scsiTransportTypes 7 } 1166 --****************** Instance Table ***************************** 1167 scsiInstanceTable OBJECT-TYPE 1168 SYNTAX SEQUENCE OF ScsiInstanceEntry 1169 MAX-ACCESS not-accessible 1170 STATUS current 1171 DESCRIPTION 1172 "A list of SCSI instances present on the system. 1173 The SCSI Instance is the top-level entity, to which everything 1174 else belongs. An SNMP agent could represent more than one 1175 instance if it represents either a stack of devices, or virtual 1176 partitions of a larger device, or a host running multiple SCSI 1177 implementations from different vendors." 1178 ::= { scsiGeneral 1 } 1180 scsiInstanceEntry OBJECT-TYPE 1181 SYNTAX ScsiInstanceEntry 1182 MAX-ACCESS not-accessible 1183 STATUS current 1184 DESCRIPTION 1185 "An entry (row) containing management information applicable to 1186 a particular SCSI instance." 1187 INDEX { scsiInstIndex } 1188 ::= { scsiInstanceTable 1 } 1190 ScsiInstanceEntry ::= SEQUENCE { 1191 scsiInstIndex ScsiIndexValue, 1192 scsiInstAlias SnmpAdminString, 1193 scsiInstSoftwareIndex ScsiHrSWInstalledIndexOrZero, 1194 scsiInstVendorVersion SnmpAdminString, 1195 scsiInstScsiNotificationsEnable TruthValue, 1196 scsiInstStorageType StorageType 1197 } 1199 scsiInstIndex OBJECT-TYPE 1200 SYNTAX ScsiIndexValue 1201 MAX-ACCESS not-accessible 1202 STATUS current 1203 DESCRIPTION 1204 "This object represents an arbitrary integer used to uniquely 1205 identify a particular SCSI instance." 1207 ::= { scsiInstanceEntry 1 } 1209 scsiInstAlias OBJECT-TYPE 1210 SYNTAX SnmpAdminString (SIZE(0..79)) 1211 MAX-ACCESS read-write 1212 STATUS current 1213 DESCRIPTION 1214 "This object represents an administrative string, configured by 1215 the administrator. It can be a zero-length string." 1216 ::= { scsiInstanceEntry 2 } 1218 scsiInstSoftwareIndex OBJECT-TYPE 1219 SYNTAX ScsiHrSWInstalledIndexOrZero 1220 MAX-ACCESS read-only 1221 STATUS current 1222 DESCRIPTION 1223 "If this management instance corresponds to an installed 1224 software module, then this object's value is the value of the 1225 hrSWInstalledIndex of that module. If there is no 1226 correspondence to an installed software module (or no module 1227 which has a hrSWInstalledIndex value), then the value of this 1228 object is zero." 1229 REFERENCE 1230 "hrSWInstalledIndex is defined in the Host Resources MIB, 1231 [RFC2790]." 1232 ::= { scsiInstanceEntry 3 } 1234 scsiInstVendorVersion OBJECT-TYPE 1235 SYNTAX SnmpAdminString 1236 MAX-ACCESS read-only 1237 STATUS current 1238 DESCRIPTION 1239 "This object represents a text string set by the manufacturer 1240 describing the version of this instance. The format of this 1241 string is determined solely by the manufacturer, and is for 1242 informational purposes only. It is unrelated to the SCSI 1243 specification version numbers." 1244 ::= { scsiInstanceEntry 4 } 1246 scsiInstScsiNotificationsEnable OBJECT-TYPE 1247 SYNTAX TruthValue 1248 MAX-ACCESS read-write 1249 STATUS current 1250 DESCRIPTION 1251 " This object indicates whether notifications defined in this 1252 MIB module will be generated." 1253 DEFVAL { true } 1254 ::= { scsiInstanceEntry 5 } 1255 scsiInstStorageType OBJECT-TYPE 1256 SYNTAX StorageType 1257 MAX-ACCESS read-write 1258 STATUS current 1259 DESCRIPTION 1260 "This object specifies the memory realization for 1261 this SCSI entity. 1262 Specifically, each row in the following tables: 1264 scsiIntrDevTable 1265 scsiDscTgtTable 1266 scsiAuthorizedIntrTable 1267 scsiLunMapTable 1269 has a StorageType as specified by the instance of 1270 this object which is INDEX-ed by the same value of 1271 scsiInstIndex. 1272 This value of this object is also used to indicate 1273 the persistence across reboots of writable values in 1274 its row of the scsiInstanceTable. 1275 Conceptual rows having the value 'permanent' need not 1276 allow write-access to any columnar objects in the row, 1277 nor to any object belonging to a table whose entry is 1278 INDEX-ed by the same value of scsiInstIndex." 1279 DEFVAL { nonVolatile } 1280 ::= { scsiInstanceEntry 6 } 1282 --******************** Device Table ******************************** 1283 scsiDeviceTable OBJECT-TYPE 1284 SYNTAX SEQUENCE OF ScsiDeviceEntry 1285 MAX-ACCESS not-accessible 1286 STATUS current 1287 DESCRIPTION 1288 "A list of SCSI Devices contained in each of the SCSI manageable 1289 instances that this agent is reporting." 1290 ::= { scsiGeneral 2 } 1292 scsiDeviceEntry OBJECT-TYPE 1293 SYNTAX ScsiDeviceEntry 1294 MAX-ACCESS not-accessible 1295 STATUS current 1296 DESCRIPTION 1297 "An entry (row) containing management information applicable to 1298 a particular SCSI Device included in this SCSI manageable 1299 instance identifiable by the value of scsiInstIndex." 1300 INDEX {scsiInstIndex, scsiDeviceIndex} 1301 ::= { scsiDeviceTable 1 } 1302 ScsiDeviceEntry ::= SEQUENCE { 1303 scsiDeviceIndex ScsiIndexValue, 1304 scsiDeviceAlias SnmpAdminString, 1305 scsiDeviceRole BITS, 1306 scsiDevicePortNumber Unsigned32 1307 } 1309 scsiDeviceIndex OBJECT-TYPE 1310 SYNTAX ScsiIndexValue 1311 MAX-ACCESS not-accessible 1312 STATUS current 1313 DESCRIPTION 1314 "This object is an arbitrary integer used to uniquely identify 1315 a particular device within a particular SCSI instance." 1316 ::= { scsiDeviceEntry 1 } 1318 scsiDeviceAlias OBJECT-TYPE 1319 SYNTAX SnmpAdminString (SIZE(0..79)) 1320 MAX-ACCESS read-write 1321 STATUS current 1322 DESCRIPTION 1323 "This object contains an administrative name for this device. 1324 If no name is assigned, the value of this object is the 1325 zero-length string. 1326 The StorageType of this object is specified by the instance 1327 of scsiInstStorageType which is INDEX-ed by the same value of 1328 scsiInstIndex." 1329 ::= { scsiDeviceEntry 2 } 1331 scsiDeviceRole OBJECT-TYPE 1332 SYNTAX BITS { 1333 target(0), 1334 initiator(1) 1335 } 1336 MAX-ACCESS read-only 1337 STATUS current 1338 DESCRIPTION 1339 "This object determines whether this device is acting as a 1340 SCSI initiator device, or as a SCSI target device or as both." 1341 ::= { scsiDeviceEntry 3 } 1343 scsiDevicePortNumber OBJECT-TYPE 1344 SYNTAX Unsigned32 1345 MAX-ACCESS read-only 1346 STATUS current 1347 DESCRIPTION 1348 "This object represents the number of ports contained in this 1349 device." 1351 ::= { scsiDeviceEntry 4 } 1353 --****************** Port Table ************************************ 1354 scsiPortTable OBJECT-TYPE 1355 SYNTAX SEQUENCE OF ScsiPortEntry 1356 MAX-ACCESS not-accessible 1357 STATUS current 1358 DESCRIPTION 1359 "A list of SCSI Ports for each SCSI device in each instance." 1360 ::= { scsiGeneral 3 } 1362 scsiPortEntry OBJECT-TYPE 1363 SYNTAX ScsiPortEntry 1364 MAX-ACCESS not-accessible 1365 STATUS current 1366 DESCRIPTION 1367 "An entry (row) containing management information applicable to 1368 a particular SCSI port of a particular SCSI device in a 1369 particular SCSI instance." 1370 INDEX { scsiInstIndex, scsiDeviceIndex, scsiPortIndex } 1371 ::= { scsiPortTable 1 } 1373 ScsiPortEntry ::= SEQUENCE { 1374 scsiPortIndex ScsiIndexValue, 1375 scsiPortRole BITS, 1376 scsiPortTransportPtr RowPointer, 1377 scsiPortBusyStatuses Counter32 1378 } 1380 scsiPortIndex OBJECT-TYPE 1381 SYNTAX ScsiIndexValue 1382 MAX-ACCESS not-accessible 1383 STATUS current 1384 DESCRIPTION 1385 "An arbitrary integer used to uniquely identify a particular 1386 port of a given device within a particular SCSI instance." 1387 ::= { scsiPortEntry 1 } 1389 scsiPortRole OBJECT-TYPE 1390 SYNTAX BITS { 1391 target(0), 1392 initiator(1) 1393 } 1394 MAX-ACCESS read-only 1395 STATUS current 1396 DESCRIPTION 1397 "This object indicates whether this port is acting as a 1398 SCSI initiator port, or as a SCSI target port or as both." 1399 ::= { scsiPortEntry 2 } 1401 scsiPortTransportPtr OBJECT-TYPE 1402 SYNTAX RowPointer 1403 MAX-ACCESS read-only 1404 STATUS current 1405 DESCRIPTION 1406 "This object is a pointer to the corresponding row in the 1407 scsiTransportTable. This row contains information on the 1408 transport like transport type and port name." 1409 ::= { scsiPortEntry 3 } 1411 scsiPortBusyStatuses OBJECT-TYPE 1412 SYNTAX Counter32 1413 MAX-ACCESS read-only 1414 STATUS current 1415 DESCRIPTION 1416 "This object represents the number of port busy status sent or 1417 received by this port. Note: Initiator ports only receive busy 1418 status and SCSI target ports only send busy status. 1419 Discontinuities in the value of this counter can occur at re- 1420 initialization of the management system." 1421 ::= { scsiPortEntry 4 } 1423 --******************** Table of supported transports *************** 1424 scsiTransportTable OBJECT-TYPE 1425 SYNTAX SEQUENCE OF ScsiTransportEntry 1426 MAX-ACCESS not-accessible 1427 STATUS current 1428 DESCRIPTION 1429 "This table contains the device transport-specific information 1430 for each transport connected to each device in 1431 scsiDeviceTable." 1432 ::= { scsiGeneral 5 } 1434 scsiTransportEntry OBJECT-TYPE 1435 SYNTAX ScsiTransportEntry 1436 MAX-ACCESS not-accessible 1437 STATUS current 1438 DESCRIPTION 1439 "An entry (row) containing parameters applicable to a transport 1440 used by a particular device of a particular SCSI manageable 1441 instance." 1442 INDEX { scsiInstIndex, scsiDeviceIndex, scsiTransportIndex} 1443 ::= { scsiTransportTable 1 } 1444 ScsiTransportEntry ::= SEQUENCE { 1445 scsiTransportIndex ScsiIndexValue, 1446 scsiTransportType AutonomousType, 1447 scsiTransportPointer RowPointer, 1448 scsiTransportDevName ScsiName 1449 } 1451 scsiTransportIndex OBJECT-TYPE 1452 SYNTAX ScsiIndexValue 1453 MAX-ACCESS not-accessible 1454 STATUS current 1455 DESCRIPTION 1456 "An arbitrary integer used to uniquely identify a particular 1457 transport within a given device within a particular SCSI 1458 instance." 1459 ::= { scsiTransportEntry 1 } 1461 scsiTransportType OBJECT-TYPE 1462 SYNTAX AutonomousType 1463 MAX-ACCESS read-only 1464 STATUS current 1465 DESCRIPTION 1466 "This object identifies the transport type of this row of the 1467 transport table. For example, if this object has the value 1468 scsiTransportFCP, then the identified transport is FCP." 1469 ::= { scsiTransportEntry 2 } 1471 scsiTransportPointer OBJECT-TYPE 1472 SYNTAX RowPointer 1473 MAX-ACCESS read-only 1474 STATUS current 1475 DESCRIPTION 1476 "This object represents a pointer to a conceptual row in a 1477 'transport' MIB module allowing a manager to get useful 1478 information for the transport described by this entry. 1479 For example, if the transport of this device is iSCSI, this 1480 object will point to the iSCSI Instance of the iSCSI MIB 1481 module. 1482 If there is no MIB for this transport, this object has the 1483 value 0.0." 1484 ::= { scsiTransportEntry 3 } 1486 scsiTransportDevName OBJECT-TYPE 1487 SYNTAX ScsiName 1488 MAX-ACCESS read-only 1489 STATUS current 1490 DESCRIPTION 1491 "This object represents the name of this device in one of the 1492 format(s) appropriate for this type of transport." 1493 ::= { scsiTransportEntry 4 } 1495 --******************** SCSI Initiator Device Table *************** 1496 scsiIntrDevTable OBJECT-TYPE 1497 SYNTAX SEQUENCE OF ScsiIntrDevEntry 1498 MAX-ACCESS not-accessible 1499 STATUS current 1500 DESCRIPTION 1501 "This table contains information for each local SCSI initiator 1502 device in each instance." 1503 ::= { scsiInitiatorDevice 1} 1505 scsiIntrDevEntry OBJECT-TYPE 1506 SYNTAX ScsiIntrDevEntry 1507 MAX-ACCESS not-accessible 1508 STATUS current 1509 DESCRIPTION 1510 "An entry (row) containing information applicable to a SCSI 1511 initiator device within a particular SCSI instance." 1512 INDEX { scsiInstIndex, scsiDeviceIndex } 1513 ::= { scsiIntrDevTable 1 } 1515 ScsiIntrDevEntry ::= SEQUENCE { 1516 scsiIntrDevTgtAccessMode INTEGER, 1517 scsiIntrDevOutResets Counter32 1518 } 1520 scsiIntrDevTgtAccessMode OBJECT-TYPE 1521 SYNTAX INTEGER { 1522 unknown(1), 1523 autoEnable(2), 1524 manualEnable(3) 1525 } 1526 MAX-ACCESS read-write 1527 STATUS current 1528 DESCRIPTION 1529 "This object controls whether a discovered SCSI target device is 1530 immediately authorized or not: 1531 - autoEnable (2) means that when a SCSI initiator device 1532 discovers a SCSI target device, it can use it immediately, 1533 - manualEnable (3) means that the SCSI initiator device 1534 must wait for an operator to set scsiIntrDscTgtConfigured 1535 = true before it is authorized. 1536 The StorageType of this object is specified by the instance 1537 of scsiInstStorageType which is INDEX-ed by the same value of 1538 scsiInstIndex." 1539 ::= { scsiIntrDevEntry 1 } 1540 scsiIntrDevOutResets OBJECT-TYPE 1541 SYNTAX Counter32 1542 MAX-ACCESS read-only 1543 STATUS current 1544 DESCRIPTION 1545 "This object represents the total number of times that this SCSI 1546 Initiator Device has issued: 1547 - a LOGICAL UNIT RESET or TARGET RESET task management request, 1548 or 1549 - any other SCSI transport protocol-specific action or event 1550 that causes a Logical Unit Reset or a Hard Reset at one or 1551 more SCSI Target Ports ([SAM2] chapter 5.9.6, 5.9.7) 1552 Discontinuities in the value of this counter can occur at re- 1553 initialization of the management system." 1554 REFERENCE 1555 "SCSI Architecture Model-2 (SAM-2), ANSI INCITS 366-2003, 1556 T10 Project 1157-D, 12 September 2002 1557 Chapters 5.9.6 & 5.9.7 [SAM2]" 1558 ::= { scsiIntrDevEntry 2 } 1560 -- The following section describes managed objects related to 1561 -- SCSI initiator ports. 1563 scsiIntrPortTable OBJECT-TYPE 1564 SYNTAX SEQUENCE OF ScsiIntrPortEntry 1565 MAX-ACCESS not-accessible 1566 STATUS current 1567 DESCRIPTION 1568 "This table contains all the SCSI initiator ports for each 1569 local SCSI Initiator or Target/Initiator devices in each SCSI 1570 instance." 1571 ::= { scsiInitiatorDevice 2 } 1573 scsiIntrPortEntry OBJECT-TYPE 1574 SYNTAX ScsiIntrPortEntry 1575 MAX-ACCESS not-accessible 1576 STATUS current 1577 DESCRIPTION 1578 "An entry (row) containing information applicable to a 1579 particular SCSI initiator port of a particular SCSI device 1580 within a SCSI instance. " 1581 INDEX { scsiInstIndex, scsiDeviceIndex, scsiPortIndex } 1582 ::= { scsiIntrPortTable 1 } 1584 ScsiIntrPortEntry ::= SEQUENCE { 1585 scsiIntrPortName ScsiName, 1586 scsiIntrPortIdentifier ScsiIdentifier, 1587 scsiIntrPortOutCommands Counter32, 1588 scsiIntrPortWrittenMegaBytes Counter32, 1589 scsiIntrPortReadMegaBytes Counter32, 1590 scsiIntrPortHSOutCommands Counter64 1591 } 1593 scsiIntrPortName OBJECT-TYPE 1594 SYNTAX ScsiName 1595 MAX-ACCESS read-only 1596 STATUS current 1597 DESCRIPTION 1598 "This object represents the name of the port assigned for use 1599 by the SCSI protocol. The format will depend on the type of 1600 transport this port is using." 1601 ::= { scsiIntrPortEntry 1 } 1603 scsiIntrPortIdentifier OBJECT-TYPE 1604 SYNTAX ScsiIdentifier 1605 MAX-ACCESS read-only 1606 STATUS current 1607 DESCRIPTION 1608 "This object represents the identifier of the port in one of 1609 the format(s) appropriate for the type of transport in use." 1610 ::= { scsiIntrPortEntry 2 } 1612 scsiIntrPortOutCommands OBJECT-TYPE 1613 SYNTAX Counter32 1614 UNITS "commands" 1615 MAX-ACCESS read-only 1616 STATUS current 1617 DESCRIPTION 1618 "This object represents the number of commands sent by this 1619 SCSI initiator port. 1620 Discontinuities in the value of this counter can occur at re- 1621 initialization of the management system." 1622 ::= { scsiIntrPortEntry 3 } 1624 scsiIntrPortWrittenMegaBytes OBJECT-TYPE 1625 SYNTAX Counter32 1626 UNITS "Megabytes" 1627 MAX-ACCESS read-only 1628 STATUS current 1629 DESCRIPTION 1630 "This object represents the amount of data in Megabytes sent 1631 by this SCSI initiator port. 1632 Discontinuities in the value of this counter can occur at re- 1633 initialization of the management system." 1635 ::= { scsiIntrPortEntry 4 } 1637 scsiIntrPortReadMegaBytes OBJECT-TYPE 1638 SYNTAX Counter32 1639 UNITS "Megabytes" 1640 MAX-ACCESS read-only 1641 STATUS current 1642 DESCRIPTION 1643 "This object represents the amount of data in Megabytes 1644 received by this SCSI initiator port. 1645 Discontinuities in the value of this counter can occur at re- 1646 initialization of the management system." 1647 ::= { scsiIntrPortEntry 5 } 1649 scsiIntrPortHSOutCommands OBJECT-TYPE 1650 SYNTAX Counter64 1651 UNITS "commands" 1652 MAX-ACCESS read-only 1653 STATUS current 1654 DESCRIPTION 1655 "This object represents the number of commands sent by this 1656 SCSI initiator port. This object provides support for systems 1657 which can quickly generate a large number of commands because 1658 they run at high speed. 1659 Discontinuities in the value of this counter can occur at re- 1660 initialization of the management system." 1661 ::= { scsiIntrPortEntry 6 } 1663 --******************** Discovered SCSI Target Device group ******** 1664 scsiRemoteTgtDev OBJECT IDENTIFIER ::= { scsiInitiatorDevice 3 } 1666 -- SCSI target device discovered or authorized to attach each of the 1667 -- SCSI initiator ports of each SCSI initiator device of each 1668 -- instance. 1670 scsiDscTgtTable OBJECT-TYPE 1671 SYNTAX SEQUENCE OF ScsiDscTgtEntry 1672 MAX-ACCESS not-accessible 1673 STATUS current 1674 DESCRIPTION 1675 "This table includes all the remote (not in the local system) 1676 SCSI target ports that are authorized to attach to each local 1677 SCSI initiator port of this SCSI instance." 1678 ::= { scsiRemoteTgtDev 1 } 1680 scsiDscTgtEntry OBJECT-TYPE 1681 SYNTAX ScsiDscTgtEntry 1682 MAX-ACCESS not-accessible 1683 STATUS current 1684 DESCRIPTION 1685 "Each entry (row) contains information about the SCSI target 1686 device or port to which this SCSI initiator port (or all SCSI 1687 initiator ports in the SCSI initiator entry indexed by 1688 scsiInstIndex, scsiDeviceIndex) will attempt to attach. The 1689 entry is either for all local ports (if scsiDscTgtIntrPortIndex 1690 is zero), or only for the specific SCSI initiator port 1691 identified by scsiDscTgtIntrPortIndex. Note that if an entry in 1692 this table is deleted, any corresponding entries in the 1693 scsiDscLunsTable must be deleted as well. 1694 The StorageType of a row in this table is specified by the 1695 instance of scsiInstStorageType which is INDEX-ed by the same 1696 value of scsiInstIndex." 1697 INDEX { scsiInstIndex, scsiDeviceIndex, scsiDscTgtIntrPortIndex, 1698 scsiDscTgtIndex } 1699 ::= { scsiDscTgtTable 1 } 1701 ScsiDscTgtEntry ::= SEQUENCE { 1702 scsiDscTgtIntrPortIndex ScsiPortIndexValueOrZero, 1703 scsiDscTgtIndex ScsiIndexValue, 1704 scsiDscTgtDevOrPort ScsiDeviceOrPort, 1705 scsiDscTgtName ScsiName, 1706 scsiDscTgtConfigured TruthValue, 1707 scsiDscTgtDiscovered TruthValue, 1708 scsiDscTgtInCommands Counter32, 1709 scsiDscTgtWrittenMegaBytes Counter32, 1710 scsiDscTgtReadMegaBytes Counter32, 1711 scsiDscTgtHSInCommands Counter64, 1712 scsiDscTgtLastCreation TimeStamp, 1713 scsiDscTgtRowStatus RowStatus 1714 } 1716 scsiDscTgtIntrPortIndex OBJECT-TYPE 1717 SYNTAX ScsiPortIndexValueOrZero 1718 MAX-ACCESS not-accessible 1719 STATUS current 1720 DESCRIPTION 1721 "This object relates to a particular local device within a 1722 particular SCSI instance and specifies: 1723 - the index of the local SCSI initiator port, 1724 - or zero, if this entry refers to the local device and 1725 therefore refers to all the local SCSI initiator ports." 1726 ::= { scsiDscTgtEntry 1 } 1728 scsiDscTgtIndex OBJECT-TYPE 1729 SYNTAX ScsiIndexValue 1730 MAX-ACCESS not-accessible 1731 STATUS current 1732 DESCRIPTION 1733 "This object is an arbitrary integer used to uniquely identify 1734 a particular SCSI target device either discovered by, or 1735 configured for use with, one or more ports scsiDscTgtName of 1736 a particular device within a particular SCSI instance. " 1737 ::= { scsiDscTgtEntry 2 } 1739 scsiDscTgtDevOrPort OBJECT-TYPE 1740 SYNTAX ScsiDeviceOrPort 1741 MAX-ACCESS read-create 1742 STATUS current 1743 DESCRIPTION 1744 "This object indicates whether this entry describes a 1745 configured SCSI target device name (and applies to all ports 1746 on the identified SCSI target device) or an individual SCSI 1747 target port." 1748 ::= { scsiDscTgtEntry 3 } 1750 scsiDscTgtName OBJECT-TYPE 1751 SYNTAX ScsiName 1752 MAX-ACCESS read-create 1753 STATUS current 1754 DESCRIPTION 1755 "This object represents the name of this configured or 1756 discovered SCSI target device or port depending on the value 1757 of scsiDscTgtDevOrPort." 1758 ::= { scsiDscTgtEntry 4 } 1760 scsiDscTgtConfigured OBJECT-TYPE 1761 SYNTAX TruthValue 1762 MAX-ACCESS read-create 1763 STATUS current 1764 DESCRIPTION 1765 "This object means: 1766 -true(1): this entry has been configured by an administrator 1767 -false(2): this entry has been added from a discovery 1768 mechanism (eg. SendTargets, SLP, iSNS). 1769 An administrator can modify this value from false to true." 1770 DEFVAL { true } 1771 ::= { scsiDscTgtEntry 5 } 1773 scsiDscTgtDiscovered OBJECT-TYPE 1774 SYNTAX TruthValue 1775 MAX-ACCESS read-only 1776 STATUS current 1777 DESCRIPTION 1778 "This object means: 1779 -true(1): this entry has been discovered by the SCSI instance 1780 as result of an automatic discovery process. 1781 -false(2):this entry has been added by manual configuration. 1782 This entry is read-only because an administrator cannot change 1783 it. 1784 Note that it is an implementation decision to determine how 1785 long to retain a row with configured=false, such as when the 1786 SCSI target device is no longer visible/accessible to the local 1787 SCSI initiator device." 1788 ::= { scsiDscTgtEntry 6 } 1790 scsiDscTgtInCommands OBJECT-TYPE 1791 SYNTAX Counter32 1792 UNITS "commands" 1793 MAX-ACCESS read-only 1794 STATUS current 1795 DESCRIPTION 1796 "This object represents the number of commands received from 1797 this SCSI target port or device. 1798 Discontinuities in the value of this counter can occur at re- 1799 initialization of the management system, and at other times as 1800 indicated by the value of scsiDscTgtLastCreation." 1801 ::= { scsiDscTgtEntry 7 } 1803 scsiDscTgtWrittenMegaBytes OBJECT-TYPE 1804 SYNTAX Counter32 1805 UNITS "Megabytes" 1806 MAX-ACCESS read-only 1807 STATUS current 1808 DESCRIPTION 1809 "This object represents the amount of megabytes of data sent as 1810 the result of WRITE commands to this SCSI target port or device. 1811 Discontinuities in the value of this counter can occur at re- 1812 initialization of the management system, and at other times as 1813 indicated by the value of scsiDscTgtLastCreation." 1814 ::= { scsiDscTgtEntry 8 } 1816 scsiDscTgtReadMegaBytes OBJECT-TYPE 1817 SYNTAX Counter32 1818 UNITS "Megabytes" 1819 MAX-ACCESS read-only 1820 STATUS current 1821 DESCRIPTION 1822 "This object represents the amount of megabytes received as the 1823 result of READ commands to this SCSI target port or device. 1824 Discontinuities in the value of this counter can occur at re- 1825 initialization of the management system, and at other times as 1826 indicated by the value of scsiDscTgtLastCreation." 1827 ::= { scsiDscTgtEntry 9 } 1829 scsiDscTgtHSInCommands OBJECT-TYPE 1830 SYNTAX Counter64 1831 UNITS "commands" 1832 MAX-ACCESS read-only 1833 STATUS current 1834 DESCRIPTION 1835 "This object represents the number of commands received by this 1836 SCSI target port or device. This object provides support for 1837 system, which can quickly generate a large number of commands 1838 because they run at high speed. 1839 Discontinuities in the value of this counter can occur at re- 1840 initialization of the management system, and at other times as 1841 indicated by the value of scsiDscTgtLastCreation." 1842 ::= { scsiDscTgtEntry 10 } 1844 scsiDscTgtLastCreation OBJECT-TYPE 1845 SYNTAX TimeStamp 1846 MAX-ACCESS read-only 1847 STATUS current 1848 DESCRIPTION 1849 "This object represents the value of sysUpTime when this row 1850 was created." 1851 ::= { scsiDscTgtEntry 11 } 1853 scsiDscTgtRowStatus OBJECT-TYPE 1854 SYNTAX RowStatus 1855 MAX-ACCESS read-create 1856 STATUS current 1857 DESCRIPTION 1858 "This object allows an administrator to configure dynamically a 1859 new entry in this table via SNMP or eventually delete it. 1860 An administrator is not allowed to delete an entry for which 1861 the value of the object scsiIntrDscTgtDiscovered is equal to 1862 true. 1863 Note that when an entry in this table is deleted, then any 1864 corresponding entries in the scsiDscLunsTable must also be 1865 automatically deleted. 1867 A newly created row cannot be made active until a value has 1868 been set for scsiDscTgtName. In this case, the value of the 1869 corresponding instance of the scsiDscTgtRowStatus column will 1870 stay 'notReady'. 1871 The RowStatus TC [RFC2579] requires that this DESCRIPTION 1872 clause states under which circumstances other objects in this 1873 row can be modified: 1875 The value of this object has no effect on whether other objects 1876 in this conceptual row can be modified. " 1877 ::= { scsiDscTgtEntry 12 } 1879 --********************** LUNs discovered *************************** 1880 scsiDscLunTable OBJECT-TYPE 1881 SYNTAX SEQUENCE OF ScsiDscLunEntry 1882 MAX-ACCESS not-accessible 1883 STATUS current 1884 DESCRIPTION 1885 "This table includes all the remote (not in the local system) 1886 logical unit numbers (LUNs) discovered via each local SCSI 1887 initiator port of each local device within a particular SCSI 1888 instance." 1889 ::= { scsiRemoteTgtDev 2 } 1891 scsiDscLunEntry OBJECT-TYPE 1892 SYNTAX ScsiDscLunEntry 1893 MAX-ACCESS not-accessible 1894 STATUS current 1895 DESCRIPTION 1896 "An entry (row) represents a discovered LUN at a particular 1897 SCSI target device (scsiDscTgtIndex), where the LUN was 1898 discovered by a particular local SCSI initiator device within a 1899 particular SCSI instance, possibly via a particular local 1900 SCSI initiator port. 1901 Note that when an entry in the scsiDscTgtTable is deleted, 1902 all corresponding entries in this table should automatically be 1903 deleted." 1904 INDEX { scsiInstIndex, scsiDeviceIndex, scsiDscTgtIntrPortIndex, 1905 scsiDscTgtIndex, scsiDscLunIndex } 1906 ::= { scsiDscLunTable 1 } 1908 ScsiDscLunEntry ::= SEQUENCE { 1909 scsiDscLunIndex ScsiIndexValue, 1910 scsiDscLunLun ScsiLUN 1911 } 1913 scsiDscLunIndex OBJECT-TYPE 1914 SYNTAX ScsiIndexValue 1915 MAX-ACCESS not-accessible 1916 STATUS current 1917 DESCRIPTION 1918 "This object is an arbitrary integer used to uniquely identify 1919 a particular LUN discovered by a particular SCSI initiator port 1920 or a particular SCSI initiator device within a particular SCSI 1921 instance. 1923 Entries in the scsiDscLunIdTable are associated with a LUN by 1924 having the value of this object in their INDEX." 1925 ::= { scsiDscLunEntry 1 } 1927 scsiDscLunLun OBJECT-TYPE 1928 SYNTAX ScsiLUN 1929 MAX-ACCESS read-only 1930 STATUS current 1931 DESCRIPTION 1932 "This object contains the Logical Unit Number (LUN) of the 1933 discovered logical unit." 1934 ::= { scsiDscLunEntry 2 } 1936 --******************** LU Identifiers discovered ******************* 1937 scsiDscLunIdTable OBJECT-TYPE 1938 SYNTAX SEQUENCE OF ScsiDscLunIdEntry 1939 MAX-ACCESS not-accessible 1940 STATUS current 1941 DESCRIPTION 1942 "This table includes all the known LU Identifiers of the remote 1943 (not in the local system) logical units discovered via each 1944 local SCSI initiator port or device of this SCSI instance." 1945 ::= { scsiRemoteTgtDev 3 } 1947 scsiDscLunIdEntry OBJECT-TYPE 1948 SYNTAX ScsiDscLunIdEntry 1949 MAX-ACCESS not-accessible 1950 STATUS current 1951 DESCRIPTION 1952 "An entry (row) represents the LU Identifier of a discovered 1953 LUN at a particular SCSI target device (scsiDscTgtIndex), where 1954 the LUN was discovered by a particular local SCSI initiator 1955 device within a particular SCSI instance, possibly via a 1956 particular local SCSI initiator port." 1957 INDEX { scsiInstIndex, scsiDeviceIndex, scsiDscTgtIntrPortIndex, 1958 scsiDscTgtIndex, scsiDscLunIndex, scsiDscLunIdIndex } 1959 ::= { scsiDscLunIdTable 1 } 1961 ScsiDscLunIdEntry ::= SEQUENCE { 1962 scsiDscLunIdIndex ScsiIndexValue, 1963 scsiDscLunIdCodeSet ScsiIdCodeSet, 1964 scsiDscLunIdAssociation ScsiIdAssociation, 1965 scsiDscLunIdType ScsiIdType, 1966 scsiDscLunIdValue ScsiIdValue 1967 } 1969 scsiDscLunIdIndex OBJECT-TYPE 1970 SYNTAX ScsiIndexValue 1971 MAX-ACCESS not-accessible 1972 STATUS current 1973 DESCRIPTION 1974 "This object is an arbitrary integer used to uniquely identify 1975 a particular LUN Identifier discovered by each SCSI initiator 1976 device or particular SCSI initiator port within a particular 1977 SCSI instance." 1978 ::= { scsiDscLunIdEntry 1 } 1980 scsiDscLunIdCodeSet OBJECT-TYPE 1981 SYNTAX ScsiIdCodeSet 1982 MAX-ACCESS read-only 1983 STATUS current 1984 DESCRIPTION 1985 "This object specifies the code set in use with this 1986 identifier. The value is represented in the same format as 1987 is contained in the identifier's Identification Descriptor 1988 within the Logical Unit's Device Identification Page." 1989 REFERENCE 1990 "ANSI - SCSI Primary Commands - 2 (SPC-2), 1991 ANSI INCITS 351-2001, 11 July 2001 Chapter 8: section 8.4.4, 1992 Vital Product Data Parameters [SPC2]" 1993 ::= { scsiDscLunIdEntry 2 } 1995 scsiDscLunIdAssociation OBJECT-TYPE 1996 SYNTAX ScsiIdAssociation 1997 MAX-ACCESS read-only 1998 STATUS current 1999 DESCRIPTION 2000 "This object specifies what the identifier is associated with 2001 (e.g, with the addressed physical/logical device or with a 2002 particular port). The value is represented in the same format 2003 as is contained in the identifier's Identification Descriptor 2004 within the Logical Unit's Device Identification Page." 2005 REFERENCE 2006 "ANSI - SCSI Primary Commands - 2 (SPC-2), 2007 ANSI INCITS 351-2001, 11 July 2001 Chapter 8: section 8.4.4, 2008 Vital Product Data Parameters [SPC2]" 2009 ::= { scsiDscLunIdEntry 3 } 2011 scsiDscLunIdType OBJECT-TYPE 2012 SYNTAX ScsiIdType 2013 MAX-ACCESS read-only 2014 STATUS current 2015 DESCRIPTION 2016 "This object specifies the type of the identifier. 2017 The value is represented in the same format as is contained in 2018 the identifier's Identification Descriptor within the Logical 2019 Unit's Device Identification Page." 2020 REFERENCE 2021 "ANSI - SCSI Primary Commands - 2 (SPC-2), 2022 ANSI INCITS 351-2001, 11 July 2001 Chapter 8: section 8.4.4, 2023 Vital Product Data Parameters [SPC2]" 2024 ::= { scsiDscLunIdEntry 4 } 2026 scsiDscLunIdValue OBJECT-TYPE 2027 SYNTAX ScsiIdValue 2028 MAX-ACCESS read-only 2029 STATUS current 2030 DESCRIPTION 2031 "This object represents the actual value of this identifier. 2032 The format is defined by the objects scsiDscLunIdCodeSet, 2033 scsiDscLunIdAssociation, scsiDscLunIdType. 2034 The value is represented in the same format as is contained in 2035 the identifier's Identification Descriptor within the Logical 2036 Unit's Device Identification Page." 2037 REFERENCE 2038 "ANSI - SCSI Primary Commands - 2 (SPC-2), 2039 ANSI INCITS 351-2001, 11 July 2001 Chapter 8: section 8.4.4, 2040 Vital Product Data Parameters [SPC2]" 2041 ::= { scsiDscLunIdEntry 5 } 2043 --***** Table of SCSI Target Device Attached to local SCSI 2044 --***** Initiator Ports 2045 scsiAttTgtPortTable OBJECT-TYPE 2046 SYNTAX SEQUENCE OF ScsiAttTgtPortEntry 2047 MAX-ACCESS not-accessible 2048 STATUS current 2049 DESCRIPTION 2050 "This table includes all the remote (not in the local system) 2051 SCSI target ports that are currently attached to each local 2052 SCSI initiator port of this SCSI instance." 2053 ::= { scsiRemoteTgtDev 4 } 2055 scsiAttTgtPortEntry OBJECT-TYPE 2056 SYNTAX ScsiAttTgtPortEntry 2057 MAX-ACCESS not-accessible 2058 STATUS current 2059 DESCRIPTION 2060 "An entry (row) represents a remote SCSI target port 2061 (scsiAttTgtPortIndex) currently attached to a particular 2062 SCSI initiator port (scsiPortIndex) of a particular SCSI 2063 initiator device within a particular SCSI instance." 2064 INDEX { scsiInstIndex, scsiDeviceIndex, scsiPortIndex, 2065 scsiAttTgtPortIndex } 2067 ::= { scsiAttTgtPortTable 1 } 2069 ScsiAttTgtPortEntry ::= SEQUENCE { 2070 scsiAttTgtPortIndex ScsiIndexValue, 2071 scsiAttTgtPortDscTgtIdx ScsiIndexValueOrZero, 2072 scsiAttTgtPortName ScsiName, 2073 scsiAttTgtPortIdentifier ScsiIdentifier 2074 } 2076 scsiAttTgtPortIndex OBJECT-TYPE 2077 SYNTAX ScsiIndexValue 2078 MAX-ACCESS not-accessible 2079 STATUS current 2080 DESCRIPTION 2081 "An arbitrary integer used to uniquely identify a particular 2082 SCSI target currently attached to a particular SCSI initiator 2083 port of a particular SCSI initiator device within a particular 2084 SCSI instance." 2085 ::= { scsiAttTgtPortEntry 1 } 2087 scsiAttTgtPortDscTgtIdx OBJECT-TYPE 2088 SYNTAX ScsiIndexValueOrZero 2089 MAX-ACCESS read-only 2090 STATUS current 2091 DESCRIPTION 2092 "This object contains the value of the scsiDscTgtIntrPortIndex 2093 index variable for the row in the scsiDscTgtTable representing 2094 this currently attached SCSI target port. If the currently 2095 attached SCSI target port is not represented in the 2096 scsiDscTgtTable, then the value of this object is zero." 2097 ::= { scsiAttTgtPortEntry 2 } 2099 scsiAttTgtPortName OBJECT-TYPE 2100 SYNTAX ScsiName 2101 MAX-ACCESS read-only 2102 STATUS current 2103 DESCRIPTION 2104 "This object contains the name of the attached SCSI target 2105 port." 2106 ::= { scsiAttTgtPortEntry 3 } 2108 scsiAttTgtPortIdentifier OBJECT-TYPE 2109 SYNTAX ScsiIdentifier 2110 MAX-ACCESS read-only 2111 STATUS current 2112 DESCRIPTION 2113 "This object contains the identifier of the attached SCSI 2114 target port." 2116 ::= { scsiAttTgtPortEntry 4 } 2118 -- ***************************************************************** 2119 -- ***** Table of SCSI Target devices 2120 -- 2121 scsiTgtDevTable OBJECT-TYPE 2122 SYNTAX SEQUENCE OF ScsiTgtDevEntry 2123 MAX-ACCESS not-accessible 2124 STATUS current 2125 DESCRIPTION 2126 "This table contains information about each local SCSI target 2127 device." 2128 ::= { scsiTargetDevice 1 } 2130 scsiTgtDevEntry OBJECT-TYPE 2131 SYNTAX ScsiTgtDevEntry 2132 MAX-ACCESS not-accessible 2133 STATUS current 2134 DESCRIPTION 2135 "An entry (row) containing information applicable to a 2136 particular local SCSI target device within a particular SCSI 2137 instance." 2138 INDEX { scsiInstIndex, scsiDeviceIndex } 2139 ::= { scsiTgtDevTable 1 } 2141 ScsiTgtDevEntry ::= SEQUENCE { 2142 scsiTgtDevNumberOfLUs Gauge32, 2143 scsiTgtDeviceStatus INTEGER, 2144 scsiTgtDevNonAccessibleLUs Gauge32, 2145 scsiTgtDevResets Counter32 2146 } 2148 scsiTgtDevNumberOfLUs OBJECT-TYPE 2149 SYNTAX Gauge32 2150 MAX-ACCESS read-only 2151 STATUS current 2152 DESCRIPTION 2153 "This object is the number of Logical Units accessible via this 2154 local SCSI target device." 2155 ::= { scsiTgtDevEntry 1 } 2157 scsiTgtDeviceStatus OBJECT-TYPE 2158 SYNTAX INTEGER { 2159 unknown(1), 2160 available(2), 2161 broken(3), 2162 readying(4), 2163 abnormal(5), 2164 nonAddrFailure(6), 2165 nonAddrFailReadying(7), 2166 nonAddrFailAbnormal(8) 2167 } 2168 MAX-ACCESS read-only 2169 STATUS current 2170 DESCRIPTION 2171 "This object represents the status of this SCSI device, 2172 summarizing the state of both the addressable devices (i.e., 2173 the logical units) and the non-addressable devices within this 2174 SCSI device: 2175 - unknown(1): This value is used when the status cannot be 2176 determined 2177 - available(2): All addressable and non-addressable 2178 devices within the SCSI device are fully operational (i.e., 2179 no logical units have an abnormal status). 2180 - broken(3): The SCSI device is not operational and cannot 2181 be made operational without external intervention. 2182 - readying(4): One or more logical units within the SCSI 2183 device are being initialized and access to the SCSI device 2184 is temporarily limited (i.e., one or more of the logical 2185 unit have a readying status). 2186 - abnormal(5): One or more addressable devices within the 2187 SCSI device are indicating a status other than available; 2188 nevertheless, the SCSI device is operational (i.e., one or 2189 more of the logical units have an abnormal status). 2190 - nonAddrFailure(6): One or more non-addressable devices 2191 within the SCSI device have failed; nevertheless, the SCSI 2192 device is operational (i.e., no logical units have an 2193 abnormal or readying status). 2194 - nonAddrFailReadying(7): One or more non-addressable 2195 devices within the SCSI device have failed; nevertheless, 2196 one or more logical units within the SCSI device are being 2197 initialized and access to the SCSI device is temporarily 2198 limited. 2199 - nonAddrFailAbnormal(8): One or more non-addressable 2200 devices within the SCSI device have failed and one or more 2201 addressable devices within the SCSI device are indicating a 2202 status other than available however the SCSI device is 2203 operational. 2204 " 2205 REFERENCE 2206 "SCSI Controller Commands-2 (SCC-2) ANSI INCITS 318-1998 2207 6.3.1.8 REPORT STATES service action [SCC2]" 2208 ::= { scsiTgtDevEntry 2} 2210 scsiTgtDevNonAccessibleLUs OBJECT-TYPE 2211 SYNTAX Gauge32 2212 MAX-ACCESS read-only 2213 STATUS current 2214 DESCRIPTION 2215 "This object is the number of Logical Units existing but not 2216 currently accessible via this local SCSI target device." 2217 ::= { scsiTgtDevEntry 3 } 2219 scsiTgtDevResets OBJECT-TYPE 2220 SYNTAX Counter32 2221 MAX-ACCESS read-only 2222 STATUS current 2223 DESCRIPTION 2224 "This object counts the number of hard reset encountered 2225 by this SCSI target device. 2226 Discontinuities in the value of this counter can occur at re- 2227 initialization of the management system." 2228 REFERENCE 2229 "SCSI Architecture Model-2 (SAM-2), ANSI INCITS 366-2003, 2230 T10 Project 1157-D, 12 September 2002 - Chapter 5.9.7 [SAM2]" 2231 ::= { scsiTgtDevEntry 4 } 2233 --******************** SCSI Target Port Table ********************* 2234 scsiTgtPortTable OBJECT-TYPE 2235 SYNTAX SEQUENCE OF ScsiTgtPortEntry 2236 MAX-ACCESS not-accessible 2237 STATUS current 2238 DESCRIPTION 2239 "This table includes all the local SCSI target ports of all the 2240 local SCSI target devices." 2241 ::= { scsiTargetDevice 2 } 2243 scsiTgtPortEntry OBJECT-TYPE 2244 SYNTAX ScsiTgtPortEntry 2245 MAX-ACCESS not-accessible 2246 STATUS current 2247 DESCRIPTION 2248 "An entry (row) containing information applicable to a 2249 particular local SCSI target port of a particular local SCSI 2250 target device within a particular SCSI instance. " 2251 INDEX { scsiInstIndex, scsiDeviceIndex, scsiPortIndex} 2252 ::= { scsiTgtPortTable 1 } 2254 ScsiTgtPortEntry ::= SEQUENCE { 2255 scsiTgtPortName ScsiName, 2256 scsiTgtPortIdentifier ScsiIdentifier, 2257 scsiTgtPortInCommands Counter32, 2258 scsiTgtPortWrittenMegaBytes Counter32, 2259 scsiTgtPortReadMegaBytes Counter32, 2260 scsiTgtPortHSInCommands Counter64 2261 } 2263 scsiTgtPortName OBJECT-TYPE 2264 SYNTAX ScsiName 2265 MAX-ACCESS read-only 2266 STATUS current 2267 DESCRIPTION 2268 "This object represents the name of the port assigned for use 2269 in the SCSI protocol." 2270 ::= { scsiTgtPortEntry 1 } 2272 scsiTgtPortIdentifier OBJECT-TYPE 2273 SYNTAX ScsiIdentifier 2274 MAX-ACCESS read-only 2275 STATUS current 2276 DESCRIPTION 2277 "This object represents the identifier of the port in one of 2278 the format(s) appropriate for the type of transport." 2279 ::= { scsiTgtPortEntry 2 } 2281 scsiTgtPortInCommands OBJECT-TYPE 2282 SYNTAX Counter32 2283 UNITS "commands" 2284 MAX-ACCESS read-only 2285 STATUS current 2286 DESCRIPTION 2287 "This object represents the number of commands received by this 2288 SCSI target port. 2289 Discontinuities in the value of this counter can occur at re- 2290 initialization of the management system." 2291 ::= { scsiTgtPortEntry 3 } 2293 scsiTgtPortWrittenMegaBytes OBJECT-TYPE 2294 SYNTAX Counter32 2295 UNITS "Megabytes" 2296 MAX-ACCESS read-only 2297 STATUS current 2298 DESCRIPTION 2299 "This object represents the amount of data written in Megabytes 2300 by this SCSI target port. 2301 Discontinuities in the value of this counter can occur at re- 2302 initialization of the management system." 2303 ::= { scsiTgtPortEntry 4 } 2305 scsiTgtPortReadMegaBytes OBJECT-TYPE 2306 SYNTAX Counter32 2307 UNITS "Megabytes" 2308 MAX-ACCESS read-only 2309 STATUS current 2310 DESCRIPTION 2311 "This object represents the amount of data read in Megabytes by 2312 this SCSI target port. 2313 Discontinuities in the value of this counter can occur at re- 2314 initialization of the management system." 2315 ::= { scsiTgtPortEntry 5 } 2317 scsiTgtPortHSInCommands OBJECT-TYPE 2318 SYNTAX Counter64 2319 UNITS "commands" 2320 MAX-ACCESS read-only 2321 STATUS current 2322 DESCRIPTION 2323 "This object represents the number of commands received. This 2324 object provides support for systems that can quickly generate a 2325 large number of commands because they run at high speed. 2326 Discontinuities in the value of this counter can occur at re- 2327 initialization of the management system." 2328 ::= { scsiTgtPortEntry 6 } 2330 scsiRemoteIntrDev OBJECT IDENTIFIER ::= { scsiTargetDevice 3 } 2332 -- The scsiAuthorizedIntrTable contains the list of remote initiator 2333 -- ports that are authorized to be attached to specific SCSI target 2334 -- ports and on which an administrator would like to keep permanent 2335 -- information and long term statistics even when not currently 2336 -- attached. 2338 scsiAuthorizedIntrTable OBJECT-TYPE 2339 SYNTAX SEQUENCE OF ScsiAuthorizedIntrEntry 2340 MAX-ACCESS not-accessible 2341 STATUS current 2342 DESCRIPTION 2343 "This table includes all the authorized SCSI initiator devices 2344 or ports that may attach a SCSI target device 2345 (ScsiAuthIntrTgtPortIndex = 0) or port (ScsiAuthIntrTgtPortIndex 2346 different than 0) of the local SCSI instance. Statistics are 2347 kept for each such authorization; thus, the authorizations 2348 should be configured in the manner, which will cause the desired 2349 set of statistics to be collected and that will determine the 2350 correct LUN map." 2351 ::= { scsiRemoteIntrDev 1 } 2353 scsiAuthorizedIntrEntry OBJECT-TYPE 2354 SYNTAX ScsiAuthorizedIntrEntry 2355 MAX-ACCESS not-accessible 2356 STATUS current 2357 DESCRIPTION 2358 "An entry (row) represents a remote SCSI initiator port or 2359 remote SCSI initiator device that may attach to the local SCSI 2360 target port or device within a particular SCSI instance. 2361 The StorageType of a row in this table is specified by the 2362 instance of scsiInstStorageType which is INDEX-ed by the same 2363 value of scsiInstIndex." 2364 INDEX { scsiInstIndex, scsiDeviceIndex, scsiAuthIntrTgtPortIndex, 2365 scsiAuthIntrIndex } 2366 ::= { scsiAuthorizedIntrTable 1 } 2368 ScsiAuthorizedIntrEntry ::= SEQUENCE { 2369 scsiAuthIntrTgtPortIndex ScsiPortIndexValueOrZero, 2370 scsiAuthIntrIndex ScsiIndexValue, 2371 scsiAuthIntrDevOrPort ScsiDeviceOrPort, 2372 scsiAuthIntrName ScsiName, 2373 scsiAuthIntrLunMapIndex ScsiIndexValueOrZero, 2374 scsiAuthIntrAttachedTimes Counter32, 2375 scsiAuthIntrOutCommands Counter32, 2376 scsiAuthIntrReadMegaBytes Counter32, 2377 scsiAuthIntrWrittenMegaBytes Counter32, 2378 scsiAuthIntrHSOutCommands Counter64, 2379 scsiAuthIntrLastCreation TimeStamp, 2380 scsiAuthIntrRowStatus RowStatus 2381 } 2383 scsiAuthIntrTgtPortIndex OBJECT-TYPE 2384 SYNTAX ScsiPortIndexValueOrZero 2385 MAX-ACCESS not-accessible 2386 STATUS current 2387 DESCRIPTION 2388 "This object contains either the index of the port, or zero to 2389 indicate any port, on the particular local SCSI target device." 2390 ::= { scsiAuthorizedIntrEntry 1 } 2392 scsiAuthIntrIndex OBJECT-TYPE 2393 SYNTAX ScsiIndexValue 2394 MAX-ACCESS not-accessible 2395 STATUS current 2396 DESCRIPTION 2397 "This object is an arbitrary integer used to uniquely identify 2398 a SCSI initiator device or port which is authorized to attach 2399 to a particular local SCSI target device or port of a particular 2400 SCSI instance." 2401 ::= { scsiAuthorizedIntrEntry 2 } 2402 scsiAuthIntrDevOrPort OBJECT-TYPE 2403 SYNTAX ScsiDeviceOrPort 2404 MAX-ACCESS read-create 2405 STATUS current 2406 DESCRIPTION 2407 "This object specifies whether this entry refers to a remote 2408 SCSI initiator port or to a SCSI initiator device. 2409 A value of device(1) means that the authorized remote initiator 2410 is a SCSI initiator device and includes all of its ports. 2411 A value of port(2) means that the authorized remote initiator 2412 is a SCSI initiator port." 2413 ::= { scsiAuthorizedIntrEntry 3 } 2415 scsiAuthIntrName OBJECT-TYPE 2416 SYNTAX ScsiName 2417 MAX-ACCESS read-create 2418 STATUS current 2419 DESCRIPTION 2420 "This object represents the name of the remote SCSI initiator 2421 device or port authorized by this row." 2422 ::= { scsiAuthorizedIntrEntry 4 } 2424 scsiAuthIntrLunMapIndex OBJECT-TYPE 2425 SYNTAX ScsiIndexValueOrZero 2426 MAX-ACCESS read-create 2427 STATUS current 2428 DESCRIPTION 2429 "This object identifies the set of entries in the 2430 scsiLunMapTable for which scsiLunMapIndex has the same value as 2431 the value of this object. The identified set of entries 2432 constitute the LUN map to be used for accessing logical units 2433 when the remote SCSI initiator port or device corresponding to 2434 this entry is attached to any local SCSI target port or device 2435 corresponding to this entry. 2436 Note that this object has a value of zero if this entry should 2437 use the default LUN map." 2438 ::= { scsiAuthorizedIntrEntry 5 } 2440 scsiAuthIntrAttachedTimes OBJECT-TYPE 2441 SYNTAX Counter32 2442 UNITS "Times" 2443 MAX-ACCESS read-only 2444 STATUS current 2445 DESCRIPTION 2446 "This object indicates the number of times that this remote 2447 SCSI initiator device or port has transitioned from unattached 2448 to attached to this local SCSI target device or port. 2449 Discontinuities in the value of this counter can occur at re- 2450 initialization of the management system, and at other times as 2451 indicated by the value of scsiAuthIntrLastCreation." 2452 ::= { scsiAuthorizedIntrEntry 6 } 2454 scsiAuthIntrOutCommands OBJECT-TYPE 2455 SYNTAX Counter32 2456 UNITS "commands" 2457 MAX-ACCESS read-only 2458 STATUS current 2459 DESCRIPTION 2460 "This object indicates the number of commands that the remote 2461 SCSI initiator device or port corresponding to this entry has 2462 sent to the local SCSI target device or port corresponding to 2463 this entry. 2464 Discontinuities in the value of this counter can occur at re- 2465 initialization of the management system, and at other times as 2466 indicated by the value of scsiAuthIntrLastCreation." 2467 ::= { scsiAuthorizedIntrEntry 7 } 2469 scsiAuthIntrReadMegaBytes OBJECT-TYPE 2470 SYNTAX Counter32 2471 UNITS "Megabytes" 2472 MAX-ACCESS read-only 2473 STATUS current 2474 DESCRIPTION 2475 "This object indicates the amount of data in Megabytes that 2476 the remote SCSI initiator device or port corresponding to this 2477 entry has read from the local SCSI target device or port 2478 corresponding to this entry. 2479 Discontinuities in the value of this counter can occur at re- 2480 initialization of the management system, and at other times as 2481 indicated by the value of scsiAuthIntrLastCreation." 2482 ::= { scsiAuthorizedIntrEntry 8 } 2484 scsiAuthIntrWrittenMegaBytes OBJECT-TYPE 2485 SYNTAX Counter32 2486 UNITS "Megabytes" 2487 MAX-ACCESS read-only 2488 STATUS current 2489 DESCRIPTION 2490 "This object indicates the amount of data in Megabytes that the 2491 remote SCSI initiator device or port corresponding to this 2492 entry has written to the local SCSI target device or port 2493 corresponding to this entry. 2494 Discontinuities in the value of this counter can occur at re- 2495 initialization of the management system, and at other times as 2496 indicated by the value of scsiAuthIntrLastCreation." 2497 ::= { scsiAuthorizedIntrEntry 9} 2498 scsiAuthIntrHSOutCommands OBJECT-TYPE 2499 SYNTAX Counter64 2500 UNITS "commands" 2501 MAX-ACCESS read-only 2502 STATUS current 2503 DESCRIPTION 2504 "This object represents the number of commands sent by the 2505 remote SCSI initiator device or port corresponding to this 2506 entry to the local SCSI target device or port corresponding to 2507 this entry. This object provides support for systems, which can 2508 quickly generate a large number of commands because they run at 2509 high speed. 2510 Discontinuities in the value of this counter can occur at re- 2511 initialization of the management system, and at other times as 2512 indicated by the value of scsiAuthIntrLastCreation." 2513 ::= { scsiAuthorizedIntrEntry 10 } 2515 scsiAuthIntrLastCreation OBJECT-TYPE 2516 SYNTAX TimeStamp 2517 MAX-ACCESS read-only 2518 STATUS current 2519 DESCRIPTION 2520 "This object indicates the value of sysUpTime when this row was 2521 last created." 2522 ::= { scsiAuthorizedIntrEntry 11 } 2524 scsiAuthIntrRowStatus OBJECT-TYPE 2525 SYNTAX RowStatus 2526 MAX-ACCESS read-create 2527 STATUS current 2528 DESCRIPTION 2529 "This object allows an administrator to create or delete this 2530 entry. 2531 A newly created row cannot be made active until a value has 2532 been set for scsiAuthIntrName. In this case, the value of the 2533 corresponding instance of the scsiAuthIntrRowStatus column will 2534 stay 'notReady'. 2535 The RowStatus TC [RFC2579] requires that this DESCRIPTION 2536 clause states under which circumstances other objects in this 2537 row can be modified: 2538 The value of this object has no effect on whether other objects 2539 in this conceptual row can be modified. " 2540 ::= { scsiAuthorizedIntrEntry 12 } 2542 -- Table of SCSI initiator devices or ports attached to local 2543 -- SCSI target ports 2544 -- 2545 scsiAttIntrPortTable OBJECT-TYPE 2546 SYNTAX SEQUENCE OF ScsiAttIntrPortEntry 2547 MAX-ACCESS not-accessible 2548 STATUS current 2549 DESCRIPTION 2550 "This table includes all the remote SCSI initiator ports that 2551 are currently attached to a local SCSI target port of all local 2552 devices within all SCSI instances." 2553 ::= { scsiRemoteIntrDev 2 } 2555 scsiAttIntrPortEntry OBJECT-TYPE 2556 SYNTAX ScsiAttIntrPortEntry 2557 MAX-ACCESS not-accessible 2558 STATUS current 2559 DESCRIPTION 2560 "An entry (row) represents a remote SCSI initiator port 2561 currently attached to a particular local SCSI target port of a 2562 particular SCSI target device of a particular SCSI instance." 2563 INDEX { scsiInstIndex, scsiDeviceIndex, scsiPortIndex, 2564 scsiAttIntrPortIndex } 2565 ::= { scsiAttIntrPortTable 1 } 2567 ScsiAttIntrPortEntry ::= SEQUENCE { 2568 scsiAttIntrPortIndex ScsiIndexValue, 2569 scsiAttIntrPortAuthIntrIdx ScsiIndexValueOrZero, 2570 scsiAttIntrPortName ScsiName, 2571 scsiAttIntrPortIdentifier ScsiIdentifier 2572 } 2574 scsiAttIntrPortIndex OBJECT-TYPE 2575 SYNTAX ScsiIndexValue 2576 MAX-ACCESS not-accessible 2577 STATUS current 2578 DESCRIPTION 2579 "This object represents an arbitrary integer used to uniquely 2580 identify a particular attached remote initiator port to a 2581 particular SCSI target port within a particular SCSI target 2582 device within a particular SCSI instance." 2583 ::= { scsiAttIntrPortEntry 1 } 2585 scsiAttIntrPortAuthIntrIdx OBJECT-TYPE 2586 SYNTAX ScsiIndexValueOrZero 2587 MAX-ACCESS read-only 2588 STATUS current 2589 DESCRIPTION 2590 "This object is the corresponding index in the 2591 scsiAuthorizedIntrTable for this current attached remote 2592 SCSI initiator device or zero if this remote attached SCSI 2593 initiator device is not configured in that table." 2594 ::= { scsiAttIntrPortEntry 2 } 2596 scsiAttIntrPortName OBJECT-TYPE 2597 SYNTAX ScsiName 2598 MAX-ACCESS read-only 2599 STATUS current 2600 DESCRIPTION 2601 "This object represents the name of the remote SCSI initiator 2602 device attached to this local SCSI target port." 2603 ::= { scsiAttIntrPortEntry 3 } 2605 scsiAttIntrPortIdentifier OBJECT-TYPE 2606 SYNTAX ScsiIdentifier 2607 MAX-ACCESS read-only 2608 STATUS current 2609 DESCRIPTION 2610 "This object represents the identifier of the remote SCSI 2611 initiator device attached to this local SCSI target port." 2612 ::= { scsiAttIntrPortEntry 4 } 2614 --****************** Managed Objects regarding logical units ******* 2615 scsiLuTable OBJECT-TYPE 2616 SYNTAX SEQUENCE OF ScsiLuEntry 2617 MAX-ACCESS not-accessible 2618 STATUS current 2619 DESCRIPTION 2620 "This table contains the logical units exposed by local SCSI 2621 target devices. 2622 It includes attributes for the WWN, scsiLuVendorId, 2623 scsiLuProductId, and scsiLuRevisionId, which may also appear in 2624 the scsiLuIdTable. If an implementation exposes a WWN as a 2625 LuIdTable entry, it must match the scsiLuWwnName in this table. 2626 If an implementation exposes a (vendor, product, revision) 2627 identifier as an LuIdTable entry, each of these fields must 2628 match the scsiLuVendorId, scsiLuProductId, and scsiLuRevisionId 2629 attributes in this table." 2630 ::= { scsiLogicalUnit 1 } 2632 scsiLuEntry OBJECT-TYPE 2633 SYNTAX ScsiLuEntry 2634 MAX-ACCESS not-accessible 2635 STATUS current 2636 DESCRIPTION 2637 "An entry (row) contains information applicable to a particular 2638 logical unit of a particular local SCSI target device within a 2639 particular SCSI instance. " 2640 INDEX { scsiInstIndex, scsiDeviceIndex, scsiLuIndex} 2642 ::= { scsiLuTable 1 } 2644 ScsiLuEntry ::= SEQUENCE { 2645 scsiLuIndex ScsiIndexValue, 2646 scsiLuDefaultLun ScsiLUN, 2647 scsiLuWwnName ScsiLuNameOrZero, 2648 scsiLuVendorId SnmpAdminString, 2649 scsiLuProductId SnmpAdminString, 2650 scsiLuRevisionId SnmpAdminString, 2651 scsiLuPeripheralType Unsigned32, 2652 scsiLuStatus INTEGER, 2653 scsiLuState BITS, 2654 scsiLuInCommands Counter32, 2655 scsiLuReadMegaBytes Counter32, 2656 scsiLuWrittenMegaBytes Counter32, 2657 scsiLuInResets Counter32, 2658 scsiLuOutTaskSetFullStatus Counter32, 2659 scsiLuHSInCommands Counter64, 2660 scsiLuLastCreation TimeStamp 2661 } 2663 scsiLuIndex OBJECT-TYPE 2664 SYNTAX ScsiIndexValue 2665 MAX-ACCESS not-accessible 2666 STATUS current 2667 DESCRIPTION 2668 "This object represents an arbitrary integer used to uniquely 2669 identify a particular logical unit within a particular SCSI 2670 target device within a particular SCSI instance." 2671 ::= { scsiLuEntry 1 } 2673 scsiLuDefaultLun OBJECT-TYPE 2674 SYNTAX ScsiLUN 2675 MAX-ACCESS read-only 2676 STATUS current 2677 DESCRIPTION 2678 "This object represents the default Logical Unit Number (LUN) 2679 for this logical unit; if a SCSI initiator device has not been 2680 configured to view this Logical Unit via an entry in the 2681 ScsiLunMapTable, the LU will be visible as scsiLuDefaultLun. 2682 If this Logical Unit does not have a default LUN, it will only 2683 be visible if specified via the ScsiLunMapTable, and this 2684 object will contain a zero-length string." 2685 ::= { scsiLuEntry 2 } 2687 scsiLuWwnName OBJECT-TYPE 2688 SYNTAX ScsiLuNameOrZero 2689 MAX-ACCESS read-only 2690 STATUS current 2691 DESCRIPTION 2692 "This object represents the World-Wide Name of this LU that is 2693 the device identifier of the VPD page name; if there is no WWN 2694 for this LU, this object will contain a zero-length string. 2695 If there is more than one identifier, they will be listed in 2696 the scsiLuIdTable and this object will contain a 2697 zero-length string. " 2698 ::= { scsiLuEntry 3 } 2700 scsiLuVendorId OBJECT-TYPE 2701 SYNTAX SnmpAdminString 2702 MAX-ACCESS read-only 2703 STATUS current 2704 DESCRIPTION 2705 "This object represents a string identifying the vendor of this 2706 LU as reported in the Standard INQUIRY data." 2707 ::= { scsiLuEntry 4 } 2709 scsiLuProductId OBJECT-TYPE 2710 SYNTAX SnmpAdminString 2711 MAX-ACCESS read-only 2712 STATUS current 2713 DESCRIPTION 2714 "This object represents a string identifying the product for 2715 this LU as reported in the Standard INQUIRY data." 2716 ::= { scsiLuEntry 5 } 2718 scsiLuRevisionId OBJECT-TYPE 2719 SYNTAX SnmpAdminString 2720 MAX-ACCESS read-only 2721 STATUS current 2722 DESCRIPTION 2723 "This object represents a string defining the product revision 2724 of this LU as reported in the Standard INQUIRY data." 2725 ::= { scsiLuEntry 6 } 2727 scsiLuPeripheralType OBJECT-TYPE 2728 SYNTAX Unsigned32 2729 MAX-ACCESS read-only 2730 STATUS current 2731 DESCRIPTION 2732 "This object is the value returned by SCSI Standard INQUIRY 2733 data. It can be: direct-access device, sequential-access 2734 device, printer, communication device and so on. 2735 The values that can be returned here are defined in SCSI 2736 Primary Commands -2." 2737 REFERENCE 2738 "ANSI - SCSI Primary Commands - 2 (SPC-2), 2739 ANSI INCITS 351-2001,11 July 2001 [SPC2]- Table 48." 2740 ::= { scsiLuEntry 7 } 2742 scsiLuStatus OBJECT-TYPE 2743 SYNTAX INTEGER { 2744 unknown(1), 2745 available(2), 2746 notAvailable(3), 2747 broken(4), 2748 readying(5), 2749 abnormal(6) 2750 } 2751 MAX-ACCESS read-only 2752 STATUS current 2753 DESCRIPTION 2754 "This object represents the status of this logical unit: 2755 - unknown(1): The status of this logical unit cannot be 2756 determined. 2757 - available(2): The logical unit is fully operational (i.e., 2758 accepts media access SCSI commands and has no state 2759 information to report). 2760 - notAvailable(3): The logical unit is capable of being 2761 supported but not available (i.e., no logical unit is 2762 currently present or the logical unit is present but not 2763 configured for use). 2764 - broken(4): The logical unit has failed and cannot respond 2765 to SCSI commands. 2766 - readying(5): The logical unit is being initialized and 2767 access is temporarily limited. 2768 - abnormal(6): The logical unit has state information 2769 available that indicates it is operating with limits. The 2770 scsiLuState indicates what those limits are. 2771 " 2772 REFERENCE 2773 "SCSI Controller Commands-2 (SCC-2) ANSI INCITS 318-1998 2774 6.3.1.8 REPORT STATES service action [SCC2]" 2775 ::= { scsiLuEntry 8 } 2777 scsiLuState OBJECT-TYPE 2778 SYNTAX BITS { 2779 dataLost(0), 2780 dynamicReconfigurationInProgress(1), 2781 exposed(2), 2782 fractionallyExposed(3), 2783 partiallyExposed(4), 2784 protectedRebuild(5), 2785 protectionDisabled(6), 2786 rebuild(7), 2787 recalculate(8), 2788 spareInUse(9), 2789 verifyInProgress(10) 2790 } 2791 MAX-ACCESS read-only 2792 STATUS current 2793 DESCRIPTION 2794 "This object represents the state of a logical unit and its 2795 meaning is according the bit position: 2796 0 Data lost: Within the logical unit data has been lost. 2797 1 Dynamic reconfiguration in progress: The logical unit is 2798 being reconfigured. In this state all data is still 2799 protected. 2800 2 Exposed: Within the logical unit data is not protected. 2801 In this state all data is still valid, however, loss 2802 of data/data-availability is unavoidable in the event 2803 of a failure. 2804 3 Fractionally exposed: Within the logical unit part of 2805 the data is not protected. In this state all data is 2806 still valid, however, a failure may cause a loss of 2807 data or a loss of data availability. 2808 4 Partially exposed: Within the logical unit one or more 2809 underlying storage devices have failed. In this state 2810 all data is still protected. 2811 5 Protected rebuild: The logical unit is in the process of 2812 a rebuild operation. In this state all data is 2813 protected. 2814 6 Protection disabled: Within the logical unit the data 2815 protection method has been disabled. 2816 In this state all data is still valid, however, 2817 however,loss of data/data-availability is unavoidable 2818 in the event of a failure. 2819 7 Rebuild: The data protection method is in the process of 2820 rebuilding data. In this state data is not protected. 2821 8 Recalculate: The logical unit is in the process of a 2822 recalculate operation. 2823 9 Spare in use: Within the logical unit a storage device 2824 in full or part being used to store data. In this 2825 state all data is still protected. 2826 10 Verify in progress: Within the logical unit data is 2827 being verified." 2828 REFERENCE 2829 "SCSI Controller Commands-2 (SCC-2) ANSI INCITS 318-1998 2830 6.3.1.8 REPORT STATES service action [SCC2]" 2831 ::= { scsiLuEntry 9 } 2833 scsiLuInCommands OBJECT-TYPE 2834 SYNTAX Counter32 2835 UNITS "commands" 2836 MAX-ACCESS read-only 2837 STATUS current 2838 DESCRIPTION 2839 "This object represents the number of commands received by this 2840 logical unit. 2841 Discontinuities in the value of this counter can occur at re- 2842 initialization of the management system, and at other times as 2843 indicated by the value of scsiLuLastCreation." 2844 ::= { scsiLuEntry 10 } 2846 scsiLuReadMegaBytes OBJECT-TYPE 2847 SYNTAX Counter32 2848 UNITS "Megabytes" 2849 MAX-ACCESS read-only 2850 STATUS current 2851 DESCRIPTION 2852 "This object represents the amount of data in Megabytes read 2853 from this logical unit. 2854 Discontinuities in the value of this counter can occur at re- 2855 initialization of the management system, and at other times as 2856 indicated by the value of scsiLuLastCreation." 2857 ::= { scsiLuEntry 11 } 2859 scsiLuWrittenMegaBytes OBJECT-TYPE 2860 SYNTAX Counter32 2861 UNITS "Megabytes" 2862 MAX-ACCESS read-only 2863 STATUS current 2864 DESCRIPTION 2865 "This object represents the amount of data in Megabytes written 2866 to this logical unit. 2867 Discontinuities in the value of this counter can occur at re- 2868 initialization of the management system, and at other times as 2869 indicated by the value of scsiLuLastCreation." 2870 ::= { scsiLuEntry 12 } 2872 scsiLuInResets OBJECT-TYPE 2873 SYNTAX Counter32 2874 UNITS "resets" 2875 MAX-ACCESS read-only 2876 STATUS current 2877 DESCRIPTION 2878 "This object represents the number of times that this logical 2879 unit received: 2880 - a LOGICAL UNIT RESET or TARGET RESET task management request, 2881 or 2882 - any other SCSI transport protocol-specific action or event 2883 that causes a Logical Unit Reset or a Hard Reset at a SCSI 2884 target port of the containing device 2885 ([SAM2] Chapters 5.9.6, 5.9.7). 2886 Discontinuities in the value of this counter can occur at re- 2887 initialization of the management system, and at other times as 2888 indicated by the value of scsiLuLastCreation." 2889 REFERENCE 2890 "SCSI Architecture Model-2 (SAM-2), ANSI INCITS 366-2003, 2891 T10 Project 1157-D, 12 September 2002 - Chapter 5.9.7 [SAM2]" 2892 ::= { scsiLuEntry 13 } 2894 scsiLuOutTaskSetFullStatus OBJECT-TYPE 2895 SYNTAX Counter32 2896 MAX-ACCESS read-only 2897 STATUS current 2898 DESCRIPTION 2899 "This object represents the number of Task Set full statuses 2900 issued for this logical unit. 2901 Discontinuities in the value of this counter can occur at re- 2902 initialization of the management system, and at other times as 2903 indicated by the value of scsiLuLastCreation." 2904 ::= { scsiLuEntry 14 } 2906 scsiLuHSInCommands OBJECT-TYPE 2907 SYNTAX Counter64 2908 UNITS "commands" 2909 MAX-ACCESS read-only 2910 STATUS current 2911 DESCRIPTION 2912 "This object represents the number of commands received by this 2913 logical unit. This object provides support for systems that can 2914 quickly generate a large number of commands because they run at 2915 high speed. 2916 Discontinuities in the value of this counter can occur at re- 2917 initialization of the management system, and at other times as 2918 indicated by the value of scsiLuLastCreation." 2919 ::= { scsiLuEntry 15 } 2921 scsiLuLastCreation OBJECT-TYPE 2922 SYNTAX TimeStamp 2923 MAX-ACCESS read-only 2924 STATUS current 2925 DESCRIPTION 2926 "This object indicates the value of sysUpTime when this row was 2927 last created." 2928 ::= { scsiLuEntry 16 } 2929 --****************** Logical Unit Identifier Table ***************** 2930 scsiLuIdTable OBJECT-TYPE 2931 SYNTAX SEQUENCE OF ScsiLuIdEntry 2932 MAX-ACCESS not-accessible 2933 STATUS current 2934 DESCRIPTION 2935 "A table of identifiers for all logical units exposed by local 2936 SCSI target device." 2937 ::= { scsiLogicalUnit 2 } 2939 scsiLuIdEntry OBJECT-TYPE 2940 SYNTAX ScsiLuIdEntry 2941 MAX-ACCESS not-accessible 2942 STATUS current 2943 DESCRIPTION 2944 "An entry (row) containing information applicable to a 2945 particular identifier for a particular logical unit of a 2946 particular SCSI target device within a particular SCSI 2947 instance. " 2948 INDEX {scsiInstIndex, scsiDeviceIndex, scsiLuIndex, scsiLuIdIndex} 2949 ::= { scsiLuIdTable 1 } 2951 ScsiLuIdEntry ::= SEQUENCE { 2952 scsiLuIdIndex ScsiIndexValue, 2953 scsiLuIdCodeSet ScsiIdCodeSet, 2954 scsiLuIdAssociation ScsiIdAssociation, 2955 scsiLuIdType ScsiIdType, 2956 scsiLuIdValue ScsiIdValue 2957 } 2959 scsiLuIdIndex OBJECT-TYPE 2960 SYNTAX ScsiIndexValue 2961 MAX-ACCESS not-accessible 2962 STATUS current 2963 DESCRIPTION 2964 "This object represents an arbitrary integer used to uniquely 2965 identify a particular LU Identifier within a particular logical 2966 unit within a particular SCSI target device within a particular 2967 SCSI instance." 2968 ::= { scsiLuIdEntry 1 } 2970 scsiLuIdCodeSet OBJECT-TYPE 2971 SYNTAX ScsiIdCodeSet 2972 MAX-ACCESS read-only 2973 STATUS current 2974 DESCRIPTION 2975 "This object specifies the code set in use with this 2976 identifier. The value is represented in the same format as is 2977 contained in the identifier's Identification Descriptor within 2978 the Logical Unit's Device Identification Page." 2979 REFERENCE 2980 "ANSI - SCSI Primary Commands - 2 (SPC-2), 2981 ANSI INCITS 351-2001, 11 July 2001 Chapter 8: section 8.4.4, 2982 Vital Product Data Parameters [SPC2]" 2983 ::= { scsiLuIdEntry 2 } 2985 scsiLuIdAssociation OBJECT-TYPE 2986 SYNTAX ScsiIdAssociation 2987 MAX-ACCESS read-only 2988 STATUS current 2989 DESCRIPTION 2990 "This object specifies what the identifier is associated with 2991 (e.g, with the addressed physical/logical device or with a 2992 particular port). The value is represented in the same format 2993 as is contained in the identifier's Identification Descriptor 2994 within the Logical Unit's Device Identification Page." 2995 REFERENCE 2996 "ANSI - SCSI Primary Commands - 2 (SPC-2), 2997 ANSI INCITS 351-2001, 11 July 2001, Chapter 8: section 8.4.4, 2998 Vital Product Data Parameters [SPC2]" 2999 ::= { scsiLuIdEntry 3 } 3001 scsiLuIdType OBJECT-TYPE 3002 SYNTAX ScsiIdType 3003 MAX-ACCESS read-only 3004 STATUS current 3005 DESCRIPTION 3006 "This object specifies the type of the identifier. 3007 The value is represented in the same format as is contained in 3008 the identifier's Identification Descriptor within the Logical 3009 Unit's Device Identification Page." 3010 REFERENCE 3011 "ANSI - SCSI Primary Commands - 2 (SPC-2), 3012 ANSI INCITS 351-2001, 11 July 2001, Chapter 8: section 8.4.4, 3013 Vital Product Data Parameters [SPC2]" 3014 ::= { scsiLuIdEntry 4 } 3016 scsiLuIdValue OBJECT-TYPE 3017 SYNTAX ScsiIdValue 3018 MAX-ACCESS read-only 3019 STATUS current 3020 DESCRIPTION 3021 "This object represents the actual value of this identifier. 3022 The format is defined by the objects scsiLuIdCodeSet, 3023 scsiLuIdAssociation, scsiLuIdType. 3024 The value is represented in the same format as is contained in 3025 the identifier's Identification Descriptor within the Logical 3026 Unit's Device Identification Page." 3027 REFERENCE 3028 "ANSI - SCSI Primary Commands - 2 (SPC-2), 3029 ANSI INCITS 351-2001, 11 July 2001, Chapter 8: section 8.4.4, 3030 Vital Product Data Parameters [SPC2]" 3031 ::= { scsiLuIdEntry 5 } 3033 --******************* The LUN Map Table **************************** 3035 scsiLunMapTable OBJECT-TYPE 3036 SYNTAX SEQUENCE OF ScsiLunMapEntry 3037 MAX-ACCESS not-accessible 3038 STATUS current 3039 DESCRIPTION 3040 "This table provides the ability to present a logical unit 3041 using different Logical Unit Numbers for different SCSI 3042 initiator devices. 3043 This table provides a mapping between a logical unit and a 3044 logical unit number, and can be referenced by a 3045 ScsiAuthorizedIntrEntry to specify the LUN map for that 3046 initiator." 3047 ::= { scsiLogicalUnit 3 } 3049 scsiLunMapEntry OBJECT-TYPE 3050 SYNTAX ScsiLunMapEntry 3051 MAX-ACCESS not-accessible 3052 STATUS current 3053 DESCRIPTION 3054 "An entry containing information about the mapping of a 3055 particular Logical Unit to a particular LUN. The set of 3056 entries which all have the same values of scsiInstIndex, 3057 scsiDeviceIndex and scsiLunMapIndex constitute a LUN Map 3058 within a particular SCSI instance. 3059 The StorageType of a row in this table is specified by 3060 the instance of scsiInstStorageType which is INDEX-ed by 3061 the same value of scsiInstIndex." 3062 INDEX { scsiInstIndex, scsiDeviceIndex, scsiLunMapIndex, 3063 scsiLunMapLun} 3064 ::= { scsiLunMapTable 1 } 3066 ScsiLunMapEntry ::= SEQUENCE { 3067 scsiLunMapIndex ScsiIndexValue, 3068 scsiLunMapLun ScsiLUN, 3069 scsiLunMapLuIndex ScsiIndexValue, 3070 scsiLunMapRowStatus RowStatus 3071 } 3072 scsiLunMapIndex OBJECT-TYPE 3073 SYNTAX ScsiIndexValue 3074 MAX-ACCESS not-accessible 3075 STATUS current 3076 DESCRIPTION 3077 "This object represents an arbitrary integer used to uniquely 3078 identify a particular LunMap within a particular SCSI target 3079 device within a particular SCSI instance." 3080 ::= { scsiLunMapEntry 1 } 3082 scsiLunMapLun OBJECT-TYPE 3083 SYNTAX ScsiLUN 3084 MAX-ACCESS not-accessible 3085 STATUS current 3086 DESCRIPTION 3087 "This object specifies the Logical Unit Number, to which a 3088 logical unit is mapped by this row." 3089 ::= { scsiLunMapEntry 2 } 3091 scsiLunMapLuIndex OBJECT-TYPE 3092 SYNTAX ScsiIndexValue 3093 MAX-ACCESS read-create 3094 STATUS current 3095 DESCRIPTION 3096 "This object identifies the logical unit for which the value of 3097 scsiLuIndex is the same as the value of this object. The 3098 identified logical unit is the one mapped to a LUN by this 3099 row." 3100 ::= { scsiLunMapEntry 3 } 3102 scsiLunMapRowStatus OBJECT-TYPE 3103 SYNTAX RowStatus 3104 MAX-ACCESS read-create 3105 STATUS current 3106 DESCRIPTION 3107 "This object allows an administrator to create and delete this 3108 entry." 3109 ::= { scsiLunMapEntry 4 } 3111 --********************** Notifications ****************************** 3112 -- scsiNotifications OBJECT IDENTIFIER ::= { scsiMIB 2 } 3114 scsiNotificationsPrefix OBJECT IDENTIFIER 3115 ::= { scsiNotifications 0 } 3117 scsiTgtDeviceStatusChanged NOTIFICATION-TYPE 3118 OBJECTS { scsiTgtDeviceStatus } 3119 STATUS current 3120 DESCRIPTION 3121 "This notification will be generated for each occurrence of the 3122 abnormal status (e.g., if the SCSI target device's current 3123 status is abnormal) providing that the SCSI instance's value of 3124 scsiInstScsiNotificationsEnable is enabled. 3125 An SNMP agent implementing the SCSI MIB module should not send 3126 more than three SCSI identical notifications in any 10-second 3127 period." 3128 ::= { scsiNotificationsPrefix 1 } 3130 scsiLuStatusChanged NOTIFICATION-TYPE 3131 OBJECTS { scsiLuStatus } 3132 STATUS current 3133 DESCRIPTION 3134 "This notification will be generated each time that 3135 scsiLuStatus changes providing that the SCSI instance's value 3136 of scsiInstScsiNotificationsEnable is enabled. 3137 An SNMP agent implementing the SCSI MIB module should not send 3138 more than three SCSI identical notifications in any 10-second 3139 period." 3140 ::= { scsiNotificationsPrefix 2 } 3142 --****************************************************************** 3143 -- The next part defines the conformance groups in use 3144 -- for SCSI MIB module. 3145 scsiCompliances OBJECT IDENTIFIER ::= { scsiConformance 1 } 3147 scsiCompliance MODULE-COMPLIANCE 3148 STATUS current 3149 DESCRIPTION 3150 "Describes the requirements for compliance to this SCSI MIB 3151 module. 3152 If an implementation can be both a SCSI target device and a SCSI 3153 initiator device, all groups are mandatory." 3154 MODULE -- this module 3155 MANDATORY-GROUPS { 3156 scsiDeviceGroup 3157 } 3159 OBJECT scsiInstAlias 3160 MIN-ACCESS read-only 3161 DESCRIPTION 3162 "Write access is not mandatory." 3164 OBJECT scsiInstScsiNotificationsEnable 3165 MIN-ACCESS read-only 3166 DESCRIPTION 3167 "Write access is not mandatory." 3169 OBJECT scsiDeviceAlias 3170 MIN-ACCESS read-only 3171 DESCRIPTION 3172 "Write access is not mandatory." 3174 OBJECT scsiInstStorageType 3175 MIN-ACCESS read-only 3176 DESCRIPTION 3177 "Write access is not required." 3179 -- Conditionally mandatory groups to be included with 3180 -- the mandatory groups when the implementation has 3181 -- SCSI target device. 3183 GROUP scsiTargetDeviceGroup 3184 DESCRIPTION 3185 "This group is mandatory for all SCSI implementations that 3186 have SCSI target devices." 3187 GROUP scsiLunMapGroup 3188 DESCRIPTION 3189 "This group is mandatory for system having the capabilities 3190 of mapping local SCSI target devices and logical units 3191 according remote SCSI initiator devices." 3193 OBJECT scsiAuthIntrDevOrPort 3194 MIN-ACCESS read-only 3195 DESCRIPTION 3196 "Write access is not required." 3198 OBJECT scsiAuthIntrName 3199 MIN-ACCESS read-only 3200 DESCRIPTION 3201 "Write access is not required." 3203 OBJECT scsiAuthIntrLunMapIndex 3204 MIN-ACCESS read-only 3205 DESCRIPTION 3206 "Write access is not required." 3208 OBJECT scsiAuthIntrRowStatus 3209 SYNTAX RowStatus { active(1) } 3210 MIN-ACCESS read-only 3211 DESCRIPTION 3212 "Write access is not required, and only one of the six 3213 enumerated values for the RowStatus textual convention need 3214 be supported, specifically: active(1)." 3216 GROUP scsiTgtDevLuNotificationsGroup 3217 DESCRIPTION 3218 "This group is mandatory for all SCSI implementations that 3219 have SCSI target devices and are able to report status 3220 changes." 3222 -- Conditionally mandatory groups to be included with 3223 -- the mandatory groups when the implementation has 3224 -- SCSI initiator device. 3226 GROUP scsiInitiatorDeviceGroup 3227 DESCRIPTION 3228 "This group is mandatory for all SCSI implementations that 3229 have SCSI initiator devices." 3231 OBJECT scsiIntrDevTgtAccessMode 3232 MIN-ACCESS read-only 3233 DESCRIPTION "Write access is not mandatory." 3235 GROUP scsiDiscoveryGroup 3236 DESCRIPTION 3237 "This group is mandatory for system having the capabilities 3238 of discovering remote SCSI target devices via local SCSI 3239 initiator devices." 3241 OBJECT scsiLunMapLuIndex 3242 MIN-ACCESS read-only 3243 DESCRIPTION 3244 "Write access is not mandatory." 3246 OBJECT scsiLunMapRowStatus 3247 SYNTAX RowStatus { active(1) } 3248 MIN-ACCESS read-only 3249 DESCRIPTION 3250 "Write access is not required, and only one of the six 3251 enumerated values for the RowStatus textual convention need 3252 be supported, specifically: active(1)." 3254 OBJECT scsiDscTgtDevOrPort 3255 MIN-ACCESS read-only 3256 DESCRIPTION 3257 "Write access is not mandatory." 3259 OBJECT scsiDscTgtName 3260 MIN-ACCESS read-only 3261 DESCRIPTION "Write access is not mandatory." 3263 OBJECT scsiDscTgtConfigured 3264 SYNTAX TruthValue { false(2) } 3265 MIN-ACCESS read-only 3266 DESCRIPTION 3267 "The value of true(1) is not mandatory neither the write 3268 access." 3270 OBJECT scsiDscTgtRowStatus 3271 SYNTAX RowStatus { active(1) } 3272 MIN-ACCESS read-only 3273 DESCRIPTION 3274 "Write access is not required, and only one of the six 3275 enumerated values for the RowStatus textual convention need 3276 be supported, specifically: active(1)." 3278 -- Conditionally mandatory groups to be included with the mandatory 3279 -- groups when the implementation can gather statistics. 3280 GROUP scsiDeviceStatGroup 3281 DESCRIPTION 3282 "This group is mandatory for all SCSI implementations that 3283 can gather statistics." 3285 -- Conditionally mandatory groups to be included with the mandatory 3286 -- groups when the implementation can gather statistics at the SCSI 3287 -- initiator device side. 3288 GROUP scsiInitiatorDevStatsGroup 3289 DESCRIPTION 3290 "This group is mandatory for all SCSI implementations that 3291 can gather statistics at SCSI initiator device side." 3293 GROUP scsiDiscoveryStatsGroup 3294 DESCRIPTION 3295 "This group is mandatory for system having the capabilities 3296 of gathering statistics regarding remote SCSI target devices 3297 via local SCSI initiator devices." 3299 -- Conditionally mandatory groups to be included with the mandatory 3300 -- groups when the implementation can gather statistics at the SCSI 3301 -- target side. 3302 GROUP scsiTargetDevStatsGroup 3303 DESCRIPTION 3304 "This group is mandatory for all SCSI implementations that 3305 can gather statistics at SCSI target devices." 3307 GROUP scsiLunMapStatsGroup 3308 DESCRIPTION 3309 "This group is mandatory for SCSI implementations able to map 3310 local SCSI target devices and logical units according remote 3311 SCSI initiator devices." 3313 -- Conditionally mandatory groups to be included with the mandatory 3314 -- groups when the implementation is running at high speed and can 3315 -- gather statistics at the SCSI initiator device side. 3316 GROUP scsiInitiatorDevHSStatsGroup 3317 DESCRIPTION 3318 "This group is mandatory for all SCSI implementations that 3319 can gather statistics at SCSI initiator device side and are 3320 running at high speed, meaning speed of 4 Gbit/second or 3321 higher." 3323 GROUP scsiDiscoveryHSStatsGroup 3324 DESCRIPTION 3325 "This group is mandatory for system having the capabilities 3326 of gathering statistics regarding remote SCSI target devices 3327 via local SCSI initiator devices and are running at high 3328 speed, meaning speed of 4 Gbit/second or higher." 3330 -- Conditionally mandatory groups to be included with the mandatory 3331 -- groups when the implementation is running at high speed and can 3332 -- gather statistics at the SCSI target side. 3333 GROUP scsiTargetDevHSStatsGroup 3334 DESCRIPTION 3335 "This group is mandatory for all SCSI implementations that 3336 can gather statistics at SCSI target devices in high speed 3337 system, meaning speed of 4 Gbit/second or higher." 3339 GROUP scsiLunMapHSStatsGroup 3340 DESCRIPTION 3341 "This group is mandatory for SCSI implementations able to map 3342 local SCSI target devices and logical units according remote 3343 SCSI initiator devices in high speed system, meaning speed of 3344 4 Gbit/second or higher." 3345 ::= { scsiCompliances 1 } 3347 scsiGroups OBJECT IDENTIFIER ::= { scsiConformance 2 } 3349 scsiDeviceGroup OBJECT-GROUP 3350 OBJECTS { 3351 scsiInstAlias, 3352 scsiInstSoftwareIndex, 3353 scsiInstVendorVersion, 3354 scsiInstScsiNotificationsEnable, 3355 scsiInstStorageType, 3356 scsiDeviceAlias, 3357 scsiDeviceRole, 3358 scsiDevicePortNumber, 3359 scsiPortRole, 3360 scsiPortTransportPtr, 3361 scsiTransportType, 3362 scsiTransportPointer, 3363 scsiTransportDevName 3364 } 3365 STATUS current 3366 DESCRIPTION 3367 "A collection of objects providing information about SCSI 3368 instances, devices and ports." 3369 ::= { scsiGroups 1 } 3371 scsiInitiatorDeviceGroup OBJECT-GROUP 3372 OBJECTS { 3373 scsiIntrDevTgtAccessMode, 3374 scsiIntrPortName, 3375 scsiIntrPortIdentifier, 3376 scsiAttTgtPortDscTgtIdx, 3377 scsiAttTgtPortName, 3378 scsiAttTgtPortIdentifier 3379 } 3380 STATUS current 3381 DESCRIPTION 3382 "This group is relevant for s SCSI initiator device and port." 3383 ::= { scsiGroups 2 } 3385 scsiDiscoveryGroup OBJECT-GROUP 3386 OBJECTS { 3387 scsiDscTgtDevOrPort, 3388 scsiDscTgtName, 3389 scsiDscTgtConfigured, 3390 scsiDscTgtDiscovered, 3391 scsiDscTgtRowStatus, 3392 scsiDscTgtLastCreation, 3393 scsiDscLunLun, 3394 scsiDscLunIdCodeSet, 3395 scsiDscLunIdAssociation, 3396 scsiDscLunIdType, 3397 scsiDscLunIdValue 3398 } 3399 STATUS current 3400 DESCRIPTION 3401 "This group is relevant for the discovered SCSI target devices 3402 by a SCSI initiator port." 3403 ::= { scsiGroups 3 } 3404 scsiTargetDeviceGroup OBJECT-GROUP 3405 OBJECTS { 3406 scsiTgtDevNumberOfLUs, 3407 scsiTgtDeviceStatus, 3408 scsiTgtDevNonAccessibleLUs, 3409 scsiTgtPortName, 3410 scsiTgtPortIdentifier, 3411 scsiAttIntrPortAuthIntrIdx, 3412 scsiAttIntrPortName, 3413 scsiAttIntrPortIdentifier, 3414 scsiLuDefaultLun, 3415 scsiLuWwnName, 3416 scsiLuVendorId, 3417 scsiLuProductId, 3418 scsiLuRevisionId, 3419 scsiLuPeripheralType, 3420 scsiLuStatus, 3421 scsiLuState, 3422 scsiLuLastCreation, 3423 scsiLuIdCodeSet, 3424 scsiLuIdAssociation, 3425 scsiLuIdType, 3426 scsiLuIdValue 3427 } 3428 STATUS current 3429 DESCRIPTION 3430 "This group is relevant for a SCSI target device and port." 3431 ::= { scsiGroups 4 } 3433 scsiLunMapGroup OBJECT-GROUP 3434 OBJECTS { 3435 scsiLunMapLuIndex, 3436 scsiLunMapRowStatus, 3437 scsiAuthIntrDevOrPort, 3438 scsiAuthIntrName, 3439 scsiAuthIntrLunMapIndex, 3440 scsiAuthIntrLastCreation, 3441 scsiAuthIntrRowStatus 3442 } 3443 STATUS current 3444 DESCRIPTION 3445 "This group is a collection of attributes regarding the mapping 3446 between logical unit number, logical unit and target device." 3447 ::= { scsiGroups 5} 3449 scsiTargetDevStatsGroup OBJECT-GROUP 3450 OBJECTS { 3451 scsiTgtDevResets, 3452 scsiTgtPortInCommands, 3453 scsiTgtPortWrittenMegaBytes, 3454 scsiTgtPortReadMegaBytes, 3455 scsiLuInCommands, 3456 scsiLuReadMegaBytes, 3457 scsiLuWrittenMegaBytes, 3458 scsiLuInResets, 3459 scsiLuOutTaskSetFullStatus 3460 } 3461 STATUS current 3462 DESCRIPTION 3463 "This group is a collection of statistics for all 3464 implementations of the SCSI MIB module that contain SCSI target 3465 devices." 3466 ::= { scsiGroups 6} 3468 scsiTargetDevHSStatsGroup OBJECT-GROUP 3469 OBJECTS { 3470 scsiTgtPortHSInCommands, 3471 scsiLuHSInCommands 3472 } 3473 STATUS current 3474 DESCRIPTION 3475 "This group is a collection of high speed statistics for all 3476 implementations of the SCSI MIB module that contain SCSI target 3477 devices." 3478 ::= { scsiGroups 7} 3480 scsiLunMapStatsGroup OBJECT-GROUP 3481 OBJECTS { 3482 scsiAuthIntrAttachedTimes, 3483 scsiAuthIntrOutCommands, 3484 scsiAuthIntrReadMegaBytes, 3485 scsiAuthIntrWrittenMegaBytes 3486 } 3487 STATUS current 3488 DESCRIPTION 3489 "This group is a collection of statistics regarding SCSI 3490 initiator devices authorized to attach local logical unit and 3491 SCSI target device." 3492 ::= { scsiGroups 8} 3494 scsiLunMapHSStatsGroup OBJECT-GROUP 3495 OBJECTS { 3496 scsiAuthIntrHSOutCommands 3497 } 3498 STATUS current 3499 DESCRIPTION 3500 "This group is a collection of high speed statistics regarding 3501 SCSI initiator devices authorized to attach local logical unit 3502 and SCSI target device." 3503 ::= { scsiGroups 9} 3505 scsiInitiatorDevStatsGroup OBJECT-GROUP 3506 OBJECTS { 3507 scsiIntrDevOutResets, 3508 scsiIntrPortOutCommands, 3509 scsiIntrPortWrittenMegaBytes, 3510 scsiIntrPortReadMegaBytes 3511 } 3512 STATUS current 3513 DESCRIPTION 3514 "This group is a collection of statistics for all 3515 implementations of the SCSI MIB module that contain SCSI 3516 initiator devices." 3517 ::= { scsiGroups 10} 3519 scsiInitiatorDevHSStatsGroup OBJECT-GROUP 3520 OBJECTS { 3521 scsiIntrPortHSOutCommands 3522 } 3523 STATUS current 3524 DESCRIPTION 3525 "This group is a collection of high speed statistics for all 3526 implementations of the SCSI MIB module that contain SCSI 3527 initiator devices." 3528 ::= { scsiGroups 11} 3530 scsiDiscoveryStatsGroup OBJECT-GROUP 3531 OBJECTS { 3532 scsiDscTgtInCommands, 3533 scsiDscTgtReadMegaBytes, 3534 scsiDscTgtWrittenMegaBytes 3535 } 3536 STATUS current 3537 DESCRIPTION 3538 "This group is a collection of statistics for all 3539 implementations of the SCSI MIB module that contain discovered 3540 SCSI initiator devices." 3541 ::= { scsiGroups 12} 3543 scsiDiscoveryHSStatsGroup OBJECT-GROUP 3544 OBJECTS { 3545 scsiDscTgtHSInCommands 3546 } 3547 STATUS current 3548 DESCRIPTION 3549 "This group is a collection of high speed statistics for all 3550 implementations of the SCSI MIB module that contain discovered 3551 SCSI initiator devices." 3552 ::= { scsiGroups 13} 3554 scsiDeviceStatGroup OBJECT-GROUP 3555 OBJECTS { 3556 scsiPortBusyStatuses 3557 } 3558 STATUS current 3559 DESCRIPTION 3560 "A collection of statistics regarding about SCSI devices and 3561 ports." 3562 ::= { scsiGroups 14 } 3564 scsiTgtDevLuNotificationsGroup NOTIFICATION-GROUP 3565 NOTIFICATIONS { 3566 scsiTgtDeviceStatusChanged, 3567 scsiLuStatusChanged 3568 } 3569 STATUS current 3570 DESCRIPTION 3571 "A collection of notifications regarding status change of SCSI 3572 target devices and logical units." 3573 ::= { scsiGroups 15 } 3575 END 3577 10. Acknowledgments 3579 This document is the result of the work of the SCSI MIB Group. In 3580 particular, the contributions of Sajay Selvaraj (HCL Technologies), 3581 George Penokie (IBM) and Roger Cummings (Veritas Software) were 3582 critical to the formulation of this specification. 3584 11. Object Population Example: SCSI Target and Initiator devices on a 3585 pSCSI bus 3587 This section provides a sample set of values for a parallel SCSI 3588 scenario in which a SCSI MIB module can be implemented. The example 3589 shown below is not a normative part of this draft and makes some 3590 assumptions about the underlying implementation, which are not based 3591 on actual implementations. 3593 The respective sections describe the sequence of object 3594 instantiations and attempts to explain non-typical values for 3595 attributes that are unique to the scenario. 3597 Note: While populating the objects, the population of statistics is 3598 not considered. 3600 This scenario deals with a SCSI target and initiator devices attached 3601 to a parallel SCSI bus, defined by one of the SCSI-3 Parallel 3602 Interface standards (the version referenced in the MIB module is the 3603 4th generation, called SPI-4). We assume that the SCSI Initiator 3604 Device is a Host Bus Adaptor (HBA), and the SCSI Target Device is a 3605 physical disk. We assume that the SCSI Target Device has one 3606 integrated logical unit, identified by a Logical Unit Number(LUN) of 3607 0, which is the default LUN. The Parallel SCSI transport only 3608 supports port identifiers, and not port names. The transport pointer 3609 is set to 0 since there is no MIB module defined for SPI-4. 3611 We assume an HBA as the SCSI initiator device and a disk as SCSI 3612 target device. We assume that the SCSI target device has one logical 3613 unit, addressed by logical unit number set to 0 (LUN0), which is the 3614 default LUN. Parallel SCSI only has port identifiers, no port names. 3615 The transport pointer for parallel SCSI is set to 0 since, there is 3616 no reference transport (SPI) MIB module. 3618 Once the SCSI system is initialized, SNMP agent should be able to 3619 view the values of variables populated in the ScsiDevice, 3620 ScsiInitiatorDevice, ScsiTargetDevice, ScsiPort, 3621 ScsiTargetPort,ScsiInitiatorPort, ScsiLogicalUnit, ScsiLUIdentifier 3622 objects. 3624 The ScsiAuthorizedIntr population depends on the transport and the 3625 implementation. As this example scenario is parallel scsi, we deal 3626 with the ports. Hence the ScsiPortIndexOrZero is the index of the 3627 SCSI target port and ScsiAuthIntrDevOrPort is "port". Same is the 3628 case with the variables in scsiDscTgtDevOrPort also. 3630 Note that "" means zero-length string. 3632 11.1. scsiInstance Table: 3634 Attribute Value 3635 ---------- ------ 3636 scsiInstIndex 1 3637 scsiInstAlias "pSCSI-1" 3638 scsiInstSoftwareIndex 1000 3639 scsiInstVendorVersion "1.0a" 3640 scsiInstScsiNotificationsEnable true 3641 scsiInstStorageType nonVolatile 3643 11.2. scsiDevice Table: 3645 Attribute Value 3646 ---------- ------ 3647 scsiInstIndex 1 1 3648 scsiDeviceIndex 1 2 3649 scsiDeviceAlias "pSCSI-HBA" "pSCSI-Disk1" 3650 scsiDeviceRoles initiator(1) target(0) 3651 scsiDevicePortNumber 1 1 3653 11.3. scsiPort Table: 3655 Attribute Value 3656 ---------- ------ 3657 scsiInstIndex 1 1 3658 scsiDeviceIndex 1 2 3659 scsiPortIndex 1 2 3660 scsiPortRoles initiator(1) target(0) 3661 scsiPortTransportPtr 1 2 3663 11.4. scsiTransport Table: 3665 Attribute Value 3666 ---------- ------ 3667 scsiInstIndex 1 1 3668 scsiDeviceIndex 1 2 3669 scsiTransportIndex 1 2 3670 scsiTransportType scsiTransportSPI scsiTransportSPI 3671 scsiTransportPointer 0.0 0.0 3672 scsiTransportDevName "" "" 3674 11.5. scsiIntrDev Table: 3676 Attribute Value 3677 ---------- ------ 3678 scsiInstIndex 1 3679 scsiDeviceIndex 1 3680 scsiIntrDevTgtAccessMode autoEnable(2) 3682 11.6. scsiInitiatorPort Table: 3684 Attribute Value 3685 ---------- ------ 3686 scsiInstIndex 1 3687 scsiDeviceIndex 1 3688 scsiPortIndex 1 3689 scsiIntrPortName "" 3690 scsiIntrPortIdentifier *1 0001b 3692 *1 Port Identifier for SCSI is represented by 4 bits. 3694 11.7. scsiDscTgt Table: 3696 Attribute Value 3697 ---------- ------ 3698 scsiInstIndex 1 3699 scsiDeviceIndex 1 3700 scsiDscTgtIntrPortIndex 1 3701 scsiDscTgtIndex 1 3702 scsiDscTgtDevOrPort port(2) 3703 scsiDscTgtName "" 3704 scsiDscTgtConfigured false(2) 3705 scsiDscTgtDiscovered true(1) 3706 scsiDscTgtRowStatus active(1) 3708 11.8. scsiDscLUN: 3710 Attribute Value 3711 ---------- ------ 3712 scsiInstIndex 1 3713 scsiDeviceIndex 1 3714 scsiDscTgtIntrPortIndex 1 3715 scsiDscTgtIndex 1 3716 scsiDscLunIndex 1 3717 scsiDscLunLun 0 3719 11.9. scsiDscLUNIdentifier: 3721 Attribute Value 3722 ---------- ------ 3723 scsiInstIndex 1 3724 scsiDeviceIndex 1 3725 scsiDscLunIndex 1 3726 scsiDscLunIdIndex 1 3727 scsiDscLunIdCodeSet *1 2 3728 scsiDscLunIdAssociation *2 1 3729 scsiDscLunIdType *3 1 3730 scsiDscLunIdValue ASPENsl318203-001 3732 *1 - The identifier field will have ASCII graphic codes. 3733 *2 - The identifier is associated with the port that received 3734 the request. 3735 *3 - As defined in SPC (This value specifies that the 3736 scsiDscLunIdValue contains a vendorID in the first 8 bytes 3737 concatenated with the product identifier field and product 3738 serial number 3740 11.10. scsiAttTgtPort Table: 3742 Attribute Value 3743 ---------- ------ 3744 scsiInstIndex 1 3745 scsiDeviceIndex 1 3746 scsiPortIndex 1 3747 scsiAttTgtPortIndex 1 3748 scsiAttTgtPortDscTgtIdx 1 3749 scsiAttTgtPortName "" 3750 scsiAttTgtPortId 0011b 3752 11.11. scsiTgtDev Table: 3754 Attribute Value 3755 ---------- ------ 3756 scsiInstIndex 1 3757 scsiDeviceIndex 2 3758 scsiTgtDevNumberOfLUs 1 3759 scsiTgtDeviceStatus available(2) 3760 scsiTgtDevNonAccessibleLUs 0 3762 11.12. scsiTgtPort Table: 3764 Attribute Value 3765 ---------- ------ 3766 scsiInstIndex 1 3767 scsiDeviceIndex 2 3768 scsiPortIndex 2 3769 scsiPortName "" 3770 scsiTgtPortIdentifier 0010b 3772 11.13. scsiLU Table: 3774 Attribute Value 3775 ---------- ------ 3776 scsiInstIndex 1 3777 scsiDeviceIndex 2 3778 scsiLuIndex 1 3779 scsiLuDefaultLun 0 3780 scsiLuWwnName "" 3781 scsiLuVendorId "xyz-corp" 3782 scsiLuProductId "super turbo disk" 3783 scsiRevisionId 02 3784 scsiLUPeripheralType 00 3785 scsiLUStatus available(2) 3786 scsiLuState exposed(3) 3788 11.14. scsiLuId Table: 3790 Attribute Value 3791 ---------- ------ 3792 scsiInstIndex 1 3793 scsiDeviceIndex 2 3794 scsiLuIndex 1 3795 scsiLuIdIndex 1 3796 scsiLuIdCodeSet *1 2 3797 scsiLuIdAssociation *2 1 3798 scsiLuIdType *3 1 3799 scsiLuIdValue ASPENsl318203-0004 3801 *1 - The identifier field will have ASCII graphic codes. 3802 *2 - The identifier is associated with the port that received 3803 the request. 3804 *3 - As defined in SPC (This value specifies that the 3805 LuIdValue contains a vendorID in the first 8 bytes concatenated 3806 with the product identifier field and product serial number 3808 11.15. scsiLunMap Table: 3810 Attribute Value 3811 ---------- ------ 3812 scsiInstIndex 1 3813 scsiDeviceIndex 2 3814 scsiLunMapIndex 1 3815 scsiLunMapLun 0 3816 scsiLunMapLuIndex 1 3817 scsiLunMapLunRowStatus active(1) 3819 11.16. scsiAuthorizedIntr Table: 3821 Attribute Value 3822 ---------- ------ 3823 scsiInstIndex 1 3824 scsiDeviceIndex 2 3825 scsiAuthIntrTgtPortIndex 2 3826 scsiAuthIntrIndex 1 3827 scsiAuthIntrDevOrPort port(2) 3828 scsiAuthIntrName "" 3829 scsiAuthIntrLunMapIndex 1 3830 scsiAuthIntrRowStatus active(1) 3832 11.17. scsiAttIntrPort Table: 3834 Attribute Value 3835 ---------- ------ 3836 scsiInstIndex 1 3837 scsiDeviceIndex 2 3838 scsiPortIndex 2 3839 scsiAttIntrPortIdx 1 3840 scsiAttIntrPortAuthIntrIdx 1 3841 scsiAttIntrPortName "" 3842 scsiAttIntrPortIdentifier 0011b 3844 12. Security Considerations 3846 There are a number of management objects defined in this MIB module 3847 that have a MAX-ACCESS clause of read-write and/or read-create. Such 3848 objects may be considered sensitive or vulnerable in some network 3849 environments. The support for SET operations in a non-secure 3850 environment without proper protection can have a negative effect on 3851 network operations. These are: 3853 o scsiInstAlias, scsiInstScsiNotificationsEnable, 3854 scsiInstStorageType and scsiDeviceAlias: these objects can be 3855 manipulated to affect the management of a SCSI instance and its 3856 devices; specifically, the SCSI instance's administrative alias, 3857 whether it generates notifications, whether its non-default 3858 parameter settings are retained over restarts, and the 3859 administrative alias for each of its devices. 3861 o scsiIntrDevTgtAccessMode: this object can be manipulated to allow 3862 immediate access by local SCSI initiator devices to discovered 3863 SCSI target devices without waiting for administrator approval, 3864 where such approval might not be forthcoming. 3866 o scsiDscTgtTable: the objects in this table can be manipulated to 3867 remove administrator-specified controls on access by local SCSI 3868 initiator devices to discovered SCSI target devices. 3870 o scsiAuthorizedIntrTable: the objects in this table can be 3871 manipulated to remove administrator-specified controls on access 3872 by remote SCSI initiator devices to local SCSI target devices. 3874 o scsiLunMapTable: the objects in this table can be manipulated to 3875 provide access by a remote SCSI initiator device to logical units 3876 which an administrator has configured as not accessible to said 3877 initiator. 3879 In each of the last four cases, the objects in the tables can also be 3880 manipulated to cause a Denial-of-Service attack, by preventing 3881 administrator-authorized access. 3883 Some of the readable objects in this MIB module (i.e., objects with a 3884 MAX-ACCESS other than not-accessible) may be considered sensitive or 3885 vulnerable in some network environments. It is thus important to 3886 control even GET and/or NOTIFY access to these objects and possibly 3887 to even encrypt the values of these objects when sending them over 3888 the network via SNMP. All seventeen of the tables in this MIB module 3889 contain information which might be considered sensitive to read 3890 access in some environments, e.g., 3891 o the settings of all read-write/read-create parameter objects 3892 mentioned above, 3894 o scsiInstSoftwareIndex, scsiInstVendorVersion 3895 --which version of which software is running; 3897 o scsiDeviceRole, scsiPortRole, scsiTransportType, 3898 scsiTransportPointer, scsiTransportDevName, scsiDscLunIdCodeSet, 3899 scsiDscLunIdAssociation,scsiDscLunIdType, scsiDscLunIdValue plus 3900 information in several tables: scsiTgtDevTable, scsiLuTable, 3901 scsiLuIdTable, scsiLunMapTable 3902 --topology information indicating which devices/ports are targets, 3903 about the transport protocols they use, and more specific 3904 information about such targets, including detailed information 3905 about the LUNs they expose and how they are mapped onto Logical 3906 Units; 3908 o scsiIntrPortOutCommands, 3909 scsiIntrPortWrittenMegaBytes,scsiIntrPortReadMegaBytes, 3910 scsiIntrPortHSOutCommands scsiDscTgtInCommands, 3911 scsiDscTgtWrittenMegaBytes,scsiDscTgtReadMegaBytes, 3912 scsiDscTgtHSInCommands, scsiTgtPortInCommands, 3913 scsiTgtPortWrittenMegaBytes, scsiTgtPortReadMegaBytes, 3914 scsiTgtPortHSInCommands, scsiAuthIntrAttachedTimes, 3915 scsiAuthIntrOutCommands, scsiAuthIntrReadMegaBytes, 3916 scsiAuthIntrWrittenMegaBytes, scsiAuthIntrHSOutCommands, 3917 scsiLuInCommands, scsiLuReadMegaBytes, scsiLuWrittenMegaBytes, 3918 scsiLuHSInCommands 3919 -- statistics which could be used for traffic analysis. 3921 o scsiAttTgtPortTable 3922 -- information on which initiators are connected to which targets 3923 which could be used for traffic analysis. 3925 o scsiAuthorizedIntrTable and scsiAttIntrPortTable tables 3926 -- information about which initiators are authorized to connect to 3927 which targets. 3929 These information may need to be kept private in sensitive 3930 environments. 3932 SNMP versions prior to SNMPv3 did not include adequate security. 3933 Even if the network itself is secure (for example by using IPSec), 3934 even then, there is no control as to who on the secure network is 3935 allowed to access and GET/SET (read/change/create/delete) the objects 3936 in this MIB module. 3938 It is RECOMMENDED that implementers consider the security features as 3939 provided by the SNMPv3 framework (see [RFC3410], section 8), 3940 including full support for the SNMPv3 cryptographic mechanisms (for 3941 authentication and privacy). 3943 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3944 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3945 enable cryptographic security. It is then a customer/operator 3946 responsibility to ensure that the SNMP entity giving access to an 3947 instance of this MIB module is properly configured to give access to 3948 the objects only to those principals (users) that have legitimate 3949 rights to indeed GET or SET (change/create/delete) them. 3951 13. IANA Considerations 3953 IANA is requested to make a MIB OID assignment under the mib-2 3954 branch. 3956 14. References 3958 14.1. Normative References 3960 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3961 Requirement Levels", BCP 14, RFC 2119, March 1997. 3963 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3964 Schoenwaelder, Ed., "Structure of Management Information 3965 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 3967 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3968 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 3969 STD 58, RFC 2579, April 1999. 3971 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 3972 "Conformance Statements for SMIv2", STD 58, RFC 2580, 3973 April 1999. 3975 [RFC2790] Waldbusser, S. and P. Grillo, "Host Resources MIB", 3976 RFC 2790, March 2000. 3978 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 3979 Architecture for Describing Simple Network Management 3980 Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, 3981 December 2002. 3983 [RFC3413] Levi, D., Meyer, P., and B. Stewart, "Simple Network 3984 Management Protocol (SNMP) Applications", STD 62, 3985 RFC 3413, December 2002. 3987 [SAM2] ANSI INCITS 366-2003, "SCSI Architecture Model-2 (SAM-2)", 3988 SAM-2 Revision 24, September 2002. 3990 RFC Editor: URLs introduced by the text "Final draft 3991 available at:" are for review purpose only. Those URLs 3992 and that introductory text should be removed before 3993 publication along with this note." 3995 Final draft available at: 3996 http://www.t10.org/ftp/t10/drafts/sam2/sam2r24.pdf 3998 [SPC2] ANSI INCITS 351-2001, "SCSI Primary Commands - 2 (SPC-2)", 3999 SPC-2 Revision 20, July 2001. 4001 Final draft available at: 4002 http://www.t10.org/ftp/t10/drafts/spc2/spc2r20.pdf 4004 [X3T10] X3T10/97-101, "IEEE Tutorial for SCSI use of IEEE 4005 company_id", X3T10 Revision 2, February 1997, 4006 . 4008 14.2. Informative References 4010 [FCP2] ANSI INCITS 350-2003, "Fibre Channel Protocol for SCSI 4011 (FCP-2)", FCP-2 Revision 08, September 2002. 4013 Final draft available at: 4014 http://www.t10.org/ftp/t10/drafts/fcp2/fcp2r08.pdf 4016 [I-D.ietf-ips-iscsi-mib] 4017 Bakke, M., "Definitions of Managed Objects for iSCSI", 4018 draft-ietf-ips-iscsi-mib-11 (work in progress), 4019 October 2005. 4021 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 4022 "Introduction and Applicability Statements for Internet- 4023 Standard Management Framework", RFC 3410, December 2002. 4025 [RFC3720] Satran, J., Meth, K., Sapuntzakis, C., Chadalapaka, M., 4026 and E. Zeidner, "Internet Small Computer Systems Interface 4027 (iSCSI)", RFC 3720, April 2004. 4029 [RFC4022] Raghunarayan, R., "Management Information Base for the 4030 Transmission Control Protocol (TCP)", RFC 4022, 4031 March 2005. 4033 [RFC4044] McCloghrie, K., "Fibre Channel Management MIB", RFC 4044, 4034 May 2005. 4036 [SAS-1.1] T10 Project #1601-D, "Serial Attached SCSI - 1.1 4037 (SAS-1.1)", SAS-1.1 Revision 10, September 2005. 4039 Final draft available at: 4040 http://www.t10.org/ftp/t10/drafts/sas1/sas1r10.pdf 4042 [SBP3] ANSI INCITS 375-2004, "Serial Bus Protocol 3 (SBP-3)", 4043 SBP-3 Revision 05, September 2003. 4045 Final draft available at: 4046 http://www.t10.org/ftp/t10/drafts/sbp3/sbp3r05.pdf 4048 [SCC2] ANSI INCITS 318-1998, "SCSI Controller Commands - 2 4049 (SCC-2)", SCC-2 Revision 04, September 1997. 4051 Final draft available at: 4053 http://www.t10.org/ftp/t10/drafts/scc2/scc2r04.pdf 4055 [SPI4] ANSI INCITS 362-2002, "SCSI Parallel Interface-4 (SPI4)", 4056 SPI-4 Revision 10, May 2002. 4058 Final draft available at: 4059 http://www.t10.org/ftp/t10/drafts/spi4/spi4r10.pdf 4061 [SRP] ANSI INCITS 365-2002, "SCSI RDMA Protocol (SRP)", 4062 SRP Revision 16a, July 2002. 4064 Final draft available at: 4065 http://www.t10.org/ftp/t10/drafts/srp/srp-r16a.pdf 4067 Authors' Addresses 4069 Michele Hallak-Stamler 4070 Sanrad Intelligent Storage 4071 32 Habarzel Street 4072 Tel Aviv 69710 4073 IL 4075 Phone: +972 3 7674809 4076 Email: michele@sanrad.com 4077 URI: http://www.sanrad.com/ 4079 Mark Bakke 4080 Cisco Systems, Inc. 4081 6450 Wedgwood Road, Suite 130 4082 Maple Grove, MN 55311 4083 USA 4085 Phone: +1 3 763-398-1000 4086 Email: mbakke@cisco.com 4087 URI: http://www.cisco.com/ 4089 Yaron Lederman 4090 Siliquent Technologies 4091 21 Etzel Street 4092 Ramat Gan 4093 IL 4095 Phone: +972 3 6777375 4096 Email: yaronled@bezeqint.net 4098 Marjorie Krueger 4099 Hewlett-Packard 4100 8000 Foothills Blvd 4101 Roseville, CA 95747 4102 US 4104 Phone: +1 916-785-2656 4105 Email: marjorie_krueger@hp.com 4106 Keith McCloghrie 4107 Cisco Systems, Inc. 4108 170 West Tasman Drive 4109 San Jose, CA 95134 4110 US 4112 Phone: +1 408 526-5260 4113 Email: kzm@cisco.com 4115 Intellectual Property Statement 4117 The IETF takes no position regarding the validity or scope of any 4118 Intellectual Property Rights or other rights that might be claimed to 4119 pertain to the implementation or use of the technology described in 4120 this document or the extent to which any license under such rights 4121 might or might not be available; nor does it represent that it has 4122 made any independent effort to identify any such rights. Information 4123 on the procedures with respect to rights in RFC documents can be 4124 found in BCP 78 and BCP 79. 4126 Copies of IPR disclosures made to the IETF Secretariat and any 4127 assurances of licenses to be made available, or the result of an 4128 attempt made to obtain a general license or permission for the use of 4129 such proprietary rights by implementers or users of this 4130 specification can be obtained from the IETF on-line IPR repository at 4131 http://www.ietf.org/ipr. 4133 The IETF invites any interested party to bring to its attention any 4134 copyrights, patents or patent applications, or other proprietary 4135 rights that may cover technology that may be required to implement 4136 this standard. Please address the information to the IETF at 4137 ietf-ipr@ietf.org. 4139 Disclaimer of Validity 4141 This document and the information contained herein are provided on an 4142 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 4143 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 4144 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 4145 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 4146 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 4147 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 4149 Copyright Statement 4151 Copyright (C) The Internet Society (2006). This document is subject 4152 to the rights, licenses and restrictions contained in BCP 78, and 4153 except as set forth therein, the authors retain all their rights. 4155 Acknowledgment 4157 Funding for the RFC Editor function is currently provided by the 4158 Internet Society.