Top
ServerView Resource Orchestrator Cloud Edition V3.1.1 Setup Guide
ServerView
Appendix C Configuration when Creating Virtual L-Servers > C.3 Hyper-V > C.3.4 Automatic Network Configuration
PreviousNext

C.3.4 Automatic Network Configuration

Network settings on Hyper-V differ depending on hardware (such as blade servers and rack mount servers), and whether network redundancy will be performed for L-Servers.

Automatic Network Configuration for Blade Servers

If the NIC and network resources are connected when an L-Server is created, the following settings will be registered automatically for the VM host that the L-Server will operate on.

In environments using the clustering function of VM management software, in order to enable the migration of VM guests and operation using the HA function, settings for LAN switch blades and virtual switches are performed automatically for all VM hosts comprising the cluster.

When not configuring the tagged VLAN automatically for the uplink port of network resources, use the ROR console to configure the VLAN settings of uplink ports. Right-click the LAN switch in the server resource tree, and select [Modify]-[Network Settings] from the popup menu.

For details, refer to "5.4.4 Configuring VLANs on LAN Switch Blades" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

Note

After creating an L-Server, if VM hosts are added to the cluster afterwards, Resource Orchestrator network settings are not performed automatically.

Perform the same settings as the existing VM hosts in the cluster configuration for the LAN switch blades and virtual networks of the additional VM hosts.

Virtual network definition files for blade servers

  • When configuring the network for blade servers automatically

    It is not necessary to create a virtual network definition file.

  • When a virtual network definition file exists and no virtual network with a VLAN ID is defined

    The virtual network is automatically configured.

  • When a virtual network with a VLAN ID is defined, using a virtual network definition file

    It is necessary that a virtual network with the VLAN ID be manually configured beforehand.

    For details, refer to "C.3.5 Manual Network Configuration".


Default Blade Server Configuration to Support Automation of Network Configuration in Resource Orchestrator

The default blade server configuration to support automation of network configuration in Resource Orchestrator (server blades, specification of uplink ports for network resource, correspondence relation of numbers of LAN switch blades and physical network adapters, etc.) is shown in the following list. When there are no server NIC definitions, for network auto-configuration, a virtual network is created using the physical network adapter selected according to this list.

Table C.12 Default Blade Server Configuration for Network Auto-Configuration (for PRIMERGY BX900 S1/S2 Chassis)

Server Blade

Specification of Uplink Port
(Location of LAN Switch Blade)

LAN Switch Blade to Use

Physical Network Adapter Number (*6)

BX920 S1
BX920 S2
BX920 S3
BX922 S2
BX924 S3

CB1 and CB2, or no specification for uplink port

PY-SWB102(PG-SW111)
PY-SWB103(PG-SW112)

3,4

PY-SWB101(PG-SW201)
PY-SWB104(PG-SW109) (*1)
PY-CNB101 (*2)
PY-FEB101 (*3)

1,2

CB3 and CB4

PY-SWB101(PG-SW201)
PY-SWB102(PG-SW111)
PY-SWB103(PG-SW112)
PY-SWB104(PG-SW109)
PY-CNB101
PY-FEB101 (*3)

5,6

CB5 and CB6

PY-SWB104(PG-SW109)
PY-CNB101
PY-FEB101 (*3)

9,10

CB7 and CB8

PY-SWB102(PG-SW111)
PY-SWB103(PG-SW112)

11,12

PY-SWB101(PG-SW201)

9,10

BX924 S2

CB1 and CB2, or no specification for uplink port

PY-SWB101(PG-SW201)
PY-SWB102(PG-SW111)
PY-SWB103(PG-SW112)
PY-SWB104(PG-SW109)

1,2

CB3 and CB4

PY-SWB101(PG-SW201)
PY-SWB102(PG-SW111)
PY-SWB103(PG-SW112)
PY-SWB104(PG-SW109)
PY-CNB101
PY-FEB101 (*3)

3,4

CB5 and CB6

PY-SWB104(PG-SW109)
PY-CNB101
PY-FEB101 (*3)

7,8

CB7 and CB8

PY-SWB102(PG-SW111)
PY-SWB103(PG-SW112)

