Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Mail and Web Security Blog

Important information for users of Brightmail Gateway Virtual Edition

Created: 23 Jun 2009 • Updated: 27 Jul 2009 • 8 comments
Ian McShane's picture
+2 2 Votes
Login to vote

Here's some information you should be aware of before upgrading to the forthcoming Symantec Brightmail Gateway 8.0.2 release.

//Ian

<go>
Notification type: New version will be available – Important information to read prior to updating on VMware environments
Product: Symantec Brightmail Gateway
Version: 8.0.1
Patch: 8.0.2
Other Hardware/Software/Environment: VMware ESX Server 3.0.2 or prior with virtual LSI SCSI controller

Overview:
Action required for customers using Virtual Edition of Symantec Brightmail Gateway and VMware ESX Server 3.0.2 or prior with virtual LSI SCSI controller. Prior to updating to 8.0.2., Symantec is strongly recommending that customers assure themselves that they are current with VMware 3.5 or later prior to upgrading to Brightmail Gateway 8.0.2 to prevent loss of functionality.  An alternative workaround is provided if VMware 3.5 is not available.

Recommendation:
Symantec encourages all customers to update Brightmail Gateway to 8.0.2. The update is available via the Control Center or through the Command Line Interface (SSH).
For more information about all changes in this update, please copy and paste the URL below in a browser:
http://service1.symantec.com/SUPPORT/ent-gate.nsf/...

If you have deployed Brightmail Gateway as a virtual appliance and are using a VMware ESX Server environment with a release prior to 3.5update4, you must upgrade the virtual environment to 3.5update 4 or later prior to performing the software update. Failure to do so will result in complete loss of functionality for your Brightmail installation.

This notice is applicable to the following customer configuration;

- VMware Server Version 3.0.2 or prior
AND
- Using the virtual LSI SCSI controller

If you have the above combination and do not take one of the actions specified below, Symantec Brightmail Gateway will not function after updating to version 8.0.2. A kernel panic will occur after rebooting the virtual appliance after the update. The following options are available to prevent this issue:

* The Primary recommended method is to upgrade to VMware ESX Server Version 3.5.

Upgrading typically requires down time and a reboot for the virtual machine in which Symantec Brightmail Gateway runs. These steps may also be necessary for other virtual machines on the same physical computer. Before upgrading, perform the following tasks on Symantec Brightmail Gateway Virtual Edition:

1. Back up your existing data.
2. Check for a running LDAP synchronization cycle.
3. Check for a running Scanner replication cycle.
4. Halt incoming messages to drain all message queues.

These steps are similar to preparing for a software update. See "Running software update" in this document for more information about these steps.
For more information about upgrading, copy and paste the URL below into a Web browser:
https://www.vmware.com/pdf/vi3_35/esx_3/r35/vi3_35_25_upgrade_guide.pdf  

* If you are unable to upgrade to the latest version of VMware ESX Server, you can alternately change your virtual machine to use the BusLogic SCSI controller. For more information about changing the SCSI controller configuration, copy and paste the URL below into a Web browser:
http://www.vmware.com/support/vc14/doc/c14chgscsicontrol11.html

* For the most current information about this issue, copy and paste the URL below into a Web browser:
http://service1.symantec.com/SUPPORT/ent-gate.nsf/docid/2009051416195754

Comments 8 CommentsJump to latest comment

doni's picture

I'm confused: Do we need 3.5 U4 or anything past 3.0.2? We're still running 3.5 U3 -- will that also hose the update? How about 3.0.3? Thanks

0
Login to vote
Ian McShane's picture

Great question Doni, thanks.

I've removed the reference to 3.5 U4 specifically as that was just plain stupid looking.
3.5 U3 is fine.

For a little further clarity:
ESX 3.0.3 _should_ also be just fine, it's the 3.0.2 version of the LSI SCSI controller that is the problem.  However we recommend that everyone is on ESX 3.5 by now.

Bottom Line - If you are running ESX 3.0.2, upgrade (or change the SCSI controller) else you're going to be in a world of pain when upgrading to SBG 8.0.2.

//ian

+2
Login to vote
doni's picture

Thanks Ian! We were hoping to skip right from 3.5 U3 to vSphere 4, so I'm glad to avoid any interim steps for a smooth-as-usual Brightmail update. Speaking of which, been meaning to ask: Brightmail supports vSphere 4, right? Thanks again .d

0
Login to vote
Nel Ramos's picture

thank you for the info...
we await the next info on brightmail..

Nel Ramos

0
Login to vote
Ian McShane's picture

@Doni - Another great question :) Let me check on that and get back to you.

@Nel - Sure thing, be sure to follow the @brightmail Twitter account and as soon as it's out (very very soon, like probably today) I'll circulate the info.

//ian 

+1
Login to vote
Ian McShane's picture

Hey,

So the answer is that it's not been officially certified just yet but it's on the to-do list for sure.
Sorry I can't be more specific than that right now.

//ian 

+1
Login to vote
Guclu's picture

Hello,
I see a new update 8.0.3-11 .Is this version supports vSphere4?

0
Login to vote
Ian McShane's picture

 @Guclu

Hi, yes indeed.  

More info here -> https://www-secure.symantec.com/connect/blogs/symantec-brightmail-gateway-803-released

//ian

0
Login to vote