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.

router ospf 1

router-id 2.2.2.2

log-adjacency-changes

area 1 virtual-link 3.3.3.3

router-id 3.3.3.3

log-adjacency-changes

area 1 virtual-link 2.2.2.2

*Mar 1 00:23:02.203: %OSPF-5-ADJCHG: Process 1, Nbr 3.3.3.3 on OSPF_VL1 from LOADING to FULL, Loading Done

Now Virtual link is up and we will see all all area are connected.

3.0.0.0/24 is subnetted, 1 subnets

O IA 3.3.3.0 [110/2] via 10.1.2.2, 00:03:59, FastEthernet1/0

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

R1#sh ip route ospf

3.0.0.0/24 is subnetted, 1 subnets

O IA 3.3.3.0 [110/3] via 10.1.1.2, 00:05:07, FastEthernet0/0

R1#sh ip ospf data

OSPF Router with ID (1.1.1.1) (Process ID 1)

Router Link States (Area 0)

Link ID ADV Router Age Seq# Checksum Link count

1.1.1.1 1.1.1.1 388 0x80000002 0x00947B 1

2.2.2.2 2.2.2.2 380 0x80000004 0x004097 2

3.3.3.3 3.3.3.3 2 (DNA) 0x80000003 0x0019E5 1

Net Link States (Area 0)

Link ID ADV Router Age Seq# Checksum

10.1.1.1 1.1.1.1 387 0x80000001 0x0052CD

Summary Net Link States (Area 0)

Link ID ADV Router Age Seq# Checksum

3.3.3.0 3.3.3.3 11 (DNA) 0x80000001 0x00CC5A

10.1.2.0 2.2.2.2 395 0x80000001 0x00A089

10.1.2.0 3.3.3.3 11 (DNA) 0x80000001 0x0082A3

But Virtual link can't support Stub area and NSSA area.

Comments

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...

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 ကျလာရင်တော့ ...

Networking

Search This Blog