Solution Properties
Solution ID:
242403050011918
Last Modified Date:
Sun Aug 18 21:42:12 EDT 2024
Taxonomy Path:
Support Information//Data Collection//Storage//Hitachi Content Platform
Author:
hvuser
HCP S Series Data Collection
Content

Objective

Collect logs from HCP S Series.

Environment

  • Hitachi Content Platform (HCP) S Series

Procedure

Collect HCP S Series Logs and HCP Logs Together

  1. Log into the HCP System Management Console.
  2. Navigate to Monitoring tab → Internal Logs.
    Note: For the more information on how to collect the HCP logs, refer to the article Hitachi Content Platform (HCP) Data Collection.
  3. Under "S Series Node Preparation", select the checkbox next to the desired HCP S Series device before beginning the log collection:
    090240412049649.png
  4. Click "Prepare Internal Logs".
  5. Wait for the HCP to finish collecting the logs, when HCP finishes preparing the logs, the "Prepare Internal Logs" button changes to "Download Internal Logs".
  6. Click on the "Download Internal Logs" button.
  7. When prompted, choose a location to save the log file download on your local system drive.

 

Collect HCP S Series Logs Only

  1. Login to the HCP S Series Management Console with the user that has the "Admin" role.
  2. Navigate to Monitor → Internal Logs.
  3. Select the Start date and End date and, optionally, mark the logs with a comment.
  4. Click "Prepare".
    090240412049650.png
  5. Once the logs are finished preparing, click "Download" to save them locally.
Attachments
Service Partner Notes
Employee Notes

If the HCP S Series Management Console is not available, logs for these systems can be collected manually using the logdl command in the same way as is done on HCP.  This should be run manually on both server modules, as the cluster-wide logdl script does not work on the HCP S Series.

logdl <newest-day> <number-of-days> > <output-filepath>/<server module number>.tar.xz

Example:

Collect logs for the last 7 days from SM1:

logdl 6 7 > logs_sm1_10_23_2019.tar.xz

Note: In the past, we needed to append nocrypt to the command to generate the logs.  This no longer seems to be the case and results in an error output to the filename (can be verified by doing a cat on the filename after generation). 
Old format of command:

logdl <newest-day> <number-of-days> nocrypt > <output-filepath>.tar.xz


If needed, log collection status can be viewed via the following CLI command:

admin logs state


The following values may be returned:

  • Not Started - There is no log collection in progress at this time and the GUI should show ready to generate logs
  • Preparing - Log collection script is in progress and bundling the data
  • Pending  - Log collection is complete and package is awaiting download

If the log collection is hung (indicated by GUI / CLI hang and / or error message in the GUI in addition to a status of either Preparing or Pending), you can cancel and reset it via the following CLI command:

admin logs reset

 

Support Center Notes
CXone Metadata

Tags: Data Collection,S10,Rhino,S30,HCP S Series Node,Logs,Log Collection,HCP-S

PageID: 11918