Problem z BGP na Ruterze Cisco ASR1001 Temat rozwiązany

Problemy związane z routingiem

Moderatorzy: mikrobi, aron, garfield, gangrena, Seba

Wiadomość
Autor
Awatar użytkownika
nell
wannabe
wannabe
Posty: 190
Rejestracja: 10 maja 2009, 12:17

Problem z BGP na Ruterze Cisco ASR1001

#1

#1 Post autor: nell » 25 kwie 2019, 16:05

Mam taki problem ze skonfigurowaniem BGP na ASR1001. Router zaczyna pobierać tablice, po czym przerywa i po chwili zrywa sesję i ponownie zaczyna i tak w kółko. W ip bgp summary, póki trwa sesja widać czasem 20 tys prefixow czasem 190 tys itd. Router ma 8GB RAM, więc z tego co czytałem wspiera 1mln prefixów. W logach nie mogę się dopatrzeć przyczyny....

konfiguracja BGP

Kod: Zaznacz cały

router bgp 108802
bgp router-id 138.115.177.254
bgp log-neighbor-changes
neighbor 31.21.183.129 remote-as 9012
show ip bgp summary

Kod: Zaznacz cały

Router#show ip bgp summary
BGP router identifier 138.115.177.254, local AS number 108802
BGP table version is 72712, main routing table version 72712
28107 network entries using 6970536 bytes of memory
28107 path entries using 3147984 bytes of memory
3437/3437 BGP path/bestpath attribute entries using 769888 bytes of memory
2927 BGP AS-PATH entries using 130834 bytes of memory
867 BGP community entries using 82116 bytes of memory
2 BGP extended community entries using 100 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP using 11101458 total bytes of memory
BGP activity 29707/1600 prefixes, 50409/22302 paths, scan interval 60 secs

Neighbor        V           AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down  State/PfxRcd
31.21.183.129   4        9012     3630       7    72712    0    0 00:01:23    28107
show ver

Kod: Zaznacz cały

Router(config)#do sh ver
Cisco IOS Software, IOS-XE Software (X86_64_LINUX_IOSD-UNIVERSAL-M), Version 15.2(4)S0b, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2012 by Cisco Systems, Inc.
Compiled Thu 23-Aug-12 23:42 by mcpre

IOS XE Version: 03.07.00b.S

Cisco IOS-XE software, Copyright (c) 2005-2012 by cisco Systems, Inc.
All rights reserved.  Certain components of Cisco IOS-XE software are
licensed under the GNU General Public License ("GPL") Version 2.0.  The
software code licensed under GPL Version 2.0 is free software that comes
with ABSOLUTELY NO WARRANTY.  You can redistribute and/or modify such
GPL code under the terms of GPL Version 2.0.  For more details, see the
documentation or "License Notice" file accompanying the IOS-XE software,
or the applicable URL provided on the flyer accompanying the IOS-XE
software.


ROM: IOS-XE ROMMON

Router uptime is 3 hours, 46 minutes
Uptime for this control processor is 3 hours, 47 minutes
System returned to ROM by reload
System image file is "bootflash:asr1001-universal.03.07.00b.S.152-4.S0b.bin"
Last reload reason: Reload Command


License Level: adventerprise
License Type: Permanent
Next reload license Level: adventerprise

cisco ASR1001 (1RU) processor with 3835109K/6147K bytes of memory.
Processor board ID SSL1219LCC
4 Gigabit Ethernet interfaces
32768K bytes of non-volatile configuration memory.
8388608K bytes of physical memory.
7741439K bytes of eUSB flash at bootflash:.

Configuration register is 0x2102

show memory

Kod: Zaznacz cały

 
Router#show memory
                Head    Total(b)     Used(b)     Free(b)   Lowest(b)  Largest(b)
 Address      Bytes     Prev     Next Ref     PrevF    NextF Alloc PC  what
Processor  7F57FA69E010   3926984224   358974676   3568009548   3009575816   3040654012
 lsmpi_io  7F57F9E951A8     6295128     6294304         824         824         412




debug ip bgp all

Kod: Zaznacz cały

 
*Apr 25 13:02:26.709: BGP_Router: unhandled major event code 128, minor 0
*Apr 25 13:02:26.821: BGP_Router: unhandled major event code 128, minor 0
*Apr 25 13:03:19.833: BGP: topo global:IPv4 Unicast:base Scanning routing tables
*Apr 25 13:03:19.844: BGP: topo global:IPv4 Multicast:base Scanning routing tables
*Apr 25 13:03:19.844: BGP: topo global:MVPNv4 Unicast:base Scanning routing tables
*Apr 25 13:03:57.010: BGP: 31.21.183.129 connection timed out 90197ms (last update) 90000ms (hold time)
*Apr 25 13:03:57.010: BGP: 31.21.183.129 went from Established to Closing
*Apr 25 13:03:57.010: %BGP-3-NOTIFICATION: sent to neighbor 31.21.183.129 4/0 (hold time expired) 0 bytes
*Apr 25 13:03:57.010: BGP: ses global 31.21.183.129 (0x7F5829F55C98:1) Send NOTIFICATION 4/0 (hold time expired) 0 bytes
*Apr 25 13:03:57.010: BGP: 31.21.183.129 local error close after sending NOTIFICATION
*Apr 25 13:03:57.010: %BGP-5-NBR_RESET: Neighbor 31.21.183.129 reset (BGP Notification sent)
*Apr 25 13:03:57.059: BGP: nbr_topo global 31.21.183.129 IPv4 Unicast:base (0x7F5829F55C98:1) NSF delete stale NSF not active
*Apr 25 13:03:57.059: BGP: nbr_topo global 31.21.183.129 IPv4 Unicast:base (0x7F5829F55C98:1) NSF no stale paths state is NSF not active
*Apr 25 13:03:57.059: BGP: nbr_topo global 31.21.183.129 IPv4 Unicast:base (0x7F5829F55C98:1) Resetting ALL counters.
*Apr 25 13:03:57.059: BGP: 31.21.183.129 closing
*Apr 25 13:03:57.059: BGP: ses global 31.21.183.129 (0x7F5829F55C98:1) Session close and reset neighbor 31.21.183.129 topostate
*Apr 25 13:03:57.059: BGP: nbr_topo global 31.21.183.129 IPv4 Unicast:base (0x7F5829F55C98:1) Resetting ALL counters.
*Apr 25 13:03:57.059: BGP: 31.21.183.129 went from Closing to Idle
*Apr 25 13:03:57.059: %BGP-5-ADJCHANGE: neighbor 31.21.183.129 Down BGP Notification sent
*Apr 25 13:03:57.059: %BGP_SESSION-5-ADJCHANGE: neighbor 31.21.183.129 IPv4 Unicast topology base removed from session  BGP Notification sent
*Apr 25 13:03:57.059: BGP: ses global 31.21.183.129 (0x7F5829F55C98:1) Removed topology IPv4 Unicast:base
*Apr 25 13:03:57.059: BGP: ses global 31.21.183.129 (0x7F5829F55C98:1) Removed last topology
*Apr 25 13:03:57.059: BGP: nbr global 31.21.183.129 Open active delayed 13312ms (35000ms max, 60% jitter)
*Apr 25 13:03:57.059: BGP: nbr global 31.21.183.129 Active open failed - open timer running
*Apr 25 13:04:09.757: BGP: 31.21.183.129 active went from Idle to Active
*Apr 25 13:04:09.757: BGP: 31.21.183.129 open active, local address 31.21.183.130
*Apr 25 13:04:09.762: BGP: ses global 31.21.183.129 (0x7F5829F55C98:0) act Adding topology IPv4 Unicast:base
*Apr 25 13:04:09.762: BGP: ses global 31.21.183.129 (0x7F5829F55C98:0) act Send OPEN
*Apr 25 13:04:09.762: BGP: ses global 31.21.183.129 (0x7F5829F55C98:0) act Building Enhanced Refresh capability
*Apr 25 13:04:09.762: BGP: 31.21.183.129 active went from Active to OpenSent
*Apr 25 13:04:09.762: BGP: 31.21.183.129 active sending OPEN, version 4, my as: 23456, holdtime 180 seconds, ID BC7D9CFE
*Apr 25 13:04:09.764: BGP: 31.21.183.129 active rcv message type 1, length (excl. header) 44
*Apr 25 13:04:09.764: BGP: ses global 31.21.183.129 (0x7F5829F55C98:0) act Receive OPEN
*Apr 25 13:04:09.764: BGP: 31.21.183.129 active rcv OPEN, version 4, holdtime 90 seconds
*Apr 25 13:04:09.764: BGP: 31.21.183.129 active rcv OPEN w/ OPTION parameter len: 34
*Apr 25 13:04:09.764: BGP: 31.21.183.129 active rcvd OPEN w/ optional parameter type 2 (Capability) len 6
*Apr 25 13:04:09.764: BGP: 31.21.183.129 active OPEN has CAPABILITY code: 1, length 4
*Apr 25 13:04:09.764: BGP: 31.21.183.129 active OPEN has MP_EXT CAP for afi/safi: 1/1
*Apr 25 13:04:09.764: BGP: 31.21.183.129 active rcvd OPEN w/ optional parameter type 2 (Capability) len 2
*Apr 25 13:04:09.764: BGP: 31.21.183.129 active OPEN has CAPABILITY code: 128, length 0
*Apr 25 13:04:09.764: BGP: 31.21.183.129 active OPEN has ROUTE-REFRESH capability(old) for all address-families
*Apr 25 13:04:09.764: BGP: 31.21.183.129 active rcvd OPEN w/ optional parameter type 2 (Capability) len 2
*Apr 25 13:04:09.764: BGP: 31.21.183.129 active OPEN has CAPABILITY code: 2, length 0
*Apr 25 13:04:09.764: BGP: 31.21.183.129 active OPEN has ROUTE-REFRESH capability(new) for all address-families
*Apr 25 13:04:09.764: BGP: 31.21.183.129 active rcvd OPEN w/ optional parameter type 2 (Capability) len 4
*Apr 25 13:04:09.764: BGP: 31.21.183.129 active OPEN has CAPABILITY code: 64, length 2
*Apr 25 13:04:09.764: BGP: ses global 31.21.183.129 (0x7F5829F55C98:0) act NSF OPEN has GR cap
*Apr 25 13:04:09.764: BGP: ses global 31.21.183.129 (0x7F5829F55C98:0) act NSF Peer has not restarted. Restart Time: 120
*Apr 25 13:04:09.764: BGP: 31.21.183.129 active rcvd OPEN w/ optional parameter type 2 (Capability) len 6
*Apr 25 13:04:09.764: BGP: 31.21.183.129 active OPEN has CAPABILITY code: 65, length 4
*Apr 25 13:04:09.764: BGP: 31.21.183.129 active OPEN has 4-byte ASN CAP for: 9012
*Apr 25 13:04:09.764: BGP: 31.21.183.129 active rcvd OPEN w/ optional parameter type 2 (Capability) len 2
*Apr 25 13:04:09.764: BGP: 31.21.183.129 active OPEN has CAPABILITY code: 71, length 0
*Apr 25 13:04:09.764: BGP: 31.21.183.129 active unrecognized capability code: 71 - ingored
*Apr 25 13:04:09.764: BGP: nbr global 31.21.183.129 neighbor does not have IPv4 MDT topology activated
*Apr 25 13:04:09.764: BGP: 31.21.183.129 active rcvd OPEN w/ remote AS 9012, 4-byte remote AS 9012
*Apr 25 13:04:09.764: BGP: 31.21.183.129 active went from OpenSent to OpenConfirm
*Apr 25 13:04:09.766: BGP: 31.21.183.129 active went from OpenConfirm to Established
*Apr 25 13:04:09.766: BGP: ses global 31.21.183.129 (0x7F5829F55C98:1) act Assigned ID
*Apr 25 13:04:09.766: BGP: ses global 31.21.183.129 (0x7F5829F55C98:1) Up
*Apr 25 13:04:09.766: %BGP-5-ADJCHANGE: neighbor 31.21.183.129 Up
*Apr 25 13:04:14.779: BGP_Router: unhandled major event code 128, minor 0
*Apr 25 13:04:14.785: BGP_Router: unhandled major event code 128, minor 0
*Apr 25 13:04:14.855: BGP: ses global 31.21.183.129 (0x7F5829F55C98:1) read request no-op
*Apr 25 13:04:19.807: BGP_Router: unhandled major event code 128, minor 0
*Apr 25 13:04:19.834: BGP_Router: unhandled major event code 128, minor 0
*Apr 25 13:04:19.848: BGP: topo global:IPv4 Unicast:base Scanning routing tables
*Apr 25 13:04:19.898: BGP: topo global:IPv4 Multicast:base Scanning routing tables
*Apr 25 13:04:19.898: BGP: topo global:MVPNv4 Unicast:base Scanning routing tables
*Apr 25 13:04:28.539: BGP_Router: unhandled major event code 128, minor 0
*Apr 25 13:04:28.565: BGP_Router: unhandled major event code 128, minor 0
*Apr 25 13:04:34.568: BGP_Router: unhandled major event code 128, minor 0
*Apr 25 13:04:34.638: BGP_Router: unhandled major event code 128, minor 0
*Apr 25 13:04:34.737: BGP_Router: unhandled major event code 128, minor 0
*Apr 25 13:05:19.988: BGP: topo global:IPv4 Unicast:base Scanning routing tables
*Apr 25 13:05:20.119: BGP: topo global:IPv4 Multicast:base Scanning routing tables
*Apr 25 13:05:20.119: BGP: topo global:MVPNv4 Unicast:base Scanning routing tables
*Apr 25 13:06:04.890: BGP: 31.21.183.129 connection timed out 90217ms (last update) 90000ms (hold time)
*Apr 25 13:06:04.890: BGP: 31.21.183.129 went from Established to Closing
*Apr 25 13:06:04.890: %BGP-3-NOTIFICATION: sent to neighbor 31.21.183.129 4/0 (hold time expired) 0 bytes
*Apr 25 13:06:04.890: BGP: ses global 31.21.183.129 (0x7F5829F55C98:1) Send NOTIFICATION 4/0 (hold time expired) 0 bytes
*Apr 25 13:06:04.890: BGP: 31.21.183.129 local error close after sending NOTIFICATION
*Apr 25 13:06:04.890: %BGP-5-NBR_RESET: Neighbor 31.21.183.129 reset (BGP Notification sent)
*Apr 25 13:06:05.406: BGP: nbr_topo global 31.21.183.129 IPv4 Unicast:base (0x7F5829F55C98:1) NSF delete stale NSF not active
*Apr 25 13:06:05.406: BGP: nbr_topo global 31.21.183.129 IPv4 Unicast:base (0x7F5829F55C98:1) NSF no stale paths state is NSF not active
*Apr 25 13:06:05.406: BGP: nbr_topo global 31.21.183.129 IPv4 Unicast:base (0x7F5829F55C98:1) Resetting ALL counters.
*Apr 25 13:06:05.406: BGP: 31.21.183.129 closing
*Apr 25 13:06:05.406: BGP: ses global 31.21.183.129 (0x7F5829F55C98:1) Session close and reset neighbor 31.21.183.129 topostate
*Apr 25 13:06:05.406: BGP: nbr_topo global 31.21.183.129 IPv4 Unicast:base (0x7F5829F55C98:1) Resetting ALL counters.
*Apr 25 13:06:05.406: BGP: 31.21.183.129 went from Closing to Idle
*Apr 25 13:06:05.406: %BGP-5-ADJCHANGE: neighbor 31.21.183.129 Down BGP Notification sent
*Apr 25 13:06:05.406: %BGP_SESSION-5-ADJCHANGE: neighbor 31.21.183.129 IPv4 Unicast topology base removed from session  BGP Notification sent
*Apr 25 13:06:05.406: BGP: ses global 31.21.183.129 (0x7F5829F55C98:1) Removed topology IPv4 Unicast:base
*Apr 25 13:06:05.406: BGP: ses global 31.21.183.129 (0x7F5829F55C98:1) Removed last topology
*Apr 25 13:06:05.406: BGP: nbr global 31.21.183.129 Open active delayed 12288ms (35000ms max, 60% jitter)
*Apr 25 13:06:05.406: BGP: nbr global 31.21.183.129 Active open failed - open timer running
*Apr 25 13:06:06.006: BGP: Sched timer-wheel running slow by 1 ticks
*Apr 25 13:06:08.113: BGP: timer-wheel running slow by 2 ticks
*Apr 25 13:06:16.546: BGP: 31.21.183.129 active went from Idle to Active
*Apr 25 13:06:16.546: BGP: 31.21.183.129 open active, local address 31.21.183.130
*Apr 25 13:06:16.711: BGP: ses global 31.21.183.129 (0x7F58126D9B98:0) act Adding topology IPv4 Unicast:base
*Apr 25 13:06:16.711: BGP: ses global 31.21.183.129 (0x7F58126D9B98:0) act Send OPEN
*Apr 25 13:06:16.711: BGP: ses global 31.21.183.129 (0x7F58126D9B98:0) act Building Enhanced Refresh capability
*Apr 25 13:06:16.711: BGP: 31.21.183.129 active went from Active to OpenSent
*Apr 25 13:06:16.711: BGP: 31.21.183.129 active sending OPEN, version 4, my as: 23456, holdtime 180 seconds, ID BC7D9CFE
*Apr 25 13:06:16.906: BGP: 31.21.183.129 active rcv message type 1, length (excl. header) 44
*Apr 25 13:06:16.906: BGP: ses global 31.21.183.129 (0x7F58126D9B98:0) act Receive OPEN
*Apr 25 13:06:16.906: BGP: 31.21.183.129 active rcv OPEN, version 4, holdtime 90 seconds
*Apr 25 13:06:16.906: BGP: 31.21.183.129 active rcv OPEN w/ OPTION parameter len: 34
*Apr 25 13:06:16.906: BGP: 31.21.183.129 active rcvd OPEN w/ optional parameter type 2 (Capability) len 6
*Apr 25 13:06:16.906: BGP: 31.21.183.129 active OPEN has CAPABILITY code: 1, length 4
*Apr 25 13:06:16.906: BGP: 31.21.183.129 active OPEN has MP_EXT CAP for afi/safi: 1/1
*Apr 25 13:06:16.906: BGP: 31.21.183.129 active rcvd OPEN w/ optional parameter type 2 (Capability) len 2
*Apr 25 13:06:16.906: BGP: 31.21.183.129 active OPEN has CAPABILITY code: 128, length 0
*Apr 25 13:06:16.906: BGP: 31.21.183.129 active OPEN has ROUTE-REFRESH capability(old) for all address-families
*Apr 25 13:06:16.906: BGP: 31.21.183.129 active rcvd OPEN w/ optional parameter type 2 (Capability) len 2
*Apr 25 13:06:16.906: BGP: 31.21.183.129 active OPEN has CAPABILITY code: 2, length 0
*Apr 25 13:06:16.906: BGP: 31.21.183.129 active OPEN has ROUTE-REFRESH capability(new) for all address-families
*Apr 25 13:06:16.906: BGP: 31.21.183.129 active rcvd OPEN w/ optional parameter type 2 (Capability) len 4
*Apr 25 13:06:16.906: BGP: 31.21.183.129 active OPEN has CAPABILITY code: 64, length 2
*Apr 25 13:06:16.906: BGP: ses global 31.21.183.129 (0x7F58126D9B98:0) act NSF OPEN has GR cap
*Apr 25 13:06:16.906: BGP: ses global 31.21.183.129 (0x7F58126D9B98:0) act NSF Peer has not restarted. Restart Time: 120
*Apr 25 13:06:16.906: BGP: 31.21.183.129 active rcvd OPEN w/ optional parameter type 2 (Capability) len 6
*Apr 25 13:06:16.906: BGP: 31.21.183.129 active OPEN has CAPABILITY code: 65, length 4
*Apr 25 13:06:16.906: BGP: 31.21.183.129 active OPEN has 4-byte ASN CAP for: 9012
*Apr 25 13:06:16.906: BGP: 31.21.183.129 active rcvd OPEN w/ optional parameter type 2 (Capability) len 2
*Apr 25 13:06:16.906: BGP: 31.21.183.129 active OPEN has CAPABILITY code: 71, length 0
*Apr 25 13:06:16.906: BGP: 31.21.183.129 active unrecognized capability code: 71 - ingored
*Apr 25 13:06:16.906: BGP: nbr global 31.21.183.129 neighbor does not have IPv4 MDT topology activated
*Apr 25 13:06:16.906: BGP: 31.21.183.129 active rcvd OPEN w/ remote AS 9012, 4-byte remote AS 9012
*Apr 25 13:06:16.906: BGP: 31.21.183.129 active went from OpenSent to OpenConfirm
*Apr 25 13:06:16.995: BGP: 31.21.183.129 active went from OpenConfirm to Established
*Apr 25 13:06:16.995: BGP: ses global 31.21.183.129 (0x7F58126D9B98:1) act Assigned ID
*Apr 25 13:06:16.995: BGP: ses global 31.21.183.129 (0x7F58126D9B98:1) Up
*Apr 25 13:06:16.995: %BGP-5-ADJCHANGE: neighbor 31.21.183.129 Up
*Apr 25 13:06:17.101: BGP_Router: unhandled major event code 128, minor 0
*Apr 25 13:06:17.188: BGP_Router: unhandled major event code 128, minor 0
*Apr 25 13:06:17.241: BGP_Router: unhandled major event code 128, minor 0
*Apr 25 13:06:17.294: BGP_Router: unhandled major event code 128, minor 0
*Apr 25 13:06:17.347: BGP_Router: unhandled major event code 128, minor 0
*Apr 25 13:06:17.430: BGP_Router: unhandled major event code 128, minor 0
*Apr 25 13:06:17.437: BGP_Router: unhandled major event code 128, minor 0

