Netgear CSM4532 Software Administration Manual - Page 164

Monitoring and Completing the DHCP Auto Install Process

Page 164 highlights

6.2.1.3. Obtaining the Configuration File If the DHCP OFFER identifies a configuration file, either as option 67 or in the file field of the DHCP header, the switch attempts to download the configuration file. Note: The configuration file is required to have a file type of *.cfg. The TFTP client makes three unicast requests. If the unicast attempts fail, or if the DHCP OFFER did not specify a TFTP server address, the auto install process will fail. 6.2.2. Monitoring and Completing the DHCP Auto Install Process When the switch boots and triggers an Auto Install, a message is written to the buffered log. After the process completes, the Auto Install process writes a log message. You can use the show logging buffered command to view information about the process. Additionally, while the Auto Install is running, you can issue the show autoinstall command to view information about the current Auto Install state. When Auto Install has successfully completed, you can execute a show running-config command to validate the contents of configuration. 6.2.2.1. Saving a Configuration The Auto Install feature includes an AutoSave feature that allows the downloaded configuration to be automatically saved; AutoSave is enabled by default. This makes the configuration available for the next reboot. In the CLI, this is performed by issuing a copy running-config startup-config command and should be done after validating the contents of saved configuration. 6.2.2.2. Stopping and Restarting the Auto Install Process You can terminate the Auto Install process at any time before the configuration file is downloaded. This is useful when the switch is disconnected from the network. Termination of the Auto Install process ends further periodic requests for a host-specific file. 6.2.2.3. Managing Downloaded Configuration Files The configuration files downloaded to the switch by Auto Install are stored in the nonvolatile memory as .scr files. The files may be managed (viewed or deleted) along with files downloaded by the configuration scripting utility. If the Auto Install persistent mode is enabled (boot-system host autoinstall) and the switch reboots, the .scr configuration file created by the switch in the non-volatile memory is overwritten during the Auto Install process. To ensure that the downloaded configuration file is used during the next boot cycle, make sure that the Auto Install persistent mode is disabled (no boot-system host autoinstall) and save the configuration (copy running-config startup-config). NETGEAR M4500 Series Switches Software Administration Manual 164

  • 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

NETGEAR M4500 Series Switches Software Administration Manual
164
6.2.1.3.
Obtaining the Configuration File
If the DHCP OFFER identifies a configuration file, either as option 67 or in the
file
field of the DHCP header, the
switch attempts to download the configuration file.
Note:
The configuration file is required to have a file type of *.cfg.
The TFTP client makes three unicast requests. If the unicast attempts fail, or if the DHCP OFFER did not specify a
TFTP server address, the auto install process will fail.
6.2.2.
Monitoring and Completing the DHCP Auto Install Process
When the switch boots and triggers an Auto Install, a message is written to the buffered log. After the process
completes, the Auto Install process writes a log message. You can use the
show logging buffered
command
to view information about the process.
Additionally, while the Auto Install is running, you can issue the
show autoinstall
command to view
information about the current Auto Install state.
When Auto Install has successfully completed, you can execute a
show running-config
command to validate
the contents of configuration.
6.2.2.1.
Saving a Configuration
The Auto Install feature includes an AutoSave feature that allows the downloaded configuration to be
automatically saved; AutoSave is enabled by default. This makes the configuration available for the next
reboot. In the CLI, this is performed by issuing a
copy running-config startup-config
command and should
be done after validating the contents of saved configuration.
6.2.2.2.
Stopping and Restarting the Auto Install Process
You can terminate the Auto Install process at any time before the configuration file is downloaded. This is
useful when the switch is disconnected from the network. Termination of the Auto Install process ends further
periodic requests for a host-specific file.
6.2.2.3.
Managing Downloaded Configuration Files
The configuration files downloaded to the switch by Auto Install are stored in the nonvolatile memory as
.scr
files. The files may be managed (viewed or deleted) along with files downloaded by the configuration scripting
utility. If the Auto Install persistent mode is enabled (
boot-system host autoinstall
) and the switch reboots,
the
.scr
configuration file created by the switch in the non-volatile memory is overwritten during the Auto
Install process.
To ensure that the downloaded configuration file is used during the next boot cycle, make sure that the Auto
Install persistent mode is disabled (
no boot-system host autoinstall
) and save the configuration (
copy
running-config startup-config
).