Create the necessary definition files.
This section explains how to create the following definition files:
Configuration information pre-definition file
Specify when using rack mount servers.
Definition files combining ports of SAN storage
Create definition files combining ports of SAN storage.
Network configuration information files
Create the network configuration information file necessary for registering NS Appliance as a network device.
NS Appliance Pre-configuration File
Create the NS Appliance pre-configuration file which is necessary for pre-configuring the external network that is a prerequisite for use of the auto-configuration function during L-Platform creation.
Network Device Configuration File Management Function Definition
Define it when using the network device configuration file management functions.
Configuration Files for Creating Dedicated Physical L-Servers for NS Appliance
Create the configuration file when creating a dedicated physical L-Server for NS Appliances using the rcxnetworkservice create command.
Specify when using rack mount servers.
For details, refer to "7.1.6 Configuration when Creating a Physical L-Server without Specifying a Model Name in the L-Server Template" in the "Setup Guide CE".
Create definition files combining ports of SAN storage.
For details, refer to "7.1 Creating Definition Files" in the "Setup Guide CE".
Create the network configuration information file necessary for registering NS Appliance as a network device.
In the network configuration information file, specify the information defined when "2.1.2 Designing the Network Environment".
For details on creating network configuration information files and their definition content, refer to "15.7 Network Configuration Information" in the "Reference Guide (Command/XML) CE".
A tool for quickly creating network configuration information (XML definitions) is available on the FUJITSU Software ServerView Resource Orchestrator Web site. This tool makes it easy to create network configuration information (XML definitions).
Specify an IPv4 address.
Specify in the IPv4 format.
Specify a character string containing up to 32 alphanumeric characters, periods ("."), and hyphens ("-").
When using it as a firewall, specify "Firewall".
Specify "Firewall" and "SLB", when using it as an integrated network device.
Specify "virtual".
Specify the IP address of the dedicated server for NS Appliance in IPv4 format.
Specify "Fujitsu".
Specify "NSAppliance".
Specify a character string containing up to 32 alphanumeric characters, underscores ("_"), and hyphens ("-").
Specify "user".
Specify a character string containing up to 32 alphanumeric characters, underscores ("_"), and hyphens ("-").
Specify a character string containing between 6 and 64 alphanumeric characters and symbols (!$%()_-~^[]:+,).
Specify a character string containing between 6 and 64 alphanumeric characters and symbols (!$%()_-~^[]:+,).
For network configuration using the same VLAN ID (same network) as the admin LAN of dedicated servers for deployment of NS Appliances, omit this element.
For network configuration using different VLAN IDs from the admin LAN of dedicated servers for NS Appliances, specify the VLAN ID of the admin LAN of NS Appliances.
When Using Auto-configuration of Network Devices Using User Customization Mode
Omit this element.
When Using Auto-configuration on Network Devices Using Simple Configuration Mode
Specify "1", "5", or "9".
When omitted, "5" is set.
When Using Auto-configuration of Network Devices Using User Customization Mode
Omit this element.
When Using Auto-configuration on Network Devices Using Simple Configuration Mode
Specify "Simple".
When performing automatic configuration of an integrated network device in simple mode, specify "60".
See
For more information about registering network configuration information (XML definition), refer to "9.4.8 When Managing Network Devices as Resources" in the "Design Guide CE".
Create an NS Appliance pre-configuration file according to the information decided in "2.1.3 Designing the L-Platform Network Environment".
The XML definition of the NS Appliance pre-configuration file is as shown below.
<?xml version="1.0" encoding="utf-8"?> <NsAppConfigurations> <NsAppConfig name="NS Appliance name"> <PublicInterfaces> <Interface type="Interface type" ip="IP address" mask="Subnet mask" vlanid="VLAN-ID"/> </PublicInterfaces> <IpRoutes> <IpRoute network="Destination address" gateway="Gateway address"/> </IpRoutes> </NsAppConfig> </NsAppConfigurations>
The items specified in the XML Definition for the NS Appliance Pre-configuration File are as follow.
Element Name | Description | Available Values or Example |
|---|---|---|
NS appliance name (NsAppConfig name) | NS appliance device name | Specify the NS appliance device name. Use the same name as the device name described in the network configuration information file. |
Interface (Interface) | Interface definition | When performing auto-configuration in user customization mode, specify only one definition configured in the external interface. When performing auto-configuration in simple configuration mode, specify the definition configured in the interface for the internet side and for the intranet side respectively, based on the network design. |
Interface type (Interface type) | Type of interface | Specify the interface type configured in the external interface of the NS appliance. Specify one of the following, only when performing auto-configuration in simple configuration mode.
|
IP address (Interface ip) | IP address of interface | Specify an IPv4 address. |
Subnet mask (Interface mask) | Subnet mask of interface Subnet mask | Specify the subnet mask. Specify the subnet mask using a value between 128.0.0.0 and 255.255.255.252. |
VLAN-ID (Interface vlanid) | VLAN-ID of interface VLAN-ID | Specify the VLAN-ID. Specify an integer between 1 and 4094. |
Route information (IpRoute) | Route information | Specify the route information. Specify one or multiple sets of route information. |
Destination address (IpRoute network) | Network Address/Mask Length | Specify the address using the IPv4 prefix format. When specifying it as the default gateway, specify "0.0.0.0/0". |
Gateway Address (IpRoute gateway) | Gateway Address | Specify the gateway address. |
Example
<?xml version="1.0" encoding="utf-8"?>
<NsAppConfigurations>
<NsAppConfig name="NS01">
<PublicInterfaces>
<Interface type="Internet" ip="192.168.10.10" mask="255.255.255.0" vlanid="10"/>
<Interface type="Intranet" ip="192.168.15.10" mask="255.255.255.0" vlanid="15"/>
</PublicInterfaces>
<IpRoutes>
<IpRoute network="0.0.0.0/0" gateway="192.168.10.1"/>
</IpRoutes>
</NsAppConfig>
</NsAppConfigurations>Define it when using the network device configuration file management functions.
When using an internal disk of a dedicated server for an NS Appliance, the network device file management functions make it easier to recover from server failure.
For details on the network device configuration file management functions, refer to the following:
Usage method
"9.4.8.2 When Using the Network Device File Management Function" in the "Design Guide CE"
Operation method
"10.2 Backup and Restoration of Network Devices" in the "Operation Guide CE"
When using the network device file management function, note the following points:
The network device configuration file management function creates a temporary file in NS Appliances.
For this reason, do not create the following files in NS Appliances:
ror-running-config.cli
ror-startup-config.cli
When performing the following on an NS Appliance, back up the network device configuration file using the rcxadm netdevice cfbackup command.
Preparations for NS Appliances
Pre-configuration of NS Appliances
For details on the rcxadm netdevice command, refer to "3.8 rcxadm netdevice" in the "Reference Guide (Command/XML) CE".
Create the configuration file when creating a dedicated physical L-Server for NS Appliances using the rcxnetworkservice create command.
It can be created using commands when the following conditions are satisfied. When the conditions are not met or when performing creation using the GUI (operation from the ROR console), it is not necessary to create this file.
When creating a dedicated server for NS appliances using SAN storage
When using an admin LAN in which NIC1 and NIC2 are in a redundant configuration
State one item on each line as follows:
"item name" = value
Be aware that character strings are case-sensitive.
When omitting optional items, do not state the entire line.
Save the file using the UTF-8 encoding format.
Specify the following information:
Item Name | Description | Expected Values |
|---|---|---|
FOLDER | Destination resource folder | The folder to which the L-Server will be deployed To specify the level, use the following format: Resource_folder_name/Resource_folder_name Tenant_folder_name/Resource_folder_name Resource_folder_name/Tenant_folder_name |
LSERVER | L-Server name | The name of the L-Server to be deployed |
IMAGE | Image | A cloning image for NS Option to use for deployment |
FC_CONNECTION | FC connection pattern (optional) | Specify the name of the pattern file for FC connections, excluding the file extension. For details on FC connection pattern files, refer to "7.1 Creating Definition Files" in the "Setup Guide CE". |
MODEL | Model name of the server that is being assigned to the L-Server (optional) | Specify the model name of the server that is being assigned to the L-Server. The model name of a server can be confirmed by selecting a server resource from the server resource tree and checking the [Resource Details] tab. If the model name is omitted, it is treated as if PRIMERGY BX924 S2 was specified. |
DISK_NAME | Disk name of the existing LUN | Disk name of the LUN which was created in advance using storage management software, for allocation to the L-Server |
VSTORAGE_NAME | Virtual storage resource (Optional, when specifying the storage pool) | The resource name of an existing virtual storage |
STORAGE_POOL | Storage pool (Optional, when specifying a virtual storage resource) | 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 to enable identification. Resource_folder_name/Resource_pool_name |
NETWORK_NAME | Network | Name of the network resource that the L-Server connects to Specify an admin LAN resource. |
IP_AUTO | IP address automatic configuration | For automatic configuration of the IP address to be assigned to the L-Server, specify one of the following:
|
IP_ADDRESS | IP address (Specify when specifying "false" for IP address automatic configuration) | IP address |
MAC_[index]_AUTO (*1) | MAC address automatic configuration | Determines whether to perform automatic configuration of the MAC address to be assigned to a NIC. Specify one of the following:
|
MAC_[index]_ADDRESS (*1) | MAC address (Specify when specifying "false" for MAC address automatic configuration) | MAC address Enter a string delimited by hyphens ("-") or colons (":"). |
MAC_[index]_RESOURCE (*1) | MAC address set resource (Specify when specifying "true" for MAC address automatic configuration | Address set resource from which the MAC address is assigned |
MAC_[index]_POOL (*1) | MAC address pool (Specify when specifying "true" for MAC address automatic configuration | Address pool from which the MAC address is assigned |
HBA | HBA count | The number of HBAs to allocate to the L-Server |
WWN_[index]_AUTO (*2) | WWN automatic configuration (Specify the same number as the HBA count) | Determines whether to allocate a WWN automatically. Specify one of the following:
|
WWN_[index] (*2) | WWN (Specify when specifying "false" for WWN automatic configuration) | WWN Specify the WWN in colon (":") delimited form. |
WWN_[index]_RESOURCE (*2) | WWN address set resource (Specify when specifying "true" for WWN automatic configuration | Address set resource from which the WWN is assigned |
WWN_[index]_POOL (*2) | WWN address pool (Specify when specifying "true" for WWN automatic configuration | Address pool from which the WWN is assigned |
ADDRESS_POOL | Address pool | Address pool to allocate to the L-Server If there are storage pools with the same name on different levels, the level must also be specified to enable identification. To specify the level, use the following format: Resource_folder_name/Resource_pool_name |
REDUNDANCY | Redundancy | Specify the server redundancy to be assigned to the L-Server. Specify one of the following:
|
PHYSICAL_SERVER | Physical server (Optional, when specifying the server pool) | Physical server to allocate to the L-Server |
SERVER_POOL | Server pool (Optional, when specifying a physical server) | Resource pool that comprises the physical servers allocated to L-Servers If there are storage pools with the same name on different levels, the level must also be specified to enable identification. To specify the level, use the following format: Resource_folder_name/Resource_pool_name |
RESERVE_SERVER_POOL | Server pool for reserve settings (Specify when specifying "HA" for Redundancy) | Server pool for reserve settings |
*1: In index, specify 0 and 1.
*2: In index, specify an integer starting from 0 to the number specified for the HBA item.
Example
FOLDER=NSAPP
LSERVER=NSApp
IMAGE=NS_OPTION_BX924S2_001_001
DISK_NAME=NS
STORAGE_POOL=NS_Storage_Pool
NETWORK_NAME=AdminLAN
IP_AUTO=true
MAC_0_AUTO=true
MAC_1_AUTO=false
MAC_1_ADDRESS="XX:XX:XX:XX:XX:X1"
MAC_0_POOL=NS_Pool
HBA=1
WWN_0_AUTO=true
WWN_0_POOL=NS_Pool
ADDRESS_POOL=NS_pool
REDUNDANCY=HA
PHYSICAL_SERVER=BX924
RESERVE_SERVER_POOL=NS_Server_Pool