Доброго времени суток, уважаемые.
Прошу вашей помощи.
распишу проблему максимально конкретно.Ситуация.
Имеется cisco 3661.
c3661#sh ver
Cisco Internetwork Operating System Software
IOS (tm) 3600 Software (C3660-IS-M), Version 12.2(13)T, RELEASE SOFTWARE (fc1)
TAC Support: http://www.cisco.com/tac
Copyright (c) 1986-2002 by cisco Systems, Inc.
Compiled Sat 16-Nov-02 01:48 by ccai
Image text-base: 0x60008940, data-base: 0x61A60000
ROM: System Bootstrap, Version 12.0(6r)T, RELEASE SOFTWARE (fc1)
c3661 uptime is 6 days, 6 hours, 3 minutes
System returned to ROM by power-on
System restarted at 14:46:19 MSK Fri Nov 3 2006
System image file is "flash:c3660-is-mz.122-13.T.bin"
cisco 3660 (R527x) processor (revision 1.0) with 223232K/38912K bytes of memory.
Processor board ID JAC0533A2SK
R527x CPU at 225Mhz, Implementation 40, Rev 10.0, 2048KB L2 Cache
Bridging software.
X.25 software, Version 3.0.0.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
3660 Chassis type: ENTERPRISE
3 FastEthernet/IEEE 802.3 interface(s)
DRAM configuration is 64 bits wide with parity disabled.
125K bytes of non-volatile configuration memory.
24576K bytes of processor board System flash (Read/Write)
Configuration register is 0x3922
На ней поднят бгп.
router bgp 41784
no synchronization
bgp router-id 91.102.111.254
bgp log-neighbor-changes
bgp bestpath dampening
bgp dampening
network 91.102.104.0 mask 255.255.248.0
neighbor 83.239.128.192 remote-as 33934
neighbor 83.239.128.192 ebgp-multihop 3
neighbor 83.239.128.192 update-source FastEthernet1/0
neighbor 83.239.128.192 filter-list 7 in
neighbor 83.239.128.192 filter-list 9 out
no auto-summary
ip as-path access-list 6 permit ^31585$
ip as-path access-list 7 permit ^33934$
ip as-path access-list 9 permit ^41784$
Пиринг поднимается без проблем. Анонсы рассылаю и получаю. Все ок.
Но происходит следующее.
Получаем анонсы...
c3661#sh ip bgp
BGP table version is 281, local router ID is 91.102.111.254
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
r> 0.0.0.0 83.239.128.192 0 33934 i
*> 62.183.116.0/24 83.239.128.192 20 0 33934 i
*> 83.239.128.0/18 83.239.128.192 20 0 33934 i
*> 85.172.112.0/20 83.239.128.192 20 0 33934 i
*> 85.172.168.0/22 83.239.128.192 20 0 33934 i
*> 85.172.172.0/24 83.239.128.192 20 0 33934 i
Маршрутизация добавляется в таблицу и видна по sh ip route.
Проходит ровно минута и ситуация меняется
c3661#sh ip bgp
BGP table version is 287, local router ID is 91.102.111.254
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
* 0.0.0.0 83.239.128.192 0 33934 i
* 62.183.116.0/24 83.239.128.192 20 0 33934 i
* 83.239.128.0/18 83.239.128.192 20 0 33934 i
* 85.172.112.0/20 83.239.128.192 20 0 33934 i
* 85.172.168.0/22 83.239.128.192 20 0 33934 i
* 85.172.172.0/24 83.239.128.192 20 0 33934 i
И вот при таком раскладе по sh ip route не видно маршрутов, кторые присутствуют в sh ip bgp. Причем из таблицы марщрутизации удаляются ВСЕ бгпшные маршруты.
Проходит еще минута и все появляется. Еще минута и исчезает... и так до посинения.
Что кажет debug bgp updates после clear ip bgp
### Собственно кладем и поднимаем пир. Получаем анонсы...
Nov 9 21:34:22.747 MSK: BGP: 83.239.128.192 went from Established to Idle
Nov 9 21:34:22.747 MSK: %BGP-5-ADJCHANGE: neighbor 83.239.128.192 Down User reset
Nov 9 21:34:22.747 MSK: BGP: 83.239.128.192 closing
Nov 9 21:34:42.752 MSK: BGP: 83.239.128.192 went from Idle to Active
Nov 9 21:34:42.752 MSK: BGP: 83.239.128.192 open active, delay 23207ms
Nov 9 21:35:05.105 MSK: BGP: 83.239.128.192 passive open
Nov 9 21:35:05.105 MSK: BGP: 83.239.128.192 went from Active to Idle
Nov 9 21:35:05.105 MSK: BGP: 83.239.128.192 went from Idle to Connect
Nov 9 21:35:05.109 MSK: BGP: 83.239.128.192 rcv message type 1, length (excl. header) 26
Nov 9 21:35:05.109 MSK: BGP: 83.239.128.192 rcv OPEN, version 4
Nov 9 21:35:05.109 MSK: BGP: 83.239.128.192 went from Connect to OpenSent
Nov 9 21:35:05.109 MSK: BGP: 83.239.128.192 sending OPEN, version 4, my as: 41784
Nov 9 21:35:05.109 MSK: BGP: 83.239.128.192 rcv OPEN w/ OPTION parameter len: 16
Nov 9 21:35:05.109 MSK: BGP: 83.239.128.192 rcvd OPEN w/ optional parameter type 2 (Capability) len 6
Nov 9 21:35:05.109 MSK: BGP: 83.239.128.192 OPEN has CAPABILITY code: 1, length 4
Nov 9 21:35:05.109 MSK: BGP: 83.239.128.192 OPEN has MP_EXT CAP for afi/safi: 1/1
Nov 9 21:35:05.109 MSK: BGP: 83.239.128.192 rcvd OPEN w/ optional parameter type 2 (Capability) len 2
Nov 9 21:35:05.109 MSK: BGP: 83.239.128.192 OPEN has CAPABILITY code: 128, length 0
Nov 9 21:35:05.109 MSK: BGP: 83.239.128.192 OPEN has ROUTE-REFRESH capability(old) for all address-families
Nov 9 21:35:05.109 MSK: BGP: 83.239.128.192 rcvd OPEN w/ optional parameter type 2 (Capability) len 2
Nov 9 21:35:05.109 MSK: BGP: 83.239.128.192 OPEN has CAPABILITY code: 2, length 0
Nov 9 21:35:05.109 MSK: BGP: 83.239.128.192 OPEN has ROUTE-REFRESH capability(new) for all address-families
Nov 9 21:35:05.109 MSK: BGP: 83.239.128.192 went from OpenSent to OpenConfirm
Nov 9 21:35:05.109 MSK: BGP: 83.239.128.192 send message type 1, length (incl. header) 45
Nov 9 21:35:05.113 MSK: BGP: 83.239.128.192 went from OpenConfirm to Established
Nov 9 21:35:05.113 MSK: %BGP-5-ADJCHANGE: neighbor 83.239.128.192 Up
Nov 9 21:35:05.117 MSK: BGP(0): 83.239.128.192 rcvd UPDATE w/ attr: nexthop 83.239.128.192, origin i, path 33934
Nov 9 21:35:05.117 MSK: BGP(0): 83.239.128.192 rcvd 0.0.0.0/0
Nov 9 21:35:08.633 MSK: BGP(0): 83.239.128.192 rcvd UPDATE w/ attr: nexthop 83.239.128.192, origin i, metric 20, path 33934
Nov 9 21:35:08.633 MSK: BGP(0): 83.239.128.192 rcvd 62.183.116.0/24
Nov 9 21:35:08.633 MSK: BGP(0): 83.239.128.192 rcvd 83.239.128.0/18
Nov 9 21:35:08.633 MSK: BGP(0): 83.239.128.192 rcvd 85.172.112.0/20
Nov 9 21:35:08.633 MSK: BGP(0): 83.239.128.192 rcvd 85.172.168.0/22
Nov 9 21:35:08.633 MSK: BGP(0): 83.239.128.192 rcvd 85.172.172.0/24
Nov 9 21:35:08.633 MSK: BGP(0): 83.239.128.192 rcvd UPDATE w/ attr: nexthop 83.239.128.192, origin i, path 33934 25510
Nov 9 21:35:08.633 MSK: BGP(0): 83.239.128.192 rcvd 195.160.244.0/22 -- DENIED due to: filter-list;
Nov 9 21:35:08.633 MSK: BGP(0): 83.239.128.192 rcvd 195.245.211.0/24 -- DENIED due to: filter-list;
Nov 9 21:35:08.633 MSK: BGP(0): 83.239.128.192 rcvd UPDATE w/ attr: nexthop 83.239.128.192, origin i, path 33934 34287
Nov 9 21:35:08.633 MSK: BGP(0): 83.239.128.192 rcvd 80.69.144.0/20 -- DENIED due to: filter-list;
Nov 9 21:35:08.633 MSK: BGP(0): 83.239.128.192 rcvd UPDATE w/ attr: nexthop 83.239.128.192, origin i, path 33934 34804
Nov 9 21:35:08.633 MSK: BGP(0): 83.239.128.192 rcvd 85.159.224.0/21 -- DENIED due to: filter-list;
### Тут, насколько я понимяю, создается маршрутизация
Nov 9 21:35:55.735 MSK: BGP(0): Revise route installing 1 of 1 route for 0.0.0.0/0 -> 83.239.128.192 to main IP table
Nov 9 21:35:55.735 MSK: BGP(0): Revise route installing 1 of 1 route for 62.183.116.0/24 -> 83.239.128.192 to main IP table
Nov 9 21:35:55.735 MSK: BGP(0): Revise route installing 1 of 1 route for 83.239.128.0/18 -> 83.239.128.192 to main IP table
Nov 9 21:35:55.735 MSK: BGP(0): Revise route installing 1 of 1 route for 85.172.112.0/20 -> 83.239.128.192 to main IP table
Nov 9 21:35:55.735 MSK: BGP(0): Revise route installing 1 of 1 route for 85.172.168.0/22 -> 83.239.128.192 to main IP table
Nov 9 21:35:55.735 MSK: BGP(0): Revise route installing 1 of 1 route for 85.172.172.0/24 -> 83.239.128.192 to main IP table
Nov 9 21:35:55.735 MSK: BGP(0): Revise route installing 1 of 1 route for 0.0.0.0/0 -> 83.239.128.192 to main IP table
Nov 9 21:35:55.735 MSK: BGP(0): 83.239.128.192 computing updates, afi 0, neighbor version 0, table version 8, starting at 0.0.0.0
Nov 9 21:35:55.735 MSK: BGP(0): 83.239.128.192 update run completed, afi 0, ran for 0ms, neighbor version 0, start version 8, throttled to 8
Nov 9 21:35:55.735 MSK: BGP: 83.239.128.192 initial update completed
### И... через минутут приходит вот что
Nov 9 21:36:52.965 MSK: BGP(0): no valid path for 0.0.0.0/0
Nov 9 21:36:52.965 MSK: BGP(0): no valid path for 62.183.116.0/24
Nov 9 21:36:52.965 MSK: BGP(0): no valid path for 83.239.128.0/18
Nov 9 21:36:52.965 MSK: BGP(0): no valid path for 85.172.112.0/20
Nov 9 21:36:52.965 MSK: BGP(0): no valid path for 85.172.168.0/22
Nov 9 21:36:52.969 MSK: BGP(0): no valid path for 85.172.172.0/24
Nov 9 21:36:52.969 MSK: BGP: Import walker start version 0, end version 1
Nov 9 21:36:52.969 MSK: BGP: ... start import cfg version = 0
Nov 9 21:36:53.349 MSK: BGP(0): nettable_walker 0.0.0.0/0 no best path
Nov 9 21:36:53.349 MSK: BGP(0): nettable_walker 62.183.116.0/24 no best path
Nov 9 21:36:53.349 MSK: BGP(0): nettable_walker 83.239.128.0/18 no best path
Nov 9 21:36:53.349 MSK: BGP(0): nettable_walker 85.172.112.0/20 no best path
Nov 9 21:36:53.349 MSK: BGP(0): nettable_walker 85.172.168.0/22 no best path
Nov 9 21:36:53.349 MSK: BGP(0): nettable_walker 85.172.172.0/24 no best path
Nov 9 21:36:53.349 MSK: BGP(0): 83.239.128.192 computing updates, afi 0, neighbor version 8, table version 14, starting at 0.0.0.0
Nov 9 21:36:53.349 MSK: BGP(0): 83.239.128.192 update run completed, afi 0, ran for 0ms, neighbor version 8, start version 14, throttled to 14
### Маршрутизация прибивается...
### Через минуту вновь приходит update и все повторяется сначала. Инсталим в таблицу, убиваем, инсталим, убиваем...
Вот такая штука. Я в отчаянии. Может как всегда мелочь пропустил какую...
Помогите пожалуйста советом. Дело это очень горит, как всегда впрочем.
Заранее благодарен.