Home » Dell Manuals » Servers » Dell DX6004S » Manual Viewer

Dell DX6004S DX Content Router Setup and Configuration Guide - Page 27

Request for Source Cluster IP Addresses

Add to My Manuals
Save this manual to your list of manuals

Page 27 highlights

uuid=... . . . 5.5.3. Request for Source Cluster IP Addresses Publisher clients such as Replicator may need to know IP addresses of nodes in the CAStor source cluster that Publisher listens to (in order to make SCSP requests to this cluster). The Publisher Channel Server will support a request for a list of source cluster IP addresses and SCSP port numbers: GET /sourceclusteripports.bin HTTP/1.1 You will want to provide the publisher's IP address & the Publication Server Port as part of the request. For example: http://publisherIp:publicationServerPort/sourceclusteripports.bin A normal response to this request is: HTTP/1.1 200 Date: ... Server: Content Router Publisher Content-Type: text/plain Content-Length: ... Each line of the response body will be of the form ":". Over time, new source cluster nodes may come online and others may go offline, so it may become necessary for a client to update its list of IP addresses. This could be done, for instance, whenever a previously accessible source cluster node is no longer accessible, or at regular time intervals. Copyright © 2010 Caringo, Inc. All rights reserved 23 Version 2.2 December 2010

Section	Page
Content Router Setup and Configuration Guide	1
Table of Contents	3
Chapter 1. Introduction to DX Content Router	5
1.1. Overview of DX Content Router	5
1.2. About this Document	5
1.2.1. Audience	5
1.2.2. Scope	5
Chapter 2. Replication Topologies	6
2.1. Disaster Recovery	6
2.2. Mirrored Clusters	6
2.3. Multi-Site Disaster Recovery	6
2.4. Content Distribution	7
Chapter 3. DX Content Router Services	8
3.1. Basic Architecture	8
3.1.1. Structure of a DX Content Router Node	9
3.1.2. Publisher Service	11
3.1.2.1. Filtering UUIDs for Publication	11
3.1.2.2. Rules	13
3.1.3. Replicator Service	14
Chapter 4. Installation	15
4.1. Requirements	15
4.1.1. Operating System	15
4.1.2. 3rd Party Package Pre-requisites	15
4.1.3. Network	15
4.1.3.1. Required Communications	15
4.1.3.2. Bandwidth Requirements	15
4.1.3.3. Recommended Infrastructure	16
4.1.3.4. IP Address Configuration	16
4.2. Installing and Configuring DX Content Router Services	17
4.2.1. Installing Services	17
4.2.2. Configuring Services and Rules	17
4.3. Upgrading DX Content Router	18
4.3.1. Upgrading from 1.x	18
4.3.2. Upgrading from 2.x	18
4.4. Removing DX Content Router	18
Chapter 5. Running and Managing DX Content Router	19
5.1. Starting DX Content Router Services	19
5.2. Publisher and Replicator Shutdown	19
5.3. Customizing the Standard Rule Sets	19
5.3.1. Publish all streams on a single channel	19
5.3.2. Publish all streams on two separate channels	20
5.3.3. Publish streams with header ‘someHeaderName’ on one channel and all others except text files to a second	20
5.3.4. Complex Content Metadata Analysis	20
5.3.4.1. Filter Clause	20
5.3.4.2. Exists Clause	21
5.3.4.3. NotExists Clause	22
5.3.4.4. All Clauses	22
5.4. Using the Publisher Console	22
5.4.1. Publisher Console layout:	23
5.5. HTTP Status Reporting for Publisher and Replicator	25
5.5.1. Publisher Response	25
5.5.2. Replicator Response	26
5.5.3. Request for Source Cluster IP Addresses	27
Chapter 6. Support for Content Restoration and Fail-Over	28
6.1. Administrative Disaster Recovery	28
6.2. Content Mirroring	28
6.3. Application-Assisted Fail-Over	28
Appendix A. Content Metadata	29
A.1. System Metadata	29
A.2. Content File Server Metadata	29
A.2.1. Custom Metadata	29
Appendix B. DX Content Router Configuration	30
B.1. Publisher Configuration	30
B.2. Replicator Configuration	34
Appendix C. Enumerator API	38
C.1. Enumerator Types	38
C.2. Enumerator Start	38
C.2.1. Enumerator Start Query Arguments	39
C.2.2. Enumerator Start Response	39
C.3. Enumerator Next	40
C.3.1. Enumerator Next Query Arguments	40
C.3.2. Enumerator Next Response	41
C.4. Enumerator End	41
C.4.1. End Response	41
C.5. Enumerator Timeout	42

Match case Limit results 1 per page

Version 2.2

December 2010

uuid=...

5.5.3. Request for Source Cluster IP Addresses

Publisher clients such as Replicator may need to know IP addresses of nodes in the CAStor source

cluster that Publisher listens to (in order to make SCSP requests to this cluster). The Publisher

Channel Server will support a request for a list of source cluster IP addresses and SCSP port

numbers:

GET /sourceclusteripports.bin HTTP/1.1

You will want to provide the publisher's IP address & the Publication Server Port as part of the

request. For example:

http://publisherIp:publicationServerPort/sourceclusteripports.bin

A normal response to this request is:

HTTP/1.1 200

Date: ...

Server: Content Router Publisher

Content-Type: text/plain

Content-Length: ...

Each line of the response body will be of the form "<source cluster IP address>:<SCSP port

number>". Over time, new source cluster nodes may come online and others may go offline, so

it may become necessary for a client to update its list of IP addresses. This could be done, for

instance, whenever a previously accessible source cluster node is no longer accessible, or at

regular time intervals.