Awatar użytkownika
psles
wannabe
wannabe
Posty: 114
Rejestracja: 04 sie 2011, 06:09
Lokalizacja: STL, USA

Re: Problem z BGP na Ruterze Cisco ASR1001

#2

#2 Post autor: psles » 25 kwie 2019, 17:45

A nie powinieneś mieć troche dłuższego tego hold-time? 90s to jakoś dziwnie mało. Default jeśli pamiętam jest 180s, ale sprawdź jeszcze z T-mobile jak powinno być w twoim przypadku. Z drugiej strony troche jakbyś keepalives nie dostawał.
.ılı..ılı. CCNP

Awatar użytkownika
nell
wannabe
wannabe
Posty: 190
Rejestracja: 10 maja 2009, 12:17

Re: Problem z BGP na Ruterze Cisco ASR1001

#3

#3 Post autor: nell » 25 kwie 2019, 19:29

Ten hold-time to mi druga strona zapodała, ale wymusiłem 180s, ale to nic nie zmieniło, tutaj dodam, że skonfigurowałem drugiego peera i tam jest wszystko ok, zastanawiam się czy to może nie MTU ? albo też coś tam widziałem z TCP MSS. Gdzieś tam szperając w sieci w którym dokumencie było aby sprawdzić pinga na neibhora ze zdefiniowanym rozmiarem pakietu na 1500, tak zrobiłem ale ping nie poszedł co się okazało w ogóle nie idzie nawet jak określę size nawet nawet na 64, podczas gdy drugi peer odpowiada zawsze. NIe wiem czy we właściwą stroną w ogóle kombinuje ...

lbromirs
CCIE
CCIE
Posty: 4023
Rejestracja: 30 lis 2006, 08:44

Re: Problem z BGP na Ruterze Cisco ASR1001

#4

#4 Post autor: lbromirs » 25 kwie 2019, 23:13

Rzuć okiem czy to nie kwestia CoPP (control-plane XXX). Na moim domowym 1001 pełne BGP zbiegało się przez link 100Mbit/s znacznie poniżej 60s, na obecnym 1001X jest jeszcze szybciej. Przy takiej skali MTU nie zrobi dużej różnicy.

Awatar użytkownika
nell
wannabe
wannabe
Posty: 190
Rejestracja: 10 maja 2009, 12:17

Re: Problem z BGP na Ruterze Cisco ASR1001

#5

#5 Post autor: nell » 26 kwie 2019, 10:48

Hmm u mnie przy control-plane mogę tylko dodać polisę w kierunku in lub out to miałeś na myśli ? scheaping ?

jankad
wannabe
wannabe
Posty: 94
Rejestracja: 26 lis 2009, 20:58
Lokalizacja: Katowice

Re: Problem z BGP na Ruterze Cisco ASR1001  Temat rozwiązany

#6

#6 Post autor: jankad » 26 kwie 2019, 11:31

Czy to czasem druga strona nie zrywa? Może wysyłasz za dużo prefiksów?
Sprawdź co rozgłaszasz za pomocą:
sh ip bgp neighbors 31.21.183.129 advertised-routes
--
Z poważaniem:
Adam Wołk-Jankowski
www.systel.pl

