Hardware-address can be used only for bootp clients. If there's an Option 61 present, hardware-address cannot be used. No workaround - use "client-identifier" option under the pool.
-- Marko Milivojevic - CCIE #18427 :: This message was sent from a mobile device. I apologize for errors and brevity. :: On Apr 15, 2012, at 9:08, Kingsley Charles <[email protected]> wrote: > Hi all > Hi all > > If I want to configure manual binding that doesn't working with hardware > address. Instead, if I specify the client identifies, it works. > > ip dhcp pool cat > host 10.20.30.40 255.255.255.0 > hardware-address 0001.0002.0003 > > > The snippet below, claims that hardware address can be used with bootp > requests only. Logically, I feel that should be the case because bootp > request doesn't have options field. In the case of DHCP request, the option > 61 is used to carry client identifier. Hence, it seems, the IOS expect client > identifies to be configured, if it a dhcp request. > > Comments please. > > > Snippet from > http://www.cisco.com/en/US/docs/ios/12_2/ip/configuration/guide/1cfdhcp.html#wp1001108 > > Router(dhcp-config)# client-identifier unique-identifier > > Specifies the unique identifier for DHCP clients. This command is used for > DHCP requests. > > Router(dhcp-config)# hardware-address hardware-address type > > (Optional) Specifies a hardware address for the client. This command is used > for BOOTP requests. > > With regards > Kings > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > Are you a CCNP or CCIE and looking for a job? Check out > www.PlatinumPlacement.com
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
