Loading...
Loading...
Some of the Link Aggregation Control Protocol (LACP) trunk members are missing after rebooting the primary blade.
Some LACP trunk members are missing.
This occurs on VIPRION chassis with more than one blade, configured for LACP after rebooting the primary blade.
If you have not saved the configuration in the bad state (that is, saved the configuration while the LACP trunk members are missing), you might be able to recover by running the command: tmsh load sys config.
All LACP trunk members remain present after rebooting primary blade.
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.