What can cause a configuration update to stall and fail?

[jpye]

What can cause a configuration update to stall and fail?

[GeorgiaMason]

*Or a firewall block, updates use UPD 12222, TCP 22 or HTTP 80, TCP 443. If you can pull tech data or SSH in from the HM, it's probably not firewall because those use the same ports I think.

[GeorgiaMason · Accepted solution]

Generally it either means one of the commands used to build the config was rejected for some reason (check the failure message, it should give you the line that failed, I run that on the CLI to see what the error actually was and go from there), or that it lost connection to the internet for some reason during the push.

Things we have run in to in the past:

• IP method is changing, and the new address doesn't work for some reason (can't reach new DHCP server, IP conflict, etc)
• Management or native VLAN is changing and isn't supported by the switch port/backend network (check the network policy proper, the advanced settings in the network policy, and device specific settings in Monitor)
• Speaking of VLANs, I'd check those anyway (there's a probe in the GUI or you can do it on the CLI)
• Check DNS
• Changing Eth mode (from backhaul to bridge-access for instance)