PM76509: Shipping server needs to account for Windows 'deferred bind on connect' behavior when strict port allocation in use.

Fixes are available

APAR status

Closed as program error.

Error description

When using the IBM Rational ClearCase MultiSite shipping server
in a firewall-enabled configuration with strict outbound port
allocation on Microsoft Windows 2008 R2 Server, connection
errors may occur, causing hosts to be incorrectly flagged as
down.

This issue is caused by a new Windows Sockets behavior in the
most recent version of Microsoft Windows.

The current workarounds are:
1) Do not use MSSHP_STRICT port allocation.
2) Use a Unix or Linux host to provide firewall-compatible
shipping server services.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:                                              *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
shipping server fails on connect command even if with a
valid binding port

Problem conclusion

A fix is available in ClearCase versions 7.1.2.10 and
8.0.0.6

Temporary fix

Comments

APAR Information

APAR number
PM76509
Reported component name
CLRCASE MSITE W
Reported component ID
5724G3200
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-11-05
Closed date
2013-03-20
Last modified date
2013-03-20

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
CLRCASE MSITE W
Fixed component ID
5724G3200

Applicable component levels

R800 PSN
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSSH3S","label":"Rational ClearCase MultiSite"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
20 March 2013

Tips

PM76509: Shipping server needs to account for Windows 'deferred bind on connect' behavior when strict port allocation in use.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R800 PSN

Document Information

Share your feedback

Need support?