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


Dell EqualLogic CLI Undocumented Support Commands

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.


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.


EqualLogic PS Series Firmware update using the CLI

After our EqualLogic PS6000 decided to go into a NetBSD Kernel Panic (crash) while performing a firmware update from version 5.1.1 to 5.1.2 using the Group Manager GUI, resulting in a firmware mismatch on our controllers, As advised by EqualLogic Tech support I performed another update to FW 5.1.2 using the CLI, with success.

Using the CLI has its advantages, altough the process is a little more involved, ie copying the firmware to the array member using FTP then SHH to the member to execute the update, you do get to see what happens during a firmware update in more detail.

Here is the process of performing a Firmware update using the CLI.

I will be using winscp to copy the firmware TGZ file to the group member, winscp can be downloaded here, and PuTTY a free Telnet/SSH client which can be found here.

Firstly download the firmware from EqualLogic Support

Lets update the firmware.


Dell PowerConnect 5400 Switch config for EqualLogic iSCSI Network

At this current moment we use 2 PowerConnect 5424 switches for our iSCSI backend network.  The PowerConnect 5424 has 24 10/100/1000 BASE-T auto-sensing gigabit Ethernet switching ports and 4 SFP combo ports for fibre connectivity.

The PowerConnect series of switches have many good features some which are irrelevant to what I am talking about so I will leave this out and comment on the features which are important in relation to iSCSI backend networks. Notice I say backend, if this were not a backend network I may be interested in some of the other features such as multiple VLAN capability and iSCSI optimization and QOS. But as this is a backend network I will not require the use of multiple VLANS or iSCSI optimization as I don't see the need to optimise iSCSI on purely iSCSI network.

Get Adobe Flash player