[j-nsp] can i see bgp looped AS PATH prefixes on the receiving router

[Aaron Gould]

I'm able to use traceoptions to see prefixes that have an AS PATH with a
looped AS, but Is there a way to see these prefixes that are being rcv'd as
loop detected with a cli show command ?



Jun 16 11:41:25.766030 BGP RECV 10.0.2.9+53391 -> 10.0.2.10+179

Jun 16 11:41:25.766076 BGP RECV message type 2 (Update) length 69

Jun 16 11:41:25.766097 BGP RECV Update PDU length 69

Jun 16 11:41:25.766120 BGP RECV flags 0x40 code Origin(1): IGP

Jun 16 11:41:25.766152 BGP RECV flags 0x40 code ASPath(2) length 10: (65001
65000)

Jun 16 11:41:25.766179 BGP RECV flags 0x40 code NextHop(3): 10.0.6.1

Jun 16 11:41:25.766200 BGP RECV flags 0x40 code LocalPref(5): 101

Jun 16 11:41:25.766222 BGP RECV flags 0xc0 code Communities(8): 65535:65281

Jun 16 11:41:25.766539 BGP RECV 192.168.10.0/24 , 192.168.100.0/24



Jun 16 11:41:25.766640 As loop detected. Rejecting update



Jun 16 11:41:25.766700 bgp_rcv_nlri: 192.168.10.0/24

Jun 16 11:41:25.766733 bgp_rcv_nlri: Uninstalling 192.168.10.0/24: route
entry not found

Jun 16 11:41:25.766759 bgp_rcv_nlri: 192.168.100.0/24

Jun 16 11:41:25.766788 bgp_rcv_nlri: Uninstalling 192.168.100.0/24: route
entry not found

Jun 16 11:41:25.766828

Jun 16 11:41:25.766828 BGP RECV 10.0.2.9+53391 -> 10.0.2.10+179

Jun 16 11:41:25.766862 BGP RECV message type 2 (Update) length 58

Jun 16 11:41:25.766882 BGP RECV Update PDU length 58

Jun 16 11:41:25.766904 BGP RECV flags 0x40 code Origin(1): IGP

Jun 16 11:41:25.766933 BGP RECV flags 0x40 code ASPath(2) length 10: (65001
65000)

Jun 16 11:41:25.766959 BGP RECV flags 0x40 code NextHop(3): 10.0.2.2

Jun 16 11:41:25.766979 BGP RECV flags 0x40 code LocalPref(5): 100

Jun 16 11:41:25.767007 BGP RECV 192.168.30.0/24



Jun 16 11:41:25.767042 As loop detected. Rejecting update



Jun 16 11:41:25.767081 bgp_rcv_nlri: 192.168.30.0/24

Jun 16 11:41:25.767109 bgp_rcv_nlri: Uninstalling 192.168.30.0/24: route
entry not found

Jun 16 11:41:25.767144

Jun 16 11:41:25.767144 BGP RECV 10.0.2.9+53391 -> 10.0.2.10+179

Jun 16 11:41:25.767177 BGP RECV message type 2 (Update) length 23

Jun 16 11:41:25.767197 BGP RECV End of RIB: AFI 1 SAFI 1

Jun 16 11:41:25.767236 rt_close: 4 routes proto BGP_65001.10.0.2.9+53391

Jun 16 11:41:25.767236

Jun 16 11:41:25.767278 bgp_read_v4_message: done with 10.0.2.9 (External AS
65001) received 258 octets 5 updates 5 routes

Jun 16 11:41:25.767533 bgp_flash_cb: rtt (null)(0x2a5c000) rib=0 flash
type=1 cb target=group my-cbgp type External

Jun 16 11:41:25.768970 bgp_flash_cb: rtt (null)(0x2a5c000) rib=0 flash
type=1 cb target=group my-cbgp type External



- Aaron Gould

_______________________________________________
juniper-nsp mailing list juniper-***@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

[Aaron Gould]

Nothing hidden.





[edit]

***@lab-mx104:r4# run show route receive-protocol bgp 10.0.2.9



inet.0: 33 destinations, 33 routes (33 active, 0 holddown, 0 hidden)

Prefix Nexthop MED Lclpref AS path

* 192.168.50.0/24 10.0.2.9 100 (65001) I

* 192.168.60.0/24 10.0.9.6 100 (65001) I

* 192.168.70.0/24 10.0.9.7 100 (65001) I



[edit]

***@lab-mx104:r4# run show route receive-protocol bgp 10.0.2.9 hidden



inet.0: 33 destinations, 33 routes (33 active, 0 holddown, 0 hidden)



[edit]

***@lab-mx104:r4# run show route hidden



inet.0: 33 destinations, 33 routes (33 active, 0 holddown, 0 hidden)



- Aaron Gould





From: Tomasz Mikołajek [mailto:***@gmail.com]
Sent: Friday, June 16, 2017 7:17 AM
To: Aaron Gould <***@gvtc.com>
Subject: Re: [j-nsp] can i see bgp looped AS PATH prefixes on the receiving router



Hello.

Trzy Show route hidden



_______________________________________________
juniper-nsp mailing list juniper-***@puck.nether.net
https://puck.net

[Shamen Snyder]

Looped as-path routes should show up as hidden. Do you have *bgp keep none *
configured?

Post by Aaron Gould
Nothing hidden.
[edit]
inet.0: 33 destinations, 33 routes (33 active, 0 holddown, 0 hidden)
Prefix Nexthop MED Lclpref AS path
* 192.168.50.0/24 10.0.2.9 100 (65001) I
* 192.168.60.0/24 10.0.9.6 100 (65001) I
* 192.168.70.0/24 10.0.9.7 100 (65001) I
[edit]
inet.0: 33 destinations, 33 routes (33 active, 0 holddown, 0 hidden)
[edit]
inet.0: 33 destinations, 33 routes (33 active, 0 holddown, 0 hidden)
- Aaron Gould
Sent: Friday, June 16, 2017 7:17 AM
Subject: Re: [j-nsp] can i see bgp looped AS PATH prefixes on the receiving router
Hello.
Trzy Show route hidden
_______________________________________________
https://puck.nether.net/mailman/listinfo/juniper-nsp

_______________________________________________
juniper-nsp mailing list juniper-***@puck.nether.net
https://puck.n

[Aaron Gould]

I wonder if confederations are creating the difference with what y’all are expecting to see ? In other words, perhaps confederations don’t show loop AS’s as hidden. Just guessing as I learn…



Here’s both sides, of what is sent from r5 and what is received on r4 ?



[edit]

***@lab-mx104:r4# show protocols bgp group my-cbgp | display set

set logical-systems r4 protocols bgp group my-cbgp type external

set logical-systems r4 protocols bgp group my-cbgp traceoptions file r4-cgp

set logical-systems r4 protocols bgp group my-cbgp traceoptions flag state detail

set logical-systems r4 protocols bgp group my-cbgp traceoptions flag route detail

set logical-systems r4 protocols bgp group my-cbgp traceoptions flag update detail

set logical-systems r4 protocols bgp group my-cbgp export my-ibgp

set logical-systems r4 protocols bgp group my-cbgp neighbor 10.0.2.9 peer-as 65001



[edit]

***@lab-mx104:r4# run show route receive-protocol bgp 10.0.2.9



inet.0: 35 destinations, 39 routes (35 active, 0 holddown, 0 hidden)

Prefix Nexthop MED Lclpref AS path

* 192.168.50.0/24 10.0.2.9 100 (65001) I

192.168.60.0/24 10.0.9.6 100 (65001) I

192.168.70.0/24 10.0.9.7 100 (65001) I



[edit]







[edit]

***@lab-mx104:r5# show protocols bgp group my-cbgp | display set

set logical-systems r5 protocols bgp group my-cbgp type external

set logical-systems r5 protocols bgp group my-cbgp export my-ibgp

set logical-systems r5 protocols bgp group my-cbgp neighbor 10.0.2.2 peer-as 65000

set logical-systems r5 protocols bgp group my-cbgp neighbor 10.0.2.10 peer-as 65000



