idnits 2.17.1 draft-asai-vmm-mib-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 289 has weird spacing: '...nString vmH...' == Line 290 has weird spacing: '...nString vmH...' == Line 294 has weird spacing: '...meTicks vmTab...' == Line 297 has weird spacing: '...neIndex vmInd...' == Line 360 has weird spacing: '...ineList vmAf...' == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (July 3, 2013) is 3921 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. 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: 'RFC4122' is defined on line 1969, but no explicit reference was found in the text Summary: 0 errors (**), 0 flaws (~~), 8 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 OPSAWG H. Asai 3 Internet-Draft Univ. of Tokyo 4 Intended status: Standards Track M. MacFaden 5 Expires: January 4, 2014 VMware Inc. 6 J. Schoenwaelder 7 Jacobs University 8 Y. Sekiya 9 Univ. of Tokyo 10 K. Shima 11 IIJ Innovation Institute Inc. 12 T. Tsou 13 Huawei Technologies (USA) 14 C. Zhou 15 Huawei Technologies 16 H. Esaki 17 Univ. of Tokyo 18 July 3, 2013 20 Management Information Base for Virtual Machines Controlled by a 21 Hypervisor 22 draft-asai-vmm-mib-04 24 Abstract 26 This document defines a portion of the Management Information Base 27 (MIB) for use with network management protocols in the Internet 28 community. In particular, this specifies objects for managing 29 virtual machines controlled by a hypervisor (a.k.a. virtual machine 30 manager). 32 Status of this Memo 34 This Internet-Draft is submitted in full conformance with the 35 provisions of BCP 78 and BCP 79. 37 Internet-Drafts are working documents of the Internet Engineering 38 Task Force (IETF). Note that other groups may also distribute 39 working documents as Internet-Drafts. The list of current Internet- 40 Drafts is at http://datatracker.ietf.org/drafts/current/. 42 Internet-Drafts are draft documents valid for a maximum of six months 43 and may be updated, replaced, or obsoleted by other documents at any 44 time. It is inappropriate to use Internet-Drafts as reference 45 material or to cite them other than as "work in progress." 47 This Internet-Draft will expire on January 4, 2014. 49 Copyright Notice 51 Copyright (c) 2013 IETF Trust and the persons identified as the 52 document authors. All rights reserved. 54 This document is subject to BCP 78 and the IETF Trust's Legal 55 Provisions Relating to IETF Documents 56 (http://trustee.ietf.org/license-info) in effect on the date of 57 publication of this document. Please review these documents 58 carefully, as they describe your rights and restrictions with respect 59 to this document. Code Components extracted from this document must 60 include Simplified BSD License text as described in Section 4.e of 61 the Trust Legal Provisions and are provided without warranty as 62 described in the Simplified BSD License. 64 Table of Contents 66 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 67 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 68 2. The Internet-Standard Management Framework . . . . . . . . . . 4 69 3. Managed Objects for Virtual Machines Controlled by a 70 Hypervisor . . . . . . . . . . . . . . . . . . . . . . . . . . 5 71 3.1. Managed Objects on Virtualization Environment . . . . . . 5 72 3.2. Overview of the MIB Module . . . . . . . . . . . . . . . . 6 73 3.3. Definitions . . . . . . . . . . . . . . . . . . . . . . . 10 74 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 42 75 5. Security Considerations . . . . . . . . . . . . . . . . . . . 43 76 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 45 77 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 46 78 7.1. Normative References . . . . . . . . . . . . . . . . . . . 46 79 7.2. Informative References . . . . . . . . . . . . . . . . . . 47 80 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 48 82 1. Introduction 84 This document defines a portion of the Management Information Base 85 (MIB) for use with network management protocols in the Internet 86 community. In particular, this specifies objects for managing 87 virtual machines controlled by a hypervisor (a.k.a. virtual machine 88 managers). A hypervisor controls multiple virtual machines on a 89 single physical machine by allocating resources to each virtual 90 machine using virtualization technologies. Therefore, this MIB 91 module contains information on virtual machines and their resources 92 controlled by a hypervisor as well as hypervisor's hardware and 93 software information. 95 The design of this MIB module has been derived from enterprise 96 specific MIB modules, namely a MIB module for managing guests of the 97 Xen hypervisor, a MIB module for managing virtual machines controlled 98 by the VMware hypervisor, and a MIB module using the libvirt 99 programming interface to access different hypervisors. 101 1.1. Requirements Language 103 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 104 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 105 document are to be interpreted as described in RFC 2119 [RFC2119]. 107 2. The Internet-Standard Management Framework 109 For a detailed overview of the documents that describe the current 110 Internet-Standard Management Framework, please refer to section 7 of 111 RFC 3410 [RFC3410]. Managed objects are accessed via a virtual 112 information store, termed the Management Information Base or MIB. 113 MIB objects are generally accessed through the Simple Network 114 Management Protocol (SNMP). Objects in the MIB are defined using the 115 mechanisms defined in the Structure of Management Information (SMI). 116 This memo specifies a MIB module that is compliant to the SMIv2, 117 which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 118 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 120 3. Managed Objects for Virtual Machines Controlled by a Hypervisor 122 3.1. Managed Objects on Virtualization Environment 124 +------------------------------------------------------------------+ 125 | +-------------------------------------------+ | 126 | | Virtual machine | | 127 | | | | 128 | | +---------+ +---------+ +---------+ | ......... | 129 | | | Virtual | | Virtual | | Virtual | | | 130 | +-| CPU |-| memory |-| storage |... ---+ | 131 | +---------+ +---------+ +---------+ | 132 | Virtual resources | 133 | ^ | 134 | | Allocation using virtualization technologies | 135 | | | 136 | +---------- Physical resources ._____. | 137 | +--------+ .--------. / \ | 138 | +==============+ | | /________/| *\_______/* | 139 +- || SNMP agent || - - | CPU | - | Memory |/ - | Storage | .. -+ 140 | +==============+ +--------+ +--------+ \_______/ | 141 | Hypervisor | 142 +------------------------------------------------------------------+ 144 A hypervisor allocates resources as virtual devices such as virtual 145 CPU, virtual memory, virtual storage, and virtual network interface 146 to multiple virtual machines controlled by the hypervisor from 147 physical resources. 149 Figure 1: An example of a virtualization environment 151 On the common implementations of hypervisor softwares, a hypervisor 152 allocates resources as virtual devices such as virtual CPUs, virtual 153 memory, virtual storage, and virtual network interface to multiple 154 virtual machines controlled by the hypervisor from physical 155 resources. This document defines objects related to system and 156 software information of a hypervisor, the list of virtual machines 157 controlled by the hypervisor, and virtual resources allocated by the 158 hypervisor to virtual machines. As shown in Figure 1, the virtual 159 resource objects are defined as virtual devices. Consequently, this 160 document specifies four specific types of virtual devices; CPUs 161 (processors), memory, network interfaces, and storage devices. Note 162 that physical resources are managed in HOST-RESOURCES-MIB [RFC2790]. 163 In case that each virtual resource device object has a corresponding 164 parent physical device managed in HOST-RESOURCES-MIB, the object of 165 the virtual resource device contains a pointer to the physical 166 device. The objects related to virtual network interfaces are mapped 167 to the objects managed in IF-MIB [RFC2863]. 169 The objects defined in this document are managed at a hypervisor and 170 an SNMP agent is launched at the hypervisor to provide access to the 171 objects. The objects are managed from the viewpoint of the operators 172 of hypervisors, but not the operators of virtual machines; i.e., the 173 objects do not take into account the actual resource utilization on 174 each virtual machine but the resource allocation from the physical 175 resources. For example, vmNetworIfIndex indicates the virtual 176 interface associated with an interface of a virtual machine at the 177 hypervisor, and consequently, the `in' and `out' directions denote 178 `from a virtual machine to the hypervisor' and `from the hypervisor 179 to a virtual machine', respectively. Moreover, 180 vmStorageAllocatedSize denotes the size allocated by the hypervisor, 181 but not the size actually used by the operating system on the virtual 182 machine. This means that vmStorageDefinedSize and 183 vmStorageAllocatedSize must not take different values when the 184 vmStorageSourceType is `block' or `raw'. 186 3.2. Overview of the MIB Module 188 The MIB module is organized into a group of scalars and tables. The 189 scalars below `hypervisor' provide basic information about the 190 hypervisor. The `vmTable' lists the virtual machines (guests) that 191 are known to the hypervisor. The `vmCpuTable' and 192 'vmCpuAffinityTable' provide the mapping of virtual CPUs and their 193 affinity to virtual machines. The `vmStorageTable' and the 194 `vmNetworkTable' provide the mapping of logical storage areas and 195 network interfaces to virtual machines. 197 *: `vmAdminState' write access 198 !: Notification 199 +-------------+ + - - - - - - + 200 | finite | | transient | 201 | vmOperState | | vmOperState | 202 +-------------+ + - - - - - - + 204 ================================================================ 206 +--------------+ + - - - - - - + +-------------+ 207 | suspended |<--| suspending | | paused | 208 | !vmSuspended | | | | !vmPaused | 209 +--------------+ + - - - - - - + +-------------+ 210 | ^ *suspended ^ *paused 211 | | | 212 v *running | *running | 213 + - - - - - - + +-------------+<----------+ + - - - - - - + 214 | resuming |-->| running |<-------------->| migrating | 215 | | | !vmRunning | | | 216 + - - - - - - + +-------------+ + - - - - - - + 217 | ^ *running ^ 218 | | | 219 | +-------------------+ | 220 | | | 221 v *shutdown *destroy v v 222 + - - - - - - - + +-------------+ 223 | shuttingdown |--------->| shutdown | 224 | | | !vmShutdown | 225 + - - - - - - - + +-------------+ 226 ^ | 227 | v !vmDeleted 228 + - - - - - - + +-------------+ + - - - - - - + (Deleted from 229 | blocked | | crashed | | preparing | vmTable) 230 | | | !vmCrashed | | | 231 + - - - - - - + +-------------+ + - - - - - - + 233 The state transition of a virtual machine 235 Figure 2: State transition of a virtual machine 237 The vmAdminState' and `vmOperState' textual conventions define an 238 administrative state and an operational state model for virtual 239 machines. Events causing transitions between major operational 240 states will cause the generation of notifications. Per-VM 241 notifications (vmRunning, vmShutdown, vmPaused, vmSuspended, 242 vmCrashed, vmDeleted) are generated if vmPerVMNotificationsEnabled is 243 true(1). Bulk notifications (vmBulkRunning, vmBulkShutdown, 244 vmBulkPaused, vmBulkSuspended, vmBulkCrashed, vmBulkDeleted) are 245 generated if vmBulkNotificationsEnabled is true(1). The transition 246 of `vmOperState' by the write access to `vmAdminState' and the 247 notifications generated by the operational state changes are 248 summarized in Figure 2. Note that the notifications shown in this 249 figure are per-VM notifications. In the case of Bulk notifications, 250 the prefix `vm' is replaced with 'vmBulk'. 252 The bulk notification mechanism is designed to reduce the number of 253 notifications that are trapped by an SNMP manager. This is because 254 the number of virtual machines managed by a bunch of hypervisors in a 255 datacenter possibly becomes several thousands or more, and 256 consequently, many notifications could be trapped if these virtual 257 machines frequently change their administrative state. The per-VM 258 notifications carry more detailed information, but the scalability 259 shall be a problem. An implementation shall support both, either of, 260 or none of per-VM notifications and bulk notifications. The 261 notification filtering mechanism described in section 6 of RFC 3413 262 [RFC3413] is used by the management applications to control the 263 notifications. 265 The MIB module provides a few writable objects that can be used to 266 make non-persistent changes, e.g., changing the memory allocation or 267 the CPU allocation. It is not the goal of this MIB module to provide 268 a configuration interface for virtual machines since other protocols 269 and data modeling languages are more suitable for this task. 271 The OID tree structure of the MIB module is shown below. 273 --vmMIB (1.3.6.1.2.1.yyy) 274 +--vmNotifications(0) 275 | +--vmRunning(1) [vmName, vmUUID, vmOperState] 276 | +--vmShutdown(2) [vmName, vmUUID, vmOperState] 277 | +--vmPaused(3) [vmName, vmUUID, vmOperState] 278 | +--vmSuspended(4) [vmName, vmUUID, vmOperState] 279 | +--vmCrashed(5) [vmName, vmUUID, vmOperState] 280 | +--vmDeleted(6) [vmName, vmUUID, vmOperState, vmPersistent] 281 | +--vmBulkRunning(7) [vmAffectedVMs] 282 | +--vmBulkShutdown(8) [vmAffectedVMs] 283 | +--vmBulkPaused(9) [vmAffectedVMs] 284 | +--vmBulkSuspended(10) [vmAffectedVMs] 285 | +--vmBulkCrashed(11) [vmAffectedVMs] 286 | +--vmBulkDeleted(12) [vmAffectedVMs] 287 +--vmObjects(1) 288 | +--vmHypervisor(1) 289 | | +-- r-n SnmpAdminString vmHvSoftware(1) 290 | | +-- r-n SnmpAdminString vmHvVersion(2) 291 | | +-- r-n OBJECT IDENTIFIER vmHvObjectID(3) 292 | | +-- r-n TimeTicks vmHvUpTime(4) 293 | +-- r-n Integer32 vmNumber(2) 294 | +-- r-n TimeTicks vmTableLastChange(3) 295 | +--vmTable(4) 296 | | +--vmEntry(1) [vmIndex] 297 | | +-- --- VirtualMachineIndex vmIndex(1) 298 | | +-- r-n SnmpAdminString vmName(2) 299 | | +-- r-n UUIDorZero vmUUID(3) 300 | | +-- r-n SnmpAdminString vmOSType(4) 301 | | +-- rwn VirtualMachineAdminState 302 | | | vmAdminState(5) 303 | | +-- r-n VirtualMachineOperState 304 | | | vmOperState(6) 305 | | +-- rwn VirtualMachineAutoStart 306 | | | vmAutoStart(7) 307 | | +-- r-n VirtualMachinePersistent 308 | | | vmPersistent(8) 309 | | +-- r-n Integer32 vmCurCpuNumber(9) 310 | | +-- rwn Integer32 vmMinCpuNumber(10) 311 | | +-- rwn Integer32 vmMaxCpuNumber(11) 312 | | +-- r-n Integer32 vmMemUnit(12) 313 | | +-- r-n Integer32 vmCurMem(13) 314 | | +-- rwn Integer32 vmMinMem(14) 315 | | +-- rwn Integer32 vmMaxMem(15) 316 | | +-- r-n TimeTicks vmUpTime(16) 317 | | +-- r-n Counter64 vmCpuTime(17) 318 | +--vmCpuTable(5) 319 | | +--vmCpuEntry(1) [vmIndex, vmCpuIndex] 320 | | +-- --- VirtualMachineCpuIndex 321 | | | vmCpuIndex(1) 322 | | +-- r-n Counter64 vmCpuCoreTime(2) 323 | +--vmCpuAffinityTable(6) 324 | | +--vmCpuAffinityEntry(1) [vmIndex, 325 | | | vmCpuIndex, 326 | | | vmCpuPhysIndex] 327 | | +-- --- Integer32 vmCpuPhysIndex(1) 328 | | +-- rwn Integer32 vmCpuAffinity(2) 329 | +--vmStorageTable(7) 330 | | +--vmStorageEntry(1) [vmStorageVmIndex, vmStorageIndex] 331 | | +-- --- VirtualMachineIndexOrZero 332 | | | vmStorageVmIndex(1) 333 | | +-- --- VirtualMachineStorageIndex 334 | | | vmStorageIndex(2) 335 | | +-- r-n Integer32 vmStorageParent(3) 336 | | +-- r-n VirtualMachineStorageSourceType 337 | | | vmStorageSourceType(4) 338 | | +-- r-n SnmpAdminString vmStorageSourceTypeString(5) 339 | | +-- r-n SnmpAdminString vmStorageResourceID(6) 340 | | +-- r-n VirtualMachineStorageAccess 341 | | | vmStorageAccess(7) 342 | | +-- r-n VirtualMachineStorageMediaType 343 | | | vmStorageMediaType(8) 344 | | +-- r-n SnmpAdminString vmStorageMediaTypeString(9) 345 | | +-- r-n Integer32 vmStorageSizeUnit(10) 346 | | +-- r-n Integer32 vmStorageDefinedSize(11) 347 | | +-- r-n Integer32 vmStorageAllocatedSize(12) 348 | | +-- r-n Counter64 vmStorageReadIOs(13) 349 | | +-- r-n Counter64 vmStorageWriteIOs(14) 350 | +--vmNetworkTable(8) 351 | | +--vmNetworkEntry(1) [vmIndex, vmNetworkIndex] 352 | | +-- --- VirtualMachineNetworkIndex 353 | | | vmNetworkIndex(1) 354 | | +-- r-n InterfaceIndexOrZero vmNetworIfIndex(2) 355 | | +-- r-n InterfaceIndexOrZero vmNetworkParent(3) 356 | | +-- r-n SnmpAdminString vmNetworkModel(4) 357 | | +-- r-n PhysAddress vmNetworkPhysAddress(5) 358 | +-- rwn TruthValue vmPerVMNotificationsEnabled(9) 359 | +-- rwn TruthValue vmBulkNotificationsEnabled(10) 360 | +-- --n VirtualMachineList vmAffectedVMs(11) 361 +--vmConformance(2) 362 +--vmCompliances(1) 363 | +--vmFullCompliances(1) 364 | +--vmReadOnlyCompliances(2) 365 +--vmGroups(2) 366 +--vmHypervisorGroup(1) 367 +--vmVirtualMachineGroup(2) 368 +--vmCpuGroup(3) 369 +--vmCpuAffinityGroup(4) 370 +--vmStorageGroup(5) 371 +--vmNetworkGroup(6) 372 +--vmPerVMNotificationOptionalGroup(7) 373 +--vmBulkNotificationsVariablesGroup(8) 374 +--vmBulkNotificationOptionalGroup(9) 376 3.3. Definitions 378 VM-MIB DEFINITIONS ::= BEGIN 380 IMPORTS 381 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, TimeTicks, 382 Counter64, Integer32, mib-2 383 FROM SNMPv2-SMI 384 OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP 385 FROM SNMPv2-CONF 386 TEXTUAL-CONVENTION, PhysAddress, TruthValue 387 FROM SNMPv2-TC 388 SnmpAdminString 389 FROM SNMP-FRAMEWORK-MIB 390 UUIDorZero 391 FROM UUID-TC-MIB 392 InterfaceIndexOrZero 393 FROM IF-MIB; 395 vmMIB MODULE-IDENTITY 396 LAST-UPDATED "201307020000Z" -- 2 July 2013 397 ORGANIZATION "IETF Operations and Management Area Working Group" 398 CONTACT-INFO 399 " 400 WG E-mail: (To be added after approved by WG) 401 Mailing list subscription info: 402 http:// (To be added after approved by WG) 404 Hirochika Asai 405 The University of Tokyo 406 7-3-1 Hongo 407 Bunkyo-ku, Tokyo 113-8656 408 JP 409 Phone: +81 3 5841 6748 410 Email: panda@hongo.wide.ad.jp 412 Michael MacFaden 413 VMware Inc. 414 Email: mrm@vmware.com 416 Juergen Schoenwaelder 417 Jacobs University 418 Campus Ring 1 419 Bremen 28759 420 Germany 421 Email: j.schoenwaelder@jacobs-university.de 423 Yuji Sekiya 424 The University of Tokyo 425 2-11-16 Yayoi 426 Bunkyo-ku, Tokyo 113-8658 427 JP 428 Email: sekiya@wide.ad.jp 430 Keiichi Shima 431 IIJ Innovation Institute Inc. 432 3-13 Kanda-Nishikicho 433 Chiyoda-ku, Tokyo 101-0054 434 JP 435 Email: keiichi@iijlab.net 436 Tina Tsou 437 Huawei Technologies (USA) 438 2330 Central Expressway 439 Santa Clara CA 95050 440 USA 441 Email: tina.tsou.zouting@huawei.com 443 Cathy Zhou 444 Huawei Technologies 445 Bantian, Longgang District 446 Shenzhen 518129 447 P.R. China 448 Email: cathyzhou@huawei.com 450 Hiroshi Esaki 451 The University of Tokyo 452 7-3-1 Hongo 453 Bunkyo-ku, Tokyo 113-8656 454 JP 455 Email: hiroshi@wide.ad.jp 456 " 458 DESCRIPTION 459 "This MIB module is for use in managing a hypervisor and 460 virtual machines controlled by the hypervisor. The OID 461 `yyy' is temporary one, and it must be assigned by IANA 462 when this becomes an official document. 464 Copyright (c) 2013 IETF Trust and the persons identified 465 as authors of the code. All rights reserved. 467 Redistribution and use in source and binary forms, with 468 or without modification, is permitted pursuant to, and 469 subject to the license terms contained in, the 470 Simplified BSD License set forth in Section 4.c of the 471 IETF Trust's Legal Provisions Relating to IETF Documents 472 (http://trustee.ietf.org/license-info)." 474 REVISION "201307020000Z" -- 2 July 2013 475 DESCRIPTION 476 "The original version of this MIB, published as 477 RFCXXXX." 478 ::= { mib-2 yyy } 480 vmNotifications OBJECT IDENTIFIER ::= { vmMIB 0 } 481 vmObjects OBJECT IDENTIFIER ::= { vmMIB 1 } 482 vmConformance OBJECT IDENTIFIER ::= { vmMIB 2 } 483 -- Textual conversion definitions 484 -- 485 VirtualMachineIndex ::= TEXTUAL-CONVENTION 486 DISPLAY-HINT "d" 487 STATUS current 488 DESCRIPTION 489 "A unique value, greater than zero, identifying a 490 virtual machine. The value for each virtual machine 491 must remain constant at least from one re-initialization 492 of the hypervisor to the next re-initialization." 493 SYNTAX Integer32 (1..2147483647) 495 VirtualMachineIndexOrZero ::= TEXTUAL-CONVENTION 496 DISPLAY-HINT "d" 497 STATUS current 498 DESCRIPTION 499 "This textual convention is an extension of the 500 VirtualMachineIndex convention. This extension permits 501 the additional value of zero. The meaning of the value 502 zero is object-specific and must therefore be defined as 503 part of the description of any object which uses this 504 syntax. Examples of the usage of zero might include 505 situations where a virtual machine is unknown, or when 506 none or all virtual machines need to be referenced." 507 SYNTAX Integer32 (0..2147483647) 509 VirtualMachineAdminState ::= TEXTUAL-CONVENTION 510 STATUS current 511 DESCRIPTION 512 "The administrative state of a virtual machine: 514 running(1) The administrative state of the virtual 515 machine indicating the virtual machine 516 should be brought online. 518 suspended(2) The administrative state of the virtual 519 machine where its memory and CPU execution 520 state has been saved to persistent store 521 and will be restored at next running(1). 523 paused(3) The administrative state indicating the 524 virtual machine is resident in memory but 525 is no longer scheduled to execute by the 526 hypervisor. 528 shutdown(4) The administrative state of the virtual 529 machine indicating the virtual machine 530 should be taken shuttingdown. 532 destroy(5) The administrative state of the virtual 533 machine indicating the virtual machine 534 should be forcibly shutdown. After the 535 destroy operation, the administrative 536 state should be automatically changed to 537 shutdown." 538 SYNTAX INTEGER { 539 running(1), 540 suspend(2), 541 pause(3), 542 shutdown(4), 543 destroy(5) 544 } 546 VirtualMachineOperState ::= TEXTUAL-CONVENTION 547 STATUS current 548 DESCRIPTION 549 "The operational state of a virtual machine: 551 unknown(1) The state is unknown, e.g., because the 552 implementation failed to obtain the state 553 from the hypervisor. 555 other(2) The state has been obtained but it is not 556 a known state. 558 preparing(3) The virtual machine is currently in the 559 process of preparation, e.g., allocating 560 and initializing virtual storage are 561 after creating (defining) virtual 562 machine. 564 running(4) The virtual machine is currently running. 566 blocked(5) The virtual machine is currently blocked. 568 suspending(6) The virtual machine is currently in the 569 process of suspending. 571 suspended(7) The virtual machine is currently 572 suspended. 574 resuming(8) The virtual machine is currently in the 575 process of resuming. This is a transient 576 state from suspended state to running 577 state. 579 paused(9) The virtual machine is currently paused. 581 migrating(10) The virtual machine is currently 582 migrating. 584 shuttingdown(11) 585 The virtual machine is currently in the 586 process of shutting down. 588 shutdown(12) The virtual machine is down. 590 crashed(13) The virtual machine has crashed." 591 SYNTAX INTEGER { 592 unknown(1), 593 other(2), 594 preparing(3), 595 running(4), 596 blocked(5), 597 suspending(6), 598 suspended(7), 599 resuming(8), 600 paused(9), 601 migrating(10), 602 shuttingdown(11), 603 shutdown(12), 604 crashed(13) 605 } 607 VirtualMachineAutoStart ::= TEXTUAL-CONVENTION 608 STATUS current 609 DESCRIPTION 610 "The autostart configuration of a virtual machine: 612 unknown(1) The autostart configuration is unknown, 613 e.g., because the implementation failed 614 to obtain the autostart configuration 615 from the hypervisor. (read-only) 617 enable(2) The autostart configuration of the 618 virtual machine is enabled. 620 disable(3) The autostart configuration of the 621 virtual machine is disabled." 622 SYNTAX INTEGER { 623 unknown(1), 624 enable(2), 625 disable(3) 626 } 628 VirtualMachinePersistent ::= TEXTUAL-CONVENTION 629 STATUS current 630 DESCRIPTION 631 "This value indicates whether a virtual machine has a 632 persistent configuration which means the virtual machine 633 will still exist after shutting down: 635 unknown(1) The persistent configuration is unknown, 636 e.g., because the implementation failed 637 to obtain the persistent configuration 638 from the hypervisor. (read-only) 640 persistent(2) The virtual machine is persistent. 642 transient(3) The virtual machine is transient, i.e., 643 the virtual machine does not exist after 644 its power-off." 645 SYNTAX INTEGER { 646 unknown(1), 647 persistent(2), 648 transient(3) 649 } 651 VirtualMachineCpuIndex ::= TEXTUAL-CONVENTION 652 DISPLAY-HINT "d" 653 STATUS current 654 DESCRIPTION 655 "A unique value, greater than zero, identifying a 656 virtual CPU assigned to a virtual machine. The value 657 for each virtual CPU must remain constant at least from 658 one re-initialization of the virtual machine to the next 659 re-initialization." 660 SYNTAX Integer32 (1..2147483647) 662 VirtualMachineStorageIndex ::= TEXTUAL-CONVENTION 663 DISPLAY-HINT "d" 664 STATUS current 665 DESCRIPTION 666 "A unique value, greater than zero, identifying a 667 virtual storage device allocated to a virtual machine. 668 The value for each virtual storage device must remain 669 constant at least from one re-initialization of the 670 virtual machine to the next re-initialization." 671 SYNTAX Integer32 (1..2147483647) 673 VirtualMachineStorageSourceType ::= TEXTUAL-CONVENTION 674 STATUS current 675 DESCRIPTION 676 "The source type of a virtual storage device: 678 unknown(1) The source type is unknown, e.g., because 679 the implementation failed to obtain the 680 media type from the hypervisor. 682 other(2) The source type is other than those 683 defined in this conversion. 685 block(3) The source type is a block device. 687 raw(4) The source type is a raw-formatted file. 689 sparse(5) The source type is a sparse file. 691 network(6) The source type is a network device." 692 SYNTAX INTEGER { 693 unknown(1), 694 other(2), 695 block(3), 696 raw(4), 697 sparse(5), 698 network(6) 699 } 701 VirtualMachineStorageAccess ::= TEXTUAL-CONVENTION 702 STATUS current 703 DESCRIPTION 704 "The access permission of a virtual storage: 706 readwrite(1) The virtual storage is a read-write 707 device. 709 readonly(2) The virtual storage is a read-only 710 device." 711 SYNTAX INTEGER { 712 readwrite(1), 713 readonly(2) 714 } 716 VirtualMachineStorageMediaType ::= TEXTUAL-CONVENTION 717 STATUS current 718 DESCRIPTION 719 "The media type of a virtual storage device: 721 unknown(1) The media type is unknown, e.g., because 722 the implementation failed to obtain the 723 media type from the hypervisor. 725 other(2) The media type is other than those 726 defined in this conversion. 728 hardDisk(3) The media type is hard disk. 730 opticalDisk(4) The media type is optical disk." 731 SYNTAX INTEGER { 732 other(1), 733 unknown(2), 734 hardDisk(3), 735 opticalDisk(4) 736 } 738 VirtualMachineNetworkIndex ::= TEXTUAL-CONVENTION 739 DISPLAY-HINT "d" 740 STATUS current 741 DESCRIPTION 742 "A unique value, greater than zero, identifying a 743 virtual network interface allocated to a virtual 744 machine. The value for each virtual network interface 745 must remain constant at least from one re-initialization 746 of the virtual machine to the next re-initialization." 747 SYNTAX Integer32 (1..2147483647) 749 VirtualMachineList ::= TEXTUAL-CONVENTION 750 DISPLAY-HINT "1x" 751 STATUS current 752 DESCRIPTION 753 "Each octet within this value specifies a set of eight 754 Virtual Machine vmIndex, with the first octet specifying 755 Virtual Machine 1 through 8, the second octet specifying 756 Virtual Machine 9 through 16, etc. Within each octet, 757 the most significant bit represents the lowest numbered 758 vmIndex, and the least significant bit represents the 759 highest numbered vmIndex. Thus, each Virtual Machine of 760 the host is represented by a single bit within the value 761 of this object. If that bit has a value of '1', then 762 that Virtual Machine is included in the set of Virtual 763 Machines; the Virtual Machine is not included if its bit 764 has a value of '0'." 765 SYNTAX OCTET STRING 767 -- The hypervisor group 768 -- 769 -- A collection of objects common to all hypervisors. 770 -- 771 vmHypervisor OBJECT IDENTIFIER ::= { vmObjects 1 } 773 vmHvSoftware OBJECT-TYPE 774 SYNTAX SnmpAdminString (SIZE (0..255)) 775 MAX-ACCESS read-only 776 STATUS current 777 DESCRIPTION 778 "A textual description of the hypervisor software. This 779 value should not include its version, and it should be 780 included in `vmHvVersion'." 781 ::= { vmHypervisor 1 } 783 vmHvVersion OBJECT-TYPE 784 SYNTAX SnmpAdminString (SIZE (0..255)) 785 MAX-ACCESS read-only 786 STATUS current 787 DESCRIPTION 788 "A textual description of the version of the hypervisor 789 software." 790 ::= { vmHypervisor 2 } 792 vmHvObjectID OBJECT-TYPE 793 SYNTAX OBJECT IDENTIFIER 794 MAX-ACCESS read-only 795 STATUS current 796 DESCRIPTION 797 "The vendor's authoritative identification of the 798 hypervisor software contained in the entity. This value 799 is allocated within the SMI enterprises 800 subtree (1.3.6.1.4.1). Note that this is different from 801 sysObjectID in the SNMPv2-MIB [RFC3418] because 802 sysObjectID is not the identification of the hypervisor 803 software but the device, firmware, or management 804 operating system." 805 ::= { vmHypervisor 3 } 807 vmHvUpTime OBJECT-TYPE 808 SYNTAX TimeTicks 809 MAX-ACCESS read-only 810 STATUS current 811 DESCRIPTION 812 "The time (in centi-seconds) since the hypervisor was 813 last re-initialized. Note that this is different from 814 sysUpTime in the SNMPv2-MIB [RFC3418] and hrSystemUptime 815 in the HOST-RESOURCES-MIB [RFC2790] because sysUpTime is 816 the uptime of the network management portion of the 817 system, and hrSystemUptime is the uptime of the 818 management operating system but not the hypervisor 819 software." 820 ::= { vmHypervisor 4 } 822 -- The virtual machine information 823 -- 824 -- A collection of objects common to all virtual machines. 825 -- 826 vmNumber OBJECT-TYPE 827 SYNTAX Integer32 (0..2147483647) 828 MAX-ACCESS read-only 829 STATUS current 830 DESCRIPTION 831 "The number of virtual machines (regardless of their 832 current state) present on this hypervisor." 833 ::= { vmObjects 2 } 835 vmTableLastChange OBJECT-TYPE 836 SYNTAX TimeTicks 837 MAX-ACCESS read-only 838 STATUS current 839 DESCRIPTION 840 "The value of vmHvUpTime at the time of the last creation 841 or deletion of an entry in the vmTable." 842 ::= { vmObjects 3 } 844 vmTable OBJECT-TYPE 845 SYNTAX SEQUENCE OF VmEntry 846 MAX-ACCESS not-accessible 847 STATUS current 848 DESCRIPTION 849 "A list of virtual machine entries. The number of 850 entries is given by the value of vmNumber." 851 ::= { vmObjects 4 } 853 vmEntry OBJECT-TYPE 854 SYNTAX VmEntry 855 MAX-ACCESS not-accessible 856 STATUS current 857 DESCRIPTION 858 "An entry containing management information applicable 859 to a particular virtual machine." 860 INDEX { vmIndex } 861 ::= { vmTable 1 } 863 VmEntry ::= 864 SEQUENCE { 865 vmIndex VirtualMachineIndex, 866 vmName SnmpAdminString, 867 vmUUID UUIDorZero, 868 vmOSType SnmpAdminString, 869 vmAdminState VirtualMachineAdminState, 870 vmOperState VirtualMachineOperState, 871 vmAutoStart VirtualMachineAutoStart, 872 vmPersistent VirtualMachinePersistent, 873 vmCurCpuNumber Integer32, 874 vmMinCpuNumber Integer32, 875 vmMaxCpuNumber Integer32, 876 vmMemUnit Integer32, 877 vmCurMem Integer32, 878 vmMinMem Integer32, 879 vmMaxMem Integer32, 880 vmUpTime TimeTicks, 881 vmCpuTime Counter64 882 } 884 vmIndex OBJECT-TYPE 885 SYNTAX VirtualMachineIndex 886 MAX-ACCESS not-accessible 887 STATUS current 888 DESCRIPTION 889 "A unique value, greater than zero, identifying the 890 virtual machine. The value assigned to a given Virtual 891 machine may not persist across a reboot. A command 892 generator must use the vmUUID to identify a given 893 Virtual Machine of interest." 894 ::= { vmEntry 1 } 896 vmName OBJECT-TYPE 897 SYNTAX SnmpAdminString (SIZE (0..255)) 898 MAX-ACCESS read-only 899 STATUS current 900 DESCRIPTION 901 "A textual name of the virtual machine." 902 ::= { vmEntry 2 } 904 vmUUID OBJECT-TYPE 905 SYNTAX UUIDorZero 906 MAX-ACCESS read-only 907 STATUS current 908 DESCRIPTION 909 "The virtual machine's 128-bit UUID or the zero-length 910 string when a UUID is not available. The UUID if set 911 must uniquely identify a VM from all other Virtual 912 Machines in an administrative region. (*mrm -note- 913 explain case when this value may be empty." 914 ::= { vmEntry 3 } 916 vmOSType OBJECT-TYPE 917 SYNTAX SnmpAdminString (SIZE (0..255)) 918 MAX-ACCESS read-only 919 STATUS current 920 DESCRIPTION 921 "A textual description containing operating system 922 information installed on the virtual machine. This 923 value corresponds to the operating system the hypervisor 924 assumes to be running when the virtual machine is 925 started. This may differ from the actual operating 926 system in case the virtual machine boots into a 927 different operating system." 928 ::= { vmEntry 4 } 930 vmAdminState OBJECT-TYPE 931 SYNTAX VirtualMachineAdminState 932 MAX-ACCESS read-write 933 STATUS current 934 DESCRIPTION 935 "The administrative power state of the virtual machine. 936 Note that a virtual machine is supposed to be resumed 937 when vmAdminState of the virtual machine is changed from 938 pause(3) to on(1)." 939 ::= { vmEntry 5 } 941 vmOperState OBJECT-TYPE 942 SYNTAX VirtualMachineOperState 943 MAX-ACCESS read-only 944 STATUS current 945 DESCRIPTION 946 "The current operational state of the virtual machine." 947 ::= { vmEntry 6 } 949 vmAutoStart OBJECT-TYPE 950 SYNTAX VirtualMachineAutoStart 951 MAX-ACCESS read-write 952 STATUS current 953 DESCRIPTION 954 "The autostart configuration of the virtual machine." 955 ::= { vmEntry 7 } 957 vmPersistent OBJECT-TYPE 958 SYNTAX VirtualMachinePersistent 959 MAX-ACCESS read-only 960 STATUS current 961 DESCRIPTION 962 "This value indicates whether the virtual machine has a 963 persistent configuration which means the virtual machine 964 will still exist after shutting down." 965 ::= { vmEntry 8 } 967 vmCurCpuNumber OBJECT-TYPE 968 SYNTAX Integer32 (0..2147483647) 969 MAX-ACCESS read-only 970 STATUS current 971 DESCRIPTION 972 "The number of virtual CPUs currently assigned to the 973 virtual machine." 974 ::= { vmEntry 9 } 976 vmMinCpuNumber OBJECT-TYPE 977 SYNTAX Integer32 (-1|0..2147483647) 978 MAX-ACCESS read-write 979 STATUS current 980 DESCRIPTION 981 "The minimum number of virtual CPUs that are assigned to 982 the virtual machine when it is in a power-on state. The 983 value -1 indicates that there is no hard boundary for 984 the minimum number of virtual CPUs. Changes to this 985 object may not persist across restarts of the 986 hypervisor." 987 ::= { vmEntry 10 } 989 vmMaxCpuNumber OBJECT-TYPE 990 SYNTAX Integer32 (-1|0..2147483647) 991 MAX-ACCESS read-write 992 STATUS current 993 DESCRIPTION 994 "The maximum number of virtual CPUs that are assigned to 995 the virtual machine when it is in a power-on state. The 996 value -1 indicates that there is no limit. Changes to 997 this object may not persist across restarts of the 998 hypervisor." 999 ::= { vmEntry 11 } 1001 vmMemUnit OBJECT-TYPE 1002 SYNTAX Integer32 (1..2147483647) 1003 MAX-ACCESS read-only 1004 STATUS current 1005 DESCRIPTION 1006 "The multiplication unit for vmCurMem, vmMinMem, and 1007 vmMaxMem. For example, when this value is 1024, the 1008 memory size unit for vmCurMem, vmMinMem, and vmMaxMem is 1009 KiB." 1010 ::= { vmEntry 12 } 1012 vmCurMem OBJECT-TYPE 1013 SYNTAX Integer32 (0..2147483647) 1014 MAX-ACCESS read-only 1015 STATUS current 1016 DESCRIPTION 1017 "The current memory size currently allocated to the 1018 virtual memory module in the unit designated by 1019 vmMemUnit." 1020 ::= { vmEntry 13 } 1022 vmMinMem OBJECT-TYPE 1023 SYNTAX Integer32 (-1|0..2147483647) 1024 MAX-ACCESS read-write 1025 STATUS current 1026 DESCRIPTION 1027 "The minimum memory size defined to the virtual machine 1028 in the unit designated by vmMemUnit. The value -1 1029 indicates that there is no hard boundary for the minimum 1030 memory size. Changes to this object may not persist 1031 across the restart of the hypervisor." 1032 ::= { vmEntry 14 } 1034 vmMaxMem OBJECT-TYPE 1035 SYNTAX Integer32 (-1|0..2147483647) 1036 MAX-ACCESS read-write 1037 STATUS current 1038 DESCRIPTION 1039 "The maximum memory size defined to the virtual machine 1040 in the unit designated by vmMemUnit. The value -1 1041 indicates that there is no limit. Changes to this 1042 object may not persist across the restart of the 1043 hypervisor." 1044 ::= { vmEntry 15 } 1046 vmUpTime OBJECT-TYPE 1047 SYNTAX TimeTicks 1048 MAX-ACCESS read-only 1049 STATUS current 1050 DESCRIPTION 1051 "The time (in centi-seconds) since the administrative 1052 state of the virtual machine was last changed to power 1053 on." 1054 ::= { vmEntry 16 } 1056 vmCpuTime OBJECT-TYPE 1057 SYNTAX Counter64 1058 UNITS "microsecond" 1059 MAX-ACCESS read-only 1060 STATUS current 1061 DESCRIPTION 1062 "The total CPU time used in microsecond. If the number 1063 of virtual CPUs is larger than 1, vmCpuTime may exceed 1064 real time." 1065 ::= { vmEntry 17 } 1067 -- The virtual CPU on each virtual machines 1068 vmCpuTable OBJECT-TYPE 1069 SYNTAX SEQUENCE OF VmCpuEntry 1070 MAX-ACCESS not-accessible 1071 STATUS current 1072 DESCRIPTION 1073 "The table of virtual CPUs provided by the hypervisor." 1074 ::= { vmObjects 5 } 1076 vmCpuEntry OBJECT-TYPE 1077 SYNTAX VmCpuEntry 1078 MAX-ACCESS not-accessible 1079 STATUS current 1080 DESCRIPTION 1081 "An entry for one virtual processor assigned to a 1082 virtual machine." 1083 INDEX { vmIndex, vmCpuIndex } 1084 ::= { vmCpuTable 1 } 1086 VmCpuEntry ::= 1087 SEQUENCE { 1088 vmCpuIndex VirtualMachineCpuIndex, 1089 vmCpuCoreTime Counter64 1090 } 1092 vmCpuIndex OBJECT-TYPE 1093 SYNTAX VirtualMachineCpuIndex 1094 MAX-ACCESS not-accessible 1095 STATUS current 1096 DESCRIPTION 1097 "A unique value identifying a virtual CPU assigned to 1098 the virtual machine." 1099 ::= { vmCpuEntry 1 } 1101 vmCpuCoreTime OBJECT-TYPE 1102 SYNTAX Counter64 1103 UNITS "microsecond" 1104 MAX-ACCESS read-only 1105 STATUS current 1106 DESCRIPTION 1107 "The total CPU time used by this virtual CPU in 1108 microsecond." 1109 ::= { vmCpuEntry 2 } 1111 -- The virtual CPU affinity on each virtual machines 1112 vmCpuAffinityTable OBJECT-TYPE 1113 SYNTAX SEQUENCE OF VmCpuAffinityEntry 1114 MAX-ACCESS not-accessible 1115 STATUS current 1116 DESCRIPTION 1117 "A list of CPU affinity entries of a virtual CPU." 1118 ::= { vmObjects 6 } 1120 vmCpuAffinityEntry OBJECT-TYPE 1121 SYNTAX VmCpuAffinityEntry 1122 MAX-ACCESS not-accessible 1123 STATUS current 1124 DESCRIPTION 1125 "An entry containing CPU affinity associated with a 1126 particular virtual machine." 1127 INDEX { vmIndex, vmCpuIndex, vmCpuPhysIndex } 1128 ::= { vmCpuAffinityTable 1 } 1130 VmCpuAffinityEntry ::= 1131 SEQUENCE { 1132 vmCpuPhysIndex Integer32, 1133 vmCpuAffinity Integer32 1134 } 1136 vmCpuPhysIndex OBJECT-TYPE 1137 SYNTAX Integer32 (1..2147483647) 1138 MAX-ACCESS not-accessible 1139 STATUS current 1140 DESCRIPTION 1141 "A value identifying a physical CPU on the hypervisor. 1142 On systems implementing the HOST-RESOURCES-MIB, the 1143 value must be the same value that is used as the index 1144 in the hrProcessorTable (hrDeviceIndex)." 1145 ::= { vmCpuAffinityEntry 2 } 1147 vmCpuAffinity OBJECT-TYPE 1148 SYNTAX INTEGER { 1149 unknown(0), -- unknown 1150 enable(1), -- enabled 1151 disable(2) -- disabled 1152 } 1153 MAX-ACCESS read-write 1154 STATUS current 1155 DESCRIPTION 1156 "The CPU affinity of this virtual CPU to the physical 1157 CPU represented by `vmCpuPhysIndex'." 1158 ::= { vmCpuAffinityEntry 3 } 1160 -- The virtual storage devices on each virtual machine. This 1161 -- document defines some overlapped objects with hrStorage in 1162 -- HOST-RESOURCES-MIB [RFC2790], because virtual resources shall be 1163 -- allocated from the hypervisor's resources, which is the `host 1164 -- resources' 1165 vmStorageTable OBJECT-TYPE 1166 SYNTAX SEQUENCE OF VmStorageEntry 1167 MAX-ACCESS not-accessible 1168 STATUS current 1169 DESCRIPTION 1170 "The conceptual table of virtual storage devices 1171 attached to the virtual machine." 1172 ::= { vmObjects 7 } 1174 vmStorageEntry OBJECT-TYPE 1175 SYNTAX VmStorageEntry 1176 MAX-ACCESS not-accessible 1177 STATUS current 1178 DESCRIPTION 1179 "An entry for one virtual storage device attached to the 1180 virtual machine." 1181 INDEX { vmStorageVmIndex, vmStorageIndex } 1182 ::= { vmStorageTable 1 } 1184 VmStorageEntry ::= 1185 SEQUENCE { 1186 vmStorageVmIndex VirtualMachineIndexOrZero, 1187 vmStorageIndex VirtualMachineStorageIndex, 1188 vmStorageParent Integer32, 1189 vmStorageSourceType VirtualMachineStorageSourceType, 1190 vmStorageSourceTypeString 1191 SnmpAdminString, 1192 vmStorageResourceID SnmpAdminString, 1193 vmStorageAccess VirtualMachineStorageAccess, 1194 vmStorageMediaType VirtualMachineStorageMediaType, 1195 vmStorageMediaTypeString 1196 SnmpAdminString, 1197 vmStorageSizeUnit Integer32, 1198 vmStorageDefinedSize Integer32, 1199 vmStorageAllocatedSize Integer32, 1200 vmStorageReadIOs Counter64, 1201 vmStorageWriteIOs Counter64 1202 } 1204 vmStorageVmIndex OBJECT-TYPE 1205 SYNTAX VirtualMachineIndexOrZero 1206 MAX-ACCESS not-accessible 1207 STATUS current 1208 DESCRIPTION 1209 "This value identifies the virtual machine (guest) this 1210 storage device has been allocated to. The value zero 1211 indicates that the storage device is currently not 1212 allocated to any virtual machines." 1213 ::= { vmStorageEntry 1 } 1215 vmStorageIndex OBJECT-TYPE 1216 SYNTAX VirtualMachineStorageIndex 1217 MAX-ACCESS not-accessible 1218 STATUS current 1219 DESCRIPTION 1220 "A unique value identifying a virtual storage device 1221 allocated to the virtual machine." 1222 ::= { vmStorageEntry 2 } 1224 vmStorageParent OBJECT-TYPE 1225 SYNTAX Integer32 (0..2147483647) 1226 MAX-ACCESS read-only 1227 STATUS current 1228 DESCRIPTION 1229 "The value of hrStorageIndex which is the parent (i.e., 1230 physical) device of this virtual device on systems 1231 implementing the HOST-RESOURCES-MIB. The value zero 1232 denotes this virtual device is not any child represented 1233 in the hrStorageTable." 1234 ::= { vmStorageEntry 3 } 1236 vmStorageSourceType OBJECT-TYPE 1237 SYNTAX VirtualMachineStorageSourceType 1238 MAX-ACCESS read-only 1239 STATUS current 1240 DESCRIPTION 1241 "The source type of the virtual storage device." 1242 ::= { vmStorageEntry 4 } 1244 vmStorageSourceTypeString OBJECT-TYPE 1245 SYNTAX SnmpAdminString (SIZE (0..255)) 1246 MAX-ACCESS read-only 1247 STATUS current 1248 DESCRIPTION 1249 "A (detailed) textual string of the source type of the 1250 virtual storage device. For example, this represents 1251 the specific format name of the sparse file." 1252 ::= { vmStorageEntry 5 } 1254 vmStorageResourceID OBJECT-TYPE 1255 SYNTAX SnmpAdminString (SIZE (0..255)) 1256 MAX-ACCESS read-only 1257 STATUS current 1258 DESCRIPTION 1259 "A textual string that represents the resource 1260 identifier of the virtual storage. For example, this 1261 contains the path to the disk image file that 1262 corresponds to the virtual storage." 1263 ::= { vmStorageEntry 6 } 1265 vmStorageAccess OBJECT-TYPE 1266 SYNTAX VirtualMachineStorageAccess 1267 MAX-ACCESS read-only 1268 STATUS current 1269 DESCRIPTION 1270 "The access permission of the virtual storage device." 1271 ::= { vmStorageEntry 7 } 1273 vmStorageMediaType OBJECT-TYPE 1274 SYNTAX VirtualMachineStorageMediaType 1275 MAX-ACCESS read-only 1276 STATUS current 1277 DESCRIPTION 1278 "The media type of the virtual storage device." 1279 ::= { vmStorageEntry 8 } 1281 vmStorageMediaTypeString OBJECT-TYPE 1282 SYNTAX SnmpAdminString (SIZE (0..255)) 1283 MAX-ACCESS read-only 1284 STATUS current 1285 DESCRIPTION 1286 "A (detailed) textual string of the virtual storage 1287 media. For example, this represents the specific driver 1288 name of the emulated media such as `IDE' and `SCSI'." 1289 ::= { vmStorageEntry 9 } 1291 vmStorageSizeUnit OBJECT-TYPE 1292 SYNTAX Integer32 (1..2147483647) 1293 MAX-ACCESS read-only 1294 STATUS current 1295 DESCRIPTION 1296 "The multiplication unit for vmStorageDefinedSize and 1297 vmStorageAllocatedSize. For example, when this value is 1298 1048576, the storage size unit for vmStorageDefinedSize 1299 and vmStorageAllocatedSize is MiB." 1300 ::= { vmStorageEntry 10 } 1302 vmStorageDefinedSize OBJECT-TYPE 1303 SYNTAX Integer32 (-1|0..2147483647) 1304 MAX-ACCESS read-only 1305 STATUS current 1306 DESCRIPTION 1307 "The defined virtual storage size defined in the unit 1308 designated by vmStorageSizeUnit. If this information is 1309 not available, this value shall be -1." 1310 ::= { vmStorageEntry 11 } 1312 vmStorageAllocatedSize OBJECT-TYPE 1313 SYNTAX Integer32 (-1|0..2147483647) 1314 MAX-ACCESS read-only 1315 STATUS current 1316 DESCRIPTION 1317 "The storage size allocated to the virtual storage from 1318 a physical storage in the unit designated by 1319 vmStorageSizeUnit. When the virtual storage is block 1320 device or raw file, this value and vmStorageDefinedSize 1321 are supposed to equal. This value must not be different 1322 from vmStorageDefinedSize when vmStorageSourceType is 1323 `block' or `raw'. If this information is not available, 1324 this value shall be -1." 1325 ::= { vmStorageEntry 12 } 1327 vmStorageReadIOs OBJECT-TYPE 1328 SYNTAX Counter64 1329 MAX-ACCESS read-only 1330 STATUS current 1331 DESCRIPTION 1332 "The number of read I/O requests." 1333 ::= { vmStorageEntry 13 } 1335 vmStorageWriteIOs OBJECT-TYPE 1336 SYNTAX Counter64 1337 MAX-ACCESS read-only 1338 STATUS current 1339 DESCRIPTION 1340 "The number of write I/O requests." 1341 ::= { vmStorageEntry 14 } 1343 -- The virtual network interfaces on each virtual machine. 1344 vmNetworkTable OBJECT-TYPE 1345 SYNTAX SEQUENCE OF VmNetworkEntry 1346 MAX-ACCESS not-accessible 1347 STATUS current 1348 DESCRIPTION 1349 "The conceptual table of virtual network interfaces 1350 attached to the virtual machine." 1351 ::= { vmObjects 8 } 1353 vmNetworkEntry OBJECT-TYPE 1354 SYNTAX VmNetworkEntry 1355 MAX-ACCESS not-accessible 1356 STATUS current 1357 DESCRIPTION 1358 "An entry for one virtual storage device attached to the 1359 virtual machine." 1360 INDEX { vmIndex, vmNetworkIndex } 1361 ::= { vmNetworkTable 1 } 1363 VmNetworkEntry ::= 1364 SEQUENCE { 1365 vmNetworkIndex VirtualMachineNetworkIndex, 1366 vmNetworkIfIndex InterfaceIndexOrZero, 1367 vmNetworkParent InterfaceIndexOrZero, 1368 vmNetworkModel SnmpAdminString, 1369 vmNetworkPhysAddress PhysAddress 1370 } 1372 vmNetworkIndex OBJECT-TYPE 1373 SYNTAX VirtualMachineNetworkIndex 1374 MAX-ACCESS not-accessible 1375 STATUS current 1376 DESCRIPTION 1377 "A unique value identifying a virtual network interface 1378 allocated to the virtual machine." 1379 ::= { vmNetworkEntry 1 } 1381 vmNetworkIfIndex OBJECT-TYPE 1382 SYNTAX InterfaceIndexOrZero 1383 MAX-ACCESS read-only 1384 STATUS current 1385 DESCRIPTION 1386 "The value of ifIndex which corresponds to this virtual 1387 network interface. If this device is not represented in 1388 the ifTable, then this value shall be zero." 1389 ::= { vmNetworkEntry 2 } 1391 vmNetworkParent OBJECT-TYPE 1392 SYNTAX InterfaceIndexOrZero 1393 MAX-ACCESS read-only 1394 STATUS current 1395 DESCRIPTION 1396 "The value of ifIndex which corresponds to the parent 1397 (i.e., physical) device of this virtual device on. The 1398 value zero denotes this virtual device is not any child 1399 represented in the ifTable." 1400 ::= { vmNetworkEntry 3 } 1402 vmNetworkModel OBJECT-TYPE 1403 SYNTAX SnmpAdminString (SIZE (0..255)) 1404 MAX-ACCESS read-only 1405 STATUS current 1406 DESCRIPTION 1407 "A textual string containing the (emulated) model of 1408 virtual network interface. For example, this value is 1409 `virtio' when the emulation driver model is virtio." 1410 ::= { vmNetworkEntry 4 } 1412 vmNetworkPhysAddress OBJECT-TYPE 1413 SYNTAX PhysAddress 1414 MAX-ACCESS read-only 1415 STATUS current 1416 DESCRIPTION 1417 "The MAC address of the virtual network interface." 1418 ::= { vmNetworkEntry 5 } 1420 -- Notification definitions: 1422 vmPerVMNotificationsEnabled OBJECT-TYPE 1423 SYNTAX TruthValue 1424 MAX-ACCESS read-write 1425 STATUS current 1426 DESCRIPTION 1427 "Indicates if notification generator will send 1428 notifications per VM." 1429 ::= { vmObjects 9 } 1431 vmBulkNotificationsEnabled OBJECT-TYPE 1432 SYNTAX TruthValue 1433 MAX-ACCESS read-write 1434 STATUS current 1435 DESCRIPTION 1436 "Indicates if notification generator will send 1437 notifications per set of VMs." 1438 ::= { vmObjects 10 } 1440 vmAffectedVMs OBJECT-TYPE 1441 SYNTAX VirtualMachineList 1442 MAX-ACCESS accessible-for-notify 1443 STATUS current 1444 DESCRIPTION 1445 "A complete list of Virtual Machines whose state has 1446 changed. This object is the only object sent with bulk 1447 notifications." 1448 ::= { vmObjects 11 } 1450 vmRunning NOTIFICATION-TYPE 1451 OBJECTS { 1452 vmName, 1453 vmUUID, 1454 vmOperState 1455 } 1456 STATUS current 1457 DESCRIPTION 1458 "This notification is generated when the operational 1459 state of a virtual machine has been changed to 1460 `running' from some other state. The other state is 1461 indicated by the included value of vmOperState." 1462 ::= { vmNotifications 1 } 1464 vmShutdown NOTIFICATION-TYPE 1465 OBJECTS { 1466 vmName, 1467 vmUUID, 1468 vmOperState 1469 } 1470 STATUS current 1471 DESCRIPTION 1472 "This notification is generated when the operational 1473 state of a virtual machine has been changed to 1474 `shutdown' from some other state. The other state is 1475 indicated by the included value of vmOperState." 1476 ::= { vmNotifications 2 } 1478 vmPaused NOTIFICATION-TYPE 1479 OBJECTS { 1480 vmName, 1481 vmUUID, 1482 vmOperState 1483 } 1484 STATUS current 1485 DESCRIPTION 1486 "This notification is generated when the operational 1487 state of a virtual machine has been changed to 1488 `paused' from some other state. The other state is 1489 indicated by the included value of vmOperState." 1490 ::= { vmNotifications 3 } 1492 vmSuspended NOTIFICATION-TYPE 1493 OBJECTS { 1494 vmName, 1495 vmUUID, 1496 vmOperState 1497 } 1499 STATUS current 1500 DESCRIPTION 1501 "This notification is generated when the operational 1502 state of a virtual machine has been changed to 1503 `suspended' from some other state. The other state is 1504 indicated by the included value of vmOperState." 1505 ::= { vmNotifications 4 } 1507 vmCrashed NOTIFICATION-TYPE 1508 OBJECTS { 1509 vmName, 1510 vmUUID, 1511 vmOperState 1512 } 1513 STATUS current 1514 DESCRIPTION 1515 "This notification is generated when a virtual machine 1516 has been crashed. The previos state of the virtual 1517 machine is indicated by the included value of 1518 vmOperState." 1519 ::= { vmNotifications 5 } 1521 vmDeleted NOTIFICATION-TYPE 1522 OBJECTS { 1523 vmName, 1524 vmUUID, 1525 vmOperState, 1526 vmPersistent 1527 } 1528 STATUS current 1529 DESCRIPTION 1530 "This notification is generated when a virtual machine 1531 has been deleted. The prior state of the virtual 1532 machine is indicated by the included value of 1533 vmOperState." 1534 ::= { vmNotifications 6 } 1536 vmBulkRunning NOTIFICATION-TYPE 1537 OBJECTS { 1538 vmAffectedVMs 1539 } 1540 STATUS current 1541 DESCRIPTION 1542 "This notification is generated when the operational 1543 state of one or more virtual machine has been changed to 1544 `running' from a all prior states except for 'running.' 1545 Management stations are encouraged to subsequently 1546 poll the subset of VMs of interest for vmOperState." 1548 ::= { vmNotifications 7 } 1550 vmBulkShutdown NOTIFICATION-TYPE 1551 OBJECTS { 1552 vmAffectedVMs 1553 } 1554 STATUS current 1555 DESCRIPTION 1556 "This notification is generated when the operational 1557 state of one or more virtual machine has been changed to 1558 `shutdown' from a state other than `shutdown`. 1559 Management stations are encouraged to subsequently poll 1560 the subset of VMs of interest for vmOperState." 1561 ::= { vmNotifications 8 } 1563 vmBulkPaused NOTIFICATION-TYPE 1564 OBJECTS { 1565 vmAffectedVMs 1566 } 1567 STATUS current 1568 DESCRIPTION 1569 "This notification is generated when the operational 1570 state of one or more virtual machines have been changed 1571 to `paused' from a state other than `paused.` 1572 Management stations are encouraged to subsequently poll 1573 the subset of VMs of interest for vmOperState." 1574 ::= { vmNotifications 9 } 1576 vmBulkSuspended NOTIFICATION-TYPE 1577 OBJECTS { 1578 vmAffectedVMs 1579 } 1580 STATUS current 1581 DESCRIPTION 1582 "This notification is generated when the operational 1583 state of one or more virtual machines have been changed 1584 to `suspended' from a state other than 'suspended.' 1585 Management stations are encouraged to subsequently poll 1586 the subset of VMs of interest for vmOperState." 1587 ::= { vmNotifications 10 } 1589 vmBulkCrashed NOTIFICATION-TYPE 1590 OBJECTS { 1591 vmAffectedVMs 1592 } 1593 STATUS current 1594 DESCRIPTION 1595 "This notification is generated when one or more virtual 1596 machines have been crashed. Management stations are 1597 encouraged to subsequently poll the subset of VMs of 1598 interest for vmOperState." 1599 ::= { vmNotifications 11 } 1601 vmBulkDeleted NOTIFICATION-TYPE 1602 OBJECTS { 1603 vmAffectedVMs 1604 } 1605 STATUS current 1606 DESCRIPTION 1607 "This notification is generated when one or more virtual 1608 machines have been deleted. Management stations are 1609 encouraged to subsequently poll the subset of VMs of 1610 interest for vmOperState." 1611 ::= { vmNotifications 12 } 1613 -- Compliance definitions: 1614 vmGroups OBJECT IDENTIFIER ::= { vmConformance 1 } 1615 vmCompliances OBJECT IDENTIFIER ::= { vmConformance 2 } 1617 vmFullCompliances MODULE-COMPLIANCE 1618 STATUS current 1619 DESCRIPTION 1620 "Compliance statement for implementations supporting 1621 read/write access, according to the object definitions." 1622 MODULE -- this module 1623 MANDATORY-GROUPS { 1624 vmHypervisorGroup, 1625 vmVirtualMachineGroup, 1626 vmCpuGroup, 1627 vmCpuAffinityGroup, 1628 vmStorageGroup, 1629 vmNetworkGroup 1630 } 1631 GROUP vmPerVMNotificationOptionalGroup 1632 DESCRIPTION 1633 "Support for per-VM notifications is optional. If not 1634 implemented then vmPerVMNotificationsEnabled must report 1635 false(2)." 1636 GROUP vmBulkNotificationsVariablesGroup 1637 DESCRIPTION 1638 "Necessary only if vmPerVMNotificationOptionalGroup is 1639 implemented." 1640 GROUP vmBulkNotificationOptionalGroup 1641 DESCRIPTION 1642 "Support for bulk notifications is optional. If not 1643 implemented then vmBulkNotificationsEnabled must report 1644 false(2)." 1646 ::= { vmCompliances 1 } 1648 vmReadOnlyCompliances MODULE-COMPLIANCE 1649 STATUS current 1650 DESCRIPTION 1651 "Compliance statement for implementations supporting 1652 only readonly access." 1653 MODULE -- this module 1654 MANDATORY-GROUPS { 1655 vmHypervisorGroup, 1656 vmVirtualMachineGroup, 1657 vmCpuGroup, 1658 vmCpuAffinityGroup, 1659 vmStorageGroup, 1660 vmNetworkGroup 1661 } 1663 OBJECT vmAdminState 1664 MIN-ACCESS read-only 1665 DESCRIPTION 1666 "Write access is not required." 1668 OBJECT vmAutoStart 1669 MIN-ACCESS read-only 1670 DESCRIPTION 1671 "Write access is not required." 1673 OBJECT vmMinCpuNumber 1674 MIN-ACCESS read-only 1675 DESCRIPTION 1676 "Write access is not required." 1678 OBJECT vmMaxCpuNumber 1679 MIN-ACCESS read-only 1680 DESCRIPTION 1681 "Write access is not required." 1683 OBJECT vmMinMem 1684 MIN-ACCESS read-only 1685 DESCRIPTION 1686 "Write access is not required." 1688 OBJECT vmMaxMem 1689 MIN-ACCESS read-only 1690 DESCRIPTION 1691 "Write access is not required." 1693 OBJECT vmCpuAffinity 1694 MIN-ACCESS read-only 1695 DESCRIPTION 1696 "Write access is not required." 1698 OBJECT vmPerVMNotificationsEnabled 1699 MIN-ACCESS read-only 1700 DESCRIPTION 1701 "Write access is not required." 1703 OBJECT vmBulkNotificationsEnabled 1704 MIN-ACCESS read-only 1705 DESCRIPTION 1706 "Write access is not required." 1707 ::= { vmCompliances 2 } 1709 vmHypervisorGroup OBJECT-GROUP 1710 OBJECTS { 1711 vmHvSoftware, 1712 vmHvVersion, 1713 vmHvObjectID, 1714 vmHvUpTime, 1715 vmNumber, 1716 vmTableLastChange, 1717 vmPerVMNotificationsEnabled, 1718 vmBulkNotificationsEnabled 1719 } 1720 STATUS current 1721 DESCRIPTION 1722 "A collection of objects providing insight into the 1723 hypervisor itself." 1724 ::= { vmGroups 1 } 1726 vmVirtualMachineGroup OBJECT-GROUP 1727 OBJECTS { 1728 -- vmIndex 1729 vmName, 1730 vmUUID, 1731 vmOSType, 1732 vmAdminState, 1733 vmOperState, 1734 vmAutoStart, 1735 vmPersistent, 1736 vmCurCpuNumber, 1737 vmMinCpuNumber, 1738 vmMaxCpuNumber, 1739 vmMemUnit, 1740 vmCurMem, 1741 vmMinMem, 1742 vmMaxMem, 1743 vmUpTime, 1744 vmCpuTime 1745 } 1746 STATUS current 1747 DESCRIPTION 1748 "A collection of objects providing insight into the 1749 virtual machines) controlled by a hypervisor." 1750 ::= { vmGroups 2 } 1752 vmCpuGroup OBJECT-GROUP 1753 OBJECTS { 1754 -- vmCpuIndex, 1755 vmCpuCoreTime 1756 } 1757 STATUS current 1758 DESCRIPTION 1759 "A collection of objects providing insight into the 1760 virtual machines) controlled by a hypervisor." 1761 ::= { vmGroups 3 } 1763 vmCpuAffinityGroup OBJECT-GROUP 1764 OBJECTS { 1765 -- vmCpuPhysIndex, 1766 vmCpuAffinity 1767 } 1768 STATUS current 1769 DESCRIPTION 1770 "A collection of objects providing insight into the 1771 virtual machines) controlled by a hypervisor." 1772 ::= { vmGroups 4 } 1774 vmStorageGroup OBJECT-GROUP 1775 OBJECTS { 1776 -- vmStorageVmIndex, 1777 -- vmStorageIndex, 1778 vmStorageParent, 1779 vmStorageSourceType, 1780 vmStorageSourceTypeString, 1781 vmStorageResourceID, 1782 vmStorageAccess, 1783 vmStorageMediaType, 1784 vmStorageMediaTypeString, 1785 vmStorageSizeUnit, 1786 vmStorageDefinedSize, 1787 vmStorageAllocatedSize, 1788 vmStorageReadIOs, 1789 vmStorageWriteIOs 1790 } 1791 STATUS current 1792 DESCRIPTION 1793 "A collection of objects providing insight into the 1794 virtual storage devices controlled by a hypervisor." 1795 ::= { vmGroups 5 } 1797 vmNetworkGroup OBJECT-GROUP 1798 OBJECTS { 1799 -- vmNetworkIndex, 1800 vmNetworkIfIndex, 1801 vmNetworkParent, 1802 vmNetworkModel, 1803 vmNetworkPhysAddress 1804 } 1805 STATUS current 1806 DESCRIPTION 1807 "A collection of objects providing insight into the 1808 virtual network interfaces controlled by a hypervisor." 1809 ::= { vmGroups 6 } 1811 vmPerVMNotificationOptionalGroup NOTIFICATION-GROUP 1812 NOTIFICATIONS { 1813 vmRunning, 1814 vmShutdown, 1815 vmPaused, 1816 vmSuspended, 1817 vmCrashed, 1818 vmDeleted 1819 } 1820 STATUS current 1821 DESCRIPTION 1822 "A collection of notifications for per-VM notification 1823 of changes to virtual machine state (vmOperState) as 1824 reported by a hypervisor." 1825 ::= { vmGroups 7 } 1827 vmBulkNotificationsVariablesGroup OBJECT-GROUP 1828 OBJECTS { 1829 vmAffectedVMs 1830 } 1831 STATUS current 1832 DESCRIPTION 1833 "The variables used in vmBulkNotificationOptionalGroup 1834 virtual network interfaces controlled by a hypervisor." 1836 ::= { vmGroups 8 } 1838 vmBulkNotificationOptionalGroup NOTIFICATION-GROUP 1839 NOTIFICATIONS { 1840 vmBulkRunning, 1841 vmBulkShutdown, 1842 vmBulkPaused, 1843 vmBulkSuspended, 1844 vmBulkCrashed, 1845 vmBulkDeleted 1846 } 1847 STATUS current 1848 DESCRIPTION 1849 "A collection of notifications for bulk notification of 1850 changes to virtual machine state (vmOperState) as 1851 reported by a given hypervisor." 1852 ::= { vmGroups 9 } 1854 END 1856 4. IANA Considerations 1858 The MIB module in this document uses the following IANA-assigned 1859 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 1861 Descriptor OBJECT IDENTIFIER value 1862 ---------- ----------------------- 1864 vmMIB { mib-2 TBD } 1866 5. Security Considerations 1868 There are a number of management objects defined in this MIB that 1869 have a MAX-ACCESS clause of read-write and/or read-create. Such 1870 objects may be considered sensitive or vulnerable in some network 1871 environments. The support for SET operations in a non-secure 1872 environment without proper protection can have a negative effect on 1873 hypervisor and virtual machine operations. 1875 There are a number of managed objects in this MIB that may contain 1876 sensitive information. The objects in the vmHvSoftware and 1877 vmHvVersion list information about the hypervisor's software and 1878 version. Some may wish not to disclose to others which software they 1879 are running. Further, an inventory of the running software and 1880 versions may be helpful to an attacker who hopes to exploit software 1881 bugs in certain applications. Moreover, the objects in the vmTable, 1882 vmCpuTable, vmCpuAffinityTable, vmStorageTable and vmNetworkTable 1883 list information about the virtual machines and their virtual 1884 resource allocation. Some may wish not to disclose to others how 1885 many and what virtual machines they are operating. 1887 It is thus important to control even GET access to these objects and 1888 possibly to even encrypt the values of these object when sending them 1889 over the network via SNMP. Not all versions of SNMP provide features 1890 for such a secure environment. 1892 It is recommended that attention be specifically given to 1893 implementing the MAX-ACCESS clause in a number of objects, including 1894 vmAdminState, vmAutoStart, vmMinCpuNumber, vmMaxCpuNumber, vmMinMem, 1895 vmMaxMem, and vmCpuAffinity in scenarios that DO NOT use SNMPv3 1896 strong security (i.e. authentication and encryption). Extreme 1897 caution must be used to minimize the risk of cascading security 1898 vulnerabilities when SNMPv3 strong security is not used. When SNMPv3 1899 strong security is not used, these objects should have access of 1900 read-only, not read-create. 1902 SNMPv1 by itself is not a secure environment. Even if the network 1903 itself is secure (for example by using IPsec), even then, there is no 1904 control as to who on the secure network is allowed to access and GET/ 1905 SET (read/change/create/delete) the objects in this MIB. 1907 It is recommended that the implementers consider the security 1908 features as provided by the SNMPv3 framework. Specifically, the use 1909 of the User-based Security Model [RFC3414] and the View-based Access 1910 Control Model [RFC3415] is recommended. 1912 It is then a customer/user responsibility to ensure that the SNMP 1913 entity giving access to an instance of this MIB, is properly 1914 configured to give access to the objects only to those principals 1915 (users) that have legitimate rights to indeed GET or SET (change/ 1916 create/delete) them. 1918 6. Acknowledgements 1920 The authors like to thank Randy Presuhn and David Black for providing 1921 helpful comments during the development of this specification. 1923 Juergen Schoenwaelder was partly funded by Flamingo, a Network of 1924 Excellence project (ICT-318488) supported by the European Commission 1925 under its Seventh Framework Programme. 1927 7. References 1929 7.1. Normative References 1931 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1932 Requirement Levels", BCP 14, RFC 2119, March 1997. 1934 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1935 Schoenwaelder, Ed., "Structure of Management Information 1936 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 1938 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1939 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 1940 STD 58, RFC 2579, April 1999. 1942 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1943 "Conformance Statements for SMIv2", STD 58, RFC 2580, 1944 April 1999. 1946 [RFC2790] Waldbusser, S. and P. Grillo, "Host Resources MIB", 1947 RFC 2790, March 2000. 1949 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1950 MIB", RFC 2863, June 2000. 1952 [RFC3413] Levi, D., Meyer, P., and B. Stewart, "Simple Network 1953 Management Protocol (SNMP) Applications", STD 62, 1954 RFC 3413, December 2002. 1956 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model 1957 (USM) for version 3 of the Simple Network Management 1958 Protocol (SNMPv3)", STD 62, RFC 3414, December 2002. 1960 [RFC3415] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1961 Access Control Model (VACM) for the Simple Network 1962 Management Protocol (SNMP)", STD 62, RFC 3415, 1963 December 2002. 1965 [RFC3418] Presuhn, R., "Management Information Base (MIB) for the 1966 Simple Network Management Protocol (SNMP)", STD 62, 1967 RFC 3418, December 2002. 1969 [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally 1970 Unique IDentifier (UUID) URN Namespace", RFC 4122, 1971 July 2005. 1973 7.2. Informative References 1975 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 1976 "Introduction and Applicability Statements for Internet- 1977 Standard Management Framework", RFC 3410, December 2002. 1979 Authors' Addresses 1981 Hirochika Asai 1982 The University of Tokyo 1983 7-3-1 Hongo 1984 Bunkyo-ku, Tokyo 113-8656 1985 JP 1987 Phone: +81 3 5841 6748 1988 Email: panda@hongo.wide.ad.jp 1990 Michael MacFaden 1991 VMware Inc. 1993 Email: mrm@vmware.com 1995 Juergen Schoenwaelder 1996 Jacobs University 1997 Campus Ring 1 1998 Bremen 28759 1999 Germany 2001 Email: j.schoenwaelder@jacobs-university.de 2003 Yuji Sekiya 2004 The University of Tokyo 2005 2-11-16 Yayoi 2006 Bunkyo-ku, Tokyo 113-8658 2007 JP 2009 Email: sekiya@wide.ad.jp 2011 Keiichi Shima 2012 IIJ Innovation Institute Inc. 2013 3-13 Kanda-Nishikicho 2014 Chiyoda-ku, Tokyo 101-0054 2015 JP 2017 Email: keiichi@iijlab.net 2018 Tina Tsou 2019 Huawei Technologies (USA) 2020 2330 Central Expressway 2021 Santa Clara CA 95050 2022 USA 2024 Email: tina.tsou.zouting@huawei.com 2026 Cathy Zhou 2027 Huawei Technologies 2028 Bantian, Longgang District 2029 Shenzhen 518129 2030 P.R. China 2032 Email: cathyzhou@huawei.com 2034 Hiroshi Esaki 2035 The University of Tokyo 2036 7-3-1 Hongo 2037 Bunkyo-ku, Tokyo 113-8656 2038 JP 2040 Phone: +81 3 5841 6748 2041 Email: hiroshi@wide.ad.jp