Top
ServerView Resource Orchestrator Cloud Edition V3.0.0 Setup Guide
Chapter 4 Pre-setup Preparations > 4.2 Defining and Configuring the Network Environment > 4.2.4 Preparations for Resource Orchestrator Network Environments
PreviousNext

4.2.4 Preparations for Resource Orchestrator Network Environments

This section explains the preparations for setting up the network environment.

Conditions

Necessary Preparations

When automatically configuring the network

Create network resources

When using IBP

Create an IBP uplink set

When using an iSCSI LAN for iSCSI boot

Create a network definition file for iSCSI boot

When using Link Aggregation

Pre-configure link aggregation for LAN switch blades and L2 switches

When using NICs other than those in the default configuration of the automatic network configuration used when using blade servers

Create a server NIC definition

When using VMware on rack mount or tower servers to use automatic virtual switch configuration

Create a server NIC definition

When deploying L-Servers even if the service console and port group is the same, when VMware is being used for server virtualization software

Create the VMware excluded port group definition file

When registering network devices as resources

Create network resources

When using the automatic configuration function for network devices registered as network device resources

Create model definitions for the network devices

Create a folder for registering rulesets

Register sample scripts


4.2.4.1 When Automatically Configuring the Network

By connecting the NIC for an L-Server to a network resource, the following settings are automatically configured.

Automatic VLAN Configuration for LAN Switch Blades (Physical/Virtual L-Servers)

VLANs are automatically configured on LAN switch blades.

There are the following three types of firmware for LAN switch blades:

In Resource Orchestrator, operation of a LAN switch blade using Switch firmware is called Switch mode, operation using end-host firmware is called end-host mode, and operation using IBP firmware is called IBP mode.

For details, refer to the manual of the LAN switch blade.

Network Configuration for Blade Servers (Physical/Virtual L-Servers)

Network Configuration for Rack Mount or Tower Servers (Physical/Virtual L-Servers)

For rack mount or tower servers, make connections between L-Server virtual NICs and virtual switches.

Figure 4.18 Network Configuration for Rack Mount or Tower Servers

Table 4.4 Network Configurations for Rack Mount or Tower Servers

Physical L-Server

Virtual L-Server

VMware

Hyper-V

RHEL5-Xen

RHEL-KVM

Oracle VM

Redundancy (*1)

Redundancy (*1)

Redundancy (*1)

Redundancy (*1)

Redundancy (*1)

Redundancy (*1)

Without

With

Without

With

Without

With

Without

With

Without

With

Without

With

A

Creating virtual switches and connecting to NICs (*2)

-

-

Yes

Yes

No

No

No

No

No

No

No

No

B

Connection between L-Server virtual NICs and virtual switches (*3)

-

-

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

C

Configuration of VLAN IDs used by L-Server virtual NICs

-

-

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

D

Configuration of LAN switch ports for external L2 switches (*4)

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes: Configured in Resource Orchestrator
No: Not configured in Resource Orchestrator
*1: LAN redundancy.
For physical L-Servers, the NIC of the physical L-Server is the target of LAN redundancy.

For virtual L-Servers, the NIC connected to the virtual switch is the target of LAN redundancy.

*2: In order to configure the network automatically, it is necessary to create a server NIC definition suitable for the server to be configured, and then reflect the definition on the manager using the rcxadm nicdefctl commit command in advance.
For details on the server NIC definitions, refer to "2.11 Server NIC Definition" of the "Reference Guide (Resource Management) CE".
For details on the rcxadm nicdefctl command, refer to "1.7.16 rcxadm nicdefctl" of the "Reference Guide (Resource Management) CE".

Replace as follows for each server virtualization software.

Table 4.5 Correspondence Table for Server Virtualization Software

VMware

Creating virtual switches and port groups

Hyper-V

Creating a virtual network

RHEL5-Xen
RHEL-KVM
Oracle VM

Creating a virtual bridge

Information

When using VMware as server virtualization software, the following configurations are automatically performed:

  • Virtual switch creation

  • VLAN configuration for virtual switches

  • Teaming connection of virtual switches and NICs

The model names of rack mount or tower servers that can perform virtual switch creation, VLAN configuration, and teaming connection are as follows:

  • RX100 S5/S6

  • RX200 S4/S5/S6

  • RX300 S4/S5/S6

  • RX600 S4/S5

  • RX900 S1

  • TX150 S6/S7

  • TX200 S5/S6

  • TX300 S4/S5/S6

*3: Replace as follows for each server virtualization software.

Table 4.6 Correspondence Table for Server Virtualization Software

VMware

Connections Virtual NICs of L-Servers and Port Groups of Virtual Switches

Hyper-V

Connections Virtual NICs of L-Servers and Virtual Networks

RHEL5-Xen
RHEL-KVM
Oracle VM

VLAN ID configuration for the L-Server virtual network interface and connection with virtual bridges which have been created manually in advance

Information

If VMware is used as the server virtualization software and the same VLAN ID is used for the service console and port group, the port group and L-Server can be connected by creating a VMware excluded port group definition file.

See

For details on VMware excluded port group definition files, refer to "2.12 VMware Excluded Port Group Definition File" in the "Reference Guide (Resource Management) CE".

*4: Configured by network device automatic configuration.


IP Address Auto-Configuration (Virtual L-Servers)

[Windows/Linux] [VMware] [Hyper-V] [KVM]
If a subnet address has been set for the network resource, the IP address can be automatically set when deploying an image to an L-Server.
The settings for the IP address, subnet mask and default gateway are configured according to DHCP settings.

[Hyper-V]
IP addresses can be automatically configured, on the following guest OS's on which the integrated services are installed.

[KVM]
When the guest OS type is Linux, IP addresses can be automatically configured.

[Xen] [Oracle VM]
Automatic configuration of IP addresses is not supported.

If a subnet address is set for a network resource, set an IP address manually after deploying an image to an L-Server (Also set an IP address manually on the DNS server).
For details on how to check IP addresses, refer to the Note of "10.3.4 [Network] Tab" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

If no subnet address has been set, manually set a subnet address for operation on the DHCP server after deploying an image to an L-Server.


Automatic Configuration for L2 Switches

When an L-Server or a firewall resource is deployed on an L-Platform, definitions such as interfaces can be automatically configured on the L2 switch on the communication route, using a script created in advance.


Available Network Configurations

Available network configurations and configuration methods in Resource Orchestrator are given below.

PRIMERGY Blade Servers
PRIMERGY Rack Mount Servers, PRIMERGY Tower Servers, or PRIMEQUEST Servers

Point


Network Settings for Physical L-Servers

When configuring NIC redundancy and tagged VLANs, or specifying a Red Hat Enterprise Linux image, the network on the OS is not automatically configured.
Collect an image with the preset script that configures the network at initial OS startup, and then create an L-Server using that image.

Physical L-Server network information (such as IP address, NIC redundancy, and tagged VLAN settings) is transferred to the OS as a network information file when the image is deployed to the OS.
For details on how to configure a network using a network information file, refer to "D.7.4 Network Redundancy and VLAN Settings of L-Servers".

When network configuration is not performed on the OS, create the L-Server then connect to it via the admin LAN or using the console, and configure the network on the OS on the L-Server.

Note

Depending on operating conditions of the network configuration script, a communication error may occur on the business application that is installed on the server.

Since this error cannot be detected by Resource Orchestrator, please check any network errors that occur on user applications to detect it.

When those errors occur, the server or the application must be restarted.

Restart the server using the network configuration script.


Modifying Network Resource Specifications

The following network resource specifications can be modified.

For details on how to modify network specifications, refer to "3.6 Changing Network Resource Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE", and "2.5.2 Modification" in the "Reference Guide (Resource Management) CE".


4.2.4.2 When Using IBP

When using IBP, it is necessary to create an IBP uplink set for the public LAN and the admin LAN in advance.

It is not necessary to combine the name of the uplink set and the name of the network resource.


4.2.4.3 When Using an iSCSI LAN for iSCSI Boot

[Windows/Linux]
Create the following file in advance to define the network information used for iSCSI boot.
The network information is linked with the iSCSI boot information that is registered using the iSCSI boot operation command (rcxadm iscsictl). Refer to "2.4.2 iSCSI Boot Information" in the "Reference Guide (Resource Management) CE" beforehand.

Storage Location of the Definition File

[Windows]
Installation_folder\Manager\etc\customize_data

[Linux]
/etc/opt/FJSVrcvmr/customize_data

Definition File Name

  • User Groups

    iscsi_user_group_name.rcxprop

  • Common on System

    iscsi.rcxprop

Definition File Format

In the definition file, an item to define is entered on each line. Enter the items in the following format.

Variable = Value

When adding comments, start the line with a number sign ("#").

Definition File Items
Table 4.7 Network Definition File Items for iSCSI Boot

Variable

Meaning

Value

server_model.model_name.boot_nic

Specify the server model name and NIC to be booted using iSCSI.
Multiple NICs can be specified.

The following models can be specified:

  • BX620

  • BX920

  • BX922

  • BX924

  • BX960

When setting the default, specify an asterisk ("*").

Specify the items in the following format.

NIC[index]

index is an integer starting from 1.

Example

#Server Section
server_model.BX922.boot_nic = NIC1
server_model.BX924.boot_nic = NIC1,NIC2
server_model.*.boot_nic = NIC1,NIC2

  • The entries are evaluated in the order they are added. When the same entry is found, the evaluation will be performed on the first one.

  • When setting the default, specify an asterisk ("*").


4.2.4.4 When Using Link Aggregation

When using link aggregation, configure link aggregation on the LAN switch blade and L2 switch in advance. For details on configuration of link aggregation, refer to the manual of the LAN switch blade and L2 switch.

When creating a network resource, specify the link aggregation group name as the external connection port of the network resource.

For details, refer to "C.3 Using Link Aggregation".


4.2.4.5 When Using NICs other than Those in the Default Configuration of the Automatic Network Configuration

When using blade servers, NICs other than those in the default configuration of automatic network configuration can be used by creating and registering a server NIC definition with the manager in advance.

The created server NIC definition can be enabled by executing the rcxadm nicdefctl commit command. In the server NIC definition, define the relationship between the NICs of the managed blade servers and a physical LAN segment. By specifying this physical LAN segment from the network resource, it is possible to specify the NIC used by the network resource.

For details on the server NIC definitions, refer to "2.11 Server NIC Definition" of the "Reference Guide (Resource Management) CE".
For details on the rcxadm nicdefctl commit command, refer to "1.7.16 rcxadm nicdefctl" in the "Reference Guide (Resource Management) CE".


4.2.4.6 When Using Automatic Virtual Switch Configuration on Rack Mount or Tower Servers

When using VMware on managed rack mount or tower servers, virtual switches and port groups can be automatically configured. In this case, it is necessary to create a server NIC definition and register it with the manager.

Use the rcxadm nicdefctl commit command to register the server NIC definition with the manager.
For details on the server NIC definitions, refer to "2.11 Server NIC Definition" of the "Reference Guide (Resource Management) CE".
For details on the rcxadm nicdefctl commit command, refer to "1.7.16 rcxadm nicdefctl" in the "Reference Guide (Resource Management) CE".


4.2.4.7 When Deploying L-Servers even if the Service Console and Port Group are the Same

When using VMware as the server virtualization software, in order to deploy L-Servers even if the service console and port group is the same, it is necessary to create a VMware excluded port group definition file.

For details on VMware excluded port group definition files, refer to "2.12 VMware Excluded Port Group Definition File" in the "Reference Guide (Resource Management) CE".


4.2.4.8 When Registering Network Devices as Resources

The infrastructure administrator creates network configuration information (XML definition files) for registering network devices based on the network device information (admin IP address, account information, connection information) obtained from the network device administrator.

See

  • For details on network configuration information (XML definitions), refer to "2.6 Network Configuration Information" in the "Reference Guide (Resource Management) CE".

  • For details on the rcxadm netconfig command, refer to "1.3.7 rcxadm netconfig" in the "Reference Guide (Resource Management) CE".

  • For details on releasing maintenance mode, refer to "14.1 Switchover of Maintenance Mode" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

  • For details on model definitions for network devices, refer to "2.13 Network Device Model Definition" in the "Reference Guide (Resource Management) CE".



