15.11 Server NIC Definition

To register the server NIC definition, create the following files:

[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data\nicdefctl\model\Chassis_model_name_product_name.xml (*1)
Installation_folder\SVROR\Manager\etc\customize_data\nicdefctl\host\VM_host_name.xml (*2)

[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data/nicdefctl/model/Chassis_model_name_product_name.xml (*1)
/etc/opt/FJSVrcvmr/customize_data/nicdefctl/host/VM_host_name.xml (*2)

*1: For the chassis name and product name used as file name, set the specified value of element name for server NIC definition using lower case. When using a rack mount server or a tower server, set the file name to create to "Product name.xml". For the product name, specify the value of the model attribute of the Server element using lower case letters, removing blank spaces.

Example

When "PRIMERGY RX300 S6" is displayed on the GUI, specify "primergyrx300s6" for the file name.

*2: For a VM host name used as a file name, set the same format as the element name for server NIC definition.

The XML definition for server NIC definition is shown below.

<Server chassis_model="Chassis Model Name" model="Product Name" name = "VM Host Name">
  <NICGroups>
    <NICGroup>
      <NICs>
        <NIC index="Index Number" redundant="Active/Standby Type"/>
      </NICs>
      <PhysicalLANSegments>
        <PhysicalLANSegment name="Physical LAN Segment Name"/>
      </PhysicalLANSegments>
    </NICGroup>
  </NICGroups>
</Server>

Table 15.21 List of Items Specified in XML for Server NIC Definition
Element Name	Description	Remarks (Possible Values, Examples)
Chassis Model Name (Server chassis_model)	Chassis model name When using a blade server, specify the chassis model name. This cannot be specified when a rack mount server, a tower server, or a VM host name is specified.	Specify the following values for the chassis model name. When the chassis is a BX900 series "BX900" When the chassis is a BX600 series "BX600" When the chassis is a BX400 series "BX400"
Product Name (Server model)	Server product name Specify the name when using a blade server, rack mount server, or tower server. When specifying the VM host name, the name cannot be specified.	Specify the product name that is displayed by selecting the [Resource Details] tab which is the server attribute of the server tree.
VM Host Name (Server name)	VM host name Specify when using a VM host name. When specifying the chassis model name or the product name, the name cannot be specified.	Specify the server name that is displayed by selecting the [Resource Details] tab which is the VM host attribute of the server tree.
NIC Definition Group Information (NICGroups)	Collection of NIC definition group	Specify one or more NICGroup elements.
NIC Definition Group (NICGroup)	NIC definition and physical LAN segment group	Specify one NICs element and one PhysicalLANSegments element.
NIC Definition Information (NICs)	A collection of NIC definitions	Specify one or two NIC elements.
Index Number (NIC index)	NIC index number	Specify an integer starting from "1". For blade servers The index number of physical network information displayed by selecting the [Resource Details] tab which is the server attribute of the server tree. For rack mount servers or tower servers The number corresponding to the name of a NIC recognized by server virtualization software. (*)
Active/Standby Type (NIC redundant)	Type of active or standby, when using NICs in teaming configurations When only specifying one NIC for the NIC definition information, this specification is invalid. When specifying two NICs for the NIC definition information, this specification cannot be omitted. When "Active" is specified for two NICs, load balancing is performed based on virtual port IDs. For details on load balancing based on virtual port IDs, refer to the VMware manual. The values specified for this element are only valid when the virtual L-Server destination of server virtualization software is VMware. When the server virtualization software is not VMware, this specification is disabled.	When using the element with teaming configurations, specify active or standby. Active Indicates active. Standby Indicates standby.
Physical LAN Segment Information (PhysicalLANSegments)	Collection of physical LAN segments	Specify one or more PhysicalLANSegment elements. When sharing server NIC configurations, multiple PhysicalLANSegment elements are necessary.
Physical LAN Segment Name (PhysicalLANSegment name)	Physical LAN segment identifier name	Specify character string beginning with an alphanumeric character and containing up to 32 alphanumeric characters, underscores ("_"), and hyphens ("-"). Specify the identifier name of physical LAN segment that will use the NIC definition information within the NIC definition group.

* Note: For VMware, index numbers are integers starting from 1 (1, 2, 3 ...). The numbers correspond to the names of NICs (vmnic0, vmnic1, vmnic2 ...) of the managed servers recognized by VMware.

Example

The sample XML files for server NIC definitions are stored in the following folders:

The configuration used by default is described in the sample file.

[Windows Manager]

Installation_folder\Manager\etc\customize_data\nicdefctl\sample\model

[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data/nicdefctl/sample/model

For bx900_d2952.xml

<?xml version="1.0" encoding="utf-8"?>
<Server chassis_model="BX900" model="D2952">
  <NICGroups>
    <NICGroup>
      <NICs>
        <NIC index="1" redundant="Active" />
        <NIC index="2" redundant="Standby" />
      </NICs>
      <PhysicalLANSegments>
        <PhysicalLANSegment name="BX900_BX924S2_PGSW111_CB1CB2" />
        <PhysicalLANSegment name="BX900_BX924S2_PGSW112_CB1CB2" />
        <PhysicalLANSegment name="BX900_BX924S2_PGSW109_CB1CB2" />
        <PhysicalLANSegment name="BX900_BX924S2_PGSW201_CB1CB2" />
      </PhysicalLANSegments>
    </NICGroup>
    <NICGroup>
      <NICs>
        <NIC index="3" redundant="Active" />
        <NIC index="4" redundant="Standby" />
      </NICs>
      <PhysicalLANSegments>
        <PhysicalLANSegment name="BX900_BX924S2_PGSW111_CB3CB4" />
        <PhysicalLANSegment name="BX900_BX924S2_PGSW112_CB3CB4" />
        <PhysicalLANSegment name="BX900_BX924S2_PGSW109_CB3CB4" />
        <PhysicalLANSegment name="BX900_BX924S2_PGSW201_CB3CB4" />
      </PhysicalLANSegments>
    </NICGroup>
    <NICGroup>
      <NICs>
        <NIC index="7" redundant="Active" />
        <NIC index="8" redundant="Standby" />
      </NICs>
      <PhysicalLANSegments>
        <PhysicalLANSegment name="BX900_BX924S2_PGSW109_CB5CB6" />
        <PhysicalLANSegment name="BX900_BX924S2_PGSW201_CB7CB8" />
      </PhysicalLANSegments>
    </NICGroup>
    <NICGroup>
      <NICs>
        <NIC index="9" redundant="Active" />
        <NIC index="10" redundant="Standby" />
      </NICs>
      <PhysicalLANSegments>
        <PhysicalLANSegment name="BX900_BX924S2_PGSW111_CB7CB8" />
        <PhysicalLANSegment name="BX900_BX924S2_PGSW112_CB7CB8" />
      </PhysicalLANSegments>
    </NICGroup>
  </NICGroups>
</Server>

After Modifying the Server NIC Definition

Virtual switches, port groups, and virtual bridges already deployed can continue to be operated without any modifications, even if the server NIC definition is modified.
Newly deployed virtual switches, port groups, and virtual bridges should be configured according to the server NIC definition that has been modified.
This also applies when physical LAN segments referred to from network resources are modified.
When modifying already deployed networks, directly operate server virtualization software to modify them.