Intermediate System - Intermediate System -- Part 1

ISIS was originally designed for Open System Interconnect (OSI) protocol Suite. The Connectionless Network Service (CLNS) is been used & introduced by OSI.

The form of running on Cisco routers is Integrated IS-IS, Which supports both CLNP and IP.

ISIS Terminology

An OSI domain is very much like a domain with the other routing protocols you've studied – it's a segment of a network that's under a common administrative control. An area is a logical segment of the network that is composed of contiguous router and their connecting data links.

These are logical entities, but there are two physical bodies as well. A host is an End system (ES). An Intermediate System (IS) is a router. Not a group of routers, a single router.

ISIS uses a two level hierarchy, allowing a large domain to be subdivided into areas

An L1/L2 router can act as an L1 and L2 router at the same time. An L1/L2 router can have neighbor in separates ISIS areas. The L1/L2 router will have two separate database – one for L1 routes and another for L2 routes

L1/L2 is the default setting for Cisco routers running ISIS

In Upcomming parts will digg further.

ISIS has three type of router: - Level 1 [L1], Level 2[L2] and L1/L2 

Level -1

L1 routers are contained in a single area, and are connected to other areas by an L1/L2 router. The L1 uses the L1/L2 router as a default gateway to reach destination contained in other areas.

Level - 1/2

An L1/L2 router can act as an L1 and L2 router at the same time. An L1/L2 router can have neighbor in separates ISIS areas. The L1/L2 router will have two separate database – one for L1 routes and another for L2 routes

L1/L2 is the default setting for Cisco routers running ISIS

CCIE Service Provider Lab Equipment and Operating System v3.0

The practical exam tests any feature that can be configured on the equipment and the IOS versions indicated in the document below. You may see more recent IOS versions installed in the lab, but you will not be tested on the new features of a release unless indicated below.


Lab Equipment

• Cisco XR12000 Series Routers
• Cisco 7200/7600 Series equivalent Routers (Using Simulator)
• Cisco ME3400E Series Switches

Software Versions

• XR12000 routers running IOS-XR Software Version 3.9.1
• 7200/7600 routers running IOS Software Version 12.2-33 SR
• ME3400E switches running IOS Software Version 12.2-54 SE

CCIE Service Provider Lab Exam v3.0 Checklist

1. Implement, Optimize and Troubleshoot Core IP Technologies



1.1. Packet over SONET
1.1.1. Cisco HDLC encapsulation
1.1.2. PPP encapsulation
1.1.3. Frame Relay encapsulation
1.1.4. Maximum transmission unit (MTU)
1.1.5. Cyclic redundancy check (CRC)
1.1.6. Keepalive timer
1.1.7. Frame Relay DLCI on point to point sub-interface
1.1.8. SONET Controller
1.1.9. POS channel



1.2. GE/10GE in the Core

1.2.1. MAC accounting
1.2.2. Speed
1.2.3. Duplex mode
1.2.4. Carrier Delay
1.2.5. MTU
1.2.6. Flow control
1.2.7. 802.1Q VLAN sub-interface



1.3. IGP routing

1.3.1. IS-IS Multi topology
1.3.2. IS-IS Multi instance
1.3.2. IS-IS System Type
1.3.3. IS-IS Metric Type
1.3.4. IS-IS Area
1.3.5. IS-IS Designated Intermediate Systems
1.3.6. IS-IS Interface Circuit Type
1.3.7. IS-IS Interface Metric
1.3.8. IS-IS Retransmission Throttle Interval
1.3.9. IS-IS LSP Interval and Lifetime
1.3.10. IS-IS Point-to-point Adjacency over Broadcast Media
1.3.11. IS-IS route leaking
1.3.12. OSPF multi instance
1.3.13. OSPF Multi Areas
1.3.14. OSPF router ID
1.3.15. OSPF over different physical network
1.3.16. OSPF neighbor
1.3.17. OSPF interface cost
1.3.18. OPSF designated router
1.3.19. OSPFv3 support for IPv6
1.3.20. EIGRP multi instance
1.3.21. EIGRP Autonomous System Configuration
1.3.22. EIGRP Cost Metrics
1.3.23. EIGRP Equal and Unequal Cost Load Balancing
1.3.24. EIGRP support for IPv6
1.3.25. RIP v2
1.3.26. RIP support for IPv6
1.3.27. Redistribution between OSPF,IS-IS and EIGRP
1.3.28. Redistribution of Directly connected routes
1.3.29. Redistribution of Static routes
1.3.30. Route summary
1.3.31. IOS-XR routing policy language (RPL)
1.3.32. Routing policy using route-map



1.4. MPLS and LDP


1.4.1. IP CEF
1.4.2. LDP router ID
1.4.3. LDP interface
1.4.4. LDP neighbor auto discovery
1.4.5. MPLS MTU
1.4.6. MPLS LDP Static label
1.4.7. MPLS LDP—Local Label Allocation Filtering
1.4.8. MPLS LDP-IGP synchronization
1.4.9. MPLS LDP Inbound/outbound Label Binding Filtering



1.5. MPLS Traffic Engineering

1.5.1. IS-IS support for MPLS TE
1.5.2. OSPF support for MPLS TE
1.5.3. RSVP for MPLS TE
1.5.4. MPLS TE tunnel setup
1.5.5. MPLS TE Tunnel bandwidth
1.5.6. MPLS TE Automatic Bandwidth
1.5.7. MPLS TE Static route
1.5.8. MPLS TE Auto route
1.5.9. MPLS TE Policy route
1.5.10. MPLS TE Forwarding adjacency
1.5.11. MPLS TE Metric
1.5.12. MPLS TE LSP attributes
1.5.13. MPLS TE Class-based Tunnel selection
1.5.14. MPLS TE Policy-based Tunnel selection
1.5.15. MPLS Pseudowire Tunnel Selection
1.5.16. Point to multi point ( P2MP) MPLS TE
1.5.17. Inter-Domain MPLS TE
1.5.18. Inter-Area MPLS TE



1.6. BGP


1.6.1. IBGP IPv4/IPv6 Peering
1.6.2. EBGP IPv4/IPv6 Peering
1.6.3. EBGP IPv4/IPv6 multi hop peering
1.6.4. BGP IPv4/IPv6 routes advertising
1.6.5. EBGP IPv4/IPv6 peering using local-AS
1.6.6. EBGP IPv4/IPv6 peering using AS-override
1.6.7. BGP IPv4/IPv6 using private AS number
1.6.8. Dual AS configuration for Network AS migration
1.6.9. BGP Next-Hop
1.6.10. BGP Weight
1.6.11. BGP Local Preference
1.6.12. BGP MED
1.6.13. BGP Origin
1.6.14. BGP Communites
1.6.15. BGP Confederation
1.6.16. BGP Router reflector
1.6.17. BGP Cluster list
1.6.18. BGP Peer Groups
1.6.19. BGP Synchronization
1.6.20. BGP Aggregation
1.6.21. BGP Conditional Advertising
1.6.22. BGP Routing policy
1.6.23. Redistributing IGP, static and connected route into BGP
1.6.24. BGP Multi-path Load Sharing
1.6.25. BGP Link Bandwidth



1.7. Multicast

