Guest

Preview Tool

Cisco Bug: CSCvw01064 - J2: CFM Ping and traceroute fails for Bundle interface with rewrite ingress tag configured

Last Modified

Oct 14, 2020

Products (1)

  • Cisco ASR 9000 Series Aggregation Services Routers

Known Affected Releases

7.3.1.BASE

Description (partial)

Symptom:
J2: CFM Ping and traceroute fails for Bundle interface with rewrite ingress tag configured

Conditions:
when bundle has rewrite ingress tag configured , ethernet cfm ping fails 

RP/0/RP0/CPU0:J2#show ru int bundle-Ether 201.301
interface Bundle-Ether201.301 l2transport
 encapsulation dot1q 301 second-dot1q 301
 rewrite ingress tag pop 2 symmetric
 ethernet cfm
  mep domain bun_sub_up service bun_sub_upmep301 mep-id 15
  !
  mep domain bun_sub_down service bun_sub_downmep301 mep-id 35
  !


RP/0/RP0/CPU0:J2#ping ethernet  cfm domain bun_sub_up service bun_sub_upmep301 mep-id 16 source interface bundle-Ether 201.301
Type escape sequence to abort.
Sending 5 CFM Loopbacks, timeout is 2 seconds -
Domain bun_sub_up (level 3), Service bun_sub_upmep301
Source: MEP ID 15, interface Bundle-Ether201.301
Target: d46a.35ee.04d0 (MEP ID 16):
  Running (5s) ...
Success rate is 0.0 percent (0/5), round-trip min/avg/max = 0/0/0 ms
RP/0/RP0/CPU0:J2#traceroute ethernet  cfm domain bun_sub_up service bun_sub_upmep301 mep-id 16 source interface bundle-Ether 201.301
Type escape sequence to return to prompt.

Traceroutes in domain bun_sub_up (level 3), service bun_sub_upmep301
Source: MEP-ID 15, interface Bundle-Ether201.301
================================================================================
Traceroute at 2020-10-07 14:49:47 to d46a.35ee.04d0,
TTL 64, Trans ID 988039577:

  Running (7s) ...

Hop Hostname/Last            Ingress MAC/name       Egress MAC/Name        Relay
--- ------------------------ ---------------------- ---------------------- -----
  1 J2                       b402.1631.1488 [Ok]                           FDB  
      0000-b402.1631.1488    BE201.301                                          
Replies dropped: 0
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.