Top
ServerView Resource Orchestrator Cloud Edition V3.1.1 Reference Guide (Command/XML)
ServerView
Part 2 File Reference > Chapter 15 XML Files > 15.3 L-Servers > 15.3.1 Definition Information for Physical L-Servers (XML)
PreviousNext

15.3.1 Definition Information for Physical L-Servers (XML)

This section explains the XML definitions of physical L-Servers.

To specify the level, change the Resources element to the Folder element.

Refer to "Example Creating an L-Server in a resource folder or a tenant".

The XML definition for a physical L-Server is shown below.

<?xml version="1.0" encoding="utf-8"?>
<Resources>
  <LServer name="L-Server Name" label="Label">
    <Comment>Comment</Comment>
    <TemplateLink name="L-Server Template Name"/>
    <ServerImageLink name="Image Name" version="Image Version"/>
    <FCConnectionPattern>FC connection pattern</FCConnectionPattern>
    <ServerType>Server Type</ServerType>
    <Model>Model Name</Model>
    <BootType>Boot Mode</BootType>
    <CPU>
      <CPUPerf>CPU Performance</CPUPerf>
      <NumOfCPU>Number of CPUs</NumOfCPU>
    </CPU>
    <Memory>
      <MemorySize>Memory Size</MemorySize>
    </Memory>
    <PXENetworkLink name="Network Name for PXE Boot"/>
    <Disks>
      <Disk name="Disk Name" type="Disk Connection Type">
        <DiskIndex>Disk Index</DiskIndex>
        <Exist>Existing LUN</Exist>
        <DiskLink name="Disk Name of Existing LUN"/>
      </Disk>
      <Disk>
        <DiskLink name="Disk Name of Existing LUN" />
        <DiskIndex>Disk Index</DiskIndex>
      </Disk>
      <Disk>
        <Exist>Existing LUN</Exist>
        <DiskLink name="Disk Name of Existing LUN" />
        <DiskIndex>Disk Index</DiskIndex>
      </Disk>
      <Disk name="Disk Name" type="Disk Connection Type">
        <DiskIndex>Disk Index</DiskIndex>
        <DiskSize>Disk Size</DiskSize>
        <From>
          <VirtualStorage name="Virtual Storage Resource Name"/>
          <Pool name="Storage Pool Name"/>
        </From>
      </Disk>
    </Disks>
    <NICGroups>
      <NICGroup>
        <NICGroupIndex>NIC Redundancy Group Index</NICGroupIndex> 
        <NetworkLinks>
           <NetworkLink name="Network_name" index="Network_index" vlan_mode="VLAN_mode">
            <IpAddress auto="Automatic IP Configuration" address="IP address"/>
          </NetworkLink>
        </NetworkLinks>
        <NICLinks>
          <NICLink>Numbers of NICs contained in NIC group</NICLink>
        </NICLinks>
      </NICGroup>
    </NICGroups>
    <NICs>
      <NIC>
        <NICIndex>NIC Index</NICIndex>
          <NetworkLinks>
            <NetworkLink name="Network_name" index="Network_index" vlan_mode="VLAN_mode">
              <IpAddress auto="Automatic IP Configuration" address="IP address"/>
            </NetworkLink>
          </NetworkLinks>
        <MacAddress auto="MAC Address Auto Select" Address Set Resource of MAC Address or Address Pool/>
      </NIC>
    </NICs>
    <HBAs>
      <HBA>
        <HBAIndex>HBA Index</HBAIndex>
        <WWN auto="WWNAutoSelect" WWN Address Set Resource or Address Pool/>
      </HBA>
    </HBAs>
    <IOVirtualOptionPool name="Address Pool Name"/>
    <Policy>
      <Redundancy>Redundancy</Redundancy>
      <Priority>Priority</Priority>
      <Repurpose>Server Automatic Release(true|false)</Repurpose>
      <SpareSelection method="Spare Server Selection Method" />
      <FCSinglePath>SAN Path Status</FCSinglePath>
      <AliveMonitoring>AliveMonitoring Setting(true|false)</AliveMonitoring>
      <SpareServerForceOFF>Use Active spare server with forced tuning OFF(true|false)</SpareServerForceOFF >
      <AllowForceOFF>Allow forced tuning OFF(true|false)</AllowForceOFF>
    </Policy>
    <Primary>Next Server to Start</Primary>
    <From>
      <PhysicalServer name="Physical Server Name"/>
    </From>
    <From>
      <Pool name="Server Pool Name"/> or
      <PhysicalServer name="Physical Server Name"/>
    </From>
    <Spare>
      <Pool name="Reserve Setting Server Pool Name"/>
    </Spare>
    <Allocation>Allocation of Resources</Allocation>
    <OSSetting>
      <ComputerName>Computer Name, Hostname</ComputerName>
    </OSSetting>
  </LServer>
</Resources>
Table 15.3 List of Items Specified in XML Definitions for Physical L-Servers

Element Name

Description

Remarks (Possible Values, Examples)

L-Server name (*1, *2, *3)

(LServer name)

Name of the L-Server

Specify a character string beginning with an alphanumeric character and containing up to 64 alphanumeric characters, underscores ("_"), and hyphens ("-").

Label (*1, *2)

(LServer label)

Label for the L-Server

(optional)

Specify a character string of up to 32 alphanumeric characters or symbols.

Comment (*1, *2)

(Comment)

Comment for the L-Server

(optional)

Specify a character string of up to 256 alphanumeric characters or symbols.

L-Server template name (*2)

(TemplateLink name)

Name of the L-Server template to use for the L-Server

(optional)

Specify the resource name of an existing L-Server template.

Image name (*2)

(ServerImageLink name)

Name of the cloning image to deploy to the L-Server's boot disk

(optional)

Specify the resource name of an existing cloning image.

Specify a name containing a resource folder.
For details, refer to "16.1 Creation Using an L-Server Template" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

Image version (*2)

(ServerImageLink version)

Version of the cloning image to deploy to the L-Server's boot disk

(optional)

Specify an integer.

If omitted, the latest version is used.

FC connection pattern

(FCConnectionPattern)

FC connection pattern file

Specify the file name of the FC connection pattern file that has been located in the following directory. (excluding those with the .rcxprop extension)

For details on the FC connection pattern file, refer to "B.1 Creating Definition Files" in the "Setup Guide CE"

[Windows Manager]

Installation_folder\SVROR\Manager\etc\customize_data\fc_connection_pattern

[Linux Manager]

/etc/opt/FJSVrcvmr/customize_data/fc_connection_pattern

For the FC connection pattern file name, enter a string that is no more than 64 characters long, where the first character is a number or letter and the remaining characters are alphanumeric characters, underscores ("_"), or hyphens ("-").

Server type (*4)

(ServerType)

Type of server to allocate as an L-Server

Specify "Physical".

Model name (*2, *4)

(Model)

Model name of the server to allocate to L-Server

Specify the model name of the server to allocate to the L-Server.

Specify the model name of the server after selecting the server resource on the server resource tree, and checking the model name on the [Resource Details] tab.

The model name cannot be specified when the following is specified.

  • CPU performance

  • Number of CPUs

  • Memory size

Boot mode (*1, *2, *3, *5)

(BootType)

L-Server boot method

Specify the L-Server boot method.

  • Disk

    Specify this mode when performing the boot from the disk connected to the L-Server.

  • PXE

    Specify this mode when performing the network boot using PXE (Preboot eXecution Environment).

This can also be specified using the rcxadm lserver set command.
For details, refer to "3.6 rcxadm lserver".

CPU performance (*1, *2, *3, *4)

(CPUPerf)

CPU performance to allocate to L-Server

Specify a number between 0.1 and 10.0 with up to one decimal place, in units of gigahertz.

For details on the scope which can be specified, refer to "16.2.2 [Server] Tab" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
CPU Performance cannot be specified when Model Name is specified.

Number of CPUs (*1, *2 , *3, *4)

(NumOfCPU)

Number of CPUs to allocate to L-Server

Specify an integer equal to or greater than "1".

For details on the scope which can be specified, refer to "16.2.2 [Server] Tab" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

There is no upper limit when performing creation or modification using the command.

Number of CPUs cannot be specified when Model Name is specified.

Memory size (*1, *2, *3, *4)

(MemorySize)

Size of memory to allocate to L-Server

Specify a number with up to one decimal place, in units of gigabytes.

For details on the scope which can be specified, refer to "16.2.2 [Server] Tab" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Memory Size cannot be specified when Model Name is specified.

Network name for PXE boot (*1, *2, *3, *5)

(PXENetworkLink name)

Name of network resource to perform PXE boot of the L-Server

(optional)

Specify the resource name of an existing network when performing a PXE boot.

This can also be specified using the rcxadm lserver set command.
For details, refer to "3.6 rcxadm lserver".

Disk name (*2)

(Disk name)

The disk name to allocate to L-Servers

(optional)

Specify a character string beginning with an alphanumeric character and containing up to 32 alphanumeric characters, underscores ("_"), and hyphens ("-").

If omitted, a name is automatically generated.

Disk connection type (*2, *4)

(Disk type)

The connection method of the disk to allocate to the L-Server

  • FC

    Specify the disk with a Fibre Channel connection to allocate.

  • iSCSI

    Specify the disk with an iSCSI connection to allocate.

Setting is possible only when disks have the number "0".
If omitted, "FC" is set.

Disk index (*2, *4)

(DiskIndex)

Number of the disk to allocate to the L-Server

Specify an integer starting from "0".

0: Boot disk
Other than 0: Data disk

Specify a number between 0 and 59.
Specify "0" if "iSCSI" was specified for Disk Connection Type.

Existing LUN (*2)

(Exist)

Specify that the LUN to allocate to the L-Server was created in advance by using storage management software, or was automatically created by Resource Orchestrator

(optional)

  • true

    Specify when the LUN was created in advance by using storage management software, or was automatically created by Resource Orchestrator.

  • false

    Specify when the LUN was created automatically by Resource Orchestrator.

When connecting a LUN that was created in advance by using storage management software, or was automatically created by Resource Orchestrator, this setting cannot be omitted.

Disk name of existing LUN (*2)

(DiskLink name)

Disk name of the LUN which was created in advance by using storage management software, or was automatically created by Resource Orchestrator to allocate to the L-Server

(optional)

Specify the disk name to allocate.

Disk size (*2, *4)

(DiskSize)

Size of disk to create

Specify a number with up to one decimal place, in units of gigabytes.

For details on the scope which can be specified, refer to "16.2.3 [Disk] Tab" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

Virtual storage resource name (*2)

(VirtualStorage name)

Virtual storage from which the disk to allocate to the L-Server is created
If specified at the same time as storage pool, priority is given to this attribute.

(optional)

Specify the resource name of an existing virtual storage.

Storage pool name (*2)

(Pool name)

Resource pool for extracting the virtual storage to create the disk to allocate to the L-Server

(optional)

Specify the resource name of an existing storage pool.

If there are storage pools with the same name on different levels, the level must also be specified.
Resource_folder/Resource_pool

NICGroups

(NICGroups)

A collection of NIC redundancy group definitions

(optional)

Specify when NIC redundancy is necessary.

Specify one or more NICGroup elements.

NIC redundancy group (*2, *4)

(NICGroup)

NIC redundancy group

Specify a NIC redundancy group.

NIC IP addresses with the index specified in NICLink, and the Network name, are ignored.

NIC redundancy group index (*2)

(NICGroupIndex)

NIC redundancy index

Specify a NIC redundancy index.

Specify for each NICGroup.
Specify sequential numbers starting from "0".

Network name (*2)

(NetworkLink name)

Name of the network that the L-Server connects to

Specify the name of an existing network resource.

When the network resource is an admin LAN resource or one for iSCSI, specify "untagged" for vlan_mode.

Network index (*2, *4)

(NetworkLink index)

Network index

Specify a network index.

The index starts from "0".

IP address (*2)

(IpAddress)

IP address to allocate to L-Servers

(optional)

The IP can be specified using the following methods:
<IpAddress auto="false" address="xxx.xxx.xxx.xxx"/>
Specify an IP address.

