System information

VNX™ System Operations106 of 114 Release 7.0
Recovery after an VNX SP failure
If a storage processor (SP) panics (software failure) or must be removed and
replaced (hardware failure), perform the following to get the SP back online after it
restarts:
1. Determine if an SP failed over by using the following CLI command:
nas_storage -info -id=<storage_id>
If an SP failed over, its disk volumes were transferred to the other SP.
2. Transfer the disk volumes back to the default (owning) SP by using the
command:
nas_storage -failback -id=<storage_id>
3. After the SP is backed up, restart any Data Mover or blade that restarted while
the SP was down.
A Data Mover or blade that restarts while one SP is down runs with only a single
I/O path, even after both SPs are up again. If this single I/O path fails, the Data
Mover or blade panics. This step avoids a Data Mover or blade panic and
maintains the server’s high-availability operation.
Monitor system activity
Table 13 on page 106 describes various statistical outputs to help you monitor
system activity.
server_stats
server_stats provides real-time statistics for the specified Data Mover. Statistics are
displayed in a time-series fashion at the end of each interval. The statistics are
organized as a hierarchy of families that replaces the summary and table
collections. Previously defined summary and table collections have been converted
Table 13 System activity monitoring
Type of display Output Command line
Protocol Packet statistics and
connection statuses
server_netstat <movername> -s
-p { tcp|udp|icmp|ip }
Routing table Routing table statistics
server_netstat <movername> -r
Interface Specific interface statistics
server_netstat <movername> -i
Active connections TCP or UDP connections
server_netstat <movername>
-p { tcp|udp }
System Threads information, memory
status, and CPU state
server_sysstat <movername>