Troubleshooting FTP transfers

When you attempt to send files to IBM® by using FTP, such as a log package from the System Management page or a compressed file from the service tool, the upload cannot be completed. This problem might occur because of network or firewall restrictions.

When IBM Spectrum® Control uploads a log package to IBM Software Support, it is sent to the Enhanced Customer Data Repository (ECuRep) by using standard FTP protocol. The upload is secure and the data is encrypted with AES-128 key for each file part and RSA-2048 key for the key exchange. The name of the FTP server that receives the upload is ftp.ecurep.ibm.com.

If IBM Spectrum Control cannot connect to the FTP server because of firewall restrictions in your organization, you must open the necessary ports for FTP transfers from the IBM Spectrum Control server. Because standard, unencrypted FTP in passive mode is used for uploads (encryption is done that the data level, not the connection level), the firewall must be configured to allow passive FTP connections to ftp.ecurep.ibm.com. Contact your network administrator for assistance.

For older firewalls, open port 21 (the default FTP) and ports 65024 - 65535 (for passive FTP). For more information, see http://www.ibm.com/de/support/ecurep/send_ftp.html.

If your organization uses a proxy server for FTP, complete the following steps to troubleshoot uploads from IBM Spectrum Control:

Use a text editor to create a file that is named ibmsdduu.config.

In ibmsdduu.config, specify the proxy configuration to use.

To determine the specific information that must be included in ibmsdduu.config for your FTP proxy, review the following instructions:

SOCKS Server and HTTP Proxy Support
 
 -socks4 enable SOCKS 4 support
 -socks5 enable SOCKS 5 support
 -http_proxy enable support for http proxy tunneling
 
 -socks4 -sock5 and -http_proxy are exclusive, the last switch in
 command line is used
 
 -proxyhost=<host> define the address of the proxy or SOCKS server
 
 -proxyport=<port>  define the port of the proxy. 
                    default: 1080 for SOCKS4 and SOCKS5
                             8080 for http_proxy
                             
 -proxyuser=<userid> define the userid for the proxy or SOCKS server
 -proxypw=<password> define the password for the proxy or SOCKS server
 
 proxy userid and proxy password are optional
 
 
 FTP Proxies
 
 ftp proxy support is enabled with a separate command line option.
 This enables the combination of SOCKS server and a ftp proxy if necessary.
 
 -ftp_proxytype=<type>  enables ftp proxy support and define the type of
                        the proxy. <type> is an integer, see 
                        ftp proxy types below 
                        Default: 0 - no proxy
                        
 -ftp_proxyuser         userid for the ftp proxy
 
 -ftp_proxypw password for the ftp proxy
 
 -ftp_proxyhost hostname or ip address of the ftp proxy
 
 -ftp_proxyport port number of the ftp proxy
                        Default: 21
                         
                        
  
  FTP Proxy Types
  
  There are several ftp proxy types known. Each type is using a different
  login procedure and needs different commands to connect to the target
  ftp server.                        
  
  In the list of supported ftp proxy types <server>,<user>,<password> 
  are refering to the target ftp server, <p_user> and <p_passwd> to the 
  ftp proxy account.
  
  -ftp_proxytype=0 
    no ftp proxy is used ( this is the default )
  
  -ftp_proxytype=1
    connect; USER <p_user>; PASS <p_passwd>; 
             SITE <server>; USER <user>; PASS <passwd>
            
 -ftp_proxytype=2
    connect; SITE <server>; USER <user>; PASS <passwd>
                          
 -ftp_proxytype=3             
    connect; USER <p_user>; PASS <p_passwd>;
             OPEN <server>; USER <user>; PASS <passwd>

  -ftp_proxytype=4             
    connect; OPEN <server>; USER <user>; PASS <passwd>
              
  -ftp_proxytype=5
    connect; USER <user>@<server>; PASS <passwd>
    
  -ftp_proxytype=6                                         
    connect; USER <p_user>@<server>; PASS <p_passwd>;
             USER <user>; PASS <passwd>

  -ftp_proxytype=7
    connect; USER <user>@<server> <p_user>;PASS <p_passwd>;
             ACCT <passwd>
             
  -ftp_proxytype=8
    connect; USER <user>@<server> <p_user>;PASS <passwd>;
             ACCT <p_passwd>
             
  -ftp_proxytype=9
    connect; USER <user>@<p_user>@<server>;PASS <passwd>;
             ACCT <p_passwd>
             
  -ftp_proxytype=10             
    connect; USER <user>@<p_user>@<server>;PASS <p_passwd>;
             ACCT <passwd>         
             
  -ftp_proxytype=11
    connect; USER <p_user>; PASS <p_passwd>;
             USER <user>@<server>; PASS <passwd>
             
  -ftp_proxytype=12  (CheckPoint Firewall 1)
    connect; USER <user>@<p_user>@<server>
    PASS <passwd>@<p_passwd>

Based on the type of FTP proxy server that you use, copy and paste the appropriate section from step 2a into ibmsdduu.config.
For the section that you pasted into ibmsdduu.config, provide information such as host name, port, user ID, and password, as needed.
For example:
```
-ftp_proxytype=1
-ftp_proxyuser=my_user_id
-ftp_proxypw=my_password
-ftp_proxyhost=ftp_proxy.my_company.com
-ftp_proxyport=21
```
Where:
- my_user_id and my_password represent the authentication credentials for connecting to the FTP proxy server.
- ftp_proxy.my_company.com represents the DNS name of the FTP proxy server.

Save the file to installation_dir/services, where installation_dir represents the directory where IBM Spectrum Control is installed.
The default installation directory is as follows:
- Windows™: C:\Program Files\IBM\TPC
- Linux® / AIX®: /opt/IBM/TPC
Try to upload the log package or compressed file again.

If you still cannot automatically upload a log package in the IBM Spectrum Control GUI, you can try uploading it manually. For information about how upload files to ECuRep manually, see the following topics:

Log packages are stored on the IBM Spectrum Control server at the following location: installation_dir/wlp/usr/servers/webServer/apps/WebServer.ear/TPC-GUI.war/serviceLog