1.7.1. IPv4/IPv6 Multicast addressing
1.7.2. IPv4/IPv6 Multicast routing
1.7.3. PIM Sparse Mode for IPv4/IPv6
1.7.4. IGMP V2/V3
1.7.5. IPV6 Multicast Listener Discover (MLD)
1.7.6. PIM Source Specific Multicast (SSM) for IPv4/IPv6
1.7.7. Multicast Rate-limiting
1.7.8. PIM Bidirectional (BiDir)
1.7.9. PIM Static RP
1.7.10. PIM Bootstrap Router (BSR)
1.7.11. PIM Auto RP
1.7.12. PIM Anycast RP
1.7.13. Multicast Administrative Boundaries
1.7.14. MSDP
1.7.15. MP-BGP peer for Multicast
1.7.16. MP-BGP Multicast route advertising


1.8. High Availability

1.8.1. NSF/SSO for IGP routing
1.8.2. NSF/SSO for BGP routing
1.8.3. NSF/SSO for LDP, TE, Multicast
1.8.4. HSRP, VRRP, GLBP
1.8.5. Graceful Restart
1.8.6. Control Plane Policing (CPP)
1.8.7. Bidirectional forwarding detection (BFD)
1.8.8. IP event dampening
1.8.9. IGP Fast Re-route
1.8.10. MPLS TE Fast Re-route (FRR)
1.8.11. Link Protection using MPLS-TE
1.8.12. Node Production using MPLS-TE
1.8.13. Embedded event management (EEM)


1.9. Convergence

1.9.1. IS-IS fast convergence
1.9.2. IS-IS to utilize the Overload Bit
1.9.3. OSPF fast convergence
1.9.4. BGP fast convergence
1.9.5. BGP Route Dampening
1.9.6. BGP Fast Peering Session Deactivation
1.9.7. BGP Prefix Independent Convergence (PIC)
1.9.8. BGP next hop tracking
1.9.9. BGP address tracking filter
1.9.10. BGP path MTU discovery
1.9.11. IP fast reroute (IPFRR)
1.9.12. Multicast-only Fast Re-Route (MoFRR)
1.9.13. MPLS LDP convergence


1.10. SP QoS

1.10.1. Marking using DSCP, IP precedence and CoS
1.10.2. Priority Queuing
1.10.3. Custom Queuing
1.10.4. Weighted Fair Queuing
1.10.5. WRED
1.10.6. Policing
1.10.7. Class-based Weighted Faire Queuing (CB-WFQ)
1.10.8. Low-Latency Queuing (LLQ)
1.10.9. Random-Detect using MQC
1.10.10. NBAR for QoS
1.10.11. MPLS EXP
1.10.12. Differentiated Services Traffic Engineering (DS-TE)
1.10.13. Maximum Allocation Model (MAM)
1.10.14. Russian Dolls Model (RDM)
1.10.15. Class-Based Tunnel Selection: CBTS
1.10.16. Policy-based Tunnel Selection: PBTS


1.11. Security in core

1.11.1. Standard Access-lists
1.11.2. Extended Access-lists
1.11.3. Routing Protocol Authentication for RIP V2
1.11.4. Routing Protocol Authentication for EIGRP
1.11.5. Routing Protocol Authentication for OSPF
1.11.6. Routing Protocol Authentication for IS-IS
1.11.7. Routing Protocol Authentication for BGP
1.11.8. BGP TTL Security Check
1.11.9. Infrastructure ACL
1.11.10. Anti Fragment Attacks
1.11.11. Filtering RFC 1918 Routes
1.11.12. uRPF for Anti-Spoofinng
1.11.13. Selective packet discard (SPD)
1.11.14. LDP authentication
1.11.15. Remote triggered black hole (RTBH)
1.11.16. NTP
1.11.17. Attack mitigation
1.11.18. SNMP Management
1.11.19. IP packet Accounting
1.11.20. Syslog



2. Implement, Optimize and Troubleshoot Edge/Access Technologies

2.1. FE/GE and Ethernet Trunk

2.1.1. Ethernet channel
2.1.2. Virtual Trunking Protocol (VTP)
2.1.3. Spanning Tree Protocol (STP)
2.1.4. 802.1Q VLAN
2.1.5. 802.1QinQ
2.1.6. 802.1ad Provider Bridges (PB)
2.1.7. 802.1ah Provider Backbone Bridge (PBB)
2.1.8. Connectivity Fault Management (CFM)


2.2. Frame-Relay connection

2.2.1. Frame-Relay DLCI
2.2.2. Frame-Relay map
2.2.3. Frame-Relay switching
2.2.4. Frame-Relay multilink
2.2.5. Frame-Relay LMI-Type
2.2.6. PPP over Frame-Relay


2.3. PPP connections

2.3.1. PPP encapsulation
2.3.2. PPP multilink
2.3.3. PPP Multi chassis multilink
2.3.4. PPPoE client
2.3.5. PPPoE server
2.3.6. PPP authentication


3. Implement, Optimize and Troubleshoot Layer 3 VPN

3.1. Intra AS L3 MPLS VPN
3.1.1. MP-IBGP VPNv4/VPNv6 peering
3.1.2. MP-IBGP peering using loopback interface
3.1.3. VPNv4/VPNv6 Route Reflector
3.1.4. VRF definition
3.1.5. Route Distinguisher
3.1.6. Route Target
3.1.7. Route Target import/export
3.1.8. Intra AS MPLS VPNV4/VPNV6 load balancing
3.1.9. SOO Community
3.1.10. PE-CE – RIP V2
3.1.11. PE-CE – IS-IS
3.1.12. PE-CE – OSPF
3.1.13. PE-CE – EBGP
3.1.14. PE-CE – Static Routes
3.1.15. Redistributing dynamic PE-CE routes into VPNv4/VPNv6
3.1.16. Redistributing static PE-CE routes into VPNv4/VPNv6
3.1.17. Redistributing VPN4/VPNv6 routes into PE-CE routing table
3.1.18. Intra-AS MPLS VPN multipath
3.1.19. Intra-AS MPLS VPN path selection


3.2. Inter AS L3 MPLS VPN

3.2.1. MP-EBGP VPNv4/VPNv6 peering using direct interface
3.2.2. MP-EBGP VPNv4/VPNv6 peer using multi-hop interface
3.2.3. MP-EBGP VPNv4/VPNv6 peer between RRs
3.2.4. VPNV4/VPNv6 next-hop unchanged
3.2.5. VPNV4/VPNv6 next-hop self
3.2.6. Multi VRF between ASPEs
3.2.7. Inter-AS MPLS VPNV4/VPNv6 multipath
3.2.8. Route target rewrite
3.2.9. Inter-AS MPLS VPN path selection


3.3. Carrier supporting carrier

3.3.1. MPLS LDP in customer carrier site
3.3.2. EBGPv4 + label between CSC-PE and CSC-CE
3.3.3. IGP + LDP between CSC-PE and CSC-CE
3.3.4. MPLS VPNv4 between customer carrier sites PEs
3.3.5. CSC VPN load balancing
3.3.6. VRF definition in customer carrier site
3.3.7. Customer carrier site PE-CE routing


3.4. VPN Extranet and internet access

3.4.1. MP-BGP VPNv4/VPNv6 Extra-Net
3.4.2. MP-BGP VPNv4/VPNv6 internet access
3.5. VRF service
3.5.1. Multiple VRF
3.5.2. Multiple VRF routing
3.5.3. VRF Selection based on Source IP Address

3.6. Multicast VPN

3.6.1. Default MDT
3.6.2. Data MDT
3.6.3. MP-BGP mdt peering
3.6.4. Multicast routing in VPN site
3.6.5. PM-SM in VPN site
3.6.6. RP in VPN site
3.6.7. Multicast VPN extranet



3.7. GRE L3 VPN

3.7.1. MPLS VPN—L3VPN over GRE


