The stacking configurations are stored in the NVRAM of each node. Some of these configurations take effect only during the next node restart.
| 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 a standalone switch is configured for stacking, after reboot the non-slotted configuration is converted to a single slot (slot = 1) configuration (all port numbers and port ranges are prepended with "1:"). The configuration is not automatically saved. You must save the configuration to overwrite the existing primary.cfg, secondary.cfg, or custom named file.