♥ 0 |
Hello, We have a BGP peer with a Cisco device, i need to deploy a L3VPN scenario, the configurations seems very straight forward but for some reason we’re not able to ping from a VRF. We have all the routes coming from our BGP peer to that VRF and we have our Loopback IP add announced to our BGP Peer. When i try to ping it shows the following error ARISTAPPASBR01#ping vrf MGMT 192.168.222.151 source 192.168.222.168 PING 192.168.222.151 (192.168.222.151) from 192.168.222.168 : 72(100) bytes of data. ping: sendmsg: Invalid argument ping: sendmsg: Invalid argument ping: sendmsg: Invalid argument ping: sendmsg: Invalid argument ping: sendmsg: Invalid argument --- 192.168.222.151 ping statistics --- 5 packets transmitted, 0 received, 100% packet loss, time 40ms Also we’ve tried that configuration on a virtual lab using vEOS and the result is the same between Cisco and Arista as well as two Arista devices, . We have a working environment with Cisco devices right now and i have tested the same between Mikrotik and Cisco and it works fine.
This is the current configuration we have on the Arista Switch DCS-7280SR2A-48YC6
-----------INTERFACES--------- interface Loopback222 vrf forwarding MGMT ip address 192.168.222.168/32 --------BGP CONFIG------------ ARISTAPPASBR01#sh run | sec bgp router bgp 264750 router-id 172.30.0.18 no bgp default ipv4-unicast neighbor 172.30.0.1 remote-as 264750 neighbor 172.30.0.1 update-source Loopback0 neighbor 172.30.0.1 send-community standard extended neighbor 172.30.0.1 maximum-routes 12000 ! address-family vpn-ipv4 neighbor 172.30.0.1 activate neighbor default encapsulation mpls next-hop-self source-interface Loopback0 ! vrf MGMT rd 172.30.0.18:22 route-target import vpn-ipv4 264750:22 route-target export vpn-ipv4 264750:22 redistribute connected -----------VRF MGMT---------------- VRF: MGMT B I 192.168.222.151/32 [200/0] via 172.30.0.1/32, LDP tunnel index 7, label 30 via 172.20.0.253, Ethernet45, label imp-null(3) |
Post your Answer
You must be logged in to post an answer.