mkomon wrote: » I did what Mike has just written and with some labtime the BGP exam was a cake. There was still a couple of things that were not covered in neither of the books but it was not a big deal.
Sett wrote: » Like what ? Not anything specific of course, just the topics
mikej412 wrote: » Start with BGP.
APA wrote: » I'll always say it......... but don't skimp on reading the following..... BGP Design and Implementation - by Randy Zhang Awesome book...and mike is right..... For the BGP exam anything is fair game..... Even if the objectives don't explicitly state it!
Ryan82 wrote: » As long as R1 has IP reachability to R2, they should be able to form an LDP relationship. Make sure "mpls ip" is enabled globally, on the interfaces connecting R1 and R2, and cef is enabled on both devices.
interface FastEthernet0/0 ip address 200.1.1.2 255.255.255.0 duplex auto speed auto ! interface FastEthernet0/1 ip address 10.0.0.1 255.255.255.252 duplex auto speed auto mpls ip router eigrp 1 network 10.0.0.0 no auto-summary ! router bgp 65000 no synchronization bgp log-neighbor-changes network 200.1.1.0 neighbor 10.2.2.2 remote-as 65000 neighbor 200.1.1.1 remote-as 65100 no auto-summary
interface FastEthernet0/1 ip address 10.0.0.2 255.255.255.252 duplex auto speed auto mpls ip ! router eigrp 1 network 10.0.0.0 no auto-summary
R3#sh mpls ldp neighbor R3#
R1#sh mpls ldp neighbor Peer LDP Ident: 10.2.2.1:0; Local LDP Ident 10.1.1.1:0 TCP connection: 10.2.2.1.41798 - 10.1.1.1.646 State: Oper; Msgs sent/rcvd: 26/26; Downstream Up time: 00:17:25 LDP discovery sources: FastEthernet0/0, Src IP addr: 10.1.1.2 Addresses bound to peer LDP Ident: 10.1.1.2 10.2.2.1 R1#
R3#traceroute 10.2.2.2 Type escape sequence to abort. Tracing the route to 10.2.2.2 1 10.0.0.2 60 msec 80 msec 8 msec 2 10.1.1.2 16 msec 8 msec 8 msec 3 10.2.2.2 52 msec * 92 msec R3#
*Mar 1 00:00:27.519: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.0.0.2 (FastEthernet0/1) is up: new adjacency *Mar 1 00:00:30.251: %LDP-5-NBRCHG: LDP Neighbor 1.1.1.1:0 (1) is UP *Mar 1 00:00:51.387: %BGP-5-ADJCHANGE: neighbor 200.1.1.1 Up *Mar 1 00:01:00.427: %BGP-5-ADJCHANGE: neighbor 10.2.2.2 Up
*Mar 1 00:00:18.447: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.0.0.1 (FastEthernet0/1) is up: new adjacency *Mar 1 00:00:21.347: %LDP-5-NBRCHG: LDP Neighbor 3.3.3.3:0 (1) is UP *Mar 1 00:00:34.983: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.1.1.2 (FastEthernet0/0) is up: new adjacency *Mar 1 00:00:37.947: %LDP-5-NBRCHG: LDP Neighbor 2.2.2.2:0 (2) is UP
1 10.0.0.2 [MPLS: Label 18 Exp 0] 52 msec 104 msec 8 msec 2 10.1.1.2 20 msec 12 msec 8 msec 3 10.2.2.2 40 msec * 76 msec
mkomon wrote: » -add a route for 200.1.1.2 on R1 or add the network into EIGRP
mkomon wrote: » Your "AS prepends" will propagate globally. They will become a part of the AS_PATH attribute and won't be stripped off by anybody.