Skip to main content

BGP Lab 1


Study lab for ebgp and ibgp. 
Figure 1.1
In this scenario ebgp and ibgp configured.

Router 1 and router 2 connect as eBGP. Router 1 and router 3 connect as iBGP.

R2
router bgp 100
neighbor 10.1.12.1 remote 200

R1 
router bgp 200
neighbor 10.1.12.2 remote 100
neighbor 10.1.13.3 remote 200

R3
router bgp 200
neighbor 10.1.13.1 remote 200


Now neighbor is up we can verify neighbors with 'show ip bgp summary'.

R2#show ip bgp summary
BGP router identifier 2.2.2.2, local AS number 100
BGP table version is 7, main routing table version 7
2 network entries using 234 bytes of memory
2 path entries using 104 bytes of memory
3/2 BGP path/bestpath attribute entries using 372 bytes of memory
1 BGP AS-PATH entries using 24 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP using 734 total bytes of memory
BGP activity 4/2 prefixes, 4/2 paths, scan interval 60 secs

Neighbor        V    AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down  State/PfxRcd
10.1.12.1       4   200       5       5                   7      0    0     00:00:05        1

Verify the routing tables.

R1
R1#show ip route bgp
     2.0.0.0/24 is subnetted, 1 subnets
B       2.2.2.0 [20/0] via 10.1.12.2, 00:25:33
     3.0.0.0/24 is subnetted, 1 subnets
B       3.3.3.0 [200/0] via 10.1.13.3, 00:30:02

R2
R2#show ip route bgp
     3.0.0.0/24 is subnetted, 1 subnets
B       3.3.3.0 [20/0] via 10.1.12.1, 00:24:44

R3
R3#show ip route
     3.0.0.0/24 is subnetted, 1 subnets
C       3.3.3.0 is directly connected, Loopback0
     10.0.0.0/24 is subnetted, 1 subnets
C       10.1.13.0 is directly connected, FastEthernet0/0

At router 1 and 2 can see the 3.3.3.0/24 and 2.2.2.0/24 networks but router can't see the 2.2.2.0/24 network. So we check with another way.

show ip bgp 
This command to check bgp network are best route or fail.

R3#show ip bgp
BGP table version is 2, local router ID is 3.3.3.3
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
              r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete

   Network          Next Hop            Metric LocPrf Weight Path
* i2.2.2.0/24       10.1.12.2                0    100      0 100 i
*> 3.3.3.0/24       0.0.0.0                  0         32768 i

2.2.20/24 is valid but not best, it next hop router is R2. R3 don't know R2 so we must change in R1 as next hop router. 
Next hop self concept is like, if you want to go U.S from Myanmar, you need to go air port.
In this scenario R1 is like air port.
 
R1 
router bgp 200
neighbor 10.1.13.3 next-hop-self

Now we see the change at next hop router.

R3#sh ip bgp
BGP table version is 3, local router ID is 3.3.3.3
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
              r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete

   Network          Next Hop            Metric LocPrf Weight Path
*>i2.2.2.0/24       10.1.13.1                0    100      0 100 i
*> 3.3.3.0/24       0.0.0.0                  0         32768 i

R3#sh ip route bgp
     2.0.0.0/24 is subnetted, 1 subnets
B       2.2.2.0 [200/0] via 10.1.13.1, 00:14:33

Testing
R3#ping 2.2.2.2 source 3.3.3.3

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2.2.2.2, timeout is 2 seconds:
Packet sent with a source address of 3.3.3.3
!!!!!

R3#traceroute 2.2.2.2 source 3.3.3.3

Type escape sequence to abort.
Tracing the route to 2.2.2.2

  1 10.1.13.1 24 msec 40 msec 52 msec
  2 10.1.12.2 68 msec 72 msec 80 msec


Labels:

Comments

Post a Comment

Popular posts from this blog

Access-list at SVI

SVI (Switch Virtual Interfaces) We use the SVI for inter vlan routing. In this scenario I will configure the access list with SVI. In this scenario I want to permit vlan 10 network to vlan 50 Server farm. Vlan 10 and vlan 20 can communicate each other. First create vlan and then interface vlan#. Switch(config)#vlan 10 Switch(config)#interface vlan 10 Switch(config-if)#ip address 192.168.10.254 255.255.255.0 Switch(config)#vlan 20 Switch(config)#interface vlan 20 Switch(config-if)#ip address 192.168.20.254 255.255.255.0 Switch(config)#vlan 50 Switch(config)#interface vlan 50 Switch(config-if)#ip address 192.168.50.254 255.255.255.0 when we finish the vlan interface create make sure the switch port are belong to each vlan. Port to vlan assign configure is Switch(config)#interface g0/1 Switch(config-if)#switchport access vlan 10 Switch(config)#interface g0/2 Switch(config-if)#switchport access vlan 20 Switch(config)#int...
1 comment
Read more

OSPF Stub

The following restrictions apply to stub areas:     You cannot create a virtual link through a stub area.   A stub area cannot contain an AS boundary router.   You cannot configure the backbone as a stub area.   You cannot configure an area as both a stub area and an not-so-stubby area (NSSA). Ref : Juniper.net
Post a Comment
Read more

OSPF Virtual Link

OSPF Virtual Link OSPF virtual link is use for that area far from backbone area 0. At this figure 1.1 area 2 is far from area 0 so area 2 can't reach other area. Figure 1.1 After configure OSPF, neighbor is up but router 2 don't see 3.3.3.0/24 network. R3#sh ip ospf nei Neighbor ID     Pri   State           Dead Time   Address         Interface 2.2.2.2           1   FULL/DR         00:00:39    10.1.2.1        FastEthernet0/0 R2#sh ip route      10.0.0.0/30 is subnetted, 2 subnets C       10.1.2.0 is directly connected, FastEthernet1/0 C       10.1.1.0 is directly connected, FastEthernet0/0 One of OSPF rule all area must connect to area 0.In this cause we can use virtual link at area 1. R2 router ospf 1  router-id 2.2.2.2  log-adjace...
Post a Comment
Read more