oracle® hardware management pack 2.3.x release notes

Oracle® Hardware Management Pack2.3.x Release Notes

Part No: E52100-18January 2017

Oracle Hardware Management Pack 2.3.x Release Notes

Part No: E52100-18

Copyright © 2014, 2017, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Exceptas expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform,publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, isprohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS. Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, deliveredto U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. Assuch, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/ordocumentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerousapplications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take allappropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of thissoftware or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks ofSPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registeredtrademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates arenot responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreementbetween you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content,products, or services, except as set forth in an applicable agreement between you and Oracle.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info


http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs

Référence: E52100-18

Copyright © 2014, 2017, Oracle et/ou ses affiliés. Tous droits réservés.

Ce logiciel et la documentation qui l’accompagne sont protégés par les lois sur la propriété intellectuelle. Ils sont concédés sous licence et soumis à des restrictions d’utilisation etde divulgation. Sauf stipulation expresse de votre contrat de licence ou de la loi, vous ne pouvez pas copier, reproduire, traduire, diffuser, modifier, accorder de licence, transmettre,distribuer, exposer, exécuter, publier ou afficher le logiciel, même partiellement, sous quelque forme et par quelque procédé que ce soit. Par ailleurs, il est interdit de procéder à touteingénierie inverse du logiciel, de le désassembler ou de le décompiler, excepté à des fins d’interopérabilité avec des logiciels tiers ou tel que prescrit par la loi.

Les informations fournies dans ce document sont susceptibles de modification sans préavis. Par ailleurs, Oracle Corporation ne garantit pas qu’elles soient exemptes d’erreurs et vousinvite, le cas échéant, à lui en faire part par écrit.

Si ce logiciel, ou la documentation qui l’accompagne, est livré sous licence au Gouvernement des Etats-Unis, ou à quiconque qui aurait souscrit la licence de ce logiciel pour lecompte du Gouvernement des Etats-Unis, la notice suivante s’applique:

U.S. GOVERNMENT END USERS. Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, deliveredto U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. Assuch, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/ordocumentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Ce logiciel ou matériel a été développé pour un usage général dans le cadre d’applications de gestion des informations. Ce logiciel ou matériel n’est pas conçu ni n’est destinéà être utilisé dans des applications à risque, notamment dans des applications pouvant causer des dommages corporels. Si vous utilisez ce logiciel ou matériel dans le cadre d’applications dangereuses, il est de votre responsabilité de prendre toutes les mesures de secours, de sauvegarde, de redondance et autres mesures nécessaires à son utilisation dans desconditions optimales de sécurité. Oracle Corporation et ses affiliés déclinent toute responsabilité quant aux dommages causés par l’utilisation de ce logiciel ou matériel pour ce typed’applications.

Oracle et Java sont des marques déposées d’Oracle Corporation et/ou de ses affiliés. Tout autre nom mentionné peut correspondre à des marques appartenant à d’autres propriétairesqu’Oracle.

Intel et Intel Xeon sont des marques ou des marques déposées d’Intel Corporation. Toutes les marques SPARC sont utilisées sous licence et sont des marques ou des marquesdéposées de SPARC International, Inc. AMD, Opteron, le logo AMD et le logo AMD Opteron sont des marques ou des marques déposées d’Advanced Micro Devices. UNIX est unemarque déposée d’The Open Group.

Ce logiciel ou matériel et la documentation qui l’accompagne peuvent fournir des informations ou des liens donnant accès à des contenus, des produits et des services émanant detiers. Oracle Corporation et ses affiliés déclinent toute responsabilité ou garantie expresse quant aux contenus, produits ou services émanant de tiers, sauf mention contraire stipuléedans un contrat entre vous et Oracle. En aucun cas, Oracle Corporation et ses affiliés ne sauraient être tenus pour responsables des pertes subies, des coûts occasionnés ou desdommages causés par l’accès à des contenus, produits ou services tiers, ou à leur utilisation, sauf mention contraire stipulée dans un contrat entre vous et Oracle.

Accessibilité de la documentation

Pour plus d’informations sur l’engagement d’Oracle pour l’accessibilité à la documentation, visitez le site Web Oracle Accessibility Program, à l’adresse http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Accès aux services de support Oracle

Les clients Oracle qui ont souscrit un contrat de support ont accès au support électronique via My Oracle Support. Pour plus d’informations, visitez le site http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info ou le site http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs si vous êtes malentendant.





http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs

Contents

Using This Documentation ................................................................................ 11Documentation and Feedback .......................................................................... 11Support and Training ..................................................................................... 11Contributing Authors ..................................................................................... 12Change History ............................................................................................. 12

Software Release Information ........................................................................... 15Oracle Hardware Management Pack and Oracle Solaris ........................................ 15Updates in Oracle Hardware Management Pack 2.3.x .......................................... 15

New Features ........................................................................................ 16Platform and Component Support ............................................................. 19Issues Fixed ......................................................................................... 20

Oracle Hardware Management Pack 2.3.x Documentation ..................................... 24

Installation Notes and Issues ............................................................................ 25Host-to-ILOM Interconnect Feature Might be Left in Disabled State When OracleSolaris Automated Installer is Used (18652144) .................................................. 26Oracle VM 3.2 and 3.3 Oracle HMP Installation Packages (18131790) .................... 26Oracle Solaris 10 Patches Needed for Oracle HMP (17582162 and 25246804) .......... 27Might Need to Reboot Oracle Solaris 11.1 System After Oracle HMP Installation(18231930) ................................................................................................... 27Invalid Publisher in Package Repository Causes Installation Failure on Oracle SolarisSystem (18262997) ........................................................................................ 28Disable Host-to-ILOM Interconnect Before Installing Oracle HMP on WindowsSystems (16521844) ....................................................................................... 28

To Disable the Host Interconnect ............................................................. 28Installing in Oracle Solaris Zones ..................................................................... 29Do Not Use install.bin -uninstall Command to Uninstall Oracle HardwareManagement Pack (15777347) ......................................................................... 29

5

Contents

Hardware Management Pack Installer GUI Requires libXtst.i686 for an OracleLinux 6.1 System (15766013) .......................................................................... 30Install glibc.i686 for Oracle Enterprise Linux 6 Before Running the Installer(15715967) ................................................................................................... 30Red Hat Installation Dependencies ................................................................... 31Install Path Issues .......................................................................................... 31Software Has Not Passed Windows Logo Testing Warning Message DuringHardware Management Pack Installation (15666328) ........................................... 31Latest Windows Service Pack Update Required .................................................. 31Oracle ILOM 3.0 and Windows Server 2003 R2 ................................................. 32Oracle Hardware Management Pack Uninstaller Does Not Remove hwmgmtd anditpconfig Components in Solaris 11 (20163489) ............................................... 32After Manually Installing the Hardware Management Agent (hwmgmtd) on a LinuxSystem, You Must Start the Agent Service (25429970) ......................................... 32

Known Issues and Notes for Software Release 2.3.x ........................................ 35Common Oracle Hardware Management Pack Known Issues ................................ 35

Some Utilities Run Slowly on SPARC T3 Systems (15705545) ...................... 36System Hangs During Boot Process After Reset (21962254) ......................... 36Oracle Hardware Management Pack CLI Tools Fail on Linux 5 and 6(22673965, 22599886) ............................................................................ 37Oracle Hardware Management Pack Memory Message Might Be Displayed onLinux Systems Using UEFI Mode (22667196, 22144232) ............................. 38

biosconfig Known Issues .............................................................................. 38Windows Server 2008 x64 SP2 Driver Warning (15636772) .......................... 38

firmware-check Known Issues ........................................................................ 38firmware-check Command Support Requirements ...................................... 39

fwupdate Known Issues ................................................................................. 39The Onboard Ethernet Controller for Sun Server X4-8 Cannot Be UpdatedUsing fwupdate (19790933) .................................................................... 40Automatic Power Cycle Does Not Work for fwupdate on Sun Server X4-4 andLater Platforms (18866436) ..................................................................... 41User is Prompted to Confirm an Update for a Mellanox CX3 IB Card on aSolaris System (17656671) ...................................................................... 41Remote SP Update Does Not Power Cycle the System (18048467) ................. 41fwupdate Might Hang on Solaris 10 System With Emulex and Qlogic 16GbFibre Channel or Dual 10 GbE Card Installed (18044689) ............................. 42

6 Oracle Hardware Management Pack 2.3.x Release Notes • January 2017

Contents

Firmware Update Failure With a 16Gb Fibre Channel or Dual 10 GbE Card(Emulex) on a Solaris 10 1/13 System (17551814) ...................................... 42Notes for Dual 16Gb Fibre Channel or Dual 10 GbE Card (Emulex)(17503938) ........................................................................................... 42Power Cycle Required to Update Oracle ILOM Version on Sun Fire X4170 M2Server (16562687) ................................................................................. 43fwupdate Not Supported for Flash Accelerator F40 PCIe Card on a WindowsSystems (16278659) ............................................................................... 43Emulex Fibre Channel Cards Are Not Visible on Oracle VM 3.1.1(15790684) ........................................................................................... 43Error Messages Can Be Disregarded When Updating Firmware for a EmulexFiber Channel Card (15762571) ............................................................... 44For a Sun Fire X4270 M3 Server With Oracle Enterprise Linux 6.0 a QlogicCard in Slot 2 is Not Displayed (15763607, 11177285) ................................ 44After Updating the Firmware on an Internal Expander Configured for a SunStorageTek 6Gb/s SAS PCIe HBA, Internal (SGX-SAS6-INT-Z), a Reboot isRequired (15657192) ............................................................................. 44fwupdate Cannot Downgrade Firmware (15663490) .................................... 45Cannot Update HDDs Firmware With fwupdate update Command WithWindows 2008 R2 and OEL 5.4 (15643212) .............................................. 45IPMI Initialization Causes an Error Message in the fwupdate.log File(15670576) ........................................................................................... 45fwupdate Commands on Network Controllers Might Not Show Device Detailsor Fail When Executed Right After Linux OS Loads (21210340) .................... 46fwupdate Might Fail When Updating Firmware on the Oracle Quad 10GbEthernet Adapter (21446307) ................................................................... 46fwupdate Might Fail or Take a Long Time Listing or Updating Four or MoreIntel Network Controllers (21920385) ....................................................... 47fwupdate list Might Show the Sun Dual 10GbE SFP+ PCIe 2.0 Low ProfileAdapter as "Intel Ethernet Server" (25348996) ............................................ 47

Host-to-ILOM Interconnect Issues .................................................................... 47Host-to-ILOM Interconnect Not Supported for Oracle VM 3.0.3(17256129) ........................................................................................... 48Do Not Change Hostmanaged Setting to "False" for the Host-to-ILOMInterconnect From Oracle ILOM .............................................................. 48

hwmgmtcli Known Issues ................................................................................ 48Running hwmgmtcli on a Sun Blade X6270 M2 Server Might Return ErrorMessages for Chassis Information (15801911) ............................................ 49Sun Blade X6270 M2 Shows Incorrect Chassis Data (15732926) .................... 49

7

Contents

hwmgmtd Known Issues ................................................................................... 49hwmgmtd Memory Usage Grows Over Time in Windows Systems(15752292) ........................................................................................... 50hwmgmtd Not Started When Oracle Hardware Management Pack 2.2.1 or 2.2.2is Installed on an ESX 3.5 Server (15738417) ............................................ 50hwmgmtd Service Cannot Start on Linux and Oracle Solaris With OracleHardware Management Pack 2.3.1 (20200641) ........................................... 51hwmgmtd Service Goes Into Maintenance Mode on Oracle SPARC SystemsWith Oracle Hardware Management Pack 2.3.1 (19890355) .......................... 51hwmgmtd Can Crash When Getting Information From the InfiniBand CardPlugin (22066585) ................................................................................. 51

ilomconfig Known Issues .............................................................................. 52Start New Shell for Solaris ilomconfig After Uninstalling Oracle HMPilomconfig (18277233) .......................................................................... 52DHCP Discover When Enabling Local Host-to-ILOM Interconnect on a LinuxSystem (17563392) ................................................................................ 52ilomconfig Commands Might Fail When Using ILOM 3.0.9 (15650623) ......... 53ilomconfig Host Local Credential Cache Feature Has Been Disabled(21563538) ........................................................................................... 53

ipmitool Known Issues ................................................................................. 54ipmitool Error Might Occur When SP Is Booted When SPARC T3-4 Host IsOn (15719015, 15691003) ...................................................................... 54

itpconfig Known Issues ................................................................................ 55itpconfig Error 83 "ERROR: Service Processor has conflictingconfiguration" ....................................................................................... 55

raidconfig Known Issues .............................................................................. 55User Warning: raidconfig Shows the System Boot Disk as Available(20992189) ........................................................................................... 56Sun Flash Accelerator Cards Incorrectly Identified as RAID-Capable(18519959) ........................................................................................... 56Hot Spares Not Visible on SPARC System With MegaRAID SAS Controller(16729481) ........................................................................................... 57On SLES 11 SP 1 System, Disks Might Disappear (15845681) ...................... 57RAID Volume Might Not Be Visible in Oracle ILOM on SPARC Systems(15782246) ........................................................................................... 57RAID 1 Volume With More Than Two Disks Is Not Handled Correctly(15747500) ........................................................................................... 57When Running init Task on RAID Volume clear Tasks on Disks Always Show0% Complete (15742034) ....................................................................... 58


Contents

Mounted Property for RAID Volumes is Not Visible When Using SGX-SAS6-R-REM-Z or SGX-SAS6-R-INT-Z (15666684) ........................................... 58After Creating a RAID Volume With --name Option With LSI REM, Volume'sName is Still Null (15675209) ................................................................. 58Different RAID Volumes Have the Same Device Name When OS is VMWareESX 3.5 Update 5 (15674922) ................................................................. 59RAID 10 Listed as Not Supported When Creating RAID Volume Withraidconfig (22129034) .......................................................................... 59

ubiosconfig Known Issues ............................................................................. 59ubiosconfig Cannot Connect to BMC On Systems With Oracle ILOM 3.2.6(24356013) ........................................................................................... 60

SNMP Agent Known Issues ............................................................................ 60snmpwalk of the Storage MIB Results in a Timeout or Error Message(15694465) ........................................................................................... 61SNMP Trap Issues ................................................................................. 61Sun X6250 Server Module Reports Wrong Service Processor VersionNumber ............................................................................................... 61Parent FRU Name for Sensors on Shared Components in a Blade Chassis isIncorrect (15728111, 15688172) ............................................................... 62Discrete Current Sensors Are Miscategorized on SPARC T3-Series Servers(15687547) ........................................................................................... 62SunHwMonInventoryTable Shows Incorrect Number of DIMMs (15566455) ..... 62SunHwMonDiscreteHardDriveSensorTable Incorrect Sensors ........................ 63Host Agent Might Generate Incorrect Notification (15675490) ....................... 63Windows Hardware Management Agent SNMP Walk on a Sensor Group Issue(15604854) ........................................................................................... 63sunStorageVolumeOSMountPoint Not Showing Mount Point (15666684) ......... 63Incorrect DiskOSDeviceName on SPARC T3-2 System (15668518) .................. 64Storage MIB Does Not Expose Dual Path Disks (15673745) ......................... 64

Storage Viewer Known Issues ......................................................................... 64Global Hot Spare for RAID 1 Volume Displayed as a Dedicated Hot Spare onOracle Solaris (15586295) ...................................................................... 65The max_disks Property Is Incorrect When Using Adaptec Disk Controller(SGXPCIESAS-R-INT-Z) (15584958) ...................................................... 65The write_cache_enabled Property Not Available for Adaptec Controllers(SGXPCIESAS-R-INT-Z) (15583722) ...................................................... 65

Using Oracle Hardware Management Pack With SPARC M5-32 and M6-32Servers ........................................................................................................ 65

ilomconfig (16369886) .......................................................................... 66

9

Contents

hwmgmtcli (16507559) ........................................................................... 67itpconfig (16508501, 16507898) ............................................................ 68hwmgmtd (15824059, 15824037) ............................................................... 68


Using This Documentation

This section describes product information, documentation and feedback, and a documentchange history.

■ “Documentation and Feedback” on page 11■ “Support and Training” on page 11■ “Contributing Authors” on page 12■ “Change History” on page 12

Documentation and Feedback

The following documentation is available related to the Oracle Hardware Management Pack.

Documentation Link

All Oracle products https://docs.oracle.com

Oracle Hardware Management Pack http://www.oracle.com/goto/ohmp/docs

Oracle ILOM http://www.oracle.com/goto/ilom/docs

Provide feedback on this documentation at:

http://www.oracle.com/goto/docfeedback

Support and Training

These web sites provide additional resources:

■ Support: https://support.oracle.com

Using This Documentation 11

https://docs.oracle.com

http://www.oracle.com/goto/ohmp/docs

http://www.oracle.com/goto/ilom/docs

http://www.oracle.com/goto/docfeedback

https://support.oracle.com

Contributing Authors

■ Training: http://education.oracle.com

Contributing Authors

The following authors contributed to this documentation: Cynthia Chin-Lee, Lisa Kuder, DavidMoss, Ralph Woodley, Michael Bechler.

Change History

The following changes have been made to the documentation set.

■ May 2014. Initial publication.■ June 2014. Updated Release Notes to add issue 18866436. Updated the Hardware

Management Agent overview description in the Installation Guide and Management AgentsUser's Guide. Updated the CLI Tools User's Guide to add a procedure on checking the Host-to-ILOM Interconnect connection.

■ August 2014. Added a note regarding Oracle Solaris 11.2 integration. Updated the CLITools User's Guide to make editorial improvements. Updated the Installation Guide todocument an installation issue and updated the Management Agents User's Guide to makeminor technical updates.

■ September/October 2014. Updated the Installation Guide and Release Notes to add supportfor Oracle Linux Fault Management Architecture (FMA) software.

■ November 2014. Updated the CLI Tools User's Guide and Release Notes to include NVMecontroller support and additional Oracle Hardware Management Pack 2.3.1 updates.

■ January 2015. Updated the Release Notes to include Oracle Hardware Management Pack2.3.1.1 updates (issue fixes only, no new features).

■ June 2015. Updated the Release Notes to include Oracle Hardware Management Pack2.3.2.2 updates. Updated the CLI Tools User's Guide to add error codes for the ubiosconfigcommand and added information on updating firmware on QLogic and Emulex fiberchannel controllers. Updated the Installation Guide, Management Agents User's Guide andCLI Tools User's Guide to make editorial improvements and other minor technical updates.

■ July 2015. Updated Release Notes for minor editorial change. Updated the ManagementAgents User's Guide add additional information on Sun Storage 6 Gb SAS PCIe HBA diskevents. Other minor editorial updates made to library.

■ September 2015. Updated Release Notes to include Oracle Hardware ManagementPack 2.3.3 updates. Updated the Installation Guide and Linux FMA User's Guide to addinformation on disabling EDAC. Updated CLI Tools User's Guide to describe manual powercycle requirement for remote service processor firmware updates. Updated Management


http://education.oracle.com

Change History

Agents User's Guide snmpwalk and set examples. Other minor editorial updates made tolibrary.

■ November 2015. Updated Release Notes to include Oracle Hardware Management Pack2.3.4 updates.

■ December 2015. Updated the Release Notes to add information about feature releasesand bug fixes per release. Updated the CLI Tools User's Guide to add nvmeadm errorcodes. Updated the Command Quick Reference to add note about Oracle ILOM local hostcredential cache support.

■ January 2016. Updated the Release Notes to include Oracle Hardware Management Pack2.3.5 updates. Updated the Installation Guide to document for Linux FMA installation withOracle Linux 7.

■ February 2016. Updated the Release Notes for bugs 22673965 and 22667196. Updated theInstallation Guide for bug 22673965.

■ April 2016. Updated the Release Notes to list support for X6 series systems.■ May 2016. Updated the Release Notes, Installation Guide and Management Agents User's

Guide for bug 23299302.■ July 2016. Updated the Release Notes to include Oracle Hardware Management Pack

2.3.6 updates. Updated the CLI Tools User's Guide and Command Quick Reference to addfirmware-check command and check subcommand for fwupdate. Updated the InstallationGuide for Oracle Hardware Management Pack OS dependencies.

■ July 2016. Updated Release Notes to add issue about ubiosconfig.■ August 2016. Updated the Release Notes to include Oracle Hardware Management Pack

2.3.7 updates. Updated the CLI Tools User's Guide to add additional information onupdating firmware with the fwupdate command.

■ January 2017. Updated the Release Notes to include Oracle Hardware Management Pack2.3.8 updates. Updated the License Information User Manual to provide attributions forincluded third-party software. Minor editorial updates to the Management Agents User'sGuide.

Using This Documentation 13

Software Release Information

This section contains the following information:

■ “Oracle Hardware Management Pack and Oracle Solaris” on page 15■ “Updates in Oracle Hardware Management Pack 2.3.x” on page 15■ “Oracle Hardware Management Pack 2.3.x Documentation” on page 24

Oracle Hardware Management Pack and Oracle Solaris

This documentation applies to servers running Oracle Solaris 11.1 and earlier or other supportedoperating systems.

Beginning with Oracle Solaris 11.2, Oracle Hardware Management Pack has become anintegrated component of the operating system (called Oracle Hardware Management Pack forOracle Solaris). Do not download and use other versions of Oracle Hardware Management Packthat are not specifically qualified for the Oracle Solaris 11.2 (and later) operating system.

If you have Oracle Solaris 11.1 or earlier or other operating systems, continue to use thestandalone version of Oracle Hardware Management Pack, available as a separate downloadfrom https://support.oracle.com.

Updates in Oracle Hardware Management Pack 2.3.x

This section describes changes in 2.3.x releases.

■ “New Features” on page 16■ “Platform and Component Support” on page 19■ “Issues Fixed” on page 20

Software Release Information 15

https://support.oracle.com


New Features

The following new features are part of the 2.3.x releases.

Release 2.3.8 Features

■ Updated software infrastructure for optimal performance, security, and stability forcurrently supported Windows operating systems. See “Platform and ComponentSupport” on page 19

Note - This is the last release of Oracle Hardware Management Pack to includesupport for the Windows operating system.


■ Added support for the Oracle Quad 10 Gb or Dual 40 Gb Ethernet Adapter. See “Platformand Component Support” on page 19

■ Added the firmware-check command to check that the system firmware is at the minimumrequired version for updates and security. This command can be run manually or runs bydefault at system boot. For this release, firmware-check is supported on systems runningOracle Linux 6 or 7.

■ Added the check subcommand to the fwupdate command to check that the system firmwareis at the minimum required version for updates and security. For this release, the checksubcommand is supported on systems running Oracle Linux 6 or 7.

■ Added sysfw target for both SPARC and x86 systems for the fwupdate command (thoughsp_bios is still supported for backwards compatibility).

■ Added --vendor_specific option to nvmeadm list command to display vendorinformation for the Oracle Flash Accelerator F160 and F320 PCIe Cards and the 1.6 TB and3.2 TB NVMe SSDs.

■ Added support to nvmeadm getlog command to output crashdump and memory dump filesfor the Oracle Flash Accelerator F320 PCIe Card and 3.2 TB NVMe SSD.


■ Support added for X6 series platforms and components. See “Platform and ComponentSupport” on page 19.



■ Added Oracle Storage 12 Gb/s SAS PCIe RAID HBA backup battery status to raidconfiglist output (21077324)


The following features were added or removed in Oracle Hardware Management Pack 2.3.3:

■ The ilomconfig create local host credential cache feature is no longer supported. Youcan still use ilomconfig to delete a previously saved local host credential cache. Foradditional details see “ilomconfig Host Local Credential Cache Feature Has Been Disabled(21563538)” on page 53.

■ The fwupdate command now additionally supports updating the firmware of supportedIntel-based Ethernet network cards (add-in cards or onboard controllers) from supportedversions of Microsoft Windows Server OS.

Release 2.3.2.2 Features

The following new feature was added in Oracle Hardware Management Pack 2.3.2.2:

■ The fwupdate tool does not support updating firmware on Intel-based Ethernet networkinterface cards (add-in cards or onboard controllers) in systems running any versionMicrosoft Windows or Oracle VM.To update Intel-based Ethernet network interface card firmware on systems runningMicrosoft Windows or Oracle VM, use the optional Oracle System Assistant managementtool included with your system. Otherwise, network add-in cards can be moved to an Oracleserver running a supported version of Linux with Oracle Hardware Management Pack orOracle System Assistant installed to perform the update.

■ Enhanced diagnostic features were added to collect more data from the Sun Storage 6Gb SAS PCIe HBA, Internal (SGX-SAS6-INT-Z). This includes various disk errors andSMART events generated for disks in a RAID in the Solaris and Linux environments. Theseevents help better identify suspect disks in a RAID. For more information, see “UsingOracle Hardware Management Pack to Monitor Disk Diagnostic Events” in Oracle ServerManagement Agents User’s Guide.

■ For new Oracle Solaris or Linux installations of Oracle Hardware Management Packbeginning with version 2.3.2.2, the sun-ssm directory name that used to be used in thepath for components has been changed to ssm. For upgrades of older versions of OracleHardware Management Pack before version 2.3.2.2, pre-existing sun-ssm directories areretained during the upgrade for compatibility.


http://www.oracle.com/pls/topic/lookup?ctx=E52095-01&id=OHMIIgjabc





The following is a list of new features in Oracle Hardware Management Pack 2.3.1:

■ The nvmeadm tool has been added to configure NVMe controllers. For more information, see“Using nvmeadm to Configure an NVM Express Device” in Oracle Server CLI Tools User’sGuide.

■ New targets have been added to the fwupdate update command for updating NVMe andNIC controllers. For more information, see “Updating Component Firmware” in OracleServer CLI Tools User’s Guide.

■ For a system with an Oracle Storage 12 Gb/s SAS PCIe RAID HBA, you can enable JBODmode so the underlying operating system can access a disk directly without creating a RAIDvolume first. For more information, see “Enable or Disable JBOD Mode” in Oracle ServerCLI Tools User’s Guide.

Note - JBOD mode support is also included in Oracle Hardware Management Pack 2.3.0,but the hardware was not available at the initial Oracle Hardware Management Pack 2.3.0release.


The following is a list of new features in Oracle Management Pack 2.3.0:

■ Support added for X5 series platforms and components. See “Platform and ComponentSupport” on page 19.

■ Oracle Linux Fault Management Architecture (FMA) is available for supported serversrunning Oracle Linux 6.5 or later. Oracle Linux FMA is a host-based command-lineinterface that allows you to view and act on faults from the host operating system usingfault management commands similar to those available from the Oracle ILOM FaultManagement shell.To find out if your server is supported to use Oracle Linux FMA, refer to the server'sdocumentation or the Oracle Hardware Management Pack support matrix at: http://www.oracle.com/goto/ohmp.

■ A watchdog agent has been added. This provides the ability to perform pre-set actions ifOracle ILOM or the host OS become unresponsive on a Linux system.■ For more information on the Oracle HMP watchdog agent, refer to “Configuring the

HMP Watchdog Agent” in Oracle Server Management Agents User’s Guide.■ For more information on the ilomconfig targets that can configure the Oracle HMP

watchdog agent, refer to “Managing ILOM and Host Watchdog” in Oracle Server CLITools User’s Guide.


http://www.oracle.com/pls/topic/lookup?ctx=E52095-01&id=OHMIJgooju

http://www.oracle.com/pls/topic/lookup?ctx=E52095-01&id=OHMIJgooju

http://www.oracle.com/pls/topic/lookup?ctx=E52095-01&id=OHMIJgltkm

http://www.oracle.com/pls/topic/lookup?ctx=E52095-01&id=OHMIJgltkm

http://www.oracle.com/pls/topic/lookup?ctx=E52095-01&id=OHMIJgoogy

http://www.oracle.com/pls/topic/lookup?ctx=E52095-01&id=OHMIJgoogy

http://www.oracle.com/goto/ohmp


http://www.oracle.com/pls/topic/lookup?ctx=E52095-01&id=OHMIIgnzkt

http://www.oracle.com/pls/topic/lookup?ctx=E52095-01&id=OHMIIgnzkt

http://www.oracle.com/pls/topic/lookup?ctx=E52095-01&id=OHMIJgomym

http://www.oracle.com/pls/topic/lookup?ctx=E52095-01&id=OHMIJgomym


■ The fast_updates_enabled feature is available for hwmgmtd.conf. This enables youto increase the frequency of drive temperature sensor polling for more accurate diskmonitoring.

■ The Hardware Management Agent on a SPARC server running Oracle VM can be installedto logical domains. This enables you to monitor storage devices found in the logical domainusing the Hardware Management Agent in a primary domain.

■ SUN-HW-MONITORING-MIB, part of the Oracle Hardware Management Pack SNMPplugins, has been extended to include new sensor types found on recent Oracle servers.

■ The itpconfig tool has been updated to forward event traps based on the ILOM-SYSTEM-MIB. You can use Oracle ILOM web interface to download MIBs (under ILOMAdministration > Management Access > SNMP) to confirm that your server supports thisMIB.

■ System event log (SEL) monitoring is disabled in the hardware agent (hwmgmtd). Use one ofthe following tools to access the SEL and fault-based traps:■ Use the ipmievd utility to log IPMI SEL events from Oracle ILOM to syslog.

ipmievd is a binary that is part of the ipmitool package in Oracle HardwareManagement Pack. See the ipmievd.8 man page for more information.

■ Use itpconfig (the Oracle ILOM trap proxy) to forward the SNMP traps directly tothe host from Oracle ILOM using the Host-to-ILOM interconnect feature. For moreinformation on configuring Oracle ILOM to send SNMP traps, refer to the Oracle ILOMdocumentation at http://www.oracle.com/goto/ilom/docs. For more informationon using itpconfig, refer to “Using the itpconfig Tool” in Oracle Server ManagementAgents User’s Guide.

Note - FRU (Field Replaceable Unit) add/remove traps and storage device traps are stillhandled by the management agent (hwmgmtd). The management agent must be installed andrunning to receive these traps.

Platform and Component SupportFor information on support for new platforms and components per Oracle HardwareManagement Pack 2.3 release, refer to the system management support matrix web page. Newplatforms and components are added periodically. As they are added, a release-specific supportmatrix link is added to the main page which includes a superset of all products and componentssupported in the release.

A link to the support matrices for all versions is available at:



http://www.oracle.com/goto/ilom/docs

http://www.oracle.com/pls/topic/lookup?ctx=E52095-01&id=OHMIIgmrio

http://www.oracle.com/pls/topic/lookup?ctx=E52095-01&id=OHMIIgmrio



Issues Fixed

The following are issues that were fixed in the Oracle Hardware Management Pack 2.3.xreleases:

Issues Fixed in Release 2.3.8

■ hwmgmtd agent latency issues on Linux systems with Intel Ethernet controllers (24750793)


■ fwupdate cannot update SPARC S7 LAN-On-Motherboard controller firmware (21616063)■ ubiosconfig cannot connect to BMC on systems with Oracle ILOM 3.2.6 (24356013)


■ ilomconfig list system-summary does not include BIOS version for X5-8 (22875818)■ fwupdate does not update Flash Accelerator F320 PCIe Card on Linux (23174970)■ raidconfig add disk command outputs wrong return code (23214158)■ raidconfig start task command outputs wrong return code (23214036)■ On systems running SLES 11, using raidconfig with the --write-cache enabled option

on a system whose RAID HBA does not have a battery backup shows successful when itshould not (23306392)

■ ilomconfig says Host-to-ILOM interconnect enabled successfully even when hostmanagedsetting in Oracle ILOM is set to false (23321066)

■ ilomconfig dumps core SIGSEGV (Segmentation Fault) during system boot (23226087)■ fwupdate fails to identify the Oracle Quad 10 Gb or Dual 40 Gb Ethernet Adapter

(23230293)■ Inappropriate error when trying to create a user account that already exists using

ilomconfig create user command (22739057)■ fwupdate cannot be performed through local Host-to-ILOM interconnect if hostmanaged

attribute in Oracle ILOM is not set to "true" (22822620)■ Hardware Management Agent log entry starts with raidconfig version information instead

of hwmgmtd (22674966)■ Oracle Hardware Management Pack fishwrap XML has duplicate sun-ids in multipath

configuration (22456828)



■ System panic can occur when running multiple nvmeadm commands at once (22301202)■ hwmgmtcli list all command might show "broken pipe" error on some SPARC systems

running Oracle Solaris 10 (23504711)■ hwmgmtcli list storage --details command might show false disk failure with no

"storage health" details on systems running Oracle ILOM 3.0 (23555649)


■ Core file is generated after modifying SP Interconnect IP Address (22012637)■ After disconnecting and reconnecting a storage chassis to the system, the hwmgmtd agent

might crash (21903729)■ fwupdate list controller command displays duplicate Emulex controller (22155186)■ Description of -H option in fwupdate(1m) man page is not correct (21889911)■ fwupdate tool does not list LAN-on-Motherboard information on Oracle's Sun Server X3-

2L and X4-2L systems running Linux (22333747)


The following issues are fixed in Oracle Hardware Management Pack 2.3.4:

■ Oracle Hardware Management Pack CLI commands do not work on some server platformswith Oracle Hardware Management Pack 2.3.3 (22098019). This issue is limited to serverplatforms running a Linux OS in UEFI boot mode.

■ Installing hmp-zoningcli did not work correctly (22145208).



■ Remote SP update does not power cycle the system (18048467). Firmware updates overthe network to a remote system's service processor using the fwupdate command nowsupport automatic reboot. For x86 systems, the --silent-reboot option is also supported.In previous versions, a manual power cycle was required after updating a remote SP.

■ System hangs during boot process after reset (21962254)■ hwmgmtcli output does not display certain disk errors on systems with Oracle ILOM 3.1.x

or earlier (21482027). In addition to already captured errors, such as disk over temperature,self test failure, and predictive failure, hwmgmtcli will now include disk recovered errors,bad device faults, media errors, device errors, and transport errors.



■ Duplicated disk events should be integrated to one in event log (21495102)■ Network bonding configuration of multiple Ethernet cards can cause management agent to

hang ILOM (21439951)■ fwupdate tries to get local ILOM credentials when running with -H option (21086520)■ Remote ILOM update: the host, where command is launched, is rebooted (18048467)■ Unexpected "%s" characters in component names in sunStorageMIB query output

(21657443)■ fwupdate terminates with alarm clock message (21330923)■ ilomconfig reset hostprofile does not remove all previous host profile updates (21207930)■ Change nvmeadm to improve error messages and controller error case behavior (21093595)■ User warning: raidconfig shows the system boot disk as available (20992189)■ When creating a RAID volume, cachemode NRWTC is configured by default (20988172)■ RAID cache setting changes in raidconfig manpage (21098717)■ ubiosconfig reports inaccurate error messages for BIOS upgrade failures (21155720)■ Memory leak in HMP agent (21151019)

Issues Fixed in Release 2.3.2.2

The following issues are fixed in Oracle Hardware Management Pack 2.3.2.2:

■ Fix incorrect hwmgmtd log message when child process is killed (20905150)■ Some nvmeadm message output on some commands are not clear (20898666)■ nvmeadm getlog does not report correct value for available error logs (20884169)■ When using raidconfig to import the configuration of RAIDs with subdisks, if multiple

RAIDs on a controller have been modified, only the modified properties on first RAID willbe imported (16494064)

■ Need to add auto powercycle support to fwupdate for SPARC systems (15775719)■ Use of vendor tool quacli by hwmgmtd causing FC storage links to go offline/online

(20950982)■ nvmeadm online/offline options (only supported on Solaris 11.2 and above) are not identified

as invalid subcommands on Linux/Windows (20916889)■ nvmeadm format and import online device error message should include device name

(20923927)■ HMP Installer for Linux does not perform rpm dependancy check for Linux FMA

component support (20956762)■ nvmeadm import/export subcommand functionality is not properly documented (20884222)■ ilomconfig reports benign "Unable to get mutex" log message (20761474)



■ HMP 2.3.1 creates hwmgmtd.log under root (/) instead of /var/opt/sun-ssm/ (20269424)■ fwupdate fails with "ERROR: Platform not supported" message (19207713)■ Display controller serial number if available (20515989)

Issues Fixed in Release 2.3.1.1

The following issues are fixed in Oracle Hardware Management Pack 2.3.1.1:

■ hwmgmtd service cannot start on Linux and Oracle Solaris with Oracle HardwareManagement Pack 2.3.1 (20200641, 20266980)

■ hwmgmtd service goes into maintenance mode on Oracle SPARC systems with OracleHardware Management Pack 2.3.1 (19890355)

■ Oracle Hardware Management Pack uninstaller does not remove hwmgmtd and itpconfigcomponents in Oracle Solaris 11 (20163489)



■ Error message with fwupdate list all command (18707048)■ Not all package dependencies are caught by HMP installer (19561983)■ HMP cannot automatically configure USB based ILOM interconnect in Oracle Linux 7

(19357806)■ Missing add_on_disks and add_on_disk_size properties in hwmgtmcli report (19205811)■ hwMonMib and storageMib data not provided in Oracle Linux 7 (19603933)■ fwupdate does not correctly identify multi-path NVMe disks (19603409)



■ Working directory must be writeable to run commands (16538678)■ Installing Oracle Hardware Management Pack on Oracle Solaris 11 system with zones

(16970964)■ Sun Flash Accelerator F20 PCIe Card FDOMs not visible in /STORAGE (15645766)■ Some SNMP traps available in Oracle ILOM are not generated by Hardware Management

Pack (15686011)■ sunHwMonFruStatus does not reflect the fault state of a component (15687574)


Oracle Hardware Management Pack 2.3.x Documentation

■ Updating Oracle ILOM on a Windows system with fwupdate command fails (17576286)■ Firmware versions do not display with 16Gb Fibre Channel or Dual 10 GbE Card (Emulex)

(17037795)■ raidconfig hangs when disk is removed from SPARC server (15826569)■ Segmentation fault in system with more than 16 of the same type of LSI Storage Controller

(16618057)■ hwmgmtd cannot start successfully on system with Red Hat Linux 6.4 (16975947)■ fwupdate only upgrades firmware for the first port on a StorageTek 8 Gb FC PCI-Express

Dual Port HBA (Emulex) (15811623)■ If required hmptmp directory is unavailable due to being removed or permissions/ownship,

hwmgmtd reports no relevant storage errors/data to Oracle ILOM with sunhwmonmib(18770002, 18764373)

Oracle Hardware Management Pack 2.3.x Documentation

Complete documentation for Hardware Management Pack can be found on the web at:




Installation Notes and Issues

The following items affect Oracle Hardware Management Pack installation.

Issue Workaround

“Host-to-ILOM Interconnect Feature Might be Left in Disabled State When Oracle SolarisAutomated Installer is Used (18652144)” on page 26

Yes

“Oracle VM 3.2 and 3.3 Oracle HMP Installation Packages (18131790)” on page 26 No

“Oracle Solaris 10 Patches Needed for Oracle HMP (17582162 and25246804)” on page 27

No

“Might Need to Reboot Oracle Solaris 11.1 System After Oracle HMP Installation(18231930)” on page 27

Yes

“Invalid Publisher in Package Repository Causes Installation Failure on Oracle SolarisSystem (18262997)” on page 28

Yes

“Disable Host-to-ILOM Interconnect Before Installing Oracle HMP on Windows Systems(16521844)” on page 28

No

“Installing in Oracle Solaris Zones” on page 29 No

“Do Not Use install.bin -uninstall Command to Uninstall Oracle HardwareManagement Pack (15777347)” on page 29

Yes

“Hardware Management Pack Installer GUI Requires libXtst.i686 for an Oracle Linux6.1 System (15766013)” on page 30

Yes

“Install glibc.i686 for Oracle Enterprise Linux 6 Before Running the Installer(15715967)” on page 30

No

“Red Hat Installation Dependencies” on page 31 Yes

“Install Path Issues” on page 31 No

“Software Has Not Passed Windows Logo Testing Warning Message During HardwareManagement Pack Installation (15666328)” on page 31

No

“Latest Windows Service Pack Update Required” on page 31 No

“Oracle ILOM 3.0 and Windows Server 2003 R2” on page 32 No

“Oracle Hardware Management Pack Uninstaller Does Not Remove hwmgmtd anditpconfig Components in Solaris 11 (20163489)” on page 32

Yes

“After Manually Installing the Hardware Management Agent (hwmgmtd) on a LinuxSystem, You Must Start the Agent Service (25429970)” on page 32

Yes

Installation Notes and Issues 25

Host-to-ILOM Interconnect Feature Might be Left in Disabled State When Oracle Solaris Automated Installer is Used (18652144)

Host-to-ILOM Interconnect Feature Might be Left inDisabled State When Oracle Solaris Automated Installer isUsed (18652144)

When using the Oracle Solaris Automated Installer (introduced with Oracle Solaris 11) todeploy software on a server, the server's Host-to-ILOM interconnect feature (required formany Oracle Hardware Management Pack features) might be left in a disabled state after theAutomated Installer performs a reboot during installation.

To determine if your server was set up by the Automated Installer, enter the followingcommand:

# netadm list | grep ncp

ncp Automatic online <-- Automated Installer was used

ncp DefaultFixed disabled

Workaround

If this happens, reboot the server a second time after the installation has completed.

Oracle VM 3.2 and 3.3 Oracle HMP Installation Packages(18131790)

An Oracle Hardware Management Pack install package for Oracle VM 3.3 or later is nowavailable.

The package name is oracle-hmp-2.3.0.0-ovm3.3-x86_64.zip. This package hasdependencies such as policycoreutils and policycoreutils-python removed.

For Oracle VM 3.2 or earlier, use the oracle-hmp-2.3.0.0-oel5-x86_64.zip package.

The oracle-hmp-2.3.0.0-ovm3-x86_64.zip file has been removed from Oracle HardwareManagement Pack 2.3 since the oracle-hmp-2.3.0.0-oel5-x86_64.zip packages can be usedinstead.


Oracle Solaris 10 Patches Needed for Oracle HMP (17582162 and 25246804)

Oracle Solaris 10 Patches Needed for Oracle HMP(17582162 and 25246804)

Oracle recommends that you install the latest patches for your system to ensure security andstability. If not, and are running Oracle Hardware Management Pack on a Oracle Solaris10 system, install the following patches in order to avoid issues with accessing storageinformation:

For bug 17582162 (management agent stops reporting mass storage information to OracleILOM), these are the minimum patches required:

■ For SPARC systems: 148421-02■ For X86 Systems: 148422-02

For bug 25246804 (error output: ld.so.1: ilomconfig: fatal: libcrypto.so.1.0.0: openfailed: No such file or directory), these are the minimum patches required:

■ For SPARC systems: 148071-19, 151912-02■ For X86 Systems: 148072-19, 151913-02

Might Need to Reboot Oracle Solaris 11.1 System AfterOracle HMP Installation (18231930)

You might see a message similar to the following during the installation of Oracle HardwareManagement Pack on a Oracle Solaris 11.1 system:

Host-to-ILOM Interconnect could not be enabled.

-----------------------------------------------

.

ipadm: cannot create interface net2: Operation failed

ipadm: cannot create address: No such interface

ERROR: ILOM not reachable over internal LAN

.

Interface name is net2

net2 should be up

Workaround

In order to enable the Host-to-ILOM interconnect, reboot your system.


Invalid Publisher in Package Repository Causes Installation Failure on Oracle Solaris System (18262997)

Invalid Publisher in Package Repository Causes InstallationFailure on Oracle Solaris System (18262997)

If a you have an invalid publisher configured in the 'pkg' system on a Oracle Solaris system, theinstallation of Oracle Hardware Management Pack will encounter multiple errors and none ofthe tools will be correctly installed. The following is an example error message:

Custom Action: InstallSolaris11

Status: ERROR

Additional Notes: ERROR - class

InstallSolaris11 NonfatalInstallException pkg: 1/2 catalogs successfully

updated:

Unable to contact valid package repository

Encountered the following error(s):

Unable to contact any configured publishers.

This is likely a network configuration problem.

file protocol error: code: 22 reason: The path '/mnt/repo' does not contain a

valid package repository.

Repository URL: 'file:///mnt/repo'. (happened 2 times)

Workaround

If you encounter this error message:

1. Remove the publisher associated with the Repository URL shown in the error message.2. Uninstall Oracle Hardware Management Pack.3. Reinstall Oracle Hardware Management Pack.

Disable Host-to-ILOM Interconnect Before Installing OracleHMP on Windows Systems (16521844)

When installing Oracle Hardware Management Pack on a Windows system, the Host-to-ILOMInterconnect needs to be disabled from Oracle ILOM prior to the Host-to-ILOM installation orthe configuration might fail.

To Disable the Host Interconnect1. Log into the Oracle ILOM web interface.2. Select ILOM Administration -> Connectivity .


Installing in Oracle Solaris Zones

3. In the Local Host Interconnect section, select the Configure link .4. In the Configure USB Ethernet Parameters dialog:

a. Select True in the Host Managed field.b. Deselect Enabled in the State field.

Note - If State is set to enabled, you will need to deselect the Host Managed box, deselectthe Enabled box and then select Host Manage True box.

Installing in Oracle Solaris Zones

The Oracle Hardware Management Pack packages will install in all Oracle Solaris zones.However, the Oracle Hardware Management Pack utilities in both Oracle Solaris 10 and 11have limited or no functionality in non-global zones.

The following Oracle Hardware Management Pack utilities will be non-functional in the non-global zone:

■ biosconfig

■ fwupdate

■ raidconfig

■ hwmgmtcli

■ hwmgmtd

■ Management Agent

These utilities will only function if the LAN interface is used in the non-global zone:

■ ipmitool

■ ilomconfig

■ ubiosconfig

Do Not Use install.bin -uninstall Command to UninstallOracle Hardware Management Pack (15777347)

The install.bin -uninstall command launches the Hardware Management Pack Installer,not the Uninstaller.


Hardware Management Pack Installer GUI Requires libXtst.i686 for an Oracle Linux 6.1 System (15766013)

Workaround

Use the following commands to launch the Uninstaller:

■ For Oracle Solaris OS or Linux systems:

/opt/ssm_directory/setup/uninstall

Where ssm_directory is either sun-ssm or ssm, depending on your version of OracleHardware Management Pack.

■ For Windows systems:

C:\Program Files (x86)\Oracle\Oracle Hardware Management Pack\setup

\uninstall.exe

Hardware Management Pack Installer GUI Requires libXtst.i686 for an Oracle Linux 6.1 System (15766013)

If you want to use the Hardware Management Pack Installer GUI on a system running OracleLinux 6.1, you need to run the following command to install libXtst.i686:

yum install libXtst.i686

Workaround

Use the console installation mode instead of GUI mode.

Install glibc.i686 for Oracle Enterprise Linux 6 BeforeRunning the Installer (15715967)

Before installing Hardware Management Pack 2.2.1, 2.2.2, or 2.2.3 on a system running OracleEnterprise Linux 6, you must install glibc.i686.

To install glibc.i686, run the following command:

yum install glibc.i686


Red Hat Installation Dependencies

Red Hat Installation Dependencies

During an automatic installation on Red Hat Enterprise Linux, the Net-SNMP service is notautomatically started. The Net-SNMP service must be restarted before running the HardwareManagement Agent.

Workaround

To restart the service, run the following command:

service snmpd restart

Install Path Issues

■ On all operating systems, if you modify the installation path of the Hardware ManagementAgent, you must ensure that the path is no longer than 70 characters, does not contain anywhite spaces, and does not contain any of these characters: ? - _ . /

■ When creating a response file for a silent installation, you must use an absolute path tocreate the response file (described in issue 6982588) . For example: ./install.bin -i GUI -r /tmp/response.txt

Software Has Not Passed Windows Logo Testing WarningMessage During Hardware Management Pack Installation(15666328)

When installing the LAN-Over-USB driver on a Windows system, a message warns that thesoftware has not passed Windows logo testing. This does not affect operation of the software,and it is safe to continue with the installation.

Latest Windows Service Pack Update Required

To avoid errors during Oracle Hardware Management Pack installation, install the latestsecurity updates from Microsoft for the target server. Under some circumstances, an old versionof the file vcredist_x86.exe might cause an error during Hardware Management Agentinstallation.


