Read your server and storage logs in seconds.

Drop an HPE, Huawei, IBM or Lenovo server health log, the diagnostics of a Dell EqualLogic, HPE MSA, HPE EVA, HPE 3PAR, IBM / Lenovo Storwize or FlashSystem, or Dell EMC VNX or Unity storage array, or the supportshow of a Brocade Fibre Channel switch and get a clear, interactive report: health, events, inventory, sensors, storage, and for switches and Storwize / FlashSystem the ports, link errors and performance charts. Sign in with your free professional account; your files and reports are not kept.

Sign in to convert your logs

EveryLog is for IT professionals. Create a free account with your work e-mail address: confirm it, and an administrator approves it within 24 hours.

Sign inCreate account
Before you upload: make sure you are authorised to share this diagnostic file. It must come from equipment you own or manage, or you must have the permission of the equipment's owner (for example your customer or your employer) to have it processed by an external service. Logs can contain serial numbers, network addresses, user names and other confidential details.

By uploading a file you confirm that you are authorised to share it. Use of EveryLog is subject to the Terms of Use. See how your account and your files are handled in the Privacy notice.

Professional accounts

Accounts are for work e-mail addresses only. Each one is confirmed by e-mail and approved by an administrator, usually within 24 hours. Nothing to install.

Nothing is kept

Your file is deleted as soon as it is converted. The report is deleted when you click Delete, or automatically after 30 minutes. Download it if you want to keep it.

Isolated conversion

Each file is checked first, then converted in a sandbox with no network access and strict time and memory limits.

Supported formats

A .rar or .7z must be extracted first.

Getting EqualLogic diagnostics

  1. Collect diagnostics on the member: in Group Manager open Tools > Diagnostic reports, or run diag in the CLI.
  2. Retrieve the segment files, named like <service tag>_<member>_<date>_Seg_1.dgo to …_Seg_6.dgo, by e-mail, FTP or SCP.
  3. Select all of them at once above (or a .zip of them). Missing segments are allowed; the report says which parts are absent.

Getting HPE MSA store logs

  1. In the Storage Management Utility (SMU), choose Maintenance > Support > Collect logs (older firmware: Tools > Save Logs). Or, with FTP enabled, run get logs store.zip from an FTP client connected to a controller.
  2. You get a .zip holding store_YYYY_MM_DD__hh_mm_ss.logs and the controllers' file-system logs.
  3. Upload the .zip as it is, or only the .logs file inside it.

Getting an HPE EVA capture

  1. Collect a capture of the storage system with HP Command View EVA (P6000 Command View), the capture HPE support usually asks for.
  2. You get <user>-capture-<date>.zip (a .tar.gz on the management module) with one folder per array: EVA_config.xml, the controller event logs and the termination events.
  3. Upload the archive as it is. A capture of several arrays gives one report with an array selector.

Getting an HPE 3PAR InSplore

  1. On the Service Processor (SP or SSMC), collect an InSplore of the storage system, the diagnostic data HPE support usually asks for.
  2. You get InSplore.<system>-<serial>.<date>.tbz2 (sometimes inside a .zip): the output of about 150 CLI commands, the health checks and the event log, plus each node's own files.
  3. Upload the archive as it is, even if it is several hundred megabytes; converting it takes a few minutes. An InSplore that was cut short during a copy still gives a report of what it holds.

Getting a Huawei iBMC dump

  1. In the server's iBMC web interface, export One-Click Information Collection (under Maintenance > iBMC Logs or Diagnosis > Fault Diagnosis, depending on the version), or run ipmcget -d diaginfo on the iBMC command line.
  2. You get dump_info.tar.gz (some versions name it <model>_<serial>_<date>-<time>.tar.gz): the iBMC's inventory, sensors, event log, logs and RAID controller data.
  3. Upload it as it is. A .zip may hold several dumps: the report then has a server selector.

Getting IBM / Lenovo IMM2 service data

  1. In the server's IMM2 web interface, open Service and Support > Download Service Data and download the Service and Support Data, or run ffdc generate -t 1 on the IMM command line.
  2. You get <type-model>_<serial>_imm2_<date>_<time>.tgz: the IMM's report, event log, sensor readings, inventory (processors, memory, RAID and disks) and logs. The event log alone can also be saved from Events > Event Log as an .elg file.
  3. Upload it as it is. A .zip may hold several: the report then has a server selector.

Getting a Brocade supportshow

  1. Open an SSH session to the switch with session logging on (PuTTY: Session > Logging > All session output; MobaXterm and SecureCRT have the same option), sign in and run supportshow. Let it finish (one to ten minutes, until the prompt is back).
  2. Upload the log as it is: 2 to 25 MB of text, any name. The terminal's banner, the login and other commands around it are ignored. The report checks every optic against Brocade's MAPS limits for its type and speed, and shows errors, throughput, peak use and slow-drain signs per port.
  3. Put several captures in one .zip for more: the switches of a fabric give a switch selector and the link loss of the ISLs between them; one switch captured hours or days apart gives a Trend tab with the errors, traffic and optic power of that window. A .rar or .7z must be extracted first.

Getting a Storwize / FlashSystem snap

  1. In the management GUI open Settings > Support > Support Package (older code: Download Support Package), choose Standard logs plus new statesaves or the type support asked for, and download it. From the CLI: svc_snap gui3, then copy /dumps/snap.*.tgz off the configuration node.
  2. Upload snap.<panel>.<date>.<time>.tgz as it is (5 to 250 MB); the partner nodes' snaps inside it are read too. The report shows the findings, unfixed alerts, nodes, enclosures and a drive-slot map, the parts inventory, pools, volumes, hosts and their paths, ports and link errors, and performance charts (IOPS, throughput and response time per volume, MDisk and drive, CPU, write cache, port traffic).
  3. Put several snaps in one .zip for more (several systems, or one system on several days). A snap.single.*.tgz of a node in service state shows its node errors, hardware and dumps.

Getting a VNX SPcollect or Unity service data

  1. VNX: in Unisphere, System > Diagnostic Files: Generate Diagnostic Files for SP A and for SP B, then Get Diagnostic Files and download each SP's newest <serial>_SPA_<date>_data.zip / _SPB_. CLI: naviseccli -h <SP> spcollect, then managefiles -list and managefiles -retrieve.
  2. Unity: in Unisphere, Service > Service Tasks > Collect Service Information, then download Unity_<model>_service_data_<serial>_<date>.tar. It holds both SPs; either spa / spb.service_dc.tgz can also be uploaded on its own.
  3. Take both SPs (select both files together): each SP sees the drives through its own back-end path and keeps its own error counters, reboots, panics, BMC log and boot SSD (on a VNX also its own event log). One SP still gives a full report, and it says what the other would add. The report shows failing and worn disks on an enclosure map, batteries and write cache, pools and LUNs, each SP's reboots and BMC log, and the event log on a timeline.

Getting IBM / Lenovo DSA output

  1. Run the portable Dynamic System Analysis for the server (lnvgy_utl_dsa_* or ibm_utl_dsa_*) on Windows or Linux, or DSA Preboot (F2 at start-up). With no options it collects everything.
  2. DSA writes <type-model>_<serial>_<date>-<time>.xml.gz in C:\IBM_Support or /var/log/IBM_Support: inventory, RAID (storcli), sensors, the IMM event log and SEL, and the operating system's logs.
  3. Upload it as it is. A .zip may hold several: the report then has a server selector. If DSA stopped before writing it, a .zip of the IBM_Support folder shows DSA's run logs.