[edit]

***@lab-mx104:r5# run show route advertising-protocol bgp 10.0.2.10



inet.0: 38 destinations, 43 routes (38 active, 0 holddown, 0 hidden)

Prefix Nexthop MED Lclpref AS path

* 192.168.10.0/24 10.0.6.1 101 (65000) I

* 192.168.20.0/24 10.0.6.2 100 (65000) I

* 192.168.30.0/24 10.0.2.2 100 (65000) I

* 192.168.50.0/24 Self 100 I

* 192.168.60.0/24 10.0.9.6 100 I

* 192.168.70.0/24 10.0.9.7 100 I

* 192.168.100.0/24 10.0.6.1 101 (65000) I





_______________________________________________
juniper-nsp mailing list juniper-***@puck.nether.net
https://puck.nether.net/m

[Shamen Snyder]

Originally you did need bgp keep all to see routes that failed as-path loop
checks. I thought that changed in one of the version releases however, that
doesn't appear to be the case. Its the same on eBGP and cBGP. You need keep
all to see it.

I did this from 12.1.


***@mpr0.rdu.lab# run show route hidden extensive

inet.0: 17 destinations, 19 routes (17 active, 0 holddown, 2 hidden)
1.1.1.0/24 (3 entries, 1 announced)
TSI:
KRT in-kernel 1.1.1.0/24 -> {}
Page 0 idx 0 Type 1 val 9365148
Nexthop: Self
Localpref: 100
AS path: [65000] I
Communities:
Path 1.1.1.0 Vector len 4. Val: 0
BGP
Next hop type: Unusable
Address: 0x8f28f64
Next-hop reference count: 4
State: <Hidden Int Ext>
Inactive reason: Unusable path
Local AS: 65000 Peer AS: 65002
Age: 1:00
Task: BGP_65002.10.10.10.5+179
AS path: (65002 65000) I (Looped: 65000)
Router ID: 10.0.0.2
Indirect next hops: 1
Protocol next hop: 10.10.10.4
Indirect next hop: 0 -
Indirect path forwarding next hops: 0
Next hop type: Unusable

Post by Aaron Gould
I wonder if confederations are creating the difference with what y’all are
expecting to see ? In other words, perhaps confederations don’t show loop
AS’s as hidden. Just guessing as I learn…
Here’s both sides, of what is sent from r5 and what is received on r4 ?
[edit]
set logical-systems r4 protocols bgp group my-cbgp type external
set logical-systems r4 protocols bgp group my-cbgp traceoptions file r4-cgp
set logical-systems r4 protocols bgp group my-cbgp traceoptions flag state detail
set logical-systems r4 protocols bgp group my-cbgp traceoptions flag route detail
set logical-systems r4 protocols bgp group my-cbgp traceoptions flag update detail
set logical-systems r4 protocols bgp group my-cbgp export my-ibgp
set logical-systems r4 protocols bgp group my-cbgp neighbor 10.0.2.9 peer-as 65001
[edit]
inet.0: 35 destinations, 39 routes (35 active, 0 holddown, 0 hidden)
Prefix Nexthop MED Lclpref AS path
* 192.168.50.0/24 10.0.2.9 100 (65001) I
192.168.60.0/24 10.0.9.6 100 (65001) I
192.168.70.0/24 10.0.9.7 100 (65001) I
[edit]
[edit]
set logical-systems r5 protocols bgp group my-cbgp type external
set logical-systems r5 protocols bgp group my-cbgp export my-ibgp
set logical-systems r5 protocols bgp group my-cbgp neighbor 10.0.2.2 peer-as 65000
set logical-systems r5 protocols bgp group my-cbgp neighbor 10.0.2.10 peer-as 65000
[edit]
inet.0: 38 destinations, 43 routes (38 active, 0 holddown, 0 hidden)
Prefix Nexthop MED Lclpref AS path
* 192.168.10.0/24 10.0.6.1 101 (65000) I
* 192.168.20.0/24 10.0.6.2 100 (65000) I
* 192.168.30.0/24 10.0.2.2 100 (65000) I
* 192.168.50.0/24 Self 100 I
* 192.168.60.0/24 10.0.9.6 100 I
* 192.168.70.0/24 10.0.9.7 100 I
* 192.168.100.0/24 10.0.6.1 101 (65000) I