4.2.4.9 When Automatically Configuring Network Devices

This section explains how to prepare to use the function for automatically configuring network devices.

Information

Automatic configuration of firewalls is not possible if they are not registered in a network pool.


Creating Model Definitions for Network Devices

Rulesets used for the function that automatically configures network devices are registered by network device model. Therefore, it is necessary to create model definitions for determining the models of network devices.

The created model definitions are enabled by registering the following XML definition file:

[Windows]
Installation_folder\Manager\etc\customize_data\network_device_model.xml

[Linux]
/etc/opt/FJSVrcvmr/customize_data/network_device_model.xml

Newly-added models can be supported by editing the model definitions.

The network device model definitions provided with sample scripts for automatic configuration of network devices are registered in the above folder when Resource Orchestrator is installed.

Information

When editing a model definition, check the sysObjectID of the network device using the snmpwalk command.

Example

snmpwalk -v 1 -c [SNMP_community_name] [IP_address] sysObjectID

If the information is available from the manual or vendor of the destination device, obtain it from there.

See

For details on model definitions for network devices, refer to "2.13 Network Device Model Definition" in the "Reference Guide (Resource Management) CE".

Note

Use the specified OID string as the SysObjectId element in the Model element to specify the model name of the network device.

  • The model definition file of network devices is searched from the start, and the first sysObjectID that matches will be used as the model name of the name attribute of the Model element.

  • When there is no matching OID string in the model definition file, the model name is not specified.



Creating a Folder for Registering Rulesets

The function for automatically configuring network devices is used by executing the scripts prepared by the infrastructure administrator for each network device.

When it is necessary to specify settings that differ according to the provided service, register these patterns as separate rules to manage them. This management is performed by the ruleset.
Create a folder for registering scripts, etc. for each ruleset.

There are two types of folders for registering rulesets; folders for L-Platform templates and folders for network resources.

Folders for L-Platform Templates

Create the folders for registering rulesets for L-Platform templates with the following name:

[Windows]
Installation_folder\Manager\etc\scripts\vendor_name\unit_name or model_name\rulesets\ruleset_name\

[Linux]
/etc/opt/FJSVrcvmr/scripts/vendor_name/unit_name or model_name/rulesets/ruleset_name/

Folders for Network Resources

Create the folders for registering rulesets for network resources with the following name:

[Windows]
Installation_folder\Manager\etc\scripts\network_resource\ruleset_name\

[Linux]
/etc/opt/FJSVrcvmr/scripts/network_resource/ruleset_name/

Information

  • For "vendor_name", "unit_name", and "model_name", specify the "vendor name", "unit name", and "model name" of the target network device for script execution, respectively.
    The "Vendor name", "unit name", and "model name" of a network device can be confirmed by checking the model definition (XML file) for that device.
    For details on model definitions for network devices, refer to "2.13 Network Device Model Definition" in the "Reference Guide (Resource Management) CE".

  • Specify the folder name of "ruleset name" using up to 32 characters, including alphanumeric characters, underscores ("_"), and hyphens ("-"). This name should start with an alphabetical character.

    Set a unique name for the folder name of "ruleset name", excluding the following folders in which sample scripts are registered.

    [Windows]
    Installation_folder\Manager\etc\scripts\

    [Linux]
    /etc/opt/FJSVrcvmr/scripts/



Sample Scripts

Sample scripts to be used for automatic configuration of network devices are registered in the following folder when Resource Orchestrator is installed.

[Windows]
Installation_folder\Manager\etc\scripts\original\vendor_name\unit_name\rulesets\ruleset_name\
Installation_folder\Manager\etc\scripts\original\network_resource\ruleset_name\

[Linux]
/etc/opt/FJSVrcvmr/scripts/original/vendor_name/unit_name/rulesets/ruleset_name/
/etc/opt/FJSVrcvmr/scripts/original/network_resource/ruleset_name/

The following table lists the unit names supported by the sample scripts provided by Resource Orchestrator:

Table 4.8 Units for which Sample Scripts are Provided

