cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1246
Views
15
Helpful
1
Replies

Data Center Network Manager freeform config

laurent.dewilde
Level 1
Level 1

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!

1 Accepted Solution

Accepted Solutions

laurent.dewilde
Level 1
Level 1

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

 

View solution in original post

1 Reply 1

laurent.dewilde
Level 1
Level 1

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

 

Review Cisco Networking for a $25 gift card