Last Modified: Nov 07, 2022
See more info
Known Affected Versions:
1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4
Opened: Jun 02, 2021
Restoring configuration file saved with different portgroup mode(s) than the running configuration leaves interfaces without a hardware MAC address.
The lack of hw-mac-address per interface impacts the overall functionality of L2 protocols (e.g. LACP members cannot become operationally UP because LACP BPDUs exchange require port hw-mac-address).
The issue occurs when the user does a restore of a backup file which has portgroup mode configuration different than what is currently running on the box.
On a chassis after backup/restore with different portgroup modes, follow the steps to address the issue: - change the portgroup modes of the impacted blades to default MODE_100GB - commit and allow blade(s) to reboot - verify the blade ports are now matching the 100GB mode - restore the portgroup mode of the impacted blades to desired mode (matching what is in the backup file) - commit and allow blade(s) to reboot - verify the ports are published to match the desired mode and the state contains hw-mac-address (issue command: show interfaces interface ethernet state hw-mac-address) - reapply the configuration that references the interfaces (e.g. add back interface members into the LACP LAG)
Restoring configuration files now works when the restored configuration has different portgroup modes.