Testing mechanism for FTAM over X.25 with one FTAM Initiator and multiple FTAM Responders with distinct NUAs
Original Publication Date: 2004-Oct-13
Included in the Prior Art Database: 2004-Oct-13
Disclosed here is an inexpensive, faster, and comprehensive software solution to test changes to Open Systems Interconnection's (OSI's) File Transfer, Access, and Management (FTAM) software between an FTAM Initiator and mulitple FTAM Responders within laboratory test environment that mimicks real world production environment.
Testing mechanism for FTAM over X .25 with one FTAM Initiator and multiple FTAM Responders with distinct NUAs
File Transfer, Access, and Management (FTAM) is an application in the Open Systems Interconnection (OSI) networking stack. FTAM Initiators (clients) and FTAM Responders (servers) can communicate over various networks within Local Area Network (LAN) and Wide Area Network (WAN) realm. Within WAN, one of the most common networks used is X.25 network.
While making changes to an application such as FTAM or any other element of the OSI stack (such as Application Layer, Presentation Layer, Session Layer, Transport Layer, Network Layer) on which FTAM runs, typically transport layer driver over X.25 network, it is essential to test the changes with the setup such that an FTAM Initiator over an X.25 port with an Network User Address (NUA) initiates requests to more than one FTAM Responders over distinct ports with distinct NUAs.
Although in a test environment or during problem recreation such as network memory leaks, FTAM Initiator running on a machine with mulitport X.25 adapter can initate requests to FTAM Responder which is running on another machine with typically multiport X.25 adapter connected via a modem eliminator, communication is between two fixed and hardwired ports (i.e between two fixed and hardwired NUAs), one each on multiport X.25 adapters on two distinct machines.
But it is important that one FTAM Initiator running over an NUA be able to initiate requests to more than one FTAM Responders running over distinct NUAs simultaneously because such is the production environment at customer sites where one machine running FTAM Initiator over an NUA is initiating multiple requests to more than one telephone switches, each telephone switch with distinct NUA running FTAM Responder simultaneously.
There are couple of solutions to this. One of them is to use X.25 cloud i.e. connect the machines on which FTAM Responder and FTAM Initiator are running to the X.25 cloud. Thus one FTAM Initiator can not initiate requests to more than one FTAM Responders on more that one machine. This solution is expensive and not every testing facility is equipped to have X.25 cloud.
Another solution is to connect FTAM Initiator to a fan-out device which on ther other end con...