When an attribute in a ClusterXL object is changed, the entire object is saved in $FWDIR/conf/objects_5_0.C
, and a save does not guarantee that the order of interfaces is maintained. As a result, the index of the VIP interface may change, which may cause the VMAC ID to change as well, since part of the VMAC ID is based on the index of the interface.
Note: The issue does not apply to R75.40VS