Skip to main content

OSPF Virtual Link 2

We know the virtual link for connect to OSPF backbone area 0.
How about two that network have 2 backbone area? 

Figure 1.1
R1 and R6 can't connect.
R1
R1(config-router)#do sh ip route ospf
     3.0.0.0/24 is subnetted, 1 subnets
O IA    3.3.3.0 [110/3] via 10.1.12.2, 00:22:38, FastEthernet0/0
     4.0.0.0/24 is subnetted, 1 subnets
O IA    4.4.4.0 [110/4] via 10.1.12.2, 00:21:52, FastEthernet0/0
     10.0.0.0/24 is subnetted, 3 subnets
O IA    10.1.23.0 [110/2] via 10.1.12.2, 00:23:28, FastEthernet0/0
O IA    10.1.34.0 [110/3] via 10.1.12.2, 00:22:38, FastEthernet0/0

R6
R6(config-if)#do sh ip route ospf
     3.0.0.0/24 is subnetted, 1 subnets
O IA    3.3.3.0 [110/4] via 10.1.56.5, 00:16:06, FastEthernet0/0
     4.0.0.0/24 is subnetted, 1 subnets
O IA    4.4.4.0 [110/3] via 10.1.56.5, 00:16:06, FastEthernet0/0
     10.0.0.0/24 is subnetted, 3 subnets
O IA    10.1.45.0 [110/2] via 10.1.56.5, 00:16:06, FastEthernet0/0
O IA    10.1.34.0 [110/3] via 10.1.56.5, 00:16:06, FastEthernet0/0

Not only Router 3 can connect to Router 1 but also Router 4 can connect to Router 6.

R3
R3#ping 1.1.1.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 1.1.1.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 44/57/64 ms
R3#ping 6.6.6.6

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 6.6.6.6, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)

R4
R4#ping 1.1.1.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 1.1.1.1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
R4#ping 6.6.6.6

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 6.6.6.6, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 48/83/140 ms

In this cause, we can solve with Virtual Link 

Only configure Virtual Link at area 51.

R3
router ospf 1
area 51 virtual-link 4.4.4.4

R4
router ospf 1
area 51 virtual-link 3.3.3.3

Just do like my old post.

http://outbox-network.blogspot.com/2016/03/ospf-virtual-link-ospf-virtual-link-is.html.

After Configure virtual link you will see result like that.

R1
R1#sh ip route ospf
       6.0.0.0/24 is subnetted, 1 subnets
O IA    6.6.6.0 [110/6] via 10.1.12.2, 00:00:00, FastEthernet0/0
R6
R6#sh ip route ospf
     1.0.0.0/24 is subnetted, 1 subnets
O IA    1.1.1.0 [110/6] via 10.1.56.5, 00:01:41, FastEthernet0/0



Comments

Popular posts from this blog

Prefix list

In this scenario I want to filter 192.168.3.x /25 , /26, /27 networks form R1 route update. I can use access list but I need to set the rules for every network. In prefix list it will easy to filter. R2(config-router)#do sh ip bgp BGP table version is 8, local router ID is 2.2.2.2 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 *> 192.168.1.0      10.10.10.1               0             0 1 i *> 192.168.2.0      10.10.10.1 ...

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

Nested Route Reflection Cluster

Figure 1.1 R1 router bgp 65000  bgp cluster-id 10  neighbor 2.2.2.2 remote-as 65000  neighbor 2.2.2.2 update-source Loopback0  neighbor 2.2.2.2 route-reflector-client  neighbor 3.3.3.3 remote-as 65000  neighbor 3.3.3.3 update-source Loopback0  neighbor 3.3.3.3 route-reflector-client R2 router bgp 65000  bgp cluster-id 20  net 22.22.22.0 mask 255.255.255.0  neighbor 1.1.1.1 remote-as 65000  neighbor 1.1.1.1 update-source Loopback0  neighbor 4.4.4.4 remote-as 65000  neighbor 4.4.4.4 update-source Loopback0  neighbor 4.4.4.4 route-reflector-client R3 router bgp 65000  bgp cluster-id 30  net 33.33.33.0 mask 255.255.255.0  neighbor 1.1.1.1 remote-as 65000  neighbor 1.1.1.1 update-source Loopback0  neighbor 5.5.5.5 remote-as 65000  neighbor 5.5.5.5 update-source Loopback0  neighbor 5.5.5.5 route-reflector-client R4 router bgp 65000 ...