C9300 DHCP Server Issue with Shure Clients - Page 2

SimonSpl · ‎01-05-2024

Hi,
I have a stack of c9300s with local DHCP server enabled on it. Here is the DHCP config:
ip dhcp excluded-address 192.168.4.1 192.168.4.255
!
ip dhcp pool 192.168.4.0
network 192.168.4.0 255.255.254.0
default-router 192.168.4.201

Server works fine with dozens of devices. However, it fails with a certain type of hardware manufactured by Shure. Example MXWAPt8 (dual logical/MAC interface on a single physical, "control" and "Dante"). What is interesting is that the MXWAPt's Dante interface acquires IP (MAC ending in .73bd, IP .38 in the below log). The same MXWAPt8 unit is pulling IPs to both interfaces on a different switch (including c9300 but DHCP server living else where). So my first though was something to do with the dual MACs of a single port, but the same exact behavior is observed with Shure MXWncs4 (network charging station) which has only one logical (single MAC). Shure blames the switch. Anyone has any idea if I can pull more detailed logs or if I am doing something wrong here?

c9300>en
c9300#debug dhcp detail
DHCP client activity debugging is on (detailed)
c9300#debug ip dhcp server events
DHCP server event debugging is on.
*Jan 5 12:55:27.372: DHCPD: checking for expired leases.
c9300# ! Plugged in Shure MXAWAPt8 at this point (POE)
*Jan 5 12:55:57.533: %ILPOWER-5-DETECT: Interface Tw1/0/27: Power Device detected: IEEE PD
*Jan 5 12:55:58.532: %ILPOWER-5-POWER_GRANTED: Interface Tw1/0/27: Power granted
*Jan 5 12:56:04.414: %LINK-3-UPDOWN: Interface TwoGigabitEthernet1/0/27, changed state to up
*Jan 5 12:56:05.415: %LINEPROTO-5-UPDOWN: Line protocol on Interface TwoGigabitEthernet1/0/27, changed state to up
*Jan 5 12:56:05.415: DHCPD: interface TwoGigabitEthernet1/0/27 coming up
*Jan 5 12:56:12.440: DHCPD: Reload workspace interface Vlan202 tableid 0.
*Jan 5 12:56:12.440: DHCPD: excluded address: 192.168.4.201
*Jan 5 12:56:12.440: DHCPD: FSM state change INVALID
*Jan 5 12:56:12.440: DHCPD: Workspace state changed from INIT to INVALID
*Jan 5 12:56:12.440: DHCPD: Client either rebooted or rebinding we are seeing the client for first time
*Jan 5 12:56:12.440: DHCPD: Sending notification of ASSIGNMENT FAILURE:
*Jan 5 12:56:12.440: DHCPD: htype 1 chaddr 000e.ddfd.73bd
*Jan 5 12:56:12.440: DHCPD: circuit id 000400ca011b
*Jan 5 12:56:12.440: DHCPD: interface = Vlan202
*Jan 5 12:56:12.440: DHCPD: class id 756468637020302e392e392d707265
*Jan 5 12:56:12.440: DHCPD: Sending notification of ASSIGNMENT_FAILURE:
*Jan 5 12:56:12.440: DHCPD: due to: CLIENT CHANGED SUBNET
*Jan 5 12:56:12.440: DHCPD: htype 1 chaddr 000e.ddfd.73bd
*Jan 5 12:56:12.440: DHCPD: circuit id 000400ca011b
*Jan 5 12:56:12.440: DHCPD: interface = Vlan202
*Jan 5 12:56:12.440: DHCPD: class id 756468637020302e392e392d707265
*Jan 5 12:56:12.440: DHCPD: Sending DHCPNAK to client 0100.0edd.fd73.bd.
*Jan 5 12:56:14.841: DHCPD: Reload workspace interface Vlan202 tableid 0.
*Jan 5 12:56:14.841: DHCPD: Sending notification of DISCOVER:
*Jan 5 12:56:14.841: DHCPD: htype 1 chaddr 000e.dd49.9c0e
*Jan 5 12:56:14.841: DHCPD: circuit id 000400ca011b
*Jan 5 12:56:14.841: DHCPD: interface = Vlan202
*Jan 5 12:56:14.841: DHCPD: Sending notification of DISCOVER:
*Jan 5 12:56:14.841: DHCPD: htype 1 chaddr 000e.dd49.9c0e
*Jan 5 12:56:14.841: DHCPD: circuit id 000400ca011b
*Jan 5 12:56:14.841: DHCPD: interface = Vlan202
*Jan 5 12:56:14.841: DHCPD: FSM state change INVALID
*Jan 5 12:56:14.841: DHCPD: Workspace state changed from INIT to INVALID
*Jan 5 12:56:14.841: DHCPD: classname not set in msg
*Jan 5 12:56:14.841: DHCPD: Allocated binding 7FE0F6E85F50
*Jan 5 12:56:14.841: DHCPD: Adding binding to radix tree (192.168.5.37)
*Jan 5 12:56:14.841: DHCPD: Adding binding to hash tree 7FE0F6E85F50
*Jan 5 12:56:14.841: DHCPD:dhcpd_binding_add_to_mac_hash: index- 108 add binding 7FE0F6E85F50
*Jan 5 12:56:14.841: DHCPD: assigned IP address 192.168.5.37 to client 0100.0edd.499c.0e.
*Jan 5 12:56:16.841: DHCPD: Reprocessing saved workspace (ID=0xEB000028)
*Jan 5 12:56:16.841: DHCPD: Sending notification of DISCOVER:
*Jan 5 12:56:16.841: DHCPD: htype 1 chaddr 000e.dd49.9c0e
*Jan 5 12:56:16.841: DHCPD: circuit id 000400ca011b
*Jan 5 12:56:16.841: DHCPD: interface = Vlan202
*Jan 5 12:56:16.841: DHCPD: Sending DHCPOFFER to client 0100.0edd.499c.0e (192.168.5.37).
*Jan 5 12:56:16.842: DHCPD: Freeing saved workspace (ID=0xEB000028)
*Jan 5 12:56:17.747: DHCPD: Reload workspace interface Vlan202 tableid 0.
*Jan 5 12:56:17.747: DHCPD: Sending notification of DISCOVER:
*Jan 5 12:56:17.747: DHCPD: htype 1 chaddr 000e.ddfd.73bd
*Jan 5 12:56:17.747: DHCPD: circuit id 000400ca011b
*Jan 5 12:56:17.747: DHCPD: interface = Vlan202
*Jan 5 12:56:17.747: DHCPD: class id 756468637020302e392e392d707265
*Jan 5 12:56:17.747: DHCPD: Sending notification of DISCOVER:
*Jan 5 12:56:17.747: DHCPD: htype 1 chaddr 000e.ddfd.73bd
*Jan 5 12:56:17.747: DHCPD: circuit id 000400ca011b
*Jan 5 12:56:17.747: DHCPD: interface = Vlan202
*Jan 5 12:56:17.747: DHCPD: class id 756468637020302e392e392d707265
*Jan 5 12:56:17.747: DHCPD: FSM state change INVALID
*Jan 5 12:56:17.747: DHCPD: Workspace state changed from INIT to INVALID
*Jan 5 12:56:17.747: DHCPD: classname not set in msg
*Jan 5 12:56:17.747: DHCPD: Allocated binding 7FE0F6E85D60
*Jan 5 12:56:17.748: DHCPD: Adding binding to radix tree (192.168.5.38)
*Jan 5 12:56:17.748: DHCPD: Adding binding to hash tree 7FE0F6E85D60
*Jan 5 12:56:17.748: DHCPD:dhcpd_binding_add_to_mac_hash: index- 463 add binding 7FE0F6E85D60
*Jan 5 12:56:17.748: DHCPD: assigned IP address 192.168.5.38 to client 0100.0edd.fd73.bd.
*Jan 5 12:56:19.747: DHCPD: Reprocessing saved workspace (ID=0xBA000029)
*Jan 5 12:56:19.747: DHCPD: Sending notification of DISCOVER:
*Jan 5 12:56:19.747: DHCPD: htype 1 chaddr 000e.ddfd.73bd
*Jan 5 12:56:19.747: DHCPD: circuit id 000400ca011b
*Jan 5 12:56:19.747: DHCPD: interface = Vlan202
*Jan 5 12:56:19.747: DHCPD: class id 756468637020302e392e392d707265
*Jan 5 12:56:19.747: DHCPD: Sending DHCPOFFER to client 0100.0edd.fd73.bd (192.168.5.38).
*Jan 5 12:56:19.747: DHCPD: Freeing saved workspace (ID=0xBA000029)
*Jan 5 12:56:22.882: DHCPD: Reload workspace interface Vlan202 tableid 0.
*Jan 5 12:56:22.882: DHCPD: Found previous binding
*Jan 5 12:56:22.882: DHCPD: FSM state change INVALID
*Jan 5 12:56:22.882: DHCPD: Workspace state changed from INIT to INVALID
*Jan 5 12:56:22.882: DHCPD: client is directly connected going with default flow
*Jan 5 12:56:22.882: DHCPD: Sending notification of ASSIGNMENT:
*Jan 5 12:56:22.882: DHCPD: address 192.168.5.38 mask 255.255.254.0
*Jan 5 12:56:22.882: DHCPD: htype 1 chaddr 000e.ddfd.73bd
*Jan 5 12:56:22.882: DHCPD: lease time remaining (secs) = 86400
*Jan 5 12:56:22.882: DHCPD: interface = Vlan202
*Jan 5 12:56:22.882: DHCPD: Sending DHCPACK to client 0100.0edd.fd73.bd (192.168.5.38).
! Following 13 lines repeat every 25 seconds forever, "Control" interface never acquires IP from c9300
*Jan 5 12:56:22.941: DHCPD: Reload workspace interface Vlan202 tableid 0.
*Jan 5 12:56:22.941: DHCPD: Sending notification of DISCOVER:
*Jan 5 12:56:22.941: DHCPD: htype 1 chaddr 000e.dd49.9c0e
*Jan 5 12:56:22.941: DHCPD: circuit id 000400ca011b
*Jan 5 12:56:22.941: DHCPD: interface = Vlan202
*Jan 5 12:56:22.941: DHCPD: Sending notification of DISCOVER:
*Jan 5 12:56:22.941: DHCPD: htype 1 chaddr 000e.dd49.9c0e
*Jan 5 12:56:22.941: DHCPD: circuit id 000400ca011b
*Jan 5 12:56:22.941: DHCPD: interface = Vlan202
*Jan 5 12:56:22.941: DHCPD: FSM state change INVALID
*Jan 5 12:56:22.941: DHCPD: Workspace state changed from INIT to INVALID
*Jan 5 12:56:22.941: DHCPD: Found previous server binding
*Jan 5 12:56:22.941: DHCPD: Sending DHCPOFFER to client 0100.0edd.499c.0e (192.168.5.37).

