Make sure that either your MX records are ordered in a round robin fashion in order to ensure that incoming mail gets an equal chance to hit all of the machines. Below is a link to an article that illustrates this:
We have six appliances handling our inbound mail (3x C60 and 3x C600), but we have a single MX record which ultimately points to an IP address that is managed by a load balancer. This works wonders at preventing uneven loading, and also makes it easier to add/remove appliances from the service as necessary. I highly recommend it.
We have connection persistence turned on, with a sticky time of one hour. This is necessary for SenderBase rate limiting to work effectively, since otherwise a suspicious sender would get connected to a different appliance each time it connects. This makes for occasional unbalanced loads, when a hot sender gets nailed to a particular appliance. However, it happens very seldom (maybe once a month or so), and I've never seen it fail to sort itself out within half an hour or so.
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...