in

CCIE - Internetwork Expert's Online Community
Forums » Internetwork Expert Products » CCIE R&S Lab Workbook Volume II Version 4.1 » IEWB-RS Volume 2 Version 4.1 Lab 12 » Task 5.1
Latest post 09-28-2008 7:55 PM by danielowhite. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next

  • 09-23-2008 12:33 PM

    • noairbag
    • Top 75 Contributor
    • Joined on 08-04-2008
    • Posts 17
    • Points 205

    Task 5.1

    Reply Contact

    I understand why we send next-hop-self from eBGP peers towards iBGP peers, but I do not understand why we set next-hop-self when peering with Backbone devices. Is this necessary?

     

    For example, R2 is setting next-hop-self when peering with BB2 - why? I thought that no matter what the next-hop value is for a particular route that R2 has, BB2 will see all routes passed from R2 with R2 as next-hop. Correct?
    • Post Points: 20

  • 09-28-2008 7:55 PM In reply to

    Re: Task 5.1

    Reply Contact

    ...correct....

    it is passed on to ebgp automatically.. below is not good example...but if i was sending other routes it would show 192.10.1.2 as next hop..

    BB2#sh ip b | be Net
       Network          Next Hop            Metric LocPrf Weight Path
    *> 129.1.0.0        192.10.1.2               0             0 200 i
    *> 150.1.0.0        192.10.1.2               0             0 200 i
    • Post Points: 5
Page 1 of 1 (2 items)