726 Implementing the IBM Storwize V7000 with IBM Spectrum Virtualize V8.2.1
(build 13.4.1709291021000)#FRU=fan 31P1847 
#AdditionalData(0->63)=00000000460000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000#Additional
Data(64-127)=000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000
13.8  Audit log
The audit log is useful when analyzing past configuration events, especially when trying to 
determine, for example, how a volume ended up being shared by two hosts, or why the 
volume was overwritten. The audit log is also included in the svc_snap support data to aid in 
problem determination.
The audit log tracks action commands that are issued through a Secure Shell (SSH) session, 
management GUI, or Remote Support Assistance. It provides the following entries:
/SM590000Identity of the user who issued the action command
/SM590000Name of the actionable command
/SM590000Time stamp of when the actionable command was issued on the configuration node
/SM590000Parameters that were issued with the actionable command
The following items are not documented in the audit log:
/SM590000Commands that fail are not logged.
/SM590000A result code of 0 (success) or 1 (success in progress) is not logged.
/SM590000Result object ID of node type (for the addnode command) is not logged.
/SM590000Views are not logged.
Several specific service commands are not included in the audit log:
/SM590000dumpconfig 
/SM590000cpdumps 
/SM590000cleardumps 
/SM590000finderr 
/SM590000dumperrlog 
/SM590000dumpintervallog 
/SM590000svcservicetak dumperrlog 
/SM590000svcservicetask finderr 
Figure 13-65 shows the access to the audit log. Click Audit Log in the left menu to see which 
configuration CLI commands were run on IBM Storwize V7000 system.
Figure 13-65   Audit Log from Access menu