Hpe Moonshot System Troubleshooting Guide

Transcript

HPE Moonshot System Troubleshooting Guide Abstract This document describes common procedures and solutions for troubleshooting the HPE Moonshot System. This document is intended for the person who installs, administers, and troubleshoots the HPE Moonshot System. Hewlett Packard Enterprise assumes you are qualified to service computer equipment and are trained in recognizing hazards in products with hazardous energy levels. Part Number: 725258-003 September 2016 Edition: 3 © Copyright 2016 Hewlett Packard Enterprise Development LP The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein. Contents Getting started ..........................................................................................................................................6 Introduction ...............................................................................................................................................................6 Important safety information .....................................................................................................................................6 Symbols on equipment ..................................................................................................................................6 Warnings and cautions ..................................................................................................................................7 Electrostatic discharge ..................................................................................................................................7 Troubleshooting preparation .....................................................................................................................9 Prerequisites for diagnosis .......................................................................................................................................9 Collecting symptom information ...............................................................................................................................9 Preparing the HPE Moonshot System for diagnosis ..............................................................................................10 Diagnosing the HPE Moonshot System .................................................................................................................10 Component and LED identification .........................................................................................................11 Component LEDs ...................................................................................................................................................11 Chassis front panel LEDs and buttons ........................................................................................................11 Cartridge LEDs and buttons ........................................................................................................................12 Switch module button, sensor, and LEDs ...................................................................................................13 Moonshot-6SFP Uplink Module LEDs and buttons .....................................................................................14 Moonshot-4QSFP+ Uplink Module LEDs and buttons ................................................................................14 Moonshot-16SFP+ Uplink Module LEDs and buttons .................................................................................15 HPE Moonshot 1500 Chassis Management module LEDs and buttons .....................................................16 Device ports and connectors .......................................................................................................................16 Diagnostic flowcharts ..............................................................................................................................19 Chassis power-on problems ........................................................................................................................19 Cartridge troubleshooting ............................................................................................................................19 Switch troubleshooting ................................................................................................................................21 Hardware problems ................................................................................................................................24 General hardware problems ...................................................................................................................................24 Resolving loose connections .......................................................................................................................24 Moonshot system does not recognize new hardware .................................................................................24 Unknown problem........................................................................................................................................25 Power problems .....................................................................................................................................................26 Power source is not working........................................................................................................................26 Power supply issues ....................................................................................................................................26 Cartridge problems .................................................................................................................................................27 Cartridge reboots randomly .........................................................................................................................27 HPE Moonshot Remote Console Administrator overview ...........................................................................29 System battery.............................................................................................................................................29 Fan problems .........................................................................................................................................................29 General fan issues.......................................................................................................................................29 Hot-plug fan issues ......................................................................................................................................31 Drive problems (hard drives and solid state drives) ...............................................................................................31 Drives do not display ...................................................................................................................................31 Data is inaccessible .....................................................................................................................................31 Response time is slower than usual ............................................................................................................32 HPE Moonshot 1500 Chassis Management Module management interfaces .......................................................32 Moonshot 1500 CM Module network port locations ....................................................................................32 Serial port locations .....................................................................................................................................33 Software problems ..................................................................................................................................34 Operating system problems and resolutions ..........................................................................................................34 Operating system locks up ..........................................................................................................................34 Contents 3 Errors are displayed in the error log ............................................................................................................34 Issues occur after the installation of a service pack ....................................................................................34 Reconfiguring or reloading software ............................................................................................................35 Linux resources ...........................................................................................................................................35 Application software problems ...............................................................................................................................35 Software locks up ........................................................................................................................................35 Errors occur after a software setting is changed .........................................................................................36 Errors occur after the system software is changed .....................................................................................36 Errors occur after an application is installed ................................................................................................36 ROM problems .......................................................................................................................................................36 Boot problems .............................................................................................................................................36 Flashing ROM problems .........................................................................................................................................37 Show firmware revisions command shows 00/00/00 date...........................................................................37 Error message received when trying to update the ROM on a selected cartridge ......................................37 The ROM flash updates did not take affect after update .............................................................................37 Firmware updates ........................................................................................................................................37 UEFI BIOS Issues ..................................................................................................................................................38 Cannot download the file in the network boot URL .....................................................................................38 Cannot network boot from downloaded image file ......................................................................................38 Cannot deploy from the UEFI Shell script ...................................................................................................39 Software tools and solutions ...................................................................................................................40 Hewlett Packard Enterprise product QuickSpecs ...................................................................................................40 HPE Moonshot iLO Chassis Management Firmware .............................................................................................40 HPE Moonshot iLO CM Integrated Management Log .................................................................................40 HPE Moonshot iLO CM Event Log ..............................................................................................................40 HPE Insight Cluster Management Utility ................................................................................................................40 HPE Moonshot Component Pack ...........................................................................................................................41 Resources for troubleshooting ................................................................................................................42 Online resources ....................................................................................................................................................42 HPE Moonshot Information Library .............................................................................................................42 Product documentation................................................................................................................................42 Driver, firmware updates, and software updates .........................................................................................43 HPE Moonshot Videos ................................................................................................................................43 Product QuickSpecs ....................................................................................................................................43 White papers ...............................................................................................................................................43 Service notifications, advisories, and notices ..............................................................................................43 Subscription services...................................................................................................................................43 HPE Technology Service Portfolio ..............................................................................................................43 Product information resources ...............................................................................................................................44 Additional product information .....................................................................................................................44 Register the product ....................................................................................................................................44 Overview of product features and installation instructions ..........................................................................44 Key features, option part numbers ..............................................................................................................44 Cartridge configuration information .............................................................................................................44 Product and option specifications, symbols, installation warnings, and notices ..........................................45 HPE Moonshot System specifications, symbols, installation warnings, and notices ...................................45 Teardown procedures, part numbers, specifications ...................................................................................45 Teardown or removal and replacement procedure videos ..........................................................................45 Technical topics ...........................................................................................................................................45 Product installation resources ................................................................................................................................45 External cabling information ........................................................................................................................45 Power capacity ............................................................................................................................................45 LED functions, component installation instructions, and component identification .....................................46 Product configuration resources .............................................................................................................................46 Operating System Version Support .............................................................................................................46 Operating system deployment .....................................................................................................................46 HPE Moonshot System configuration information .......................................................................................46 Software installation and configuration of the HPE Moonshot System........................................................46 HPE Moonshot management ......................................................................................................................46 Contents 4 Error messages ......................................................................................................................................47 POST error messages ............................................................................................................................................47 Introduction to POST error messages .........................................................................................................47 MCU buffer unit has detected an error. .......................................................................................................47 Memory Controller Unit (MCU) has detected an error. ................................................................................47 RCEC has detected an error. ......................................................................................................................47 PCIe RP[1] has detected an error. ..............................................................................................................47 PCIe RP[2] has detected an error. ..............................................................................................................47 PCIe RP[3] has detected an error. ..............................................................................................................47 PCIe RP[4] has detected an error. ..............................................................................................................48 Error detected with the ROM image. ...........................................................................................................48 Error detected with drive 1...........................................................................................................................48 Error detected with drive 2...........................................................................................................................48 Fatal error detected and forced system reset! .............................................................................................48 Cartridge error detected in CPU subsystem ................................................................................................48 Cartridge error detected in memory subsystem ..........................................................................................48 Cartridge error detected in storage subsystem ...........................................................................................48 Cartridge error detected in network subsystem ...........................................................................................48 Cartridge error detected in I/O subsystem...................................................................................................49 Cartridge error detected in thermal subsystem ...........................................................................................49 Cartridge error detected in BIOS/Flash subsystem .....................................................................................49 Cartridge error detected in security subsystem ...........................................................................................49 Cartridge error detected in mezzanine subsystem ......................................................................................49 Cartridge error detected in power subsystem..............................................................................................49 Fatal error detected and forced system reset! .............................................................................................49 HPE iLO errors .......................................................................................................................................................50 Event log entries ..........................................................................................................................................50 Support and other resources ..................................................................................................................57 Accessing Hewlett Packard Enterprise Support .....................................................................................................57 Information to collect ...................................................................................................................................57 Accessing updates .................................................................................................................................................57 Websites .................................................................................................................................................................57 Service notifications ...............................................................................................................................................58 Acronyms and abbreviations...................................................................................................................59 Documentation feedback ........................................................................................................................61 Index .......................................................................................................................................................62 Contents 5 Getting started Introduction This guide provides common procedures and solutions for troubleshooting the HPE Moonshot System. Use this guide to troubleshoot the HPE Moonshot 1500 Chassis, along with supported cartridges and switches. Important safety information Familiarize yourself with the safety information in the following sections before troubleshooting the system. Important safety information Before servicing this product, read the Safety, Compliance, and Warranty Information document provided with the system. Symbols on equipment The following symbols may be placed on equipment to indicate the presence of potentially hazardous conditions. This symbol indicates the presence of hazardous energy circuits or electric shock hazards. Refer all servicing to qualified personnel. WARNING: To reduce the risk of injury from electric shock hazards, do not open this enclosure. Refer all maintenance, upgrades, and servicing to qualified personnel. This symbol indicates the presence of electric shock hazards. The area contains no user or field serviceable parts. Do not open for any reason. WARNING: To reduce the risk of injury from electric shock hazards, do not open this enclosure. This symbol on an RJ-45 receptacle indicates a network interface connection. WARNING: To reduce the risk of electric shock, fire, or damage to the equipment, do not plug telephone or telecommunications connectors into this receptacle. This symbol indicates the presence of a hot surface or hot component. If this surface is contacted, the potential for injury exists. WARNING: To reduce the risk of injury from a hot component, allow the surface to cool before touching. 81.65 kg 180.00 lb This symbol indicates that the component exceeds the recommended weight for one individual to handle safely. WARNING: To reduce the risk of personal injury or damage to the equipment, observe local occupational health and safety requirements and guidelines for manual material handling. Getting started 6 These symbols, on power supplies or systems, indicate that the equipment is supplied by multiple sources of power. WARNING: To reduce the risk of injury from electric shock, remove all power cords to disconnect power from the system completely. Warnings and cautions WARNING: Only authorized technicians trained by Hewlett Packard Enterprise should attempt to repair this equipment. All troubleshooting and repair procedures are detailed to allow only subassembly/module-level repair. Because of the complexity of the individual boards and subassemblies, no one should attempt to make repairs at the component level or to make modifications to any printed wiring board. Improper repairs can create a safety hazard. WARNING: To reduce the risk of personal injury or damage to the equipment, be sure that: • The leveling feet are extended to the floor. • The full weight of the rack rests on the leveling feet. • The stabilizing feet are attached to the rack if it is a single-rack installation. • The racks are coupled together in multiple-rack installations. • Only one component is extended at a time. A rack may become unstable if more than one component is extended for any reason. WARNING: To reduce the risk of electric shock or damage to the equipment: • Do not disable the power cord grounding plug. The grounding plug is an important safety feature. • Connect the power cord into a grounded (earthed) electrical outlet that is easily accessible at all times. • Disconnect the power cord from the power supply to disconnect power to the equipment. • Do not route the power cord where it can be walked on or pinched by items placed against it. Pay particular attention to the plug, electrical outlet, and the point where the cord extends from the chassis. 81.65 kg 180.00 lb WARNING: To reduce the risk of personal injury or damage to the equipment: • Observe local occupation health and safety requirements and guidelines for manual handling. • Obtain adequate assistance to lift and stabilize the chassis during installation or removal. • The chassis is unstable when not fastened to the rails. • When mounting the chassis in a rack, remove the power supplies and any other removable module to reduce the overall weight of the product, if needed. CAUTION: To properly ventilate the system, you must provide at least 7.6 cm (3.0 in) of clearance at the front and back of the server. CAUTION: The server is designed to be electrically grounded (earthed). To ensure proper operation, plug the AC power cord into a properly grounded AC outlet only. Electrostatic discharge Preventing electrostatic discharge To prevent damaging the system, be aware of the precautions you must follow when setting up the system or handling parts. A discharge of static electricity from a finger or other conductor may damage Getting started 7 system boards or other static-sensitive devices. This type of damage may reduce the life expectancy of the device. To prevent electrostatic damage: • Avoid hand contact by transporting and storing products in static-safe containers. • Keep electrostatic-sensitive parts in their containers until they arrive at static-free workstations. • Place parts on a grounded surface before removing them from their containers. • Avoid touching pins, leads, or circuitry. • Always be properly grounded when touching a static-sensitive component or assembly. Grounding methods to prevent electrostatic discharge Several methods are used for grounding. Use one or more of the following methods when handling or installing electrostatic-sensitive parts: • Use a wrist strap connected by a ground cord to a grounded workstation or computer chassis. Wrist straps are flexible straps with a minimum of 1 megohm ±10 percent resistance in the ground cords. To provide proper ground, wear the strap snug against the skin. • Use heel straps, toe straps, or boot straps at standing workstations. Wear the straps on both feet when standing on conductive floors or dissipating floor mats. • Use conductive field service tools. • Use a portable field service kit with a folding static-dissipating work mat. If you do not have any of the suggested equipment for proper grounding, have an authorized reseller install the part. For more information on static electricity or assistance with product installation, contact an authorized reseller. Getting started 8 Troubleshooting preparation Prerequisites for diagnosis Review the following steps before preparing the HPE Moonshot system for diagnosis. 1. Review the important safety information (on page 6). 2. Gather symptom information ("Collecting symptom information" on page 9). 3. Prepare the HPE Moonshot System for diagnosis ("Preparing the HPE Moonshot System for diagnosis" on page 10). 4. To troubleshoot the HPE Moonshot System, use the Diagnostic flowcharts (on page 19). WARNING: To avoid potential issues, ALWAYS read the warnings and cautionary information in the product documentation before removing, replacing, reseating, or modifying system components. Collecting symptom information Before troubleshooting a problem, collect the following information: • Does the chassis power on? • Do the cartridges power on? • What do the health LEDs indicate for each component (chassis, switch, cartridge)? • Does the cartridge successfully boot an operating system? If not, does the cartridge display any of the following symptoms? • o An uncorrectable machine check exception o Linux kernel panic o A system “hang” o A system “freeze” If the problem occurs after an OS is installed: o Does the problem occur when a new application is loading? o What symptoms did the Moonshot System display when the malfunction occurred? For example, did it reboot? Were there LED codes, health logs, messages on the screen, and so forth? • When did the problem occur? Record exactly when the problem occurs, including the date and time. If it occurs more than once, keep a list of all symptoms for each occurrence. • What events preceded the failure? After which steps does the problem occur? • What has been changed since the time the Moonshot System was working? • Did you recently add or remove hardware or software? • How long has the system exhibited problem symptoms? • If the problem occurs randomly, what is the duration or frequency? • What failed, based on the HPE iLO CM Event Log or the HPE iLO CM IML? Troubleshooting preparation 9 To answer these questions, observe the LEDs and their statuses. For more information, see the cartridge user and maintenance guide or the HPE Moonshot 1500 Chassis Setup and Installation Guide on the Hewlett Packard Enterprise website (http://www.hpe.com/info/moonshot). Preparing the HPE Moonshot System for diagnosis 1. Verify that the system is in the proper operating environment with adequate power, air conditioning, and humidity control. For required environmental conditions, see "Product documentation (on page 42)." 2. Record any error messages displayed by the system. For more information about Moonshot iLO CM logs, see "HPE Moonshot iLO CM Integrated Management Log (on page 40)" or "HPE Moonshot iLO CM Event Log (on page 40)." 3. Collect all tools and utilities necessary to troubleshoot the problem, such as a Torx screwdriver, loopback adapters, ESD wrist strap, and software utilities. For product-specific information, Hewlett Packard Enterprise recommends that you have access to the product documentation (on page 42). Diagnosing the HPE Moonshot System 1. Review the iLO CM IML. For more information about iLO CM logs, see "HPE Moonshot iLO CM Integrated Management Log (on page 40)." 2. Record survey data. Troubleshooting preparation 10 Component and LED identification Component LEDs Common issues can be identified by reviewing the chassis, cartridge, switch module, and uplink module LEDs. For more information, see the documentation in the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). Chassis front panel LEDs and buttons Item Description LED Status 1 Chassis power LED 2 Chassis health LED 3 Chassis UID LED/button Flashing green = The chassis is waiting to power on. Green = Normal operation Amber = Standby operation Off = No power Green = Normal operation Flashing amber = Degraded condition Flashing red = Critical condition Off = No power Blue = Chassis ID is selected. Flashing blue = System firmware update is in process. Off = Chassis ID is not selected. 4 Cartridge health LEDs: • • • Left: Cartridges 1-18 Center: Cartridges 19-27 Right: Cartridges 28-45 5 Switch module A health LED 6 Switch module B health LED Green = Normal operation Amber = Standby mode Flashing amber = Degraded condition Flashing amber (All) = Moonshot 1500 CM module is not installed. Flashing red = Critical condition Off = Cartridge is not installed or no power exists. Green = Normal operation Flashing amber = Degraded condition Flashing red = Critical condition Off = Switch module is not installed or no power exists. Green = Normal operation Flashing amber = Degraded condition Flashing red = Critical condition Off = Switch module is not installed or no power exists. Component and LED identification 11 Cartridge LEDs and buttons Item Description Status 1 Cartridge power LED/button 2 Cartridge health LED 3 Drive LED Green = Normal operation Amber = Standby operation Off = No power Green = Normal operation Flashing amber = Degraded condition Flashing red = Critical condition Off = No power Green = Activity Off = No activity 4 Cartridge UID LED/button 5 Cartridge link LED/button Depending on the cartridge installed, there might be zero, one, or two drive LEDs. Blue = Cartridge ID is selected. Flashing blue = Cartridge firmware update is in progress. Off = Cartridge ID is not selected. Flashing white = Cartridges are linked. Off = Cartridge is not linked to other cartridges. The cartridge link LED flashes for 10 seconds after the link button is pressed. Component and LED identification 12 Switch module button, sensor, and LEDs Item Description 1 Switch module power LED 2 3 4 5 6 Status Green = Normal operation Amber = Standby operation Off = No power Switch module Green = Normal operation health LED Flashing amber = Degraded condition Flashing red = Critical condition Off = No power Switch module uplink Green = Link activity LED Flashing green = Activity Off = No activity Switch module Green = Link downlink activity Flashing green = Activity LED Off = No activity Switch module UID Solid blue = Switch module ID is selected. LED/button Flashing blue = Switch module firmware update is in progress. Off = Switch module ID is not selected. Access panel sensor Detects the presence of the access panel* *The fan speed adjusts automatically when the access panel is installed or removed. Component and LED identification 13 Moonshot-6SFP Uplink Module LEDs and buttons Item Description 1 Uplink module UID LED/button 2 3 4 5 Status Solid blue = Switch module ID is selected. Flashing blue = Switch module firmware update is in progress. Off = Switch module ID is not selected. Uplink module health Green = Normal operation LED Flashing amber = Degraded condition Flashing red = Critical condition Off = No power Uplink module link Solid green = Link LED Off = No link Uplink module Flashing green = Activity activity LED Off = No activity Reset button Resets the switch module Moonshot-4QSFP+ Uplink Module LEDs and buttons Component and LED identification 14 Item Description 1 Uplink module UID LED/button 2 3 4 5 Status Solid blue = Switch module ID is selected. Flashing blue = Switch module firmware update is in progress. Off = Switch module ID is not selected. Uplink module health Green = Normal operation LED Flashing amber = Degraded condition Flashing red = Critical condition Off = No power Uplink module link Solid green = Link LED Off = No link Uplink module Flashing green = Activity activity LED Off = No activity Reset button Resets the switch module Moonshot-16SFP+ Uplink Module LEDs and buttons Item Description 1 2 Reset button Uplink module UID LED/button 3 4 5 Status Resets the switch module Solid blue = Switch module ID is selected. Flashing blue = Switch module firmware update is in progress. Off = Switch module ID is not selected. Uplink module health Green = Normal operation LED Flashing amber = Degraded condition Flashing red = Critical condition Off = No power Bottom port Off = No link link/activity LED Solid green = 10Gb link Blinking green = Active 10Gb traffic Solid amber = 1Gb link Blinking amber = Active 1Gb traffic Top port link/activity Off = No link LED Solid green = 10Gb link Blinking green = Active 10Gb traffic Solid amber = 1Gb link Blinking amber = Active 1Gb traffic Component and LED identification 15 HPE Moonshot 1500 Chassis Management module LEDs and buttons Item Description Label 1 2 3 4 5 6 iLO CM management port link LED iLO CM management port activity LED iLO CM link port link LED iLO CM link port activity LED Moonshot 1500 CM module UID LED/button Moonshot 1500 CM module health LED iLO/MGMT iLO/MGMT LINK LINK — — Device ports and connectors Many Moonshot System troubleshooting processes require connection to the Moonshot 1500 CM module or the uplink module. For more information, see the documentation in the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). HPE Moonshot 1500 Chassis Management module components Item Description Label 1 iLO CM management port (Ethernet) iLO/MGMT iLO CM link port (disabled by default) LINK HPE Moonshot 1500 CM module HPE APM port Moonshot 1500 CM module diagnostic port RCM iLO CM management serial port — 2 3 4 5 DEBUG Component and LED identification 16 Item Description Label 6 Moonshot 1500 CM module USB connector — QR code MAC address Moonshot 1500 CM module microSD slot — 7 8 Moonshot-16SFP+ Uplink Module components Item Component Description 1 2 SFP+ ports X1–X16 Serial console port 1Gb or 10Gb Ethernet* For management *Ports X1–X16 support Ethernet traffic only. The following cables and transceiver modules are supported: • 10GBASE DAC SFP+ • 10GBASE-SR SFP+ • 1000BASE-T SFP • 1000BASE-SX SFP Use any available port to connect to the data center. Be sure the port is populated with a supported transceiver module that is compatible with the data center switch port type. For a list of supported transceivers, see the product QuickSpecs. Moonshot-4QSFP+ Uplink Module components Component and LED identification 17 Item Component Description 1 2 Serial console port QSFP+ ports Q1–Q4 For management 40Gb Ethernet QSFP+ ports Q1 through Q4 support Ethernet traffic only. QSFP+ ports support the following pluggable Ethernet transceiver modules: • HPE 40GBASE QSFP+ SR4 • HPE 40GBASE QSFP+ DAC • HPE 40GBASE QSFP+ to 4x10G SFP+ • HPE QSFP+/SFP+ Adapter Any available port can be used to connect to the data center. Ensure the port is populated with supported transceiver modules that are compatible with the data center port type. Moonshot-6SFP Uplink Module components Item Component Description 1 2 Serial console port SFP+ ports X1–X6 For management 1Gb or 10Gb Ethernet SFP+ ports X1 through X6 support Ethernet traffic only. SFP+ ports support the following pluggable Ethernet transceiver modules: • HPE 1000BASE-T SFP • HPE 1000BASE-SX SFP • HPE 10GBASE-SR SFP+ • HPE 10GBASE-DAC SFP+ Any available port can be used to connect to the data center. Ensure the port is populated with supported Hewlett Packard Enterprise transceiver modules that are compatible with the data center port type. Component and LED identification 18 Diagnostic flowcharts Diagnostic flowcharts are used to easily and effectively troubleshoot issues that may occur with the chassis, the cartridge, or the switch module. This guide contains the following flowcharts: • Chassis power-on problems (on page 19) • Cartridge power-on problems (on page 20) • Cartridge boot problems (on page 21) • Switch power problems (on page 22) • Switch connectivity problems (on page 23) Click the underlined text inside of the flowcharts to locate the appropriate information. Additionally, use the information in the section of this guide that relates to the issue to explain the issue or solution in further detail. Additional information can also be found using the resources provided on the Hewlett Packard Enterprise website. Chassis power-on problems Use this flowchart to troubleshoot chassis power-on problems. Cartridge troubleshooting Use the flowcharts in this section to troubleshoot cartridge power-on problems and cartridge boot problems. Diagnostic flowcharts 19 Cartridge power-on problems Diagnostic flowcharts 20 Cartridge boot problems Switch troubleshooting Use the flowcharts in this section to troubleshoot switch power problems and switch connectivity problems. Diagnostic flowcharts 21 Switch power problems Use this flowchart to troubleshoot switch power problems. Diagnostic flowcharts 22 Switch connectivity problems Use this flowchart to troubleshoot switch connectivity problems. Diagnostic flowcharts 23 Hardware problems Use this section to troubleshoot issues relating to hardware. This section may provide solutions to issues regarding hardware features not supported by the cartridge you are troubleshooting. General hardware problems Resolving loose connections Symptom The system does not power on. Cause • The power cords or cables are not properly aligned. • The power cords or cables are not securely connected. • There may be damages cables or power cords. Action 1. Verify all power cords are securely connected. 2. Verify all cables are properly aligned and securely connected for all external and internal components. 3. Remove and check all data and power cables for damage. Be sure no cables have bent pins or damaged connectors. 4. If a device has latches, be sure they are completely closed and locked. 5. If problems continue to occur, remove and reinstall each device, checking the connectors and sockets for bent pins or other damage. Moonshot system does not recognize new hardware Symptom New hardware is not being recognized on the Moonshot system. Cause The hardware is not installed properly or is not supported by the Moonshot system. Action 1. Verify that the hardware being installed is supported on the Moonshot System. For more information on supported hardware, see the documentation in the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). If necessary, remove unsupported hardware. 2. Review the release notes included with the hardware to verify that the issue is not caused by a change to the hardware release. If no documentation is available, see the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). Hardware problems 24 3. Verify that the new hardware is installed properly. To be sure that all requirements are met, see the device, cartridge, chassis, and OS documentation. 4. Verify that no loose connections exist ("Resolving loose connections" on page 24). 5. Verify that all cables are connected to the correct locations and are the correct lengths. For more information, see the chassis documentation in the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). 6. Verify that other components were not accidentally unseated during the installation of the new hardware component. 7. Install all necessary software updates, such as firmware, ROM updates, patches, and the correct version for the hardware. For more information on supported hardware, see the documentation in the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). 8. Verify that all switch settings are correct. For more information about required switch settings, see the switch documentation in the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). 9. Uninstall the new hardware. Unknown problem Symptom The Moonshot System does not power on. Cause Unknown Action 1. Review the statuses of the LEDs to locate the source of the problem. For LED information, see the product documentation in the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). 2. Power down and disconnect all power sources to the chassis. 3. Verify no loose connections exist ("Resolving loose connections" on page 24). 4. Reduce the Moonshot System to the minimum hardware configuration by removing all devices that are not necessary to power on the system. Review the guidelines and cautionary information in the chassis documentation prior to reducing the Moonshot System to minimum hardware configuration. Hewlett Packard Enterprise recommends the cartridge is not removed entirely from the chassis when reducing the number of cartridges to one. When unseating a cartridge, leave the cartridge inside of the slot or replace it with a cartridge blank to maintain proper airflow. If you do remove cartridges from the chassis, be sure the components are returned to their original locations. 5. Reconnect the power, and power on the Moonshot System. o If issues continue to occur while the Moonshot System is in minimum configuration, then an issue exists with one of the primary components. If the cartridge and power supply have been working prior to this point, replace the cartridge. o If the Moonshot System successfully powers on, add each component back to the chassis one at a time, restarting the system after each component is added to determine which component is the source of the problem. When adding each component back to the chassis, disconnect the power to the chassis and follow the guidelines and cautionary information in the chassis documentation. Hardware problems 25 Power problems Power source is not working Symptom The Moonshot System does not power on. Cause • There are components or cables that might not be properly connected or seated. • The grounded power outlet is not working. • The power cord is not functional. • The circuit breaker is in the off position. • The line voltage is insufficient for the load. Action 1. Review the front panel LED display and the rear of the chassis for illuminated LEDs. For more information about the front panel LED status, see "Chassis front panel LEDs and buttons (on page 11)." 2. Plug another device into the grounded power outlet to be sure the outlet works. Also, be sure that the power source meets applicable standards. 3. Replace the power cord with a known functional power cord to verify that it is working properly. 4. Replace the power strip with a known functional power strip to verify that it is working properly. 5. Have a qualified electrician check the line voltage to be sure that it meets the required specifications. 6. Verify that the proper circuit breaker is in the On position. 7. Verify that no loose connections exist ("Resolving loose connections" on page 24). Power supply issues Symptom The power supply is not working or is in standby mode. Cause • The power supply is not fully seated. • The power supply has exceeded the current limit. • The power is not sufficient for the hardware installed. • The power supply is not supported on the cartridge. Action 1. Use the following iLO CM firmware command to review the power supply status for the chassis: SHOW CHASSIS POWERSUPPLY 2. Verify no loose connections exist ("Resolving loose connections" on page 24). 3. Review the power supply LEDs to verify each power supply is working properly. If the LED light is off, check the power source. If the power source is working properly, replace the power supply. For more information, see the chassis documentation in the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). Hardware problems 26 4. Verify there is enough power to support the system. Check the Moonshot System information from the iLO CM IML. If new hardware has been added, remove the newly added component. If the issue no longer exist, additional or upgraded power supplies are required to support the system. For more information about the iLO CM IML, see "HPE Moonshot iLO CM Integrated Management Log (on page 40)." For product-specific information, see the product documentation in the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). For more information on power supplies, see the HPE Power Advisor on the Hewlett Packard Enterprise website (http://www.hpe.com/info/poweradvisor). Power supply power LED is green but the chassis does not power on Symptom Although the power supply LED displays green, the chassis will not power on. Cause The power supplies being used have different outputs and efficiency ratings. Action Verify that the power supplies installed in the chassis have the same output and efficiency rating. Power supplies cannot be mixed in the same chassis. If non-matching power supplies are installed in the chassis, remove all power supplies and install only power supplies with the same spare part number. Redundant power supplies not available Symptom The AC power is not available. Cause Redundant power supplies are configured, but the power supplies are not compatible. Action 1. Use the following iLO CM firmware command to review the power supply status for the chassis: SHOW CHASSIS POWERSUPPLY 2. Verify that no loose connections exist ("Resolving loose connections" on page 24). 3. Verify that all the Moonshot System power supplies have the same spare part number and are supported by the Moonshot System. For a list of supported power supplies, see the product documentation in the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). Cartridge problems Cartridge reboots randomly Symptom The cartridge node restarts without being prompted. Cause Errors exist on the cartridge. Action 1. Log in to the iLO CM firmware. Hardware problems 27 If the issue occurs after loading the operating system, troubleshoot the operating system. 2. Use the following command to display the iLO CM firmware IML and event log: show log iml all show log ilo all 3. Review the IML for issues marked Critical severity. 4. Perform steps to resolve the errors displayed in the IML. 5. Use one of the following command to power down the cartridge node experiencing the issue: set node power off shutdown {} set node power off force {} Where x is the cartridge slot number and y is the node number. 6. Use the following command to power on and connect to the VSP for the cartridge experiencing the issue. set node power on {} connect node vsp {} Where x is the cartridge slot number and y is the node number. 7. Observe the node during the boot process and watch for errors. 8. Perform steps to resolve the errors displayed. 9. If the issue still exists, contact Hewlett Packard Enterprise technical support ("Accessing Hewlett Packard Enterprise Support" on page 57). If the cartridge experiencing the issues is an HPE ProLiant m700 Server Cartridge, see "HPE ProLiant m700 Server Cartridge reboots randomly (on page 28)." For more information about iLO CM firmware, see the HPE Moonshot iLO Chassis Management CLI User Guide on the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). HPE ProLiant m700 Server Cartridge reboots randomly Symptom The HPE ProLiant m700 server cartridge restarts without being prompted. Cause Errors exist on the cartridge. Action 1. Log in to the iLO CM firmware. If the problem occurs after loading the operating system, troubleshoot the operating system. 2. Use the following command to display the iLO CM firmware IML and event log: show log iml all show log ilo all 3. Review the IML for issues marked as Critical severity. 4. Perform steps to resolve the issues displayed on the IML. 5. Use the following command to power down the cartridge node experiencing the issue: set node power off shutdown {} set node power off force {} Where x is the cartridge slot number and y is the node number. 6. Use the following command to power on and connect to the VSP for the cartridge experiencing the issue. set node power on {} Hardware problems 28 connect node vsp {} Where x is the cartridge slot number and y is the node number. 7. Maintain the VSP connection on the node until another unexpected reboot occurs. If the following message displays, a memory issue exists and the cartridge must be replaced. ECC Uncorrectable Multiple Bit Errors Detected 8. If the issue still exists, contact Hewlett Packard Enterprise technical support ("Accessing Hewlett Packard Enterprise Support" on page 57). For more information about iLO CM firmware, see the HPE Moonshot iLO Chassis Management CLI User Guide in the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). HPE Moonshot Remote Console Administrator overview The HPE Moonshot Remote Console Administrator (mRCA), loaded with HPE iLO 4 enables an IT administrator to interface with the Moonshot System. To interface with the specific server cartridge node, the mRCA must be installed in a specific slot within the chassis, relative to the linking server cartridge. For more information about the mRCA cartridge, see the HPE Moonshot Remote Console Administrator Cartridge User and Maintenance Guide in the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). System battery If the cartridge no longer automatically displays the correct date and time, you might have to replace the battery that provides power to the real-time clock. Under normal use, battery life is 5 to 10 years. WARNING: The computer contains an internal lithium manganese dioxide, a vanadium pentoxide, or an alkaline battery pack. A risk of fire and burns exists if the battery pack is not properly handled. To reduce the risk of personal injury: • Do not attempt to recharge the battery. • Do not expose the battery to temperatures higher than 60°C (140°F). • Do not disassemble, crush, puncture, short external contacts, or dispose of in fire or water. • Replace only with the spare designated for this product. For more information about the system battery, refer to the cartridge user and maintenance guide in the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). Fan problems General fan issues Cause • The fans are not seated properly. • The fan configuration does not meet the functional requirements of the cartridge. • The cartridge is not ventilated properly. • One or more required fans are not installed. • Required fan blanks are not installed. • Error messages display during POST or in the IML. • One or more fans are not functioning. Hardware problems 29 Action 1. Verify that no fan LEDs are illuminated. Immediately replace any fans that have a solid amber fan LED. 2. Unseat, and then reseat, each fan according to the proper procedures. Review and follow the procedures and warnings in the chassis documentation before removing and replacing fans. 3. Replace any non-functioning fans. For specifications on fan requirements, see the chassis documentation in the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). 4. Restart the Moonshot System. Fans not working Symptom Fans are seated properly, but are not working. Cause • One or more required fans, or fan blanks, are not installed. • The fan configuration does not meet functional requirements for the cartridge. • Error messages display during POST. Action 1. Verify the fan configuration meets functional requirements for the Moonshot System. For more information, see the chassis documentation in the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). 2. Be sure no POST error messages are displayed while booting the Moonshot System that indicate temperature violation or fan failure information. For the temperature requirements for the Moonshot System, see the chassis documentation in the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). 3. Access the iLO CM IML to see if any error messages relating to fans are listed. For more information on accessing the iLO CM IML, see "HPE Moonshot iLO CM Integrated Management Log (on page 40)." 4. 5. In the iLO CM firmware, enter the following command and review the fan status for problems: SHOW CHASSIS FAN ALL Replace any non-functioning fans. For specifications on fan requirements, see the chassis documentation in the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). 6. Verify fans are installed and operating on all fan bays. For requirements, see the chassis documentation in the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). 7. Restart the Moonshot system. Fans are not cooling Symptom Fans are not properly cooling. Cause The fan airflow path may be blocked. Hardware problems 30 Action 1. Verify that no ventilation problems exist. If the Moonshot system has been operating for an extended period with the access panel removed, airflow might have been impeded. Fans operate at 100% when the access panel is removed. For further requirements, see the chassis documentation in the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). 2. Verify that the fan airflow path is not blocked by cables or other material. Hot-plug fan issues Symptom Hot-plug fans are not working properly. Cause The hot-plug fans are not installed properly or do not meet requirements for the Moonshot System. Action 1. Check the LEDs to be sure the hot-plug fans are working. For more information, see the HPE Moonshot 1500 Chassis Setup and Installation Guide in the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). 2. Verify that no POST error messages are displayed. For a list of POST error messages, see "Error messages (on page 47)." 3. Verify that the hot-plug fans meet the requirements for the Moonshot System. For more information, see the HPE Moonshot System Configuration and Compatibility Guide in the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). Drive problems (hard drives and solid state drives) Drives do not display Symptom The drives do not display in iLO CM. Cause The Moonshot system is not powered on. Action Power on the Moonshot system. NOTE: NVMe M.2 drives do not display in iLO CM. Data is inaccessible Symptom The data on the drives cannot be accessed. Cause • The files on the drive are corrupt. Hardware problems 31 • A virus exists on the cartridge. Action 1. Run the repair utility for the operating system to check for corrupt files. 2. Run a current version of a virus scan utility. 3. Migrate the data to a new cartridge. When migrating encrypted data to a new cartridge, follow the recovery procedures in the operating system documentation. Response time is slower than usual Symptom Cartridge response time is slower than usual. Cause • The drive is full. • Operating system encryption technology is causing a decrease in performance. Action 1. Be sure the drive is not full. If needed, increase the amount of free space on the drive. Hewlett Packard Enterprise recommends that drives have a minimum of 15 % free space. 2. Review information about the operating system encryption technology, which can cause a decrease in system performance. For more information, see the operating system documentation. HPE Moonshot 1500 Chassis Management Module management interfaces The Moonshot 1500 CM module supports management through the following: • Serial port (default 115200,8,n,1) • SSH using an Ethernet connection (default 10/100/1000 DHCP) • HTTP/web/REST management Troubleshooting the Moonshot 1500 CM module may require using either interface to assess problems with the other. Moonshot 1500 CM Module network port locations The Moonshot 1500 CM module has two iLO management ports at the rear of the chassis. By default, iLO management port 1 is enabled, and iLO management port 2 is disabled. For more information on the management port locations, see "HPE Moonshot 1500 Chassis Management module components (on page 16).“ For information about networking, see the HPE Moonshot Networking Cookbook in the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/networking). Cannot connect to iLO CM firmware through network port Symptom Hardware problems 32 Issues occur when attempting to connect to the iLO CM firmware. Action • Verify that there is a single Ethernet connection to the Moonshot 1500 CM module iLO management port 1 (labeled iLO/MGMT). • Check that the external networking gear is configured to link at 10/100/1000 speeds supported by the Moonshot 1500 CM module. • Verify that the management ports are not connected to the same switch unless loop protection has been configured. • Enable iLO management port 2 if this port is being used. • If needed, disconnect the cable from iLO management port 2 (labeled LINK). • Disable DHCP on the iLO CM firmware to configure a static IP address. DHCP is enabled by default on the iLO CM firmware. Once a static IP address has been configured, use the following command to reset the iLO CM firmware for the new configuration to take effect. Reset CM If issues continue to occur in the network connection to the iLO CM firmware, a serial connection to the Moonshot 1500 CM module can be used to view the current network status, configuration, and most recently used network addresses. For more information, see the Moonshot Networking Cookbook on the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). Viewing the current network address For systems with iLO CM firmware versions prior to version 1.10, use the following commands to view information regarding the current network address: • • To view the current network address information for the Moonshot 1500 CM module, use the serial connection for access to the Moonshot 1500 CM module and issue the following command: SHOW To view the current network address configuration and status for the Moonshot 1500 CM module, use the serial connection for access to the Moonshot 1500 CM module and issue the following command: ZONE 1 SHOW NETWORK Serial port locations The Moonshot 1500 CM module has a serial port located at the rear of the chassis. For more information on the serial port location, see the "HPE Moonshot 1500 Chassis Management module components (on page 16).“ Cannot connect to iLO CM firmware through serial port Symptom Issues occur when attempting to connect to the iLO CM firmware using the serial port. Action 1. Log in to the iLO CM firmware remotely. 2. Use the SHOW SERIAL command to verify the current serial status. Hardware problems 33 Software problems The best sources of information for software problems are the operating system and application software documentation, which might also point to fault detection tools that report errors and preserve the system configuration. For more information about supported software tools, see "Software tools and solutions (on page 40)." Operating system problems and resolutions Operating system locks up Symptom The operating system freezes. Action • Scan for viruses with an updated virus scan utility. • Review the iLO CM event log. For more information, see "HPE Moonshot iLO CM Event Log (on page 40)." • Review the iLO CM IML. For more information, see "HPE Moonshot iLO CM Integrated Management Log (on page 40)." For more information about operating system deployment, see Operating system deployment (on page 46). Errors are displayed in the error log Symptom Error messages are displayed in the error log. Action Follow the information provided in the error log. For more information, see the operating system documentation. Issues occur after the installation of a service pack Symptom Issues occur after the installation of a service pack. Action Update the operating system. For more information, see "Updating the operating system." Software problems 34 Reconfiguring or reloading software Prerequisites for reconfiguring or reloading software If all other options have not resolved the problem, consider reconfiguring the system. Before you take this step, do the following: 1. Weigh the projected downtime of a software reload against the time spent troubleshooting intermittent problems. You might consider starting over by removing and reinstalling the software containing issues. 2. Be sure the cartridge has adequate resources (processor speed, drive space, and memory) for the software. 3. Be sure the cartridge ROM is current. 4. Be sure you have printed records of all troubleshooting information you have collected to this point. 5. Be sure you have two good backups before you start. Test the backups using a backup utility. 6. Check the operating system and application software resources to be sure you have the latest information. 7. If the last-known functioning configuration does not work, try to recover the system with operating system recovery software. For more information, see the operating system documentation. Restoring to a backed-up version If you recently upgraded the operating system or software and cannot resolve the issue, try restoring a previously saved version of the system. Before restoring the backup, make a backup of the current system. If restoring the previous system does not correct the issue, you can restore the current set to be sure you do not lose additional functionality. For more information, see the documentation provided with the backup software. Linux resources For Linux operating system support matrix, see the Hewlett Packard Enterprise website (http://www.hpe.com/info/proliantlinux). To assist in possible Linux installation issues on the Moonshot System, capture the data using OS native data collection utilities such as sosreport, RHEL/CentOs, supportconfig, or SLES before contacting Hewlett Packard Enterprise technical support ("Accessing Hewlett Packard Enterprise Support" on page 57). Application software problems Software locks up Symptom The software locks up. Cause • The software might be incompatible with other software on the cartridge. • Known issues might exist with the software. • The cartridge configuration might have changed. • The cartridge might be infected by a virus. Action Software problems 35 1. Check the application log and operating system log for entries indicating why the software locked up. 2. Check for incompatibility with other software on the cartridge. 3. Check the support website of the software vendor for known issues. 4. Review log files for changes made to the cartridge that might have caused the issue. 5. Scan the cartridge for viruses with an updated virus scan utility. Errors occur after a software setting is changed Symptom The system locks up after settings were changed. Cause The new system settings are not supported. Action Check the system logs to determine what changes were made, and then change the settings back to the original configuration. Errors occur after the system software is changed Symptom Errors occur after the system software is changed. Action Change the settings back to the original configuration. If more than one setting was changed, change the settings one at a time to isolate the cause of the issue. Errors occur after an application is installed Action: • Check the application log and operating system log for entries indicating why the software failed. • Check for overwritten files. For more information, see the application documentation to find out which files are added by the application. • Reinstall the application. • Be sure you have the most current drivers. ROM problems Boot problems Cartridge does not boot Cause The system ROM is corrupt. Action Update the firmware. Software problems 36 For more information about updating firmware, see the HPE Moonshot iLO Chassis Management CLI User Guide in the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). Flashing ROM problems Action: After updating the satellite firmware or the system ROM on the cartridge, power cycle the cartridge before initiating the Show Firmware Revision command. Show firmware revisions command shows 00/00/00 date Action: After updating the satellite firmware or the system ROM on the cartridge, power cycle the cartridge before initiating the Show Firmware Revision command. Error message received when trying to update the ROM on a selected cartridge Action: • • For iLO CM firmware versions prior to version 1.10, verify that you are signed into the correct iLO zone for the cartridge being updated. o Zone 1 = Cartridges 1-18 o Zone 2 = Cartridges 19-27 o Zone 3 = Cartridges 28-45 Try updating the cartridge ROM a second time. If the update fails again, try reseating or replacing the cartridge. The ROM flash updates did not take affect after update Action: After updating the system ROM on the cartridge, power cycle the node. The node must be rebooted to complete the ROM flash update. Firmware updates Many common problems can be resolved by updating the firmware. Firmware updates and additional information can be found in the following ways: • HPE Moonshot Component Pack: Update the firmware by downloading the component pack from the Hewlett Packard Enterprise website (http://www.hpe.com/info/moonshot/download). • Subscription services: Hewlett Packard Enterprise offers a subscription service that can provide notification of firmware updates. For more information, see "Subscription services (on page 43)." Software problems 37 UEFI BIOS Issues Cannot download the file in the network boot URL Symptom An error message displays when trying to download the file in the URL that was specified for a network boot. Cause • The network connection settings specified during static configuration are incorrect. • The DHCP server did not respond. • No cable is connected to the selected NIC port. • The file is incorrect or not present on the server. • The file cannot be downloaded due to insufficient privileges. • The HTTP or FTP server is down or did not respond. Action 1. Use the Embedded UEFI Shell ping command to check the network connection. See "Ping" in the UEFI Shell User Guide for HPE ProLiant in the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). 2. Change the static network connection settings. 3. Ensure that there is an operational DHCP server available. 4. Verify that there is a cable connection. 5. Check the file name and verify that it exists on the server. 6. Verify that you have admin privileges on the server. 7. Verify that the HTTP or FTP server you specified is available and operational. 8. Try to download the URL again. Cannot network boot from downloaded image file Symptom Booting from the image specified in the URL fails. Cause • The image is not signed and Secure Boot is enabled. • The downloaded file is corrupt. Action 1. Verify that the image is signed and that its Secure Boot settings are correct. See "Secure Boot" in the UEFI System Utilities User Guide for HPE ProLiant in the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). 2. Try to download the file in the URL again. 3. Select a new file and repeat the URL configuration, specifying the new file. 4. Try to download the new file in the URL. Software problems 38 Cannot deploy from the UEFI Shell script Symptom An error message displays when attempting to deploy an OS using the UEFI Shell script. Cause Configuration settings are not correct. Action 1. Verify the following. o The Embedded UEFI Shell interface is added to the UEFI Boot Order list or One-Time Boot Menu. o When added to the UEFI Boot Order list, the Embedded UEFI Shell interface is the first boot option in the UEFI Boot Order list so that it overrides other boot options to load. o UEFI Shell Script Auto-Start is enabled. o The correct startup.nsh script file location in attached media or a network location is specified. If it is in attached media, the startup.nsh script must be either inside the fsX:\ or the fsX:\efi\boot directory. o o o 2. The .nsh script only contains supported commands. The system has enough RAM memory to create RAM disks during automated script execution. Any OS boot loader or diagnostics application launched using the .nsh script is supported to run in the UEFI environment. Try the deployment again. Software problems 39 Software tools and solutions Hewlett Packard Enterprise product QuickSpecs For more information about product features, specifications, options, configurations, and compatibility, see the product QuickSpecs on the Hewlett Packard Enterprise website (http://www.hpe.com/info/qs). HPE Moonshot iLO Chassis Management Firmware The Moonshot iLO Chassis Management Firmware is the gateway for aggregated chassis management on the Moonshot System. As a single point of access to the chassis, iLO CM firmware enables you to configure, update, and operate the Moonshot System through the GUI, CLI, IPMI, and remote serial console access. For more information, see the HPE Moonshot iLO Chassis Management CLI User Guide in the Hewlett Packard Enterprise Information Library (http://www.hpe.com/info/moonshot/docs). HPE Moonshot iLO CM Integrated Management Log The iLO CM IML records hundreds of events and stores them in an easy-to-view form. The iLO CM IML timestamps each event with 1-minute granularity. Logged events include fan, power supply, cartridge and switch insertion, removal or failure events, temperature events, and firmware updates. To view recorded events in the iLO CM IML, use the GUI or enter the show log iml all command in iLO CM firmware. For more information, see the HPE Moonshot iLO Chassis Management CLI User Guide in the Hewlett Packard Enterprise Information Library (http://www.hpe.com/info/moonshot/docs). HPE Moonshot iLO CM Event Log The iLO CM Event Log is an operating system-independent log that maintains a record of events by date and time. Logged events include major events, such as a power outage or a reset, login events, node power on/off events, configuration changes, and iLO CM firmware events. To view recorded events in the iLO CM Event Log, use the GUI or enter show log ilo all command in iLO CM firmware. For more information, see the HPE Moonshot iLO Chassis Management CLI User Guide in the Hewlett Packard Enterprise Information Library (http://www.hpe.com/info/moonshot/docs). HPE Insight Cluster Management Utility The Insight CMU is an efficient and robust hyperscale cluster lifecycle management framework and suite of tools for large Linux clusters. A simple graphical interface enables an at-a-glance view of the entire cluster across multiple metrics, provides frictionless scalable remote management and analysis, and allows rapid software provisioning to all system nodes. Insight CMU makes cluster management more user friendly, efficient, and error-free than if it were being managed by scripts, or on a node-by-node basis. Insight CMU is highly flexible and customizable, offers both GUI and CLI interfaces, and is used to deploy a range of software environments, from simple compute farms to highly customized, application-specific configurations. For more information on Insight CMU features and links to technical documentation, QuickSpecs, and a product demo, see the Hewlett Packard Enterprise website (http://www.hpe.com/info/cmu). Software tools and solutions 40 To download the product, go to the Hewlett Packard Enterprise Software Depot (http://www.hpe.com/support/softwaredepot). Click Insight Management, then click Insight Cluster Management. HPE Moonshot Component Pack The Moonshot Component Pack is a comprehensive firmware solution tested on the Moonshot System and delivered as a compressed file. The compressed file includes all the component files needed to update a Moonshot System. Users deploy the firmware updates contained in the Moonshot Component Pack using the included HP Smart Update Manager, or by using the iLO Chassis Manager GUI or CLI, or the HPE Moonshot switch module CLI. Download the latest pack from the Hewlett Packard Enterprise website (http://www.hpe.com/info/moonshot/download). Software tools and solutions 41 Resources for troubleshooting Online resources HPE Moonshot Information Library The HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs) is a task-based repository that includes installation instructions, user guides, maintenance and service guides, best practices, useful links, and videos. Use this website to obtain the latest documentation and look up information about the following: • Learning about the Moonshot System technology • Setting up and configuring the Moonshot System • Updating the components of the Moonshot System • Integrating the Moonshot System and understanding how it connects to the outside world • Using and managing the Moonshot System Product documentation Product documentation is available online to assist the user with setting up and installing, maintaining, and troubleshooting the Moonshot System. Most documents are available as a PDF. All Moonshot System user documentation can be accessed from the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). HPE Moonshot 1500 Chassis Setup and Installation Guide The HPE Moonshot 1500 Chassis Setup and Installation Guide provides information about installation, components and LEDs, cable routing, and configuration for the HPE Moonshot 1500 Chassis. This guide can be accessed from the following locations: • HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs) • Hewlett Packard Enterprise Support Center website (http://www.hpe.com/support/hpesc) HPE Moonshot iLO Chassis CLI User Guide The HPE Moonshot iLO Chassis CLI User Guide provides information describing the tools available to access Moonshot iLO CM firmware through the command line. Moonshot iLO CM firmware commands provide a method to configure the HPE Moonshot 1500 Chassis to incorporate a standard configuration into the deployment process and to control cartridges. This guide can be accessed from the following locations: • HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs) • Hewlett Packard Enterprise Support Center website (http://www.hpe.com/support/hpesc) Resources for troubleshooting 42 Driver, firmware updates, and software updates To download the latest drivers, firmware updates, and software updates, see the HPE Moonshot Component Pack download page (http://www.hpe.com/info/moonshot/download). HPE Moonshot Videos View short videos hosted by Hewlett Packard Enterprise technical experts in the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). Product QuickSpecs For more information about product features, specifications, options, configurations, and compatibility, see the product QuickSpecs on the Hewlett Packard Enterprise website (http://www.hpe.com/info/qs). White papers White papers are electronic documentation on complex technical topics. Some white papers contain in-depth details and procedures. Topics include Hewlett Packard Enterprise products, technology, OS, networking products, and performance. For more information, see the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). Service notifications, advisories, and notices To search for service notifications, see the Hewlett Packard Enterprise Support Center (http://www.hpe.com/support/hpesc). Enter the product name or number, and then click Go. Select Top Issues and Solutions, and then Advisories Bulletins & Notices. The complete list of documents is displayed. Subscription services Receive support alerts, product support communications, driver updates, software releases, firmware updates, and customer replaceable component information in your email by signing up on the Hewlett Packard Enterprise website (http://www.hpe.com/info/myadvisory). To change options for support alerts you already receive, click the link to sign in on the right. HPE Technology Service Portfolio Hewlett Packard Enterprise Technology Services—Offers a targeted set of consultancy, deployment, and support service solutions designed to meet the needs of the most demanding business and IT environments Hewlett Packard Enterprise Foundation Care services—Delivers scalable hardware and software support packages for the Hewlett Packard Enterprise Moonshot System and industry-standard software. You can choose the type and level of service that is most suitable for your business needs. Hewlett Packard Enterprise Collaborative Support—With a single call, Hewlett Packard Enterprise addresses initial hardware and software support needs and helps to quickly identify if a problem is related to hardware or software. If the problem is related to hardware, Hewlett Packard Enterprise will resolve the issue based on service level commitments. If the reported incident is related to a Hewlett Packard Enterprise software or supported third-party software product and cannot be resolved by applying known fixes, Hewlett Packard Enterprise will contact the third-party vendor and create a problem incident on your behalf. Resources for troubleshooting 43 Hewlett Packard Enterprise Proactive Care—For customers running business critical environments where down time is not an option, Hewlett Packard Enterprise Proactive Care helps to deliver high levels of availability and to prevent issues before they occur. Hewlett Packard Enterprise Datacenter Care—The recommended service to support the datacenter environment, particularly for “hyperscale” customers. Datacenter Care is flexible support from a partner that understands web-scale computing, featuring one service relationship combining globally delivered building blocks with Hewlett Packard Enterprise Datacenter Care, fast escalation to real experts at the Hyperscale Center of Excellence, and on-site spare parts kiosk to service products. Hewlett Packard Enterprise Technology Consulting—Expertise to help customers evaluate workloads for migration to the Moonshot System, and to plan and implement the transition to this new platform in an orderly, predictable way Hewlett Packard Enterprise Critical Facilities Energy Services—Designed to help optimize infrastructure performance and boost system performance, while improving energy efficiency and reducing energy costs Product information resources Additional product information For additional product information, see the product page on the Hewlett Packard Enterprise website (http://www.hpe.com/info/moonshot). Register the product To experience quicker service and more efficient support, register the product at the Hewlett Packard Enterprise Product Registration website (http://www.hpe.com/info/register). Overview of product features and installation instructions For more information about product features, specifications, options, configurations, and compatibility, see the product QuickSpecs on the Hewlett Packard Enterprise website (http://www.hpe.com/info/qs). For installation instructions, see the cartridge user and maintenance guide or the HPE Moonshot 1500 Chassis Setup and Installation Guide in the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). Key features, option part numbers For more information about product features, specifications, options, configurations, and compatibility, see the product QuickSpecs on the Hewlett Packard Enterprise website (http://www.hpe.com/info/qs). Cartridge configuration information For cartridge configuration information, see the cartridge user guide or setup and installation guide. These guides are available in the following locations: • Hewlett Packard Enterprise Information Library (http://www.hpe.com/info/enterprise/docs) • Hewlett Packard Enterprise Support Center website (http://www.hpe.com/support/hpesc) Resources for troubleshooting 44 Product and option specifications, symbols, installation warnings, and notices See the product documentation and notices. Product documentation is available in the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). HPE Moonshot System specifications, symbols, installation warnings, and notices See the product documentation and notices. The notices and product documentation are available in the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). Teardown procedures, part numbers, specifications HPE Moonshot System documentation provides teardown procedures, part numbers, and specifications in the following documents in the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs): • HPE Moonshot 1500 Chassis Maintenance and Service Guide • Cartridge user and maintenance guide • Switch user and maintenance guide Teardown or removal and replacement procedure videos For more information about removal and replacement procedures for the Moonshot System, see the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). Technical topics White papers are electronic documentation on complex technical topics. Some white papers contain in-depth details and procedures. Topics include Hewlett Packard Enterprise products, technology, OS, networking products, and performance. For more information, see the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). Product installation resources External cabling information See the cabling information on the Hewlett Packard Enterprise website (http://www.hpe.com/support/hpesc). Power capacity See the HPE Power Advisor on the Hewlett Packard Enterprise website (http://www.hpe.com/info/hpepoweradvisor). Resources for troubleshooting 45 LED functions, component installation instructions, and component identification See the hood label and the HPE Moonshot 1500 Chassis Setup and Installation Guide. The hood label is located on the access panel of the chassis, and the HPE Moonshot 1500 Chassis Setup and Installation Guide is available in the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). Product configuration resources Operating System Version Support For information about specific versions of a supported operating system, refer to the operating system support matrix (http://www.hpe.com/info/ossupport). Operating system deployment For deployment procedures, see the Operating System Deployment on HPE ProLiant Server Cartridges User Guide in the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). HPE Moonshot System configuration information See the HPE Moonshot 1500 Chassis Setup and Installation Guide in the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). Software installation and configuration of the HPE Moonshot System See the HPE Moonshot 1500 Chassis Setup and Installation Guide in the HPE Moonshot Information Library (http://www.hpe.com/info/moonshot/docs). HPE Moonshot management For more information on HPE Insight CMU features and links to technical documentation, QuickSpecs, and a product demo, see the Hewlett Packard Enterprise website (http://www.hpe.com/info/cmu). Resources for troubleshooting 46 Error messages POST error messages Introduction to POST error messages The error messages and codes in this section are generated by the HPE Moonshot System. Some messages are informational only and do not indicate any error. WARNING: To avoid potential issues, ALWAYS read the warnings and cautionary information in the product documentation before removing, replacing, reseating, or modifying system components. MCU buffer unit has detected an error. Possible cause: Set on an uncorrectable memory error Action: For more information, see the operating system logs. Memory Controller Unit (MCU) has detected an error. Possible cause: Set on an uncorrectable memory error Action: For more information, see the operating system logs. RCEC has detected an error. Possible cause: Set on an internal SoC (Intel Atom CPU) error Action: For more information, see the operating system logs. PCIe RP[1] has detected an error. Possible cause: Root port 1 uncorrectable error Action: For more information, see the operating system logs. PCIe RP[2] has detected an error. Possible cause: Root port 2 uncorrectable error Action: For more information, see the operating system logs. PCIe RP[3] has detected an error. Possible cause: Root port 3 uncorrectable error Action: For more information, see the operating system logs. Error messages 47 PCIe RP[4] has detected an error. Possible cause: Root port 4 uncorrectable error Action: For more information, see the operating system logs. Error detected with the ROM image. Possible cause: Error with ROM flash update on previous boot Action: Flash the BIOS image again. Error detected with drive 1. Possible cause: Error found with drive 1 on the previous boot Action: Repair or replace drive 1. Error detected with drive 2. Possible cause: Error found with drive 2 on the previous boot Action: Repair or replace drive 2. Fatal error detected and forced system reset! Possible cause: A fatal memory error, a SoC error, or a PCIe error caused the HPE Moonshot System to reset. Action: Replace the cartridge. Cartridge error detected in CPU subsystem Possible cause: Machine check or uncorrectable error within the CPU subsystem Action: For more information, see the operating system logs. Cartridge error detected in memory subsystem Possible cause: Uncorrectable multi-bit error in system memory Action: For more information, see the operating system logs. Cartridge error detected in storage subsystem Possible cause: Failure on the hard disk or storage controller Action: For more information, see the operating system logs. Cartridge error detected in network subsystem Possible cause: Uncorrectable failure in the network interface controller Action: For more information, see the operating system logs. Error messages 48 Cartridge error detected in I/O subsystem Possible cause: Uncorrectable error on one of the embedded or expansion PCI Express devices Action: For more information, see the operating system logs. Cartridge error detected in thermal subsystem Possible cause: Over-temperature condition Action: For more information, see the operating system logs. Cartridge error detected in BIOS/Flash subsystem Possible cause: Invalid image or corrupted image in the BIOS flash Action: For more information, see the operating system logs. Cartridge error detected in security subsystem Possible cause: Security system violation Action: For more information, see the operating system logs. Cartridge error detected in mezzanine subsystem Possible cause: Uncorrectable error on a mezzanine device Action: For more information, see the operating system logs. Cartridge error detected in power subsystem Possible cause: Failure in the power supply Action: For more information, see the operating system logs. Fatal error detected and forced system reset! Possible cause: A fatal uncorrectable error in a processor, the memory, or a PCIe has caused the HPE Moonshot System to reset. Action: For more information, see the operating system logs. Error messages 49 HPE iLO errors Event log entries Event log display Event log explanation Access options IPMI/DCMI modified by: [user name] The options to access iLO via IPMI/DCMI were modified by the listed user. Active Health System cleared by: [user name] Active Health System disabled by: [user name] Active Health System enabled by: [user name] Active Health System logging hardware disabled The Active Health System was cleared by the listed user. The Active Health System was disabled by the listed user. The Active Health System was enabled by the listed user. The Active Health System was disabled in hardware. Active Health System logging hardware enabled The Active Health System was enabled in hardware. Added group [group name] by: [user name] The listed directory group was added by the listed user. AlertMail modified by: [user name] AlertMail sent to: [user name] The AlertMail settings were modified by the listed user. An AlertMail has been sent to the listed user. APO: iLO attempting to power-on the system iLO attempted to power on the system according to the Auto Power On settings. APO: Last power state restored The Auto Power On setting was set to restore the last power state when the power to the system was restored. APO: Restored power state to standby The system power has been restored to the standby state according to the Auto Power On settings. APO: Settings modified by: [user name] The Auto Power On settings were modified by the listed user. APO: System configured to always remain off after power was restored The Auto Power On setting was set to remain off after the power to the system was restored. Asset tag changed by: [user name] Attempting to install language pack [name] BMC IPMI iLO: [event message] The server asset tag was modified by the listed user. iLO attempted to install the given language pack. BMC IPMI events BMC IPMI Watchdog Timer Timeout: [details] BMC IPMI Watchdog Timer timed out with the listed details. Brown-out: recovery The system was recovered from brown-out. Brown-out: System configured to always remain off after power was restored The system brown-out recovery did not occur because the system was configured to remain off after the power was restored. Browser login failure from: [IP address and DNS name] An attempt to login to the iLO web user interface has failed. The login request came from the listed IP address and DNS name. Browser login: [user name] - [IP address and DNS The listed user logged in to iLO via the web user interface from the listed IP address and DNS name. name] The listed user logged out of iLO via the web user Browser logout: [user name] - [IP address and interface from the listed IP address and DNS name. DNS name] The connection between iLO and the listed server was not Certificate Warning: Subject [certificate subject] secure because the server name did not match the does not match server name [server name] server's SSL certificate. Default language settings modified by: [user name] Deleted group [group name] by: [user name] Deleted user: [user name] Directory settings modified by: [user name] The default language settings were modified by the listed user. The listed directory group was deleted by the listed user. The listed user account was deleted. The directory settings were modified by the listed user. Error messages 50 Event log display Event log explanation Duplicate IP address [IP address] detected on network. Duplication of the listed IP address was detected. Dynamic Power Cap disabled by : [user name] The server dynamic power cap was disabled by the listed user. Dynamic Power Cap set to [value] by : [user name] The server dynamic power cap was set to the listed value by the listed user. Embedded Flash/SD-CARD: [status details] Enforce AES/3DES encryption disabled: [user name] Enforce AES/3DES encryption enabled: [user name] eRS - [status] Event log cleared Event log cleared by: [user name] The status of the Embedded Flash/SD card. Enforcement of AES/3DES encryption was disabled by the listed user. Enforcement of AES/3DES encryption was enabled by the listed user. The status of the embedded Remote Support subsystem. The iLO event log was cleared. The iLO event log has been cleared by the listed user. Excessive network delay while communicating with virtual [virtual media device] The virtual media connection timed out due to excessive network delay while communicating with the listed virtual media device. FIPS Mode Enabled The FIPS-compliant mode was enabled. Firmware reset by [source] for network modifications. iLO was reset by the listed source for network modifications. FIPS mode was disabled and iLO was reset to the factory FIPS Mode was disabled and iLO was reset because of multiple Known Answer Test failures. defaults because there were multiple FIPS Known Answer Test failures. Firmware reset to use new hardware Firmware upgrade complete Firmware upgrade started from: [IP address and DNS name] Firmware upgrade via CLI failed Firmware upgrade via online flash component failed iLO was reset to use new hardware. Firmware upgrade has completed. Firmware update was initiated from the listed IP address and DNS name. An attempt to update the firmware via the CLI failed. An attempt to update the firmware using the online flash component failed. Firmware upgrade via web page failed Firmware update did not complete successfully. Make sure the firmware image file is correct. Firmware upgrade via XML failed Firmware upgrade via RIBCL script failed. Make sure the firmware image file is correct. Firmware upgraded to version [version] Firmware was successfully updated to the listed version. Group Power Cap for [group] disabled by: [user name] Group Power Cap for [group] set to [value] by: [user name] Host server reset by: [user name] Hotkey modified by: [user name] iLO clock has been synchronized with [IP address] iLO clock has been synchronized with the Onboard Administrator iLO Federation Group [group] added by: [user name] iLO Federation Group [group] deleted by: [user name] iLO Federation Group [group] modified by: [user name] The Group Power Cap for the listed iLO Federation Group was disabled by the listed user. The Group Power Cap for the listed iLO Federation Group was set to the listed value by the listed user. The server was reset (warm-rebooted) by the list user. Hotkey settings were modified by the listed user. iLO clock has been synchronized with the NTP server at the listed IP address. iLO clock has been synchronized with the BladeSystem Onboard Administrator. The listed iLO Federation Group was added to this iLO by the listed user. The listed iLO Federation Group was deleted from iLO by the listed user. The listed iLO Federation Group was modified by the listed user. Error messages 51 Event log display Event log explanation iLO Federation Management login failure from: [IP address and DNS name] An attempt to login by the iLO Federation Management failed. iLO Management Processor reset iLO was restarted. iLO Federation Management login: [user name] - The iLO Federation Management logged in with the listed user name from the listed IP address and DNS name. [IP address and DNS name] iLO Federation Management logout: [user name] The iLO Federation Management logged out with the listed user name from the listed IP address and DNS - [IP address and DNS name] name. iLO Management Processor reset iLO Management Processor reset to factory defaults iLO was reset by the firmware, typically to apply settings. iLO was reset to factory defaults. All configurations are restored to the factory defaults. iLO memory error detected at [address] iLO detected a correctable memory error at the listed address. iLO Network Configuration modified by [user name] The iLO network configuration was modified by the listed user. iLO network link down iLO was not connected to a network iLO network link up at [link speed] iLO network connection was established at the listed speed iLO RBSU exited The iLO RBSU session ended. User logged out and the iLO RBSU exited. iLO RBSU login failure An attempt to login to iLO via the iLO RBSU failed. iLO RBSU login: [user name] The listed user logged in to iLO via the iLO RBSU. iLO reset by user diagnostics iLO was reset by user for diagnostics. This is typically initiated from the Diagnostic page of the iLO web user interface. iLO reset for Firmware upgrade iLO was reset to apply firmware updates. iLO Self Test Error: [error code] iLO has failed an internal test. The probable cause is that a critical component has failed. Further use of iLO on this server is not recommended. iLO SNMP settings modified by: [user name] The SNMP was modified by the listed user. iLO time update failed. Unable to contact NTP server iLO updated the host Date and Time. iLO was hard reset by a local user or device iLO was reset because a FIPS Known Answer Test failed iLO was reset for network link auto-detection iLO was soft reset by a local user, device or enclosure iLO was unable to synchronize the time with the NTP server because the server cannot be reached. iLO updated the server onboard clock. iLO was hard reset by a local user or device iLO was reset because a FIPS Known Answer Test failed. iLO was reset for network link auto-detection. iLO was soft reset by a local user, device or enclosure Integrated Remote Console Trust Settings disabled by: [user name] The IRC Trust Setting was disabled by the listed user. A trusted SSL certificate would be required to launch the IRC. Integrated Remote Console Trust Settings Enabled by: [user name] The IRC Trust Setting was enabled by the listed user. A trusted SSL certificate would be required to launch the IRC. IPMI/RMCP login by [user name] - [IP address and DNS name] The listed user logged in to iLO via IPMI/RMCP from the listed IP address and DNS name. IPMI/RMCP login failure from: [IP address and DNS name] An attempt to login to iLO via IPMI/RMCP failed from the listed IP address and DNS name. IPMI/RMCP logout: [user name] - [IP address and The listed user logged out of iLO via IPMI/RMCP from the listed IP address and DNS name. DNS name] Error messages 52 Event log display Event log explanation Key manager configuration modified by: [user name] The key manager configuration was modified by the listed user. Key manager redundancy modified by: [user name] Language pack added Language pack removed The key manager redundancy setting was modified by the listed user. Language pack was installed. Language pack was removed. Language pack upgrade failed An error occurred while iLO attempted to update the language pack. License activation error by: [user name] The license activation key cannot be installed. Possibly the activation key was invalid or not supported. License added by: [user name] A license activation key was installed by the listed user. License expired Login security banner disabled by: [user name] Login security banner enabled by: [user name] Modified group [group name] by: [user name] Modified user: [user name] License expired and licensed features are deactivated. The login security banner was disabled by the listed user. The login security banner was enabled by the listed user. The listed directory group was modified by the listed user. The listed user account was modified. Multicast configuration modified by: [user name] The multicast configuration was modified by the listed user. New user: [user name] A new user account was added with the listed user name. No valid SNMP trap destinations. FQDN lookup failed There are no valid SNMP trap destinations. iLO was unable to look-up the supplied FQDN's. On-board clock set; was [mm/dd/yyyy ##:##:##] The server onboard clock was set or changed. The persistent mouse and keyboard setting was disabled Persistent mouse and keyboard DISABLED by: by the listed user. [user name] The persistent mouse and keyboard setting was enabled Persistent mouse and keyboard ENABLED by: by the listed user. [user name] The server power consumption exceeded a user-defined Power consumption exceeded user-defined threshold and SNMP warning has been issued. threshold, SNMP warning issued iLO receives power on request from the listed source. The Power on request received by: [source] source can be the power buttons, wake-on-LAN, automatic power recovery. Power Regulator setting changed by: [user name] Power Regulator setting changed by the listed user. The server Power-Off request was sent by the list user. Power-Off signal sent to host server by: [user name] The server Power-On request was sent by the list user. Power-On signal sent to host server by: [user name] A non-critical error has occurred in iLO and iLO has reset Recoverable iLO Error, code [error code] itself. If this issue persists, call customer support. Remote console computer lock Disabled by: [user The remote console auto-lock setting was disabled. The server console lock needs to be done manually. name] Remote console computer lock Enabled by: [user The remote console auto-lock setting was enabled. The server console will be automatically locked when the name] remote console session ends. Remote console login failure from: [IP address and DNS name] An attempt to login to use the iLO Remote Console has failed. The request came from the listed IP address and DNS name. Remote console session shared by: [IP address and DNS name] A shared remote console session was established for the listed IP address and DNS name. Remote console started by: [user name] - [IP address and DNS name] Remote console started by: [user name] - [IP address and DNS name] The remote console session was started by the listed user from the listed IP address and DNS name. The remote console session was closed by the listed user from the listed IP address and DNS name. Error messages 53 Event log display Event log explanation Remote Syslog modified by: [user name] The Remote Syslog settings were modified by the listed user. Rest API Info: Rest API Provider Added [provider A REST API provider was added at the listed index. index] The REST API memory was cleared for the listed reason. Rest API Warning: Rest API memory cleared [reason] A REST API provider was removed for the listed reason. Rest API Warning: Rest API Provider Removed [reason] The AHS counter for RIBCL was cleared by the listed RIBCL AHS count cleared by: [user name] user. ROM Swap: System ROM has been swapped to backup ROM by: [user name] Scriptable virtual media ejected by: [user name] System ROM has been swapped to backup ROM by the listed user. Scriptable virtual media was ejected by the listed user. Scriptable Virtual Media HTTP error [error code] iLO received an HTTP error with the listed error code from the scriptable virtual media hosting server. Scriptable virtual media inserted by: [user name] Scriptable virtual media was inserted by the listed user. Scripted Virtual Media could not establish a connection to [URL] iLO could not establish a connection with the listed URL to use as a scriptable virtual media device. Security jumper override detected. Security disabled! The security-override jumper was added on the system board (not recommended). Security was disabled (overridden). Security jumper setting normal The security-override jumper is not added on the system board (recommended). Security settings operate normally. Serial CLI login failure An attempt to login to iLO from the Serial CLI failed. Serial CLI login: [user name] Serial CLI logout: [user name] Serial CLI session started The listed user logged in to iLO via the Serial CLI. The listed user logged out of iLO via the Serial CLI. A Serial CLI session started. Serial CLI session stopped A Serial CLI session stopped. Server Name changed by: [user name] The server name was modified by the listed user. Server power removed The server power is turned off. Server cumulative power on time cleared by [user The server cumulative power-on time was cleared by the listed user from the listed IP address and DNS name. name] - [IP address and DNS name] The server Fully Qualified Domain Name was modified by Server FQDN changed by: [user name] the listed user. Server power loss caused by: [cause]. Attempt to The server power was lost due to the listed cause. iLO will attempt to restore the server power after the listed restore server power in [duration]. duration. Server power restored Server reset Shared remote console session has disconnected: [IP address and DNS name] The server power is turned on. The server was reset (warm-rebooted). The shared remote console session was disconnected from the listed IP address and DNS name. SMH FQDN changed by: [user name] The Fully Qualified Domain Name of the System Management Homepage was modified by the listed user. SNMP Alert on Breach of Power Threshold modified by: [user name] The SNMP Alert on Breach of Power Threshold setting was modified by the listed user. SNTP server settings modified by: [user name] SSH key for [user 1] added by: [user 2] SSH key for [user 1] removed by: [user 2] SSH login failure from: [IP address and DNS name] The NTP servers were modified by the listed user. The SSH key was added for user 1 by user 2. The SSH key for user 1 has been removed by user 2. An attempt to login to iLO failed from the listed IP address and DNS name, via SSH. Error messages 54 Event log display Event log explanation SSH login: [user name] - [IP address and DNS name] The listed user logged in to iLO via SSH from the listed IP address and DNS name. SSH logout: [user name] - [IP address and DNS name] The listed user logged out of iLO via SSH from the listed IP address and DNS name. SSL Certificate installed by : [user name] An SSL certificate was installed on iLO by the listed user. SSO login attempt from [IP address] via [SSO server] as [SSO role] by user: [user name] The listed user attempted to login to iLO using SSO from the listed IP address and SSO server. SSO [role] role privileges set by user: [user name] The SSO role (administrator, operator, user...) was set to listed role by the listed user. SSO rejected An attempt to login to iLO using SSO was rejected. SSO rejected: Certificate mismatch An attempt to login to iLO using SSO was rejected because the SSO certificate was not trusted. SSO rejected: not enabled An attempt to login to iLO using SSO was rejected because SSO was not enabled. SSO rejected: Unknown host An attempt to login to iLO using SSO was rejected because the host name was not trusted. SSO server [index] removed by user: [user name] The SSO server at the listed index has been removed by the listed user. SSO server [server name] added by user: [user name] The listed SSO server name was added by the listed user. Stale host ROM detected. Please use System ROM [mm/dd/yyyy] or later. The system BIOS does not meet the minimum requirement of this iLO firmware. Please use the system BIOS version that matches the listed date or newer. System Boot Mode modified by: [user name] The server boot mode setting was modified by the listed user. System Boot Order modified by: [user name] The server boot device order was modified by the listed user. SSO server [server name] removed by user: [user The listed SSO server name has been removed by the listed user. name] The SSO Trust Mode was set to the listed mode by the SSO Trust Mode set to [mode] by user: [user listed user. name] System One-Time Boot modified by: [user name] The system One-Time Boot selection was modified by the listed user. System power was cycled for update to take effect System Programmable Logic Device update complete. Mandatory system A/C power cycle is required for update to take effect. System Programmable Logic Device update failed System Programmable Logic Device update starting The system power was cycled for update to take effect. The System Programmable Logic Device has been successfully updated. Cycle system A/C power for the update to take effect. An attempt to update the System Programmable Logic Device failed. System Programmable Logic Device update was started. Textcons session started by: [user name] - [IP address and DNS name] A text remote console (TEXTCONS) session was started by the listed user from the listed IP address and DNS name. Textcons session stopped by: [user name] - [IP address and DNS name] A text remote console (TEXTCONS) session was stopped by the listed user from the listed IP address and DNS name. Unable to export key from key manager iLO was unable to export a key from the key manager. Unable to import key into key manager Update of Power Management Controller failed iLO was unable to import a key into the key manager. An attempt to update the Power Management Controller failed. Error messages 55 Event log display Event log explanation Update of Power Management Controller from version [version number] starting. The Power Management Controller update was started. The current version is listed. Update of Power Management Controller to version [version number] complete User [user 1] added by [user 2] User [user 1] deleted by [user 2] User [user 1] modified by [user 2] Utility data center lock disabled by: [user name] Utility data center lock enabled by: [user name] Virtual media connected by: [user name] The Power Management Controller has been successfully updated to the listed version. A user account was added. A user account was deleted. A user account was modified. The utility data center lock was disabled by the listed user. The utility data center lock was enabled by the listed user. A virtual media device was connected by the listed user. Virtual media disconnected by: [user name] A virtual media device was disconnected by the listed user. Virtual NMI selected by: [user name] The virtual non-maskable interrupt was generated by the listed user. Virtual Serial Port started by: [user name] - [IP address and DNS name] Virtual Serial Port was started by the listed user from the listed IP address and DNS name. Virtual Serial Port stopped by: [user name] - [IP address and DNS name] XML login failure from: [IP address and DNS name]. XML login: [user name] - [IP address and DNS name]. XML logout: [user name] - [IP address and DNS name]. Virtual Serial Port was stopped by the listed user from the listed IP address and DNS name. An attempt to login to iLO failed from the listed IP address and DNS name, via the RIBCL interface. The listed user logged in to iLO via the RIBCL interface from the listed IP address and DNS name. The listed user logged out of iLO via the RIBCL interface from the listed IP address and DNS name. Error messages 56 Support and other resources Accessing Hewlett Packard Enterprise Support • For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website (http://www.hpe.com/assistance). • To access documentation and support services, go to the Hewlett Packard Enterprise Support Center website (http://www.hpe.com/support/hpesc). Information to collect Be sure to have the following information available before you call Hewlett Packard Enterprise: • Technical support registration number (if applicable) • Product name • Chassis serial number • Product identification number • Applicable error messages • Operating system type and revision level To obtain product information, log in to iLO CM firmware and use the Show Chassis Info command. For more information, see the HPE Moonshot iLO Chassis Management CLI User Guide in the Hewlett Packard Enterprise Information Library (http://www.hpe.com/info/moonshot/docs). Accessing updates • Some software products provide a mechanism for accessing software updates through the product interface. Review your product documentation to identify the recommended software update method. • To download product updates, go to either of the following: • o Hewlett Packard Enterprise Support Center Get connected with updates page (http://www.hpe.com/support/e-updates) o Software Depot website (http://www.hpe.com/support/softwaredepot) To view and update your entitlements, and to link your contracts and warranties with your profile, go to the Hewlett Packard Enterprise Support Center More Information on Access to Support Materials page (http://www.hpe.com/support/AccessToSupportMaterials). IMPORTANT: Access to some updates might require product entitlement when accessed through the Hewlett Packard Enterprise Support Center. You must have an HP Passport set up with relevant entitlements. Websites • Hewlett Packard Enterprise Information Library (http://www.hpe.com/info/enterprise/docs) • Hewlett Packard Enterprise Support Center (http://www.hpe.com/support/hpesc) Support and other resources 57 • Contact Hewlett Packard Enterprise Worldwide (http://www.hpe.com/assistance) • Subscription Service/Support Alerts (http://www.hpe.com/support/e-updates) • Software Depot (http://www.hpe.com/support/softwaredepot) • Customer Self Repair (http://www.hpe.com/support/selfrepair) • Insight Remote Support (http://www.hpe.com/info/insightremotesupport/docs) • Serviceguard Solutions for HP-UX (http://www.hpe.com/info/hpux-serviceguard-docs) • Single Point of Connectivity Knowledge (SPOCK) Storage compatibility matrix (http://www.hpe.com/storage/spock) • Storage white papers and analyst reports (http://www.hpe.com/storage/whitepapers) Service notifications Service notifications are created to provide solutions for known issues with the Moonshot System. Check to see if your issue is covered by an existing service notification. To search for service notifications, see the Hewlett Packard Enterprise Support Center (http://www.hpe.com/support/hpesc). Enter the product name or number, and then click Go. Select Top Issues and Solutions, and then Advisories Bulletins & Notices. The complete list of documents is displayed. Support and other resources 58 Acronyms and abbreviations ASR Automatic Server Recovery CM chassis management CMU HPE Insight Cluster Management Utility DAC direct attach cable DHCP Dynamic Host Configuration Protocol ESD electrostatic discharge iLO Integrated Lights-Out IML Integrated Management Log IPMI Intelligent Platform Management Interface NVRAM nonvolatile memory POST Power-On Self-Test SD Secure Digital SFP+ enhanced small form-factor pluggable Acronyms and abbreviations 59 SR short range SSD solid-state drive SSH Secure Shell SYSROM System ROM UPS uninterruptible power system USB universal serial bus VSP virtual serial port Acronyms and abbreviations 60 Documentation feedback Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (mailto:[email protected]). When submitting your feedback, include the document title, part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page. Documentation feedback 61 Index A additional information 44 application software problems 35 authorized reseller 8, 57 B backup, restoring 35 before you contact Hewlett Packard Enterprise 57 button, UID 12 C cables 24 cables, troubleshooting 24 cabling 45 cartridge boot problems flowchart 21 cartridge error 48, 49 cartridge health LED 11, 12 cartridge link LED/button 12 cartridge power LED 12 cartridge power-on problems flowchart 20 cartridge problems 27 cartridge rebooting randomly 27, 28 cartridge UID LED/button 12 cautions 7 chassis components 11 chassis health LED 11 chassis power LED 11 chassis power-on problems flowchart 19 chassis UID LED/button 11 CMU 40, 59 compatibility 57 component LEDs 46 component location 46 configuration of system 46 connection problems 24 contact information 57 contacting Hewlett Packard Enterprise 57 D data recovery 31 device information 16 diagnostic flowcharts 19 documentation 42, 43, 61 documentation feedback 61 drive errors 48 drive LEDs 12 drive problems 31 drive, failure of 31 drivers 43 drives 31 drives, troubleshooting 31 E electrostatic discharge 7, 8 error log 34 error messages 34, 37, 47, 48, 49 error messages, POST 47 errors 48 event logs 40 F fan LED 31 fan problems 29, 31 fans 29, 31 features 44 firmware 37, 46 firmware, updating 37, 43 firmware, upgrading 37 flash ROM 37 flowcharts 19, 20, 21, 22, 23 G getting started 6 grounding methods 7, 8 grounding requirements 7 H hard drive LEDs 12 hard drive problems, diagnosing 31 hard drive, failure of 31 hard drives, moving 31 hardware features 24 hardware problems 24 hardware supported 24 hardware troubleshooting 24 health LED 11, 12, 13, 16 Hewlett Packard Enterprise contact information 57 Hewlett Packard Enterprise website 57 HP technical support 43, 57 HPE Insight Cluster Management Utility 40 HPE Moonshot Component Pack 41 HPE Moonshot iLO Chassis Management Firmware 40 HPE Moonshot videos 43 HPE Power Advisor 45 Index 62 HPE support services 43, 57 I iLO (Integrated Lights-Out) 40 IML (Integrated Management Log) 40 Important Safety Information document 6 information library 42 installation and configuration 45 installation instructions 44, 46 Integrated Management Log (IML) 40 L LED, fan 31 LED, health 11, 12, 13 LED, system power 12 LED, unit identification (UID) 11, 12, 13 LEDs 11, 12, 13, 46 LEDs, front panel 11, 12 LEDs, hard drive 12 LEDs, power supply 27 LEDs, troubleshooting 11 Linux 35 loose connections 24 M maintenance and service guide 45 management module connectors 16 management module LEDs 16 memory controller unit (MCU) 47 N network connection problems 32 network ports 32 new hardware 24 notices 43 O online troubleshooting resources 42 operating system crash 34 operating system version support 46 operating systems 34, 35, 46 operating systems supported 40, 46 P part numbers 44, 45 PCIe errors 47, 48 phone numbers 57 POST error messages 47, 48, 49 power calculator 45 power problems 26 power source 26 power supplies 26, 27 power supply LEDs 27 power-on problems flowchart 19, 20 pre-diagnostic steps 9 preparation procedures 10 preparing the server for diagnosis 10 product configuration resources 44 product documentation 42 product information resources 40, 44 product installation resources 44 Q QuickSpecs 40, 43, 44 R RCEC 47 reconfiguring software 35 redundant ROM 36 registering the server 44 reloading software 35 removal and replacement procedures 45 resources 57 resources, troubleshooting 42 restoring 35 ROM error 36, 37, 48 ROM redundancy 36 ROM, updating 37 S safety considerations 6, 7, 8 safety information 6 serial port 33 server documentation 45, 46 server response time 32 server specifications 45 Service Packs 34 software 34, 40, 43, 46 software errors 36 software failure 35 software problems 34 software resources 40, 46 software troubleshooting 34, 35, 36 specifications 45 specifications, option 45 specifications, server 45 static electricity 7 supported operating systems 46 switch connectivity problems 23 switch health LEDs 13 switch LEDs 13 switch power problems 22 symbols in text 45 symbols on equipment 6, 45 symptom information 9 T teardown procedures 45 Index 63 technical support 43, 57 technical topics 45 technology services 43 telephone numbers 57 troubleshooting 24 troubleshooting resources 42 U unknown problem 25 updating the firmware 43 utilities 40 V videos, HPE Moonshot 43 W warnings 45 website, Hewlett Packard Enterprise 44, 57 white papers 43, 45 Index 64