Tripp Lite B098048 Owners Manual for B093- B097- and B098-Series Console Serve - Page 34

Configuration over DHCP ZTP

Page 34 highlights

3. System Configuration 3.6.6 Static Routes Firmware 3.4 and later support static routes, which provide a quick way to route data from one subnet to a different subnet. You can hard code a path that specifies to the console server/router to get to a certain subnet by using a certain path. This may be useful for remotely accessing various subnets at a remote site when being accessed using the cellular OOB connection. To add to the static route to the system's route table: • Select the Route Settings tab on the System: IP General Settings menu. • Enter a meaningful Route Name for the route. • In the Destination Network/Host field, enter the IP address of the destination network/host that the route provides access to. • Enter a value in the Destination netmask field that identifies the destination network or host. Any number between 0 and 32 can be used. A subnet mask of 32 identifies a host route. • Enter Route Gateway with the IP address of a router that will route packets to the destination network. This field may be left blank. • Select the Interface to use to reach the destination. This field may be left as None. • Enter a value in the Metric field that represents the metric of this connection. This generally has to be set only if two or more routes conflict or have overlapping targets. Any number equal to or greater than 0. • Click Apply. Note: The route details page provides a list of network interfaces and modems to which a route can be bound. In the case of a modem, the route will be attached to any dial-up session, which is established via that device. A route can be specified with a gateway, an interface or both. If the specified interface is not active for whatever reason, then the routes configured for that interface will not be active. 3.7 Configuration over DHCP (ZTP) Configuration-over-DHCP is available for all Tripp Lite console managers running firmware release 3.16 or later. With this feature, Tripp Lite devices can be provisioned during their initial boot from a DHCP server. Provisioning on untrusted networks can be facilitated by providing keys on a USB flash drive. Preparation The typical steps for configuration over a trusted network are: • Manually configure a same-model Tripp Lite device. • Save its configuration as a backup (.opg) file. • Select System > Configuration Backup > Remote Backup. • Click Save Backup. 34

  • 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

34
3.6.6 Static Routes
Firmware 3.4 and later support static routes, which provide a quick way to route data from one subnet to a different subnet.
You can hard code a path that specifies to the console server/router to get to a certain subnet by using a certain path.
This may be useful for remotely accessing various subnets at a remote site when being accessed using the cellular OOB
connection.
To add to the static route to the system’s route table:
• Select the
Route Settings
tab on the
System: IP General Settings
menu.
• Enter a meaningful
Route Name
for the route.
• In the
Destination Network/Host
field, enter the IP address of the destination network/host that the route provides access
to.
• Enter a value in the
Destination netmask
field that identifies the destination network or host. Any number between 0 and
32 can be used. A subnet mask of 32 identifies a host route.
• Enter
Route Gateway
with the IP address of a router that will route packets to the destination network. This field may be
left blank.
• Select the
Interface
to use to reach the destination. This field may be left as
None
.
• Enter a value in the
Metric
field that represents the metric of this connection. This generally has to be set only if two or
more routes conflict or have overlapping targets. Any number equal to or greater than 0.
• Click
Apply
.
Note:
The route details page provides a list of network interfaces and modems to which a route can be bound. In the case of a modem, the
route will be attached to any dial-up session, which is established via that device. A route can be specified with a gateway, an interface or
both. If the specified interface is not active for whatever reason, then the routes configured for that interface will not be active.
3.7 Configuration over DHCP (ZTP)
Configuration-over-DHCP is available for all Tripp Lite console managers running firmware release 3.16 or later. With this
feature, Tripp Lite devices can be provisioned during their initial boot from a DHCP server. Provisioning on untrusted networks
can be facilitated by providing keys on a USB flash drive.
Preparation
The typical steps for configuration over a trusted network are:
• Manually configure a same-model Tripp Lite device.
• Save its configuration as a backup (.opg) file.
• Select
System > Configuration Backup > Remote Backup
.
• Click
Save Backup
.
3. System Configuration