Firewall - Check Point

Firewall - Check Point Firewall - Check Point

downloads.checkpoint.com
from downloads.checkpoint.com More from this publisher
13.07.2015 Views

SecurePlatform1. Log into SecurePlatform.2. Place the CD into the CD drive.3. Enter the Expert mode.4. Type mount /mnt/cdrom.5. Type patch add/mnt/cdrom/SecurePlatform/patch/CPpatch_command_update.tgz6. Answer y when prompted.After this update is complete, the system will allow multiple upgrade operations.6. When upgrading from SecurePlatform FP2, FP3 and FP4, you must update the"patch" command before proceeding with the upgrade. To apply the patch, insertthe SecurePlatform installation CD and run the following commands:1. mount /mnt/cdrom2. patch add /mnt/cdrom/SecurePlatform/patch/CPpatch_command_update.tgzAfter applying this patch, proceed with the upgrade.7. The installation process fails with some USB CD-ROM models. Use the floppy tostart the installation, or install via the network.8. During upgrade, the following console messages can be safely ignored:• INIT: version 2.78 reloading• INIT: version 2.85 reloading9. During the SecurePlatform upgrade, the following message may appear:cpprod_util: error while loading shared libraries: libcpprod50.so: cannotopen shared object file: No such file or directoryThis message does not indicate any problem and can be ignored.10. The SecurePlatform WebUI management interface will only upload an upgradepackage if the browser being used is Microsoft Internet Explorer.11. On some older computers (usually 5-6 years old), the SecurePlatform CDROM willfail to boot due to BIOS limitations. In this case, create a boot floppy and use it tostart the installation.Unicast Routing12. If working with the Advanced Routing suite, and Multihomed Link Selection isconfigured with identical routes via multiple redundant interfaces, the followingworkaround is required:Enterprise Suite NGX R61 Known Limitations Supplement Last Update — February 7, 2007 22

SecurePlatform• If there are only two identical routes, one of the routes must be split into tworoutes: The first route covers half of the subnet and the second route the otherhalf of the subnet.13. Configuring any redistribute options in the RIP environment will remove the defaultredistribute rip and redistribute direct options. These options can beconfigured manually, if needed.14. Despite establishing OSPF adjacency, kernel-sourced routes may not be distributedimmediately. In those cases, a 10 minute delay may be experienced.15. During reboot, a number of Dynamic Routing messages appear on the console.These messages can be safely ignored.16. When working with VTI unnumbered interfaces, changes to the IP address of theproxy interface do not immediately register with Dynamic Routing. For the changesto take effect, run the commands drouter stop and drouter start.17. After running the command service network restart, the previous kernel routespersist. For the changes to take effect, run the commands drouter stop anddrouter start.18. When publishing a network from two (or more) sources with the same Distance andMetric, the network will be deleted from the RIB of the operating system. Aworkaround is to change the metric for one of the peers, or if one peer is reachedvia a different interface, to change the metric of one of the local interfaces.19. When changing the VTI netmask to a specific mask length, the Dynamic Routingdaemon creates three routes: two connected routes for local and remote IPs, andone additional network kernel route for a defined subnet. After VTI removal, thethird network route is preserved in the Dynamic Routing table, but removed fromthe OS routing table.Multicast Routing20. Defining NAT on a host that transmits multicast traffic is not supported.21. To enable multicast service on a VPN gateway functioning as a rendezvous point,add a rule to the Security Policy of that gateway to allow only the specific multicastservice to be accepted unencrypted, and to accept all other services only throughthe community.22. A SecurePlatform machine with more than 10 interfaces may encounter difficultyrunning Multicast Dynamic Routing protocols (as well as OSPF). This issue may beaddressed by adjusting the number of multicast groups that can be joined by asingle process. The limit is set in the fileproc/sys/net/ipv4/igmp_max_memberships, and the default number is 20.Enterprise Suite NGX R61 Known Limitations Supplement Last Update — February 7, 2007 23

SecurePlatform• If there are only two identical routes, one of the routes must be split into tworoutes: The first route covers half of the subnet and the second route the otherhalf of the subnet.13. Configuring any redistribute options in the RIP environment will remove the defaultredistribute rip and redistribute direct options. These options can beconfigured manually, if needed.14. Despite establishing OSPF adjacency, kernel-sourced routes may not be distributedimmediately. In those cases, a 10 minute delay may be experienced.15. During reboot, a number of Dynamic Routing messages appear on the console.These messages can be safely ignored.16. When working with VTI unnumbered interfaces, changes to the IP address of theproxy interface do not immediately register with Dynamic Routing. For the changesto take effect, run the commands drouter stop and drouter start.17. After running the command service network restart, the previous kernel routespersist. For the changes to take effect, run the commands drouter stop anddrouter start.18. When publishing a network from two (or more) sources with the same Distance andMetric, the network will be deleted from the RIB of the operating system. Aworkaround is to change the metric for one of the peers, or if one peer is reachedvia a different interface, to change the metric of one of the local interfaces.19. When changing the VTI netmask to a specific mask length, the Dynamic Routingdaemon creates three routes: two connected routes for local and remote IPs, andone additional network kernel route for a defined subnet. After VTI removal, thethird network route is preserved in the Dynamic Routing table, but removed fromthe OS routing table.Multicast Routing20. Defining NAT on a host that transmits multicast traffic is not supported.21. To enable multicast service on a VPN gateway functioning as a rendezvous point,add a rule to the Security Policy of that gateway to allow only the specific multicastservice to be accepted unencrypted, and to accept all other services only throughthe community.22. A SecurePlatform machine with more than 10 interfaces may encounter difficultyrunning Multicast Dynamic Routing protocols (as well as OSPF). This issue may beaddressed by adjusting the number of multicast groups that can be joined by asingle process. The limit is set in the fileproc/sys/net/ipv4/igmp_max_memberships, and the default number is 20.Enterprise Suite NGX R61 Known Limitations Supplement Last Update — February 7, 2007 23

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!