02-02-2004 02:22 PM - edited 03-09-2019 06:18 AM
Perhaps some of my peers in Helath Care can help on this one.
We run an HL7 connection thru a PIX firewall. Basically, the server on the far end is listening on a port. (In this case 17303), If I issue a "clear xlate" on the pix, and then try to send a packet to the listener, the transaction fails.
The application folks have to go into the system and 'reset" the lines, then the transaction will pass.
Any ideas?
02-02-2004 04:02 PM
If this is a persistent connection then the remote side is not getting reset.
In a different industry we had the same problem here but with regards to timeouts, not clear xlates (although the concept is the same). Specifically, if the timeout was hit and the connection was cleared from the table (same as issuing a clear xlate) the remote machine was never aware of this happening -- so it's got a persistent listener listening on a connection which doesn't exist anymore!
In this case your best option is to have a heartbeat put into the connection if it's going to have that xlate table cleared on a regular basis. Then when the translations are cleared the remote side will "notice" and reset it's own connections.
02-03-2004 07:01 AM
The application needs to use TCP keepalives so that it can recognize a lost peer.
Is this a recurring problem? You can selectively clear xlate entries by local and global addresses so as not to interupt other connections like the HL7.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide