Monitoring Domains
This section describes how to monitor logical domains (domains) by querying the
Oracle VM Server for SPARC MIB. This section also provides descriptions of
the various types of MIB output.
This section covers the following topics:
Setting Environment Variables
How to Set Environment Variables
Before you can query the Oracle VM Server for SPARC MIB, you
must set environment variables for the shell that you use. The values
are different for Oracle Solaris 10 and Oracle Solaris 11. This procedure
describes how to set these variables for the C shell, Bourne shell,
and Korn shell.
- Set the PATH, MIBDIRS, and MIBS environment variables for Oracle Solaris 10.
- For C shell users:
% setenv PATH /usr/sfw/bin:$PATH
% setenv MIBDIRS /opt/SUNWldmib/lib/mibs:/etc/sma/snmp/mibs
% setenv MIBS +SUN-LDOM-MIB
- For Bourne and Korn shell users:
$ PATH=/usr/sfw/bin:$PATH; export PATH
$ MIBDIRS=/opt/SUNWldmib/lib/mibs:/etc/sma/snmp/mibs; export MIBDIRS
$ MIBS=+SUN-LDOM-MIB; export MIBS
- Set the PATH, MIBDIRS, and MIBS environment variables for Oracle Solaris 11.
- For C shell users:
% setenv PATH /usr/bin:$PATH
% setenv MIBDIRS /opt/SUNWldmib/lib/mibs:/etc/net-snmp/snmp/mibs
% setenv MIBS +SUN-LDOM-MIB
- For Bourne and Korn shell users:
$ PATH=/usr/bin:$PATH; export PATH
$ MIBDIRS=/opt/SUNWldmib/lib/mibs:/etc/net-snmp/snmp/mibs; export MIBDIRS
$ MIBS=+SUN-LDOM-MIB; export MIBS
Querying the Oracle VM Server for SPARC MIB
How to Retrieve Oracle VM Server for SPARC MIB Objects
When a system has large number of domains, the SNMP agent might
time out before being able to respond to an SNMP request. To
increase the timeout value, use the -t option to specify a longer
timeout value. For example, the following snmpwalk command sets the timeout value
to 20 seconds:
# snmpwalk -t 20 -v1 -c public localhost SUN-LDOM-MIB::ldomTable
You can also use the -t option to specify the timeout value
for the snmpget and snmptable commands.
- Retrieve one or more MIB objects.
- Retrieve a single MIB object.
# snmpget -v version -c community-string host MIB-object
- Retrieve an array of MIB objects.
Use the snmpwalk or snmptable command.
# snmpwalk -v version -c community-string host MIB-object
# snmptable -v version -c community-string host MIB-object
Example 16-1 Retrieving a Single Oracle VM Server for SPARC MIB Object (snmpget)
The following snmpget command queries the value of the ldomVersionMajor object. The
command specifies snmpv1 (-v1) and a community string (-c public) for the
localhost host.
# snmpget -v1 -c public localhost SUN-LDOM-MIB::ldomVersionMajor.0
SUN-LDOM-MIB::ldomVersionMajor.0 = INTEGER: 1
Example 16-2 Retrieving Object Values From ldomTable (snmpwalk)
The following examples show how to use the snmpwalk command to retrieve
object values from ldomTable.
-
The following snmpwalk -v1 command returns the values for all objects in the ldomTable table:
# snmpwalk -v1 -c public localhost SUN-LDOM-MIB::ldomTable
SUN-LDOM-MIB::ldomName.1 = STRING: primary
SUN-LDOM-MIB::ldomName.2 = STRING: LdomMibTest_1
SUN-LDOM-MIB::ldomAdminState.1 = INTEGER: 0
SUN-LDOM-MIB::ldomAdminState.2 = INTEGER: 0
SUN-LDOM-MIB::ldomOperState.1 = INTEGER: active(1)
SUN-LDOM-MIB::ldomOperState.2 = INTEGER: bound(6)
SUN-LDOM-MIB::ldomNumVCpu.1 = INTEGER: 8
SUN-LDOM-MIB::ldomNumVCpu.2 = INTEGER: 4
SUN-LDOM-MIB::ldomMemSize.1 = INTEGER: 3360
SUN-LDOM-MIB::ldomMemSize.2 = INTEGER: 256
SUN-LDOM-MIB::ldomMemUnit.1 = INTEGER: megabytes(2)
SUN-LDOM-MIB::ldomMemUnit.2 = INTEGER: megabytes(2)
SUN-LDOM-MIB::ldomNumCrypto.1 = INTEGER: 1
SUN-LDOM-MIB::ldomNumCrypto.2 = INTEGER: 0
SUN-LDOM-MIB::ldomNumIOBus.1 = INTEGER: 2
SUN-LDOM-MIB::ldomNumIOBus.2 = INTEGER: 0
SUN-LDOM-MIB::ldomUUID.1 = STRING: 5f8817d4-5d2e-6f7d-c4af-91b5b34b5723
SUN-LDOM-MIB::ldomUUID.2 = STRING: 11284146-87ca-4877-8d80-cd0f60d5ec26
SUN-LDOM-MIB::ldomMacAddress.1 = STRING: 00:14:4f:46:47:d6
SUN-LDOM-MIB::ldomMacAddress.2 = STRING: 00:14:4f:f8:d5:6c
SUN-LDOM-MIB::ldomHostID.1 = STRING: 0x844647d6
SUN-LDOM-MIB::ldomHostID.2 = STRING: 0x84f8d56c
SUN-LDOM-MIB::ldomFailurePolicy.1 = STRING: ignore
SUN-LDOM-MIB::ldomFailurePolicy.2 = STRING: ignore
SUN-LDOM-MIB::ldomMaster.1 = STRING:
SUN-LDOM-MIB::ldomMaster.2 = STRING:
SUN-LDOM-MIB::ldomExtMapinSpace.1 = STRING: off
SUN-LDOM-MIB::ldomExtMapinSpace.2 = STRING: off
SUN-LDOM-MIB::ldomThreading.1 = STRING: max-throughput
SUN-LDOM-MIB::ldomThreading.2 = STRING: max-throughput
SUN-LDOM-MIB::ldomWholeCore.1 = INTEGER: 0
SUN-LDOM-MIB::ldomWholeCore.2 = INTEGER: 0
SUN-LDOM-MIB::ldomCpuArch.1 = STRING: native
SUN-LDOM-MIB::ldomCpuArch.2 = STRING: native
SUN-LDOM-MIB::ldomShutdownGroup.1 = INTEGER: 0
SUN-LDOM-MIB::ldomShutdownGroup.2 = INTEGER: 15
-
The following snmpwalk commands use snmpv2c and snmpv3 to retrieve the contents of ldomTable:
# snmpwalk -v2c -c public localhost SUN-LDOM-MIB::ldomTable
# snmpwalk -v 3 -u test -l authNoPriv -a MD5 -A testpassword localhost \
SUN-LDOMMIB::ldomTable
Example 16-3 Retrieving Object Values From ldomTable in Tabular Form (snmptable)
The following examples show how to use the snmptable command to retrieve
object values from ldomTable in tabular form.
-
The following snmptable -v1 command shows the contents of ldomTable in tabular form:
# snmptable -v1 -c public localhost SUN-LDOM-MIB::ldomTable
-
The following snmptable command shows the contents of ldomTable in tabular form by using snmpv2c.
Note that for the v2c or v3 snmptable command, use the -CB option to specify only GETNEXT, not GETBULK, requests to retrieve data.
# snmptable -v2c -CB -c public localhost SUN-LDOM-MIB::ldomTable
Retrieving Oracle VM Server for SPARC MIB Information
This section describes the information that you can retrieve from the Oracle
VM Server for SPARC MIB in the form of tables or scalar
objects.
Domain Table (ldomTable)
ldomTable is used to represent each domain in the system. Information includes
resource constraints for virtual CPUs, memory, cryptographic units, and I/O buses. The
table also includes other domain information, such as the universally unique identifier
(UUID), MAC address, host ID, failure policy, and master domain.
Table 16-1 Domain Table (ldomTable)
|
|
|
|
ldomIndex |
Integer |
Not accessible |
Integer
that is used as an index of this table |
ldomName |
Display string |
Read-only |
Name of the
domain |
ldomAdminState |
Integer |
Read/Write |
Starts or stops the domain for active management:
|
ldomOperState |
Integer |
Read-only |
Current state of the domain,
which can be one of the following values:
1 is the Active state
2 is the Stopping state
3 is the Inactive state
4 is the Binding state
5 is the Unbinding state
6 is the Bound state
7 is the Starting state
|
ldomNumVCPU |
Integer |
Read-only |
Number of virtual CPUs used.
If the domain is in an inactive state, this value is the
requested number of virtual CPUs. |
ldomMemSize |
Integer |
Read-only |
Amount of virtual memory used. If the domain
is in an inactive state, this value is the requested memory size. |
ldomMemUnit |
Integer |
Read-only |
One
of the following memory units:
1 is KB
2 is MB
3 is GB
4 is bytes
If not specified, the unit value is bytes. |
ldomNumCrypto |
Integer |
Read-only |
Number
of cryptographic units used. If the domain is in an inactive state,
this value is the requested number of cryptographic units. |
ldomNumIOBus |
Integer |
Read-only |
Number of physical I/O
devices used |
ldomUUID |
Display string |
Read-only |
UUID of the domain |
ldomMacAddress |
Display string |
Read-only |
MAC address of the domain |
ldomHostID |
Display string |
Read-only |
Host
ID of the domain |
ldomFailurePolicy |
Display string |
Read-only |
Master domain's failure policy, which can be one
of ignore, panic, reset, or stop |
ldomMaster |
Display string |
Read-only |
Name of up to four master
domains for a slave domain |
ldomExtMapinSpace |
Display string |
Read-only |
Extended mapin space for a domain. The
extended mapin space refers to the additional LDC shared memory space. This
memory space is required to support a large number of virtual I/O
devices that use direct-mapped shared memory. This space is also used by
virtual network devices to improve performance and scalability. The default value is
off. |
ldomThreading |
Display string |
Read-only |
Specifies the high instructions per cycle (IPC) threading control for a
domain. The dynamic threading provides control over the number of hardware threads
activated per core. Valid values are:
max-throughput, which means that all strands per core are active (default value)
max-ipc, which means that one strand per core is active
|
ldomWholeCore |
Integer |
Read-only |
Constrains the domain to use whole-cores only.
If the whole-core constraint is not enabled, the value is 0. Otherwise,
the value shows the number of max-cores. |
ldomCpuArch |
Display string |
Read-only |
CPU architecture for a domain.
The CPU architecture specifies whether the domain can be migrated to another
sun4v CPU architecture. Valid values are:
native, which means that the domain is only permitted to be migrated to platforms of the same sun4v CPU architecture (default value)
generic, which means that the domain is permitted to be migrated to all compatible sun4v CPU architectures
|
ldomShutdownGroup |
Integer |
Read-only |
Shutdown-group number for a guest domain. On
a SPARC64-X system, an SP-initiated ordered shutdown will shut down domains in
descending order of their shutdown-group numbers, from 15 to 0. The default
value is 15. |
|
Environment Variables Table (ldomEnvVarsTable)
ldomEnvVarsTable describes the OpenBoot PROM environment variables that all domains use.
Table 16-2 Environment Variables Table (ldomEnvVarsTable)
|
|
|
|
ldomEnvVarsLdomIndex |
Integer |
Read-only |
Integer
that is used as an index into ldomTable that represents the domain
that contains the OpenBoot PROM environment variables |
ldomEnvVarsIndex |
Integer |
Read-only |
Integer that is used to index
the OpenBoot PROM environment variables in this table |
ldomEnvVarsName |
Display string |
Read-only |
Name of the OpenBoot
PROM variable |
ldomEnvVarsValue |
Display string |
Read-only |
Value of the OpenBoot PROM variable |
|
Domain Policy Table (ldomPolicyTable)
ldomPolicyTable describes the dynamic resource management (DRM) policies that apply to all
domains.
Table 16-3 Domain Policy Table (ldomPolicyTable)
|
|
|
|
ldomPolicyLdomIndex |
Integer |
Read-only |
Integer that is used as an index into ldomTable that represents
the domain that contains the DRM policy |
ldomPolicyIndex |
Integer |
Not accessible |
Integer that is used to
index the DRM policy in this table |
ldomPolicyName |
Display string |
Read-only |
Policy name |
ldomPolicyStatus |
Display string |
Read-only |
Policy status |
ldomPolicyPriority |
Integer |
Read-only |
Priority that
is used to determine which DRM policy is selected when policies overlap |
ldomPolicyVcpuMin |
Integer |
Read-only |
Minimum
number of virtual CPUs for a domain |
ldomPolicyVcpuMax |
Integer |
Read-only |
Maximum number of virtual CPUs for
a domain. A value of unlimited uses the maximum integer value of
2147483647. |
ldomPolicyUtilLower |
Integer |
Read-only |
Lower utilization level at which policy analysis is triggered |
ldomPolicyUtilUpper |
Integer |
Read-only |
Upper utilization level at
which policy analysis is triggered |
ldomPolicyTodBegin |
Display string |
Read-only |
Effective start time of a policy with
a format of hh:mm:[ss] |
ldomPolicyTodEnd |
Display string |
Read-only |
Effective stop time of a policy with a
format of hh:mm:[ss] |
ldomPolicySampleRate |
Integer |
Read-only |
Resource cycle time in seconds |
ldomPolicyElasticMargin |
Integer |
Read-only |
Amount of buffer between util-lower property
(ldomPolicyUtilLower) and the number of free virtual CPUs to avoid oscillations at
low virtual CPU counts |
ldomPolicyAttack |
Integer |
Read-only |
Maximum amount of a resource to be added during
any one resource-control cycle. A value of unlimited uses the maximum integer
value of 2147483647. |
ldomPolicyDecay |
Integer |
Read-only |
Maximum amount of a resource to be removed during any
one resource-control cycle |
|
Service Processor Configuration Table (ldomSPConfigTable)
ldomSPConfigTable describes the service processor (SP) configurations for all domains.
Table 16-4 Service Processor Configuration Table (ldomSPConfigTable)
|
|
|
|
ldomSPConfigIndex |
Integer |
Not accessible |
Integer
that is used to index an SP configuration in this table |
ldomSPConfigName |
Display string |
Read-only |
SP
configuration name |
ldomSPConfigStatus |
Display string |
Read-only |
SP configuration status |
|
Domain Resource Pool and Scalar Variables
The following resources can be assigned to domains:
-
Virtual CPU (vcpu)
-
Memory (mem)
-
Cryptographic unit (mau)
-
Virtual switch (vsw)
-
Virtual network (vnet)
-
Virtual disk server (vds)
-
Virtual disk server device (vdsdev)
-
Virtual disk (vdisk)
-
Virtual console concentrator (vcc)
-
Virtual console (vcons)
-
Physical I/O device (io)
The following scalar MIB variables are used to represent resource pools and
their properties.
Table 16-5 Scalar Variables for CPU Resource Pool
|
|
|
|
ldomCpuRpCapacity |
Integer |
Read-only |
Maximum reservation allowed by the resource pool in ldomCpuRpCapacityUnits |
ldomCpuRpReserved |
Integer |
Read-only |
Accumulated processor
clock speed of the CPU, in MHz, that is currently reserved from
the resource pool |
ldomCpuRpCapacityUnit and ldomCpuRpReservedUnit |
Integer |
Read-only |
One of the following CPU allocation units:
The default
value is MHz. |
|
Table 16-6 Scalar Variables for Memory Resource Pool
|
|
|
|
ldomMemRpCapacity |
Integer |
Read-only |
Maximum reservation allowed by the resource pool in MemRpCapacityUnits |
ldomMemRpReserved |
Integer |
Read-only |
Amount
of memory, in MemRpReservedUnits, that is currently reserved from the resource pool |
ldomMemRpCapacityUnit
and ldomMemRpReservedUnit |
Integer |
Read-only |
One of the following memory allocation units:
1 is KB
2 is MB
3 is GB
4 is bytes
If not specified, the unit
value is bytes. |
|
Table 16-7 Scalar Variables for Cryptographic Resource Pool
|
|
|
|
ldomCryptoRpCapacity |
Integer |
Read-only |
Maximum reservation allowed by the resource pool |
ldomCryptoRpReserved |
Integer |
Read-only |
Number of cryptographic
units that is currently reserved from the resource pool |
|
Table 16-8 Scalar Variables for I/O Bus Resource Pool
|
|
|
|
ldomIOBusRpCapacity |
Integer |
Read-only |
Maximum reservation allowed
by the pool |
ldomIOBusRpReserved |
Integer |
Read-only |
Number of I/O buses that is currently reserved from the
resource pool |
|
Virtual CPU Table (ldomVcpuTable)
ldomVcpuTable describes the virtual CPUs that all domains use.
Table 16-9 Virtual CPU Table (ldomVcpuTable)
|
|
|
|
ldomVcpuLdomIndex |
Integer |
Read-only |
Integer that is
used as an index into ldomTable that represents the domain that contains
the virtual CPU |
ldomVcpuIndex |
Integer |
Not accessible |
Integer that is used to index the virtual CPU
in this table |
ldomVcpuDeviceID |
Display string |
Read-only |
Identifier of the virtual CPU (VID) |
ldomVcpuOperationalStatus |
Integer |
Read-only |
One of the following
CPU statuses: 1=Unknown 2=Other 3=OK 4=Degraded 5=Stressed 6=Predictive failure 7=Error 8=Nonrecoverable error 9=Starting 10=Stopping 11=Stopped 12=In service 13=No contact 14=Lost communication 15=Aborted 16=Dormant 17=Supporting entity in error 18=Completed 19=Power mode The default
value is 1 (Unknown) because the Logical Domains Manager does not provide
the CPU state. |
ldomVcpuPhysBind |
Display string |
Read-only |
Physical binding (PID). Contains the identifier of a hardware
thread (strand) that is assigned to this virtual CPU. This identifier uniquely
identifies the core and the chip. |
ldomVcpuPhysBindUsage |
Integer |
Read-only |
Indicates how much (in MHz) of the
total capacity of the thread is used by this virtual CPU. For
example, assume a thread can run at a maximum of one GHz.
If only half of that capacity is allocated to this virtual CPU
(50% of the thread), the property value is 500. |
ldomVcpuCoreID |
Display string |
Read-only |
Identifier of the
core (core ID). |
ldomVcpuUtilPercent |
Display string |
Read-only |
Indicates the utilization percentage of the virtual CPU. |
|
Virtual Memory Tables
A domain's memory space is referred to as real memory, that is, virtual memory.
Host platform memory space that is detected by the hypervisor is referred
to as physical memory. The hypervisor maps blocks of physical memory to form
a block of real memory that is used by a domain.
The following example shows that the requested memory size can be split
between two memory blocks instead of being assigned to a single large
memory block. Assume that a domain requests 521 Mbytes of real memory.
The memory can be assigned two 256-Mbyte blocks on the host system
as physical memory by using the {physical-address, real-address, size} format.
{0x1000000, 0x1000000, 256}, {0x2000000, 0x2000000,256}
A domain can have up to 64 physical memory segments assigned to
a guest domain. So, an auxiliary table, instead of a display string,
is used to hold each memory segment. A display string has a
255-character limit.
Virtual Memory Table (ldomVmemTable)
ldomVmemTable describes the properties of virtual memory that domains use.
Table 16-10 Virtual Memory Table (ldomVmemTable)
|
|
|
|
ldomVmemLdomIndex |
Integer |
Read-only |
Integer that
is used as an index into ldomTable that represents the domain that
contains the virtual memory |
ldomVmemIndex |
Integer |
Not accessible |
Integer that is used to index the virtual
memory in this table |
ldomVmemNumberofBlocks |
Integer |
Read-only |
Number of blocks of virtual memory |
|
Virtual Memory Physical Binding Table (ldomVmemPhysBindTable)
ldomVmemPhysBindTable is an auxiliary table that contains physical memory segments for all
domains.
Table 16-11 Virtual Memory Physical Binding Table (ldomVmemPhysBindTable)
|
|
|
|
ldomVmemPhysBindLdomIndex |
Integer |
Read-only |
Integer that is used as an index into ldomTable that represents
the domain that contains the physical memory segments |
ldomVmemPhysBind |
Display string |
Read-only |
List of physical memory
that is mapped to this virtual memory block in the following format:
{physical-address, real-address, size} |
|
Virtual Disk Tables
A virtual disk service (vds) and the physical device to which it
maps (vdsdev) provide the virtual disk capability to the Oracle VM Server
for SPARC technology. A virtual disk service exports a number of local
volumes (physical disks or file systems). When a virtual disk service is
specified, the following are included:
One or more disks, disk slices, and file systems can be bound
to a single disk service. Each disk has a unique name and
volume name. The volume name is used when the disk is bound
to the service. The Logical Domains Manager creates virtual disk clients (vdisk)
from the virtual disk service and its logical volumes.
Virtual Disk Service Table (ldomVdsTable)
ldomVdsTable describes the virtual disk services for all domains.
Table 16-12 Virtual Disk Service Table (ldomVdsTable)
|
|
|
|
ldomVdsLdomIndex |
Integer |
Read-only |
Integer that is
used as an index into ldomTable that represents the domain that contains
the virtual disk service |
ldomVdsIndex |
Integer |
Not accessible |
Integer that is used to index the virtual
disk service in this table |
ldomVdsServiceName |
Display string |
Read-only |
Service name for the virtual disk service.
The property value is the service-name specified by the ldm add-vds command. |
ldomVdsNumofAvailVolume |
Integer |
Read-only |
Number of
logical volumes exported by this virtual disk service |
ldomVdsNumofUsedVolume |
Integer |
Read-only |
Number of logical volumes used
(bound) to this virtual disk service |
|
Virtual Disk Service Device Table (ldomVdsdevTable)
ldomVdsdevTable describes the virtual disk service devices that all virtual disk services
use.
Table 16-13 Virtual Disk Service Device Table (ldomVdsdevTable)
|
|
|
|
ldomVdsdevVdsIndex |
Integer |
Read-only |
Integer that is used to index into ldomVdsTable that represents the
virtual disk service that contains the virtual disk device |
ldomVdsdevIndex |
Integer |
Not accessible |
Integer that is
used to index the virtual disk service device in this table |
ldomVdsdevVolumeName |
Display string |
Read-only |
Volume
name for the virtual disk service device. This property specifies a unique
name for the device that is being added to the virtual disk
service. This name is exported by the virtual disk service to the
clients for the purpose of adding this device. The property value is
the volume-name specified by the ldm add-vdsdev command. |
ldomVdsdevDevPath |
Display string |
Read-only |
Path name of the physical
disk device. The property value is the backend specified by the ldm add-vdsdev
command. |
ldomVdsdevOptions |
Display string |
Read-only |
One or more of the options for the disk device, which
are ro, slice, or excl |
ldomVdsdevMPGroup |
Display string |
Read-only |
Multipath group name for the disk device |
|
Virtual Disk Table (ldomVdiskTable)
ldomVdiskTable describes the virtual disks for all domains.
Table 16-14 Virtual Disk Table (ldomVdiskTable)
|
|
|
|
ldomVdiskLdomIndex |
Integer |
Read-only |
Integer that is used
as an index into ldomTable that represents the domain that contains the
virtual disk device |
ldomVdiskVdsDevIndex |
Integer |
Read-only |
Integer that is used to index into ldomVdsdevTable that represents
the virtual disk service device |
ldomVdiskIndex |
Integer |
Not accessible |
Integer that is used to index the
virtual disk in this table |
ldomVdiskName |
Display string |
Read-only |
Name of the virtual disk. The property
value is the disk-name specified by the ldm add-vdisk command. |
ldomVdiskTimeout |
Integer |
Read-only |
Timeout, in seconds, for
establishing a connection between a virtual disk client and a virtual disk
server |
ldomVdiskID |
Display string |
Read-only |
Identifier of the virtual disk |
|
The following figure shows how indexes are used to define relationships among
the virtual disk tables and the domain table. The indexes are used
as follows:
-
ldomIndex in ldomVdsTable and ldomVdiskTable points to ldomTable.
-
VdsIndex in ldomVdsdevTable points to ldomVdsTable.
-
VdsDevIndex in ldomVdiskTable points to ldomVdsdevTable.
Figure 16-3 Relationship Among Virtual Disk Tables and the Domain Table
Virtual Network Tables
Oracle VM Server for SPARC virtual network support enables guest domains to
communicate with each other and with external hosts through a physical Ethernet
device. The virtual network contains the following main components:
After you create a virtual switch on a service domain, you can
bind a physical network device to the virtual switch. After that, you
can create a virtual network device for a domain that uses the
virtual switch service for communication. The virtual switch service communicates with other
domains by connecting to the same virtual switch. The virtual switch service
communicates with external hosts if a physical device is bound to the
virtual switch.
Virtual Switch Service Table (ldomVswTable)
ldomVswTable describes the virtual switch services for all domains.
Table 16-15 Virtual Switch Service Table (ldomVswTable)
|
|
|
|
ldomVswLdomIndex |
Integer |
Read-only |
Integer that is
used as an index into ldomTable that represents the domain that contains
the virtual switch service |
ldomVswIndex |
Integer |
Not accessible |
Integer that is used to index the virtual
switch device in this table |
ldomVswServiceName |
Display string |
Read-only |
Virtual switch service name |
ldomVswMacAddress |
Display string |
Read-only |
MAC address used
by the virtual switch |
ldomVswPhysDevPath |
Display string |
Read-only |
Physical device path for the virtual network switch.
The property value is null when no physical device is bound to
the virtual switch. |
ldomVswMode |
Display string |
Read-only |
Value is mode=sc for running cluster nodes |
ldomVswDefaultVlanID |
Display string |
Read-only |
Default VLAN
ID for the virtual switch |
ldomVswPortVlanID |
Display string |
Read-only |
Port VLAN ID for the virtual switch |
ldomVswVlanID |
Display
string |
Read-only |
VLAN ID for the virtual switch |
ldomVswLinkprop |
Display string |
Read-only |
Value is linkprop=phys-state to report the
link status based on the physical network device |
ldomVswMtu |
Integer |
Read-only |
Maximum transmission unit (MTU) for
a virtual switch device |
ldomVswID |
Display string |
Read-only |
Identifier of the virtual switch device |
ldomVswInterVnetLink |
Display string |
Read-only |
State of
LDC channel assignment for inter-vnet communications. Value is either on or off. |
|
Virtual Network Device Table (ldomVnetTable)
ldomVnetTable describes the virtual network devices for all domains.
Table 16-16 Virtual Network Device Table (ldomVnetTable)
|
|
|
|
ldomVnetLdomIndex |
Integer |
Read-only |
Integer that is
used as an index into ldomTable that represents the domain that contains
the virtual network device |
ldomVnetVswIndex |
Integer |
Read-only |
Integer that is used to index into the virtual
switch service table |
ldomVnetIndex |
Integer |
Not accessible |
Integer that is used to index the virtual network
device in this table |
ldomVnetDevName |
Display string |
Read-only |
Virtual network device name. The property value is
the net-dev property specified by the ldm add-vnet command. |
ldomVnetDevMacAddress |
Display string |
Read-only |
MAC address for this
network device. The property value is the mac-addr property specified by the
ldm add-vnet command. |
ldomVnetMode |
Display string |
Read-only |
Value is mode=hybrid to use NIU hybrid I/O on the
virtual network device |
ldomVnetPortVlanID |
Display string |
Read-only |
Port VLAN ID for the virtual network device |
ldomVnetVlanID |
Display string |
Read-only |
VLAN
ID for the virtual network device |
ldomVnetLinkprop |
Display string |
Read-only |
Value is linkprop=phys-state to report the
link status based on the physical network device |
ldomVnetMtu |
Integer |
Read-only |
MTU for a virtual network
device |
ldomVnetID |
Display string |
Read-only |
Identifier of the virtual network device |
|
Virtual Console Tables
The Oracle VM Server for SPARC service domain provides a virtual network
terminal service (vNTS). vNTS provides a virtual console service, called a virtual
console concentrator (vcc), with a range of port numbers. Each virtual console
concentrator has multiple console groups (vcons), and each group is assigned a
port number. Each group can contain multiple domains.
Virtual Console Concentrator Table (ldomVccTable)
ldomVccTable describes the virtual console concentrators for all domains.
Table 16-17 Virtual Console Concentrator Table (ldomVccTable)
|
|
|
|
ldomVccLdomIndex |
Integer |
Read-only |
Integer that is
used as an index into ldomTable that represents the domain that contains
the virtual console service |
ldomVccIndex |
Integer |
Not accessible |
Integer that is used to index the virtual
console concentrator in this table |
ldomVccName |
Display string |
Read-only |
Virtual console concentrator name. The property value
is the vcc-name specified by the ldm add-vcc command. |
ldomVccPortRangeLow |
Integer |
Read-only |
Low number for the range
of TCP ports to be used by the virtual console concentrator. The
property value is the x part of the port-range specified by the
ldm add-vcc command. |
ldomVccPortRangeHigh |
Integer |
Read-only |
High number for the range of TCP ports to be used
by the virtual console concentrator. The property value is the y part
of the port-range specified by the ldm add-vcc command. |
|
Virtual Console Group Table (ldomVconsTable)
ldomVconsTable describes the virtual console groups for all virtual console services.
Table 16-18 Virtual Console Group Table (ldomVconsTable)
|
|
|
|
ldomVconsIndex |
Integer |
Not
accessible |
Integer that is used to index a virtual group in this table |
ldomVconsGroupName |
Display
string |
Read-only |
Group name to which to attach the virtual console. The property value
is the group specified by the ldm set-vcons command. |
ldomVconsPortNumber |
Integer |
Read-only |
Port number assigned to this
group. The property value is the port specified by the ldm set-vcons command. |
|
Virtual Console Relationship Table (ldomVconsVccRelTable)
ldomVconsVccRelTable contains index values to show the inter-table relationships among a domain,
a virtual console concentrator, and console groups.
Table 16-19 Virtual Console Relationship Table (ldomVconsVccRelTable)
|
|
|
|
ldomVconsVccRelVconsIndex |
Integer |
Read-only |
Value of ldomVconsIndex in ldomVconsTable |
ldomVconsVccRelLdomIndex |
Integer |
Read-only |
Value
of ldomIndex in ldomTable |
ldomVconsVccRelVccIndex |
Integer |
Read-only |
Value of ldomVccIndex in ldomVccTable |
|
The following figure shows how indexes are used to define relationships among
the virtual console tables and the domain table. The indexes are used
as follows:
-
ldomIndex in ldomVccTable and ldomVconsVccRelTable points to ldomTable.
-
VccIndex in ldomVconsVccRelTable points to ldomVccTable.
-
VconsIndex in ldomVconsVccRelTable points to ldomVconsTable.
Figure 16-4 Relationship Among Virtual Console Tables and the Domain Table
Cryptographic Units Table (ldomCryptoTable)
ldomCryptoTable describes the cryptographic units that all domains use. A cryptographic unit
is sometimes referred to as a modular arithmetic unit (MAU).
Table 16-20 Cryptographic Units Table (ldomCryptoTable)
|
|
|
|
ldomCryptoLdomIndex |
Integer |
Read-only |
Integer that
is used as an index into ldomTable that represents the domain that
contains the cryptographic unit |
ldomCryptoIndex |
Integer |
Not accessible |
Integer that is used to index the cryptographic
unit in this table |
ldomCryptoCpuSet |
Display string |
Read-only |
List of CPUs that is mapped to MAU-unit cpuset.
For example, {0, 1, 2, 3}. |
|
I/O Bus Table (ldomIOBusTable)
ldomIOBusTable describes the physical I/O devices and PCI buses that all domains
use.
Table 16-21 I/O Bus Table (ldomIOBusTable)
|
|
|
|
ldomIOBusLdomIndex |
Integer |
Read-only |
Integer that is used as an index into ldomTable that represents
the domain that contains the I/O bus |
ldomIOBusIndex |
Integer |
Not accessible |
Integer that is used to
index the I/O bus in this table |
ldomIOBusName |
Display string |
Read-only |
Physical l/O device name |
ldomIOBusPath |
Display string |
Read-only |
Physical
I/O device path |
ldomIOBusOptions |
Display string |
Read-only |
Physical I/O device options |
|
Core Table (ldomCoreTable)
ldomCoreTable describes the core information, such as core-id and cpuset, for all
domains.
Table 16-22 Core Table (ldomCoreTable)
|
|
|
|
ldomCoreLdomIndex |
Integer |
Read-only |
Integer that is used as an index into ldomTable that represents
the domain that contains the core |
ldomCoreIndex |
Integer |
Not accessible |
Integer that is used to index
a core in this table |
ldomCoreID |
Display string |
Read-only |
Identifier of a core (core ID) |
ldomCoreCpuSet |
Display string |
Read-only |
List
of CPUs that is mapped to the core cpuset |
|
Scalar Variables for Logical Domains Version Information
The Logical Domains Manager protocol supports Logical Domains versions, which consists of
a major number and a minor number. The Oracle VM Server for
SPARC MIB has scalar variables to describe the Logical Domains version information.
Table 16-23 Scalar Variables for Logical Domains Version Information
|
|
|
|
ldomVersionMajor |
Integer |
Read-only |
Major version number |
ldomVersionMinor |
Integer |
Read-only |
Minor version number |
|
The values for ldomVersionMajor and ldomVersionMinor are equivalent to the version shown
by the ldm list -p command. For example:
$ ldm ls -p
VERSION 1.6
...
$ snmpget -v1 -c public localhost SUN-LDOM-MIB::ldomVersionMajor.0
SUN-LDOM-MIB::ldomVersionMajor.0 = INTEGER: 1
$ snmpget -v1 -c public localhost SUN-LDOM-MIB::ldomVersionMinor.0
SUN-LDOM-MIB::ldomVersionMinor.0 = INTEGER: 5