Rakesh M

Author Archives: Rakesh M

JAUT Course – Review Midweek

Hi,

Its been 3/5 Days in JAUT training and I should say Juniper has done a great job in introducing various training concept and methodologies towards Network scripting / automation.

Here are some-thing that helped

– No high stress on learning programming , they kept it to minimal and interestingly they made it more on how automation works and done instead of programming concepts – this is done in many courses

– Stress on PYEZ and Good Introduction to Ansible, simple labs  and then making the lab cover all the concepts is another great way Juniper helped to Learn us the course

– Main take-away till now is Ansible / intro to Jinja2 & YAML and templating configuration which i felt very refreshing and all my fears about templating has atleast vanished  till now.

I cant wait to blog on things that i have learnt during the training and implement it in my own lab, i will keep this topic alive for a while.

 

Cheers

Rakesh M

J-AUT Course

Hi ,

I have enrolled for Juniper-JAUT Course and looking forward to it.

Below are the details. Its a 5 Day course and am expecting more out of this course.

https://learningportal.juniper.net/juniper/user_activity_info.aspx?id=5186

My main interest lies in YAML / JSON use cases with Juniper Devices and their interaction. I will let you know how the course goes as the day progresses and over all efficiency of the course.

 

-Rakesh

Passed JNCIP-DC

I took JNCIP-DC Exam and could pass it. My review on the exam and Prep strategy.

Materials

-> Juniper Documentation

-> Cisco Implementing EVPN Video series – Safari press

-> Juniper Qfx1000 Github and vagrant images

-> DCX , ADCX , TDCX Materials

-> Hand’s on Implementation and 4 months Study (Not including any weekends)

 

Exam in itself was not that tough to be frank, but depth of questions covered all the concepts. There is no topic that you could leave from official blue-print, everything is touched and everything is touched at a fairly equal way.

 

Recommendations

-> Use the Github page for Juniper QFX1000 and download the vagrant images for practise

-> Revise Evpn and QFX-Series Books and you should be good

-> If you can, go through the official course-ware as they are good for review and exam prep

-> Evpn from Cisco’s standpoint is pretty much covered by Many learning instructors like INE,CBT use them to learn the technology if you are Video based learning individual.

 

-RAKESH

 

 

 

 

IP CLOS – EBGP – Multipath Multiple-as

Hi,

We have seen how iBGP was used to do the IP Clos with a RR Setup, how about eBGP.

Configurations / EVE Topology – https://github.com/r2079/JDC

Two simple rules

  • All spines have connections to all leaves – eBGP
  • No leaf or No spine devices have interconnected BGP.

Here is the topology.

 

 

The picture says 1000 words here – How the physical links are connected that’s how the bgp flows.

 

Lets see the BGP Status on R1 and R2

 

Since the hurdles of multipath has been explained. The use ADD-Path is not required here, instead since the update comes from Different AS numbers (R4 and R5) giving out the same update, we have to use another knob called MULTIPLEAS. This has to be on all Spine and leaf devices so that proper Load Balancing can be done along with EXPORTLB policy in the forwarding table.

Lets see one of the routers

 

Verification from R6

 

Regards

Rakesh

 

BGP ADD-PATH – Summary

Hi,

First things first, I have been getting a lot of requests to upload the lab’s which i illustrate as is, so i shall be uploading them to a Github page with initial and final-configs and Instead of vagrant i shall be using EVE-NG as a tool so that you guys can import them easily.

https://github.com/r2079/JDC

Going through Fabric-Path and CLOS concepts, got myself started with 3 Stage Clos and as a part of understanding it, discovered something.

Why –  To make sure Servers at one end have equal cost path to the servers-at other end, at scale the spine accordingly optimizing the CAPEX.

Simple words, in the below topology, we need to make sure that R6 has equal cost to R7 and vice-versa.

 

Protocols and setup

-> OSPF for the entire domain and Ibgp to peer between RR (R2) and all other loopbacks, we use OSPF so that Ibgp peering will be over Loopback and also for load-balancing protocol Next-hops

-> Default routes on R6 and R7, load-balance (per-packet) on all-routers (where technically required)

-> R3 AND R4,R5 has static back to loopbacks of R6 and R7 respectively, advertising them into OSPF will defeat the purpose obviously Continue reading

1 … 4 5 6