| General |
| Q1. |
How is the Toolkit made available? |
| A1. |
The Toolkit can be downloaded at no charge following a simple registration. |
| |
| Q2. |
Do I need SmartStart to use the Toolkit? |
| A2. |
The SmartStart Scripting Toolkit does not require the use of the SmartStart CD. However, the SmartStart CD contains drivers and utilities that enhance the functionality of the target server. These drivers and utilities can be copied to the custom installation CD or to the shared network drive. You can also download support software. |
| |
| Q3. |
Can the Toolkit be used to install ProLiant Support Software? |
| A3. |
Yes. The SmartStart Scripting Toolkit is a deployment tool that relies on the unattended installation capabilities of the executable file that it runs to deploy an operating system or install an application onto a target system. To find sample scripts for integrating ProLiant support software in your deployment scripts, refer to the SmartStart Scripting Toolkit Best Practices. |
| |
| Q4. |
What is PXE (pre-boot execution environment)? |
| A4. |
Pre-boot eXecution Environment (PXE) is a feature that allows a server to boot from a remote PXE-enabled server. The source server must be configured with a PXE capable image, and the target server must be enabled for PXE.
For more information on how to enable and use PXE, refer to Using PXE Technology with HP ProLiant Servers. |
| |
| Q5. |
Why is there no new release of the DOS version of SmartStart Scripting Toolkit? |
| A5. |
Support for DOS version of the SmartStart Scripting Tool Kit has End Of Life in May 2005.
The Win32 version of the Scripting ToolKit is available for Scripting Windows based Servers and a Linux version for the Linux operating system based Servers. |
| |
| Support |
| Q1. |
What level of support is offered with the SmartStart Scripting Toolkit? |
| A1. |
The SmartStart Scripting Toolkit offers the following support. Submit questions using the e-mail support form.
- Diagnosis of problems related to the functionality of the utilities in the Toolkit
- Advice about proper installation and setup of the software configuration parameters
- Solutions to known Toolkit problems
HP responds to questions relating to software features, functionality, and all utilities packaged in the Toolkit. HP also provides technical assistance on areas such as creating an installation CD or setting up software configuration parameters. Advanced topics such as script development and debugging are supported on a best-effort basis. Any customized troubleshooting or development of scripts will be offered for-fee based of support services. |
| |
| Q2. |
What operating systems does the Toolkit support? |
| A2. |
The SmartStart Scripting Toolkit is server operating system-independent, relying on the unattended installation capabilities of each operating system for successful unattended deployments onto target servers. The Linux Edition integrates unattended installations of Linux operating systems via the kickstart.cfg file. The Win32 Edition integrates unattended installations of WinPE operating system via the unattend.txt files. |
| |
| Q3. |
What server and server hardware does the SmartStart Scripting Toolkit support? |
| A3. |
The SmartStart Scripting toolkit supports the ProLiant ML/DL 300, 500, 700, and BL servers. For a complete list of supported servers and options, refer to the SmartStart Scripting Toolkit Support Matrix. |
| |
| Q4. |
Where can I find more information about the operating system's unattended installation mechanisms? |
| A4. |
Operating system vendors have information regarding deployment and unattended installation mechanisms on their web pages. Additional information on creating the unattended installation text file and operating system deployment can be found in the Operating System resource documents ( Microsoft Windows NT Server 4.0 Server Resource Kit, Microsoft Windows 2000 Server Resource Kit , Microsoft Windows Server 2003 Resource Kit, Deployment Resources Roadmap: A Guide to Deploying Windows NT Server 4.0, RedHat Linux KickStart HOWTO ). |
| Configuration and Utilities |
| Q1. |
What is the new migration utility for the Win32 Edition? |
| A1. |
The migration utility converts data files from the DOS Edition into XML files used by the Win32 Edition. This utility facilitates the transition for current DOS Edition users to Win32 Edition. Review the User Guide for more details.
|
| Q2. |
What is scriptable erase? |
| A2. |
Scriptable erase is a command line unattended erase that provides a way to return a ProLiant server to its original "clean" state by erasing hard drives and clearing system BIOS settings. HP provides the information necessary to create a boot configuration and diskette that performs a system erase. This diskette is not included in the default set of HP provided diskettes, because this diskette has the potential to erase large numbers of systems accidentally. However, creating this diskette is simple, and if you need an unattended command line erase utility, all the required information is available in the SmartStart Scripting Toolkit Best Practices document. |
| |
| Q3. |
What scripting is available for RILOE II and iLO? |
| A3. |
HP offers scripting support for the Remote Insight Lights-Out Edition II (RILOE II) and iLo features for the ProLiant servers with the HPONCFG utility. HPONCFG is a command-line utility that generates a hardware configuration script file used to duplicate the RILOE configuration of a source ProLiant ML or DL server on a target server. HPONCFG enables you to configure features exposed through F8 startup or the graphical user interface. This utility is not intended for continued administration. The Remote Insight Board Command Language should be used to administer user rights and network functionality on the server. For more information on these utilities, refer to the Integrated Lights-Out Edition User Guide or the Remote Insight Lights-Out Edition II User Guide. |
| |
| Q4. |
What is the Network Teaming and Configuration utility? |
| A4. |
The Network Teaming and Configuration utility enables configuration of network adapters (NICs) and teams of network adapters. The scripting feature of the utility enables adapter configuration using a batch process.
Scripting functionality enables configuration of a target system based on configuration information saved from a source server. The target system does not need to be identical to the source server. The configuration of the source server may not be duplicated in its entirety on the target system.
NICs and teams of NICs can be configured on the target system. When scripting is run, the NIC properties specified in the data file from the source server are used to modify the configuration of the NICs on the target system.
For more information, refer to the "Network Teaming and Configuration" appendix of the SmartStart Scripting Toolkit Best Practices document. |
| |
| Q5. |
How does the Toolkit work with Microsoft Automated Deployment Service (ADS)? |
| A5. |
The DOS Edition of the Toolkit has been tested with Microsoft ADS on selected ProLiant servers. Detailed information is available on support of the Toolkit when using Microsoft ADS. |
| |
| |
| Troubleshooting |
| Q1. |
I set up PXE boot as described in the HP SmartStart Scripting Toolkit Linux Edition Best Practices document, but when I boot the server, I receive the following message: "Could not find kernel image: linux" and I am left at a boot: prompt. Why? |
| A1. |
The Best Practices document incorrectly instructs you to place the default.cfg file in the /tftpboot/pxelinux.cfg/ directory. The correct file is default. Be sure to use /tftpboot/pxelinux.cfg/default and the system will boot properly. |
| |
| |
| Q2. |
The sample Linux scripts do not work with the IDE controller on the ProLiant BL10e. What should I do? |
| A2. |
Customize a function to detect and use the IDE drive as the boot device. |
| |
| Q3. |
Why does the HPONCFG utility return an error? |
| A3. |
The most common cause is missing drivers. Run the load_health.sh script to load the required health and system agents and install the appropriate drivers. |
| |
| Q4. |
HPONCFG seems to fail when trying to read a configuration from a file. Why? |
| A4. |
HPONCFG only supports certain versions of RILOE II and iLO firmware. Use the -get_hostinfo argument to HPONCFG to check the current firmware version before using the tool to configure the device. |
| |
| Q5. |
I have the newest version of the RILOE II firmware and the HPONCFG tool, but it still seems to fail. Why? |
| A5. |
An issue has been discovered with the Linux RILOE/RILOEII driver included in the Smart Start Scripting Toolkit which prevents the HPONCFG tool from communicating properly with the RILOE II device. Future versions of the tool may be able to recover from this error, but will not be able to configure the RILOE II device without a driver update. |
| http://h18013.www1.hp.com/products/servers/management/toolkit/downloadtkpage.html |
