On a Symantec Messaging Gateway appliance, when making configuration changes to a Scanner and then saving with the option "Apply above settings to all Scanners" selected, some scanners behave differently than others. Inspecting the individual scanner configurations in the Control Center shows no difference but inspecting the actual configuration files reveals that the configurations are not the same.
Navigate to Administration->Host->Configuration to get to the "Host Configuration" page, choose the Control Center appliance from the list and click on it to get to the "Edit Host Configuration" page, then on the "SMTP" tab, click the "Outbound" tab, then modify the "Outbound Mail Acceptance" list of that appliance, and save using the option "Apply above settings to all Scanners" located on the bottom of the "Edit Host Configuration" page. If network issues prevented the Control Center from communicating to that Scanner, there will not be any error showing on that page but the affected Scanner will not accept outbound connections from the new IP address added and it's configuration file will not be modified.
There are no errors displayed on the "Edit Host Configuration" or "Host Configuration" pages when saving changes in the Control Center with the "Apply above settings to all Scanners" option even if the Control Center is unable to communicate with that scanner.
However, here are some exaples of error messages that are displayed in the BrightmailLog.log file when the Control Center cannot reach the Scanner. These errors can be seen by executing the "tail -f BrightmailLog.log" command from the admin command line interface (admin CLI) when logged into the Control Center appliance as the "admin" user. The "126.96.36.199" is an example of an ip address for the scanner.
ERROR - com.brightmail.common.BrightmailException: The Agent running on 188.8.131.52 is temporarily unreachable. Please check the specified host.
Oct 05 2011 06:59:43 [http-41443-Processor10] ERROR - The response object is null.
When saving changes to Scanners using the "Apply above settings to all Scanners" option, if there are any network issues causing the Control Center to fail to communicate with a Scanner it will not report the error. The database will be updated, so the Control Center will show the Scanner configuration as updated. However, due to the failed communication, the Scanner's local configuration files will not be updated at that time and the configurations will differ between Scanner systems.
Saving the configuration change on some other configuration screen of the Control Center, such as the "Log Settings" page, will correct the situation if the Control Center can appropriately communicate with that Scanner again. This is because the changes have been already stored inside the database, just not replicated to the Scanner yet.
However, if while waiting for the Scanner to be accessible again, the user navigates to another configuration section of the appliance, then comes back, does not see the change made earlier while the Scanner was not available, but saves the configuration anyway, the earlier configuration change stored inside the database is gone. In this case, the desired configuration change needs to be re-entered and re-saved when the Scanner is available, so the new configuration can be pushed to the Scanner.
Imported Document ID: TECH170888
Subscribing will provide email updates when this Article is updated. Login is required.