Difference between revisions of "SG Lab Exercises"

Revision as of 16:08, 4 October 2017

EXERCISE #1

Issue: Web page won't load after setting up the ova file on VMware server.

Cause:

a) They didn't go through the GWAVA install? http://support.gwava.com/documentation/GWAVA/70/html/GWAVA_Installation.htm

• login as user: gwava
• run the following command: sudo /opt/gwavapreinstall.sh

b) If they have gone through the GWAVA install, check to see if there is a /opt/gwava directory that was installed. If there's not, then the install failed. This is usually because they can't get out to get the Ubuntu or Secure Gateway updates.

1. ) Check the firewall, or a web filter they might be using, that might be blocking the connection.
2. ) The DNS could be failing to resolve the hostnames for these updates as well, you could try using a public DNS server if that is the case.
3. ) Run the install script again by typing: sudo /opt/gwavapreinstall.sh.complete

Note: Use putty so that you can scroll up to view the errors, if there are any. Such as:

"svn: E170013: Unable to connect to a repository at URL 'https://gwava7updates.gwava.com/update/gwava7/release' 
svn: E670002: Name or service not known"

1. ) If a different DNS is needed, while going through the install the second time, enter in a DNS that should resolve these, such as Google's 8.8.8.8 and 8.8.4.4.

EXERCISE #2

How do I prevent outbound email from getting scanned for anything but the Virus Filter Group: Anti-Virus, Zero Hour Virus, Fingerprinting, and Named Executables)?

1. ) Set up a new policy using the wizard, selecting 'outbound' only.
2. ) Edit Outbound policy, under Policy management, ensuring that it has the following checked 'Enabled', 'Scan by message direction' and 'Handle outbound mail'
3. ) On the workbench for the outbound policy, make sure you have the following:
4. ) Edit Inbound policy, under Policy management, uncheck 'Handle outbound mail'

Now Outbound email will only be scanned by the 'Outbound Mail Filter Policy'.

EXERCISE #3

Common issue: End user whitelist or blacklist is not working (not seeing the option in their QMS). Task: Set up end user whitelist or blacklist correctly.

1. ) Add the box for the whitelist, under Exceptions to the workbench.
2. ) Add the box for blacklist, under Filters to the workbench.
3. ) Link the whitelist box to Spam Filter Group
4. ) Link the blacklist box to Message Block service
5. ) Link the whitelist to the QMS by clicking on the "click to configure it and click on link to qms icon)
6. ) Verify that the users have rights for the blacklist/whitelist. QMS as admin | settings | users rights | select which options you want users to have rights for.
7. ) Login to the QMS as the user that you gave blacklist/whitelist rights to, in the step above. You should see the buttons for Whitelist and Blacklist.

EXERCISE #4

Common Issue: How to add the Secure Messaging Gateway License.

You will need the customer's Validation key and Customer ID (which is their email address). You can get this from licensing, if the customer does not have it.

1. ) While logged in as admin to the System Management web page, go to System Management | Licensing.
2. ) Click on Add License.
3. ) Enter in the Customer ID (email address), and their Validation key. Supports license details are: Customer ID- corp@gwavanation.com Validation key- H7j3-d4f
4. ) Hit Send Request
5. ) Click on the EULA agreement.
   1. ) Fill out the form to confirm details.
   2. ) Check the box that you have read and understand it.
   3. ) Click Accept.
6. ) Check the box next to the license in the list.
7. ) Click Intstall.

You should now see the license show up.

EXERCISE #5

Common Issue: One module will not start up using the UI Start or Restart buttons.

If you see this happen, you can stop all the modules from a prompt (kill the ones that are hung) and start them back up.

1. ) Open Putty to the Secure Messaging Gateway server and login as the gwava user.
2. ) To switch to root rights type: sudo su
3. ) Enter the password for the gwava user. Unless you changed it, it is: gwava
4. ) Change directories to /etc/init.d
5. ) To see which modules are currently running type: ./gwava7 status
6. ) Stop all the modules by typing: ./gwava7 stop
7. ) Check the status again to make sure everything is down: ./gwava7 status
8. ) If a module is still running, find the PID so you can kill it by typing: ps ax | grep gwava
9. ) Kill the PID that is hung by typing: kill -9 <PID>