Alcatel OS6850-P48 User Guide - Page 196

Reloading All Switches in a Stack, Software Synchronization During a Full Reload

Get Alcatel OS6850-P48 PDF manuals and user guides View all Alcatel OS6850-P48 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 196 highlights

Reloading Switches Managing OmniSwitch 6850/6850E Series Stacks Reloading All Switches in a Stack Reloading all switches in the stack is essentially a full reboot of the virtual chassis. This can be useful in restoring a stack's previously configured topology-i.e., the stack's saved slot numbers and management roles. Note, however, that all data flow on the stack is interrupted whenever a full reboot is issued. To reset all switches in a stack use the reload all command. For example: -> reload all Important. Before issuing the reload all command, be sure to read the sections below. Understanding topics such as software synchronization and the effects of saved slot information can help users avoid unexpected results following a full stack reboot. Software Synchronization During a Full Reload If the checksum value on the stack's non-primary switches differs in any way from the checksum value on the primary switch, the primary switch automatically distributes its system and configuration software to all other switches in the stack whenever a full reload is executed. During this automatic software synchronization, system and configuration software on the secondary and idle switches is overwritten. Because the primary switch's "last known good" software is propagated to all switches, the synchronization process helps ensure effective redundancy across the stack. Effects of Saved Slot Number Information on the Reload Process Depending on the status of saved slot information across the stack, there are different slot numbering and management role scenarios that can occur following a full reboot. For this reason, checking the current stack topology before issuing a full reboot is strongly recommended. To check the current stack topology, use the show stack topology command. Refer to the OmniSwitch CLI Reference Guide for detailed command information. Possible saved slot number conditions include: • All switches have unique saved slot information • No switches in the stack have saved slot information • Some switches have saved slot information, others do not • Two or more switches have duplicate slot information All Switches Have Unique Saved Slot Information If a full reload is issued and all switches have unique slot numbers saved to their boot.slot.cfg files, the slot numbers will be assigned according to the saved slot information. The primary management role will be given to the switch with the lowest saved slot number. The secondary management role will be given to the switch with the second-lowest saved slot number. All other switches will be assigned to idle roles. An illustrated example of this method for assigning slot numbers and management roles is provided on pages 6-25 and 6-26. page 6-34 OmniSwitch 6850/6850E Series Hardware Users Guide June 2011

  • 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
Reloading Switches
Managing OmniSwitch 6850/6850E Series Stacks
page 6-34
OmniSwitch 6850/6850E Series Hardware Users Guide
June 2011
Reloading All Switches in a Stack
Reloading all switches in the stack is essentially a full reboot of the virtual chassis. This can be useful in
restoring a stack’s previously configured topology—i.e., the stack’s saved slot numbers and management
roles. Note, however, that all data flow on the stack is interrupted whenever a full reboot is issued.
To reset all switches in a stack use the
reload all
command. For example:
-> reload all
Important.
Before issuing the
reload all
command, be sure to read the sections below. Understanding
topics such as software synchronization and the effects of saved slot information can help users avoid
unexpected results following a full stack reboot.
Software Synchronization During a Full Reload
If the checksum value on the stack’s non-primary switches differs in any way from the checksum value on
the primary switch, the primary switch automatically distributes its system and configuration software to
all other switches in the stack whenever a full reload is executed.
During this automatic software synchronization, system and configuration software on the secondary and
idle switches is overwritten. Because the primary switch’s “last known good” software is propagated to all
switches, the synchronization process helps ensure effective redundancy across the stack.
Effects of Saved Slot Number Information on the Reload Process
Depending on the status of saved slot information across the stack, there are different slot numbering and
management role scenarios that can occur following a full reboot. For this reason, checking the current
stack topology before issuing a full reboot is strongly recommended. To check the current stack topology,
use the
show stack topology
command. Refer to the
OmniSwitch CLI Reference Guide
for detailed
command information.
Possible saved slot number conditions include:
•
All switches have unique saved slot information
•
No switches in the stack have saved slot information
•
Some switches have saved slot information, others do not
•
Two or more switches have duplicate slot information
All Switches Have Unique Saved Slot Information
If a full reload is issued and all switches have unique slot numbers saved to their
boot.slot.cfg
files, the
slot numbers will be assigned according to the saved slot information. The primary management role will
be given to the switch with the
lowest
saved slot number. The secondary management role will be given to
the switch with the
second-lowest
saved slot number. All other switches will be assigned to idle roles.
An illustrated example of this method for assigning slot numbers and management roles is provided on
pages
6-25
and
6-26
.