Print | Rate this content

HPE Integrated Lights Out (iLO 5) for Gen10 Servers - Configuring iLO Management Settings

Agentless management and AMS

Agentless Management uses out-of-band communication for increased security and stability. WithAgentless Management, health monitoring and alerting is built into the system and begins working themoment a power cord is connected to the server. This feature runs on the iLO hardware, independent ofthe operating system and processor.

To collect information from devices and components that cannot communicate directly with iLO, install theAgentless Management Service (AMS).

Information provided by Agentless Management with and without AMS

Component
Agentless Management without AMS
Additional information provided whenAMS is installed
Server health
  • Fans

  • Temperatures

  • Power supplies

  • Memory

  • CPU

  • NVDIMM

N/A
Storage
  • Smart Array

  • SMART Drive Monitoring (connectedto Smart Array)

  • Internal and external drives connectedto Smart Array

  • Smart Storage battery monitoring(supported servers only)

  • SMART Drive Monitoring (connectedto Smart Array, Smart HBA, and AHCI)

  • iSCSI (Windows)

  • NVMe drives

Network
  • MAC addresses for embedded NICsthat support NC-SI over MCTP

  • Physical link connectivity and link up/link down traps for NICs that supportNC-SI over MCTP

  • Fibre Channel adapters that supportHewlett Packard Enterprise vendordefinedMCTP commands

  • MAC and IP address for standup andembedded NICs

  • Link up/link down traps

  • NIC teaming and bridging information(Windows and Linux)

  • Supported Fibre Channel adapters

  • VLAN information (Windows andLinux)

Other
  • iLO data

  • Firmware inventory

  • Device inventory

  • OS information (host SNMP MIB)

  • Driver/service inventory

  • Logging events to OS logs1,2

Prefailure warranty
  • Memory

  • Drives (physical and logical)

N/A
NOTE: 1.AMS-based OS logging for Linux (/var/log/messages for Red Hat and SuSE Linux Enterprise Serverand /var/log/syslogfor VMware).

2.Smart Array logging is supported.

top

Agentless management service

  • AMS is installed automatically if you use the Intelligent Provisioning Recommended installationmethod for Windows installation.

  • When you install AMS on Windows systems, the Agentless Management Service Control Panel isinstalled. You can use the Control Panel to configure SNMP settings, to enable or disable AMS, and toremove AMS.

  • AMS writes operating system configuration information and critical events to the Active Health SystemLog.

  • Install the iLO Channel Interface Driver before installing AMS.

  • With iLO 5, AMS includes the optional System Management Assistant. You can use the SystemManagement Assistant if you want to use an OS-based SNMP service to handle information providedby iLO Agentless Management and AMS.

  • If AMS is not installed:

    • iLO does not display a full set of data on the component information pages, which are included inthe System Information and Firmware & OS Software sections of the navigation tree.

    • iLO does not have access to OS-specific information.

top

Installing AMS

Procedure

  1. Obtain AMS from one of the following sources:

  2. Install the software.

    For instructions on using the SPP, see the SPP documentation at Click here to access the Hewlett Packard Enterprise Information Library .

    For other download types, follow the installation instructions provided with the software.

top

Verifying AMS installation

Verifying AMS status: iLO web interface

Procedure

  1. Click System Information in the navigation tree.

    AMS is listed in the Subsystems and Devices table on the Health Summary page. The possiblevalues follow:

    • Not available - AMS is not available because it was not detected, the server is in POST, or theserver is powered off.

    • OK - AMS is installed and running.

top

Verifying AMS status: windows

Procedure

  1. Open the Windows Control Panel.

    If the AMS Control Panel is present, then AMS is installed.

  2. Open the AMS Control Panel.

  3. Click the service tab.

    If AMS is enabled, the following message appears:

    Agentless Management Service(AMS) is enabled.

top

Verifying AMS status: SuSE and red hat enterprise linux

