Dell PowerConnect B - MLXe 16 Hardware Installation Guide - Page 164

Dynamic configuration loading, Preparing the configuration file

Page 164 highlights

6 Dynamic configuration loading Dynamic configuration loading You can load dynamic configuration commands (these commands do not require a reload to take affect) from a file on a TFTP server into the running configuration file on the router. You can also make configuration changes off-line, then load the changes directly into the running configuration file on the router, without reloading the software. Consider the following factors when using this feature: • Use this feature only to load configuration information that does not require a software reload to take effect. For example, you cannot use this feature to change statically-configured memory (the system-max command). • Do not load port configuration information for secondary ports in a trunk group. Since all ports in a trunk group use the port configuration settings of the primary port in the group, the software cannot implement the changes to the secondary port. Preparing the configuration file Create a copy of the startup configuration file that follows the same syntax rules as the startup configuration file created by the router. When preparing this duplicate startup configuration file consider the following: • The startup configuration file is a script containing CLI configuration commands. The CLI reacts to each command entered from the file in the same way it reacts to the command if you enter it. For example, if the command results in an error message or a change to the CLI configuration level, the software responds by displaying the message, or changing the CLI level. • The software retains the running configuration file currently on the router, and changes this file only by adding new commands from the startup configuration file. If the running configuration already contains a command that is also in the startup configuration file you are loading, the CLI rejects the new command as a duplicate and displays an error message. For example, if the running configuration file already contains a command that configures ACL 1, the software rejects ACL 1 in the startup configuration file, and displays a message that ACL 1 is already configured. • The duplicate startup configuration file can contain global CONFIG commands or configuration commands for interfaces, routing protocols, and so on. You cannot enter User EXEC or Privileged EXEC commands. • Since the default CLI configuration level in a startup configuration file is the global CONFIG level, the first command in the file must be a global CONFIG command or "!". The ! (exclamation point) character means "return to the global CONFIG level". NOTE You can enter text following "! "as a comment. However, the "!" is not a comment marker. It returns the CLI to the global configuration level. NOTE The CLI switches to the global CONFIG level if you load the configuration as a startup configuration instead of the running configuration (using the copy tftp startup-config command or ncopy tftp startup-config command). 152 PowerConnect B-MLXe Hardware Installation Guide 53-1002111-01

  • 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

152
PowerConnect B-MLXe Hardware Installation Guide
53-1002111-01
Dynamic configuration loading
6
Dynamic configuration loading
You can load dynamic configuration commands (these commands do not require a reload to take
affect) from a file on a TFTP server into the running configuration file on the router. You can also
make configuration changes off-line, then load the changes directly into the running configuration
file on the router, without reloading the software.
Consider the following factors when using this feature:
Use this feature only to load configuration information that does not require a software reload
to take effect. For example, you cannot use this feature to change statically-configured
memory (the
system-max
command).
Do not load port configuration information for secondary ports in a trunk group. Since all ports
in a trunk group use the port configuration settings of the primary port in the group, the
software cannot implement the changes to the secondary port.
Preparing the configuration file
Create a copy of the startup configuration file that follows the same syntax rules as the startup
configuration file created by the router. When preparing this duplicate startup configuration file
consider the following:
The startup configuration file is a script containing CLI configuration commands. The CLI reacts
to each command entered from the file in the same way it reacts to the command if you enter
it. For example, if the command results in an error message or a change to the CLI
configuration level, the software responds by displaying the message, or changing the CLI
level.
The software retains the running configuration file currently on the router, and changes this file
only by adding new commands from the startup configuration file. If the running configuration
already contains a command that is also in the startup configuration file you are loading, the
CLI rejects the new command as a duplicate and displays an error message. For example, if
the running configuration file already contains a command that configures ACL 1, the software
rejects ACL 1 in the startup configuration file, and displays a message that ACL 1 is already
configured.
The duplicate startup configuration file can contain global CONFIG commands or configuration
commands for interfaces, routing protocols, and so on. You cannot enter User EXEC or
Privileged EXEC commands.
Since the default CLI configuration level in a startup configuration file is the global CONFIG
level, the first command in the file must be a global CONFIG command or “!”. The !
(exclamation point) character means “return to the global CONFIG level”.
NOTE
You can enter text following “! “as a comment. However, the “!” is not a comment marker. It
returns the CLI to the global configuration level.
NOTE
The CLI switches to the global CONFIG level if you load the configuration as a startup
configuration instead of the running configuration (using the
copy tftp startup-config
<
ip-addr
>
<
filename
> command or
ncopy tftp
<
ip-addr
> <
from-name
>
startup-config
command).