Multiple changes in the CLI - one restart of the ISE application

[Gioacchino]

Me again

Is there a way to apply more than one significant change in the ISE CLI and having a final restart of the application, instead of having to wait for a ISE restart every time one of them is applied?

I had to modify an IP address of an interface and add two ip host ... and in total I experienced 3 restarts. Each time is 10 minutes.

TIA, Gio

[Aref Alsouqi]

Welcome back Gio. I think the only option you would have in these cases would be to trying to type "no" when ISE prompts you for the services restart and see if it allows you to carry on with the other changes.

[Gioacchino]

Yeah, sorry. It slipped my mind such a simple answer. Too busy on many fronts that I lost the capability to stop and think.
Thanks again @Aref

[Aref Alsouqi]

No worries Gio, I hear you man : - )

[ieraceja]

So this doesn't actually work. If you type No then the config doesn't get applied (No basically means abort what you just configured). 

[thomas]

There is a little-known command to do this: reset-config (do not confuse this with application reset-config ise)

See details about this command documented in Reset ISE host OS config with a single CLI?

[JuanVelez]

Hi @thomas, thanks for your answer! I have the same problem, reset-config is definitely useful when you need to re-address or re-name a node from scratch, and it does solve the “single restart” problem for the initial baseline configuration.

However, it still falls short for more advanced or incremental interface work. For example:

• Assigning multiple IPv6 addresses to the same NIC (GUA + ULA)

• Configuring secondary interfaces dedicated to CWA, guest portals, or provisioning

• Applying any additional L3 parameters beyond the basic IP/gateway/DNS/NTP set

All of those still trigger ISE to restart services per change, and resetting the entire node per command line until you enter everything isn’t practical in a production deployment.

I also tested stopping services first (application stop ise) hoping to stage multiple interface modifications, but ISE auto-starts services as soon as the first network change is committed, so batching changes that way isn't possible either.

So while reset-config is great for clean slate scenarios, it seems we still don’t have a supported way to make multiple advanced network-level changes and then do a single consolidated restart afterward. It would be really helpful if Cisco added a way to queue OS-level networking changes.