lbromirs
CCIE
CCIE
Posty: 4023
Rejestracja: 30 lis 2006, 08:44

Re: Problem z BGP na Ruterze Cisco ASR1001

#7

#7 Post autor: lbromirs » 26 kwie 2019, 15:13

Pokaż pełną konfigurację - wywal tylko użytkowników i zamaskuj adresy IP.

Awatar użytkownika
nell
wannabe
wannabe
Posty: 190
Rejestracja: 10 maja 2009, 12:17

Re: Problem z BGP na Ruterze Cisco ASR1001

#8

#8 Post autor: nell » 28 kwie 2019, 08:36

Myślę, że to druga strona zrywała, nie do końca wiem dlaczego, ale ustawieniu filtrowania wysyłanych prefixów poszło.

Awatar użytkownika
toczyskik
wannabe
wannabe
Posty: 296
Rejestracja: 09 maja 2006, 14:28
Lokalizacja: Warszawa

Re: Problem z BGP na Ruterze Cisco ASR1001

#9

#9 Post autor: toczyskik » 29 kwie 2019, 09:16

Ponieważ zacząłeś im rozgłaszać całą tablice routingu :). Operatorzy przed czymś takim się zabezpieczają ustawiając limit na sesji BGP. Ty też byś się nie chciał się zrobić tranzytem dla ruchu IP.

Co do timerów. Każdy vendor ma swoje ustawiania Cisco 180/60, Juniper 90/30, itd. Wygrywa ten niższy timer o ile dobrze pamiętam.
Pozdrawiam
Krzysiek Te.

ODPOWIEDZ