9,10

PY-SWB101(PG-SW201)

7,8

BX960 S1

CB1 and CB2, or no specification for uplink port

PY-SWB101(PG-SW201)
PY-SWB102(PG-SW111)
PY-SWB103(PG-SW112)
PY-SWB104(PG-SW109)

11,12

CB3 and CB4 (*4)

PY-SWB101(PG-SW201)
PY-SWB102(PG-SW111)
PY-SWB103(PG-SW112)
PY-SWB104(PG-SW109)
PY-CNB101
PY-FEB101 (*3)

3,4

CB5 and CB6 (*5)

PY-SWB104(PG-SW109)
PY-CNB101
PY-FEB101 (*3)

7,8

CB7 and CB8 (*5)

PY-SWB102(PG-SW111)
PY-SWB103(PG-SW112)

9,10

PY-SWB101(PG-SW201)

7,8

*1: When installing a PY-SWB104 (PG-SW109) on CB1 or CB2, set the transmission speed at the down link port of PY-SWB104 (PG-SW109) to 1 Gbps. For details on how to configure the settings, refer to the corresponding hardware manual.
*2: Only BX920 S3 and BX924 S3 are supported as server blades, when mounting PY-CNB101 on CB1 and CB2.
*3: Only BX920 S3 and BX924 S3 are supported as server blades, when using PY-FEB101.
*4: A LAN expansion card is mounted in expansion slot 1.
*5: A LAN expansion card is mounted in expansion slot 2.
*6: Configure a virtual network automatically on a virtual interface configured beforehand in a redundant configuration using individual physical network adapters. Configure the virtual interface on the managed server using one of following products beforehand.

Table C.13 Default Blade Server Configuration for Network Auto-Configuration (for PRIMERGY BX400 S1 Chassis)

Server Blade

Specification of Uplink Port
(Location of LAN Switch Blade)

LAN Switch Blade to Use

Physical Network Adapter Number (*5)

BX920 S2
BX920 S3
BX922 S2
BX924 S3

CB1 and CB2 (*1), or no specification for uplink port

PY-SWB102(PG-SW111)
PY-SWB103(PG-SW112)

3,7

PY-SWB101(PG-SW201)
PY-SWB104(PG-SW109) (*2)
PY-CNB101 (*3)
PY-FEB101 (*4)

2,6

CB3 and CB4

PY-SWB101(PG-SW201)
PY-SWB102(PG-SW111)
PY-SWB103(PG-SW112)
PY-SWB104(PG-SW109)
PY-CNB101
PY-FEB101 (*4)

9,10

BX924 S2

CB1 and CB2 (*1), or no specification for uplink port

PY-SWB101(PG-SW201)
PY-SWB102(PG-SW111)
PY-SWB103(PG-SW112)
PY-SWB104(PG-SW109)

2,4

CB3 and CB4

PY-SWB101(PG-SW201)
PY-SWB102(PG-SW111)
PY-SWB103(PG-SW112)
PY-SWB104(PG-SW109)
PY-CNB101
PY-FEB101 (*4)

7,8

*1: The same LAN switch blade model should be mounted in CB1 and CB2.
*2: When installing a PY-SWB104 (PG-SW109) on CB1 or CB2, set the transmission speed at the down link port of PY-SWB104 (PG-SW109) to 1 Gbps. For details on how to configure the settings, refer to the corresponding hardware manual.
*3: Only BX920 S3 and BX924 S3 are supported as server blades, when mounting PY-CNB101 on CB1 and CB2.
*4: Only BX920 S3 and BX924 S3 are supported as server blades, when using PY-FEB101.
*5: Configure a virtual network automatically on a virtual interface configured beforehand in a redundant configuration using individual physical network adapters. Configure the virtual interface on the managed server using one of following products beforehand.

Table C.14 Default Blade Server Configuration for Network Auto-Configuration (for PRIMERGY BX600 S3 Chassis)

Server Blade

Specification of Uplink Port
(Location of LAN Switch Blade)

LAN Switch Blade to Use

Physical Network Adapter Number (*)

BX600 series servers

NET1 and NET2, or no specification for uplink port

