Information about settings in the IBM VGP XML file

This topic contains the following sections:

Description of sections and settings

Section

Settings

<GeneralInfo>

<Name> and <Description> — Name and description of the Virtual Guest Package (VGP).
<DepotGroupId> — You store VGPs in the Depot. You can get the ID of a depot group by using the command DepotGroup : groupNameToId.
<VirtualGuestPackageType> — Specify one of the following integers:
3 — ManagedSystemLpar
4 — ManagedSystemVIO
<VirtualGuestName> — The partition name for the VGP.

<PartitionInfo>

This section is mandatory. It contains all partition information for the LPAR or VIO server

<PartitionGeneralSettings>

This section is mandatory and represents general settings of the partition.
<PartitionId> — Optional. If you specify an ID here, the partition is created with the ID. Otherwise, it is autogenerated by Managed System.
<ProfileName> — Optional. Name of the profile for the partition. If you specify a name here, the profile is created with the name. Otherwise, the profile name is taken from the VirtualGuestName element in the <GeneralInfo> section.
<UseAllResources> — Valid values are:
 false — Do not use all the managed system resources.
true — Use all the managed system resources.

<OptionalSettings> —

  • <ConnectionMonitoring> — Valid values are: true or false
  • <AutoStartManagedSystem> — Valid values are: true or false
  • <RedundantErrorPathReporting> — Valid values are: true or false
  • <BootMode> — Applies only to IBM AIX, Linux, and virtual I/O servers. Valid values are:
    • norm — normal
    • dd — diagnostic with default boot list
    • ds — diagnostic with stored boot list
    • of — Open Firmware OK prompt
    • sms — System Management Services
  • <WorkloadGroupId> — Name of the workload group of the Managed System.
  • <MoverServicePartition> — Applies only to virtual I/O servers, POWER6 servers. Valid values are:
    • false — The partition is not a mover service partition.
    • true — The partition is a mover service partition.
<ProcessorSettings>

<ProcessorMode> — Valid values are:
*ded — dedicated processors
8shared — shared processors

<ProcessorSharingMode> — Valid values for partitions using dedicated processors are:
keep_idle_procs — never share processors
share_idle_procs — share processors only when partition is inactive
share_idle_procs_active — share processors only when partition
is active (POWER6 servers only)
share_idle_procs_always — always share processors (POWER6 servers only)

Valid values for partitions using shared processors are:
cap — capped
uncap — uncapped

<MinimumProcessingUnits> — Double value, for example: 1.0
<DesiredProcessingUnits> — Double value, for example: 1.0
<MaximumProcessingUnits> — Double value, for example: 1.0
<SharedPool> — Name of the shared processor pool. For information on how to get this name, see To get the IBM shared processor pool name.
<MinimumProcessors> — Positive int value, for example: 1
<DesiredProcessors> — Positive int value, for example: 1
<MaximumProcessors> — Positive int value, for example: 1
<UncappedWeight> — Positive int value, for example: 128

<MemorySettings>>

<MemoryMode> — Set to either dedicated memory or shared memory, using the following values:
ded — Dedicated. This is the default.
shared ---Setting <MemoryMode> to shared applies only to client partitions. Also, you cannot assign physical adapters, lhea and dedicated processors if <MemoryMode> is set to shared.

<PrimaryPagingVIOS> — Name of the primary paging VIOS partition. For information on how to get this value, see To get the VIOS paging partitions.
<SecondaryPagingVIOS> — Set this to the name of the secondary paging VIOS partition, or to None. For information on how to get this value, see To get the VIOS paging partitions.
<MemoryWeight> — The shared memory weight of the shared memory partition. The memory weight is used to determine the priority of logical partitions in a memory pool for distributing memory. Valid values are 0 - 255. The default value is 128.
<CustomEntitledMemory> — The amount of I/O entitled memory for a shared memory partition. This means the guaranteed amount of physical memory that will get to this partition from the frame. Set <CustomEntitledMemory> to one of the following values:
0 (not specified)
A number that is less than to value specified for <DesiredMemory>.

<MinimumMemory> — Expressed in MB. Positive int value, for example: 128
<DesiredMemory> — Expressed in MB. Positive int value, for example: 128
<MaximumMemory> — Expressed in MB. Positive int value, for example: 128

<Storage>

FOR client LPARs: You can provide storage information in either of the following ways:

  • Fill in the <Storage> section. The <Storage> section applies only to client partitions.
  • Provide virtual client SCSI/FC adapters.

For VIOServer partitions — You can provide only SCSI/FC adapters.
<VirtualDisk>
<Name> — Optional. Name of the virtual disk. If you do not provide this value, the system automatically generates a name, using the following format:

lv_s<<adapter_id>>_c<<adapter_id>>

<SizeInGB> — size of disk, expressed in GB
<Location> — The VIOServer is the specialized partition on the frame that serves I/O resources to client partitions. For information on how to get the virtual disk <Location> value, see To get the storage locations.
<PhysicalVolume>
<Location> — The VIOServer is the specialized partition on the frame that serves I/O resources to client partitions. For information on how to get the physical volume <Location> value, see To get the storage locations.

<FiberChannelPort>
<Location> — The VIOServer is the specialized partition on the frame that serves I/O resources to client partitions. For information on how to get the fiber channel port <Location> value, see To get the storage locations.

<PhysicalIO>

<SlotDRCIndex> — DRC Index of physical slot. For information on how to get this index, see To get the DRC index.
<SlotIOPoolId> — Optional. I/O pool ID to assign this physical adapter.
<Required> — Indicates whether this slot is required or not at the time of LPAR/VIO startup. Valid values are: true/false.

<VirtualAdapters>

<MaxVirtualAdapters> — Maximum number of virtual adapters that can be assigned to the parition. Value can be a positive integer, for example: 10

<EthernetAdapter>

<AdapterId> — Positive integer, for example:3. Note the following restrictions:

For LPAR, the first 2 AdapterIds (1,2) are reserved for default serial adapters. So the available AdapterId must start with 3 and must be less than <MaxVirtualAdapters> value defined for that LPAR.

For VIO, the first 10 AdapterIds (1,2..10) are reserved for default serial adapters. So the available AdapterId must start with 11 and must be less than <MaxVirtualAdapters> value defined for that LPAR.

AdapterId should be unique for all virtual adapters defined for the LPAR/VIO.

<VirtualSwitch> — Name of the virtual switch. For information on how to get this name, see To get the virtual switch name.
Name of the virtual switch can be retrieved from the CLI:
<VLANId> — Positive integer, for example:1
<Required> — Valid values are: true/false.
<AccessExternalNetwork> — True – Partition can connect to external network through this Ethernet adapter. False – Partition cannot connect to external network through this Ethernet adapter.
<TrunkPriority> — Valid values are:
0 — This adapter is not a trunk adapter
1 - 15 — This adapter is a trunk adapter with the specified priority
<AdditionalVLANs> — Lets you define additional vlanIds. The valid value is a comma separated list of non-negative numbers, for example: 2,3

<FiberChannelAdapter>

<AdapterId> — Positive integer, for example:3. Note the following restrictions:

For LPAR, the first 2 AdapterIds (1,2) are reserved for default serial adapters. So the available AdapterId must start with 3 and must be less than the <MaxVirtualAdapters> value defined for that LPAR.

For VIO, the first 10 AdapterIds (1,2..10) are reserved for default serial adapters. So the available AdapterId must with 11 and must be less than the <MaxVirtualAdapters> value defined for that LPAR.

AdapterId must be unique for all virtual adapters defined for the LPAR/VIO.

<AdapterType> — Valid values are:
client - Use with LPAR type packages
server - Use with VIOS type packages

<Required> — Valid values are: true/false.
<RemotePartitionName> — Name of the remote partition:
For LPAR type packages, it should be the VIOS name.
For VIOS type packages, it should be the LPAR name.

<RemoteAdapterId> — ID of the remote partition:
For LPAR type packages, it should be the VIOS ID.
For VIOS type packages, it should be the LPAR ID

<SCSIAdapter>>

<AdapterId> — Positive integer, for example:3. Note the following restrictions:

For LPAR, the first 2 adapterIds (1,2) are reserved for default serial adapters. So the available adapterId must start with 3 and must be less than the <MaxVirtualAdapters> value defined for that LPAR.

For VIO, the first 10 adapterIds (1,2..10) are reserved for default serial adapters. So the available adapterId must start with 11 and must be less than the <MaxVirtualAdapters> value defined for that LPAR.

<AdapterId> should be unique for all virtual adapters defined for the LPAR/VIO.

<AdapterType> — Valid values are:
client — Use with LPAR type packages
server — Use with VIOS type packages

<Required> — Valid values are: true/false.
<RemotePartitionName> — Name of the remote partition:
For LPAR type packages, it should be the VIOS name.
For VIOS type packages, it should be the LPAR name.

<RemoteAdapterId> — ID of the remote partition:
For LPAR type packages, it should be the VIOS ID.
For VIOS type packages, it should be the LPAR ID.

<SerialAdapter>

<AdapterId> — Positive integer, for example:3. Note the following restrictions:

For LPAR, the first 2 adapterIds (1,2) are reserved for default serial adapters. So the available adapterId must start with 3 and must be less than the <MaxVirtualAdapters> value defined for that LPAR.

For VIO, the first 10 adapterIds (1,2..10) are reserved for default serial adapters. So the available adapterId must start with 11 and must be less than the <MaxVirtualAdapters> value defined for that LPAR.

AdapterId should be unique for all virtual adapters defined for the LPAR/VIO.

<AdapterType> — Valid values are:
client
server

<Required> — Valid values are true or false.
<SupportsHMC> — Valid values are true orfalse.
<ConnectingRemotePartition> —

  • <RemotePartitionName> — Name of the remote partition
  • <RemoteAdapterId> — ID of the remote partition
<LHEA>

<AdapterId> — Positive integer, for example: 23000000
<PortGroup> — Positive integer, for example:1 . For information on how to get the port group, see To get the port settings - PortGroup, PhysicalPortId, LogicalPortId.
<PhysicalPortId> — Positive integer, for example:1. For information on how to get the physical port ID, see To get the port settings - PortGroup, PhysicalPortId, LogicalPortId.
<LogicalPortId> — Positive integer, for example:1. For information on how to get the physical port ID, see To get the port settings - PortGroup, PhysicalPortId, LogicalPortId.
<AllowAllVLANIDs> — Valid values are: true/false.
<AllowedVLANs> — Specifies allowed vlanIds. The valid value is comma-separated list of non-negative numbers, for example: 2,3

To get the managed system ID - IBM

Some of the commands you use to get VGP values require you to pass in the ID of the Managed System.

To do this, use the listVirtualEntityManagers command, and pass in an EntityType of ManagedSystem:

Command

Virtualization listVirtualEntityManagers ManagedSystem

Output format

ManagedSystemID::ManagedSystemName

Output example

1::MyManagedSystem

In this example, the Managed System ID is 1.

To get the IBM shared processor pool name

  1. Get the Managed System ID, as described in To get the managed system ID - IBM. For the purpose of this example, assume the ID is 1.

  2. Use the listVirtualEntitiesByEntityManagerServerIdAndEntityType command to get the shared processor pool name. This command takes 2 arguments – ServerId and EntityType. You already have the ServerId (1). Because you want a shared processor pool name, you specify ManagedSystemSharedProcessorPool as EntityType:

    Command

    Virtualization listVirtualEntitiesByEntityManagerServerIdAndEntityType 1 ManagedSystemSharedProcessorPool

    Output format

    Name

    Output example

    Pool1 \\
    Pool2 \\
    Pool3

    Example: In the VGP file, you might specify:

    <SharedPool>Pool3</SharedPool>

To get the DRC index

  1. Get the Managed System ID, as described in To get the managed system ID - IBM. For the purpose of this example, assume the ID is 1.

  2. Use the listVirtualEntitiesByEntityManagerServerIdAndEntityType command to get the shared processor pool name. This command takes 2 arguments – ServerId and EntityType. You already have the ServerId (1). Because you want a DRC index, you specify ManagedSystemPhysicalAdapters as EntityType:

    Command

    Virtualization listVirtualEntitiesByEntityManagerServerIdAndEntityType 1 ManagedSystemPhysicalAdapters

    Output format

    Slot::Description::DRC Index::Location Code::I/O Pool Id::Partition Name::Partition Id

    Output example

    C1::Empty slot::21010204::U789C.001.DQDJ634-P1-C1::none::::0
    C2::4 Gigabit PCI Express Single Port Fibre Channel Adapter::21010205::U789C.001.DQDJ634-P1-C2::none::viosrdsaix03::1
    C3::Empty slot::21010207::U789C.001.DQDJ634-P1-C3::none::::0
    C4::Empty slot::21010202::U789C.001.DQDJ634-P1-C4::none::::0
    C5::Empty slot::21010203::U789C.001.DQDJ634-P1-C5::none::::0
    C9::Empty slot::21010206::U789C.001.DQDJ634-P1-C9::none::::0
    T7::Universal Serial Bus UHC Spec::21010201::U789C.001.DQDJ634-P1-T7::none::Automation_pun-lpar-rds28::3
    T9::RAID Controller::21010200::U789C.001.DQDJ634-P1-T9::1::viosrdsaix03::1

    The DRC index is the third field. For example, the DRC index for the RAID Controller in the sample output shown above is 21010200.

    for example, in the VGP file you might specify the following:

    <SlotDRCIndex>21010200</SlotDRCIndex>

To get the virtual switch name

  1. Get the Managed System ID, as described in To get the managed system ID - IBM. For the purpose of this example, assume the ID is 1.

  2. Use the listVirtualEntitiesByEntityManagerServerIdAndEntityType command to get the virtual switch name. This command takes 2 arguments – ServerId and EntityType. You already have the ServerId (1). Because you want a virtual switch name, you specify ManagedSystemLPARVirtualEthernet as EntityType:

    Command

    Virtualization listVirtualEntitiesByEntityManagerServerIdAndEntityType 1 ManagedSystemLPARVirtualEthernet

    Output format

    VIO Server::Name::Virtual Switch::VLAN ID::Additional VLAN IDs::Status

    Output example

    Automation_VIO::Eth_11::ETHERNET0::1::::Unavailable
    viosrdsaix03::Eth_11::ETHERNET0::1::::Available

    The virtual switch is the third field. For example, in the sample output above, the virtual switch is ETHERNET0.

    Forexample, in the VGP file you might specify the following:

    <VirtualSwitch>ETHERNET0</VirtualSwitch>

To get the port settings - PortGroup, PhysicalPortId, LogicalPortId

  1. Get the Managed System ID, as described in To get the managed system ID - IBM. For the purpose of this example, assume the ID is 1.

  2. Use the listVirtualEntitiesByEntityManagerServerIdAndEntityType command to get the port settings. This command takes 2 arguments – ServerId and EntityType. You already have the ServerId (1).
    For EntityType, specify ManagedSystemHEALogicalPort.

    Command

    Virtualization listVirtualEntitiesByEntityManagerServerIdAndEntityType 1 ManagedSystemHEALogicalPort

    Output format

    Logical Port Id::Adapter Id::Port Group::Physical Port Id::VLAN Id List::Partition Id::Partition Name::Status

    Output example

    1::23000000::1::0::all::1::viosrdsaix03::Available
    10::23000000::1::0::none::none::::Unavailable
    11::23000000::1::0::none::none::::Unavailable

    PortGroup: Third field
     PhysicalPortId: Fourth field
     LogicalPortId: First field

    For example, in the VGP file you might specify the following:

    <PortGroup>1</PortGroup>
    <PhysicalPortId>0</PhysicalPortId>
    <LogicalPortId>1</LogicalPortId>

To get the storage locations

The <Storage> element requires you to provide <Location> values for the following elements:

  • <VirtualDisk>
  • <PhysicalVolume>
  • <FiberChannelPort>
  1. Get the Managed System ID, as described in To get the managed system ID - IBM. For the purpose of this example, assume the ID is 1.

  2. Use the listVirtualEntitiesByEntityManagerServerIdAndEntityType command to get the location you want. This command takes 2 arguments – ServerId and EntityType. You already have the ServerId(1). Depending on which <Location> value you want, specify one of the following strings as EntityType:

    <Location> value

    String for EntityType

    <VirtualDisk>

    ManagedSystemStoragePool

    <PhysicalVolume>

    ManagedSystemAvailableDisks

    <FiberChannelPort>

    ManagedSystemFiberChannelHBAPorts

    This example continues with getting a <Location> value for <VirtualDisk>. You can use the same general procedure to get <Location> values for <PhysicalVolume> and <FiberChannelPort>.

    Because you want a virtual disk storage location, you specify ManagedSystemStoragePool as EntityType:

    Command

    Virtualization listVirtualEntitiesByEntityManagerServerIdAndEntityType 1 ManagedSystemStoragePool

    Output format

    VIO Server::Storage Location::Total Size(GB)::Available Size(GB)

    Output example

    SSBVIO1::viosrdsaix03:client_vg::279.0::268.5
    viosrdsaix03::viosrdsaix03:client_vg::279.0::268.5
    SSBVIO1::viosrdsaix03:rootvg::279.0::233.5
    viosrdsaix03::viosrdsaix03:rootvg::279.0::233.5


    The <Location> field requires you to provide the contents of the Storage Location field, for example, viosrdsaix03:client_vg.

    For example, n the VGP file, you might specify the following:

    <Location>viosrdsaix03:client_vg</Location>

To get the VIOS paging partitions

You can get the names of the primary and secondary VIOS paging partitions.

  1. Get the Managed System ID, as described in To get the managed system ID - IBM. For the purpose of this example, assume the ID is 1.

  2. Ue the listVirtualEntitiesByEntityManagerServerIdAndEntityType command to get the paging partitions. This command takes 2 arguments – ServerId and EntityType. You already have the ServerId (1). Because you want a paging partition, you specify ManagedSystemSharedMemoryPool as EntityType:

    Command

    Virtualization listVirtualEntitiesByEntityManagerServerIdAndEntityType 1 ManagedSystemSharedMemoryPool

    Output format

    Supported VIOServers::Maximum Pool Size(mb)::Pool Size(MB)::Available pool memory(MB)

    Output example

    viosrdsaix03::1024::1024::634

    For example, in the VGP file you might specify the following:

    <PrimaryPagingVIOS>viosrdsaix03</PrimaryPagingVIOS>

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*