05-12-2021 07:45 AM - edited 05-19-2021 03:56 AM
We are testing the setup capabilites on IOS-XE (on CAT9200L and 9300L) and it was working great with IOS-XE 16.12.05b (cat9k_lite_iosxe.16.12.05b.SPA.bin) But with 17.03.03 (cat9k_lite_iosxe.17.03.03.SPA.bin) we get following error while booting up:
*May 12 14:29:17.015: AUTOINSTALL: GigabitEthernet0/0 releasing DHCP ip address 172.16.220.6
*May 12 14:29:17.081: %IP-4-CLASS: Bad IP address and mask 0.0.0.0/0 in class_resolve()
And after that, it just loops with:
No startup-config, starting autoinstall/pnp/ztp... Autoinstall will terminate if any input is detected on console No startup-config, starting autoinstall/pnp/ztp... Autoinstall will terminate if any input is detected on console No startup-config, starting autoinstall/pnp/ztp... Autoinstall will terminate if any input is detected on console No startup-config, starting autoinstall/pnp/ztp...
If we cancel the task and see the configuration of the management interface, the ip part is disabled:
Switch#sh run int gig 0/0 Building configuration... Current configuration : 94 bytes ! interface GigabitEthernet0/0 vrf forwarding Mgmt-vrf no ip address negotiation auto end
If we then manually set the interface to dhcp, we immediately get an IP address.
Switch#sh run int gig 0/0 Building configuration... Current configuration : 96 bytes ! interface GigabitEthernet0/0 vrf forwarding Mgmt-vrf ip address dhcp negotiation auto end Switch# *May 12 14:34:50.663: %DHCP-6-ADDRESS_ASSIGN: Interface GigabitEthernet0/0 assigned DHCP address 172.16.220.6, mask 255.255.255.0, hostname
We have the exact same setup, only difference is the Firmware version. So this seems like a bug in the firmware 17.03.03
EDIT: Just tested all the IOS-XE 17 versions (17.03.01/17.03.02a/17.03.03) and they all have the same issue. When going back to 16.12.05b, the issue is gone.
EDIT2: Just tested on the 9300L devices, and they do not suffer this issue. I get an IP address on the Gi0/0 interface with firmware 17.03.03 on a C9300L-24P-4G
04-14-2023 05:08 PM
Seems like the bug happens during the boot-up process. As a workaround, I've found it helps to let the switch boot up first with the interface disconnected. Once the switch is up and running, connect the interface.
07-30-2024 10:26 AM
We're seeing the same thing with 17.9.5. If we connect the gi0/0 port when the device is powered on, autoinstall won't ever pull an IP address - if we leave the other side shut until the switch fully boots, then we're good to go. Took a lot of debugging to figure this out.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide