Tag archive: MPLS

Sham Link feature is necessary if we want to deploy backdoor link between 2 OSPFs domains belong to the same area but split by MPLS. The issue that we will come across is a result that backdoor link will have priority over the MPLS.

MPLS works based on underlying IGP protocol. It may be OSPF or IS-IS, but whatever we choose, we are still dependant to IGP path calculation. Of course we may manipulate the cost of path and this way provide traffic enginering, but MPLS has its own mechanism.

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…

If you use VRFs, sometimes you may want to use something what is being called “route leaking”. Route leaking consists in importing and exporting prefixes between VRFs or between VRF and global routing table. In this article I’ll show you how to implement route leaking in 5 different ways.

If we can virtualize  layer 2 with Vlans, maybe there is a solution that enables us to virtualize layer 3 on a router? If we could separate the traffic within the same  interface and prevent particular flow in participating in choosen routing processes. In other words alike on ASA where we create contexts in order to split one single chassis…

Cisco Express Forwarding (CEF) the technology which has been invented by Cisco   omitted layer 3 in order to accelerate packets switching. It has increased significantly the efficiency and speed of packets forwarding, but there was a problem because CEF is Cisco proprietary and has worked only with Cisco devices. Then  MPLS has been invented as an…

Menu