Troubleshooting NAT 1827Network diagramFigure 531 Export NAT log to log serverConfiguration proceduren The following only lists configurations pertinent to NAT logs. Configurationsregarding the IP addresses of the devices and NAT function are omitted here.# Specify to export the NAT logs of Device A to the NAT log server. system-view[DeviceA] userlog nat export host 3.3.3.7 9021# Set the source IP address of NAT log packets for Device A to 9.9.9.9[DeviceA] userlog nat export source-ip 9.9.9.9# Enable the NAT log function on Device A.[DeviceA] nat log enableYou must run XLog on the NAT log server or the system log server to view NAT loginformation.Troubleshooting NATSymptom 1: AbnormalTranslation of IPAddressesSolution: Enable debugging for NAT. Try to locate the problem based on thedebugging display. Use other commands, if necessary, to further identify theproblem. Pay special attention to the source address after the address translationand ensure that this address is the address that you intend to change to. If not,there may be an address pool bug. Also ensure a route is available between thedestination network and the address pool segment. Be aware of the possibleeffects that the firewall or the ACLs have to NAT, and also note the routeconfigurations.Symptom 2: InternalServer FunctionsAbnormallySolution: Check whether the internal server host is properly configured; whetherthe router is correctly configured with respect to the internal server parameters,such as the internal server IP address. It is also possible that the firewall that hasHost192.168.1.6/24Vlan -int1192.168 .1.5/24Eth1/0Eth1/11.1 .1.1/24Eth1/01.1.1.4/24Device A Device BLoop 12.2.2.2/24NAT log server/system log server3.3.3.7/24Eth1/2
