Dell DX6004S DX Object Storage Administration Guide - Page 56
B.3.2. SNMP Examples with DX Storage, B.3.3. SNMP Action OIDs, B.3.3.1. castorShutdownAction
View all Dell DX6004S manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 56 highlights
B.3.2. SNMP Examples with DX Storage The following example shows an SNMP walk of all the DX Storage values on a node. snmpwalk -v 2c -c pwd -m +CASTOR-MIB 192.168.1.101 caringo The following example shows the request of a specific SNMP variable from a DX Storage node. snmpget -v 2c -c pwd -m +CASTOR-MIB 192.168.1.101 caringo.castor.scsp.reads The following example shows a set request that will shutdown a DX Storage node. snmpset -v 2c -c pwd -m +CASTOR-MIB 192.168.1.101 caringo.castor.castorShutdownAction = "shutdown" The following example shows a set request that will retire the volume "/dev/sda". snmpset -v 2c -c pwd -m +CASTOR-MIB 192.168.1.101 caringo.castor.castorRetireAction = "/dev/sda" B.3.3. SNMP Action OIDs The "action" OIDs in DX Storage are the SNMP objects that can be written to in order to affect the operation of a node or the cluster. To prevent conflicts for cluster level parameters like volumeRecoverySuspend, the action should only be written to a single node, allowing updates to the persisted settings UUID from a single node. B.3.3.1. castorShutdownAction Writing to this object allows for the graceful shutdown or reboot of a node or and entire cluster. Value values are: • "shutdown" - shuts down this node only • "reboot" - reboots this node only • "clustershutdown" - shuts down all nodes in the cluster • "clusterreboot" - reboots all nodes in the cluster B.3.3.2. castorRetireAction Writing to this object allows for the orderly removal of the contents of a disk volume or an entire node. It is important to retire disks in case they contain the only copies of content. The device name, from the vols parameter of the node configuration, or the string "all" is written to this OID. You may simultaneously retire volumes from multiple nodes in the cluster. B.3.3.3. castorLogLevelAction Writing to this object allows the logging level to be changed. When a node is booted, it sets the logging level based on the loglevel parameter. An administrator may wish to increase the logging level in order to debug an issue and then return the level it to its previous value when finished. B.3.3.4. castorSyslogHostAction Writing to this object allows an administrator to change the location to which log messages are written. When a node is booted, it sets the logging host based on the loghost parameter. It may be desirable to redirect syslog messages to an administrator's workstation in order to debug an issue. Copyright © 2010 Caringo, Inc. All rights reserved 51 Version 5.0 December 2010