Options

RIPng strange behavior?

tomislav91tomislav91 Member Posts: 59 ■■□□□□□□□□
in CCNP
Does it possible that I ping something, and in period of time 3,4 min, it is unreachable and request timed out? 
PC>ping 2A00:7F00::260:70FF:FE20:B84A  
Pinging 2A00:7F00::260:70FF:FE20:B84A with 32 bytes of data: 
 Reply from 2A00:7F00::260:70FF:FE20:B84A: bytes=32 time=2111ms TTL=121
 Reply from 2A00:7F00::260:70FF:FE20:B84A: bytes=32 time=3381ms TTL=121
 Reply from 2A00:7F00::260:70FF:FE20:B84A: bytes=32 time=2305ms TTL=121
 Reply from 2A00:7F00::260:70FF:FE20:B84A: bytes=32 time=2164ms TTL=121
  Ping statistics for 2A00:7F00::260:70FF:FE20:B84A:     Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
 Approximate round trip times in milli-seconds:    
 Minimum = 2111ms, Maximum = 3381ms, Average = 2490ms  
 PC>ping 2A00:7F00::260:70FF:FE20:B84A 
 Pinging 2A00:7F00::260:70FF:FE20:B84A with 32 bytes of data: 
 Reply from 2A01:6AA0:C000:0:204:9AFF:FE2C:C839: Destination host unreachable.
 Reply from 2A01:6AA0:C000:0:204:9AFF:FE2C:C839: Destination host unreachable.
 Reply from 2A01:6AA0:C000:0:204:9AFF:FE2C:C839: Destination host unreachable.
 Reply from 2A01:6AA0:C000:0:204:9AFF:FE2C:C839: Destination host unreachable. 
 Ping statistics for 2A00:7F00::260:70FF:FE20:B84A:   
  Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), 
 PC>ping 2A00:7F00::260:70FF:FE20:B84A  
Pinging 2A00:7F00::260:70FF:FE20:B84A with 32 bytes of data:  
Request timed out. 
Request timed out.
 Request timed out.
 Request timed out.
  Ping statistics for 2A00:7F00::260:70FF:FE20:B84A:   
  Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

PC>tracert 2A00:7F00::260:70FF:FE20:B84A 
 Tracing route to 2A00:7F00::260:70FF:FE20:B84A over a maximum of 30 hops:
     1   *         0 ms      0 ms      2A01:6AA0:C000:0:204:9AFF:FE2C:C839 
  2   0 ms      0 ms      0 ms      2001:4C28:26:1:2D0:D3FF:FE16:8901 
  3   25 ms     12 ms     12 ms     2001:4C28:23:1:290:2BFF:FE16:D02 
  4   *         12 ms     13 ms     2001:4C28:7:1:201:C9FF:FE3E:4E01
   5   12 ms     14 ms     14 ms     2001:4C28:5:1:20A:F3FF:FEC6:9D02
   6   35 ms     10 ms     146 ms    2001:1B38:11:1:2D0:58FF:FED0:C702 
  7   23 ms     23 ms     24 ms     2001:1B38:13:2:2E0:A3FF:FE7D:2001
   8   23 ms     23 ms     34 ms     2A00:7F00::260:70FF:FE20:B84A 
 Trace complete.

And this behaviour 
PC>tracert 2A01:6A00:4000:0:206:2AFF:FE4D:EEB8 
 Tracing route to 2A01:6A00:4000:0:206:2AFF:FE4D:EEB8 over a maximum of 30 hops: 
    1   1 ms      0 ms      0 ms      2A02:5180:8000:0:203:E4FF:FE27:A902 
 2   0 ms      *         470 ms    2A02:5180:8000:0:203:E4FF:FE27:A902  
 3   *         1 ms      *         Request timed out.  
 4   0 ms      *         0 ms      2A02:5180:8000:0:203:E4FF:FE27:A902 
  5   *         0 ms      *         Request timed out.  
 6   218 ms    *         0 ms      2A02:5180:8000:0:203:E4FF:FE27:A902 
  7   *         71 ms     *         Request timed out. 
  8   0 ms      *         0 ms      2A02:5180:8000:0:203:E4FF:FE27:A902 
  9   *         0 ms      *         Request timed out.   
10   0 ms      *         0 ms     2A02:5180:8000:0:203:E4FF:FE27:A902
I didn't wait all 30 hops, but same behavior is, and at the end, show destination IP and trace complete. But destination hos unreachable allways. But router show his route. It pings 2 PC from 4 at this network, but it does not make sense, all routes come through that router, and the second one.
Router22#sh ipv6 ro
IPv6 Routing Table - 13 entries
Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP
       U - Per-user Static route, M - MIPv6
       I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary
       O - OSPF intra, OI - OSPF inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
       ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
       D - EIGRP, EX - EIGRP external
R   2001:1B38::/32 [120/1]
     via FE80::2E0:8FFF:FE2B:5852, FastEthernet0/0
R   2001:4C28::/32 [120/1]
     via FE80::2E0:8FFF:FE2B:5852, FastEthernet0/0
C   2A00:C10:8:1::/64 [0/0]
     via ::, FastEthernet0/0
L   2A00:C10:8:1:207:ECFF:FE32:101/128 [0/0]
     via ::, FastEthernet0/0
R   2A00:7F00::/32 [120/1]
     via FE80::2E0:8FFF:FE2B:5852, FastEthernet0/0
R   2A01:6AA0::/32 [120/1]
     via FE80::2E0:8FFF:FE2B:5852, FastEthernet0/0
C   2A02:5180::/64 [0/0]
     via ::, FastEthernet0/1
L   2A02:5180::207:ECFF:FE32:102/128 [0/0]
     via ::, FastEthernet0/1
C   2A02:5180:4000::/64 [0/0]
     via ::, FastEthernet1/0
L   2A02:5180:4000:0:203:E4FF:FE27:A901/128 [0/0]
     via ::, FastEthernet1/0
C   2A02:5180:8000::/64 [0/0]
     via ::, FastEthernet1/1
L   2A02:5180:8000:0:203:E4FF:FE27:A902/128 [0/0]
     via ::, FastEthernet1/1
L   FF00::/8 [0/0]
     via ::, Null0

Router#sh ipv6 route
IPv6 Routing Table - 14 entries
Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP
       U - Per-user Static route, M - MIPv6
       I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary
       O - OSPF intra, OI - OSPF inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
       ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
       D - EIGRP, EX - EIGRP external
S   2001:1B38::/32 [1/0]
     via 2A00:C10:6:1:20A:F3FF:FEC6:9D01
S   2001:4C28::/32 [1/0]
     via 2A00:C10:7:1:290:2BFF:FE16:D01
C   2A00:C10:6:1::/64 [0/0]
     via ::, FastEthernet0/0
L   2A00:C10:6:1:204:9AFF:FE05:5501/128 [0/0]
     via ::, FastEthernet0/0
C   2A00:C10:7:1::/64 [0/0]
     via ::, FastEthernet0/1
L   2A00:C10:7:1:204:9AFF:FE05:5502/128 [0/0]
     via ::, FastEthernet0/1
C   2A00:C10:8:1::/64 [0/0]
     via ::, FastEthernet1/0
L   2A00:C10:8:1:2E0:8FFF:FE2B:5852/128 [0/0]
     via ::, FastEthernet1/0
S   2A00:7F00::/32 [1/0]
     via 2A00:C10:6:1:20A:F3FF:FEC6:9D01
S   2A01:6AA0::/32 [1/0]
     via 2A00:C10:7:1:290:2BFF:FE16:D01
R   2A02:5180::/64 [120/2]
     via FE80::207:ECFF:FE32:101, FastEthernet1/0
R   2A02:5180:4000::/64 [120/2]
     via FE80::207:ECFF:FE32:101, FastEthernet1/0
R   2A02:5180:8000::/64 [120/2]
     via FE80::207:ECFF:FE32:101, FastEthernet1/0
L   FF00::/8 [0/0]
     via ::, Null0

r53.jpg 40.2K
· Share on FacebookShare on Twitter

Comments

  • Options
    lrblrb Member Posts: 526
    RIP uses a default flush timer of 4 minutes. Does the router in the middle flap some RIP learned routes? If they continually enter the RIPng database and then expire, then come back, I would say that there is a misconfiguration somewhere.

    Or maybe its just a weird PT bug?
    · Share on FacebookShare on Twitter
  • Options
    tomislav91tomislav91 Member Posts: 59 ■■□□□□□□□□
    Because i want someone to just take a look of my pkt file to look, am I wrong or don't. But I double check it.

    This is the rest of my network, red is PC that don't ping. Black is static routes, and in routers are in redistribute static state.

    But is weard that come to router, and request timed out, and tat again, how he doesn't know route, when it is present in router table
    Router22#sh ipv6 route 
IPv6 Routing Table - 13 entries
Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP
       U - Per-user Static route, M - MIPv6
       I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary
       O - OSPF intra, OI - OSPF inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
       ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
       D - EIGRP, EX - EIGRP external
R   2001:1B38::/32 [120/1]
     via FE80::2E0:8FFF:FE2B:5852, FastEthernet0/0
R   2001:4C28::/32 [120/1]
     via FE80::2E0:8FFF:FE2B:5852, FastEthernet0/0
C   2A00:C10:8:1::/64 [0/0]
     via ::, FastEthernet0/0
L   2A00:C10:8:1:207:ECFF:FE32:101/128 [0/0]
     via ::, FastEthernet0/0
R   2A00:7F00::/32 [120/1]
     via FE80::2E0:8FFF:FE2B:5852, FastEthernet0/0
[B]R   2A01:6AA0::/32 [120/1]
     via FE80::2E0:8FFF:FE2B:5852, FastEthernet0/0[/B]
C   2A02:5180::/64 [0/0]
     via ::, FastEthernet0/1
L   2A02:5180::207:ECFF:FE32:102/128 [0/0]
     via ::, FastEthernet0/1
C   2A02:5180:4000::/64 [0/0]
     via ::, FastEthernet1/0
L   2A02:5180:4000:0:203:E4FF:FE27:A901/128 [0/0]
     via ::, FastEthernet1/0
C   2A02:5180:8000::/64 [0/0]
     via ::, FastEthernet1/1
L   2A02:5180:8000:0:203:E4FF:FE27:A902/128 [0/0]
     via ::, FastEthernet1/1
L   FF00::/8 [0/0]
     via ::, Null0

    Look this, in period in 1,2 min. First, it doesn't ping, ok, i look tracert, and stops at some router, ok, went there, show ipv6 route, no all routes? Only few, then, check all in close of him, it's OK, check him again, it's OK, try to tracert again, it's OK, ping..Well, it's ok?
    PC>ping 2A01:6AA0:C000:0:2D0:D3FF:FED4:682D

Pinging 2A01:6AA0:C000:0:2D0:D3FF:FED4:682D with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 2A01:6AA0:C000:0:2D0:D3FF:FED4:682D:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

PC>tracert 2A01:6AA0:C000:0:2D0:D3FF:FED4:682D

Tracing route to 2A01:6AA0:C000:0:2D0:D3FF:FED4:682D over a maximum of 30 hops: 

  1   0 ms      0 ms      3 ms      2A02:5180:4000:0:203:E4FF:FE27:A901
  2   0 ms      0 ms      0 ms      2A00:C10:8:1:2E0:8FFF:FE2B:5852
  3   0 ms      11 ms     11 ms     2A00:C10:7:1:290:2BFF:FE16:D01
  4   13 ms     12 ms     10 ms     2001:4C28:23:1:2D0:D3FF:FE16:8902
  5   *         *         *         Request timed out.
  6   *         *         *         Request timed out.
  7   *         *         
Control-C
^C
PC>tracert 2A01:6AA0:C000:0:2D0:D3FF:FED4:682D

Tracing route to 2A01:6AA0:C000:0:2D0:D3FF:FED4:682D over a maximum of 30 hops: 

  1   385 ms    0 ms      0 ms      2A02:5180:4000:0:203:E4FF:FE27:A901
  2   281 ms    0 ms      0 ms      2A00:C10:8:1:2E0:8FFF:FE2B:5852
  3   794 ms    880 ms    467 ms    2A00:C10:7:1:290:2BFF:FE16:D01
  4   770 ms    1069 ms   1642 ms   2001:4C28:23:1:2D0:D3FF:FE16:8902
  5   2867 ms   3409 ms   822 ms    2001:4C28:26:1:201:C7FF:FEEE:B902
  6   1101 ms   709 ms    1164 ms   2A01:6AA0:C000:0:2D0:D3FF:FED4:682D

Trace complete.

PC>ping 2A01:6AA0:C000:0:2D0:D3FF:FED4:682D

Pinging 2A01:6AA0:C000:0:2D0:D3FF:FED4:682D with 32 bytes of data:

Reply from 2A01:6AA0:C000:0:2D0:D3FF:FED4:682D: bytes=32 time=22ms TTL=123
Reply from 2A01:6AA0:C000:0:2D0:D3FF:FED4:682D: bytes=32 time=32ms TTL=123
Reply from 2A01:6AA0:C000:0:2D0:D3FF:FED4:682D: bytes=32 time=246ms TTL=123
Reply from 2A01:6AA0:C000:0:2D0:D3FF:FED4:682D: bytes=32 time=732ms TTL=123

Ping statistics for 2A01:6AA0:C000:0:2D0:D3FF:FED4:682D:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 22ms, Maximum = 732ms, Average = 258ms

    But no have sense, when go through same router, must past his. I don't know why only same address and request timed error showing..
    · Share on FacebookShare on Twitter
Sign In or Register to comment.