From: Tom Lijnse (Tom.Lijnse@globalknowledge.nl)
Date: Thu Jan 29 2004 - 05:53:33 GMT-3
Hi Marko,
that's strange. If I try it on one of my routers it works exactly like it does on Scott's (see below). This is also the expected behavior according to the documentation.
I'm running 12.2(17a) on a 3640. So apparently the behavior is IOS version dependent (bug?).
Regards,
Tom Lijnse
R3(config)#int e 0/0
R3(config-if)#ip addr dhcp client-id ethernet 0/0
R3(config-if)#^Z
<snip>
20:01:11: DHCP: SDiscover attempt # 1 for entry:
20:01:11: Temp IP addr: 0.0.0.0 for peer on Interface: Ethernet0/0
20:01:11: Temp sub net mask: 0.0.0.0
20:01:11: DHCP Lease server: 0.0.0.0, state: 1 Selecting
20:01:11: DHCP transaction id: 1F94
20:01:11: Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs
20:01:11: Next timer fires after: 00:00:03
20:01:11: Retry count: 1 Client-ID: 0006.53ab.5841
20:01:11: Hostname: R3
20:01:11: DHCP: SDiscover: sending 274 byte length DHCP packet
20:01:11: DHCP: SDiscover 274 bytes
20:01:11: B'cast on Ethernet0/0 interface from 0.0.0.0
<snip>
R3#sh ver
Cisco Internetwork Operating System Software
IOS (tm) 3600 Software (C3640-JK8O3S-M), Version 12.2(17a), RELEASE SOFTWARE (fc1)
-----Original Message-----
From: Marko Berend [mailto:marko.berend@storm.hr]
Sent: Thursday, January 29, 2004 9:36 AM
To: ccielab@groupstudy.com
Subject: RE: DHCP Manual Binding
Scott
How did you get away with short client-id's?
R5 is requesting the 3550 swithch fora an address.
After initialy configuring ip address dhcp client-id f 0/0 the router is
still using the long client-id
Note that R5 is sending "cisco-000a.417a.9ba0-Fa0/0" but when it comes
to the switch it is somewhat longer...
R5:
---------
interface FastEthernet0/0
ip address dhcp client-id FastEthernet0/0
duplex auto
speed auto
R5(config-if)#no shut
R5(config-if)#
17:09:07: DHCP: DHCP client process started: 10
17:09:09: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state to up
17:09:12: %LINEPROTO-5-UPDOWN: Line protocol on Interface
FastEthernet0/0, changed state to up
17:09:12: DHCP: DHCP client process started: 10
17:09:12: DHCP: allocate request
17:09:12: DHCP: zapping entry in DHC_PURGING state for Fa0/0
17:09:12: DHCP: new entry. add to queue
17:09:12: DHCP: SDiscover attempt # 1 for entry:
17:09:12: Temp IP addr: 0.0.0.0 for peer on Interface: FastEthernet0/0
17:09:12: Temp sub net mask: 0.0.0.0
17:09:12: DHCP Lease server: 0.0.0.0, state: 1 Selecting
17:09:12: DHCP transaction id: 16AE
17:09:12: Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs
17:09:12: Next timer fires after: 00:00:02
17:09:12: Retry count: 1 Client-ID: cisco-000a.417a.9ba0-Fa0/0
17:09:12: DHCP: SDiscover: sending 300 byte length DHCP packet
17:09:12: DHCP: SDiscover 300 bytes
17:09:12: B'cast on FastEthernet0/0 interface from 0.0.0.0
17:09:12: DHCP: Received a BOOTREP pkt
17:09:12: DHCP: Scan: Message type: DHCP Offer
17:09:12: DHCP: Scan: Server ID Option: 172.168.136.10 = ACA8880A
17:09:12: DHCP: Scan: Lease Time: 86400
17:09:12: DHCP: Scan: Renewal time: 43200
17:09:12: DHCP: Scan: Rebind time: 75600
17:09:12: DHCP: Scan: Subnet Address Option: 255.255.255.192
17:09:12: DHCP: rcvd pkt source: 172.168.136.10, destination:
255.255.255.255
17:09:12: UDP sport: 43, dport: 44, length: 308
17:09:12: DHCP op: 2, htype: 1, hlen: 6, hops: 0
17:09:12: DHCP server identifier: 172.168.136.10
17:09:12: xid: 16AE, secs: 0, flags: 8000
17:09:12: client: 0.0.0.0, your: 172.168.136.5
17:09:12: srvr: 0.0.0.0, gw: 0.0.0.0
17:09:12: options block length: 60
17:09:12: DHCP Offer Message Offered Address: 172.168.136.5
17:09:12: DHCP: Lease Seconds: 86400 Renewal secs: 43200 Rebind
secs: 75600
17:09:12: DHCP: Server ID Option: 172.168.136.10
17:09:12: DHCP: offer received from 172.168.136.10
17:09:12: DHCP: SRequest attempt # 2 for entry:
17:09:12: Temp IP addr: 172.168.136.5 for peer on Interface:
FastEthernet0/0
17:09:12: Temp sub net mask: 255.255.255.192
17:09:12: DHCP Lease server: 172.168.136.10, state: 1 Selecting
17:09:12: DHCP transaction id: 16AE
17:09:12: Lease: 86400 secs, Renewal: 0 secs, Rebind: 0 secs
17:09:12: Next timer fires after: 00:00:02
17:09:12: Retry count: 2 Client-ID: cisco-000a.417a.9ba0-Fa0/0
17:09:12: DHCP: SRequest- Server ID option: 172.168.136.10
17:09:12: DHCP: SRequest- Requested IP addr option: 172.168.136.5
17:09:12: DHCP: SRequest placed lease len option: 86400
17:09:12: DHCP: SRequest: 318 bytes
17:09:12: DHCP: SRequest: 318 bytes
17:09:12: B'cast on FastEthernet0/0 interface from 0.0.0.0
17:09:12: DHCP: Received aInterface FastEthernet0/0 assigned DHCP
address 172.168.136.5, mask 255.255.255.192
BOOTREP pkt
17:09:12: DHCP: Scan: Message type: DHCP Ack
17:09:12: DHCP: Scan: Server ID Option: 172.168.136.10 = ACA8880A
17:09:12: DHCP: Scan: Lease Time: 86400
17:09:12: DHCP: Scan: Renewal time: 43200
17:09:12: DHCP: Scan: Rebind time: 75600
17:09:12: DHCP: Scan: Subnet Address Option: 255.255.255.192
17:09:12: DHCP: rcvd pkt source: 172.168.136.10, destination:
255.255.255.255
17:09:12: UDP sport: 43, dport: 44, length: 308
17:09:12: DHCP op: 2, htype: 1, hlen: 6, hops: 0
17:09:12: DHCP server identifier: 172.168.136.10
17:09:12: xid: 16AE, secs: 0, flags: 8000
17:09:12: client: 0.0.0.0, your: 172.168.136.5
17:09:12: srvr: 0.0.0.0, gw: 0.0.0.0
17:09:12: options block length: 60
17:09:12: DHCP Ack Message
17:09:12: DHCP: Lease Seconds: 86400 Renewal secs: 43200 Rebind
secs: 75600
17:09:12: DHCP: Server ID Option: 172.168.136.10
17:09:15: DHCP Proxy Client Pooling: ***Allocated IP address:
172.168.136.5
17:09:15: Allocated IP address = 172.168.136.5 255.255.255.192
Sw1: dhcp server (3550)
-----------------------------
2d22h: %LINK-3-UPDOWN: Interface FastEthernet0/5, changed state to up
2d22h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5,
changed state to up
2d22h: DHCP glean: extract option 82:
2d22h: DHCPD: DHCPDISCOVER received from client
0063.6973.636f.2d30.3030.612e.3431.3761.2e39.6261.302d.4661.302f.30 on
interface Vlan136.
2d22h: DHCPD: Sending DHCPOFFER to client
0063.6973.636f.2d30.3030.612e.3431.3761.2e39.6261.302d.4661.302f.30
(172.168.136.5).
2d22h: DHCPD: broadcasting BOOTREPLY to client 000a.417a.9ba0.
2d22h: DHCP glean: extract option 82:
2d22h: DHCPD: DHCPREQUEST received from client
0063.6973.636f.2d30.3030.612e.3431.3761.2e39.6261.302d.4661.302f.30.
2d22h: DHCPD: Sending DHCPACK to client
0063.6973.636f.2d30.3030.612e.3431.3761.2e39.6261.302d.4661.302f.30
(172.168.136.5).
2d22h: DHCPD: broadcasting BOOTREPLY to client 000a.417a.9ba0.
R5#sh ver
Cisco Internetwork Operating System Software
IOS (tm) C2600 Software (C2600-JK9O3S-M), Version 12.2(2)T1, RELEASE
SOFTWARE (fc2)
TAC Support: http://www.cisco.com/tac
Copyright (c) 1986-2001 by cisco Systems, Inc.
Compiled Wed 18-Jul-01 08:44 by ccai
Image text-base: 0x80008088, data-base: 0x816583D0
ROM: System Bootstrap, Version 12.2(6r), RELEASE SOFTWARE (fc1)
R5 uptime is 16 hours, 56 minutes
System returned to ROM by reload at 20:14:12 UTC Wed Mar 3 1993
System image file is "flash:c2600-jk9o3s-mz.122-2.T1.bin"
cisco 2620 (MPC860) processor (revision 0x00) with 49152K/16384K bytes
of memory.
Processor board ID JAD0626CF3H (2096042778)
M860 processor: part number 0, mask 49
Bridging software.
X.25 software, Version 3.0.0.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
TN3270 Emulation software.
Basic Rate ISDN software, Version 1.1.
1 FastEthernet/IEEE 802.3 interface(s)
1 Serial network interface(s)
1 ISDN Basic Rate interface(s)
32K bytes of non-volatile configuration memory.
16384K bytes of processor board System flash (Read/Write)
Configuration register is 0x2102
This archive was generated by hypermail 2.1.4 : Mon Feb 02 2004 - 09:07:51 GMT-3