Vendor

Unit Name

Type

Setting Details

Fujitsu

SR-X500

L2 switch

  • Add VLAN (tagged VLAN, port VLAN)

  • Delete VLAN (tagged VLAN, port VLAN)

  • Add VLAN to LAG interface (tagged VLAN, port VLAN)

  • Delete VLAN of LAG interface (tagged VLAN, port VLAN)

SR-X300

IPCOMEXSC

Firewall (*1)

  • External interface (center switch side)

    • Add or delete Firewall rules

    • Add or delete dstNAT rules

    • Add or delete srcNAT rules

  • Internal interface (L2 switches)

    • Add or delete VLAN interface

    • Add or delete Firewall rules

IPCOMEXIN

Cisco

Catalyst

L2 switch

  • Add VLAN (tagged VLAN, port VLAN)

  • Delete VLAN (tagged VLAN, port VLAN)

  • Add VLAN to LAG interface (tagged VLAN, port VLAN)

  • Delete VLAN of LAG interface (tagged VLAN, port VLAN)

ASA5500

Firewall (*1)

  • External interface (center switch side)

    • Add or delete Firewall rules

    • Add or delete dstNAT rules

    • Add or delete srcNAT rules

  • Internal interface (L2 switches)

    • Add or delete VLAN interface

    • Add or delete Firewall rules

*1: Configure Firewall rules for the VLAN interfaces of LAN ports to use as public LANs.

The default model configuration assumed by a sample script is given below:

Figure 4.19 Default Model Configuration for a Sample Script

Listed below are sample ruleset names provided by Resource Orchestrator:

For SR-X300
tag_vlan_port--SR-X300
tag_vlan_port--SR-X300_n

For the systems that configure tagged VLANs on the LAN ports connected with firewalls and servers

untag_vlan_port--SR-X300
untag_vlan_port--SR-X300_n

For the systems that configure port VLANs on the LAN ports connected with firewalls and servers

tag_vlan_net--SR-X300
tag_vlan_net--SR-X300_n

For the systems that configure tagged VLAN networks

untag_vlan_net--SR-X300
untag_vlan_net--SR-X300_n

For the systems that configure untagged VLAN networks

n: Number of "2" or larger

For SR-X500
tag_vlan_port--SR-X500
tag_vlan_port--SR-X500_n

For the systems that configure tagged VLANs on the LAN ports connected with firewalls and servers

untag_vlan_port--SR-X500
untag_vlan_port--SR-X500_n

For the systems that configure port VLANs on the LAN ports connected with firewalls and servers

tag_vlan_net--SR-X500
tag_vlan_net--SR-X500_n

For the systems that configure tagged VLAN networks

untag_vlan_net--SR-X500
untag_vlan_net--SR-X500_n

For the systems that configure untagged VLAN networks

n: Number of "2" or larger

For IPCOM EX SC
3Tier_system_firewall--IPCOMSC1

For the systems that use IPCOMEX1100_SC/1300_SC/2000A_SC as an IPCOM EX SC series model for three-tier models

LAN Ports to be Used

  • For Public LANs (Center Switch Side)

    LAN0.0

  • For Public LANs (L2 Switch Side)

    LAN0.1

  • For the Admin LAN

    LAN0.3

  • For Unit Synchronization

    LAN0.2

3Tier_system_firewall--IPCOMSC2

For the systems that use IPCOMEX2000A_SC/2300_SC as an IPCOM EX SC series model for three-tier models

LAN Ports to be Used

  • For Public LANs (Center Switch Side)

    bnd0: Redundant LAN Channels

    LAN0.0
    LAN1.0

  • For Public LANs (L2 Switch Side)

    bnd1: Redundant LAN Channels

    LAN0.1
    LAN1.1

  • For the Admin LAN

    LAN0.3

  • For Unit Synchronization

    LAN1.3

3Tier_system_firewall--IPCOMSC3

For the systems that use IPCOMEX2500_SC as an IPCOM EX SC series model for three-tier models

LAN Ports to be Used

  • For Public LANs (Center Switch Side)

    bnd0: Redundant LAN Channels

    LAN0.0
    LAN1.0

  • For Public LANs (L2 Switch Side)

    bnd1: Redundant LAN Channels

    LAN0.1 and LAN0.2
    LAN1.1 and LAN1.2

    Connection using Link aggregation

  • For the Admin LAN

    LAN0.3

  • For Unit Synchronization

    LAN1.3

For IPCOM EX IN
3Tier_system_firewall--IPCOMIN2

For the systems that use IPCOMEX2000A_IN/2300_IN as an IPCOM EX IN series model for three-tier models

LAN Ports to be Used

  • For Public LANs (Center Switch Side)

    bnd0: Redundant LAN Channels

    LAN0.0
    LAN1.0

  • For Public LANs (L2 Switch Side)

    bnd1: Redundant LAN Channels

    LAN0.1
    LAN1.1

  • For the Admin LAN

    LAN0.3

  • For Unit Synchronization

    LAN1.3

3Tier_system_firewall--IPCOMIN3

For the systems that use IPCOMEX2500_IN as an IPCOM EX IN series model for three-tier models

LAN Ports to be Used

  • For Public LANs (Center Switch Side)

    bnd0: Redundant LAN Channels

    LAN0.0
    LAN1.0

  • For Public LANs (L2 Switch Side)

    bnd1: Redundant LAN Channels

    LAN0.1 and LAN0.2
    LAN1.1 and LAN1.2

    Connection using Link aggregation

  • For the Admin LAN

    LAN0.3

  • For Unit Synchronization

    LAN1.3

For Catalyst
tag_vlan_port--Catalyst
tag_vlan_port--Catalystn

For the systems that configure tagged VLANs on the LAN ports connected with firewalls and servers

untag_vlan_port--Catalyst
untag_vlan_port--Catalystn

For the systems that configure port VLANs on the LAN ports connected with firewalls and servers

tag_vlan_net--Catalyst
tag_vlan_net--Catalystn

For the systems that configure tagged VLAN networks

untag_vlan_net--Catalyst
untag_vlan_net--Catalystn

For the systems that configure untagged VLAN networks

n: Number of "2" or larger

For ASA5500
3Tier_system_firewall--ASA1

For the systems that use ASA5510 as an ASA5500 series model for three-tier models

LAN Ports to be Used

  • For Public LANs (Center Switch Side)

    redundant1: Redundant LAN Channels

    ethernet0/0
    ethernet0/1

  • For Public LANs (L2 Switch Side)

    redundant2: Redundant LAN Channels

    ethernet0/2
    ethernet0/3

  • For the Admin LAN

    management0/0

3Tier_system_firewall--ASA2

For the systems that use ASA5520/5540/5550 as an ASA5500 series model for three-tier models

LAN Ports to be Used

  • For Public LANs (Center Switch Side)

    redundant1: Redundant LAN Channels

    gigabitethernet0/0
    gigabitethernet0/1

  • For Public LANs (L2 Switch Side)

    redundant2: Redundant LAN Channels

    gigabitethernet0/2
    gigabitethernet0/3

  • For the Admin LAN

    management0/0

3Tier_system_firewall--ASA3

For the systems that use ASA5580 as an ASA5500 series model for three-tier models

LAN Ports to be Used

  • For Public LANs (Center Switch Side)

    redundant1: Redundant LAN Channels

    gigabitethernet3/0
    gigabitethernet3/1

  • For Public LANs (L2 Switch Side)

    redundant2: Redundant LAN Channels

    gigabitethernet3/2
    gigabitethernet3/3

  • For the Admin LAN

    management0/0

The following script lists are also provided as samples for each ruleset:

Note

The sample scripts provided by Resource Orchestrator may be added or deleted when the software is updated.

When using the sample scripts, confirm the directory on the admin server in which the sample scripts are registered beforehand.


Copy Destination of Sample Script Rulesets

Rulesets in which sample scripts are registered are copied to the folder for ruleset registration during installation and made available for use.

For example, when using an SR-X300 as an L2 switch, and an IPCOM EX1300 SC, rulesets are copied as follows:

PreviousNext
Copyright FUJITSU LIMITED 2010-2012