Quantcast
Channel: All Routing posts
Viewing all articles
Browse latest Browse all 8688

Re: FBF, "then next-interface" action, forwards traffic with dynamic IGP on interface vs blackholes traffic with static routes

$
0
0

next-ip statement worked from the beginning.

The question is why next-interface works only when IGP is present on interface. 

 

Regarding configs, route with preference 25 is from another setup. 

 

current setup without adding rins1-import (so the interface is isolated in rins1)

testuser@mx01> show route

inet.0: 8 destinations, 8 routes (8 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

0.0.0.0/0          *[Static/5] 2w6d 19:10:15
                    > to 10.128.64.1 via fxp0.0
1.1.1.0/24         *[Direct/0] 00:00:14> via ge-0/2/0.0
1.1.1.1/32         *[Local/0] 00:00:14
                      Local via ge-0/2/0.0
2.2.2.0/30         *[Direct/0] 00:00:14> via ge-0/3/0.0
2.2.2.1/32         *[Local/0] 00:00:14
                      Local via ge-0/3/0.0
10.128.64.0/24     *[Direct/0] 2w6d 19:10:15> via fxp0.0
10.128.64.15/32    *[Local/0] 2w6d 19:10:15
                      Local via fxp0.0
66.66.66.66/32     *[Static/5] 00:00:14> to 2.2.2.2 via ge-0/3/0.0

rins1.inet.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

3.3.3.0/30         *[Direct/0] 00:00:14
                    > via ge-0/2/1.0
3.3.3.1/32         *[Local/0] 00:00:14
                      Local via ge-0/2/1.0
66.66.66.66/32     *[Static/5] 00:00:14> to 3.3.3.2 via ge-0/2/1.0

after adding rins1-import interface appears both in inet.0 and rins1.inet.0

testuser@mx01> show route

inet.0: 10 destinations, 11 routes (10 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

0.0.0.0/0          *[Static/5] 2w6d 19:08:05
                    > to 10.128.64.1 via fxp0.0
1.1.1.0/24         *[Direct/0] 00:04:01> via ge-0/2/0.0
1.1.1.1/32         *[Local/0] 00:04:01
                      Local via ge-0/2/0.0
2.2.2.0/30         *[Direct/0] 00:04:01> via ge-0/3/0.0
2.2.2.1/32         *[Local/0] 00:04:01
                      Local via ge-0/3/0.0
3.3.3.0/30         *[Direct/0] 00:04:01> via ge-0/2/1.0
3.3.3.1/32         *[Local/0] 00:04:01
                      Local via ge-0/2/1.0
10.128.64.0/24     *[Direct/0] 2w6d 19:08:05> via fxp0.0
10.128.64.15/32    *[Local/0] 2w6d 19:08:05
                      Local via fxp0.0
66.66.66.66/32     *[Static/5] 00:04:01> to 2.2.2.2 via ge-0/3/0.0
                    [Static/5] 00:04:01> to 3.3.3.2 via ge-0/2/1.0

rins1.inet.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

3.3.3.0/30         *[Direct/0] 00:04:01
                    > via ge-0/2/1.0
3.3.3.1/32         *[Local/0] 00:04:01
                      Local via ge-0/2/1.0
66.66.66.66/32     *[Static/5] 00:04:01> to 3.3.3.2 via ge-0/2/1.0

Unfotunatly, in both cases traffic matching ff with next-interface action is still blackholed. 

 


Viewing all articles
Browse latest Browse all 8688

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>