ODR

Hi Guys,

I was doing the lab of ODR and my R1 is not configured as point-to-point. I expereinced that even though R5 can see it in "sh cdp neighbor" but R2, R3 and R4 are unable to ping R1 Loopback.

 

While R5 can ping to R1 and all. and R1 can ping to all as well. After spending some time I just changed the R1 multipoint interface to point-to-point and than everthing start working fine.

 

I need to know why this happen it means that the stub should always be point-to-point. (R5 is a HUB)

 

Regards

Mahir

Comments

  • Hi mahirali,

    ODR is completely CDP based routing, which injects default route to neighbor found by CDP. As far as HUB found Spoke as a neighbor, injects default route, doesn't matter either point-to-point or multipoint. just remember to enable cdp on multipoint interface.

    See this example:

    R3#show run int s0/0.301
    Building configuration...

    Current configuration : 166 bytes
    !
    interface Serial0/0.301 multipoint
     ip address 192.168.0.3 255.255.255.0
     cdp enable
     frame-relay map ip 192.168.0.1 301 broadcast
     no frame-relay inverse-arp
    end

    !

    R3#ping 192.168.0.1

    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 192.168.0.1, timeout is 2 seconds:
    !!!!!
    Success rate is 100 percent (5/5), round-trip min/avg/max = 36/79/144 ms
    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 = 36/61/128 ms
    R3#ping 4.4.4.4 so lo0

    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 4.4.4.4, timeout is 2 seconds:
    Packet sent with a source address of 3.3.3.3
    !!!!!
    Success rate is 100 percent (5/5), round-trip min/avg/max = 92/120/164 ms
    R3#
    R5#show running-config int s0/0
    Building configuration...

    Current configuration : 160 bytes
    !
    interface Serial0/0
     ip address 192.168.0.5 255.255.255.0
     encapsulation frame-relay
     serial restart-delay 0
     cdp enable
     frame-relay interface-dlci 501
    end
    R1#show running-config int s0/0.100
    Building configuration...

    Current configuration : 258 bytes
    !
    interface Serial0/0.100 multipoint
     ip address 192.168.0.1 255.255.255.0
     cdp enable
     frame-relay map ip 192.168.0.3 103 broadcast
     frame-relay map ip 192.168.0.4 104 broadcast
     frame-relay map ip 192.168.0.5 105 broadcast
     no frame-relay inverse-arp
    end

    HAPPY STUDY

    [:D]


  • ODR is independent of the type of interface you're using in FR, so it could be either p2p or p2multipoint


  • Hi,

     

    That is what I learned, it is independent of interface type, but I was on the main interface of R1 and it gave me this issue. That is why I put this question.

     

    Regards

    Mahir

  • That is what I learned, it is independent of interface type, but I was on the main interface of R1 and it gave me this issue. That is why I put this question.

    I hope my example cleared your doubt!

    HAPPY STUDY

    [:D]

  • Hi Mahir,

        The problem you encountered is because, by default, CDP is NOT enabled on the frame-relay physical multipoint interface and on any multipoint sub-interfaces, but is enabled on the point-to-point sub-interface. If you used show cdp interface serialx/y you should have seen no output for the multipoint interface/sub-interface.

    Good luck with your studies!

Sign In or Register to comment.