NGX R65 Release Notes - Check Point

More documents

Recommendations

Info

SmartUpdate SmartUpdate In This Section Installation, Backward Compatibility, and Upgrade page 36 Miscellaneous page 37 Platform Specific — Nokia page 37 Platform Specific — SecurePlatform page 37 Policy Installation page 37 GUI page 37 Licensing page 37 Installation, Backward Compatibility, and Upgrade 1. When a gateway has been upgraded and then rolled back to the previously installed version, SmartUpdate will not be able to report its status. This occurs because the gateway restarts with the initial policy, instead of the last installed policy. The workaround is to re-install the old policy via SmartDashboard. 2. The command line executable for upgrading remote gateways, cprinstall, does not currently support the upgrade all option. Instead, run cprinstall install to upgrade individual packages, or use the SmartUpdate GUI. 3. After using SmartUpdate to install a firmware package on a UTM-1 Edge gateway, renaming the gateway in SmartDashboard may fail and result in the following message: Internal Error [12] while handling object edge1. Failed to update references of object edge1. Please contact technical support. If this should occur, you can safely ignore this message and perform the rename operation again. To avoid this message, leave SmartDashboard open during firmware installation. 4. After upgrading a pre-NGX SmartCenter to NGX R61, software packages (except for UTM-1 Edge firmware packages) that were displayed in the Package Repository of SmartUpdate do not appear. The packages are in the directory $SUROOT, and can be re-added to the Package Repository using the SmartUpdate command Add From File. 5. After upgrading a SecurePlatform gateway from NGX (R60) to NGX (R60A), SmartUpdate erroneously reports that the upgrade has failed. This message can be safely ignored. 6. After a SmartCenter server has been upgraded or copied via the Advanced Upgrade feature, previously defined UTM-1 Edge devices will not be able to connect to the SmartCenter server, and the Connection Wizard will generate object non-registered messages. To resolve this issue, use SmartUpdate to re-install a specific firmware package. 7. SmartUpdate can be used to upgrade a Log Server, but it cannot be used to downgrade a Log Server. Downgrading a Log Server should only be done locally. 8. SmartPortal NGX (R60) cannot be upgraded to NGX R61 via SmartUpdate. A workaround is to install SmartPortal NGX R61 directly (locally) to the NGX R60 machine. 9. When using SmartUpdate to upgrade Eventia Reporter Server from NGX (R60), the message Execution error may appear at the end of the upgrade process. This message may be safely ignored. To confirm that the upgrade was successful, in SmartUpdate select the Reporter Server and run the operation Get Gateway Data. 10. Eventia Analyzer cannot be upgraded to version NGX 2.0 via SmartUpdate, however SmartUpdate does support Eventia Analyzer license operations. VPN-1/FireWall-1 NGX R65 Known Limitations Supplement. Last Update — February 4, 2008 5:37 pm 36
SmartUpdate Miscellaneous 11. When running Fetch CPInfo on a non-Windows Management server, while trying to fetch CPInfo for the Management itself, in certain cases the command may halt unexpectedly. In this case, rerun the command, or run CPInfo locally. 12. When upgrading to any NGX version from any pre-NGX version (e.g., R55), the SmartUpdate Package Repository is not upgraded. After the upgrade, the SmartUpdate Package Repository will therefore be empty. 13. In SmartDashboard, the version number of an NGX (R60A) gateway may be changed to NGX (R60) when performing an operation via SmartUpdate. There are two workarounds to this issue: • Always have SmartDashboard open when performing SmartUpdate operations on an NGX (R60A) gateway. • If the version number has changed, open SmartDashboard and manually change the gateway's version to NGX (R60A). 14. If, while pushing new firmware to a UTM-1 Edge device, the Secondary SmartCenter has just failed over, the firmware may not be successfully installed. To resolve this issue, synchronize the Edge device with the Secondary SmartCenter and run the Push Now operation again. Platform Specific — Nokia 15. Upgrade All and separate transfer and install is not supported on flash-based Nokia. To resolve this issue you should explicitly install Nokia IPSO and thereafter you should install the Check Point products, one by one. Alternatively, use Nokia Voyager to install the wrapper and manage the installation packages. 16. When trying to install or verify an NG_AI R55P HFA package via SmartUpdate, the following error message may be displayed Package has wrong format. In this case, you should install your package locally on a module. 17. When upgrading Nokia flash-based machines via SmartUpdate, the following error message is displayed at the end of the upgrade process Execution error. CPRID session timed out. It is highly probable that your module was successfully upgraded, and that this message can be safely ignored. To ensure that this is the case, run the operation Get Gateway Data for this gateway and see that the module was indeed upgraded in SmartUpdate. Platform Specific — SecurePlatform 18. When using the SmartUpdate option Upgrade All, make sure that a VPN-1 Power/UTM Linux package is not in the Package Repository of any gateway running on SecurePlatform. Policy Installation 19. When upgrading from R55W on a SecurePlatform machine, SmartUpdate will not reestablish a connection with the gateway after reboot. This is caused by the gateway failing to fetch a new policy and starting with an initial policy. To resolve this issue, go to the gateway and fetch the policy manually, or install policy from the SmartDashboard. GUI 20. The feature Add Package From Download Center is not supported if the machine running SmartUpdate accesses the Download Center through a proxy server. Licensing 21. If a local license is detached from the license repository and then reattached without first closing SmartUpdate, the license appears in the repository as unattached. In such a scenario, either attach the license manually, or close and restart SmartUpdate before reattaching the license. VPN-1/FireWall-1 NGX R65 Known Limitations Supplement. Last Update — February 4, 2008 5:37 pm 37
Page 1 and 2: Check Point NGX R65 Known Limitatio
Page 3 and 4: ClusterXL ClusterXL In This Section
Page 5 and 6: ClusterXL 2. Performing an SNMP que
Page 7 and 8: ClusterXL Platform Specific — Sol
Page 9 and 10: ClusterXL 39. The following Web Int
Page 11 and 12: Endpoint Security Endpoint Security
Page 13 and 14: Endpoint Security 18. Endpoint Secu
Page 15 and 16: Eventia Suite 15. To upgrade a dist
Page 17 and 18: Firewall 5. The name of the install
Page 19 and 20: Firewall 31. In a cluster environme
Page 21 and 22: Firewall SecureClient 56. Policy in
Page 23 and 24: Provider-1/SiteManager-1 3. After u
Page 25 and 26: Provider-1/SiteManager-1 In additio
Page 27 and 28: Provider-1/SiteManager-1 SmartUpdat
Page 29 and 30: SecureXL SecureXL In This Section G
Page 31 and 32: SmartCenter Server SmartCenter Serv
Page 33 and 34: SmartCenter Server Policy Installat
Page 35: SmartPortal Platform Specific - Nok
Page 39 and 40: VPN VPN VPN Communities 1. When man
Page 41 and 42: VPN-1 Power VSX 27. When connecting

NGX R65 Release Notes - Check Point

Create successful ePaper yourself

Delete template?

Save as template?