Oracle ILOM 3.0 and Windows Server 2003 R2

Oracle ILOM 3.0 and Windows Server 2003 R2

Microsoft hotfix http://support.microsoft.com/kb/982915 must be installed on WindowsServer 2003 R2 in order for Hardware Management Agent to work correctly with Oracle ILOM3.0.

Oracle Hardware Management Pack Uninstaller Does NotRemove hwmgmtd and itpconfig Components in Solaris 11(20163489)

This issue is fixed in Oracle Hardware Management Pack 2.3.1.1.

In Oracle Hardware Management Pack 2.3.1, the uninstaller program does not remove thehwmgmtd and itpconfig components in the Solaris OS 11.0 and 11.1 environments. To uninstallthese packages, you must remove them manually.

Use the following commands to manually remove these packages:

# pkg uninstall system/management/hmp/hmp-hwmgmt

# pkg uninstall system/management/hmp/hmp-tools

# pkg uninstall system/management/hmp/hmp-libs

After Manually Installing the Hardware Management Agent(hwmgmtd) on a Linux System, You Must Start the AgentService (25429970)

On a Linux system, if you opt to manually install the Oracle Hardware Management Agentcomponent using a tool such as rpm (not using the Oracle Hardware Management Packinstaller), you will need to start the agent service after installation. Once started, the agent willperform as intended. When installing Oracle Hardware Management Pack using the installer,you are prompted to start any required services.

Use one of the following commands to manually start the Hardware Management Agent:

■ For systems running Oracle Linux or Red Hat Linux versions 4, 5 and 6, and SUSE Linuxversions 10 and 11:


http://support.microsoft.com/kb/982915

After Manually Installing the Hardware Management Agent (hwmgmtd) on a Linux System, You Must Start the Agent Service(25429970)

# service hwmgmtd start■ For systems running Oracle Linux or Red Hat Linux version 7, and SUSE Linux version 12:

# systemctl start hwmgmtd


Known Issues and Notes for Software Release2.3.x

This section describes the known issues for the current version of Hardware Management Pack.Where appropriate, issue reference numbers are provided. Use these numbers in any contactwith Oracle support.

The following topics are covered in this section:

■ “Common Oracle Hardware Management Pack Known Issues” on page 35■ “biosconfig Known Issues ” on page 38■ “firmware-check Known Issues” on page 38■ “fwupdate Known Issues” on page 39■ “Host-to-ILOM Interconnect Issues” on page 47■ “hwmgmtcli Known Issues” on page 48■ “hwmgmtd Known Issues” on page 49■ “ilomconfig Known Issues” on page 52■ “ipmitool Known Issues” on page 54■ “itpconfig Known Issues” on page 55■ “raidconfig Known Issues” on page 55■ “ubiosconfig Known Issues” on page 59■ “SNMP Agent Known Issues” on page 60■ “Storage Viewer Known Issues” on page 64■ “Using Oracle Hardware Management Pack With SPARC M5-32 and M6-32

Servers” on page 65

Common Oracle Hardware Management Pack Known Issues

The issues shown in the following table are related to all Hardware Management Pack tools.

Known Issues and Notes for Software Release 2.3.x 35


Issue Workaround

“Some Utilities Run Slowly on SPARC T3 Systems (15705545)” on page 36 Yes

“System Hangs During Boot Process After Reset (21962254)” on page 36 Yes

“Oracle Hardware Management Pack CLI Tools Fail on Linux 5 and 6 (22673965,22599886)” on page 37

Yes

“Oracle Hardware Management Pack Memory Message Might Be Displayed on LinuxSystems Using UEFI Mode (22667196, 22144232)” on page 38

N/A

Some Utilities Run Slowly on SPARC T3 Systems(15705545)

The hwmgmtd utility might not provide accurate results when run on a SPARC T3 system.

Some other Oracle Hardware Management Pack utilities (such as raidconfig and hwmgmtcli)can also run very slowly on a SPARC T3 system.

These problems are due to a Oracle Solaris issue documented in issue 6937169.

Workaround

1. Disable the affected utility.2. Issue the following commands:

Note - Make sure that you read the mdb documentation carefully before issuing thesecommands.

# mdb -kw

> ddi_aliases_present/W 0

3. Re-enable the utility.

System Hangs During Boot Process After Reset(21962254)

Fixed in Oracle Hardware Management Pack 2.3.3.

In rare instances on Oracle x86 systems running Linux, the system might hang during theBIOS boot process after being reset. A BIOS error might also be displayed during boot, such



as "AF OO". This issue can sometimes occur when the Oracle Hardware Management Packmanagement agent (hwmgmtd) is running and the Ethernet interface has been configured fornetwork bonding.

This issue has been seen with the Oracle Server X5-4 in an Exalytic product configuration.

Workaround

If you encounter this issue, disable the management agent (hwmgmtd) and reboot the system.

1. From the Linux host when logged in as administrator, enter the following commands to stopand disable the management agent:

# /sbin/chkconfig hwmgmtd off

# /sbin/service hwmgmtd stop

2. Use ipmitool to reset the service processor by entering the command:

# ipmitool bmc reset cold

3. Reboot the system by entering the command:

# reboot

The system should reboot normally.

Oracle Hardware Management Pack CLI Tools Failon Linux 5 and 6 (22673965, 22599886)

Oracle Hardware Management Pack server CLI tools might fail on systems running Linux 5 or6 with older versions of the Linux kernel. This issue is seen with Oracle Hardware ManagementPack versions 2.3.3.0 through 2.3.5.0.

For example, when running a command such as fwupdate -V to obtain the version of fwupdatetool, you will see an error in the command output, the command will fail, and the followingmessage will be seen in syslog:

fwupdate version 2.3.5.0 r19425

Thu Feb 4 07:20:02 2016:(CLI) Fishwrap version 4.1.0

Thu Feb 4 07:20:02 2016:(CLI) Host Profile update failed.

Workaround

If you encounter this issue, update your Linux kernel to version 2.6.32 or later.


biosconfig Known Issues

Oracle Hardware Management Pack MemoryMessage Might Be Displayed on Linux SystemsUsing UEFI Mode (22667196, 22144232)

On Linux systems running Oracle Hardware Management Pack utilities and agents under UEFImode, a message similar to the following might appear in the system logs:

Program fwupdate tried to access /dev/mem between f0000->101000.

This message does not cause any functional issues and can be safely ignored.

biosconfig Known Issues

The issues shown in the following table are related to the biosconfig tool.

Issue Workaround

“Windows Server 2008 x64 SP2 Driver Warning (15636772)” on page 38 Yes

Windows Server 2008 x64 SP2 Driver Warning(15636772)

When using biosconfig on Windows Server 2008 x64 SP2, you might encounter an unsigneddriver warning. This warning can be safely ignored.

firmware-check Known Issues

The issues shown in the following table are related to the firmware-check tool.

Issue Workaround

“firmware-check Command Support Requirements” on page 39 No


fwupdate Known Issues

firmware-check Command Support Requirements

firmware-check is not supported for use with systems that have a version of Oracle ILOMolder than 3.0.2.

firmware-check should only be run on domains that have direct access to ILOM/sysfwversions, such as DOM0 and Control Domains. It cannot be run in non-global or Kernel zones,or in virtual environments.


The issues shown in the following table are related to the fwupdate tool.

Issue Workaround

“The Onboard Ethernet Controller for Sun Server X4-8 Cannot Be Updated Using fwupdate(19790933)” on page 40

Yes

“Automatic Power Cycle Does Not Work for fwupdate on Sun Server X4-4 and LaterPlatforms (18866436)” on page 41

No

“User is Prompted to Confirm an Update for a Mellanox CX3 IB Card on a Solaris System(17656671)” on page 41

Yes

“Remote SP Update Does Not Power Cycle the System (18048467)” on page 41 Yes

“fwupdate Might Hang on Solaris 10 System With Emulex and Qlogic 16Gb Fibre Channelor Dual 10 GbE Card Installed (18044689)” on page 42

Yes

“Firmware Update Failure With a 16Gb Fibre Channel or Dual 10 GbE Card (Emulex) on aSolaris 10 1/13 System (17551814)” on page 42

No

“Notes for Dual 16Gb Fibre Channel or Dual 10 GbE Card (Emulex)(17503938)” on page 42

No

“Power Cycle Required to Update Oracle ILOM Version on Sun Fire X4170 M2 Server(16562687)” on page 43

No

“fwupdate Not Supported for Flash Accelerator F40 PCIe Card on a Windows Systems(16278659)” on page 43

No

“Emulex Fibre Channel Cards Are Not Visible on Oracle VM 3.1.1(15790684)” on page 43

No

“Error Messages Can Be Disregarded When Updating Firmware for a Emulex FiberChannel Card (15762571)” on page 44

No

“For a Sun Fire X4270 M3 Server With Oracle Enterprise Linux 6.0 a Qlogic Card in Slot 2is Not Displayed (15763607, 11177285)” on page 44

Yes

“After Updating the Firmware on an Internal Expander Configured for a SunStorageTek 6Gb/s SAS PCIe HBA, Internal (SGX-SAS6-INT-Z), a Reboot is Required(15657192)” on page 44

Yes



Issue Workaround

“fwupdate Cannot Downgrade Firmware (15663490)” on page 45 Yes

“Cannot Update HDDs Firmware With fwupdate update Command With Windows 2008R2 and OEL 5.4 (15643212)” on page 45

No

“IPMI Initialization Causes an Error Message in the fwupdate.log File(15670576)” on page 45

No

“fwupdate Commands on Network Controllers Might Not Show Device Details or FailWhen Executed Right After Linux OS Loads (21210340)” on page 46

Yes

“fwupdate Might Fail When Updating Firmware on the Oracle Quad 10Gb Ethernet Adapter(21446307)” on page 46

Yes

“fwupdate Might Fail or Take a Long Time Listing or Updating Four or More Intel NetworkControllers (21920385)” on page 47

Yes

“fwupdate list Might Show the Sun Dual 10GbE SFP+ PCIe 2.0 Low Profile Adapter as"Intel Ethernet Server" (25348996)” on page 47

Yes

The Onboard Ethernet Controller for Sun ServerX4-8 Cannot Be Updated Using fwupdate(19790933)

This issue is fixed in Oracle Hardware Management Pack 2.3.2.2 (see note below).

The fwupdate nic-controller-firmware command that was added in Oracle HardwareManagement Pack 2.3.1 cannot currently be used to update the Sun Server X4-8 onboardEthernet controller.

However, the Ethernet controllers on installed PCIe network interface cards (NICs) can beupdated with this command.

Workaround

Use a different method, such as Oracle System Assistant, to update the Sun Server X4-8onboard Ethernet controller.

Note - If you are using Oracle Hardware Management Pack 2.3.2.2, the fwupdate commandcannot be used to update Ethernet controllers on systems with Microsoft Windows or OracleVM. Use Oracle System Assistant to update Ethernet controllers if your system has one of theseoperating systems.

If you are using Oracle Hardware Management Pack 2.3.3 or later, you can also use fwupdateon systems with supported Linux or Microsoft Windows operating systems to update Ethernetcontrollers.



Automatic Power Cycle Does Not Work forfwupdate on Sun Server X4-4 and Later Platforms(18866436)This issue is fixed in Oracle Hardware Management Pack 2.3.0.1.

When using a Sun Server X4-4 or later x86 server with ILOM v3.2.10.0 or later firmware,fwupdate cannot perform an automatic power cycle when a power cycle is specified in thefirmware metadata.

After you run a fwupdate update command, you will get the following message and the hostsystem will power off:

A PowerCycle was attempted and is not currently supported on this platform. You

will need to perform a manual power cycle. Reference your firmware documentation

for more information.

You will need to manually power the system back on either locally using the server powerbutton or remotely using the Oracle ILOM power management features.

User is Prompted to Confirm an Update fora Mellanox CX3 IB Card on a Solaris System(17656671)

When you use fwupdate to update a Mellanox CX3 Infiniband card on a Solaris system, you areprompted again to confirm whether the update is needed.

Workaround

Type y when prompted to continue with the firmware update.

Remote SP Update Does Not Power Cycle theSystem (18048467)This issue is fixed in Oracle Hardware Management Pack 2.3.3.