PG-SW107

3,4

NET3 and NET4

PG-SW104

7,8

* Note: Configure a virtual network automatically on a virtual interface configured beforehand in a redundant configuration using individual physical network adapters. Configure the virtual interface on the managed server using one of following products beforehand.

The numbers of physical network adapters given above can be checked on the details window of the LAN switch blade.

The MAC address (IP address) information of managed servers can be confirmed in [Hardware Maintenance] on the [Resource Details] tab.

Configure the Intel PROSet or PRIMECLUSTER GLS settings on the managed server in advance, using this MAC address information.

When the LAN switch blade is in IBP mode, create a virtual network on the virtual interface configured beforehand in the redundant configuration using the same physical network adapter as in the case of "no specification for uplink port" in the list above.

Performing the following procedure enables automatic network configuration using an arbitrary physical NIC.

  1. Create a server NIC definition and reflect it on Resource Orchestrator.

    1. Create a server NIC definition

      Edit the template file and create a server NIC definition.

    2. Reflect the server NIC definition

      Execute the rcxadm nicdefctl commit command to reflect the physical NIC configuration specified in the server NIC definition file on Resource Orchestrator.

    3. Confirm the reflected server NIC definition

      Execute the rcxadm nicdefctl show command and confirm the server NIC definition has been reflected on Resource Orchestrator.

  2. Create a network resource.

    • From the GUI:

      1. In the ROR console orchestration tree, right-click the network pool to create a network resource in, and select [Create Network Resource].
        When creating a new network resource, select [New].
        When creating a resource using an already registered admin LAN subnet, select [Using existing admin subnet].

      2. In the [Create a network resource] dialog, clear the [Use configured virtual switches.] checkbox.

      3. In the [Create a Network Resource] dialog, select "Settings" in "Physical LAN Segment".

      4. In the [Physical LAN segment settings] dialog, select the physical LAN segment specified in PhysicalLANSegment name of the server NIC definition.

    • From the Command-line:

      1. Create the XML file that defines network resources.
        Specify the physical LAN segment name that was specified for "PhysicalLANSegment name" in the server NIC definition file for "PhysicalLANSegment" in the XML file that defines network resources.
        In this case, specify auto="true" in the Network element.

      2. Create a network resource.
        Execute the rcxadm network create command specifying the XML file created in step a.

See

  • For details on the server NIC definitions, refer to "15.11 Server NIC Definition" in the "Reference Guide (Command/XML) CE".

  • For details on the nicdefctl command, refer to "5.15 rcxadm nicdefctl" in the "Reference Guide (Command/XML) CE".

  • For details on how to define network resources, refer to "15.5 Network Resources" in the "Reference Guide (Command/XML) CE".

  • For details on the rcxadm network command, refer to "3.9 rcxadm network" in the "Reference Guide (Command/XML) CE".

Note

  • If there are VM hosts that meet the following conditions, automation of network configuration is not supported in the chassis.

    • Network resources with uplink ports specified are used

    • There is a virtual network that uses a NIC in a VM host configuration pattern that differs from the ones supporting automation of network configuration

  • If there are VM hosts that meet the following conditions, automation of network configuration is not supported.

    • Network resources with no uplink port specified are used

    • There is a virtual network that uses a NIC in a VM host configuration pattern that differs from the ones supporting automation of network configuration

In the diagram, the default blade server configurations as described in the following configuration example when using a PRIMERGY BX900 S1 chassis are shown.

Table C.15 Configuration Example 1

Server blades

BX920 S2

Specification of uplink port

CB1 and CB2

LAN switch blade to use

PY-SWB103(PG-SW112)

Virtual interface

PRIMECLUSTER GLS

Table C.16 Configuration Example 2

Server blades

BX920 S2

Specification of uplink port

Both "no specification for uplink port" and "CB3 and CB4" are specified

LAN switch blade to use

PY-SWB104(PG-SW109)

Virtual interface

PRIMECLUSTER GLS

Figure C.4 Blade Server Diagram of Configuration Example 1

Figure C.5 Blade Server Diagram of Configuration Example 2


PreviousNext
Copyright 2010-2013 FUJITSU LIMITED