IPv6 Buzz 039: Bringing IPv6 Into Enterprise Wireless
This week's IPv6 Buzz discusses getting IPv6 into enterprise wireless environments. We discuss what proper vendor support for v6 looks like, evaluate the impact of a lack of DHCPv6 support in Android, why running dual stack is more work than a clean cutover, and more. Our guest is Joe Neville, a technical consultant at HPE Aruba.
The post IPv6 Buzz 039: Bringing IPv6 Into Enterprise Wireless appeared first on Packet Pushers.
Getting Started With Automation Hub
In the past, Ansible content such as roles, modules and plugins was usually consumed in two ways: the modules were part of the Ansible package, and roles could be found in Galaxy. However, as time went on the current method of content distribution had challenges with scale for both contributors and consumers of Ansible content. Dylan described this in a blog post worth reading.
Recent releases of Ansible started a journey towards better content management. In previous Ansible releases, each and every module was strictly tied to the release schedule of Ansible and community, customer, and partner feedback demonstrated that the release schedule of content needed to evolve. Ansible content collections allow our Ansible contributors to create specialized content without being tied to a specific release cycle of the Ansible product, making it easier to plan and deliver. For Ansible newcomers, the collections come “pre-packaged” with modules and playbooks around common use cases like networking and security, making it easier to get off the ground with Ansible. If you want to learn more about Ansible content collections, check out our series about collections!
The introduction of collections to the Ansible ecosystem solves a number of challenges for access to Continue reading
Getting Started With Ansible Content Collections
With the release of Red Hat Ansible Automation Platform, Ansible Content Collections are now fully supported. Ansible Content Collections, or collections, represent the new standard of distributing, maintaining and consuming automation. By combining multiple types of Ansible content (playbooks, roles, modules, and plugins), flexibility and scalability are greatly improved.
Who Benefits?
Everyone!
Traditionally, module creators have had to wait for their modules to be marked for inclusion in an upcoming Ansible release or had to add them to roles, which made consumption and management more difficult. By shipping modules within Ansible Content Collections along with pertinent roles and documentation, and removing the barrier to entry, creators are now able to move as fast as the demand for their creations. For a public cloud provider, this means new functionality of an existing service or a new service altogether, can be rolled out along with the ability to automate the new functionality.
For the automation consumer, this means that fresh content is continuously made available for consumption. Managing content in this manner also becomes easier as modules, plugins, roles, and docs are packaged and tagged with a collection version. Modules can be updated, renamed, improved upon; roles can be updated to Continue reading
Getting Started With Ansible Hub
In the past, Ansible content such as roles, modules and plugins was usually consumed in two ways: the modules were part of the Ansible package, and roles could be found in Galaxy. However, as time went on the current method of content distribution had challenges with scale for both contributors and consumers of Ansible content. Dylan described this in a blog post worth reading.
Recent releases of Ansible started a journey towards better content management. In previous Ansible releases, each and every module was strictly tied to the release schedule of Ansible and community, customer, and partner feedback demonstrated that the release schedule of content needed to evolve. Ansible content collections allow our Ansible contributors to create specialized content without being tied to a specific release cycle of the Ansible product, making it easier to plan and deliver. For Ansible newcomers, the collections come “pre-packaged” with modules and playbooks around common use cases like networking and security, making it easier to get off the ground with Ansible. If you want to learn more about Ansible content collections, check out our series about collections!
The introduction of collections to the Ansible ecosystem solves a number of challenges for access to Continue reading
Getting Started With Automation Analytics
With the upcoming release of the Red Hat Ansible Automation Platform there are now included Software as a Service (SaaS) offerings, one of which is Automation Analytics. This application provides a visual dashboard, health notifications and organization statistics for your Ansible Automation. Automation Analytics works across multiple Ansible Tower clusters allowing holistic analytics across your entire infrastructure.
When talking to the community and our customers, a question that often comes up is: “How do we measure success?”. Automation Analytics provides key data on Job Template usage, Ansible Module usage, organizational comparisons across your enterprise, and much more. This data can be used to assess usage, success criteria, and even charge backs between different groups. This blog post will outline how to get started with Automation Analytics and start collecting data right away.
What you need to get started:
- Red Hat Ansible Tower 3.5.3 or newer
Ansible Automation Platform terminology
There are some terms used in this blog post that may be unfamiliar Continue reading
DMVPN Point-to-Point GRE and mGRE
DMVPN spokes can use either point-to-point GRE tunnels or multipoint GRE tunnel interface. Recently, I received a question regarding DMVPN.
In fact, the Reader asked me two questions: When is GRE used in network design? When is mGRE used in network design?
Answering the aforementioned questions are the basics that you must know if you are planning to design DMVPN network.
As you might have known, DMVPN is a hub, spoke type of topology. And the most useful, important functionality of DMVPN is that it provides excellent scalability by reducing the number of tunnel interfaces configured on the hub and spokes.
I mentioned the DMVPN phases in one of my articles. Because of that, I will not explain them here again. However, if you don’t understand the meaning of DMVPN phases, I would recommend that you peruse the article on DMVPN basics before reading this article.
Point-to-Point GRE interface is used, only in Phase 1, on the spokes.
In all the Phases, mGRE interface type is always used on the hubs.
In Phase 2 and Phase 3 of DMVPN implementation, spokes also use mGRE (not multicast GRE, but multipoint GRE) interface types.
Compared to the point-to-point GRE interface, mGRE provides Continue reading
2017 CCDE Exam Dates!
2017 CCDE Exam dates has been announced.There are four CCDE exam every year. More precisely there are four CCDE Practical/Lab exam every year. There is no limitation for the CCDE Written exam.
You can join CCDE Written exam anytime in any Pearson Vue Center. It is not only 4 times in a year.
CCDE Practical exam is not only in the Cisco Office anymore, but it is in the Professional Pearson Vue Locations. There are 275 of them and unfortunatelly, not every country has PPC (Professional PearsonVue Center)
If you are in Middle East, India, Turkey, Greece and Europe would be nice location.
I attended and passed the exam in Greece and Athens is one of the most beautiful city guys 
I definitely recommend it.
Below is the 2017 CCDE Practical/Lab exam dates and I wish Good Luck for everyone and definitely recommend my Self Paced CCDE Training or Instructor Led CCDE Training.
Nothing Should Stop You!
As many of you know, I was born in Turkey. And unfortunately, the educational system of that country is very weak. And guess what: If you can’t afford to go to private school in Turkey, you may not be able to learn English in the government school.
However, if you are a very diligent student, you may learn the basics of writing or speaking English. I have decided not to allow my proofreader to edit this post. My reason is simple. I want you to notice that I am still struggling with English. But that’s okay. It’s a learning curve. So, nothing should stop you !|
My aim of writing this post is to share some of my thoughts with you. And I know many people will read this and I hope it will inspire some of you.
I worked as a network operation center engineer, presales engineer and consultant while I was in Turkey. Fortunately, I joined and managed many design projects during that time. After that, I moved to other countries with the aim of sharing my knowledge with others and getting some money of course
At this point, you might be having this thought: “With your weak Continue reading
Is Cisco CCDE Exam Vendor Neutral?
Is Cisco CCDE Exam really vendor neutral?.Recently one of my CCDE Bootcamp students asked me this question. He heard that DMVPN might come in the exam.
In the beginning of my each CCDE class, I introduce the topics which will most likely asked in the CCDE Practical exam. Cisco claims that CCDE Practical exam is vendor neutral network design exam.
And I totally agree. Actually not only DMVPN, but also HSRP, GLBP, EIGRP, GETVPN might come in the exam and you should know the details of these technologies from the design point of view.
All these technologies are Cisco specific, why then it is vendor neutral ?
Reason is simple but not maybe obvious for those who don’t know the details of the exam.
These are very commonly deployed technologies in the networks. Almost everyone learned HSRP when they studied first hop redundancy protocols, I believe, right ?
Or, can be any decent network engineer who don’t know EIGRP ?
If you think that you know routing protocols, or you think that you are familiar with them, you have to know it.
But it is not about that they are commonly used technologies.
They are actually derived from the very well known Continue reading
Mobile Broadband – Trending Technologies
For me and for most of Mobile broadband professionals, we are used to meeting the Telco Vendors such as Ericsson, Huawei, Cisco, Nokia, etc. It was a mind-shift for me personally when I started to meet RedHat, Mirantis, & VMware as a part of the NFV talks and I was really surprised that a company like RedHat is a member of the European Telecommunications Standards Institute (ETSI) with more focus on the Mobile Broadband Evolution participating in Mobile Edge Computing (MEC) Work Group.
To have a great understanding of SP Networks, you can check my new published “Service Provider Networks Design and Architecture Perspective” Book.
It is obvious nowadays that the borders between different technology domains are fading in the sense that Networks are shifting into software-defined Networks with new abstraction layers realizing network convergence.
With this post being the last one, I chose to talk a little bit about some trending and future Mobile Broadband technologies with the goal of having an overview of the Technology Roadmap.
NFV (Network Functions Virtualization)
NFV offers a way to design, deploy, & manage Network Services via decoupling the Network Functions from proprietary Hardware enabling them to run in Continue reading
Mobile Broadband Ecosystem
Mobile Broadband… You might have heard this term before, possibly in an ISP environment. The term has always represented a name of a department within a mobile operator or a vendor organization. It is always there in profile description for telecom professionals. It is everywhere actually when it comes to a certain ecosystem or framework that delivers Internet Service using Mobile Network.
To have a great understanding of SP Networks, you can check my new published “Service Provider Networks Design and Architecture Perspective” Book.
Let me bring the Wikipedia definition followed with a small note …
Mobile broadband is the marketing term for wireless Internet access through a portable modem, mobile phone, USB wireless modem, tablet or other mobile devices.
Definition is true but the note here is that you can’t rely solely on google to understand the MBB related technologies (EDGE, UMTS, 4G/LTE, etc.) because what is in google is mainly the marketing articles and the vendor specific publications which is fine but as a lesson learned, one need always to understand the technology concept decoupled from vendors influence.
The good thing is that the whole knowledge, principles, & Service descriptions for Mobile Broadband is Continue reading
Common Networking Protocols in LAN, WAN and Datacenter
Spanning Tree, Link Aggregation , VLAN and First Hop Redundancy protocols are used in Campus, Service Provider Access and Aggregation and in the Datacenter environment. There are definitely other protocols which are common across the Places in the Networks but in order to keep this article short and meaningful I choose these four.
I will describe Spanning tree, link aggregation, 802.1q Vlan and First hop redundancy protocols at a high level since I will explained them in detail later in the separate articles.
For the more advanced layer 2 protocol information check this article.
Spanning Tree – IEEE 802.1d, 802.1w, 802.1s
Spanning tree is used to build a control path between the Ethernet switches in the campus , service provider and data center environment. It prevents data plane loops by creating a tree !
Loop preventation is very crirical for the Ethernet since there is no TTL value or any other loop mitigation mechanism encoded in the Ethernet header.
Loop prevention is achieved by blocking the link which has a higher cost to the root switch in the topology.
802.1d is also known as original spanning tree or legacy spanning tree has been Continue reading
Push and Pull Based Control Plane Mechanisms
Control plane packets are used to build a communication path between the networking devices. In some cases control plane is used to advertise and learn the endpoints.
Imagine a network which consist of these networking devices, in order to crate a graph or tree among them for bridging or routing purpose, control plane protocols are used.
As a network engineer although I keep Application requirements in my mind during a network design, in general layer 4 and above is just boring.
Spanning tree, G.8032, RPR, Trill, SPB, Fabricpath,EAPS, PBB-TE (PBT) are the control plane protocols at the layer 2. They are used to create a communication path , in general a tree. Some of them allow Vlan based load balancing , some of them allow flow based load balancing with ECMP ( Equal Cost Multipath ) or ECT ( Equal Cost Tree ).
But if you read so far, I didn’t mention from reachability information. For the layer 2, reachability for us, Ethernet Mac addresses, Frame relay pdu, ATM cells etc, all of the above protocols are used for Ethernet control plane though.
In general ( SPBM is different ), reachability information is learned through flooding and learning Continue reading
Datacenter Design: Shortest Path Bridging 802.1aq
IEEE 802.1aq Shortest Path Bridging (SPB) uses IS-IS as an underlying control plane mechanism that allows all the links in the topology to be active.
In sum, it supports layer 2 multipath. SPB is used in the datacenter; however, it can also be used in the local area network. In this article, Figure-1 will be used to explain shortest path bridging operation.
Figure-1 – Leaf and Spine Topology
In Figure-1, both leaf and spine nodes run IS-IS to advertise the topological information to each other.
In SPB, IS-IS is used by the bridges to find the shortest path to each other, and it allows the topology to be calculated.
But unlike routing, large scale bridging uses only IS-IS link state protocol for the topological information, not for the reachability information.
This means that the addresses of MAC are not advertised within IS-IS.
Some vendor implementations can also use IS-IS to advertise MAC address information since they only need an additional TLV for this operation. Scalability of IS-IS for the MAC addresses advertisement is questionable for large scale deployment; thus, both BGP for MAC address distribution and IS-IS for physical topology creation might be a good option.
HSRP, VRRP and GLBP Basics and Comparison
HSRP, VRRP and GLBP are the three commonly used first hop redundancy protocols in local area networks and the data center.
In this post, I will briefly describe them and highlight the major differences. I will ask you a design question so we will discuss in the comment section below.
I am explaining this topic in deep detail in my Instructor Led CCDE and Self Paced CCDE course.
HSRP and GLBP are the Cisco specific protocols but VRRP is an IETF standard. So if the business requirement states that more than one vendor will be used , then VRRP is the best choice to avoid any vendor interoperability issue.
For the default gateway functionality HSRP and VRRP uses one virtual IP corresponds one Virtual Mac address.
GLBP operates in a different way. Clients still use one virtual IP address but more than one virtual mac address is used. So each default gateway switch has its own virtual Mac address but same virtual IP address.
To illustrate this, let’s look at the below picture.
In the above picture, clients use same gateway mac address since the first hop redundancy protocol is HSRP.
If GLBP was in used, on the Continue reading
Inter AS Option C – Design Considerations and Comparison
Inter AS Option C is the most complex, insecure, uncommon, but extremely scalable inter provider MPLS VPN solution.
I am explaining this topic in deep detail in my Instructor Led CCDE and Self Paced CCDE course.
In this post, I will explain how service providers can use Inter AS Option C to assist customers to have an end-to-end MPLS VPN service.
In the Inter AS Option B post, I explained that ASBR routers between the service providers do not keep a VRF table for the VPN customers.
As depicted in the fig.1 (shown below), as for Inter AS Option B, MP-BGP VPNv4 session is set up between service providers’ ASBR PEs.
Figure 1: Inter-AS Option B
As for Inter AS Option B, ASBR routers – the provider-edge devices between the service providers – maintain only the VPN prefixes of the customers in the BGP table.
In fact, I have shown that VPNv4 BGP session has been set up between the ASBRs.
The high-level operational differences between Inter AS Option C and Inter AS Option B are in two folds: one is that ASBRs do not have VRF table; the other is that unlike Continue reading
Russ White – Orhan Ergun CCDE Practical Exam Scenario
I am glad to announce that Russ White and I have been preparing a CCDE Practical Exam ( Lab Exam ) Scenario. This is the most realistic scenario available anywhere. Why? Because it is not only prepared by a CCDE but also by one of the exam founders!
Disclosure : This is not asked in the CCDE exam , but the structure and idea is very similar to what would be found in the exam.
Russ White is one of the CCDE exam founders and the Author of Optimal Routing Design, Practical BGP, Advanced IP Network Design, and many other network design and architecture books. Russ and I have put much effort into preparing this scenario.
I will first present this scenario for the first time in the July CCDE Training class. (You can see from here the topics which I will talk about in the class as well.)
There are already more than 20 people in the class and multiple people will attend the CCDE Exam in August. I am sure this scenario will be an excellent resource for the CCDE candidates.
If you want to be a good network designer as well as a CCDE, it is Continue reading
MPLS Layer 3 VPN Deployment
In this post I will explain MPLS Layer 3 VPN deployment by providing a case study. This deployment mainly will be for green field environment where you deploy network nodes and protocols from scratch. This post doesn’t cover migration from Legacy transport mechanisms such as ATM and Frame Relay migration as it is covered in the separate post on the website.
I am explaining this topic in deep detail in my Instructor Led CCDE and Self Paced CCDE course.
With MPLS, Layer 2 and Layer 3 VPN can be provided and main difference between MPLS Layer 2 and Layer 3 VPN from the deployment point of view is, in MPLS Layer 3 VPN, customer has a routing neighborship with the Service Provider.
In MPLS Layer 2 VPN, Service Provider doesn’t setup a routing neighborship with the customer.
In the below topology I show you basic MPLS network.
Figure – MPLS Network , Components and the Protocols
- CE is the Customer Edge device and generally located at the customer location.
- PE is the Provider Edge Device and located at the Service Provider POP location.
- P is the Provider device and located inside the Service Provider POP location.