The configuration process involves creating and connecting the following configuration objects.

1. On the Main tab, click Local Traffic > Pools .
   The Pool List screen opens.
2. Click Create.
   The New Pool screen opens.
3. In the Name field, type a unique name for the pool.
4. Using the New Members setting, add the IP address for each IPFIX collector that you want to include in the pool:
   1. Type the collector's IP address in the Address field, or select a node address from the Node List.
   2. Type a port number in the Service Port field.
      By default, IPFIX collectors listen on UDP or TCP port 4739 and Netflow V9 devices listen on port 2055, though the port is configurable at each collector.
   3. Click Add.
5. Click Finished.

1. On the Main tab, click System > Logs > Configuration > Log Destinations .
   The Log Destinations screen opens.
2. Click Create.
3. In the Name field, type a unique, identifiable name for this destination.
4. From the Type list, select IPFIX.
5. From the Protocol list, select IPFIX or Netflow V9, depending on the type of collectors you have in the pool.
6. From the Pool Name list, select an LTM^® pool of IPFIX collectors.
7. From the Transport Profile list, select TCP, UDP, or any customized profile derived from TCP or UDP.
8. The Template Retransmit Interval is the time between transmissions of IPFIX templates to the pool of collectors. The BIG-IP system only retransmits its templates if the Transport Profile is a UDP profile.
   An IPFIX template defines the field types and byte lengths of the binary IPFIX log messages. The logging destination sends the template for a given log type (for example, NAT44 logs or customized logs from an iRule) before sending any of those logs, so that the IPFIX collector can read the logs of that type. The logging destination assigns a template ID to each template, and places the template ID into each log that uses that template.

   The log destination periodically retransmits all of its IPFIX templates over a UDP connection. The retransmissions are helpful for UDP connections, which are lossy.

9. The Template Delete Delay is the time that the BIG-IP device should pause between deleting an obsolete template and re-using its template ID. This feature is helpful for systems that can create custom IPFIX templates with iRules.
10. The Server SSL Profile applies Secure Socket Layer (SSL) or Transport Layer Security (TLS) to TCP connections. You can only choose an SSL profile if the Transport Profile is a TCP profile. Choose an SSL profile that is appropriate for the IPFIX collectors' SSL/TLS configuration.
    SSL or TLS requires extra processing and therefore slows the connection, so we only recommend this for sites where the connections to the IPFIX collectors have a potential security risk.
11. Click Finished.

1. On the Main tab, click System > Logs > Configuration > Log Publishers .
   The Log Publishers screen opens.
2. Click Create.
3. In the Name field, type a unique, identifiable name for this publisher.
4. Use the Log Destinations setting to select an existing IPFIX destination (perhaps along with other destinations for your logs): click any destination name in the Available list, and move it to the Selected list.
   Important: If you configure a log publisher to use multiple logging destinations, then, by default, all logging destinations must be available in order to log to each destination. Unless all logging destinations are available, no logging will occur. If you want to log to the available logging destinations when one or more destinations become unavailable, you must set the logpublisher.atomic db key to false. If all the remote high-speed log (HSL) destinations are down (unavailable), setting the logpublisher.atomic db key to false will not work to allow the logs to be written to local-syslog. The logpublisher.atomic db key has no effect on local-syslog.
5. Click Finished.

1. On the Main tab, click Carrier Grade NAT > Logging Profiles > LSN .
   The LSN profile list screen opens.
2. Click Create.
   The New LSN Logging Profile screen opens.
3. In the Name field, type a unique name for the logging profile.
4. From the Parent Profile list, select a profile from which the new profile inherits properties.
5. For the Log Settings area, select the Custom check box.
6. For the Log Settings area, select Enabled for the following settings, as necessary.

   Setting	Description
   CSV Format	Generates log entries in comma-separated-values (CSV) format.
   Start Outbound Session	Generates event log entries at the start of a translation event for an LSN client.
   End Outbound Session	Generates event log entries at the end of a translation event for an LSN client.
   Start Inbound Session	Generates event log entries at the start of an incoming connection event for a translated endpoint.
   End Inbound Session	Generates event log entries at the end of an incoming connection event for a translated endpoint.
   Quota Exceeded	Generates event log entries when an LSN client exceeds allocated resources.
   Errors	Generates event log entries when LSN translation errors occur.
   Subscriber ID	Allows for subscriber ID logging.

7. Click Finished.

1. On the Main tab, click Carrier Grade NAT > LSN Pools > LSN Pool List .
   The LSN Pool List screen opens.
2. Select an LSN pool from the list.
   The configuration screen for the pool opens.
3. From the Log Publisher list, select the log publisher that the BIG-IP system uses to send log messages to a specified destination.
   Important: If you configure a log publisher to use multiple logging destinations, then, by default, all logging destinations must be available in order to log to each destination. Unless all logging destinations are available, no logging can occur. If you want to log to the available logging destinations when one or more destinations become unavailable, you must set the logpublisher.atomic db key to false. If all the remote high-speed log (HSL) destinations are down (unavailable), setting the logpublisher.atomic db key to false will not work to allow the logs to be written to local-syslog. The logpublisher.atomic db key has no effect on local-syslog.
4. Optional: From the Logging Profile list, select the logging profile the BIG-IP system uses to configure logging options for various LSN events.
5. Click Finished.