After upgrading the Messaging Gateway to version 10.9.1, communication with Ethernet interface eth1 (called Ethernet 2 in the web interface) is not working as expected.
Changes to a kernel parameter in the new SMG operating system is causing packets to not be routed through eth1 (Ethernet 2)
This issue was addressed in patch 10.9.1-296 as well as in the 10.9.1 re-release.
Workaround (if you encounter this issue and cannot apply the patch for some reason)
As a temporary workaround to this issue while it is being investigated, you can disable eth1 (Ethernet 2) and apply the IP as a virtual IP of eth0 (Ethernet 1):
Once the update has completed, your appliance should be using the IP as before, though it is now a virtual IP of Ethernet 1.
For information on patch management in the Messaging Gateway, please see this article:
Installing and removing patches for Messaging Gateway