Look for the '-panio' string in the dp-monitor log (this information is logged every 10 minutes) or run the show running resource-monitor command from the CLI to view DP resource usage. When a customer reports a performance issue, generate a tech support file while the issue is occurring. The first step is to isolate where the performance issue is occurring: If issues are being reported, are these reports coinciding with specific peak times of the day, at regular intervals, or at totally random moments?.Are users experiencing high latency, and if so, does latency affect all traffic or just certain applications?.Is some, all, or no traffic through the firewall affected?.Several factors that need to be identified before taking action: Getting an understanding of the impact of the high dataplane CPU is important: high dataplane CPU usage may not present an immediate cause for concern, but being aware of what is causing high CPU and possible consequences will help you respond appropriately. This article shows a couple of ways to verify the actual load of the dataplane and help determine the potential impact on your network. Learn to troubleshoot high dataplane CPU.

These factors and more can cause increases in packet rate, packet buffer utilization, or a huge amount of new connections per second that lead to the dataplane CPU reaching a critical level. A number of factors can cause the dataplane's CPUs to spike or continuously run high: a sudden increase due to the implementation of a new service or resource, or a buildup over time due to added connected networks, segments and hosts.

Views from the 6 zip mps