From: Carlos Chorao (cchorao@solvertech.co.nz)
Date: Mon Jun 07 2004 - 06:32:48 GMT-3
Richard,
Im sure you have moved on so apologies for the late reply but I have
been away for a while. Construction of the "client identifier" is
documented. Look at link below, in the Usage Guidelines section you will
see "client identifier is formed by concatenating the media type and the
MAC address" for Ethernet media type = 01.
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/
fipras_r/1rfdhcp.htm#1017558
Carlos
#11351
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Richard Dumoulin
Sent: 09 May 2004 08:19
To: groupstudy@cconlinelabs.com; ccielab@groupstudy.com
Subject: RE: DHCP manual binding
Yes !! Many thanks. But this is undocumented ?!?!?
-----Original Message-----
From: Tony Schaffran [mailto:groupstudy@cconlinelabs.com]
Sent: sabado, 08 de mayo de 2004 22:09
To: Richard Dumoulin; ccielab@groupstudy.com
Subject: RE: DHCP manual binding
I discovered how to make this work.
Enable 'debug ip dhcp server packet' on the dhcp server.
You will then see a long client-identifier from the router requesting
DHCP.
After you get this info, you will need to undebug all.
Then instead of using hardware-address, use client-identifier and use
the
long string that was found in the debug.
Tony Schaffran
Network Analyst
CCIE #11071
CCNP, CCNA, CCDA,
NNCDS, NNCSS, CNE, MCSE
www.cconlinelabs.com
Your #1 choice for online Cisco rack rentals.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Richard Dumoulin
Sent: Saturday, May 08, 2004 7:25 AM
To: ccielab@groupstudy.com
Subject: DHCP manual binding
Hello group,
I would appreciate any help with the following DHCP issue I am
encountering.
I don't know much about DHCP so I am just reading the doc-cd about DHCP
manual binding. The recommended configuration seems straightforward but
for
some it does not work:
Here is ithe config from the following link:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/
fipr
_c/ipcprt1/1cfdhcp.htm#xtocid16
<http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr
/fip
r_c/ipcprt1/1cfdhcp.htm#xtocid16>
R1
!
ip dhcp pool test
host 1.1.1.2 255.0.0.0
hardware-address 0002.fd9c.6da0
default-router 1.1.1.1
!
interface Ethernet0/0
ip address 1.1.1.1 255.0.0.0
R2
!
interface Ethernet0/0
ip address dhcp
end
!
R2#sh int eth 0/0
Ethernet0/0 is up, line protocol is up
Hardware is AmdP2, address is 0002.fd9c.6da0 (bia 0002.fd9c.6da0)
I can see the broadcast coming in the dhcp server:
R1#deb ip pa det
IP packet debugging is on (detailed)
R1#
*Mar 1 02:29:21.786: IP: s=0.0.0.0 (Ethernet0/0), d=255.255.255.255,
len
604, rcvd 2
*Mar 1 02:29:21.786: UDP src=68, dst=67
*Mar 1 02:29:24.783: IP: s=0.0.0.0 (Ethernet0/0), d=255.255.255.255,
len
604, rcvd 2
*Mar 1 02:29:24.787: UDP src=68, dst=67
*Mar 1 02:29:27.784: IP: s=0.0.0.0 (Ethernet0/0), d=255.255.255.255,
len
604, rcvd 2
*Mar 1 02:29:27.788: UDP src=68, dst=67
But R2 never gets its IP address:
R2#
*Mar 1 02:31:16.938: DHCP: QScan: Purging entry
*Mar 1 02:31:16.938: DHCP: deleting entry 81A46AD4 0.0.0.0 from list
*Mar
1 02:31:16.938: Temp IP addr: 0.0.0.0 for peer on Interface:
Ethernet0/0
*Mar 1 02:31:16.938: Temp sub net mask: 0.0.0.0
*Mar 1 02:31:16.938: DHCP Lease server: 0.0.0.0, state: 8 Purging
*Mar 1 02:31:16.938: DHCP transaction id: 1C3C
*Mar 1 02:31:16.938: Lease: 0 secs, Renewal: 0 secs, Rebind: 0
secs
*Mar 1 02:31:16.938: No timer running
*Mar 1 02:31:16.943: Retry count: 0 Client-ID:
cisco-0002.fd9c.6da0-Et0/0
*Mar 1 02:31:16.943: DHCP: Try 7 to acquire address for Ethernet0/0
*Mar 1
02:31:16.971: DHCP: allocate request *Mar 1 02:31:16.971: DHCP: new
entry.
add to queue *Mar 1 02:31:16.971: DHCP: SDiscover attempt # 1 for
entry:
*Mar 1 02:31:16.971: Temp IP addr: 0.0.0.0 for peer on Interface:
Ethernet0/0 *Mar 1 02:31:16.971: Temp sub net mask: 0.0.0.0
*Mar 1 02:31:16.971: DHCP Lease server: 0.0.0.0, state: 1 Selecting
*Mar 1 02:31:16.971: DHCP transaction id: 1B46
*Mar 1 02:31:16.975: Lease: 0 secs, Renewal: 0 secs, Rebind: 0
secs
*Mar 1 02:31:16.975: Next timer fires after: 00:00:02
*Mar 1 02:31:16.975: Retry count: 1 Client-ID:
cisco-0002.fd9c.6da0-Et0/0
*Mar 1 02:31:16.975: DHCP: SDiscover: sending 294 byte length DHCP
packet
*Mar 1 02:31:16.975: DHCP: SDiscover 294 bytes
*Mar 1 02:31:16.975: B'cast on Ethernet0/0 interface from
0.0.0.0
*Mar 1 02:31:19.971: DHCP: SDiscover attempt # 2 for entry: *Mar 1
02:31:19.971: Temp IP addr: 0.0.0.0 for peer on Interface: Ethernet0/0
*Mar
1 02:31:19.971: Temp sub net mask: 0.0.0.0
*Mar 1 02:31:19.971: DHCP Lease server: 0.0.0.0, state: 1 Selecting
*Mar 1 02:31:19.971: DHCP transaction id: 1B46
*Mar 1 02:31:19.971: Lease: 0 secs, Renewal: 0 secs, Rebind: 0
secs
*Mar 1 02:31:19.971: Next timer fires after: 00:00:03
*Mar 1 02:31:19.971: Retry count: 2 Client-ID:
cisco-0002.fd9c.6da0-Et0/0
*Mar 1 02:31:19.975: DHCP: SDiscover: sending 294 byte length DHCP
packet
*Mar 1 02:31:19.975: DHCP: SDiscover 294 bytes
*Mar 1 02:31:19.975: B'cast on Ethernet0/0 interface from
0.0.0.0
*Mar 1 02:31:22.972: DHCP: SDiscover attempt # 3 for entry: *Mar 1
02:31:22.972: Temp IP addr: 0.0.0.0 for peer on Interface: Ethernet0/0
*Mar
1 02:31:22.972: Temp sub net mask: 0.0.0.0
*Mar 1 02:31:22.972: DHCP Lease server: 0.0.0.0, state: 1 Selecting
*Mar 1 02:31:22.972: DHCP transaction id: 1B46
*Mar 1 02:31:22.972: Lease: 0 secs, Renewal: 0 secs, Rebind: 0
secs
*Mar 1 02:31:22.972: Next timer fires after: 00:00:03
*Mar 1 02:31:22.972: Retry count: 3 Client-ID:
cisco-0002.fd9c.6da0-Et0/0
*Mar 1 02:31:22.976: DHCP: SDiscover: sending 294 byte length DHCP
packet
*Mar 1 02:31:22.976: DHCP: SDiscover 294 bytes
*Mar 1 02:31:22.976: B'cast on Ethernet0/0 interface from
0.0.0.0
*Mar 1 02:31:25.973: DHCP: QScan: Timed out Selecting state%Unknown
DHCP
problem.. No allocation possible *Mar 1 02:31:37.356: DHCP: Waiting for
35
seconds on interface Ethernet0/0
Thank you
--Richard
This archive was generated by hypermail 2.1.4 : Sat Jul 03 2004 - 19:40:34 GMT-3