cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1697
Views
0
Helpful
6
Replies

ASR9000 dhcp proxy

On our ASR9010 router I maked dhcp proxy for subscribers, and it worked untill software upgrade (from 4.3.2 to 5.2.4).

After upgrade most of subscribers received IP addresses, but some of them did not. All subscribers are getting their IP statically based on their MAC address. After changing IP addresses for problem subscribers they received new addresses.

For problem subscribers I see this:

0060.1d72.a6f3  10.20.10.213    OFFER_SENT 53         BE1.3993             TEST   0x0       
0060.1d5a.4be8  10.20.10.207    OFFER_SENT 53         BE1.3993             TEST   0x0  

 

Jul 27 11:22:09.896 dhcpd/proxy_errors 0/RSP0/CPU0 t7  TP3647: FSM call returned error for chaddr_string: 9067.b508.d28b, msg_type:3, mode: 4, event: 2
Jul 27 11:22:12.896 dhcpd/proxy_errors 0/RSP0/CPU0 t7  TP485: Packet drop
Jul 27 11:22:12.896 dhcpd/proxy_errors 0/RSP0/CPU0 t7  TP3647: FSM call returned error for chaddr_string: 9067.b508.d28b, msg_type:3, mode: 4, event: 2
Jul 27 11:22:19.896 dhcpd/proxy_errors 0/RSP0/CPU0 t7  TP485: Packet drop
Jul 27 11:22:19.896 dhcpd/proxy_errors 0/RSP0/CPU0 286925# t7  TP3647: FSM call returned error for chaddr_string: 9067.b508.d28b, msg_type:3, mode: 4, event: 2
Jul 27 11:22:34.894 dhcpd/proxy_errors 0/RSP0/CPU0 t7  TP485: Packet drop
Jul 27 11:22:34.894 dhcpd/proxy_errors 0/RSP0/CPU0 289033# t7  TP3647: FSM call returned error for chaddr_string: 9067.b508.d28b, msg_type:3, mode: 4, event: 2
Jul 27 11:23:05.890 dhcpd/errors 0/RSP0/CPU0 24746# t7  TP254: Base Client request packet processing failed, chaddr 9067.b508.d28b
Jul 27 11:23:05.890 dhcpd/proxy_errors 0/RSP0/CPU0 282713# t7  TP3647: FSM call returned error for chaddr_string: 9067.b508.d28b, msg_type:3, mode: 4, event: 2
Jul 27 11:23:05.890 dhcpd/proxy_errors 0/RSP0/CPU0 t7  TP3647: FSM call returned error for chaddr_string: 9067.b508.d28b, msg_type:3, mode: 4, event: 16
Jul 27 11:23:05.890 dhcpd/proxy_errors 0/RSP0/CPU0 281661# t7  TP2102: REQUEST process error, Proxy mode, chaddr 9067.b508.d28b
Jul 27 11:24:13.694 dhcpd/proxy_errors 0/RSP0/CPU0 t7  TP485: Packet drop
Jul 27 11:24:13.694 dhcpd/proxy_errors 0/RSP0/CPU0 t7  TP3647: FSM call returned error for chaddr_string: 9067.b508.d28b, msg_type:3, mode: 4, event: 2
Jul 27 11:24:17.694 dhcpd/proxy_errors 0/RSP0/CPU0 t7  TP485: Packet drop
Jul 27 11:24:17.694 dhcpd/proxy_errors 0/RSP0/CPU0 290093# t7  TP3647: FSM call returned error for chaddr_string: 9067.b508.d28b, msg_type:3, mode: 4, event: 2
Jul 27 11:24:24.693 dhcpd/proxy_errors 0/RSP0/CPU0 t7  TP485: Packet drop
Jul 27 11:24:24.693 dhcpd/proxy_errors 0/RSP0/CPU0 t7  TP3647: FSM call returned error for chaddr_string: 9067.b508.d28b, msg_type:3, mode: 4, event: 2
Jul 27 11:24:40.692 dhcpd/proxy_errors 0/RSP0/CPU0 287990# t7  TP485: Packet drop
Jul 27 11:24:40.692 dhcpd/proxy_errors 0/RSP0/CPU0 t7  TP3647: FSM call returned error for chaddr_string: 9067.b508.d28b, msg_type:3, mode: 4, event: 2
Jul 27 11:25:12.690 dhcpd/errors 0/RSP0/CPU0 6940# t7  TP254: Base Client request packet processing failed, chaddr 9067.b508.d28b
Jul 27 11:25:12.690 dhcpd/proxy_errors 0/RSP0/CPU0 t7  TP3647: FSM call returned error for chaddr_string: 9067.b508.d28b, msg_type:3, mode: 4, event: 2
Jul 27 11:25:12.690 dhcpd/proxy_errors 0/RSP0/CPU0 t7  TP3647: FSM call returned error for chaddr_string: 9067.b508.d28b, msg_type:3, mode: 4, event: 16
Jul 27 11:25:12.690 dhcpd/proxy_errors 0/RSP0/CPU0 t7  TP2102: REQUEST process error, Proxy mode, chaddr 9067.b508.d28b
Jul 27 11:26:19.543 dhcpd/proxy_errors 0/RSP0/CPU0 285888# t7  TP485: Packet drop
Jul 27 11:26:19.543 dhcpd/proxy_errors 0/RSP0/CPU0 291156# t7  TP3647: FSM call returned error for chaddr_string: 9067.b508.d28b, msg_type:3, mode: 4, event: 2
Jul 27 11:26:22.542 dhcpd/proxy_errors 0/RSP0/CPU0 t7  TP485: Packet drop
Jul 27 11:26:22.542 dhcpd/proxy_errors 0/RSP0/CPU0 t7  TP3647: FSM call returned error for chaddr_string: 9067.b508.d28b, msg_type:3, mode: 4, event: 2
Jul 27 11:26:29.542 dhcpd/proxy_errors 0/RSP0/CPU0 267802# t7  TP485: Packet drop
Jul 27 11:26:29.542 dhcpd/proxy_errors 0/RSP0/CPU0 280629# t7  TP3647: FSM call returned error for chaddr_string: 9067.b508.d28b, msg_type:3, mode: 4, event: 2
Jul 27 11:26:44.540 dhcpd/proxy_errors 0/RSP0/CPU0 t7  TP485: Packet drop
Jul 27 11:26:44.540 dhcpd/proxy_errors 0/RSP0/CPU0 284841# t7  TP3647: FSM call returned error for chaddr_string: 9067.b508.d28b, msg_type:3, mode: 4, event: 2
Jul 27 11:27:15.538 dhcpd/errors 0/RSP0/CPU0 25717# t7  TP254: Base Client request packet processing failed, chaddr 9067.b508.d28b
Jul 27 11:27:15.538 dhcpd/proxy_errors 0/RSP0/CPU0 t7  TP3647: FSM call returned error for chaddr_string: 9067.b508.d28b, msg_type:3, mode: 4, event: 2
Jul 27 11:27:15.538 dhcpd/proxy_errors 0/RSP0/CPU0 t7  TP3647: FSM call returned error for chaddr_string: 9067.b508.d28b, msg_type:3, mode: 4, event: 16
Jul 27 11:27:15.538 dhcpd/proxy_errors 0/RSP0/CPU0 261378# t7  TP2102: REQUEST process error, Proxy mode, chaddr 9067.b508.d28b
Jul 27 11:28:20.394 dhcpd/errors 0/RSP0/CPU0 23775# t7  TP2283: Lease Max is 68 years, not 136 years
Jul 27 11:28:20.395 dhcpd/proxy_errors 0/RSP0/CPU0 t7  TP3647: FSM call returned error for chaddr_string: 9067.b508.d28b, msg_type:5, mode: 4, event: 18
Jul 27 11:28:20.395 dhcpd/proxy_errors 0/RSP0/CPU0 t7  TP1665: Proxy process client request packet failed for chaddr 9067.b508.d28b
Jul 27 11:28:20.395 dhcpd/proxy_errors 0/RSP0/CPU0 t7  TP3647: FSM call returned error for chaddr_string: 9067.b508.d28b, msg_type:5, mode: 4, event: 18
Jul 27 11:28:20.395 dhcpd/proxy_errors 0/RSP0/CPU0 282742# t7  TP1665: Proxy process client request packet failed for chaddr 9067.b508.d28b
Jul 27 11:29:46.417 dhcpd/errors 0/RSP0/CPU0 t7  TP2468: rib route delete failed, null ifhandle or IPv4 address
Jul 27 11:29:51.428 dhcpd/errors 0/RSP0/CPU0 t7  TP2283: Lease Max is 68 years, not 136 years
Jul 27 11:29:51.428 dhcpd/proxy_errors 0/RSP0/CPU0 t7  TP3647: FSM call returned error for chaddr_string: 9067.b508.d28b, msg_type:5, mode: 4, event: 18
Jul 27 11:29:51.428 dhcpd/proxy_errors 0/RSP0/CPU0 290118# t7  TP1665: Proxy process client request packet failed for chaddr 9067.b508.d28b
Jul 27 11:29:51.428 dhcpd/proxy_errors 0/RSP0/CPU0 289066# t7  TP3647: FSM call returned error for chaddr_string: 9067.b508.d28b, msg_type:5, mode: 4, event: 18
Jul 27 11:29:51.428 dhcpd/proxy_errors 0/RSP0/CPU0 t7  TP1665: Proxy process client request packet failed for chaddr 9067.b508.d28b

 

