Skip to content

feat(iosxe): add mtu to port-channel and ip_mtu to loopback and vlan interfaces#496

Open
ChristopherJHart wants to merge 4 commits intoCiscoDevNet:mainfrom
ChristopherJHart:feat/iosxe-interface-mtu
Open

feat(iosxe): add mtu to port-channel and ip_mtu to loopback and vlan interfaces#496
ChristopherJHart wants to merge 4 commits intoCiscoDevNet:mainfrom
ChristopherJHart:feat/iosxe-interface-mtu

Conversation

@ChristopherJHart
Copy link
Copy Markdown
Collaborator

@ChristopherJHart ChristopherJHart commented Apr 27, 2026

Summary

  • Add interface-level mtu attribute to iosxe_interface_port_channel resource and data source
  • Add ip_mtu attribute to iosxe_interface_loopback and iosxe_interface_vlan resources and data sources

Fixes #441

Notes

  • Live device testing revealed that interface-level mtu (L2 frame size) is only supported on Port-Channel interfaces (physical switches like C9300). Loopback, VLAN, and Tunnel interfaces require ip mtu (L3 packet size) instead.
  • Tunnel already had ip_mtu support, so no change was needed there.
  • YANG source: interface-common-grouping in Cisco-IOS-XE-interfaces.yang defines both mtu (uint16, 64-18000) and ip/mtu (uint16, 68-18000)
  • Tested on Cat8kv (Loopback ip mtu 1400), Cat9kv (VLAN ip mtu 1400), and C9300 physical switch (Port-Channel mtu 1500)

AI Generation Metadata

  • AI Generated: Yes
  • AI Tool: claude-code
  • AI Model: opus-4.6
  • AI Reason: feature implementation across provider definitions, code generation, and documentation

…unnel interfaces

Add the interface-level mtu attribute to iosxe_interface_loopback,
iosxe_interface_vlan, iosxe_interface_port_channel, and
iosxe_interface_tunnel resources and data sources, matching the existing
support in iosxe_interface_ethernet.

For netascode/nac-iosxe#441

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
AI-Generated: yes
AI-Tool: claude-code
AI-Model: opus-4.6
AI-Percent: 100
AI-Reason: add mtu to interface definitions and regenerate
ChristopherJHart and others added 2 commits April 26, 2026 21:15
…e-mtu

# Conflicts:
#	CHANGELOG.md
#	docs/guides/changelog.md
#	templates/guides/changelog.md.tmpl
…nel only

Live device testing showed that interface-level mtu (L2) is only
supported on Port-Channel (physical switches). Loopback, VLAN, and
Tunnel interfaces require ip mtu (L3) instead. Tunnel already had
ip/mtu, so this change adds ip/mtu to loopback and vlan, keeps mtu
on port-channel, and removes the non-functional mtu from tunnel.

Tested on Cat8kv (Loopback ip mtu), Cat9kv (VLAN ip mtu), and
C9300 physical switch (Port-Channel mtu).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
AI-Generated: yes
AI-Tool: claude-code
AI-Model: opus-4.6
AI-Percent: 41
AI-Reason: pivot to ip_mtu for loopback/vlan, keep mtu for port-channel only
@ChristopherJHart ChristopherJHart changed the title feat(iosxe): add mtu attribute to loopback, vlan, port-channel, and tunnel interfaces feat(iosxe): add mtu to port-channel and ip_mtu to loopback and vlan interfaces Apr 27, 2026
@aitestino aitestino added the dependencies Pull requests that update a dependency file label Apr 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Enhancement] Add MTU support for Loopback, VLAN, Port-Channel, and Tunnel interfaces

2 participants