Header Only - DO NOT REMOVE - Extreme Networks

Renumbering a SecureStack Manager Unit Results in Configuration Loss


Userlevel 3
Article ID: 10749

Products
SecureStack C3, C2, B3, B2, A2

Changes
Renumbered a switch unit which is serving as the stack's Mgmt Switch.

Symptoms
Upon execution of the renumber operation, the stack lost its user configurations.

Cause
If the current Mgmt Switch (per a 'show switch' query) is directly renumbered to a different unit number using the 'set switch renumber...' command, this will reset the Stack Configuration back to default values.

Solution/Workaround
Functions as Designed (FAD)

Workaround: Renumbering a Mgmt Switch should only be done indirectly.

There are two general scenarios which may be encountered:

    Scenario- The desired manager unit number is presently assigned to a non-manager unit. Example- Unit numbers are 1, 2, and 3; 3 is the manager; and 1 should be the manager. Procedure- Reassign the management role from unit 3 to unit 1.
C2(su)->set switch movemanagement 3 1

Moving stack management will unconfigure entire stack including
all interfaces.
Are you sure you want to move stack management? (y/n) y[/code]
    Scenario- The desired manager unit number is presently Unassigned or non-existing. Example- Unit numbers are 2 and 3; 3 is the manager; and 1 should be the manager. Procedure- Renumber non-manager unit 2 to the desired manager unit 1, then reassign the management role from unit 3 to unit 1.
    C3(su)->set switch renumber 2 1 C2(su)->set switch movemanagement 3 1 Moving stack management will unconfigure entire stack including all interfaces. Are you sure you want to move stack management? (y/n) y[/code] Note: The 'set switch movemanagement' command is disruptive! All stack traffic handling is suspended until the transfer process is complete (perhaps 20-40 seconds, depending upon the configuration complexity). See also: 7086.

0 replies

Be the first to reply!

Reply