Guest

Preview Tool

Cisco Bug: CSCun03374 - Getting errors that interfac is not part of XC when CFM is added to XC

Last Modified

Jun 12, 2020

Products (1)

  • Cisco ASR 9000 Series Aggregation Services Routers

Known Affected Releases

4.2.3.BASE 4.2.3.FWDG

Description (partial)

Symptom:
bdxc_lookups for ?xcgroup:xcname? > 38 chars fails.  L2vpn/l2fib notifications for the same names succeed.


-	If you configure CFM /after/ configuring l2vpn, none of the MEPs will come up (the lookup fails)
-	If you configure CFM /before/ configuring l2vpn, the MEPs come up fine (cfmd stores the name locally when first configured & when l2vpn/l2fib notifications come in, we bring up the MEP)

The only triggers we have so far are
a)	An l2vpn config change, not low impact.
b)	A restart of l2fib/l2vpn, not low impact.
c)	Triggering a change in XC state (e.g. the customer tried enabling remote loopback & removing), not low impact.

Conditions:
when ?xcgroup:xcname? is greater than 38 characters
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.