Dell PowerConnect B-RX16 Installation Guide - Page 201

Loading and saving configuration files, Setting up consoles, Executing the hitless upgrade command

Page 201 highlights

Loading and saving configuration files 7 Setting up consoles Hitless Layer 2 OS upgrade is executed at the active management module. During the process of upgrading the image, control of the router shifts to the standby management module. For this reason, you need to have management sessions enabled on both the active and the standby management modules. When the reload is complete, the management module that was in the standby condition at the beginning will be in the active state. If you want the original management module to be active, you must manually fail-over control to it. Executing the hitless upgrade command To begin the process of a hitless upgrade, use the following command: BigIron RX(config)# hitless-reload mp primary lp primary Syntax: hitless-reload mp [primary | secondary ] lp [primary | secondary] The mp parameter specifies that the management module will be reloaded with either the primary or secondary image as directed. The lp parameter specifies that the interface module will be reloaded with either the primary or secondary image as directed. Verify the new software image Enter the show version command at any CLI level, and verify that all management and interface modules are running the new software image version. Loading and saving configuration files For easy configuration management, the BigIron RX Series switch supports both the download and upload of configuration files between the switch and a TFTP server on the network. You can also copy the startup configuration file locally between the management module's code flash and a PCMCIA flash card inserted in the management module's slot 1 or 2. You can upload either the startup configuration file or the running configuration to the TFTP server, code flash, or a flash card for backup and use in booting the system. • Startup configuration file - This file (startup-config) contains the configuration information that is currently saved in the management module's code flash. To display this file, enter the show configuration command at any CLI prompt. • Running configuration - This active configuration is in the system RAM but not yet saved to code flash. These changes could represent a short-term requirement or general configuration change. To display this configuration, enter the show running-config or write terminal command at any CLI prompt. Each device can have one startup configuration file and one running configuration. The startup configuration file is shared by both flash modules. The running configuration resides in DRAM. BigIron RX Installation Guide 189 53-1001811-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
  • 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

BigIron RX Installation Guide
189
53-1001811-01
Loading and saving configuration files
7
Setting up consoles
Hitless Layer 2 OS upgrade is executed at the active management module. During the process of
upgrading the image, control of the router shifts to the standby management module. For this
reason, you need to have management sessions enabled on both the active and the standby
management modules. When the reload is complete, the management module that was in the
standby condition at the beginning will be in the active state. If you want the original management
module to be active, you must manually fail-over control to it.
Executing the hitless upgrade command
To begin the process of a hitless upgrade, use the following command:
BigIron RX(config)# hitless-reload mp primary lp primary
Syntax:
hitless-reload mp [primary | secondary ] lp [primary | secondary]
The
mp
parameter specifies that the management module will be reloaded with either the
primary
or
secondary
image as directed.
The
lp
parameter specifies that the interface module will be reloaded with either the
primary
or
secondary
image as directed.
Verify the new software image
Enter the
show version
command at any CLI level, and verify that all management and interface
modules are running the new software image version.
Loading and saving configuration files
For easy configuration management, the BigIron RX Series switch supports both the download and
upload of configuration files between the switch and a TFTP server on the network. You can also
copy the startup configuration file locally between the management module’s code flash and a
PCMCIA flash card inserted in the management module’s slot 1 or 2.
You can upload either the startup configuration file or the running configuration to the TFTP server,
code flash, or a flash card for backup and use in booting the system.
Startup configuration file
– This file (startup-config) contains the configuration information
that is currently saved in the management module’s code flash. To display this file, enter the
show configuration
command at any CLI prompt.
Running configuration
– This active configuration is in the system RAM but not yet saved to
code flash. These changes could represent a short-term requirement or general configuration
change. To display this configuration, enter the
show running-config
or
write terminal
command at any CLI prompt.
Each device can have one startup configuration file and one running configuration. The startup
configuration file is shared by both flash modules. The running configuration resides in DRAM.