VLAN=yes
4. Start the new interface:
ifup ifcfg-eth1:1
Note, that if the DX Content Router services are installed on a Cluster Services Node (CSN),
creation of the IP addresses is performed automatically when the services are configured.
4.2. Installing and Configuring DX Content Router Services
4.2.1. Installing Services
The DX Content Router distribution is available as a RHEL rpm package that is installed with a shell
script. The package and its dependencies must be installed as a 'root' user with the following steps:
1. Copy the distributed zip file to your RHEL server and unzip it. Unzipping the distribution on a
separate server and then transferring it to the DX Content Router server is not recommended
as the file may become corrupted during the transfer. The following commands will unzip the file
after it has been copied to the server:
$ sudo su -
# unzip contentrouter-install-2.2.0b1.zip -d
2. Install DX Content Router by running the shell script from the directory location where the shell
script was unzipped. For instance, to install the 2.2 Beta 1 version of the software from the
contentrouter-install-2.2.0b1 directory created above you would run the following commands:
$ sudo su -
# cd contentrouter-install-2.2.0b1
# ./contentrouter-install.sh
Note
If the installation fails due to 'Missing Dependency', make sure you have installed the
packages mentioned above in the 3rd Party Package Pre-requisites section.
If DX Content Router is installed on a Cluster Services Node (CSN), the necessary software will be
installed automatically as part of the overall software bundle.
4.2.2. Configuring Services and Rules
After installing DX Content Router, you must configure the installed services by updating the
configuration files for each service, Replicator and Publisher, you plan to run as well as creating a
filter rules file for Publisher. The configuration files do not exist on the system after installation and
must be created prior to attempting either service. Failure to create and configure these files will
result in a 'Publisher/Replicator not configured' error when you attempt to start the service.
Both services would be utilized for a mirrored configuration where the server is both publishing
UUIDs from a local cluster and receiving incoming UUIDs to replicate from a remote cluster. For a
one-way Disaster Recovery scenario, you would likely only need to configure one of the services
on a single server. Both the Publisher and Replicator services can be configured from the CSN
management console. Please see the 'Configuration' appendix for a full list of all parameters and
best practice instructions for creating the configuration files and rules.xml file by copying the existing
sample configuration.
Copyright © 2010 Caringo, Inc.
All rights reserved
contentrouter-install-2.2.0b1
13
Version 2.2
December 2010
ページを印刷する