Juniper Specialist for Data Center Migration (vxlan, evpn, bgp, ibgp)
Budget: €100 – €900 EUR
We’re seeking a highly experienced Juniper specialist to help migrate our infrastructure from one data center to another.
This is second post of this project because first one has some issues.
This role requires advanced, practical knowledge of Juniper data center networking (particularly VXLAN, BGP EVPN) and ISP-level routing (BGP, routing policies, etc.).
We need someone with real-world, hands-on expertise—not just theory—who can diagnose and fix complex issues (like ARP suppression problems) swiftly and effectively.
Scope of Work:
Relocate Juniper MX Routers:
1: We have two Juniper MX routers at our old location, each with full BGP views and complex routing policies (e.g., RPF loose checks, default-route splitting, etc.).
2: You’ll move one MX to the new location while maintaining interconnectivity (iBGP sessions) so subnets remain available at both ends. When new location will be fully configured and ready to move we will move second router there too and all devices what is connected in L2
Establish Connectivity Between Sites:
1: Maintain iBGP sessions between the old and new sites via a tunnel or a leased last-mile connection.
2: Ensure all subnets remain up and announced at both locations during the transition.
Set Up VXLAN BGP EVPN at the New Location:
1: The new site will include an MX960 (router), QFX5110 (spine), and QFX5100 (leaf).
2: Configure a spine-leaf architecture using VXLAN BGP EVPN for the server infrastructure.
Migrate Existing Services & Subnets:
1: Previously, we had a Juniper SRX active/active cluster (and announced gateways was there); those gateways are now on an IRB interface of one MX (because we turned off srx cluster and we are not using them anymore).
2: You’ll ensure a seamless gateway transition and subnet availability as services move from the old to the new site.
I hope that you will nor simply repeat all this text and will tell that you are the best for this job or you will use AI to generate answer - this will be noticable instantly and i will deprioritate these requests. For AI users, if you think that you can achieve this task by using AI then answer to you is NO YOU CANT DO THAT EVEN YOU HAVE STRONG NETWORKING KNOWLAGE BECAUSE THERE IS NEEDED REAL WORLD EXPIERENCE WITH JUNIPER DEVICES AND CONFIGS AND TOPOLOGY IS NOT UNDERSTANDABLE FOR AI.
The main issue is that now on old infrastructure we have hudge vlan and almost all subnets are in same vlan. End users (virtual machines) are connected via access mode to same vlan and some virtual machines has ip addresses from different subnets!.
This is second post of this project because first one has some issues.
This role requires advanced, practical knowledge of Juniper data center networking (particularly VXLAN, BGP EVPN) and ISP-level routing (BGP, routing policies, etc.).
We need someone with real-world, hands-on expertise—not just theory—who can diagnose and fix complex issues (like ARP suppression problems) swiftly and effectively.
Scope of Work:
Relocate Juniper MX Routers:
1: We have two Juniper MX routers at our old location, each with full BGP views and complex routing policies (e.g., RPF loose checks, default-route splitting, etc.).
2: You’ll move one MX to the new location while maintaining interconnectivity (iBGP sessions) so subnets remain available at both ends. When new location will be fully configured and ready to move we will move second router there too and all devices what is connected in L2
Establish Connectivity Between Sites:
1: Maintain iBGP sessions between the old and new sites via a tunnel or a leased last-mile connection.
2: Ensure all subnets remain up and announced at both locations during the transition.
Set Up VXLAN BGP EVPN at the New Location:
1: The new site will include an MX960 (router), QFX5110 (spine), and QFX5100 (leaf).
2: Configure a spine-leaf architecture using VXLAN BGP EVPN for the server infrastructure.
Migrate Existing Services & Subnets:
1: Previously, we had a Juniper SRX active/active cluster (and announced gateways was there); those gateways are now on an IRB interface of one MX (because we turned off srx cluster and we are not using them anymore).
2: You’ll ensure a seamless gateway transition and subnet availability as services move from the old to the new site.
I hope that you will nor simply repeat all this text and will tell that you are the best for this job or you will use AI to generate answer - this will be noticable instantly and i will deprioritate these requests. For AI users, if you think that you can achieve this task by using AI then answer to you is NO YOU CANT DO THAT EVEN YOU HAVE STRONG NETWORKING KNOWLAGE BECAUSE THERE IS NEEDED REAL WORLD EXPIERENCE WITH JUNIPER DEVICES AND CONFIGS AND TOPOLOGY IS NOT UNDERSTANDABLE FOR AI.
The main issue is that now on old infrastructure we have hudge vlan and almost all subnets are in same vlan. End users (virtual machines) are connected via access mode to same vlan and some virtual machines has ip addresses from different subnets!.