Hewlett Packard Enterprise Management Web Interface Moonshot iLO Chassis User Guide
Reklāma
Reklāma
HPE Moonshot iLO Chassis
Management Web Interface
User Guide
Abstract
This guide provides information about configuring, updating, and operating HPE Moonshot Systems by using the
Moonshot iLO Chassis Management web interface. This document is intended for system administrators, Hewlett
Packard Enterprise representatives, and Hewlett Packard Enterprise Authorized Channel Partners who are involved in configuring and using HPE Moonshot Systems.
Part
Number: 802725-004
Published:
February 2017
Edition:
1
© Copyright 2012, 2017 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.
Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or copying. Consistent with FAR
12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise website.
Acknowledgments
Intel ®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in the United States and other countries.
Microsoft ® and Windows® are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
Adobe ® and Acrobat® are trademarks of Adobe Systems Incorporated.
Java and Oracle are registered trademarks of Oracle and/or its affiliates.
UNIX ® is a registered trademark of The Open Group.
Contents
1 Introduction to the HPE Moonshot iLO Chassis Management web interface......5
3 Using the web interface to view Moonshot System details ..............................11
Contents 3
4 Contents
1 Introduction to the HPE Moonshot iLO Chassis
Management web interface
Overview
The Moonshot iLO Chassis Management web interface allows GUI-based aggregated chassis management on the Moonshot System. The interface runs on the iLO CM firmware version 1.30
and later, and provides access to many of the same functions available from the iLO CM firmware command line. The interface allows you to view component information, configure settings, update firmware, and operate Moonshot via a detailed graphical environment.
HPE Moonshot iLO CM firmware web interface features
Using the iLO CM firmware web interface, you can do the following:
•
View extensive chassis, cartridge, node and switch details and health information, all event and IML logs down to the node level, active sessions (both via CLI and web interface), and power, fan and temperature details.
•
View firmware versions and update firmware for components, including the chassis components, cartridges, nodes, and switches using local or remote files, or files that are loaded in the Chassis Manager Repository.
•
Manage the power and booting of all server nodes, and the power for cartridges and switches.
•
Configure Moonshot 1500 Chassis networking and hostname.
•
Configure SSL certificate security, time settings, and up to 12 local user accounts.
Moonshot web interface
The Moonshot web interface common areas, icons, and controls are shown below.
Overview 5
1. HPE Moonshot main menu: The primary menu for navigating to resources. Click to expand.
2. View customization menus: Filters your view to only the desired components. Also available to customize log views.
3. View selector: Enables you to select the information displayed about a resource.
4. Actions menu: Provides the actions that are available to run on the current resource. Actions include, but are not limited to: adding, creating, deleting, removing, and editing a resource instance. If you do not have the appropriate permissions to perform an action, the action does not appear on the Actions menu.
5. Activity control: Expands (or hides) a sidebar of recent activity (from the current login session). This icon displays a number badge to indicate the number of activities recorded in the session.
6. Session control: Session control: Displays the current user and duration of the current session. Also provides links to the User Administration page , the Active Sessions page, and a link to Logout of the session.
7. Help control: Opens a new browser page which displays the online help.
8. Activity sidebar: Shows recent alert and task activity for the current resource. Use the Activity control icon to open
(or close) this sidebar.
9. Details pane: Provides information about a selected resource.
10. Master pane: Lists all resource instances that have been configured on the appliance. In some cases, a status icon indicates general health of the resource.
Moonshot scripting and command line
You can use basic scripting tools to configure the iLO CM firmware, and to develop and incorporate a standard configuration into the deployment process for multiple Moonshot 1500 Chassis
Management Modules.
The HPE Moonshot iLO Chassis Management CLI User guide describes the syntax and tools available for using the ILO CM firmware through a command line interface.
6 Introduction to the HPE Moonshot iLO Chassis Management web interface
RESTful API for HPE Moonshot iLO Chassis Manager
HPE iLO CM firmware version 1.30 and later includes the RESTful API for iLO Chassis Manager.
The RESTful API is a management interface that server management tools can use to perform configuration, inventory, and monitoring of a Moonshot System.
For more information about the RESTful API see the following website: http://www.hpe.com/
info/restfulinterface/docs.
RESTful API for HPE Moonshot iLO Chassis Manager 7
2 Setting up a Moonshot System
Overview
The default settings enable you to use most features without additional configuration. However, the configuration flexibility of iLO CM firmware enables customization for multiple enterprise environments. This chapter references the initial iLO CM setup steps.
Complete the initial setup steps:
1.
Install the Moonshot System in a data center.
For more information, see the moonshot 1500 chassis setup and installation guide available at http://www.hpe.com/info/moonshot/docs.
2.
Connect the Moonshot System to a network.
For more information, see
“Connecting the Moonshot System to a network” (page 8)
.
3.
If you are not using dynamic IP addressing, configure a static IP address.
For more information, see
“Managing network settings” (page 56) .
4.
Set up your local user accounts.
For more information, see
“iLO CM firmware user accounts” (page 81)
.
Connecting the Moonshot System to a network
You can connect the Moonshot System to the following networks:
•
Data center management network
•
Data center production network
Data center management network
To connect the chassis to a management network, connect an Ethernet cable from the Moonshot
1500 CM module to the management network. Always connect to the iLO CM management port first. Do not connect both the iLO CM management port and the iLO CM link port to the same network switch. For information about enabling the iLO link port using the set network daisy command, see the HPE Moonshot iLO chassis management CLI user guide in the moonshot information library (http://www.hpe.com/info/moonshot/docs).
Moonshot iLO CM firmware SSH sessions and switch SSH sessions share connectivity through the iLO CM management port. The iLO CM management port is located on the Moonshot 1500
CM module on the rear of the chassis.
8 Setting up a Moonshot System
Data center production network
To connect the chassis to a production network, connect to any available SFP+ or QSFP+ port.
The SFP+/QSFP+ ports are located on the uplink module installed in the rear of the chassis.
•
Moonshot-6SFP Uplink Module
•
Moonshot 4QSFP+ Uplink Module
Connecting the Moonshot System to a network 9
Setting up Moonshot by using the Moonshot iLO CM firmware web interface
You can use the iLO CM firmware web interface to configure the Moonshot System if you can connect to the web interface on the network with a web browser.
Access the iLO CM firmware web interface from a remote network client by using a supported browser to access the hostname and then entering a user name and password.
Logging in to the iLO CM firmware web interface for the first time
The iLO CM firmware web interface is configured with a default user name and password. Use these values to access the web interface remotely from a network client through a web browser.
The default values follow:
•
User name—Administrator
•
Password—password
•
DNS name—The pre-set DNS information uses the serial number located on a label attached to the chassis that contains the Moonshot 1500 CM module
In a DHCP environment, the serial number is registered as the host/DNS name with the DNS server on boot. Enter the serial number from the label together with the domain name into a browser address bar (in an HTTPS session) to access the iLO CM firmware web interface. For example, if the serial number is iLOCM1234 and your domain is domain.com, then enter
https://ilocm1234.domain.com
into the address bar of a supported browser.
Alternatively, use the DNS name (serial number) to determine the IP address using standard network tools.
If you enter an incorrect user name and password, or a login attempt fails, the web interface imposes a security delay.
IMPORTANT:
Hewlett Packard Enterprise recommends changing the default Administrator password after you log in to web interface for the first time. For instructions, see
“iLO CM firmware user accounts” (page 81)
.
If you reset Moonshot 1500 CM module to the factory default settings, use the default account information to log in after the reset.
10 Setting up a Moonshot System
3 Using the web interface to view Moonshot System details
This chapter provides information about viewing the available information using Moonshot web interface.
iLO CM firmware web interface
You can use the iLO CM firmware web interface to manage the HPE Moonshot System. You can also use the iLO CM firmware command line.
For more information about the command line, see the Moonshot iLO Chassis Management CLI user guide.
Browser support
The iLO CM firmware web interface requires a browser that meets the following requirements:
•
JavaScript—The iLO CM firmware web interface uses client-side JavaScript extensively.
•
Cookies—Cookies must be enabled for certain features to function correctly.
•
Pop-up windows—Pop-up windows must be enabled for certain features to function correctly.
Verify that pop-up blockers are disabled.
•
TLS—To access the iLO CM firmware web interface, you must enable TLS 1.0 or later in your browser.
For a list of supported browsers, see
Table 1 Supported browsers iLO CM firmware version Internet Explorer
1.51
11
Firefox
ESR 24
Chrome
Latest version
Logging in to the iLO CM firmware web interface
1.
Enter https://<iLO CM firmware host name or IP address>.
You must access the iLO CM firmware web interface through HTTPS.
2.
Do one of the following:
•
On the login page, enter a directory or local user account name and password, and then click Log In.
•
Click the Zero Sign In button.
If the iLO CM firmware web interface is configured for Kerberos network authentication, the Zero Sign In button is displayed below the Log In button. Clicking the Zero Sign
In button logs the user in without requiring the user to enter a user name and password.
For information about login issues, see
Viewing overview information
Viewing Moonshot general information
From the main menu, select Chassis to display high level information about the chassis. It includes general chassis information and reference images of the chassis, along with cartridge health and node power gauges.
iLO CM firmware web interface 11
Viewing the Chassis top view
From the main menu, select Chassis to view chassis cartridge and switch information.
The Top View section includes an interactive image that displays a representation of the cartridge and switch slots of the Moonshot chassis. Unoccupied or locked slots (slots to which you do not have access) are gray, while unlocked populated slots are white and include power, health, and
UID indicators. These slots offer more information when rolled over with the mouse.
NOTE:
Slots that are gray and show a lock symbol ( ) have been specifically blocked by settings in your user account. If you have restricted access to only specific cartridges and switches, all other pages of the interface show only the Moonshot components to which you have access.
You may also see the message “Logged-in user does not have the privilege” depending on the page you are viewing.
To view cartridge information
To view cartridge information, roll over a populated cartridge slot with the mouse.
•
Launch IRC icon—Click this icon to launch the iLO integrated remote console on compatible cartridges (when linked with an mRCA).
•
Health icon—each cartridge displays a health indicator:
◦
OK—No health issues
◦
Degraded—Significant service issue with possible service degradation
12 Using the web interface to view Moonshot System details
◦
Critical—Service lost or imminent service loss, immediate attention needed
◦
Unknown
•
Cartridge number
NOTE:
Click the cartridge number link to open the Cartridges page and display specifics about the installed cartridge. For more information, see
Viewing ProLiant server cartridge information .
•
Cartridge name (model)
•
CPU number and architecture
•
UID control—click this icon to turn the cartridge UID on or off.
◦
UID is off. Click the icon to turn the UID on.
◦
UID is on. Click the icon to turn the UID off.
◦
UID is blinking. A blinking UID indicates the cartridge might be in an active integrated remote console session, or a firmware update is in progress.
•
Power indicator—This icon reports the cartridge’s power status.
◦
The cartridge is powered off.
◦
One or more nodes are powered on.
To view switch information
To view switch information, roll over a populated switch slot with the mouse.
•
Health icon—each switch displays a health indicator:
◦
OK—No health issues
◦
◦
Degraded—Significant service issue with possible service degradation
Critical—Service lost or imminent service loss, immediate attention needed
◦
Unknown
•
Switch designator
NOTE:
Click the link to open the Switches page and display specifics about the installed switches. For more information, see
•
Model
Viewing overview information 13
•
UID control—click this icon to turn the switch UID on or off.
◦
UID is off. Click the icon to turn the UID on.
◦
UID is on. Click the icon to turn the UID off.
•
Switch power control—This icon simulates the physical power button on the switch. Click the icon to turn the switch on or off.
◦
◦
The switch is off.
The switch is on.
Viewing the chassis back view
From the main menu, select Chassis to view basic chassis fan and power supply information using the back view.
The Back View section displays a representation of the fans, Moonshot Uplink Modules, the
Moonshot 1500 CM Module, and the power supplies installed in the Moonshot chassis. Unoccupied slots are gray. Populated slots are white and show a health icon and basic status information:
•
Fans (top row)—Displays the speed (from zero to 100 percent) of each fan. Hover over an installed fan with the mouse to display a link to the
.
•
Moonshot Uplink Modules and Moonshot 1500 CM Module (center row): Displays the presence of the components, and the status of the Moonshot 1500 CM module.
◦
Moonshot Uplink Modules—On the left and the right of this row, uplink positions are displayed.
◦
Moonshot 1500 CM Module—In the center of this row, the module position is displayed, along with the health, UID state, and power status. Click the UID icon to turn it on or off.
•
Power supplies (bottom row)—Displays the current output in watts for each power supply.
Hover over an installed power supply with the mouse to display a link to the
Viewing general chassis information
From the main menu, select Chassis to view chassis information.
The Chassis Information section displays the following information:
The Cartridge Health gauge shows the health of all cartridges. The gauge is divided into cartridges that have critical issues, issues that cause degraded performance, and cartridges that are OK (have no issues).
•
•
•
Critical
•
Degraded
•
OK
•
Unknown
The Node Power State gauge displays the total number of nodes in the Moonshot 1500 Chassis, and how many are powered on and off.
Nodes that are off.
Nodes that are on.
14 Using the web interface to view Moonshot System details
Viewing ProLiant server cartridge information
The Moonshot web interface Cartridges page displays information about the HPE ProLiant server cartridges installed in the Moonshot 1500 Chassis.
NOTE:
If you have restricted slot access, the interface shows only the Moonshot components to which you have access. You may also see the message “Logged-in user does not have the privilege” depending on the page you are viewing.
Customizing the cartridge list
By default, all of the cartridges installed in the Moonshot 1500 Chassis are listed in the left pane, including Health, Cartridge (slot), and Model information. Filter which cartridges are displayed in the list by using the cartridge filter menus.
To customize the cartridge list, do one or more of the following:
1.
Click the System Power menu and select one or more power states. A selected filter is bold. Click a bold entry again to deselect it.
2.
Click the Server health menu and select one or more health states. A selected filter is bold.
Click a bold entry again to deselect it.
3.
Click the UID menu and select one or more UID states. A selected filter is bold. Click a bold entry again to deselect it.
4.
Click Reset filters to return all filters to the default selections. By default, all selections from each filter are shown (all power states, all health statuses, and all UID states).
Selecting multiple cartridges
To select multiple cartridges from the cartridge list, do one of the following:
•
Hold Ctrl and click each cartridge to be selected.
•
Click Select all.
•
Click a cartridge to select it, hold Shift, and then click another cartridge to select all the cartridges between the two selections.
Viewing overview information 15
Viewing Moonshot cartridge overview information
From the main menu, select Cartridges to view cartridge overview information. The page defaults to an overview of the first cartridge in the list of all available cartridges, shown on the left side of the page.
The General section displays the following:
•
Model—The model name of the server cartridge.
•
Product ID—The product ID of the server cartridge. This value is set by the manufacturer, but can be changed by an Administrator using the iLO CM firmware command line if the server cartridge is replaced.
•
Serial number—The serial number of the server cartridge. This value is assigned when the system is manufactured, but can be reset by an Administrator using the command line if the server cartridge is replaced.
•
AutoRev—The hardware revision of the cartridge. Used by Hewlett Packard Enterprise
Support.
•
Manufacturing date—The date the server cartridge was built.
•
Cartridge Asset Tag—The end-user defined cartridge tracking number for your organization.
Assign an asset tag using the Action menu.
The Cartridge Information section displays the following:
•
Power—Indicates the power state of the cartridge.
◦
The cartridge is powered off.
◦
One or more cartridge server nodes are powered on.
•
Health status—each cartridge displays a health indicator:
◦
OK—No health issues
◦
Degraded—Significant service issue with possible service degradation
◦
Critical—Service lost or imminent service loss, immediate attention needed
◦
Unknown—A detected health problem cannot be classified
•
Cartridge UID—Shows the state of the UID for the server cartridge.
◦
UID is off.
◦
UID is on.
◦
UID is blinking. A blinking UID indicates the cartridge might be in an active integrated remote console session, or a firmware update is in progress.
•
Management status—Displays whether the Moonshot web interface is successfully managing the server cartridge.
•
Instant wattage—A reading of the current power usage of the server cartridge.
•
Links—Displays the cartridges that are linked to the selected cartridge.
•
Login to iLO—Provides a convenient link to open a window to the iLO login page for the cartridge (if linked via an mRMA.) See
Launching an Integrated Remote Console session
for more information.
16 Using the web interface to view Moonshot System details
The System Firmware section displays the following, as applicable. If the selected cartridge does not have a specific firmware, it is not displayed:
•
System ROM firmware
•
CPLD
•
Satellite firmware
•
Cartridge data
•
iLO
•
Mellanox ConnectX3Pro
•
Mellanox ConnectX3
•
SLIMpro
•
System ME ROM
The Mezzanine section displays information about any accessory cards attached to the server cartridge. If present, the information can include the following for each mezzanine attachment:
•
Model—The model name of attached accessory.
•
Serial number—The serial number of the attached accessory.
•
Spare part number—The part number of the spare attached accessory.
•
Cartridge mezz data—The version of the accessory’s data firmware file.
When multiple cartridges are selected, the Overview page changes to display the following information about each cartridge:
•
Name
•
Model
•
Asset Tag
•
Power
•
UID
•
Health status
•
Management status
•
AutoRev
•
Instant wattage
•
Product ID
•
Serial number
Assigning or changing a cartridge asset tag
1.
Select a cartridge.
2.
Click Actions→Set Cartridge Asset Tag.
The edit cartridge asset tag settings window appears.
3.
Enter a new asset tag or edit the existing tag in the Asset tag box.
4.
Click Apply to save your changes and close the window, or click Cancel to close the window without saving.
Changing the state of a cartridge’s UID
To change the state of a cartridge UID:
Viewing overview information 17
1.
Select a cartridge.
2.
Click Actions→UID on or UID off, depending on the current state of the cartridge UID.
The icon changes to indicate the new UID state, and an activity message briefly appears at the top right of the screen.
Changing the power state of a cartridge
To change the power state of a cartridge:
1.
Select one or more cartridges.
2.
Click Actions→Power off or Power on.
When powering off a cartridge, the iLO CM firmware warns you that this action will force the power off on the cartridge (and the nodes).
3.
Click Yes if powering off a cartridge.
Launching an Integrated Remote Console session
An Integrated Remote Console is a graphical remote console that turns a supported browser into a virtual desktop, allowing full control over the display, keyboard, and mouse of a ProLiant server cartridge. Using the Remote Console also provides access to the remote file system and network drives.
With Integrated Remote Console access, you can observe POST boot messages as the ProLiant server cartridge node restarts. When you are installing operating systems remotely, the Integrated
Remote Console enables you to view and control the ProLiant server throughout the installation process.
NOTE:
When opening an IRC session to a compute cartridge with iLO, no mRCA is needed.
Compute cartridges without iLO must be linked to an mRCA to provide IRC capabilities.
Integrated Remote Console launch options
.NET IRC—Provides access to the system KVM, allowing control of Virtual Power and Virtual
Media from a single console through a supported browser on a Windows client. In addition to the standard features, the .NET IRC supports Console Capture, Shared Console, Virtual Folder, and Scripted Media. The option is only available when using Internet Explorer.
Java Web Start and Java Applet—Provide access to the system KVM, allowing control of Virtual
Power and Virtual Media. In addition to the standard features, the Java IRC includes the iLO disk image tool and Scripted Media. Choose one of these options when you are not using Internet
Explorer.
NOTE:
When using the Chrome browser and selecting the Java Web Start option, you must accept the download of a .jnlp file. Once downloaded, click on the file to continue opening the
IRC session.
Integrated Remote Console usage information and tips
•
Pop-up blockers prevent the Remote Console from running.
•
You must use a compatible browser to access the Remote Console. Hewlett Packard
Enterprise recommends using Internet Explorer version 11 or later.
NOTE:
You must have .NET Framework version 3.5 or later installed to enable Remote
Console sessions. If you have an earlier version installed, you may see a message about a required system update when you attempt to launch a remote session.
•
If you receive a permission error when mounting Virtual Media in a Remote Console session, and you are using Microsoft Internet Explorer, restart the session with a fresh Internet Explorer window with administrator level permissions (Run as Administrator).
18 Using the web interface to view Moonshot System details
•
When you refresh or close the iLO web interface window, the Remote Console connection is closed, and you will lose access to Virtual Media devices that were connected through the Remote Console.
•
If you mount a Virtual Drive of type URL during an IRC session, use the IP address and not a domain name. This avoids any errors if the cartridge iLO cannot resolve the domain name.
To launch an Integrated Remote Console session:
1.
If you are not using a compute cartridge with iLO, then ensure that you link an mRCA with the desired cartridge. For more information, see
“Viewing and editing cartridge links” (page
2.
Select the Cartridges page from the main menu.
3.
Select either a compute cartridge with iLO or select an mRCA from the list in the left pane.
NOTE:
The compute cartridge without iLO to which you can link the mRCA is dependent on the slot position of the mRCA in the chassis. For more information, see the moonshot system configuration and compatibility guide in the moonshot information library at http://
www.hpe.com/info/moonshot/docs.
4.
Do one of the following:
•
Click Actions→Integrated Remote Console.
•
Click the monitor icon next to the Actions menu.
•
Click the Login link under the Cartridge Information section.
•
On the Chassis page, roll over an mRCA or compute cartridge with iLO and then click the monitor icon.
A session selection screen appears.
5.
Select one of the following:
•
.NET
•
Java WebStart
•
Java Applet
See
“Integrated Remote Console launch options”
for more information.
6.
Click Launch.
The session opens in a new window or tab (depending on your browser settings.)
NOTE:
The server cartridge node to which you can link the mRCA is dependent on the slot position of the mRCA in the chassis. For more information, see the Moonshot System Configuration
and Compatibility Guide in the moonshot information library at http://www.hpe.com/info/
moonshot/docs.
Calculating the web address for server cartridges with iLO
Besides the existing methods offered by the iLO CM web interface for starting an iLO remote session with a compatible ProLiant server cartridge, you can also determine cartridge web addresses independently. For HPE ProLiant server cartridges that offer on-board iLO, the iLO web address for a server cartridge is:
https://<iLO CM IP>:(735+<slot number>)
Where:
•
<iLO CM IP>
is the IPv4 address of the iLO Chassis Manager
•
<slot number>
is a number from 1 to 45, corresponding to the slot in which the server cartridge is installed
Viewing overview information 19
For example, if the iLO CM chassis manager IP address is 192.0.2.15, and the server cartridge is in slot 1, the web address would be:
https://192.0.2.15:736
Viewing cartridge logs
Cartridge logs provide a record of historical events that have occurred. Events are generated by the system ROM and include all cartridge-specific events. Log entries can help you diagnose issues or identify potential issues. Preventative action might help to avoid disruption of service.
From the main menu, select Cartridges to view the Cartridges page. The page defaults to an overview of the first cartridge in the list of all available cartridges, shown on the left side of the page. Select Logs from the View menu to show the cartridge logs.
The Log information available for each cartridge includes the following:
•
ID—The event ID number. Events are numbered in the order in which they are generated.
By default, the Event Log is sorted by the ID, with the most recent event at the top.
•
Severity—The importance of the detected event.
Possible values include:
◦
Critical—The event indicates a service loss or an imminent service loss. Immediate attention is needed.
◦
Caution—The event is significant but does not indicate performance degradation.
◦
Informational—The event provides background information.
◦
Repaired—An event has undergone corrective action.
◦
Unknown—The event severity could not be determined.
•
Type—A further descriptor of the nature of the event.
•
Created on—For events with a count of 1, this is the date the event first occurred. For events with a count greater than 1, this is column shows the date the event was last updated.
•
Count—The number of times this event has occurred (if supported).
In general, important events generate an event log entry each time they occur. They are not consolidated into one event log entry.
When less important events are repeated, they are consolidated into one event log entry, the Count value is updated. Each event type has a specific time interval that determines whether repeated events are consolidated or a new event is logged.
•
Description—The description identifies the component and detailed characteristics of the recorded event.
Customizing the cartridge log view
You can customize which log entries are displayed as follows:
•
To filter by severity, select a severity level from the Severity menu. The selection is cumulative; and you can select more than one severity level. A selected severity level is bold. Click a bold entry again to deselect it.
20 Using the web interface to view Moonshot System details
•
Select a preset range or a date range in the Created on menu.
•
To search for events based on dates, event IDs, or description text, enter text in the Search box, and then press Enter.
•
Click Reset filters to set the filters back to the default values.
Saving the cartridge event log
To save the cartridge Moonshot Event Log as a CSV file:
Viewing overview information 21
1.
Click Actions→View CSV.
The Moonshot Event Log CSV for the cartridge is displayed.
2.
Click Save or click Close to close the window.
Clearing the cartridge IML
Users with the Administrator and Operator privilege can clear a cartridge IML of all previously logged information.
To clear a cartridge IML:
1.
Click Actions→Clear Log.
The following message appears:
All log entries for this device will be deleted. This action cannot be undone. Continue with clearing the log?
2.
Click Yes.
The log is cleared and a new entry is recorded which includes the date and time of the event, the responsible user, and the cartridge number.
Viewing cartridge temperature sensor data
Select Thermal from the View menu to show the cartridge temperature sensor data. Temperatures are displayed in degrees Celsius.
22 Using the web interface to view Moonshot System details
The Thermal table displays the following information for the selected cartridge:
•
Sensor—The ID of the temperature sensor, which also gives an indication of the sensor’s location.
•
Status—The temperature status of the cartridge. Depending on the server cartridge configuration, some sensors show a status of Not installed.
•
Current Reading—The temperature recorded by the listed temperature sensor. If a temperature sensor is not installed, the Current Reading column shows the value N/A.
•
Thresholds—The temperature thresholds for the warning for overheating conditions. The two threshold values are Caution and Critical. If a temperature sensor is not installed, the
Thresholds column shows the value N/A.
◦
Caution—The cartridge is designed to maintain a temperature below the caution threshold while operating. If a failure prevents the cartridge from maintaining this temperature, the chassis increases the fan speed and initiates a graceful operating system shutdown. This ensures both data integrity and system safety.
◦
Critical—If temperatures are uncontrollable or rise quickly, the critical temperature threshold prevents system failure by physically shutting down the cartridge before the high temperature causes an electronic component failure.
•
Temperature Meter—A graphical representation of the current temperature reading and whether that reading has reached the Caution or Critical thresholds. The left edge of the column represents a temperature of 0°C, the grey bar represents the Caution threshold, and the right edge of the column represents the Critical threshold. If a temperature sensor is not installed, is missing, or is not reporting a temperature reading, an empty graph is displayed.
Viewing thermal history
Scroll down to see the Thermal History graph and choose a sample period and select the sensors to be displayed.
Viewing overview information 23
The graph displays the specified temperature along the y axis, with the specified sample period along the x axis.
•
When temperatures are displayed in Celsius, click the F button to change the display to
Fahrenheit. When temperatures are displayed in Fahrenheit, click the C button to change the display to Celsius.
•
The circles on the graph correspond to the sensors listed in the Sensor Name column to the right of the table.
•
Move the mouse over a circle on the graph to view the sensor ID and temperature reading.
Each sensor has a unique associated color.
•
The color on the graph is a gradient that ranges from blue to red to white. Blue represents a temperature of 0°C to approximately 24°C and the gradient changes from blue to red as temperatures get hotter.
To change the sample view, select a new sample period from the column to the right of the graph.
A true full history of temperature data is not saved due to memory restraints. Instead, the temperature data is averaged in the following sample sizes:
•
Last Minute (2 seconds)—Displays the averages for the last minute with samples every two seconds.
•
Last Hour (1 minute)—Displays the averages for the last hour with samples every minute.
•
Last Day (1 hour)—Displays the averages for the last day with samples every hour.
24 Using the web interface to view Moonshot System details
•
Last Month (1 day)—Displays the averages for the last month with samples every day.
•
Last Year (1 month)—Displays the averages for the last year with samples every month.
To change which sensors are displayed in the graph, select the sensors from the Sensor Name list to the right of the graph. Be default, all sensors are selected. Unavailable sensors are grayed out and are inactive.
NOTE:
Thermal history samples only record temperatures since the iLO CM was powered on.
Thermal history is reset whenever the iLO CM is powered off and then on.
Viewing cartridge power data
Select Power from the View menu to show a graph of power consumption that allows you to choose a sample period and select the series to be displayed.
The graph displays the specified power usage in Watts along the y axis, with the specified sample period along the x axis.
•
Click the Watts or BTU/h buttons to specify how to display the power usage.
•
The circles on the graph correspond to the series listed in the Series Name column to the right of the table.
•
Move the mouse over a circle on the graph to view the series name and power usage reading.
Each series has a unique associated color.
To change the sample view, select a new sample period from the column to the right of the graph.
A true full history of temperature data is not saved due to memory restraints. Instead, the temperature data is averaged in the following sample sizes:
•
Last 5 Minutes (15 seconds)—Displays the averages for the last five minutes with samples every 15 seconds.
•
Last Hour (5 minutes)—Displays the averages for the last hour with samples every five minutes.
•
Last Day (1 hour)—Displays the averages for the last day with samples every hour.
Viewing overview information 25
•
Last 2 Weeks (1 day)—Displays the averages for the last two weeks with samples every day.
•
Last Year (2 weeks)—Displays the averages for the last year with samples every two weeks.
To change which information to display in the graph, select a series from the Series Name list to the right of the graph. Be default, all available series are selected. Unavailable series are grayed out and are inactive.
Viewing ProLiant server cartridge node information
The Moonshot web interface Nodes page displays information about the ProLiant server cartridges installed in the chassis.
NOTE:
If you have restricted slot access, the interface shows only the Moonshot components to which you have access. You may also see the message “Logged-in user does not have the privilege” depending on the page you are viewing.
Customizing the node list
You can customize which nodes are displayed in the node list by using the node filter menus. A selected filter is bold. Click a bold entry again to deselect it.
Customize the node list by doing one or more of the following:
•
Select a power state from the System Power menu.
•
Select a health status from the Server health menu.
•
Select a boot source from the Boot options menu.
•
Click the Reset filters link to start over with the default selections.
26 Using the web interface to view Moonshot System details
Viewing ProLiant server cartridge node overview information
From the main menu, select Nodes to view node overview information. The page defaults to an overview of the first node in the list, shown on the left side of the page, of installed nodes.
The General section displays the following about the server cartridge on which the node is installed:
•
Model—The model name of the server cartridge.
•
Product ID—The product ID of the server cartridge. This value is set by the manufacturer, but can be changed by an Administrator using the iLO CM firmware command line.
•
UUID—The universally unique identifier for the node. This value is assigned when the system is manufactured.
•
Serial number—The serial number of the cartridge on which the node resides.
•
Node Asset Tag—Your organization’s asset tag information for the node.
Assign an asset tag using the Action menu.
The Node status section displays the following:
•
Power—The node power status.
◦
The node is off.
◦
The node is on.
The Node Details section displays the following:
•
Processor family—The architecture of the processor.
•
Number of cores—The number of processing cores in the node.
•
Max clock speed—The maximum operating speed of the node cores expressed in MHz.
•
Total memory—The amount of permanent system memory available to the node expressed in GB.
•
DIMM <x>—(Where x is a number indicating the memory slot.) This displays the amount of additional (optional) memory, and the serial number of the DIMM.
•
MAC<x>—(Where x is a number indicating the number of the MAC address.) This displays the media access control (MAC) address.
•
Disk <x>—(Where x indicates the disk number.) The disk section includes the following information regarding installed storage drives:
◦
Model—The model number of the disk.
◦
Serial Number—The serial number of the disk.
◦
Firmware—The version of manufacturer-installed firmware.
NOTE:
The displayed information regarding storage drives varies based on the type of drive, the model of ProLiant server cartridge, and whether the node was booted after the
HPE Moonshot 1500 Chassis booted.
•
Trusted Platform Module (TPM)—Indicates whether the TPM is enabled or disabled.
When an embedded Trusted Platform Modules is included with a ProLiant server cartridge, it is disabled by default. If a ProLiant server cartridge with an enabled TPM is booted at least once in the Moonshot chassis, the presence and status of the TPM is reported on this page.
To change the status of a TPM, access the node’s BIOS configuration.
Viewing overview information 27
The Node Settings section displays the following, as applicable. If the selected node does not support a certain setting, it is not displayed:
•
Boot order—The boot devices available to the node and the order in which a typical boot sequence will search for boot information.
•
Boot once—The boot device to be used on the next boot only.
•
WOL—The node wake on LAN (WOL) setting.
•
CPU speed—The selected CPU speed.
•
BSC—Whether the BIOS serial console is enabled or disabled. If this setting is not supported by the node, N/A is displayed.
Selecting multiple nodes
You can select more than one node from the node list. Selecting at least two nodes displays the following information about the selected nodes, as applicable. If the selected nodes do not support a certain feature, it is not displayed:
•
Name
•
Model
•
Power
•
SKU
•
Serial number
•
UUID
•
Host MAC Address
•
Boot once
•
Boot order
•
BSC
•
HyperThreading
•
WOL
•
BootType
•
RestoreUEFIDefaults
•
CPU
Downloading node information
When at least two nodes are selected on the Nodes page, you can create a CSV file of the information displayed.
1.
From the main menu, select Nodes.
2.
Select two or more nodes in the node list.
3.
Click Actions→View CSV.
The Download Nodes Information screen displays, with the node information showing in comma separated format.
4.
Do one of the following:
•
Copy the information and paste it into a separate document.
•
Click Save, and depending on your browser settings, choose where to save the .csv
file. Saving the information closes the window automatically.
5.
If needed, click Close to close the screen.
28 Using the web interface to view Moonshot System details
Selecting node boot options
The boot order, boot once, and other boot options can be set from the Nodes page for one or more nodes. From the main menu, select Nodes and then select one or more nodes from the list in the left pane.
To set node boot options:
1.
Click Actions→Boot options. The Select boot options page displays.
2.
In the Select boot order section, select the following:
•
Boot device 1—The primary device to seek on boot.
•
Boot device 2—The secondary, or backup, device to seek on boot if the primary device is not present or contains no boot instructions.
3.
In the Select boot once section, select a device to seek on boot for the next boot only.
Boots subsequent to the next boot revert back to the Boot device 1 and 2 settings.
4.
In the Select boot options section, depending on the cartridges selected, select from the following:
•
BSC—Enable or disable access to the BIOS serial console. The selection becomes active on the next boot. If this option is unsupported, the selections are unavailable. A
Viewing overview information 29
third option, do not apply, appears only when multiple nodes are selected, allowing you to skip enabling or disabling the setting when it’s supported.
•
HyperThreading—Enable or disable HyperThreading, which allows compatible ProLiant server cartridge nodes and operating systems to address each physical processor core as two logical cores.
•
Wake-On-LAN (WOL)—Enable or disable WOL for the node. The selection becomes active on the next boot. If this option is unsupported, the selections are unavailable. A third option, do not apply, appears only when multiple nodes are selected, allowing you to skip enabling or disabling the setting when it’s supported.
•
BootType—Select the type of boot sequence for the node, either legacy Uboot or UEFI.
•
RestoreUefiDefaults—Restores the original factory UEFI settings for the node.
•
CPU—Select a speed for the CPU to adopt on the next boot. Unsupported cartridge nodes show N/A in this menu.
5.
Click Apply to assign the chosen settings, or click Cancel.
Changing the power state of a node
To change the power state of a node:
1.
Select one or more nodes.
2.
The available selections depend on the current state of the selected nodes. Do one of the following:
•
Click Actions→Power off Node (Shutdown) to gracefully exit the running operating system and power off the node.
•
Click Actions→Power off Node (Force) to power off the node when an OS is not installed.
•
Click Actions→Power On Node to power on the selected node.
NOTE:
When planning to change the power state for multiple selected nodes, Hewlett
Packard Enterprise recommends that you verify that all the selected nodes have the same current power state before selecting a power state change from the Actions menu.
Setting a node asset tag
To set or change the asset tag for a node:
1.
Select one or more nodes. If you select multiple nodes, the asset tag you specify will be assigned to all selected nodes.
2.
Click Actions→Set Node Asset Tag.
The Node Asset Tag window displays.
3.
Enter an asset tag in the space provided.
4.
Click Apply to assign the tag, or click Cancel.
Viewing node logs
Node logs provide a record of historical events that have occurred. Events are generated by the system ROM and include all node-specific events. Log entries can help you diagnose issues or identify potential issues. Preventative action might help to avoid disruption of service.
To view the Nodes page, from the main menu, select Nodes. The page defaults to an overview of the first node in the node list, shown on the left side of the page. Select Logs from the View menu to show the node logs.
30 Using the web interface to view Moonshot System details
The log information available for each node includes the following:
•
ID—The event ID number. Events are numbered in the order in which they are generated.
By default, the log is sorted by the ID, with the most recent event at the top.
•
Severity—The importance of the detected event.
Possible values include:
◦
Critical—The event indicates a service loss or an imminent service loss. Immediate attention is needed.
◦
Caution—The event is significant but does not indicate performance degradation.
◦
Informational—The event provides background information.
◦
Repaired—An event has undergone corrective action.
◦
Unknown—The event severity could not be determined.
•
Type—A further descriptor of the nature of the event.
•
Created on—For events with a count of 1, this is the date the event first occurred. For events with a count greater than 1, this is column shows the date the event was last updated.
•
Count—The number of times this event has occurred (if supported).
In general, important events generate an event log entry each time they occur. They are not consolidated into one event log entry.
When less important events are repeated, they are consolidated into one event log entry, the Count value is updated. Each event type has a specific time interval that determines whether repeated events are consolidated or a new event is logged.
•
Description—The description identifies the component and detailed characteristics of the recorded event.
Customizing the node log view
You can customize which log entries are displayed as follows:
•
To filter by severity, select a severity level from the Severity menu. The selection is cumulative; and you can select more than one severity level. A selected severity level is bold. Click a bold entry again to deselect it.
•
Select a preset range or a date range in the Created on menu.
Viewing overview information 31
•
To search for events based on dates, event IDs, or description text, enter text in the Search box, and then press Enter.
•
Click Reset filters to set the filters back to the default values.
Saving a node event log
To save the node event log as a CSV file:
1.
Select Actions→View CSV.
The node event log is displayed in a format that you can copy and paste into a text editor.
2.
Click Save, and then follow the browser prompts to save or open the file.
3.
Click Close to close the window.
Clearing a node event log
Users with the Administrator privilege can clear logs of all previously logged information.
To clear a node event log:
1.
Select Actions→Clear Log.
The following message appears:
All log entries for this device will be deleted. This action cannot be undone. Continue with clearing the log?
2.
Click Yes.
The log is cleared and a new entry is recorded which includes the date and time of the event, the responsible user, and the cartridge number.
32 Using the web interface to view Moonshot System details
Viewing Moonshot switch information
From the main menu, select Switches to display details about the Moonshot Switch Modules installed in the Moonshot System. The page defaults to switch overview information.
NOTE:
If you have restricted slot access, the interface shows only the Moonshot components to which you have access. You may also see the message “Logged-in user does not have the privilege” depending on the page you are viewing.
Viewing switch overview information
To view switch overview information, select Switches from the main menu.
For each switch, the following information is displayed:
•
Name—The name of the installed switch, Switch A or Switch B.
•
AutoRev—The hardware revision of the cartridge. Used by Hewlett Packard Enterprise
Support.
•
Model—The model name of the switch.
•
Product ID—The product ID of the switch. This value is set by the manufacturer, but can be changed by an Administrator using the iLO CM firmware command line if the switch is replaced.
•
Serial number—The serial number of the switch. This value is assigned when the switch is manufactured, but can be reset by an Administrator using the command line if the server cartridge is replaced.
•
Manufacturing date—The date and time the switch was built.
•
Remote management IP—The IP address to be used by supported remote management tools.
The association between the Moonshot System and a remote management tool is configured by using the remote management tool. For instructions, see your remote management tool documentation.
•
IPv6—The link local IPv6 address of the switch, for communications between installed node operating systems (if enabled) and the switches.
•
MAC Address—The media access control (MAC) address of the switch.
Viewing overview information 33
•
Power—The switch power status.
◦
The switch is off.
◦
The switch is on.
•
Health status—A short description of the switch’s health.
•
UID—Shows the state of the UID for the switch.
◦
The UID is off.
◦
The UID is on.
•
Instant wattage—A reading of the current power usage of the switch.
•
Maximum wattage—The maximum amount of power in watts that the switch will consume.
•
UUID—The universally unique identifier for the switch. This value is assigned when the switch is manufactured.
•
Firmware version—Installed firmware version.
•
Satellite firmware—The version of the switch satellite firmware.
•
Switch data—The version of the switch data file.
For each uplink, the following information is displayed:
•
Model—The model name of the uplink module.
•
Product ID—The product ID of the uplink module. This value is set by the manufacturer.
•
Serial number—The serial number of the switch. This value is assigned by the manufacturer.
Changing the power state of a switch
1.
Select the check box next to either Switch A or Switch B. You cannot select both switches at once.
2.
The available actions depend on the current state of the selected switch.
NOTE:
No selections are available in the Actions menu until a switch is selected.
Do one of the following:
•
Select Actions→Power off to power off the selected switch.
•
Select Actions→Power on to power on the selected switch.
Changing the state of a switch’s UID
1.
Select the check box next to either Switch A or Switch B. You cannot select both switches at once.
2.
The available actions depend on the current state of the selected switch.
NOTE:
No selections are available in the Actions menu until a switch is selected.
Do one of the following:
•
Select Actions→UID on to turn on the UID of the selected switch.
•
Select Actions→UID off to turn off the UID of the selected switch.
The UID icon changes and an activity message is briefly shown.
34 Using the web interface to view Moonshot System details
Viewing switch logs
Switch logs provide a record of historical events that have occurred. The log entries shown on this page are all IML entries related to the switches. Log entries can help you diagnose issues or identify potential issues. Preventative action might help to avoid disruption of service.
From the main menu, select Switches to view switch log information. The page defaults to an overview of the switches. Select Logs from the View menu to show the switch logs.
The Log information available for each switch includes the following:
•
ID—The event ID number. Events are numbered in the order in which they are generated.
By default, the log is sorted by the ID, with the most recent event at the top.
•
Severity—The importance of the detected event.
Possible values include:
◦
Critical—The event indicates a service loss or an imminent service loss. Immediate attention is needed.
◦
Caution—The event is significant but does not indicate performance degradation.
◦
◦
Informational—The event provides background information.
Repaired—An event has undergone corrective action.
◦
Unknown—The event severity could not be determined.
•
Type—A further descriptor of the nature of the event.
•
Created on—For events with a count of 1, this is the date the event first occurred. For events with a count greater than 1, this is column shows the date the event was last updated.
•
Count—The number of times this event has occurred (if supported).
In general, important events generate an event log entry each time they occur. They are not consolidated into one event log entry.
When less important events are repeated, they are consolidated into one event log entry, the Count value is updated. Each event type has a specific time interval that determines whether repeated events are consolidated or a new event is logged.
•
Description—The description identifies the component and detailed characteristics of the recorded event.
Customizing the switch log view
You can customize which log entries are displayed as follows:
•
To filter by severity, select a severity level from the Severity menu. The selection is cumulative; and you can select more than one severity level. A selected severity level is bold. Click a bold entry again to deselect it.
Viewing overview information 35
•
Select a preset range or a date range in the Created on menu.
•
To search for events based on dates, event IDs, or description text, enter text in the Search box, and then press Enter.
•
Click Reset filters to set the filters back to the default values.
Saving a switch log
To save the switch log as a CSV file:
1.
Select the check box next to either Switch A or Switch B. You cannot select both switches at once.
2.
Select Actions→View CSV.
The Switch Event Log is displayed.
36 Using the web interface to view Moonshot System details
3.
Click Save or click Close to close the window.
Clearing a switch log
Users with the Administrator privilege can clear switch logs of all previously logged information.
To clear a switch log:
1.
Select the check box next to either Switch A or Switch B. You cannot select both switches at once.
2.
Select Actions→Clear Log.
The following message appears:
All log entries for this device will be deleted. This action cannot be undone. Continue with clearing the log?
3.
Click Yes.
The log is cleared and a new entry is recorded which includes the date and time of the event, the responsible user, and the cartridge number.
Viewing switch temperature sensor data
From the main menu, select Switches to display the switch information. The page defaults to an overview of the switches. Select Thermal from the View menu to show the temperature information. Temperatures are displayed in degrees Celsius.
Viewing overview information 37
The Thermal table displays the following information for each switch:
•
Sensor—The ID of the temperature sensor, which also gives an indication of the sensor’s location.
•
Status—A health icon showing the current sensor status. Depending on the switch configuration, some sensors show a status of Not installed.
•
Current Reading—The current temperature reported by the sensor.
•
Thresholds—The temperature thresholds for the warning for overheating conditions. The two threshold values are Caution and Critical.
◦
Caution—The switch is designed to maintain a temperature below the caution threshold while operating.
◦
Critical—If temperatures are uncontrollable or rise quickly, the critical temperature threshold prevents switch failure by physically shutting down the switch before the high temperature causes an electronic component failure.
•
Temperature Meter—A graphical representation of the current temperature reading and whether that reading has reached the Caution or Critical thresholds. The left edge of the column represents a temperature of 0°C, the grey bar represents the Caution threshold, and the right edge of the column represents the Critical threshold. If a temperature sensor is not installed, is missing, or is not reporting a temperature reading, an empty graph is displayed.
Viewing thermal history
Scroll down to see the Thermal History graph and choose a sample period and select the sensors to be displayed.
38 Using the web interface to view Moonshot System details
The graph displays the specified temperature along y axis, with the specified sample period along the x axis.
•
When temperatures are displayed in Celsius, click the F button to change the display to
Fahrenheit. When temperatures are displayed in Fahrenheit, click the C button to change the display to Celsius.
•
The circles on the graph correspond to the sensors listed in the Sensor Name column to the right of the table.
•
Move the mouse over a circle on the graph to view the sensor ID and temperature reading.
Each sensor has a unique associated color.
•
The color on the graph is a gradient that ranges from blue to red to white. Blue represents a temperature of 0°C to approximately 24°C and the gradient changes from blue to red as temperatures get hotter.
To change the sample view, select a new sample period from the column to the right of the graph.
A true full history of temperature data is not saved due to memory restraints. Instead, the temperature data is averaged in the following sample sizes:
•
Last Minute (2 seconds)—Displays the averages for the last minute with samples every two seconds.
•
Last Hour (1 minute)—Displays the averages for the last hour with samples every minute.
•
Last Day (1 hour)—Displays the averages for the last day with samples every hour.
Viewing overview information 39
•
Last Month (1 day)—Displays the averages for the last month with samples every day.
•
Last Year (1 month)—Displays the averages for the last year with samples every month.
To change which sensors are displayed in the graph, select the sensors from the Sensor Name list to the right of the graph. Be default, all sensors are selected. Unavailable sensors are grayed out and are inactive.
NOTE:
Thermal history samples only record temperatures since the iLO CM was powered on.
Thermal history is reset whenever the iLO CM is powered off and then on.
Viewing switch power data
Select Power from the View menu to show a graph of power consumption that allows you to choose a sample period and select the series to be displayed.
The graph displays the specified power usage in Watts along the y axis, with the specified sample period along the x axis.
•
Click the Watts or BTU/h buttons to specify how to display the power usage.
•
The circles on the graph correspond to the series listed in the Series Name column to the right of the table.
•
Move the mouse over a circle on the graph to view the series name and power usage reading.
Each series has a unique associated color.
To change the sample view, select a new sample period from the column to the right of the graph.
A true full history of temperature data is not saved due to memory restraints. Instead, the temperature data is averaged in the following sample sizes:
•
Last 5 Minutes (15 seconds)—Displays the averages for the last five minutes with samples every 15 seconds.
•
Last Hour (5 minutes)—Displays the averages for the last hour with samples every five minutes.
•
Last Day (1 hour)—Displays the averages for the last day with samples every hour.
40 Using the web interface to view Moonshot System details
•
Last 2 Weeks (1 day)—Displays the averages for the last two weeks with samples every day.
•
Last Year (2 weeks)—Displays the averages for the last year with samples every two weeks.
To change which information to display in the graph, select a series from the Series Name list to the right of the graph. Be default, all available series are selected. Unavailable series are grayed out and are inactive.
Viewing and editing cartridge links
To view the current cartridge links, select Links from the main menu.
NOTE:
Slots that are gray and show a lock symbol ( ) have been specifically blocked by settings in your user account. If you have restricted access to only specific cartridges and switches, all other pages of the interface show only the Moonshot components to which you have access.
You may also see the message “Logged-in user does not have the privilege” depending on the page you are viewing.
Linking allows cartridges to connect electrically and share capabilities and resources. Linking can also affect power on and off commands. In general, cartridges must be powered off to be linked. Hover the mouse over any currently active link ( ) to display details about the link.
For example, a Moonshot Remote Console Administrator (mRCA) can be linked with a ProLiant server cartridge to provide a cartridge node with Remote Console and virtual media functionality.
Once an mRCA is linked, controls become available on the Cartridges page that allow you to start the Integrated Remote Console application.
NOTE:
The server cartridge node to which you can link the mRCA is dependent on the slot position of the mRCA in the chassis. For more information, see the Moonshot System Configuration
And Compatibility Guide in the Moonshot Information Library at http://www.hpe.com/info/
moonshot.
Viewing overview information 41
List of Links
The List of Links table displays all of the currently configured links, and shows the location of the originating link, the location of the cartridge linked to, the architecture used in the link, and the speed of the link. Clicking a row in the table highlights the links in the Links View image.
About the Integrated Remote Console
An Integrated Remote Console is a graphical remote console that turns a supported browser into a virtual desktop, allowing full control over the display, keyboard, and mouse of the linked
ProLiant server cartridge. Using the Remote Console also provides access to the remote file system and network drives.
With Integrated Remote Console access, you can observe POST boot messages as the linked
ProLiant server cartridge node restarts. When you are installing operating systems remotely, the
Integrated Remote Console enables you to view and control the linked ProLiant server node throughout the installation process.
Editing cartridge links
Use the buttons at the bottom of the page as appropriate:
•
Click DeleteAll to remove all existing cartridge links. Click Yes to confirm the operation.
•
Click Clear to clear all selections without affecting existing cartridge links.
•
Click Apply to save your changes.
•
Click Close to leave the page.
Adding cartridge links
To add cartridge links, follow these steps:
1.
Select Links from the main menu.
2.
Click Actions→Edit.
The Edit Links page appears.
42 Using the web interface to view Moonshot System details
3.
Select a ProLiant server cartridge.
•
Single cartridge selections are highlighted with an orange border. Populated cartridge slots that are available to be linked to the selected cartridge (based on the position) turn white, unpopulated or unavailable slots that cannot be linked are gray.
•
Hover the mouse over unlinked cartridges (those with a icon) to display a table to the right of the image showing potential links. Hover over a linked cartridge ( ) to display details about the current link.
4.
Select one or more cartridges to be linked to the first.
5.
Click Apply.
NOTE:
Some cartridges, such as the HPE mRCA cartridge, cannot be linked with more than one cartridge at a time.
Removing cartridge links
To remove cartridge links, follow these steps:
1.
Select Links from the main menu.
2.
Click Actions→Edit.
The Edit Links page appears.
Viewing overview information 43
3.
(Optional) Click DeleteAll and then click Yes to remove all existing cartridge links.
4.
Select a single cartridge check box.
Hover the mouse over a linked cartridge ( ) to display details about the current link.
5.
Clear the selection box on other cartridges to be unlinked.
IMPORTANT:
Leave the first cartridge box checked.
6.
Click Apply and then click Yes to confirm.
Viewing firmware information
From the main menu, select Firmware to view firmware information. The Firmware Information page displays firmware information for various components.
NOTE:
If you have restricted slot access, the interface shows only the Moonshot components to which you have access. You may also see the message “Logged-in user does not have the privilege” depending on the page you are viewing.
The following information is displayed:
Chassis
•
Firmware Type—The name of the chassis firmware component.
•
Current Version—The version of the firmware currently installed on the component.
Switches
This section displays the following information about the installed switches:
•
Bay—The location of the switch (A or B).
•
Product name—The model name of the switch.
•
Switch—The switch firmware version.
•
Satellite—The satellite firmware version.
•
Data—The switch data file version.
Cartridges
This section displays the following information about the installed ProLiant server cartridges:
44 Using the web interface to view Moonshot System details
•
Bay—The slot location of the cartridge.
•
Product name—The model name of the cartridge.
•
System ROM—The ProLiant series server ROM version.
•
Satellite—The cartridge satellite firmware version.
•
Data—The server cartridge data firmware version.
•
CPLD—ProLiant server programmable logic device firmware version.
•
Other firmware—The names and versions of additional cartridge component firmware are listed here.
Power Supplies
This section displays information on any installed power supplies.
•
Bay—The slot location of the power supply.
•
Product name—The model name of the power supply.
•
Status—A representation of component’s health.
•
Current Version—Firmware version.
Viewing Moonshot power information
The iLO CM firmware monitors the power supplies in the server to ensure the longest available uptime of the server and operating system. Power supplies might be affected by brownouts and other electrical conditions, or AC cords might be unplugged accidentally. These conditions result in a loss of redundancy if redundant power supplies are configured, or result in a loss of operation if redundant power supplies are not in use. If a power supply failure is detected (hardware failure) or the AC power cord is disconnected, events are recorded in the IML and LED indicators are used.
From the main menu, select Power to view the power information page.
The Power Supplies section displays the following:
•
Bay—The bay number of the power supply.
•
Status—The status of the power supply.
•
Model—The model name of the power supply.
Viewing overview information 45
•
Capacity—The capacity of the power supply (watts).
•
Present Power Reading—The amount that the power supply is consuming, measured in watts.
•
Serial—The serial number of the power supply.
•
Spare—The part number of the spare power supply.
•
Firmware—The installed power supply firmware.
The Chassis Manager Power Metrics section displays
•
Power Consumed (Watts)—The power used by the Moonshot 1500 Chassis, measured in watts.
•
Power Capacity (Watts)—The maximum amount of power the Moonshot 1500 Chassis is capable of supporting.
The Power Meter section displays a graph that allows you to choose a sample period and select the series to be displayed.
The graph displays the specified power usage in Watts along the y axis, with the specified sample period along the x axis.
•
Click the Watts or BTU/h buttons to specify how to display the power usage.
•
The circles on the graph correspond to the series listed in the Series Name column to the right of the table.
•
Move the mouse over a circle on the graph to view the series name and power usage reading.
Each series has a unique associated color.
46 Using the web interface to view Moonshot System details
To change the sample view, select a new sample period from the column to the right of the graph.
A true full history of temperature data is not saved due to memory restraints. Instead, the temperature data is averaged in the following sample sizes:
•
Last 2 Minutes (4 seconds)—Displays the averages for the last two minutes with samples every 4 seconds.
•
Last Hour (2 minutes)—Displays the averages for the last hour with samples every two minutes.
•
Last Day (1 hour)—Displays the averages for the last day with samples every hour.
•
Last 2 Weeks (1 day)—Displays the averages for the last two weeks with samples every day.
•
Last Year (2 weeks)—Displays the averages for the last year with samples every two weeks.
To change which information to display in the graph, select a series from the Series Name list to the right of the graph. Be default, all available series are selected. Unavailable series are grayed out and are inactive.
Viewing fan information
From the main menu, select Fans to view fan information. The Fans page displays details about the fans installed in the Moonshot System.
The iLO CM firmware, in conjunction with the hardware, controls the operation and speed of the fans. Fans provide essential cooling of components to ensure reliability and continued operation.
The fans react to the temperatures monitored throughout the system to provide sufficient cooling with minimal noise.
Monitoring the fan subsystem includes the sufficient, redundant, and nonredundant fan configurations. If one or more fans fail, the Moonshot System still provides sufficient cooling to continue operation.
In nonredundant configurations, or redundant configurations where multiple fan failures occur, the system might be incapable of providing sufficient cooling to protect the server from damage and to ensure data integrity. In this case, in addition to the cooling policies, the firmware might start a graceful shutdown of the Moonshot System.
The page displays the following information:
•
Bay—Chassis location.
•
Type—The model.
•
Status—Health status, indicated by an icon.
◦
OK—No health issues
◦
Degraded—Significant service issue with possible service degradation
◦
Critical—Service lost or imminent service loss, immediate attention needed
Viewing overview information 47
◦
Disabled or Not installed—Service is unavailable or the component is not present.
◦
Unknown—A detected health problem cannot be classified
•
Speed—The percentage of maximum speed at which the fan is currently running.
Viewing temperature information
The Temperatures page displays the status, current reading, threshold settings, and temperature meter values for temperature sensors in the chassis.
For information about viewing cartridge and switch temperature readings, see
“Viewing ProLiant server cartridge information” (page 15)
and
“Viewing Moonshot switch information” (page 33)
.
Viewing temperature sensor data
Select Temperatures from the main menu.
Temperature sensor details
•
Sensor—The ID of the temperature sensor, which also gives an indication of the sensor location.
•
Status—The temperature status.
•
Current Reading—The temperature recorded by the temperature sensor. If a temperature sensor is not installed, the Current Reading column shows the value N/A.
•
Thresholds—The temperature thresholds for the warning for overheating conditions. The two threshold values are Caution and Critical. If a temperature sensor is not installed, the
Thresholds column shows the value N/A.
•
Temperature Meter—A graphical representation of the current temperature reading and whether that reading has reached the Caution or Critical thresholds. The left edge of the
48 Using the web interface to view Moonshot System details
column represents a temperature of 0°C, the grey bar represents the Caution threshold, and the right edge of the column represents the Critical threshold. If a temperature sensor is not installed, is missing, or is not reporting a temperature reading, an empty graph is displayed.
Temperature monitoring
The following temperature thresholds are monitored:
•
Caution—The HPE Moonshot System is designed to maintain a temperature below the caution threshold.
If the temperature exceeds the caution threshold, the fan speeds are increased to maximum.
If the temperature exceeds the caution threshold for 60 seconds, a graceful shutdown of the
Moonshot System cartridges and switches is attempted.
•
Critical—If temperatures are uncontrollable or rise quickly, the critical temperature threshold prevents system failure by physically shutting down the Moonshot System cartridges and switches before the high temperature causes an electronic component failure.
Monitoring policies differ depending on the chassis requirements. Policies usually include increasing fan speeds to maximum cooling, logging temperature events in the IML, providing a visual indication of events by using LED indicators, and starting a graceful shutdown of the operating system to avoid data corruption.
Additional policies are implemented after an excessive temperature condition is corrected, including returning the fan speed to normal, recording the event in the IML, turning off the LED indicators, and canceling shutdowns in progress (if applicable).
Viewing thermal history
Scroll down to see the Thermal History graph and choose a sample period and select the sensors to be displayed.
Viewing overview information 49
The graph displays the specified temperature along y axis, with the specified sample period along the x axis.
•
When temperatures are displayed in Celsius, click the F button to change the display to
Fahrenheit. When temperatures are displayed in Fahrenheit, click the C button to change the display to Celsius.
•
The circles on the graph correspond to the sensors listed in the Sensor Name column to the right of the table.
•
Move the mouse over a circle on the graph to view the sensor ID and temperature reading.
Each sensor has a unique associated color.
•
The color on the graph is a gradient that ranges from blue to red to white. Blue represents a temperature of 0°C to approximately 24°C and the gradient changes from blue to red as temperatures get hotter.
To change the sample view, select a new sample period from the column to the right of the graph.
A true full history of temperature data is not saved due to memory restraints. Instead, the temperature data is averaged in the following sample sizes:
•
Last Minute (2 seconds)—Displays the averages for the last minute with samples every two seconds.
•
Last Hour (1 minute)—Displays the averages for the last hour with samples every minute.
•
Last Day (1 hour)—Displays the averages for the last day with samples every hour.
50 Using the web interface to view Moonshot System details
•
Last Month (1 day)—Displays the averages for the last month with samples every day.
•
Last Year (1 month)—Displays the averages for the last year with samples every month.
To change which sensors are displayed in the graph, select the sensors from the Sensor Name list to the right of the graph. Be default, all sensors are selected. Unavailable sensors are grayed out and are inactive.
NOTE:
Thermal history samples only record temperatures since the iLO CM was powered on.
Thermal history is reset whenever the iLO CM is powered off and then on.
Viewing and managing active iLO CM firmware sessions
Select Active Sessions in the main menu to view the active iLO CM firmware sessions.
All active sessions are listed in the All Sessions section, and the current session is also listed in the Current Session section.
The following information is listed for each session:
•
User—The login name used to log in to the session.
•
IP—The IP address of the computer used to log in to the session.
•
Login Time—The date and time that the session started.
•
Access Time—The date and time that the Moonshot 1500 CM module was last accessed by the listed session.
•
Expires—The date and time that the session will expire.
•
Source—The method used to initiate the session (for example, web interface or SSH).
•
Permissions (Current Session only)—The enabled privileges for the current session user account. For information about user privileges, see
“iLO CM firmware user accounts” (page
Viewing overview information 51
Disconnecting iLO CM firmware sessions
The iLO CM Firmware deletes idle sessions if the session timeout setting is configured. The default value is 30 minutes.
For information about setting the session timeout value, see the HPE Moonshot iLO Chassis
Management CLI User Guide.
To disconnect an iLO CM firmware session:
1.
From the main menu, select Active Sessions.
The Active Sessions page opens.
2.
In the All Sessions section, select the check box next to the session you want to disconnect.
The current session is displayed in bold text.
3.
Click Disconnect Session.
If you selected the current session, the following message appears:
You have selected your current Web UI session. Disconnecting this session will force a logout of this browser window. Are you sure you want to disconnect your current session?
4.
Click Yes to continue, or click Cancel.
If you disconnected the current session, the browser returns to the login page.
If you disconnected a remote session, the following message appears:
Active Session(s) successfully disconnected.
Viewing the time settings
SNTP allows the iLO CM firmware to synchronize its clock with an external time source.
To view the time settings, select Settings in the main menu, and then scroll down to the Time
Settings section.
52 Using the web interface to view Moonshot System details
The following information is displayed:
•
Primary NTP server—The configured primary NTP server.
•
Secondary NTP server—The configured secondary NTP server.
•
Configure using DHCPv4—Whether the iLO CM Firmware is configured to use a
DHCPv4-provided NTP server.
•
NTP polling period—The time period (in seconds) that determines how often the time is synchronized with the NTP servers.
•
Current time zone—The configured time zone.
•
Current date—The current date in month, day, year format.
•
Current time—The current time in 12 hour format.
For information about configuring these settings, see
“Editing the time settings” (page 79) .
Viewing overview information 53
4 Configuring Moonshot System
This chapter includes procedures for configuring a Moonshot System by using the iLO CM firmware web interface.
Updating firmware
Firmware updates enhance functionality with new features, improvements, and security updates.
Updating Moonshot firmware
From the main menu, select Firmware Update to view the firmware update page. Updating
Moonshot System firmware keeps it up to date with the latest features and enhancements.
The Firmware Update page includes the following sections:
•
Chassis Manager Firmware—This section displays information about the current firmware installed on the Moonshot 1500 CM module.
•
Chassis Manager Repository—This section displays information about the files currently stored in non-volatile flash memory that can be used to update components of the Moonshot
System. This section also includes controls for installing and removing files from the iLO
Chassis Manager Repository.
•
Upload Firmware—This section includes controls for uploading firmware to individual components or to the iLO Chassis Manager Repository.
Preparing for a firmware update
Firmware updates for the Moonshot System are delivered in an Moonshot Component Pack.
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
54 Configuring Moonshot System
to update a Moonshot System. Deploy the firmware updates contained in the Moonshot
Component Pack using the following tools:
• iLO Chassis Manager CLI
•
Moonshot Web Interface
•
Moonshot Switch Module CLI
•
HP Smart Update Manager
Download the latest pack from the Hewlett Packard Enterprise website (http://www.hpe.com/
info/moonshot/download).
Extracting files from the Moonshot Component Pack
The Moonshot Component Pack is delivered in zip format and the files can be extracted using standard tools. Aside from the firmware update files, the Moonshot Component Pack also includes
HP SUM and related support files. HP SUM files are not needed when you update firmware using the iLO CM firmware web interface.
Unzip the Moonshot Component Pack on a local drive. The subdirectory \content is created, and includes the file cp<XXXXXX>.zip. Unzip cp<XXXXXX>.zip to see the moonshot system firmware update files.
NOTE:
Some releases of the Moonshot Component Pack include firmware update files outside of the cp<XXXXXX>.zip. See the moonshot component pack release notes for more information.
Uploading firmware
You can upload local or remote firmware files to the iLO CM Repository, or apply them directly to specified components.
Using local files
To upload a local file:
1.
From the main menu, select Firmware Update.
2.
Select Browse local files to load a file from local storage.
3.
Do one of the following:
•
Drag and drop a file from Windows Explorer onto the deployment box.
•
Click Choose file to browse to the firmware file.
The filename appears in the gray box.
4.
Click Start upload to upload the firmware file to Chassis Manager Repository.
IMPORTANT:
Firmware updates are supported on the Moonshot-45G and Moonshot-180G
Switch Modules. You must enable TFTP from the iLO CM Firmware command line before using the Moonshot Web Interface to update switch module firmware. Remember to disable
TFTP after switch firmware updates are complete as good security policy.
Using remote files
To upload a local file:
1.
From the main menu, select Firmware Update.
2.
Select HTTP URL to load a file from an HTTP server. When this is selected, the drag and drop box is replaced with the Firmware Image URL field.
3.
Enter an URL in the Firmware Image URL.
4.
Click Upload to copy the file from the specified URL to the iLO CM Repository.
Updating firmware 55
5.
Specify the applicable component to update in the Targets (optional) field:
•
Chassis—Chassis firmware updates do not require targets.
•
Cartridges—Enter the applicable cartridges targets using c<x> notation. For example, to apply an upload to cartridge 6, enter c6. You can also specify a range of cartridges, such as c6–10, or multiple specific cartridges, such as c6,8,10. Enter all to upload a firmware file to all cartridges.
•
Switches—Specify the switch, either sA, or sB as targets for switch firmware files.
IMPORTANT:
Firmware updates are supported on the Moonshot-45G and
Moonshot-180G Switch Modules. You must enable TFTP from the iLO CM Firmware command line before using the Moonshot Web Interface to update switch module firmware. Remember to disable TFTP after switch firmware updates are complete as good security policy.
6.
Click Install. A meter displays to show the upload progress.
Installing files from the iLO Chassis Manager Repository
Files that have already been uploaded to the iLO CM Repository can be used to update component firmware.
To install firmware from the iLO CM Repository:
1.
Select the firmware file in the Uploaded Files list.
2.
Specify the applicable component to flash in the Targets (optional) field:
•
Chassis—Chassis firmware updates do not require targets.
•
Cartridges—Enter the applicable cartridges targets using c<x> notation. For example, to apply an upload to cartridge 6, enter c6. You can also specify a range of cartridges, such as c6–10, or multiple specific cartridges, such as c6,8,10. Enter all to upload a firmware file to all cartridges.
•
Switches—Specify the switch, either sA, or sB as targets for switch firmware files.
IMPORTANT:
Firmware updates are supported on the Moonshot-45G and
Moonshot-180G Switch Modules. You must enable TFTP from the iLO CM Firmware command line before using the Moonshot Web Interface to update switch module firmware. Remember to disable TFTP after switch firmware updates are complete as good security policy.
NOTE:
Select Force if a message displays requiring the use of the force command.
3.
Click Install.
A meter displays to show the installation progress.
4.
(Optional) When finished installing a file from the iLO CM Repository, select the file in the
Uploaded Files list and then click Remove to delete the file from the iLO CM Repository.
Managing network settings
Viewing general network information
To view a summary of the configured network settings, select Network Configuration from the main menu.
56 Configuring Moonshot System
The General section lists the following:
•
MAC address—The MAC address of the iLO CM management port on the Moonshot 1500
CM module.
•
Host name—The Moonshot 1500 CM module host name. This name serves as the host-specific label portion of the DNS name.
•
Domain name—The Moonshot 1500 CM module domain name.
•
FQDN—The fully-qualified Moonshot 1500 CM module DNS name.
Viewing IPv4 information
To view IPv4 configuration information:
Managing network settings 57
1.
From the main menu, select Network Configuration.
The IPv4 summary section displays the DHCPv4 status, IPv4 address, Subnet mask, and
Default gateway settings.
58 Configuring Moonshot System
2.
Select IPv4 in the View menu in the upper left corner of the page, or click the More link in the IPv4 summary section.
The following information is displayed:
•
IPv4 address
◦
IPv4 address—The IPv4 address currently in use. If the value is 0.0.0.0, the
IPv4 address is not configured.
◦
Subnet mask—The subnet mask of the IPv4 address currently in use. If the value is 0.0.0.0, no address is configured.
◦
Default gateway—The default gateway address in use for the IPv4 protocol. If the value is 0.0.0.0, the gateway is not configured.
◦
DHCPv4—Indicates whether DHCP is enabled for IPv4.
◦
Ping gateway on startup—Causes the iLO CM Firmware to send four ICMP echo request packets to the gateway when the Moonshot 1500 CM module initializes.
This ensures that the ARP cache entry is up-to-date on the router responsible for routing packets to and from the Moonshot 1500 CM module.
•
DHCPv4 options—This section lists the following DHCPv4 options and whether they are enabled or disabled:
◦
Use gateway
◦
Use domain name
◦
Use DNS servers
◦
Use WINS servers
◦
Use NTP servers
◦
Use static routes
•
Static routes
◦
Static route #1—The static route 1 destination, mask, and gateway addresses.
◦
Static route #2—The static route 2 destination, mask, and gateway addresses.
◦
Static route #3—The static route 3 destination, mask, and gateway addresses.
•
DNS
◦
Primary DNS server—The primary DNS server address.
◦
Secondary DNS server—The secondary DNS server address.
◦
Tertiary DNS server—The tertiary DNS server address.
◦
DDNS registration—Specifies whether the Moonshot 1500 CM module registers its IPv4 address and name with a DNS server.
•
Daisy chain status—Specifies whether the Moonshot 1500 CM module is connected to one or more other CM modules.
•
WINS
◦
Primary WINS server—The Primary WINS server address.
Managing network settings 59
◦
Secondary WINS server—The Secondary WINS server address.
◦
WINS registration—Specifies whether the Moonshot 1500 CM module registers its name with a WINS server.
Configuring IPv4 settings
1.
Select Network Configuration from the main menu.
2.
Select Actions→Edit.
3.
Configure the following settings in the IPv4 section:
•
DHCPv4—Enables the Moonshot 1500 CM module to obtain its IP address (and many other settings) from a DHCP server.
•
IPv4 address—The Moonshot 1500 CM module IP address. If DHCP is used, this value is supplied automatically. If DHCP is not used, enter a static IP address.
•
Subnet mask—The subnet mask of the Moonshot 1500 CM module IP network. If
DHCP is used, this value is supplied automatically. If DHCP is not used, enter a subnet mask for the network.
•
Gateway—The Moonshot 1500 CM module gateway IP address. If DHCP is used, this value is supplied automatically. If DHCP is not used, enter a gateway IP address.
4.
Click Advanced, to edit the advanced IPv4 settings.
5.
Configure the following settings in the Advanced section:
•
Ping gateway on startup—Causes the iLO CM Firmware to send four ICMP echo request packets to the gateway when the Moonshot 1500 CM module initializes. This
60 Configuring Moonshot System
ensures that the ARP cache entry is up-to-date on the router responsible for routing packets to and from the Moonshot 1500 CM module.
•
Daisy chain—Select the check box if this CM module is connected to one or more other
CM modules in a daisy chain.
•
Use DHCPv4 for—Select from the following check boxes to configure the values that will be provided by the DHCP server.
◦
Gateway—Specifies whether the DHCP server-supplied gateway is used. If DHCP is not used, enter a gateway address in the Gateway box in the IPv4 section.
◦
Domain name—Specifies whether the DHCP server-supplied domain name is used. If DHCP is not used, enter a domain name in the Domain Name box in the
Host name section.
◦
DNS—Specifies whether the DHCP server-supplied DNS server list is used. If not, enter the DNS server addresses in the Primary DNS server, Secondary DNS
server, and Tertiary DNS server boxes in the DNS section.
◦
NTP—Specifies whether the DHCP server-supplied NTP service locations are used. If not, enter the NTP servers on the Time Settings page.
◦
WINS—Specifies whether the DHCP server-supplied WINS server list is used. If not, enter the WINS server addresses in the Primary WINS server and Secondary
WINS server boxes in the WINS section.
◦
Static routes—Specifies whether the DHCP server-supplied static routes is used.
If not, enter the static route destination, mask, and gateway addresses in the Static
routes section.
6.
If DHCPv4 is not used for the DNS settings, click DNS, and then configure the following settings in the DNS section:
•
Primary DNS server—If Use DNS servers is enabled, this value is supplied automatically. If not, enter the primary DNS server address.
•
Secondary DNS server—If Use DNS servers is enabled, this value is supplied automatically. If not, enter the secondary DNS server address.
•
Tertiary DNS server—If Use DNS servers is enabled, this value is supplied automatically. If not, enter the tertiary DNS server address.
•
DDNS registration—Select or clear this check box to specify whether the Moonshot
1500 CM module registers its IPv4 address and name with a DNS server.
7.
If DHCPv4 is not used for the WINS settings, click WINS, and then configure the following settings in the WINS section:
•
Primary WINS server—If Use WINS servers is enabled, this value is supplied automatically. If not, enter the Primary WINS Server address.
•
Secondary WINS server—If Use WINS servers is enabled, this value is supplied automatically. If not, enter the Secondary WINS Server address.
•
WINS registration—Select or clear this check box to specify whether the Moonshot
1500 CM module registers its name with a WINS server.
Managing network settings 61
8.
If DHCPv4 is not used for the static route settings, click Static routes, and then configure the following settings in the Static routes section:
•
Static route #1—The static route 1 destination, mask, and gateway addresses. If Use
static routes is enabled, this value is supplied automatically. If not, enter the static route value.
•
Static route #2—The static route 2 destination, mask, and gateway addresses. If Use
static routes is enabled, this value is supplied automatically. If not, enter the static route value.
•
Static route #3—The static route 3 destination, mask, and gateway addresses. If Use
static routes is enabled, this value is supplied automatically. If not, enter the static route value.
9.
Click Apply to save the changes.
A message similar to the following appears:
The chassis manager will automatically reset to apply the settings.
Continue to apply the settings and reset the chassis manager?
10. Click Yes.
A reset ends all active sessions. It might take several minutes before you can re-establish a connection.
Configuring the host name
When you configure the Moonshot 1500 CM module host name, note the following limitations:
•
Name service limitations—The host name is used as part of the DNS name.
◦
DNS allows alphanumeric characters and hyphens.
◦
Name service limitations also apply to the Domain name.
•
Namespace issues—To avoid these issues:
◦
Do not use the underscore character.
◦
Limit host names to 15 characters.
◦
Verify that you can ping Moonshot 1500 CM module by IP address and by DNS/WINS name.
◦
Verify that NSLOOKUP resolves the Moonshot 1500 CM module network address correctly and that no namespace conflicts exist.
◦
If you are using both DNS and WINS, verify that they resolve the Moonshot 1500 CM module network address correctly.
◦
Flush the DNS name if you make any namespace changes.
To configure the host name:
62 Configuring Moonshot System
1.
From the main menu, select Network Configuration.
2.
Select Actions→Edit.
3.
Enter the following information in the Host name section:
•
Host name—The Moonshot 1500 CM module host name. This name serves as the host-specific label portion of the DNS name. This name can be used only if DHCP and
DNS are configured to connect to the host name instead of the IP address.
•
Domain name—The Moonshot 1500 CM module domain name.
This name is entered automatically if Use DHCPv4 supplied domain name is selected.
If DHCP is not used, enter a domain name.
4.
Click Apply to save the changes.
The Apply network settings dialog box notifies you that a reset is required to apply the changes.
5.
Click Yes.
A reset ends all active sessions. It might take several minutes before you can re-establish a connection.
Configuring security
Viewing SSL certificate information
To view certificate information, select Security from the main menu.
The following certificate details are displayed:
•
Issued to—The entity to which the certificate was issued
•
Issued by—The CA that issued the certificate
•
Valid from—The first date that the certificate is valid
•
Valid until—The date that the certificate expires
•
Serial number—The serial number that the CA assigned to the certificate
Obtaining a trusted SSL certificate iLO CM allows you to create a Certificate Signing Request that you can send to a Certificate
Authority to obtain a trusted SSL certificate to import into iLO CM.
An SSL certificate works only with the keys generated with its corresponding CSR. If the Moonshot
1500 CM module is reset to the factory default settings, or another CSR is generated before the
Configuring security 63
certificate that corresponds to the previous CSR is imported, the certificate does not work. In that case, a new CSR must be generated and used to obtain a new certificate from a CA.
Prerequisites
Administrator privilege
Obtaining an SSL certificate
1.
Select Security from the main menu.
2.
Select Actions→Customize Certificate.
The Generate Certificate Signing Request page opens.
64 Configuring Moonshot System
3.
Enter the following information in the Information section:
•
Country (C)—The two-character country code that identifies the country where the company or organization that owns this HPE Moonshot System is located. Enter the two-letter abbreviation in capital letters.
•
State (ST)—The state where the company or organization that owns this Moonshot
System is located.
•
City or Locality (L)—The city or locality where the company or organization that owns this Moonshot System is located.
•
Organization Name (O)—The name of the company or organization that owns this
Moonshot System.
•
Common Name (CN)—The FQDN of this Moonshot System.
The FQDN is entered automatically in the Common Name (CN) box.
•
Organizational Unit (OU)—(Optional) The unit within the company or organization that owns this Moonshot System.
•
Email Address—(Optional) The email address to be embedded in the certificate.
4.
Click Generate CSR.
A message notifies you that a certificate is being generated and that the process might take up to 10 minutes.
Configuring security 65
5.
After a few minutes (up to 10), click Generate CSR again, or select Actions→View CSR on the SSL Certificate page.
The CSR is displayed.
The CSR contains a public and private key pair that validates communications between the client browser and iLO CM firmware. Key sizes up to 2,048 bits are supported. The generated
CSR is held in memory until a new CSR is generated, the iLO CM firmware is reset to the factory default settings, or a certificate is imported.
6.
Do one of the following:
•
Click Save to save the CSR text to a file.
•
Select and copy the CSR text.
7.
Open a browser window and navigate to a third-party CA.
8.
Follow the onscreen instructions and submit the CSR to the CA.
When you submit the CSR to the CA, your environment might require the specification of
Subject Alternative Names (SAN). This information is typically included in the Additional
Attributes box. If necessary, enter the Moonshot 1500 CM module DNS short name and
IP address in the Additional Attributes box by using the following syntax: san:dns=<IP address>&dns=<server name>
.
The CA generates a certificate in PKCS #10 format.
9.
After you obtain the certificate, make sure that:
•
The CN matches the Moonshot 1500 CM module FQDN.
This value is listed on the Network Configuration page.
•
The certificate is a Base64-encoded X.509 certificate.
•
The first and last lines are included in the certificate.
10. Return to the SSL Certificate page in the iLO CM Firmware web interface.
11. Import the certificate.
For instructions, see
“Importing a trusted SSL certificate” (page 66)
.
Importing a trusted SSL certificate
Use the following procedure to import a trusted SSL certificate.
1.
Obtain a certificate from a CA.
For instructions, see
“Obtaining a trusted SSL certificate” (page 63)
.
2.
Verify that the certificate meets the following requirements:
•
The certificate is in PKCS #10 format.
•
The CN matches the Moonshot 1500 CM module FQDN.
This is listed on the Network Configuration page.
•
The certificate is a Base64-encoded X.509 certificate.
•
The certificate meets the file size requirements.
The iLO CM firmware supports DER-encoded SSL certificates that are up to 3 KB in size (including the 609 or 1,187 bytes used by the private key, for 1,024-bit and 2,048-bit certificates, respectively).
•
The first and last lines are included in the certificate.
3.
Select Security from the main menu.
66 Configuring Moonshot System
4.
Select Actions→Import Certificate.
The Import SSL Certificate page appears.
5.
Select Browse local files or Copy into text box. This determines the method of inserting the certificate contents into the iLO CM firmware.
•
Browse local files—Select this option to load a certificate file stored on the local system.
•
Copy into text box—Select this option to paste the certificate text into a text box.
6.
Depending on the selected method, do one of the following:
•
Click Browse, and then select a certificate file.
•
Drag a certificate file into the Drag and drop a file or browse to select a file section on the Import Certificate page.
•
Paste the certificate contents into the Certificate text box.
7.
Click Import.
The iLO CM firmware prompts you to confirm that you want to import the certificate and initiate an iLO CM firmware reset.
8.
Click Yes to import the certificate and initiate a reset.
A reset ends all active sessions. It might take several minutes before you can re-establish a connection.
Viewing a certificate signing request
After you generate a CSR on the Generate Certificate Signing Request page, use the following procedure to view the CSR text:
1.
Select Security from the main menu.
2.
Select Actions→View CSR.
The CSR text is displayed.
Configuring security 67
3.
Click Save to save the CSR text to a file.
For information about using the CSR to obtain a trusted certificate, see
Managing other Moonshot settings
The Settings page displays other Moonshot System settings and enables further configuration.
Viewing Moonshot settings
The Settings page allows users to view and modify other chassis, AlertMail, Remote Syslog, and SNMP settings. From the main menu, select Settings to view settings information.
68 Configuring Moonshot System
The page displays the following sections:
•
Chassis Settings
This section displays common chassis information such as auto power, asset tag, name, model, and power mode. You must have the Administrator privilege to change Chassis settings.
•
AlertMail
AlertMail enables you to configure Moonshot to send alert conditions detected independently of the host operating system to a specified email address. iLO mail alerts include major host system events. You must have the Administrator privilege to change AlertMail settings.
•
Authentication and Directory Server
The iLO CM firmware supports Microsoft Active Directory and Kerberos for user authentication and authorization.
•
Remote syslog
The Remote Syslog feature allows Moonshot to send event notification messages to Syslog servers. The Moonshot firmware Remote Syslog includes the IML and iLO Event Log. You must have the Administrator privilege to change these settings.
Managing other Moonshot settings 69
•
SNMP Settings
SNMP enables you to configure up to three email addresses to be sent alerts when Moonshot conditions warrant administrative attention. You must have the Administrator privilege to change these settings.
•
Time Settings
Time settings allows you to view and configure network time server information and current date and time.
Except for Time Settings, you can click the title of each section to open a new window and adjust the settings. For Time Settings, hover over the section with your mouse and then click .
Configuring chassis settings
1.
Select Settings from the main menu.
2.
Click Chassis Settings >.
3.
Click Actions→Edit.
4.
Select an Auto power-on setting. This setting determines whether cartridges are automatically powered on when inserted or when the chassis is powered on.
5.
Enter the following information:
•
Asset tag—Your organization’s asset tag information for this Moonshot chassis. Enter a maximum of 32 characters.
•
Name—An easily recognized name for the chassis. This is not a hostname. Enter a maximum of 32 characters.
6.
Select a Power Mode. This setting configures the chassis power cap mode. Choose one of the following:
•
No Redundancy mode
•
Max Performance with redundancy mode
•
Full AC/DC redundancy mode
•
Power feed redundancy mode
7.
Click Apply to save the settings and return to the Chassis settings page.
8.
Optional: Click Actions→Set factory default to restore all Moonshot 1500 CM module parameters to factory defaults. The Moonshot 1500 CM module resets after all changes are made.
70 Configuring Moonshot System
WARNING!
All of the current configuration settings for the Moonshot 1500 CM module are lost when this command is run.
9.
Optional: Click Actions→Reboot iLO CM to restart the Moonshot iLO CM firmware. This does not erase any settings.
NOTE:
This action closes all open connections and restarts the iLO Chassis Manager.
Rebooting does not impact cartridge state, workloads, or the switches.
Configuring AlertMail settings
Enabling AlertMail
1.
Select Settings from the main menu.
2.
Click AlertMail >.
3.
Click Actions→Edit.
4.
Select the Enable iLO AlertMail check box.
5.
Enter the following information:
•
Email Address—The destination email address for email alerts. This string can be up to 63 characters and should be in standard email address format. You can enter only one email address.
•
Sender Domain—The domain name specified in the sender (From) email address. The sender email address is formed by using the iLO CM name as the host name, and the sender domain as the domain name. This string can be up to 63 characters.
•
SMTP Server—The IP address or DNS name of the SMTP server. This string can be up to 63 characters.
•
SMTP Port—The port that the SMTP server will use for unauthenticated SMTP connections. The default value is 25.
6.
Click OK to save the changes and return to the Settings page.
Managing other Moonshot settings 71
7.
Optional: Click Actions→Test AlertMail to send a test message to the configured email address.
This action is available only when AlertMail is enabled.
Disabling AlertMail
1.
Select Settings from the main menu.
2.
Click AlertMail >.
3.
Click Actions→Edit.
4.
Clear the Enable iLO AlertMail check box.
Directory authentication and authorization
The iLO CM firmware supports Microsoft Active Directory and Kerberos for user authentication and authorization. The iLO CM firmware connects to directory services by using SSL connections to the directory server LDAP port. The default secure LDAP port is 636.
Locally stored user accounts (listed on the User Administration page) can be active when iLO
CM directory support is enabled. This enables both local-based and directory-based user access.
Typically, you can delete local user accounts (with the exception of an emergency access account) after iLO CM is configured to access the directory service. You can also disable access to these accounts when directory support is enabled.
Configuring authentication and directory server settings
Configuring the authentication and directory server settings is one step in the process of configuring iLO CM to use a directory or Kerberos login.
Prerequisites
•
You have Administrator privilege to change the directory settings.
•
An iLO license that supports this feature is installed. For more information, see the following website: http://www.hpe.com/us/en/products/servers/ilo/licenses.
•
The environment is configured to support Kerberos authentication or directory integration.
•
The Kerberos keytab file is available (Kerberos authentication only).
Configuring authentication and directory server settings
1.
Navigate to the Main menu→Settings→Authentication and Directory Server.
2.
Click Actions→Edit
3.
LDAP Directory Authentication—Select the check box to enable LDAP directory authentication, or clear the check box to disable it.
4.
Configure Kerberos Authentication. This setting enables or disables Kerberos login. If
Kerberos login is enabled and configured correctly, the Zero Sign In button appears on the login page.
5.
If Kerberos Authentication is enabled, configure the following settings:
•
Kerberos Realm—The name of the Kerberos realm in which the iLO processor is operating. This string can be up to 128 characters. A realm name is usually the DNS name converted to uppercase. Realm names are case sensitive.
•
Kerberos KDC Server Address—The IP address or DNS name of the KDC server.
This string can be up to 128 characters. Each realm must have at least one KDC that contains an authentication server and a ticket grant server. These servers can be combined.
72 Configuring Moonshot System
•
Kerberos KDC Server Port—The TCP or UDP port number on which the KDC is listening. The default KDC port is 88.
•
Kerberos Keytab—A binary file that contains pairs of service principal names and encrypted passwords. In the Windows environment, the keytab file is generated by the ktpass utility. Click Browse (Internet Explorer or Firefox) or Choose File (Chrome), and then follow the onscreen instructions to select a file.
The components of the service principal name stored in the Kerberos keytab file are case sensitive. The primary (service type) must be in uppercase letters, for example,
(HTTP). The instance (iLO host name) must be in lowercase letters, for example, example.example.net
. The realm name must be in uppercase, for example,
EXAMPLE.NET
.
6.
Enter the directory server settings.
•
Directory Server Address—Specifies the network DNS name or IP address of the directory server. The directory server address can be up to 127 characters.
IMPORTANT:
If LDAP directory authentication is enabled and the Directory server
address is set in FQDN format instead of an IP address, verify you have the correct
Directory server address before entering it. The iLO CM firmware login page will stop responding for an extended period of time if the DNS server is unreachable during the login. This does not occur if no DNS servers are configured on the Network Configuration page; however, it is also then not possible to use FQDNs for LDAP authentication.
•
Directory Server LDAP Port—Specifies the port number for the secure LDAP service on the server. The default value is 636. You can specify a different value if your directory service is configured to use a different port.
NOTE:
If the Directory server port is not configured correctly, iLO CM firmware could become unresponsive.
•
Directory User Contexts—These boxes enable you to specify common directory subcontexts so that users do not need to enter their full DNs at login. Directory user contexts can be up to 128 characters. For more information, see
7.
Click Apply.
8.
Add a Kerberos Keytab—A binary file that contains pairs of service principal names and encrypted passwords. In the Windows environment, the keytab file is generated by the ktpass utility. Click Browse (Internet Explorer or Firefox) or Choose File (Chrome), and then follow the onscreen instructions to select a file.
The components of the service principal name stored in the Kerberos keytab file are case sensitive. The primary (service type) must be in uppercase letters, for example, (HTTP). The instance (iLO host name) must be in lowercase letters, for example, example.example.net.
The realm name must be in uppercase, for example, EXAMPLE.NET.
9.
To test the communication between the directory server and iLO CM, select Actions→Start
Test.
For more information, see
“Running directory tests” (page 74)
.
10. Optional: Select Main menu→User Administration to navigate to the User Administration page, where you can add or edit directory groups.
Directory user contexts
You can identify the objects listed in a directory by using unique DNs. However, DNs can be long, and users might not know their DNs or might have accounts in different directory contexts.
Managing other Moonshot settings 73
iLO attempts to contact the directory service by DN, and then applies the search contexts in order until successful.
•
Example 1—If you enter the search context ou=engineering,o=ab, you can log in as user instead of logging in as cn=user,ou=engineering,o=ab.
•
Example 2—If a system is managed by Information Management, Services, and Training, search contexts such as the following enable users in any of these organizations to log in by using their common names:
Directory User Context 1:ou=IM,o=ab
Directory User Context 2:ou=Services,o=ab
Directory User Context 3:ou=Training,o=ab
If a user exists in both the IM organizational unit and the Training organizational unit, login is first attempted as cn=user,ou=IM,o=ab.
•
Example 3 (Active Directory only)—Microsoft Active Directory allows an alternate user credential format. A user can log in as [email protected], in which case a search context of @domain.example.com allows the user to log in as user. Only a successful login attempt can test search contexts in this format.
Running directory tests
Directory tests enable you to validate the configured directory settings. The directory test results are reset when directory settings are saved, or when the directory tests are started.
1.
Select Actions→Start test on the Main menu→Authentication and Directory Server page.
2.
In the Directory Test Controls section, enter the DN and password of a directory administrator in the Directory Administrator Distinguished Name and Directory
Administrator Password boxes.
HPE recommends that you use the same credentials that you used when creating the iLO
CM objects in the directory. These credentials are not stored by iLOCM; they are used to verify the iLO CM object and user search contexts.
3.
In the Directory Test Controls section, enter a test user name and password in the Test
User Name and Test User Password boxes.
4.
Click Apply.
Several tests begin after the Directory Tests window closes.
While the tests are running, the page refreshes periodically. You can stop the tests or manually refresh the page at any time.
More information
Directory test results
The Directory Test Results section shows the directory test status.
•
Overall Status—Summarizes the results of the tests.
◦
Not Run—No tests were run.
◦
Inconclusive—No results were reported.
◦
Passed—No failures were reported.
◦
Problem Detected—A problem was reported.
74 Configuring Moonshot System
◦
Failed—A specific subtest failed. Check the onscreen log to identify the problem.
◦
Warning—One or more of the directory tests reported a Warning status.
•
Test—The name of each test.
For more information about the directory tests, see
“About the iLO directory tests” (page
•
Result—Reports status for a specific directory setting or an operation that uses one or more directory settings. These results are generated when a sequence of tests is run. The results stop when the tests run to completion, when a test failure prevents further progress, or when the tests are stopped. Test results follow:
◦
Passed—The test ran successfully. If more than one directory server was tested, all servers that ran this test were successful.
◦
Not Run—The test was not run.
◦
Failed—The test was unsuccessful on one or more directory servers. Directory support might not be available on those servers.
◦
Warning—The test ran and reported a warning condition, for example, a certificate error. Check the Notes column for suggested actions to correct the warning condition.
•
Notes—Indicates the results of various phases of the directory tests. The data is updated with failure details and information that is not readily available, like the directory server certificate subject and which roles were evaluated successfully.
About the iLO directory tests
Descriptions of the directory tests follow:
•
Directory Server DNS Name—If the directory server is defined in FQDN format
(directory.company.com), iLO CM resolves the name from FQDN format to IP format, and queries the configured DNS server.
If the test is successful, iLO CM obtained an IP address for the configured directory server.
If iLO CM cannot obtain an IP address for the directory server, this test and all subsequent tests fail.
If the directory server is configured with an IP address, iLO CM skips this test.
If a failure occurs:
1.
Verify that the DNS server configured in iLO CM is correct.
2.
Verify that the directory server FQDN is correct.
3.
As a troubleshooting tool, use an IP address instead of the FQDN.
4.
If the problem persists, check the DNS server records and network routing.
•
Ping Directory Server—iLO CM initiates a ping to the configured directory server.
The test is successful if iLO CM receives the ping response; it is unsuccessful if the directory server does not reply to iLOCM .
If the test fails, iLOCM will continue with the subsequent tests.
If a failure occurs:
1.
Check to see if a firewall is active on the directory server.
2.
Check for network routing issues.
•
Connect to Directory Server—iLO CM attempts to negotiate an LDAP connection with the directory server.
If the test is successful, iLO CM was able to initiate the connection.
Managing other Moonshot settings 75
If the test fails, iLO CM was not able to initiate an LDAP connection with the specified directory server. Subsequent tests will stop.
If a failure occurs:
1.
Verify that the configured directory server is the correct host.
2.
Verify that iLO CM has a clear communication path to the directory server through port
636 (consider any routers or firewalls between iLO CM and the directory server).
3.
Verify that any local firewall on the directory server is enabled to allow communications through port 636.
•
Connect using SSL—iLO CM initiates SSL handshake and negotiation and LDAP communications with the directory server through port 636.
If the test is successful, the SSL handshake and negotiation between iLO and the directory server were successful.
If a failure occurs, the directory server is not enabled for SSL negotiations.
If you are using Microsoft Active Directory, verify that Active Directory Certificate Services is installed.
•
Bind to Directory Server—This test binds the connection with the user name specified in the test boxes. If no user is specified, iLO CM does an anonymous bind.
If the test is successful, the directory server accepted the binding.
If a failure occurs:
1.
Verify that the directory server allows anonymous binding.
2.
If you entered a user name in the test boxes, verify that the credentials are correct.
3.
If you verified that the user name is correct, try using other user-name formats; for example, [email protected], DOMAIN\username, username (called Display Name in Active Directory), or userlogin.
4.
Verify that the specified user is allowed to log in and is enabled.
•
Directory Administrator Login—If Directory Administrator Distinguished Name and
Directory Administrator Password were specified, iLO CM uses these values to log in to the directory server as an administrator. These boxes are optional.
•
User Authentication—iLO CM authenticates to the directory server with the specified user name and password.
If the test is successful, the supplied user credentials are correct.
If the test fails, the user name and/or password is incorrect.
If a failure occurs:
1.
If you verified that the user name is correct, try using other user-name formats; for example, [email protected], DOMAIN\username, username (called Display Name in Active Directory), or userlogin.
2.
Verify that the specified user is allowed to log in and is enabled.
3.
Check to see if the specified user name is restricted by logon hours or IP-based logging.
•
User Authorization—This test verifies that the specified user name is part of the specified directory group, and is part of the directory search context specified during directory services configuration.
If a failure occurs:
76 Configuring Moonshot System
1.
Verify that the specified user name is part of the specified directory group.
2.
Check to see if the specified user name is restricted by logon hours or IP-based logging.
•
Directory User Contexts—If Directory Administrator Distinguished Name was specified, iLO CM tries to search the specified context.
If the test is successful, iLO CM found the context by using the administrator credentials to search for the container in the directory.
Contexts that begin with "@" can be tested only by user login.
A failure indicates that the container could not be located.
Configuring Remote Syslog settings
Enabling Remote Syslog
1.
Select Settings from the main menu.
2.
Click Remote syslog >.
3.
Click Actions→Edit.
4.
Select the Enable iLO Remote Syslog check box.
5.
Enter the following information:
•
Remote Syslog Server—The IP address, FQDN, IPv6 name, or short name of the server running the Syslog service. This string can be up to 127 characters.
On Linux systems, system events are logged by a tool called syslog. This tool should be installed on all Linux systems. You can set a syslog server on a remote system that will act as a central logging system for iLO systems. This way, if the iLO Remote Syslog feature is enabled in iLO, it can send its logs to the syslog server.
•
Remote Syslog Port—The port number through which the Syslog server is listening.
The default value is 514.
6.
Click Apply to save the changes and return to the Remote Syslog settings display page.
7.
Optional: Click Actions→Test Syslog to send a test message to the configured syslog server.
This action is available only when Remote Syslog is enabled.
Disabling Remote Syslog
1.
Select Settings from the main menu.
2.
Click Remote syslog >.
Managing other Moonshot settings 77
3.
Click Actions→Edit.
4.
Clear the Enable iLO Remote Syslog check box.
5.
Click Apply to return to the Remote Syslog settings display page.
Configuring SNMP
The iLO CM firmware can automatically send SNMP alerts to IP addresses that you specify.
Enabling SNMP alerts
1.
Select Settings from the main menu.
2.
Click SNMP >.
3.
Click Actions→Edit.
4.
Select the Alerts enabled check box.
5.
Enter up to three SNMP Alert Destination(s). These must be IP addresses or FQDNs of remote management systems that will receive SNMP alerts.
6.
Enter a new SNMP Trap Community String so traps can be filtered as they are received.
The default is COMPAQ.
7.
Click Apply to return to the SNMP settings display page.
8.
Optional: Click Actions→Send SNMP Test Trap to send a test message to the configured
SNMP alert destinations.
This action is available only when SNMP alerts are enabled.
Disabling SNMP alerts
1.
Select Settings from the main menu.
2.
Click SNMP >.
3.
Click Actions→Edit.
4.
Clear the Alerts enabled check box.
5.
Click Apply to return to the SNMP settings display page.
Viewing the time settings
SNTP allows the iLO CM firmware to synchronize its clock with an external time source.
To view the time settings, select Settings in the main menu, and then scroll down to the Time
Settings section.
78 Configuring Moonshot System
The following information is displayed:
•
Primary NTP server—The configured primary NTP server.
•
Secondary NTP server—The configured secondary NTP server.
•
Configure using DHCPv4—Whether the iLO CM Firmware is configured to use a
DHCPv4-provided NTP server.
•
NTP polling period—The time period (in seconds) that determines how often the time is synchronized with the NTP servers.
•
Current time zone—The configured time zone.
•
Current date—The current date in month, day, year format.
•
Current time—The current time in 12 hour format.
For information about configuring these settings, see
“Editing the time settings” (page 79) .
Editing the time settings
SNTP allows the iLO CM Firmware to synchronize its clock with an external time source.
To use SNTP, you must have at least one NTP server available on your management network.
Primary and secondary NTP server addresses can be configured manually or via DHCP servers.
If the primary time server address cannot be contacted, the secondary address is used. You must have the Administrator privilege to change these settings.
To configure the time settings:
1.
From the main menu, select Settings.
2.
Move the mouse over the Time Settings section and then click Edit.
Managing other Moonshot settings 79
3.
Do one of the following:
•
Select the Configure using DHCPv4 check box to use a DHCP-provided NTP server address.
NOTE:
To configure a DHCPv4-provided NTP server, you must first enable DHCPv4 on the Network Configuration page. For more information, see
“Managing network settings” (page 56)
.
•
Enter NTP server addresses in the Primary NTP server and Secondary NTP server boxes. You can enter the server addresses by using the IPv4 address.
4.
Enter the NTP polling period.
This value, measured in seconds, determines how often the time is synchronized with the
NTP servers. Enter a value of 60 seconds or greater.
5.
If you entered a primary and secondary time server, select the server time zone from the
Time zone list.
This setting determines how the iLO CM firmware adjusts UTC time to obtain the local time, and how it adjusts for Daylight Savings Time (Summer Time). In order for the entries in the event log and IML to display the correct local time, you must specify the time zone in which the Moonshot System is located.
If you want the iLO CM firmware to use the time the NTP server provides, without adjustment, use a time zone that does not apply an adjustment to UTC time. In addition, that time zone must not apply a Daylight Savings Time (Summer Time) adjustment. There are several time zones that fit this requirement. One example is the Atlantic/Reykjavik time zone, which is
80 Configuring Moonshot System
neither east or west of the Prime Meridian, and in which the time does not change in the spring or fall. If you select the Atlantic/Reykjavik time zone, the iLO CM firmware web pages and log entries display the exact time provided by the NTP server.
NOTE:
Configure the NTP servers to use Coordinated Universal Time (GMT).
6.
(Optional) To manually set the date and time, do the following:
•
Click the date box and select the desired date from the calendar.
•
Click the time box and then enter a time using the keyboard (you can clear the time by clicking the X icon).
7.
Click Apply to save the changes.
The following message appears:
The chassis manager will automatically reset to apply the settings.
Continue to apply the settings and reset the chassis manager?
8.
Click Yes.
A reset ends all active sessions. It might take several minutes before you can re-establish a connection.
TIP:
If you notice that event log entries have an incorrect date or time, make sure that the NTP server addresses and time zone are correct. The event log includes entries that indicate success or failure when contacting the NTP server(s).
iLO CM firmware user accounts
The iLO CM firmware enables you to manage user accounts stored locally in secure memory.
You can create up to 12 local user accounts with custom login names and advanced password encryption. Privileges control individual user settings, and can be customized to meet user access requirements.
The Administrator privilege is required for adding, modifying, and deleting users. If you do not have this privilege, you can view your own settings and change your own password.
Viewing local user accounts
Select User Administration from the main menu.
iLO CM firmware user accounts 81
The User Administration page shows the login name and full name of each user. To view the following information for a user, select the user in the user list:
•
Privileges—The access level granted to the specified user.
◦
Administrator—Read and write access to all iLO CM firmware features.
◦
Operator—Allows system actions, but cannot configure the iLO CM firmware or manage user accounts.
◦
User—Read-only access. A user cannot configure or write to the iLO CM firmware, or perform system actions.
◦
None—If no privilege is selected, a user cannot log into the iLO CM firmware.
•
Chassis access—Indicates whether a specified user has chassis access.
•
Cartridge access—If a custom access level is set for the specified user, this indicates which cartridges the user can access.
•
Switches access—If a custom access level is set for the specified user, this indicates which switches the user can access.
•
User status—Indicates whether a specified user access is enabled or disabled.
•
Authorized SSH Keys—Displays the public key hash for the specified user, if an SSH key was added to the user’s account.
Authorizing new SSH keys
1.
Create a new public SSH key.
2.
Select User Administration from the main menu.
3.
Select a user.
4.
Click Actions+Authorize new SSH key.
The Authorize New Key window displays.
5.
Paste your public ASCII PEM base64 encoded key in the box provided.
NOTE:
HPE recommends using RSA key encryption. The Moonshot Web Interface accepts
RSA keys up to 8096-bits in length. While the interface also accepts DSA encrypted keys, it only supports up to 3072-bit DSA key length. Additionally, DSA key verification is a much longer operation compared to RSA key verification of the same encryption level.
6.
Click Import Public Key.
Deleting SSH keys
1.
Select User Administration from the main menu.
2.
Select a user.
3.
Click Actions+Delete SSH key.
A prompt displays verifying the action to be taken.
4.
Click Yes to confirm the deletion or click Cancel.
Adding local user accounts
Prerequisites
You must have the Administrator privilege to perform this procedure.
Adding a user account
1.
From the main menu, select User Administration.
82 Configuring Moonshot System
2.
Do one of the following:
•
Click + Add user.
•
Select Actions→Add.
3.
Provide the following details on the Add User page:
•
Full name appears in the user list on the User Administration page. It does not have to be the same as the Login name. The Full name must use printable characters.
•
Login name is the name you use when logging in to the iLO CM firmware. It appears in the user list on the User Administration page and in logs. The Login name does not have to be the same as the Full name. The login name must use printable characters.
•
Password and Password confirm set and confirm the password that is used for logging in to the iLO CM firmware.
Use the set password minimum command to configure the password minimum length. For more information, see the Moonshot iLO Chassis Management CLI user guide.
4.
Select from the following privileges:
•
Administrator
•
Operator
•
User
•
None
5.
Select whether to enable or disable the account by clearing or selecting the User status box. This is useful for administrator who want to add users who will later be activated.
iLO CM firmware user accounts 83
6.
Optional—Do one of the following for Slot access:
•
Select All to give the user access to all cartridge and switch slots in the chassis.
•
Select Custom to configure the user’s access to only specific cartridge and switch slots.
When this option is selected, a top view of the chassis appears. When adding a user, by default all cartridge and switch slots are selected.
◦
Select each cartridge and switch bay the user should have access to by selecting or clearing the checkboxes in the image.
◦
Click Select all to give access to all cartridge and switch bays. Click Select all again to clear all of your selections.
◦
Select Chassis access to allow the user to modify chassis settings. If Chassis
access is the only option selected, the user will be able to add and edit user accounts, regardless of the iLO CM privileges level.
•
Select None to restrict a user’s access to all non-cartridge or switch related functions.
7.
Click Apply to save the new user.
More information
“Password guidelines” (page 87)
Editing local user accounts
Prerequisites
You must have the Administrator privilege to perform this procedure.
Editing a user account
1.
From the main menu, select User Administration.
2.
Select a user account and then select Actions→Edit.
3.
Provide the following details on the Edit <user name> page:
•
Full name appears in the user list on the User Administration page. It does not have to be the same as the Login name. The Full name must use printable characters.
•
Login name is the name you use when logging in to the iLO CM firmware. It appears in the user list on the User Administration page and in logs. The Login name does not have to be the same as the Full name. The login name must use printable characters.
•
Password and Password confirm set and confirm the password that is used for logging in to the iLO CM firmware.
Use the set password minimum command to configure the password minimum length. For more information, see the Moonshot iLO Chassis Management CLI user guide.
4.
Select from the following privileges:
•
Administrator
•
Operator
•
User
•
None
5.
Select whether to enable or disable the account by clearing or selecting the User status box. If you clear the box for the currently logged in user, the system immediately logs out.
84 Configuring Moonshot System
6.
Optional—Do one of the following for Slot access:
•
Select All to give the user access to all cartridge and switch slots in the chassis.
•
Select Custom to configure the user’s access to only specific cartridge and switch slots.
When this option is selected, a top view of the chassis appears. When adding a user, by default all cartridge and switch slots are selected.
◦
Select each cartridge and switch bay the user should have access to by selecting or clearing the checkboxes in the image.
◦
Click Select all to give access to all cartridge and switch bays. Click Select all again to clear all of your selections.
◦
Select Chassis access to allow the user to modify chassis settings. If Chassis
access is the only option selected, the user will be able to add and edit user accounts, regardless of the iLO CM privileges level.
•
Select None to restrict a user’s access to all non-cartridge or switch related functions.
7.
Click Apply to save the user account changes.
More information
“Password guidelines” (page 87)
Adding and editing directory groups
Users who have the Administrator privilege can add and edit iLO CM firmware directory groups.
Adding directory group accounts
Users who have the Administrator privilege can add iLO CM firmware directory groups.
1.
From the main menu, select User Administration.
2.
Do one of the following:
•
Click + Directory Groups.
•
Click an existing directory group and then select Actions→Add.
NOTE:
The Directory Group must already exist in the directory before adding it as a group with access to the iLO CM firmware.
iLO CM firmware user accounts 85
3.
Provide the following details on the Add Directory Group page:
•
Group DN appears in the user list on the User Administration page.
•
Group SID is the security identifier of the group, and also appears in the user list.
4.
Select from the following privileges:
•
Administrator—Read and write access to all iLO CM firmware features.
•
Operator—Allows system actions, but cannot configure the iLO CM firmware or manage user accounts.
•
User—Read-only access. The group cannot configure or write to the iLO CM firmware, or perform system actions.
•
None—If no privilege is selected, a user cannot log into the iLO CM firmware.
For information about the iLO CM privileges and the features they enable, see the moonshot iLO chassis management CLI user guide.
5.
Optional—Do one of the following for Slot access:
•
Select All to give the group access to all cartridge and switch slots in the chassis.
•
Select Custom to configure the group’s access to only specific cartridge and switch slots. When this option is selected, a top view of the chassis appears. When adding a group, by default all cartridge and switch slots are selected.
◦
Select each cartridge and switch bay the group should have access to by selecting or clearing the checkboxes in the image.
◦
Click Select all to give access to all cartridge and switch bays. Click Select all again to clear all of your selections.
◦
Select Chassis access to allow the group to modify chassis settings. If Chassis
access is the only option selected, the user will be able to add and edit user accounts, regardless of the iLO CM privileges level.
•
Select None to restrict a user’s access to all non-cartridge or switch related functions.
6.
Click Apply to save the new user.
Editing directory group access
Users who have the Administrator privilege can edit iLO CM firmware group access.
1.
From the main menu, select User Administration.
2.
Select a directory group and then select Actions→Edit.
3.
Provide the following details on the Edit Directory Group page:
•
Group DN appears in the user list on the User Administration page.
•
Group SID is the security identifier of the group, and also appears in the user list.
4.
Select from the following privileges:
•
Administrator—Read and write access to all iLO CM firmware features.
•
Operator—Allows system actions, but cannot configure the iLO CM firmware or manage user accounts.
•
User—Read-only access. A user cannot configure or write to the iLO CM firmware, or perform system actions.
•
None—If no privilege is selected, a user cannot log into the iLO CM firmware.
For information about the iLO CM privileges and the features they enable, see the moonshot iLO chassis management CLI user guide.
86 Configuring Moonshot System
5.
Optional—Do one of the following for Slot access:
•
Select All to give the group access to all cartridge and switch slots in the chassis.
•
Select Custom to configure the group’s access to only specific cartridge and switch slots. When this option is selected, a top view of the chassis appears.
◦
Select each cartridge and switch bay the group should have access to by selecting or clearing the checkboxes in the image.
◦
Click Select all to give access to all cartridge and switch bays. Click Select all again to clear all of your selections.
◦
Select Chassis access to allow the user to modify chassis settings. If Chassis
access is the only option selected, the user will be able to add and edit user accounts, regardless of the iLO CM privileges level.
•
Select None to restrict a user’s access to all non-cartridge or switch related functions.
6.
Click Apply to save the user account changes.
Password guidelines
HP recommends that you follow these password guidelines:
•
The maximum password length is 39 characters.
•
Passwords can include any characters except for spaces.
•
The default minimum password length is 8 characters.
Modify this with the set password minimum CLI command.
For information about setting the password minimum value, see the HPE Moonshot iLO Chassis
Management CLI User Guide.
iLO CM firmware user accounts 87
5 Working with events iLO CM event log
The event log provides a record of significant events recorded by the iLO CM firmware.
Logged events include major events such as a power outage or system reset, and iLO CM firmware events such as firmware updates, configuration changes, and successful or unsuccessful browser and SSH logins.
Viewing the event log
1.
Select Event Log in the main menu.
2.
Use the event log filters to customize the log view.
More information
“Customizing the event log view” (page 89)
Event log details
•
ID—The event ID number. Events are numbered in the order in which they are generated.
By default, the event log is sorted by the ID, with the most recent event at the top.
•
Severity—The importance of the detected event.
•
Last Update—The date and time when the latest event of this type occurred. This value is based on the date and time stored by the iLO CM firmware.
For information about setting the time in the iLO CM firmware, see
88 Working with events
•
Initial Update—The date and time when the first event of this type occurred. This value is based on the date and time stored by the iLO CM firmware.
If the iLO CM firmware did not recognize the date and time when the event was first created,
[NOT SET] is displayed.
•
Count—The number of times this event has occurred (if supported).
In general, important events generate an event log entry each time they occur. They are not consolidated into one event log entry.
When less important events are repeated, they are consolidated into one event log entry, and the Count and Last Update values are updated. Each event type has a specific time interval that determines whether repeated events are consolidated or a new event is logged.
•
Description—The description identifies the component and detailed characteristics of the recorded event.
•
Location—The component or subsystem that identified the logged event.
More information
Event log icons
•
•
• iLO CM uses the following icons to indicate event severity:
•
Critical—The event indicates a service loss or imminent service loss. Immediate attention is needed.
Caution—The event is significant but does not indicate performance degradation.
Informational—The event provides background information.
Unknown—The event severity could not be determined.
Customizing the event log view
To customize the list of events, do one of the following:
•
To filter by severity, select a severity level from the Severity menu.
•
To filter by the Last Update date, select a date range in the Last Update menu.
iLO CM event log 89
•
To filter by the Initial Update date, select a date range in the Initial Update menu.
•
To search for events based on dates, event IDs, or description text, enter text in the Search box, and then press Enter.
•
Click Reset filters to set the filters back to the default values.
•
Click a column heading to sort the event log table by that column.
•
When sorting the event log table by column, click the triangle next to the column heading to change the display to ascending or descending order.
Saving the event log to a CSV file
1.
From the main menu, select Event Log.
2.
Select Actions→View CSV.
90 Working with events
3.
In the Moonshot Event Log CSV window, click Save, and then follow the browser prompts to save or open the file.
4.
Click Close to close the window.
Clearing the event log
Users with the Administrator privilege can clear the event log of all previously logged information.
1.
From the main menu, select Event Log.
2.
Select Actions→Clear Log.
3.
When prompted to confirm the request, click Yes.
The following event is recorded:
Event log cleared by <user name>.
Integrated Management Log
The IML provides a record of historical events that have occurred on the HPE Moonshot System.
Entries in the IML can help you diagnose issues or identify potential issues. Preventative action might help to avoid disruption of service.
Examples of the types of information recorded in the IML follow:
•
Fan insertion, removal, or failure
•
Cartridge insertion, removal, or error
•
Power supply insertion, removal, or failure
•
Temperature events
•
AlertMail activities
•
Firmware updates
•
Switch insertion and removal
•
IML cleared
Integrated Management Log 91
Viewing the IML
1.
To view the IML, select Integrated Management Log in the main menu.
2.
Use the IML filters to customize the log view.
The IML displays the following information:
•
The first column on the left side of the web interface displays a check box next to each event with Critical or Caution status. Use this check box to select an event to mark as repaired.
For information about marking events as repaired, see
“Marking an IML entry as repaired”
•
ID—The event ID number. Events are numbered in the order in which they are generated.
By default, the IML is sorted by the ID, with the most recent event at the top. A factory reset will reset the counter.
•
Severity—The importance of the detected event.
Possible values follow:
◦
Critical—The event indicates a service loss or an imminent service loss. Immediate attention is needed.
◦
Caution—The event is significant but does not indicate performance degradation.
◦
Informational—The event provides background information.
◦
Repaired—An event has undergone corrective action.
◦
Unknown—The event severity could not be determined.
•
Class—Identifies the type of event that occurred, for example, Environment, Error Report,
Maintenance, OS, Rack Infrastructure, or System Revision.
•
Last Update—The date and time when the latest event of this type occurred. This value is based on the date and time stored by the iLO CM firmware.
For more information about setting the time in the iLO CM firmware, see
“Editing the time settings” (page 79)
.
•
Initial Update—The date and time when the first event of this type occurred. This value is based on the date and time stored by the iLO CM firmware.
92 Working with events
•
Count—The number of times this event has occurred (if supported).
In general, important events generate an IML entry each time they occur. They are not consolidated into one event log entry.
When less important events are repeated, they are consolidated into one IML entry, and the
Count and Last Update values are updated. Each event type has a specific time interval that determines whether repeated events are consolidated or a new event is logged.
•
Description—The description identifies the component and detailed characteristics of the recorded event.
•
Location—The component or subsystem that identified the logged event.
More information
“Customizing the IML view” (page 93)
Customizing the IML view
To customize the list of events, do one of the following:
•
To filter by severity, select a severity level from the Severity menu.
•
To filter by class, select a class from the Class menu.
•
To filter by the Last Update date, select a date range in the Last Update menu.
Integrated Management Log 93
•
To filter by the Initial Update date, select a date range in the Initial Update menu.
•
To search for events based on dates, event IDs, or description text, enter text in the Search box, and then press Enter.
•
Click Reset filters to set the filters back to the default values.
•
Click a column heading to sort the IML table by that column.
•
When sorting the IML table by column, click the triangle next to the column heading to change the display to ascending or descending order.
Marking an IML entry as repaired
Use this feature to change the status of an IML entry from Critical or Caution to Repaired. You must have the Administrator privilege to use this feature.
When a Critical or Caution event is reported in the IML:
1.
Investigate and repair the issue.
2.
From the main menu, select Integrated Management Log.
94 Working with events
3.
Select the log entry.
To select an IML entry, click the check box next to the entry in the first column of the IML table. If a check box is not displayed next to an IML entry, that entry cannot be marked as repaired.
4.
Select Actions→Mark Repaired.
The iLO CM firmware web interface refreshes, and the selected log entry status changes to
Repaired.
Adding a maintenance note to the IML
Use the maintenance note feature to create a log entry that logs information about maintenance activities such as component upgrades, system backups, periodic system maintenance, or software installations. You must have the Administrator privilege to use this feature.
1.
From the main menu, select Integrated Management Log.
2.
Select Actions→Add Maintenance Note.
The Add Maintenance Note window opens.
3.
Enter the text that you want to add as a log entry, and then click OK.
You can enter up to 227 bytes of text. You cannot submit a maintenance note without entering some text.
An Informational log entry with the class Maintenance is added to the IML.
Saving the IML to a CSV file
1.
From the main menu, select Integrated Management Log.
2.
Select Actions→View CSV.
Integrated Management Log 95
3.
In the Integrated Management Log CSV window, click Save, and then follow the browser prompts to save or open the file.
4.
Click Close to close the window.
Clearing the IML
Users with the Administrator privilege can clear the IML of all previously logged information.
1.
From the main menu, select Integrated Management Log.
2.
Select Actions→Clear Log.
3.
When prompted to confirm the request, click Yes.
The following event is recorded:
IML Cleared by <user name>.
96 Working with events
6 Troubleshooting
This chapter provides troubleshooting solutions for the Moonshot Web Interface.
Recovering a Moonshot iLO CM firmware password
Moonshot 1500 CM modules ship with default credentials, Administrator and password.
Change these credentials after deployment, in accordance with good security practices.
If user credentials are forgotten or lost, and no administrator access is available, use the security override switch located on the Moonshot 1500 CM module. In the proper position, the security override switch allows authentication as Administrator to the Moonshot iLO CM firmware without validating login credentials. New user account credentials can be defined once access to iLO CM is established. Restore the security override switch to the default position after this procedure is complete.
NOTE:
Existing account passwords cannot be retrieved from the Moonshot iLO CM firmware.
You must use this procedure to restore Administrator access.
Access to the security override switch requires physical access to the iLO Chassis Manager module.
1.
Remove the Moonshot 1500 CM module.
The following changes occur while the Moonshot 1500 CM module is removed:
•
Chassis fans automatically switch to maximum speed.
•
Powered cartridges remain on, and unpowered cartridges remain off.
•
Cartridge buttons (power, UID, Link) do not work.
Management capabilities resume and chassis fans switch to an appropriate speed after the
Moonshot 1500 CM module is reinserted.
2.
Locate the switch bank at the back of the iLO Chassis Manager module, on the bottom printed circuit assembly (PCA) between the high-density pin connectors. The switch bank can be accessed without disassembling the chassis management module. The default position is for all of the DIP switches to be in the same position, closest to the adjacent edge of the PCA.
3.
Toggle the security override switch, DIP switch 1, which is the left-most position closest to the center of the module. Do not change the position of any other switches.
Recovering a Moonshot iLO CM firmware password 97
Figure 1 Toggle the security override switch
4.
Reinsert the Moonshot 1500 CM module and wait for it to boot.
5.
Connect to the Moonshot iLO CM firmware using a serial port or SSH. When the Login prompt displays, press Enter twice.
WARNING!
While the security override is toggled, anyone may log into the chassis manager as the Administrator because no password is required. Anyone accessing the Moonshot iLO CM firmware will see a security alert display after login.
6.
Set up a new account or reset the password for the Administrator account.
The following example shows how to find the list of existing user accounts and modify one to have a known password “Moonsh0t”:
Example 1 Resetting the Administrator password
hpiLO-> show user all
Local User Accounts:
#-----------------------
Current User:
User Name: Administrator
Full Name: Administrator
User Privilege: ADMINISTRATOR
Status: ENABLED hpiLO-> set user password Administrator Moonsh0t
User: "Administrator" password set.
To configure a new user, you may need some or all of the following commands:
• show user all
• set user password
• set user privilege
• enable user
98 Troubleshooting
• remove user
• set password minimum
7.
After creating a new user account or resetting the Administrator password, remove the iLO
Chassis Manager module.
The following changes occur while the Moonshot 1500 CM module is removed:
•
Chassis fans automatically switch to maximum speed.
•
Powered cartridges remain on, and unpowered cartridges remain off.
•
Cartridge buttons (power, UID, Link) do not work.
Management capabilities resume and chassis fans switch to an appropriate speed after the
Moonshot 1500 CM module is reinserted.
8.
Restore the security DIP switch to its original position.
Figure 2 Re-enable security DIP switch
9.
Insert the iLO Chassis Manager module.
10. Verify access to the Moonshot iLO CM firmware with the new username or password.
A connection error occurs after a firmware update
Symptom
You cannot connect the iLO CM firmware after updating the firmware by using the web interface.
Action
Clear the browser cache and try again.
iLO CM firmware login name and password not accepted
Symptom
An iLO CM firmware login attempt fails.
A connection error occurs after a firmware update 99
Solution 1
Cause
The user account information was entered incorrectly.
Action
Enter the correct user account information.
•
Passwords are case-sensitive.
•
User names are not case-sensitive. Uppercase and lowercase characters are treated the same (for example, Administrator is treated as the same user as administrator).
100 Troubleshooting
7 Support and other resources
Accessing Hewlett Packard Enterprise Support
•
For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website:
www.hpe.com/assistance
•
To access documentation and support services, go to the Hewlett Packard Enterprise Support
Center website:
www.hpe.com/support/hpesc
Information to collect
•
Technical support registration number (if applicable)
•
Product name, model or version, and serial number
•
Operating system name and version
•
Firmware version
•
Error messages
•
Product-specific reports and logs
•
Add-on products or components
•
Third-party products or components
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:
◦
Hewlett Packard Enterprise Support Center Get connected with updates page:
www.hpe.com/support/e-updates
◦
Software Depot website:
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:
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
Website
Hewlett Packard Enterprise Information Library
Hewlett Packard Enterprise Support Center
Link www.hpe.com/info/enterprise/docs www.hpe.com/support/hpesc
Accessing Hewlett Packard Enterprise Support 101
Website
Contact Hewlett Packard Enterprise Worldwide
Subscription Service/Support Alerts
Link www.hpe.com/assistance www.hpe.com/support/e-updates
Software Depot
Customer Self Repair
Insight Remote Support
Serviceguard Solutions for HP-UX
www.hpe.com/support/softwaredepot www.hpe.com/support/selfrepair www.hpe.com/info/insightremotesupport/docs www.hpe.com/info/hpux-serviceguard-docs
Single Point of Connectivity Knowledge (SPOCK) Storage compatibility matrix
www.hpe.com/storage/spock
Storage white papers and analyst reports
www.hpe.com/storage/whitepapers
Customer self repair
Hewlett Packard Enterprise customer self repair (CSR) programs allow you to repair your product.
If a CSR part needs to be replaced, it will be shipped directly to you so that you can install it at your convenience. Some parts do not qualify for CSR. Your Hewlett Packard Enterprise authorized service provider will determine whether a repair can be accomplished by CSR.
For more information about CSR, contact your local service provider or go to the CSR website:
www.hpe.com/support/selfrepair
Remote support
Remote support is available with supported devices as part of your warranty or contractual support agreement. It provides intelligent event diagnosis, and automatic, secure submission of hardware event notifications to Hewlett Packard Enterprise, which will initiate a fast and accurate resolution based on your product’s service level. Hewlett Packard Enterprise strongly recommends that you register your device for remote support.
For more information and device support details, go to the following website:
www.hpe.com/info/insightremotesupport/docs
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 ([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.
102 Support and other resources
8 A Appendix
SNMP trap codes and descriptions
shows the possible traps and their descriptions.
Table 2 SNMP traps
Trap Code
cpqHe3FltTolFanDegraded 6035 cpqHe3FltTolFanInserted 6038 cpqHe3FltTolFanRemoved 6039 cpqHe4FltTolPowerSupplyOk 6048 cpqHe4FltTolPowerSupplyFailed 6050 cpqHo2GenericTrap 11003
Desription
The fault-tolerant fan condition has been set to Degraded.
A fault-tolerant fan has been inserted.
A fault-tolerant fan has been removed.
The power supply condition has been reset to ok.
The power supply condition has been set to Failed.
Generic trap. Verifies that the SNMP configuration, client
SNMP console, and network are operating correctly. You can use the cpqHo2GenericTrap 11003 iLO web interface to generate this alert to verify receipt of the alert on the SNMP console.
cpqNodeTempDegraded 23001 cpqNodeTempOk 23002 cpqNodeTempFailed 23003 cpqNodeErrorEvent 23004 cpqNodePowerOn 23010 cpqNodePowerOff 23011
The temperature status of a Moonshot node has been set to Degraded, and the temperature is outside the normal operating range. Depending on the system configuration, this system might be shut down.
The temperature status of a Moonshot node has been set to OK.
The temperature status of a Moonshot node has been set to be above the critical threshold.
The node has reported an error event. The details of the error event are in the cpqNodeErrorMessage string.
A Moonshot node has been powered on
A Moonshot node has been powered off
SNMP trap codes and descriptions 103
Index
A
accessing
Active Directory
active iLO sessions
active sessions
B
browser support
C
certificate signing request
contacting Hewlett Packard Enterprise, 101
D
DHCP
directory settings
authentication, 72 configuring, 72 directory server settings, 72
test results, 74 verifying, 74
directory tests
disconnecting
DNS name
DNS servers
documentation
domain name
E
event log
F
firmware
viewing installed firmware, 44
104 Index
G
gateway IP address
H
host name
I
iLO
iLO connection error
iLO login
iLO web interface see web interface
IP address
IPv4
DNS servers, 60 gateway address, 60
IP address, 60 ping gateway on startup, 60 static routes, 60 subnet mask, 60
K
L
logs
M
maintenance note
N
name service limitations, 62 namespace issues, 62
network configuration
P
ping gateway on startup
R
S
scripting and command line
setting up iLO
network connection, 8 overview, 8
setting up Moonshot
SSL
SSL certificates
static routes
subnet mask
support
Hewlett Packard Enterprise, 101
T
temperature information
Troubleshooting
troubleshooting
iLOconnection error, 99 login, 99
U
updates
user accounts
overview, 81 privileges, 81 viewing, 81
W
web interface
WINS servers
105
Lejupielādēt
Publiskā saite ir atjaunināta
Ir atjaunināta publiskā saite uz jūsu tērzēšanu. You may view and manage your chat links after registration here.
Dokumenta publiskā saite
Reklāma