<IpAddress auto="true"/>
An IP address is automatically assigned from the address range set for the network resource.
Even if the IpAddress element is omitted, an IP address is automatically assigned from the address range set for the network resource.

Numbers of NICs contained in NIC group (*2, *4)

(NICLink)

NIC number contained in the NIC group

Specify NIC numbers contained in the NIC group.

If there are multiple NIC numbers, specify the NICLink for each NIC number.
Specify a set of redundancies.
The NIC number cannot be longer than the length of the NICGroup element.

For physical L-Servers, specify the value for the NIC number for a rack mount server or a tower server minus 1. The NIC number is defined in preparations explained in "9.3.5 Pre-configuring Managed Servers" in the "Design Guide CE".

Example

If "1" is defined for the NIC number placed on the upper left of the back face of a rack mount server, specify "0".

NIC

(NIC)

NIC definition

When not performing NIC redundancy, specify the NetworkLink element and the NetworkLinks element.

When not connecting a NIC to a network, the NetworkLink element and the NetworkLinks element are not necessary.
The child elements are as follows:

  • IpAddress element

  • NetworkLink element

  • NetworkLinks element

  • MacAddress element

  • NICIndex element

NIC index (*2, *4)

(NICIndex)

Number to identify the NIC definition to allocate to the L-Server

Specify an integer between 0 and 31 starting with "0".
Check that sequential numbers starting from "0" are used for each NIC element.
NIC number (NICIndex) + 1 corresponds to a network (NIC) number of the [General] tab in the [Create an L-Server] dialog.

For physical L-Servers, specify the value for the NIC number for a rack mount server or a tower server minus 1. The NIC number is defined in preparations explained in "9.3.5 Pre-configuring Managed Servers" in the "Design Guide CE".

Example

If "1" is defined for the NIC number placed on the upper left of the back face of a rack mount server, specify "0".

VLAN mode (*2)

(NetworkLink vlan_mode)

VLAN mode

(optional)

Specify a VLAN mode.

The VLAN mode can be specified using the following methods:

  • Untagged VLAN communication

    vlan_mode="untagged"

  • Tagged VLAN communication

    vlan_mode="tagged"

When vlan_mode is omitted, tagged VLAN communication is used.

MAC address (*2)

(MacAddress)

MAC address to allocate to the L-Server

(Optional, when specifying the address pool)

The MAC address can be specified using the following methods:

  • MAC address direct specification
    <MacAddress auto="false">MAC address format</MacAddress>
    For the MAC address format, specify the MAC address in either hyphen ("-") or colon (":") delimited form.
    ("xx-xx-xx-xx-xx-xx" or "xx:xx:xx:xx:xx:xx")

  • Auto allocation
    <MacAddress auto="true" from="MacAddressSetResource"/>
    or
    <MacAddress auto="true" pool="Address Pool Name"/>
    An address in the MAC address range set in the MACAddressSetResource or MAC address range registered in the specified address pool will automatically be allocated.

HBA Index (*2)

(HBAIndex)

Number to identify the HBA definition to allocate to the L-Server

Specify an integer starting from "0".

Specify a number between 0 and 1.

WWN (*2)

(WWN)

WWN to allocate to the L-Server

(Optional, when specifying the address pool)

The WWN can be specified using the following methods:

  • WWN direct specification
    <WWN auto="false">WWN format</WWN>
    For the WWN format, specify the WWN in colon (":") delimited form.
    ("xx:xx:xx:xx:xx:xx")

  • Auto allocation
    <WWN auto="true" from="WWNAddressSetResource"/>
    <WWN auto="true" pool="Address Pool Name"/>
    An address in the WWN scope set in the WWN address set resources or WWN scope registered in the specified address pool will automatically be assigned.

Address pool name (*2)

(IOVirtualOptionPool name)

Address pool to allocate to the L-Server
If specified at the same time as MAC Address and WWN, priority is given to this attribute.

(Optional, when specifying MAC Address and WWN)

Specify the resource name of the address pool to store address set resources (WWNs and MAC addresses) to allocate to L-Servers.

