10-12-2021 12:17 AM
Since private VLANs cannot be configured via DCNM, we thought to add this config via the freeform template.
The VLANs (networks in DCNM) are first provisioned as a Layer 2-only VLAN on the fabric.
Next, we add the freeform config by right-clicking on a leaf -> view/edit policies -> add a new policy based on the freeform template.
The following information is entered:
feature private-vlan
vlan 940
private-vlan primary
private-vlan association 941
vlan 941
private-vlan isolated
However, when viewing the generated config, DCNM makes the following out of it:
feature private-vlan private-vlan primary private-vlan association 941 private-vlan isolated
So the "vlan 940" and "vlan 941" commands are ignored. Any ideas on how to tackle this?
An additional question: is it mandatory to create the primary VLAN as an SVI (anycast gateway)?
Thanks a lot!
Solved! Go to Solution.
10-15-2021 04:05 AM
Ok, found the solution.
The intent and the spacing must be exactly as the 'sh run' output. Like this:
(The below CLI can be split into 2 different Freeform templates, one for VLAN 940 and another for VLAN 941, as an FYI).
feature private-vlan vlan 940 private-vlan primary private-vlan association 941 vlan 941 private-vlan isolated
10-15-2021 04:05 AM
Ok, found the solution.
The intent and the spacing must be exactly as the 'sh run' output. Like this:
(The below CLI can be split into 2 different Freeform templates, one for VLAN 940 and another for VLAN 941, as an FYI).
feature private-vlan vlan 940 private-vlan primary private-vlan association 941 vlan 941 private-vlan isolated
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide