When investigating slow performance at a hub site with PerfStack, which device should you focus on first?

When investigating slow performance at a hub site with PerfStack, which device should you focus on first?

• A. The hub site's edge router
• B. The hub site's core switch
• C. The remote office router
• D. The data center switch

Answer: (A)

When a hub site is experiencing slow performance, start by looking at the hub site’s edge router. This device sits at the boundary of your network, acting as the gateway between the hub and the rest of the network (remote offices and the WAN). If traffic from remote sites is slow or if there’s congestion entering or leaving the hub, the edge router is the most likely point to show the bottleneck through metrics like interface utilization, queueing, CPU, and error counts. Using PerfStack, you can quickly correlate spikes in latency or drops in throughput on the hub’s edge router with other metrics to confirm if contention or processing limits at the boundary are the root cause. If the edge router checks out, you then expand the investigation to internal devices such as the hub’s core switch or remote office routers to pinpoint secondary bottlenecks.

When a hub site is experiencing slow performance, start by looking at the hub site’s edge router. This device sits at the boundary of your network, acting as the gateway between the hub and the rest of the network (remote offices and the WAN). If traffic from remote sites is slow or if there’s congestion entering or leaving the hub, the edge router is the most likely point to show the bottleneck through metrics like interface utilization, queueing, CPU, and error counts. Using PerfStack, you can quickly correlate spikes in latency or drops in throughput on the hub’s edge router with other metrics to confirm if contention or processing limits at the boundary are the root cause. If the edge router checks out, you then expand the investigation to internal devices such as the hub’s core switch or remote office routers to pinpoint secondary bottlenecks.