MXWNCS log (not poe):
*Jan 5 13:15:44.382: DHCPD: Reload workspace interface Vlan202 tableid 0.
*Jan 5 13:15:44.382: DHCPD: Sending notification of DISCOVER:
*Jan 5 13:15:44.382: DHCPD: htype 1 chaddr 000e.dd46.17d4
*Jan 5 13:15:44.382: DHCPD: circuit id 000400ca022f
*Jan 5 13:15:44.382: DHCPD: interface = Vlan202
*Jan 5 13:15:44.382: DHCPD: Sending notification of DISCOVER:
*Jan 5 13:15:44.382: DHCPD: htype 1 chaddr 000e.dd46.17d4
*Jan 5 13:15:44.382: DHCPD: circuit id 000400ca022f
*Jan 5 13:15:44.382: DHCPD: interface = Vlan202
*Jan 5 13:15:44.382: DHCPD: FSM state change INVALID
*Jan 5 13:15:44.382: DHCPD: Workspace state changed from INIT to INVALID
*Jan 5 13:15:44.382: DHCPD: classname not set in msg
*Jan 5 13:15:44.382: DHCPD: Allocated binding 7FE0F6E85B70
*Jan 5 13:15:44.382: DHCPD: Adding binding to radix tree (192.168.5.39)
*Jan 5 13:15:44.382: DHCPD: Adding binding to hash tree 7FE0F6E85B70
*Jan 5 13:15:44.382: DHCPD:dhcpd_binding_add_to_mac_hash: index- 303 add binding 7FE0F6E85B70
*Jan 5 13:15:44.382: DHCPD: assigned IP address 192.168.5.39 to client 0100.0edd.4617.d4.
*Jan 5 13:15:46.382: DHCPD: Reprocessing saved workspace (ID=0x1B00002B)
*Jan 5 13:15:46.382: DHCPD: Sending notification of DISCOVER:
*Jan 5 13:15:46.382: DHCPD: htype 1 chaddr 000e.dd46.17d4
*Jan 5 13:15:46.382: DHCPD: circuit id 000400ca022f
*Jan 5 13:15:46.382: DHCPD: interface = Vlan202
*Jan 5 13:15:46.382: DHCPD: Sending DHCPOFFER to client 0100.0edd.4617.d4 (192.168.5.39).
*Jan 5 13:15:46.382: DHCPD: Freeing saved workspace (ID=0x1B00002B)
*Jan 5 13:15:48.428: DHCPD: Reload workspace interface Vlan202 tableid 0.
*Jan 5 13:15:48.428: DHCPD: Sending notification of DISCOVER:
*Jan 5 13:15:48.428: DHCPD: htype 1 chaddr 000e.dd46.17d4
*Jan 5 13:15:48.428: DHCPD: circuit id 000400ca022f
*Jan 5 13:15:48.428: DHCPD: interface = Vlan202
*Jan 5 13:15:48.428: DHCPD: Sending notification of DISCOVER:
*Jan 5 13:15:48.428: DHCPD: htype 1 chaddr 000e.dd46.17d4
*Jan 5 13:15:48.428: DHCPD: circuit id 000400ca022f
*Jan 5 13:15:48.428: DHCPD: interface = Vlan202
*Jan 5 13:15:48.428: DHCPD: FSM state change INVALID
*Jan 5 13:15:48.428: DHCPD: Workspace state changed from INIT to INVALID
*Jan 5 13:15:48.428: DHCPD: Found previous server binding
*Jan 5 13:15:48.428: DHCPD: Sending DHCPOFFER to client 0100.0edd.4617.d4 (192.168.5.39).

MHM Cisco World · ‎01-08-2024

Mismatch mask

Both must have /24

MHM

SimonSpl · ‎01-09-2024

What do you mean by both?
Once again, I did setup a separate c9200 unit (older IOS image), 192.168.0.0/24, default-router is the switch's VLAN IP address. No NAK msgs in the switch DHCPD events. Multiple clients (including other Shure line of products, also with dual MACs) acquire IPs, one of the MXWapt interfaces does not. So what ever you had in mind (hard to follow) is likely not the issue. Unfortunately, I have to ship this system somewhere, so my time with it is about to end. Shure support wasn't very helpful (blamed the switch) and I decided to use these device types with static IPs due to lack of time.

Georg Pauwen · ‎01-08-2024

Hello,

I somewhere recall that Shure requires option 43 in the DHCP pool:

"option 43 hex <hex_value>: Configure DHCP option 43 for Shure devices. The <hex_value> is a hexadecimal string representing the required information for Shure devices. You would need to obtain this value from Shure or the device documentation."

I'll try to find out what that value is (unless you have that value already of course...)

EDIT: there are several online Option 43 generators on the Internet (search for 'Option 43 Generator')...