Nov 2006
Checkpoint Secure Platform (SPLAT) Smartcentre

Found this page that described the same problem, and a likely solution:
The management station returned a 1, indicating that it was indeed a firewall so we unloaded the firewall policy:cpprod_util FwIsFireWallModule
fw unloadlocal
got rid of the installed policy temporarily and we then changed the setting:
Restarting the firewall services saw everything working fine:cpprod_util FwSetFireWallModule 0
but a reboot left us in the exact same position, with the node loading the "initial" firewall policy on boot, even though it was now reporting itself not to be a firewall enforcement node. (now, trying to perform an "fw unloadlocal" resulted in the SPAT box telling us that it could not, because it was not a firewall.cprestart
Now there are ways to prevent the initial policy from loading at bootup , but I am always after a cleaner install, and less hacking of a nice fresh clean system, so we gave Checkpoint a call. The Checkpoint guy promptly advised us that the use of SmartView Monitor was not supported, and was not even supposed to work unless the node was also a firewall. Now this was news to us, as we had been running Smartview Monitor for the last 2 years on this system without skipping a beat.
It did however lead us in the right direction: We reinstalled the SPLAT server, only selected Smartcentre, configured it as a secondary management server, got the whole thing working, THEN installed Smarview Monitor after the fact (just like I now remember we did when it was built the first time!!)
Problem solved. It would appear that if you install Smartview Monitor at the initial run of cpconfig, it assumes that you want to make the node an enforcement point, but if you install it as a dedicated Smartcentre first, then install Smartview Monitor, it works.
Ubuntu Server 6.1.0 under Parallels: unknown
interrupt or fault at EIP 00000060 c0100295
00000294

unknown interrupt or fault at EIP 00000060 c0100295 00000294
The install was a dead duck...
Found this article on the Parallels support site that saw me through. Required steps were as follows:
1) Boot from CD, type 'rescue' at the prompt to launch the rescue kernel image;
2) Follow the bouncing ball, and answer the questions. I had to set up the NIC addressing manually.
3) Select the option: "Execute a shell in /dev/hda1"
4) Install the generic kernel: (you will need an Internet connection...)
4.1) apt-get install linux-image-generic
4.2) exit
5) The installer hung. Pressed (fn*) ALT-F2 to get to a different console;
6) Unmounted the live disk: umount /dev/hda1
7) Rebooted: shutdown -r now
8) When logged in to the new system, change the GRUB default to boot the Generic Kernel:
8.1) vi /boot/grub/menu.lst
8.2) change the line "default 0" to "default 2"
9) reboot.
* fn needed as I am on a laptop, and F?? keys are not real F?? keys by default...