![]() ![]() The key thing is this is expected behavior on a router running multiple BGP peers such as this one. Since there are always routes being withdrawn and re-added to the routing table it is a busy process. This means BGP is limited to just one core to do it’s work. Remember earlier when we talked about BGP? In Mikrotik, BGP is not a multi-core aware process. ![]() So, why is this CPU at 100% and what ramifications does this have? Oh My we have 100% CPU! Must replace this router ASAP! Calm down, remember you have 16 cores. It will then bring up a screen that looks like the following. Th next thing to investigate when it comes to CPU is to open up System.resources. I like to think of this as an overall view of the CPUs on this router. ![]() One of the first things people turn on is the overall CPU usage within winbox. Most of the traffic is on VLANs coming from a Cisco switch to the SFPPlus port. The router handles a little over 3 gigs of routed traffic at peak times. There are two transit provider BGP feeds, multiple direct peers, an Internet Exchange peer to dual-route servers. It is currently pulling in 1,764,849 IPv4 routes. This is a 16 core 1.2GHz per core and 2GB RAM tilex based router. I wanted to take a few minutes and go over a real-world example and explain some of the ins and outs when discussing Mikrotik CPU usage. There always is a lot of talk about Mikrotik RouterOS CPU usage. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |