Dell DX6004S DX Object Storage SCSP Proxy Overview - Page 5

Response Headers, Response, Description, Reason for empty node list, Meaning

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

Page 5 highlights

configured cluster name. If the names do not match, no node IP addresses are returned in the response. If Scsp-Proxy-Cluster is not present, the request uses the configured cluster name and the list of node IP addresses reflects the currently known node IPs for that cluster. In either case, the response metadata includes a response header with the same name containing the cluster name used by the Proxy. 1.1.1.2. Response Headers The following table discusses response headers: Response Scsp-Proxy-Cluster Scsp-Proxy-Nodes Scsp-Proxy-Agent Castor-SystemTotalGBAvailable, CastorSystem-TotalGBCapacity Description Cluster name (for example, if the cluster is configured on a CSN, it is the value of scsp.clusterName in /etc/ caringo/scspproxy/scspproxy.cfg). ASCII string count of the number of node IP addresses returned in the body of the response. If this count is zero, an additional reason is supplied to explain why there were no nodes returned. More information about the zero-node response is discussed following the table. Proxy and its software version. Obtained by polling any available node on the local cluster. These headers are provided to maintain consistency with current Proxy and DX Storage responses. For example, the following response indicates there are 10 nodes in the cluster: Scsp-Proxy-Nodes: count=10 If the response indicates zero nodes in the cluster, it is accompanied by a reason, as follows: Scsp-Proxy-Nodes: count=0, reason=no-nodes The following table discusses reason codes. Reason for empty node list no-nodes bad-subnet bad-cluster Meaning The Proxy reports no nodes when, for example, the cluster is off-line or is being rebooted. The request was made from a subnet from which the node IP addresses are not routable. The Proxy determines whether or not a request originated from the same private subnet as its cluster and responds only if the request did originate in that subnet. The Proxy does this to help prevent malicious discovery about the cluster and because private IP addresses are not routable anyway. The cluster name supplied in the Scsp-Proxy-Cluster header did not match the currently configured cluster. Copyright © 2010 Caringo, Inc. All rights reserved 2 Version 1.2 December 2010

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
Copyright © 2010 Caringo, Inc.
All rights reserved
2
Version 1.2
December 2010
configured cluster name. If the names do not match, no node IP addresses are returned in the
response.
If Scsp-Proxy-Cluster is not present, the request uses the configured cluster name and the list of
node IP addresses reflects the currently known node IPs for that cluster.
In either case, the response metadata includes a response header with the same name containing
the cluster name used by the Proxy.
1.1.1.2. Response Headers
The following table discusses response headers:
Response
Description
Scsp-Proxy-Cluster
Cluster name (for example, if the cluster is configured on
a CSN, it is the value of
scsp.clusterName
in
/etc/
caringo/scspproxy/scspproxy.cfg
).
Scsp-Proxy-Nodes
ASCII string count of the number of node IP addresses
returned in the body of the response. If this count is zero,
an additional reason is supplied to explain why there were
no nodes returned. More information about the zero-node
response is discussed following the table.
Scsp-Proxy-Agent
Proxy and its software version.
Castor-System-
TotalGBAvailable
,
Castor-
System-TotalGBCapacity
Obtained by polling any available node on the local
cluster. These headers are provided to maintain
consistency with current Proxy and DX Storage
responses.
For example, the following response indicates there are 10 nodes in the cluster:
Scsp-Proxy-Nodes: count=10
If the response indicates zero nodes in the cluster, it is accompanied by a reason, as follows:
Scsp-Proxy-Nodes: count=0, reason=no-nodes
The following table discusses
reason
codes.
Reason for empty node list
Meaning
no-nodes
The Proxy reports no nodes when, for example, the cluster is
off-line or is being rebooted.
bad-subnet
The request was made from a subnet from which the node IP
addresses are not routable.
The Proxy determines whether or not a request originated from
the same private subnet as its cluster and responds only if the
request did originate in that subnet. The Proxy does this to help
prevent malicious discovery about the cluster and because
private IP addresses are not routable anyway.
bad-cluster
The cluster name supplied in the
Scsp-Proxy-Cluster
header did not match the currently configured cluster.