Table of Contents
Advertisement
DHCP
DHCP External Server
DHCP packets are not forwarded to the DHCP server over dynamically created
interfaces when all of the following are true: [Defect ID 180343]
DHCP relay or DHCP relay proxy is configured on the router.
The client-facing interfaces are created dynamically using bridged Ethernet
over static ATM PVCs.
The ip auto-detect ip-subscriber command is configured to enable packet
detection (packet triggering) and to trigger creation of dynamic subscriber
interfaces.
Work-around: To avoid this defect, do all of the following:
Do not use the ip auto-detect ip-subscriber command to enable packet
triggering and to create dynamic subscriber interfaces
Ensure that DHCP external server is configured in the virtual router.
Ensure that the set dhcp relay inhibit-access-route-creation command is
configured in the virtual router to prevent DHCP relay from installing host
routes by default.
The DHCP renew counter and release counter (displayed with the show ip
dhcp-external statistics command) are doubled rather than incremented for
each renew and release sent. [Defect ID 78802]
When DHCP clients on an S-VLAN over bridged Ethernet stack send a decline
message to a router that has DHCP relay and DHCP external server configured
in the same VR, the clients bindings are not removed from the DHCP external
server. [Defect ID 87086]
When DHCP relay and DHCP external server are configured in the same VR
with server-sync enabled, bindings are not created in the DHCP external server
when DHCP clients on an ATM bulk configuration interface stack and dynamic
VLAN over Ethernet stack sends a renew message. [Defect ID 87087]
DHCP NAK packets are sent from a different VLAN than the one on which the
renew request is received on a router that is configured with dynamic VLANs,
DHCP local server, and automatically created dynamic subscriber interfaces.
This behavior occurs only after a link flap has taken place. [Defect ID 87062]
With the unique client ID option enabled, when two clients with the same MAC
address or client ID are on an interface (where one client is connected over a
router and relay and the other client is connected directly). Sending a release
request from one of the clients might terminate another client. [Defect ID
179759]
Release 10.2.2
Known Problems and Limitations
37
Advertisement
Table of Contents
