Jump to content

ccie8704

Members
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ccie8704

  • Rank
    Junior Member
  1. Hi there !!! Local preference was not configured in my case. See one of my friend attempted exam and in his case default originate was not attached to neighboe statement. instead he had under bgp "default information originate". If you have above command , med statement with neighbor works and you don't need to add default originate route-map MED. router bgp x neighbor x.x.x.x route-map MED default information originate so default route that is advertised carries MED as per map. However this is not the case when you have following config: router bgp x neighbor x.x.x.x default originate so you need to add route map along with it.
  2. Hi there !!! Your command syntax might be true as well however in my case these two commands worked fine as well.
  3. Hi Everyone. 3.2 MPLS VPN part 2 All ip add used for eBGP peering must pass the BGP's directly connected check Does anybody have an idea what configuration do we require to fulfill it. I do not see any configuration in PDF against it.
  4. Did anyone encounter these logs on R17,R18: *May 9 17:31:15.553: %ADJ-5-PARENT: Midchain parent maintenance for IP midchain out of Tunnel0, addr 215.0.0.15 - looped chain attempting to stack R17# Problem is that to establish tunnel, R17 need to reach NBMA IP of R15. Ideally R17 should go default route 0.0.0.0 provided by R12. But, see below: R17#show ip route 145.67.89.10 Routing entry for 145.67.89.8/30 Known via "eigrp 200", distance 170, metric 26905600, type external Redistributing via eigrp 200 Last update from 215.0.0.15 on Tunnel0, 00:00:01 ago Routing Descriptor Blocks: * 215.0.0.15, from 215.0.0.15, 00:00:01 ago, via Tunnel0 Route metric is 26905600, traffic share count is 1 Total delay is 51000 microseconds, minimum bandwidth is 100 Kbit Reliability 255/255, minimum MTU 1476 bytes Loading 15/255, Hops 1 To reach 145.67.89.10 of R15 and to establish tunnel, R17 is using its route for 145.67.89.10 learnt over the same tunnel and hence this error log. In order to stop R15 from advertising its NBMA .10 IP, I removed "red connected" and tunnel came up. After this we see no route for 145.67.89.10 and it goes out via 0.0.0.0 R17#show ip route 145.67.89.10 % Subnet not in table R17#show ip route 0.0.0.0 Routing entry for 0.0.0.0/0, supernet Known via "static", distance 1, metric 0, candidate default path Routing Descriptor Blocks: * 145.67.89.21 Route metric is 0, traffic share count is 1 Not sure if there is any other way of doing it or not ?
×
×
  • Create New...