Netgear GSM7248v1 GSM7224 Administration manual - Page 135

Merging Two Operational Stacks, Preconfiguration, Upgrading Firmware, member

Get Netgear GSM7248v1 - ProSafe 48 Port Layer 2 Gigabit L2 Ethernet Switch PDF manuals and user guides View all Netgear GSM7248v1 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 135 highlights

NETGEAR 7000 Series Managed Switch Administration Guide Version 6.0 Merging Two Operational Stacks It is strongly recommended that two functioning stacks (each having an independent master) not be merged simply by the reconnection of stack cables. That process may result in a number of unpredictable results and should be avoided. 1. Always power off all units in one stack before connecting into another stack. 2. Add the units as a group by unplugging one stacking cable in the operational stack and physically connecting all unpowered units at that point. 3. Completely cable the stacking connections, making sure the redundant link is also in place. 4. Then, power up each unit, one at a time, by following "Adding a Unit to an Operating Stack". Preconfiguration All configuration on the stack except unit numbers is stored on the management unit. This means that a stack unit may be replaced with another device of the same type without having to reconfigure the switch. Unit numbers are stored independently on each switch, so that after power cycling the stack the units always come back with the same unit numbers. The unit type associated with each unit number may be learned by the management unit automatically as the units are connected or preconfigured by the administrator. 1. Issue the member command to preconfigure a unit. Supported unit types are shown by the show supported switchtype command. 2. Next, configure the unit you just defined with configuration commands, just as if the unit were physically present. 3. Ports for the preconfigured unit come up in "detached" state and can be seen with the show port all command. The detached ports may now be configured for VLAN membership and any other port-specific configuration. 4. After a unit type is preconfigured for a specific unit number, attaching a unit with different unit type for this unit number causes the switch to report an error. The show switch command indicates "config mismatch" for the new unit and the ports on that unit don't come up. To resolve this situation the customer may change the unit number of the mismatched unit or delete the preconfigured unit type using the no member command. Upgrading Firmware New code is downloaded via TFTP or xmodem to the management unit using the copy command. Once code is successfully loaded on the management unit, it automatically propagates the code to the other units in the stack. If some error occurs during code propagation to stack units then the Managing Switch Stacks v1.0, Jan 2007 19-15

  • 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
NETGEAR 7000
Series Managed Switch Administration Guide Version 6.0
Managing Switch Stacks
19-15
v1.0, Jan 2007
Merging Two Operational Stacks
It is strongly recommended that two functioning stacks (each having an independent master) not
be merged simply by the reconnection of stack cables. That process may result in a number of
unpredictable results and should be avoided.
1.
Always power off all units in one stack before connecting into another stack.
2.
Add the units as a group by unplugging one stacking cable in the operational stack and
physically connecting all unpowered units at that point.
3.
Completely cable the stacking connections, making sure the redundant link is also in place.
4.
Then, power up each unit, one at a time, by following
“Adding a Unit to an Operating Stack”
.
Preconfiguration
All configuration on the stack except unit numbers is stored on the management unit. This means
that a stack unit may be replaced with another device of the same type without having to
reconfigure the switch. Unit numbers are stored independently on each switch, so that after power
cycling the stack the units always come back with the same unit numbers. The unit type associated
with each unit number may be learned by the management unit automatically as the units are
connected or preconfigured by the administrator.
1.
Issue the
member
<unit-id> <switchindex> command to preconfigure a unit. Supported unit
types are shown by the
show supported switchtype
command.
2.
Next, configure the unit you just defined with configuration commands, just as if the unit were
physically present.
3.
Ports for the preconfigured unit come up in “detached” state and can be seen with the
show
port all
command. The detached ports may now be configured for VLAN membership and
any other port-specific configuration.
4.
After a unit type is preconfigured for a specific unit number, attaching a unit with different unit
type for this unit number causes the switch to report an error. The
show switch
command
indicates “config mismatch” for the new unit and the ports on that unit don’t come up. To
resolve this situation the customer may change the unit number of the mismatched unit or
delete the preconfigured unit type using the
no member
<unit-id> command.
Upgrading Firmware
New code is downloaded via TFTP or xmodem to the management unit using the
copy
command.
Once code is successfully loaded on the management unit, it automatically propagates the code to
the other units in the stack. If some error occurs during code propagation to stack units then the