BGP Path Manipulations

Applied Advanced Routing Project BY Lokesh Galla Isaac Ledoux Djomo Mambou Tayebeh Taheri

Abstract Unlike other IGP (Interior Gateway Protocol) routing protocols, BGP is design as EGP (Exterior Gateway Protocol) to following the fastest routing path. BGP is design to manipulate traffic with the efficient ways. Manipulating traffic policies can have huge impact on an autonomous system (AS). This paper is about BGP manipulation and the role of the various attributes to obtain different results. We will start by examining the flow of traffic for five autonomous systems with their default settings of BGP. BGP routes that took by the various autonomous systems to reach another autonomous system had been captured and illustrated. Our approach will be by starting a default system with all the AS and later manipulating the various attributes and observe the flow of traffic. Our research provides a model of a better understanding of BGP, and its path manipulation.

Table of Contents
Abstract ................................................................................................................................................ 0 Introduction: ......................................................................................................................................... 2 Background: ......................................................................................................................................... 3 BGP Attributes: .................................................................................................................................... 5 BGP Path Manipulation: ...................................................................................................................... 6 Implementation work: .......................................................................................................................... 7 Scenario 1:............................................................................................................................................ 8 Results: ................................................................................................................................................. 8 Scenario 2:............................................................................................................................................ 9 Results: ................................................................................................................................................. 9 Conclusions: ....................................................................................................................................... 11 Reference: .......................................................................................................................................... 11 Appendix: ........................................................................................................................................... 11 Configurations Scenario 1:................................................................................................................. 11 Configurations Scenario 2:................................................................................................................. 23

Introduction: The time Internet was newly discovered, it was much easier to route packet to their final destination. The number of users was small and the requirements were used simple routing protocol. But as the number of users began to grow steadily, it was the interest of ISP to control traffic flowed for economic and political reasons. BGP was discovered to solve the need of route selection, manipulation and propagation. The flexibility of BGP is one of its unique characteristics and its ability to connect together different autonomous system. The only requirement for BGP connection is that a router must connect to at least one AS BGP router. BGP uses path vector protocol and presently, there has been much modification on BGP that would allow ISP to manage and control the flow of traffic with the objective to minimize their resources while sending packet to their destination as quickly as possible. A poorly design or selection of attributes in BGP can cause enormous problem such security problem, vast or resources, congestion etc. So it is the responsibility of the ISP to manage resources in BGP to avoid under or over utilization of resources. Exchange of Information about the reachable network is also another major task for BGP. This exchange of information includes a list of autonomous systems and a BGP router uses this information from a BGP router to build a routing table of autonomous systems. Each autonomous system is identifying by a unique number and a path is form when two autonomous systems are connected which is also a route to a destination. BGP is assuming not to know anything about the functions within the AS which is a very important prerequisite for AS. This factor makes that AS to be autonomous and has it own topology, makes decision about route determination. The responsibility of BGP is to share information gotten from an AS with other ASs. When two AS's agrees to exchange routing information, each AS will assign a router that will speak BGP on its behalf and the two router exchanging information are said to be BGP peers and they are usually at the edge or border of the AS.

Background: The goal of this research is to investigate the optimal use of some of the attributes to control the flow of traffic, utilization of these links and capacity constraint. BGP is the only inter-domain routing protocol used by the internet that allows each autonomous system to make decision on its routing policies and to override some policies in favour of some. However because each autonomous system can make their own routing policies, these policies can conflict resulting in persistent route oscillations. In this research, some of the important features of BGP will be discuss. Characteristics of BGP: There are lots of differences between BGP and other routing protocol. In this section we would consider some of the distinct characteristics of BGP compare to the IGP protocols. -> Inter-AS Configuration: BGPs establish connection or communication between two autonomous. -> Next-Hop: Information about the next hop to a destination is provided by BGP which is similar to RIP, EIGRP. BGP communicate among multiple BGP speakers with AS. An AS has more than one router and each of these router is communicating with a peer in other AS , a form of coordination is needed among routers to ensure that they all propagate same information. ->Path information: Path information is advertised by BGP together with the reachable destination and the next destination. This would cause the receiver to learn all the AS along the path to that destination. ->Policy support: An administrator can use BGP to implement policies by configuration. This feature is quite unique compare to other distance-vector protocol. For example, route learn within an AS and route learn from outside can be distinguish by simple BGP configuration. ->Runs over TCP: In other to ensure reliability, BGP uses TCP for all communication. ->Conserve network bandwidth: During message updates, BGP doesn't send complete information on each updates. Complete information is send once and other information coming after only carries the incremental changes. These changes are called deltas. This process helps to save bandwidth. Routes information

aggregation by senders with multiple destinations represented by a single route also help to saved bandwidth. ->Support s CIDR: CIDR is supported by BGP which allows network mask to be sent along with addresses. ->Security: Verifying the authentication of the message. BGP Functionality and Route Information Management BGP facilitate the exchange of routing information between AS's and each router running BGP uses these information and their description to established efficient route to each network. This information and their description include the main data that work with BGP devices. BGP peers have three main functions. The first function is about peer acquisition and authentication which is about peers establishing a TCP connection and message exchange as a sign of acceptance to communicate. The second functionality is about sending reachability information which can be positive or negative which the third functionality is about connection verification that is both the peers and the network are connected. It is the responsibility of every BGP speaker to use specific guidelines to manage route description. BGP Route Information Management Functions Route information management can be considered to comprise of four main tasks. i) Route Storage: Routing information received from other routers is store in a database. So that the database contains information on how to reach the various network. ii) Route Update: When an update is received, BGP uses special techniques to determine how to use the received information from a peer to update the other routers. iii) Route Selection: in other to select good and efficient route BGP must use information in it route database. iv) Route Advertisement: BGP uses the BGP update message to inform its peers about other reachable network. BGP Messages: There are four types of messages.

i) OPEN Message: This message is send after a TCP connection has been established BGP peers. Open message include exchange of AS number of the peers and other parameters. ii) UPDATE Messages: If connection has been established and acknowledgement received, BGP uses the update message to advertise the information it has on it database. This update message includes all reachable destinations. iii) Notification Message: In the presence of an error, the notification message is send to other BGP peers and TCP connection is close immediately. Error can come from different sources. iv) KeepAlive Message: This message type is use to test connectivity and functionality between BGP peers by periodically exchanging the KEEPALIVE message type.

BGP Attributes: In order to efficiently design and build a robust network, we must have knowledge about the BGP attributes use in path manipulation. BGP attributes are a set of properties which BGP uses to select the best route or to alter its route for administratively reasons. AS_path : This indicate a list of Autonomous System numbers through which a source must use to reach a destination. AS_path is use to detect routing loops and route calculation. Next hop: This is usually the next-hop router address used to reach a destination. In EBGP, the IP address that is used to reach the advertising router is the next-hop attributes. Weight: This is Cisco-defined attributes and this attributes is not advertised to neighbouring routers. A route with the highest weight to the same destination will be considered locally in case of multiple routes. Local preference: Use to make preference of a particular route by communicating

between BGP speakers in the same AS. When there are multi-exit points from an AS, this attributes is used to select the exit point of any specific route. Multi-exit discriminator: This is a value used to discriminate between one or more path for the purpose of selecting a prefer path. Origin: This is about the origin of a particular route. Path is either originated from IGP, EGP or other source and this attributes is also used for route selection. Community: This attribute allows the sharing of common routing policy such as acceptance and preference across multiple BGP peers that belongs to the same group. A set of policy is shared among BGP peers with similar properties.

Properties community attributes includes: No-exportRoute are not advertised to EBGP peer. No-advertiseRoute are not advertised to any peer. Internetroute is advertised to the internet community and all the routers that belongs to the network.

BGP Path Manipulation: The advertisement of a particular route can come from more than source which implies that BGP will have the task to select the best path and include it in its routing table. In case of just one route to a destination, this route is added in the routing table but when there exist multiple routes to a destinations, BGP uses some rules to determine which route to install. The following steps are a chronological order in which BGP uses to select a particular route. However, because of the flexibility of BGP, the administrator can manipulate these rules to favour of the selection of another route. -> consider the route with the highest weight (a local, Cisco-proprietary parameter). -> Consider the route with the highest local preference. -> Consider locally-originated routes compare those learned from a neighbour. -> Consider the route with the shortest AS path. -> Consider IGP-learned routes over those EGP or unknown origin. -> Consider the route with the lowest MED for route with the same next-hop AS. -> Consider EBGP-learned routes over IBGP-learned routes to facilitate egress from AS at the earliest opportunity. -> Consider the route whose next-hop address has the lowest IGP metric or smallest intra-domain to egress border router

-> Multipath determination -> In the existence of best path exists, consider it over newer routes. -> Consider the path from the router with the lowest router ID. -> In case the router IDs are the same, consider the lowest neighbour IP address. Implementation work: Implementation work is done in two scenarios. Scenario 1 is a basic set of BGP configurations along different ASs (autonomous systems). Scenario 2 is a path manipulation of BGP by administrator along with Scenario 1. In this project we are only interested in communication between NE 1 to NE 5 and NE 5 to NE 1. The topology for both scenarios looks like figure -1 below.

Loop100: 172.168.10. 1 Loop 200: 192.168.10.

Figure-1: Implementation topology IP address Scheme: Int / NE 1 NE 2 NE 3 NE 4 NE 5 Node Loopback 1.1.1.1 /32 2.2.2.2 / 32 0 Gig 0/0 10.10.10.1/24 10.10.10.2/24 Gig 0/1 10.10.11.1/24 10.10.11.2/24 40.40.40.2/24 Gig 0/2 20.20.20.1/24 30.30.30.1/24 30.30.30.2/24 Fa 0/0 192.168.10.1/24 192.168.10.2/24 Fa 0/1 20.20.20.2/24 40.40.40.1/24 Table-1: IP address table for Implementation topology.

Above table Table-1 represents the IP address scheme for each interface at the different nodes in the topology. Scenario 1: Main goal of the first scenario was to set up the network between different nodes and configure basic BGP protocol in the network topology. This scenario is to assess the BGP routing tables from node NE1 to NE5 and vice versa. Results: After successful connections has been made between NE1 as AS 6500 to NE5 as AS 6800. There are two ways to reach the destination from NE1 to NE5 and vice versa. Below figure-2 explains the trace route from NE1 to NE5.

Figure-2: NE1 trace-route topology From Figure-2 trace route explains the path it took to reach from NE1 to NE5 in the topology. First Path selected: NE1---> NE3 ---> NE4 --> NE5 Another second existed path: NE1 --> NE2 ---> NE5 Reason behind the selection of the first path even though another path existed was that BGP sees only AS_path to reach the destination. According to the topology NE3 and NE4 are in the same topology as AS (6700) . BGP notices that to reach NE5 from NE1, there are two paths, one either NE2 AS (6900) or NE3 AS (6700).From NE1,

there are two hops of AS-path to reach the destination. Basically if all BGP attributes are same it will consider lowest AS number as next hop to reach the destination. In this case via NE3 has less AS number than NE2. Scenario 2: Scenario 2 is configured by the administrator by one of the BGP attributes to control the traffic flow between NE1 to NE5. This scenario is extension of Scenario 1. As an administrator felt that to reach NE5 from NE1 was via NE2 is the best path. The reason was that link between NE1 to NE2 is dual homed, and it has only two hops distance to the destination. So an administrator used Local preference, one of BGP attributes for inbound traffic for BGP. Results: Results are as follows after local presence had been implemented on NE1 for inbound traffic.

Figure 3: Trace route from NE1 to NE5 From figure-3 explains the trace route that took form NE1 to NE5. Path Selected was NE1 --> NE2 --> NE5 as an administrator wished, not other like NE1 --> NE3 --> NE4 --> NE5 from Scenario 1.

Trace route Back from NE5 to NE1:

Figure -4: Trace route from NE5 to NE1 Since administrator doesnt specify the traffic from NE5 it uses same principles like Scenario 1 .Instead the traffic from NE5 took path via NE4 --> NE3 --> NE1. BGP Topology from NE1:

Figure 5: BGP Topology from NE1

Figure-5 Explains the BGP topology in NE1 to whole network in the project. Going in detailed, there are two paths to reach the NE5 network 40.40.40.0/24, but it selected next hop was 2.2.2.2 via NE2 because it has greater local preference value 500 than other path is 100 default. Conclusions: BGP is only the present EGP protocol running over the Internet. It is only protocol that uses path vector routing protocol. BGP supports different attributes to control the traffic flow. One of them is Local preference. It was used in this project to control the traffic. BGP required much more memory according to the network it connected; Because BGP has to maintain all paths for the specific destinations. BGP can become vital for poor configuration of attributes.

Reference: 1. http://nptel.iitk.ac.in/courses/Webcoursecontents/IIT%20Kharagpur/Computer%20networks/pdf/M7L4.pdf 2.http://www.utdallas.edu/~kxs028100/Papers/stable-paths-problem-andinterdomain-routing.pdf 3.http://infocom2003.ieee-infocom.org/papers/23_01.PDF Appendix: Configurations Scenario 1:

NE1#sh run Building configuration... Current configuration : 2055 bytes ! ! Last configuration change at 05:11:46 UTC Fri Jan 23 2015 ! NVRAM config last updated at 05:15:47 UTC Fri Jan 23 2015 ! NVRAM config last updated at 05:15:47 UTC Fri Jan 23 2015 version 15.1 service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname NE1 ! boot-start-marker boot-end-marker

! ! ! no aaa new-model ! ! no ipv6 cef ip source-route ip cef ! multilink bundle-name authenticated ! ! crypto pki token default removal timeout 0 ! ! license udi pid CISCO2911/K9 sn FCZ161920P6 ! ! ! redundancy ! ! ! ! ! ! ! ! ! ! ! interface Loopback0 ip address 1.1.1.1 255.255.255.255 ! interface Embedded-Service-Engine0/0 no ip address shutdown ! interface GigabitEthernet0/0 ip address 10.10.10.1 255.255.255.0 duplex auto speed auto ! interface GigabitEthernet0/1 ip address 10.10.11.1 255.255.255.0 duplex auto speed auto ! interface GigabitEthernet0/2 ip address 20.20.20.1 255.255.255.0

duplex auto speed auto ! interface Serial0/1/0 no ip address shutdown no fair-queue clock rate 64000 ! interface Serial0/1/1 no ip address shutdown clock rate 2000000 ! router bgp 6500 bgp log-neighbor-changes network 1.1.1.1 mask 255.255.255.255 network 10.10.10.0 mask 255.255.255.0 network 10.10.11.0 mask 255.255.255.0 network 20.20.20.0 mask 255.255.255.0 neighbor 2.2.2.2 remote-as 6900 neighbor 2.2.2.2 ebgp-multihop neighbor 2.2.2.2 next-hop-self neighbor 2.2.2.2 update-source Loopback0 neighbor 20.20.20.2 remote-as 6700 ! ip forward-protocol nd ! no ip http server no ip http secure-server ! ip route 2.2.2.2 255.255.255.255 10.10.11.2 ip route 2.2.2.2 255.255.255.255 10.10.10.2 ! ! ! ! ! ! ! ! control-plane ! ! ! line con 0 line aux 0 line 2 no activation-character no exec transport preferred none transport input all

transport output pad telnet rlogin lapb-ta mop udptn v120 ssh stopbits 1 line vty 0 4 login transport input all ! scheduler allocate 20000 1000 end -----------------------------------------------------------------------------------------------------------------------NE2#sh run Building configuration... Current configuration : 1732 bytes ! ! Last configuration change at 17:03:11 UTC Thu Jan 22 2009 version 15.1 service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname NE2 ! boot-start-marker boot-end-marker ! ! ! no aaa new-model ! ! no ipv6 cef ip source-route ip cef ! ! ! ! ! multilink bundle-name authenticated ! ! crypto pki token default removal timeout 0 ! ! license udi pid CISCO2911/K9 sn FCZ161920NX ! ! ! redundancy ! ! !

! ! ! ! ! ! ! interface Loopback0 ip address 2.2.2.2 255.255.255.255 ! interface Embedded-Service-Engine0/0 no ip address shutdown ! interface GigabitEthernet0/0 ip address 10.10.10.2 255.255.255.0 duplex auto speed auto ! interface GigabitEthernet0/1 ip address 10.10.11.2 255.255.255.0 duplex auto speed auto ! interface GigabitEthernet0/2 ip address 30.30.30.1 255.255.255.0 duplex auto speed auto ! interface Serial0/1/0 no ip address shutdown no fair-queue clock rate 2000000 ! interface Serial0/1/1 no ip address shutdown no fair-queue clock rate 2000000 ! router bgp 6900 bgp log-neighbor-changes network 10.10.10.0 mask 255.255.255.0 network 10.10.11.0 mask 255.255.255.0 network 30.30.30.0 mask 255.255.255.0 neighbor 2.2.2.2 remote-as 6500 neighbor 1.1.1.1 ebgp-multihop neighbor 1.1.1.1 next-hop-self neighbor 1.1.1.1 update-source Loopback0 neighbor 30.30.30.2 remote-as 6800 !

ip forward-protocol nd ! no ip http server no ip http secure-server ! ip route 1.1.1.1 255.255.255.255 10.10.10.1 ip route 1.1.1.1 255.255.255.255 10.10.11.1 ! ! ! ! ! ! ! control-plane ! ! ! line con 0 line aux 0 line 2 no activation-character no exec transport preferred none transport input all transport output pad telnet rlogin lapb-ta mop udptn v120 ssh stopbits 1 line vty 0 4 login transport input all ! scheduler allocate 20000 1000 end ----------------------------------------------------------------------------------------------------------------------NE3#sh run Building configuration... Current configuration : 1215 bytes ! version 12.4 service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname NE3 ! boot-start-marker boot-end-marker ! ! no aaa new-model

! resource policy ! memory-size iomem 5 mmi polling-interval 60 no mmi auto-configure no mmi pvc mmi snmp-timeout 180 ip subnet-zero ip cef ! ! ! ! ! ! voice-card 0 ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! interface FastEthernet0/0 ip address 192.168.10.1 255.255.255.0 duplex auto speed auto ! interface FastEthernet0/1 ip address 20.20.20.2 255.255.255.0 duplex auto speed auto ! interface Serial0/1/0 no ip address no fair-queue clock rate 125000

! interface Serial0/1/1 no ip address clock rate 125000 ! interface Serial0/2/0 no ip address shutdown clock rate 125000 ! interface Serial0/2/1 no ip address shutdown clock rate 125000 ! router bgp 6700 no synchronization bgp log-neighbor-changes network 20.20.20.0 mask 255.255.255.0 network 192.168.10.0 neighbor 20.20.20.1 remote-as 6500 neighbor 192.168.10.2 remote-as 6700 no auto-summary ! ip classless ! ! ip http server no ip http secure-server ! ! ! ! ! control-plane ! ! ! ! ! ! ! ! ! line con 0 line aux 0 line vty 0 4 login ! end ------------------------------------------------------------------------------------------------------------------------

NE4#sh run Building configuration... Current configuration : 1455 bytes ! ! Last configuration change at 11:49:22 UTC Mon Apr 14 2014 version 15.2 service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname NE4 ! boot-start-marker boot-end-marker ! ! ! no aaa new-model memory-size iomem 5 ! ip cef ! ! ! ! ! ! no ipv6 cef ! multilink bundle-name authenticated ! ! ! ! license udi pid CISCO2911/K9 sn FCZ172360Q9 ! ! ! redundancy ! ! ! ! ! ! ! ! ! ! ! !

! ! interface Embedded-Service-Engine0/0 no ip address shutdown ! interface GigabitEthernet0/0 ip address 192.168.10.2 255.255.255.0 duplex auto speed auto ! interface GigabitEthernet0/1 ip address 40.40.40.1 255.255.255.0 duplex auto speed auto ! interface GigabitEthernet0/2 no ip address shutdown duplex auto speed auto ! interface Serial0/0/0 no ip address shutdown clock rate 2000000 ! interface Serial0/0/1 no ip address shutdown clock rate 2000000 ! router bgp 6700 bgp log-neighbor-changes network 40.40.40.0 mask 255.255.255.0 network 192.168.10.0 neighbor 40.40.40.2 remote-as 6800 neighbor 192.168.10.1 remote-as 6700 ! ip forward-protocol nd ! ip http server no ip http secure-server ! ! ! ! ! control-plane ! ! !

line con 0 line aux 0 line 2 no activation-character no exec transport preferred none transport input all transport output pad telnet rlogin lapb-ta mop udptn v120 ssh stopbits 1 line vty 0 4 login transport input all ! scheduler allocate 20000 1000 ! end -----------------------------------------------------------------------------------------------------------------------NE5#sh run Building configuration... Current configuration : 1451 bytes ! ! Last configuration change at 14:17:50 UTC Mon Apr 14 2014 version 15.2 service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname NE5 ! boot-start-marker boot-end-marker ! ! ! no aaa new-model ! ip cef ! ! ! ! ! ! no ipv6 cef ! multilink bundle-name authenticated ! ! ! ! license udi pid CISCO2911/K9 sn FCZ172360QF

! ! ! redundancy ! ! ! ! ! ! ! ! ! ! ! ! ! ! interface Embedded-Service-Engine0/0 no ip address shutdown ! interface GigabitEthernet0/0 no ip address shutdown duplex auto speed auto ! interface GigabitEthernet0/1 ip address 40.40.40.2 255.255.255.0 duplex auto speed auto ! interface GigabitEthernet0/2 ip address 30.30.30.2 255.255.255.0 duplex auto speed auto ! interface Serial0/0/0 no ip address shutdown clock rate 2000000 ! interface Serial0/0/1 no ip address shutdown clock rate 2000000 ! router bgp 6800 bgp log-neighbor-changes network 30.30.30.0 mask 255.255.255.0 network 40.40.40.0 mask 255.255.255.0

neighbor 30.30.30.1 remote-as 6900 neighbor 40.40.40.1 remote-as 6700 ! ip forward-protocol nd ! no ip http server no ip http secure-server ! ! ! ! ! control-plane ! ! ! line con 0 line aux 0 line 2 no activation-character no exec transport preferred none transport input all transport output pad telnet rlogin lapb-ta mop udptn v120 ssh stopbits 1 line vty 0 4 login transport input all ! scheduler allocate 20000 1000 ! end

Configurations Scenario 2:
NE1#sh run Building configuration... Current configuration : 2120 bytes ! ! Last configuration change at 17:27:22 UTC Thu Apr 17 2014 ! NVRAM config last updated at 17:45:17 UTC Thu Apr 17 2014 ! NVRAM config last updated at 17:45:17 UTC Thu Apr 17 2014 version 15.1 service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname NE1 ! boot-start-marker boot-end-marker

! ! ! no aaa new-model ! ! no ipv6 cef ip source-route ip cef ! ! ! ! ! ! multilink bundle-name authenticated ! ! crypto pki token default removal timeout 0 ! ! license udi pid CISCO2911/K9 sn FCZ161970C1 ! ! ! redundancy ! ! ! ! ! ! ! ! ! ! ! interface Loopback0 ip address 1.1.1.1 255.255.255.255 ! interface Embedded-Service-Engine0/0 no ip address shutdown ! interface GigabitEthernet0/0 ip address 10.10.10.2 255.255.255.0 duplex auto speed auto ! interface GigabitEthernet0/1 ip address 10.10.11.2 255.255.255.0 duplex auto

speed auto ! interface GigabitEthernet0/2 ip address 20.20.20.1 255.255.255.0 duplex auto speed auto ! interface Serial0/1/0 no ip address shutdown no fair-queue clock rate 64000 ! interface Serial0/1/1 no ip address shutdown no fair-queue clock rate 2000000 ! router bgp 6500 bgp log-neighbor-changes network 1.1.1.1 mask 255.255.255.255 network 10.10.10.0 mask 255.255.255.0 network 10.10.11.0 mask 255.255.255.0 network 20.20.20.0 mask 255.255.255.0 neighbor 2.2.2.2 remote-as 6900 neighbor 2.2.2.2 ebgp-multihop 255 neighbor 2.2.2.2 update-source Loopback0 neighbor 2.2.2.2 next-hop-self neighbor 2.2.2.2 route-map BGPLOCALpref in neighbor 20.20.20.2 remote-as 6700 maximum-paths 2 ! ip forward-protocol nd ! no ip http server no ip http secure-server ! ip route 2.2.2.2 255.255.255.255 10.10.10.1 ip route 2.2.2.2 255.255.255.255 10.10.11.1 ! ! ! ! ! route-map BGPLOCALpref permit 10 set local-preference 500 ! ! ! control-plane !

! ! line con 0 line aux 0 line 2 no activation-character no exec transport preferred none transport input all transport output pad telnet rlogin lapb-ta mop udptn v120 ssh stopbits 1 line vty 0 4 login transport input all ! scheduler allocate 20000 1000 end -----------------------------------------------------------------------------------------------------------------------NE2#sh run Building configuration... Current configuration : 1958 bytes ! ! Last configuration change at 18:35:19 UTC Sun Jan 25 2009 ! NVRAM config last updated at 18:23:18 UTC Sun Jan 25 2009 ! NVRAM config last updated at 18:23:18 UTC Sun Jan 25 2009 version 15.1 service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname NE2 ! boot-start-marker boot-end-marker ! ! ! no aaa new-model ! ! no ipv6 cef ip source-route ip cef ! ! ! ! ! ! multilink bundle-name authenticated !

! crypto pki token default removal timeout 0 ! ! license udi pid CISCO2911/K9 sn FCZ161920NX ! ! ! redundancy ! ! ! ! ! ! ! ! ! ! ! interface Loopback0 ip address 2.2.2.2 255.255.255.255 ! interface Embedded-Service-Engine0/0 no ip address shutdown ! interface GigabitEthernet0/0 ip address 10.10.10.1 255.255.255.0 duplex auto speed auto ! interface GigabitEthernet0/1 ip address 10.10.11.1 255.255.255.0 duplex auto speed auto ! interface GigabitEthernet0/2 ip address 30.30.30.1 255.255.255.0 duplex auto speed auto ! interface Serial0/1/0 no ip address shutdown no fair-queue clock rate 2000000 ! interface Serial0/1/1 no ip address shutdown no fair-queue

clock rate 2000000 ! router bgp 6900 bgp log-neighbor-changes network 2.2.2.2 mask 255.255.255.255 network 10.10.10.0 mask 255.255.255.0 network 10.10.11.0 mask 255.255.255.0 network 30.30.30.0 mask 255.255.255.0 neighbor 1.1.1.1 remote-as 6500 neighbor 1.1.1.1 ebgp-multihop 255 neighbor 1.1.1.1 next-hop-self neighbor 30.30.30.2 remote-as 6800 ! ip forward-protocol nd ! no ip http server no ip http secure-server ! ip route 1.1.1.1 255.255.255.255 10.10.10.2 ip route 1.1.1.1 255.255.255.255 10.10.11.2 ! ! ! ! ! ! ! control-plane ! ! ! line con 0 line aux 0 line 2 no activation-character no exec transport preferred none transport input all transport output pad telnet rlogin lapb-ta mop udptn v120 ssh stopbits 1 line vty 0 4 login transport input all ! scheduler allocate 20000 1000 end -----------------------------------------------------------------------------------------------------------------------NE3#sh run Building configuration... Current configuration : 1215 bytes

! version 12.4 service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname NE3 ! boot-start-marker boot-end-marker ! ! no aaa new-model ! resource policy ! memory-size iomem 5 mmi polling-interval 60 no mmi auto-configure no mmi pvc mmi snmp-timeout 180 ip subnet-zero ip cef ! ! ! ! ! ! voice-card 0 ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! interface FastEthernet0/0

