The usual explanation I have run into for high CPU utilization on Cisco switches is its use of PVST+. This isn't a flaw just something that you need to consider when configuring these switches. The issue is the switch maintains a separate spanning tree instance for each VLAN on each configured trunk port. If you use the command "show spanningtree summary you will notice the total spanning tree instances on the switch. Maintaining soo many is CPU expensive. Use allowed lists on the trunk ports to ensure the trunks aren't required to support instances for all VLANS on the switch but just the required ones for the trunk port itself. Use the command "switchport trunk allowed vlan 1,22" where this port propagates VLAN 1 and 22.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...