- ページ 16

サーバー Dell DX6000のPDF 設定・構成マニュアルをオンラインで閲覧またはダウンロードできます。Dell DX6000 43 ページ。 Rack installation instructions — static rails
Dell DX6000 にも：補足マニュアル (4 ページ), ハードウェア取り付け説明書 (2 ページ), ユーザーマニュアル (46 ページ), インストールおよび設定マニュアル (35 ページ), スタートマニュアル (28 ページ), お知らせ (28 ページ), お知らせ (20 ページ), 概要 (19 ページ), 設定マニュアル (9 ページ), 設定マニュアル (9 ページ), リリースノート (8 ページ), リファレンス・マニュアル (12 ページ), 設定マニュアル (7 ページ), リリースノート (6 ページ), リリースノート (5 ページ), リリースノート (5 ページ), インストレーション・インストラクション (2 ページ), インストレーション・インストラクション (2 ページ)

bytes/sec between clusters based on the calculation above will need to modify the 'minBytesPerSec'

parameter in the DX Storage node.cfg or common.cfg file to account for a slower rate and avoid

timeouts. For example, to lower DX Storage's expectations for transfer rate to 512 bytes/sec, the

following parameter should be added to the node or cluster level configuration file to override the

default:

minBytesPerSec = 512

4.1.3.3. Recommended Infrastructure

The following networking services are recommended for the management of a DX Storage cluster

that includes DX Content Router nodes.

• Syslog server for receiving critical alerts

• NTP time server to provide clock synchronization.

Gigabit Ethernet is the recommended connection speed between DX Content Router servers and

DX Storage cluster nodes. A DX Content Router node should use the same speed connection as

the fastest DX Storage node it communicates with to prevent bottlenecks.

4.1.3.4. IP Address Configuration

DX Content Router Services expect a predictable communication pattern and therefore

configuration of one or more static IP addresses for each Content Router server is required. This

can be accomplished through either mapping MAC addresses via DHCP or by physically assigning

the IP addresses on the server. For mirrored environments, Publisher and Replicator each require

their own IP address to ensure communications for the two services do not intermingle. Please

reference the Red Hat documentation for materials on configuring static IPs. The following is an

example of the steps to configure additional alias interfaces in the '/etc/sysconfig/network-scripts'

directory:

1. cd /etc/sysconfig/network-scripts

2. Copy an existing interface file that has the same characteristics as the new alias interface:

cp ifcfg-eth1 ifcfg-eth1:1

3. Edit the new file to create the new alias. The essential fields to update are: DEVICE, IPADDR,

and VLAN. The following is an example of possible modifications to the file created above for a

new eth1:1 interface:

# Public ALIAS bonded interface

# the device value needs to be unique on the system, and should match the

# name specified in the file name.

DEVICE=eth1:1

# the static ip for the interface

IPADDR=192.168.99.110

NETMASK=255.255.0.0

GATEWAY=192.168.1.1

NETWORK=192.168.0.0

BROADCAST=192.168.255.255

BOOTPROTO=none

ONBOOT=yes

USERCTL=no

# set VLAN to yes for ALIAS network interfaces

Version 2.2

December 2010