WWNs and MAC addresses of address set resources are the target of configuration.

The address pool can be specified using the following methods:
<IOVirtualOptionPool name="Address Pool Name"/>
If there are address pools with the same name on different levels, the level must also be specified.
Resource_folder_name/Resource_pool_name

Redundancy (*1, *2, *7)

(Redundancy)

Server redundancy to allocate to L-Servers

(optional)

  • None

    None

  • HA

    Specify when performing redundancy.

If omitted, "None" is set.
For details on the redundancy, refer to "16.2.2 [Server] Tab" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

Priority (*1, *2)

(Priority)

Priority when allocating resources or creating an L-Server

(optional)

When the L-Server is the target of batch power operations, or when performing batch creation of multiple L-Servers using XMLs of resource folders, specify the priority in the range of 1 to 256.

Smaller values indicate higher priority.
If omitted, "128" is set.
When "0" is specified, the server is excluded from batch power operations.

Automatic server release (*1, *2, *4, *5)

(Repurpose)

Automatic release of servers during power off

(optional)

Specify whether to automatically release the servers allocated to the L-Server, when they are powered off.

  • When using automatic release

    Specify "true".

  • When not using automatic release

    Specify "false".

If the values of this attribute and "Server Automatic Release" of the L-Server template are omitted, the value that is set in the definition file is used.
For details on the definition file, refer to "17.8.1 Installation" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Ensure that "true" is specified for L-Servers to change the usage of.

Spare server selection method (*1, *2, *4)

(SpareSelection method)

Selection method for spare servers

(optional)

  • name_order

    Spare servers are selected from among servers that match the model name of the operating server, in order of physical server names.

  • keep_spec

    A server that provides the same or higher performance figures as the operating server, and the least difference in performance is selected.

If omitted, "keep_spec" is set.

SAN path status (*1, *2, *3, *4, *5)

(FCSinglePath)

San path status after physical L-Server creation

Configure the SAN path status after physical L-Server creation.

  • true

    Specify when setting single-path.

  • false

    Specify when setting multi-path.

If left blank, "false" is set.

This can also be specified using the rcxadm lserver set command.
For details, refer to "3.6 rcxadm lserver".

Alive monitoring settings (*1, *2, *4, *7)

(AliveMonitoring)

Alive Monitoring Settings

(optional)

  • When enabling alive monitoring

    Specify "true"

  • When disabling alive monitoring

    Specify "false"

If omitted and not specified when creating the L-Server, "false" is set.

Use Active spare server with forced tuning OFF
(*1, *2, *4, *5, *7)

(SpareServerForceOFF)

Set to use Physical Server with forced OFF

(optional)

Server|When Physical servers in Spare server pool are running out; use the Physical server that is set "Allow forced turning off" after perform force OFF the target Physical server.

  • When setting this parameter,

    Specify "true"

  • When not setting this parameter

    Specify "false"

If omitted or not specified at L-Server creation, "false" is set.

Allow forced tuning OFF
(*1, *2, *4, *5, *7)

(AllowForceOFF)

Allow forced tuning OFF

(optional)

When Physical servers in Spare server pool are running out allow to perform force OFF the target Physical server even if that server is Power on

  • When setting this parameter

    Specify "true"

  • When not setting this parameter

    Specify "false"

If omitted or not specified at L-Server creation, "false" is set.

Physical server name (*1, *2, *5)

(PhysicalServer name)

Physical server to allocate to the L-Server

If specified at the same time as server pool, priority is given to the specifications of the physical server.

Specify the physical server to allocate to the L-Server.

Server pool name (*1, *2, *5)

(Pool name)

Resource pool that comprises the physical servers allocated to L-Servers

Specify the resource names of existing server pools.
If there are server pools with the same name on different levels, the level must also be specified.
Resource_folder/Resource_pool

Reserve setting server pool name (*1, *2)

(Pool name)

Server pool for reserve settings

(optional)

Valid when redundancy has been configured.
If there are server pools with the same name on different levels, the level must also be specified.
Resource_folder/Resource_pool

Allocation of resources

(Allocation)

Status of resources allocated to the L-Server

