Dell DX6004S DX Object Storage Administration Guide - Page 71

Symptom, Resolution, Managing DX, Storage Administrators and Users

Page 71 highlights

Symptom 3. You have read-only access to the Admin Console even though you are a member of the Castor administrators realm, or you cannot view the Admin Console. Resolution You added an operator (that is, a read-only user) to the Castor operators realm but did not add your administrator user name and password to the Castor operators realm. Failure to do so prevents you, an administrator, from properly accessing the Admin Console. To resolve this issue, add all of your administrator users to the operators parameter in the node or cluster configuration file as discussed in Section 6.2, "Managing DX Storage Administrators and Users". 4. A node has become unresponsive to network requests. Please be sure that your client network settings are correct and that the node has really become unresponsive before taking the next steps. This can be done by pinging the node and trying to display the web console (ie. http://192.168.3.200:90). 5. Network never becomes connected on a node with multiple network interface ports. 6. A node is rebooting itself. If you have a keyboard that can be attached to the system, you may hit Ctrl-Alt-Del in order to attempt a graceful shutdown. Otherwise, hit the hardware reset button or power cycle the node. Check that the network cable is plugged into the correct NIC. Depending upon the bus order and the order in which kernel drivers are loaded, the network ports may not match their external labeling. If the electrical power is constant and the hardware is functioning properly, this may indicate a software problem. The DX Storage system has a built-in failsafe and will reboot itself if something goes wrong. You should contact Caringo support. Copyright © 2010 Caringo, Inc. All rights reserved 66 Version 5.0 December 2010

  • 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
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74

Copyright © 2010 Caringo, Inc.
All rights reserved
66
Version 5.0
December 2010
Symptom
Resolution
3. You have read-only access to the Admin
Console even though you are a member of
the
Castor administrators
realm, or
you cannot view the Admin Console.
You added an operator (that is, a read-only
user) to the
Castor operators
realm but
did not add your administrator user name and
password to the
Castor operators
realm.
Failure to do so prevents you, an administrator,
from properly accessing the Admin Console.
To resolve this issue, add all of your
administrator users to the
operators
parameter in the node or cluster configuration
file as discussed in
Section 6.2, “Managing DX
Storage Administrators and Users”
.
4. A node has become unresponsive to network
requests.
Please be sure that your client network settings
are correct and that the node has really
become unresponsive before taking the next
steps. This can be done by pinging the node
and trying to display the web console (ie.
If you have a keyboard that can be attached to
the system, you may hit Ctrl-Alt-Del in order to
attempt a graceful shutdown. Otherwise, hit the
hardware reset button or power cycle the node.
5. Network never becomes connected on a
node with multiple network interface ports.
Check that the network cable is plugged into
the correct NIC. Depending upon the bus
order and the order in which kernel drivers are
loaded, the network ports may not match their
external labeling.
6. A node is rebooting itself.
If the electrical power is constant and the
hardware is functioning properly, this may
indicate a software problem. The DX Storage
system has a built-in failsafe and will reboot
itself if something goes wrong. You should
contact Caringo support.