Manual Chapter :
Common Elements for Logging Topics
Applies To:
Show VersionsBIG-IP LTM
- 15.0.1, 15.0.0, 14.1.3, 14.1.2, 14.1.0
Common Elements for Logging Topics
- On the Main tab, click.The Protocol Security event log displays.
- On the Main tab, click.The Network Firewall event log displays.
- Select an event log item, and clickCreate Rule.TheNew Rulescreen opens. The new rule is populated with source, destination, VLAN, protocol, and port info derived from the log entry.
- On the Main tab, click.The HTTP, FTP, SMTP statistics screen opens.
- On the Main tab, click.The Requests screen opens.
- On the Main tab, click.The System logs screen opens.
- On the Main tab, click.The Remote Logging screen opens.
- On the Main tab, click.The Log Destinations screen opens.
- On the Main tab, click.The Log Publishers screen opens.
- On the Main tab, click.The Log Filters screen opens.
- On the menu bar, clickLocal Traffic.The Local Traffic logs screen opens.
- On the menu bar, clickPacket Filter.The Packet Filter logs screen opens.
- On the menu bar, clickSystem.The System logs screen opens.
- You can either scroll through the log or search for a log entry about a specific event.
- ClickCreate.
- ClickUpdate.
- ClickFinished.
- ClickAdd.
- In theRemote IPfield, type the IP address of the remote server to which the BIG-IP system will send the log messages.
- In theRemote Portfield, retain the default port number or type a different port number.
- Optionally, in theLocal IPfield, type the IP address of the local BIG-IP system that is sending the log messages.
- In theNamefield, type a unique, identifiable name for this destination.
- From theTypelist, selectRemote High-Speed Log.
- From theTypelist, selectRemote High-Speed Log.If you use log servers such as Remote Syslog, Splunk, or ArcSight, which require data be sent to the servers in a specific format, you must create an additional log destination of the required type, and associate it with a log destination of theRemote High-Speed Logtype. With this configuration, the BIG-IP system can send data to the servers in the required format.The BIG-IP system is configured to send an unformatted string of text to the log servers.
- From theTypelist, selectIPFIX.
- From theTypelist, selectRemote High-Speed Log.If you use log servers such as Remote Syslog, Splunk, or IPFIX, which require data be sent to the servers in a specific format, you must create an additional log destination of the required type, and associate it with a log destination of theRemote High-Speed Logtype. This allows the BIG-IP system to send data to the servers in the required format.The BIG-IP system is configured to send an unformatted string of text to the log servers.
- From theTypelist, selectRemote Syslog.
- From theTypelist, select a formatted logging destination, such asIPFIX,Remote Syslog,Splunk, orArcSight.ArcSight formatting is only available for logs coming from Advanced Firewall Manager (AFM), Application Security Manager (ASM), and the Secure Web Gateway component of Access Policy Manager (APM). IPFIX is not available for Secure Web Gateway. Remote Syslog formatting is the only type supported for logs coming from APM. The Splunk format is a predefined format of key value pairs.The BIG-IP system is configured to send a formatted string of text to the log servers.
- From theTypelist, select a formatted logging destination, such asRemote Syslog,Splunk, orArcSight.The Splunk format is a predefined format of key value pairs.The BIG-IP system is configured to send a formatted string of text to the log servers.
- From theTypelist, select a formatted logging destination, such asRemote Syslog,Splunk, orIPFIX.The Splunk format is a predefined format of key value pairs.The BIG-IP system is configured to send a formatted string of text to the log servers.
- From theTypelist, selectSplunk.The Splunk format is a predefined format of key value pairs.
- If you selectedSplunkorIPFIX, then from theForward Tolist, select the destination that points to a pool of high-speed log servers to which you want the BIG-IP system to send log messages.
- If you selectedSplunk, then from theForward Tolist, select the destination that points to a pool of high-speed log servers to which you want the BIG-IP system to send log messages.The Splunk format is a predefined format of key value pairs.
- If you selectedRemote Syslog, then from theSyslog Formatlist select a format for the logs, and then from theHigh-Speed Log Destinationlist, select the destination that points to a pool of remote Syslog servers to which you want the BIG-IP system to send log messages.For logs coming from Access Policy Manager (APM), only the BSD Syslog format is supported.
- From theForward Tolist, selectlocal-syslog.
- From thePool Namelist, select the pool of remote log servers to which you want the BIG-IP system to send log messages.
- From thePool Namelist, select the alert pool that you defined previously.
- From thePool Namelist, select an LTM pool of IPFIX collectors.
- From theProtocollist, select the protocol used by the high-speed logging pool members.
- From theProtocollist, select the TCP protocol.
- From theProtocollist, selectIPFIXorNetflow V9, depending on the type of collectors you have in the pool.
- From theTransport Profilelist, selectTCP,UDP, or any customized profile derived from TCP or UDP.
- TheTemplate Retransmit Intervalis the time between transmissions of IPFIX templates to the pool of collectors. The BIG-IP system only retransmits its templates if theTransport Profileis aUDPprofile.AnIPFIX templatedefines 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.
- TheTemplate Delete Delayis 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.
- TheServer SSL Profileapplies Secure Socket Layer (SSL) or Transport Layer Security (TLS) to TCP connections. You can only choose an SSL profile if theTransport Profileis aTCPprofile. 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.
- In theNamefield, type a unique, identifiable name for this publisher.
- For theDestinationssetting, select a destination from theAvailablelist, and click<<to move the destination to theSelectedlist.If you are using a formatted destination, select the destination that matches your log servers, such as Remote Syslog, Splunk, or ArcSight.
- For theDestinationssetting, select the log destination you created previously from theAvailablelist, and click<<to move the destination to theSelectedlist.
- For theDestinationssetting, select a destination from theAvailablelist, and click<<to move the destination to theSelectedlist.If you are using a formatted destination, select the destination that matches your log servers, such as Remote Syslog, Splunk, or IPFIX.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 thelogpublisher.atomicdb variable tofalse.
- For theDestinationssetting, select a destination from theAvailablelist, and click<<to move the destination to theSelectedlist.If you are using a formatted destination, select the destination that matches your log servers, such as Remote Syslog, Splunk, or IPFIX.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 thelogpublisher.atomicdb key tofalse. If all the remote high-speed log (HSL) destinations are down (unavailable), setting thelogpublisher.atomicdb key tofalsewill not work to allow the logs to be written to local-syslog. Thelogpublisher.atomicdb key has no effect on local-syslog.
- For theDestinationssetting, select the previously created destination from theAvailablelist (which formats the logs in the Splunk format and forwards the logs to the local Syslog database) and move the destination to theSelectedlist.
- Use theLog Destinationssetting to select an existing IPFIX destination (perhaps along with other destinations for your logs): click any destination name in theAvailablelist, and click<<to move it to theSelectedlist.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 thelogpublisher.atomicdb variable tofalse.
- Use theLog Destinationssetting to select an existing IPFIX destination (perhaps along with other destinations for your logs): click any destination name in theAvailablelist, and click<<to move it to theSelectedlist.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 thelogpublisher.atomicdb key tofalse. If all the remote high-speed log (HSL) destinations are down (unavailable), setting thelogpublisher.atomicdb key tofalsewill not work to allow the logs to be written to local-syslog. Thelogpublisher.atomicdb key has no effect on local-syslog.
- For theDestinationssetting, select a destination from theAvailablelist, and move the destination to theSelectedlist.If you are using a formatted destination, select the destination that matches your log servers, such as Remote Syslog, Splunk, or IPFIX.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 thelogpublisher.atomicdb key tofalse. If all the remote high-speed log (HSL) destinations are down (unavailable), setting thelogpublisher.atomicdb key tofalsewill not work to allow the logs to be written to local-syslog. Thelogpublisher.atomicdb key has no effect on local-syslog.
- In theNamefield, type a unique, identifiable name for this filter.
- From theSeveritylist, select the level of alerts that you want the system to use for this filter.The severity level that you select includes all of the severity levels that display above your selection in the list. For example, if you selectEmergency, the system publishes only emergency messages to the log. If you selectCritical, the system publishes critical, alert, and emergency-level messages in the log.
- From theSeveritylist, selectDebug.
- From theSourcelist, select the system processes from which messages will be sent to the log.
- From theSourcelist, selectAll.
- In theMessage IDfield, type the first eight hex-digits of the specific message ID that you want the system to include in the log. Use this field when you want a log to contain only each instance of one specific log message.BIG-IP system log messages contain message ID strings in the format:xxxxxxxx:x:. For example, in this log message:Oct 31 11:06:27 olgavmmgmt notice mcpd[5641]: 01070410:5: Removed subscription with subscriber id lind, the message ID string is:01070410:5:. You enter only the first eight hex-digits:01070410.
- From theLog Publisherlist, select the publisher that includes the destinations to which you want to send log messages.
- From theLog Publisherlist, selectNone.
- Select the check box next to the name of the log filter that you want to delete. ClickDelete, and then clickDeleteagain.
- To search for specific events, clickCustom Search. Drag the event data that you want to search for from the Event Log table into the Custom Search table, and then clickSearch.
- To search for enforced policy events, in the search field, typeEnforced, then clickSearch.
- To narrow your search for enforced events, clickCustom Search. Drag theEnforcedtext from thePolicy Typecolumn to the custom search table. Narrow your search further by dragging other items from the log display, for example, from theaction,policy, orrulecolumns. the event data that you want to search for from the Event Log table into the Custom Search table, and then clickSearch.
- To search for staged policy events, in the search field, typeStaged, then clickSearch.
- To narrow your search for staged policy events, clickCustom Search. Drag theStagedtext from thePolicy Typecolumn to the custom search table. Narrow your search further by dragging other items from the log display. For example, from theaction,policy, orrulecolumns, you can drag event data that you want to search for from the Event Log table into the Custom Search table, and then clickSearch.