NAT mechanics are complex, but NAT configuration is pretty simple. However, if something does not work as expected, there are a bunch of things you can do. The show ip nat translations and show ip nat statistics commands covered in previous sections usually provide enough information to be able to identify problems with NAT. However there is another useful tool you should probably have in your toolbox and that is the debug ip nat command:
IP NAT debugging is on
*Mar 1 00:20:24.007: NAT*: s=192.168.1.2->18.104.22.168, d=22.214.171.124 
*Mar 1 00:20:24.035: NAT*: s=126.96.36.199, d=188.8.131.52->192.168.1.2 
*Mar 1 00:20:29.355: NAT*: s=192.168.1.3->184.108.40.206, d=220.127.116.11 
*Mar 1 00:20:29.395: NAT*: s=18.104.22.168, d=22.214.171.124->192.168.1.3 
*Mar 1 00:20:33.583: NAT*: s=192.168.1.4->126.96.36.199, d=188.8.131.52 
*Mar 1 00:20:33.599: NAT*: s=184.108.40.206, d=220.127.116.11->192.168.1.4 
The above output is from router R1 configured with Static NAT as presented earlier in the chapter. Nothing is broken here and the configuration is good. We generate a single ping from each of the inside hosts 192.168.1.2, 192.168.1.3, 192.168.1.4 to the server 18.104.22.168. You can see six debug entries in the above output for outgoing as well as return packets. In the outgoing packets, the source IP address is translated. While in the return packets, the destination IP address is translated.
The debug ip nat command can be used to verify the operation of NAT displaying information about each packet the router translates. This command also displays information about certain errors, such as the failure to allocate a global address.
As a general rule, you should always use show commands first for verification and troubleshooting. All debug commands should be used only when you have exhausted your options with show commands. These debug commands consume resources namely CPU cycles and memory, and should be used with caution on production networks especially if you love your current job.