This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revisionBoth sides next revision |
| public:srmclientinstallation [2015-07-14 11:53] – [Proxy generation] Joern Kuensemoeller | public:srmclientinstallation [2015-09-01 12:51] – [FNAL/dCache client tools] Joern Kuensemoeller |
|---|
| |
| * 145.100.32.0/22, i.e. 145.100.32.0 to 145.100.35.255, for SURFsara | * 145.100.32.0/22, i.e. 145.100.32.0 to 145.100.35.255, for SURFsara |
| * 134.94.*.* for FZJuelich. | * 134.94.32.0/22, i.e. 134.94.32.0 to 134.94.32.255, for FZJuelich. |
| |
| Active gridftp can improve performance of a single transfer as it will use multiple parallel connections for retrieving a file. For the FNAL/dCache client, 'active' transfers are initiated if the ''-server_mode=passive'' setting is omitted. For the Berkely client, parallel transfers will be initiated when the ''-parallelism'' parameter is set to a value larger than 1. Since most cases LOFAR datasets consist of a large number of files, a similar performance improvement can be achieved by splitting the set of files over multiple srm copy processes. This is usually easier to set up than the firewall requirements. Note that e.g. the dCache client does not have a default setting for the gridftp port range. Further, srmcp ignores the GLOBUS_TCP_PORT_RANGE environment variable. You have to specify the port range (that you opened in your firewall) via the ''globus_tcp_prt_range'' option of srmcp, e.g.: | Active gridftp can improve performance of a single transfer as it will use multiple parallel connections for retrieving a file. For the FNAL/dCache client, 'active' transfers are initiated if the ''-server_mode=passive'' setting is omitted. For the Berkely client, parallel transfers will be initiated when the ''-parallelism'' parameter is set to a value larger than 1. Since most cases LOFAR datasets consist of a large number of files, a similar performance improvement can be achieved by splitting the set of files over multiple srm copy processes. This is usually easier to set up than the firewall requirements. Note that e.g. the dCache client does not have a default setting for the gridftp port range. Further, srmcp ignores the GLOBUS_TCP_PORT_RANGE environment variable. You have to specify the port range (that you opened in your firewall) via the ''globus_tcp_prt_range'' option of srmcp, e.g.: |