CNR 6.2 - DHCP Trouble-shooting

Unanswered Question
Apr 30th, 2007
User Badges:

Our Primary DNS server on our internal network has just been upgraded from 5.5.13 -> -> ->

The CNR 6.2 DNS server upgrade was a complete success. However the DHSP server function is not providing any leased addresses to client requests. The log is recording:


04/30/2007 16:13:39 name/dhcp/1 Warning Protocol 0 04664 Received DHCPDISCOVER packet but Scope for source network '' is deactivated. Dropping packet.


I have tried to make sure that the scope is activated, can you direct me to where I need to make sure the scope is activated as I may have overlooked some stage. Is it possible that the dhcp database may not have upgraded properly. Are there any CLI commands which I can perform to check the status of a Scope (activated / deactivated).

Any help will be much appreciated

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
jreekers Mon, 04/30/2007 - 19:44
User Badges:
  • Cisco Employee,


Do you have a failover DHCP server, and if so, did you upgrade it prior to upgrading the primary? Often times, this issue is seen when you are set in a failover configuration, but one (or both) servers are not configured for failover (neither main nor failover).

Please review the dhcp logs for messages with the text "unable to successfully configure for DHCP failover". That would indicate your problem with failover configuration.

ppdnetman Tue, 05/01/2007 - 02:03
User Badges:

Thank you for your quick reply and help with this...

We have a failover DHCP server. However this is not yet upgarded to 6.2x - it is still running CNR 5.513 (to be upgraded to 6.2x in the next two weeks). Can you confirm if both versions are compatible in a failover DHCP server pair implementation (and if any particular settings need to be configured), or if this is not possible because both servers need to be on the same CNR release.

Thanks again

jreekers Tue, 05/01/2007 - 08:58
User Badges:
  • Cisco Employee,


Actually, having v6.2x and 5.5x in a failover configuration is possible, although it makes it very difficult to manage. That difficulty stems from the very different User Interfaces between the two versions, and the fact that it's not possible to sync the config from one to the other. The soonest you can get both on the same version, the better.



This Discussion