SonicWALL Global Management System Standard Edition Version Release Notes

Transcription

1 SonicWALL Global Management System Standard Edition Version Release Notes These release notes pertain to SonicWALL GMS 2.4. They contain up-to-date product information and updates to SonicWALL GMS documentation. It also lists important information about the product and explains known problems and limitations. ADDITION TO SOFTWARE LICENSE AGREEMENT LIMITED WARRANTY SonicWALL warrants that a) the software product will perform substantially in accordance with the accompanying written materials for a period of ninety (90) days from the date of purchase, and b) any support services provided by SonicWALL shall be substantially as described in applicable written materials provided to you by SonicWALL. Any implied warranties on the software product are limited to ninety (90) days. Some states and jurisdictions do not allow limitations on duration of an implied warranty, so the above limitation may not apply to you. SUPPORTED PLATFORMS SonicWALL GMS supports Solaris 8, Windows NT 4.0 with SP4 or higher, Windows 2000, and Windows XP Professional. SYSTEM REQUIREMENTS Recommended minimum system requirements for SonicWALL GMS are: MHz UltraSPARC IIi processor, 1 GB memory, two 40 GB IDE drives, and CD-ROM (Sun Fire V100 Server) 2. Windows NT 4.0 with SP4 or higher/2000/xp Professional with minimum of 512MB RAM, 85MB free disk space, and 750MHz processor FIRMWARE REQUIREMENTS SonicWALL GMS 2.4 requires the minimum firmware version to be running on the managed SonicWALL appliances. For SonicWALL TELE3 TZ, minimum firmware is supported. For SonicWALL TELE3 TZX, minimum firmware is supported. For SonicWALL TELE3 SP, minimum firmware is supported. It also supports the minimum firmware version on the RedCreek Ravlin devices. SonicWALL GMS 2.4 has been tested with firmware English, English, Chinese, Japanese, English, English, English, English, English, English, English, Japanese, English, Japanese, English, and b2 Japanese. SUPPORTED APPLIANCES SonicWALL GMS 2.4 supports SonicWALL TELE2/TELE3, TELE3 TZ, TELE3 TZX, TELE3 SP, SOHO2/SOHO3, XPRS/XPRS2, PRO series, and GX series. It also supports Ravlin 7160, 7150/5300, 5100 (Ravlin 10), 3300/3200, and 2200 (PRAV II). SonicWALL, Inc Borregas Drive, Sunnyvale, CA /10/03-1

2 DATABASE SUPPORT SonicWALL GMS 2.4 has been tested with MS SQL Server 2000 SP2 and Oracle 9i Enterprise Edition Release Production; both databases running on Windows platform. Note that SonicWALL GMS 2.4 works with the MS SQL Server database when the database is installed as case INSENSITIVE (default database installation). If the database is installed as case SENSITIVE, SonicWALL GMS will not work. DEPLOYMENT REQUIREMENTS For deployment requirements, see SonicWALL GMS 2.3 Introduction and Installation User Guides. UPGRADE INSTALLATION NOTES To upgrade your SonicWALL GMS 2.3 system to version 2.4, refer to the SonicWALL GMS 2.4 Upgrade document and GMS 2.4 Addendum. If you have confi gured your SonicWALL GMS 2.3 system to run on HTTPS for SSL access, during the SonicWALL GMS 2.4 upgrade, you will loose your configuration files for this SSL access. Workaround: Before the SonicWALL GMS 2.4 upgrade, save the <sgms_directory>\jre\lib\security\java.security and <sgms_directory>\tomcat\conf\server.xml files. After the SonicWALL GMS 2.4 upgrade is complete, replace the new server.xml file with the saved server.xml file. INSTALLATION NOTES On Windows systems, SonicWALL GMS can be installed on a drive other than the C:\ drive. However, the Windows system must have the C:\ drive since the sgmsconfig.xml file needs to be installed and reside on the C:\ drive. In addition, SonicWALL GMS should not be installed in a path that has spaces in the folder names. NEW FEATURES AND ENHANCEMENTS The new features and key enhancements in SonicWALL GMS 2.4 are: Feature Simple Global Rule Management SNMP Relay Auto Saving of Prefs Files and AddUnit.XML New Privileges for Operator Users Reporting Management per Firewall Reporting Management of the HomePort CLI Enhancement for Reporting Reporting API Additional Reporting Enhancements Description/Benefits Support for defining and distributing global security rules based on a global object that can be applied to a group of firewalls, simplifying distribution and enforcement of global policies to hosts on the LAN. Centrally receive firewall SNMP traps over the secure management tunnel and forward them to a 3rd party SNMP management system, ensuring security of firewall traps. Send GMS traps to a 3 rd party SNMP management system, for greater management and insight to GMS activity. Automate and schedule saving of prefs files for the managed SonicWALL appliances and creation of the AddUnit.XML file, providing backup recovery in the event of a failure or errors in policy configuration and deployment. Support for additional set of privileges for GMS operator and other non-administrator users, increasing flexibility in administration and management. Manage reporting for the managed SonicWALL appliances by enabling/disabling distribution of syslog messages to GMS per firewall, reducing data reporting and management traffic. This requires minimum firmware Control reporting on the HomePort for the managed SonicWALL TZ and TZX appliances, reducing private data reporting and management traffic. Support for using CLI scripts to schedule ing and archiving of reports, offering integration to the provisioning legacy systems. Support for an API to modify the look and feel of reports, including logo and text, an important competitive feature in the Service Provider market. Enhancements for increased reporting flexibility and scalability o One single syslog raw database o Modify scheduled reports SonicWALL, Inc Borregas Drive, Sunnyvale, CA /10/03-2

3 Ease of Use Enhancements AutoUpdate Service for New GMS Software and Patch Updates Support for New Firmware Features Support for SonicWALL PRO 230 and PRO 330 o Run reports for a previous day, week, or month o Change the default scheduled report time o Timestamps for last summarization, next summarization, last ed/archived scheduled daily/monthly/weekly reports are displayed o Zip reports to a single file attachment o Log Viewer search engine results for a number of days and per a message text Enhancements for greater administrative flexibility and control o Ability to display firewall dynamic data (i.e., firewall up time, ARP cache, number of allowed LAN IPs) o VPN SAs and Modem Profiles are now inherited from Group o Modify data for units once they have been added o Modify GMS for a unit that is replaced in the field o Views can now be based on Networking Mode and Scheduler o Addition of tool-tip in the TreeControl o Addition of 3 default views (GlobalView, FirmwareView, and ModelView) with fresh install Send automatic alerts of new GMS software and patch updates when they are available on Mysonicwall.com for download to ensure administrators keep their network security management current. Some of the new key features are: o Single-Arm Mode VPN - Allows the firewall to act as a pure VPN device and be placed in parallel with an existing firewall. o RIPv2 Advertising - Allows the firewall to dynamically advertise updated VPN routing information to the internal network. o AES support - Support for Advanced Encryption Standard (AES) encryption algorithm. o Flexible DMZ - Enables configuration of the DMZ port as a second LAN, including support for NAT, DHCP, AV and CFL on the DMZ. o PPTP Client support - Allows WAN protocol support for Microsoft Point-to-Point Tunneling Protocol (PPTP), and connection to a PPTP based Virtual Private Network (VPN). o SNMP VPN MIBs and VPN Stats - Provide SNMP information on VPN tunnel status and VPN traffic statistics. o DPD configuration for tunnel failover - Allows you to configure time interval for DPD in order to control VPN tunnel re-creation times. Some of the key features are: o Support for firmware o AES support o Interfaces on the front o Increased RAM to 64MB o Dual power supplies for PRO 300 ENHANCEMENTS AND FIXED PROBLEMS The following issues have been fixed in GMS 2.4 Patch 24_0001. Database issues o When the GMS database goes down, the access between the GMS servers and the database server also goes down. You need to re-start the GMS services. o When the GMS services start and the database service is not running at that time, the GMS services would stop and exit. For single-system GMS installation on Windows, if the SQLServer service starts at the end, you have to manually start the GMS services. Windows and SQL environment issues o When scheduled reports get archived in the default folder (i.e. no folder is specified in the schedule), SonicWALL GMS then incorrectly enters a log saying the archiving has failed, even though the archiving has succeeded. o If the Internet connection is down, and SonicWALL GMS is set to ignore the Internet connection status, the recovery of firewalls does not happen. SonicWALL, Inc Borregas Drive, Sunnyvale, CA /10/03-3

4 o Summarization of firewalls is not working correctly. o For PRO 230 and 330, the DMZ screen is missing. o For GroupVPN, the XAUTH checkbox is not exposed in GMS UI. o On the Console Panel/Management/Users screen, all users in the Administrators UserType are not able to see the views owned by the user admin; therefore, they cannot assign them as default views. o Number of units does not show up correctly at the global/group levels for Views that list the Scheduler option at any level; the Re-assign dialog box also does not work correctly for these Views. o In the Scheduler view, unit permissions cannot be set correctly. o The Screen Permissions in the Management/Users screen does not show some screens correctly. o If a UserType is selected and the default view is reset to None, exceptions are displayed when the Update button is clicked. o When configuring the SNMP Manager screen, task description is missing. o The Create AddUnit.xml option does not create the entry correctly for units that are managed using existing tunnels. o Deselecting some tasks on the current page will undo the Select All pending Tasks on all the other screens now, instead of deleting all tasks. o The default value for Save Directory in Single Day Report is using From Address value. o Next summary time is reflected correctly. o Single and Multi-Day reports do not default the From: address value to the one specified in Console Panel/Login/SGMS Settings panel, for the sender address. o If a new-line character is entered in the Comment section of the Management/Users screen, it causes problems in viewing the user info. o SonicWALL GMS registration fails if there are trailing spaces in the GMS serial number. o When a scheduled operation is running, a Send Now operation is not allowed. Storing Heartbeat Messages GMS can now store heartbeat messages in the database. This feature is off by default. For enabling instructions, refer to the GMS 2.4 Addendum. GMS 2.3 Patches 1. Patch 23_ For Mysonicwall.com-database sync for a Unit, warranty & CFL expiry dates are no longer updated in the GMS database, if the data is not provided by Mysonicwall.com (i.e., no 'null' updates). This resolves an issue seen at some GMS installations using Oracle where GMS does not show a Unit as being registered at the backend even though it is actually registered. This patch is not officially released. 2. Patch 23_ For blocked websites, the syslog message had the dstname field incorrectly containing the whole URL instead of just the domain name. This was causing exceptions in the Scheduler since the column size for storing this expanded dstname was not wide enough. Scheduler now creates a wider column to handle this. This issue has been addressed in firmware 6.4 as well. This patch is not officially released. 3. Patch 23_0005 for removing the Clustered index when Oracle Database Server is the backend. This patch is not officially released. 4. Patch 23_0005 for better handling of situations where units incorrectly go red when syslog rate is high and database server performance is slow. This patch is not officially released. 5. Patch 23_0004 is not officially released and addresses the following: o Database cursors were being left open and the max number allowed was being reached, beyond which the database server would not respond. Fixed. o Temporary Database View needs to be deleted before another view is created. This was not being done correctly, as a result of which the General/Status page would not display the firewall model type, etc. Fixed. o GMS no longer displays the unnecessary error messages when a reporting database is already created and the Scheduler tries to create it again. SonicWALL, Inc Borregas Drive, Sunnyvale, CA /10/03-4

5 o The date formats stored into the SGMS_CONFIG database table for Oracle are now correct. o GMS also stores the bytes info for OTHER service for the Services Summary reports page. 8. Patch 23_0003 addresses a number of GMS reporting and VPN issues. 9. Patch 23_0002 addresses a number of issues, improving and optimizing the performance of Scheduler and ViewPoint Summarizer. 10. GMS Uninstall program works fine if all the GMS services are running on the system. In rare situations, and if any of the GMS services is not running on the system, the GMS services may not be un-installed correctly. A new GMS Uninstall program helps to clean up the uninstallation of the GMS services. This issue is also addressed in Patch 23_0003. XML CLI changes 1. XML can handle spaces in the group name. 2. XML filenames can start with alpha_numeric character. 3. XML filenames can have under_scores. 4. No need to double-quote XML filenames if they are not in the CLI folder. 5. The AddUnit.xml file created by GMS now correctly handles spaces in the custom attribute names and values as well as special characters such as &. 6. Password is no longer echoed through CLI. 7. Installer now installs a number of sample XML files in the CLI folder. Installation/Un-installation/Upgrade 1. Installer performs cleanup if Phase 2 install fails. 2. Installer provides better checks for Phase 2 install success. 3. Installer offers more debug data for Phase 2 install. 4. Installer now installs a number of sample XML files in the CLI folder. 5. Upgrade install now forces write permissions on all files in the GMS folders. 6. Uninstall now backs up sgms.o, sgmsconfig.xml, web.xml, and prefs files; it creates and backs up the addunit.xml file; it dumps contents of the SGMS_CONFIG table to sgms_configtable.txt. All are stored in the <sgms_directory>\backup folder. The sgms24_uninstall.log file is also now copied to this backup folder. GMS reporting 1. There is a single database support for raw syslog data. The data now gets logged in the main GMS database, SGMSDB. There are 15 new tables that get created for this data, for each UTC day. For the name of these tables, refer to GMS 2.4 Addendum. 2. Log Viewer Settings, Summarizer, and Services pages are moved from Reports Panel to the Console Panel. 3. Log Viewer displays syslog in local time zone of the firewall instead of UTC. 4. Available daily reports are also provided for weekly/monthly time frames (i.e., Mail Usage Top Users). 5. Reporting of firewalls in time zones that are not rounded (i.e., Australia which is 9.5 hours ahead of UTC) now done accurately. 6. If you have access only to one firewall, at group levels you are no longer able to view reports for all firewalls. 7. Feedback is now provided at the top of the screens if you make any changes to reporting configuration, and is also logged into GMS Logs. If you do not have update permissions on any screen, the top of the screen indicates this. 8. The location for archiving reports can now be changed. 9. Subject lines for ed reports are now customizable. SNMP traps through the management SA SNMP traps can now travel from the managed SonicWALL appliances through the management VPN tunnels to a SNMP management system. SonicWALL, Inc Borregas Drive, Sunnyvale, CA /10/03-5

6 Cannot delete the NTP server You can now delete the NTP server of a SonicWALL appliance from SonicWALL GMS. This requires firmware 6.4 or higher. SonicWALL TELE3 TZ and TZX o If adding routes to any interface of the SonicWALL TELE3 TZ or TZX, SonicWALL GMS always displays the routes for the WorkPort interface although the routes are displayed correctly in the firmware for the assigned interface. Furthermore, the routes cannot be deleted from SonicWALL GMS if the routes are specified for any interface other than WorkPort. This is an issue with the firmware prefs file for the TELE3 TZ and firmware prefs file for the TELE3 TZX. When a change is made to an appliance, GMS will read the prefs file to update its database with the new change. Since the route information is incorrect in the prefs file, the GMS database will also contain and display the incorrect data. Note that if the firmware of TELE3 TZ or TELE3 TZX is wiped out and the latest prefs file is added back to the appliance from the local interface, this problem will also exhibit itself in the firmware. This is fixed in firmware 6.4. o GMS 2.3 manages SonicWALL TZX correctly, except that it displays LAN/DMZ instead of WorkPort/HomePort. GMS 2.4 now correctly displays WorkPort/HomePort for TZX. VPN changes 1. SPD files can now be ed to multiple addresses. 2. Message field is added allowing you to write a message when ing the VPN Client or the spd file. 3. GMS now checks for the existence of VPN Client zip file when ing the spd file. 4. A change to an SA no longer impacts it if it is also being used for DHCP over VPN. 5. GMS displays the number of SAs defined, enabled and allowed in a firewall at Unit level. 6. Firewall point of contact information can be changed at Group level. Other o SonicWALL GMS no longer caches the LATTEUSERNAME and LATTEPASSWORD value from SGMS_CONFIG table for Mysonicwall interactions; it now accesses the database when it needs these values. o When a unit is registered, GMS also now sends the friendly name of the unit to Mysonicwall.com. o New Synchronize option added to sync up Mysonicwall.com with GMS (i.e., units deleted, renamed, etc.). o New Renew option added to renew GMS support. o If the gateway IP address/password is changed on the Management/Agent page, the Scheduler no longer needs to be started. o If the Agents have not been enabled for failover on Internet connectivity loss, GMS still sends an if the Agent loses Internet access. o You can no longer change the status of an Agent to 'down. o The custom groups layout is altered; they are all at the same level. o When a firewall is deleted, any diagnostic data in the system now gets correctly deleted. o GMS can now manage the backup HA unit when it goes active. Fixed in firmware 6.4. o When a firewall has not been registered, GMS now displays the subscriptions and upgrades as N/A for the firewall. o When a firewall has not been acquired, GMS now displays its status as Not Acquired. o If a firewall is not registered, GMS does not show the free trial and join LSG buttons. o For license sharing, now the number of used licenses and the number of available licenses are displayed. o Firmware upgrade from local hard disk is no longer firmware-filename-case-sensitive. o The s that specify the models and the number of each model that is being managed by GMS also now specify the Ravlin devices. o The Radius Client Test controls are removed. SonicWALL, Inc Borregas Drive, Sunnyvale, CA /10/03-6

7 o Inherit settings from Group feature now inherits VPN SAs as well as Modem Profiles. o GMS now enables/disables some of the firewall screens based on the firmware language tag. o View names are now unique. o When renaming a unit, the dialog box now is filled with the current name of the unit. o A unit can be searched on partial serial number or partial WAN IP. o The Select All button is now provided for the daily/multi-day report schedules. o GMS displays the acceptable range of log messages per screen. o GMS now records which Agent has executed the tasks. Additional actions are also now logged: o If tasks are re-scheduled o 24-hour license validation o When a unit is locally changed o The Synchronize Now option on General/Tools page now logs a warning if it cannot access the unit. o All scheduled tasks can now be selected; this is in addition to just the tasks on the current screen. o Select All Tasks (all tasks spanned across multiple screens) o Select All x Tasks (where x is the number of tasks per screen) o The Agent Name field is added to provide a user-friendly name for the schedulers. This will then allow you to create views based on the schedulers. o If multiple "enter" keystrokes are entered in the chat script windows, the "add profile", "delete profile", "update", and "reset" buttons will disappear. This is fixed. KNOWN ISSUES 1. Firmware 6.4 related issues o There is a known issue with firmware syslog messages that impacts GMS reporting. If a SonicWALL appliance is upgraded to firmware , the firewall will not be sending syslog messages with connection category (c=1024). In this case, the admin will not be able to log the firewall usage based on tcp/udp. You will not be able to see messages of the following type: id=firewall sn= af4b time=" :38:58" fw= pri=6 c=1024 m=97 n=2 src= :1600:lan dst= :80:wan proto=tcp/http op=get rcvd=583 result=200 dstname=c.msn.com arg=/c.gif?ps=10274&na=1154&nc=10009&pi=7317&di=340 If you are using the syslog messages from your managed firewalls for reporting, at this time do not upgrade to firmware This problem is addressed in firmware o Changing the WAN IP address through GMS does not work for firmware 6.4. GMS will incorrectly say that the task has failed. This requires firmware 6.4 or higher. o Uploading prefs file from GMS does not work for firmware 6.4. This requires firmware 6.4 or higher. 2. Non-English SonicWALL firmware issues o SonicWALL GMS cannot handle Japanese characters of Japanese firmware. The same limitation exists for Chinese and Korean firmware. o For SonicWALL appliances running Chinese firmware, SonicWALL GMS displays the Anti-virus pages although these pages are not available in the firmware UI. o You cannot upgrade from Japanese or Chinese firmware to a newer firmware version using SonicWALL GMS firmware auto-update feature. Workaround: You can use the Enable Firmware Upgrade From Local Drive feature to upgrade to a newer Japanese or Chinese firmware version from the hard disk. SonicWALL, Inc Borregas Drive, Sunnyvale, CA /10/03-7

8 3. Database issues o Support for default database instance - It is possible that there are multiple instances of the SQL database on the system. SonicWALL GMS currently works only with the default instance. 4. Command Line Interface (CLI) issues o The CLI does not support changes to the GMS users. With CLI, you cannot add GMS users, delete GMS users, or change GMS users password. o You no longer can change the AV password from GMS UI or CLI since the AV password is not longer supported in the firmware. o You cannot use CLI to perform firmware upgrades. 5. HA issues o For SonicWALL appliances in HA mode that are under GMS management, firmware upgrade as well as AV and CFL will work only on the active HA firewall. GMS still cannot manage firmware upgrade, node upgrade, and subscriptions for backup HA units. These are firmware issues. o For the SonicWALL appliances in HA mode, GMS cannot make changes to the active back-up unit through the management tunnel. Workaround: You need to push the changes to the active primary unit, and then the primary will automatically synchronize with the backup unit. o No PKI certificate for the HA unit. The PKI cert is tied to the serial number of the primary unit and cannot be switched to the HA unit since the serial number is different. 6. Registration issues o Registration of SonicWALL GMS is not supported over dialup. o Once the SonicWALL GMS registration fails, this information is cached and making a correction to the SonicWALL GMS Registration page will not succeed in re-registration. You need to clear the cache, close the web browser session and re-start SonicWALL GMS. 7. VPN issues o In SonicWALL GMS, Once the LAN IP address of a SonicWALL GMS is changed, the change is not reflected in the VPN LAN-to-LAN or remote-to-lan SA configuration. o If a SonicWALL appliance in the Interconnected Mode is deleted from SonicWALL GMS, you can no longer delete the SA associated to the same appliance. Workaround: You need to manually remove the SA from the firmware UI. 8. No display of dynamic firewall data SonicWALL GMS does not display dynamic firewall information such as if SonicWALL TELE3 SP is using the Ethernet or dialup port. 9. Firewalls are not sending heartbeat messages You should not set the heartbeat messages interval rate to 0. This will cause the firewall to stop sending the heartbeat messages. 10. Un-supported SonicWALL GMS features for Ravlin devices The following SonicWALL GMS features are not available for the Ravlin products: o No load balancing redundancy support - whether you use the management SA or the site-to-site SA for the primary agent, you cannot assign a standby management SA for the secondary agent. o No interconnected mode SA - the VPN Interconnected Mode option does not exist for the Ravlin products; therefore, you cannot create a VPN mesh topology among the Ravlin products. SonicWALL, Inc Borregas Drive, Sunnyvale, CA /10/03-8

9 o No interconnected mode SA between the Ravlin devices and SonicWALL appliances - the VPN Interconnected Mode option does not exist between the Ravlin devices and the SonicWALL appliances; therefore, you cannot create a VPN mesh topology between the Ravlin devices and the SonicWALL appliances. o No GMS Reporting support, except for the Log Viewer. o No "inherit group settings" feature - you cannot inherit the group settings of a Group to a Ravlin device under the Group. o SonicWALL GMS does not support management of Ravlin devices in a cluster mode. 11. GMS reporting o Requesting Summarize now ; at UTC midnight sometimes does not work. It is recommended that you summarize your raw syslog data or schedule your data summarization to run on 10 or 15 minutes of the UTC hour (i.e., 1:10, 1:15). o Ensure that the dates in the managed SonicWALL appliances are set accurately by configuring the NTP server or setting the correct date. If the firewall date is inaccurate, the GMS Reporting would not have accurate or any data. The Scheduler will also show high CPU activity over extended periods. o If you change the GMS Reporting enable/disable setting on the SGMS Settings page, it is highly recommended to re-start the SGMS Scheduler service. All SonicWALL appliances should be showing correct time if you enable GMS reporting. o For Oracle based environment, in order to archive the GMS reports, you need to enter an address in the configuration of the scheduled report. o For Oracle based environment, you cannot archive reports if an id is not specified. 12. Other o Inheriting group settings does not modify or delete the existing SA. o From the GMS UI, you cannot change the HTTP port on the Policies Panel/Access/Management screen. This is read-only mode. o You cannot now use single quotes in the Comments filed to create user group types and individual users. o You cannot add a SonicWALL appliance with a single quote in its name. o SonicWALL GMS does not check the serial numbers in the Peer SonicWALL serial # field, when trying to create an SA in the IKE using Certificates non-interconnected mode option. o Do not use the Correct password (CMP) To field at the Policies Panel/PKI/Admin Cert unit level to change the CMP for your managed SonicWALL appliances. o SonicWALL GMS does not support management of SonicWALL Vulnerability Scanning Service. o The SGMS desktop icon on Windows XP Professional has the IE image. o SonicWALL ViewPoint 1.x cannot be installed on the SonicWALL GMS server(s). o Using SonicWALL GMS, you cannot use the PKI activation codes to activate PKI in the SonicWALL GX products. SonicWALL GMS logs the Activation key is invalid error message. o If you are using any Netscape version on a Solaris system to register your SonicWALL GMS, the Update button on the Registration page does not work. Workaround: Use Internet Explorer from a Windows system. o During SonicWALL GMS Phase 2 installation, the 'Enter' key does not work for selecting the highlighted "OK" button. Workaround: You need to use the mouse or the Space bar key. o Using SonicWALL GMS, you cannot use any special characters (except for the period) for the Host # fields in the Access/SNMP page on the Policies Panel. Workaround: You need to either enter an IP address in the fields or a hostname that does not contain any special characters (exception is the period). SonicWALL, Inc Borregas Drive, Sunnyvale, CA /10/03-9

10 13. Registration fails Problem: Registration of GMS, activation of GMS node license upgrades, or activation of GMS service contact fails with the following error message: "Upgrade failed: Error During Impersonation of user". Cause: This is because there is a mis-match between the password for the gms account on mysonicwall.com (as mysonicwall thinks it is) and the password that is recorded in the SGMSDB database. Solution: The best way is to grab the password from the SGMSDB database (the sgms_config table) and provide it to SonicWALL (registration site engineering team) to modify the GMS account on mysonicwall.com. 14. SonicWALL GMS installation failure Problem: The SonicWALL GMS Phase 2 installation on a Windows system fails with a communication link error message. Cause: There are multiple instances of the SQL database on the system and SonicWALL GMS is using the JDBC driver to access the wrong database. Each instance is installed at a different port number. SonicWALL GMS currently works only with the default instance. Solution: Ensure that the port number in the JDBC driver URL is valid for the SQL database that SonicWALL GMS should be accessing. 15. SonicWALL GMS installation failure Problem: The SonicWALL GMS Phase 2 installation on a Windows system fails with the error message: "WINNT_install.tmp cannot create". Cause: The SonicWALL GMS Phase 2 installation, postinstall.bat, must be invoked from the DOS prompt. For this problem, the DOS prompt screen was opened up by the command.com. Solution: The DOS prompt screen should be opened by the cmd.exe or by going into Start- >Programs->Accessories->Command Prompt. 16. SonicWALL GMS installation failure Problem: The SonicWALL GMS Phase 2 installation on a Windows system fails with the error message: "Cannot create C:\Program Files\Microsoft SQL Server\MSSQL\Data\SGMSDB.LDF. Cause: The SGMSDB.LDF and SGMSDB_log.LDF files have remained from a previous installation. Solution: Delete the SGMSDB files and continue with the SonicWALL GMS Phase 2 installation. 17. Internet Explorer 5.5 crash Problem: If you are using Internet Explorer (IE) 5.5 and double clicking very fast, the IE application may crash if you are using the Java Plug-in To check the version of the plug-in you are using, go to Start -->Settings -->Control Panel, double-click on the Java Plugin icon and select the About tab. Cause: This is a JRE/Java Plug-in version bug. SonicWALL, Inc Borregas Drive, Sunnyvale, CA /10/03-10

11 Solution: You should uninstall the Java Plug-in from your system and save any modifications that you may have done to the java.policy file. SonicWALL GMS will then download and install the latest Java Plug-in 1.3.1_01 that has a fix for the crash. Add your modifications to the new java.policy file. The java.policy is typically located in the c:\program Files\JavaSoft\JRE\1.3\lib\security directory. 18. Additions to Documentations The following have not been documented in the SonicWALL GMS user guides. SonicWALL GMS ViewPoint Guide The SonicWALL GMS ViewPoint Guide references Kilobytes instead of Megabytes in some areas of the documentation. With GMS 2.3 Patches 23_0002 and 23_0003, all reports are now in Megabytes. DOCUMENTATION SonicWALL GMS has the following user guides. They are o SonicWALL GMS Standard Edition 2.3 Introduction Guide o SonicWALL GMS Standard Edition 2.3 Installation Guide o SonicWALL GMS Standard Edition 2.3 Configuration Guide o SonicWALL GMS Standard Edition 2.3 Command Line Interface Guide o SonicWALL GMS Standard Edition 2.3 ViewPoint Guide o SonicWALL GMS 2.4 Addendum OBTAINING TECHNICAL SUPPORT For timely resolution of any technical questions, please visit SonicWALL s Technical Support web site at < There, you will find resources to help you resolve most SonicWALL technical issues, as well as a means to contact one of SonicWALL s Technical Support engineers.? 2003 SonicWALL, Inc. All Rights Reserved. SonicWALL is a registered trademark of SonicWALL, Inc. All other trademarks and trade names belong to their respective holders. SonicWALL, Inc Borregas Drive, Sunnyvale, CA /10/03-11