Unable to Perform Debug Flow

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

Unable to Perform Debug Flow

Not applicable

Hello, have a PAN-5050 running 4.1.13, where I am trying to debug flow on.  Followed the steps necessary to turn on flow debugging but I am not seeing anything log to either of the dataplane pan_packet logs files. I've confirmed the settings are in place on both data planes but nothing is logged.  Anyone know of any issues with flow debugging on 4.1.13? 

debug dataplane packet-diag set filter on

debug dataplane packet-diag set filter match <match_criteria>

debug dataplane packet-diag set log feature flow basic

debug dataplane packet-diag set log on

Thanks!

1 accepted solution

Accepted Solutions

L3 Networker

KayvanRomaezi,

There are no reported issues with flow basic debugging being broken in 4.1.13.

If you are not capturing anything in your logs, try the following stesp:

1. Clear all debugging settings

    > debug dataplane packet-diag clear all

2. Set your filter as needed first

    > debug dataplane packet-diag set filter match <match_criteria>

3. Set the filter on

    > debug dataplane packet-diag set filter on

4. It's always helpful to turn off session offloading if your system's current condition can handle it. Check the packet rate on the device and turn session offloading on/off with the following commands:

    > show session info

    > set session offload yes | no

5. Aggregate all logs to a single file prior to running the flow basic

    > debug dataplane packet-diag set log log-option aggregate-to-single-file yes

6. Set flow basic logging on

    > debug dataplane packet-diag set log feature flow basic

    > debug dataplane packet-diag seg log on

As always, use the flow basic debugging tool sparingly as this is very CPU intensive.

Also, remember to turn session offloading back on after your troubleshooting session.

Hope this helps.

Regards,

tasonibare

View solution in original post

1 REPLY 1

L3 Networker

KayvanRomaezi,

There are no reported issues with flow basic debugging being broken in 4.1.13.

If you are not capturing anything in your logs, try the following stesp:

1. Clear all debugging settings

    > debug dataplane packet-diag clear all

2. Set your filter as needed first

    > debug dataplane packet-diag set filter match <match_criteria>

3. Set the filter on

    > debug dataplane packet-diag set filter on

4. It's always helpful to turn off session offloading if your system's current condition can handle it. Check the packet rate on the device and turn session offloading on/off with the following commands:

    > show session info

    > set session offload yes | no

5. Aggregate all logs to a single file prior to running the flow basic

    > debug dataplane packet-diag set log log-option aggregate-to-single-file yes

6. Set flow basic logging on

    > debug dataplane packet-diag set log feature flow basic

    > debug dataplane packet-diag seg log on

As always, use the flow basic debugging tool sparingly as this is very CPU intensive.

Also, remember to turn session offloading back on after your troubleshooting session.

Hope this helps.

Regards,

tasonibare

  • 1 accepted solution
  • 2599 Views
  • 1 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!