Ads 468x60px

Wednesday, August 25, 2010

Basic MPLS

This post is for new engineers, those who are learning MPLS L3 VPN. This post include a link of full lab with configuration files.
In this Lab vrf VPN_A from PE to CE , I used BGP and OSPF. For vrf VPN_B EIGRP and static. So Here you will find basic configuration of all protocols between CE to PE. Same time you will see the redistribution.

This topology I am going to use for configurations.
1.       R1 and R6 are in vrf VPN_A,R1 is using BGP to exchange the routes with PE-1 and R6 is using OSPF to share the routes with PE-2.
2.       R7 and R8 are in vrf VPN_B, R7 is using EIGRP to exchange the routes with PE-1 and R8 is using static routes with PE-2.
3.       In Core, OSPF is used as IGP.
4.       MP-IBGP is configured in PE-1 and PE-2.
Here is PE 1 and PE-2 configurations, Download full lab and configuration from link.

PE-1

hostname PE-1
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
memory-size iomem 5
ip cef
!

!
!
ip vrf VPN_A
 rd 100:1
 route-target export 100:1
 route-target import 100:1
!
ip vrf VPN_B
 rd 100:2
 route-target export 100:2
 route-target import 100:2
!
no ip domain lookup
!
mpls label protocol ldp
!
!
interface Loopback0
 ip address 100.1.1.1 255.255.255.255
!
interface FastEthernet0/0
 no ip address
 duplex auto
 speed auto
!
interface FastEthernet0/0.10
 encapsulation dot1Q 10
 ip vrf forwarding VPN_A
 ip address 10.1.1.2 255.255.255.252
!
interface FastEthernet0/0.30
 encapsulation dot1Q 30
 ip vrf forwarding VPN_B
 ip address 192.168.1.2 255.255.255.252
!
interface FastEthernet0/1
 ip address 172.16.1.1 255.255.255.252
 duplex auto
 speed auto
 mpls label protocol ldp
 mpls ip
!
!
router eigrp 200
 auto-summary
 !
 address-family ipv4 vrf VPN_B
 redistribute bgp 100 metric 256 20 200 100 20
 network 192.168.1.0 0.0.0.3
 no auto-summary
 autonomous-system 100
 exit-address-family
!
router ospf 1
 log-adjacency-changes
 network 100.1.1.1 0.0.0.0 area 0
 network 172.16.1.0 0.0.0.3 area 0
!
router bgp 100
 bgp log-neighbor-changes
 neighbor 100.1.1.3 remote-as 100
 neighbor 100.1.1.3 update-source Loopback0
 !
 address-family ipv4
 neighbor 100.1.1.3 activate
 neighbor 100.1.1.3 next-hop-self
 no auto-summary
 no synchronization
 exit-address-family
 !
 address-family vpnv4
 neighbor 100.1.1.3 activate
 neighbor 100.1.1.3 send-community extended
 neighbor 100.1.1.3 next-hop-self
 exit-address-family
 !
 address-family ipv4 vrf VPN_B
 redistribute eigrp 100
 no synchronization
 exit-address-family
 !
 address-family ipv4 vrf VPN_A
 neighbor 10.1.1.1 remote-as 200
 neighbor 10.1.1.1 activate
 no synchronization
 exit-address-family
!
ip http server
no ip http secure-server
!
!
control-plane

!
line con 0
line aux 0
line vty 0 4
!
!
end

PE-2:

hostname PE-2
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
memory-size iomem 5
ip cef
!
!
!
!
ip vrf VPN_A
 rd 100:1
 route-target export 100:1
 route-target import 100:1
!
ip vrf VPN_B
 rd 100:2
 route-target export 100:2
 route-target import 100:2
!
no ip domain lookup
!
mpls label protocol ldp
!
interface Loopback0
 ip address 100.1.1.3 255.255.255.255
!
interface FastEthernet0/0
 ip address 172.17.1.2 255.255.255.252
 duplex auto
 speed auto
 mpls label protocol ldp
 mpls ip
!
interface FastEthernet0/1
 no ip address
 duplex auto
 speed auto
!
interface FastEthernet0/1.20
 encapsulation dot1Q 20
 ip vrf forwarding VPN_A
 ip address 20.1.1.2 255.255.255.252
!
interface FastEthernet0/1.40
 encapsulation dot1Q 40
 ip vrf forwarding VPN_B
 ip address 192.168.2.2 255.255.255.252
!
!
router ospf 2 vrf VPN_A
 log-adjacency-changes
 redistribute bgp 100 subnets
 network 20.1.1.0 0.0.0.3 area 0
!
router ospf 1
 log-adjacency-changes
 network 100.1.1.3 0.0.0.0 area 0
 network 172.17.1.0 0.0.0.3 area 0
!
router bgp 100
 no synchronization
 bgp log-neighbor-changes
 neighbor 100.1.1.1 remote-as 100
 neighbor 100.1.1.1 update-source Loopback0
 neighbor 100.1.1.1 next-hop-self
 no auto-summary
 !
 address-family vpnv4
 neighbor 100.1.1.1 activate
 neighbor 100.1.1.1 send-community extended
 neighbor 100.1.1.1 next-hop-self
 exit-address-family
 !
 address-family ipv4 vrf VPN_B
 redistribute connected
 redistribute static
 no synchronization
 exit-address-family
 !
 address-family ipv4 vrf VPN_A
 redistribute ospf 2 vrf VPN_A
 no synchronization
 exit-address-family
!
ip route vrf VPN_B 6.6.6.6 255.255.255.255 192.168.2.1
!
!
ip http server
no ip http secure-server
!
!
control-plane
!
!
line con 0
line aux 0
line vty 0 4
!
!
end

LAB Link :
http://www.ziddu.com/download/11368307/basicmpls.rar.html

I hope this lab will helpful for beginners.Post comments for any queries.






Posted by Uttamkumar at 12:55 PM 11 comments
Labels:

Wednesday, August 18, 2010

OSPF Network Types






  • Here we will discuss, what are the OSPF network type’s which supports on interface level to form adjacency. Some time we have to configure different network types in OSPF configuration as per network requirement. Let’s see what they are,

    *But before you will read more… To run OSPF network, we preferably use same network type in network, but if in such conditions when we have to configure OSPF between different OSPF network types, what we have to do? It is possible but till some extent by tuning hello and dead timers.
    You can use different OSPF types as mentioned below:
    Point-to-Point with Point to Multipoint (Tune hello and dead timers)
    Broadcast with NON-broadcast (Tune hello and dead timers)
    Let me know what your results…are. It will work.

    Below are OSPF network types:

    Point to Point networks:
    This network type works on point to point networks. If you are using this network type, no DR/BDR selection in this network, 10 sec hello timer and 40 sec is dead timer, Routers will communicate to only one multicast IP address 224.0.0.5.
    This network type is majorly used between two routers.

    Broadcast:
    This network type works on Ethernet networks/Shared media. In this network DR/BDR elected for further communication between Routers. In this every router can reach each other, so it is Multi access. 10 sec hello timers and 40 sec dead timers, in this network type router will communicate to two multicast IP address 224.0.0.5 and 224.0.0.6.

    NBMA, Multi-access networks:  This is having five modes which we can use, two are industry standard and three are Cisco proprietary.

    Non Broadcast mode –
          It’s a default mode for frame relay networks and ATM networks.
    In this mode no broadcast and multicast are allowed, so here is issue. How the OSPF neighborship is going to form. We have to statically configure neighbors with neighbor statements in Hub location/DR, the router will communicate to neighbors by unicast.

    router ospf 1
    neighbor x.x.x.x priority 0

    This mode acts like a LAN environment, So DR and BDR selection will happen. (Full state with DR/BDR)
    The whole network should be in one single subnet.
    30 sec hello timers and 120 sec dead timers.
    In frame relay network make sure about frame relay map statements to all neighbors with same DLCI. They should able to ping each other.

    Point to Multipoint mode –
         No DR/BDR in this mode. It overcomes the limitations Non- broadcast mode, No need of extra frame map statements. The whole network should be in same subnet. 30 sec hello timers and 120 sec dead timers. No need to configure neighbor statement manually. Each router will be in full state with each other. It allows broadcast and multicast in network, so neighborship is auto discovered.

    ip ospf network point-to-multipoint

    Point to Multipoint, NON- broadcast mode – (Cisco)


    • It is Cisco proprietary mode, This is same like Point to multipoint mode, But in this broadcast are not allowed, So we have to configure the neighbors manually with neighbor statements in OSPF Process and same time in interface specify the network type –                                                                                                                                                



    Router(config-if)#ip ospf network point-to-multipoint ?
     non-broadcast  Specify non-broadcast point-to-mpoint network 

    In this also NO DR/BDR elections and network should be in one single subnet.

    Broadcast mode – (Cisco)


    • It works like LAN network in NBMA cloud. But Full mesh is required in this network, one subnet is required in network. DR/BDR is elected. Neighbors are auto discovered. 



    Syntax – ip ospf network broadcast.

    Point-to-Point Mode – (Cisco)
    Use separate sub interfaces, No DR/BDR is elected, requires different subnets, Neighbors auto discovered.

    This networks are depends on network design and your preference.
Posted by Uttamkumar at 1:44 PM 123 comments
Labels:
Subscribe to: Posts (Atom)
Related Posts Plugin for WordPress, Blogger...