'Detected network configuration mismatch on Bond1G/Bond10G' alert on SolidFire node

Example:

Detected network configuration mismatch on Bond1G:

{ - "#default" : false,

+ "#default" : true,

"address" : "xx.xx.xx.xx",

"auto" : true,

"bond-downdelay" : "0",

@@ -9,10 +9,18 @@

"bond-primary_reselect" : "Failure",

"bond-slaves" : "eth2 eth3",

"bond-updelay" : "200",

+ "dns-nameservers" : "xx.xx.xx.xx",

"family" : "inet",

+ "gateway" : "xx.xx.xx.xx",

"method" : "static",

"mtu" : "1500",

"netmask" : "xx.xx.xx.xx",

"network" : "xx.xx.xx.xx",

- "status" : "UpAndRunning"

+ "status" : "UpAndRunning",

+ "symmetricRouteRules" : [ + "ip route add xx.xx.xx.xx/23 dev Bond1G src xx.xx.xx.xx table Bond1G",

+ "ip route add default via xx.xx.xx.xx",

+ "ip route add default via xx.xx.xx.xx dev Bond1G src xx.xx.xx.xx table Bond1G",

+ "ip rule add from xx.xx.xx.xx table Bond1G" + ] }

Detected network configuration mismatch on Bond10G:

The cluster is created and then all node's eth3 cables are removed before the above warning is detected.