Technical data

ServerIron ADX NAT64 Configuration Guide 7
53-1002288-02
NAT64 Connection logging
1
DRAFT: BROCADE CONFIDENTIAL
• NAT pool IP
• NAT port
A user can recreate an IPv6 destination IP address by concatenating the NAT64 prefix+ the IPv4
destination IP address.
Currently a Syslog message is sent each time a flow session pair is created. There is no buffering or
batching in the current release.
Beginning with release 12.301a, the connection creation is logged. The ServerIron ADX does not
currently log connection teardown.
NOTE
This feature is only applicable to Stateful NAT64 since no sessions are created for Stateless NAT64
traffic.
NOTE
Enabling NAT64 logging will have an impact on performance.
Configuring NAT64 Connection logging
To enable NAT64 Connection logging on a ServerIron ADX, you must configure the IP address of the
external Syslog Server and enable NAT64 connection-logging.
Configuring the IP address of the external Syslog Server
You can configure the IP address of the external Syslog Server using the following commands.
ServerIronADX#configure terminal
ServerIronADX(config)# logging 100.100.100.1
ServerIronADX(config)#
Syntax: [no] logging <ip_address>
Enabling NAT64 connection-logging
You can enable NAT64 connection-logging using the following commands.
adx-nat64#conf t
adx-nat64(config)#nat64 connection-log
adx-nat64(config)#
Syntax: [no] nat64 connection-log
Example of NAT64 Connection logging
The following example displays Syslog output for NAT64 Connection logging.
USER.INFO Jul 13 02:44:47 192.168.13.1 NAT64-EST proto=UDP
sip=2013::20c:29ff:fe06:4473 sp=53947 prefix=3013:: dip=192.168.130.200 dp=00053
nip=192.168.130.10 np=37888
USER.INFO Jul 13 02:44:57 192.168.13.1 NAT64-EST proto=TCP
sip=2013::20c:29ff:fe06:4473 sp=35659 prefix=3013:: dip=192.168.130.200 dp=00053
nip=192.168.130.10 np=37889