I have been using _DUMPNATTCP for a long time to help determine if myfirewall filters are working correctly. It has been a great help.
However, I am still fighting with occasional (every two weeks or so)
lockups and abends that involve the proxy. I have been told that this

can be caused by conflicts with DNS.
So I removed DNS proxy and opened port 53, DNS Stateful filtering,
from the private network to the public side.
Just out of curiousity, I decided to try the command _DUMPNATUDP.
I was really shocked when I saw the NATUDP.LOG file. Here is an
example taken from the end of the file. (I have changed the actual IP

addresses.)
Is it normal for this file to have this many entries? I was under
the impression that the NAT table has a practical limit. I have beenmonitoring this for a couple of days. The NATTCP.LOG file changes asPeople use the firewall for various applications. The port closes
right after the application closes, as it should. But the NATUDP.LOGfile seems to stay at 5000 entries. I would just like to compare this

with other BorderManagers and see if this is the way the file should
look.
If this is normal, I will look elsewhere to solve the abends.

(lines 1- 4993 ommitted for simplicity)

4994. 10.1.1.254 | 2392 | 59563 | 128.1.8.7 | 53

4995. 10.1.1.254 | 2391 | 59564 | 128.1.1.7 | 53

4996. 10.1.1.254 | 2391 | 59565 | 128.1.8.7 | 53

4997. 10.1.1.254 | 2377 | 59571 | 128.1.1.7 | 53

4998. 10.1.1.254 | 2377 | 59572 | 128.1.8.7 | 53

4999. 10.1.1.254 | 2376 | 59575 | 128.1.1.7 | 53

5000. 10.1.1.254 | 2376 | 59576 | 128.1.8.7 | 53