Dell PowerVault DX6112 Dell DX Object Storage Platform User's Guide - Page 12

Application Access To DX Object Storage Platform, Communicating Directly With A Local Cluster

Get Dell PowerVault DX6112 PDF manuals and user guides View all Dell PowerVault DX6112 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 12 highlights

NOTE: There can be multiple publishers per cluster, but only the active (or primary) Cluster Services Node can be the active subscriber. Clusters may be connected by any type of link that can handle the desired traffic volume. This link must be secured to prevent reading cluster data being passed between clusters. Cluster data is passed directly between the two DX Cluster Services Nodes. NOTE: It is not recommended to have direct communication between storage nodes in remote clusters. However, for high throughput and high availability applications, system administrators who are well versed with managing RHEL or CentOS systems and who are familiar with IP networking concepts, can directly route to the storage network. For more information about multiple cluster configurations, see the Content Router Setup and Configuration Guide at dell.com/support/manuals. For more information about direct routing between CSN Storage Networks, see the Caringo TechNote2011001 at support.caringo.com. Figure 4. Multiple Cluster Configuration Application Access To DX Object Storage Platform Communicating Directly With A Local Cluster Applications can communicate with a DX Storage Node at any time. The DX Object Storage software automatically redirects applications to the proper node even if the addressed node is an incorrect node to handle a request. If both Cluster Services Node and cluster nodes are not responding, you can communicate with the remote cluster by addressing the remote Cluster Storage Nodes or remote Cluster Services Node directly through the Administrator Console and the appropriate IP address (for example: http://192.168.3.200:90). 12

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
NOTE:
There can be multiple publishers per cluster, but only the active (or primary) Cluster Services Node can be
the active subscriber.
Clusters may be connected by any type of link that can handle the desired traffic volume. This link must be secured to
prevent reading cluster data being passed between clusters.
Cluster data is passed directly between the two DX Cluster Services Nodes.
NOTE:
It is not recommended to have direct communication between storage nodes in remote clusters. However,
for high throughput and high availability applications, system administrators who are well versed with managing
RHEL or CentOS systems and who are familiar with IP networking concepts, can directly route to the storage
network.
For more information about multiple cluster configurations, see the
Content Router Setup and Configuration Guide
at
dell.com/support/manuals
.
For more information about direct routing between CSN Storage Networks, see the
Caringo TechNote2011001
at
support.caringo.com
.
Figure 4. Multiple Cluster Configuration
Application Access To DX Object Storage Platform
Communicating Directly With A Local Cluster
Applications can communicate with a DX Storage Node at any time. The DX Object Storage software automatically
redirects applications to the proper node even if the addressed node is an incorrect node to handle a request. If both
Cluster Services Node and cluster nodes are not responding, you can communicate with the remote cluster by
addressing the remote Cluster Storage Nodes or remote Cluster Services Node directly through the Administrator
Console and the appropriate IP address (for example:
).
12