Quantcast
Channel: IEOC - INE's Online Community
Viewing all articles
Browse latest Browse all 10744

ODR - On-Demand Routing & Dynamic Routing

$
0
0

Hi all,

I see this statement "For ODR to be functional, there should be no dynamic routing protocol configured on spokes."

Is this saying there should be no dynamic protocol over the link where ODR is running? What is meant by functional, as I have run dynamic routing and it all works ok.

 

I have the following setup,

{R6}-OSPF-{R1}--ODR--{R5}-OSPF-{R8}

R5 is the hub configured wiht "router odr",

R1 is the Spoke (there are other spojes to not shown).

OSPF is running at the other side of hte deivces & all work ok, pings are fine.

 

I then enabled OSPF over the R1--R5 link, so we have ODR and OSPF together from hub to spoke & its all working ok;

 

I know this is 1 task, prob not even in the lab, I just need to satify myself with an answer on this :)

 

Outputs

R1#show ip ospf neighbor

Neighbor ID     Pri   State           Dead Time   Address         Interface
150.1.5.5         0   FULL/  -        00:00:33    155.1.0.5       Tunnel0
150.1.5.5         1   FULL/DR         00:00:36    169.254.100.5   FastEthernet0/0.100
150.1.6.6         1   FULL/DR         00:00:39    155.1.146.6     FastEthernet0/0.146

 

R1#show ip route

Gateway of last resort is 155.1.0.5 to network 0.0.0.0

o*    0.0.0.0/0 [160/1] via 155.1.0.5, 00:13:58, Tunnel0
      150.1.0.0/32 is subnetted, 4 subnets
C        150.1.1.1 is directly connected, Loopback0
O        150.1.5.5 [110/2] via 169.254.100.5, 00:00:28, FastEthernet0/0.100
O        150.1.6.6 [110/2] via 155.1.146.6, 00:11:22, FastEthernet0/0.146
O        150.1.8.8 [110/3] via 169.254.100.5, 00:00:28, FastEthernet0/0.100
      155.1.0.0/16 is variably subnetted, 12 subnets, 2 masks
C        155.1.0.0/24 is directly connected, Tunnel0
L        155.1.0.1/32 is directly connected, Tunnel0
O        155.1.5.0/24 [110/2] via 169.254.100.5, 00:00:28, FastEthernet0/0.100
O        155.1.8.0/24 [110/3] via 169.254.100.5, 00:00:28, FastEthernet0/0.100
C        155.1.13.0/24 is directly connected, FastEthernet0/0.13
L        155.1.13.1/32 is directly connected, FastEthernet0/0.13
O        155.1.45.0/24
           [110/2] via 169.254.100.5, 00:00:29, FastEthernet0/0.100
O        155.1.58.0/24
           [110/2] via 169.254.100.5, 00:00:29, FastEthernet0/0.100
O        155.1.67.0/24 [110/2] via 155.1.146.6, 00:11:23, FastEthernet0/0.146
O        155.1.108.0/24
           [110/3] via 169.254.100.5, 00:00:29, FastEthernet0/0.100
C        155.1.146.0/24 is directly connected, FastEthernet0/0.146
L        155.1.146.1/32 is directly connected, FastEthernet0/0.146
      169.254.0.0/16 is variably subnetted, 2 subnets, 2 masks
C        169.254.100.0/24 is directly connected, FastEthernet0/0.100
L        169.254.100.1/32 is directly connected, FastEthernet0/0.100

 

Ping to other hub, routed via ODR

R1(config-router)#do ping 150.1.2.2

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

 


R1(config-router)#do show ip cef 150.1.2.2 inter
0.0.0.0/0, epoch 0, RIBTime, refcount 5, per-destination sharing
  sources: RIB, DRH
  feature space:
   IPRM: 0x00058000
  ifnums:
   Tunnel0(9): 155.1.0.5
  path 687779C4, path list 686F25A8, share 1/1, type attached nexthop, for IPv4
  nexthop 155.1.0.5 Tunnel0, adjacency IP midchain out of Tunnel0, addr 155.1.0.5 67320840
  output chain: IP midchain out of Tunnel0, addr 155.1.0.5 67320840 IP adj out of FastEthernet0/0.100, addr 169.254.100.5 673206E0


Viewing all articles
Browse latest Browse all 10744

Trending Articles