отмена
Отображаются результаты для 
Вместо этого искать 
Вы имели в виду: 
Объявления
Добро пожаловать в Сообщество Технической поддержки Cisco. Мы рады получить обратную связь .

Разрыв BGP (Hold timer expired) на 7600

Здравствуйте, столкнулся с проблемой, периодическим обрывом bgp сессий, причем это никак не зависит от нагрузки, и других подобных факторов. Это происходит только с eBGP соседями. Может продолжаться каждые 5-7 минут на протяжение часа, может разово пару раз в день. Может кто-то сможет подсказать куда смотреть, потому что у меня уже варианты кончились. Заранее спасибо.

 

Oct 30 10:33:14: BGP: X.X.X.100 active went from Idle to Active
Oct 30 10:33:14: BGP: X.X.X.100 open active, local address X.X.X.196
Oct 30 10:33:14: BGP: ses global X.X.X.100 (0x1EF954E8:0) act Adding topology IPv4 Unicast:base
Oct 30 10:33:14: BGP: ses global X.X.X.100 (0x1EF954E8:0) act Send OPEN
Oct 30 10:33:14: BGP: X.X.X.100 active went from Active to OpenSent
Oct 30 10:33:14: BGP: X.X.X.100 active sending OPEN, version 4, my as: xxx19, holdtime 180 seconds, ID D9461F87
Oct 30 10:33:14: BGP: ses global X.X.X.100 (0x1EF954E8:0) act Remote close.
Oct 30 10:33:14: BGP: nbr_topo global X.X.X.100 IPv4 Unicast:base (0x1EF954E8:0) Not scheduling for GR processing [Peer did not advertise GR cap]
Oct 30 10:33:14: BGP: ses global X.X.X.100 (0x1EF954E8:0) act Reset (Peer closed the session).
Oct 30 10:33:14: BGP: nbr_topo global X.X.X.100 IPv4 Unicast:base (0x1EF954E8:0) NSF delete stale NSF not active
Oct 30 10:33:14: BGP: nbr_topo global X.X.X.100 IPv4 Unicast:base (0x1EF954E8:0) NSF no stale paths state is NSF not active
Oct 30 10:33:14: BGP: nbr_topo global X.X.X.100 IPv4 Unicast:base (0x1EF954E8:0) Resetting ALL counters.
Oct 30 10:33:14: BGP: X.X.X.100 active closing
Oct 30 10:33:14: BGP: nbr_topo global X.X.X.100 IPv4 Unicast:base (0x1EF954E8:0) Resetting ALL counters.
Oct 30 10:33:14: BGP: X.X.X.100 active went from OpenSent to Idle
Oct 30 10:33:14: %BGP_SESSION-5-ADJCHANGE: neighbor X.X.X.100 IPv4 Unicast topology base removed from session  Peer closed the session
Oct 30 10:33:14: BGP: ses global X.X.X.100 (0x1EF954E8:0) act Removed topology IPv4 Unicast:base
Oct 30 10:33:14: BGP: ses global X.X.X.100 (0x1EF954E8:0) act Removed last topology
Oct 30 10:33:14: BGP: nbr global X.X.X.100 Open active delayed 8192ms (35000ms max, 60% jitter)
Oct 30 10:33:14: BGP: nbr global X.X.X.100 Active open failed - open timer running
Oct 30 10:33:22: BGP: X.X.X.100 active went from Idle to Active
Oct 30 10:33:22: BGP: X.X.X.100 open active, local address X.X.X.196
Oct 30 10:33:22: BGP: ses global X.X.X.100 (0x2631CEEC:0) act Adding topology IPv4 Unicast:base
Oct 30 10:33:22: BGP: ses global X.X.X.100 (0x2631CEEC:0) act Send OPEN
Oct 30 10:33:22: BGP: X.X.X.100 active went from Active to OpenSent
Oct 30 10:33:22: BGP: X.X.X.100 active sending OPEN, version 4, my as: xxx19, holdtime 180 seconds, ID D9461F87
Oct 30 10:33:22: BGP: ses global X.X.X.100 (0x2631CEEC:0) act Remote close.
Oct 30 10:33:22: BGP: nbr_topo global X.X.X.100 IPv4 Unicast:base (0x2631CEEC:0) Not scheduling for GR processing [Peer did not advertise GR cap]
Oct 30 10:33:22: BGP: ses global X.X.X.100 (0x2631CEEC:0) act Reset (Peer closed the session).
Oct 30 10:33:22: BGP: nbr_topo global X.X.X.100 IPv4 Unicast:base (0x2631CEEC:0) NSF delete stale NSF not active
Oct 30 10:33:22: BGP: nbr_topo global X.X.X.100 IPv4 Unicast:base (0x2631CEEC:0) NSF no stale paths state is NSF not active
Oct 30 10:33:22: BGP: nbr_topo global X.X.X.100 IPv4 Unicast:base (0x2631CEEC:0) Resetting ALL counters.
Oct 30 10:33:22: BGP: X.X.X.100 active closing
Oct 30 10:33:22: BGP: nbr_topo global X.X.X.100 IPv4 Unicast:base (0x2631CEEC:0) Resetting ALL counters.
Oct 30 10:33:22: BGP: X.X.X.100 active went from OpenSent to Idle
Oct 30 10:33:22: %BGP_SESSION-5-ADJCHANGE: neighbor X.X.X.100 IPv4 Unicast topology base removed from session  Peer closed the session
Oct 30 10:33:22: BGP: ses global X.X.X.100 (0x2631CEEC:0) act Removed topology IPv4 Unicast:base
Oct 30 10:33:22: BGP: ses global X.X.X.100 (0x2631CEEC:0) act Removed last topology
Oct 30 10:33:22: BGP: nbr global X.X.X.100 Open active delayed 13312ms (35000ms max, 60% jitter)
Oct 30 10:33:22: BGP: nbr global X.X.X.100 Active open failed - open timer running
Oct 30 10:33:36: BGP: X.X.X.100 active went from Idle to Active
Oct 30 10:33:36: BGP: X.X.X.100 open active, local address X.X.X.196
Oct 30 10:33:36: BGP: ses global X.X.X.100 (0x1EF954E8:0) act Adding topology IPv4 Unicast:base
Oct 30 10:33:36: BGP: ses global X.X.X.100 (0x1EF954E8:0) act Send OPEN
Oct 30 10:33:36: BGP: X.X.X.100 active went from Active to OpenSent
Oct 30 10:33:36: BGP: X.X.X.100 active sending OPEN, version 4, my as: xxx19, holdtime 180 seconds, ID D9461F87
Oct 30 10:33:36: BGP: X.X.X.100 active rcv message type 1, length (excl. header) 30
Oct 30 10:33:36: BGP: ses global X.X.X.100 (0x1EF954E8:0) act Receive OPEN
Oct 30 10:33:36: BGP: X.X.X.100 active rcv OPEN, version 4, holdtime 30 seconds
Oct 30 10:33:36: BGP: X.X.X.100 active rcv OPEN w/ OPTION parameter len: 20
Oct 30 10:33:36: BGP: X.X.X.100 active rcvd OPEN w/ optional parameter type 2 (Capability) len 18
Oct 30 10:33:36: BGP: X.X.X.100 active OPEN has CAPABILITY code: 1, length 4
Oct 30 10:33:36: BGP: X.X.X.100 active OPEN has MP_EXT CAP for afi/safi: 1/1
Oct 30 10:33:36: BGP: X.X.X.100 active OPEN has CAPABILITY code: 2, length 0
Oct 30 10:33:36: BGP: X.X.X.100 active OPEN has ROUTE-REFRESH capability(new) for all address-families
Oct 30 10:33:36: BGP: X.X.X.100 active OPEN has CAPABILITY code: 64, length 2
Oct 30 10:33:36: BGP: ses global X.X.X.100 (0x1EF954E8:0) act NSF OPEN has GR cap
Oct 30 10:33:36: BGP: ses global X.X.X.100 (0x1EF954E8:0) act NSF Peer has not restarted. Restart Time: 0
Oct 30 10:33:36: BGP: X.X.X.100 active OPEN has CAPABILITY code: 65, length 4
Oct 30 10:33:36: BGP: X.X.X.100 active OPEN has 4-byte ASN CAP for: xxx1
Oct 30 10:33:36: BGP: nbr global X.X.X.100 neighbor does not have IPv4 MDT topology activated
Oct 30 10:33:36: BGP: X.X.X.100 active rcvd OPEN w/ remote AS xxx1, 4-byte remote AS xxx1
Oct 30 10:33:36: BGP: X.X.X.100 active went from OpenSent to OpenConfirm
Oct 30 10:33:36: BGP: X.X.X.100 active went from OpenConfirm to Established
Oct 30 10:33:36: BGP: ses global X.X.X.100 (0x1EF954E8:1) act Assigned ID
Oct 30 10:33:36: BGP: ses global X.X.X.100 (0x1EF954E8:1) Up
Oct 30 10:33:36: %BGP-5-ADJCHANGE: neighbor X.X.X.100 Up

Партнер мне сообщает, что я ему присылаю Received: Hold timer expired, после чего срабатывает дампенинг на 60/120 сек в течении которого мы не можем установить сессию, у он отправляет Reject.

 

CPU в пиках загружен на 25%


Cisco CISCO7604 (M8500) processor (revision 2.0) with 1900544K/131072K bytes of memory.
Processor board ID FOX1240GV33
 BASEBOARD: RSP720-10GE
 CPU: MPC8548_E, Version: 2.0, (0x80390020)
 CORE: E500, Version: 2.0, (0x80210020)
 CPU:1200MHz, CCB:400MHz, DDR:200MHz,
 L1:    D-cache 32 kB enabled
           I-cache 32 kB enabled

 

 

 

Теги (1)
1 ОТВЕТ

Oct 30 10:33:36: BGP: X.X.X

Oct 30 10:33:36: BGP: X.X.X.100 active sending OPEN, version 4, my as: xxx19, holdtime 180 seconds, ID D9461F87

Oct 30 10:33:36: BGP: X.X.X.100 active rcv OPEN, version 4, holdtime 30 seconds

 

Это значит, что у вас hold time 180 секунд, а у той стороны - 30 секунд. А так как вычисление hello интервала у всех свое и не особо описано в стандарте... В общем, поставьте со своей стороны таймеры hello/hold 10/30. Это наверняка устранит проблему.

179
Просмотры
0
Полезный материал
1
Ответы