(optional)

  • true

    Specify to allocate resources.

  • false

    Only specify when creating a configuration definition.

If this attribute is omitted, the value set in the definition file is used.
For details on the definition file, refer to "17.8.1 Installation" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

Computer name, hostname (*2, *6)

(ComputerName)

Computer name and hostname

[Physical Servers]
For specifiable values, refer to "B.7 [OS] Tab Configuration" in the "Setup Guide CE".

*1: Values can be changed by modifying an L-Server, only when its status is "allocated" (resources have been allocated) or "preserved" (servers have been released). Even if an L-Server template name or the content of an L-Server template specified for the L-Server template name is modified, the configuration of L-Servers already created using the template will not be modified.
*2: Values can be changed by modifying an L-Server, only when its status is "defined" (only the configuration definition has been created). When modifying an L-Server for which only the configuration definition has been created, unmodified information must be described also.
*3: In addition to *1, the value can be changed during power off.
*4: Specify if no L-Server template is used or if the values specified in the L-Server template will not be used.
*5: This cannot be changed when the L-Server is being linked to a configured physical server.
*6: Personalizing information to be specified after the image is deployed.
*7: The values for an L-Server deployed from an L-Platform can be changed by changing the configuration. In this case, use an XML file which only contains the elements for alive monitoring settings and redundancy.

Example

  • Creating an L-Server that does not deploy a cloning image using an L-Server template

    <?xml version="1.0" encoding="utf-8"?>
<Resources>
  <LServer name="first_server">
    <TemplateLink name="small"/>
    <ServerType>Physical</ServerType>
    <Model>PRIMERGY BX920 S2</Model>
    <NICs>
      <NIC>
        <NICIndex>0</NICIndex>
          <NetworkLinks>
            <NetworkLink name="AdminLan" vlan_mode="untagged" index="0"/>
          </NetworkLinks>
      </NIC>
    </NICs>
    <IOVirtualOptionPool auto="true" name="AddressPool"/>
  </LServer>
</Resources>

  • Creating an L-Server that deploys a cloning image using an L-Server template

    <?xml version="1.0" encoding="utf-8"?>
<Resources>
  <LServer name="second_server">
    <TemplateLink name="small"/>
    <ServerType>Physical</ServerType>
    <Model>PRIMERGY BX920 S2</Model>
    <ServerImageLink name="/ImagePool/master_image"/>
    <NICs>
      <NIC>
        <NICIndex>0</NICIndex>
          <NetworkLinks>
            <NetworkLink name="AdminLan" vlan_mode="untagged" index="0"/>
          </NetworkLinks>
      </NIC>
    </NICs>
    <IOVirtualOptionPool auto="true" name="AddressPool"/>
    <OSSetting>
      <ComputerName>host1</ComputerName>
    </OSSetting>
  </LServer>
</Resources>

  • Creating an L-Server that deploys a Linux cloning image without using an L-Server template

    <?xml version="1.0" encoding="utf-8"?>
<Resources>
  <LServer name="L-Server">
    <ServerImageLink name="/ImagePool/RHEL5"/>
    <ServerType>Physical</ServerType>
    <Model>PRIMERGY BX920 S2</Model>
    <BootType>Disk</BootType>
    <Disks>
      <Disk>
        <DiskIndex>0</DiskIndex>
        <DiskSize>40.0</DiskSize>
      </Disk>
      <Disk>
        <DiskIndex>1</DiskIndex>
        <DiskSize>30.0</DiskSize>
      </Disk>
    </Disks>
    <NICs>
      <NIC>
        <NICIndex>0</NICIndex>
          <NetworkLinks>
            <NetworkLink name="AdminLan" vlan_mode="untagged" index="0"/>
          </NetworkLinks>
      </NIC>
    </NICs>
    <IOVirtualOptionPool auto="true" name="AddressPool"/>
    <HBAs>
      <HBA>
        <HBAIndex>0</HBAIndex>
      </HBA>
    </HBAs>
    <IOVirtualOptionPool auto="true" />
    <Policy>
      <Redundancy>None</Redundancy>
      <Priority>128</Priority>
    </Policy>
    <Repurpose>true</Repurpose>
    <Allocation>true</Allocation>
    <OSSetting>
      <ComputerName>host1</ComputerName>
    </OSSetting>
  </LServer>
