Dell PowerEdge R830 Integrated Remote Access Controller 8 Version 2.70.70.70 U - Page 44

Auto Config sequence, DHCP options, Related concepts

Page 44 highlights

NOTE: To set the workload profile along with other attributes using SCP, ensure that you run the SCP import job twice to get the correct configuration changes. NOTE: If none of these files are on the network share, then the server configuration profile import job is marked as failed for file not found. For iDRAC firmware 2.70.70.70 and later versions, JSON format profile files are supported. The following file names will be used, if the Filename parameter is not present: • "-config.xml" (Example: CDVH7R1-config.xml) • "

  • 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
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298

NOTE:
To set the workload profile along with other attributes using SCP, ensure that you run the SCP import job twice
to get the correct configuration changes.
NOTE:
If none of these files are on the network share, then the server configuration profile import job is marked as
failed for file not found.
For iDRAC firmware 2.70.70.70 and later versions, JSON format profile files are supported. The following file names will be used, if the
Filename parameter is not present:
"<service tag>-config.xml" (Example: CDVH7R1-config.xml)
"<model number)-config.xml" (Example: R630-config.xml)
"config.xml"
"<service tag>-config.json" (Example: CDVH7R1-config.json)
"<model number)-config.json" (Example: R630-config.json)
"config.json"
Related concepts
Auto Config sequence
DHCP options
Related tasks
Enabling Auto Config using iDRAC web interface
Enabling Auto Config using RACADM
Auto Config sequence
1.
Create or modify the SCP file that configures the attributes of Dell servers.
2.
Place the SCP file in a share location that is accessible by the DHCP server and all the Dell servers that are assigned IP address from
the DHCP server.
3.
Specify the SCP file location in vendor-option 43 field of DHCP server.
4.
The iDRAC as part of acquiring IP address advertises vendor class identifier iDRAC. (Option 60)
5.
The DHCP server matches the vendor class to the vendor option in the
dhcpd.conf
file and sends the SCP file location and, if
specified the SCP file name to the iDRAC.
6.
The iDRAC processes the SCP file and configures all the attributes listed in the file
DHCP options
DHCPv4 allows many globally defined parameters to be passed to the DHCP clients. Each parameter is known as a DHCP option. Each
option is identified with an option tag, which is a 1-byte value. Option tags 0 and 255 are reserved for padding and end of options,
respectively. All other values are available for defining options.
The DHCP Option 43 is used to send information from the DHCP server to the DHCP client. The option is defined as a text string. This
text string is set to contain the values of the XML filename, share location and the credentials to access the location. For example,
option myname code 43 = text;
subnet 192. 168.0.0 netmask 255.255.255.0 {
# default gateway
option routers 192.168.0.1;
option subnet-mask 255.255.255.0;
option nis-domain
"domain.org";
option domain-name "domain.org";
option domain-name-servers 192.168.1.1;
option time-offset -18000; #Eastern Standard Time
option vendor-class-identifier "iDRAC";
set vendor-string = option vendor-class-identifier;
option myname "-f system_config.xml -i 192.168.0.130 -u
user
-p
password
-n cifs -s 2 -d
0 -t 500";
where, -i is the location of the Remote File Share and –f is the file name in the string along with the credentials to the Remote File Share.
The DHCP Option 60 identifies and associates a DHCP client with a particular vendor. Any DHCP server configured to take action based
on a client’s vendor ID should have Option 60 and Option 43 configured. With Dell PowerEdge servers, the iDRAC identifies itself with
44
Setting up managed system and management station