cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2263
Views
5
Helpful
5
Replies

Switch not forwarding DHCP request to relay

darren-carr
Level 2
Level 2

Hi,

 

I am experiencing a strange problem with my WS-C3560CG-8PC and a Meraki MV device.

Set-up: 1 x WS-C3560CG-8PC, enabled for routing, service dhcp enabled, DHCP server is the switch and I am looking to relay the information to a 3P NAC solution. 

When I connect a standard laptop to the switch the device gets an IP address from the switch and the DHCP request is relayed to my 3P NAC solution. I am debugging DHCP on the switch and see the request being forwarded to the 3P NAC solution IP as per the interface configuration. However when I connect the Meraki camera I do not see the request being forwarded. If I connect the camera to a HPE/Aruba switch and move the configuration to this device it works. So it looks like something specific on the switch. Any idea what might be causing this, the switch configuration is very basic and seems to work for everything aside from this camera.

 

Below is a capture from the switch for a working device and after this the camera. 

 

WORKING_PC

 

May 22 21:43:27.853: DHCPD: DHCPREQUEST received from client 0134.e6d7.4e9f.7c.
May 22 21:43:27.853: DHCPD: Finding a relay for client 0134.e6d7.4e9f.7c on interface Vlan57.
May 22 21:43:27.853: DHCPD: Looking up binding using address 10.5.7.1
May 22 21:43:27.853: DHCPD: setting giaddr to 10.5.7.1.
May 22 21:43:27.853: DHCPD: BOOTREQUEST from 0134.e6d7.4e9f.7c forwarded to 10.0.10.254.
May 22 21:43:29.331: %LINK-3-UPDOWN: Interface GigabitEthernet0/5, changed state to up
May 22 21:43:29.331: DHCPD: interface GigabitEthernet0/5 coming up
May 22 21:43:29.913: DHCPD: Reload workspace interface Vlan57 tableid 0.
May 22 21:43:29.913: DHCPD: tableid for 10.5.7.1 on Vlan57 is 0
May 22 21:43:29.913: DHCPD: client's VPN is .
May 22 21:43:29.913: DHCPD: DHCPREQUEST received from client 0134.e6d7.4e9f.7c.
May 22 21:43:29.913: DHCPD: Finding a relay for client 0134.e6d7.4e9f.7c on interface Vlan57.
May 22 21:43:29.913: DHCPD: Looking up binding using address 10.5.7.1
May 22 21:43:29.913: DHCPD: setting giaddr to 10.5.7.1.
May 22 21:43:29.918: DHCPD: BOOTREQUEST from 0134.e6d7.4e9f.7c forwarded to 10.0.10.254

 

CAMERA

May 22 22:13:42.726: DHCPD: tableid for 10.5.7.1 on Vlan57 is 0
May 22 22:13:42.726: DHCPD: client's VPN is .
May 22 22:13:42.726: DHCPD: using received relay info.
May 22 22:13:42.726: DHCPD: Sending notification of DISCOVER:
May 22 22:13:42.726: DHCPD: htype 1 chaddr ac17.c80c.3ef1
May 22 22:13:42.726: DHCPD: interface = Vlan57
May 22 22:13:42.726: DHCPD: class id 4d4552414b49
May 22 22:13:42.726: DHCPD: out_vlan_id 0
May 22 22:13:42.726: DHCPD: DHCPDISCOVER received from client 01ac.17c8.0c3e.f1 on interface Vlan57.
May 22 22:13:42.726: DHCPD: using received relay info.
May 22 22:13:42.726: DHCPD: Sending notification of DISCOVER:
May 22 22:13:42.726: DHCPD: htype 1 chaddr ac17.c80c.3ef1
May 22 22:13:42.726: DHCPD: interface = Vlan57
May 22 22:13:42.726: DHCPD: class id 4d4552414b49
May 22 22:13:42.726: DHCPD: out_vlan_id 0
May 22 22:13:42.726: DHCPD: DHCPOFFER notify setup address 10.5.7.12 mask 255.255.255.0
May 22 22:13:42.726: DHCPD: Sending DHCPOFFER to client 01ac.17c8.0c3e.f1 (10.5.7.12).
May 22 22:13:42.726: DHCPD: no option 125
May 22 22:13:42.726: DHCPD: Check for IPe on Vlan57
May 22 22:13:42.726: DHCPD: creating ARP entry (10.5.7.12, ac17.c80c.3ef1).
May 22 22:13:42.726: DHCPD: unicasting BOOTREPLY to client ac17.c80c.3ef1 (10.5.7.12).
May 22 22:13:42.747: DHCPD: Reload workspace interface Vlan57 tableid 0.
May 22 22:13:42.747: DHCPD: tableid for 10.5.7.1 on Vlan57 is 0
May 22 22:13:42.747: DHCPD: client's VPN is .
May 22 22:13:42.747: DHCPD: DHCPREQUEST received from client 01ac.17c8.0c3e.f1.
May 22 22:13:42.747: DHCPD: Sending notification of ASSIGNMENT:
May 22 22:13:42.747: DHCPD: address 10.5.7.12 mask 255.255.255.0
May 22 22:13:42.747: DHCPD: htype 1 chaddr ac17.c80c.3ef1
May 22 22:13:42.752: DHCPD: lease time remaining (secs) = 86400
May 22 22:13:42.752: DHCPD: interface = Vlan57
May 22 22:13:42.752: DHCPD: out_vlan_id 0

5 Replies 5

can I see the config ?
are the Server and Camera in same VLAN and you config DHCP relay under VLAN SVI ?
I think that this make issue to server, can you move Camera to other VLAN.

 

pease note sending notification in my below comment.

May 22 22:13:42.747: DHCPD: Sending notification of ASSIGNMENT:
May 22 22:13:42.747: DHCPD: address 10.5.7.12 mask 255.255.255.0
May 22 22:13:42.747: DHCPD: htype 1 chaddr ac17.c80c.3ef1
May 22 22:13:42.752: DHCPD: lease time remaining (secs) = 86400
May 22 22:13:42.752: DHCPD: interface = Vlan57
May 22 22:13:42.752: DHCPD: out_vlan_id 0

this error notify that why the DHCP not 
assign IP to Camera.
check the OP82 is add correctly.

 

Hi

 It seems that the camera receives dhcp offer:

 

May 22 22:13:42.726: DHCPD: DHCPOFFER notify setup address 10.5.7.12 mask 255.255.255.0
May 22 22:13:42.726: DHCPD: Sending DHCPOFFER to client 01ac.17c8.0c3e.f1 (10.5.7.12).
May 22 22:13:42.726: DHCPD: no option 125

But, looks like the camera is asking for option 150. This could be due the fact that option 150 is cisco proprietary. Probably on the CDP negociation something more is going on as they are both cisco which may not happen with different verndor. 

 

darren-carr
Level 2
Level 2

Hi,

 

@MHM Cisco World 

Please see configuration from switch below. 

1. Camera is in Vlan57, DHCP server is the switch. Relay server is in Vlan10 (not shown) but which is routed from the switch. No firewall, etc between the Vlans it is just routing. 

 

hostname REMOVED
!
ip routing
!
ip dhcp excluded-address 10.5.7.1 10.5.7.9
!
ip dhcp pool LAB_UNTRUSTED
network 10.5.7.0 255.255.255.0
default-router 10.5.7.1
dns-server 8.8.8.8 8.8.4.4
!
vlan internal allocation policy ascending
!
vlan 57
name UNTRUSTED
!
interface GigabitEthernet0/5
description MERAKI-MV12
switchport access vlan 57
switchport mode access
spanning-tree portfast
!
interface Vlan57
description UNTRUSTED
ip address 10.5.7.1 255.255.255.0
ip helper-address 10.0.10.254
!
ip route 0.0.0.0 0.0.0.0 10.128.0.1

 

@Flavio Miranda 

I'm not sure what option 125 or 150 are used for in this regard. I did capture the DHCP request from the MV please see attached.