HP 6005 Implementing Out-Of-Band Desktop Management with DASH - Page 16

Troubleshooting Upgrading Management Software The installation of management agent is required to support various DASH functions, such as gracefully shutting down the system, and is installed on factory system image. When building a custom image, management agent and CIM options can be selected during Broadcom Advance Control Suite (BACS) installation. The following command line can be used to silently install management agent with BACS similar to factory image. Please note, command and parameters must be entered on the same line. Refer to SilentMgmtAppsa.txt in MgmtApps directory for more information on silent installation. Setup.exe /s /v" /qn ADDSOURCE=BACSi32,BASPi32,CIMi32,MgmtCfgi32,MgmtAgenti32" Firmware updates are currently released as an image file with factory default settings. BMCC tool can be used to export current settings into a file that can be used to import the settings back after update. A sample batch file is included with the firmware update as an example to automate settings export, firmware update, and setting import. This example uses BMCC and firmware upgrade utility for Windows. Both are included in the firmware softpaq. PCIe Add-in Card Issues DASH functionality requires a communication channel between the hardware platform features, system BIOS, and the Broadcom NetXtreme™ Gigabit Ethernet Controller. The introduction of additional PCI Express cards into the platform can disrupt the communication channels utilized for DASH. This type of disruption can be manifested as the inability to issue requested power state changes to the DASH enabled platform for example. In the event that you experience inconsistencies in DASH behavior, remove PCIe option cards one by one to determine the conflicting device. Once you have determined the PCIe option card that is interfering with DASH functionality, contact HP or the PCIe device manufacturer for firmware updates to correct the issue. Power-On Password The Broadcom NetXtreme™ Gigabit Ethernet Plus functions very similarly between a dc7900 and a dc5850. However, there is one important difference regarding remote wake and Power-On Password behavior. A remote shutdown into a sleep state, S3 - S5, and subsequent remote wake of the dc5850 will bypass the Power-On Password as the system resumes from the sleep state. This is the expected behavior. In the case of the dc7900, there is a hardware limitation that does not report the remote wake and wakes the system as a localized wake. Therefore, the BIOS reaction to the wake event is to process it as a localized wake and not bypass the Power-On Password.