Here are the first commands I’ll type when I suspect there is a problem with the Celerra, or if I want to do a simple health check.
1. <watch> /nas/sbin/getreason. This will quickly give you the current status of each data mover. 5=up, 0=down/rebooting. Typing watch before the command will run the command with continuous updates so you can monitor a datamover if you are purposely rebooting it.
10 – slot_0 primary control station
5 – slot_2 contacted
5 – slot_3 contacted
2. nas_server -list. This lists all of the datamovers and their current state. It’s a good way to quickly tell which datamovers are active and which are standby.
1=nas, 2=unused, 3=unused, 4=standby, 5=unused, 6=rdf
id type acl slot groupID state name
1 1 0 2 0 server_2
2 4 0 3 0 server_3
3. server_sysstat. This will give you a quick overview of memory and CPU utilization.
threads runnable = 6
threads blocked = 4001
threads I/J/Z = 1
memory free(kB) = 2382807
cpu idle_% = 70
4. nas_checkup. This runs a system health check.
Check Version: 220.127.116.11
Check Command: /nas/bin/nas_checkup
Check Log : /nas/log/checkup-run.110608-143203.log
Control Station: Checking if file system usage is under limit………….. Pass
Control Station: Checking if NAS Storage API is installed correctly…….. Pass
5. server_log server_2. This shows the current alert log. Alert logs are also stored in /nas/log/webui.
6. vi /nas/jserver/logs/system_log. This is the java system log.
7. vi /var/log/messages. This displays system messages.