Note: This command will save the output toВ the mtrace1В file in the /var/log directory.

Run the mpidump utility by typingВ the following command:.

Note: The output from the mpidump utility may not be intuitively understandable, but is frequently requested by support engineers when you open a case. To use the mpidumputility, perform the following procedure: It is especially useful in SSO and mixed module configuration debugging. You can use the mpidump command toВ view product modules activity. The logs are locatedВ in the /var/log/pktfilter file.

Change the Log drop-down menu to Packet.

Navigate to the Access Policy: Web Applications: Web Applications List: Resource Items properties page.

To do so,В perform the following procedure: You can inspect each packet that is sent using the Web Application resource. The following three logs files may be most relevant for troubleshooting purposes: Note: For more information, refer to SOL4714: Performing a packet trace and providing the results to F5 Networks Technical Support. The trace files can be copied off the BIG-IP device with a utility,В suchВ as WinSCP.

If you know the IP addresses of the backend servers and/or the self IPs of the VLANs, you can further limit the capture using the following command syntax:.

This command will record all traffic on all interfaces and write it to the trace1 file.

Connect to the BIG-IP deviceВ using SSH.

To do so, performВ the following procedure: You can use the command line to take a network trace. Increased logging levels should be reserved for testing and troubleshooting purposes only, to avoid increasing the load on the device. Important: Setting the log level to Information or debug will record a lot of data.В F5 recommends that youВ avoid setting the log level that high on a production system. The logging level for the Access Policy, SSO, and Web Applications can be increased on the System: Logs: Options page. Note: For more information, refer to the Configuration Guide for BIG-IP Access Policy Manager. In addition, the release notes for your version will have information regarding issues that are fixed in that release, outstanding issues, and new features. You can access online help from the Configuration utility.

Note: A separate DevCentral login is required to access this content you will be redirected to authenticate or register (if necessary). You should not need to use iRulesВ for general troubleshooting however, in specialized cases you may be using them.В For information about iRules, refer to the DevCentralsite.

In addition, you can create your own customer session variables in the Access Policy. If you switch the log levels to Information for each individual session variable, you can see examples of internal session variables used in the /var/log/apm file. SOL11253: Session variable logging within an access policy SOL11125: Performing a web applications trace You can use many different tools and resources to troubleshoot issues for BIG-IP APM and Edge Gateway.В The following list provides an overviewВ of the most commonly used tools and resources. SOL13595: Frequently used tools for troubleshooting BIG-IP APM and Edge Gateway issues (11.x).For information about other versions, refer to the following article:

This article applies to BIG-IP APM version 10.x.

F5 big ip edge client command line