APAR status
Closed as program error.
Error description
For FTP, the data port is opened from the backend server to the client. WebSPhere Edge Load Balancer sees a [SYN, ACK] as the first packet on the connection. Load Balancer has a check that the [SYN, ACK] is only valid if using the wildcard port (0) or the default FTP data port of 20.
Local fix
N/A
Problem summary
When FTP involves a control port (client -> server) and a data port (server->client), LB will only work with the standard ports 20 & 21.
Problem conclusion
Modified code to allow default ftp ports to be changed. To change the default ports, user must enter "dscontrol e xm 47 <ControlPort> <DataPort>". This statement must come after the cluster is added but before the ports are added. Only the controlport should be added to LB. Affects all OSes. Fix levels : 5.1.1.77 6.0.2.73 6.1.0.16 Does not apply to ipv6 releases. NOTE-There can only be 1 FTP control/data pair. To balance traffic for multiple FTP sites, they will need to use the same ports but configured on different clusters.
Temporary fix
Comments
APAR Information
APAR number
PK50971
Reported component name
WAS LOAD BALANC
Reported component ID
5630A3611
Reported release
510
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-08-14
Closed date
2007-08-23
Last modified date
2007-08-23
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WAS LOAD BALANC
Fixed component ID
5630A3611
Applicable component levels
R510 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
26 May 2020