Tripp Lite B0930042E4U Owners Manual for B093- B097- and B098-Series Console S - Page 268

Bulk Provisioning, 15 Zero Touch Provisioning

Page 268 highlights

15. Advanced Configuration 15.14 Bulk Provisioning Tripp Lite devices include wizard scripts to facilitate configuration and deployment en masse. These wizards operate at the command line level, so knowledge of the Linux command line and shell scripting is useful, but not necessary. Rather, they aim to be sufficiently user-friendly for remote hands to manage. This bulk-provisioning feature is supported by firmware version 3.9.1 or later. The basic steps are: 1. Configure an individual "golden Primary" appliance with the baseline configuration shared by all Tripp Lite devices. This may be a minimal configuration if the installs are quite diverse, or a complete configuration when dealing with replicated installs. 2. Use make-template to turn the golden Primary's active configuration into a template configuration that may be applied to other devices. 3. Create an OPG backup of the templated golden Primary appliance. 4. Restore this configuration to each target devices via the CLI, web UI or using a USB thumb drive. 5. Login via the CLI to complete configuration using setup-wizard. 15.15 Zero Touch Provisioning Zero Touch Provisioning (ZTP) was introduced with firmware release 3.15.1 to allow Tripp Lite devices to be provisioned during their initial boot from a DHCP server. 15.15.1 Preparation These are typical steps for configuration over a trusted network: 1. Configure a same-model Tripp Lite device. 2. Optionally use the Bulk Provisioning wizard scripts to remove any appliance-specific settings (i.e. create a template configuration). Refer to 15.14 Bulk Provisioning for more information. 3. Save the configuration as a Tripp Lite backup (.opg) file under System: Configuration Backup in the web UI, or via config -e in the CLI. Alternately, you can save the XML configuration as a file ending in .xml. 4. Publish the .opg or.xml file on a fileserver that understands one of the HTTPS, HTTP, FTP or TFTP protocols. 5. Configure your DHCP server to include a "vendor specific" option for Tripp Lite devices. The option text should be a URL to the location of the .opg or .xml file. The option text should not exceed 250 characters in length. It must end in either .opg or .xml. 6. Connect a new Tripp Lite device (either at defaults from the factory, or config erased) to the network. Apply power. 7. It may take up to 5 minutes for the device to find the .opg or .xml file via DHCP, download, install file and reboot. 15.15.2 Example ISC DHCP Server Configuration The following is an example of an ISC DHCP server configuration fragment for serving an .opg configuration image: option space tripp-lite code width 1 length width 1; option tripp-lite.config-url code 1 = text; class " tripp-lite -ztp" { match if option vendor-class-identifier ~~ "^Tripp Lite /"; vendor-option-space tripp-lite; option tripp-lite.config-url "https://example.com/opg/${class}.opg"; } For other DHCP servers, please consult their documentation on specifying "Vendor Specific" option fields. We use sub-option 1 to hold the URL text. 268

  • 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

268
15. Advanced Configuration
15.14 Bulk Provisioning
Tripp Lite devices include wizard scripts to facilitate configuration and deployment en masse. These wizards operate at the
command line level, so knowledge of the Linux command line and shell scripting is useful, but not necessary. Rather, they aim
to be sufficiently user-friendly for remote hands to manage. This bulk-provisioning feature is supported by firmware version
3.9.1 or later.
The basic steps are:
1. Configure an individual “
golden Primary
” appliance with the baseline configuration shared by all Tripp Lite devices. This
may be a minimal configuration if the installs are quite diverse, or a complete configuration when dealing with replicated
installs.
2. Use make-template to turn the golden Primary’s active configuration into a template configuration that may be applied to
other devices.
3. Create an OPG backup of the templated golden Primary appliance.
4. Restore this configuration to each target devices via the CLI, web UI or using a USB thumb drive.
5. Login via the CLI to complete configuration using
setup-wizard
.
15.15 Zero Touch Provisioning
Zero Touch Provisioning (ZTP) was introduced with firmware release 3.15.1 to allow Tripp Lite devices to be provisioned during
their initial boot from a DHCP server.
15.15.1 Preparation
These are typical steps for configuration over a trusted network:
1. Configure a same-model Tripp Lite device.
2. Optionally use the Bulk Provisioning wizard scripts to remove any appliance-specific settings (i.e. create a template
configuration). Refer to
15.14 Bulk Provisioning
for more information.
3. Save the configuration as a Tripp Lite backup (.opg) file under
System: Configuration Backup
in the web UI, or via config
-e in the CLI. Alternately, you can save the XML configuration as a file ending in
.xml
.
4. Publish the .opg or.xml file on a fileserver that understands one of the HTTPS, HTTP, FTP or TFTP protocols.
5. Configure your DHCP server to include a “vendor specific” option for Tripp Lite devices. The option text should be a URL to
the location of the .opg or .xml file. The option text should not exceed 250 characters in length. It must end in either .opg
or .xml.
6. Connect a new Tripp Lite device (either at defaults from the factory, or config erased) to the network. Apply power.
7. It may take up to 5 minutes for the device to find the .opg or .xml file via DHCP, download, install file and reboot.
15.15.2 Example ISC DHCP Server Configuration
The following is an example of an ISC DHCP server configuration fragment for serving an .opg configuration image:
option space tripp-lite code width 1 length width 1;
option tripp-lite.config-url code 1 = text;
class “ tripp-lite -ztp” {
match if option vendor-class-identifier ~~ “^Tripp Lite /”;
vendor-option-space tripp-lite;
option tripp-lite.config-url “https://example.com/opg/${class}.opg”;
}
For other DHCP servers, please consult their documentation on specifying “Vendor Specific” option fields. We use sub-option 1
to hold the URL text.