I was just wondering if there are any restriction on running MPLS L3 VPN and VPLS on the same PE ?   Use case would be a corporate network where the core is MPLS and they use L3VPNs to provide segmentation (basically the aggregation L2/L3 boundary is a PE). Now what of they also wanted to provide some multipoint connectivity for "customers" located in the same campus. Customers would be using their own WAN routers etc so this would be equivalent to just giving them some ports on a VLAN with no SVI if this was a flat network. Never tried it so I was curious. Thanks   ... View more

Hi   I have setup a lab with both eBGP and iBGP connections. I am noticing some strange results with iBGP. I am running iBGP between the loopbacks of two routers and do not have "next-hop self" set on the iBGP neighbours but still the routers are changing the next hop of prefixes learned from eBGP to the loopback IP when updating an iBGP neighbour. I have tried with both a 3700 image and a 7200VXR (ver (C7200-ADVIPSERVICESK9-M), Version 15.2(4)S5)  with the same result. GNS3 is 2.2.3 on Ubuntu 18.04.3 LTS up to date as of this morning.   Without "next-hop self" iBGP should use the IP of the originating eBGP router as the next hop (in this case that should be 172.20.1.2 and 172.22.1.2) and not modify it but it is.   I know i should have "next-hop" self in for this to work but I am trying to document common errors for a customer so am deliberately leaving it out to show the effect (unfortunately leaving it out isnt doing anything).   R2 Advertising router:   interface Loopback0  ip address 172.16.1.2 255.255.255.255 end    router bgp 65001   bgp log-neighbor-changes   neighbor 172.16.1.1 remote-as 65001   neighbor 172.16.1.1 update-source Loopback0   neighbor 172.16.1.1 soft-reconfiguration inbound   neighbor 172.20.1.2 remote-as 65004   neighbor 172.20.1.2 soft-reconfiguration inbound   neighbor 172.22.1.2 remote-as 65004   neighbor 172.22.1.2 soft-reconfiguration inbound   neighbor 172.24.1.2 remote-as 65002   neighbor 172.24.1.2 soft-reconfiguration inbound   neighbor 172.26.1.2 remote-as 65002   neighbor 172.26.1.2 soft-reconfiguration inbound   maximum-paths 2 R2#debug ip bgp update   *Nov 19 19:57:27.779: BGP(0): 172.16.1.1 NEXT_HOP is set to self for net 0.0.0.0/0, *Nov 19 19:57:27.779: BGP(0): (base) 172.16.1.1 send UPDATE (format) 0.0.0.0/0, next 172.16.1.2, metric 0, path 65004 *Nov 19 19:57:27.779: BGP(0): 172.16.1.1 NEXT_HOP is set to self for net 192.168.1.0/24,   R1 receiving router:   interface Loopback0  ip address 172.16.1.1 255.255.255.255 end   router bgp 65001  bgp log-neighbor-changes  neighbor 172.16.1.2 remote-as 65001  neighbor 172.16.1.2 update-source Loopback0  neighbor 172.16.1.2 soft-reconfiguration inbound  neighbor 172.19.1.2 remote-as 65004  neighbor 172.19.1.2 soft-reconfiguration inbound  neighbor 172.21.1.2 remote-as 65004  neighbor 172.21.1.2 soft-reconfiguration inbound  neighbor 172.23.1.2 remote-as 65002  neighbor 172.23.1.2 soft-reconfiguration inbound  neighbor 172.25.1.2 remote-as 65002  neighbor 172.25.1.2 soft-reconfiguration inbound  maximum-paths 2   show ip route (snippet)   B     192.168.1.0/24 [200/0] via 172.16.1.2, 00:04:28   R1#show ip bgp neigh 172.16.1.2 received-routes BGP table version is 8, local router ID is 172.16.1.1 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,               r RIB-failure, S Stale, m multipath, b backup-path, f RT-Filter,               x best-external, a additional-path, c RIB-compressed, Origin codes: i - IGP, e - EGP, ? - incomplete RPKI validation codes: V valid, I invalid, N Not found      Network          Next Hop            Metric LocPrf Weight Path  *>i 0.0.0.0          172.16.1.2               0    100      0 65004 i  *>i 192.168.1.0      172.16.1.2               0    100      0 65004 i  * i 192.168.2.0      172.16.1.2               0    100      0 65002 65003 i Total number of prefixes 3   Weird. Any ideas why it's doing this ? IOS bug or GNS3 bug ?   Thanks ... View more