Config:

dhcp ipv4
 profile DHCP_proxy proxy
  helper-address vrf TEST 10.15.128.1 giaddr 0.0.0.0
  helper-address vrf TEST 10.15.132.1 giaddr 0.0.0.0
  broadcast-flag policy unicast-always
  relay information option
  relay information policy keep
  relay information option allow-untrusted
 !
 interface Bundle-Ether1.3993 proxy profile DHCP_proxy

 

What can be the reason of the problem?

6 Replies 6

Aleksandar Vidakovic
Cisco Employee
Cisco Employee

This message would typically be reported when a CPE is moved from one access interface to another. Was this move done during the MW, after the upgrade? The previous binding must be cleared in that case. Alternatively, you can enable support for duplicate MAC addresses.

hth,

Aleksandar

All our subscribers are binded to the interface BE1.3993 and can't move to another access interface.

I tried to clear subscribers in state OFFER_SENT. Binding was cleared but when subscriber tried to set up binding next time the same occured.

I am confused of this:

dhcpd/errors 0/RSP0/CPU0 t7  TP2283: Lease Max is 68 years, not 136 years

May be this is the reason of the problem. But problem subscriber can receive IP address when we change its IP in DHCP config, without changing lease time.

Hi Vladimir,

what is the lease time on the DHCP server?

Aleksandar

Hi Alexandr!

This is an example of individual user configuration on our DHCP:

host 10.16.10.109 {
fixed-address 10.16.10.109;
option routers 172.16.36.5;
min-lease-time 4294967295;
uid 01:00:1D:4C:00:DE:D2;

Hi Vladimir,

 4294967295 / (86400 [hours/day] * 365 [days/year]) = 136 years

Can you set the lease time on the server to something more reasonable? Did that help resolve the issue?

Aleksandar

lukas.tribus
Level 1
Level 1

Probably a good idea to install the DHCP umbrella SMU CSCuv39265 for this configuration in 5.2.4.