Interweb Blog Hyper-V, App-V, Dell Equallogic, Forefront TMG Security, DPM 2010, SCVMM


EqualLogic PS Series Array – Gathering Diagnostic Logs using CLI

When calling EqualLogic Technical support with any isue's (as in my recent case a failed disk), you will more than likely be asked to gather diagnostic logs from the array and send them across for further investigation.  This is normally the process before any parts are dispatched.  In anticipation of this I generally gather the diagnostic log files in the form of .dgo from the EqualLogic I am having an issue with prior to calling.

There are a couple of different ways that log files can be generated,  using SANHQ (note this must be version 4.x or above) or via the command line interface.  The diagnostic process gathers internal state and configuration data from the array, encodes the data and then segments this data for transmission, the files are formatted "Seg_1.dgo - Seg_2.dgo" etc.  At this point I think it is important to point out that the log file data does not include any user data, from the volumes nor the cache or any Group account passwords or access information.

To gather the logs via the CLI, you will need to SSH to the EqualLogic Array, I use puTTY for this and login using a user account with group administration rights, 'grpadmin'grpadmin.




Once you have logged in the 'diag' command will be used to gather the log files.   If you have snapshot or replication schedules and they occur while you are logged in via CLI you will see output to the screen ' MgmtExec' this is purely informational, carry on as normal it does not intertrupt gathering the diagnostic logs.


diag command


After gathering the log information, the EqualLogic Array will attempt to send them via E-Mail if you have this configured, you also have the option of outputting to a text file,  in my experience Tech support prefer the .dgo files, probably because they can easily feed these into a log analyzer and get some actual information out.

Final Steps

Final Steps


Once the .dgo files have been generated you can now use WinSCP or another FTP client of your choice to copy the logs from the EqualLogic Array.

winscp login

winscp login


Now that you have logged in via FTP using a Group Admin account, you will be able to see that the Seg_1.dgo and corresponding Segments have been output to the root of the EqualLogic.  Right click a .dgo file and copy it to your local machine.

EqualLogic Root

EqualLogic Root





Once copied to you local machine, you are free to do as you wish.  Remember that your FTP client will need to be in Binary mode to be able to copy the .dgo files as these can be quite large from the EqualLogic Array, this is why I like WinSCP.  WinSCP has an automatic preset called a  'Text File Mask' for transfer modes, By default HTML, TXT, PHP, XML, INI, C, CPP amongst others are set for 'Text Mode' with any other extension not matching the mask such as .dgo being set for 'Binary mode'.





    Comments (2) Trackbacks (0)
    1. Hi,

      Do you know how can I read the diagnostic files? I exported but dont know how to read them.

    2. The Seg_X.dgo files are Base64 and you can read the header of each with a conversion tool like
      Which in torn tells you what text file from the EqualLogic it came from.

      Seg_1.dgo says:
      Report.txt?-rw-r–r– 1 root wheel 440343 Jan 4 15:25:30 2017 /mgtdb/update/Seg_Tmp1.dgo

      Seg_2.dgo says:
      filterSettings.txt?Current eqllog filter settings from member SQLSAN

      Seg_3.dgo says:
      eqllogmgr-Output.txt?Output of “eqllogmgr -r” from member SQLSAN

      Seg_4.dgo says:
      volumePageMaps.txt?Volume pagemaps from member SQLSAN

      Seg_5.dgo says:
      TransLog.bin?Dump of /dev/lv1 from member SQLSAN

      Seg_6.dgo says:
      SNMPWalk.txt?SNMPWALK output from member SQLSAN

    Leave a comment

    No trackbacks yet.

    Get Adobe Flash player