Guest

Preview Tool

Cisco Bug: CSCur46729 - ipv6 dot1q remote ping failed (main intf sometimes also failed)

Last Modified

Aug 07, 2018

Products (1)

  • Cisco Carrier Routing System

Known Affected Releases

5.4.0.BASE

Description (partial)

Symptom:
topo:
sunstone---ASR9K

Without the dot1q vlan configured, the physical interface remote back to back ping works. But not with the dot1q interface:
RP/0/RP0/CPU0:ott02-sim-09-uut#sh run int TenGigE0/RP0/CPU0/3
Wed Oct 29 19:29:22.659 UTC
interface TenGigE0/RP0/CPU0/3
 description interface7 -> ott02-sim-09-r1:Te0/3/0/0
 mtu 1514
 ipv4 address 91.1.0.1 255.255.255.0
 ipv6 address 901:a01:1::1/112
 load-interval 30
!

RP/0/RP0/CPU0:ott02-sim-09-uut#sh run int TenGigE0/RP0/CPU0/3.110
Wed Oct 29 19:29:26.692 UTC
interface TenGigE0/RP0/CPU0/3.110
 description interface15 -> ott02-sim-09-r1:Te0/3/0/0.110
 ipv4 address 109.1.1.1 255.255.255.0
 ipv6 address 2002:6d01:100::1/112
 encapsulation dot1q 110
!

RP/0/RP0/CPU0:ott02-sim-09-uut#

RP/0/RP0/CPU0:ott02-sim-09-uut#ping 901:a03:3::2
Wed Oct 29 19:29:06.156 UTC
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 901:a03:3::2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 54/58/59 ms
RP/0/RP0/CPU0:ott02-sim-09-uut#

RP/0/RP0/CPU0:ott02-sim-09-uut#ping 2002:6d01:100::2
Wed Oct 29 19:30:22.567 UTC
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2002:6d01:100::2, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
RP/0/RP0/CPU0:ott02-sim-09-uut#                    

The self ping works:
RP/0/RP0/CPU0:ott02-sim-09-uut#ping 2002:6d01:100::1
Wed Oct 29 19:30:54.682 UTC
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2002:6d01:100::1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
RP/0/RP0/CPU0:ott02-sim-09-uut#
RP/0/RP0/CPU0:ott02-sim-09-uut#sh ipv6 nei
Wed Oct 29 19:31:11.917 UTC
IPv6 Address                              Age Link-layer Addr State Interface            Location
901:a01:1::2                             24   a80c.0d63.7fe8 REACH Te0/RP0/CPU0/3       0/RP0/CPU0
fe80::aa0c:dff:fe63:7fe8                 19   a80c.0d63.7fe8 REACH Te0/RP0/CPU0/3       0/RP0/CPU0
[Mcast adjacency]                           - 0000.0000.0000 REACH Te0/RP0/CPU0/3       0/RP0/CPU0
fe80::aa0c:dff:fe63:7fe9                 580  a80c.0d63.7fe9 GLEAN Te0/RP0/CPU0/4       0/RP0/CPU0
[Mcast adjacency]                           - 0000.0000.0000 REACH Te0/RP0/CPU0/4       0/RP0/CPU0
[Mcast adjacency]                           - 0000.0000.0000 REACH Te0/RP0/CPU0/5       0/RP0/CPU0
901:a03:3::2                             42   a80c.0d63.7fea REACH Te0/RP0/CPU0/6       0/RP0/CPU0
fe80::aa0c:dff:fe63:7fea                 35   a80c.0d63.7fea REACH Te0/RP0/CPU0/6       0/RP0/CPU0
[Mcast adjacency]                           - 0000.0000.0000 REACH Te0/RP0/CPU0/6       0/RP0/CPU0
[Mcast adjacency]                           - 0000.0000.0000 REACH Te0/RP0/CPU0/3.110   0/RP0/CPU0
RP/0/RP0/CPU0:ott02-sim-09-uut#

Conditions:
Image info:
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.