> Source: [sk69641](https://support.checkpoint.com/results/sk/sk69641) # sk69641 - FTP Server Network Requirements for Gaia on IP Series appliances installation | Property | Value | |----------|-------| | Solution ID | sk69641 | | Date Created | 2012-03-28 | | Last Modified | 2015-06-10 | | Technical Level | General | | OS | Gaia | ## Solution There are several requirements for the FTP server, which must be considered to perform an IPSO-to-Gaia upgrade. These requirements for Gaia are more stringent than what worked for IPSO, so previous success with FTP installation in IPSO does not guarantee that the Gaia installation will succeed. When you run the IPSO-to-Gaia upgrade script ([sk66569](http://supportcontent.checkpoint.com/solutions?id=sk66569 "IPSO-to-Gaia Upgrade Scripts")), it will pre-test the connection to FTP server for suitability upgrading to Gaia. If the script reports problems, it would be due to one of the issues noted here. The most basic issue is to ensure you have a route from the IP address of the Appliance to the FTP server, and that nothing is blocking incoming FTP requests to the FTP server. FTP server must be five or fewer hops away (as determined via "*traceroute* "). Otherwise, the upgrade tool will refuse to continue (because we have reports of FTP problems when accessing more distant servers during upgrade). Finally, the FTP server cannot be connected via an XMC port, so use a PMC NIC or the on-board ports (which are PMC). Once the basic connectivity is established, it is necessary to configure a particular option for the FTP server: the option is called "*maximum connections per IP address* " or "*maximum number of clients from the same IP address"* (refer to the documentation for your particular FTP server to find what option is needed - for example, *vsftpd* (Very Secure File Transfer Protocol Daemon) calls this option "*max_per_ip*"). In many FTP servers, the default value for this option is "*unlimited* ", which is ideal. Other (lower) values of this attribute are dependent on how many clients connect to the FTP server and what kind of transfers they request. When the value is too low, it is likely that an error message similar to the following would appear during the FTP download: `Traceback (most recent call first):` `File "/usr/lib/anaconda/splatcomps.py", line 44, in urlopen errnum, str(msg))` `File "/usr/lib/anaconda/splatcomps.py", line 57, in copyFile s = self.urlopen(self.source_tree + source_dir + source)` `File "/usr/lib/anaconda/splatcomps.py", line 134, in copyNextFile ret = self.copyFile(source, dir, dest)` `File "/usr/lib/anaconda/textw/splatcomps_text.py", line 28, in splatCompProcess while (sc.copyNextFile() == -1):` `File "/usr/lib/anaconda/textw/splatcomps_text.py", line 40, in __call__splatCompProcess("Blades", screen, method, sc)` `File "/usr/lib/anaconda/text.py", line 581, in run rc = win(self.screen, instance)` `File "/bin/anaconda", line 1000, in ? anaconda.intf.run(anaconda)` `AttributeError: LoggerClass instance has no __call__ method` `> /usr/lib/anaconda/splatcomps.py(44)urlopen()-> errnum, str(msg))(Pdb)` `tmp/runanaconda: line 4: 2038 Killed`
Some additional considerations if the installation fails, and the maximum connection count is set high enough: there might be a connection timeout on the FTP server which is set too low, or excess congestion on the network during the FTP transfers. If the FTP server is hosted on a Windows OS machine, it is necessary to run the batch file *copyrpms.bat*, located at the top directory of the ISO file. This file copies the installation files instead of soft-linking them, which overcomes a limitation of the Windows OS file system. There are some considerations about where to mount the ISO on the FTP server: 1. If the Gaia OS take is mounted under non-FTP directory, then the full path to the Gaia take is needed. For example, user Joe has Gaia take mounted under "/home/Joe/gaia". This user needs to specify "/home/Joe/gaia" as the path to the Gaia take. Neither "gaia", nor "./gaia" would work. 2. If the Gaia take is mounted under "/var/ftp" directory, and an FTP user account is used for installation, then the shortened path can be used. For example, Gaia take is mounted at "/var/ftp/gaia". Then FTP user can specify "gaia" (or "/gaia") as the path to the Gaia take. 3. If the Gaia take is mounted under "/var/ftp" directory and a non-FTP user account is used for installation, the full path to the Gaia take is needed. For example, Gaia take is mounted under "/var/ftp/gaia". And user Joe does not have an FTP account. Then this user needs to specify "/var/ftp/gaia" as the path when he uses his credentials for the installation. **Notes:** * For the IP280, IP290, IP690, IP1280 and IP2450 appliances there is an alternative to using the FTP server for installation - you can use a USB and ISOmorphic Tool. See [sk83200](http://supportcontent.checkpoint.com/solutions?id=sk83200) for information about this. * For the IP390 and IP560 appliances, there is no alternative to FTP installation. --- # Agent Instructions This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products. ## Navigating This Knowledge Base - **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt) - **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml) - **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}` - **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content