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

Dell DX6004S DX Object Storage Administration Guide - Page 28

Working With Inaccessible Objects, header, use PUT or POST with

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

Page 28 highlights

the next step or you can remove the Castor-Authorization header and allow another user to modify it. To remove the Castor-Authorization header, use PUT or POST with the admin query argument and your credentials to upload a user realm to the object but do not specify a Castor-Authorization header in the request. 3. PUT the updated Castor-Authorization header and user list to the object. curl -X PUT -i --post301 -H "Castor-Authorization: authorizationspecfication" -H "Castor-Stream-Type: admin" --location-trusted "http://node-ip[/bucket-name[?domain=domain-name]&admin" --anyauth -u "your-username:your-password" --data-binary @user-list [-D log-file] You must specify domain=name in a PUT for a domain. If the PUT is for a bucket, you must pass in the domain name as the Host in the request if the domain is not the default cluster domain. For example, suppose a bucket named testbucket in the domain cluster.example.com has become inaccessible due to either a bad authorization specification or user list. The example that follows shows how you can restore access by changing the Castor-Authorization header and uploading a new user list. The example makes the following assumptions: • cluster.example.com is the default cluster domain so it does not need to be passed in as the Host in the request. • The object's Castor-Authorization header does not contain either owner@ or @owner. • The cluster administrator uses the default user name (admin) and password (ourpwdofchoicehere). • Commands are sent to a node whose IP address is 172.16.0.35. 1. Create the user list. htdigest -c cluster_example_com_testbucket cluster.example.com/ testbucket john.jones 2. PUT the new Castor-Authorization header and user list. curl -i -X PUT --post301 -H "Castor-Authorization: post=cluster.example.com/testbucket, change=cluster.example.com/ testbucket, view=cluster.example.com" -H "Castor-Stream-Type: admin" -location-trusted "http://172.16.0.35/testbucket?admin" --data-binary @cluster_example_com_testbucket -u "admin:ourpwdofchoicehere" -D fixbucket.log 3. Ask a user in the user list to confirm they have access to the object by uploading a new user list to the object or by changing the Castor-Authorization header. 4.7.2. Working With Inaccessible Objects In the event a domain, bucket, or named object is not accessible by usual means, you can access it directly using the cid= query argument. Examples of when this might be useful: • The domain or bucket has been deleted. Copyright © 2010 Caringo, Inc. All rights reserved 23 Version 5.0 December 2010

Section	Page
DX Object Storage Administration Guide	1
Table of Contents	3
Chapter 1. Welcome to DX Storage	6
1.1. Overview of DX Storage	6
1.2. Components	6
1.3. About this Document	6
1.3.1. Audience	6
1.3.2. Scope	6
Chapter 2. Introduction to the Admin Console	7
2.1. Accessing the Admin Console	7
2.2. Initial View of the Admin Console	7
2.2.1. Viewing the Cluster Status Page	7
2.2.2. Viewing a Node's Status Page	8
2.3. Printing the Admin Console	8
2.4. Viewing License Information	8
Chapter 3. Managing the Cluster	10
3.1. Viewing the Cluster Status Page	10
3.2. Authenticating Cluster-Wide Actions	11
3.3. Shutting Down or Restarting the Cluster	12
3.4. Viewing Nodes in the Cluster	12
3.5. Searching for Nodes By IP Address	13
3.6. Searching for Nodes by Status	13
3.7. Choosing and Preserving Cluster Settings	13
3.7.1. Enabling Logging	15
3.7.2. Replication	15
3.7.3. Suspend	15
3.7.4. Power	15
3.7.5. Managing Tenants	15
3.8. Cluster Name	15
3.9. Cluster Multicast Address	15
3.10. % Used Indicator	15
Chapter 4. Managing Tenants	17
4.1. Terminology Related to Tenant Security	18
4.2. About the Default Cluster Domain	19
4.3. Security Privileges for Administrative Operations	20
4.4. Rules and Recommendations for Managing Tenants	21
4.5. Domain Naming Rules	21
4.6. Adding, Editing, or Deleting Tenants	22
4.7. Other Cluster Administrator Tasks	24
4.7.1. Using Administrative Override	25
4.7.1.1. Using Override to Delete an Object	25
4.7.1.2. Using Override to GET or APPEND User Lists	25
4.7.1.3. Using Override to Resolve Authorization Specification Issues	27
4.7.2. Working With Inaccessible Objects	28
Chapter 5. Managing Nodes	30
5.1. Viewing the Node Status Page	30
5.1.1. Shutting Down or Restarting a Node	30
5.1.2. Retiring or Identifying a Node	30
5.1.2.1. Retiring a Node or Volume	30
5.1.2.2. Identifying a Volume	31
5.1.3. Errors and Announcements	31
5.1.4. Additional Node Status Information	31
5.1.4.1. Hardware Status Reporting	33
5.2. Displaying Subcluster Information	34
Chapter 6. Configuring the Node	35
6.1. Option Names and Descriptions	35
6.2. Managing DX Storage Administrators and Users	41
6.2.1. Defining CAStor administrators and SNMP Administrators	41
6.2.2. Defining DX Storage Operators	42
6.2.3. Securing the Administrator and Operator Passwords	42
6.3. Managing Content Integrity Settings	43
6.3.1. autoRepOnWrite	43
6.3.2. repPriority	43
6.3.3. autoValidateRead	43
6.4. Managing Other Stream Replication Settings	44
6.4.1. minreps, maxreps, and defreps	44
6.4.2. hpStartDelay	44
6.5. Managing Volumes	44
6.5.1. device	45
6.5.2. policy	46
6.5.3. Specifying Exceptions	46
6.6. Configuring Power Management Settings	46
6.6.1. sleepAfter	46
6.6.2. wakeAfter	46
6.7. Managing Other Settings	46
6.7.1. consolePort	46
6.7.2. domainHeaders	46
6.7.3. loghost	47
6.7.4. timeSource	47
Chapter 7. Managing Volumes	49
7.1. Volume Expiration	49
7.2. Movement Between Nodes	49
7.3. Physical Errors	49
Appendix A. Implementation of Multi-Server Chassis	51
A.1. Configuration Parameters	51
A.1.1. Processes parameter	51
A.1.2. Network Setup parameters	51
A.1.3. Using the vols parameter	52
A.1.4. Using the subcluster parameter	52
A.2. Monitoring and Administration	53
Appendix B. Using SNMP with DX Storage	54
B.1. SNMP Management Information Base (MIB) Reference	54
B.2. Managing DX Storage Nodes	54
B.2.1. Shutdown Action for Nodes	54
B.2.2. Retire Action for Nodes and Volumes	54
B.2.2.1. Single Volumes	55
B.2.2.2. Entire Node	55
B.3. SNMP Tools and Monitoring Systems	55
B.3.1. Open Source Tools	55
B.3.2. SNMP Examples with DX Storage	56
B.3.3. SNMP Action OIDs	56
B.3.3.1. castorShutdownAction	56
B.3.3.2. castorRetireAction	56
B.3.3.3. castorLogLevelAction	56
B.3.3.4. castorSyslogHostAction	56
B.3.3.5. volumeRecoverySuspend	57
B.3.4. Practical SNMP with DX Storage	57
B.3.4.1. Health Monitoring	57
B.3.4.2. Capacity Monitoring	57
B.3.4.3. Client Activity Reporting	58
Appendix C. Upgrading a License or Cluster	59
C.1. Upgrading a License File	59
C.2. Software Upgrade Overview	59
C.2.1. Preparation	59
C.2.2. Upgrade Steps	60
C.2.2.1. Example Shutdown Script	60
C.2.2.2. Cluster Reboot	60
C.3. Back-out Steps	61
Appendix D. Troubleshooting	62
D.1. Restoring Domains and Buckets	62
D.1.1. Recovering a Deleted Domain	62
D.1.2. Recovering a Deleted Bucket	65
D.2. Resolving Duplicate Domain Names in a Mirrored or Disaster Recovery (DR) Cluster	66
D.2.1. Renaming a Domain in its Source Cluster (DR Cluster Conflict Only)	66
D.2.2. Renaming a Domain in a Mirrored or DR Cluster	67
D.3. Using DX Content Router to List Buckets and Objects	69
D.4. Boot Errors	69
D.5. Configuration	70
D.6. Operational Problems	70
Appendix E. Drive Identification API	72
E.1. Overview	72
E.2. Customization Steps	72
Appendix F. Customizing the Admin Console	73

Match case Limit results 1 per page

Version 5.0

December 2010

the next step or you can remove the

Castor-Authorization

header and allow

another user to modify it.

To remove the

Castor-Authorization

header, use PUT or POST with the

admin

query argument and your credentials to upload a user realm to the object but do not

specify a

Castor-Authorization

header in the request.

3. PUT the updated

Castor-Authorization

header and user list to the object.

curl -X PUT -i --post301 -H "Castor-Authorization:

authorization-

specfication

" -H "Castor-Stream-Type: admin" --location-trusted

"http://

node-ip

bucket-name

[?domain=

domain-name

]&admin" --anyauth -u

your-username

your-password

" --data-binary @

user-list

[-D

log-file

]

You must specify

domain=

name

in a PUT for a domain. If the PUT is for a bucket, you must pass

in the domain name as the Host in the request if the domain is not the default cluster domain.

For example, suppose a bucket named

testbucket

in the domain

cluster.example.com

has

become inaccessible due to either a bad authorization specification or user list. The example that

follows shows how you can restore access by changing the

Castor-Authorization

header and

uploading a new user list. The example makes the following assumptions:

•

cluster.example.com

is the default cluster domain so it does not need to be passed in as the

Host in the request.

•

The object's

Castor-Authorization

header does

not

contain either

owner@

@owner

•

The cluster administrator uses the default user name (

admin

) and password

(

ourpwdofchoicehere)

•

Commands are sent to a node whose IP address is 172.16.0.35.

1. Create the user list.

htdigest -c cluster_example_com_testbucket cluster.example.com/

testbucket john.jones

2. PUT the new

Castor-Authorization

header and user list.

curl -i -X PUT --post301 -H "Castor-Authorization:

post=cluster.example.com/testbucket, change=cluster.example.com/

testbucket, view=cluster.example.com" -H "Castor-Stream-Type: admin" --

location-trusted "http://172.16.0.35/testbucket?admin" --data-binary

@cluster_example_com_testbucket -u "admin:ourpwdofchoicehere" -D fix-

bucket.log

3. Ask a user in the user list to confirm they have access to the object by uploading a new user list

to the object or by changing the

Castor-Authorization

header.

4.7.2. Working With Inaccessible Objects

In the event a domain, bucket, or named object is not accessible by usual means, you can access it

directly using the

cid=

query argument. Examples of when this might be useful:

•

The domain or bucket has been deleted.