The stacking configurations are stored in the NVRAM of each node. Some of these configurations take effect only during the next node restart.
Stacking Configuration Items, Time of Effect and Default Value
| Configuration Item | Takes Effect | Default Value |
|---|---|---|
| Stacking Mode | at boot time | Disabled |
| Slot Number | at boot time | 1 |
| Master-Capable | at boot time | Yes |
| License Restriction | at boot time | Not configured |
| Priority | at the next master election | Automatic |
| Alternate IP Address | immediately | Not configured |
| Stack MAC | at boot time | Not configured |
Stacking parameters, such as mode, slot number, etc., can be configured from a single unit in the stack topology. You can change the stacking-specific configuration even when a node is not in stacking mode but is connected to the stack. The target node for the configuration must be powered on and running a version of ExtremeXOS that supports stacking. Further, the node need not be in stacking mode and can be in any node role.
Most ExtremeXOS configuration parameters are not stored in NVRAM, but are instead stored in a configuration file. Configurations stored in NVRAM are those that are needed when the configuration file is not available. The configuration file chosen for the stack is the one selected on the master node that is first elected after a stack restart.
The data (non-stacking) port numbers, in the existing configuration files (which were created when not in stacking mode), are simple integer quantities. On a stack, the data port numbers are expressed as slot:port; where the slot is an integer representing the slot and port is an integer representing the port. For example, 1:2. The configuration file contains an indication that it was created on a stackable switch in stacking mode. The indication is the stacking platform ID.
Thus, when in stacking mode, the ports are referenced in the configuration file with the slot:port notation and when not in stacking mode, the ports are referenced as simple integers.
When the stack restarts, if a switch becomes the master and its selected configuration file was not created in stacking mode, the configuration file is de-selected, and the stack completes its restart using a default configuration. In addition, if the previously selected file was named with one of the default names (primary.cfg or secondary.cfg), the file is renamed to old_non_stack.cfg.
Similarly, if a switch is configured not to operate in stacking mode and the selected configuration file was created in stacking mode, the configuration file is de-selected, and the switch boots with a default configuration. In addition, if the file was named with one of the default names (primary.cfg or secondary.cfg), the file is renamed to old_non_stack.cfg.
The renamed file replaces any file that exists with the same name; the existing file is deleted.
Print
this page
Email this topic
Feedback
View PDF
Download EPUB