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.

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

NNI doesn't import ae sub interfaces #7

Open
XioNoX opened this issue Feb 8, 2019 · 3 comments
Open

NNI doesn't import ae sub interfaces #7

XioNoX opened this issue Feb 8, 2019 · 3 comments
Labels
enhancement New feature or request

Comments

@XioNoX
Copy link

XioNoX commented Feb 8, 2019

Subinterfaces such as ae2.2002, ae3.2003, etc.. are not being imported into Netbox and their IPs appear under the parent ae interface.
This is at least on Juniper MX routers running 13.3.

Please let me know how I can help troubleshoot it.

@aruhier
Copy link
Contributor

aruhier commented Feb 11, 2019

Hi,
Thanks a lot for your bugreport. I'm going to dig a bit, I don't remember if I did this on purpose or not (and let the user tag the parent interfaces into the right vlan instead of creating the subinterfaces).

@aruhier
Copy link
Contributor

aruhier commented Feb 11, 2019

Yes, I did this on purpose: https://github.com/Anthony25/netbox-netprod-importer/blob/master/netbox_netprod_importer/importer.py#L143

Would you like an option to import the subinterfaces?

@aruhier aruhier added the enhancement New feature or request label Feb 11, 2019
@XioNoX
Copy link
Author

XioNoX commented Feb 13, 2019

Ideally yeah, Netbox should see every configurable interfaces of the device, sub-interfaces included (at least for our usecase).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants