With 2 different hardware models of the CSS (especially with one 2nd gen and one 1st gen) the configs will not be the exact. They will have different settings for number of interfaces as well as possibly different interface names.
The script will always copy to the backup, and will always fail the byte check, if you use different hardware versions.
either way, the redundancy should work fine. It is typically recommended that both CSSs run the same version of code, but that is impossible with the 2 hardware models you have. If there was a problem with the redundancy, this configuration would be very diffucult to support.
so, to answer your question, the upgrade to 6.10 will not eliminate the error. The only way to eliminate the error is to eliminate the check for filesize at the end of the script, and there is not an option to do that.
You are welcome to modify the script, but again, that is not supported by TAC. Many still do modify scripts on the CSS though with success.
The issue here is the differnet versions, so I would think the probability of having issues with box-to-box is the same as vip/interface. If you have issues with box-to-box, it is possible that VIP/Interface may not have the same issues (and visa-versa).
If it were me, I would configure VIP/Interface because it seems a little more scalable to me. If you have issues with that, then maybe explore box-to-box.
If you do have issues, you can also troubleshoot them. It will be difficult for TAC because of the unsupported version mix. However, it should still follow the same redundancy rules.
If you intend to modify the script, be sure to keep the original, and put your version with a different name.
The unmanaged mode is also known as Network only switching, which is introduced in Brazos release. It adds the flexibility for customer to use only network automation for service appliance.
If a device is configured a...
Usually, we can access ESXi Shell by pressing Alt+F1 from ESXi DCUI (Direct Console User Interface).
But on HyperFlex system, it just shows black window.
This is expected behavior because HyperFlex redirects ESXi Shell output to SoL...
Configuring an Export Policy Using the GUI
This procedure explains how to configure an Export policy using the APIC GUI. Follow these steps to trigger a backup of your data:
On the menu bar, choose Admi...