Toon posts:

bgp / unrecognized capability code: 65

Pagina: 1
Acties:

maandag 21 september 2009 19:47

Acties:
  • DDX
  • Registratie: April 2001
  • Laatst online: 21:26

DDX

Topicstarter
Wij hebben een probleem met een van onze routers (linux / quagga)
Op dit moment krijgen we geen default route (0.0.0.0/0) van onze uplink provider.
Via de support van onze provider schieten we niet echt op, dus ik hoop dat iemand hier misschien een idee heeft wat onderstaande melding kan beteken :

2009/09/20 11:57:08 BGP: 10.1.1.1 unrecognized capability code: 65 - ignored
2009/09/20 11:57:08 BGP: %ADJCHANGE: neighbor 10.1.1.1 Up

De quagga website/mailinglist is al enige tijd down, daar kan ik niet echt terecht.

Het probleem/deze melding lijken met elkaar te maken te hebben.
Onze provider had issues/heeft hun hardware vervangen en sindsdien krijgen we deze melding/geen default meer.

(ter info: we hebben een exact zelfde router/configuratie staan als backup die gewoon netjes een default route krijgt/niet deze melding)

https://www.strava.com/athletes/2323035

maandag 21 september 2009 21:15

Acties:
  • jvanhambelgium
  • Registratie: April 2007
  • Laatst online: 29-01 21:25

jvanhambelgium

Code 65 heeft te maken met de AS nummering, namelijk de ondersteuning voor 4byte AS-nummering.

Blijkbaar heeft jullie neighbor 10.1.1.1 deze "capability" niet voor 4byte AS nummering, maar waarom jullie dan geen default zouden krijgen is me ook een raadsel natuurlijk.

Standaard is de BGP AS encoding 2 bytes, dus 16 bits oftewel tot AS0 -> AS65535
Deze capability doet daar nog een schepje bovenop tot AS4294967295


Krijg je voor de rest routes binnen ?? Wat voor een peering-relatie heb je met deze ISP ?
Doet deze router peerings met andere ISP's ?

[ Voor 14% gewijzigd door jvanhambelgium op 21-09-2009 21:18 ]

dinsdag 22 september 2009 09:29

Acties:
  • DDX
  • Registratie: April 2001
  • Laatst online: 21:26

DDX

Topicstarter
Wij krijgen enkel de 0.0.0.0/0 van onze provider
We hebben 2 routers staan die beide de default route binnenkrijgen. (tenminste normaal gesproken)
En wij vertellen onze netwerken aan hun. (intern draaien we ospf)

Even wat configuratie :

router1 die het probleem heeft :
code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32

router bgp 10753
 bgp router-id 213.19.134.1
 bgp log-neighbor-changes
 redistribute static route-map static-into-bgp
 neighbor level-3 peer-group
 neighbor level-3 description ***Peering with level 3*** 
 neighbor level-3 soft-reconfiguration inbound
 neighbor level-3 route-map import-from-level3 in
 neighbor level-3 route-map export-to-level3 out
 neighbor 212.72.44.81 remote-as 3356
 neighbor 212.72.44.81 peer-group level-3
 neighbor 213.19.134.2 remote-as 10753
 neighbor 213.19.134.2 update-source 213.19.134.1
 neighbor 213.19.134.2 next-hop-self
 neighbor 213.19.134.2 soft-reconfiguration inbound
!
ip prefix-list default-only seq 5 permit 0.0.0.0/0
ip prefix-list pv-networks seq 5 permit 212.72.36.0/23
ip prefix-list pv-networks seq 10 permit 213.19.134.0/24
ip prefix-list pv-networks seq 15 permit 213.19.167.0/24
ip prefix-list pv-networks seq 20 permit 213.19.176.0/23
ip prefix-list pv-networks seq 25 permit 213.19.178.0/24
!
route-map export-to-level3 permit 5
 match ip address prefix-list pv-networks
!
route-map import-from-level3 permit 5
 match ip address prefix-list default-only
 set local-preference 100
!
route-map static-into-bgp permit 5
 match ip address prefix-list pv-networks


show ip bgp neighbor output :
code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37

BGP neighbor is 212.72.44.81, remote AS 3356, local AS 10753, external link
 Member of peer-group level-3 for session parameters
  BGP version 4, remote router ID 4.68.186.139
  BGP state = Established, up for 1d21h30m
  Last read 00:00:09, hold time is 90, keepalive interval is 30 seconds
  Neighbor capabilities:
    Route refresh: advertised and received(old & new)
    Address family IPv4 Unicast: advertised and received
    Address family IPv4 Multicast: received
    Graceful Restart Capabilty: received
      Remote Restart timer is 120 seconds
      Address families preserved by peer:
        none
  Received 9400 messages, 1 notifications, 0 in queue
  Sent 8987 messages, 4 notifications, 0 in queue
  Route refresh request: received 0, sent 0
  Minimum time between advertisement runs is 30 seconds

 For address family: IPv4 Unicast
  level-3 peer-group member
  Inbound soft reconfiguration allowed
  Community attribute sent to this neighbor(both)
  Inbound path policy configured
  Outbound path policy configured
  Route map for incoming advertisements is *import-from-level3
  Route map for outgoing advertisements is *export-to-level3
  0 accepted prefixes

  Connections established 33; dropped 32
  Last reset 2d13h22m, due to Admin. shutdown
Local host: 212.72.44.82, Local port: 47100
Foreign host: 212.72.44.81, Foreign port: 179
Nexthop: 212.72.44.82
Nexthop global: ::
Nexthop local: ::
BGP connection: non shared network
Read thread: on  Write thread: off


en nog wat bgp output :
code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

# show ip bgp neighbors 212.72.44.81 received-routes 
# show ip bgp 
BGP table version is 0, local router ID is 213.19.134.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal
Origin codes: i - IGP, e - EGP, ? - incomplete

   Network          Next Hop            Metric LocPrf Weight Path
*>i0.0.0.0          213.19.134.2                   50      0 3356 i
*> 212.72.36.0/23   212.72.44.82             0         32768 ?
*> 213.19.134.0     212.72.44.82             0         32768 ?
*> 213.19.167.0     212.72.44.82             0         32768 ?
*> 213.19.176.0/23  212.72.44.82             0         32768 ?
*> 213.19.178.0     212.72.44.82             0         32768 ?

Total number of prefixes 6



router2 :
code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34

router bgp 10753
 bgp router-id 213.19.134.2
 bgp log-neighbor-changes
 redistribute static route-map static-into-bgp
 neighbor level-3 peer-group
 neighbor level-3 description ***Peering with level 3*** 
 neighbor level-3 soft-reconfiguration inbound
 neighbor level-3 route-map import-from-level3 in
 neighbor level-3 route-map export-to-level3 out
 neighbor 212.72.45.145 remote-as 3356
 neighbor 212.72.45.145 peer-group level-3
 neighbor 213.19.134.1 remote-as 10753
 neighbor 213.19.134.1 update-source 213.19.134.2
 neighbor 213.19.134.1 next-hop-self
 neighbor 213.19.134.1 soft-reconfiguration inbound
 distance bgp 20 20 200
!
ip prefix-list default-only seq 5 permit 0.0.0.0/0
ip prefix-list pv-networks seq 5 permit 212.72.36.0/23
ip prefix-list pv-networks seq 10 permit 213.19.134.0/24
ip prefix-list pv-networks seq 15 permit 213.19.167.0/24
ip prefix-list pv-networks seq 20 permit 213.19.176.0/23
ip prefix-list pv-networks seq 25 permit 213.19.178.0/24
!
route-map export-to-level3 permit 5
 match ip address prefix-list pv-networks
 set metric 20
!
route-map import-from-level3 permit 5
 match ip address prefix-list default-only
 set local-preference 50
!
route-map static-into-bgp permit 5
 match ip address prefix-list pv-networks


code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32

BGP neighbor is 212.72.45.145, remote AS 3356, local AS 10753, external link
 Member of peer-group level-3 for session parameters
  BGP version 4, remote router ID 4.68.0.173
  BGP state = Established, up for 19:15:43
  Last read 00:00:55, hold time is 180, keepalive interval is 60 seconds
  Neighbor capabilities:
    Route refresh: advertised and received(old & new)
    Address family IPv4 Unicast: advertised and received
  Received 28707 messages, 0 notifications, 0 in queue
  Sent 28866 messages, 3 notifications, 0 in queue
  Route refresh request: received 0, sent 0
  Minimum time between advertisement runs is 30 seconds

 For address family: IPv4 Unicast
  level-3 peer-group member
  Inbound soft reconfiguration allowed
  Community attribute sent to this neighbor(both)
  Inbound path policy configured
  Outbound path policy configured
  Route map for incoming advertisements is *import-from-level3
  Route map for outgoing advertisements is *export-to-level3
  1 accepted prefixes

  Connections established 4; dropped 3
  Last reset 19:17:54, due to Admin. shutdown
Local host: 212.72.45.146, Local port: 179
Foreign host: 212.72.45.145, Foreign port: 53072
Nexthop: 212.72.45.146
Nexthop global: ::
Nexthop local: ::
BGP connection: non shared network
Read thread: on  Write thread: off


code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23

# show ip bgp neighbors 212.72.45.145 received-routes 
BGP table version is 0, local router ID is 213.19.134.2
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal
Origin codes: i - IGP, e - EGP, ? - incomplete

   Network          Next Hop            Metric LocPrf Weight Path
*> 0.0.0.0          212.72.45.145                          0 3356 i

Total number of prefixes 1
# show ip bgp 
BGP table version is 0, local router ID is 213.19.134.2
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal
Origin codes: i - IGP, e - EGP, ? - incomplete

   Network          Next Hop            Metric LocPrf Weight Path
*> 0.0.0.0          212.72.45.145                  50      0 3356 i
*>i212.72.36.0/23   213.19.134.1             0    100      0 ?
*>i213.19.134.0     213.19.134.1             0    100      0 ?
*>i213.19.167.0     213.19.134.1             0    100      0 ?
*>i213.19.176.0/23  213.19.134.1             0    100      0 ?
*>i213.19.178.0     213.19.134.1             0    100      0 ?

Total number of prefixes 6


En vanuit onze provider de bgp config (die volgens hun goed moet staan)
code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53

============= BGP config ========

chsmith@edge3.ams1> ...ocols bgp group peer-212.72.44.82
type external;
description "81699-00001::Uplink for EXPLAINER DC";
import [ peer-212.72.44.82 customer bb2 ];
family inet {
    any {
        prefix-limit {
            maximum 110;
            teardown 90;
        }
    }
}
export [ none send-default ];
remove-private;
peer-as 10753;
neighbor 212.72.44.82;


======= display set on network and BGP neighbor ======


chsmith@edge3.ams1> show configuration | display set | grep 212.72.44.80
set routing-options static route 212.72.44.80/30 next-hop 212.72.44.82
set routing-options static route 212.72.44.80/30 community 3356:123
set routing-options static route 212.72.44.80/30 community 3356:22
set policy-options policy-statement connected-non-pool-bb2 term route-set1 from 
route-filter 212.72.44.80/30 exact

chsmith@edge3.ams1> show configuration | display set | grep 212.72.44.82
set routing-options static route 212.72.44.80/30 next-hop 212.72.44.82
set protocols bgp group peer-212.72.44.82 type external
set protocols bgp group peer-212.72.44.82 description "81699-00001::Uplink for EXPLAINER DC"
set protocols bgp group peer-212.72.44.82 import peer-212.72.44.82
set protocols bgp group peer-212.72.44.82 import customer
set protocols bgp group peer-212.72.44.82 import bb2
set protocols bgp group peer-212.72.44.82 family inet any prefix-limit maximum 110
set protocols bgp group peer-212.72.44.82 family inet any prefix-limit teardown 90
set protocols bgp group peer-212.72.44.82 export none
set protocols bgp group peer-212.72.44.82 export send-default
set protocols bgp group peer-212.72.44.82 remove-private
set protocols bgp group peer-212.72.44.82 peer-as 10753
set protocols bgp group peer-212.72.44.82 neighbor 212.72.44.82
set policy-options policy-statement peer-212.72.44.82 term route-set1 from route-filter 212.72.36.0/23 exact
set policy-options policy-statement peer-212.72.44.82 term route-set1 from route-filter 213.19.134.0/24 exact
set policy-options policy-statement peer-212.72.44.82 term route-set1 from route-filter 213.19.167.0/24 exact
set policy-options policy-statement peer-212.72.44.82 term route-set1 from route-filter 213.19.176.0/24 exact
set policy-options policy-statement peer-212.72.44.82 term route-set1 from route-filter 213.19.178.0/24 exact
set policy-options policy-statement peer-212.72.44.82 term route-set1 then next policy
set policy-options policy-statement peer-212.72.44.82 term route-set1 then accept
set policy-options policy-statement peer-212.72.44.82 term reject then reject
set firewall filter internet term customer-bgp from source-address 212.72.44.82/32

[ Voor 68% gewijzigd door DDX op 22-09-2009 09:34 ]

https://www.strava.com/athletes/2323035

dinsdag 22 september 2009 10:26

Acties:
  • TrailBlazer
  • Registratie: Oktober 2000
  • Laatst online: 22-01 08:08

TrailBlazer

Karnemelk FTW

wat gebeurt er als je bij de niet werkende router de IBGP neighbor even disabled. Volgens de local-pref zou je inderdaad de EBGP route moeten preferren. Als je die inderdaad krijgt van je provider maar als je even helemaal zonder filtering/ andere neighbors kijkt weet je tenminste zeker dat je daar geen fuckup maakt.

[ Voor 35% gewijzigd door TrailBlazer op 22-09-2009 10:31 ]

dinsdag 22 september 2009 11:12

Acties:
  • jvanhambelgium
  • Registratie: April 2007
  • Laatst online: 29-01 21:25

jvanhambelgium

Er is wel degelijk verschil tussen de configs van "router1" en "router2" namelijk de LOCALPREF waarde die op de inbound policy hebt gezet en een metric statement op de jullie segmentjes die je wil announcen.


Router1
route-map export-to-level3 permit 5
match ip address prefix-list pv-networks

route-map import-from-level3 permit 5
match ip address prefix-list default-only
set local-preference 100


Router2
route-map export-to-level3 permit 5
match ip address prefix-list pv-networks
set metric 20
!
route-map import-from-level3 permit 5
match ip address prefix-list default-only
set local-preference 50


LOCAL_PREF is niet helemaal onbelangrijk natuurlijk, of zijn het net veranderingen die je inklopte om de traffiek buiten te krijgen ?


Zoals ik het nu kan zien zou correcte re-distributie alle traffiek richting ROUTER2 moeten gaan die het dan buiten gooit omdat zijn LOCAL_PREF hoger is dan die van ROUTER1.
Ook heb je op router2 nog een "distance bgp 20 20 200" staan die niet op ROUTER1 terug te vinden is


Mischien iets meer debug op zetten op router1 en de sessie een stamp geven ?
Het ondertussen al meer als 8jaar geleden dat ik nog met BGP heb liggen stoeien, maar de config ziet er betrekkelijk ok uit eigenlijk.

dinsdag 22 september 2009 11:24

Acties:
  • TrailBlazer
  • Registratie: Oktober 2000
  • Laatst online: 22-01 08:08

TrailBlazer

Karnemelk FTW

local_pref op rtr2 is juist lager dus al het verkeer zou via rtr 1 moeten gaan. Ook de metric van 20 is hoger dan de standaard waarde van 0 op rtr 1 dus dat klopt ook zo te zien.
distance zou niks uit mogen maken.

[ Voor 18% gewijzigd door TrailBlazer op 22-09-2009 11:25 ]

dinsdag 22 september 2009 11:38

Acties:
  • jvanhambelgium
  • Registratie: April 2007
  • Laatst online: 29-01 21:25

jvanhambelgium

Zoals ik schreef ... 8 jaar is een eeuwigheid ;-)
Anyway, hij zal toch moeten beginnen debuggen (aangezien je maar peanuts aan routes binnenneemt) in detail om te zien of je daar iets ziet binnenkomen van de remote peer dat op 0.0.0.0/0 trekt...

[ Voor 33% gewijzigd door jvanhambelgium op 22-09-2009 11:40 ]

dinsdag 22 september 2009 12:36

Acties:
  • DDX
  • Registratie: April 2001
  • Laatst online: 21:26

DDX

Topicstarter
Onze config draaide al zo'n 2 jaar zonder problemen.
En idd zit er verschil in config om te zorgen dat al het verkeer via router1 naar binnen komt/naar buiten gaat.
(zodat iptables conntrack werkt)

Ik zal eens gaan debuggen idd.

De ibgp neighbor heb ik al eens disabled, maakt geen verschil.

[ Voor 12% gewijzigd door DDX op 22-09-2009 12:37 ]

https://www.strava.com/athletes/2323035

dinsdag 22 september 2009 23:45

Acties:
  • DDX
  • Registratie: April 2001
  • Laatst online: 21:26

DDX

Topicstarter
goed debug output

router1 ;
code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59

# sh debugging bgp
BGP debugging status:
  BGP debugging is on
  BGP events debugging is on
  BGP updates debugging is on
  BGP filter debugging is on

# clear ip bgp 212.72.44.81

2009/09/22 23:37:58 BGP: %NOTIFICATION: sent to neighbor 212.72.44.81 6/4 (Cease/Administratively Reset) 0 bytes 
2009/09/22 23:37:58 BGP: 212.72.44.81 send message type 3, length (incl. header) 21
2009/09/22 23:37:58 BGP: %ADJCHANGE: neighbor 212.72.44.81 Down User reset
2009/09/22 23:38:05 BGP: 213.19.134.2 rcv message type 4, length (excl. header) 0
2009/09/22 23:38:05 BGP: 213.19.134.2 send message type 4, length (incl. header) 19
2009/09/22 23:38:10 BGP: 212.72.44.81 went from Idle to Connect
2009/09/22 23:38:10 BGP: 212.72.44.81 [Event] Connect start to 212.72.44.81 fd 12
2009/09/22 23:38:10 BGP: 212.72.44.81 went from Connect to OpenSent
2009/09/22 23:38:10 BGP: 212.72.44.81 sending OPEN, version 4, my as 10753, holdtime 180, id 213.19.134.1
2009/09/22 23:38:10 BGP: 212.72.44.81 send message type 1, length (incl. header) 45
2009/09/22 23:38:10 BGP: 212.72.44.81 rcv message type 1, length (excl. header) 48
2009/09/22 23:38:10 BGP: 212.72.44.81 rcv OPEN, version 4, remote-as 3356, holdtime 90, id 4.68.186.139
2009/09/22 23:38:10 BGP: 212.72.44.81 rcv OPEN w/ OPTION parameter len: 38
2009/09/22 23:38:10 BGP: 212.72.44.81 rcvd OPEN w/ optional parameter type 2 (Capability) len 6
2009/09/22 23:38:10 BGP: 212.72.44.81 OPEN has CAPABILITY code: 1, length 4
2009/09/22 23:38:10 BGP: 212.72.44.81 OPEN has MP_EXT CAP for afi/safi: 1/1
2009/09/22 23:38:10 BGP: 212.72.44.81 rcvd OPEN w/ optional parameter type 2 (Capability) len 6
2009/09/22 23:38:10 BGP: 212.72.44.81 OPEN has CAPABILITY code: 1, length 4
2009/09/22 23:38:10 BGP: 212.72.44.81 OPEN has MP_EXT CAP for afi/safi: 1/2
2009/09/22 23:38:10 BGP: 212.72.44.81 rcvd OPEN w/ optional parameter type 2 (Capability) len 2
2009/09/22 23:38:10 BGP: 212.72.44.81 OPEN has CAPABILITY code: 128, length 0
2009/09/22 23:38:10 BGP: 212.72.44.81 OPEN has ROUTE-REFRESH capability(old) for all address-families
2009/09/22 23:38:10 BGP: 212.72.44.81 rcvd OPEN w/ optional parameter type 2 (Capability) len 2
2009/09/22 23:38:10 BGP: 212.72.44.81 OPEN has CAPABILITY code: 2, length 0
2009/09/22 23:38:10 BGP: 212.72.44.81 OPEN has ROUTE-REFRESH capability(new) for all address-families
2009/09/22 23:38:10 BGP: 212.72.44.81 rcvd OPEN w/ optional parameter type 2 (Capability) len 4
2009/09/22 23:38:10 BGP: 212.72.44.81 OPEN has CAPABILITY code: 64, length 2
2009/09/22 23:38:10 BGP: 212.72.44.81 OPEN has Graceful Restart capability
2009/09/22 23:38:10 BGP: 212.72.44.81 Peer has not restarted. Restart Time : 120
2009/09/22 23:38:10 BGP: 212.72.44.81 rcvd OPEN w/ optional parameter type 2 (Capability) len 6
2009/09/22 23:38:10 BGP: 212.72.44.81 OPEN has CAPABILITY code: 65, length 4
2009/09/22 23:38:10 BGP: 212.72.44.81 unrecognized capability code: 65 - ignored
2009/09/22 23:38:10 BGP: 212.72.44.81 went from OpenSent to OpenConfirm
2009/09/22 23:38:10 BGP: 212.72.44.81 send message type 4, length (incl. header) 19
2009/09/22 23:38:10 BGP: 212.72.44.81 rcv message type 4, length (excl. header) 0
2009/09/22 23:38:10 BGP: 212.72.44.81 went from OpenConfirm to Established
2009/09/22 23:38:10 BGP: %ADJCHANGE: neighbor 212.72.44.81 Up
2009/09/22 23:38:10 BGP: 212.72.44.81 send message type 4, length (incl. header) 19
2009/09/22 23:38:10 BGP: 212.72.44.81 send UPDATE 212.72.36.0/23
2009/09/22 23:38:10 BGP: 212.72.44.81 send UPDATE 213.19.178.0/24
2009/09/22 23:38:10 BGP: 212.72.44.81 send UPDATE 213.19.176.0/23
2009/09/22 23:38:10 BGP: 212.72.44.81 send UPDATE 213.19.167.0/24
2009/09/22 23:38:10 BGP: 212.72.44.81 send UPDATE 213.19.134.0/24
2009/09/22 23:38:10 BGP: 212.72.44.81 rcv message type 4, length (excl. header) 0
2009/09/22 23:38:27 BGP: Performing BGP general scanning
2009/09/22 23:38:38 BGP: 212.72.44.81 rcv message type 4, length (excl. header) 0
2009/09/22 23:38:40 BGP: 212.72.44.81 send message type 4, length (incl. header) 19
2009/09/22 23:39:05 BGP: 213.19.134.2 rcv message type 4, length (excl. header) 0
2009/09/22 23:39:05 BGP: 213.19.134.2 send message type 4, length (incl. header) 19
2009/09/22 23:39:06 BGP: 212.72.44.81 rcv message type 4, length (excl. header)


code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50

# show debugging bgp 
BGP debugging status:
  BGP debugging is on
  BGP events debugging is on
  BGP updates debugging is on
  BGP filter debugging is on
# clear ip bgp 212.72.45.145

2009/09/22 23:42:10 BGP: %NOTIFICATION: sent to neighbor 212.72.45.145 6/4 (Cease/Administratively Reset) 0 bytes 
2009/09/22 23:42:10 BGP: 212.72.45.145 send message type 3, length (incl. header) 21
2009/09/22 23:42:10 BGP: %ADJCHANGE: neighbor 212.72.45.145 Down User reset
2009/09/22 23:42:10 BGP: 213.19.134.1 send UPDATE 0.0.0.0/0 -- unreachable
2009/09/22 23:42:20 BGP: 212.72.45.145 went from Idle to Connect
2009/09/22 23:42:20 BGP: 212.72.45.145 [Event] Connect start to 212.72.45.145 fd 12
2009/09/22 23:42:20 BGP: 212.72.45.145 went from Connect to OpenSent
2009/09/22 23:42:20 BGP: 212.72.45.145 sending OPEN, version 4, my as 10753, holdtime 180, id 213.19.134.2
2009/09/22 23:42:20 BGP: 212.72.45.145 send message type 1, length (incl. header) 45
2009/09/22 23:42:20 BGP: 212.72.45.145 rcv message type 1, length (excl. header) 26
2009/09/22 23:42:20 BGP: 212.72.45.145 rcv OPEN, version 4, remote-as 3356, holdtime 180, id 4.68.0.173
2009/09/22 23:42:20 BGP: 212.72.45.145 rcv OPEN w/ OPTION parameter len: 16
2009/09/22 23:42:20 BGP: 212.72.45.145 rcvd OPEN w/ optional parameter type 2 (Capability) len 6
2009/09/22 23:42:20 BGP: 212.72.45.145 OPEN has CAPABILITY code: 1, length 4
2009/09/22 23:42:20 BGP: 212.72.45.145 OPEN has MP_EXT CAP for afi/safi: 1/1
2009/09/22 23:42:20 BGP: 212.72.45.145 rcvd OPEN w/ optional parameter type 2 (Capability) len 2
2009/09/22 23:42:20 BGP: 212.72.45.145 OPEN has CAPABILITY code: 128, length 0
2009/09/22 23:42:20 BGP: 212.72.45.145 OPEN has ROUTE-REFRESH capability(old) for all address-families
2009/09/22 23:42:20 BGP: 212.72.45.145 rcvd OPEN w/ optional parameter type 2 (Capability) len 2
2009/09/22 23:42:20 BGP: 212.72.45.145 OPEN has CAPABILITY code: 2, length 0
2009/09/22 23:42:20 BGP: 212.72.45.145 OPEN has ROUTE-REFRESH capability(new) for all address-families
2009/09/22 23:42:20 BGP: 212.72.45.145 went from OpenSent to OpenConfirm
2009/09/22 23:42:20 BGP: 212.72.45.145 send message type 4, length (incl. header) 19
2009/09/22 23:42:20 BGP: 212.72.45.145 rcv message type 4, length (excl. header) 0
2009/09/22 23:42:20 BGP: 212.72.45.145 went from OpenConfirm to Established
2009/09/22 23:42:20 BGP: %ADJCHANGE: neighbor 212.72.45.145 Up
2009/09/22 23:42:20 BGP: 212.72.45.145 send message type 4, length (incl. header) 19
2009/09/22 23:42:20 BGP: 212.72.45.145 send UPDATE 212.72.36.0/23
2009/09/22 23:42:20 BGP: 212.72.45.145 send UPDATE 213.19.178.0/24
2009/09/22 23:42:20 BGP: 212.72.45.145 send UPDATE 213.19.176.0/23
2009/09/22 23:42:20 BGP: 212.72.45.145 send UPDATE 213.19.167.0/24
2009/09/22 23:42:20 BGP: 212.72.45.145 send UPDATE 213.19.134.0/24
2009/09/22 23:42:21 BGP: 212.72.45.145 rcvd UPDATE w/ attr: nexthop 212.72.45.145, origin i, path 3356
2009/09/22 23:42:21 BGP: 212.72.45.145 rcvd 0.0.0.0/0
2009/09/22 23:42:22 BGP: Performing BGP general scanning
2009/09/22 23:42:23 BGP: 213.19.134.1 send UPDATE 0.0.0.0/0
2009/09/22 23:42:24 BGP: 212.72.45.145 rcv message type 4, length (excl. header) 0
2009/09/22 23:42:24 BGP: 212.72.45.145 rcv message type 4, length (excl. header) 0
2009/09/22 23:43:05 BGP: 213.19.134.1 rcv message type 4, length (excl. header) 0
2009/09/22 23:43:05 BGP: 213.19.134.1 send message type 4, length (incl. header) 19
2009/09/22 23:43:20 BGP: 212.72.45.145 send message type 4, length (incl. header) 19
2009/09/22 23:43:20 BGP: 212.72.45.145 rcv message type 4, length (excl. header) 0


Blijf bij mijn conclusie dat de de 0.0.0.0/0 gewoon niet verstuurd wordt door onze provider.
Morgen nog maar eens proberen of ik iemand te pakken kan krijgen bij de supportdesk en anders ga ik het maar eens via de accountmanager spelen.

https://www.strava.com/athletes/2323035

woensdag 23 september 2009 02:04

Acties:
  • Kabouterplop01
  • Registratie: Maart 2002
  • Laatst online: 18:40

Kabouterplop01

chown -R me base:all

ik weet het niet zeker, maar het lijkt op een fout in de juniper config:
code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14

chsmith@edge3.ams1> show configuration | display set | grep 212.72.44.82
set routing-options static route 212.72.44.80/30 next-hop 212.72.44.82
set protocols bgp group peer-212.72.44.82 type external
set protocols bgp group peer-212.72.44.82 description "81699-00001::Uplink for EXPLAINER DC"
set protocols bgp group peer-212.72.44.82 import peer-212.72.44.82
set protocols bgp group peer-212.72.44.82 import customer
set protocols bgp group peer-212.72.44.82 import bb2
set protocols bgp group peer-212.72.44.82 family inet any prefix-limit maximum 110
set protocols bgp group peer-212.72.44.82 family inet any prefix-limit teardown 90
set protocols bgp group peer-212.72.44.82 export none
set protocols bgp group peer-212.72.44.82 export send-default
set protocols bgp group peer-212.72.44.82 remove-private
set protocols bgp group peer-212.72.44.82 peer-as 10753
set protocols bgp group peer-212.72.44.82 neighbor 212.72.44.82


moet volgens mij zijn:


chsmith@edge3.ams1> show configuration | display set | grep 212.72.44.82
set routing-options static route 212.72.44.80/30 next-hop 212.72.44.82
set protocols bgp group peer-212.72.44.82 type external
set protocols bgp group peer-212.72.44.82 description "81699-00001::Uplink for EXPLAINER DC"
set protocols bgp group peer-212.72.44.82 import peer-212.72.44.82
set protocols bgp group peer-212.72.44.82 import customer
set protocols bgp group peer-212.72.44.82 import bb2
set protocols bgp group peer-212.72.44.82 family inet any prefix-limit maximum 110
set protocols bgp group peer-212.72.44.82 family inet any prefix-limit teardown 90
set protocols bgp group peer-212.72.44.82 export send-default
set protocols bgp group peer-212.72.44.82 export none
set protocols bgp group peer-212.72.44.82 remove-private
set protocols bgp group peer-212.72.44.82 peer-as 10753
set protocols bgp group peer-212.72.44.82 neighbor 212.72.44.82

net als bij cisco moet de permit voor de deny komen:

woensdag 23 september 2009 12:49

Acties:
  • DDX
  • Registratie: April 2001
  • Laatst online: 21:26

DDX

Topicstarter
Hmms klinkt heel logisch, heb de opmerking doorgestuurd en die hebben het weer doorgestuurd naar het bgp team...

https://www.strava.com/athletes/2323035

woensdag 23 september 2009 13:38

Acties:
  • DDX
  • Registratie: April 2001
  • Laatst online: 21:26

DDX

Topicstarter
En dat was dus de oorzaak, ze hebben het omgewisseld en werken weer :)

code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21

corrected:

[edit protocols bgp group peer-212.72.44.82]
wsmith@edge3.ams1# show
type external;
description "81699-00001::Uplink for EXPLAINER DC";
import [ peer-212.72.44.82 customer bb2 ];
family inet {
    any {
        prefix-limit {
            maximum 110;
            teardown 90;
        }
    }
}
export [ send-default none ];
remove-private;
peer-as 10753;
neighbor 212.72.44.82;

[edit protocols bgp group peer-212.72.44.82]

https://www.strava.com/athletes/2323035

woensdag 23 september 2009 14:15

Acties:
  • Kabouterplop01
  • Registratie: Maart 2002
  • Laatst online: 18:40

Kabouterplop01

chown -R me base:all

was mijn cursus niet voor niets :*)

donderdag 24 september 2009 11:29

Acties:
  • Flyduck
  • Registratie: Juni 2001
  • Laatst online: 28-03-2025

Flyduck

Kabouterplop01 schreef op woensdag 23 september 2009 @ 14:15:
was mijn cursus niet voor niets :*)
Goed gezien !

Zijn er mensen die deze regel lezen? Graag terugkoppeling gewenst (onopvallend)

Pagina: 1
Reageer

Apple iPhone 17 LG OLED evo G5 Google Pixel 10 Samsung Galaxy S25 Star Wars: Outlaws Nintendo Switch 2 Apple AirPods Pro (2e generatie) Sony PlayStation 5 Pro

Tweakers is onderdeel van DPG Media B.V.
Alle rechten voorbehouden - Auteursrecht © 1998 - 2026 • Hosting door TrueFullstaq