After using fwupdate to update the Oracle ILOM service processor of a remote system over thenetwork, the system that has been updated does not automatically reboot.



Workaround

After performing a remote update of an Oracle ILOM SP, manually power cycle the remotesystem to enable the update. A power cycle is required to reset a service processor after afirmware update.

fwupdate Might Hang on Solaris 10 System WithEmulex and Qlogic 16Gb Fibre Channel or Dual 10GbE Card Installed (18044689)

fwupdate might hang on a Solaris 10 system with both an Emulex and a Qlogic 16Gb FibreChannel or Dual 10 GbE Cards installed.

Workaround

1. Power off the system.2. Remove the Emulex 16Gb Fibre Channel or Dual 10 GbE Card.3. Reboot the system.4. Run fwupdate.

Firmware Update Failure With a 16Gb FibreChannel or Dual 10 GbE Card (Emulex) on aSolaris 10 1/13 System (17551814)

This issue is fixed in Oracle Hardware Management Pack 2.3.

On a Solaris 10 1/3 system, 16Gb Fibre Channel or Dual 10 GbE Card (Emulex) card in FCoEor NIC mode, a firmware update using fwupdate will fail.

Notes for Dual 16Gb Fibre Channel or Dual 10 GbECard (Emulex) (17503938)

For an Emulex Dual 16Gb Fibre Channel or Dual 10 GbE controller card with the followingconditions:



■ In NIC mode or CNA mode,■ FCoE SFP transceiver is attached,■ Running under Linux unbreakable kernel mode

The following behavior applies to both automatic and manual fwupdate mode:

■ When multiple Emulex Dual 16Gb Fibre Channel or Dual 10 GbE cards are present on thesystem in NIC mode, all the cards are updated when fwupdate is used to update firmware,even if you run the command to update one card.

■ Place the firmware image to be used for the update to be in a firmware directory. Forexample, if firmware image xyz is being used for an update, this firmware image should beunder /firmware/xyz.

If multiple images exist under the firmware directory, fwupdate will use the latest versionfrom the images in the firmware directory.

Power Cycle Required to Update Oracle ILOMVersion on Sun Fire X4170 M2 Server (16562687)

When upgrading ILOM from a lower version than 3.1.2.20 to a version 3.1.2.20 or later on theSun Fire X4170 M2 server, the server must be power-cycled. If the server is not set up to powercycle automatically after the firmware update, power off the host and power it back on againafter a few minutes.

fwupdate Not Supported for Flash Accelerator F40PCIe Card on a Windows Systems (16278659)

fwupdate is not currently supported for updating a Flash Accelerator F40 PCIe Card installed asystems running a Windows operating system.

Emulex Fibre Channel Cards Are Not Visible onOracle VM 3.1.1 (15790684)

When an Emulex fibre channel card is installed on a system running Oracle VM 3.1.1,fwupdate does not recognize the card.



Error Messages Can Be Disregarded WhenUpdating Firmware for a Emulex Fiber ChannelCard (15762571)

When doing a firmware upgrade for a Emulex Fibre Channel Card, the following errormessages might be displayed, and can be disregarded:

Updating c3: lpfc 0000:b0:00.0: 0:1306 Link Up Event in loop back

>>>>> mode x1 received Data: x1 x1 x20 x1

>>>>> lpfc 0000:b0:00.0: 0:1309 Link Up Event npiv not supported in looop

>>>>> topology

>>>>> lpfc 0000:b0:00.0: 0:(0):2858 FLOGI failure Status:x3/x18 TMO:x0




>>>>> Success

For a Sun Fire X4270 M3 Server With OracleEnterprise Linux 6.0 a Qlogic Card in Slot 2 is NotDisplayed (15763607, 11177285)

fwupdate is unable to list a Qlogic card in Slot 2 of a Sun Fire X4270 M3 server running OracleEnterprise Linux 6.0.

Workaround

Move the card to another slot.

After Updating the Firmware on an InternalExpander Configured for a Sun StorageTek 6Gb/s SAS PCIe HBA, Internal (SGX-SAS6-INT-Z), aReboot is Required (15657192)

After updating the internal expander firmware on a X4270 M2 server with Sun StorageTek6Gb/s SAS PCIe HBA, Internal (SGX-SAS6-INT-Z), a reset command causes the server tobecome unstable and possibly hang.



Workaround

Reboot the server to resolve this problem.

fwupdate Cannot Downgrade Firmware (15663490)

Fixed in Oracle Hardware Management Pack 2.2.

If you attempt to downgrade firmware for an Hitachi H101414SC 146 GB disk driver usingfwupdate, you might receive a message stating that the update was successful; however,fwupdate does not support firmware downgrades on this device.

Workaround

Compare the current firmware version with the version to which you want to update. If thecurrent version is newer, do not update the firmware.

Cannot Update HDDs Firmware With fwupdateupdate Command With Windows 2008 R2 and OEL5.4 (15643212)

You cannot update HDD firmware with fwupdate update if you have the following HDDsinstalled on a Sun Fire X2270 M2 server:

■ For Windows systems: Seagate model ST35000NSSUN500G and Hitachi modelHUA7210SASUN1.0T

■ For Linux systems: Seagate model ST35000NSSUN500G

IPMI Initialization Causes an Error Message in thefwupdate.log File (15670576)

The following message appears when running fwupdate on a Windows system:

fwupdate version 2.0.0

Wed Sep 22 15:23:26 2010:(CLI) Fishwrap version 4.0.1

Failed to initialize security (80010119)

This message can be ignored.



fwupdate Commands on Network Controllers MightNot Show Device Details or Fail When ExecutedRight After Linux OS Loads (21210340)

On systems with Oracle Linux 7.x or Red Hat Enterprise Linux 7.x, attempting to run fwupdatecommands on network interface controllers within the first couple of minutes after the operatingsystem is up and available can result in incomplete information or failure of the command.

When attempting to display information using fwupdate list, the output might not showdevice information for system network controllers. When attempting to update networkcontroller firmware using fwupdate update, the update might fail.

This issue is only seen with network interface controllers. The fwupdate command can still berun successfully on other devices as soon as the OS is up and available.

Workaround

Before attempting to list network controller device information or update network controllerfirmware using the fwupdate command, wait for at least two minutes after the OS is up.

For a critical task, such as an update of network controller firmware, wait two minutes after theOS is up and then run the fwupdate list command to ensure the network controller deviceinformation is listed. If the fwupdate list command completes successfully, showing detailsof the network controller you intend to update, you can then safely run the fwupdate updatecommand.

fwupdate Might Fail When Updating Firmwareon the Oracle Quad 10Gb Ethernet Adapter(21446307)

In rare instances, updating firmware on an Oracle Quad 10Gb Ethernet Adapter using thefwupdate command might fail. This problem might also occur when attempting to update theadapter's firmware using the Oracle System Assistant.

Workaround

If you encounter this problem, retry updating the adapter's firmware using the fwupdatecommand. If the failure persists, contact Oracle Support.


Host-to-ILOM Interconnect Issues

fwupdate Might Fail or Take a Long Time Listing orUpdating Four or More Intel Network Controllers(21920385)

When four or more Intel network controllers are installed in a system, the fwupdate listcontroller command might fail or take up to 20 minutes to successfully list information aboutthem. If you have more than sixteen Intel network controllers installed, the amount of time tolist information will be longer. This issue can also affect firmware updates of Intel networkcontrollers using the fwupdate command.

Workaround

If you encounter a failure when attempting to list or update Intel network controllers usingfwupdate, retry the command and allow extra time for the command to succeed. If you areattempting to update network controller firmware and the failure persists, contact OracleSupport.

fwupdate list Might Show the Sun Dual 10GbESFP+ PCIe 2.0 Low Profile Adapter as "IntelEthernet Server" (25348996)

When listing updatable controllers using the fwupdate list command, an installed Sun Dual10GbE SFP+ PCIe 2.0 Low Profile Adapter might be listed as an "Intel Ethernet Server." Thisissue does not prevent updates to the controller and all other details about the controller in thelist output should be correct. To confirm the adapter type, look in the "Model" column of the listoutput. The Sun Dual 10GbE SFP+ PCIe 2.0 Low Profile Adapter model ID is 0x10fb.

Workaround

If you run into this issue, check the model ID to confirm whether the controller listed is actuallya Sun Dual 10GbE SFP+ PCIe 2.0 Low Profile Adapter. Oracle ILOM also correctly listsinformation about this controller.

Host-to-ILOM Interconnect Issues

The issues shown in the following table are related to the Host-to-ILOM interconnect.


hwmgmtcli Known Issues

Issue Workaround

“Host-to-ILOM Interconnect Not Supported for Oracle VM 3.0.3(17256129)” on page 48

Yes

“Do Not Change Hostmanaged Setting to "False" for the Host-to-ILOM Interconnect FromOracle ILOM” on page 48

NA

Host-to-ILOM Interconnect Not Supported forOracle VM 3.0.3 (17256129)

Do not install or enable the Host-to-ILOM interconnect on a system running Oracle VM 3.0.3.This is because Oracle VM 3.0.3 does not have the required LAN-over-USB Ethernet driver.

Workaround

If you need Host-to-ILOM functionality, update to Oracle VM 3.1.1 or later.

Do Not Change Hostmanaged Setting to "False"for the Host-to-ILOM Interconnect From OracleILOM

For several Oracle Hardware Management Pack commands and M series servers that requirethe use of the Host-to-ILOM interconnect, you should not set the "hostmanaged" property(found under /SP/network/interconnect) when logged into Oracle ILOM to "false".

If the hostmanaged setting is changed to "false" from the Oracle ILOM side, and then the stateof the interconnect is set to either disabled or enabled, applications running on the host willnot be able to detect the change in state and important functions on the host side might fail.This could affect Oracle Hardware Management Pack commands that use and configure theinterconnect, and also M series servers with multiple service processors that use it to provide SPfailover.

If you need to modify Host-to-ILOM interconnect settings with the host OS running, use theOracle Hardware Management Pack ilomconfig command from the host.

hwmgmtcli Known Issues

The issues shown in the following table are related to hwmgmtcli.


hwmgmtd Known Issues

Issue Workaround

“Running hwmgmtcli on a Sun Blade X6270 M2 Server Might Return Error Messages forChassis Information (15801911)” on page 49

Yes

“Sun Blade X6270 M2 Shows Incorrect Chassis Data (15732926)” on page 49 Yes

Running hwmgmtcli on a Sun Blade X6270 M2Server Might Return Error Messages for ChassisInformation (15801911)

Fixed in Oracle Hardware Management Pack 2.2.4.

When running hwmgmtcli commands, errors are returned for chassis information as follows:

Chassis Model: ERROR

Chassis Address: ERROR

Workaround

To avoid this error, upgrade to Oracle ILOM 3.1.

Sun Blade X6270 M2 Shows Incorrect ChassisData (15732926)

Fixed in Oracle Hardware Management Pack 2.2.

When using the hwmgmtcli command to view chassis information on a Sun Blade X6270 M2server module, some information about the chassis is missing.

Workaround

Use Oracle ILOM CMM to view the chassis information.


The issues shown in the following table are related to hwmgmtd.



Issue Workaround

“hwmgmtd Memory Usage Grows Over Time in Windows Systems(15752292)” on page 50

Yes

“hwmgmtd Not Started When Oracle Hardware Management Pack 2.2.1 or 2.2.2 is Installedon an ESX 3.5 Server (15738417)” on page 50

Yes

“hwmgmtd Service Cannot Start on Linux and Oracle Solaris With Oracle HardwareManagement Pack 2.3.1 (20200641)” on page 51

No

“hwmgmtd Service Goes Into Maintenance Mode on Oracle SPARC Systems With OracleHardware Management Pack 2.3.1 (19890355)” on page 51

No

“hwmgmtd Can Crash When Getting Information From the InfiniBand Card Plugin(22066585)” on page 51

Yes

hwmgmtd Memory Usage Grows Over Time inWindows Systems (15752292)

When hwmgmtd is running on a Windows system, the daemon uses more memory over time.

Workaround

hwmgmtd is automatically restarted every 24 hours on Windows systems so that memory usage isflushed. You will see a message in the logs stating that hwmgmtd has restarted.

hwmgmtd Not Started When Oracle HardwareManagement Pack 2.2.1 or 2.2.2 is Installed on anESX 3.5 Server (15738417)

After installing Management Pack 2.2.1 or 2.2.2 in a system running ESX 3.5 hwmgmtd does notstart automatically.

Workaround

Start the hwmgmtd agent manually. Refer to the Oracle Server Management Agents 2.2 User'sGuide for more information on running hwmgmtd manually.



hwmgmtd Service Cannot Start on Linux and OracleSolaris With Oracle Hardware Management Pack2.3.1 (20200641)


In rare instances on systems running Linux or Oracle Solaris, the Oracle Hardware ManagementPack agent (hwmgmtd) might not start or stop and go into maintenance mode soon afterstarting. The service disable/enable and clear commands do not fix the problem.

There is no workaround.

hwmgmtd Service Goes Into Maintenance Mode onOracle SPARC Systems With Oracle HardwareManagement Pack 2.3.1 (19890355)


In rare instances on Oracle SPARC systems, the Oracle Hardware Management Pack agent(hwmgmtd) might go into maintenance mode and core dump if stopped while the IPMI serviceis in the middle of a request.

There is no workaround.

hwmgmtd Can Crash When Getting Information Fromthe InfiniBand Card Plugin (22066585)

On systems running Oracle Solaris 10, the management agent (hwmgmtd) might crash whenobtaining information from the InfiniBand plugin (mlnx_ib.so).

Workaround

If you encounter this issue, rename the InfiniBand plugin file to mlnx_ib.so.disable. Thedefault path to the InfiniBand plugin file is:

/usr/lib/ssm/lib/plugins/framework/


ilomconfig Known Issues


The issues shown in the following table are related to the ilomconfig tool.

Issue Workaround

“Start New Shell for Solaris ilomconfig After Uninstalling Oracle HMP ilomconfig(18277233)” on page 52

No

“DHCP Discover When Enabling Local Host-to-ILOM Interconnect on a Linux System(17563392)” on page 52

No

“ilomconfig Commands Might Fail When Using ILOM 3.0.9 (15650623)” on page 53 Yes

“ilomconfig Host Local Credential Cache Feature Has Been Disabled(21563538)” on page 53

Yes

Start New Shell for Solaris ilomconfig AfterUninstalling Oracle HMP ilomconfig (18277233)

After the Oracle Hardware Management Pack version of ilomconfig has been uninstalled froma system running Oracle Solaris 11.1, you need to start a new shell in order to use the OracleSolaris version of ilomconfig again.

DHCP Discover When Enabling Local Host-to-ILOM Interconnect on a Linux System (17563392)

This issue is fixed in Oracle Hardware Management Pack 2.2.8.

When using ilomconfig enable interconnect on a Linux system running the NetworkManager, a DHCP discover is sometimes done on the system interconnect port.

This action is harmless but the interconnect should not be used until the DHCP discovercompletes.



ilomconfig Commands Might Fail When UsingILOM 3.0.9 (15650623)

Oracle ILOM versions 3.0.9 and earlier have limitations that might cause the ilomconfigcommand to fail with the error Cannot connect to BMC. These errors can occur when multipleprograms attempt to access the IPMI interface of Oracle ILOM.

If such errors do occur, Oracle ILOM must recover from this error. This recovery could mean aone or two minute disruption in the services provided by Oracle ILOM.

Workaround

To help avoid this error, disable the Hardware Management Agent and Storage MonitoringAgent before using ilomconfig. Also, any other IPMI access to Oracle ILOM, such as usingipmitool, should be avoided when running ilomconfig.

ilomconfig Host Local Credential Cache FeatureHas Been Disabled (21563538)As of Oracle Hardware Management Pack 2.3.3, the host credential cache feature used tofacilitate access to the Oracle ILOM service processor (SP) through the Host-to-ILOMInterconnect has been disabled. The ilomconfig create credential command will nolonger create a credential cache file on the host to store Oracle ILOM username and passwordinformation. Nor will an existing credential cache be used for Oracle Hardware ManagementPack commands accessing the Oracle ILOM SP.

This change affects the way some Oracle Hardware Management Pack commands are issuedthat access the system's local SP (like fwupdate, ilomconfig and ubiosconfig) and only onsystems with an Oracle ILOM version earlier than 3.2.4. For these systems, if you want to usea LAN interface (for either the local Host-to-ILOM interconnect or a remote Ethernet networkconnection) you must manually include credentials using the -H and -U options for commandsthat access an SP. If credentials are not provided, these commands will default to the slowerlocal KCS interface to access the local Oracle ILOM SP.

For systems with Oracle ILOM version 3.2.4 or later, credentials do not need to be includedwhen running commands that access the local SP through the Host-to-ILOM interconnect.You still need to manually include credentials (using the -H and -U options) when runningcommands that access an SP using a network connection.

The capability to delete a previously saved host credential cache is still supported using theilomconfig delete credential command.


ipmitool Known Issues

Workaround

To use the faster LAN interface for Oracle Hardware Management Pack commands that accessthe local Oracle ILOM SP (versions earlier than 3.2.4), you must manually enter the requireduser credentials from the command line. The required password can also be piped in on stdinfor scripting use.

Examples:

■ ilomconfig list system-summary --remote-hostname=sp_ip --remote-username=username■ cat passwd.file | fwupdate list all --remote-hostname=sp_ip --remote-username=username

Where sp_ip is the IP address of the Oracle ILOM SP, username is the Oracle ILOM useraccount with root priviledges, and passwd.file is a file you create that contains the Oracle ILOMuser account password.

Note - In the example above, to use the local Host-to-ILOM interconnect instead of a networkport to access the SP, obtain its IP address using the ilomconfig list interconnectcommand.

ipmitool Known Issues

The issue shown in the following table is related to ipmitool.

Issue Workaround

“ipmitool Error Might Occur When SP Is Booted When SPARC T3-4 Host Is On(15719015, 15691003)” on page 54

Yes

ipmitool Error Might Occur When SP Is BootedWhen SPARC T3-4 Host Is On (15719015,15691003)

When the SPARC T3-4 host is powered on and the SP is booted, you might receive thefollowing error:

SP communication failure....Please start IPMI


itpconfig Known Issues

ipmitool will not function in this state.

Workaround

If you encounter this error, reboot the host to clear the error.

itpconfig Known Issues

The issue shown in the following table is related to itpconfig.

Issue Workaround

“itpconfig Error 83 "ERROR: Service Processor has conflictingconfiguration"” on page 55

Yes

itpconfig Error 83 "ERROR: Service Processorhas conflicting configuration"

itpconfig uses Oracle ILOM Notification Alert Rule 15 to set up the trap forwarding. Ifthis alert rule is in use, itpconfig fails with error code 83 "ERROR: Service Processor hasconflicting configuration." This error is caused when you try to run itpconfig when OracleILOM Notification Alert Rule 15 is already defined on the system.

To work around this, set the destination IP address of Oracle ILOM Notification Alert Rule 15to 0.0.0.0. When using the Oracle ILOM command line interface, enter the following command:

-> set /SP/alertmgmt/rules/15 destination=0.0.0.0

raidconfig Known Issues

The issues shown in the following table are related to the raidconfig tool.

Issue Workaround

“User Warning: raidconfig Shows the System Boot Disk as Available(20992189)” on page 56

NA



Issue Workaround

“Sun Flash Accelerator Cards Incorrectly Identified as RAID-Capable(18519959)” on page 56

No

“Hot Spares Not Visible on SPARC System With MegaRAID SAS Controller(16729481)” on page 57

No

“On SLES 11 SP 1 System, Disks Might Disappear (15845681)” on page 57 Yes

“RAID Volume Might Not Be Visible in Oracle ILOM on SPARC Systems(15782246)” on page 57

Yes

“RAID 1 Volume With More Than Two Disks Is Not Handled Correctly(15747500)” on page 57

No

“When Running init Task on RAID Volume clear Tasks on Disks Always Show 0%Complete (15742034)” on page 58

No

“Mounted Property for RAID Volumes is Not Visible When Using SGX-SAS6-R-REM-Z orSGX-SAS6-R-INT-Z (15666684)” on page 58

Yes

“After Creating a RAID Volume With --name Option With LSI REM, Volume's Name isStill Null (15675209)” on page 58

No

“Different RAID Volumes Have the Same Device Name When OS is VMWare ESX 3.5Update 5 (15674922)” on page 59

No

“RAID 10 Listed as Not Supported When Creating RAID Volume With raidconfig(22129034)” on page 59

Yes

User Warning: raidconfig Shows the System BootDisk as Available (20992189)

raidconfig can scan your controllers and connected disks and list disks that are either alreadyin a RAID volume, or available to be included in a RAID volume. However, raidconfig cannottell if an available disk has data on it, or if a disk is otherwise used as either a boot disk orlogical disk for an application.

Before using raidconfig to create volumes (which will overwrite any existing data), useoperating system tools to take an inventory of attached disks, their enumeration, and whetherthey contain data that you want to preserve.

Sun Flash Accelerator Cards Incorrectly Identifiedas RAID-Capable (18519959)

The Sun Flash Accelerator F40 (LSI Logic 0x050a) and Sun Flash Accelerator F80 PCIe (LSILogic 0x0581) cards are identified as RAID-capable controllers in the output of the raidconfiglist command, though they are not available for RAID configuration.



The Sun Flash Accelerator F20 PCIe Card is correctly identified as a non-RAID controller andis hidden from the raidconfig list output.

Hot Spares Not Visible on SPARC System WithMegaRAID SAS Controller (16729481)If disks are added as dedicated spares to a RAID 1 volume, the hot spare disks are no longervisible with the command raidconfig list disk.

This happens on a SPARC system with a MegaRAID SAS controller.

On SLES 11 SP 1 System, Disks Might Disappear(15845681)On a SLES 11 SP 1 system, disks that are used in RAID volumes or as hot-spares might not belisted in the raidconfig list output.

Workaround

Install an updated mpt2sas driver.

RAID Volume Might Not Be Visible in Oracle ILOMon SPARC Systems (15782246)

A RAID volume created using raidconfig might not be visible under the /STORAGE target inOracle ILOM.

Workaround

Use the raidconfig list all command to view the newly created volume.

RAID 1 Volume With More Than Two Disks Is NotHandled Correctly (15747500)For the SGX-SAS6-R-INT-Z HBA, no more than two disks can be used for creating a RAID 1volume.



When Running init Task on RAID Volume clearTasks on Disks Always Show 0% Complete(15742034)

When an init task is running on a RAID volume, the disks in that RAID volume have a cleartask started on them. The percentage complete for the clear task always shows zero until the inittask has finished.

A workaround is not required.

Mounted Property for RAID Volumes is Not VisibleWhen Using SGX-SAS6-R-REM-Z or SGX-SAS6-R-INT-Z (15666684)

The Mounted property is missing from RAID volumes created when using the SGX-SAS6-R-INT-Z HBA or SGX-SAS6-R-REM-Z. raidconfig will not prevent you from deleting amounted volume.

Workaround

1. Using the raidconfig command, retrieve the Device Name for the RAID volume.2. Check the output of the mount command for an instance of the Device Name retrieved in

Step 1.3. If the Device Name is present in the output of the mount command, the RAID volume is

currently mounted and should not be deleted using raidconfig.4. Unmount the RAID volume first, then use raidconfig to delete the volume.

After Creating a RAID Volume With --nameOption With LSI REM, Volume's Name is Still Null(15675209)

After creating a RAID volume on the RAID 0/1 Expansion Module (X4607A) usingraidconfig with the ---name option, the RAID volume name is still null, though the RAIDvolume is successfully created.


ubiosconfig Known Issues

Different RAID Volumes Have the Same DeviceName When OS is VMWare ESX 3.5 Update 5(15674922)

When creating two RAID volumes on a RAID Expansion Module (X4620A) on a serverrunning VMWare ESX 3.5 Update 5, the RAID volumes have the same device name.

RAID 10 Listed as Not Supported When CreatingRAID Volume With raidconfig (22129034)

On a system with the Sun Storage 6 Gb/s SAS PCIe HBA (internal or external), attemptingto create a RAID 10 volume using raidconfig with the --level=10 option will yield thefollowing message: "ERROR: RAID level not supported by controller."

Workaround

