This article is just a summarization of 2 other articles that I put on This time we will try to utilize information about QoS with simple lab.




Access lists, prefix lists work very well in case we want to filter prefixes, but sometimes you may want to take action not against particular networks, but particular Autonomous Systems. Then AS-PATH filtering is comming forward.

Thanks to MED attribute we have influence on how adjacent eBGP router should get into our AS.It is especially helpful if we have 2 or more eBGP entrance into our AS.  Now, we will check how a single eBGP router that  receives MED attribute for the same prefix from many eBGP speakers and different AS processes metric attribute.


ISIS is considered as a protocol only for service providers. Unfairly. Very well scalable, working with different kind of information thanks to TLV is worth to learn even if you are not going to implement its as an underlay routing protocol in MPLS environment.



Even if we have only single point of failure at the edge it is well to have 2 upstream links. Having 2 upstream links is involved with having 2 VPN tunnels. If one of the tunnel goes down, the second takes over the tasks of the first one.




Redistribution proces between IGP routing protocols especially with  externally redistributed networks may cause problems like routing loops or suboptimal routing. In thic article we will look closer on particular scenarios of redistribution between them.

In this lab from the scratch we will implement fully working MPLS core with Layer 3 VPN and MP-BGP vpnv4 on the provider edge routers. Also we will achieve full connectivity between customers edge routers with routing protocols. At the end we will find out how to implement “extranets” and “shared services”, thanks to which we will be able to share for example Internet for MPLS Layer3 VPN customers, still keeping their networks separately.

bgpsmalllIn this artcile we will focus on fundamental and crucial features of BGP neighborhood establishing and routes injecting into BGP processes, we also break BGP table down  for better understanding.

In this part part we will get to know what is the congestion management and queuing mechanisms based on fair queuing like Weighted Fair Queuing or Class Based Weighted Fair Queuing and how to configure them. Also how to avoid the congestion.



Thanks to this lab with simple topology we will study, how to configure iSCSI protocol in Linux and SAN environment. We gonna pass through iSCSI, Network File System and Server Message Block (SMB) also known as CIFS and at the end of the day we will be able to use  resources in SAN connected to the file server by iSCSI from Linux and Windows hosts.

Overlay Transport Virtualization is the technology that you may encounter, if you are going to span your Data Center across different geographical location with full retaining of layer 2 information. It literally enables you connectivity between 2 servers within the same Vlan that are placed far away of each other. 


In this part we will learn what is the QoS, what consists of and consists in, what are Queiuing and Scheduling. Also how to classify and mark the traffic with using of  basic configuration.




The other way of providing Data Center Interconnectivity besides OTV is VxLAN. VxLAN has ben developed through a few years and despite at the beginning was considered as a solution that enabled spanning VLANs across the single Data Center, nowadays is considered as a solution equal or even better to compare with OTV and enables us spanning VLANs across different geographical locations.

We usually think about multicast in the context of streaming video, audio, gaming, live transmissions, but also routing protocols use multicast to send updates. Moreover, if you are going to deal with Data Center Interconnect,  you gonna come across multicast trafic. But, before we go over the lab let’s get to know what is the multicast transmissions, what elements consists of and how is being used.


In the course of time the old-fashioned model od Data Center became inefficient especially when requirements regarding the traffic from North-South (client-server) have changed itself to East-West (server-server) and demanding applications started to be “hungry” for more than Gigabit links bundled via Portchannel. Also the better redundancy with non blocking links has started to be desirable.  All this problems resolved   new Spine-Leaf architecture and Application Centric Infrastructure as an easing in management.