You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Route map actually prohibits machine -> machine connection due to:
Feb 01 14:24:07 vagrant-leaf01 bgpd[4433]: swp1 rcvd UPDATE about ::/0 IPv6 unicast -- DENIED due to: route-map;
Feb 01 14:24:07 vagrant-leaf01 bgpd[4433]: swp1 rcvd UPDATE w/ attr: , origin ?, mp_nexthop fe80::204:ff:fe11:1101(fe80::204:ff:fe11:1101)(fe80::204:ff:fe11:1101), metric 0, path 4210000030
Feb 01 14:24:07 vagrant-leaf01 bgpd[4433]: swp1 rcvd UPDATE wlen 0 attrlen 79 alen 0
Feb 01 14:24:07 vagrant-leaf01 bgpd[4433]: swp1 rcvd UPDATE about 2002::3/128 IPv6 unicast -- DENIED due to: route-map;
ip prefix-list vrf30-in-prefixes seq 10 permit 10.0.0.1/32 le 32
ip prefix-list vrf30-in-prefixes seq 11 permit 10.0.4.1/32 le 32
ip prefix-list vrf30-in-prefixes seq 12 permit 2002::/64 le 32 <-- wrong bitlength
ip prefix-list vrf30-in-prefixes seq 13 permit 10.244.0.0/16 le 32
Turns out the match expression differs between ip and ipv6, with this route-map it works:
!
address-family ipv4 unicast
redistribute connected
neighbor MACHINE maximum-prefix 24000
neighbor MACHINE route-map vrf30-in in
exit-address-family
!
address-family ipv6 unicast
redistribute connected
neighbor MACHINE maximum-prefix 24000
neighbor MACHINE route-map vrf30-in6 in
neighbor MACHINE activate
exit-address-family
!
address-family l2vpn evpn
advertise ipv4 unicast
advertise ipv6 unicast
exit-address-family
!
ip prefix-list vrf30-in6-prefixes seq 12 permit 2002::/64 le 128
route-map vrf30-in6 permit 10
match ipv6 address prefix-list vrf30-in6-prefixes <-- match ipv6
!
# route-maps for vrf30
ip prefix-list vrf30-in-prefixes seq 10 permit 10.0.0.1/32 le 32
ip prefix-list vrf30-in-prefixes seq 11 permit 10.0.4.1/32 le 32
ip prefix-list vrf30-in-prefixes seq 13 permit 10.244.0.0/16 le 32
route-map vrf30-in permit 10
match ip address prefix-list vrf30-in-prefixes
The text was updated successfully, but these errors were encountered:
Route map actually prohibits machine -> machine connection due to:
ip prefix-list vrf30-in-prefixes seq 10 permit 10.0.0.1/32 le 32
ip prefix-list vrf30-in-prefixes seq 11 permit 10.0.4.1/32 le 32
ip prefix-list vrf30-in-prefixes seq 12 permit 2002::/64 le 32 <-- wrong bitlength
ip prefix-list vrf30-in-prefixes seq 13 permit 10.244.0.0/16 le 32
Turns out the match expression differs between ip and ipv6, with this route-map it works:
The text was updated successfully, but these errors were encountered: