Traffic Engineering with L2TPv3

As previously I had shared the document that show how to configure MPLS Traffic Engineering with Per VRF , But if we ant to have Traffic Engineering with L2 Circuit the how it can possible ?


Traffic Engineering is possible in most of the scenario & with most of the protocol, But only think is that we need to tweak the old technology with new technology to achieve the requirement.

Here the below document shows that how we can do Traffic Engineering with L2tpv3 aka L2Circuit .

Traffic Engineering with L2TPv3
 

OSPF Without Area 0

As we know that in OSPF we need to have Area 0 and also aka Backbone Area. But In MPLS Domain the OSPF Backbone Area term had detached.

Instead of having Backbone Area, In MPLS Domain we have some thing known as Super Back Bone. The Service Provider network is Know as Super Backbone area in MPLS Domain, which replace you traditional OPSF backbone Area.


So as per Traditional OSPF design we supposed to have Area 0 but in MPLS domain Super Back bone area is not associated with any area number. So in MPLS domain OSPF can work without Area 0.

Below Document show that how OSPF is configured without Area 0

OSPF Without Area 0

Ethernet over MPLS

EoMPLS, as specified in the draft-martini allows Layer 2 Ethernet frames to be transported across a Multiprotocol Label Switching (MPLS) core network. For the label switch router (LSR) to switch Layer 2 virtual circuits (VC), it must have IP connectivity to transport any Layer 2 attachment services. Thus, the edge LSRs must have the capability to switch Layer 2 VCs.

The EoMPLS can configured as below.

•  Router to RouterPort Based
•  Router to RouterVLAN Based
•  VLAN Rewrite
•  Switch to SwitchVLAN Based
•  Switch to SwitchPort Based
• VLAN Rewrite in Cisco 12000 Series Routers

 The Below link show how to configure Router to Router VLAN Based EoMPLS.

VLAN Based EoMPLS

Importing Routes from Global Table into a VRF Table

Every time I saw that we leake route from VRF to global routing table, So VRF can use the Global routing table for Internet Accsess ( Internet over L3 VPN ) or for specific network access.

But heere we are going to see that If we want to import routes from Global routing table to VRF then how  we can configure the network device .

Using the feature know as Import Route Map  ( import ipv4 unicase | multicast )

The BGP Support to Import routes  from Global Table into a VRF Table feature introduces the capability to import IPv4 unicast prefixes from the global routing table into a Virtual Private Network (VPN) routing/forwarding instance (VRF) table using an import route map.

Below is the Example :

ip prefix-list chetan seq 10 permit x.x.x.x/x


ip prefix-list chetan seq 20 permit x.x.x.x/x
ip prefix-list chetane seq 30 permit x.x.x.x/x
!

ip vrf ckumar
rd 50:1

import ipv4 unicast map CHETAN_IMPORT
route-target export 50:1

route-target import 50:1

!

exit

!

route-map CHETAN_IMPORT permit 10

match ip address prefix-list chetan

Cisco IOS Release Naming

Letter Definitions for Cisco IOS Release Trains

The first character assigned to the release is based on the technology specific to that release. These are technology characters utilized in Cisco's IOS Release deployment.


A = Aggregation/Access Server/Dial technology


B = Broadband

C = Core routers (11.1CA, 11.1CT, 11.1CC)

D = xDSL technology

E = Enterprise feature set

F = Feature Specific enhancements (11.2F)

G = Gigabit Switch Routers (GSR)

H = SDH/SONET technology (11.3HA)

J = Wireless Networking technology (Aironet)

M = Mobile (Restricted to Mobile Wireless BU usage and further reserved for Mainline)

N = Voice, Multimedia, Conference (11.3NA)

P = Platform features (11.2P)

R = Reserved for ROMMON reference

S = Service Provider

T = Reserved for Consolidated Technology Train

W = LAN Switching/Layer 2 routing

X = A short lived, one-time release (12.0XA)

Y = A short-lived, one-time release (when Xs are exhausted)

Z = A short-lived, one-time release (reserved if Ys are exhausted

Cisco IOS S Family Numbering

Cisco IOS Mainline and T Trains Numbering

How Cisco IOS Life Cycle Works

1] First Customer Shipment (FCS)

2] End of Sale (EoS) Announcement

3] End of Software Maintenance (EoSWM or EoSW)

4] End of Vulnerability/Security Fixes

5] Last Date of Support

Cisco IOS Naming Standard

Below is Cisco IOS Naming Standard

Cisco IOS Family

Below Diagram show the Cisco ISO Tree