LO92713: REQUESTS LOAD BALANCED FROM OLDER SERVERS GETTING REJECTED FOR NON-SPECIFIC DEVICE ID
Direct links to fixes
Closed as program error.
When a pre-22.214.171.124 Traveler server is load balancing a request to a 126.96.36.199 server and the request is for an operation that requires a device ID, the request is getting rejected for not being specified. This only applies to HA pools that are running different Traveler versions (should only be a small migration period of time) and only applies to requests that are load balanced between servers of the different versions (requests going to a same level server, whether load balanced or not, work successfully).
This problem is only experienced when running one or more 188.8.131.52 servers in an HA Pool with one or more pre 184.108.40.206 servers running at the same time. And even then the problem doesn't occur unless the load balance routes a user to one of the earlier servers but the request needs to be handled by the 220.127.116.11 server.
The IBM Traveler server has been updated to handle this scenario correctly and improve behavior when upgrading from older servers.
This fix will be included in IBM Traveler 18.104.22.168 and all later releases. For the latest available maintenance release see this technote: http://www.ibm.com/support/docview.wss?uid=swg24019529
Reported component name
LOTUS NOTES TRA
Reported component ID
NoSpecatt / Xsystem
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
LOTUS NOTES TRA
Fixed component ID
Applicable component levels
Translate this page: