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

ASA DHCP relay issue

adel85
Level 1
Level 1

running cisco ASA 5516-x with DHCP relay enabled 

some of PC are getting IPs and others not, i have tried alot of TS steps

 

here are some of DHCP relay debug from the ASA ( i want to know if the ASA dropping something or is it DHCP server issue ?)

dhcprelay server 10.204.38.13 NC_DC
dhcprelay server 10.204.38.14 NC_DC
dhcprelay enable Data1_52
dhcprelay enable Data2_53
dhcprelay enable Voice1_54
dhcprelay enable Voice2_55
dhcprelay setroute Data1_52
dhcprelay setroute Data2_53
dhcprelay setroute Voice1_54
dhcprelay setroute Voice2_55

interface GigabitEthernet1/1.x
 vlan x
 nameif NC_DC
 security-level 100
 ip address 192.168.10.4 255.255.255.248 
 dhcprelay information trusted

 

dhcpd_forward_request: request from c81f.ea6f.c6c9 forwarded to 10.204.38.13.
dhcpd_forward_request: request from c81f.ea6f.c6c9 forwarded to 10.204.38.14.
DHCPD/RA: Relay msg received, fip=ANY, fport=0 on Data1_52 interface
DHCP: Received a BOOTREQUEST from interface 10 (size = 996)
DHCPRA: relay binding found for client c81f.ea6f.d7cc.
DHCPRA: setting giaddr to 10.201.52.1.
dhcpd_forward_request: request from c81f.ea6f.d7cc forwarded to 10.204.38.13.
dhcpd_forward_request: request from c81f.ea6f.d7cc forwarded to 10.204.38.14.
DHCPD/RA: Relay msg received, fip=ANY, fport=0 on Data1_52 interface
DHCP: Received a BOOTREQUEST from interface 10 (size = 300)
DHCPRA: relay binding found for client 3417.ebd8.fb57.
DHCPRA: setting giaddr to 10.201.52.1.
dhcpd_forward_request: request from 3417.ebd8.fb57 forwarded to 10.204.38.13.
dhcpd_forward_request: request from 3417.ebd8.fb57 forwarded to 10.204.38.14.
DHCPD/RA: Relay msg received, fip=ANY, fport=0 on Data1_52 interface
DHCP: Received a BOOTREQUEST from interface 10 (size = 996)
DHCPRA: relay binding found for client c81f.ea70.e268.
DHCPRA: setting giaddr to 10.201.52.1.
dhcpd_forward_request: request from c81f.ea70.e268 forwarded to 10.204.38.13.
dhcpd_forward_request: request from c81f.ea70.e268 forwarded to 10.204.38.14.
DHCPD/RA: Relay msg received, fip=ANY, fport=0 on Data2_53 interface
DHCP: Received a BOOTREQUEST from interface 11 (size = 300)
DHCPD/RA: Binding successfully added to hash table
DHCPRA: relay binding created for client 3417.ebb8.c101.
DHCPRA: setting giaddr to 10.201.53.1.
dhcpd_forward_request: request from 3417.ebb8.c101 forwarded to 10.204.38.13.
dhcpd_forward_request: request from 3417.ebb8.c101 forwarded to 10.204.38.14.
DHCPD/RA: Relay msg received, fip=ANY, fport=0 on NC_DC interface
DHCP: Received a BOOTREPLY from relay interface 4 (size = 304, xid = 0x7372a255) at 04:07:50 EEST Sun Apr 25 2021
DHCPRA: relay binding found for client 3417.ebb8.c101.
DHCPRA: Adding rule to allow client to respond using offered address 10.201.53.191
DHCPRA: forwarding reply to client 3417.ebb8.c101.
DHCPD/RA: Relay msg received, fip=ANY, fport=0 on NC_DC interface
DHCP: Received a BOOTREPLY from relay interface 4 (size = 304, xid = 0x7372a255) at 04:07:50 EEST Sun Apr 25 2021
DHCPRA: relay binding found for client 3417.ebb8.c101.
DHCPRA: forwarding reply to client 3417.ebb8.c101.
DHCPD/RA: Relay msg received, fip=ANY, fport=0 on Data2_53 interface
DHCP: Received a BOOTREQUEST from interface 11 (size = 328)
DHCPRA: relay binding found for client 3417.ebb8.c101.
DHCPRA: Server requested by client 10.204.38.13
DHCPRA: setting giaddr to 10.201.53.1.
DHCPRA: Server request counter 2
dhcpd_forward_request: request from 3417.ebb8.c101 forwarded to 10.204.38.13.
dhcpd_forward_request: request from 3417.ebb8.c101 forwarded to 10.204.38.14.
DHCPD/RA: Relay msg received, fip=ANY, fport=0 on NC_DC interface
DHCP: Received a BOOTREPLY from relay interface 4 (size = 309, xid = 0x7372a255) at 04:07:50 EEST Sun Apr 25 2021
DHCPRA: relay binding found for client 3417.ebb8.c101.
DHCPRA: exchange complete - relay binding deleted for client 3417.ebb8.c101.
DHCPD/RA: Binding successfully deactivated
dhcpd_destroy_binding() removing NP rule for client 10.201.53.1
DHCPD/RA: free ddns info and binding
DHCPRA: forwarding reply to client 3417.ebb8.c101.
DHCPD/RA: Relay msg received, fip=ANY, fport=0 on Voice1_54 interface

1 Accepted Solution

Accepted Solutions

adel85
Level 1
Level 1

thank you all for helping and appreciate your support, but it turned out the issue was from DHCP server which belong the the customer and it was solved from his side

View solution in original post

6 Replies 6

balaji.bandi
Hall of Fame
Hall of Fame

A high level may be not able to see what is the issue here based on the Logs,

What Pool you able to get IP address lease, what Pool you do not? or is this a random issue in the same IP address pool?

it would be nice to post some network diagram and what DHCP Server is this? is this a single server or split DHCP Servers?

You need to capture information about the one failing.

 

Some reference configuraiton and DHCP messages for informaiton :

https://www.cisco.com/c/en/us/support/docs/security/adaptive-security-appliance-asa-software/116265-configure-product-00.html

 

 

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

It was split server and I think the customer had conflict in his DHCP server between our network and another network, solved by them.

Hello
Can you post the output -

show dhcprelay statistics
show dhcprelay state


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

if the PC not get IP is the PC connect to native VLAN then, 
ASA is drop native VLAN which is not tag because ASA don't accept the not tag frame. 
just change the VLAN from native to other VLAN and see result.

Have you verified that the dhcp pool has IP adresses available?

--
Please remember to select a correct answer and rate helpful posts

adel85
Level 1
Level 1

thank you all for helping and appreciate your support, but it turned out the issue was from DHCP server which belong the the customer and it was solved from his side

Review Cisco Networking for a $25 gift card