</Resources>

  • Creating an L-Server in a resource folder or a tenant

    <?xml version="1.0" encoding="utf-8"?>
<Folder name="Resource Folder Name or Tenant Name">
  <LServer name="L-Server Name" label="Label">
    ...
  </LServer>
</Folder>
    Table 15.4 List of Items Specified in XML Definitions when Creating an L-Server in a Resource Folder or a Tenant

    Element Name

    Description

    Remarks (Possible Values, Examples)

    Resource folder name or Tenant name (*1)

    (Folder name)

    Name of the resource folder or the tenant to place the L-Server in

    (optional)

    To specify the level, use the following format:

    Resource_folder_name/Resource_folder_name
    Tenant_name/Resource_folder_name
    Resource_folder_name/Tenant_name

    *1: Specify if creating an L-Server in a resource folder.

  • Creating another L-Server using detailed L-Server information

    Modify the following information.

    • Modify the name attribute of the LServer element

    • Delete the name attribute of the DiskLink and Disk elements (If an existing LUN is allocated, modify the name attribute)

      If none of these elements exist, add them.

    • Modify the MacAddress, IpAddress, and WWN elements (If specifying an address pool for address assignment, or resources)

      If none of these elements exist, add them as necessary.

    • Modify the PhysicalServer element in the From or Spare element (If the elements are specified)

    <?xml version="1.0" encoding="utf-8"?>
<Resources>
<LServer name="P-Server2" id="WIN-66N8JTJM2BD_2853" label="">
  <Comment></Comment>
  <ServerType>Physical</ServerType>
  <Model>PRIMERGY BX920 S1</Model>
  <CPU>
    <CPUArch>ia32</CPUArch>
    <CPUPerf>2.0</CPUPerf>
    <NumOfCPU>0</NumOfCPU>
  </CPU>
  <Memory>
    <MemorySize>0.0</MemorySize>
  </Memory>
  <BootType>Disk</BootType>
  <Disks>
      <Disk name="P-Server2-0-disk0">
        <DiskIndex>0</DiskIndex>
        <DiskSize>20.0</DiskSize>
      </Disk>
  </Disks>
  <NICGroups>
  </NICGroups>
  <NICs>
    <NIC>
      <NICIndex>0</NICIndex>
      <MacAddress auto="true" from="mac_address_set"/>
      <NetworkLinks>
          <NetworkLink name="admin_lan" index="0" vlan_mode="untagged">
            <IpAddress auto="true"/>
          </NetworkLink>
      </NetworkLinks>
    </NIC>
  </NICs>
  <HBAs>
    <HBA>
      <HBAIndex>0</HBAIndex>
      <WWN auto="true" pool="/AddressPool" />
    </HBA>
  </HBAs>
  <ExternalIdentifier></ExternalIdentifier>
  <Current>
    <PhysicalServer name="chassis4-2" id="WIN-66N8JTJM2BD_83" />
  </Current>
  <ExternalProfile/>
  <Policy>
    <Redundancy>None</Redundancy>
    <Positioning>Fixed</Positioning>
    <Exclusion></Exclusion>
    <Priority>128</Priority>
    <Repurpose>false</Repurpose>
  </Policy>
  <Status>
    <ResourceStatus>stop</ResourceStatus>
    <PowerStatus>off</PowerStatus>
    <AllocationStatus>attached</AllocationStatus>
    <MaintenanceMode>active</MaintenanceMode>
    <Resources>allocated</Resources>
    <ServerAllocationStatus>true</ServerAllocationStatus>
    <DiskAllocationStatus>false</DiskAllocationStatus>
    <AddressAllocationStatus>true</AddressAllocationStatus>
  </Status>
  <From>
    <PhysicalServer name="chassis4-2" id="WIN-66N8JTJM2BD_83" />
  </From>
  <Spare>
  </Spare>
</LServer>
</Resources>

PreviousNext
Copyright 2010-2013 FUJITSU LIMITED