Dell PowerEdge M520 Dell PowerConnect M6220/M6348/M8024 Switches Configuration - Page 154

Saving a Configuration, Host-Specific Config File Not Found, Terminating the Auto Config Process

Page 154 highlights

Table 9-2. TFTP Request Types TFTP Server Address Available Host-specific Router Config TFTP Request Method Filename Available Yes Yes Issue a unicast request for the host-specific router config file to the TFTP server Yes No Issue a unicast request for a default network or router config file to the TFTP server No Yes Issue a broadcast request for the host-specific router config file to any available TFTP server No No Issue a broadcast request for the default network or router config file to any available TFTP server Monitoring and Completing the Auto Config Process When a switch begins bootup and there is no saved configuration, a message appears on the console informing the user that the Auto Config procedure is starting. A message also appears when Auto Config completes. The user is reminded with a message indicating that configuration must be saved in order to avoid performing Auto Config on the next reboot. When Auto Config has successfully completed, an administrator can execute a show running-config command to validate the contents of configuration. Saving a Configuration An administrator must explicitly save the downloaded configuration in non-volatile memory. This makes the configuration available for the next reboot. In the CLI, this is performed by issuing copy runningconfig startup-config command and should be done after validating the contents of saved configuration. Host-Specific Config File Not Found If the Auto Config process fails to download a configuration file, a message is logged. If a final configuration file is not downloaded, as described in Table 9-1, the Auto Config procedure continues to issue TFTP broadcast requests. The frequency of the broadcasts is once per 10 minute period. Terminating the Auto Config Process A user can terminate the Auto Config process at any time prior to the downloading of the config file. This is useful when the switch is disconnected from the network, or when the requisite configuration files are configured on TFTP servers. Termination of the Auto Config process ends further periodic requests for a host-specific file. Managing Downloaded Config Files The configuration files downloaded by Auto Config are stored in the nonvolatile memory. The files may be managed (viewed, displayed, deleted) along with files downloaded by the configuration scripting utility. 154 Utility

  • 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

154
Utility
Table 9-2.
TFTP Request Types
Monitoring and Completing the Auto Config Process
When a switch begins bootup and there is no saved configuration, a message appears on the console
informing the user that the Auto Config procedure is starting. A message also appears when Auto Config
completes. The user is reminded with a message indicating that configuration must be saved in order to
avoid performing Auto Config on the next reboot.
When Auto Config has successfully completed, an administrator can execute a
show running-config
command to validate the contents of configuration.
Saving a Configuration
An administrator must explicitly save the downloaded configuration in non-volatile memory. This makes
the configuration available for the next reboot. In the CLI, this is performed by issuing
copy running-
config startup-config
command and should be done after validating the contents of saved configuration.
Host-Specific Config File Not Found
If the Auto Config process fails to download a configuration file, a message is logged. If a final
configuration file is not downloaded, as described in Table 9-1, the Auto Config procedure continues to
issue TFTP broadcast requests. The frequency of the broadcasts is once per 10 minute period.
Terminating the Auto Config Process
A user can terminate the Auto Config process at any time prior to the downloading of the config file.
This is useful when the switch is disconnected from the network, or when the requisite configuration
files are configured on TFTP servers. Termination of the Auto Config process ends further periodic
requests for a host-specific file.
Managing Downloaded Config Files
The configuration files downloaded by Auto Config are stored in the nonvolatile memory. The files may
be managed (viewed, displayed, deleted) along with files downloaded by the configuration scripting
utility.
TFTP Server Address Available
Host-specific Router Config
Filename Available
TFTP Request Method
Yes
Yes
Issue a unicast request for the host-specific router
config file to the TFTP server
Yes
No
Issue a unicast request for a default network or router
config file to the TFTP server
No
Yes
Issue a broadcast request for the host-specific router
config file to any available TFTP server
No
No
Issue a broadcast request for the default network or
router config file to any available TFTP server