Open Networking Hardware Diagnostic Guide April 2016
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. © 2016 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents 1 About this Guide.......................................................................................................................................................7 Notices.......................................................................................................................................................................... 7 Related Documents.......................................................................................................................................
CLI Options.......................................................................................................................................................... 32 Output................................................................................................................................................................... 33 Configuration File Format.................................................................................................................................35 ethtool......
nputool....................................................................................................................................................................... 54 Tests...................................................................................................................................................................... 54 CLI Options....................................................................................................................................................
CLI Options.......................................................................................................................................................... 83 Outputs................................................................................................................................................................. 83 edatool....................................................................................................................................................................
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 Installation Instructions for ONIE and the Dell OS This section describes the different methods to install ONIE and the Dell Networking OS on your system. ONIE Install Mode Assumes Ownership (Sticky) NOTE: After installing the NOS/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/Diag-OS is successfully installed again.
NOTE: The following output examples are for reference only; your output may be different. NOTE: The management port IP, FTP server IP address, MAC address, and user-id shown are for illustration purpose only. You must use your system’s applicable values. ONIE Service Discovery and OS Installation ONIE attempts to locate the installer through several discovery methods, as shown. To download and run an installer, the ONIE Service Discovery feature uses the first successful method found.
The BIOS running on your system must meet the following requirements: • Allows a change to the boot order so the system can boot from media (USB). • Allows a baud-rate change. This is optional and you do not need it if your BIOS is running at 115200 baud rate. The default baud rate for ONIE is 115200. CAUTION: • These procedures are for x86-based targets only, particularly targets using Rangeley or Centerton CPU-based boards. • Dell Networking recommends checking the console (UART-0/1) used on target.
5 Set boot option 1 to USB using the following path: Advanced > USB configuration >Mass Storage Devices: [USB device] Figure 2. USB Configuration 6 Set the Boot order to boot from the USB device using the following path: Boot > Hard Drive BBS Priorities > Boot Option #1 7 In the Boot Option #1 option, select the device that corresponds to your USB device. 8 Select Save and exit the BIOS menu. 9 The BIOS boots from the ONIE Recovery USB device.
. . . Please press Enter to activate this console. Info: eth0: Checking link... up. Info: Trying DHCPv4 on interface: eth0 DHCPv4 on interface: eth0 failedONIE: Using default IPv4 addr: eth0: 192.168.3.10/255.255.255.0 ONIE: Starting ONIE Service Discovery Info: Found static url: file:///lib/onie/onie-updater ONIE: Executing installer: file:///lib/onie/onie-updater Verifying image checksum ... OK. Preparing image archive ... OK. ONIE: Version : n.n.n.
POST Lower DRAM ECC check ................... PASS SM Bus1 PHY...done DxE POST POST Upper DRAM Memory test Short memory cell test .... POST Upper DRAM Memory test ................. POST PCI test ............................... POST NVRAM check ............................ POST overall test results ................... 11 PASS PASS PASS PASS Change the BIOS back to CFast/mSATA using the procedure shown in Steps 5 through 8. Figure 4. Configure the BIOS to Boot from CFast/mSATA GNU GRUB version 2.
Info: Using eth0 MAC address: 4c:76:25:f4:f0:00 Info: eth0: Checking link... up. Info: Trying DHCPv4 on interface: eth0 scsi 6:0:0:0: Direct-Access Kingston DataTraveler 102 1.00 PQ: 0 ANSI: 2 sd 6:0:0:0: [sdb] 3913664 512-byte logical blocks: (2.00 GB/1.
12 Set the Boot order to the boot from the usb option using the following path: Boot > Hard Drive BBS Priorities > Boot Option #1 13 In the Boot Option #1 option, select the device that corresponds to your USB device. 14 Select Save and exit the BIOS menu. Figure 5. Set Boot Option #1 to USB The BIOS boots from the ONIE Recovery USB.
ONIE-RECOVERY:/ # ONIE-RECOVERY:/ # ONIE-RECOVERY:/ # DHCPv4 on interface: eth0 failedONIE: Using default IPv4 addr: eth0: 192.168.3.10/255.255.255.0 ONIE: Starting ONIE Service Discovery Info: Found static url: file:///lib/onie/onie-updater ONIE: Executing installer: file:///lib/onie/onie-updater Verifying image checksum ... OK. Preparing image archive ... OK. ONIE: Version : n.n.n.
| ONIE: Rescue | | ONIE: Uninstall OS | | ONIE: Update ONIE | | ONIE: Embed ONIE | | | | | | | | | | | | | | | +----------------------------------+ Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, `e' to edit the commands before booting or `c' for a command-line. ONIE: OS Install Mode ... Version : 3.20.1.3 Build Date: 2015-03-18T20:55-0700 Info: Mounting kernel filesystems... done. Info: Mounting LABEL=ONIE-BOOT on /mnt/onie-boot ...
DHCP/TFTP Server Installation The following procedure installs the DHCP/TFTP server on a Linux machine. This procedure uses dnsmasq. NOTE: To configure the DHCP/TFTP server, you can use any Linux-based host machine. Before you begin, be sure that you have the root access on your system. 1 Install dnsmasq on your Linux machine. apt-get can be used to install dnsmasq. apt-get install dnsmasq Alternatively, you can download the debian package of dnsmasq and install it.
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.
Changing the Default Grub Boot Entry To view or set the default Grub boot entry, use the following command. The onie-boot-mode command has two options —l (the default) and —o to view or set the default Boot mode. The Grub boot default shows the current default entry. View or set the default Grub boot entry.
Example of the onie-sysinfo —a command. ONIE:/ # onie-sysinfo -a CN0WKFYN7793157U0002 0GTX3X 4C:76:25:F4:F0:00 n.n.n.
4 Dell DIAG OS The following describes the Dell diagnostics. These instructions apply to systems for which the ONIE diagnostics are not available. Topics: • Downloading the Diagnostic Package • Viewing the Dell DIAGs Versions • Viewing the CPLD Versions • Installing or Upgrading DIAG Tools in the Dell DIAGs OS • Restoring the Factory Defaults Downloading the Diagnostic Package To download the diagnostic package on your system, follow these steps.
This command needs to be executed if diag-os needs to run in installer mode with diag-os already installed on the system ONIE:/ # touch /tmp/diag_os_install_mode ONIE:/ # ONIE:/ # ONIE:/ # ONIE:/ # onie-nos-install tftp://n.n.n.n/sm//diag-installer-x86_64-dell_ _-r0.bin discover: installer mode detected. Stopping: discover... done. Info: Fetching tftp://n.n.n.n/sm//diag-installer-x86_64-dell__-r0.bin ...
Installation finished. No error reported. ONIE ver 3 supports 50_onie_grub... Generating onie and diag-os grub config using 50_onie_grub grub cfg /tmp/tmp.aZBTn0 and ngos_mnt /boot Removing /tmp/tmp.AvXUTZ Rebooting... ONIE:/ # discover: installer mode detected. Stopping: discover...start-stop-daemon: warning: killing process 279: No such process done. Stopping: dropbear ssh daemon... done. Stopping: telnetd... done. Stopping: syslogd... done.
POST PCI test ............................... PASS POST NVRAM check ............................ PASS POST overall test results ................... PASS NVRAM: 00 9F 00 E6 0B 01 00 EA A2 Version 2.17.1245. Copyright (C) 2015 American Megatrends, Inc. BIOS Date: 08/28/2015 16:17:45 Ver: 0ACBZ028 Press or to enter setup. Booting `EDA-DIAG' Loading DIAG-OS ... [ 1.238906] dummy-irq: no IRQ given. Use irq=N [ 11.
[ OK [ OK ] Reached target Graphical Interface. Starting Update UTMP about System Runlevel Changes... ] Started Update UTMP about System Runlevel Changes. Debian GNU/Linux 8 dell-diag-os.com ttyS1 dell-diag-os login: root Password: Linux dell-diag-os.com 3.15.10 #1 SMP Fri Sep 4 15:34:15 PDT 2015 x86_64 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright.
| | | | Viewing the Dell DIAGs Versions To display the Dell DIAG version installed in the Dell DIAG OS, use the dpkg -l | grep dn-diags command at the root@dell-diag-os:~ prompt. root@dell-diag-os:~# dpkg -l | grep dn-diags ||/ Name Version Architecture Description +++-==============-=====================-================== ii dn-diags- 1.
CAUTION: Restoring factory defaults erases any installed operating system and requires a long time to erase storage. 1 Restore the factory defaults on your system from the Grub menu using the ONIE: Uninstall OS command. Use the up and down arrow keys to select which entry is highlighted. Press Enter to select an operating software-selected OS or enter e to edit the commands before booting. Enter c for a command line. The highlighted entry (*) executes automatically in the operating system.
5 Dell DiagOS Tools This guide helps you use the Dell diagnostics operating system (DiagOS). The DiagOS is an environment that provides a suite of tools that you can use to help diagnose issues seen on the system, or to run a general health check to make sure 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@dell-diag-os:~# cpldupgradetool Dell Diag - CPLD Upgrade Tool version 1.1, 1.
Valid CPLD Binary file size 0.998490MB Writing CPLD Binary File: final.vme ...... ******************************************** -------------------------------------P A S S E D! -------------------------------------****************************************** Configuration File Format Configuration File Format There is no configuration file associated with the cpldupgradetool cputool The cputool displays the CPU information, reads and writes of the MSR and the LPC bus.
-1, --one-cpu display information only for the current CPU -f FILE, --file=FILE read raw hex information (-r output) from FILE instead of from executions of the cpuid instruction -h, -H, --help display this help information -i, --inst use the CPUID instruction: The information it provides is reliable. It is not necessary to be root. (This option is the default.) -k, --kernel use the CPUID kernel module: The information does not seem to be reliable on all combinations of CPU type and kernel version.
Syntax: eepromtool
************PSU1_DellPartNumber************* Registers 0x24c - 0x251 0XTVK2 ************PSU1_MfgID************* Registers 0x252 - 0x256 0XTVK ************PSU1_MfgDate************* Registers 0x257 - 0x25e 150102 ************PSU1_SerialNo************* Registers 0x25f - 0x262 CN17 ************PSU1_ServiceTag************* Registers 0x263 - 0x269 ************PSU1_LabelRevision************* Registers 0x26a - 0x26c A00 ************PSU2_CountryCode************* Registers 0x283 - 0x284 CH ************PSU2_DellPartNu
Notice: Invalid TLV checksum found. Using default contents. TlvInfo Header: Id String: TlvInfo Version: 1 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 are listed 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.
NOTE: (Optional) For systems that use the SmartFusion chip, the eepromtool also has two companion configuration files — default_mailbox_eeprom.cfg which holds information for the --psueepromdump command, and default_fan_mailbox_eeprom.cfg which holds information for the --faneepromdump command. ethtool The ethtool provides management interface details. fantool The fantool tests the fans in the system, sets and reports the fan speeds and the fan tray field replaceable unit (FRU) registers.
Output test Output root@dell-diag-os:~# fantool --test --lpc Fan Controller Test LPC....................................
#R | NAME | Offset | Size in bytes LPC-INTERFACE D | 0 | Fan 1| 0x01 | 0x115 | 0x01 | 0x01 | 0xF3 | 2 … D | 9 | Fan 10| 0x10| 0x114 | 0x02 | 0x10 | 0x105 | 2 R | 0xF0 | 1 |Fan Tray Count Register R | 0xF1 | 1 |Fan Count Per Fan Tray Register R | 0xF2 | 1 |Max Fan Speed Set Register R | 0x113 | 1 |Fan Tray Presence Register R | 0x116 | 1 |Fan Tray Air Flow Register ===== /dev/i2c-2 0x70:0:0xff:0x9:,:0x74:1:0xff:0xa flashrom To update or erase the BIOS flash memory, the smbiostool uses flashrom.
37 38 39 40 49 50 51 52 53 54 55 58 59 PMU_SLP_DDRVTT_B PMU_SLP_LAN_B PMU_WAKE_B PMU_PWRBTN_B GBE_SDP0_1 GBE_LED0 GBE_LED1 GBE_LED2 GBE_LED3 NCSI_RXD1 GBE_MDIO0_I2C_CLK GBE_MDIO1_I2C_DATA JTAG_TRST IN IN OUT IN IN IN IN IN IN OUT OUT IN OUT LOW LOW LOW LOW LOW LOW LOW LOW LOW LOW LOW LOW LOW 0 0 0 0 0 0 0 0 0 0 0 0 0 get Output root@amazon:/opt/ngos/bin# ./gpiotool --get --pin=1 GPIO pin # 1 is 1 set Output root@amazon:/opt/ngos/bin# .
present. The i2ctool does not automatically traverse MUXes along the i2c bus. Other tools use this tool to read i2c device information and pass the results back through a named pipe. Tests To test, the i2ctool has a configuration file that lists all the devices on the busses. The tool runs through the list and tries to reach the devices. The i2ctool reports when a device is not returning data. CLI Options Dell Diag - I2C Tool version 1.5, 1.10 build, 2014/11/10, Syntax: .
50: 50 -- -- -- -- -- -- -- -- -- -60: -- -- -- -- -- -- -- -- -- 69 -70: -- -- -- -- -- -- -- -- RR RR RR 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: RR RR RR RR RR RR RR RR -- -- -10: -- -- -- -- -- -- -- -- -- -- -20: -- -- -- -- -- -- -- -- -- -- -30: -- -- -- -- -- -- -- -- -- -- -40: -- -- -- -- -- -- -- -- -- -- -50: 50 51 52 53 54 55 56 57 -- -- -60: -- -- -- -- -- -- -- -- -- -- -70: 70 -- -- -- -- -- -- -- RR RR RR I2C devices found on bus #1: 5 0x18 0x2e 0x30 0x50 0x69 I2C devices found on bus #2: 10 0x3
+ Checking IOM_1 QSFP2 0x50 ..... Passed + Checking IOM_1 QSFP3 0x50 ..... Passed + Checking IOM_1 QSFP4 0x50 ..... Passed + Checking IOM_1 QSFP5 0x50 ..... Passed + Checking IOM_1 QSFP6 0x50 ..... Passed + Checking IOM_1 QSFP7 0x50 ..... Passed + Checking IOM_1 QSFP8 0x50 ..... Passed + Checking IOM_1 QSFP9 0x50 ..... Passed + Checking IOM_1 QSFP10 0x50 ..... Passed + Checking IOM_1 QSFP11 0x50 ..... Passed + Checking IOM_1 QSFP12 0x50 .....
Testing I2C devices: Checking I2C devices on bus 1: + Checking Clock GEN 0x69 ..... Passed + Checking DDR3 VREF Tuning 0x2e ..... Passed + Checking SPD0 0x50 ..... Passed + Checking SPD1 0x52 Error reading at offset 0x00 ..... FAILED <<<--Checking I2C devices on bus 2: + Checking CPU Board I2C Mux 0x70 ..... Passed + Checking CPU Board EEPROM1 0x50 ..... Passed + Checking CPU Board EEPROM2 0x51 ..... Passed + Checking CPU Board EEPROM3 0x52 ..... Passed + Checking CPU Board EEPROM4 0x53 .....
Each device is listed on its own line for that bus in comma separated format: Name mux bus mux level 1 setting in the format of address:value mux level 2 setting in the format of address:value device address Register we can read from byte count For example: I2C devices found on bus #0: 0 I2C devices found on bus #1: 4 Clock GEN ,/dev/i2c-1, - ,0x69,0x00,1 DDR3 VREF Tuning ,/dev/i2c-1, - ,0x2e,0x00,1 SPD0 ,/dev/i2c-1, - ,0x50,0x00,1 SPD1 ,/dev/i2c-1, - ,0x52,0x00,1 I2C devices found on bus #2: 31 CPU Board I
--get [--led=led] := get the state of all leds or the specified led --set <--led=led> [--instance=instance] <--state=state | --val=value> := set the specified led to the state for color and blink --test [--config=config_file] := test using the test config file A list of the LEDs and their states follow the help output. • list — Provides a list of all the LEDs and their settings. • test — Testing LEDs is not supported.
Output list Output root@dell-diag-os:~# ledtool --list Platform Stacking Led : options green off Power Led : options green amber flashing-amber off Fan Led : options green flashing-amber off Beacon LED : options flashing-blue off 7-Digit Stack Led : options val IOM1 PortLED Mode : options normal-mode test-mode IOM1 FrontEnd AmberLed : options off flashing-amber amber flashing-amber IOM1 FrontEnd GreenLed : options off flashing-green green flashing-green IOM1 Module StatusLed : options green flashing-green a
Beacon LED : off 7-Digit Stack Led : Value 0xff IOM1 PortLED Mode : normal-mode IOM1 FrontEnd AmberLed : off IOM1 FrontEnd GreenLed : off IOM1 Module StatusLed : flashing-green IOM1 Module BeaconLed : off IOM2 PortLED Mode : normal-mode IOM2 FrontEnd AmberLed : off IOM2 FrontEnd GreenLed : off IOM2 Module StatusLed : flashing-green IOM2 Module BeaconLed : off IOM3 PortLED Mode : normal-mode IOM3 FrontEnd AmberLed : off IOM3 FrontEnd GreenLed : off IOM3 Module StatusLed : flashing-green IOM3 Module BeaconLed
IOM2 IOM3 IOM3 IOM3 IOM3 IOM3 IOM4 IOM4 IOM4 IOM4 IOM4 Module BeaconLed : off PortLED Mode : normal-mode FrontEnd AmberLed : off FrontEnd GreenLed : off Module StatusLed : flashing-green Module BeaconLed : off PortLED Mode : normal-mode FrontEnd AmberLed : off FrontEnd GreenLed : off Module StatusLed : flashing-green Module BeaconLed : off Configuration File Format CONTROL_CONFIG | 2 #Control Config | method | | | | | I2C Device Flag |
admin, 2014-10-01, bamboo-build-num Syntax: %s
• Data Write — Places data patterns on the bus for testing the bus and looks for stuck data bits. • Data Walking 1 — Walks a 1 through the data bits within an address location and verifies that the values are valid prior to overwriting. • Data Walking 0 — Walks a 0 bit through the data bits and verifies the value as it is testing. • Data Sliding 1 — Slides a 1 through the data testing for stuck bits. By xor of each shift to the data, when finished, the cell holds all the 1s.
Output list Output root@dell-diag-os:~# memtool --list =================================== Region ID: 0 Region Name: DDR3-0 Address: dynamically allocated, Chunk: 0x2800 KB Largest Cache Size: 0, Cache Line Size : 0 Access: d Increment: 8 Ecc: Y Iterations: 1 Configuration device: SPD (/dev/i2c-1) at 0x50, Regs 0 to 255 Tests: Address Read Test Address Write Test Address Walking 1's Test Address Walking 0's Test Data Read Test Data Write Test Data Walking 1's Test Data Walking 0's Test Data Sliding 1's Test
[000000e0]: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 || ................ [000000f0]: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 || ............... test Output root@dell-diag-os:/opt/ngos/bin# ./memtool --test Testing Memory Regions: Testing Memory Region 0: Address Read Test ......................................... Address Write Test ........................................ Address Walking 1's Test ..................................
Configuration File Format The configuration file for the memtool is a list of memory segments separated by a ==== divider. Each entry describes the memory in a system that is accessible. This allows you to review memory in RAMs, FPGAs, and RAM in a memory-mapped PCI BAR. Each parameter is on a separate line and consists of: • Name — The name of the memory region. • Start Address — The address that the memory starts with.
SPD Access:/dev/i2c-2 SPD Address:50 SPD Registers:0,ff nputool The nputool allows for configuring and testing the switch ASICs. The nputool tests the NPU in the system. The nputool verifies that ports are up and traffic between the ports is working either using the CPU-generated packet or using IXIA connected to port-1 and port-2 based on the configuration. Tests Tests are shown in the following sections. CLI Options The nputool shows the available options with the nputool -h or nputool command.
Test Test Test Test Test prbs_ext_test for NPU 0 .................... uplink_link_status_test for NPU 0 .......... uplink_snake_traffic_test for NPU 0 ........ uplink_prbs_mac_test for NPU 0 ............. uplink_prbs_ext_test for NPU 0 ............. SKIPPED SKIPPED SKIPPED SKIPPED SKIPPED <<<--<<<--<<<--<<<--<<<--- NPU tests .......................................
Test uplink_prbs_ext_test for NPU 0 ............ SKIPPED <<<--NPU tests ...................................... Passed CPU Traffic with Adjacent Loopback Tests the traffic sent from the CPU internally generated packet to the front-end ports which are connected with direct attach cables (DACs) or optics with cables connected top-to-bottom. Connect all the ports with DACs or 40G/100G optics with cables. • nputool -i -t 1 -T cpu_adj • nputool --init --test 1 --traffic cpu_adj root@amazon:/opt/ngos/bin# .
Connect the first two ports to IXIA and all the remaining ports with DACs or 40G/100G optics with cables. • nputool –i –t 1 –T ixia_adj • nputool --init --test 1 --traffic ixia_adj The above commands configure the VLAN and after the BCM.0> shell displays. To verify the counters, run the show c command in the BCM shell. CPU Traffic with External Loopback for Uplink Ports (SFP+) Traffic is sent from the CPU to the SFP+ ports. Connect all the ports with the SFP+ optics with TX and RX shorted.
PCI unit 0: Dev 0xb960, Rev 0x01, Chip BCM56960_A0, Driver BCM56960_A0 sysconf_probe successful global_sal_config successful *** 1 BCM devices are detected Current mode is now ESW Diag NPU initialization over Test link_status_test for NPU 0 ................ SKIPPED <<<--Test snake_traffic_test for NPU 0 .............. SKIPPED <<<--Test prbs_mac_test for NPU 0 ................... Passed Test prbs_ext_test for NPU 0 ................... SKIPPED <<<--Test uplink_link_status_test for NPU 0 .........
7 38.4 41.3 ------------------------Average 39.8, maximum peak 43.8 root@dell-diag-os:/opt/ngos/bin# root@dell-diag-os:/opt/ngos/bin# nputool --init --show temp DMA pool size: 67108864 PCI unit 0: Dev 0xb960, Rev 0x01, Chip BCM56960_A0, Driver BCM56960_A0 sysconf_probe successful global_sal_config successful *** 1 BCM devices are detected Current mode is now ESW Diag NPU initialization over NPU 0 Temperature ------------------------monitor current peak ------------------------0 40.4 42.8 1 40.4 42.8 2 39.
Output read Output root@dell-diag-os:~# nvramtool --read NVRAM Values: 0x00 0x9f 0x00 0xe6 0x03 0x01 0x00 0xea Test Status Fail Bits : offset 0x50 = 0x0 7 NVRAM test = 0 6 CFast test = 0 5 Reg check = 0 4 PCI test = 0 3 Upper DRAM test = 0 2 Lower DRAM test = 0 1 ECC test = 0 0 SPD test = 0 Test Status Pass Bits : offset 0x51 = 0x9f 7 NVRAM test = 1 6 CFast test = 0 5 Reg check = 0 4 PCI test = 1 3 Upper DRAM test = 1 2 Lower DRAM test = 1 1 ECC test = 1 0 SPD test = 1 RMT Control : offset 0x52 = 0x0 7: 4 U
Configuration File Format The nvramtool configuration file uses the device description format and is the same format as the pltool configuration file.
Output show=brief Output root@dell-diag-os:/etc/dn/diag# opticstool --show=brief Show Optics in System (brief) Port # Name Status ------ ------------1 QSFP28 1 PRESENT 2 QSFP28 2 PRESENT … show Output root@dell-diag-os:/etc/dn/diag# opticstool --show Show Optics in System Port # Name Status Type Part Number Rev Serial Number ------ ------------- ------- --------------- --- --------------1 QSFP28 1 PRESENT QSFP28 EL-13-08002-001 01 28-0197 2 QSFP28 2 PRESENT QSFP28 EL-13-08002-001 01 28-0319 … show --int=i
Part No: EL-13-08002-001 Revision: 01 Serial Num: 28-0197 ID : 0x11 Extended ID : 0x00 Connector : 0x23 Specification : 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 Encoding : 0x00 BR Nominal : 0xfa Length (9um) Km : 0x00 Length (9um) 100m : 0x00 Length (50um) 10m : 0x00 Length (62.5um) 10m : 0x00 Length (copper) 10m : 0x01 Cable Attenuation : 0x00 (2.5 Ghz) 0x00 (5.
– MUX settings to access the device • Reset — Hardware reset of the device.
• scan — Scans all the devices on the PCI bus and returns any device information that is found. • test — Checks the devices on the PCI bus against those that are defined in the configuration file. • show — Shows the configuration space information for the device. • read — Reads specific configuration bytes from the configuration space of a specified device (similar to show). • write — Writes a specific configuration byte in the configuration space of the specified device.
[00000040]: 0x01 0x00 || ................ [00000050]: 0x00 0x00 || .........p...... [00000060]: 0x00 0xe3 || ..^............. [00000070]: 0x70 0xe3 p.^.....@.@..... [00000080]: 0xd0 0xe4 || ..^.......@..... [00000090]: 0x04 0x00 || ..........^..... [000000a0]: 0xbf 0x3e || .>@..... .^..... [000000b0]: 0xf0 0xe3 || ..^............. [000000c0]: 0x30 0x34 04.0.tes........ [000000d0]: 0x2f 0x70 || /proc/bus/pci/00 [000000e0]: 0x2f 0x30 || /04.0.....^..... [000000f0]: 0x00 0x00 || ................
Tests The pltool tests specified registers and values SDI identifies in the testable bits of the register. The tool reads the register using SDI interfaces and compares the testable bits from those the SDI database provides. If a mismatch occurs, an error displays. CLI Options Dell Diag - Programable Logic Tool version 1.5, 1.
listdevicenames Output Based from the output of --devicenames, you can decide if you need to use the --devname= option in the read or write functions.
Configuration File Format The pltool uses the device tree configuration format.
Power Supply 1 Output Voltage(VOUT) : 12.210000 V Power Supply 1 Input Current(IIN) : 0.380000 A Power Supply 1 Output Current(IOUT) : 5.390000 A Power Supply 1 Input Power(PIN) : 75.000000 W Power Supply 1 Output Power(POUT) : 65.700000 W Power Supply 1 Temperature : 30.
SmartFusion (SMF) had two upgradable parts — Microcontroller subsystem (MSS) and field programmable gate array (FPGA), as shown in the following illustration. The online upgrade MSS images are in *.bin files. The online upgrade of FPGA image is in a *.dat file. The external upgrade of both MSS and FPGA is a *.pdb file. Figure 7. smarttool Upgradable MSS and FPGA SMF Upgrade Binaries • _SMF_MSS_V1.41_logic_V0.E_Release_Notes.xls • _SMF_MSS_v1.41_A_region.bin • _SMF_MSS_v1.
Upgrade mss A-region when mss is running in B-region: ./smarttool -um /dev/ _SMF_MSS_v1.41_A_region.bin 1 Copy all the binaries needed for the upgrade into a local directory. Figure 8. Copy All Needed Binaries 2 Check the MSS region using the smarttool –gmr /dev/ttyS0 command. Figure 9. Check the MSS Region 3 Check the MSS version using smarttool –gmv /dev/ttyS0 command. Figure 10.
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 11. Upgrade Using Region A 5 Ensure that MSS has upgraded successfully by using the smarttool –gmv /dev/ttyS0 command after the system reboots. Figure 12.
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 13. Copy the Needed Binaries 2 Check the FPGA region using smarttool –gfr /dev/ttyS0 command. Figure 14. Check the FPGA Region 3 Get the current version of the FPGA using the lpctool utility. You can get the FPGA running image version through the ./ lpctool --read --addr=0x200 --size=b registers at the LPC tool. Table 1.
4 Upgrade the FPGA in smartfusion using the # ./smarttool -uf /dev/ttyS0 / _SMF_logic_v0.E.dat command. You must be in region G to upgrade to region A. The device automatically reboots after the upgrade. Figure 16. Upgrade the FPGA 5 Verify that the FPGA is upgraded using the lpctool utility. You can get the FPGA running image version through the ./ lpctool --read --addr=0x200 --size=b registers of the LPC tool.
Output root@dell-diag-os:~# smbiostool --biosversion 3.23.0.5 root@dell-diag-os:~# smbiostool --biosflashdetect dmidecode -s system-version flashrom -V -p internal > /tmp/flhdet.txtFound Flash chip!!! Found Winbond flash chip "W25Q128.V" (16384 kB, SPI) at physical address 0xff000000.
Output list Output root@amazon:/opt/ngos/bin# ./storagetool --list Mounted Filesystem Devices: /dev/sda7 / ext4 test Output root@amazon:/opt/ngos/bin# ./storagetool --test --dev=/dev/sda7 Testing Storage Devices ............. Passed smart Output root@amazon:/opt/ngos/bin# ./storagetool --smart --dev=/dev/sda7 smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.14.0-rc8] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.
196 Reallocated_Event_Count 0x0000 100 100 016 Old_age Offline - 0 198 Offline_Uncorrectable 0x0000 100 100 050 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0000 100 100 050 Old_age Offline - 0 12 Power_Cycle_Count 0x0000 100 100 000 Old_age Offline - 157 241 Total_LBAs_Written 0x0000 100 100 000 Old_age Offline - 4696 242 Total_LBAs_Read 0x0000 100 100 000 Old_age Offline - 1267 160 Unknown_Attribute 0x0000 100 100 000 Old_age Offline - 0 161 Unknown_Attribute 0x0000 100 100 000 Old_age Offline - 142 163
Display this help and exit -V, --version, --copyright, --license Print license, copyright, and version information and exit -i, --info Show identity information for device --identify[=[w][nvb]] Show words and bits from IDENTIFY DEVICE data (ATA) -g NAME, --get=NAME Get device setting: all, aam, apm, lookahead, security, wcache, rcache, wcreorder -a, --all Show all SMART information for device -x, --xall Show all information for device --scan Scan for devices --scan-open Scan for devices and try to open each
-A, --attributes Show device SMART vendor-specific Attributes and values -f FORMAT, --format=FORMAT (ATA) Set output format for attributes: old, brief, hex[,id|val] -l TYPE, --log=TYPE Show device log.
bonnie++ bonnie++ is a test suite for storage devices that runs more comprehensive tests than the standard file system tests using the storagetool. You can run bonnie++ outside of the storagetool, but for logging purposes, Dell Networking recommends using bonnie++ within storagetool.
....................... Passed Temperature Sensor 2 temperature value is 45.7 C and temperature is ....................... Passed Temperature Sensor 3 temperature value is 17.2 C and temperature is ....................... Passed Temperature Sensor 4 temperature value is 17.7 C and temperature is ....................... Passed Temperature Sensor 6 temperature value is 21.6 C and temperature is ....................... Passed Temperature Sensor 9 temperature value is 22.2 C and temperature is .................
vmetool The CPLDupgradetool uses vmetool to upgrade CPLD. CLI Options root@dell-diag-os:/opt/dell/diag/bin# vmetool Lattice Semiconductor Corp. ispVME(tm) V12.2 Copyright 1998-2011. Outputs The following shows daisy chain programming of all in-system programmable devices. Usage: vme [option] vme_file [vme_file] Example: vme vme_file1.vme vme_file2.vme Example: vme -c | -cl | -ch Example: where sel_pin will be LOW for -cl option and HIGH for -ch Example: vme -c | -cl | -ch vme_file1.vme vme_file2.
Dell Diag cputool - version 1.1 package 1.10 2016/01/04 Dell Diag fantool - version 1.5 package 1.10 2016/01/04 Dell Diag gpiotool - version 1.4 package 1.10 2016/01/04 Dell Diag i2ctool - version 1.5 package 1.10 2016/01/04 Dell Diag ledtool - version 1.0 package 1.10 2016/01/04 Dell Diag lpctool - version 1.0 package 1.10 2016/01/04 Dell Diag memtool - version 1.5 package 1.10 2016/01/04 Dell Diag nputool - version 1.0 sdk-6.4.8 package 1.10 2016/01/04 Dell Diag nvramtool - version 1.5 package 1.
+ Checking Switch Brd EEPROM 0x50 ..... Passed + Checking Switch Brd CPLD 0x3e ..... Passed + Checking SFP1 EEPROM 0x50 ..... Passed + Checking SFP2 EEPROM 0x50 ..... Passed + Checking IOM_1 CPLD 0x3e ..... Passed + Checking IOM_1 EEPROM 0x50 ..... Passed + Checking IOM_1 QSFP1 Error reading at offset 0x00 ..... FAILED <<<--- 0x50 + Checking IOM_1 QSFP2 0x50 ..... Passed + Checking IOM_1 QSFP3 0x50 ..... Passed + Checking IOM_1 QSFP4 0x50 .....
+ Checking IOM_4 CPLD 0x3e ..... Passed + Checking IOM_4 EEPROM 0x50 ..... Passed + Checking IOM_4 QSFP1 0x50 ..... Passed + Checking IOM_4 QSFP2 0x50 ..... Passed + Checking IOM_4 QSFP3 0x50 ..... Passed + Checking IOM_4 QSFP4 0x50 ..... Passed + Checking IOM_4 QSFP5 0x50 ..... Passed + Checking IOM_4 QSFP6 0x50 ..... Passed + Checking IOM_4 QSFP7 0x50 ..... Passed + Checking IOM_4 QSFP8 0x50 .....
Fan 2 speed is 3581 RPM Getting Details for Fan 3 Fan 3 is Present Fan 3 Air flow type is Front To Rear Fan 3 status Normal Fan 3 speed is 3577 RPM Getting Details for Fan 4 Fan 4 is Present Fan 4 Air flow type is Front To Rear Fan 4 status Normal Fan 4 speed is 3526 RPM Fan Controller Test LPC.................... Passed Fan Controller Test LPC....................
....................... Passed Temp Sensors: Overall test results -------------------- >>> FAILED Testing Programmable Devices: PL Tool test: IOM1CPLD: SW_SCRATCH.................... Passed IOM2CPLD: SW_SCRATCH.................... Passed IOM3CPLD: SW_SCRATCH.................... Passed IOM4CPLD: SW_SCRATCH.................... Passed CPLD1 .................... Passed SmartFusion FPGA .................... Passed bus:dev.fn 08:00.0 [00000000]: 0xee 0x10 0x21 0x70 0x07 0x00 0x10 0x00 0x00 0x00 0x00 || ..!p......
17 IOM2 QSFP PRESENT QSFP28 1PCP8 X0 LEO1513001M 18 IOM2 QSFP PRESENT QSFP28 1PCP8 X0 LEO1513002C 19 IOM2 QSFP PRESENT QSFP28 1PCP8 X0 LEO15130016 20 IOM2 QSFP PRESENT QSFP28 1PCP8 X0 LEO15130011 21 IOM2 QSFP PRESENT QSFP28 1PCP8 X0 LEO1513008D 22 IOM2 QSFP PRESENT QSFP28 1PCP8 X0 LEO1513009X 23 IOM2 QSFP PRESENT QSFP28 1PCP8 X0 LEO1513009P 24 IOM2 QSFP PRESENT QSFP28 1PCP8 X0 LEO1513009R 33 IOM3 QSFP PRESENT QSFP28 1PCP8 X0 LEO15130091 34 IOM3 QSFP PRESENT QSFP28 1PCP8 X0 LEO151300AL 35 IOM3 QSFP PRESENT Q
Firmware download through MDIO success Starting Firmware download through MDIO, it takes few seconds... Firmware download through MDIO success Starting Firmware download through MDIO, it takes few seconds... Firmware download through MDIO success Starting Firmware download through MDIO, it takes few seconds... Firmware download through MDIO success Starting Firmware download through MDIO, it takes few seconds...
ERROR: ERROR: ERROR: ERROR: ERROR: ERROR: ERROR: ERROR: ERROR: ERROR: ERROR: ERROR: ERROR: ERROR: ERROR: ERROR: npu_link_status_test[61]: ERROR: NPU 0 - Port 106 is DOWN npu_link_status_test[61]: ERROR: NPU 0 - Port 107 is DOWN npu_link_status_test[61]: ERROR: NPU 0 - Port 6 is DOWN npu_link_status_test[61]: ERROR: NPU 0 - Port 115 is DOWN npu_link_status_test[61]: ERROR: NPU 0 - Port 82 is DOWN npu_link_status_test[61]: ERROR: NPU 0 - Port 83 is DOWN npu_link_status_test[61]: ERROR: NPU 0 - Port 81 is DOW
storagetool --list nputool -i -t 0 root@dell-diag-os:/etc/dn/diag# cat default_eda_extended_script.cfg ledtool --test Do not modify the default scripts as they are used as tests for the general health status of the switch. Instead, you can write your own scripts and use them through edatool using the --config= and --extended-config= parameters, as shown. root@dell-diag-os:/etc/dn/diag# edatool --config=/etc/dn/diag/eda.
6 Technical Support This chapter contains the following sections: • Dell Support • Contacting the Technical Assistance Center • Requesting a Hardware Replacement Topics: • Dell Support • Contacting the Technical Assistance Center • Requesting a Hardware Replacement Dell Support Dell Support provides a range of documents and tools to assist you with effectively using Dell Networking equipment and mitigating the impact of network outages.
Managing Your Case Log in to Dell Support and select the Service Request tab to view all open cases and Return Materials Authorizations (RMAs). Technical Documentation Log in to Dell Support and select the Documents tab. You can access this page without logging in using the Documentation link on the Support page. Contact Information Web: http://www.dell.com. Email: Networking-Support@Dell.com Telephone: • US and Canada: 1.866.965.5800 • International: +1.800.456.
