Guidelines for changing hardware profiles
Note the following guidelines for changing hardware profiles:
- In fabric cluster and logical chassis cluster mode, you must reload the target switch after changing a switch-based profile for the new profile to take effect.
- In logical chassis mode, when a secondary switch rejoins the cluster with a default profile configuration while the profile configuration for the secondary switch is "nondefault" on the principle switch, you must reload the secondary switch again after it has rejoined the cluster for the nondefault profile to take effect. The TCAM and route-table hardware profiles are persistent across a “copy default-config startup-config” operation.
- In fabric cluster mode, you must use the copy running-config startup-config command first, before reloading the switch.
- After a Netinstall or a firmware upgrade, the default profiles are automatically set for all hardware types, with OpenFLow disabled and maximum-paths set to 8. Also, the profile configuration defaults after changing a switch VCS ID or RBridge ID. However, the current profile persists after the copy default-config startup-config command completes and the switch reboots. Additionally, the current profile persists after a VCS mode change.
- There is no "no" option for the switch-based hardware-profile command, because switch-based hardware profiles always exist, with either the default or one of the nondefault configurations.
- When you change a hardware profile, the supported scale numbers remain the same with respect to the configuration even if hardware may not be able to fulfill them. This ensures that the same protocol and interface information remain valid with all hardware profile settings.