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....................................................................................................................7 2 Installation Instructions for ONIE and the Dell OS............................
Tests.......................................................................................................................................35 CLI Options.......................................................................................................................... 35 Output...................................................................................................................................36 Configuration File Format...................................................................
memtool..................................................................................................................................... 57 Tests.......................................................................................................................................57 CLI Options.......................................................................................................................... 58 Outputlist Output.......................................................................
Upgrading SMF MSS...........................................................................................................82 Upgrading SMF FPGA.........................................................................................................85 smbiostool................................................................................................................................. 86 CLI Options.........................................................................................................
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.
• Dell Release Notes About this Guide 8
2 Installation Instructions for ONIE and the Dell OS This chapter describes the different methods to install ONIE and the Dell Networking OS on your system. Topics: • Installing the DIAG-OS • Installing ONIE and the DIAG OS • ONIE Service Discovery and OS Installation • Installing ONIE from the BIOS Installing the DIAG-OS To install the DIAG-OS, use the following steps. NOTE: If you have a recovery USB plugged into your system, you must remove it prior to installing the DIAG-OS.
• Installing the DIAG-OS — Install the DIAG-OS from the ONIE prompt. Ensure that your TFTP server is reachable over your network. • The ONIE operates using a 115200 baud rate. Ensure that any equipment attached to the serial port can support the required 115200 baud rate. 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.
To assign an IP address to the management interface (eth0) and verify network connectivity, use the ifconfig eth0 command, as shown in the following example. ONIE:/ # ifconfig eth0 n.n.n.n/n UP Verify the network connection with ping. ONIE:/ # ping n.n.n.n 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 Installing ONIE from the BIOS There are two options for installing ONIE from the BIOS.
onie-recovery-x86_64 100% |*******************************| 18432k ONIE:/mnt # 2 0:00:00 ETA Create a bootable USB using the ONIE .iso image. ONIE:/mnt # dd if=onie-recovery-x86_64-dell__-r0.iso of=/dev/sdb bs=10 M 1+1 records in 1+1 records out 18874368 bytes (18.0MB) copied, 0.025707 seconds, 700.2MB/s ONIE:/mnt # 3 Insert your USB device in the target system. 4 Power up the target system and enter the BIOS configuration menu.
9 The BIOS boots from the ONIE Recovery USB device. In the Grub menu, select the ONIE: Embed ONIE option, as shown. Figure 3. ONIE: Embed ONIE Option 10 This installs ONIE on the disk and reboots the system to regular ONIE mode. The following shows detailed logs using the Embed ONIE option on a Dell Networking S6000 platform: Loading vmlinuz...... Loading initrd.xz................ready. Linux version 3.2.35-onie+ (lsharma@netlogin-eqx-03) (gcc version 4.7.3 (crosstool-NG 1.19.0 - ONIE-n.n.n.
Sent SIGTERM to all processes Sent SIGKILL to all processes Requesting system reboot sd 4:0:0:0: [sda] Synchronizing SCSI cache Restarting system. machine restart BIOS (Dell, Inc.) Boot Selector n.n.n.
11 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.02~beta2+e4a1fe391 +------------------------------------+ |*ONIE: Install OS | | ONIE: Rescue | | ONIE: Uninstall OS | | ONIE: Update ONIE | | ONIE: Embed ONIE | | | | | | | | | | | | | | | +------------------------------------+ Use the ^ and v keys to select which entry is highlighted.
sd 6:0:0:0: [sdb] Assuming drive cache: write through sd 6:0:0:0: [sdb] No Caching mode page present sd 6:0:0:0: [sdb] Assuming drive cache: write through sd 6:0:0:0: [sdb] Attached SCSI removable disk DHCPv4 on interface: eth0 failedONIE: Using default IPv4 addr: eth0: 192.168.3.10/255.255.255.0 Starting: dropbear ssh daemon... done. Starting: telnetd... done. discover: installer mode detected. Running installer. Starting: discover... done. Please press Enter to activate this console.
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.
. . . Please press Enter to activate this console. Info: eth0: Checking link... up. Info: Trying DHCPv4 on interface: eth0 To check the install status inspect /var/log/onie.log. Try this: tail -f /var/log/onie.log ** ONIE Update Mode Enabled ** ONIE-RECOVERY:/ # ONIE-RECOVERY:/ # ONIE-RECOVERY:/ # DHCPv4 on interface: eth0 failedONIE: Using default IPv4 addr: eth0: 192.168.3.10/255.255.255.
POST Upper DRAM Memory test SpeedStep enabled, Processor Bus Ratio=10, Vid=4b Short memory cell test Perf cnt (curr/fixed): b903308/b9034a8 POST Upper DRAM Memory test ................. PASS POST Upper DRAM ECC check ................... PASS POST PCIe test .............................. PASS POST NVRAM check ............................ PASS POST overall test results ................... PASS Version 2.15.1236. Copyright (C) 2012 American Megatrends, Inc.
16 Change the BIOS from the boot device to the mSATA. Figure 6. Changing From Boot to the mSATA 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.
Or service dnsmasq stop service dnsmasq start 15 If you see a port-specific error when you start dnsmasq; for example: Port 53 already in use. find the process ID of the process using the specific port (in this example, Port 53) and stop the port. Start dnsmasq again and check that it starts correctly. The DHCP/TFTP server is now ready for the ONIE target.
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.
• kernel_cmdline • runtime-export-env • runtime-process • runtime-set-env • log/messages • log/onie.log 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.
Product Name Device Version Label Revision Manufacturer Country Code Vendor Extension MAC Addresses Vendor Name Diag Version Part Number Service Tag Base MAC Address Platform Name ONIE Version CRC-32 Checksum is valid. ONIE:/ # 0x21 0x26 0x27 0x2B 0x2C 0xFD 0x2A 0x2D 0x2E 0x22 0x2F 0x24 0x28 0x29 0xFE 8 1 3 5 2 1 2 4 5 6 7 6 26 8 4 0 X01 77931 CN 0x00 384 DELL 01.10 0GTX3X 19HTG02 4C:76:25:F4:F0:00 x86_64-dell__c2538-r0 n.n.n.n 0xD7A4DFB2 Example of the onie-sysinfo —a command.
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.
NOTE: In Install mode, the DIAG-OS installation removes any existing NOS and DIAG-OS partition. If you do not create file /tmp/diag_os_install_mode, the DIAG-OS installs in Upgrade mode. In this case, the installation process does NOT touch any existing NOS.
Superblock backups stored on blocks: 32768, 98304, 163840, 229376 Allocating group tables: done Writing inode tables: done Creating journal (8192 blocks): done Writing superblocks and filesystem accounting information: done Preparing /dev/sda3 EDA-DIAG for rootfs install Preparing Diag-OS file system : dev /dev/sda3 mnt dir /boot untaring into /boot Success: Support tarball created: /boot/onie-support.tar.
CPGC Memtest ................................ PASS POST: RTC Battery OK at last cold boot RTC date Thursday 9/17/2015 19:04:51 POST SPD test ............................... PASS POST Lower DRAM Memory test .... Perf cnt (curr,fixed): 0x1DA5A3316,0x3B4B47B00 POST Lower DRAM Memory test ................. PASS 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 .......
[ [ [ [ [ [ OK OK OK OK OK OK ] ] ] ] ] ] [ OK ] [ OK ] [ [ [ OK OK OK ] ] ] [ OK ] [ OK ] [ OK ] [ OK ] [ OK ] [ OK ] [ [ [ [ [ OK OK OK OK OK ] ] ] ] ] [ OK ] Found device /dev/ttyS1. Started LSB: Raise network interfaces.. Reached target Network. Reached target System Initialization. Reached target Timers. Reached target Basic System. Starting OpenBSD Secure Shell server... Started OpenBSD Secure Shell server. Starting Regular background program processing daemon...
a b c d Boot into the Diag OS. Login as root. Install the EDA-DIAG tools package. Run /opt/ngos/bin/edatool. NOTE: To return to your networking operating software, enter the reboot command. Using the Dell Diagnostic Test Suite To run the Dell diagnostic test suite, use the following command after the system boots up. To run the Dell diagnostic test suite, select the EDA-DIAG option. NOTE: Use the up and down arrow keys to select which entry is highlighted.
CPLD 1 VERSION ========================= 0x3 ========================= CPLD 2 VERSION ========================= 0x02 ========================= CPLD 3 VERSION ========================= 0x02 ========================= CPLD 4 VERSION ========================= 0x02 Installing or Upgrading DIAG Tools in the Dell DIAGs OS To install or upgrade the DIAGs in the Dell DIAGs OS, use the dpkg -i dn-diags-DiagOS-1.10.deb command. root@dell-diag-os:~# dpkg -i dn-diags--DiagOS-1.10.
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. GNU GRUB version 2.
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.
• temptool • vmetool • edatool • Diagnostic Packaging 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.
========================= CPLD 2 VERSION ========================= 0x02 ========================= CPLD 3 VERSION ========================= 0x02 ========================= CPLD 4 VERSION ========================= 0x02 root@dell-diag-os:/opt/ngos/bin# ./cpldupgradetool --write final.vme File final.vme exists!! Valid CPLD Binary file size 0.998490MB Writing CPLD Binary File: final.vme ......
--readmsr <--cpu=cpuNumber> <--reg=regOffset> := read cpu register --writemsr <--cpu=cpu number> <--reg=reg offset> <--val=value> := Write cpu register --readlpc <--reg=reg> <--size=size> := read the specified register in lpc bus --writelpc <--reg=reg> <--val=value> <--size=size> := write at the specified register in lpc bus • • cpuid — Displays information about the CPU, for example, the processor name and number, codename, real-time measurement of each core’s internal frequency, memory frequency, and ca
Value at lpc register 0x102 : 0xde root@dell-diag-os:~# ./cputool --writelpc --reg=0x102 --val=0xab Size of read or write is set to be a byte Value 0xab written at lpc register 0x102 root@dell-diag-os:~# ./cputool --readlpc --reg=0x102 Size of read or write is set to be a byte Value at lpc register 0x102 : 0xab Configuration File Format There is no configuration file associated with the cputool. eepromtool To program the type, length, value (TLV) format EEPROMs, use the eepromtool.
• faneepromdump — Allows you to dump the fan eeprom. • eeprom — This option is provided every time you access the EEPROM. • show — Shows the types and values of the EEPROM you specify. • erase — Erases the contents of the EEPROM. Only the CRC value is available after erasing the EEPROM contents. • test — Allows you to verify the MAC address in the system-eeprom and the mac-eeprom. • get — Retrieves a particular value in the specified EEPROM. • set — Sets the values for the specified EEPROM.
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_DellPartNumber************* Registers 0x285 - 0x28a 0XTVK2 ************PSU2_MfgID************* Registers 0x28b - 0x28f 0XTVK ************PSU2_MfgDate************* Registers 0x290 - 0x297 150102 ************PSU2_Ser
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. The order of the fields are: 1 Name of the EEPROM.
0x00 0x00 0x00 0x00 |-| |-| |-| |-| 0xe8 0xed 0xf1 0xf2 | | | | 5 4 1 5 | | | | Power Source Power Wattage Num Fans Fan Speed 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.
The fantool uses long options which requires two hyphens in front of the options. Options are required, optional, or none. If you require a parameter, specify it and include an equal sign; if a parameter is optional, enclose it with square brackets to show that it is optional (but do not type the brackets at the CLI). For example, --fan is optional and enter it as --fan=1 or --fan=all, and so forth. Parameters with angle brackets are required but have multiple options for the input.
Configuration File Format This section shows if the fans are controlled by an LPC device such as a field programmable gate array (FPGA). D - Data Description # - The zero based number for this fan Descriotion - The Readable fan description Presence Bit Mask Register Offset Status Bit Mask Airflow Bitmask Speed Register Offset Speed Register Size R - Register description Offset of Register Size in bytes Register Name The section is MUX information when accessing the LPC and the timeout value.
For devices such as the complex programmable logic device (CPLD) or field programmable gate arrays (FPGA), gpiotool accesses those devices to drive the GPIO lines using the standard bus interfaces such as i2c, mem, or pci. CLI Options ./gpiotool - GPIO Tool version 2.0 admin, 2014-10-01, bamboo-build-num Syntax: .
get Output root@amazon:/opt/ngos/bin# ./gpiotool --get --pin=1 GPIO pin # 1 is 1 set Output root@amazon:/opt/ngos/bin# ./gpiotool --set --pin=1 --val=1 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.
to 0x7f on all i2c busses 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: .
30: 40: 50: 60: 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: -- -- -- -- -- -- -- -- 18 -- -20: -- -- -- -- -- -- -- -- -- -- -30: 30 -- -- -- -- -- -- -- -- -- -40: -- -- -- -- -- -- -- -- -- -- -50: 50 -- -- -- -- -- -- -- -- -- -60: -- -- -- -- -- -- -- -- -- 69 -70: -- -- -- -- -- -- -- -- RR RR RR 0 1 2 3 4 5 6 7 8 9
+ Checking CPU Board EEPROM7 0x56 ..... Passed + Checking CPU Board EEPROM8 0x57 ..... Passed + 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 0x50 ..... Passed + Checking IOM_1 QSFP2 0x50 ..... Passed + Checking IOM_1 QSFP3 0x50 .....
+ Checking IOM_2 QSFP7 0x50 ..... Passed + Checking IOM_2 QSFP8 0x50 ..... Passed + Checking IOM_3 CPLD 0x3e ..... Passed + Checking IOM_3 EEPROM 0x50 ..... Passed + Checking IOM_3 QSFP1 0x50 ..... Passed + Checking IOM_3 QSFP2 0x50 ..... Passed + Checking IOM_3 QSFP3 0x50 ..... Passed + Checking IOM_3 QSFP4 0x50 ..... Passed + Checking IOM_3 QSFP5 0x50 ..... Passed + Checking IOM_3 QSFP6 0x50 ..... Passed + Checking IOM_3 QSFP7 0x50 .....
0x00 0x00 0x31 0x32 0x00 0xff 0xff 0xff 0xff 0xff 0x00 0x00 0x38 0x20 0x00 0xff 0xff 0xff 0xff 0xff 0x00 0x00 0x4b 0x45 0x00 0xff 0xff 0xff 0xff 0xff 0x00 0x00 0x53 0x32 0x00 0xff 0xff 0xff 0xff 0xff 0x00 0x00 0x46 0x80 0x00 0xff 0xff 0xff 0xff 0xff 0x00 0x80 0x31 0x2c 0x00 0xff 0xff 0xff 0xff 0xff 0x00 0x2c 0x47 0x00 0x00 0xff 0xff 0xff 0xff 0xff 0x00 0x0f 0x37 0x00 0x00 0xff 0xff 0xff 0xff 0xff 0x00 0x13 0x32 0x00 0x00 0xff 0xff 0xff 0xff 0xff 0x00 0x35 0x48 0x00 0x00 0xff 0xff 0xff 0xff 0xff 0x
PSU2 ,/dev/i2c-2,0x70:0x0:0x9:0x74:0x1:0xb:0x73:0x0:0x0:0x72:0x2:0x2,0x58,0x00,1 FAN1 EEPROM ,/dev/i2c-2,0x70:0x0:0x9:0x74:0x1:0xb: 0x73:0x0:0x0:0x72:0x4:0x4,0x50,0x00,1 FAN2 EEPROM ,/dev/i2c-2,0x70:0x0:0x9:0x74:0x1:0xb: 0x73:0x0:0x0:0x72:0x8:0x8,0x50,0x00,1 FAN3 EEPROM ,/dev/i2c-2,0x70:0x0:0x9:0x74:0x1:0xb: 0x73:0x0:0x0:0x72:0x10:0x10,0x50,0x00,1 FAN4 EEPROM ,/dev/i2c-2,0x70:0x0:0x9:0x74:0x1:0xb: 0x73:0x0:0x0:0x72:0x20:0x20,0x50,0x00,1 Front Panel GE TMP ,/dev/i2c-2,0x70:0x0:0x9:0x74:0x1:0xb: 0x73:0x0:0x0:
• set — Sets the state of an LED. If you have multiple instances of an LED, such as fans, specify which instance of that entity you want to set. Value is only valid for stack numbers or other seven-segment LED displays.
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
get Output root@dell-diag-os:~# ledtool --get Platform Stacking Led : off Power Led : green Fan Led : green 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 Front
IOM4 Module StatusLed : flashing-green IOM4 Module BeaconLed : off root@dell-diag-os:~# ledtool --set --state=off root@dell-diag-os:~# ledtool --get Platform Stacking Led : off Power Led : off Fan Led : off 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 Modul
• Value — The value to write to this bit or set of bits. [Power] Power Led [off] 1 | 6:5 | [/off] [green] 1 | 6:5 | [/green] [yellow] 1 | 6:5 | [/yellow] [/Power] | lpc | 0x020a | 0x0 2 0 1 lpctool To access devices on the LPC bus, use the lpctool. The lpctool allow access on the LPC bus by using I/O transactions at the processor level. This access does not include LPC interfaces in other devices. Other DiagOS tools use lpctool to read LPC-connected registers.
write Output root@dell-diag-os:/opt/ngos/bin# ./lpctool --write --addr=102 --val=10 memtool The memtool tests the physical memories in the system. The memtool performs address bus and data tests that moves 1s or 0s through the bus lines to detect stuck, missing, bridged, or other issues found during board tests. The tool also places hamming values or addresses into memory to test and report failing bits. All tests are similar to the memtest86 application but are available through the CLI.
portions of these patterns in the memory to fill the memory and as Hamming patterns (such as Hamming [8,4], Hamming[16,11], Hamming[32,26] or Hamming[64,57]) encoding with the additional most significant byte (MSB) parity bit to cover the parity bits in the Hamming code. This allows for detecting multiple bit errors. • Data Cache — Performs a rotation of a 16MB array in four clockwise rotations for 16 iterations of the complete rotation.
• Write — Writes to a physical memory address to test write cycles and memory. Similar to the Read command, this command takes a region, address in that region, and a comma-separated list of values to write.
0x44 0x31 || NLQ1G7235107C-D1 [00000090]: 0x32 0x54 0x48 0x41 0x00 0x00 || 2THA............ [000000a0]: 0x00 0x00 0x00 0x00 0x00 0x00 || ................ [000000b0]: 0x00 0x00 0x00 0x00 0x00 0x00 || ................ [000000c0]: 0x00 0x00 0x00 0x00 0x00 0x00 || ................ [000000d0]: 0x00 0x00 0x00 0x00 0x00 0x00 || ................ [000000e0]: 0x00 0x00 0x00 0x00 0x00 0x00 || ................ [000000f0]: 0x00 0x00 0x00 0x00 0x00 || ...............
Constraints You cannot perform memory tests while other tests that allocate and use memory within the region are performing. However, you can perform Read tests concurrently with other processes. You cannot run multiple memory tests at the same time as they may collide within the memory spaces. Memory tests cannot test all the memory, and without cache flushes, memory tests may not get out of the caches. The SDI must ensure the memory accessed is accessing the physical memory. This slows down the tests.
• 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. • DATA_SLIDING0 — Sliding a 0 through the data lines. • DATA_PATTERN — Writing and reading patterns from the memory. • • DATA_CACHE — Exercises the RAM by completing cache evictions by rotating a very large array, usually cache-line size square, of the values in memory multiple times.
Usage: .
NPU tests ....................................... Passed root@dell-diag-os:/opt/ngos/bin# 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 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 .......... 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 .....
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. Default pre-emphasis for Port-1 (ce0) and Port-2 (ce1) connected to IXIA: 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.
Connect ports with Loopback cables and run the PRBS MAC and EXT Loopback tests.
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 40.4 42.3 3 38.4 42.3 4 40.8 43.8 5 40.8 42.8 6 38.9 42.3 7 38.4 41.3 ------------------------Average 39.8, maximum peak 43.
and how the tests are performed. The nvramtool controls both the BIOS and EDA for testing. The bits are not common across platforms and are defined in the configuration file. When using this tool, you must write the correct bits because the tool does not know the details of the registers it is writing. The nvramtool can display the bit-level detail in the NVRAM registers, depending on how you define it in the configuration file. Tests There are no tests of the NVRAM. This tool only controls the bits.
7: 4 Undefined = 0 3 RMT Test Enable = 0 2: 0 Loop 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 = 0x1 5: 4 EDA Verbose Level = 0 3 EDA Extended Tests = 0 2 EDA Verbose Mode = 0 1 EDA Stop on Error = 0 0 EDA Enable = 1 EDA Extra Bits : offse
B | B | B | … 2 | Lower DRAM test | RO | 0x0 1 | ECC test | RO | 0x0 0 | SPD test | RO | 0x0 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 Dell Diag - Optics Tool version 2.
… 1 2 QSFP28 1 QSFP28 2 PRESENT QSFP28 PRESENT QSFP28 EL-13-08002-001 EL-13-08002-001 01 01 28-0197 28-0319 show --int=interface # Output root@dell-diag-os:/etc/dn/diag# opticstool --show --int=1 Show Optics in System ======================================= QSFP28 1 Detailed Display ======================================= Link Status ---------------------------------------Port Status Loss of Signal : RX Signal Lock Error : PCS Link State : Link Faults : Remote : Local : Idle Error : Illegal Symbol :
Options BR Max BR Min Date Code CheckCodeExt TX Output Disable : : : : 2014-09-29 : 0x0e (0x0e) : Not Disabled ---------------------------------------Diagnostics Information ---------------------------------------Module Monitoring Values: Current Temp: 19.000 (Celsius) Supply Volts: 0.000 (Volts) Channel Monitoring Values: Recv: 0.000 0.000 Bias: 0.000 0.000 0.000 0.000 0.000 0.
• Data: • Bus to use to access the device • Address of device on the bus • MUX settings to access the device # portnum|Name # Present|dev|addr|reg|bit(s)|p_val|pres Mux type|mux addr|mux reg|mux setting # Select|mux bus|addr|reg|val|slect mux|s_mux addr|s_mux reg|s_mux val # Data|device bus|device addr|device mux type|mux addr|mux reg|mux setting|mux2 ...
• • • • • 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.
[00000000]: 0x60 0x27 0xc7 0xa6 0x00 0x00 || `'.............. [00000010]: 0x38 0x02 0x00 0x00 0x00 0x00 || 8........?@..... [00000020]: 0x60 0x27 0xc7 0xa6 0x00 0x00 || `'.............. [00000030]: 0x00 0xe3 0x5e 0x9e 0x00 0x00 || ..^......?@..... [00000040]: 0x01 0x00 0x00 0x00 0x00 0x00 || ................ [00000050]: 0x00 0x00 0x00 0x00 0x00 0x00 || .........p...... [00000060]: 0x00 0xe3 0x5e 0x9e 0x00 0x00 || ..^............. [00000070]: 0x70 0xe3 0x5e 0x9e 0x00 0x00 || p.^.....@.@.....
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. The tool uses the CLI to list the devices and their registers, and allows you to read and write registers in the device. The read functionality prints the details to the bit level and also any bit groupings and their meanings. The tool uses the SDI interface to get a list of devices and registers in the system, and then uses SDI to access the devices.
Output list Output root@dell-diag-os:/etc/dn/diag# 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 BOARD_TYPE bits:8 RO val:0xff mask:0xff test:0 ver:0x0 7:0 BOARD_TYPE RO 0x1 0x102 SW_SCRATCH bits:8 RW val:0xde mask:0xff test:1 ver:0x0 7:0 SW_SCRATCH RW 0xde 0x103 CPLD_ID bits:8 RO val:0xff mask:0xff test:0 ver:0x0 7:0 CPLD_ID RO 0x1 listdevicenames Output Based from the output of --devicenames, you can decide if
0 QSFP1_ModeSel = 1 root@dell-diag-os:/opt/ngos/bin# ./pltool --read --devname=CPLD1 --reg=0x101 BOARD_TYPE : offset 0x101 = 0x1 7: 0 BOARD_TYPE = 1 write Output ONIE:/diag # ./pltool --write --dev=0x33 --reg=0x0 --val=0x7f root@dell-diag-os:/opt/ngos/bin# ./pltool --write --devname=CPLD1 --reg=0x102 -val=0xfa root@dell-diag-os:/opt/ngos/bin# ./pltool --read --devname=CPLD1 --reg=0x102 SW_SCRATCH : offset 0x102 = 0xfa 7: 0 SW_SCRATCH = fa test Output ONIE:/diag # .
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 Power Power Power Power Power Power Supply Supply Supply Supply Supply Supply Supply 2 2 2 2 2 2 2 Output Voltage(VOUT) : 12.190000 V Input Current(IIN) : 0.440000 A Output Current(IOUT) : 6.400000 A Input Power(PIN) : 87.000000 W Output Power(POUT) : 77.200000 W Temperature : 30.
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.41_B_region.bin • _SMF_MSS_v1.41_G_region.bin • _SMF_MSS_v1.41_logic_v0.E.pdb Upgrading SMF MSS You can upgrade SMF MSS using the following steps.
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.
--biosdumpfields [SUBOPT] := Check whether the SPI flash was detected SUBOPT for --biosdumpfields : -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 FILE := Dump the DMI data to a binary file --from-dump FILE := Read the DMI data from a binary file -V := Display the version of dmidecode binary Output root@dell-diag-os:~# smbiostool --biosversion 3.23.0.
Syntax: storagetool
=== START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED See vendor-specific Attribute list for marginal Attributes. 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: ( 0) seconds. Offline data collection capabilities: (0x00) Offline data collection not supported.
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.03 ------Sequential Output------ --Sequential Input- --Random-Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks-Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP amazon.
-q TYPE, --quietmode=TYPE (ATA) Set smartctl quiet mode to one of: errorsonly, silent, noserial -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, 3w are,N,hpt,L/M/N, megaraid,N, cciss,N, auto, test -T TYPE, --tolerance=TYPE (ATA) Tolerance: normal, conservative, permissive, verypermissive -b TYPE, --badsum=TYPE (ATA) Set action on bad checksum to one of: warn, exit, ignore -r TYPE, --report=TYPE Rep
-P TYPE, --presets=TYPE (ATA) Drive-specific presets: use, ignore, show, showall -B [+]FILE, --drivedb=[+]FILE (ATA) Read and replace [add] drive database from FILE [default is +/usr/etc/smart_drivedb.h and then /usr/share/smartmontools/drivedb.h] ============================ DEVICE SELF-TEST OPTIONS ===== -t TEST, --test=TEST Run test.
[-x number-of-tests] [-u uid-to-use:gid-to-use] [-g gid-to-use] [-q] [-f] [-b] [-p processes | -y] Version: 1.03 We run bonnie++ in the system using the parameters ./bonnie++ -u root:0 -s 400 -n 32 -r 200 -d /tmp temptool The temptool reads from the temperature devices and reports back the temperatures. The temperature sensors on the board are commonly connected through i2c busses.
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 .......................
CPU Errata Sensor|MAX6699|/dev/i2c-3|0x1a|2|/dev/i2c-3 0x73:0x0:0xff:0x2|-5|45|50| Rear to Front - Q6 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.
Syntax: edatool
+ Checking DDR3 VREF Tuning 0x2e ..... Passed + Checking SPD0 0x50 ..... Passed + 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 ..... Passed + Checking CPU Board EEPROM5 0x54 ..... Passed + Checking CPU Board EEPROM6 0x55 ..... Passed + Checking CPU Board EEPROM7 0x56 .....
+ Checking IOM_2 QSFP4 0x50 ..... Passed + Checking IOM_2 QSFP5 0x50 ..... Passed + Checking IOM_2 QSFP6 0x50 ..... Passed + Checking IOM_2 QSFP7 0x50 ..... Passed + Checking IOM_2 QSFP8 0x50 ..... Passed + Checking IOM_3 CPLD 0x3e ..... Passed + Checking IOM_3 EEPROM 0x50 ..... Passed + Checking IOM_3 QSFP1 0x50 ..... Passed + Checking IOM_3 QSFP2 0x50 ..... Passed + Checking IOM_3 QSFP3 0x50 ..... Passed + Checking IOM_3 QSFP4 0x50 .....
Power Supply 1 Temperature : 48.000000 C Power Supply 1 Fan Present Power Supply 1 Fan Status is Normal Power Supply 1 Fan Airflow Type is F2B Power Supply 1 Fan Speed(RPM) : 2576 Getting details of Power Supply 2 using LPC interface Power Supply 2 is Present Power Supply 2 Input Type DC Power Supply 2 Output Voltage High Power Supply 2 Output Voltage Low Power Supply 2 Type Mismatching Power Supply 2 Input Voltage(VIN) : 0.000000 V Power Supply 2 Output Voltage(VOUT) : 0.
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.......................
0x00 0x00 || .H#......`...... [00000050]: 0x00 0x00 0x00 0x00 0x00 0x00 || ................ [00000060]: 0x10 0x00 0x02 0x00 0x03 0x00 || ....)...'(...... [00000070]: 0x40 0x00 0x12 0x10 0x00 0x00 || @............... [00000080]: 0x00 0x00 0x00 0x00 0x00 0x00 || ................ [00000090]: 0x02 0x00 0x00 0x00 0x00 0x00 || ................ [000000a0]: 0x00 0x00 0x00 0x00 0x00 0x00 || ................ [000000b0]: 0x00 0x00 0x00 0x00 0x00 0x00 || ................ [000000c0]: 0x00 0x00 0x00 0x00 0x00 0x00 || ...
38 IOM3 QSFP PRESENT QSFP28 1PCP8 X0 LEO151300AN 39 IOM3 QSFP PRESENT QSFP28 1PCP8 X0 LEO1513008G 40 IOM3 QSFP PRESENT QSFP28 1PCP8 X0 LEO151300C0 49 IOM4 QSFP PRESENT QSFP28 1PCP8 X0 LEO151300AV 50 IOM4 QSFP PRESENT QSFP28 1PCP8 X0 LEO1513003M 51 IOM4 QSFP PRESENT QSFP28 1PCP8 X0 LEO1513002X 52 IOM4 QSFP PRESENT QSFP28 1PCP8 X0 LEO1513001Q 53 IOM4 QSFP PRESENT QSFP28 1PCP8 X0 LEO1513006G 54 IOM4 QSFP PRESENT QSFP28 1PCP8 X0 LEO1513003A 55 IOM4 QSFP PRESENT QSFP28 1PCP8 X0 LEO1513002Q 56 IOM4 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: ERROR: npu_link_status_test[61]: ERROR: NPU 0 - Port 75 is DOWN 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
i2ctool --test psutool --test --lpc fantool --test --lpc fantool --short-test --lpc fantool --get --fan=all --lpc temptool --test --lpc pltool --test opticstool --show memtool --test rtctool --test 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.
NOTE: If you do not need the Verbose mode settings to persist through reboots, you can use the environment variable method to enable Verbose Mode. export VERB_LEVEL= To clear the environment variable, use the unset VERB_LEVEL command. Diagnostic Packaging The diagnostic applications, libraries, and configurations are packaged in a debian package called dn-diags{PLATFORM}-{PACKAGE_VERSION}.deb.
6 Technical Support This chapter contains the following sections: • The Dell Support Website • 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.
Contacting the Technical Assistance Center How to Contact Dell Networking TAC Information to Submit When Opening a Support Case Log in to Dell Support at http://www.dell.com/support and select the Service Request tab.
• Shipping address for the replacement component, including a contact name, phone number, and email address.