Procedure

  1. To verify that AMS is installed, enter the following command rpm –qi amsd.

  2. To verify that AMS is running, enter one of the following commands:

    • SuSE Linux Enterprise Server 12 and Red Hat Enterprise Linux 7 - systemctl statussmad; systemctl status amsd.

    • SuSE Linux Enterprise Server 11 and Red Hat Enterprise Linux 6 - service smad status;service amsd status.

top

Verifying AMS status: VMware

Procedure

  1. Verify that AMS is installed.

    1. Access the VMware host from the VMware vSphere Client.

    2. Navigate to the Inventory > Configuration > Health Status tab for the server.

    3. Click the plus sign (+) next to Software Components.

      The software installed on the host is listed. The AMS component includes the string amsd.

      The full name of the AMS component is different for each supported version of ESX/ESXi.

  2. To verify that AMS is running, enter the following command:/etc/init.d/ams.sh status.

top

Verifying AMS status: ubuntu

Procedure

  1. To verify that AMS is installed, enter the following command: dpkg -l amsd.

  2. To verify that AMS is running, enter one of the following commands:

    • Ubuntu 14 - systemctl status smad; systemctl status amsd.

    • Ubuntu 12 - service smad status; service amsd status.

top

Restarting AMS

Procedure

  • Windows - Navigate to the Windows Services page and restart AMS.

  • SuSE Linux Enterprise Server 12 and Red Hat Enterprise Linux 7 - Enter the following command: systemctl restart smad; systemctl restart amsd.

  • SuSE Linux Enterprise Server 11 and Red Hat Enterprise Linux 6 - Enter the following command: service smad restart; service amsd restart.

  • VMware - Enter the following command: /etc/init.d/ams.sh restart.

  • Ubuntu 14 - Enter the following command: sudo systemctl restart smad; sudo systemctlrestart amsd.

  • Ubuntu 12 - Enter the following command: sudo service smad restart; sudo service amsd restart.

top

System management assistant

With the release of Gen10 servers, iLO no longer supports OS-based SNMP agents. The SystemManagement Assistant (SMA) is an Agentless Management Service feature for users who want to runapplications that obtain SNMP information from the OS.

Security

SMA communicates over secure iLO channels.

AMS modes

  • AMS (forward mode) - The standard configuration of AMS is to pass information from the OS toiLO.

  • SMA (reverse mode) - When SMA is enabled, information is passed from iLO to the OS.

Installation

SMA is installed as part of the AMS package, and it is disabled by default.

Enabling SMA
  • Windows - Use the default AMS configuration to pass information from the OS to iLO. EnableSMA to pass information from iLO to the OS. The standard configuration of AMS and SMA can beenabled at the same time.

  • Linux and VMware - Use the default AMS configuration to pass information from the OS to iLO.Enable SMA to pass information from iLO to the OS. The default AMS configuration and SMAcannot be enabled at the same time.

SMA functionality

When SMA is enabled, it does the following:

  • Linux - Proxies AgentX protocol requests between iLO and a host-based SNMP master.

  • Windows, Linux, VMware - Proxies SNMP protocol requests between iLO and a host-basedSNMP service.

    This method is used when the host-based SNMP service does not support AgentX subagents.

SNMP master

With the default AMS configuration, AMS uses iLO as the SNMP master. SMA requires a host-basedservice to act as the SNMP master.

Information provided when SMA is enabled

  • Windows and Linux - SMA provides the same information that is listed in the AgentlessManagement with AMS column in the following table: Information provided by AgentlessManagement with and without AMS

  • VMware - SMA provides only SNMP traps.

top

Using the system management assistant (windows)

User can choose whether to enable the SMA during an interactive AMS installation, and the SMA is notenabled during a silent installation.

To use SMA, start the SMA service and verify that the Windows SNMP service is installed and configured.

Prerequisites

AMS is installed.

