Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

question: How can I create a routed domain without associating it with a vlan pool #87

Closed
micronemo opened this issue May 17, 2024 · 1 comment · Fixed by #76
Closed

question: How can I create a routed domain without associating it with a vlan pool #87

micronemo opened this issue May 17, 2024 · 1 comment · Fixed by #76
Labels
question Further information is requested

Comments

@micronemo
Copy link

micronemo commented May 17, 2024 •
edited
Loading

How can I create a routed domain without associating it with a vlan pool which is a mandatory field

apic:
access_policies:
routed_domains:
- name: L3Out
vlan_pool: ??? <- mandatory

Leave the VLAN pool field blank because you do not need it for routed interface L3
For example, you need the pool for L3 connections with SVIs and subinterfaces.
@danischm danischm added the question Further information is requested label May 26, 2024
@danischm
Copy link
Member

We are adding this functionality in the next release.

@andbyrne andbyrne linked a pull request Jun 21, 2024 that will close this issue
AP routed domain input validation needs to be updated to make vlan_pool an optional value #76
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

AP routed domain input validation needs to be updated to make vlan_pool an optional value
3 participants
@micronemo @andbyrne @danischm