Alcatel OS6855-24 User Guide - Page 153

Important Note., Redundant Management Module Failover Three or More Switches, for more information.

Page 153 highlights

Managing OmniSwitch 6855 Series Stacks Roles Within the Stack Important Note. For management module redundancy to work effectively, the software on all switches operating in the stack must be synchronized at all times. Refer to "Synchronizing Switches in a Stack" on page 7-37 for more information. Primary Secondary Idle Idle 1 A stack of four OmniSwitches is operating normally. The stack consists of a primary module, secondary module, and two elements operating in idle status. (The software on all elements in the stack is synchronized.) ! Offline Secondary Idle Idle 2 The primary management module in the stack fails or is taken offline (e.g., powered off or rebooted by the user). Offline Primary Secondary Idle 3 The switch operating as the secondary management module immediately takes over the primary role. Meanwhile, the adjacent switch-previously operating in idle status-now assumes the secondary management role. Idle Primary Secondary Idle 4 If the switch that failed or was taken offline comes back online, it will assume an idle role in the stack. In other words, it will act essentially as an NI module in the virtual chassis, passing traffic via its Ethernet. Redundant Management Module Failover (Three or More Switches) OmniSwitch 6855 Series Hardware Users Guide September 2011 page 7-5

  • 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

Managing OmniSwitch 6855 Series Stacks
Roles Within the Stack
OmniSwitch 6855 Series Hardware Users Guide
September 2011
page 7-5
Important Note.
For management module redundancy to work effectively, the software on all switches
operating in the stack must be synchronized at all times. Refer to
“Synchronizing Switches in a Stack” on
page 7-37
for more information.
Redundant Management Module Failover (Three or More Switches)
Secondary
Primary
Idle
Idle
Secondary
Offline
Idle
Idle
Primary
Offline
Secondary
Idle
!
Primary
Idle
Secondary
Idle
A stack of four OmniSwitches is operating normally.
The stack consists of a primary module, secondary
module, and two elements operating in idle status. (The
software on all elements in the stack is synchronized.)
The primary management module in the stack fails or is
taken offline (e.g., powered off or rebooted by the user).
The switch operating as the secondary management module
immediately takes over the primary role. Meanwhile, the
adjacent switch—previously operating in idle status—now
assumes the secondary management role.
If the switch that failed or was taken offline comes back
online, it will assume an idle role in the stack. In other
words, it will act essentially as an NI module in the virtual
chassis, passing traffic via its Ethernet.
1
2
3
4