You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
• Cannot add a Multicast Route-map Source Filter / Destination Filter on existing BD when previous RM value is empty.
• Failure is not seen when a previous Multicast RM Source/Destination Filter is already configured on the BD.
For instance, these two scenarios are working:
• push playbook with the same RM as the current one configured under the BD.
• Replace an existing Multicast RM Source Filter /destination filter under the BD.
Affected Module Name(s):
mso_schema_template_bd
MSO version and MSO Platform
ND: 3.0.1i
NDO: 4.2(3k) / 4.4.1.1012
APIC version and APIC Platform for Site Level Resources
github-actionsbot
changed the title
Adding Multicast Route-map Source Filter/ Destination Filter on existing BD fails when previous RM values are empty
Adding Multicast Route-map Source Filter/ Destination Filter on existing BD fails when previous RM values are empty (DCNE-305)
Feb 20, 2025
Community Note
Description
• Cannot add a Multicast Route-map Source Filter / Destination Filter on existing BD when previous RM value is empty.
• Failure is not seen when a previous Multicast RM Source/Destination Filter is already configured on the BD.
For instance, these two scenarios are working:
• push playbook with the same RM as the current one configured under the BD.
• Replace an existing Multicast RM Source Filter /destination filter under the BD.
Affected Module Name(s):
mso_schema_template_bd
MSO version and MSO Platform
ND: 3.0.1i
NDO: 4.2(3k) / 4.4.1.1012
APIC version and APIC Platform for Site Level Resources
APIC: 5.3(2c)
Collection versions
cisco.mso 2.9.0
Output/ Error message
Expected Behavior
• Associate/add new Multicast Route-map for Source or Destination Filter under a BD with L3 Multicast enabled.
Actual Behavior
• error at playbook execution
Playbook tasks to Reproduce
The text was updated successfully, but these errors were encountered: