06-10-2016 03:11 AM - edited 03-01-2019 03:01 PM
Hello friends,
I have some weeks experiencing some troubles when i want to Shutdown a BGP session in my Cisco Catalyst. When i Shutdown the BGP session, the others sessions in my router went down also. I experience high CPU load, but i was reading about that and is because the BGP router process that generate high load in the CPU when add, remove or soft-reconfigure a sessions.
Should be great if somebody had a similar experience and can help me to solve this issue. And also if you need some information to understand the problem, let me know.
Al the best. Thanks
06-10-2016 05:04 AM
Hi
If you configured soft-reconfiguration for all peering and depending on your bgp table it could have an impact on CPU.
For the other issue, when you shutdown a neighbour, all other processes are going down?
Could you please share a quick sketch, some configs and output of logs in order to better understand?
Thanks
06-10-2016 06:46 AM
Hello supportlan,
When i shutdown a neighbor, the other neighbor goes down also. Let me share with you the logs.
05.06.2016 23:41:25 66080: CISCO-CATA: Jun 5 2016 23:41:23: %BGP-5-ADJCHANGE: neighbor xxxx:xxx::xxxx:xxxxx:xxxx Up
05.06.2016 23:40:52 66079: CISCO-CATA: Jun 5 2016 23:40:50: %BGP-3-NOTIFICATION: sent to neighbor xxxx:xxx::xxxx:xxxx:xxx 4/0 (hold time expired) 0 bytes
05.06.2016 23:40:37 66078: CISCO-CATA: Jun 5 2016 23:40:35: %BGP-5-ADJCHANGE: neighbor xx.xx.xxx.xxx Up
05.06.2016 23:39:46 66077: CISCO-CATA: Jun 5 2016 23:39:45: %BGP-3-NOTIFICATION: sent to neighbor xx.xx.xxxx.xxxx 4/0 (hold time expired) 0 bytes
05.06.2016 23:38:34 66076: CISCO-CATA: Jun 5 2016 23:38:33: %SYS-5-CONFIG_I: Configured from console by xxxx on vty0 (10.1.1.253)
05.06.2016 23:37:19 66075: CISCO-CATA: Jun 5 2016 23:37:17: %BGP-3-NOTIFICATION: sent to neighbor yyyy:yyy::yyyy:yyyy:yyyyy 4/0 (hold time expired) 0 bytes
05.06.2016 23:37:19 66074: CISCO-CATA: Jun 5 2016 23:37:17: %BGP-5-ADJCHANGE: neighbor yyyy:yyy::yyyy:yyyy:yyyy Down BGP Notification sent
05.06.2016 23:36:12 66073: CISCO-CATA: Jun 5 2016 23:36:09: %BGP-3-NOTIFICATION: sent to neighbor yy.yy.yyy.yyy 4/0 (hold time expired) 0 bytes
05.06.2016 23:36:12 66072: CISCO-CATA: Jun 5 2016 23:36:09: %BGP-5-ADJCHANGE: neighbor yy.yy.yyyy.yyy Down BGP Notification sent
05.06.2016 23:35:32 66071: CISCO-CATA: Jun 5 2016 23:35:27: %BGP-5-ADJCHANGE: neighbor yy.yy.yyy.yy Up
05.06.2016 23:35:13 66070: CISCO-CATA: Jun 5 2016 23:35:11: %BGP-5-ADJCHANGE: neighbor yyyy:yyy::yyyy:0:1 Up
05.06.2016 23:35:01 66069: CISCO-CATA: Jun 5 2016 23:34:59: %BGP-5-ADJCHANGE: neighbor yy.yy.yyy.yy Up
05.06.2016 23:34:57 66068: CISCO-CATA: Jun 5 2016 23:34:55: %BGP-5-ADJCHANGE: neighbor yy.yy.yyy.yy Up
05.06.2016 23:34:49 66067: CISCO-CATA: Jun 5 2016 23:34:47: %BGP-3-NOTIFICATION: sent to neighbor yyyy:yyy::yyyy:y:y 4/0 (hold time expired) 0 bytes
05.06.2016 23:34:48 66066: CISCO-CATA: Jun 5 2016 23:34:47: %BGP-5-ADJCHANGE: neighbor yyyy:yyy::yyyy:y:y Down BGP Notification sent
05.06.2016 23:34:48 66065: CISCO-CATA: Jun 5 2016 23:34:44: %BGP-3-NOTIFICATION: sent to neighbor yy.yy.yyy.yy 4/0 (hold time expired) 0 bytes
05.06.2016 23:34:48 66064: CISCO-CATA: Jun 5 2016 23:34:44: %BGP-5-ADJCHANGE: neighbor yy.yy.yyy.yy Down BGP Notification sent
05.06.2016 23:34:44 66063: CISCO-CATA: Jun 5 2016 23:34:42: %SEC_LOGIN-5-LOGIN_SUCCESS: Login Success [user: xxx] [Source: 1.1.1.1] [localport: 22] at 23:34:42 MEST Sun Jun 5 2016
05.06.2016 23:34:38 66062: CISCO-CATA: Jun 5 2016 23:34:34: %BGP-3-NOTIFICATION: sent to neighbor yy.yy.yyy.yy 4/0 (hold time expired) 0 bytes
05.06.2016 23:34:38 66061: CISCO-CATA: Jun 5 2016 23:34:34: %BGP-5-ADJCHANGE: neighbor yy.yy.yyy.yy Down BGP Notification sent
05.06.2016 23:34:22 66060: CISCO-CATA: Jun 5 2016 23:34:18: %LDP-5-NBRCHG: LDP Neighbor yyy.yy.yyy.yy:0 (1) is UP
05.06.2016 23:34:21 66059: CISCO-CATA: Jun 5 2016 23:34:13: %BGP-3-NOTIFICATION: sent to neighbor yy.yy.yyy.yy 4/0 (hold time expired) 0 bytes
05.06.2016 23:34:21 66058: CISCO-CATA: Jun 5 2016 23:34:13: %BGP-5-ADJCHANGE: neighbor yy.yy.yyy.yy Down BGP Notification sent
05.06.2016 23:33:57 66057: CISCO-CATA: Jun 5 2016 23:33:51: %LDP-5-NBRCHG: LDP Neighbor yyy.yyy.yyy.yy:0 (1) is DOWN (Discovery Hello Hold Timer expired)
05.06.2016 23:33:24 66056: CISCO-CATA: Jun 5 2016 23:33:17: %BGP-5-ADJCHANGE: neighbor xx.xxx.xxx.xxx Down Admin. shutdown
05.06.2016 23:33:13 66055: CISCO-CATA: Jun 5 2016 23:33:11: %PARSER-5-CFGLOG_LOGGEDCMD: User:xxxx logged command:neighbor xx.xxx.xxx.xxx shutdown
the lines where the neighbor ip address is like xx.xx.xx.xxx is the neighbor that we want to shutdown and the neighbors with yy.yy.yy.yyy ip address are the other neighbors that shutdown without a reason.
Let me know if this information is enough or if i can provide something more useful.
thanks and all the best.
06-10-2016 03:05 PM
Hi
Could you share a quick drawing how there are doing peering all together?
Could you run a debug ip bgp when you are shutting down this xxx peer?
If you want to be more precise, you can do:
- debug ip bgp events
However with a debug ip bgp we will have everything concerning BGP.
When you CPU is spiking, can you do a sh proc cpu sorted in order to view all processes?
Thanks
06-27-2016 01:05 AM
Hello supportlan,
I try the debug ip bgp events, but the output in the console is similar to the another one which i already show you. do you think its ok or should be different??
thanks and all the best.
Do you have an example about how should look?
06-27-2016 08:28 AM
Hi
could you show a drawing of your bgp design and configuration of those 2 neighbors?
Thanks
06-10-2016 07:17 AM
When i shutdown the bgp neighbor start the high cpu load and the others bgp neighbors went down.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide