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

Performing a Hitless OS upgrade, Performing an image coherence check

Get Dell PowerConnect B - MLXe 16 PDF manuals and user guides View all Dell PowerConnect B - MLXe 16 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 149 highlights

Performing a Hitless OS upgrade 6 Performing a Hitless OS upgrade NOTE Note: Hitless upgrades are supported for upgrades within a major release (for example, 05.1.00 to 05.1.00a) but are not supported for upgrades from one major release to another (for example 5.1.0 to 5.2.0.) Some features and protocols are not supported for hitless upgrade. Before you perform a hitless upgrade, refer to "Hitless OS Upgrade" for more information. A Hitless OS Upgrade loads from the primary and secondary images on the management modules. To do a Hitless OS Upgrade, perform the following steps: 1. Copy the Multi-Service IronWare software images to the primary and secondary flash on the active and standby management modules and on interface modules. 2. Set up a console connection to both the active and standby management modules. These connections can be serial console sessions or sessions established through Telnet or SSH. 3. Enter thehitless-reload command at the console of the active management module. hitless-reload mp [primary | secondary] | lp [primary | secondary] The mp parameter specifies that the image will be copied to the management module. The lp parameter specifies that the image will be reloaded to the interface module. Performing an image coherence check When you enter the reload-check command, Multi-Service IronWare software performs a coherence check to ensure that compatible versions of the software are installed on management and interface modules, and that all interface module FPGAs are compatible with the current software version. If incompatible images are discovered, a warning message is sent. The image coherence check is performed in the following sequence: 1. Check management module and interface module application images for compatibility • Checks for compatibly of interface module application images on management and interface modules. • Checks for compatibly of interface module monitor images on management and interface modules. 2. Checks the interface module monitor image on the management module and all interface modules 3. Checks the management module monitor image for compatibility with the management module application image. 4. Checks the interface module monitor image for compatibility the management and interface module application images. 5. Checks all interface module FPGAs for compatibility with the application image. FPGAs include CPP, PBIF, XGMAC, STATS, XPP-OC, PBIF-OC, STATS-OC. If step 1 does not succeed, verification is stopped and a warning is issued. If step 1 succeeds, the rest of the checks are conducted in parallel. PowerConnect B-MLXe Hardware Installation Guide 137 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
PowerConnect B-MLXe Hardware Installation Guide
137
53-1002111-01
Performing a Hitless OS upgrade
6
Performing a Hitless OS upgrade
NOTE
Note:
Hitless upgrades are supported for upgrades
within
a major release (for example, 05.1.00 to
05.1.00a) but are
not supported
for upgrades from one major release to another (for example 5.1.0
to 5.2.0.)
Some features and protocols are not supported for hitless upgrade. Before you perform a hitless
upgrade, refer to “Hitless OS Upgrade” for more information.
A Hitless OS Upgrade loads from the primary and secondary images on the management modules.
To do a Hitless OS Upgrade, perform the following steps:
1.
Copy the Multi-Service IronWare software images to the primary and secondary flash on the
active and standby management modules and on interface modules.
2.
Set up a console connection to both the active and standby management modules. These
connections can be serial console sessions or sessions established through Telnet or SSH.
3.
Enter the
hitless-reload
command at the console of the active management module.
hitless-reload mp
[
primary
|
secondary
] |
lp
[
primary
|
secondary
]
The
mp
parameter specifies that the image will be copied to the
management module
.
The
lp
parameter specifies that the image will be reloaded to the
interface module.
Performing an image coherence check
When you enter the
reload-check
command, Multi-Service IronWare software performs a
coherence check to ensure that compatible versions of the software are installed on management
and interface modules, and that all interface module FPGAs are compatible with the current
software version. If incompatible images are discovered, a warning message is sent.
The image coherence check is performed in the following sequence:
1.
Check management module and interface module application images for compatibility
•
Checks for compatibly of interface module application images on management and
interface modules.
•
Checks for compatibly of interface module monitor images on management and interface
modules.
2.
Checks the interface module monitor image on the management module and all interface
modules
3.
Checks the management module monitor image for compatibility with the management
module application image.
4.
Checks the interface module monitor image for compatibility the management and interface
module application images.
5.
Checks all interface module FPGAs for compatibility with the application image. FPGAs include
CPP, PBIF, XGMAC, STATS, XPP-OC, PBIF-OC, STATS-OC.
If step 1 does not succeed, verification is stopped and a warning is issued. If step 1 succeeds, the
rest of the checks are conducted in parallel.