Procedure

  1. Install the Windows SNMP service.

    1. Open Server Manager.

    2. Select Add roles and features.

    3. Click Next in the Before You Begin section.

    4. Click Next in Installation Type section.

    5. Click Next in Server Selection section.

    6. Click Next in Server Roles section.

    7. Expand the Remote Server Administration section.

    8. Expand Feature Administration Tools

    9. Ensure that SNMP Tools is selected.

    10. Select the check box to the left of the SNMP Service option.

    11. Click Next.

    12. Click Install and wait for the installation to complete.

  2. Configure the Windows SNMP service.

    1. Navigate to the Windows Services window.

    2. Right-click the SNMP service.

    3. Click the Security tab.

    4. Click Adds in the Accepted Community Names section.

    5. Select an access type in the Community Rights section.

    6. Enter a community name in the Community Name section.

    7. Click Add.

    8. Click the Traps tab.

    9. Enter a community name in the Community Name section, and then click Add to list.

    10. In the Trap Destination section, click Add, and then enter the IP address of a trap destination.

    11. Click OK.

  3. Start the SMA service.

    1. Navigate to the Windows Services window.

    2. Right-click the System Management Assistant, and then select Properties.

    3. Select Automatic in the Startup type menu, and then click OK.

    4. Right-click the System Management Assistant, and then select Start.

      NOTE: You can also start the SMA service by:
      • Navigating to <Program Files>\OEM\AMS\Service and then running the followingcommand: Files>\OEM\AMS\Service and then running the followingcommand:
      • Entering the following commands in a command prompt window: sc config smastart=auto and net start sma

top

Disabling the system management assistant (windows)

Procedure

  1. Navigate to the Windows Services window.

  2. Right-click the System Management Assistant, and then select Properties.

  3. Select Disabled in the Startup type menu, and then OK.

  4. Right-click the System Management Assistant, and then select Stop.

    NOTE: You can also disable the SMA service by navigating to <Program Files>\OEM\AMS\Service and then running the following command DisableSma.bat /f

top

Using the system management assistant for VMware

Prerequisites

AMS is installed.

Procedure

  1. Enable SNMP on the host and specify a trap destination.

    For example:

    esxcli system snmp set -e 1 -c public -t <trap dest IP address>@162/public

  2. Enter the following command to verify that SNMP is enabled:

    esxcli system snmp get

  3. Enter the following command to enable and start SMA:

    esxcli sma enable

  4. Enter the following command to verify that SMA is running:

  5. Verify that the SMA process (smad_rev) is running.

top

Disabling the system management assistant (VMware)

Procedure

  1. Run the following command: esxcli sma disable.

top

Using the system management assistant for (Linux)

Prerequisites

  • AMS is installed.

  • The host SNMP service is configured.

  • The network is configured to pass SNMP packets between the host and the SNMP clients.

Procedure

  1. Configure the host to support AgentX subagents by adding the following line as the first noncommentline in the /etc/snmp/snmpd.conf file:

    master agentx

  2. Enable the System Management Assistant.

    • SuSE Linux Enterprise Server 12 and Red Hat Enterprise Linux 7 - Enter the followingcommand: systemctl enable smad_rev; systemctl start smad_rev.

    • SuSE Linux Enterprise Server 11 and Red Hat Enterprise Linux 6 - Enter the followingcommand: service smad_rev start.

    • Ubuntu 14 - Enter the following command: sudo systemctl enable smad_rev; sudosystemctl start smad_rev.

    • Ubuntu 12 - Enter the following command: sudo service smad_rev start.

  3. Enable and start the Agentless Management Service.

    • SuSE Linux Enterprise Server 12 and Red Hat Enterprise Linux 7 - Enter the followingcommand: systemctl enable amsd_rev; systemctl start amsd_rev.

    • SuSE Linux Enterprise Server 11 and Red Hat Enterprise Linux 6 - Enter the followingcommand: service amsd_rev start.

    • Ubuntu 14 - Enter the following command: sudo systemctl enable amsd_rev; sudosystemctl start amsd_rev.

    • Ubuntu 12 - Enter the following command: sudo service amsd_rev start.

top

Configuring SNMP settings

The settings you configure on this page are for the default Agentless Management and AMSconfiguration. If you use the System Management Assistant and an OS-based SNMP service, similarsettings must be configured on the host.

Prerequisites

Configure iLO Settings privilege.

Procedure

  1. Click Management in the navigation tree.

    The SNMP Settings page is displayed.

  2. Enter the following values in the SNMP Settings section:

    • System Location

    • System Contact

    • System Role

    • System Role

    • System Role Detail

    • Read Community

    • Trap Community

      The SNMP Port value is read-only on this page. You can change this value on the Access Settingspage.

  3. To save the configuration, click Apply.

    More Information

    System Management Assistant

    • System Location - A string of up to 49 characters that specifies the physical location of the server.

    • System Contact - A string of up to 49 characters that specifies the system administrator or serverowner. The string can include a name, email address, or phone number.

    • System Role - A string of up to 64 characters that describes the server role or function.

    • System Role Detail - A string of up to 512 characters that describes specific tasks that the servermight perform.

    • Read Community - The configured SNMP read-only community string.

      The following formats are supported:

      • A community string (for example, public).

      • A community string followed by an IP address or FQDN (for example, public 192.168.0.1).

        Use this option to specify that SNMP access will be allowed from the specified IP address orFQDN.

        You can enter an IPv4 address, an IPv6 address, or an FQDN.

    • Trap Community - The configured SNMP trap community string.

    • SNMP Alert Destination(s) - The IP addresses or FQDNs of up to three remote managementsystems that will receive SNMP alerts from iLO.

      Typically, you enter the HPE SIM server console IP address in one of the SNMP Alert Destination(s)boxes.

      When SNMP Alert Destinations are configured using FQDNs, and DNS provides both IPv4 and IPv6addresses for the FQDNs, iLO sends traps to the address specified by the iLO Client Applicationsuse IPv6 first setting on the IPv6 page. If iLO Client Applications use IPv6 first is enabled, trapswill be sent to IPv6 addresses (when available). When iLO Client Applications use IPv6 first isdisabled, traps will be sent to IPv4 addresses (when available).

    • SNMP Port - The port used for SNMP communications. This value is read-only, but can be modifiedon the Access Settings page.

      To navigate to the Access Settings page, click the SNMP Port link.

  4. To save the user profile, click Apply.

top

SNMPv3 user options

  • Security Name - The user profile name. Enter an alphanumeric string of 1 to 32 characters.

  • Authentication Protocol - Sets the message digest algorithm to use for encoding the authorizationpassphrase. The message digest is calculated over an appropriate portion of an SNMP message, andis included as part of the message sent to the recipient. Select MD5 or SHA.

  • Authentication Passphrase - Sets the passphrase to use for sign operations. Enter a value of 8 to49 characters.

  • Privacy Protocol - Sets the encryption algorithm to use for encoding the privacy passphrase. Aportion of an SNMP message is encrypted before transmission. Select AES or DES.

  • Privacy Passphrase - Sets the passphrase used for encrypt operations. Enter a value of 8 to 49characters.

top

Deleting an SNMPv3 user profile

Prerequisites

Configure iLO Settings privilege.

Procedure

  1. Click Management in the navigation tree.

    The SNMP Settings page is displayed.

  2. Scroll to the SNMPv3 Users section.

  3. Select a user profile in the SNMPv3 Users section, and then click Delete.

  4. When prompted to confirm the request, click OK.

top

Configuring the SNMPv3 Engine ID

The SNMPv3 Engine ID sets the unique identifier of an SNMP engine belonging to an SNMP agententity.

Prerequisites

Configure iLO Settings privilege

Procedure

  1. Click Management in the navigation tree.

    The SNMP Settings page is displayed.

  2. Enter a value in the SNMPv3 Engine ID box.

    This value must be a hexadecimal string of 6 to 32 characters, not counting the preceding 0x, andmust be an even number of characters (for example, 0x01020304abcdef).

  3. Click Apply.

top

Configuring SNMP alerts

Prerequisites

Configure iLO Settings privilege.

Procedure

  1. Click Management in the navigation tree.

    The SNMP Settings page is displayed.

  2. Enter a value in the SNMPv3 Engine ID box.

    This value must be a hexadecimal string of 6 to 32 characters, not counting the preceding 0x, andmust be an even number of characters (for example, 0x01020304abcdef).

  3. Click Apply.

top

Configuring SNMP alerts

Prerequisites

Configure iLO Settings privilege

  1. Click Management in the navigation tree.

    The SNMP Settings page is displayed.

  2. Scroll to the SNMP Alerts section.

  3. Configure the Trap Source Identifier by selecting iLO Hostname or OS Hostname.

  4. Enable or disable the following alert types:

    • iLO SNMP Alerts

    • Cold Start Trap Broadcast

    • SNMPv1 Traps

  5. Optional: To generate a test alert and send it to the UDP addresses in the SNMP Alert Destination(s) boxes, click Send Test Alert.

    Test alerts are used to verify the network connectivity of iLO with the SNMP Alert Destination(s) addresses. After the alert is generated, check the alert destination for receipt of the alert.

  6. To save the configuration, click Apply.

top

SNMP alert settings

Trap Source Identifier

Determines the host name that is used in the SNMP-defined sysName variable when iLO generatesSNMP traps. The default setting is iLO Hostname.

The host name is an OS construct and does not remain persistent with the server when the harddrives are moved to a new server platform. The iLO sysName, however, remains persistent with thesystem board.

top

iLO SNMP alerts

Alert conditions that iLO detects independently of the host operating system can be sent to specifiedSNMP alert destinations. If this option is disabled, no traps will be sent to the configured SNMP alertdestinations.

top

Cold start trap broadcast

When this option is enabled and no valid trap destinations are configured, Cold Start Trap isbroadcast to a subnet broadcast address.

The Cold Start Trap is broadcast when any of the following conditions is met:

  • SNMP Alert Destinations are not configured.

  • iLO failed to resolve all the SNMP Alert Destinations

    The subnet broadcast address for an IPv4 host is obtained by performing a bitwise logical ORoperation between the bit complement of the subnet mask and the host IP address. For example, thehost 192.168.1.1, which has the subnet mask 255.255.252.0, has the broadcast address 192.168.1.1 | 0.0.3.255 = 192.168.3.255.

SNMPv1 Traps

When enabled, SNMPv1 traps are sent to the remote management systems configured in the SNMPAlert Destination(s) boxes.

top

Using the AMS Control Panel to configure SNMP andSNMP alerts (Windows only)

Procedure

  1. Open the Agentless Management Service Control Panel.

  2. Click the SNMP tab.

  3. Update the SNMP settings.

  4. Optional: To generate a test alert and send it to the TCP/IP addresses in the Trap Destination(s) boxes, click Send Test Trap.

    Test alerts are used to verify the network connectivity of iLO with the Trap Destination(s) addresses.After the alert is generated, check the alert destination for receipt of the alert.

  5. To save the configuration, click Apply.

top

SNMP traps

SNMP traps lists the SNMP traps that you can generate with iLO 5 and supported ProLiant servers andSynergy compute modules.

SNMP traps

TrapNumber
Trap Name
Description
0
Cold Start Trap
SNMP has been initialized, the systemhas completed POST, or AMS hasstarted.
4
Authentication Failure Trap
SNMP has detected an authenticationfailure.
1006
cpqSeCpuStatusChange
An uncorrectable machine checkexception has been detected in aprocessor.
1010
cpqSeUSBStorage DeviceRead Error Occurred
A read error occurred on an attachedUSB storage device.ª
1011
cpqSeUSBStorage DeviceWrite Error Occurred
A write error occurred on an attachedUSB storage device.
1012
cpqSeUSBStorage Device Redundancy Lost
USB storage device redundancy waslost.
1013
cpqSeUSBStorage Device Redundancy Restored
USB storage device redundancy wasrestored.
1014
cpqSeUSBStorageDeviceSync Failed
The sync operation to restore USBstorage device redundancy failed.
1015
cpqSePCIeDisk Temperature Failed
The temperature of the PCIe diskcrossed the upper critical threshold.
1016
cpqSePCIeDiskTemperatureOk
The temperature of the PCIe disk isnormal.
1017
cpqSePCIeDiskConditionChange
The status of the PCIe disk changed.
1018
cpqSePCIeDiskWearStatusChange
The PCIe disk wear status changed.
1019
cpqSePciDeviceAddedOrPoweredOn
A PCI disk was added or powered on.
1020
cpqSePciDeviceRemovedOrPoweredOff
A PCI device was removed or poweredoff
2014
cpqSiIntrusionInstalled
System intrusion hardware installed.
2015
cpqSiIntrusionRemoved
System intrusion hardware removed.
2016
cpqSiHoodReplaced
System hood replaced.
2017
cpqSiHoodRemovedOnPowerOff
System hood removed when serverpower was off.
3033
cpqDa6CntlrStatusChange
A change has been detected in thestatus of the Smart Array controller.
3034
cpqDa6LogDrvStatusChange
A change has been detected in thestatus of a Smart Array logical drive.
3038
cpqDa6AccelStatusChange
A change has been detected in thestatus of a Smart Array cache module.
3039
cpqDa6AccelBadDataTrap
The Smart Array cache module haslost backup power.
3040
cpqDa6AccelBatteryFailed
The Smart Array cache module backuppower has failed.
3046
cpqDa7PhyDrvStatusChange
A change has been detected in thestatus of a Smart Array physical drive.
3047
cpqDa7SpareStatusChange
A change has been detected in thestatus of a Smart Array spare drive.
3049
cpqDaPhyDrvSSDWearStatusChange
A change has been detected in theSSD wear status of a Smart Arrayphysical drive.
6026
cpqHe3ThermalConfirmation
The server was shut down due to athermal anomaly and is nowoperational.
6027
cpqHe3PostError
One or more POST errors haveoccurred.
6032
cpqHe3FltTolPowerRedundancyLost
The fault-tolerant power supplies havelost redundancy for the specifiedchassis.
6033
cpqHe3FltTolPowerSupplyInserted
A fault-tolerant power supply has beeninserted.
6034
cpqHe3FltTolPowerSupplyRemoved
A fault-tolerant power supply has beenremoved.
6035
cpqHe3FltTolFanDegraded
The fault-tolerant fan condition hasbeen set to Degraded.
6036
cpqHe3FltTolFanFailed
The fault-tolerant fan condition hasbeen set to Failed.
6037
cpqHe3FltTolFanRedundancyLost
The fault-tolerant fans have lostredundancy.
6039
cpqHe3FltTolFanRemoved
A fault-tolerant fan has been removed.
6040
cpqHe3TemperatureFailed
Temperature exceeded on the server.
6041
cpqHe3TemperatureDegraded
The temperature status has been set toDegraded, and the temperature isoutside the normal operating range.Depending on the systemconfiguration, this system might beshut down.
6042
cpqHe3TemperatureOk
The temperature status has been set toOK.
6048
cpqHe4FltTolPowerSupplyOk
The fault-tolerant power supplycondition has been reset to OK.
6049
cpqHe4FltTolPowerSupplyDegraded
The fault-tolerant power supplycondition has been set to Degraded.
6050
cpqHe4FltTolPowerSupplyFailed
The fault-tolerant power supplycondition has been set to Failed.
6051
cpqHeResilientMemMirroredMemoryEngaged
The Advanced Memory Protectionsubsystem has detected a memoryfault. Mirrored Memory has beenactivated.
6054
cpqHe3FltTolPowerRedundancyRestore
The fault-tolerant power supplies havereturned to a redundant state.
6055
cpqHe3FltTolFanRedundancyRestored
The fault-tolerant fans have returned toa redundant state.
6061
cpqHeManagementProcInReset
The management processor isresetting.
6062
cpqHeManagementProcReady
The management processor is ready.
6064
cpqHe5CorrMemReplaceMemModule
Memory errors have been corrected.Replace the memory module.
6069
cpqHe4FltTolPowerSupplyACpowerloss
The fault-tolerant power supply in thespecified chassis and bay reported ACpower loss.
6070
cpqHeSysBatteryFailed
The HPE Smart Storage Battery hasfailed.
6071
cpqHeSysBatteryRemoved
The HPE Smart Storage Battery hasbeen removed.
6072
cpqHeSysPwrAllocationNotOptimized
iLO could not determine the powerrequirements. The server powerallocation is not optimized.
6073
cpqHeSysPwrOnDenied
The server could not power onbecause the hardware cannot beidentified.
6074
cpqHePowerFailureError
A device power failure has beendetected.
6075
cpqHeInterlockFailureError
A device is missing or improperlyseated on the system board.
8029
cpqSs6FanStatusChange
The storage enclosure fan statuschanged.
8030
cpqSs6TempStatusChange
The storage enclosure temperaturestatus changed.
8031
cpqSs6PwrSupplyStatusChange
The storage enclosure power statuschanged.
8032
cpqSsConnectionStatusChange
The storage enclosure status changed.
9001
cpqSm2ServerReset
The server power has been reset.
9003
cpqSm2UnauthorizedLoginAttempts
The maximum unauthorized loginattempt threshold has been exceeded.
9005
cpqSm2SelfTestError
iLO 5 detected a self test error.
9012
cpqSm2SecurityOverrideEngaged
iLO 5 detected that the securityoverride jumper has been toggled tothe engaged position.
9013
cpqSm2SecurityOverrideDisengaged
iLO 5 detected that the securityoverride jumper has been toggled tothe disengaged position.
9017
cpqSm2ServerPowerOn
The server has been powered on.
9018
cpqSm2ServerPowerOff
The server has been powered off.
9019
cpqSm2ServerPowerOnFailure
A request was made to power on theserver, but the server could not bepowered on because of a failurecondition.
9020
cpqSm2IrsCommFailure
Communication with Insight RemoteSupport or Insight Online has failed.
9021
cpqSm2FirmwareValidationScanFailed
Firmware validation failure (iLO/ IE/SPS firmware).
9022
cpqSm2FirmwareValidationScanErrorRepaired
A reported firmware integrity scanissue was repaired.
9023
cpqSm2FirmwareValidationAutoRepairFailed
Firmware recovery failed.
11003
cpqHo2GenericTrap
Generic trap. Verifies that the SNMPconfiguration, client SNMP console,and network are operating correctly.You can use the iLO web interface togenerate this alert to verify receipt ofthe alert on the SNMP console.
11018
cpqHo2PowerThresholdTrap
A power threshold has been exceeded.
11020
cpqHoMibHealthStatusArrayChangeTrap
A change in the health status of theserver has occurred.
5022
cpqSasPhyDrvStatusChange
AMS detected a change in the status ofan SAS or SATA physical drive.
14004
cpqIdeAtaDiskStatusChange
AMS detected a change in the status ofan ATA disk drive.
16028
cpqFca3HostCntlrStatusChange
AMS detected a change in the status ofa Fibre Channel host controller.
18011
cpqNic3ConnectivityRestored
Connectivity was restored to a logicalnetwork adapter.
18012
cpqNic3ConnectivityLost
The status of a logical network adapterchanged to Failed.
18013
cpqNic3RedundancyIncreased
AMS detected that a previously failedphysical adapter in a connected logicaladapter group returned to the OKstatus.
18014
cpqNic3RedundancyReduced
AMS detected that a physical adapterin a logical adapter group changed toFailed status, but at least one physicaladapter remains in OK status.

For more information about these SNMP traps, see the following MIB files in the Insight Management MIBupdate kit for HPE SIM:

cpqida.mib
Drive array
cpqhost.mib
Server host system details
cpqhlth.mib
Server health system
cpqsm2.mib
Remote Insight/Integrated Lights-Out
cpqide.mib
IDE subsystem
cpqscsi.mib
SCSI system
cpqiscsi.mib
iSCSI system
cpqnic.mib
System NIC
cpqstsys.mib
Storage systems
cpqstdeq.mib
Server standard equipment
cpqfca.mib
Fibre Channel array
cpqsinfo.mib
System Information
cpqstsys.mib
Smart Array storage

top

iLO alert mail

iLO AlertMail enables you to configure iLO to send alert conditions detected independently of the hostoperating system to a specified email address. iLO mail alerts include major host system events.

Some email service providers establish filters and rules to block problem emails such as spam,commercial content, and unwanted volume. These tools might block the receipt of messages generatedby iLO. These email services are not suitable for receiving iLO AlertMail messages.

top

Enabling alert mail

Prerequisites

Procedure

  1. Click Management in the navigation tree, and then click the AlertMail tab.

  2. Set the Enable iLO AlertMail option to enabled.

  3. Enter the following information:

    • Email Address

    • Sender Domain

    • SMTP Port

    • SMTP Server

  4. Optional: To send a test message to the configured email address, click Send Test AlertMail.

    This button is available only when AlertMail is enabled.

  5. To save the changes, click Apply.

