MSO Bug and Feature requests

[ralphcarter]

Cisco Team,

Bug Discovered

• Rename contract in MSO does not work, it changes the name in the GUI of the MSO but when deployed, it maintains old name of the contract, unless you delete the contract and recreate from scratch

Feature Requests

• Unenforced/Enforced option from VRF
• Layer3 Out configuration
• Set Rules/Match Rules for Route-map and Route-Map configuration
• Bridge-domain - Advertise host routes option
• Bridge-domain - L3Out for profile and Route-Profile

I think the above are critical to establish a true multi-site without manually creating these objects.

[DerrickTJ]

That isn't really a bug. That is intended. MSO has a concept of display names that the APICs do not have. You'll notice under the display name is the actually name of the object. I'd prefer MSO just not have display names and follow the same logic the APIC have. Working with the API can get confusing when the display name and object name do not match.

L3Out configuration will always probably be done on the APIC as L3Outs are not something you can stretch.

Bridge-domain host route and L3out are there now as of release 4.0 or 4.1.