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
Labels:

Comments

Post a Comment

Popular posts from this blog

CLI Commands for Troubleshooting FortiGate Firewalls

CLI Commands for Troubleshooting FortiGate Firewalls 2015-12-21 Fortinet , Memorandum , Network Cheat Sheet , CLI , FortiGate , Fortinet , Quick Reference , SCP , Troubleshooting Johannes Weber This blog post is a list of common troubleshooting commands I am using on the FortiGate CLI . It is not complete nor very detailled, but provides the basic commands for troubleshooting network related issues that are not resolvable via the GUI. I am not focused on too many memory, process, kernel, etc. details. These must only be used if there are really specific problems. I am more focused on the general troubleshooting stuff. I am using it personally as a cheat sheet / quick reference and will update it from time to time. Coming from Cisco, everything is “show”. With Fortinet you have the choice confusion between show | get | diagnose | execute . Not that easy to remember. It is “ get router info6 routing-table” to show the routing table but “ diagn...
Post a Comment
Read more

From MPLS to SD-WAN to SASE: An Evolution of Enterprise Networking

From MPLS to SD-WAN to SASE: An Evolution of Enterprise Networking The way we do business is changing. As critical business applications migrate to the cloud, and the mobile workforce continues to grow, networking and security solutions need to evolve in order to meet the changing business needs. Gartner believes (and we agree) that the future of networking lies with  SASE (Secure Access Service Edge)  – the convergence of networking and security into one cloud service. Here’s why. 1990s – 2000s: MPLS and the Era of Clear Network Boundaries? Back in the day, networking models were hardware-centric and manually configured. Applications, data, and services lived within private datacenters and relied on remote access solutions to connect remote workers. Dedicated network connectivity, known as MPLS, was the preferred approach for connecting remote locations. MPLS provides predictable performance, low latency and packet loss, and central management. However, MPLS is ...
Post a Comment
Read more

FortiGate: Upgrading the firmware via CLI

FortiGate: Upgrading the firmware via CLI To use the following procedure, you must have a TFTP or FTP server that FortiDB can connect to. You must also log in using the “admin” administrator account. Start the FTP or TFTP server. Copy the new firmware image file to the FTP or TFTP server. Log into the CLI. Verify that FortiDB can connect to the FTP or TFTP server. For example, if the IP address of the TFTP server is 192.168.1.168, enter the CLI command: execute ping 192.168.1.168 Enter the following command to copy the firmware image from the TFTP server to FortiDB: execute restore image ftp execute restore image tftp Where is the name and location of the firmware image file and or is the IP address of the FTP or TFTP server. For example, if the firmware image file name is image.out and the IP address of the FTP or TFTP server is 192.168.1.168, enter: execute restore image tftp image.out 192.168.1.168 FortiDB responds with the message: This oper...
Post a Comment
Read more