I recently made an interview with networkcareer.net I talked with Daniel many things on networking, brief overview of my story , predictions for the future of networking, recommended community platforms for the network engineers and many other things ! This is a new website which provides many good interviews on networking. There are many good […]
The post Did you see my Networkcareer.net Interview? appeared first on Cisco Network Design and Architecture | CCDE Bootcamp | orhanergun.net.
Last big topic that I need to practice – Data Center Interconnect (DCI).
Fortunately I pretty confident in my skills in the MPLS L3VPN area, so I think I shouldn’t spend much time for this topic.
The most complex DCI option remains – EVPN stitching. In this topic I will show you my example of EVPN-VXLAN to EVPN-MPLS stitching (there is also option of EVPN-VXLAN to EVPN-VXLAN stitching, but configuration should be similar to my example).
EVPN stitching concept is pretty simple – you just need to configure two EVPN instances on each of DC Gateway devices (MX routers) and connect them to each other using Logical Tunnel (lt-) interfaces.
Scheme of my EVPN stitching lab:
Due to time constraints I’ll show you only the upper part of topology – stitching on vMX1 and vMX3 routers. Configurations of vMX2 and vMX4 should be exactly the same as this ones.
So lets see vMX1 routing-instances configuration:
Firstly, QFX5100 series doesn’t support EVPN-VXLAN inter-VXLAN routing, so I practice all IRB related topics on vMX devices. vQFXs acts as a simple L2 EVPN gateways.
This post continues the EVPN-VXLAN lab from the previous ones.
Full vMX IRB interfaces configuration:
![]() |
Fig 1.1- BGP Synchronization |
![]() |
Fig 1.1- use of ebgp multihop |
I recently got the chance to deploy a Cisco HyperFlex solution that is composed of 3 Cisco HX nodes in my home lab. As a result, I wanted to share my experience with that new technology (for me). If you do not really know what all this “Hyperconverged Infrastructure hype” is all about, you can […]
The post Hyper-converged infrastructure – Part 2 : Planning an Cisco HyperFlex deployment appeared first on VPackets.net.
The goal is to make Kubernetes more accessible to developers.
Windstream sources its SD-WAN technology from VeloCloud.
The post Worth Watching: The big four appeared first on rule 11 reader.
Humans will be the ‘digital conductors.’
Every 4 years since its start back in 1989, a hacker/security conference takes place in the Netherlands. This summer, the eighth version of this conference, called Still Hacking Anyway 2017 (sha2017.org), will run between the 4th and 8th of August. The conference is not-for-profit and run by volunteers, and this year we’re expecting about 4000 visitors.
For an event like SHA, all the visitors need to connect to a network to access the Internet. A large part of the network is built on Cumulus Linux. In this article, we’ll dive into what the event is and how the network, with equipment sponsored by Cumulus, is being built.
What makes SHA 2017 especially exciting is that it is an outdoor event. All the talks are held in large tents, and they can be watched online through live streams. At the event site, visitors will organize “villages” (a group of tents) where they will work on several projects ranging from security research to developing electronics and building 3D printers.
Attendees will camp on a 40 acre field, but they won’t be off the grid, as wired and wireless networks will keep them connected. The network is designed Continue reading
The Internet Society African Regional Bureau has worked with Network Operator Groups (NOGs) in Africa, providing financial and technical support to organize trainings and events at the local level. We recently shared many of their stories. There are also a number of NOGs that seek to attract women engineers to share knowledge and experience as well as to encourage young women to take up technology-related fields – which are largely perceived in the African region as “men only.” Here are their stories.
New Relic expects to see integrations with cloud services from Azure, Google, IBM, and Pivotal.
This app-based approach could make private LTE networks more affordable.