[cisco-voip] slightly OT: dhcp reservations in IOS DHCP serverconfig

[Joe Cisco]

Do I have to create a separate pool for each reservation? Or can I
list multiple reservations in the same pool?

-Joe C.

On Fri, Oct 10, 2008 at 11:26 AM, Matt Slaga (US)
<Matt.Slaga at us.didata.com> wrote:
> Cisco calls it 'address binding' instead of reservation.
> Configure as follows:
>
> Ip dhcp pool xyz
> Host 10.100.1.1 /24  (set to your 'reserved' ip address)
> Client-identifier 01ab.cdef.ghij.kl  (mac address preceeded by '01' to
> specify Ethernet media type)
> Hardware-address abcd.efgh.ijkl
> Client-name xyzclient1 (optional)
>
> You can verify this with:
> Debug ip dhcp server packet
>
> And check to see if the correct IP was given.
>
> -----Original Message-----
> From: cisco-voip-bounces at puck.nether.net
> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Joe Cisco
> Sent: Friday, October 10, 2008 12:17 PM
> To: cisco-voip
> Subject: [cisco-voip] slightly OT: dhcp reservations in IOS DHCP
> serverconfig
>
> I have a client with about 70 phones that require static IP addresses.
> DHCP is currently being performed on and must stay on an IOS router. I
> would prefer to simply create dhcp reservations for the mac addresses
> of the phones, rather than physically hard code the addresses on the
> phones themselves. Anyone had any experience and/or advice and an
> example IOS dhcp config with reserved mac addresses?
>
> Thanks in advance,
>
> Joe C.
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> -----------------------------------------
> Disclaimer:
>
> This e-mail communication and any attachments may contain
> confidential and privileged information and is for use by the
> designated addressee(s) named above only.  If you are not the
> intended addressee, you are hereby notified that you have received
> this communication in error and that any use or reproduction of
> this email or its contents is strictly prohibited and may be
> unlawful.  If you have received this communication in error, please
> notify us immediately by replying to this message and deleting it
> from your computer. Thank you.
>