Inter-AS MPLS VPN Option A,B and C

Поделиться
HTML-код
  • Опубликовано: 24 июл 2024
  • In this video i talk about connecting different sites of customers who are part of different AS (Autonomous Systems). We look at 3 ways to do it via Option A, B & C
  • НаукаНаука

Комментарии • 36

  • @pritishbarbara7962
    @pritishbarbara7962 Год назад +1

    This is one of the best explanation i have ever learnt for Option A B C NNIs, I personally request you to please make a training video on SEGMENT ROUTING, Many Thanks

  • @user-tr5ko1ho2n
    @user-tr5ko1ho2n 6 месяцев назад

    You did an excellent job explaining all the options and I especially likes your troubleshooting scenarios.

  • @babrakji1
    @babrakji1 4 года назад +2

    thats what you call a great teaching technique, much appreciated.. was very easy to absorb Alhamdolellah.. thanks for the good work

  • @ravitiwari5530
    @ravitiwari5530 3 года назад +1

    Awesome stuffs. Perfectly explained.

  • @vyasbalkishan
    @vyasbalkishan 2 года назад +1

    You covered a lot and very informative. Thanks a lot.

  • @tapan838
    @tapan838 4 года назад +2

    Awesome Explanation ....Thank you so much

  • @pramodshastri
    @pramodshastri 4 года назад +2

    Soooperb explanation..... You made concept crystal clear

  • @ferozsyed2014
    @ferozsyed2014 2 года назад

    Great explanation, keep uploading more videos. Thanks man.

  • @giulianodolfi5404
    @giulianodolfi5404 Год назад

    Congrats, great explanation!

  • @kerryk232323
    @kerryk232323 2 года назад

    great video! This helped me prepare for an interview

  • @mohiuddimmohammedghazi6120
    @mohiuddimmohammedghazi6120 4 года назад +2

    Superb... Very open explanation Thanks a Lot

  • @enriquegabriel7708
    @enriquegabriel7708 5 месяцев назад +1

    Option A (treating each SP as a CE): 46:59
    Option B (ASBRs forming MP-BGP peering with huge vpnv4 tables): 58:40
    Option C (RRs forming MP-BGP peering separating Control Plane from Data Plane): 1:17:52

  • @raoufkh9781
    @raoufkh9781 Год назад

    many thanks this video help me a lot

  • @aishwarjyoee
    @aishwarjyoee 10 месяцев назад

    many thanks for this video

  • @benkoufie5400
    @benkoufie5400 4 года назад +2

    Excellent

  • @Usmantravelogs
    @Usmantravelogs Год назад

    Great explanation Great work

  • @samadwani405
    @samadwani405 2 года назад

    When you are planning for segment routing???

  • @rajeshkumarganji2095
    @rajeshkumarganji2095 4 года назад

    That was very good explanation.. But for inter-as Option-B, i think next-hop-self between R4 & RR and R8 & RR is not required because for bgp vpnv4 family next-hop-self is by default enabled.

    • @BitsPlease
      @BitsPlease  4 года назад +2

      Between R4&RR and R8&RR, we have MP-iBGP (next-hop-self disabled) and not MP-eBGP (next-hop-self enabled).

    • @BitsPlease
      @BitsPlease  4 года назад +1

      @UCpOXXnLw4FQeEPwdItHeGMQ In Option-A, the R4-R8 interface is in VRF Cust-A. So say the route 10.11.11.11 learnt on R4 from R8 appears like a PE-CE route for VRF Cust-A (E-BGP route).
      On R4, this route then moves from the VRF table to the MP-BGP table. Due to MP-BGP between R4-R3, the route is learnt on R3 with the next hop of R4.
      In Option-B, R4-R8 already have MP-BGP between them. R4 learns the route from R8 with the next-hop of R8. Thid route is sent as-is to R3 but R3 has no connectivity to R8, hence we use next-hop-self on R4. This way the next-hop changes to R4 as R3 has connectivity to R4.
      The difference is in option-A, the route becomes a M-BGP route from an ipv4 PE-CE route but in option-B, the route is learnt as a MP-BGP route.

  • @indianhun1687
    @indianhun1687 Год назад +1

    option A start from 47:00
    Option B start from 58:00
    Option C start from 1:18:00

  • @samadwani405
    @samadwani405 2 года назад

    Sir still waiting for your segment routing videos

  • @frankli7035
    @frankli7035 4 года назад +1

    can you share the eve-ng topology file ,very appreciate.

    • @BitsPlease
      @BitsPlease  4 года назад +1

      Frank Li Unfortunately I don’t store the eve files. Though it’s very easy to create the topology, I’m just using the IOL routers with 15.x release

    • @frankli7035
      @frankli7035 4 года назад

      @@BitsPlease if i want set the customer as the same ,so i need to use as-override in the vrf section ,right?

  • @nibrasalshamary4319
    @nibrasalshamary4319 3 года назад

    could you share the lab for test and study

    • @BitsPlease
      @BitsPlease  3 года назад

      Hey Nibras . This one was a while back so i dont have it handy. I talk about all the configurations in the videos though

  • @sankets392
    @sankets392 4 года назад

    how come without sending community string it worked

    • @sankets392
      @sankets392 4 года назад +1

      okay i got it, by default this comand is run by router so as to send mpls tag as community string.

  • @abhishekpratap4785
    @abhishekpratap4785 2 года назад

    Please upload p2mp rsvp te tunnel video...

  • @sankets392
    @sankets392 3 года назад

    at the end it was too confusing....and why one ISP will share all its own path to other ISP......path selection is complicated rest its awesome

  • @8051579090
    @8051579090 11 месяцев назад

    Very Helpful ! could you please help me to get that lab for study and practice.