Hitachi NAS (HNAS) Platform Data Collection

Performance problems

A performance problem is where the HNAS is perceived to be responding slowly or not at all:

• What Information Do I Need to Gather to Allow GSC to Diagnose an HNAS Performance Problem
• What Information Do I Need to Gather to Allow GSC to Diagnose a Hung HNAS System
• HNAS Performance Issues Questionnaire
• How to Collect and Download a HNAS Performance Information Report or PIR
• How To Collect a PIR If HNAS Is Not Configured to Send via Email
• HNAS Data Migrator to Cloud Performance Issue

Security permissions problems

Problems with files not being accessible or being too accessible etc:

• What Information Do I Need to Gather to Allow GSC to Diagnose a HNAS Security Permissions Issue

Heap memory issues

Heap memory related events/issues may include:

• Failed to allocate panics ("start of "FailedToAllocate" panic"),
• Heap fragmentation ("No big free heap blocks left"),
• Heap related enforced limits:
  • Insufficient free heap:
    • "There is insufficient heap: dropping new connection from"
    • "There is insufficient heap: dropping additional connection request from"
  • Insufficient free heap in big sized heap blocks:
    • "There is insufficient heap: dropping new connection from"
    • "There is insufficient heap: dropping additional connection request from"

• What Information Do I Need to Gather to Allow GSC to Diagnose Heap Issues on HNAS

File (NDMP) replication problems

Please refer to the following knowledgebase article for the information required to investigate HNAS file (NDMP) replication problems:

• What Information Do I Need to Gather to Allow GSC to Diagnose HNAS File Replication Issues

HNAS resets / HNAS "boot loops"

If a customer (or Remote Ops (Hi-Track)) reports a HNAS reset then you usually just need HNAS managed server diagnostics from after the reset.  If the server has been restarted since the reset then the diagnostics for the reset will no-longer be in the last_dblog.txt.  In that case you will need to ask the customer to get historical logs.

A boot loop is when the HNAS seems to be continually rebooting without any intervention:

• What Information Do I Need to Gather to Allow GSC to Diagnose a HNAS Boot Loop

Historical logs collection

Collection of historical logs is not usually required but in some cases, a support engineer may request this to investigate further:

• How To Collect Historical Logs from HNAS

Collect SMU diagnostics from SMU using command line

If for some reason you cannot collect SMU diagnostics from the SMU GUI it is possible to collect them from the SMU command line as follows:

• How To Collect HNAS System Management Unit SMU Logs Using Command Line Interface CLI

Packet capture of network traffic

We often need packet captures of network traffic in order to progress HNAS issues.  The following articles provide advice and guidance on how to go about collecting those:

• How to Collect Packet Captures for Troubleshooting HNAS Problems