-
Notifications
You must be signed in to change notification settings - Fork 228
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
Batfish: aggregate with no bound interfaces has bandwidth 0 #4125
Conversation
Not null, which breaks downstream pipeline. Fix batfish#4124
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewable status: 0 of 3 files reviewed, 1 unresolved discussion (waiting on @progwriter)
a discussion (no related file):
Some thoughts:
- PC1 itself does not appear in the VI Model. That's bad, right?
- Is this the right fix?
Codecov Report
@@ Coverage Diff @@
## master #4125 +/- ##
============================================
- Coverage 75.23% 75.13% -0.11%
+ Complexity 24877 24656 -221
============================================
Files 2030 2026 -4
Lines 99493 98628 -865
Branches 11796 11723 -73
============================================
- Hits 74857 74106 -751
+ Misses 19293 19194 -99
+ Partials 5343 5328 -15
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewable status: 0 of 3 files reviewed, 1 unresolved discussion (waiting on @dhalperi and @progwriter)
a discussion (no related file):
Previously, dhalperi (Dan Halperin) wrote…
Some thoughts:
- PC1 itself does not appear in the VI Model. That's bad, right?
- Is this the right fix?
If i understand portchannel interfaces and subinterfaces correctly, i believe you're right that PC1 ought to appear. However, CiscoConfiguration relies on it being explicitly defined; see also this test config.
I think we want to automatically create a VI portchannel interface when a subinterface is defined but its parent isn't (i.e., at the point in CiscoConfiguration linked above). Then i don't think it would be possible for an AGGREGATE_CHILD
interface to have no BIND
dependency (at least for Cisco portchannel interfaces).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 3 of 3 files at r1.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @dhalperi)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @dhalperi)
a discussion (no related file):
Another issue is why is ospf cost being computed in the first place. This interface should be down.
Based on offline discussion, it appears that conversion should create dependencies on non-existent interfaces and code in snapshot post-processing should turn down interfaces with bind dependencies that point to non-existent interfaces. Some other code (such as l1 logical topology computation) might need to be special cased as well.
Not null, which breaks downstream pipeline.
Fix #4124