_______________________________________________
juniper-nsp mailing list juniper-***@puck.nether.net
https://puck.nether.net/mailman/listinfo/juni

[Aaron Gould]

Here’s what happened when I added “loops 1” …it seemed to just allow those previously loop-detected prefixes, to now be allowed into the rib. True ? is this safe ? I mean isn’t this what AS PATH loop detection is supposed to prevent. Then again, maybe if you know a good reason to do this, then I guess you just have to be careful and know what you’re going huh



****** before…



[edit]

***@lab-mx104:r4# run show route receive-protocol bgp 10.0.2.9



inet.0: 35 destinations, 39 routes (35 active, 0 holddown, 0 hidden)

Prefix Nexthop MED Lclpref AS path

* 192.168.50.0/24 10.0.2.9 100 (65001) I

192.168.60.0/24 10.0.9.6 100 (65001) I

192.168.70.0/24 10.0.9.7 100 (65001) I



...looking at one of them...



[edit]

***@lab-mx104:r4# run show route protocol bgp 192.168.10.0



inet.0: 35 destinations, 39 routes (35 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both



192.168.10.0/24 *[BGP/170] 08:07:39, localpref 101, from 10.0.6.1

AS path: I, validation-state: unverified

to 10.0.4.10 via lt-0/1/0.42

****** after…



[edit]

***@lab-mx104:r4# set protocols bgp group my-cbgp family inet unicast loops 1



[edit]

***@lab-mx104:r4# run show route receive-protocol bgp 10.0.2.9



inet.0: 35 destinations, 43 routes (35 active, 0 holddown, 0 hidden)

Prefix Nexthop MED Lclpref AS path

* 192.168.10.0/24 10.0.6.1 101 (65001 65000) I

* 192.168.20.0/24 10.0.6.2 100 (65001 65000) I

192.168.30.0/24 10.0.2.2 100 (65001 65000) I

* 192.168.50.0/24 10.0.2.9 100 (65001) I

192.168.60.0/24 10.0.9.6 100 (65001) I

192.168.70.0/24 10.0.9.7 100 (65001) I

* 192.168.100.0/24 10.0.6.1 101 (65001 65000) I



...looking at one of them...



[edit]

***@lab-mx104:r4# run show route protocol bgp 192.168.10.0



inet.0: 35 destinations, 43 routes (35 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both



192.168.10.0/24 *[BGP/170] 00:00:13, localpref 101, from 10.0.2.9

AS path: (65001 65000) I, validation-state: unverified

to 10.0.4.10 via lt-0/1/0.42

[BGP/170] 08:08:35, localpref 101, from 10.0.6.1

AS path: I, validation-state: unverified

to 10.0.4.10 via lt-0/1/0.42

- Aaron Gould

_______________________________________________
juniper-nsp mailing list juniper-***@puck.nether.net
https://puck.neth

[Shamen Snyder]

I've only ever used the *loops* knob for hub and spoke VPNs. There may be
some other use cases, but I'm not aware of them.

Post by Aaron Gould
Here’s what happened when I added “loops 1” …it seemed to just allow
those previously loop-detected prefixes, to now be allowed into the rib.
True ? is this safe ? I mean isn’t this what AS PATH loop detection is
supposed to prevent. Then again, maybe if you know a good reason to do
this, then I guess you just have to be careful and know what you’re going
huh
****** before…
[edit]
inet.0: 35 destinations, 39 routes (35 active, 0 holddown, 0 hidden)
Prefix Nexthop MED Lclpref AS path
* 192.168.50.0/24 10.0.2.9 100 (65001) I
192.168.60.0/24 10.0.9.6 100 (65001) I
192.168.70.0/24 10.0.9.7 100 (65001) I
...looking at one of them...
[edit]
inet.0: 35 destinations, 39 routes (35 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
192.168.10.0/24 *[BGP/170] 08:07:39, localpref 101, from 10.0.6.1
AS path: I, validation-state: unverified

to 10.0.4.10 via lt-0/1/0.42

****** after…
[edit]
[edit]
inet.0: 35 destinations, 43 routes (35 active, 0 holddown, 0 hidden)
Prefix Nexthop MED Lclpref AS path
* 192.168.10.0/24 10.0.6.1 101 (65001 65000) I
* 192.168.20.0/24 10.0.6.2 100 (65001 65000) I
192.168.30.0/24 10.0.2.2 100 (65001 65000) I
* 192.168.50.0/24 10.0.2.9 100 (65001) I
192.168.60.0/24 10.0.9.6 100 (65001) I
192.168.70.0/24 10.0.9.7 100 (65001) I
* 192.168.100.0/24 10.0.6.1 101 (65001 65000) I
...looking at one of them...
[edit]
inet.0: 35 destinations, 43 routes (35 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
192.168.10.0/24 *[BGP/170] 00:00:13, localpref 101, from 10.0.2.9
AS path: (65001 65000) I, validation-state: unverified

to 10.0.4.10 via lt-0/1/0.42

[BGP/170] 08:08:35, localpref 101, from 10.0.6.1
AS path: I, validation-state: unverified

to 10.0.4.10 via lt-0/1/0.42

- Aaron Gould

_______________________________________________
juniper-nsp mailing list juniper-***@puck.nether.net
https://puck.nether.net/mailman/listinfo/

[Aaron Gould]

...looking at traces from previous email about “loops 1”...



***@lab-mx104> monitor list

No monitored files



***@lab-mx104> monitor start /var/log/r4/r4-cbgp



***@lab-mx104>

*** /var/log/r4/r4-cbgp ***

Jun 17 00:38:00.540852 bgp_read_v4_message: receiving packet(s) from 10.0.2.9 (External AS 65001)

Jun 17 00:38:00.540944

Jun 17 00:38:00.540944 BGP RECV 10.0.2.9+62058 -> 10.0.2.10+179

Jun 17 00:38:00.540978 BGP RECV message type 2 (Update) length 27

Jun 17 00:38:00.540998 BGP RECV Unreachable prefix data length 4

Jun 17 00:38:00.542117 BGP RECV 192.168.40.0/24

Jun 17 00:38:00.542181

Jun 17 00:38:00.542181 BGP RECV 10.0.2.9+62058 -> 10.0.2.10+179

Jun 17 00:38:00.542215 BGP RECV message type 2 (Update) length 69

Jun 17 00:38:00.542235 BGP RECV Update PDU length 69

Jun 17 00:38:00.542281 BGP RECV flags 0x40 code Origin(1): IGP

Jun 17 00:38:00.542313 BGP RECV flags 0x40 code ASPath(2) length 10: (65001 65000)

Jun 17 00:38:00.542339 BGP RECV flags 0x40 code NextHop(3): 10.0.6.1

Jun 17 00:38:00.542360 BGP RECV flags 0x40 code LocalPref(5): 101

Jun 17 00:38:00.542381 BGP RECV flags 0xc0 code Communities(8): 65535:65281

Jun 17 00:38:00.542415 BGP RECV 192.168.10.0/24 , 192.168.100.0/24

Jun 17 00:38:00.542506 bgp_rcv_nlri: 192.168.10.0/24

Jun 17 00:38:00.542635 ADD 192.168.10.0/24 nhid 0 BGP pref 170/-102 metric <Hidden Int Ext> as 65001

Jun 17 00:38:00.542771 rt_loser_eval: New is better. Flags: llxllx

Jun 17 00:38:00.542830 CHANGE 192.168.10.0/24 nhid 0 gw 10.0.4.10 BGP pref 170/-102 metric <NotBest Int Ext> as 65000

Jun 17 00:38:00.542878 CHANGE 192.168.10.0/24 nhid 0 gw 10.0.4.10 BGP pref 170/-102 metric <Active Int Ext> as 65001

Jun 17 00:38:00.542933 CHANGE 192.168.10.0/24 nhid 0 gw 10.0.4.10 BGP pref 170/-102 metric <Active Int Ext> as 65001

Jun 17 00:38:00.542984 bgp_rt_add: rt 192.168.10.0/24 { nhid 0x9fff7a48 gw 10.0.4.10 <Active Int Ext> <Accepted> from 10.0.2.9 (External AS65001) } Sync rt add for resolution

Jun 17 00:38:00.543018 bgp_multipath_check: rth 192.168.10.0/24 { nentries 2 ac 0x2aeca80 } Skip calc. multipath, was_mp_active=0, act_is_mp=0

Jun 17 00:38:00.544316 bgp_rt_add: rt 192.168.10.0/24 { nhid 0x9fff7a48 gw 10.0.4.10 <Active Int Ext> <Accepted> from 10.0.2.9 (External AS65001) } Done rt add

Jun 17 00:38:00.544372 bgp_rcv_nlri: 192.168.100.0/24

Jun 17 00:38:00.544480 ADD 192.168.100.0/24 nhid 0 BGP pref 170/-102 metric <Hidden Int Ext> as 65001

Jun 17 00:38:00.544583 rt_loser_eval: New is better. Flags: llxllx

Jun 17 00:38:00.544647 CHANGE 192.168.100.0/24 nhid 0 gw 10.0.4.10 BGP pref 170/-102 metric <NotBest Int Ext> as 65000

Jun 17 00:38:00.544691 CHANGE 192.168.100.0/24 nhid 0 gw 10.0.4.10 BGP pref 170/-102 metric <Active Int Ext> as 65001

Jun 17 00:38:00.544764 CHANGE 192.168.100.0/24 nhid 0 gw 10.0.4.10 BGP pref 170/-102 metric <Active Int Ext> as 65001

Jun 17 00:38:00.544813 bgp_rt_add: rt 192.168.100.0/24 { nhid 0x9fff7a48 gw 10.0.4.10 <Active Int Ext> <Accepted> from 10.0.2.9 (External AS 65001) } Sync rt add for resolution

Jun 17 00:38:00.544846 bgp_multipath_check: rth 192.168.100.0/24 { nentries 3 ac 0x2aecd20 } Skip calc. multipath, was_mp_active=0, act_is_mp=0

Jun 17 00:38:00.544887 bgp_rt_add: rt 192.168.100.0/24 { nhid 0x9fff7a48 gw 10.0.4.10 <Active Int Ext> <Accepted> from 10.0.2.9 (External AS 65001) } Done rt add

Jun 17 00:38:00.544928

Jun 17 00:38:00.544928 BGP RECV 10.0.2.9+62058 -> 10.0.2.10+179

Jun 17 00:38:00.544962 BGP RECV message type 2 (Update) length 54

Jun 17 00:38:00.544982 BGP RECV Update PDU length 54

Jun 17 00:38:00.545004 BGP RECV flags 0x40 code Origin(1): IGP

Jun 17 00:38:00.545032 BGP RECV flags 0x40 code ASPath(2) length 6: (65001)

Jun 17 00:38:00.545057 BGP RECV flags 0x40 code NextHop(3): 10.0.2.9

Jun 17 00:38:00.545078 BGP RECV flags 0x40 code LocalPref(5): 100

Jun 17 00:38:00.545716 BGP RECV 192.168.50.0/24

Jun 17 00:38:00.545793 bgp_rcv_nlri: 192.168.50.0/24

Jun 17 00:38:00.545837 bgp_rcv_nlri: 192.168.50.0/24 duplicate update

Jun 17 00:38:00.545873

Jun 17 00:38:00.545873 BGP RECV 10.0.2.9+62058 -> 10.0.2.10+179

Jun 17 00:38:00.545907 BGP RECV message type 2 (Update) length 65

Jun 17 00:38:00.545926 BGP RECV Update PDU length 65

Jun 17 00:38:00.545947 BGP RECV flags 0x40 code Origin(1): IGP

Jun 17 00:38:00.545977 BGP RECV flags 0x40 code ASPath(2) length 10: (65001 65000)

Jun 17 00:38:00.546002 BGP RECV flags 0x40 code NextHop(3): 10.0.6.2

Jun 17 00:38:00.546023 BGP RECV flags 0x40 code LocalPref(5): 100

Jun 17 00:38:00.546503 BGP RECV flags 0xc0 code Communities(8): 65535:65281

Jun 17 00:38:00.546543 BGP RECV 192.168.20.0/24

Jun 17 00:38:00.546614 bgp_rcv_nlri: 192.168.20.0/24

Jun 17 00:38:00.546715 ADD 192.168.20.0/24 nhid 0 BGP pref 170/-101 metric <Hidden Int Ext> as 65001

Jun 17 00:38:00.546840 rt_loser_eval: New is better. Flags: llxllx

Jun 17 00:38:00.546895 CHANGE 192.168.20.0/24 nhid 0 gw 10.0.4.10 BGP pref 170/-101 metric <NotBest Int Ext> as 65000

Jun 17 00:38:00.546942 CHANGE 192.168.20.0/24 nhid 0 gw 10.0.4.10 BGP pref 170/-101 metric <Active Int Ext> as 65001

Jun 17 00:38:00.546993 CHANGE 192.168.20.0/24 nhid 0 gw 10.0.4.10 BGP pref 170/-101 metric <Active Int Ext> as 65001

Jun 17 00:38:00.547042 bgp_rt_add: rt 192.168.20.0/24 { nhid 0x9fff7a48 gw 10.0.4.10 <Active Int Ext> <Accepted> from 10.0.2.9 (External AS65001) } Sync rt add for resolution

Jun 17 00:38:00.547076 bgp_multipath_check: rth 192.168.20.0/24 { nentries 2 ac 0x2aecad4 } Skip calc. multipath, was_mp_active=0, act_is_mp=0

Jun 17 00:38:00.547226 bgp_rt_add: rt 192.168.20.0/24 { nhid 0x9fff7a48 gw 10.0.4.10 <Active Int Ext> <Accepted> from 10.0.2.9 (External AS65001) } Done rt add

Jun 17 00:38:00.547270

Jun 17 00:38:00.547270 BGP RECV 10.0.2.9+62058 -> 10.0.2.10+179

Jun 17 00:38:00.547303 BGP RECV message type 2 (Update) length 54

Jun 17 00:38:00.547323 BGP RECV Update PDU length 54

Jun 17 00:38:00.547344 BGP RECV flags 0x40 code Origin(1): IGP

Jun 17 00:38:00.547372 BGP RECV flags 0x40 code ASPath(2) length 6: (65001)

Jun 17 00:38:00.547398 BGP RECV flags 0x40 code NextHop(3): 10.0.9.7

Jun 17 00:38:00.547418 BGP RECV flags 0x40 code LocalPref(5): 100

Jun 17 00:38:00.547448 BGP RECV 192.168.70.0/24

Jun 17 00:38:00.547510 bgp_rcv_nlri: 192.168.70.0/24

Jun 17 00:38:00.547552 bgp_rcv_nlri: 192.168.70.0/24 duplicate update

Jun 17 00:38:00.547585

Jun 17 00:38:00.547585 BGP RECV 10.0.2.9+62058 -> 10.0.2.10+179

Jun 17 00:38:00.547624 BGP RECV message type 2 (Update) length 58

Jun 17 00:38:00.547644 BGP RECV Update PDU length 58

Jun 17 00:38:00.547665 BGP RECV flags 0x40 code Origin(1): IGP

Jun 17 00:38:00.547694 BGP RECV flags 0x40 code ASPath(2) length 10: (65001 65000)

Jun 17 00:38:00.547718 BGP RECV flags 0x40 code NextHop(3): 10.0.2.2

Jun 17 00:38:00.547760 BGP RECV flags 0x40 code LocalPref(5): 100

Jun 17 00:38:00.547788 BGP RECV 192.168.30.0/24

Jun 17 00:38:00.547841 bgp_rcv_nlri: 192.168.30.0/24

Jun 17 00:38:00.547922 ADD 192.168.30.0/24 nhid 0 BGP pref 170/-101 metric <Hidden Int Ext> as 65001

Jun 17 00:38:00.548041 rt_loser_eval: Old is better. Flags: llxllx

Jun 17 00:38:00.548189 CHANGE 192.168.30.0/24 nhid 0 gw 10.0.2.9 BGP pref 170/-101 metric <NotBest Int Ext> as 65001

Jun 17 00:38:00.548245 bgp_rt_add: rt 192.168.30.0/24 { nhid 0x9fff7a48 gw 10.0.2.9 <NotBest Int Ext> <Accepted> from 10.0.2.9 (External AS65001) } Sync rt add for resolution

Jun 17 00:38:00.548279 bgp_multipath_check: rth 192.168.30.0/24 { nentries 2 ac 0x2aec984 } Skip calc. multipath, was_mp_active=0, act_is_mp=0

Jun 17 00:38:00.548319 bgp_rt_add: rt 192.168.30.0/24 { nhid 0x9fff7a48 gw 10.0.2.9 <NotBest Int Ext> <Accepted> from 10.0.2.9 (External AS65001) } Done rt add

Jun 17 00:38:00.548358

Jun 17 00:38:00.548358 BGP RECV 10.0.2.9+62058 -> 10.0.2.10+179

Jun 17 00:38:00.548391 BGP RECV message type 2 (Update) length 54

Jun 17 00:38:00.548411 BGP RECV Update PDU length 54

Jun 17 00:38:00.548432 BGP RECV flags 0x40 code Origin(1): IGP

Jun 17 00:38:00.548460 BGP RECV flags 0x40 code ASPath(2) length 6: (65001)

Jun 17 00:38:00.548485 BGP RECV flags 0x40 code NextHop(3): 10.0.9.6

Jun 17 00:38:00.548506 BGP RECV flags 0x40 code LocalPref(5): 100

Jun 17 00:38:00.548535 BGP RECV 192.168.60.0/24

Jun 17 00:38:00.548595 bgp_rcv_nlri: 192.168.60.0/24

Jun 17 00:38:00.548642 bgp_rcv_nlri: 192.168.60.0/24 duplicate update

Jun 17 00:38:00.548679 rt_close: 8 routes proto BGP_65001.10.0.2.9+62058

Jun 17 00:38:00.548679

Jun 17 00:38:00.548723 bgp_read_v4_message: done with 10.0.2.9 (External AS 65001) received 381 octets 7 updates 7 routes

Jun 17 00:38:00.548909 bgp_flash_cb: rtt (null)(0x2a5c000) rib=0 flash type=0 cb target=group my-cbgp type External

Jun 17 00:38:00.549361 bgp_flash_cb: rtt (null)(0x2a5c000) rib=0 flash type=1 cb target=group my-cbgp type External

Jun 17 00:38:00.549606 bgp_send: sending 35 bytes to 10.0.2.9 (External AS 65001)

Jun 17 00:38:00.549648

Jun 17 00:38:00.549648 BGP SEND 10.0.2.10+179 -> 10.0.2.9+62058

Jun 17 00:38:00.549682 BGP SEND message type 2 (Update) length 35

Jun 17 00:38:00.549702 BGP SEND Unreachable prefix data length 12

Jun 17 00:38:00.549744 BGP SEND 192.168.10.0/24 , 192.168.20.0/24 , 192.168.100.0/24

Jun 17 00:38:01.452052 bgp_read_v4_message: receiving packet(s) from 10.0.2.9 (External AS 65001)

Jun 17 00:38:01.452121 bgp_read_v4_message: done with 10.0.2.9 (External AS 65001) received 19 octets 0 updates 0 routes

Jun 17 00:38:09.752733 bgp_hold_timeout: peer 10.0.2.9 (External AS 65001) read-subjob 0x0 last checked 79 last recv'd 8 last sent 9 last keepalive 25

Jun 17 00:38:11.319779 bgp_keepalive_timeout: peer 10.0.2.9 (External AS 65001) last checked 1 last recv'd 9 last sent 10 last keepalive 26





- Aaron Gould

_______________________________________________
juniper-nsp mailing list juniper-***@puck.nether.net
ht