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

# iosxe_vlan must be replaced // long trink allowed vlan lists // timeout issues? #164

Open
Aswertus opened this issue Jun 1, 2024 · 0 comments

Comments

@Aswertus
Copy link

Aswertus commented Jun 1, 2024

Hi!

I'm sorry that I have to bother you all again! First! Thank you so much for your work for this TF-Provider. It made my life so much easier when replacing an old 4k5 for a new 9k5 :)

A thing stumbled into latley is, that TerraForm sometimes wants to replace all my within TF defined vlans. It doesnt seem to change anything if I apply it, but its still scary every time, since the one 9k5 is my Core-Switch/Router

# iosxe_vlan.vlan["999"] must be replaced -/+ resource "iosxe_vlan" "vlan" { ~ id = "Cisco-IOS-XE-native:native/vlan/Cisco-IOS-XE-vlan:vlan-list=999" -> (known after apply) + name = "vpc-keep-alive" + shutdown = false + vlan_id = 999 # forces replacement }

Similar thing happens with switchport interfaces which have long vlan-allowed lists.

# iosxe_interface_switchport.switchport["7"] will be updated in-place ~ resource "iosxe_interface_switchport" "switchport" { id = "Cisco-IOS-XE-native:native/interface/Port-channel=7/switchport-config/switchport" name = "7" + trunk_allowed_vlans = "1,15,60,100,111,112,250,1210-1219,1232,2000-2500" # (3 unchanged attributes hidden) }

my first thought was that the provider might be unhappy if the CLI splits it into two rows
like
switchport trunk allowed vlan 1,60,64,65,67,68,100,111,112,250,1210-1219
switchport trunk allowed vlan add 2000-2500

but I encountered it also with "shorter" interfaces.

Are any timeout problems known? I do the whole switch configuration within one script
system-settings, vlan, routing, vrf, acls, interfaces, port-channels and with all together the provider seems to struggle a bit.

Especially when creating Portchannels on this switch, it often fails while applying and I have to redo it a few times until everything works. chaning isnt a problem. it only struggels in the creation process

I have a seconf 9k5 where i do only interface config and there everything works fine without any issues.

I can provice you my whole TF+Yaml Code if nescessary. there isnt anything secret in it ;)

Thank you very much!

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

No branches or pull requests

1 participant