Guest

Preview Tool

Cisco Bug: CSCuq48542 - Comm arent propagated in vpnv4 advertisements after ipv4 mdt config

Last Modified

Sep 14, 2019

Products (1)

  • Cisco 12000 Series Routers

Known Affected Releases

12.0(33)S8

Description (partial)

Symptom:
GSR router does not send community and extended-community attributes to bgp vpnv4 neighbor, even though in the configuration of the neighbor, it is applied the command "neighbor x.x.x.x send-community both".

Conditions:
Issue happens when one bgp neighbor is already configured and activated in the bgp vpnv4 and mdt address-families, and then this same neighbor configuration is changed so it is added to an existing peer-group through the command "neighbor x.x.x.x peer-group xxxxxxx", only in the ipv4 mdt family. This will make the router stop sending the community an extended-community attributes in the vpnv4 session with this neighbor.

This issue only happens with this specific configuration order, to avoid triggering issue also apply the command in the vpnv4 address-family as recommended in the configuration guide.
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.