>[оверквотинг удален]
>>
>>Т.е. сумма всего 5-го столбца (5Sec) должна быть равна 32%, шестого (1Min)
>>- 38%, седьмого - 39% ? Считаю все на калькуляторе -
>>не сходится (получается порядка 12%).
>>Периодически загрузка плавает в районе 80-90% и никак не могу выяснить что
>>грузит свич. Постоянно примерно одинаковые результаты выдает.
>
>покажите полностью вывод команды - sh proc cpu
>
>грузит вероятнее всего () - arp,broadcast storm,pbr ... не обращайте внимание, что проценты маленькие.
ARP Input
High CPU utilization in the Address Resolution Protocol (ARP) Input process occurs if the router has to originate an excessive number of ARP requests. The router uses ARP for all hosts, not just those on the local subnet, and ARP requests are sent out as broadcasts, which causes more CPU utilization on every host in the network. ARP requests for the same IP address are rate-limited to one request every two seconds, so an excessive number of ARP requests would have to originate for different IP addresses. This can happen if an IP route has been configured pointing to a broadcast interface. A most obvious example is a default route such as:
ip route 0.0.0.0 0.0.0.0 Fastethernet0/0In this case, the router generates an ARP request for each IP address that is not reachable through more specific routes, which practically means that the router generates an ARP request for almost every address on the Internet. For more information about configuring next hop address for static routing, see Specifying a Next Hop IP Address for Static Routes.
Alternatively, an excessive amount of ARP requests can be caused by a malicious traffic stream which scans through locally attached subnets. An indication of such a stream would be the presence of a very high number of incomplete ARP entries in the ARP table. Since incoming IP packets that would trigger ARP requests would have to be processed, troubleshooting this problem would essentially be the same as troubleshooting high CPU utilization in the IP Input process.
