HP Xw460c HP Integrated Lights-Out 2 User Guide for Firmware 1.75 and 1.77 - Page 17

Management Interface Driver., HP Integrated Lights-Out Management Processor Scripting and Command

Page 17 highlights

To access iLO 2 after connecting it to the network, the management processor must acquire an IP address and subnet mask using either a dynamic or static process: o Dynamic IP address is set by default. iLO 2 obtains the IP address and subnet mask from DNS/DHCP servers. This method is the simplest. o Static IP address is used to configure a static IP address if DNS/DHCP servers are not available on the network. A static IP address can be configured in iLO 2 using the RBSU. If using a static IP, you must have an IP address before starting iLO 2 setup. 3. What access security is required and what user accounts and privileges are needed? iLO 2 provides several options to control user access. You must select one of the following methods to prevent unauthorized access to corporate IT assets: o Local accounts with up to 12 user names and passwords can be stored on iLO 2. This is ideal for small environments such as labs and small- and medium-sized businesses. o Directory services use the corporate directory (Microsoft® Active Directory or Novell eDirectory) to manage iLO 2 user access. This is ideal for environments with a large number of frequently changing users. If you plan to use Directory services leave at least one local account enabled for alternate access. For more information about iLO 2 access security see the section, "Security (on page 41)." 4. How do you want to configure iLO 2? iLO 2 supports various interfaces for configuration and operation. This guide discusses the following interfaces: o iLO 2 RBSU ("Setting up iLO 2 using iLO 2 RBSU" on page 20) can be used when the system environment does not use DHCP, DNS, or WINS. o Browser-based setup ("Setting up iLO 2 using the browser-based option" on page 20) can be used when you can connect to iLO 2 on the network using a browser. This method can also reconfigure a previously configured iLO 2. o SMASH CLP can be used when a command line is accessible through telnet, SSH, or physical serial port. See the HP Integrated Lights-Out Management Processor Scripting and Command Line Resource Guide. The iLO 2 default settings enable you to use most features with no additional configuration. However, the extensive configuration flexibility of iLO 2 enables customization for multiple enterprise environments. See the section, "Configuring iLO 2 (on page 24)" for all available options. For advanced setup of multiple iLO 2 management processors using scripting commands, the following methods are available. Scripts are text files written in an XML-based scripting language called RIBCL. You can use RIBCL scripts to configure iLO 2 on the network, during initial deployment, or from an already deployed host. Each method is described in the HP Integrated Lights-Out Management Processor Scripting and Command Line Resource Guide. • CPQLOCFG is a Microsoft® Windows® utility that sends RIBCL scripts to iLO 2 over the network. • HPONCFG is a local online scripted-setup utility that runs on the host and passes RIBCL scripts to the local iLO 2. There are Windows® and Linux versions of this utility, which require the HP iLO 2 Management Interface Driver. • Perl is a scripting language that can be used from Linux clients to send RIBCL scripts to iLO 2 over the network. iLO 2 setup 17

  • 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
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235

iLO 2 setup 17
To access iLO 2 after connecting it to the network, the management processor must acquire an IP
address and subnet mask using either a dynamic or static process:
o
Dynamic IP address is set by default. iLO 2 obtains the IP address and subnet mask from
DNS/DHCP servers. This method is the simplest.
o
Static IP address is used to configure a static IP address if DNS/DHCP servers are not available
on the network. A static IP address can be configured in iLO 2 using the RBSU.
If using a static IP, you must have an IP address before starting iLO 2 setup.
3.
What access security is required and what user accounts and privileges are needed?
iLO 2 provides several options to control user access. You must select one of the following methods
to prevent unauthorized access to corporate IT assets:
o
Local accounts with up to 12 user names and passwords can be stored on iLO 2. This is ideal for
small environments such as labs and small- and medium-sized businesses.
o
Directory services use the corporate directory (Microsoft® Active Directory or Novell eDirectory)
to manage iLO 2 user access. This is ideal for environments with a large number of frequently
changing users. If you plan to use Directory services leave at least one local account enabled for
alternate access.
For more information about iLO 2 access security see the section, "Security (on page
41
)."
4.
How do you want to configure iLO 2?
iLO 2 supports various interfaces for configuration and operation. This guide discusses the following
interfaces:
o
iLO 2 RBSU ("
Setting up iLO 2 using iLO 2 RBSU
" on page
20
) can be used when the system
environment does not use DHCP, DNS, or WINS.
o
Browser-based setup ("
Setting up iLO 2 using the browser-based option
" on page
20
) can be
used when you can connect to iLO 2 on the network using a browser. This method can also
reconfigure a previously configured iLO 2.
o
SMASH CLP can be used when a command line is accessible through telnet, SSH, or physical
serial port. See the
HP Integrated Lights-Out Management Processor Scripting and Command
Line Resource Guide
.
The iLO 2 default settings enable you to use most features with no additional configuration. However, the
extensive configuration flexibility of iLO 2 enables customization for multiple enterprise environments. See
the section, "Configuring iLO 2 (on page
24
)" for all available options.
For advanced setup of multiple iLO 2 management processors using scripting commands, the following
methods are available. Scripts are text files written in an XML-based scripting language called RIBCL. You
can use RIBCL scripts to configure iLO 2 on the network, during initial deployment, or from an already
deployed host. Each method is described in the
HP Integrated Lights-Out Management Processor Scripting
and Command Line Resource Guide.
CPQLOCFG is a Microsoft® Windows® utility that sends RIBCL scripts to iLO 2 over the network.
HPONCFG is a local online scripted-setup utility that runs on the host and passes RIBCL scripts to the
local iLO 2. There are Windows® and Linux versions of this utility, which require the HP iLO 2
Management Interface Driver.
Perl is a scripting language that can be used from Linux clients to send RIBCL scripts to iLO 2 over
the network.