-
Notifications
You must be signed in to change notification settings - Fork 231
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
Feat(eos_designs): Add support for l3_port_channel_interfaces for WAN #4752
base: devel
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -23,10 +23,18 @@ wan_router: | |
id: 11 | ||
mgmt_ip: 192.168.17.20/24 | ||
uplink_switches: [site3-leaf1] | ||
l3_interfaces: | ||
- name: Ethernet4 | ||
peer_interface: Ethernet8 | ||
l3_port_channels: | ||
- name: Port-Channel4 | ||
mode: active | ||
member_interfaces: | ||
- name: Ethernet4 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. let's set |
||
peer: inet-cloud | ||
ip_address: dhcp | ||
dhcp_ip: 100.64.30.2 | ||
profile: INTERNET-WAN-INTERFACE | ||
dhcp_accept_default_route: true | ||
ipv4_acl_in: ACL-INTERNET-IN | ||
peer_port_channel: Port-Channel8 | ||
wan_carrier: REGION2-INTERNET-CORP | ||
wan_circuit_id: inet-site3-wan1 | ||
flow_tracking: | ||
enabled: true |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -50,11 +50,15 @@ spine: | |
- name: Ethernet7 | ||
description: site2-wan2-Ethernet4 | ||
ip_address: 100.64.21.1/24 | ||
- name: Ethernet8 | ||
description: site3-wan1-Ethernet4 | ||
l3_port_channels: | ||
- name: Port-Channel8 | ||
mode: active | ||
description: site3-wan1-Port-Channel4 | ||
member_interfaces: | ||
- name: Ethernet8 | ||
ip_address: 100.64.30.1/24 | ||
structured_config: | ||
dhcp_server_ipv4: true | ||
raw_eos_cli: | | ||
dhcp server ipv4 | ||
Comment on lines
+60
to
+61
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. can we move this back to structured_config? If not lets open an issue to add this in eos_cli_config_gen There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. confirmed it is not there - lets open an issue to support this There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Issue has been opened for Once we have the fix, we could replace |
||
structured_config: | ||
router_bgp: | ||
# Neighbor definition for site2-wan2 | ||
|
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.
Should the ACL be there? I think it should not be inherited?
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.
You might be correct here.
The generated config itself does not have any ACL being applied to Ethernet4 interface.
ACL-INTERNET-IN_Port-Channel4 is being applied for Port-Channel4 interface. So that seems fine.
Issue is with documentation table being generated.
This documentation related snippet appears to be being generated via logic in
python-avd/pyavd/_eos_cli_config_gen/j2templates/documentation/ethernet-interfaces.j2
lines 430-440In the case when ethernet intf is a member of a port-channel, we seem to be setting ip_address, vrf, mtu, shutdown, acl_in, acl_out for ethernet_interface based on values derived from corresponding Port-Channel<> interface.
Would it be correct to inherit values for such attributes?