Skip to main content

How to Install Gaia on an IP Appliance

How to Install Gaia on an IP Appliance



Youtube Click HERE

 

How to Install Gaia on an IP Appliance

 

Objective:

Clean installation of Gaia on an IP Appliance with IPSO
Set up the environment:
Procedure:
Step 1: Get the IPSO to Gaia boot-manager package and the Gaia ISO image.
https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doShowupgradewizard
Step 2: Point the Gaia ISO on an FTP server:
Method:
  • Using Isomorphic tool transfer the image file and make pen drive bootable. 
  • Then transfer the contents of same pen drive to the pc where ftp server is configured. Extract it and place it in a folder (here the folder name is GAIA).]
  • After extraction, you have to run the *.bat file. 
Open up a command prompt, a black screen comes up. Drag and drop your .bat file onto the window. If that doesn’t work us cd (change directory) to go to where the file is and then press enter. I'll give you an example, let’s say execute.bat is on my desktop: 

start>run>cmd (enter) then with the window open cd C:\GAIA/(enter) then execute.bat (enter).
  • Check for the FTP server configuration parameters and point the ISO folder path (here my path is C:/GAIA) to be installed.
Initially:
  • Parameters to be set are
Step3:  Now download the R7X.XX Gaia boot manager (*.sh) and place it in the appliance location /script.  Give chmod 777 and Install as shown below.
  • Verify that the boot manager is located in the logical drive ad0 by running the command
ipsctl –a | grep CF
 The output will be similar to
hw:disk:ad:0:location = InternalCF
hw:disk:ad:0:type = CF-INTERNAL-IDE
Once the Gaia boot manager is installed successfully, appliance will reboots and (press 1) shows as below.
Step4:  Follow the instructions and enter the data. Make sure Ftp server interface is up and running (here interface from appliance to ftp is eth-s4p1).
Device reboots and starts installing Gaia if all the values are correct
  • System restarts once the installation is completed. 
Step5: Now we can run first time wizard by using the IP address of the appliance

Comments

Popular posts from this blog

Checkpoint firewall common commands part 2

Checkpoint firewall common commands part 2 For basic firewall informaton gathering: fgate stat -Status and statistics of Flood-Gate-1. fwaccel <stat|stats|conns>  – View status, statistics or connection table of SecureXL. fw getifs -Show list of configured interfaces with IP and netmask. cpstat <app_flag> [-f flavour] -View OS, HW and CP application status. Issue cpstat without any options to see all possible application flags <app_flag> and corresponding flavours. Examples: cpstat fw -f policy – verbose policy info cpstat os -f cpu – CPU utilization statistics cpinfo -y all   -List all installed patches and hotfixes. cpd_sched_config print -Show task scheduled with CPD scheduler. enabled_blades -View enabled software blades avsu_client [-app <app>]   , get_version <app>  -Get signature version and status of content security .Without the -app option “Anti Virus” is used. show configuration -Show

Unable to Connect to Server Checkpoint R80

Unable to Connect to Server Checkpoint R80 Unable to Connect to Server A connection to the management server will fail if: A firewall between SmartConsole and the management server blocks Port 19009 -  port 19009 is used for a new R80 service. Allow traffic on this port for all clients and management servers. No GUI clients are assigned -  Open the Gaia Portal. If the First Time Configuration Wizard opens, complete it. If the First Time Configuration Wizard has already run, open  User Management > GUI Clients  and add a client. When using Multi-Domain Security Management, connect SmartConsole to the Multi-Domain Server and make sure the domains have GUI clients assigned to them. The required processes are not reachable -  Make sure the computer with SmartConsole installed can reach the IP address of the management server, and that these server processes are up and running: cpm fwm Operation time out  – Your connection to the management (cloud demo

Configuring Proxy ARP for Manual NAT

Configuring Proxy ARP for Manual NAT Symptoms After creating a Manual Static NAT rule, Security Gateway does not answer the ARP Requests for the Static NATed IP address that was configured in the Manual NAT rule. Security Gateway replies to ARP requests with a wrong MAC address, mostly for the NAT traffic.  Introduction Let us consider the following scenario: Two networks ( Network_A  and  Network_B ) are separated by a Security Gateway (single Security Gateway or ClusterXL). On each network, there is a host ( Host_A  on  Network_A ,  Host_B  on  Network_B ). Let us assume, that  Network_A  represents the  Internal  network, and  Network_B  represents the  External  network. According to the existing standards, when  Host_B  needs to send data to  Host_A , an ARP Request for the MAC address of  Host_A  will be sent by  Host_B  to  Network_B . Since  Host_A  is located on another network, and the Security Gateway acts as a router, this ARP Request (sent