The FCODE version 1.00.65 on the Sun Storage 6 Gb/s SAS PCIe HBA (internal or external)does not support RAID 10. It does support an even (four or more) or odd (3 or more) number ofdisks used in a RAID level 1e. Use RAID level 1e in place of RAID level 10.

For example, to create a RAID 1e volume on four disks in the system, type:

raidconfig create raid --level=1e -d c0d0,c0d1,c0d2,c0d3

This RAID volume will be seen as RAID 1e by raidconfig, but seen as RAID 10 by the HBA'sconfiguration utility (sas2ircu).

This is expected behavior with the Sun Storage 6 Gb/s SAS PCIe HBA using FCODE version1.00.65.

ubiosconfig Known Issues

Issue Workaround

“ubiosconfig Cannot Connect to BMC On Systems With Oracle ILOM 3.2.6(24356013)” on page 60

Yes


SNMP Agent Known Issues

ubiosconfig Cannot Connect to BMC On SystemsWith Oracle ILOM 3.2.6 (24356013)

This issue is fixed in Oracle Hardware Management Pack 2.3.7.

On systems with Oracle ILOM version 3.2.6, attempting to run the ubiosconfig commandto change system UEFI BIOS settings will fail with an error message about being unable toconnect to the BMC. This issue has not been seen in other versions of Oracle ILOM.

Workaround

To make changes to UEFI BIOS settings for these systems, you must run the system's BIOSSetup Utility either at the local server console or from a remote console. Refer to your platformdocumentation for additional information on accessing the BIOS Setup Utility.


The issues shown in the following table are related to SNMP Agent.

Issue Workaround

“snmpwalk of the Storage MIB Results in a Timeout or Error Message(15694465)” on page 61

No

“SNMP Trap Issues” on page 61 Yes

“Sun X6250 Server Module Reports Wrong Service Processor VersionNumber” on page 61

Yes

“Parent FRU Name for Sensors on Shared Components in a Blade Chassis is Incorrect(15728111, 15688172)” on page 62

Yes

“Discrete Current Sensors Are Miscategorized on SPARC T3-Series Servers(15687547)” on page 62

Yes

“SunHwMonInventoryTable Shows Incorrect Number of DIMMs(15566455)” on page 62

Yes

“SunHwMonDiscreteHardDriveSensorTable Incorrect Sensors” on page 63 No

“Host Agent Might Generate Incorrect Notification (15675490)” on page 63 Yes

“Windows Hardware Management Agent SNMP Walk on a Sensor Group Issue(15604854)” on page 63

Yes

“sunStorageVolumeOSMountPoint Not Showing Mount Point (15666684)” on page 63 No

“Incorrect DiskOSDeviceName on SPARC T3-2 System (15668518)” on page 64 Yes

“Storage MIB Does Not Expose Dual Path Disks (15673745)” on page 64 Yes



snmpwalk of the Storage MIB Results in a Timeoutor Error Message (15694465)

When you use the snmpwalk command with a Storage MIB on a SPARC system, the storageinformation appears, but you might receive an error message or timeout at the end of the output.

This error message can safely be ignored.

SNMP Trap Issues

■ sunHwTrapProductName can be empty on some platforms.■ sunHwTrapSystemIdentifier is empty when the service processor is running ILOM 2.0.■ sunHwTrapAssocObjectId is always set to SNMPv2-SMI::zeroDotZero.■ sunHwTrapComponentName is set to the IPMI name of the component rather than the name

used by ILOM.■ On Sun Fire X4200 M2 servers, Hardware Management Agent sends

sunHwTrapComponentOK or sunHwTrapComponentError instead ofsunHwTrapSlotOrConnectorOk or sunHwTrapSlotOrConnectorError, which are sent byILOM.

Workaround

You can access this information from ILOM or SNMP interfaces.

Sun X6250 Server Module Reports Wrong ServiceProcessor Version Number

When you run the Hardware Management Agent on Sun X6250 server modules with olderservice processor firmware, the wrong version of service processor is reported.

Workaround

Oracle recommends that you upgrade to the latest firmware.



Parent FRU Name for Sensors on SharedComponents in a Blade Chassis is Incorrect(15728111, 15688172)

sunHwMon...SensorParentFruName is incorrectly set to /SYS for sensors on shared fieldreplaceable units (FRUs) in a blade chassis.

Workaround

Use ILOM to determine the correct parent name for these sensors.

Discrete Current Sensors Are Miscategorized onSPARC T3-Series Servers (15687547)

On SPARC T3-Series servers, discrete current sensors are miscategorized and listed insunHwMonDiscreateOtherSensorTable instead of in sunHwMonDiscreteCurrentSensorTable.

Workaround

Use the sunHwMonDiscreateOtherSensorTable to view discrete current sensors.

SunHwMonInventoryTable Shows Incorrect Number ofDIMMs (15566455)

On some platforms, DIMMs which are not present in the system are shown insunHwMonInvetoryTable.

Workaround

View the FruDescr, FruPartNumber, FruSerialNumber and FruManuacturer objects. If thesevalues are filled in, the DIMMs are present in the system. If there objects are not filled in, itindicates DIMMs that are not present and can be safely ignored.



SunHwMonDiscreteHardDriveSensorTable IncorrectSensors

Due to platform limitations, sunHwMonDiscreteHardDriveSensorTable can contain sensors fordisks not physically present on the host. These sensors have a ParentFruIndex of -1 and endwith STATE-HIDDEN. These sensors can be safely ignored.

Host Agent Might Generate Incorrect Notification(15675490)

Not all device types defined in recent releases of ILOM are recognized by the host agent,resulting in cases where the host agent generates a generic sunHwTrapComponent Notificationrather than a device specific Notification (for example, sunHwTrapSlotOrConnector). This isdue to a component error rather than a slot or connector.

Workaround

Use the NAC name from the MIB to determine the specific device for the Notification.

Windows Hardware Management Agent SNMPWalk on a Sensor Group Issue (15604854)

When you use Hardware Management Agent on a Windows operating system, an SNMP walkof a sensor group returns an empty string if this group contains discrete sensors.

Workaround

A work around is an SNMP walk of the whole Sun-HW-Monitoring MIB.

sunStorageVolumeOSMountPoint Not Showing MountPoint (15666684)

sunStorageVolumeOSMountPoint reports a device name instead of a mount point.


Storage Viewer Known Issues

Incorrect DiskOSDeviceName on SPARC T3-2 System(15668518)

DiskOSDeviceName on a SPARC T3-2 server reports 02000000:0 and 02000000:2 asOSDeviceName. No such names can be found on the host OS.

Workaround

For multipath disks, raidconfig returns only the WWN for the device instead of the full pathname. The format command returns the full path name of this device with the WWN embeddedin it. You can correlate the device by using the WWN.

For example:

■ This is the information that you get on a device using raidconfig: Device:5000CCA00A49BC1C

■ This is the information that you get on a device using the format command: Device:c0t5000CCA00A49BC1Cd0

Storage MIB Does Not Expose Dual Path Disks(15673745)

sunStorageDiskTable shows only a single disk instance when a physical disk is dual-pathed totwo controllers.

Workaround

Use ILOM to determine the correct information about the disk.

Storage Viewer Known IssuesThe issues shown in the following table are related to Storage Viewer.

Issue Workaround

“Global Hot Spare for RAID 1 Volume Displayed as a Dedicated Hot Spare on OracleSolaris (15586295)” on page 65

No

“The max_disks Property Is Incorrect When Using Adaptec Disk Controller(SGXPCIESAS-R-INT-Z) (15584958)” on page 65

No


Using Oracle Hardware Management Pack With SPARC M5-32 and M6-32 Servers

Issue Workaround

“The write_cache_enabled Property Not Available for Adaptec Controllers(SGXPCIESAS-R-INT-Z) (15583722)” on page 65

No

Global Hot Spare for RAID 1 Volume Displayedas a Dedicated Hot Spare on Oracle Solaris(15586295)

When you are using Storage Management Agent on a Oracle Solaris system configured with aglobal hot spare for a RAID 1 (Mirrored) RAID with a Sun Storagetek PCI-E SAS RAID HBA(SGXPCIESAS-R-INT-Z), the details of the disk are displayed as a dedicated hot spare.

The max_disks Property Is Incorrect When UsingAdaptec Disk Controller (SGXPCIESAS-R-INT-Z)(15584958)

The max_disks property for a Sun Storagetek PCI-E SAS RAID HBA (SGXPCIESAS-R-INT-Z) is incorrectly displayed as 0 in Storage Viewer.

The write_cache_enabled Property Not Availablefor Adaptec Controllers (SGXPCIESAS-R-INT-Z)(15583722)

The write_cache_enabled property is not available for Adaptec Controllers (SGXPCIESAS-R-INT-Z).


The following sections cover specific information for using Oracle Hardware Managementtools with the SPARC M5-32 and M6-32 servers:



■ “ilomconfig (16369886)” on page 66■ “hwmgmtcli (16507559)” on page 67■ “itpconfig (16508501, 16507898)” on page 68■ “hwmgmtd (15824059, 15824037)” on page 68

ilomconfig (16369886)

The SPARC M5-32 and M6-32 servers have a pair of dual-redundant SPs (SP0 and SP1) in thechassis. It also has 4 SP proxies (SPP0, SPP1, SPP2, SPP3).

The host OS does not have direct access to all Oracle ILOM properties from the SPs, soyou need to use Oracle ILOM to access Oracle ILOM properties from the SP, rather thanilomconfig.

For SPARC M5-32 and M6-32 servers, the Oracle Solaris host OS runs on the SPPs.ilomconfig accesses the Oracle ILOM SPP from the Oracle Solaris host OS.

The following table describes the properties of the SPs and SPPs.

Service Processor Type Description Tool to access SP

SP0, SP1 (redundant serviceprocessors)

These are the main serviceprocessors with all the standardOracle ILOM properties. The SPsmanage the SPPs.

Oracle ILOM

SPP0, SPP1, SPP2, SPP3 (serviceprocessor proxies)

Each SPP monitors a domainconfigurable unit (DCU). The hostOS runs on the SPPs.

ilomconfig

See also:

■ “Oracle ILOM Properties Not Available From the SPARC Server M5-32 and M6-32SPPs” on page 66

■ “ilomconfig Commands Supported on SPARC M Series Server Platforms” on page 67

Oracle ILOM Properties Not Available From the SPARC ServerM5-32 and M6-32 SPPs

The following table lists the Oracle ILOM properties that are not available from SPARC M5-32and M6-32 server SPPs.



Oracle ILOM Properties ilomconfig Features

/SP/config export, import

/SP/users user

/SP/services/snmp/communities snmp-community

/SP/network/pending network mgmt (read-only)

ilomconfig Commands Supported on SPARC M Series ServerPlatforms

For SPARC M Series servers, the following ilomconfig subcommands and targets aresupported:

■ list subcommand targets:■ system-summary■ network■ network-ipv6■ interconnect■ identification

■ enable subcommand target:■ interconnect

■ disable subcommand target:■ interconnect

■ modify subcommand targets:■ interconnect■ identification

■ delete subcommand target:■ credential

hwmgmtcli (16507559)

A new subsystem has been added for multi-domained systems, such as SPARC M5-32 and M6-32 servers:

dcu - Show details of dcu subsystem.



For SPARC M5-32 and M6-32 systems, open_problems diagnosed by Oracle ILOM are notreported by hwmgmtcli on PDOM hosts. In addition, health, and health_details informationmight be missiing or not reliable.

On multi-domain systems hwmgmtcli can only see the devices (such as controllers and storage)that are dedicated to the host domain where hwmgmtcli is being run. In contrast, Oracle ILOMobtains reports from all domains and therefore can report on all devices in the system.

itpconfig (16508501, 16507898)

The fault proxy cannot be enabled on the SPARC M5-32 and M6-32 servers. These servershave no Oracle ILOM alert management on the SPP, and there is no Host-to-ILOM interconnectbetween the SP and an OS, so there is no way for this tool to function.

hwmgmtd (15824059, 15824037)

hwmgmtd can be used on SPARC M5-32 and SPARC M6-32 servers to provide storageinformation to Oracle ILOM, but SNMP agent functionality of hwmgmtd should not be used, asit will provide erroneous data.


oracle® hardware management pack 2.3.x release notes

Documents