draft-ietf-opsawg-vmm-mib-04.txt   rfc7666.txt 
OPSAWG H. Asai Internet Engineering Task Force (IETF) H. Asai
Internet-Draft Univ. of Tokyo Request for Comments: 7666 Univ. of Tokyo
Intended status: Standards Track M. MacFaden Category: Standards Track M. MacFaden
Expires: February 6, 2016 VMware Inc. ISSN: 2070-1721 VMware Inc.
J. Schoenwaelder J. Schoenwaelder
Jacobs University Jacobs University
K. Shima K. Shima
IIJ Innovation Institute Inc. IIJ Innovation Institute Inc.
T. Tsou T. Tsou
Huawei Technologies (USA) Huawei Technologies (USA)
August 5, 2015 October 2015
Management Information Base for Virtual Machines Controlled by a Management Information Base for Virtual Machines
Hypervisor Controlled by a Hypervisor
draft-ietf-opsawg-vmm-mib-04
Abstract Abstract
This document defines a portion of the Management Information Base This document defines a portion of the Management Information Base
(MIB) for use with network management protocols in the Internet (MIB) for use with network management protocols in the Internet
community. In particular, this specifies objects for managing community. In particular, this specifies objects for managing
virtual machines controlled by a hypervisor (a.k.a. virtual machine virtual machines controlled by a hypervisor (a.k.a. virtual machine
monitor). monitor).
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This Internet-Draft will expire on February 6, 2016. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7666.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 25 skipping to change at page 2, line 30
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. The Internet-Standard Management Framework . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . 3
3. Overview and Objectives . . . . . . . . . . . . . . . . . . . 3 3. Overview and Objectives . . . . . . . . . . . . . . . . . . . 3
4. Structure of the VM-MIB Module . . . . . . . . . . . . . . . 5 4. Structure of the VM-MIB Module . . . . . . . . . . . . . . . 5
5. Relationship to Other MIB Modules . . . . . . . . . . . . . . 7 5. Relationship to Other MIB Modules . . . . . . . . . . . . . . 7
6. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 8 6. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 8
6.1. VM-MIB . . . . . . . . . . . . . . . . . . . . . . . . . 8 6.1. VM-MIB . . . . . . . . . . . . . . . . . . . . . . . . . 8
6.2. IANA-STORAGE-MEDIA-TYPE-MIB . . . . . . . . . . . . . . . 43 6.2. IANA-STORAGE-MEDIA-TYPE-MIB . . . . . . . . . . . . . . . 43
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 44 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 45
8. Security Considerations . . . . . . . . . . . . . . . . . . . 44 8. Security Considerations . . . . . . . . . . . . . . . . . . . 45
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 46 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 46
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 46 9.1. Normative References . . . . . . . . . . . . . . . . . . 46
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 46 9.2. Informative References . . . . . . . . . . . . . . . . . 47
11.1. Normative References . . . . . . . . . . . . . . . . . . 46 Appendix A. State Transition Table . . . . . . . . . . . . . . . 49
11.2. Informative References . . . . . . . . . . . . . . . . . 48 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 51
Appendix A. State Transition Table . . . . . . . . . . . . . . . 48 Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 50 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 52
1. Introduction 1. Introduction
This document defines a portion of the Management Information Base This document defines a portion of the Management Information Base
(MIB) for use with network management protocols in the Internet (MIB) for use with network management protocols in the Internet
community. In particular, this specifies objects for managing community. In particular, this specifies objects for managing
virtual machines controlled by a hypervisor (a.k.a. virtual machine virtual machines controlled by a hypervisor (a.k.a. virtual machine
monitor). A hypervisor controls multiple virtual machines on a monitor). A hypervisor controls multiple virtual machines on a
single physical machine by allocating resources to each virtual single physical machine by allocating resources to each virtual
machine using virtualization technologies. Therefore, this MIB machine using virtualization technologies. Therefore, this MIB
module contains information on virtual machines and their resources module contains information on virtual machines and their resources
controlled by a hypervisor as well as hypervisor's hardware and controlled by a hypervisor as well as information about a
software information. hypervisor's hardware and software.
The design of this MIB module has been derived from product-specific The design of this MIB module has been derived from product-specific
MIB modules, namely a MIB module for managing guests of the Xen MIB modules -- namely, a MIB module for managing guests of the Xen
hypervisor, a MIB module for managing virtual machines controlled by hypervisor [Xen], a MIB module for managing virtual machines
the VMware hypervisor, and a MIB module using the libvirt programming controlled by the VMware hypervisor [VMware], and a MIB module using
interface to access different hypervisors. However, this MIB module the libvirt programming interface [libvirt] to access different
attempts to generalize the managed objects to support other hypervisors. However, this MIB module attempts to generalize the
implementations of hypervisors. managed objects to support other implementations of hypervisors.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. Managed objects are accessed via a virtual RFC 3410 [RFC3410].
information store, termed the Management Information Base or MIB.
MIB objects are generally accessed through the Simple Network Managed objects are accessed via a virtual information store, termed
Management Protocol (SNMP). Objects in the MIB are defined using the the Management Information Base or MIB. MIB objects are generally
mechanisms defined in the Structure of Management Information (SMI). accessed through the Simple Network Management Protocol (SNMP).
This memo specifies a MIB module that is compliant to the SMIv2, Objects in the MIB are defined using the mechanisms defined in the
which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 Structure of Management Information (SMI). This memo specifies a MIB
[RFC2579] and STD 58, RFC 2580 [RFC2580]. module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580].
3. Overview and Objectives 3. Overview and Objectives
This document defines a portion of MIB for the management of virtual This document defines a portion of MIB for the management of virtual
machines controlled by a hypervisor. This MIB module consists of the machines controlled by a hypervisor. This MIB module consists of the
managed objects related to system and software information of a managed objects related to system and software information of a
hypervisor, the list of virtual machines controlled by the hypervisor, the list of virtual machines controlled by the
hypervisor, and information of virtual resources allocated to virtual hypervisor, and information of virtual resources allocated to virtual
machines by the hypervisor. This document specifies four specific machines by the hypervisor. This document specifies four specific
types of virtual resources that are common to many hypervisor types of virtual resources that are common to many hypervisor
implementations; processors (CPUs), memory, network interfaces implementations: processors (CPUs), memory, network interfaces
(NICs), and storage devices. These managed objects are independent (NICs), and storage devices. These managed objects are independent
of the families of hypervisors or operating systems running on of the families of hypervisors or operating systems running on
virtual machines. virtual machines.
+------------------------------------------------------------------+ +------------------------------------------------------------------+
| +-------------------------------------------------+ | | +-------------------------------------------------+ |
| | Virtual machine | | | | Virtual machine | |
| | | | | | | |
| | +---------+ +---------+ +---------+ +---------+ | ....... | | | +---------+ +---------+ +---------+ +---------+ | ....... |
| | | Virtual | | Virtual | | Virtual | | Virtual | | | | | | Virtual | | Virtual | | Virtual | | Virtual | | |
skipping to change at page 4, line 27 skipping to change at page 4, line 27
| +-- Physical resources ._____. | | +-- Physical resources ._____. |
| +--------+ .--------. / \ +--^--+ | | +--------+ .--------. / \ +--^--+ |
+- - - - - - - | | - /________/| - *\_______/* - | | - -+ +- - - - - - - | | - /________/| - *\_______/* - | | - -+
| Hypervisor | CPU | | Memory |/ | Storage | | NIC | | | Hypervisor | CPU | | Memory |/ | Storage | | NIC | |
| +--------+ +--------+ \_______/ +-----+ | | +--------+ +--------+ \_______/ +-----+ |
| +-----------------------+ | | +-----------------------+ |
| || MIB objects || | | || MIB objects || |
| +-----------------------+ | | +-----------------------+ |
+------------------------------------------------------------------+ +------------------------------------------------------------------+
A hypervisor allocates virtual resources such as virtual CPUs, Figure 1: An Example of a Virtualization Environment
virtual memory, virtual storage devices, and virtual network
interfaces to virtual machines from physical resources.
Figure 1: An example of a virtualization environment
On the common implementations of hypervisors, a hypervisor allocates On the common implementations of hypervisors, a hypervisor allocates
virtual resources from physical resources; virtual CPUs, virtual virtual resources from physical resources: virtual CPUs, virtual
memory, virtual storage devices, and virtual network interfaces to memory, virtual storage devices, and virtual network interfaces to
virtual machines as shown in Figure 1. Since the virtual resources virtual machines as shown in Figure 1. Since the virtual resources
allocated to virtual machines are managed by the hypervisor, the MIB allocated to virtual machines are managed by the hypervisor, the MIB
objects are managed at the hypervisor. In case that the objects are objects are managed at the hypervisor. In case that the objects are
accessed through the SNMP, an SNMP agent is launched at the accessed through the SNMP, an SNMP agent is launched at the
hypervisor to provide access to the objects. hypervisor to provide access to the objects.
The objects are managed from the viewpoint of the operators of The objects are managed from the viewpoint of the operators of
hypervisors, but not the operators of virtual machines; i.e., the hypervisors, but not the operators of virtual machines; that is, the
objects do not take into account the actual resource utilization on objects do not take into account the actual resource utilization on
each virtual machine but the resource allocation from the physical each virtual machine but rather the resource allocation from the
resources. For example, vmNetworkIfIndex indicates the virtual physical resources. For example, vmNetworkIfIndex indicates the
interface associated with an interface of a virtual machine at the virtual interface associated with an interface of a virtual machine
hypervisor, and consequently, the 'in' and 'out' directions denote at the hypervisor, and consequently, the 'in' and 'out' directions
'from a virtual machine to the hypervisor' and 'from the hypervisor denote 'from a virtual machine to the hypervisor' and 'from the
to a virtual machine', respectively. Moreover, hypervisor to a virtual machine', respectively. Moreover,
vmStorageAllocatedSize denotes the size allocated by the hypervisor, vmStorageAllocatedSize denotes the size allocated by the hypervisor,
but not the size actually used by the operating system on the virtual but not the size actually used by the operating system on the virtual
machine. This means that vmStorageDefinedSize and machine. This means that vmStorageDefinedSize and
vmStorageAllocatedSize do not take different values when the vmStorageAllocatedSize do not take different values when the
vmStorageSourceType is 'block' or 'raw'. vmStorageSourceType is 'block' or 'raw'.
The objectives of this document are the followings: 1) This document The objectives of this document are the following: 1) this document
defines the MIB objects common to many hypervisors for the management defines the MIB objects common to many hypervisors for the management
of virtual machines controlled by a hypervisor. 2) This document of virtual machines controlled by a hypervisor, and 2) this document
clarifies the relationship with other MIB modules for managing host clarifies the relationship with other MIB modules for managing host
computers and network devices. computers and network devices.
4. Structure of the VM-MIB Module 4. Structure of the VM-MIB Module
The MIB module is organized into a group of scalars and tables. The The MIB module is organized into a group of scalars and tables. The
scalars below 'vmHypervisor' provide basic information about the scalars below 'vmHypervisor' provide basic information about the
hypervisor. The 'vmTable' lists the virtual machines (guests) that hypervisor. The 'vmTable' lists the virtual machines (guests) that
are known to the hypervisor. The 'vmCpuTable' provides the mapping are known to the hypervisor. The 'vmCpuTable' provides the mapping
table of virtual CPUs to virtual machines, including CPU time used by table of virtual CPUs to virtual machines, including CPU time used by
skipping to change at page 6, line 49 skipping to change at page 6, line 49
| shuttingdown(10) |--------->| shutdown(11) | | shuttingdown(10) |--------->| shutdown(11) |
| !vmShuttingdown | | !vmShutdown | | !vmShuttingdown | | !vmShutdown |
+ - - - - - - - - - + +---------------+ + - - - - - - - - - + +---------------+
^ | ^ |
| v !vmDeleted | v !vmDeleted
+--------------+ + - - - - - - - -+ (Deleted from +--------------+ + - - - - - - - -+ (Deleted from
| crashed(12) | | preparing(3) | vmTable) | crashed(12) | | preparing(3) | vmTable)
| !vmCrashed | | | | !vmCrashed | | |
+--------------+ + - - - - - - - -+ +--------------+ + - - - - - - - -+
The overview of the state transition of a virtual machine Figure 2: State Transition of a Virtual Machine
Figure 2: State transition of a virtual machine
The 'vmAdminState' and 'vmOperState' textual conventions define an The 'vmAdminState' and 'vmOperState' textual conventions define an
administrative state and an operational state model for virtual administrative state and an operational state model for virtual
machines. Events causing transitions between major operational machines. Events causing transitions between major operational
states will cause the generation of notifications. Per virtual states will cause the generation of notifications. Per virtual
machine (per-VM) notifications (vmRunning, vmShutdown, vmPaused, machine (per-VM) notifications (vmRunning, vmShutdown, vmPaused,
vmSuspended, vmCrashed, vmDeleted) are generated if vmSuspended, vmCrashed, vmDeleted) are generated if
vmPerVMNotificationsEnabled is true(1). Bulk notifications vmPerVMNotificationsEnabled is true(1). Bulk notifications
(vmBulkRunning, vmBulkShutdown, vmBulkPaused, vmBulkSuspended, (vmBulkRunning, vmBulkShutdown, vmBulkPaused, vmBulkSuspended,
vmBulkCrashed, vmBulkDeleted) are generated if vmBulkCrashed, vmBulkDeleted) are generated if
skipping to change at page 7, line 25 skipping to change at page 7, line 25
transition of 'vmOperState' by the write access to 'vmAdminState' and transition of 'vmOperState' by the write access to 'vmAdminState' and
the notifications generated by the operational state changes are the notifications generated by the operational state changes are
illustrated in Figure 2. The detailed state transition is summarized illustrated in Figure 2. The detailed state transition is summarized
in Appendix A. Note that the notifications shown in this figure are in Appendix A. Note that the notifications shown in this figure are
per-VM notifications. In the case of Bulk notifications, the prefix per-VM notifications. In the case of Bulk notifications, the prefix
'vm' is replaced with 'vmBulk'. 'vm' is replaced with 'vmBulk'.
The bulk notification mechanism is designed to reduce the number of The bulk notification mechanism is designed to reduce the number of
notifications that are trapped by an SNMP manager. This is because notifications that are trapped by an SNMP manager. This is because
the number of virtual machines managed by a bunch of hypervisors in a the number of virtual machines managed by a bunch of hypervisors in a
datacenter possibly becomes several thousands or more, and data center possibly becomes several thousands or more, and
consequently, many notifications could be trapped if these virtual consequently, many notifications could be trapped if these virtual
machines frequently change their administrative state. The per-VM machines frequently change their administrative state. The per-VM
notifications carry more detailed information, but the scalability is notifications carry more detailed information, but the scalability is
a problem. The notification filtering mechanism described in section a problem. The notification filtering mechanism described in
6 of RFC 3413 [RFC3413] is used by the management applications to Section 6 of RFC 3413 [RFC3413] is used by the management
control the notifications. applications to control the notifications.
5. Relationship to Other MIB Modules 5. Relationship to Other MIB Modules
The HOST-RESOURCES-MIB [RFC2790] defines the MIB objects for managing The HOST-RESOURCES-MIB [RFC2790] defines the MIB objects for managing
host systems. On systems implementing the HOST-RESOURCES-MIB, the host systems. On systems implementing the HOST-RESOURCES-MIB, the
objects of HOST-RESOURCES-MIB indicate resources of a hypervisor. objects of HOST-RESOURCES-MIB indicate resources of a hypervisor.
Some objects of HOST-RESOURCES-MIB are used to indicate physical Some objects of HOST-RESOURCES-MIB are used to indicate physical
resources through indexes. On systems implementing HOST-RESOURCES- resources through indexes. On systems implementing
MIB, the 'vmCpuPhysIndex' points to the processor's 'hrDeviceIndex' HOST-RESOURCES-MIB, the 'vmCpuPhysIndex' points to the processor's
in the 'hrProcessorTable'. The 'vmStorageParent' also points to the 'hrDeviceIndex' in the 'hrProcessorTable'. The 'vmStorageParent'
storage device's 'hrStorageIndex' in the 'hrStorageTable'. also points to the storage device's 'hrStorageIndex' in the
'hrStorageTable'.
The IF-MIB [RFC2863] defines the MIB objects for managing network The IF-MIB [RFC2863] defines the MIB objects for managing network
interfaces. Both physical and virtual network interfaces are interfaces. Both physical and virtual network interfaces are
required to be contained in the 'ifTable' of IF-MIB. The virtual required to be contained in the 'ifTable' of IF-MIB. The virtual
network interfaces in the 'ifTable' of IF-MIB are pointed from the network interfaces in the 'ifTable' of IF-MIB are pointed from the
'vmNetworkTable' defined in this document through a pointer 'vmNetworkTable' defined in this document through a pointer
'vmNetworkIfIndex'. In case that an entry in the 'vmNetworkTable' 'vmNetworkIfIndex'. In case that an entry in the 'vmNetworkTable'
has a corresponding parent physical network interface managed in the has a corresponding parent physical network interface managed in the
'ifTable' of IF-MIB, the entry contains a pointer 'vmNetworkParent' 'ifTable' of IF-MIB, the entry contains a pointer 'vmNetworkParent'
to the physical network interface. to the physical network interface.
skipping to change at page 8, line 16 skipping to change at page 8, line 19
module defined in this document though virtual switches MAY be placed module defined in this document though virtual switches MAY be placed
on a hypervisor. This is because the virtual network interfaces are on a hypervisor. This is because the virtual network interfaces are
the lowest abstraction of network resources allocated to a virtual the lowest abstraction of network resources allocated to a virtual
machine. Instead of including the objects related to virtual machine. Instead of including the objects related to virtual
switches, for example, IEEE8021-BRIDGE-MIB [IEEE8021-BRIDGE-MIB] and switches, for example, IEEE8021-BRIDGE-MIB [IEEE8021-BRIDGE-MIB] and
IEEE8021-Q-BRIDGE-MIB [IEEE8021-Q-BRIDGE-MIB] could be used. IEEE8021-Q-BRIDGE-MIB [IEEE8021-Q-BRIDGE-MIB] could be used.
The other objects related to virtual machines such as management IP The other objects related to virtual machines such as management IP
addresses of a virtual machine are not included in this MIB module addresses of a virtual machine are not included in this MIB module
because this MIB module defines the objects common to general because this MIB module defines the objects common to general
hypervisors but they are specific to some hypervisors. They may be hypervisors, but they are specific to some hypervisors. They may be
included in the entLogicalTable of ENTITY-MIB [RFC6933]. included in the entLogicalTable of ENTITY-MIB [RFC6933].
The SNMPv2-MIB [RFC3418] provides an object 'sysObjectID' that
identifies the network management subsytem and an object 'sysUpTime'
that reports the uptime of the network management portion of the
system. The HOST-RESOURCES-MIB [RFC2790] provides an object
'hrSystemUptime' that reports the uptime of the host's operating
system. To complement these objects, the new 'vmHvUpTime' object
reports the time since the hypervisor was last re-initialized, and
the new 'vmHvObjectID' provides an identification of the hypervisor
software.
6. Definitions 6. Definitions
6.1. VM-MIB 6.1. VM-MIB
VM-MIB DEFINITIONS ::= BEGIN VM-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, TimeTicks, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, TimeTicks,
Counter64, Integer32, mib-2 Counter64, Integer32, mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
skipping to change at page 8, line 39 skipping to change at page 9, line 4
OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
TEXTUAL-CONVENTION, PhysAddress, TruthValue TEXTUAL-CONVENTION, PhysAddress, TruthValue
FROM SNMPv2-TC FROM SNMPv2-TC
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB FROM SNMP-FRAMEWORK-MIB
UUIDorZero UUIDorZero
FROM UUID-TC-MIB FROM UUID-TC-MIB
InterfaceIndexOrZero InterfaceIndexOrZero
FROM IF-MIB FROM IF-MIB
IANAStorageMediaType IANAStorageMediaType
FROM IANA-STORAGE-MEDIA-TYPE-MIB; FROM IANA-STORAGE-MEDIA-TYPE-MIB;
vmMIB MODULE-IDENTITY vmMIB MODULE-IDENTITY
LAST-UPDATED "201508050000Z" -- 5 August 2015 LAST-UPDATED "201510120000Z" -- 12 October 2015
ORGANIZATION "IETF Operations and Management Area Working Group" ORGANIZATION "IETF Operations and Management Area Working Group"
CONTACT-INFO CONTACT-INFO
" "WG Email: opsawg@ietf.org
WG E-mail: opsawg@ietf.org
Mailing list subscription info: Mailing list subscription info:
https://www.ietf.org/mailman/listinfo/opsawg https://www.ietf.org/mailman/listinfo/opsawg
Hirochika Asai Hirochika Asai
The University of Tokyo The University of Tokyo
7-3-1 Hongo 7-3-1 Hongo
Bunkyo-ku, Tokyo 113-8656 Bunkyo-ku, Tokyo 113-8656
JP Japan
Phone: +81 3 5841 6748 Phone: +81 3 5841 6748
Email: panda@hongo.wide.ad.jp Email: panda@hongo.wide.ad.jp
Michael MacFaden Michael MacFaden
VMware Inc. VMware Inc.
Email: mrm@vmware.com Email: mrm@vmware.com
Juergen Schoenwaelder Juergen Schoenwaelder
Jacobs University Jacobs University
Campus Ring 1 Campus Ring 1
Bremen 28759 Bremen 28759
Germany Germany
Email: j.schoenwaelder@jacobs-university.de Email: j.schoenwaelder@jacobs-university.de
Keiichi Shima Keiichi Shima
IIJ Innovation Institute Inc. IIJ Innovation Institute Inc.
3-13 Kanda-Nishikicho 3-13 Kanda-Nishikicho
Chiyoda-ku, Tokyo 101-0054 Chiyoda-ku, Tokyo 101-0054
JP Japan
Email: keiichi@iijlab.net Email: keiichi@iijlab.net
Tina Tsou Tina Tsou
Huawei Technologies (USA) Huawei Technologies (USA)
2330 Central Expressway 2330 Central Expressway
Santa Clara CA 95050 Santa Clara, CA 95050
USA United States
Email: tina.tsou.zouting@huawei.com Email: tina.tsou.zouting@huawei.com"
"
DESCRIPTION DESCRIPTION
"This MIB module is for use in managing a hypervisor and "This MIB module is for use in managing a hypervisor and
virtual machines controlled by the hypervisor. virtual machines controlled by the hypervisor.
Copyright (c) 2015 IETF Trust and the persons identified Copyright (c) 2015 IETF Trust and the persons identified
as authors of the code. All rights reserved. as authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with Redistribution and use in source and binary forms, with
or without modification, is permitted pursuant to, and or without modification, is permitted pursuant to, and
subject to the license terms contained in, the subject to the license terms contained in, the
Simplified BSD License set forth in Section 4.c of the Simplified BSD License set forth in Section 4.c of the
IETF Trust's Legal Provisions Relating to IETF Documents IETF Trust's Legal Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info)." (http://trustee.ietf.org/license-info)."
REVISION "201508050000Z" -- 5 August 2015 REVISION "201510120000Z" -- 12 October 2015
DESCRIPTION DESCRIPTION
"The initial version of this MIB, published as "The initial version of this MIB, published as
RFCXXXX." RFC 7666."
::= { mib-2 yyy } ::= { mib-2 236 }
-- RFC Ed.: replace XXXX with RFC number and remove this note
-- RFC Ed.: replace yyy with actual number and remove this note
vmNotifications OBJECT IDENTIFIER ::= { vmMIB 0 } vmNotifications OBJECT IDENTIFIER ::= { vmMIB 0 }
vmObjects OBJECT IDENTIFIER ::= { vmMIB 1 } vmObjects OBJECT IDENTIFIER ::= { vmMIB 1 }
vmConformance OBJECT IDENTIFIER ::= { vmMIB 2 } vmConformance OBJECT IDENTIFIER ::= { vmMIB 2 }
-- Textual conversion definitions -- Textual conversion definitions
-- --
VirtualMachineIndex ::= TEXTUAL-CONVENTION VirtualMachineIndex ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
skipping to change at page 10, line 35 skipping to change at page 10, line 45
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
VirtualMachineIndexOrZero ::= TEXTUAL-CONVENTION VirtualMachineIndexOrZero ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual convention is an extension of the "This textual convention is an extension of the
VirtualMachineIndex convention. This extension permits VirtualMachineIndex convention. This extension permits
the additional value of zero. The meaning of the value the additional value of zero. The meaning of the value
zero is object-specific and MUST therefore be defined as zero is object-specific and MUST therefore be defined as
part of the description of any object which uses this part of the description of any object that uses this
syntax. Examples of the usage of zero might include syntax. Examples of the usage of zero might include
situations where a virtual machine is unknown, or when situations where a virtual machine is unknown, or when
none or all virtual machines need to be referenced." none or all virtual machines need to be referenced."
SYNTAX Integer32 (0..2147483647) SYNTAX Integer32 (0..2147483647)
VirtualMachineAdminState ::= TEXTUAL-CONVENTION VirtualMachineAdminState ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The administrative state of a virtual machine: "The administrative state of a virtual machine:
skipping to change at page 11, line 17 skipping to change at page 11, line 25
state has been saved to persistent store state has been saved to persistent store
and will be restored at next running(1). and will be restored at next running(1).
paused(3) The administrative state indicating the paused(3) The administrative state indicating the
virtual machine is resident in memory but virtual machine is resident in memory but
is no longer scheduled to execute by the is no longer scheduled to execute by the
hypervisor. hypervisor.
shutdown(4) The administrative state of the virtual shutdown(4) The administrative state of the virtual
machine indicating the virtual machine machine indicating the virtual machine
is currently offline or should be taken is currently offline or should be
shutting down." shutting down."
SYNTAX INTEGER { SYNTAX INTEGER {
running(1), running(1),
suspended(2), suspended(2),
paused(3), paused(3),
shutdown(4) shutdown(4)
} }
VirtualMachineOperState ::= TEXTUAL-CONVENTION VirtualMachineOperState ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The operational state of a virtual machine: "The operational state of a virtual machine:
unknown(1) The operational state of the virtual unknown(1) The operational state of the virtual
machine is unknown, e.g., because the machine is unknown, e.g., because the
implementation failed to obtain the state implementation failed to obtain the state
from the hypervisor. from the hypervisor.
other(2) The operational state of the virtual other(2) The operational state of the virtual
machine indicating that an operational machine indicating that an operational
state is obtained from the hypervisor but state is obtained from the hypervisor, but
it is not a state defined in this MIB it is not a state defined in this MIB
module. module.
preparing(3) The operational state of the virtual preparing(3) The operational state of the virtual
machine indicating the virtual machine is machine indicating the virtual machine is
currently in the process of preparation, currently in the process of preparation,
e.g., allocating and initializing virtual e.g., allocating and initializing virtual
storage after creating (defining) virtual storage after creating (defining) the
machine. virtual machine.
running(4) The operational state of the virtual running(4) The operational state of the virtual
machine indicating the virtual machine is machine indicating the virtual machine is
currently executed but it is not in the currently executed, but it is not in the
process of preparing(3), suspending(5), process of preparing(3), suspending(5),
resuming(7), migrating(9), and resuming(7), migrating(9), and
shuttingdown(10). shuttingdown(10).
suspending(5) The operational state of the virtual suspending(5) The operational state of the virtual
machine indicating the virtual machine is machine indicating the virtual machine is
currently in the process of suspending currently in the process of suspending
to save its memory and CPU execution to save its memory and CPU execution
state to persistent store. This is a state to persistent store. This is a
transient state from running(4) to transient state from running(4) to
skipping to change at page 14, line 9 skipping to change at page 14, line 17
SYNTAX INTEGER { SYNTAX INTEGER {
unknown(1), unknown(1),
enabled(2), enabled(2),
disabled(3) disabled(3)
} }
VirtualMachinePersistent ::= TEXTUAL-CONVENTION VirtualMachinePersistent ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value indicates whether a virtual machine has a "This value indicates whether a virtual machine has a
persistent configuration which means the virtual machine persistent configuration, which means the virtual machine
will still exist after shutting down: will still exist after shutting down:
unknown(1) The persistent configuration is unknown, unknown(1) The persistent configuration is unknown,
e.g., because the implementation failed e.g., because the implementation failed
to obtain the persistent configuration to obtain the persistent configuration
from the hypervisor. (read-only) from the hypervisor. (read-only)
persistent(2) The virtual machine is persistent, i.e., persistent(2) The virtual machine is persistent, i.e.,
the virtual machine will exist after its the virtual machine will exist after it
shutting down. shuts down.
transient(3) The virtual machine is transient, i.e., transient(3) The virtual machine is transient, i.e.,
the virtual machine will not exist after the virtual machine will not exist after
its shutting down." it shuts down."
SYNTAX INTEGER { SYNTAX INTEGER {
unknown(1), unknown(1),
persistent(2), persistent(2),
transient(3) transient(3)
} }
VirtualMachineCpuIndex ::= TEXTUAL-CONVENTION VirtualMachineCpuIndex ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 16, line 21 skipping to change at page 16, line 31
re-initialization of the hypervisor to the next re-initialization of the hypervisor to the next
re-initialization." re-initialization."
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
VirtualMachineList ::= TEXTUAL-CONVENTION VirtualMachineList ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1x" DISPLAY-HINT "1x"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each octet within this value specifies a set of eight "Each octet within this value specifies a set of eight
virtual machine vmIndex values, with the first octet virtual machine vmIndex values, with the first octet
specifying virtual machine 1 through 8, the second octet specifying virtual machine 1 through 8, the second octet
specifying virtual machine 9 through 16, etc. Within specifying virtual machine 9 through 16, etc. Within
each octet, the most significant bit represents the each octet, the most significant bit represents the
lowest numbered vmIndex, and the least significant bit lowest-numbered vmIndex, and the least significant bit
represents the highest numbered vmIndex. Thus, each represents the highest-numbered vmIndex. Thus, each
virtual machine of the host is represented by a single virtual machine of the host is represented by a single
bit within the value of this object. If that bit has bit within the value of this object. If that bit has
a value of '1', then that virtual machine is included a value of '1', then that virtual machine is included
in the set of virtual machines; the virtual machine is in the set of virtual machines; the virtual machine is
not included if its bit has a value of '0'." not included if its bit has a value of '0'."
SYNTAX OCTET STRING SYNTAX OCTET STRING
-- The hypervisor group -- The hypervisor group
-- --
-- A collection of objects common to all hypervisors. -- A collection of objects common to all hypervisors.
-- --
vmHypervisor OBJECT IDENTIFIER ::= { vmObjects 1 } vmHypervisor OBJECT IDENTIFIER ::= { vmObjects 1 }
vmHvSoftware OBJECT-TYPE vmHvSoftware OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..255)) SYNTAX SnmpAdminString (SIZE (0..255))
skipping to change at page 17, line 19 skipping to change at page 17, line 28
vmHvObjectID OBJECT-TYPE vmHvObjectID OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The vendor's authoritative identification of the "The vendor's authoritative identification of the
hypervisor software contained in the entity. This value hypervisor software contained in the entity. This value
is allocated within the SMI enterprises is allocated within the SMI enterprises
subtree (1.3.6.1.4.1). Note that this is different from subtree (1.3.6.1.4.1). Note that this is different from
sysObjectID in the SNMPv2-MIB [RFC3418] because sysObjectID in the SNMPv2-MIB (RFC 3418) because
sysObjectID is not the identification of the hypervisor sysObjectID is not the identification of the hypervisor
software but the device, firmware, or management software but the device, firmware, or management
operating system." operating system."
::= { vmHypervisor 3 } ::= { vmHypervisor 3 }
vmHvUpTime OBJECT-TYPE vmHvUpTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time (in centi-seconds) since the hypervisor was "The time (in centiseconds) since the hypervisor was
last re-initialized. Note that this is different from last re-initialized. Note that this is different from
sysUpTime in the SNMPv2-MIB [RFC3418] and hrSystemUptime sysUpTime in the SNMPv2-MIB (RFC 3418) and hrSystemUptime
in the HOST-RESOURCES-MIB [RFC2790] because sysUpTime is in the HOST-RESOURCES-MIB (RFC 2790) because sysUpTime is
the uptime of the network management portion of the the uptime of the network management portion of the
system, and hrSystemUptime is the uptime of the system, and hrSystemUptime is the uptime of the
management operating system but not the hypervisor management operating system but not the hypervisor
software." software."
::= { vmHypervisor 4 } ::= { vmHypervisor 4 }
-- The virtual machine information -- The virtual machine information
-- --
-- A collection of objects common to all virtual machines. -- A collection of objects common to all virtual machines.
-- --
skipping to change at page 19, line 13 skipping to change at page 19, line 22
vmUpTime TimeTicks, vmUpTime TimeTicks,
vmCpuTime Counter64 vmCpuTime Counter64
} }
vmIndex OBJECT-TYPE vmIndex OBJECT-TYPE
SYNTAX VirtualMachineIndex SYNTAX VirtualMachineIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A unique value, greater than zero, identifying the "A unique value, greater than zero, identifying the
virtual machine. The value assigned to a given virtual virtual machine. The value assigned to a given virtual
machine may not persist across re-initialization of the machine may not persist across re-initialization of the
hypervisor. A command generator MUST use the vmUUID to hypervisor. A command generator MUST use the vmUUID to
identify a given virtual machine of interest." identify a given virtual machine of interest."
::= { vmEntry 1 } ::= { vmEntry 1 }
vmName OBJECT-TYPE vmName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..255)) SYNTAX SnmpAdminString (SIZE (0..255))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A textual name of the virtual machine." "A textual name of the virtual machine."
::= { vmEntry 2 } ::= { vmEntry 2 }
vmUUID OBJECT-TYPE vmUUID OBJECT-TYPE
SYNTAX UUIDorZero SYNTAX UUIDorZero
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The virtual machine's 128-bit UUID or the zero-length "The virtual machine's 128-bit Universally Unique
string when a UUID is not available. The UUID if set Identifier (UUID) or the zero-length string when a
MUST uniquely identify a virtual machine from all other UUID is not available. If set, the UUID MUST uniquely
virtual machines in an administrative domain. A identify a virtual machine from all other virtual
zero-length octet string is returned if no UUID machines in an administrative domain. A zero-length
information is known." octet string is returned if no UUID information is
known."
::= { vmEntry 3 } ::= { vmEntry 3 }
vmOSType OBJECT-TYPE vmOSType OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..255)) SYNTAX SnmpAdminString (SIZE (0..255))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A textual description containing operating system "A textual description containing operating system
information installed on the virtual machine. This information installed on the virtual machine. This
value corresponds to the operating system the hypervisor value corresponds to the operating system the hypervisor
skipping to change at page 20, line 40 skipping to change at page 20, line 49
automatically starts at the next initialization of the automatically starts at the next initialization of the
hypervisor." hypervisor."
::= { vmEntry 7 } ::= { vmEntry 7 }
vmPersistent OBJECT-TYPE vmPersistent OBJECT-TYPE
SYNTAX VirtualMachinePersistent SYNTAX VirtualMachinePersistent
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value indicates whether the virtual machine has a "This value indicates whether the virtual machine has a
persistent configuration which means the virtual machine persistent configuration, which means the virtual machine
will still exist after its shutdown." will still exist after its shutdown."
::= { vmEntry 8 } ::= { vmEntry 8 }
vmCurCpuNumber OBJECT-TYPE vmCurCpuNumber OBJECT-TYPE
SYNTAX Integer32 (0..2147483647) SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of virtual CPUs currently assigned to the "The number of virtual CPUs currently assigned to the
virtual machine." virtual machine."
skipping to change at page 21, line 31 skipping to change at page 21, line 40
"The maximum number of virtual CPUs that are assigned to "The maximum number of virtual CPUs that are assigned to
the virtual machine when it is in a power-on state. The the virtual machine when it is in a power-on state. The
value -1 indicates that there is no limit." value -1 indicates that there is no limit."
::= { vmEntry 11 } ::= { vmEntry 11 }
vmMemUnit OBJECT-TYPE vmMemUnit OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The multiplication unit in byte for vmCurMem, vmMinMem, "The multiplication unit in bytes for vmCurMem, vmMinMem,
and vmMaxMem. For example, when this value is 1024, the and vmMaxMem. For example, when this value is 1024, the
memory size unit for vmCurMem, vmMinMem, and vmMaxMem is memory size unit for vmCurMem, vmMinMem, and vmMaxMem is
KiB." KiB."
::= { vmEntry 12 } ::= { vmEntry 12 }
vmCurMem OBJECT-TYPE vmCurMem OBJECT-TYPE
SYNTAX Integer32 (0..2147483647) SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 22, line 24 skipping to change at page 22, line 33
"The maximum memory size defined to the virtual machine "The maximum memory size defined to the virtual machine
in the unit designated by vmMemUnit. The value -1 in the unit designated by vmMemUnit. The value -1
indicates that there is no limit." indicates that there is no limit."
::= { vmEntry 15 } ::= { vmEntry 15 }
vmUpTime OBJECT-TYPE vmUpTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time (in centi-seconds) since the administrative "The time (in centiseconds) since the administrative
state of the virtual machine was last changed from state of the virtual machine was last changed from
shutdown(4) to running(1)." shutdown(4) to running(1)."
::= { vmEntry 16 } ::= { vmEntry 16 }
vmCpuTime OBJECT-TYPE vmCpuTime OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "microsecond" UNITS "microsecond"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total CPU time used in microsecond. If the number "The total CPU time used in microseconds. If the number
of virtual CPUs is larger than 1, vmCpuTime may exceed of virtual CPUs is larger than 1, vmCpuTime may exceed
real time. real time.
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
at re-initialization of the hypervisor, and at re-initialization of the hypervisor and
administrative state (vmAdminState) changes of the administrative state (vmAdminState) changes of the
virtual machine." virtual machine."
::= { vmEntry 17 } ::= { vmEntry 17 }
-- The virtual CPU on each virtual machines -- The virtual CPU on each virtual machines
vmCpuTable OBJECT-TYPE vmCpuTable OBJECT-TYPE
SYNTAX SEQUENCE OF VmCpuEntry SYNTAX SEQUENCE OF VmCpuEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 23, line 39 skipping to change at page 23, line 48
the virtual machine." the virtual machine."
::= { vmCpuEntry 1 } ::= { vmCpuEntry 1 }
vmCpuCoreTime OBJECT-TYPE vmCpuCoreTime OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "microsecond" UNITS "microsecond"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total CPU time used by this virtual CPU in "The total CPU time used by this virtual CPU in
microsecond. microseconds.
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
at re-initialization of the hypervisor, and at re-initialization of the hypervisor and
administrative state (vmAdminState) changes of the administrative state (vmAdminState) changes of the
virtual machine." virtual machine."
::= { vmCpuEntry 2 } ::= { vmCpuEntry 2 }
-- The virtual CPU affinity on each virtual machines -- The virtual CPU affinity on each virtual machines
vmCpuAffinityTable OBJECT-TYPE vmCpuAffinityTable OBJECT-TYPE
SYNTAX SEQUENCE OF VmCpuAffinityEntry SYNTAX SEQUENCE OF VmCpuAffinityEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of CPU affinity entries of a virtual CPU." "A list of CPU affinity entries of a virtual CPU."
::= { vmObjects 6 } ::= { vmObjects 6 }
vmCpuAffinityEntry OBJECT-TYPE vmCpuAffinityEntry OBJECT-TYPE
SYNTAX VmCpuAffinityEntry SYNTAX VmCpuAffinityEntry
skipping to change at page 24, line 21 skipping to change at page 24, line 31
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry containing CPU affinity associated with a "An entry containing CPU affinity associated with a
particular virtual machine." particular virtual machine."
INDEX { vmIndex, vmCpuIndex, vmCpuPhysIndex } INDEX { vmIndex, vmCpuIndex, vmCpuPhysIndex }
::= { vmCpuAffinityTable 1 } ::= { vmCpuAffinityTable 1 }
VmCpuAffinityEntry ::= VmCpuAffinityEntry ::=
SEQUENCE { SEQUENCE {
vmCpuPhysIndex Integer32, vmCpuPhysIndex Integer32,
vmCpuAffinity Integer32 vmCpuAffinity INTEGER
} }
vmCpuPhysIndex OBJECT-TYPE vmCpuPhysIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value identifying a physical CPU on the hypervisor. "A value identifying a physical CPU on the hypervisor.
On systems implementing the HOST-RESOURCES-MIB, the On systems implementing the HOST-RESOURCES-MIB, the
value MUST be the same value that is used as the index value MUST be the same value that is used as the index
skipping to change at page 24, line 50 skipping to change at page 25, line 12
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The CPU affinity of this virtual CPU to the physical "The CPU affinity of this virtual CPU to the physical
CPU represented by 'vmCpuPhysIndex'." CPU represented by 'vmCpuPhysIndex'."
::= { vmCpuAffinityEntry 3 } ::= { vmCpuAffinityEntry 3 }
-- The virtual storage devices on each virtual machine. This -- The virtual storage devices on each virtual machine. This
-- document defines some overlapped objects with hrStorage in -- document defines some overlapped objects with hrStorage in
-- HOST-RESOURCES-MIB [RFC2790], because virtual resources are -- HOST-RESOURCES-MIB (RFC 2790), because virtual resources are
-- allocated from the hypervisor's resources, which is the 'host -- allocated from the hypervisor's resources, which is the 'host
-- resources' -- resources'.
vmStorageTable OBJECT-TYPE vmStorageTable OBJECT-TYPE
SYNTAX SEQUENCE OF VmStorageEntry SYNTAX SEQUENCE OF VmStorageEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The conceptual table of virtual storage devices "The conceptual table of virtual storage devices
attached to the virtual machine." attached to the virtual machine."
::= { vmObjects 7 } ::= { vmObjects 7 }
vmStorageEntry OBJECT-TYPE vmStorageEntry OBJECT-TYPE
skipping to change at page 26, line 26 skipping to change at page 26, line 35
DESCRIPTION DESCRIPTION
"A unique value identifying a virtual storage device "A unique value identifying a virtual storage device
allocated to the virtual machine." allocated to the virtual machine."
::= { vmStorageEntry 2 } ::= { vmStorageEntry 2 }
vmStorageParent OBJECT-TYPE vmStorageParent OBJECT-TYPE
SYNTAX Integer32 (0..2147483647) SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of hrStorageIndex which is the parent (i.e., "The value of hrStorageIndex, which is the parent (i.e.,
physical) device of this virtual device on systems physical) device of this virtual device on systems
implementing the HOST-RESOURCES-MIB. The value zero implementing the HOST-RESOURCES-MIB. The value zero
denotes this virtual device is not any child represented denotes this virtual device is not any child
in the hrStorageTable." represented in the hrStorageTable."
::= { vmStorageEntry 3 } ::= { vmStorageEntry 3 }
vmStorageSourceType OBJECT-TYPE vmStorageSourceType OBJECT-TYPE
SYNTAX VirtualMachineStorageSourceType SYNTAX VirtualMachineStorageSourceType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The source type of the virtual storage device." "The source type of the virtual storage device."
::= { vmStorageEntry 4 } ::= { vmStorageEntry 4 }
skipping to change at page 27, line 45 skipping to change at page 28, line 6
"A (detailed) textual string of the virtual storage "A (detailed) textual string of the virtual storage
media. For example, this represents the specific driver media. For example, this represents the specific driver
name of the emulated media such as 'IDE' and 'SCSI'." name of the emulated media such as 'IDE' and 'SCSI'."
::= { vmStorageEntry 9 } ::= { vmStorageEntry 9 }
vmStorageSizeUnit OBJECT-TYPE vmStorageSizeUnit OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The multiplication unit in byte for "The multiplication unit in bytes for
vmStorageDefinedSize and vmStorageAllocatedSize. For vmStorageDefinedSize and vmStorageAllocatedSize. For
example, when this value is 1048576, the storage size example, when this value is 1048576, the storage size
unit for vmStorageDefinedSize and vmStorageAllocatedSize unit for vmStorageDefinedSize and vmStorageAllocatedSize
is MiB." is MiB."
::= { vmStorageEntry 10 } ::= { vmStorageEntry 10 }
vmStorageDefinedSize OBJECT-TYPE vmStorageDefinedSize OBJECT-TYPE
SYNTAX Integer32 (-1|0..2147483647) SYNTAX Integer32 (-1|0..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 28, line 38 skipping to change at page 28, line 46
::= { vmStorageEntry 12 } ::= { vmStorageEntry 12 }
vmStorageReadIOs OBJECT-TYPE vmStorageReadIOs OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of read I/O requests. "The number of read I/O requests.
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
at re-initialization of the hypervisor, and at re-initialization of the hypervisor and
administrative state (vmAdminState) changes of the administrative state (vmAdminState) changes of the
virtual machine." virtual machine."
::= { vmStorageEntry 13 } ::= { vmStorageEntry 13 }
vmStorageWriteIOs OBJECT-TYPE vmStorageWriteIOs OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of write I/O requests. "The number of write I/O requests.
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
at re-initialization of the hypervisor, and at re-initialization of the hypervisor and
administrative state (vmAdminState) changes of the administrative state (vmAdminState) changes of the
virtual machine." virtual machine."
::= { vmStorageEntry 14 } ::= { vmStorageEntry 14 }
vmStorageReadOctets OBJECT-TYPE vmStorageReadOctets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of bytes read from this device. "The total number of bytes read from this device.
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
at re-initialization of the hypervisor, and at re-initialization of the hypervisor and
administrative state (vmAdminState) changes of the administrative state (vmAdminState) changes of the
virtual machine." virtual machine."
::= { vmStorageEntry 15 } ::= { vmStorageEntry 15 }
vmStorageWriteOctets OBJECT-TYPE vmStorageWriteOctets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of bytes written to this device. "The total number of bytes written to this device.
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
at re-initialization of the hypervisor, and at re-initialization of the hypervisor and
administrative state (vmAdminState) changes of the administrative state (vmAdminState) changes of the
virtual machine." virtual machine."
::= { vmStorageEntry 16 } ::= { vmStorageEntry 16 }
vmStorageReadLatency OBJECT-TYPE vmStorageReadLatency OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of microseconds read requests have "The total number of microseconds read requests have
skipping to change at page 29, line 40 skipping to change at page 29, line 49
virtual machine." virtual machine."
::= { vmStorageEntry 16 } ::= { vmStorageEntry 16 }
vmStorageReadLatency OBJECT-TYPE vmStorageReadLatency OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of microseconds read requests have "The total number of microseconds read requests have
been queued for this device. been queued for this device.
This would typically be implemented by storing the high This would typically be implemented by storing the high
precision system time stamp of when the request is precision system timestamp of when the request is
received from the virtual machine with the request, the received from the virtual machine with the request, the
difference between this initial timestamp and the time difference between this initial timestamp and the time
at which the requested operation has completed SHOULD be at which the requested operation has completed SHOULD be
converted to microseconds and accumulated. converted to microseconds and accumulated.
Discontinuities in the value of this counter can occur at Discontinuities in the value of this counter can occur at
re-initialization of the hypervisor, and administrative re-initialization of the hypervisor and administrative
state (vmAdminState) changes of the virtual machine." state (vmAdminState) changes of the virtual machine."
::= { vmStorageEntry 17 } ::= { vmStorageEntry 17 }
vmStorageWriteLatency OBJECT-TYPE vmStorageWriteLatency OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of microseconds write requests have "The total number of microseconds write requests have
been queued for this device. been queued for this device.
skipping to change at page 30, line 10 skipping to change at page 30, line 21
state (vmAdminState) changes of the virtual machine." state (vmAdminState) changes of the virtual machine."
::= { vmStorageEntry 17 } ::= { vmStorageEntry 17 }
vmStorageWriteLatency OBJECT-TYPE vmStorageWriteLatency OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of microseconds write requests have "The total number of microseconds write requests have
been queued for this device. been queued for this device.
This would typically be implemented by storing the high This would typically be implemented by storing the high
precision system time stamp of when the request is precision system timestamp of when the request is
received from the virtual machine with the request, the received from the virtual machine with the request; the
difference between this initial timestamp and the time difference between this initial timestamp and the time
at which the requested operation has completed SHOULD be at which the requested operation has completed SHOULD be
converted to microseconds and accumulated. converted to microseconds and accumulated.
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
at re-initialization of the hypervisor, and at re-initialization of the hypervisor and
administrative state (vmAdminState) changes of the administrative state (vmAdminState) changes of the
virtual machine." virtual machine."
::= { vmStorageEntry 18 } ::= { vmStorageEntry 18 }
-- The virtual network interfaces on each virtual machine. -- The virtual network interfaces on each virtual machine.
vmNetworkTable OBJECT-TYPE vmNetworkTable OBJECT-TYPE
SYNTAX SEQUENCE OF VmNetworkEntry SYNTAX SEQUENCE OF VmNetworkEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The conceptual table of virtual network interfaces "The conceptual table of virtual network interfaces
attached to the virtual machine." attached to the virtual machine."
::= { vmObjects 8 } ::= { vmObjects 8 }
vmNetworkEntry OBJECT-TYPE vmNetworkEntry OBJECT-TYPE
SYNTAX VmNetworkEntry SYNTAX VmNetworkEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry for one virtual network interfaces attached to "An entry for one virtual network interface attached to
the virtual machine." the virtual machine."
INDEX { vmIndex, vmNetworkIndex } INDEX { vmIndex, vmNetworkIndex }
::= { vmNetworkTable 1 } ::= { vmNetworkTable 1 }
VmNetworkEntry ::= VmNetworkEntry ::=
SEQUENCE { SEQUENCE {
vmNetworkIndex VirtualMachineNetworkIndex, vmNetworkIndex VirtualMachineNetworkIndex,
vmNetworkIfIndex InterfaceIndexOrZero, vmNetworkIfIndex InterfaceIndexOrZero,
vmNetworkParent InterfaceIndexOrZero, vmNetworkParent InterfaceIndexOrZero,
vmNetworkModel SnmpAdminString, vmNetworkModel SnmpAdminString,
skipping to change at page 31, line 19 skipping to change at page 31, line 31
DESCRIPTION DESCRIPTION
"A unique value identifying a virtual network interface "A unique value identifying a virtual network interface
allocated to the virtual machine." allocated to the virtual machine."
::= { vmNetworkEntry 1 } ::= { vmNetworkEntry 1 }
vmNetworkIfIndex OBJECT-TYPE vmNetworkIfIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of ifIndex which corresponds to this virtual "The value of ifIndex, which corresponds to this virtual
network interface. If this device is not represented in network interface. If this device is not represented in
the ifTable, then this value MUST be zero." the ifTable, then this value MUST be zero."
::= { vmNetworkEntry 2 } ::= { vmNetworkEntry 2 }
vmNetworkParent OBJECT-TYPE vmNetworkParent OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of ifIndex which corresponds to the parent "The value of ifIndex, which corresponds to the parent
(i.e., physical) device of this virtual device on. The (i.e., physical) device of this virtual device. The
value zero denotes this virtual device is not any child value zero denotes this virtual device is not any
represented in the ifTable." child represented in the ifTable."
::= { vmNetworkEntry 3 } ::= { vmNetworkEntry 3 }
vmNetworkModel OBJECT-TYPE vmNetworkModel OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..255)) SYNTAX SnmpAdminString (SIZE (0..255))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A textual string containing the (emulated) model of "A textual string containing the (emulated) model of the
virtual network interface. For example, this value is virtual network interface. For example, this value is
'virtio' when the emulation driver model is virtio." 'virtio' when the emulation driver model is virtio."
::= { vmNetworkEntry 4 } ::= { vmNetworkEntry 4 }
vmNetworkPhysAddress OBJECT-TYPE vmNetworkPhysAddress OBJECT-TYPE
SYNTAX PhysAddress SYNTAX PhysAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The MAC address of the virtual network interface." "The Media Access Control (MAC) address of the virtual
network interface."
::= { vmNetworkEntry 5 } ::= { vmNetworkEntry 5 }
-- Notification definitions: -- Notification definitions:
vmPerVMNotificationsEnabled OBJECT-TYPE vmPerVMNotificationsEnabled OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates if notification generator will send "Indicates if the notification generator will send
notifications per virtual machine. Changes to this notifications per virtual machine. Changes to this
object MUST NOT persist across re-initialization of object MUST NOT persist across re-initialization of
the management system, e.g., SNMP agent." the management system, e.g., SNMP agent."
::= { vmObjects 9 } ::= { vmObjects 9 }
vmBulkNotificationsEnabled OBJECT-TYPE vmBulkNotificationsEnabled OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates if notification generator will send "Indicates if the notification generator will send
notifications per set of virtual machines. Changes to notifications per set of virtual machines. Changes to
this object MUST NOT persist across re-initialization of this object MUST NOT persist across re-initialization of
the management system, e.g., SNMP agent." the management system, e.g., SNMP agent."
::= { vmObjects 10 } ::= { vmObjects 10 }
vmAffectedVMs OBJECT-TYPE vmAffectedVMs OBJECT-TYPE
SYNTAX VirtualMachineList SYNTAX VirtualMachineList
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 35, line 16 skipping to change at page 35, line 30
vmCrashed NOTIFICATION-TYPE vmCrashed NOTIFICATION-TYPE
OBJECTS { OBJECTS {
vmName, vmName,
vmUUID, vmUUID,
vmOperState vmOperState
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a virtual machine "This notification is generated when a virtual machine
has been crashed. The previos state of the virtual has been crashed. The previous state of the virtual
machine is indicated by the included value of machine is indicated by the included value of
vmOperState." vmOperState."
::= { vmNotifications 9 } ::= { vmNotifications 9 }
vmDeleted NOTIFICATION-TYPE vmDeleted NOTIFICATION-TYPE
OBJECTS { OBJECTS {
vmName, vmName,
vmUUID, vmUUID,
vmOperState, vmOperState,
vmPersistent vmPersistent
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a virtual machine "This notification is generated when a virtual machine
has been deleted. The prior state of the virtual has been deleted. The prior state of the virtual
machine is indicated by the included value of machine is indicated by the included value of
vmOperState." vmOperState."
::= { vmNotifications 10 } ::= { vmNotifications 10 }
vmBulkRunning NOTIFICATION-TYPE vmBulkRunning NOTIFICATION-TYPE
OBJECTS { OBJECTS {
vmAffectedVMs vmAffectedVMs
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when the operational "This notification is generated when the operational
state of one or more virtual machine has been changed to state of one or more virtual machines has been changed
running(4) from a all prior states except for to running(4) from any prior state, except for
running(4). Management stations are encouraged to running(4). Management stations are encouraged to
subsequently poll the subset of virtual machines of subsequently poll the subset of virtual machines of
interest for vmOperState." interest for vmOperState."
::= { vmNotifications 11 } ::= { vmNotifications 11 }
vmBulkShuttingdown NOTIFICATION-TYPE vmBulkShuttingdown NOTIFICATION-TYPE
OBJECTS { OBJECTS {
vmAffectedVMs vmAffectedVMs
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when the operational "This notification is generated when the operational
state of one or more virtual machine has been changed to state of one or more virtual machines has been changed
shuttingdown(10) from a state other than to shuttingdown(10) from a state other than
shuttingdown(10). Management stations are encouraged to shuttingdown(10). Management stations are encouraged to
subsequently poll the subset of virtual machines of subsequently poll the subset of virtual machines of
interest for vmOperState." interest for vmOperState."
::= { vmNotifications 12 } ::= { vmNotifications 12 }
vmBulkShutdown NOTIFICATION-TYPE vmBulkShutdown NOTIFICATION-TYPE
OBJECTS { OBJECTS {
vmAffectedVMs vmAffectedVMs
} }
STATUS current STATUS current
skipping to change at page 36, line 37 skipping to change at page 36, line 51
vmOperState." vmOperState."
::= { vmNotifications 13 } ::= { vmNotifications 13 }
vmBulkPaused NOTIFICATION-TYPE vmBulkPaused NOTIFICATION-TYPE
OBJECTS { OBJECTS {
vmAffectedVMs vmAffectedVMs
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when the operational "This notification is generated when the operational
state of one or more virtual machines have been changed state of one or more virtual machines has been changed
to paused(8) from a state other than paused(8). to paused(8) from a state other than paused(8).
Management stations are encouraged to subsequently poll Management stations are encouraged to subsequently poll
the subset of virtual machines of interest for the subset of virtual machines of interest for
vmOperState." vmOperState."
::= { vmNotifications 14 } ::= { vmNotifications 14 }
vmBulkSuspending NOTIFICATION-TYPE vmBulkSuspending NOTIFICATION-TYPE
OBJECTS { OBJECTS {
vmAffectedVMs vmAffectedVMs
} }
STATUS current STATUS current
skipping to change at page 36, line 51 skipping to change at page 37, line 17
vmOperState." vmOperState."
::= { vmNotifications 14 } ::= { vmNotifications 14 }
vmBulkSuspending NOTIFICATION-TYPE vmBulkSuspending NOTIFICATION-TYPE
OBJECTS { OBJECTS {
vmAffectedVMs vmAffectedVMs
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when the operational "This notification is generated when the operational
state of one or more virtual machines have been changed state of one or more virtual machines has been changed
to suspending(5) from a state other than suspending(5). to suspending(5) from a state other than suspending(5).
Management stations are encouraged to subsequently poll Management stations are encouraged to subsequently poll
the subset of virtual machines of interest for the subset of virtual machines of interest for
vmOperState." vmOperState."
::= { vmNotifications 15 } ::= { vmNotifications 15 }
vmBulkSuspended NOTIFICATION-TYPE vmBulkSuspended NOTIFICATION-TYPE
OBJECTS { OBJECTS {
vmAffectedVMs vmAffectedVMs
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when the operational "This notification is generated when the operational
state of one or more virtual machines have been changed state of one or more virtual machines has been changed
to suspended(6) from a state other than suspended(6). to suspended(6) from a state other than suspended(6).
Management stations are encouraged to subsequently poll Management stations are encouraged to subsequently poll
the subset of virtual machines of interest for the subset of virtual machines of interest for
vmOperState." vmOperState."
::= { vmNotifications 16 } ::= { vmNotifications 16 }
vmBulkResuming NOTIFICATION-TYPE vmBulkResuming NOTIFICATION-TYPE
OBJECTS { OBJECTS {
vmAffectedVMs vmAffectedVMs
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when the operational "This notification is generated when the operational
state of one or more virtual machines have been changed state of one or more virtual machines has been changed
to resuming(7) from a state other than resuming(7). to resuming(7) from a state other than resuming(7).
Management stations are encouraged to subsequently poll Management stations are encouraged to subsequently poll
the subset of virtual machines of interest for the subset of virtual machines of interest for
vmOperState." vmOperState."
::= { vmNotifications 17 } ::= { vmNotifications 17 }
vmBulkMigrating NOTIFICATION-TYPE vmBulkMigrating NOTIFICATION-TYPE
OBJECTS { OBJECTS {
vmAffectedVMs vmAffectedVMs
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when the operational "This notification is generated when the operational
state of one or more virtual machines have been changed state of one or more virtual machines has been changed
to migrating(9) from a state other than migrating(9). to migrating(9) from a state other than migrating(9).
Management stations are encouraged to subsequently poll Management stations are encouraged to subsequently poll
the subset of virtual machines of interest for the subset of virtual machines of interest for
vmOperState." vmOperState."
::= { vmNotifications 18 } ::= { vmNotifications 18 }
vmBulkCrashed NOTIFICATION-TYPE vmBulkCrashed NOTIFICATION-TYPE
OBJECTS { OBJECTS {
vmAffectedVMs vmAffectedVMs
} }
skipping to change at page 38, line 50 skipping to change at page 39, line 14
vmHypervisorGroup, vmHypervisorGroup,
vmVirtualMachineGroup, vmVirtualMachineGroup,
vmCpuGroup, vmCpuGroup,
vmCpuAffinityGroup, vmCpuAffinityGroup,
vmStorageGroup, vmStorageGroup,
vmNetworkGroup vmNetworkGroup
} }
GROUP vmPerVMNotificationOptionalGroup GROUP vmPerVMNotificationOptionalGroup
DESCRIPTION DESCRIPTION
"Support for per-VM notifications is optional. If not "Support for per-VM notifications is optional. If not
implemented then vmPerVMNotificationsEnabled MUST report implemented, then vmPerVMNotificationsEnabled MUST report
false(2)." false(2)."
GROUP vmBulkNotificationsVariablesGroup GROUP vmBulkNotificationsVariablesGroup
DESCRIPTION DESCRIPTION
"Necessary only if vmPerVMNotificationOptionalGroup is "Necessary only if vmPerVMNotificationOptionalGroup is
implemented." implemented."
GROUP vmBulkNotificationOptionalGroup GROUP vmBulkNotificationOptionalGroup
DESCRIPTION DESCRIPTION
"Support for bulk notifications is optional. If not "Support for bulk notifications is optional. If not
implemented then vmBulkNotificationsEnabled MUST report implemented, then vmBulkNotificationsEnabled MUST report
false(2)." false(2)."
::= { vmCompliances 1 } ::= { vmCompliances 1 }
vmReadOnlyCompliances MODULE-COMPLIANCE vmReadOnlyCompliances MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for implementations supporting "Compliance statement for implementations supporting
only readonly access." only read-only access."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
vmHypervisorGroup, vmHypervisorGroup,
vmVirtualMachineGroup, vmVirtualMachineGroup,
vmCpuGroup, vmCpuGroup,
vmCpuAffinityGroup, vmCpuAffinityGroup,
vmStorageGroup, vmStorageGroup,
vmNetworkGroup vmNetworkGroup
} }
skipping to change at page 40, line 33 skipping to change at page 40, line 47
vmMemUnit, vmMemUnit,
vmCurMem, vmCurMem,
vmMinMem, vmMinMem,
vmMaxMem, vmMaxMem,
vmUpTime, vmUpTime,
vmCpuTime vmCpuTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing insight into the "A collection of objects providing insight into the
virtual machines) controlled by a hypervisor." virtual machines controlled by a hypervisor."
::= { vmGroups 2 } ::= { vmGroups 2 }
vmCpuGroup OBJECT-GROUP vmCpuGroup OBJECT-GROUP
OBJECTS { OBJECTS {
-- vmCpuIndex, -- vmCpuIndex,
vmCpuCoreTime vmCpuCoreTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing insight into the "A collection of objects providing insight into the
virtual machines) controlled by a hypervisor." virtual machines controlled by a hypervisor."
::= { vmGroups 3 } ::= { vmGroups 3 }
vmCpuAffinityGroup OBJECT-GROUP vmCpuAffinityGroup OBJECT-GROUP
OBJECTS { OBJECTS {
-- vmCpuPhysIndex, -- vmCpuPhysIndex,
vmCpuAffinity vmCpuAffinity
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing insight into the "A collection of objects providing insight into the
virtual machines) controlled by a hypervisor." virtual machines controlled by a hypervisor."
::= { vmGroups 4 } ::= { vmGroups 4 }
vmStorageGroup OBJECT-GROUP vmStorageGroup OBJECT-GROUP
OBJECTS { OBJECTS {
-- vmStorageVmIndex, -- vmStorageVmIndex,
-- vmStorageIndex, -- vmStorageIndex,
vmStorageParent, vmStorageParent,
vmStorageSourceType, vmStorageSourceType,
vmStorageSourceTypeString, vmStorageSourceTypeString,
vmStorageResourceID, vmStorageResourceID,
skipping to change at page 43, line 18 skipping to change at page 43, line 31
IANA-STORAGE-MEDIA-TYPE-MIB DEFINITIONS ::= BEGIN IANA-STORAGE-MEDIA-TYPE-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, mib-2 MODULE-IDENTITY, mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC; FROM SNMPv2-TC;
ianaStorageMediaTypeMIB MODULE-IDENTITY ianaStorageMediaTypeMIB MODULE-IDENTITY
LAST-UPDATED "201508050000Z" -- 5 August 2015 LAST-UPDATED "201510120000Z" -- 12 October 2015
ORGANIZATION "IANA" ORGANIZATION "IANA"
CONTACT-INFO CONTACT-INFO
"Internet Assigned Numbers Authority "Internet Assigned Numbers Authority
Postal: ICANN Postal: ICANN
12025 Waterfront Drive, Suite 300 12025 Waterfront Drive, Suite 300
Los Angeles, CA 90094-2536 Los Angeles, CA 90094-2536
United States
Tel: +1 310-301-5800 Tel: +1 310-301-5800
E-Mail: iana&iana.org" Email: iana@iana.org"
DESCRIPTION DESCRIPTION
"This MIB module defines Textual Conventions "This MIB module defines Textual Conventions
representing the media type of a storage device. representing the media type of a storage device.
Copyright (c) 2015 IETF Trust and the persons identified Copyright (c) 2015 IETF Trust and the persons identified
as authors of the code. All rights reserved. as authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with Redistribution and use in source and binary forms, with
or without modification, is permitted pursuant to, and or without modification, is permitted pursuant to, and
subject to the license terms contained in, the subject to the license terms contained in, the
Simplified BSD License set forth in Section 4.c of the Simplified BSD License set forth in Section 4.c of the
IETF Trust's Legal Provisions Relating to IETF Documents IETF Trust's Legal Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info)." (http://trustee.ietf.org/license-info)."
REVISION "201508050000Z" -- 5 August 2015 REVISION "201510120000Z" -- 12 October 2015
DESCRIPTION DESCRIPTION
"The initial version of this MIB, published as "The initial version of this MIB, published as
RFCXXXX." RFC 7666."
::= { mib-2 zzz } ::= { mib-2 237 }
-- RFC Ed.: replace XXXX with RFC number and remove this note
-- RFC Ed.: replace zzz with actual number and remove this note
IANAStorageMediaType ::= TEXTUAL-CONVENTION IANAStorageMediaType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The media type of a storage device: "The media type of a storage device:
unknown(1) The media type is unknown, e.g., because unknown(1) The media type is unknown, e.g., because
the implementation failed to obtain the the implementation failed to obtain the
media type from the hypervisor. media type from the hypervisor.
skipping to change at page 44, line 32 skipping to change at page 45, line 7
unknown(2), unknown(2),
hardDisk(3), hardDisk(3),
opticalDisk(4), opticalDisk(4),
floppyDisk(5) floppyDisk(5)
} }
END END
7. IANA Considerations 7. IANA Considerations
This document defines the first version of the IANA-maintained IANA- This document defines the first version of the IANA-maintained
STORAGE-MEDIA-TYPE-MIB module, which allows new storage media types IANA-STORAGE-MEDIA-TYPE-MIB module, which allows new storage media
to be added to the enumeration in IANAStorageMediaType. An Expert types to be added to the enumeration in IANAStorageMediaType. An
Review, as defined in RFC 5226 [RFC5226], is REQUIRED for each Expert Review, as defined in RFC 5226 [RFC5226], is REQUIRED for each
modification. modification.
The MIB module in this document uses the following IANA-assigned The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value Descriptor OBJECT IDENTIFIER value
---------- ----------------------- ---------- -----------------------
vmMIB { mib-2 yyy } vmMIB { mib-2 236 }
IANAStorageMediaTypeMIB { mib-2 zzz } ianaStorageMediaTypeMIB { mib-2 237 }
8. Security Considerations 8. Security Considerations
This MIB module is typically implemented on the hypervisor not inside This MIB module is typically implemented on the hypervisor not inside
a virtual machine. Virtual machines, possibly under other a virtual machine. Virtual machines, possibly under other
administrative domains, would not have access to this MIB as the SNMP administrative domains, would not have access to this MIB as the SNMP
service would typically operate in a separate management network. service would typically operate in a separate management network.
There are two objects defined in this MIB module, There are two objects defined in this MIB module,
vmPerVMNotificationsEnabled and vmBulkNotificationsEnabled, that have vmPerVMNotificationsEnabled and vmBulkNotificationsEnabled, that have
skipping to change at page 45, line 26 skipping to change at page 45, line 48
read-write on deployments where SNMPv3 strong security (i.e., read-write on deployments where SNMPv3 strong security (i.e.,
authentication and encryption) is not used. authentication and encryption) is not used.
There are a number of managed objects in this MIB that may contain There are a number of managed objects in this MIB that may contain
sensitive information. The objects in the vmHvSoftware and sensitive information. The objects in the vmHvSoftware and
vmHvVersion list information about the hypervisor's software and vmHvVersion list information about the hypervisor's software and
version. Some may wish not to disclose to others which software they version. Some may wish not to disclose to others which software they
are running. Further, an inventory of the running software and are running. Further, an inventory of the running software and
versions may be helpful to an attacker who hopes to exploit software versions may be helpful to an attacker who hopes to exploit software
bugs in certain applications. Moreover, the objects in the vmTable, bugs in certain applications. Moreover, the objects in the vmTable,
vmCpuTable, vmCpuAffinityTable, vmStorageTable and vmCpuTable, vmCpuAffinityTable, vmStorageTable, and
vmNetworkTable list information about the virtual machines and their vmNetworkTable list information about the virtual machines and their
virtual resource allocation. Some may wish not to disclose to others virtual resource allocation. Some may wish not to disclose to others
how many and what virtual machines they are operating. how many and what virtual machines they are operating.
It is thus important to control even GET access to these objects and It is thus important to control even GET access to these objects and
possibly to even encrypt the values of these object when sending them possibly to even encrypt the values of these objects when sending
over the network via SNMP. Not all versions of SNMP provide features them over the network via SNMP. Not all versions of SNMP provide
for such a secure environment. features for such a secure environment.
SNMPv1 by itself is not a secure environment. Even if the network SNMPv1 by itself is not a secure environment. Even if the network
itself is secure (for example by using IPsec), even then, there is no itself is secure (for example by using IPsec), there is no control as
control as to who on the secure network is allowed to access and GET/ to who on the secure network is allowed to access and GET/SET
SET (read/change/create/delete) the objects in this MIB. (read/change/create/delete) the objects in this MIB module.
It is recommended that the implementers consider using the security It is recommended that the implementers consider using the security
features as provided by the SNMPv3 framework. Specifically, the use features as provided by the SNMPv3 framework. Specifically, the use
of the User-based Security Model [RFC3414] and the View-based Access of the User-based Security Model [RFC3414] and the View-based Access
Control Model [RFC3415] is recommended. Control Model [RFC3415] is recommended.
It is then a customer/user responsibility to ensure that the SNMP It is then a customer/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is properly entity giving access to an instance of this MIB is properly
configured to give access to the objects only to those principals configured to give access to the objects only to those principals
(users) that have legitimate rights to indeed GET or SET (change/ (users) that have legitimate rights to indeed GET or SET
create/delete) them. (change/create/delete) them.
9. Contributors
Yuji Sekiya
The University of Tokyo
2-11-16 Yayoi
Bunkyo-ku, Tokyo 113-8658
Japan
Email: sekiya@wide.ad.jp
Cathy Zhou
Huawei Technologies
Bantian, Longgang District
Shenzhen 518129
P.R. China
Email: cathyzhou@huawei.com
Hiroshi Esaki
The University of Tokyo
7-3-1 Hongo
Bunkyo-ku, Tokyo 113-8656
Japan
Email: hiroshi@wide.ad.jp
10. Acknowledgements
The authors like to thank Andy Bierman, David Black, Joe Marcus
Clarke, C.M. Heard, Joel Jaeggli, Tom Petch, Randy Presuhn, and Ian
West for providing helpful comments during the development of this
specification.
Juergen Schoenwaelder was partly funded by Flamingo, a Network of
Excellence project (ICT-318488) supported by the European Commission
under its Seventh Framework Programme.
11. References 9. References
11.1. Normative References 9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ Requirement Levels", BCP 14, RFC 2119,
RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information Schoenwaelder, Ed., "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, DOI 10.17487/ Version 2 (SMIv2)", STD 58, RFC 2578,
RFC2578, April 1999, DOI 10.17487/RFC2578, April 1999,
<http://www.rfc-editor.org/info/rfc2578>. <http://www.rfc-editor.org/info/rfc2578>.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD Schoenwaelder, Ed., "Textual Conventions for SMIv2",
58, RFC 2579, DOI 10.17487/RFC2579, April 1999, STD 58, RFC 2579, DOI 10.17487/RFC2579, April 1999,
<http://www.rfc-editor.org/info/rfc2579>. <http://www.rfc-editor.org/info/rfc2579>.
[RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Conformance Statements for SMIv2", Schoenwaelder, Ed., "Conformance Statements for SMIv2",
STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999, STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999,
<http://www.rfc-editor.org/info/rfc2580>. <http://www.rfc-editor.org/info/rfc2580>.
[RFC2790] Waldbusser, S. and P. Grillo, "Host Resources MIB", RFC [RFC2790] Waldbusser, S. and P. Grillo, "Host Resources MIB",
2790, DOI 10.17487/RFC2790, March 2000, RFC 2790, DOI 10.17487/RFC2790, March 2000,
<http://www.rfc-editor.org/info/rfc2790>. <http://www.rfc-editor.org/info/rfc2790>.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000, MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000,
<http://www.rfc-editor.org/info/rfc2863>. <http://www.rfc-editor.org/info/rfc2863>.
[RFC3413] Levi, D., Meyer, P., and B. Stewart, "Simple Network [RFC3413] Levi, D., Meyer, P., and B. Stewart, "Simple Network
Management Protocol (SNMP) Applications", STD 62, RFC Management Protocol (SNMP) Applications", STD 62,
3413, DOI 10.17487/RFC3413, December 2002, RFC 3413, DOI 10.17487/RFC3413, December 2002,
<http://www.rfc-editor.org/info/rfc3413>. <http://www.rfc-editor.org/info/rfc3413>.
[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management (USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", STD 62, RFC 3414, DOI 10.17487/ Protocol (SNMPv3)", STD 62, RFC 3414,
RFC3414, December 2002, DOI 10.17487/RFC3414, December 2002,
<http://www.rfc-editor.org/info/rfc3414>. <http://www.rfc-editor.org/info/rfc3414>.
[RFC3415] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based [RFC3415] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", STD 62, RFC 3415, DOI 10 Management Protocol (SNMP)", STD 62, RFC 3415,
.17487/RFC3415, December 2002, DOI 10.17487/RFC3415, December 2002,
<http://www.rfc-editor.org/info/rfc3415>. <http://www.rfc-editor.org/info/rfc3415>.
[RFC3418] Presuhn, R., Ed., "Management Information Base (MIB) for [RFC3418] Presuhn, R., Ed., "Management Information Base (MIB) for
the Simple Network Management Protocol (SNMP)", STD 62, the Simple Network Management Protocol (SNMP)", STD 62,
RFC 3418, DOI 10.17487/RFC3418, December 2002, RFC 3418, DOI 10.17487/RFC3418, December 2002,
<http://www.rfc-editor.org/info/rfc3418>. <http://www.rfc-editor.org/info/rfc3418>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
DOI 10.17487/RFC5226, May 2008, DOI 10.17487/RFC5226, May 2008,
<http://www.rfc-editor.org/info/rfc5226>. <http://www.rfc-editor.org/info/rfc5226>.
[RFC6933] Bierman, A., Romascanu, D., Quittek, J., and M. [RFC6933] Bierman, A., Romascanu, D., Quittek, J., and M.
Chandramouli, "Entity MIB (Version 4)", RFC 6933, DOI 10 Chandramouli, "Entity MIB (Version 4)", RFC 6933,
.17487/RFC6933, May 2013, DOI 10.17487/RFC6933, May 2013,
<http://www.rfc-editor.org/info/rfc6933>. <http://www.rfc-editor.org/info/rfc6933>.
11.2. Informative References 9.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, DOI 10.17487/
RFC3410, December 2002,
<http://www.rfc-editor.org/info/rfc3410>.
[IEEE8021-BRIDGE-MIB] [IEEE8021-BRIDGE-MIB]
IEEE, "IEEE8021-BRIDGE-MIB", October 2008, IEEE, "IEEE8021-BRIDGE-MIB", October 2008,
<http://www.ieee802.org/1/files/public/MIBs/ <http://www.ieee802.org/1/files/public/MIBs/
IEEE8021-BRIDGE-MIB-200810150000Z.txt>. IEEE8021-BRIDGE-MIB-200810150000Z.txt>.
[IEEE8021-Q-BRIDGE-MIB] [IEEE8021-Q-BRIDGE-MIB]
IEEE, "IEEE8021-BRIDGE-MIB", October 2008, IEEE, "IEEE8021-Q-BRIDGE-MIB", October 2008,
<http://www.ieee802.org/1/files/public/MIBs/ <http://www.ieee802.org/1/files/public/MIBs/
IEEE8021-Q-BRIDGE-MIB-200810150000Z.txt>. IEEE8021-Q-BRIDGE-MIB-200810150000Z.txt>.
[libvirt] The libvirt developers, "The libvirt virtialization API",
<http://www.libvirt.org/>.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410,
DOI 10.17487/RFC3410, December 2002,
<http://www.rfc-editor.org/info/rfc3410>.
[VMware] VMware, Inc., "The VMware Hypervisor",
<http://www.vmware.com/>.
[Xen] The Xen Project, "The Xen Hypervisor",
<http://www.xenproject.org/>.
Appendix A. State Transition Table Appendix A. State Transition Table
+--------------+----------------+--------------+--------------------+ +--------------+----------------+--------------+--------------------+
| State | Change to | Next state | Notification | | State | Change to | Next State | Notification |
| | vmAdminState | | | | | vmAdminState | | |
| | at the | | | | | at the | | |
| | hypervisor or | | | | | hypervisor or | | |
| | (Event) | | | | | (Event) | | |
+--------------+----------------+--------------+--------------------+ +--------------+----------------+--------------+--------------------+
| suspended | running | resuming | vmResuming | | | suspended | running | resuming | vmResuming | |
| | | | vmBulkResuming | | | | | vmBulkResuming |
| | | | | | | | | |
| suspending | (suspend | suspended | vmSuspended | | | suspending | (suspend | suspended | vmSuspended | |
| | operation | | vmBulkSuspended | | | operation | | vmBulkSuspended |
| | completed) | | | | | completed) | | |
| | | | | | | | | |
| running | suspended | suspending | vmSuspending | | | running | suspended | suspending | vmSuspending | |
| | | | vmBulkSuspending | | | | | vmBulkSuspending |
| | | | | | | | | |
| | shutdown | shuttingdown | vmShuttingdown | | | | shutdown | shuttingdown | vmShuttingdown | |
| | | | vmBulkShuttingdown | | | | | vmBulkShuttingdown |
| | | | | | | | | |
| | (migration to | migrating | vmMigrating | | | | (migration to | migrating | vmMigrating | |
| | other | | vmBulkMingrating | | | other | | vmBulkMigrating |
| | hypervisor | | | | | hypervisor | | |
| | initiated) | | | | | initiated) | | |
| | | | | | | | | |
| resuming | (resume | running | vmRunning | | | resuming | (resume | running | vmRunning | |
| | opeartion | | vmBulkRunning | | | operation | | vmBulkRunning |
| | completed) | | | | | completed) | | |
| | | | | | | | | |
| paused | running | running | vmRunning | | | paused | running | running | vmRunning | |
| | | | vmBulkRunning | | | | | vmBulkRunning |
| | | | | | | | | |
| shuttingdown | (shutdown | shutdown | vmShutdown | | | shuttingdown | (shutdown | shutdown | vmShutdown | |
| | operation | | vmBulkShutdown | | | operation | | vmBulkShutdown |
| | completed) | | | | | completed) | | |
| | | | | | | | | |
| shutdown | running | running | vmRunning | | | shutdown | running | running | vmRunning | |
skipping to change at page 50, line 14 skipping to change at page 50, line 35
| | | | | | | | | |
| (no state) | (preparation | preparing | - | | (no state) | (preparation | preparing | - |
| | initiated) | | | | | initiated) | | |
| | | | | | | | | |
| | (migrate from | shutdown (*) | vmShutdown | | | | (migrate from | shutdown (*) | vmShutdown | |
| | other | | vmBulkShutdown | | | other | | vmBulkShutdown |
| | hypervisor | | | | | hypervisor | | |
| | initiated) | | | | | initiated) | | |
+--------------+----------------+--------------+--------------------+ +--------------+----------------+--------------+--------------------+
State transition table for vmOperState State Transition Table for vmOperState
Acknowledgements
The authors would like to thank Andy Bierman, David Black, Joe Marcus
Clarke, C.M. Heard, Joel Jaeggli, Tom Petch, Randy Presuhn, and Ian
West for providing helpful comments during the development of this
specification.
Juergen Schoenwaelder was partly funded by Flamingo, a Network of
Excellence project (ICT-318488) supported by the European Commission
under its Seventh Framework Programme.
Contributors
Yuji Sekiya
The University of Tokyo
2-11-16 Yayoi
Bunkyo-ku, Tokyo 113-8658
Japan
Email: sekiya@wide.ad.jp
Cathy Zhou
Huawei Technologies
Bantian, Longgang District
Shenzhen 518129
China
Email: cathyzhou@huawei.com
Hiroshi Esaki
The University of Tokyo
7-3-1 Hongo
Bunkyo-ku, Tokyo 113-8656
Japan
Email: hiroshi@wide.ad.jp
Authors' Addresses Authors' Addresses
Hirochika Asai Hirochika Asai
The University of Tokyo The University of Tokyo
7-3-1 Hongo 7-3-1 Hongo
Bunkyo-ku, Tokyo 113-8656 Bunkyo-ku, Tokyo 113-8656
JP Japan
Phone: +81 3 5841 6748 Phone: +81 3 5841 6748
Email: panda@hongo.wide.ad.jp Email: panda@hongo.wide.ad.jp
Michael MacFaden Michael MacFaden
VMware Inc. VMware Inc.
Email: mrm@vmware.com Email: mrm@vmware.com
Juergen Schoenwaelder Juergen Schoenwaelder
skipping to change at page 50, line 44 skipping to change at page 52, line 33
Campus Ring 1 Campus Ring 1
Bremen 28759 Bremen 28759
Germany Germany
Email: j.schoenwaelder@jacobs-university.de Email: j.schoenwaelder@jacobs-university.de
Keiichi Shima Keiichi Shima
IIJ Innovation Institute Inc. IIJ Innovation Institute Inc.
2-10-2 Fujimi 2-10-2 Fujimi
Chiyoda-ku, Tokyo 102-0071 Chiyoda-ku, Tokyo 102-0071
JP Japan
Email: keiichi@iijlab.net Email: keiichi@iijlab.net
Tina Tsou Tina Tsou
Huawei Technologies (USA) Huawei Technologies (USA)
2330 Central Expressway 2330 Central Expressway
Santa Clara CA 95050 Santa Clara, CA 95050
USA United States
Email: tina.tsou.zouting@huawei.com Email: tina.tsou.zouting@huawei.com
 End of changes. 130 change blocks. 
266 lines changed or deleted 281 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/