If the master-capable nodes in a stack have different license levels and you want to operate a stack at the minimum license level, you can apply a license level restriction. The restriction is stored in the NVRAM of each master-capable node. It forces the node to reduce its license level below its purchased level at node restart time for the life of the restart. This reduced license level is called the effective license level and can be displayed by entering the show licenses command on the node you want to evaluate.
To restrict a master-capable node to operate at a license level that is lower than the one purchased for the node, use the command:
configure stacking {node-address node-address | slot slot-number} license-level license_restriction.
In the following example, node 7 is restricted to operate at the Edge license level:
Slot-1 Stack.3 # configure stacking slot 7 license-level edge This command will take effect at the next reboot of the specified node(s).
You must reboot the master-capable node for the command to take effect.
The command restricts the specified node to operate at the specified license level. The specified license level must match the effective license level of all master-capable nodes in the stack. To avoid stack reboots when future license level upgrades are purchased, during initial deployment you should purchase the same license level for every master-capable node in the stack, and the license level restriction should not be configured.