9 Replies Latest reply: Jul 11, 2019 12:17 PM by Ing_Percy RSS

    RipNG over frame relay issue

    Learner

      Hello all,

       

      I set up RipNG and frame relay on R1, R2 and R3 in the following topology.

       

      R1 has the route to reach R2, and R2 has the route to reach R1. But ping between them fails. What seems to be the problem?

       

      ccnp route OCG p110.jpg

      Below are R1, R2 and R3 config info:

       

      R1#

      R1#show ipv6 route | beg ON1

             ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2, l - LISP

      C   12::/64 [0/0]

           via GigabitEthernet0/0.12, directly connected

      L   12::1/128 [0/0]

           via GigabitEthernet0/0.12, receive

      C   2013::/64 [0/0]

           via Serial4/0.103, directly connected

      L   2013::1/128 [0/0]

           via Serial4/0.103, receive

      R   2023::/64 [120/2]

           via FE80::C803:25FF:FE0C:6, Serial4/0.103

      L   FF00::/8 [0/0]

           via Null0, receive

      R1#

      R1#

      R1#show frame-relay map

      Serial4/0.103 (up): point-to-point dlci, dlci 103(0x67,0x1870), broadcast

                status defined, active

      R1#

      R1#

      R1#ping 2023::2

      Type escape sequence to abort.

      Sending 5, 100-byte ICMP Echos to 2023::2, timeout is 2 seconds:

      .....

      Success rate is 0 percent (0/5)

      R1#

       

      ---------


      R3#

      R3#show frame-relay map

      Serial4/0.301 (up): point-to-point dlci, dlci 301(0x12D,0x48D0), broadcast

                status defined, active

      Serial4/0.302 (up): point-to-point dlci, dlci 302(0x12E,0x48E0), broadcast

                status defined, active

      R3#

      R3#

      R3#show ipv6 route | beg ON1

             ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2, l - LISP

      C   2013::/64 [0/0]

           via Serial4/0.301, directly connected

      L   2013::3/128 [0/0]

           via Serial4/0.301, receive

      C   2023::/64 [0/0]

           via Serial4/0.302, directly connected

      L   2023::3/128 [0/0]

           via Serial4/0.302, receive

      L   FF00::/8 [0/0]

           via Null0, receive

      R3#

      R3#

      R3#ping 2013::1

      Type escape sequence to abort.

      Sending 5, 100-byte ICMP Echos to 2013::1, timeout is 2 seconds:

      !!!!!

      Success rate is 100 percent (5/5), round-trip min/avg/max = 28/33/44 ms

      R3#

      R3#ping 2023::2

      Type escape sequence to abort.

      Sending 5, 100-byte ICMP Echos to 2023::2, timeout is 2 seconds:

      !!!!!

      Success rate is 100 percent (5/5), round-trip min/avg/max = 32/39/48 ms

      R3#

      ---------

       

      R2#

      R2#show frame-relay map

      Serial4/0.203 (up): point-to-point dlci, dlci 203(0xCB,0x30B0), broadcast

                status defined, active

      R2#

      R2#show ipv6 route | beg ON1

             ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2, l - LISP

      C   12::/64 [0/0]

           via GigabitEthernet0/0.12, directly connected

      L   12::2/128 [0/0]

           via GigabitEthernet0/0.12, receive

      R   2013::/64 [120/2]

           via FE80::C803:25FF:FE0C:6, Serial4/0.203

      C   2023::/64 [0/0]

           via Serial4/0.203, directly connected

      L   2023::2/128 [0/0]

           via Serial4/0.203, receive

      L   FF00::/8 [0/0]

           via Null0, receive

      R2#

        • 1. Re: RipNG over frame relay issue
          Ing_Percy

          Hi!

           

          What is the FR configuration?

          Have you applied a frame-relay map for the the link-local address, too?

           

          Example:

          interface Serial0/0

          ipv6 address FE80::1 link-local

          ipv6 address 2001::2/64

          ipv6 rip RT0 enable

          frame-relay map ipv6 2001::1 201 broadcast

          frame-relay map ipv6 FE80::2 201

           

          Regards!

          • 2. Re: RipNG over frame relay issue
            Steven Davidson

            I built this out exactly like it is depicted in the diagram (FR portion only) and ran a tcl script on R1 and here are the results of that script:

             

            R1#tclsh

            R1(tcl)#foreach ipv6 {

            +>(tcl)#2013::1

            +>(tcl)#2013::3

            +>(tcl)#2014::1

            +>(tcl)#2014::4

            +>(tcl)#2015::1

            +>(tcl)#2015::5

            +>(tcl)#2023::2

            +>(tcl)#2023::3

            +>(tcl)#2024::2

            +>(tcl)#2024::4

            +>(tcl)#2025::2

            +>(tcl)#2025::5

            +>(tcl)#2034::3

            +>(tcl)#2034::4} {ping $ipv6 repeat 3 time 1}

            Type escape sequence to abort.

            Sending 3, 100-byte ICMP Echos to 2013::1, timeout is 1 seconds:

            !!!

            Success rate is 100 percent (3/3), round-trip min/avg/max = 1/2/4 ms

            Type escape sequence to abort.

            Sending 3, 100-byte ICMP Echos to 2013::3, timeout is 1 seconds:

            !!!

            Success rate is 100 percent (3/3), round-trip min/avg/max = 44/48/52 ms

            Type escape sequence to abort.

            Sending 3, 100-byte ICMP Echos to 2014::1, timeout is 1 seconds:

            !!!

            Success rate is 100 percent (3/3), round-trip min/avg/max = 1/2/4 ms

            Type escape sequence to abort.

            Sending 3, 100-byte ICMP Echos to 2014::4, timeout is 1 seconds:

            !!!

            Success rate is 100 percent (3/3), round-trip min/avg/max = 32/42/52 ms

            Type escape sequence to abort.

            Sending 3, 100-byte ICMP Echos to 2015::1, timeout is 1 seconds:

            !!!

            Success rate is 100 percent (3/3), round-trip min/avg/max = 1/3/8 ms

            Type escape sequence to abort.

            Sending 3, 100-byte ICMP Echos to 2015::5, timeout is 1 seconds:

            !!!

            Success rate is 100 percent (3/3), round-trip min/avg/max = 20/41/52 ms

            Type escape sequence to abort.

            Sending 3, 100-byte ICMP Echos to 2023::2, timeout is 1 seconds:

            !!!

            Success rate is 100 percent (3/3), round-trip min/avg/max = 20/41/68 ms

            Type escape sequence to abort.

            Sending 3, 100-byte ICMP Echos to 2023::3, timeout is 1 seconds:

            !!!

            Success rate is 100 percent (3/3), round-trip min/avg/max = 20/46/68 ms

            Type escape sequence to abort.

            Sending 3, 100-byte ICMP Echos to 2024::2, timeout is 1 seconds:

            !!!

            Success rate is 100 percent (3/3), round-trip min/avg/max = 8/37/64 ms

            Type escape sequence to abort.

            Sending 3, 100-byte ICMP Echos to 2024::4, timeout is 1 seconds:

            !!!

            Success rate is 100 percent (3/3), round-trip min/avg/max = 16/46/72 ms

            Type escape sequence to abort.

            Sending 3, 100-byte ICMP Echos to 2025::2, timeout is 1 seconds:

            !!!

            Success rate is 100 percent (3/3), round-trip min/avg/max = 28/45/72 ms

            Type escape sequence to abort.

            Sending 3, 100-byte ICMP Echos to 2025::5, timeout is 1 seconds:

            !!!

            Success rate is 100 percent (3/3), round-trip min/avg/max = 36/49/64 ms

            Type escape sequence to abort.

            Sending 3, 100-byte ICMP Echos to 2034::3, timeout is 1 seconds:

            !!!

            Success rate is 100 percent (3/3), round-trip min/avg/max = 44/60/88 ms

            Type escape sequence to abort.

            Sending 3, 100-byte ICMP Echos to 2034::4, timeout is 1 seconds:

            !!!

            Success rate is 100 percent (3/3), round-trip min/avg/max = 20/56/100 ms

            R1(tcl)#

             

            Here's the config:

             

            R1#show run | sec ^interface Serial6/0

            interface Serial6/0

            no ip address

            encapsulation frame-relay

            serial restart-delay 0

            interface Serial6/0.3 point-to-point

            ipv6 address 2013::1/64

            ipv6 enable

            ipv6 rip RIPng enable

            frame-relay interface-dlci 103 

            interface Serial6/0.4 point-to-point

            ipv6 address 2014::1/64

            ipv6 enable

            ipv6 rip RIPng enable

            frame-relay interface-dlci 104 

            interface Serial6/0.5 point-to-point

            ipv6 address 2015::1/64

            ipv6 enable

            ipv6 rip RIPng enable

            frame-relay interface-dlci 105 

             

            R2#show run | sec ^interface Serial6/0

            interface Serial6/0

            no ip address

            encapsulation frame-relay

            serial restart-delay 0

            interface Serial6/0.3 point-to-point

            ipv6 address 2023::2/64

            ipv6 enable

            ipv6 rip RIPng enable

            frame-relay interface-dlci 203 

            interface Serial6/0.4 point-to-point

            ipv6 address 2024::2/64

            ipv6 enable

            ipv6 rip RIPng enable

            frame-relay interface-dlci 204 

            interface Serial6/0.5 point-to-point

            ipv6 address 2025::2/64

            ipv6 enable

            ipv6 rip RIPng enable

            frame-relay interface-dlci 205 

             

            R3#show run | sec ^interface Serial6/0

            interface Serial6/0

            no ip address

            encapsulation frame-relay

            serial restart-delay 0

            interface Serial6/0.1 point-to-point

            ipv6 address 2013::3/64

            ipv6 enable

            ipv6 rip RIPng enable

            frame-relay interface-dlci 301 

            interface Serial6/0.2 point-to-point

            ipv6 address 2023::3/64

            ipv6 enable

            ipv6 rip RIPng enable

            frame-relay interface-dlci 302 

             

            R4#show run | sec ^interface Serial6/0

            interface Serial6/0

            no ip address

            encapsulation frame-relay

            serial restart-delay 0

            interface Serial6/0.1 point-to-point

            ipv6 address 2014::4/64

            ipv6 enable

            ipv6 rip RIPng enable

            frame-relay interface-dlci 401 

            interface Serial6/0.2 point-to-point

            ipv6 address 2024::4/64

            ipv6 enable

            ipv6 rip RIPng enable

            frame-relay interface-dlci 402 

             

            R5#show run | sec ^interface Serial6/0

            interface Serial6/0

            no ip address

            encapsulation frame-relay

            serial restart-delay 0

            interface Serial6/0.1 point-to-point

            ipv6 address 2015::5/64

            ipv6 enable

            ipv6 rip RIPng enable

            frame-relay interface-dlci 501 

            interface Serial6/0.2 point-to-point

            ipv6 address 2025::5/64

            ipv6 enable

            ipv6 rip RIPng enable

            frame-relay interface-dlci 502 

             

            R6-FRS#show run | sec ^interface Serial6/[1-5]

            interface Serial6/1

            no ip address

            encapsulation frame-relay

            serial restart-delay 0

            frame-relay intf-type dce

            frame-relay route 103 interface Serial6/3 301

            frame-relay route 104 interface Serial6/4 401

            frame-relay route 105 interface Serial6/5 501

            interface Serial6/2

            no ip address

            encapsulation frame-relay

            serial restart-delay 0

            frame-relay intf-type dce

            frame-relay route 203 interface Serial6/3 302

            frame-relay route 204 interface Serial6/4 402

            frame-relay route 205 interface Serial6/5 502

            interface Serial6/3

            no ip address

            encapsulation frame-relay

            serial restart-delay 0

            frame-relay intf-type dce

            frame-relay route 301 interface Serial6/1 103

            frame-relay route 302 interface Serial6/2 203

            interface Serial6/4

            no ip address

            encapsulation frame-relay

            serial restart-delay 0

            frame-relay intf-type dce

            frame-relay route 401 interface Serial6/1 104

            frame-relay route 402 interface Serial6/2 204

            interface Serial6/5

            no ip address

            encapsulation frame-relay

            serial restart-delay 0

            frame-relay intf-type dce

            frame-relay route 501 interface Serial6/1 105

            frame-relay route 502 interface Serial6/2 205

            • 3. Re: RipNG over frame relay issue
              Learner

              Ing_Percy wrote:

               

              Hi!

               

              What is the FR configuration?

              Have you applied a frame-relay map for the the link-local address, too?

               

              Example:

              interface Serial0/0

              ipv6 address FE80::1 link-local

              ipv6 address 2001::2/64

              ipv6 rip RT0 enable

              frame-relay map ipv6 2001::1 201 broadcast

              frame-relay map ipv6 FE80::2 201

               

              Regards!

               

              Hi Percy,

               

              What do "frame-relay map" commands do? The frame-relay chapters from ICND2 don't use them.

              • 4. Re: RipNG over frame relay issue
                Ing_Percy

                Hi!

                 

                It is depending of your design:

                 

                *Frame-relay point-to-multipoint

                 

                interface Serial0/0

                ipv6 address FE80::1 link-local

                ipv6 address 2001::2/64

                ipv6 rip RT0 enable

                frame-relay map ipv6 2001::1 201 broadcast

                frame-relay map ipv6 FE80::2 201

                 

                *Frame-relay point-to-point

                 

                Example of configuration:

                interface Serial0/0

                ipv6 address FE80::1 link-local

                ipv6 address 2001::2/64

                ipv6 rip RT0 enable

                frame-relay interface-dlci 201

                • 5. Re: RipNG over frame relay issue
                  Ing_Percy

                  Hi!

                   

                  I Implemented a topology in GNS3 with RIPng using FR point-to-point and it works

                   

                  fr-ripng.JPG

                  R1

                  interface Serial2/0

                  no ip address

                  encapsulation frame-relay

                  !

                  interface Serial2/0.2 point-to-point

                  ipv6 address 1001::1/64

                  ipv6 rip RT0 enable

                  frame-relay interface-dlci 102

                  !

                  interface Serial2/0.3 point-to-point

                  ipv6 address 3001::1/64

                  ipv6 rip RT0 enable

                  frame-relay interface-dlci 103

                   

                  R2

                  interface Serial2/0

                  no ip address

                  encapsulation frame-relay

                  !

                  interface Serial2/0.2 point-to-point

                  ipv6 address 1001::2/64

                  ipv6 rip RT0 enable

                  frame-relay interface-dlci 201

                   

                  R3

                  interface Serial2/0

                  no ip address

                  encapsulation frame-relay

                  !

                  interface Serial2/0.3 point-to-point

                  ipv6 address 3001::2/64

                  ipv6 rip RT0 enable

                  frame-relay interface-dlci 301

                   

                  R1#sh ipv6 route rip

                  <output omitted>

                  R   2002::/64 [120/2]

                       via FE80::C802:FFF:FEC0:0, Serial2/0.2

                  R   2003::/64 [120/2]

                       via FE80::C803:1BFF:FE48:0, Serial2/0.3

                   

                  R1#ping 2002::1

                  Type escape sequence to abort.

                  Sending 5, 100-byte ICMP Echos to 2002::1, timeout is 2 seconds:

                  !!!!!

                  Success rate is 100 percent (5/5), round-trip min/avg/max = 8/16/24 ms

                   

                  R1#ping 2003::1

                  Type escape sequence to abort.

                  Sending 5, 100-byte ICMP Echos to 2003::1, timeout is 2 seconds:

                  !!!!!

                  Success rate is 100 percent (5/5), round-trip min/avg/max = 8/10/12 ms

                   

                  NOW

                  Check the following output:

                  R1#sh ipv6 int brief | sec Serial

                  Serial2/0              [up/up]

                      unassigned

                  Serial2/0.2            [up/up]

                      FE80::C801:21FF:FE08:0

                      1001::1

                  Serial2/0.3            [up/up]

                      FE80::C801:21FF:FE08:0

                      3001::1

                   

                  When you implement many point-to-point networks in all routers, a issue can be present (the same link-local address in each subinterface)

                  Then, configure ipv6 adress link-local in each subinterface manually and try again with the ping test.

                   

                  Regards!

                  • 6. Re: RipNG over frame relay issue
                    Learner

                    I found out why my config didn't work. I have an extra interface command "frame-relay lmi-type ansi" on R1, R2, R3 and FR switch.

                     

                    I think the default lmi type is cisco. Once I removed this command from all interfaces, as you guys did, the ping went through.

                     

                    So why does this matter? Are we not supposed to use ansi?

                     

                     

                    R3(config-if)#frame-relay lmi-type ?

                      cisco

                      ansi

                      q933a


                    R3(config-if)#

                    • 7. Re: RipNG over frame relay issue
                      Ing_Percy

                      Hi!

                       

                      The lmi types are incompatible betweem them.

                      In GNS3, the default lmi-type is ANSI

                      If already exists a explicit configuration of lmi-type, then it disabled the automatic detection

                       

                      You must check with the "show frame-relay lmi"

                       

                      Regards!

                      • 8. Re: RipNG over frame relay issue
                        Learner

                        Hi Percy,

                         

                        It seems the default is Cisco.

                         

                        I'm using C7200, Version 15.2

                         

                        R1#

                        R1#show run inter s4/0

                        Building configuration...


                        Current configuration : 93 bytes

                        !

                        interface Serial4/0

                        no ip address

                        encapsulation frame-relay

                        serial restart-delay 0

                        end


                        R1#

                        R1#show run inter s4/0.103

                        Building configuration...


                        Current configuration : 125 bytes

                        !

                        interface Serial4/0.103 point-to-point

                        ipv6 address 2013::1/64

                        ipv6 rip 1 enable

                        frame-relay interface-dlci 103

                        end


                        R1#

                        R1#show frame-relay lmi


                        LMI Statistics for interface Serial4/0 (Frame Relay DTE) LMI TYPE = CISCO

                          Invalid Unnumbered info 0            Invalid Prot Disc 0

                          Invalid dummy Call Ref 0              Invalid Msg Type 0

                          Invalid Status Message 0              Invalid Lock Shift 0

                          Invalid Information ID 0              Invalid Report IE Len 0

                          Invalid Report Request 0              Invalid Keep IE Len 0

                          Num Status Enq. Sent 268              Num Status msgs Rcvd 268

                          Num Update Status Rcvd 0              Num Status Timeouts 0

                          Last Full Status Req 00:00:41        Last Full Status Rcvd 00:00:41

                        R1#

                        R1#ping 2023::2

                        Type escape sequence to abort.

                        Sending 5, 100-byte ICMP Echos to 2023::2, timeout is 2 seconds:

                        !!!!!

                        Success rate is 100 percent (5/5), round-trip min/avg/max = 44/63/72 ms

                        R1#

                        • 9. Re: RipNG over frame relay issue
                          Ing_Percy

                          Hi!

                           

                          In my ancient IOS of GNS3, the default is ANSI

                           

                          R1#sh version | i IOS

                          Cisco IOS Software, 2600 Software (C2691-ADVENTERPRISEK9_SNA-M), Version 12.4(13b), RELEASE SOFTWARE (fc3)

                           

                          R1#sh frame-relay lmi

                          LMI Statistics for interface Serial0/0 (Frame Relay DTE) LMI TYPE = ANSI

                            Invalid Unnumbered info 0             Invalid Prot Disc 0

                            Invalid dummy Call Ref 0              Invalid Msg Type 0

                            Invalid Status Message 0              Invalid Lock Shift 0

                            Invalid Information ID 0              Invalid Report IE Len 0

                            Invalid Report Request 0              Invalid Keep IE Len 0

                            Num Status Enq. Sent 406              Num Status msgs Rcvd 407

                            Num Update Status Rcvd 0              Num Status Timeouts 0

                            Last Full Status Req 00:00:41         Last Full Status Rcvd 00:00:41