Open Networking Hardware Diagnostic Guide September 2017
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. Copyright © 2017 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents 1 About this guide............................................................................................................................................. 7 Notices.................................................................................................................................................................................7 Related documents..........................................................................................................................................
Configuration file format............................................................................................................................................ 31 ethtool................................................................................................................................................................................ 31 fantool.....................................................................................................................................................
Tests............................................................................................................................................................................ 50 CLI options..................................................................................................................................................................50 nvramtool..................................................................................................................................................
bonnie++..................................................................................................................................................................... 86 temptool............................................................................................................................................................................ 86 Tests..................................................................................................................................................
1 About this guide This guide provides site preparation recommendations, step-by-step procedures for rack mounting and desk mounting, inserting optional modules, and connecting to a power source. Notices CAUTION: To avoid electrostatic discharge (ESD) damage, wear grounding wrist straps when handling this equipment. WARNING: Only trained and qualified personnel can install this equipment. Read this guide before you install and power up this equipment. This equipment contains two power cords.
2 ONIE and Dell EMC OS installation instructions This section describes the different methods to install ONIE and the Dell EMC OS on your system. NOTE: After installing the NOS and DIAG-OS, if you boot into ONIE Install mode, ONIE assumes ownership of the system; ONIE Install mode is sticky. In this situation, ONIE stays in Install mode until NOS and Diag-OS is successfully installed again. If you want to boot into ONIE for any reason other than installation, use Rescue mode or Update mode.
ONIE and DIAG OS installation The following steps describe how to load ONIE and DIAG-OS on your system: • • • Installing ONIE—these instructions use the universal serial bus (USB) method. To boot from a Linux USB, you must preinstall BIOS on your system. Installing the DIAG-OS—Install the DIAG-OS from the ONIE prompt. Ensure that your TFTP server is reachable over your network. ONIE operates using a 115200 baud rate.
PING n.n.n.n (n.n.n.n): 56 data bytes 64 bytes from n.n.n.n: seq=0 ttl=62 time=1.357 ms 64 bytes from n.n.n.n: seq=1 ttl=62 time=0.577 ms ^C Installation ONIE from BIOS There are two options for installing ONIE from the BIOS.
3 Copy the ONIE ISO image to the solid-state drive (SSD) of the ONIE target. ONIE:/ # wget --quiet http://xx.xx.x.xxx/tftpboot/users//onie-recovery-x86_64dell__c2538-r0.iso To copy the image, you can use SCP, TFTP, or WGET (ftp/http). scp username@xx.xx.xxx.xxx:/tftpboot/onie-recovery-x86_64-dell__c2538-r0.iso . 4 Confirm that the ISO file copied to the SDD over the network. ONIE:/ # ls -l … -rw-r--r-- 1 root 0 39780352 Apr 10 11:55 onie-recovery-x86_64-dell__c2538-r0.
Figure 2. Setup utility After exiting the BIOS Boot menu, the system boots with the ONIE USB and presents the following menu: Figure 3. Embed ONIE menu 10 Select the Embed ONIE option. This step installs the UEFI ONIE version 3.26.1.1 on system. Any previous installation is removed. Do not press any key during the Embed ONIE installation. The following are the Embed ONIE logs: ONIE: Embedding ONIE ... Platform : x86_64-dell__c2538-r0 Version : x.xx.x.x Build Date: 2016-04-26T09:14-0700 [ 4.
[ 14.463587] mtdoops: mtd device (mtddev=name/number) must be supplied [ 16.328319] i8042: No controller found [ 16.397853] fmc_write_eeprom fake-design-for-testing-f001: fmc_write_eeprom: no busid passed, refusing all cards [ 16.568122] intel_rapl: driver does not support CPU family 6 model 77 Info: Mounting kernel filesystems... done. Info: Mounting ONIE-BOOT on /mnt/onie-boot ... Info: Using eth0 MAC address: 4c:76:25:f4:7c:80 Info: eth0: Checking link... [ 18.
Figure 4. ONIE install menu The system comes up in ONIE Install mode by default, as shown: ONIE: OS Install Mode ... Version : x.xx.x.x Build Date: 2016-04-26T09:14-0700 ONIE: OS Install Mode ... Version : x.xx.x.x Build Date: 2016-04-26T09:14-0700 [ 4.759116] dummy-irq: no IRQ given. Use irq=N [ 4.835970] esas2r: driver will not be loaded because no ATTO esas2r devices were found [ 5.003050] mtdoops: mtd device (mtddev=name/number) must be supplied [ 6.867708] i8042: No controller found [ 6.
http://xx.xx.xxx.x/onie-installer-x86_64-dell__c2538-r0 ... Info: Fetching http://xx.xx.xxx.x/onie-installer-x86_64-dell__c2538 ... Info: Fetching http://xx.xx.xxx.x/onie-installer-dell__c2538 ... Info: Fetching http://xx.xx.xxx.x/onie-installer-x86_64 ... Info: Fetching http://xx.xx.xxx.x/onie-installer ... Info: Fetching http://xx.xx.xxx.x/onie-installer-x86_64-dell__c2538-r0 ... Info: Fetching http://xx.xx.xxx.x/onie-installer-x86_64-dell__c2538 ...
3 ONIE overview This chapter describes system diagnostics and troubleshooting. After running the diagnostic tools, your system displays pass or fail test results. If all tests pass, the diagnostic tools exit normally. If a test fails, each diagnostic tool offers a different result. NOTE: The troubleshooting package includes a README file that lists the tools version and the overall troubleshooting package version. For more information, see this README file. NOTE: To download the Release Notes, go to www.
• log/messages • log/onie.log Output example Success: Support tarball created: /tmp/onie-support.tar.bz2 Change default grub boot entry To view or set the default Boot mode, the onie-boot-mode command has two options —l, the default, and —o. The Grub boot default shows the current default entry. View or set the default Grub boot entry.
CRC-32 Checksum is valid. ONIE:/ # 3 0xFE 4 0x99415608 Enter the onie-sysinfo –a command. Command Example ONIE:/ # onie-sysinfo -a CN0W1K08779316470002 0W1K08 34:17:EB:05:B4:00 3.28.1.
4 Dell EMC DIAG OS The following describes the Dell EMC diagnostics. These instructions apply to systems for which the ONIE diagnostics are not available. Topics: • Diagnostic package download • View DIAG versions • View CPLD versions • Install or upgrade DIAG tools • Restore factory defaults Diagnostic package download Load or update the DIAG-OS (diag installer image) using the onie-nos-install command in ONIE Install or ONIE-Rescue mode.
Stopping: discover... done. Info: Fetching tftp:///users///diag-installer-x86_64dell__c2538-r0-2016-08-12.bin ... users// 100% |*******************************| 154M 0:00:00 ETA ONIE: Executing installer: tftp:///users///diag-installerx86_64-dell__c2538-r0-2016-08-12.bin Ignoring Verifying image checksum ... OK. cur_dir / archive_path /var/tmp/installer tmp_dir /tmp/tmp.qlnVIY Preparing image archive ...
Primary BIOS Version x.xx.x.x_MRC48 SMF Version: MSS 1.3.1, FPGA 0.3 Last POR=0x11, Reset Cause=0x55 POST Configuration CPU Signature 406D8 CPU FamilyID=6, Model=4D, SteppingId=8, Processor=0 Microcode Revision 125 Platform ID: 0x10041A43 PMG_CST_CFG_CTL: 0x40006 BBL_CR_CTL3: 0x7E2801FF Misc EN: 0x840081 Gen PM Con1: 0x203808 Therm Status: 0x884C0000 POST Control=0xEA000100, Status=0xE6000000 BIOS initializations... CPGC Memtest ................................ PASS CPGC Memtest ............................
a b c d Boot into the DIAG OS. Log in as root. Install the EDA-DIAG tools package. Run /opt/dell/diag/bin/edatool. NOTE: To return to your networking operating software, enter the reboot command. Diagnostic test suite After the system boots up, select the EDA-DIAG option to run the diagnostic test suite. NOTE: To select which entry is highlighted, use the up and down arrow keys. Press Enter to select an operating softwareselected OS or enter e to edit the commands before booting.
Restore factory defaults To restore your system factory defaults, reboot the system to ONIE: Uninstall OS mode. If it is not possible to restore your factory defaults with the installed OS, reboot the system from the Grub menu and select ONIE: Rescue. ONIE Rescue bypasses the installed OS and boots the system into ONIE until you reboot the system. After ONIE Rescue completes, the system resets and boots to the ONIE console.
5 Dell EMC DiagOS tools This section describes how to use the Dell EMC diagnostics operating system (DiagOS). The DiagOS provides a suite of tools to help diagnose issues seen on the system, or to run a health check to ensure that the hardware is operating properly. Diagnostic tools The DiagOS uses standard Linux drivers and contains the following tools you can use to evaluate the health of your system.
cpldupgradetool The cpldupgradetool shows the CPLD version that is being used to upgrade the CPLD. Tests There are no defined tests with cpldupgradetool. CLI options root@dellemc-diag-os:~# cpldupgradetool DellEmc Diag - CPLD Upgrade Tool version 1.1, x.xx.x.
CPLD1 Version 0x00 CPLD2 Version 0x01 CPLD3 Version 0x01 CPLD4 Version 0x01 root@dell-diag-os:/# root@dell-diag-os:cpldupgradetool--write --image=_cpld_v01.vme Lattice Semiconductor Corp. ispVME(tm) V12.2 Copyright 1998-2011.
Read the specified regiser in LPC bus:= cputool --readlpc --reg= --size= cputool -d -R -Z Write the specified regiser in LPC bus:= cputool --writelpc --reg= --val= --size= cputool -W -R -V -Z Usage:= -h, -i, -x, -r, -w, -n, -R, -V, -Z, -I, -d, -W, --h --cpuid --x86info --readmsr --writemsr --cpu= --reg= --val= --size= --iteration= --readlpc --writelpc (or) (or) Show the help text CPU-Id x86 info Read operation Write operation CPU Register Val
Extended Family: 0 Extended Model: 4 Family: 6 Model: 77 Stepping: 8 Type: 0 (Original OEM) CPU Model (x86info's best guess): Unknown model. Processor name string (BIOS programmed): Intel(R) Atom(TM) CPU C2538 @ 2.40GHz Total processor threads: 4 This system has 1 dual-core processor with hyper-threading (2 threads per core) running at an estimated 2.40GHz root@dell-diag-os:/# Configuration file format There is no configuration file associated with the cputool.
Set a TLV code to a value:= eepromtool --eeprom= --set =,=...(or) eepromtool -P -s =,=...
151117 ************PSU1_SerialNo************* Registers 0x25f - 0x262 01CG ************PSU1_ServiceTag************* Registers 0x263 - 0x269 ************PSU1_LabelRevision************* Registers 0x26a - 0x26c A00 ************PSU2_CountryCode************* Registers 0x283 - 0x284 CN ************PSU2_DellPartNumber************* Registers 0x285 - 0x28a 02RPHX ************PSU2_MfgID************* Registers 0x28b - 0x28f 17972 ************PSU2_MfgDate************* Registers 0x290 - 0x297 151117 ************PSU2_Ser
Total Length: 6 TLV Name Code Len Value -------------------- ---- --- ----CRC-32 0xFE 4 0xD4431C18 Checksum is valid. root@dell-diag-os:/opt/ngos/bin# Configuration file format The eeprom devices display under the corresponding i2c bus number. Whenever you add a new EEPROM to the bus number, the number of devices in each bus number updates. Each eeprom field is separated by the ‘|’ character. The order of the fields is: 1 Name of the EEPROM. Provides the same name at the eeprom option in the eepromtool.
Tests The fantool tests the fans by setting them to different speeds and then verifying the configured fan speeds. Registers and values are passed as hexadecimal values with or without the preceding 0x. Fans display from 1 to Max System Fans. CLI options DellEmc Diag - Fan Controller Tool version 1.5, x.xx.x.
angle brackets are required but have multiple options for the input. Do not type the angle brackets or the vertical line character in the CLI. Only use one option per command; for example, --fan=1 or --fan=all. • test — Runs through the speeds for the fan, from highest to lowest, and checks that the fan can run at the speeds of the test. If a single fan is listed on the CLI, that fan is tested. If you use the all option, all fans are tested.
Getting Details for Fan 9 Fan 9 is Present Fan 9 Air flow type is Front To Rear Fan 9 status Normal Fan 9 speed is 8420 RPM Getting Details for Fan 10 Fan 10 is Present Fan 10 Air flow type is Front To Rear Fan 10 status Normal Fan 10 speed is 8566 RPM Fan Controller Test LPC.........................
R - Register description Offset of Register Size in bytes Register Name The example output shows MUX information when accessing the LPC and the timeout value.
gpiotool --iteration=max/ [option1] [option2]... (or) gpiotool -I max/ [option1] [option2]...
Configuration file format GPIOs are separated into groups within the configuration file, such as Core GPIOs and Suspend GPIOs (if they use different power wells for sleep operations). Any line starting with a # is a comment. ===== is the separator between groups. A group starts with a header using | separators and: • # of bits defined in the GPIO interface (a hardware definition, not the number of bits being defined in the config file.) • A name for the bit group, such as Core GPIO or SUS GPIO.
CLI options DellEmc Diag - I2C Tool version 1.5, x.xx.x.x-x build, 2017/05/23, Syntax: i2ctool
Output NOTE: The i2ctool does not automatically scan multiple MUXed segments. Before scanning, you MUST set the MUXes to select the devices you want to see on the busses. By default, the i2ctool scans the i2c devices from the root MUX where it sees the list of devices directly connected to the CPU MUX. The default scan function scans all connected busses. By specifying a bus, you can limit the scan to one bus.
+ Checking SFP+ 9 0x50 ..... + Checking SFP+ 10 0x50 ..... + Checking SFP+ 11 0x50 ..... + Checking SFP+ 12 0x50 ..... + Checking SFP+ 13 0x50 ..... + Checking SFP+ 14 0x50 ..... + Checking SFP+ 15 0x50 ..... + Checking SFP+ 16 0x50 ..... + Checking SFP+ 17 0x50 ..... + Checking SFP+ 18 0x50 ..... + Checking SFP+ 19 0x50 ..... + Checking SFP+ 20 0x50 ..... + Checking SFP+ 21 0x50 ..... + Checking SFP+ 22 0x50 ..... + Checking SFP+ 23 0x50 ..... + Checking SFP+ 24 0x50 ..... + Checking SFP+ 25 0x50 .....
write Output /opt/dell/diag/bin# ./i2ctool --write --bus=/dev/i2c-2 --addr=0x48 --reg=0x14 --val=1 Configuration file format The configuration file format for the i2c busses is strict. Use i2ctool --create to create a boilerplate configuration file and editing the boilerplate configuration file rather than creating it from scratch. The configuration file lists each bus from 0 to 4 and the devices. The number of devices MUST match the number of entries or the i2ctool stops functioning.
Tests To test the LEDs, use the ledtool --test command. root@dell-diag-os:/opt/ngos/bin# ./ledtool --test LED Test Started... Will take few mins to complete. LED Tool: Overall test results --------------------- >>> Passed CLI options DellEmc Diag - Led Tool version 1.0, x.xx.x.
States: off flashing-amber-fast Port#19-36-Green States: off flashing-green-fast CPLD4-Mode States: normal-mode test-mode Port#37-48-Amber States: off flashing-amber-fast Port#37-48-Green States: off flashing-green-fast amber flashing-amber green flashing-green amber flashing-amber green flashing-green Output list output root@dell-diag-os:/etc/dn/diag# ledtool --list Power Led : options green amber flashing-amber off System Led : options amber flashing-green flashing-amber green Fan Led : options green f
Configuration file format CONTROL_CONFIG | 2 #Control Config | method | | | | | I2C Device Flag | lpc | - | 0 | 0x04D8 | 0x210 | 0x211 | 0x212 | 0x213 | 0x55 | 0xAA | 0x5A | 0xA5 Led Control Flag | lpc | - | 0 | 0x04Dc | 0x210 | 0x211 | 0x212 | 0x213 | 0x55 || 0xAA | 0x55 | 0xAA [Power] Power Led | lpc | - | 0 | 0x130 [green] 1 | 5:4 | 0 [/green] [amber] 1 | 5:4 | 1 [/amber] [flashing-amber] 1 | 5:4 | 2 [/flashing-amber] [off] 1 | 5:4 |
lpctool --read --addr=
--count= [--size=] (or) lpctool -r -a -C [-z ] Write data at the specified address:= lpctool --write --addr=address --val=data [--size=b,w or l] (or) lpctool -w -a -V [-z ] Execute repeatedly command by count:= lpctool --iteration=max/ [option1] [option2]... (or) lpctool -I max/ [option1] [option2]...• • • • • • • • • Address Walking 0—Walks a 0 address bit through the memory area available to it. Address walking 0 writes the additive inverse of the address to the location. After writing all addressed locations, it walks back through and verifies the locations data. Data Read—Reads transactions similar to the Address Read test, but focuses on the data bits. Patterns are placed on the data bus to test for stuck data bits.
Available Tests are: ALL_TESTS, ADDRESS_READ, ADDRESS_WRITE, ADDRESS_WALKING1, ADDRESS_WALKING0, DATA_READ, DATA_WRITE, DATA_WALKING1, DATA_WALKING0, DATA_SLIDING1, DATA_SLIDING0, DATA_PATTERN, DATA_CACHE e.g. ADDRESS_WALKING1,DATA_WALKING1 The memtool uses long options for the parameters which requires two hyphens in front of the options. Options are required, optional, or none.
info Output root@dell-diag-os:~# memtool --info ==== SPD Data ==== Density 8192 MB, Rows: 16, Cols: 10 Bus Width: 64 bits, ECC: yes Manufacturer: Unknown Part Number : AW48M7228BNK0M [00000000]: 0x92 0x13 0x0b 0x08 0x05 0x22 || .....".......... [00000010]: 0x69 0x78 0x69 0x3c 0x69 0x11 || ixi
read Output root@dell-diag-os:~# memtool --read --addr=200 [00000200]: 0x00 || . write Output root@dell-diag-os:~# memtool --write --addr=200 --val=0x50 Constraints You cannot perform memory tests while other tests that allocate and use memory within the region are performing. However, you can perform the Read tests concurrently with other processes. You cannot run multiple memory tests at the same time as they may collide within the memory spaces.
• ADDRESS_WRITE—Write test of the address lines. • ADDRESS_WALKING1—Walking a 1 through the address lines within the memory space. • ADDRESS_WALKING0—Walking a 0 through the address lines within the memory space. • DATA_READ—Read test of the data lines. • DATA_WRITE—Write test of the data lines. • DATA_WALKING1—Walking a 1 through the data lines. • DATA_WALKING0—Walking a 0 through the data lines. • DATA_SLIDING1—Sliding a 1 through the data lines.
-t, --test -s, --show all id := Run All NPU tests := Run test based on test ID counter temp := Dump packet counters := Display NPU temperature -l, --lpbk [phy/mac/ext]:= Specify Loopback type for traffic test -T, --traffic [ixia_self,ixia_adj,cpu_self,cpu_adj] := Send IXIA or CPU traffic based on specified cfg self->timbercon lpbk, adj->fiber lpbk -I, --iteration [count]:= Execute repeatedly command by count -v, --version := Display version Usage: nputool -i -t [all/0/1,2,3/4/..
CPU traffic with external loopback Tests the traffic sent from the CPU internally generated packet to the front-end ports that are connected with external Loopback optics. Connect all the ports with QSFP28 Loopback optics.
PCI unit 0: Dev 0x8375, Rev 0x11, Chip BCM88375_B0, Driver BCM88375_B0 sysconf_probe successful global_sal_config successful *** 1 BCM devices are detected Diag NPU initialization over Test link_status_test for NPU 0 ............. SKIPPED <<<--Test snake_traffic_test for NPU 0 ............. Passed Test prbs_mac_test for NPU 0 ............. SKIPPED <<<--Test prbs_ext_test for NPU 0 ............. SKIPPED <<<--Test uplink_link_status_test for NPU 0 .............
Traffic is sent from the CPU internally generated packet to the front-end SFP+ ports which are connected with the Dell EMC SFP+ optics using a cable. Connect the first port to IXIA and all other ports with Loopback optics. • nputool -i -t 5 -T ixia_self -d • nputool --init --test 5 --traffic ixia_self -d Configure the VLAN and display the BCM.0> shell. To verify the counters, use the show c command in the BCM shell.
Connect the SFP+ ports with an external Loopback cable. • PRBS MAC level test ./nputool –i –t 6 • PRBS EXT level test “./nputool –i –t 7 NPU temperature Show the current NPU temperature.
Tests There are no tests of the NVRAM. This tool only controls the bits. CLI option DellEmc Diag - NVRAM Tool version 1.5, x.xx.x.
RMT Control : offset 0x52 = 0x0 7: 4 Undefined = 0 3 RMT Test Enable = 0 2: 0 RMT Test Reboot Count = 0 Status ID Byte : offset 0x53 = 0xe6 POST Control Bits : offset 0x54 = 0x3 7 Force Cold Boot = 0 6 POST Extended Upper DRAM test = 0 5 POST Extended Lower DRAM test = 0 4 POST Extended tests = 0 3 Reserved = 0 2 POST Verbose Mode = 0 1 POST Stop on Error = 1 0 POST Enable = 1 EDA Control Bits : offset 0x55 = 0x3 5: 4 EDA Verbose Level = 0 3 EDA Extended Tests = 0 2 EDA Verbose Mode = 0 1 EDA Stop on Error
opticstool To check the presence or absence of optic devices, link status, and to read data from the optic devices’ EEPROM, use the opticstool. Tests There are no tests on the optic devices. You can run a brief report that displays the optic presence or shows simple data, such as the serial number and device type. For more detailed information, use a device report. CLI options DellEmc Diag - Optics Tool version 1.0, x.xx.x.
8 SFP+ 8 PRESENT 9 SFP+ 9 PRESENT 10 SFP+ 10 PRESENT 11 SFP+ 11 PRESENT 12 SFP+ 12 PRESENT 13 SFP+ 13 PRESENT 14 SFP+ 14 PRESENT 15 SFP+ 15 PRESENT 16 SFP+ 16 PRESENT 17 SFP+ 17 PRESENT 18 SFP+ 18 PRESENT 19 SFP+ 19 PRESENT 20 SFP+ 20 PRESENT 21 SFP+ 21 PRESENT 22 SFP+ 22 PRESENT 23 SFP+ 23 PRESENT 24 SFP+ 24 PRESENT 25 SFP+ 25 PRESENT 26 SFP+ 26 PRESENT 27 SFP+ 27 PRESENT 28 SFP+ 28 PRESENT 29 SFP+ 29 PRESENT 30 SFP+ 30 PRESENT 31 SFP+ 31 PRESENT 32 SFP+ 32 PRESENT 33 SFP+ 33 PRESENT 34 SFP+ 34 PRESENT 35
19 SFP+ 19 PRESENT 20 SFP+ 20 PRESENT 21 SFP+ 21 PRESENT 22 SFP+ 22 PRESENT 23 SFP+ 23 PRESENT 24 SFP+ 24 PRESENT 25 SFP+ 25 PRESENT 26 SFP+ 26 PRESENT 27 SFP+ 27 PRESENT 28 SFP+ 28 PRESENT 29 SFP+ 29 PRESENT 30 SFP+ 30 PRESENT 31 SFP+ 31 PRESENT 32 SFP+ 32 PRESENT 33 SFP+ 33 PRESENT 34 SFP+ 34 PRESENT 35 SFP+ 35 PRESENT 36 SFP+ 36 PRESENT 37 SFP+ 37 PRESENT 38 SFP+ 38 PRESENT 39 SFP+ 39 PRESENT 40 SFP+ 40 PRESENT 41 QSFP+ 41 PRESENT 42 QSFP+ 42 PRESENT 43 QSFP28 43 PRESENT 44 QSFP28 44 PRESENT 45 QSFP28 45
[00000070]: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 || ................ [00000080]: 0x11 0x00 0x23 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 || ..#............. [00000090]: 0x00 0x00 0x01 0xa0 0x4d 0x6f 0x6c 0x65 0x78 0x20 0x49 || ....Molex Inc. [000000a0]: 0x20 0x20 0x20 0x20 0x00 0x00 0x09 0x3a 0x31 0x30 0x30 || ...:10029711 [000000b0]: 0x30 0x31 0x20 0x20 0x20 0x20 0x20 0x20 0x31 0x20 0x00 || 01 1 .....L [000000c0]: 0x00 0x00 0x00 0x00 0x35 0x30 0x34 0x31 0x32 0x30 0x35 || ....
Then four entries describe how to read if a device is present, select the MUX for accessing the device, reset or not reset the device, and read data from the device.
pcitool To scan and access devices on the PCI bus, use the pcitool. The pcitool checks for missing devices and that the present devices are the proper type. The pcitool scans the PCI bus for present devices and displays them and the BAR information it decodes. The tool does not handle endianess. The pcitool reads the configuration file and then iterates across all devices in the configuration file. It checks the vendor/product ID to see that the correct device is at the correct address.
-B, -D, -F, -O, -C, -V, --bus= --dev= --func= --offset= --count= --val= To specify the i2c bus Device Func Set the Offset Count Value to be set e.g.: /dev/i2c- Output scan output root@dell-diag-os:~# pcitool --scan Acquiring PCI device name database Device#01: bus:dev.fn 00:00.0 - ID=0x1f0c8086, Device#02: bus:dev.fn 00:01.0 - ID=0x1f108086, Device#03: bus:dev.fn 00:02.0 - ID=0x1f118086, Device#04: bus:dev.fn 00:03.0 - ID=0x1f128086, Device#05: bus:dev.fn 00:04.
show output root@dell-diag-os:/etc/dn/diag# pcitool --show --bus=0 --dev=4 --func=0bus bus:dev.fn 00:04.3 [00000000]: 0x00 0x00 0x00 0x00 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 || ................ [00000010]: 0x40 0x0e 0x40 0x00 0x00 0x00 0x00 0x00 0xe5 0xe2 0xdd 0x5b 0x47 || @.@........[G... [00000020]: 0xff 0xff 0xff 0xff 0x00 0x00 0x00 0x00 0x0c 0x00 0xad 0xfb 0x00 || ................ [00000030]: 0xf0 0x30 0x5f 0x02 0x00 0x00 0x00 0x00 0x10 0x30 0x5f 0x02 0x00 || .0_......0_.....
|| ................ [000000b0]: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 || ................ [000000c0]: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x01 || ................ [000000d0]: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x80 0x00 || ................ [000000e0]: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x01 0x00 0x00 || ................ [000000f0]: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x03 0x00 0x00 0x00 0x00 || ................
phytool The phytool allows setting the management phy for management port for speed, duplex auto negotiation, and Loopback; as well as reading the MAC and MAC EEPROM in the phy. Tests CLI options DellEmc Diag - PHY Tool version 1.1, x.xx.x.
Output root@dellemc-diag-os:/etc/dn/diag# phytool --read-mac 34:17:eb:07:7c:00 root@dellemc-diag-os:/etc/dn/diag# phytool --eeprom-dump Offset Values ----------0x0000: 34 17 eb 07 7c 00 00 08 ff ff 05 10 ff ff ff 0x0010: 18 00 00 00 2f 40 41 1f 86 80 41 1f 86 80 80 0x0020: ff ff ff ff 80 5c 47 00 00 00 40 00 00 4c ab 0x0030: 00 00 00 70 0e 1a 26 44 a3 07 42 1f 01 02 02 0x0040: 0c 00 47 21 00 00 ff ff ac 44 f6 00 44 1f 08 0x0050: 40 04 3c 00 00 00 04 14 00 00 00 00 00 10 ff 0x0060: 00 01 00 40 32 13 13 40 00
Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 3 Transceiver: internal Auto-negotiation: on MDI-X: off (auto) Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000007 (7) drv probe link Link detected: yes pltool To test functionality of the CPLD and FPGA devices on the boards during startup, use the pltool. The pltool also checks for the correct firmware loads.
-L, -r, -w, -I, -n, -D, --listdevicenames --read --write --iteration= --devname= --dev= -R, --reg= -V, --val= -d, --dump List Device name Read operation Write operation Iteration command execution Device name Device (should be assigned 0 for lpc access) Register Value to be set Dump the values in the registers of a device Output list output root@dell-diag-os:~# pltool --list CPLD1 0 cpld lpc 0 (U5) 0x100 CPLD_VERSION bits:8 RO val:0 mask:0xff test:0 ver:0x0 7:4 MAJOR_VER RO 0 3:0 MINOR_VER RO 0 0x101 BO
0x3e : CPLD4 0x0 : SMF_FPGA read output root@dell-diag-os:~# pltool --read --devname=CPLD4 --dev=0x3e --reg=0x2 SW_SCRATCH : offset 0x02 = 0xde 7: 0 SW_SCRATCH = de root@dell-diag-os:~# write output root@dell-diag-os:~# pltool --write --devname=CPLD4 --dev=0x3e --reg=0x2 --val=0xff test output root@dell-diag-os:~# pltool --test Testing Programmable Devices: PL Tool test: CPLD1 .................... Passed CPLD2: SW_SCRATCH.................... CPLD3: SW_SCRATCH.................... CPLD4: SW_SCRATCH.......
psutool The psutool determines which PSUs are in the system, checks the Power Good setting, and reads the field replaceable unit (FRU) information. It does not look at the PSU fans and airflow direction of the fans. Tests The psutool looks for the presence of the PSU and if the PSU is present, it checks the Power Good setting in the CPLD. It does not read directly from the PSU but reads the CPLD information instead.
Power Supply 1 Input Current(IIN) : 0.610000 A Power Supply 1 Output Current(IOUT) : 9.150000 A Power Supply 1 Input Power(PIN) : 124.000000 W Power Supply 1 Output Power(POUT) : 111.700000 W Power Supply 1 Temperature : 30.
• Tool Name—Name of the tool. • Access to Present and Power Good—The type of access to the CPLD, i2c, LPC, and MEM. • Access bus—For i2c devices. Shows which i2c bus to use. • Address—For LPC devices, the address of the device or register. • Register—Access size for LPC. • Present Bit(s)—The bit or bits to indicate presence. The range of bits display as end:start and must be contiguous. Disaggregate sets of bits are not supported. • PresentValue—The value present.
-a, -p, -I, -y, -m, -D, -H, -M, -S, -Z, --testaie --testpie --iteration= --year= --month= --day= --hour= --min= --sec= --offset= Test RTC device with alarm interrupt Test RTC device with periodic interrupt Iteration command execution Year Month Day Hour Minute Second +12.0 to -12.0 timezone offset smartctl smartctl controls the self-monitoring, analysis, and reporting technology (SMART) system built into most ATA/SATA and SCSI/SAS hard drives and solid-state drives.
CLI options root@dell-diag-os:/opt/dell/diag/bin# smarttool ERROR: main[100]: ERROR: Usage: smarttool [|] ------------------------------------------------------Usage: smarttool [] [|] - Command string (Refer below for supported commands) UART device name (say, "/dev/tty00") Specify image file path for upgrade Specify image region.
Figure 7. Check MSS region 3 Check the MSS version using smarttool –gmv /dev/ttyS0 command. Figure 8. Check MSS version 4 Because the MSS is running in region G in this example, use the region A image to upgrade your device: smarttool -um /dev/ ttyS0 /_SMF_MSS_v1.41_A_region.bin. The device automatically reboots after the upgrade.
Figure 9. Upgrade region A 5 Ensure that MSS has upgraded successfully by using the smarttool –gmv /dev/ttyS0 command after the system reboots. Figure 10. Check MSS upgrade Upgrading SMF FPGA To upgrade your system using the FPGA method, follow these steps. 1 Copy all the binaries needed for upgrade into a local directory.
Figure 11. Copy needed binaries 2 Check the FPGA region using smarttool –gfr /dev/ttyS0 command. Figure 12. Check FPGA region 3 Get the current version of the FPGA using the lpctool utility. Get the FPGA running image version through the ./lpctool -read --addr=0x200 --size=b registers at the LPC tool. Table 1. SmartFusion FPGA registers Offset Name Description 0x200 SMF_VER SmartFusion FPGA version register Figure 13. Get current FPGA version 4 Upgrade the FPGA in smartFusion using the # .
Figure 14. Upgrade FPGA 5 Verify that the FPGA is upgraded using the lpctool utility. Get the FPGA running image version through the ./lpctool --read --addr=0x200 --size=b registers of the LPC tool. smbiostool The smbiostool displays information about the BIOS and also reprograms the BIOS flash. CLI options DellEmc Diag - SMBIOS Tool version 1.2, x.xx.x.
smbiostool -S <*options*> <*options*> for biosdumpfiels:= -q Less verbose output -s Only display the value of the given DMI string -t TYPE Only display the entries of given type -u Do not decode the entries --dump-bin Dump the DMI data to a binary file --from-dump Read the DMI data from a binary file -V Display the version of dmidecode binary Output root@dell-diag-os:~# smbiostool --biosversion x.xx.x.
Test devices(empty for all):= storagetool --test [--dev=] (or) storagetool -t [-D Get the smart status for a device storagetool --smart --dev= (or) storagetool -S -D Execute repeatedly command by count:= storagetool --iteration=max/ [option1] [option2]...(or) storagetool -I max/ [option1] [option2]...
=== START OF ENABLE/DISABLE COMMANDS SECTION === SMART Enabled. === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Total time to complete Offline data collection: ( 32) seconds. Offline data collection capabilities: (0x00) Offline data collection not supported.
Writing with putc()...done Writing intelligently...done Rewriting...done Reading with getc()...done Reading intelligently...done start 'em...done...done...done... Create files in sequential order...done. Stat files in sequential order...done. Delete files in sequential order...done. Create files in random order...done. Stat files in random order...done. Delete files in random order...done. Version 1.
-d TYPE, --device=TYPE Specify device type to one of: ata, scsi, sat[,auto][,N][+TYPE], usbcypress[,X], usbjmicron[,p][,x][,N], usbsunplus, marvell, areca,N/E, 3ware,N, hpt,L/M/N, megaraid,N, cciss,N, auto, test -T TYPE, --tolerance=TYPE Tolerance: normal, conservative, permissive, verypermissive (ATA) -b TYPE, --badsum=TYPE Set action on bad checksum to one of: warn, exit, ignore (ATA) -r TYPE, --report=TYPE Report transactions (see man page) -n MODE, --nocheck=MODE No check if: never, sleep, standby,
and then /usr/share/smartmontools/drivedb.h] ============================================ DEVICE SELF-TEST OPTIONS ===== -t TEST, --test=TEST Run test.
CLI options NOTE: Before using any commands, you must set the MUX settings to select the bus segments the temperature sensors are on. DellEmc Diag - Temperature Tool version 1.4, x.xx.x.x-x build, 2017/05/23, Syntax: temptool
Temperature Sensor 8 temperature value is 31.0 C Temperature Sensor 9 temperature value is 42.0 C root@dell-diag-os:/opt/dell/diag/bin# Configuration file format This output example is for systems without a SMF chip.
edatool The edatool is included in the diagnostic tools. Use the tool to test the basic functionality of the system. The edatool executes a script of simple commands, similar to commands in the CLI. Usually, the diagnostics tools run these types of tests. The success or failure of these tools is reported, and at the end of the edatool run, reports the PASSED or FAILED results in a standard format the test scripts can easily parse.
Dell-EMC Dell-EMC Dell-EMC Dell-EMC Dell-EMC Dell-EMC Dell-EMC Dell-EMC Dell-EMC Dell-EMC Dell-EMC Dell-EMC Dell-EMC Dell-EMC Dell-EMC Dell-EMC Dell-EMC Diag Diag Diag Diag Diag Diag Diag Diag Diag Diag Diag Diag Diag Diag Diag Diag Diag cputool - version 1.1 package x.xx.x.x 2016/11/21 fantool - version 1.5 package x.xx.x.x 2016/11/21 gpiotool - version 1.4 package x.xx.x.x 2016/11/21 i2ctool - version 1.5 package x.xx.x.x 2016/11/21 ledtool - version 1.0 package x.xx.x.x 2016/11/21 lpctool - version 1.
+ Checking SFP+ 5 0x50 ..... Passed + Checking SFP+ 6 0x50 ..... Passed + Checking SFP+ 7 0x50 ..... Passed + Checking SFP+ 8 0x50 ..... Passed + Checking SFP+ 9 0x50 ..... Passed + Checking SFP+ 10 0x50 ..... Passed + Checking SFP+ 11 0x50 ..... Passed + Checking SFP+ 12 0x50 ..... Passed + Checking SFP+ 13 0x50 ..... Passed + Checking SFP+ 14 0x50 ..... Passed + Checking SFP+ 15 0x50 ..... Passed + Checking SFP+ 16 0x50 ..... Passed + Checking SFP+ 17 0x50 .....
Configuration file format Find the standard configuration files in the /etc/dn/diag directory. The configuration files are default_eda_script.cfg and default_eda_extended_script.cfg that hold the scripts for normal and extended tests, respectively. The configuration file format has a single command on a single line. The edatool does not use the complex shell script constructs in the configuration file. root@dell-diag-os:/etc/dn/diag# cat default_eda_script.
Verbose mode Use the following steps to enable and set the verbose level. 1 Set the Verbose level with a value of 0 to 3 using bits 4 and 5 of the EDA control reg (0x55). For example, to set the verbose level to 2, set bit 5 to 1 (5=1) and bit 4 to 0 (4=0). root@dellemc-diag-os:~# nvramtool --write --reg=0x55 --val=0x25 The value is written in hexadecimal. The xx10x1xx shows the bit positions of 2, 4&5, and bit 0 on the right. 2 Enable Verbose mode by setting bit 2 of the same reg to 1.
6 Technical support Dell EMC Support provides a range of documents and tools to assist you with effectively using Dell EMC equipment and mitigating the impact of network outages. Through Dell EMC Support you can obtain technical information regarding Dell EMC products, access to software upgrades and patches, and open and manage your Technical Assistance Center (TAC) cases. Dell EMC support provides integrated, secure access to these services.
Hardware replacement To request replacement hardware, follow these steps: 1 Determine the part number and serial number of the component. To list the numbers for all components installed in the chassis, use the show hardware command. 2 Request an RMA number from TAC by opening a support case. Open a support case by: • Using the Create Service Request form on the Support page. • Contacting Dell EMC directly by email or by phone.