4. Implement, Optimize and Troubleshoot Layer 2 VPN

4.1. AToM
4.1.1. Psuedowire class
4.1.2. Ethernet over MPLS (EoMPLS)
4.1.3. Ethernet VLAN over MPLS
4.1.4. Frame Relay over MPLS (FRoMPLS)
4.1.5. HDLC over MPLS (HDLCoMPLS)
4.1.6. PPP over MPLS (PPPoMPLS)
4.1.7. PWE3 control using LDP
4.1.8. Psuedowire redundancy
4.1.9. AToM interworking
4.1.10. AToM local switching
4.1.11. AToM intra-as support
4.1.12. AToM inter-as support
4.1.13. Traffic Engineering with AToM


4.2. VPLS and Carrier Ethernet

4.2.1. VPLS
4.2.2. H-VPLS
4.2.3. VFI definition
4.2.4. VPLS BGP auto discovery
4.2.5. VLAN attached circuit
4.2.6. QinQ attached circuit
4.2.7. 802.1ad attached circuit
4.2.8. 802.1ah attached circuit
4.2.9. VPLS/H-VPLS redundancy


4.3. L2TPV3 for L2VPN

4.3.1. L2TPv3
4.3.2. L2TPv3 VPN local switching
4.3.3. L2TPv3 VPN interworking
4.4. GRE L2VPN
4.4.1. L2VPN over GRE

5. Implement, Optimize and Troubleshoot Managed Services Traversing the Core


5.1. Managed Voice/Video services traversing the core
5.1.1. Traverse Voice/video packet
5.1.2. Traverse call signal packet
5.2. Managed Security services traversing the core
5.2.1. Traverse IKE packet
5.2.2. Traverse ESP, AH packet
5.2.3. Traverse SSL packet


5.3. Service Level Agreements for managed services

5.3.1. IP SLA sender
5.3.2. IP SLA responder
5.3.3. IP SLA for MPLS VPN
5.3.4. Netflow
5.3.5. Netflow for MPLS
5.3.6. Netflow for Multicast

Why OSPF Neighbors Stuck in Exstart/Exchange State ?

This is the issue that we face some time & really it get hard or will take the entire day to resolve the issue ...

Let us see the most common reason that Why OSPF Neighbor Stuck in Exstart/ Exchange state.

What happen exactly in Exstart/ Exchange State ?

OSPF neighboring routers establish the relation & move forward ... In this state, the neighboring routers establish a master/slave relationship and determine the initial database descriptor (DBD) sequence number to use while exchanging DBD packets. Once

Now below are the reason that why the neighbor stuck in exstart/ exchange state

1]  MTU Mismatch
2] Same router ID on both router.
3] SequenceNumberMismatch
4] BadLSReq

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

EIGRP CE-PE Routing Protocol with MPLS Domain

EIGRP PE-CE routing protocol is used by service providers for customers who use EIGRP as their IGP routing protocol and, hence, prefer to use EIGRP to exchange routing information between the customer sites across an MPLS VPN backbone. In an MPLS VPN environment, to achieve this, the original EIGRP metrics must be carried inside MP-BGP updates. This is achieved by using BGP extended community attributes to carry and preserve EIGRP metrics when crossing the MP-iBGP domain. These communities define the intrinsic characteristics associated with EIGRP, such as the AS number or EIGRP cost metric like bandwidth, delay, load, reliability, and MTU.

BGP Extended Communities for EIGRP PE-CE Routing

Loop Prevention : OSPF Down Bit and Domain Tag

Loop Prevention in MPLS VPN Domain using OSPF

Down Bit


Routing loops can occur in the MPLS VPN environment when customer edge routers are dual-homed to the service provider network. MPLS VPN network implementing OSPF PE-CE routing for Customer A VPN-A sites, Site 1 and Site 2. Site 2 is in OSPF Area 2 and has multiple connections to the provider backbone.

The routing loop can be prevented by the use of the OSPF down bit, which is part of the options field in the OSPF header. The LSA header with the option field

Tag

The down bit helps prevent routing loops between MP-BGP and OSPF, but not when external routes are announced, such as when redistribution between multiple OSPF domains or when external routes are injected in an area that is dual-homed to the provider network. The PE router redistributes an OSPF route from a different OSPF domain into an OSPF domain as an external route. The down bit is not set because LSA Type 5 does not support the down bit. The redistributed route is propagated across the OSPF domain.


The routing loops introduced by route redistribution between OSPF domains can be solved with the help of the tag field, using standard BGP-OSPF redistribution rules. A non-OSPF route is redistributed as an external OSPF route by a PE router. By default, the tag field is set to the BGP-AS number. The redistributed route is propagated across the OSPF domain without the down bit but with the tag field set. When the route is redistributed into another OSPF domain, the tag field is propagated. Another PE router receives the external OSPF route and filters the route based on the tag field. The tag field matches the AS number so the route is not redistributed into MP-BGP

MPLS TE with OSPF Sham-link

When OSPF sites have a backdoor connection, they will by default prefer that link over the MPLS VPN link. Because of the redistribution that occurs, the VPN routes will be seen as inter-area (if OSPF process numbers match on PEs), E1 or E2 routes. As you probably know by now, inter-area and external routes are less preferred than intra-area routes in OSPF. No amount of administrative distance-altering or interface cost- changing can affect this decision making. Here we look briefly at a feature designed to allow VPN routes to look like intra-area routes, giving us the ability to prefer them over the VPN connection by adjusting interface costs.

Above topology show the how OSPF Sham-Link configured .

Below Link give you complete Document for same .

MPLS Traffic Engineering with OSPF Sham-link

Regards
Chetan Kumar

MPLS TE VPN with OSPF Process ID vs Domain ID

The below scenario shows the different flavours of OSPF between CE-PE.

 OSPF with unique process = O IA (OSPF Route)

 OSPF with different process = O E2 (OSPF Route)

 OSPF with unique Process ID but different domain ID = O E2 (OSPF Route)

OSPF with different process ID but unique domain ID = O IA (OSPF Route)

Below link is the complete document for same.

MPLS Traffic engineering VPN with OSPF Process ID vs Domain ID

Regards
Chetan Kumar Ress

MPLS TE VPN with Extranet

MPLS provides the flexibility to link VPN sites in a number of ways. When several VPNs get access to a shared part of network infrastructure, this is called an extranet .

Below Topology show the example of MPLS Traffic Engineering VPN with Extranet.

Attach link is the complete document for same.

MPLS Traffic Engineering VPN with Extranet


Regards
Chetan Kumar Ress

MPLS TEVPN with Export-Map

The Document show that how to configure MPLS VPN with Export - Map feature .
Using Export Map feature we can advertise the route that customer had requested .

We can restrict that advertisement of HUB VPN to other Spoke VPN .
Above topology show thta how to configure MPLS VPN with Export - Map Feature.

The attach link will give you complete document.

MPLS Traffic Engineering VPN with Export-Map

Regards
Chetan Kumar Ress

MPLS TE with Per VRF / VPN

Always we can see that in service provider network there will be primary link & Secondary link but only one link will be utilize. Implementing Policy base routing somehow we manipulate the route,



But still it required man force to monitor the link & manipulate the route as per requirement. It becomes very chaotic to do route manipulation every time in service provider network. So the solution is to have a technology where we can use un-equal load balancing or path manipulation as per requirement. So it give us scalability to use or chose any path that we required, may be it can primary path, backup path or both path i.e. un-equal circuit load balancing . So the solution is MPLS- Traffic Engineering , using MPLS traffic engineering we can manipulate the route as per our requirement where you can use each circuit or you can have route path on-demand.


MPLS Traffic Engineering (MPLS TE) is a growing implementation in today's service provider networks. MPLS adoption in service provider networks has increased manifold due to its inherent TE capabilities. MPLS TE allows the MPLS-enabled network to replicate and expand upon the TE capabilities of Layer 2 ATM and Frame Relay networks. MPLS uses the reachability information provided by Layer 3 routing protocols and operates like a Layer 2 ATM network. With MPLS, TE capabilities are integrated into Layer 3, which can be implemented for efficient bandwidth utilization between routers in the SP network.

Below link is an example where we have redundant link in service provider network, Without MPLS Traffic engineering we can see that we can only one link will be utilized . But after implementing MPLS Traffic engineering we can use both circuit as per our requirement or on-demand path manipulation per VRF.

MPLS Traffic Engineering with Per VRF / VPN

Regards
Chetan Kumar

MPLS Central VPN with Route Reflector

In certain circumstances, it may be desirable to use a hub-and-spoke topology so that all spoke sites send all their traffic toward a central site location. This may be because certain central site services for a particular VPN, such as Internet access, firewalls, server farms, and so on, are housed within the hub site. Or it may be because this particular VPN customer requires that all connectivity between its sites be via the central site

Above Topology & Attach Link show how to configure MPLS Central VPN with Route Reflector ( RR is used for more scalability in SP network )

https://learningnetwork.cisco.com/docs/DOC-8644

Regards
Chetan Kumar Ress

SDH / SONET Mapping Abbreviation

In my previous post ( SDH Mapping )  i had shared all SDH mapping & here are the terms & there abbreviation that used in configuration of STM or STS .

1] STM: Synchronise Transport Module

2] STS : Synchronise Transport Signal

3] AUG: Administrative Unit Group

4] AU: Administrative Unit

5] VC: Virtual Container

6] TUG: Tributary Unit Group

7] TU: Tributary Unit Group

8] VT: Virtual Tributary

9] C: Container

MPLS Label Distribution Modes

In an MPLS domain running LDP, a label is assigned to a destination prefix found in the FIB, and it is distributed to upstream neighbors in the MPLS domain after session establishment. The labels that are of local significance on the router are exchanged with adjacent LSRs during label distribution. Label binding of a specific prefix to a local label and a next-hop label (received from downstream LSR) is then stored in the LFIB and LIB structures. The label distribution methods used in MPLS are as follows:


Downstream on demand : -This mode of label distribution allows an LSR to explicitly request from its downstream next-hop router a label mapping to a particular destination prefix and is thus known as downstream on demand label distribution.


Unsolicited downstream : - This mode of label distribution allows an LSR to distribute bindings to upstream LSRs that have not explicitly requested them and is referred to as unsolicited downstream label distribution.


Depicts the two modes of label distribution between R1 (Edge LSR) and R2 (LSR). In the downstream-on-demand distribution process, LSR R2 requests a label for the destination 172.16.10.0. R1 replies with a label mapping of label 17 for 172.16.10.0. In the unsolicited downstream distribution process, R1 does not wait for a request for a label mapping for prefix 172.16.10.0 but sends the label mapping information to the upstream LSR R2

Forwarding Equivalence Class in MPLS

Forwarding Equivalence Class (FEC) : - As noted in RFC 3031(MPLS architecture), this group of packets are forwarded in the same manner (over the same path with the same forwarding treatment).

In MPLS Domain FEC will not perform on every HOP, It will perform only on Ingress & Egress router in MPLS domain.

But in traditional IP network FEC will perform on every HOP that comes between source & destination.

The LER is the place where aggregation is completed. LER is responsible for classifying incoming packets and relating them to FECs. Each FEC is associated with an appropriate label and forwarding path. LER uses several modes to classify traffic. For example, using the packet destination adress and port as is indicated in the following table:

When packets leave the LER to go into the MPLS domain they will be forwarded using LSRs. To do this, the LSR looks just for labels on the MPLS packet and matches it with labels within its forwarding table. This forwarding table is called the Label Information Base (LIB). The LSR will push, pop or swap labels and forward packets according with LIB instructions. One representation of such a table is as follows:

Finally when the packet reaches again another LER to leave the MPLS domain, the LER removes the MPLS header and forward the packet to an IP network.

LDP Session Establishment

There are four categories of LDP messages

1] Discovery messages : - Announce and sustain an LSR's presence in the network
2] Session messages : - Establish, upkeep, and tear down sessions between LSRs
3] Advertisement messages : - Advertise label mappings to FECs
4] Notification messages : - Signal errors

All LDP messages follow the type, length, value (TLV) format. LDP uses TCP port 646, and the LSR with the higher LDP router ID opens a connection to port 646 of another LSR:

1] LDP sessions are initiated when an LSR sends periodic hellos (using UDP multicast on 224.0.0.2) on interfaces enabled for MPLS forwarding. If another LSR is connected to that interface (and the interface enabled for MPLS), the directly connected LSR attempts to establish a session with the source of the LDP hello messages. The LSR with the higher LDP router ID is the active LSR. The active LSR attempts to open a TCP connection with the passive LSR (LSR with a lower router ID) on TCP port 646 (LDP).

2] The active LSR then sends an initialization message to the passive LSR, which contains information such as the session keepalive time, label distribution method, max PDU length, and receiver's LDP ID, and if loop detection is enabled.

3] The passive LDP LSR responds with an initialization message if the parameters are acceptable. If parameters are not acceptable, the passive LDP LSR sends an error notification message.

4] Passive LSR sends keepalive message to the active LSR after sending an initialization message.

5] The active LSR sends keepalive to the passive LDP LSR, and the LDP session comes up. At this juncture, label-FEC mappings can be exchanged between the LSRs

Special Outgoing Label Types

• Untagged : -- The incoming MPLS packet is converted to an IP packet and forwarded to the destination (MPLS to IP Domain transition). This is used in the implementation of MPLS VPN

• Implicit-null or POP label : -- This label is assigned when the top label of the incoming MPLS packet is removed and the resulting MPLS or IP packet is forwarded to the next-hop downstream router. The value for this label is 3 (20 bit label field). This label is used in MPLS networks that implement penultimate hop popping .

• Explicit-null Labe : -- This label is assigned to preserve the EXP value of the top label of an incoming packet. The top label is swapped with a label value of 0 (20 bit label field) and forwarded as an MPLS packet to the next-hop downstream router. This label is used in the implementation of QoS with MPLS.

• Aggregate : -- In this label, the incoming MPLS packet is converted to an IP packet (by removing all labels if label stack is found on incoming packet), and an FIB (CEF) lookup is performed to identify the outgoing interface to destination

SDH Mapping

SONET Architecure / Layers

VPLS implementation

To illustrate the flexibility of how you can connect CE devices, the configuration example uses different switch port modes and service-delimiting VLAN tags on each PE router as follows:

1] CE1 sends and receives untagged Ethernet packets that is, null service-delimiting VLAN tags. PE1 configures the switch port mode as dot1q-tunnel to forward packets that have an unmodified Ethernet header. The internal VLAN that is associated with the switch port is 2.

2] CE2 sends and receives tagged Ethernet VLAN packets of which the service-delimiting VLAN
tag is 4. PE2 configures the switch port mode as a trunk to remove or add the service-delimiting VLAN tag accordingly. The internal VLAN that is associated with the switch port is 4.

3] CE3 sends and receives untagged Ethernet packetsthat is, null service-delimiting VLAN tags. PE2 configures the switchport mode as access to forward all untagged packets. The internal VLAN that is associated with the switchport is 8.

4] CE4 sends and receives tagged Ethernet VLAN packets of which the service-delimiting VLAN tag is 10. PE4 configures the switchport mode as a trunk to remove or add the service-delimiting VLAN tag accordingly. The internal VLAN that is associated with the switchport is 10.

Example 15-5. PE1 Configuration

hostname PE1
!
mpls label protocol ldp
mpls ldp logging neighbor-changes
mpls ldp router-id Loopback0
!
l2 vfi l2vpn manual
vpn id 1
neighbor 10.0.0.2 encapsulation mpls
neighbor 10.0.0.3 encapsulation mpls
neighbor 10.0.0.4 encapsulation mpls
!
interface Loopback0
ip address 10.0.0.1 255.255.255.255
!
interface POS3/1
ip address 10.0.1.1 255.255.255.252
mpls ip
!
interface FastEthernet4/2
no ip address
switchport
switchport access vlan 2
switchport mode dot1q-tunnel
!
interface Vlan2
no ip address
xconnect vfi l2vpn

Example 15-6. PE2 Configuration

hostname PE2
!
mpls label protocol ldp
mpls ldp logging neighbor-changes
mpls ldp router-id Loopback0
!
l2 vfi l2vpn manual
vpn id 1
neighbor 10.0.0.1 encapsulation mpls
neighbor 10.0.0.3 encapsulation mpls
neighbor 10.0.0.4 encapsulation mpls
!
interface Loopback0
ip address 10.0.0.2 255.255.255.255
!
interface POS3/1
ip address 10.0.2.1 255.255.255.252
mpls ip
!
interface FastEthernet4/2
no ip address
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 4
switchport mode trunk
!
interface Vlan4
no ip address
xconnect vfi l2vpn


Example 15-7. PE3 Configuration

hostname PE3
!
mpls label protocol ldp
mpls ldp logging neighbor-changes
mpls ldp router-id Loopback0
!
l2 vfi l2vpn manual
vpn id 1
neighbor 10.0.0.1 encapsulation mpls
neighbor 10.0.0.2 encapsulation mpls
neighbor 10.0.0.4 encapsulation mpls
!
interface Loopback0
ip address 10.0.0.3 255.255.255.255
!
interface POS3/1
ip address 10.0.3.1 255.255.255.252
mpls ip
!
interface FastEthernet4/2
no ip address
switchport
switchport access vlan 8
switchport mode access
!
interface Vlan8
no ip address
xconnect vfi l2vpn


Example 15-8. PE4 Configuration

hostname PE4
!
mpls label protocol ldp
mpls ldp logging neighbor-changes
mpls ldp router-id Loopback0
!
l2 vfi l2vpn manual
vpn id 1
neighbor 10.0.0.1 encapsulation mpls
neighbor 10.0.0.2 encapsulation mpls
neighbor 10.0.0.3 encapsulation mpls
!
interface Loopback0
ip address 10.0.0.4 255.255.255.255
!
interface POS3/1
ip address 10.0.4.1 255.255.255.252
mpls ip
!
interface FastEthernet4/2
no ip address
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10
switchport mode trunk
!
interface Vlan10
no ip address
xconnect vfi l2vpn


Example 15-9. Verifying the VFI Status

PE1#show vfi l2vpn
VFI name: l2vpn, state: up
Local attachment circuits:
Vlan2
Neighbors connected via pseudowires:
10.0.0.2 10.0.0.3 10.0.0.4

PE1#show mac-address-table vlan 2
Legend: * - primary entry
vlan mac address type learn ports
------+---------------+-------+-----+-----------------------
* 2 000b.5fb5.0080 dynamic Yes Fa4/2
* 2 000b.5fad.e580 dynamic Yes
* 2 000b.5fb1.5780 dynamic Yes
* 2 000b.5fb1.5480 dynamic Yes

PE1#show mpls l2transport vc
Local intf Local circuit Dest address VC ID Status
------------- -------------------- --------------- ---------- ----------
VFI l2vpn VFI 10.0.0.2 1 UP
VFI l2vpn VFI 10.0.0.3 1 UP
VFI l2vpn VFI 10.0.0.4 1 UP

SSO/NSF with GR and / or NSR

Some definitions


HA- High AvailabilityHigh level terminology

SSO -StatefulSwitchover

StatefulSwitchoverAn operating mode where a dual processor router has transferred state information to a standby processor to allow the standby to pickup necessary router functions in the event of an active failure. Mostly refers to L2 information (PPP state, FIB ect) but some L3 applicability. In this operating mode both processors must run identical software versions.


NSF-Non Stop ForwardingNSF


NSF refers to a routers ability to almost immediately start forwarding packets following an active processor failure. The FIB (Forwarding Information Base) is initially transferred and actively updated so that when a failure occurs, the router is able to forward packets while the control plane is rebuilt or refreshed


GR-Graceful Restart


IETF specified mechanisms for interaction between routing protocol peers which allow the peer of a failing device to continue forwarding packets to that device, even though the neighbor relationship has been destroyed.


NSR –Non Stop Routing


A routing protocol operating mode where all information needed to fully maintain the neighbor relationship and all its relevant routing information is transferred (or "checkpointed") to the standby processor. No additional communication or interaction with the routing protocol peer is needed in this mode.Some implementations allow the use of both GR and NSR for the same protocol, but single routing protocol session must be either GR or NSR.






BGP NSF Awareness Timers

This section documents the configuration of the BGP graceful restart timers.

(Optional) The restart-time argument determines how long peer routers will wait to delete stale routes before a BGP open message is received. The default value is 120 seconds.

(Optional) The stalepath-time argument determines how long a router will wait before deleting stale routes after an end of record (EOR) message is received from the restarting router. The default value is 360 seconds

Optical Fiber Type & Length

Optical fiber

Optical fiber are classified according to several parameters. The most important ones are:

1] Diameter: 9 μm, 10 μm, 50 μm and 62.5 μm
2] Wavelength: 850nm, 1300nm, 1310nm and 1550nm
3] Number of wavelength: Multi-mode Fiber (MMF) OR Single-mode Fiber (SMF)
4] Supported distant range: in meters / kilometers

Generally speaking, the "S" stands for "Short Wave Length" and "L" stands for "Long Wave
Length".

• LX fibre - e.g. 1GBASE-LX / 1000BASE-LX is available in 50 μm and 62.5 μm as multi-mode fibre (mmf) supporting about 550 meters distance at 1300 nm wavelength. Distances of 2..10 km are possible in case of single-mode fibre (smf).

• SX fibre - e.g. 1GBASE-SX / 1000BASE-SX is available in 50 μm and 62.5 μm as multi-mode fibre supporting about 250 meters distance at 850 nm wavelength. This wavlength allows for the use of LED transmitters, which are cheaper available then the normally used laser components.

• FX fibre refers to the 100BASE-FX fast ethernet standard. This fibre type is the long wavelength optics fibre type for 100Mbps transmission systems.

Multiplexing

Some Basic - Digital Signal

First some basic stuff. You will see references to 64K (bits) 'channels' all over the place. This is the basic digital voice signal - called Digital Signal 0 or the infamous DS0 for short. The digital voice signal is encoded using PCM (Pulse Code Modulation) and TDM (Time Division Multiplexing). All other classic copper signal hierarchies, known as PDH - the Plesiochronous Digital Hierarchy, such as T3, are defined as multiples of DS0. Why 64K. Well... to digitize narrowband speech (voice) you take a 4KHz spectrum (actually 3.1K). Normal sampling techniques only give reasonable resolution if sampled at twice the frequency (which gives 2 x 4K(ish) = 8K samples per second). Each sample is 8 bits which gives 8K x 8 = 64K bits per second.

BIT DROPPING - Digital Signal

Now if you think that for a T1 if you multiply 24 x DS0 (64,000) you do NOT get 1.544 Mbit/s instead you get 24 * 64,000 = 1.536 Mbit/s. The extra bits are lost between 'frames' where a frame consists of one 8 bit sample for each of the 24 channels (remember the DS0 basics). So every 192 bits (24 x 8 = 192) we add a 'frame separator' bit to give 193 bits per frame. The final arithmetic is 193 bits x 8K samples = 1.544 Mbit/s. Easy really.
If you do the same arithmetic for DS1C, T2 etc. the above will not give the right answer. In short, above T1 things get really nasty with M-Frames and M-subframes. Its mind numbing stuff and if you really need this information get hold of ANSI T1.107-2002 and lots of coffee or other mind-altering substances.

Optical Carriers

Optical transmission systems are known as SONET (Synchronous Optical NETwork) in North America and SDH (Synchronous Digital Hierarchy) in the Rest of the World. Optical Carriers are typically known by their OC-x number where x is a multiple of the OC-1 rate of 51.84 Mbps (shades of DS0 but a tad faster). While there is a common world-wide standard for optical systems there are differences but they are accommodated within the standard. North America uses an STS-x (Synchronous Transport Signal) format for frames (packets) and Europe an STM-x (Synchronous Transport Module) format because .... well its obvious really, one is from Europe and the other from North America and even if they were both exactly the same, which they are not, the terms would in any case be different. One day if we ever understand the differences we will add some more information.

LDP: Label Distribution Protocol Overview

LDP: Label Distribution Protocol Overview

Label Distribution Protocol (LDP) is a key protocol in the MPLS (Multi Protocol Label Switching) architecture. In the MPLS network, 2 label switching routers (LSR) must agree on the meaning of the labels used to forward traffic between and through them. LDP defines a set of procedures and messages by which one LSR (Label Switched Router) informs another of the label bindings it has made. The LSR uses this protocol to establish label switched paths through a network by mapping network layer routing information directly to data-link layer switched paths.
Two LSRs (Label Switched Routers) which use LDP to exchange label mapping information are known as LDP peers and they have an LDP session between them. In a single session, each peer is able to learn about the others label mappings, in other words, the protocol is bi-directional.

OSPF LSA

OSPF -- LSA -- Type

Jitter Buffer - PDV in TDM

Introduction -- TDM-over-Packet -- Jitter Buffer - PDV

The DS34T10x and DS34S10x families of TDM-over-Packet (TDMoP) devices use jitter buffers to compensate for the packet-delay variation (PDV) that is present in packet networks. These buffers are independently configurable on a per-bundle or per-connection basis. Additionally, they are dynamically adjustable, allowing them to be adapted in real-time to changes in the performance characteristics of the packet network. This application note discusses the jitter buffer controller and how to set its parameters to minimize the effects of PDV during TDM clock recovery.DS34T10x comprises the DS34T101, DS34T102, DS34T104, and DS34T108; DS34S10x comprises the DS34S101, DS34S102, DS34S104, and DS34S108.

Timing in a TDM Network

Variations in packet arrival time, called jitter, occur because of network congestion, timing drift, or route changes. Thus, when replacing the physical TDM connection with an IP/MPLS network and two TDMoP devices ,the receiving TDMoP device (slave) receives TDMoP packets with variable delays in arrival time.After processing the packets, the device should send TDM data to the TDM side at the constant rate of the TDM network to minimize the effects of this jitter. To achieve this constant data rate, the device works in clock-recovery mode to reconstruct the source TDM clock so that the destination TDM device can still work in loopback timing mode

There are two kinds of jitter buffers: static and dynamic. The static jitter buffer is hardware-based and is configured by the manufacturer. The dynamic jitter buffer is software-based and can be configured by a network administrator to adapt to changes in the network's delay and PDV.

Types of Pseudowires

Introduction to TDM Pseudowires

Pseudowires(PWs) as a technology originate from the contributions made to
the IETF PWE3 working group, which defined the transport of legacy layer 2
services over an MPLS network. These papers were coined the Martini Drafts
(some were wryly dubbed Dry Martini) after one of the lead authors, Luca
Martini. As such, pseudowires have been in existence for nearly a decade,
mainly in the core and edge of the network, typically transporting ATM and
Frame Relay traffic over a carrier IP network.
RAD has pioneered TDM pseudowires in the access sector, introducing a TDM
pseudowire technology in 1999 at ITU World Telecom in Geneva. Known as
TDMoIP®, this implementation extended the original pseudowire definition into
the access network and to the customer premises. This technology has
enabled carriers and corporate customers alike to provide TDM connectivity
and services over a packet network. TDMoIP pseudowire supports all types of
TDM services: framed, unframed, with or without Channel Associated Signaling
(CAS), enabling a smooth migration to packet networks.

Available Pseudowire Types

Following the successful deployment of TDMoIP gateways by RAD, other
flavors of TDM pseudowires have been developed under the aegis of the IETF.
These pseudowires are known as Circuit Emulation over PSN (CESoPSN) and
Structure Agnostic TDM over Packet (SAToP).

CESoPSN TDM pseudowire technology supports framed and channelized TDM
services over packet switched networks. The main difference between TDMoIP
and CESoPSN is the way CESoPSN packetizes the TDM data. Where TDMoIP
packetizes TDM data in multiples of 48 bytes, CESoPSN uses multiples of the
TDM frame itself.

SAToP (RFC 4553), or Structure Agnostic TDM over Packet, is a TDM
pseudowire technology that differs from TDMoIP and CESoPSN in that it treats
the TDM traffic as a data stream and ignores the framing or the timeslots
(DS0). It provides functionality similar to TDMoIP in its unframed mode.

1] SAToP -- Unframed

2] TDMoIP -- Unfraed , Framed , Channelized

3] CESoPSN -- Framed , Channelized.

VPLS Configuration

VPLS Configuration : The Future

VPLS allows multiple Ethernet LANs from different customer sites to be connected together across the service
provider (SP) network, thereby emulating a single Ethernet LAN segment for that customer.

SP network providing VPLS services in which multiple customer sites (belonging to Customer A) can communicate
as if they are connected as a private Ethernet LAN segment. VPLS uses Multiprotocol Label Switching (MPLS) to
offer multipoint Ethernet connectivity over a mesh of logical circuits or tunnels, with the added benefits of Traffic
Engineering (TE), resilience, and failover. VPLS enables carriers and SPs to offer managed Ethernet VPN services
easily and cost effectively

MPLS Service Provider Configuration

MPLS Service Provider Configuration












Here is the basic configuration of MPLS Service Provider with Route Reflector


!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname Cust_C_1
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
!
!
ip cef
no ip domain lookup
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Loopback10
ip address 10.1.1.1 255.255.255.0
!
interface Loopback20
ip address 10.1.2.1 255.255.255.0
!
interface Loopback30
ip address 10.1.3.1 255.255.255.0
!
interface FastEthernet0/0
ip address 51.1.1.4 255.255.255.0
duplex auto
speed auto
!
interface FastEthernet0/0.30
encapsulation dot1Q 30
ip address 10.250.30.2 255.255.255.252
!
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet1/0
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet1/1
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet2/0
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet2/1
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet3/0
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet3/1
no ip address
shutdown
duplex auto
speed auto
!
router ospf 10
log-adjacency-changes
network 10.1.1.0 0.0.0.255 area 0
network 10.1.2.0 0.0.0.255 area 0
network 10.1.3.0 0.0.0.255 area 0
network 10.250.30.0 0.0.0.3 area 0
!
!
no ip http server
no ip http secure-server
!
!
!
!
!
!
control-plane
!
!
!
!
!
!
gatekeeper
shutdown
!
!
line con 0
stopbits 1
line aux 0
stopbits 1
line vty 0 4
login
!
!
end



!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname Cust_B_1
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
!
!
ip cef
no ip domain lookup
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Loopback10
ip address 10.1.1.1 255.255.255.0
!
interface Loopback20
ip address 10.1.2.1 255.255.255.0
!
interface Loopback30
ip address 10.1.3.1 255.255.255.0
!
interface FastEthernet0/0
ip address 51.1.1.3 255.255.255.0
duplex auto
speed auto
!
interface FastEthernet0/0.20
encapsulation dot1Q 20
ip address 10.250.20.2 255.255.255.252
!
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet1/0
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet1/1
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet2/0
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet2/1
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet3/0
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet3/1
no ip address
shutdown
duplex auto
speed auto
!
router eigrp 10
network 10.0.0.0
no auto-summary
!
!
no ip http server
no ip http secure-server
!
!
!
!
!
!
control-plane
!
!
!
!
!
!
gatekeeper
shutdown
!
!
line con 0
stopbits 1
line aux 0
stopbits 1
line vty 0 4
login
!
!
end


!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname Cust_A_1
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
!
!
ip cef
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Loopback10
ip address 10.1.1.1 255.255.255.0
!
interface Loopback20
ip address 10.1.2.1 255.255.255.0
!
interface Loopback30
ip address 10.1.3.1 255.255.255.0
!
interface FastEthernet0/0
ip address 51.1.1.2 255.255.255.0
duplex auto
speed auto
!
interface FastEthernet0/0.10
encapsulation dot1Q 10
ip address 10.250.10.2 255.255.255.252
!
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet1/0
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet1/1
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet2/0
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet2/1
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet3/0
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet3/1
no ip address
shutdown
duplex auto
speed auto
!
router rip
version 2
network 10.0.0.0
no auto-summary
!
!
no ip http server
no ip http secure-server
!
!
!
!
!
!
control-plane
!
!
!
!
!
!
gatekeeper
shutdown
!
!
line con 0
stopbits 1
line aux 0
stopbits 1
line vty 0 4
login
!
!
end



!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname PE_1
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
!
!
ip cef
no ip domain lookup
!
!
ip vrf CUST_A
rd 65000:100
route-target export 65000:100
route-target import 65000:100
!
ip vrf CUST_B
rd 65000:200
route-target export 65000:200
route-target import 65000:200
!
ip vrf CUST_C
rd 65000:300
route-target export 65000:300
route-target import 65000:300
!
no mpls ip propagate-ttl
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Loopback1
description **** MPLS Lookback ****
ip address 1.1.1.1 255.255.255.255
!
interface FastEthernet0/0
ip address 51.1.1.1 255.255.255.0
duplex auto
speed auto
!
interface FastEthernet0/0.10
description description ***** Connected To Cust_A_1 *****
encapsulation dot1Q 10
ip vrf forwarding CUST_A
ip address 10.250.10.1 255.255.255.252
!
interface FastEthernet0/0.20
description description ***** Connected To Cust_B_1 *****
encapsulation dot1Q 20
ip vrf forwarding CUST_B
ip address 10.250.20.1 255.255.255.252
!
interface FastEthernet0/0.30
description description ***** Connected To Cust_C_1 *****
encapsulation dot1Q 30
ip vrf forwarding CUST_C
ip address 10.250.30.1 255.255.255.252
!
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet1/0
description ***** Connected To P_CORE_ROUTER *****
ip address 172.16.1.1 255.255.255.252
duplex auto
speed auto
mpls label protocol ldp
mpls ip
!
interface FastEthernet1/1
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet2/0
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet2/1
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet3/0
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet3/1
no ip address
shutdown
duplex auto
speed auto
!
router eigrp 1
no auto-summary
!
address-family ipv4 vrf CUST_B
redistribute bgp 65000 metric 1000 10 255 1 1
network 10.0.0.0
no auto-summary
autonomous-system 10
exit-address-family
!
router ospf 10 vrf CUST_C
log-adjacency-changes
redistribute bgp 65000 subnets
network 10.250.30.0 0.0.0.3 area 0
!
router ospf 100
router-id 1.1.1.1
log-adjacency-changes
passive-interface default
no passive-interface FastEthernet1/0
network 1.1.1.0 0.0.0.255 area 0
network 172.16.1.0 0.0.0.3 area 0
!
router rip
no auto-summary
!
address-family ipv4 vrf CUST_A
redistribute bgp 65000 metric 5
network 10.0.0.0
no auto-summary
version 2
exit-address-family
!
router bgp 65000
bgp log-neighbor-changes
neighbor 5.5.5.5 remote-as 65000
neighbor 5.5.5.5 update-source Loopback1
!
address-family ipv4
neighbor 5.5.5.5 activate
no auto-summary
no synchronization
exit-address-family
!
address-family vpnv4
neighbor 5.5.5.5 activate
neighbor 5.5.5.5 send-community extended
exit-address-family
!
address-family ipv4 vrf CUST_C
redistribute ospf 10 vrf CUST_C
no synchronization
exit-address-family
!
address-family ipv4 vrf CUST_B
redistribute eigrp 10
no synchronization
exit-address-family
!
address-family ipv4 vrf CUST_A
redistribute rip
no synchronization
exit-address-family
!
!
no ip http server
no ip http secure-server
!
!
!
!
mpls ldp router-id Loopback1
!
!
control-plane
!
!
!
!
!
!
gatekeeper
shutdown
!
!
line con 0
stopbits 1
line aux 0
stopbits 1
line vty 0 4
login
!
!
end



!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname PE_2
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
!
!
ip cef
no ip domain lookup
!
!
ip vrf CUST_A
rd 65000:100
route-target export 65000:100
route-target import 65000:100
!
ip vrf CUST_B
rd 65000:200
route-target export 65000:200
route-target import 65000:200
!
ip vrf CUST_C
rd 65000:300
route-target export 65000:300
route-target import 65000:300
!
ip vrf forwarding
!
no mpls ip propagate-ttl
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Loopback1
description **** MPLS Loopback ****
ip address 2.2.2.2 255.255.255.255
!
interface FastEthernet0/0
description description ***** Connected To P_CORE_ROUTER *****
ip address 172.16.2.2 255.255.255.252
duplex auto
speed auto
mpls label protocol ldp
mpls ip
!
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet1/0
ip address 60.1.1.1 255.255.255.0
duplex auto
speed auto
!
interface FastEthernet1/0.10
description description ***** Connected To Cust_A_2 *****
encapsulation dot1Q 10
ip vrf forwarding CUST_A
ip address 10.240.10.1 255.255.255.252
!
interface FastEthernet1/0.20
description description ***** Connected To Cust_B_2 *****
encapsulation dot1Q 20
ip vrf forwarding CUST_B
ip address 10.240.20.1 255.255.255.252
!
interface FastEthernet1/0.30
description description ***** Connected To Cust_C_2 *****
encapsulation dot1Q 30
ip vrf forwarding CUST_C
ip address 10.240.30.1 255.255.255.252
!
interface FastEthernet1/1
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet2/0
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet2/1
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet3/0
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet3/1
no ip address
shutdown
duplex auto
speed auto
!
router eigrp 1
no auto-summary
!
address-family ipv4 vrf CUST_B
redistribute bgp 65000 metric 1000 10 255 1 1
network 10.0.0.0
auto-summary
autonomous-system 10
exit-address-family
!
router ospf 10 vrf CUST_C
log-adjacency-changes
redistribute bgp 65000 subnets
network 10.240.30.0 0.0.0.3 area 0
!
router ospf 100
router-id 2.2.2.2
log-adjacency-changes
passive-interface default
no passive-interface FastEthernet0/0
network 2.2.2.2 0.0.0.0 area 0
network 172.16.2.0 0.0.0.3 area 0
!
router rip
no auto-summary
!
address-family ipv4 vrf CUST_A
redistribute bgp 65000 metric 5
network 10.0.0.0
no auto-summary
version 2
exit-address-family
!
router bgp 65000
bgp log-neighbor-changes
neighbor 5.5.5.5 remote-as 65000
neighbor 5.5.5.5 update-source Loopback1
!
address-family ipv4
neighbor 5.5.5.5 activate
no auto-summary
no synchronization
exit-address-family
!
address-family vpnv4
neighbor 5.5.5.5 activate
neighbor 5.5.5.5 send-community extended
exit-address-family
!
address-family ipv4 vrf CUST_C
redistribute ospf 10 vrf CUST_C
no synchronization
exit-address-family
!
address-family ipv4 vrf CUST_B
redistribute eigrp 10
no synchronization
exit-address-family
!
address-family ipv4 vrf CUST_A
redistribute rip
no synchronization
exit-address-family
!
!
no ip http server
no ip http secure-server
!
!
!
!
mpls ldp router-id Loopback1
!
!
control-plane
!
!
!
!
!
!
gatekeeper
shutdown
!
!
line con 0
stopbits 1
line aux 0
stopbits 1
line vty 0 4
login
!
!
end



!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname Cust_A_2
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
!
!
ip cef
no ip domain lookup
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Loopback10
ip address 20.1.1.1 255.255.255.0
!
interface Loopback20
ip address 20.1.2.1 255.255.255.0
!
interface Loopback30
ip address 20.1.3.1 255.255.255.0
!
interface FastEthernet0/0
description description ***** Connected To PE_2 *****
ip address 60.1.1.2 255.255.255.0
duplex auto
speed auto
!
interface FastEthernet0/0.10
description description ***** Connected To PE_2 *****
encapsulation dot1Q 10
ip address 10.240.10.2 255.255.255.252
!
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet1/0
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet1/1
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet2/0
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet2/1
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet3/0
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet3/1
no ip address
shutdown
duplex auto
speed auto
!
router rip
version 2
network 10.0.0.0
network 20.0.0.0
no auto-summary
!
!
no ip http server
no ip http secure-server
!
!
!
!
!
!
control-plane
!
!
!
!
!
!
gatekeeper
shutdown
!
!
line con 0
stopbits 1
line aux 0
stopbits 1
line vty 0 4
login
!
!
end




!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname Cust_B_2
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
!
!
ip cef
no ip domain lookup
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Loopback10
ip address 20.1.1.1 255.255.255.0
!
interface Loopback20
ip address 20.1.2.1 255.255.255.0
!
interface Loopback30
ip address 20.1.3.1 255.255.255.0
!
interface FastEthernet0/0
description description ***** Connected To PE_2 *****
ip address 60.1.1.3 255.255.255.0
duplex auto
speed auto
!
interface FastEthernet0/0.20
description description ***** Connected To PE_2 *****
encapsulation dot1Q 20
ip address 10.240.20.2 255.255.255.252
!
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet1/0
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet1/1
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet2/0
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet2/1
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet3/0
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet3/1
no ip address
shutdown
duplex auto
speed auto
!
router eigrp 10
network 10.0.0.0
network 20.0.0.0
no auto-summary
!
!
no ip http server
no ip http secure-server
!
!
!
!
!
!
control-plane
!
!
!
!
!
!
gatekeeper
shutdown
!
!
line con 0
stopbits 1
line aux 0
stopbits 1
line vty 0 4
login
!
!
end



!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname Cust_C_2
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
!
!
ip cef
no ip domain lookup
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Loopback10
ip address 20.1.1.1 255.255.255.0
!
interface Loopback20
ip address 20.1.2.1 255.255.255.0
!
interface Loopback30
ip address 20.1.3.1 255.255.255.0
!
interface FastEthernet0/0
description description ***** Connected To PE_2 *****
ip address 60.1.1.4 255.255.255.0
duplex auto
speed auto
!
interface FastEthernet0/0.30
description description ***** Connected To PE_2 *****
encapsulation dot1Q 30
ip address 10.240.30.2 255.255.255.252
!
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet1/0
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet1/1
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet2/0
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet2/1
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet3/0
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet3/1
no ip address
shutdown
duplex auto
speed auto
!
router ospf 10
log-adjacency-changes
network 10.240.30.0 0.0.0.3 area 0
network 20.1.1.0 0.0.0.255 area 0
network 20.1.2.0 0.0.0.255 area 0
network 20.1.3.0 0.0.0.255 area 0
!
!
no ip http server
no ip http secure-server
!
!
!
!
!
!
control-plane
!
!
!
!
!
!
gatekeeper
shutdown
!
!
line con 0
stopbits 1
line aux 0
stopbits 1
line vty 0 4
login
!
!
end



!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname P_CORE_ROUTER
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
!
!
ip cef
no ip domain lookup
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Loopback1
description **** MPLS Loopback ****
ip address 5.5.5.5 255.255.255.255
!
interface FastEthernet0/0
description description ***** Connected To PE_2 *****
ip address 172.16.2.1 255.255.255.252
duplex auto
speed auto
mpls label protocol ldp
mpls ip
!
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet1/0
description description ***** Connected To PE_1 *****
ip address 172.16.1.2 255.255.255.252
duplex auto
speed auto
mpls label protocol ldp
mpls ip
!
interface FastEthernet1/1
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet2/0
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet2/1
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet3/0
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet3/1
no ip address
shutdown
duplex auto
speed auto
!
router ospf 100
router-id 5.5.5.5
log-adjacency-changes
network 5.5.5.5 0.0.0.0 area 0
network 172.16.1.0 0.0.0.3 area 0
network 172.16.2.0 0.0.0.3 area 0
!
router bgp 65000
bgp log-neighbor-changes
neighbor 1.1.1.1 remote-as 65000
neighbor 1.1.1.1 update-source Loopback1
neighbor 2.2.2.2 remote-as 65000
neighbor 2.2.2.2 update-source Loopback1
!
address-family ipv4
neighbor 1.1.1.1 activate
neighbor 2.2.2.2 activate
no auto-summary
no synchronization
exit-address-family
!
address-family vpnv4
neighbor 1.1.1.1 activate
neighbor 1.1.1.1 send-community extended
neighbor 1.1.1.1 route-reflector-client
neighbor 2.2.2.2 activate
neighbor 2.2.2.2 send-community extended
neighbor 2.2.2.2 route-reflector-client
exit-address-family
!
!
no ip http server
no ip http secure-server
!
!
!
!
mpls ldp router-id Loopback1
!
!
control-plane
!
!
!
!
!
!
gatekeeper
shutdown
!
!
line con 0
stopbits 1
line aux 0
stopbits 1
line vty 0 4
login
!
!
end