Skip to main content

Offset list CCIE Question


In this scenario R1 connect R2 with different bandwidth line. If we can't change EIGRP 'k' values, bandwidth and delay on the existing interfaces and only involve EIGRP, offset list is the way to solve this cause.

Now R1 know only one route to 3.3.3.0/24 network.
R1#sh ip route eigrp
     3.0.0.0/24 is subnetted, 1 subnets
D       3.3.3.0 [90/3142400] via 10.10.12.2, 00:48:21, Serial0/0

     10.0.0.0/24 is subnetted, 3 subnets
D       10.10.23.0 [90/3014400] via 10.10.12.2, 00:53:18, Serial0/0

We see R1 have only one path to 3.3/14 network.Now I will set offset list on R2. First I need to check R1 metric value for 3.3.3.0/24 network.

R1#sh ip eigrp top
IP-EIGRP Topology Table for AS(123)/ID(1.1.1.1)

Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
       r - reply Status, s - sia Status

P 1.1.1.0/24, 1 successors, FD is 128256
        via Connected, Loopback0
P 3.3.3.0/24, 1 successors, FD is 3142400
        via 10.10.12.2 (3142400/156160), Serial0/0
        via 10.10.21.2 (5642496/156160), Serial0/1
P 10.10.12.0/24, 1 successors, FD is 3011840
        via Connected, Serial0/0
        via 10.10.21.2 (6023936/2169856), Serial0/1
P 10.10.21.0/24, 1 successors, FD is 5511936
        via Connected, Serial0/1
        via 10.10.12.2 (3523840/2169856), Serial0/0
P 10.10.23.0/24, 1 successors, FD is 3014400
        via 10.10.12.2 (3014400/28160), Serial0/0
        via 10.10.21.2 (5514496/28160), Serial0/1



Offset list is influence metric values so I need to setup s0/0 metric value to 5642496 for load balancing.
First step access list need.
R2(config)#access-list 1 permit 3.3.3.0 0.0.0.255

Second offset list set at EIGRP.

router eigrp 123
 offset-list 1 out 2500096 Serial0/0



Now we can verify on R1 routing table.

R1#sh ip route eigrp
     3.0.0.0/24 is subnetted, 1 subnets
D       3.3.3.0 [90/5642496] via 10.10.21.2, 00:00:07, Serial0/1
                [90/5642496] via 10.10.12.2, 00:00:07, Serial0/0

     10.0.0.0/24 is subnetted, 3 subnets
D       10.10.23.0 [90/3014400] via 10.10.12.2, 00:00:07, Serial0/0


Some time we need to clear EIGRP process with #clear ip eigrp neighbor

R1#traceroute 3.3.3.3
  1 10.10.21.2 56 msec
    10.10.12.2 64 msec
    10.10.21.2 64 msec
  2 10.10.23.3 96 msec 96 msec 64 msec


If we set the offset list on R1 config like below.
#offset-list 1 in 2500096 Serial0/0   

Comments

Popular posts from this blog

How to setup AWS VPC Peering (VPC to VPC)

    Hi Everyone... ဒီကနေ့တော့ VPC Peering လုပ်တဲ့ အကြောင်းလေးပြောပြပေးသွားမှာပါ။ VPC peering ဘာလို့လုပ်တာလဲ ဘယ်အချိန်တွေမှာသုံးတာလဲဆိုတာကို ကြည့်ရအောင်... သိတဲ့ အတိုင်း ပဲ AWS networking မှာ VPC ကမပါမဖြစ်အရေးပါပါတယ် AWS account တခုရဲ့ AWS region တခုမှာ VPC 5ခုအများဆုံး ထားလို့ရပါတယ်... AZ မဟုတ်ပါဘူး အဲ့ဒါလေးတော့သတိထားရမှာပါ.. peering က one to one ဖြစ်တဲ့အတွက် VPC များလာရင်တော့ configuation complex ဖြစ်လာပါမယ်၊ နောက်တခုကတခြား AWS account တွေရဲ့ VPC နဲ့ချိတ်ဆက်သုံးချင်တာတွေလဲရှိနိုင်ပါတယ် အဲ့လို VPC တွေများလာမယ်ဆိုရင်တော့ Transit Gateway ကိုသုံးတာက ပိုစိတ်ချမ်းသာရပါတယ်။ VPC နည်းသေးတယ် နောင်လဲတိုးလာဖို့ မရှိသေးဘူးဆိုရင်တော့ အခုနည်းလမ်းက ပိုအဆင်ပြေပါတယ်. ဆိုတော့ Pubilc VPC နဲ့ Private VPC ဆိုပြီးရှိတယ်ဆိုပါစို့ Pubilc VPC ထဲက webserver က Private VPC ထဲ က database ကိုလှမ်းသုံးချင်တယ်ဆိုရင် အဲ့ဒီ VPC တွေကို peering လုပ်ပေးဖို့လိုပါတယ်.. Peering လုပ်မယ်ဆိုရင်တော့ VPC ထဲက peering connections ကိုရွေးရပါမယ်. ပြီးရင်တော့ Create peering connections ကို click ပါ၊ ဒီ box ကျလာရင်တော့ name မှာ

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

BGP Disable Connected Check and EBGP Multi Hop

Figure 1.1 In this scenario I use OSPF for TCP reachability. We can see the difference 'disable connected' check and 'EBGP multihop'. We can use both for EBGP neighbor connection with loopback address. Disable connected check This command used to disable the connection verification process for ebgp. Use for ebgp neighbor are directly connected and they using the loopback address for peering. It not increment TTL but neighbor must reachable at single hop. EBGP multihop This command can use for ebgp neighbor are not directly connected. It increment TTL. R1 router bgp 100  neighbor 2.2.2.2 remote-as 200  neighbor 2.2.2.2 disable-connected-check  neighbor 2.2.2.2 update-source Loopback0  neighbor 3.3.3.3 remote-as 300  neighbor 3.3.3.3 ebgp-multihop 2  neighbor 3.3.3.3 update-source Loopback0 R2 router bgp 200  neighbor 1.1.1.1 remote-as 100  neighbor 1.1.1.1 disable-connected-check  neighbor 1.1.1.1 update-source Loopback0 R3