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

ipdevinfo doesn't list aggregators for some Juniper interfaces #1519

Closed
lunkwill42 opened this issue Jun 1, 2017 · 0 comments
Closed

ipdevinfo doesn't list aggregators for some Juniper interfaces #1519

lunkwill42 opened this issue Jun 1, 2017 · 0 comments
Assignees
Labels
Milestone

Comments

@lunkwill42
Copy link
Member

It appears Juniper devices will report multiple aggregator ports for some aggregated interfaces. These seem to be largely various logical subunits of the main aggregator interface.

The codebase is not equipped to handle this well, even though NAV's data model is.

A simple heuristic here would be to have Interface.get_aggregator() only return the interface with the lowest ifIndex, assuming this is the lowest level interface.

A more complex heuristic would examine the interface relationships in ifStackTable to decide whether they are logically connected or not.

Another more complex, and probably undesirable heuristic, would be to allow for multiple aggregators, and also to report linkDegraded for all of them when an aggregated interface link loss is detected.

@lunkwill42 lunkwill42 added the bug label Jun 1, 2017
@lunkwill42 lunkwill42 added this to the 4.6.3 milestone Jun 1, 2017
@lunkwill42 lunkwill42 self-assigned this Jun 1, 2017
@lunkwill42 lunkwill42 modified the milestones: 4.7.0, 4.6.3 Jun 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant