Check 3PAR event log using CLI

Most of the time system administrators have to deal with system failures and troubleshooting issues related to hardware and software bugs, the same applies to 3PAR as well. When we deal with system events and other logs, we will be relying on CLI commands rather than GUI tools. CLI commands are easy to dig in and it gives you a better option to capture the logs using PuTTy or any SSH tools which has log capturing feature.

Most of the time we will be using 3PAR insplore(SPOCC) logs and we wait for the feedback from HP back-line support. But how can we check the logs and see what all things are happening in the system? Lets see the command and its usage and options.

To see 3PAR system event log, login to CLI and run the "showeventlog" command. The command is not interactive and it will scroll the screen till it reaches the end of the log file. Let's see the options and different attributes which we can use with this command.

SYNTAX

    showeventlog [options ]

OPTIONS:-

-oneline        if you use this option with the command, each event is formatted as one line.

Eg:-

3parLab cli% showeventlog  -oneline
2015-06-30 00:01:42 EST        2 Informational   Object added    sw_vv:1520:rcpy.46.911.2 Virtual Volume 1520(rcpy.46.911.2) added
2015-06-30 00:01:42 EST        2 Informational   Object added    sw_vv:1521:rcpy.46.912.2 Virtual Volume 1521(rcpy.46.912.2) added
2015-06-30 00:01:42 EST        2 Informational   Object added    sw_vv:1522:rcpy.46.916.2 Virtual Volume 1522(rcpy.46.916.2) added
2015-06-30 00:01:42 EST        2 Informational   Object added    sw_vv:1523:rcpy.46.5286.2 Virtual Volume 1523(rcpy.46.5286.2) added

Output truncated!
-startt < time >        When this option is used, only events after a specified time are to be shown. The
        time argument can be specified as either < timespec >, < datespec >, or both.

< timespec >           Specified as the hour (hh), as interpreted on a 24 hour clock, where minutes (mm) and seconds (ss) can be optionally specified.

 < datespec >           Specified as the month (mm or month_name) and day (dd), where the year (yy) can be optionally specified. Acceptable formats are mm/dd/yy, month_name dd, dd month_name yy, or yy-mm-dd.

-endt < time >        When this option is used logs will be captured till the mentioned date or time. the attributes are similar to -startt.

Eg:-

3parLab cli% showeventlog -startt 06/30/15 -endt 07/01/15

2015-06-30 00:04:08 EST        2 Informational   Object added    sw_vv:1524:rcpy.32.871.2 Virtual Volume 1524(rcpy.32.871.2) added
2015-06-30 00:04:08 EST        2 Informational   Object added    sw_vv:1525:rcpy.32.872.2 Virtual Volume 1525(rcpy.32.872.2) added
2015-06-30 00:04:08 EST        2 Informational   Object added    sw_vv:1526:rcpy.32.9513.2 Virtual Volume 1526(rcpy.32.9513.2) added
2015-06-30 00:04:08 EST        2 Informational   Object added    sw_vv:1527:rcpy.32.9551.2 Virtual Volume 1527(rcpy.32.9551.2) added
2015-06-30 00:04:08 EST        2 Informational   Object added    sw_vv:1528:rcpy.32.9560.2 Virtual Volume 1528(rcpy.32.9560.2) added
2015-06-30 00:04:08 EST        2 Informational   Object added    sw_vv:1529:rcpy.32.9573.2 Virtual Volume 1529(rcpy.32.9573.2) added

-d  when this option is used, detailed information about the event is displayed.

Eg:-

3parLab cli% showeventlog -startt 06/30/15 -endt 07/01/15 -d
Time     : 2015-06-30 00:00:00.83 EST
Node     : 2
Seq      : 74655932
Class    : Addition to configuration
Severity : Informational
Type     : Object added
Component: sw_task:4018
Message  : Task 4018 added
Time     : 2015-06-30 00:00:01.08 EST
Node     : 1
Seq      : 15401656
Class    : Notification
Severity : Informational
Type     : CLI command executed
Component: sw_cli

Above mentioned are the most common options which we will be using in most of the time. There are additional options available with the command. You may try help showeventlog from command line.