[FROG] ipv6 network statement
Trey Aspelund
t.k.aspelund at gmail.com
Fri Sep 13 02:59:17 UTC 2024
You need to use "match ipv6 address" to reference an ipv6 ACL or
prefix-list in a route-map. It looks like you're using "match ip address"
in the route-map named transit-out6.
- Trey
On Thu, Sep 12, 2024, 20:35 Randy Bush <randy at psg.com> wrote:
> i assume i have a conf error, but can not see it
>
> no prefix is being advertised to ipv6 peer 2001:550:2:1::22 yet a
> similar template advertises one in v4
>
> r1# show bgp summary
>
> IPv4 Unicast Summary:
> BGP router identifier 198.180.150.121, local AS number 3927 VRF
> default vrf-id 0
> BGP table version 1201106
> RIB entries 1736966, using 212 MiB of memory
> Peers 2, using 48 KiB of memory
>
> Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ
> Up/Down State/PfxRcd PfxSnt Desc
> 38.88.248.236 4 174 166936 99 1201106 0 0
> 01:36:00 940141 1 N/A
> 192.168.254.10 4 3927 121068 151229 1201106 0 0
> 01:18:23 634041 753625 N/A
>
> Total number of neighbors 2
>
> IPv6 Unicast Summary:
> BGP router identifier 198.180.150.121, local AS number 3927 VRF
> default vrf-id 0
> BGP table version 304315
> RIB entries 381204, using 47 MiB of memory
> Peers 2, using 48 KiB of memory
>
> Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ
> Up/Down State/PfxRcd PfxSnt Desc
> 2001:550:2:1::22 4 174 66286 98 304315 0 0
> 01:35:55 192933 0 N/A
> fc00::10 4 3927 66566 55345 304315 0 0
> 01:28:16 153136 131291 N/A
>
> Total number of neighbors 2
>
> and it admits it
>
> r1# show ip bgp neighbors 38.88.248.236 advertised-routes
> BGP table version is 1231961, local router ID is 198.180.150.121, vrf
> id 0
> Default local pref 100, local AS 3927
> Status codes: s suppressed, d damped, h history, u unsorted, * valid,
> > best, = multipath,
> i internal, r RIB-failure, S Stale, R Removed
> Nexthop codes: @NNN nexthop's vrf id, < announce-nh-self
> Origin codes: i - IGP, e - EGP, ? - incomplete
> RPKI validation codes: V valid, I invalid, N Not found
>
> Network Next Hop Metric LocPrf Weight Path
> *> 198.180.150.0/24 0.0.0.0 0 32768 i
>
> Total number of prefixes 1
>
> vs
>
> r1# show bgp neighbors 2001:550:2:1::22 advertised-routes
> r1#
>
> [ aside: the cli asymmetry between ipv4 and ipv6 is unkind. ]
>
> config snippets
>
> ip prefix-list export4 seq 5 permit 198.180.150.0/24
> ipv6 prefix-list export6 seq 5 permit 2001:418:8006::/48
> ...
> address-family ipv4 unicast
> network 198.180.150.0/24
> neighbor 38.88.248.236 activate
> neighbor 38.88.248.236 route-map accept-all in
> neighbor 38.88.248.236 route-map transit-out4 out
> neighbor 192.168.254.10 activate
> exit-address-family
> !
> address-family ipv6 unicast
> network 2001:418:8006::/48
> neighbor 2001:550:2:1::22 activate
> neighbor 2001:550:2:1::22 route-map accept-all in
> neighbor 2001:550:2:1::22 route-map transit-out6 out
> neighbor fc00::10 activate
> exit-address-family
> ...
> route-map transit-out4 permit 20
> match ip address prefix-list export4
> exit
> ...
> route-map transit-out6 permit 20
> match ip address prefix-list export6
> exit
>
> note that only the 2001:418:8006::/64 is on the LAN interface not the
> /48
>
> r1# show ipv6 route 2001:418:8006::/64
> Routing entry for 2001:418:8006::/64
> Known via "connected", distance 0, metric 0, best
> Last update 01:52:13 ago
> * directly connected, eno3
>
> r1# show ipv6 route 2001:418:8006::/48
> % Network not in table
>
> similarly 198.180.150.0/24 is not on the LAN, it's a /25 LAN (don't ask)
>
> r1# show ip route 198.180.150.0/25
> Routing entry for 198.180.150.0/25
> Known via "isis", distance 115, metric 12
> Last update 01:52:33 ago
> 198.180.150.120, via eno3 inactive, weight 1
>
> Routing entry for 198.180.150.0/25
> Known via "connected", distance 0, metric 0, best
> Last update 01:53:02 ago
> * directly connected, eno3
>
> r1# show ip route 198.180.150.0/24
> % Network not in table
>
> but it is in bgp
>
> r1# show ip bgp 198.180.150.0/24
> BGP routing table entry for 198.180.150.0/24, version 1
> Paths: (2 available, best #1, table default)
> Advertised to non peer-group peers:
> 38.88.248.236 192.168.254.10
> Local
> 0.0.0.0 from 0.0.0.0 (198.180.150.121)
> Origin IGP, metric 0, weight 32768, valid, sourced, local, best
> (Weight)
> Last update: Thu Sep 12 21:44:49 2024
> Local
> 192.168.254.10 (metric 11) from 192.168.254.10 (192.168.254.10)
> Origin IGP, localpref 100, valid, internal
> Last update: Thu Sep 12 22:13:15 2024
>
> r1# show bgp 2001:418:8006::/48
> BGP routing table entry for 2001:418:8006::/48, version 1
> Paths: (1 available, best #1, table default)
> Advertised to non peer-group peers:
> fc00::10
> Local
> :: from :: (198.180.150.121)
> Origin IGP, metric 0, weight 32768, valid, sourced, local, best
> (First path received)
> Last update: Thu Sep 12 21:44:50 2024
>
> is it that 198.180.150.0/25 is heard via is-is and ibgp and
> 2001:418:8006::/64 is not?
>
> and for sure 174 is hearing the announcement of the 198.180.150.0/24.
> from route-views
>
> BGP routing table entry for 198.180.150.0/24, version 322874892
> Paths: (19 available, best #18, table default)
> Not advertised to any peer
> Refresh Epoch 1
> 3257 174 3927
>
> randy
>
> _______________________________________________
> frog mailing list
> frog at lists.frrouting.org
> https://lists.frrouting.org/listinfo/frog
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.frrouting.org/pipermail/frog/attachments/20240912/1bb0ed4c/attachment.htm>
More information about the frog
mailing list