Working on the 4.2.1 content right now. Most of it's done and I"m literally going through the type-5 multi-node HA service chaining documentation this week! Stay tuned
I appreciate your videos , now I’m planning migrate juniper contrail to apstra , I believe if I try to recreate my Ip fabric in a virtual lab it’s easy to understand the apstra’s features easily
Thank you for saying hello! I built my first Apstra lab about 4 months ago and it was for exactly the same reason - I needed to work with the product to really understand it. This lab has been so useful to me, particularly since the labs I had access to before this were hardware-based and very difficult to reserve. Now I can work with Apstra any time I want! Cheers
I'm sure I can figure out a way to do this that isn't using one of my personal tools. Are you having an issue building the lab, or are you just looking to save the time of setting up the nodes and building the links (which I certainly understand)?
does juniper have a simulation lab such as VIRL or CML ? I am aware of Juniper Vlabs but those are more of preset configurations and dont provide much flexibibility to modify network topology
VIRL and CML exist because the images that run on most Cisco hardware don't play nice with resources when virtualized. Junos is based on either a BSD or Linux kernel, so these considerations don't exist. Use the virtualization tool of your choice. I use eve-ng, but I could also use GNS3, ESXi, or even KVM running on Ubuntu. Hope this helps!
Thank you for your comment and thoughtful questions! Seamless EVPN-VXLAN, or EVPN-VXLAN "stitching", simplifies the interconnection of distributed fabrics by terminating VXLAN tunnels on fabric border devices and establishing discrete transit tunnels between these fabric borders across multiple DC's. Without stitching, VXLAN tunnels are meshed between access-leafs across the DCI. In short, stitching reduces the number of tunnels required to interconnect fabrics over a DCI. This functionality has been present in Junos since 2020. As of today, it is on the short-term roadmap for Apstra and could be released as soon as 4.1 later this year.
I will in a future video (once my campus fabric series is complete). We're rolling out additional security features and even integration with our firewalls. This requires the latest version of Apstra (my lab is still 4.0.1), so there will be an upgrade video, followed by security service block configuration. Stay tuned!
Thanks for the video you made, very useful video, unfortunately I can't do the DCI part because my server only got 64G ram, so I can only run 1 DC, but that's ok at least now I know how to configure Apstra, thanks, thank you very much!
you can do DCI using 3 x QFXs in one DC and 3 x QFXs in other DC. QFX run fine with 5 GB RAM [2 GB for RE / 3 GB for PFE]. This makes up to 30 GB of RAM. You can physically connect Border LEAFs together and there is no need for external router. However from Apstra side Border LEAF-2 [DC-2] would add as a generic system in DC-1 Blueprint and Border LEAF-1 [DC-1] would add as a generic system in DC-2 Blueprint.
Thanks so much for this great video lectures. It will be great if you can do service chaining video.
Working on the 4.2.1 content right now. Most of it's done and I"m literally going through the type-5 multi-node HA service chaining documentation this week!
Stay tuned
Thank you
You're welcome
Thanks so much for this series of videos on eve-ng and Apstra. It saved me so much time figuring out how to use Apstra for our use case.
Thanks for the series of videos. Very useful!
Awesome! I'm coming up for air after a long project and getting ready to record my next series on EVPN-VXLAN campus fabrics. Hope to see you soon!
I appreciate your videos , now I’m planning migrate juniper contrail to apstra , I believe if I try to recreate my Ip fabric in a virtual lab it’s easy to understand the apstra’s features easily
Thank you for saying hello!
I built my first Apstra lab about 4 months ago and it was for exactly the same reason - I needed to work with the product to really understand it. This lab has been so useful to me, particularly since the labs I had access to before this were hardware-based and very difficult to reserve. Now I can work with Apstra any time I want!
Cheers
@@5minutejunos great series videos sir,, might can combine with some case, or next level lab with apstra
Thank you for this material. Can we download an eve-ng template from somewhere?
I'm sure I can figure out a way to do this that isn't using one of my personal tools. Are you having an issue building the lab, or are you just looking to save the time of setting up the nodes and building the links (which I certainly understand)?
does juniper have a simulation lab such as VIRL or CML ? I am aware of Juniper Vlabs but those are more of preset configurations and dont provide much flexibibility to modify network topology
VIRL and CML exist because the images that run on most Cisco hardware don't play nice with resources when virtualized. Junos is based on either a BSD or Linux kernel, so these considerations don't exist. Use the virtualization tool of your choice. I use eve-ng, but I could also use GNS3, ESXi, or even KVM running on Ubuntu.
Hope this helps!
很感谢你的视频 ，期待multi-tenancy和Service Chaining。这个软件支持Juniper最新的Seamless EVPN-VXLAN的DCI吗？还有我发现这个软件构建的数据中心 Overlay使用的是EBGP，和Juniper一直推荐的underlay使用EBGP，Overlay使用的是iBGP不一样，这个能支持underlay使用EBGP和Overaly使用iBGP吗？
Thank you for your comment and thoughtful questions!
Seamless EVPN-VXLAN, or EVPN-VXLAN "stitching", simplifies the interconnection of distributed fabrics by terminating VXLAN tunnels on fabric border devices and establishing discrete transit tunnels between these fabric borders across multiple DC's. Without stitching, VXLAN tunnels are meshed between access-leafs across the DCI. In short, stitching reduces the number of tunnels required to interconnect fabrics over a DCI.
This functionality has been present in Junos since 2020. As of today, it is on the short-term roadmap for Apstra and could be released as soon as 4.1 later this year.
Could you please explain how to do firewall based filtering through apstra
I will in a future video (once my campus fabric series is complete). We're rolling out additional security features and even integration with our firewalls. This requires the latest version of Apstra (my lab is still 4.0.1), so there will be an upgrade video, followed by security service block configuration.
Stay tuned!
Thanks for the video you made, very useful video, unfortunately I can't do the DCI part because my server only got 64G ram, so I can only run 1 DC, but that's ok at least now I know how to configure Apstra, thanks, thank you very much!
you can do DCI using 3 x QFXs in one DC and 3 x QFXs in other DC. QFX run fine with 5 GB RAM [2 GB for RE / 3 GB for PFE]. This makes up to 30 GB of RAM. You can physically connect Border LEAFs together and there is no need for external router. However from Apstra side Border LEAF-2 [DC-2] would add as a generic system in DC-1 Blueprint and Border LEAF-1 [DC-1] would add as a generic system in DC-2 Blueprint.
How much RAM did you give to Apstra? Which version of Apstra you are using?
4.0.1
8 CPU's
24576 RAM
Probably could have used way less, but I have the resources, so I just took the defaults.