top

Alert mail options

  • Email Address - The destination email address for iLO email alerts. This string can be up to 63characters and must 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 emailaddress is formed by using the iLO name as the host name, and the sender domain as the domainname. This string can be up to 63 characters.

  • SMTP Port - The port that the SMTP server will use for unauthenticated SMTP connections. Thedefault value is 25.

  • SMTP Server - The IP address or DNS name of the SMTP server or the MSA. This server cooperateswith the MTA to deliver the email. This string can be up to 63 characters.

top

Disabling alert mail

Prerequisites

Procedure

  1. Click Management in the navigation tree, and then click the AlertMail tab.

  2. Set the Enable iLO AlertMail option to enabled.

  3. To save the changes, click Apply.

top

Remote syslog

The Remote Syslog feature allows iLO to send event notification messages to Syslog servers. The iLOfirmware Remote Syslog includes the IML and iLO Event Log.

top

Enabling iLO remote syslog

Prerequisites

Procedure

  1. Click Management in the navigation tree, and then click the Remote Syslog tab.

  2. Set the Enable iLO Remote Syslog option to enabled.

  3. Enter the following information:

    • Remote Syslog Server

    • Remote Syslog Port

  4. Optional: To send a test message to the configured syslog server, click Send Test Syslog.

    This button is available only when iLO Remote Syslog is enabled.

  5. To save the changes, click Apply.

top

Remote syslog options

  • Remote Syslog Server - The IP address, FQDN, IPv6 name, or short name of the server running theSyslog service. To enter multiple servers, separate the server IP address, FQDN, IPv6 name, or shortname with a semicolon. You can enter up to 63 characters per server, and a total of 127 characters.

    On Linux systems, a tool called syslog logs system events. You can set a syslog server on a remotesystem that will act as a central logging system for iLO systems. If the iLO Remote Syslog feature isenabled in iLO, it can send its logs to the syslog server.

  • Remote Syslog Port - The port number through which the Syslog server is listening. Only one portnumber can be entered in this box. When you enter multiple Remote Syslog servers, they must usethe same port. The default value is 514.

top

Disabling iLO remote syslog

Prerequisites

Procedure

  1. Click Management in the navigation tree, and then click the Remote Syslog tab.

  2. Set the Enable iLO Remote Syslog option to disabled.

  3. To save the changes, click Apply.

top

Provide feedback

Please rate the information on this page to help us improve our content. Thank you!
Document title: HPE Integrated Lights Out (iLO 5) for Gen10 Servers - Configuring iLO Management Settings
Document ID: emr_na-a00026111en_us-1
How helpful was this document?
How can we improve this document?
Note: Only English language comments can be accepted at this time.
Please wait while we process your request.