Recently I have done a couple of posts on the EqualLogic CLI, updating firmware and collecting log informaiton. Well in my travels I came across the fact that EqualLogic is NetBSD underneath the pretty exterior, with this in mind I started doing a little digging around with the mentality that there must be some information you can extract form your EqualLogic using standard NetBSD commands, afterall it is just a BASH shell!
take a look over here at what I found - Undocumented EqualLogic CLI commands
Please be mindful that entering the support layer of an EqualLogic is not supported in a normal situation by EqualLogic as stated in the message you will recieve upon entering.
"You are running a support command, which is normally restricted to PS Series Technical Support personnel. Do not use a support command without instruction from Technical Support."
I would only recommend using the support command in a test/development environment or unless you really know what you are doing.
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.