Hi Ingo ,

Thnks for the reply

I dont have issue with the excluded ip.

Even though i have enough IP in the DHCP pool after excluding PC are not taking that the maximun it goes is to 279 even the ip in pool are close to 1000

Hi,

since I can't see anything wrong with your config. I thought the router/switch might be interpreting the "ip dhcp excluded-address 192.168.128.0 192.168.129.254" command incorrectly (normally the low address would start with the first useable ip 192.168.128.1). The 3 suggestions of mine are only ways to exclude this possibility. I would definately try the first one.

Is this error only occurring when 279 addresses have been leased?

If you could post output of "show version", "show ip dhcp bindings" and "show ip dhcp server" we might be able to find out more.

There is also a possibility of an IOS bug. So check the Cisco Bug database against your IOS version and your problem.

hth

just after fixing the same issue, had 100 IP addresses and ony 48 were leased.

deleting the ip excluded ranges and the DHCP pool and adding them back in resolved the issue

Vishwancc,

While it is true that your ip pool has a maximum potential size of 1022 addresses (1024 minus network and broadcast addresses), you have excluded 515 addresses through your excluded address statements, leaving 507 potential addresses for the pool. How many do you need to allocate?

I think the clue behind the problem is indicated by the next address that is slated to be allocated. It is showing 0.0.0.0, which means that there are no more addresses to be assigned. Your debug information also indicates this, where it states that the pool is empty.

I just dealt with a similar problem today, and the cause was I had entered an exclude statement incorrectly, which effectively took out an entire pool.

Since you have supernetted four /24 address blocks together, I suggest you follow the advice of another poster and change your exclude statements. You should have:

ip excluded-address 192.168.128.1 192.168.129.255

(plus the three individual excludes)

This should start your DHCP pool at 192.168.130.0 up to the top of the range, minus the three individual excludes that you listed.

Also, you may want to try deleting all of the DHCP exclude statements before you re-do them, to insure that they have truly been removed. After you have done this, I also suggest issuing 'no service dhcp' and then reenable it ('service dhcp'). This will re-start the DHCP service. Turning off the DHCP service will not remove the DHCP configurations from your router.

Turn on the following to track what happens as you do the above:

debug ip dhcp server event

debug ip dhcp server packet

debug ip dhcp server linkage

The debugs may also give you a clue as to why it cannot allocate more addresses.

Hope this helps.

Ron Buchalski

Hi RON,

I have not got the downtime to do these changes,once i get it i will implement it along witn the other action plan to check if the issue is resolved.

Chao

Vishwa

Vishwa,

Please post an update when you have had a chance to test the suggested changes.

Ron Buchalski