Netgear GSM7248v1 GSM7224 Administration manual - Page 136

Migration of Configuration With a Firmware Upgrade, archive, the show switch

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 136 highlights

NETGEAR 7000 Series Managed Switch Administration Guide Version 6.0 archive command (in stack configuration mode) may be issued to make another attempt to copy the software to the unit(s) that did not get updated. Errors during code propagation to stack members could be caused by stack cable movement or unit reconfiguration during the propagation phase. An error could also occur in the presence of excessive network traffic (such as a broadcast event). All units in the stack must run the same code version. Ports on stack units that don't match the management unit code version don't come up and the show switch command shows a "code mismatch" error. To resolve this situation the administrator may issue archive command. This command copies management unit's software to the other units with mismatched code version. Before issuing this command, be sure the code running on the management unit is the desired code revision for all units in the stack. Once code is loaded to all members of the stack, the units must be reset in order for the new code to start running. Migration of Configuration With a Firmware Upgrade In some cases, a configuration may not be carried forward in a code update. For updates where this issue is to be expected, the following procedure should be followed: 1. Save the current configuration by uploading it from the stack, using the copy command from the CLI. 2. Load new code into the stack manager. Reboot the stack. 3. Upon reboot, go into the boot menu and erase the configuration ("restore to factory defaults") 4. Continue with boot of operational code. 5. Once the stack is up, download the saved configuration back to the master. This configuration should then be automatically propagated to all members of the stack 19-16 v1.0, Jan 2007 Managing Switch Stacks

  • 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
19-16
Managing Switch Stacks
v1.0, Jan 2007
archive
command (in stack configuration mode) may be issued to make another attempt to copy
the software to the unit(s) that did not get updated. Errors during code propagation to stack
members could be caused by stack cable movement or unit reconfiguration during the propagation
phase. An error could also occur in the presence of excessive network traffic (such as a broadcast
event).
All units in the stack must run the same code version. Ports on stack units that don’t match the
management unit code version don’t come up and
the show switch
command shows a “code
mismatch” error. To resolve this situation the administrator may issue
archive
command. This
command copies management unit’s software to the other units with mismatched code version.
Before issuing this command, be sure the code running on the management unit is the desired code
revision for all units in the stack. Once code is loaded to all members of the stack, the units must
be reset in order for the new code to start running.
Migration of Configuration With a Firmware Upgrade
In some cases, a configuration may not be carried forward in a code update. For updates where this
issue is to be expected, the following procedure should be followed:
1.
Save the current configuration by uploading it from the stack, using the copy command from
the CLI.
2.
Load new code into the stack manager. Reboot the stack.
3.
Upon reboot, go into the boot menu and erase the configuration (“restore to factory defaults”)
4.
Continue with boot of operational code.
5.
Once the stack is up, download the saved configuration back to the master. This configuration
should then be automatically propagated to all members of the stack