HP ProLiant SL2500 HP Scripting Toolkit 9.60 for Windows User Guide - Page 54

Troubleshooting, Troubleshooting table, HPSSASCRIPTING supports only HP Smart Array controllers. - review

Page 54 highlights

5 Troubleshooting Troubleshooting table Issue Data loss in STK Configuring options using STK utilities Input files for HPONCFG Sample script files HP ProLiant drivers WMI support Non-functioning IFHW CONREP version compatibility HPSSASCRIPTING support HPRCU compatibility Booting from a USB drive key Customizing the DEPLOYSERVER.CMD script SETBOOTORDER changes 54 Troubleshooting Troubleshooting Improper use of the Scripting Toolkit utilities and modification of the CONREP data files can result in loss of critical data. Because of the potential data-loss risk, only experienced individuals should use the Scripting Toolkit utilities. Before using the Scripting Toolkit, all necessary precautions must be taken to ensure that mission-critical systems remain online if a failure occurs. Not all options can be configured using Scripting Toolkit utilities. Some options must be configured manually or with other configuration utilities, which are available online, before they can be used with the Scripting Toolkit. For more information on configuration, see the option documentation. Because the -w argument does not capture certain types of information, such as the administrator password, data files created with HPONCFG using the -w argument cannot then be used as input files for HPONCFG, unless they are modified first. The script files and script segments in this guide are provided only as examples. You must modify the scripts for your environment. When creating or modifying your own scripts, the pause command is a valuable tool to help you determine that each step of the script is functioning as desired. HP ProLiant drivers must be added during Windows PE customization to ensure the Scripting Toolkit utilities function properly. See the readme.txt file provided. HP software requires that WMI support be enabled to function in Windows PE properly. IFHW is case-sensitive. Incorrect case, misspellings, and incorrect spacing cause the query to fail. The file format for the DOS version of CONREP and the current version of CONREP are not compatible. HPSSASCRIPTING supports only HP Smart Array controllers. Review the HPSSASCRIPTING documentation for the latest information. HPRCU is not compatible with UEFI-based HP ProLiant servers. Use CONREP instead. Booting from a USB drive key is supported only on certain HP ProLiant servers. For more information, see the HP Support Center and search Insight Foundation suite for ProLiant website:http://h20566.www2.hp.com/portal/ site/hpsc/. The IFHW and HWQUERY utilities can be used to customize the DEPLOYSERVER.CMD script for your environment. For more information about these utilities, see "Scripting Toolkit utilities" (page 16). Any changes you make to the SETBOOTORDER will take effect at the next reboot.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62

5 Troubleshooting
Troubleshooting table
Troubleshooting
Issue
Improper use of the Scripting Toolkit utilities and
modification of the CONREP data files can result in loss of
Data loss in STK
critical data. Because of the potential data-loss risk, only
experienced individuals should use the Scripting Toolkit
utilities. Before using the Scripting Toolkit, all necessary
precautions must be taken to ensure that mission-critical
systems remain online if a failure occurs.
Not all options can be configured using Scripting Toolkit
utilities. Some options must be configured manually or with
Configuring options using STK utilities
other configuration utilities, which are available online,
before they can be used with the Scripting Toolkit. For more
information on configuration, see the option documentation.
Because the
-w
argument does not capture certain types
of information, such as the administrator password, data
Input files for HPONCFG
files created with HPONCFG using the
-w
argument cannot
then be used as input files for HPONCFG, unless they are
modified first.
The script files and script segments in this guide are
provided only as examples. You must modify the scripts
Sample script files
for your environment. When creating or modifying your
own scripts, the pause command is a valuable tool to help
you determine that each step of the script is functioning as
desired.
HP ProLiant drivers must be added during Windows PE
customization to ensure the Scripting Toolkit utilities function
properly. See the readme.txt file provided.
HP ProLiant drivers
HP software requires that WMI support be enabled to
function in Windows PE properly.
WMI support
IFHW is case-sensitive. Incorrect case, misspellings, and
incorrect spacing cause the query to fail.
Non-functioning IFHW
The file format for the DOS version of CONREP and the
current version of CONREP are not compatible.
CONREP version compatibility
HPSSASCRIPTING supports only HP Smart Array controllers.
Review the HPSSASCRIPTING documentation for the latest
information.
HPSSASCRIPTING support
HPRCU is not compatible with UEFI-based HP ProLiant
servers. Use CONREP instead.
HPRCU compatibility
Booting from a USB drive key is supported only on certain
HP ProLiant servers. For more information, see the HP
Booting from a USB drive key
Support Center and search Insight Foundation suite for
ProLiant website:
h
t
tp://h20
5
6
6
.w
w
w2
.hp
.co
m/po
r
t
al/
sit
e/hp
s
c/
.
The IFHW and HWQUERY utilities can be used to
customize the DEPLOYSERVER.CMD script for your
Customizing the DEPLOYSERVER.CMD script
environment. For more information about these utilities, see
“Scripting Toolkit utilities” (page 16)
.
Any changes you make to the SETBOOTORDER will take
effect at the next reboot.
SETBOOTORDER changes
54
Troubleshooting