ip address 192.168.10.1 255.255.255.0 duplex auto speed auto ! interface FastEthernet0/1 ip address 20.20.20.2 255.255.255.0 duplex auto speed auto ! interface Serial0/1/0 no ip address no fair-queue clock rate 125000 ! interface Serial0/1/1 no ip address clock rate 125000 ! interface Serial0/2/0 no ip address shutdown clock rate 125000 ! interface Serial0/2/1 no ip address shutdown clock rate 125000 ! router bgp 6700 no synchronization bgp log-neighbor-changes network 20.20.20.0 mask 255.255.255.0 network 192.168.10.0 neighbor 20.20.20.1 remote-as 6500 neighbor 192.168.10.2 remote-as 6700 no auto-summary ! ip classless ! ! ip http server no ip http secure-server ! ! ! ! ! control-plane ! ! ! !

! ! ! ! ! line con 0 line aux 0 line vty 0 4 login ! end -----------------------------------------------------------------------------------------------------------------------NE4#sh run Building configuration... Current configuration : 1099 bytes ! version 12.4 service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname NE4 ! boot-start-marker boot-end-marker ! ! no aaa new-model ! resource policy ! memory-size iomem 5 mmi polling-interval 60 no mmi auto-configure no mmi pvc mmi snmp-timeout 180 ip subnet-zero ip cef ! ! ! ! ! ! voice-card 0 ! ! ! ! ! !

! ! ! ! ! ! ! ! ! ! ! ! ! ! ! interface FastEthernet0/0 ip address 192.168.10.2 255.255.255.0 duplex auto speed auto ! interface FastEthernet0/1 ip address 40.40.40.1 255.255.255.0 duplex auto speed auto ! interface Serial0/1/0 no ip address shutdown no fair-queue clock rate 125000 ! interface Serial0/1/1 no ip address shutdown clock rate 125000 ! router bgp 6700 no synchronization bgp log-neighbor-changes network 40.40.40.0 mask 255.255.255.0 network 192.168.10.0 neighbor 40.40.40.2 remote-as 6800 neighbor 192.168.10.1 remote-as 6700 no auto-summary ! ip classless ! ! ip http server no ip http secure-server ! !

! ! ! control-plane ! ! ! ! ! ! ! ! ! line con 0 line aux 0 line vty 0 4 login ! end -----------------------------------------------------------------------------------------------------------------------NE5#sh run Building configuration... Current configuration : 1471 bytes ! ! Last configuration change at 14:41:52 UTC Thu Apr 17 2014 version 15.2 service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname NE5 ! boot-start-marker boot-end-marker ! ! ! no aaa new-model memory-size iomem 5 ! ip cef ! ! ! ! ! ! no ipv6 cef ! multilink bundle-name authenticated

! ! ! ! license udi pid CISCO2911/K9 sn FCZ172360Q9 ! ! ! redundancy ! ! ! ! ! ! ! ! ! ! ! ! ! ! interface Embedded-Service-Engine0/0 no ip address shutdown ! interface GigabitEthernet0/0 no ip address shutdown duplex auto speed auto ! interface GigabitEthernet0/1 ip address 40.40.40.2 255.255.255.0 duplex auto speed auto ! interface GigabitEthernet0/2 ip address 30.30.30.2 255.255.255.0 duplex auto speed auto ! interface Serial0/0/0 no ip address shutdown clock rate 2000000 ! interface Serial0/0/1 no ip address shutdown clock rate 2000000

! router bgp 6800 bgp log-neighbor-changes network 30.30.30.0 mask 255.255.255.0 network 40.40.40.0 mask 255.255.255.0 neighbor 30.30.30.1 remote-as 6900 neighbor 40.40.40.1 remote-as 6700 ! ip forward-protocol nd ! no ip http server no ip http secure-server ! ! ! ! ! control-plane ! ! ! line con 0 line aux 0 line 2 no activation-character no exec transport preferred none transport input all transport output pad telnet rlogin lapb-ta mop udptn v120 ssh stopbits 1 line vty 0 4 login transport input all ! scheduler allocate 20000 1000 ! end