I think the subject says it all... is there any way to temporarily disable DHCP on one or more interfaces without removing the DHCP pools entirely?
I know that I can "no ip dhcp server pool POOLNAME", but that then means I have to recreate the entire pool from scratch when I want to re-enable DHCP again.
The situation here is that I'm dropping a router into a network that currently has a different IP range and is using a different router for internet access. I have a PC in that network configured with a secondary (static) IP address so it will be able to talk to this new router, but I don't want the new router assigning DHCP to the rest of the network just yet (the T1s it is handling need to be tested first).
The new router has two subinterfaces (separate VLANs) and I need to disable DHCP server on both of those.
I'm trying to avoid "no-ing" both pools and having to re-add them later because each pool has a bunch of dhcp-options that I would have to re-add as well.
On a Cisco, I believe it's possible to "no service dhcp server" or something along those lines to temporarily disable the server, without losing the config options. I'm looking for something similar - in this case, there are no interfaces / subnets that need a functional server (I don't need to selectively disable single interfaces or pools, I just need to shut off all DHCP serving from this router for a day or two).
I suppose I could simply add the entirety of both pools as excluded-addresses, but I worry then that the DHCP server will still try to reply to client requests, which I don't want (there's another DHCP server on the network that will be turned off once the T1s are ready and I can re-enable DHCP on the Adtran).
The Netvanta happens to be a 3305 on base firmware here, but I suspect this would apply to all AOS... It's on the latest long-term / maintenance release (R11.4.3).
My other alternative would be to backup the current config (with DHCP pools enabled), and then alter and save it as startup without the pools. Once the T1s are tested and functioning, I can copy <backupconfig> running-config and that should get the pools back, but I've seen strangeness when copying a stored config into the running (it seems like copying to startup-config and rebooting is safer, but I'm trying to avoid the reboot as well as having to re-add the pools by hand).