Browse Prior Art Database

Optimized Enterprise Extender Disconnect (DISCNT) timer processing

IP.com Disclosure Number: IPCOM000028488D
Original Publication Date: 2004-May-17
Included in the Prior Art Database: 2004-May-17
Document File: 2 page(s) / 44K

Publishing Venue

IBM

Abstract

Eliminate or reduce the amount of disconnect timer (DISCNT) processing overhead for Enterprise Extender.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

Optimized Enterprise Extender Disconnect (DISCNT) timer processing

Main Idea

Disclosed is a solution to eliminate or reduce the DISCNT timer processing overhead for Enterprise Extender.

Enterprise Extender (EE) connections are represented by switched physical units (PUs). Since switched PUs support disconnect (DISCNT) processing, EE PUs do as well. The DISCNT timer simply inactivates the EE PU when there are no more users. Rapid Transport Protocol (RTP) pipes are the only EE users. If a DISCNT timer is in use, when the last RTP pipe is no longer using the EE connection, the EE PU is inactivated. RTP pipes which traverse a switched connection, set the ALIVE timer to half of the DISCNT time value. These RTP ALIVE status flows let the EE connection know there are still active RTP pipes using this EE connection.

For EE DISCNT timer processing, the EE connection must be able to detect when there are no more RTP pipes using the connection. For one hop RTP pipes (which includes a single physical hop across a two-hop EE virtual routing node (VRN)) which traverse an EE connection, it is simple for the EE endpoints to recognize when there are no more RTP pipes using the EE connection. For RTP pipes which are automatic network routing (ANR) through the EE connection, this is more difficult for the EE connection to detect when the RTP pipe is no longer using the EE connection. For EE connections to detect when ANR traffic halts, it must monitor a period of data flow inactivity. Generally, the DISCNT timer is set and a boolean variable, such as Data_Flowed_over_EE, is set to FALSE. When EE detects data traffic, the Data_Flowed_over_EE variable is always set to TRUE. When the DISCNT timer pops, the Data_Flowed_over_EE variable is checked to see if there is RTP traffic flowing. If there was, the Data_Flowed_over_EE variable is set to FALSE and the DISCNT timer reset for the next interval. If there is no traffic flowing, the EE connection is inactivated. The central processing unit (CPU) costs for managing a DISCNT timer for a single EE connection may not significant, but in a large production environment where there are thousands of EE connections, the...