PR 232202 DSR Signaling Port Range Management: As of feature BUG 19107427 DSR 6.0, the DSR product has an overlapping enhancement port range (0-65535) for responder and initiator connections. Platform, OAM and signaling modules are all using the same port range for different types of connections for different services. There is likelihood of race conditions that can result in permanent socket binding failures. Several customers also have requested for the ephemeral local port range to be brought in compliance with IANA recommended port range. This DSR enhancement defines a port range partitioning for application use across DSR system and leaves an IANA compliant ephemeral port range for platform or other services use. IPFE initiator Support DSR releases to DSR 7.0, have IPFE Major feature PR 220164 support for only’ connections. enhancement ‘responder BUG 19092320 only’ and & responder’ ‘initiator ‘initiator connections are fixed DA-MP connections using IPFE Initiator+Responder static DA-MP IP addresses. Customers have Support provided feedback that initiator connections with PR 215682 static DA-MP IP addresses have operational, BUG 19087317 maintenance and service impacts synonymous with a mesh network and a single DSR view is required on the initiator side connectivity in the Diameter signaling network. BUG 20083083 Port Number Flexibility - The IPFE Initiator Major feature feature (PR 220164 / BugDB ID# 19092320) has enhancement been implemented in DSR 7.0 using the Port Striping method. This implementation is somewhat restrictive in terms of the port numbers that a specific DA-MP/TSA combination that can be used if IPFE Initiator is enabled for the TSA. The requirement here is to provide more flexibility to use any port within a configurable range on any DA-MP within a TSA to initiate connections for both Initiator – Connections as well as Initiator+Responder Connections.
PR 232202 BUG 19107427 DSR Signaling Port Range Management: As of DSR 6.0, the DSR product has an overlapping port range (0-65535) for responder and initiator connections. Platform, OAM and signaling modules are all using the same port range for different types of connections for different services. There is likelihood of race conditions that can result in permanent socket binding failures. Several customers also have requested for the ephemeral local port range to be brought in compliance with IANA recommended port range. This DSR enhancement defines a port range partitioning for application use across DSR system and leaves an IANA compliant ephemeral port range for platform or other services use. feature enhancement IPFE initiator Support PR 220164 BUG 19092320 IPFE Initiator+Responder Support PR 215682 BUG 19087317 DSR releases to DSR 7.0, have IPFE support for ‘responder only’ connections. ‘initiator only’ and ‘initiator & responder’ connections are fixed DA-MP connections using static DA-MP IP addresses. Customers have provided feedback that initiator connections with static DA-MP IP addresses have operational, maintenance and service impacts synonymous with a mesh network and a single DSR view is required on the initiator side connectivity in the Diameter signaling network. Major feature enhancement BUG 20083083 Port Number Flexibility - The IPFE Initiator feature (PR 220164 / BugDB ID# 19092320) has been implemented in DSR 7.0 using the Port Striping method. This implementation is somewhat restrictive in terms of the port numbers that a specific DA-MP/TSA combination that can be used if IPFE Initiator is enabled for the TSA. The requirement here is to provide more flexibility to use any port within a configurable range on any DA-MP within a TSA to initiate connections – for both Initiator Connections as well as Initiator+Responder Connections. Major feature enhancement
E57811-05.docx