Re: C9300 DHCP Server Issue with Shure Clients

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).

marce1000 · ‎01-05-2024

- I don't like DHCP servers on switches , because it can lead to race conditions w.r.t device networking operations ; I would try to checkout current advisory software version (first) and check if that can make a difference :
https://software.cisco.com/download/home/286315874/type/282046477/release/Cupertino-17.9.4a

If you can test that these devices can get an address from an none-switch based DHCP server/service , then consider removing DHCP services from the 9300 ,

M.

-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '

SimonSpl · ‎01-05-2024

I understand that this isn't common practice, but this is an isolated system, there is no traffic going out of the c9300 and I have 100+ devices that I rather not static one by one. Considering you can probably run DHCPD on microwave oven these days, it shouldn't be an excuse not to run it on a very expensive switch. I don't know where the problems is, just my thoughts about you dismissing the idea of not running the service. I get what you are saying, but I don't think we should just settle down for alternative when something doesn't work. Anyway, thanks for the suggestion.

marce1000 · ‎01-08-2024

Ref : DHCP server issue with shure clients

>....it shouldn't be an excuse not to run it on a very expensive switch
- Here you find a couple of reasons why i using DHCP services on network switches is not advisable :
1) Race conditions between layer2 servicing and DHCP services
2) Related to 1) : In heavy traffic scenario's DHCP done by switches may get hampered because of prioritizing layer2 traffic (the need for)
3) Less optimal DHCP lease management ; in the sense that if a single switch crashes , DHCP lease info's may get lost or it could be that they are not recovered completely. In contrast , DHCP appliance vendors usually offer DHCP-clusters where 2 nodes act as a single DHCP server but keep replicating the DHCP database on the none servicing node (too). If one node fails there is a DHCP failover which is complete and or becomes transparent ; for all customer nodes needing DHCP.

Humbly Yours,
M.

-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '

MHM Cisco World · ‎01-05-2024

ip dhcp excluded-address 192.168.4.1 192.168.4.255 <<- I see you excluded all IP

MHM

Richard Burts · ‎01-06-2024

My initial reaction was similar, about the number of excluded addresses. But if you look carefully at the dhcp pool it describes a pool with 510 addresses (255.255.254.0). So all IP are not excluded - the pool extends from 192.168.4.0 through 192.168.5.254.

I believe that the issue is that the Shure clients have a traditional classful approach to their networking. In looking at the debug output the DHCP is offering IP 192.168.5.38 address. So far so good. With a default router of 192.168.4.201. I believe that the Shure clients are rejecting the offer because of what they perceive is a mismatch between netID and gateway address. I believe that if your were to change the addressing to use class B space (172.16.x.x) it would work just fine.

I believe that your approach is logically valid. But the issue is how to deal with the Shure clients. Is it possible to change the IP addressing plan so that the excluded addresses use the high end of the range rather than the low end?

HTH

Rick

MHM Cisco World · ‎01-06-2024

thanks @Richard Burts you guide me to solution
I see this Log DHCPNAK
and I test in lab the dhcp pool and get same log message
this happened when the DHCP pool network mask not match the default GW net mask (config under GW interface)

*Jan 5 12:56:12.440: DHCPD: Sending DHCPNAK to client 0100.0edd.fd73.bd.
this case the mask is mismatch

#

this case after only correct the mask

MHM

SimonSpl · ‎01-08-2024

The only place I saw NAK in my log is in this line:
*Jan 5 12:56:12.440: DHCPD: Sending DHCPNAK to client 0100.0edd.fd73.bd.
Note that the client with MAC address 000e.ddfd.73BD acquires IP just fine. Not quite sure what 0100.0edd.fd73.bd is, but I assume it is related (some sort of table entry with parts of the client MAC address?).

So I think that theory is wrong, or I am not seeing something. Also, here is a log from C9200 (no NAK msgs), once again the control interface (ending in .9c0e) doesn't get IP, the Dante (ending in 73bd) does, although it doesn't show the IP it gets in the log (192.168.0.218):
EDIT: The network here is setup: 192.168.0.0/24, switch is 192.168.0.201;
c9200#terminal monitor
c9200#debug dhcp detail
DHCP client activity debugging is on (detailed)
c9200#debug IP dhcp server events
DHCP server event debugging is on.
c9200#
c9200#
*Jan 8 22:17:55.981: DHCPD: checking for expired leases. Cisco Smart License Utility (CSLU) : Unable to resolve server hostname/domain na me
*Jan 8 22:18:10.989: %ILPOWER-5-DETECT: Interface Gi1/0/1: Power Device detecte d: IEEE PD
*Jan 8 22:18:11.991: %ILPOWER-5-POWER_GRANTED: Interface Gi1/0/1: Power granted
*Jan 8 22:18:16.917: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to up
*Jan 8 22:18:17.919: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/1, changed state to up
*Jan 8 22:18:17.919: DHCPD: interface GigabitEthernet1/0/1 coming up
*Jan 8 22:18:25.210: DHCPD: Reload workspace interface Vlan202 tableid 0.
*Jan 8 22:18:25.211: DHCPD: excluded address: 192.168.0.201
*Jan 8 22:18:25.211: DHCPD: FSM state change INVALID
*Jan 8 22:18:25.211: DHCPD: Workspace state changed from INIT to INVALID
*Jan 8 22:18:25.211: DHCPD: Client either rebooted or rebinding we are seeing the client for first time
*Jan 8 22:18:25.211: DHCPD : Locating relay for Subnet 192.168.0.201
*Jan 8 22:18:25.211: DHCPD: Sending notification of ASSIGNMENT FAILURE:
*Jan 8 22:18:25.211: DHCPD: htype 1 chaddr 000e.ddfd.73bd
*Jan 8 22:18:25.211: DHCPD: circuit id 000400ca0101
*Jan 8 22:18:25.211: DHCPD: interface = Vlan202
*Jan 8 22:18:25.211: DHCPD: class id 756468637020302e392e392d707265
*Jan 8 22:18:25.211: DHCPD: Sending notification of ASSIGNMENT_FAILURE:
*Jan 8 22:18:25.211: DHCPD: due to: CANT FORWARD
*Jan 8 22:18:25.211: DHCPD: htype 1 chaddr 000e.ddfd.73bd
*Jan 8 22:18:25.211: DHCPD: circuit id 000400ca0101
*Jan 8 22:18:25.211: DHCPD: interface = Vlan202
*Jan 8 22:18:25.211: DHCPD: class id 756468637020302e392e392d707265
*Jan 8 22:18:27.448: DHCPD: Reload workspace interface Vlan202 tableid 0.
*Jan 8 22:18:27.448: DHCPD: excluded address: 192.168.0.201
*Jan 8 22:18:27.448: DHCPD: FSM state change INVALID
*Jan 8 22:18:27.448: DHCPD: Workspace state changed from INIT to INVALID
*Jan 8 22:18:27.448: DHCPD: Client either rebooted or rebinding we are seeing the client for first time
*Jan 8 22:18:27.448: DHCPD : Locating relay for Subnet 192.168.0.201
*Jan 8 22:18:27.448: DHCPD: Sending notification of ASSIGNMENT FAILURE:
*Jan 8 22:18:27.448: DHCPD: htype 1 chaddr 000e.ddfd.73bd
*Jan 8 22:18:27.448: DHCPD: circuit id 000400ca0101
*Jan 8 22:18:27.448: DHCPD: interface = Vlan202
*Jan 8 22:18:27.448: DHCPD: class id 756468637020302e392e392d707265
*Jan 8 22:18:27.448: DHCPD: Sending notification of ASSIGNMENT_FAILURE:
*Jan 8 22:18:27.448: DHCPD: due to: CANT FORWARD
*Jan 8 22:18:27.448: DHCPD: htype 1 chaddr 000e.ddfd.73bd
*Jan 8 22:18:27.448: DHCPD: circuit id 000400ca0101
*Jan 8 22:18:27.448: DHCPD: interface = Vlan202
*Jan 8 22:18:27.449: DHCPD: class id 756468637020302e392e392d707265
*Jan 8 22:18:28.329: DHCPD: Reload workspace interface Vlan202 tableid 0.
*Jan 8 22:18:28.329: DHCPD: Sending notification of DISCOVER:
*Jan 8 22:18:28.329: DHCPD: htype 1 chaddr 000e.dd49.9c0e
*Jan 8 22:18:28.329: DHCPD: circuit id 000400ca0101
*Jan 8 22:18:28.329: DHCPD: interface = Vlan202
*Jan 8 22:18:28.330: DHCPD: Sending notification of DISCOVER:
*Jan 8 22:18:28.330: DHCPD: htype 1 chaddr 000e.dd49.9c0e
*Jan 8 22:18:28.330: DHCPD: circuit id 000400ca0101
*Jan 8 22:18:28.330: DHCPD: interface = Vlan202
*Jan 8 22:18:28.330: DHCPD: FSM state change INVALID
*Jan 8 22:18:28.330: DHCPD: Workspace state changed from INIT to INVALID
*Jan 8 22:18:28.330: DHCPD: classname not set in msg
*Jan 8 22:18:28.330: DHCPD: Allocated binding 3AD11824
*Jan 8 22:18:28.330: DHCPD: Adding binding to radix tree (192.168.0.214)
*Jan 8 22:18:28.330: DHCPD: Adding binding to hash tree 3AD11824
*Jan 8 22:18:28.330: DHCPD:dhcpd_binding_add_to_mac_hash: index- 108 add binding 3AD11824
*Jan 8 22:18:28.330: DHCPD: assigned IP address 192.168.0.214 to client 0100.0edd.499c.0e.
*Jan 8 22:18:30.331: DHCPD: Reprocessing saved workspace (ID=0x4)
*Jan 8 22:18:30.331: DHCPD: Sending notification of DISCOVER:
*Jan 8 22:18:30.331: DHCPD: htype 1 chaddr 000e.dd49.9c0e
*Jan 8 22:18:30.331: DHCPD: circuit id 000400ca0101
*Jan 8 22:18:30.331: DHCPD: interface = Vlan202
*Jan 8 22:18:30.331: DHCPD: Sending DHCPOFFER to client 0100.0edd.499c.0e (192.168.0.214).
*Jan 8 22:18:30.331: DHCPD: Freeing saved workspace (ID=0x4)
*Jan 8 22:18:30.784: DHCPD: Reload workspace interface Vlan202 tableid 0.
*Jan 8 22:18:30.785: DHCPD: excluded address: 192.168.0.201
*Jan 8 22:18:30.785: DHCPD: FSM state change INVALID
*Jan 8 22:18:30.785: DHCPD: Workspace state changed from INIT to INVALID
*Jan 8 22:18:30.785: DHCPD: Client either rebooted or rebinding we are seeing the client for first time
*Jan 8 22:18:30.785: DHCPD : Locating relay for Subnet 192.168.0.201
*Jan 8 22:18:30.785: DHCPD: Sending notification of ASSIGNMENT FAILURE:
*Jan 8 22:18:30.785: DHCPD: htype 1 chaddr 000e.ddfd.73bd
*Jan 8 22:18:30.785: DHCPD: circuit id 000400ca0101
*Jan 8 22:18:30.785: DHCPD: interface = Vlan202
*Jan 8 22:18:30.785: DHCPD: class id 756468637020302e392e392d707265
*Jan 8 22:18:30.785: DHCPD: Sending notification of ASSIGNMENT_FAILURE:
*Jan 8 22:18:30.785: DHCPD: due to: CANT FORWARD
*Jan 8 22:18:30.785: DHCPD: htype 1 chaddr 000e.ddfd.73bd
*Jan 8 22:18:30.785: DHCPD: circuit id 000400ca0101
*Jan 8 22:18:30.785: DHCPD: interface = Vlan202
*Jan 8 22:18:30.785: DHCPD: class id 756468637020302e392e392d707265
*Jan 8 22:18:36.329: DHCPD: Reload workspace interface Vlan202 tableid 0.
*Jan 8 22:18:36.330: DHCPD: Sending notification of DISCOVER:
*Jan 8 22:18:36.330: DHCPD: htype 1 chaddr 000e.dd49.9c0e
*Jan 8 22:18:36.330: DHCPD: circuit id 000400ca0101
*Jan 8 22:18:36.330: DHCPD: interface = Vlan202
*Jan 8 22:18:36.330: DHCPD: Sending notification of DISCOVER:
*Jan 8 22:18:36.330: DHCPD: htype 1 chaddr 000e.dd49.9c0e
*Jan 8 22:18:36.330: DHCPD: circuit id 000400ca0101
*Jan 8 22:18:36.330: DHCPD: interface = Vlan202
*Jan 8 22:18:36.330: DHCPD: FSM state change INVALID
*Jan 8 22:18:36.330: DHCPD: Workspace state changed from INIT to INVALID
*Jan 8 22:18:36.330: DHCPD: Found previous server binding
*Jan 8 22:18:36.330: DHCPD: Sending DHCPOFFER to client 0100.0edd.499c.0e (192.168.0.214).
*Jan 8 22:18:38.427: DHCPD: Reload workspace interface Vlan202 tableid 0.
*Jan 8 22:18:38.427: DHCPD: excluded address: 192.168.0.201
*Jan 8 22:18:38.427: DHCPD: FSM state change INVALID
*Jan 8 22:18:38.427: DHCPD: Workspace state changed from INIT to INVALID
*Jan 8 22:18:38.427: DHCPD: Client either rebooted or rebinding we are seeing the client for first time
*Jan 8 22:18:38.427: DHCPD : Locating relay for Subnet 192.168.0.201
*Jan 8 22:18:38.427: DHCPD: Sending notification of ASSIGNMENT FAILURE:
*Jan 8 22:18:38.427: DHCPD: htype 1 chaddr 000e.ddfd.73bd
*Jan 8 22:18:38.427: DHCPD: circuit id 000400ca0101
*Jan 8 22:18:38.427: DHCPD: interface = Vlan202
*Jan 8 22:18:38.427: DHCPD: class id 756468637020302e392e392d707265
*Jan 8 22:18:38.427: DHCPD: Sending notification of ASSIGNMENT_FAILURE:
*Jan 8 22:18:38.427: DHCPD: due to: CANT FORWARD
*Jan 8 22:18:38.427: DHCPD: htype 1 chaddr 000e.ddfd.73bd
*Jan 8 22:18:38.427: DHCPD: circuit id 000400ca0101
*Jan 8 22:18:38.427: DHCPD: interface = Vlan202
*Jan 8 22:18:38.427: DHCPD: class id 756468637020302e392e392d707265
*Jan 8 22:18:52.330: DHCPD: Reload workspace interface Vlan202 tableid 0.
*Jan 8 22:18:52.330: DHCPD: Sending notification of DISCOVER:
*Jan 8 22:18:52.330: DHCPD: htype 1 chaddr 000e.dd49.9c0e
*Jan 8 22:18:52.330: DHCPD: circuit id 000400ca0101
*Jan 8 22:18:52.330: DHCPD: interface = Vlan202
*Jan 8 22:18:52.330: DHCPD: Sending notification of DISCOVER:
*Jan 8 22:18:52.330: DHCPD: htype 1 chaddr 000e.dd49.9c0e
*Jan 8 22:18:52.330: DHCPD: circuit id 000400ca0101
*Jan 8 22:18:52.331: DHCPD: interface = Vlan202
*Jan 8 22:18:52.331: DHCPD: FSM state change INVALID
*Jan 8 22:18:52.331: DHCPD: Workspace state changed from INIT to INVALID
*Jan 8 22:18:52.331: DHCPD: Found previous server binding
*Jan 8 22:18:52.331: DHCPD: Sending DHCPOFFER to client 0100.0edd.499c.0e (192.168.0.214).

MHM Cisco World · ‎01-09-2024

share the last config of DHCP pool and GW interface
share the show ip dhcp server statistic
share the show ip dhcp pool <name>

MHM

SimonSpl · ‎01-09-2024

This is all from the temporary c9200 setup since I have a less confusing /24 subnet. Switch is at 192.168.0.201;

ip dhcp excluded-address 192.168.0.1 192.168.0.210
!
ip dhcp pool 192.168.0.0 //name of pool
network 192.168.0.0 255.255.255.0
default-router 192.168.0.201
__________________________

c9200#sh ip dhcp server statistic
*Jan 9 14:59:55.981: DHCPD: checking for expired leases.
Memory usage 18077
Address pools 1
Database agents 0
Automatic bindings 5
Manual bindings 0
Expired bindings 1
Malformed messages 0
Secure arp entries 0
Renew messages 33
Workspace timeouts 0
Static routes 0
Relay bindings 0
Relay bindings active 0
Relay bindings terminated 0
Relay bindings selecting 0

Message Received
BOOTREQUEST 0
DHCPDISCOVER 1861
DHCPREQUEST 114
INIT-REBOOT 10
REQUEST 5
RENEW 33
REBIND 66
DHCPDECLINE 0
DHCPRELEASE 0
DHCPINFORM 1
DHCPVENDOR 0
BOOTREPLY 0
DHCPOFFER 0
DHCPACK 0
DHCPNAK 0

Message Sent
BOOTREPLY 0
DHCPOFFER 1861
DHCPACK 10
DHCPNAK 0

Message Forwarded
BOOTREQUEST 0
DHCPDISCOVER 0
DHCPREQUEST 0
INIT-REBOOT 0
REQUEST 0
RENEW 0
REBIND 0
DHCPDECLINE 0
DHCPRELEASE 0
DHCPINFORM 0
DHCPVENDOR 0
BOOTREPLY 0
DHCPOFFER 0
DHCPACK 0
DHCPNAK 0

DHCP-DPM Statistics
Offer notifications sent 0
Offer callbacks received 0
Classname requests sent 0
Classname callbacks received 0

Port Based Allocation Statistics
Discover MAC change 3218550665
Request MAC change 3788976009
Invalid binding in fwd req 64499593
_____________________________
Utilization mark (high/low) : 100 / 0
Subnet size (first/next) : 0 / 0
Total addresses : 254
Leased addresses : 5
Excluded addresses : 210
Pending event : none
1 subnet is currently in the pool :
Current index IP address range Leased/Excluded/Total
192.168.0.215 192.168.0.1 - 192.168.0.254 5 / 210 / 254

Richard Burts · ‎01-09-2024

Thanks for the update. I am very surprised by the result when you use a /24 pool. There must be something about those Shure devices but I am puzzled what it might be. Your choice to use these device types with static IPs seems very reasonable to me.

HTH

Rick

MHM Cisco World · ‎01-10-2024

this pool use network mask /24 and until now you dont confirm if the default-router .210 is use /24 or not?

ip dhcp excluded-address 192.168.0.1 192.168.0.210

Utilization mark (high/low) : 100 / 0
Subnet size (first/next) : 0 / 0
Total addresses : 254
Leased addresses : 5
Excluded addresses : 210 <- you excluded 210 IP from POOL
Pending event : none
1 subnet is currently in the pool :
Current index IP address range Leased/Excluded/Total
192.168.0.215 192.168.0.1 - 192.168.0.254 5 / 210 / 254

NOW the left IP after you confirm that DHCP POOL NETWORK and default-router use same netmask /24 have 45 IP

Message Received
BOOTREQUEST 0
DHCPDISCOVER 1861
DHCPREQUEST 114
INIT-REBOOT 10
REQUEST 5
RENEW 33
REBIND 66
DHCPDECLINE 0
DHCPRELEASE 0
DHCPINFORM 1
DHCPVENDOR 0
BOOTREPLY 0
DHCPOFFER 0
DHCPACK 0
DHCPNAK 0

Message Sent
BOOTREPLY 0
DHCPOFFER 1861
DHCPACK 10 <<<- from 1861 only 10 is DHCP ACK !!
DHCPNAK 0

so there is something break the DHCP, add this command under the default-router interface and check DHCP

Switch(config-if)#no ip redirects

Switch(config-if)#no ip unreachables

MHM

SimonSpl · ‎01-08-2024

Good idea. Unfortunately, that might not be the case. I pulled a c9200, configured a basic 192.168.0.0/24. Same result. Sadly, I am
running out of time and can't mess with option 43 as suggested by Georg, but I doubt this was the case since I didn't have to do this on any other switch brand (and lower tier Cisco switches work fine) with this Shure product line. I was able to confirm that another Shure unit behaves the same way (so not faulty hardware), and that different Shure hardware line with dual logical interfaces work fine (Shure MXA310 as well as ULX-D receiver) with c9300/c9200 (running firmware 17.09.04a/17.09.01).

MHM Cisco World · ‎01-08-2024

the issue is mismatch between the default-router and network of local DHCP
match it and check
MHM

SimonSpl · ‎01-08-2024

I have dozens of other devices, including different line of Shure product - all get IP addresses just fine. Default-router is the switch address/DHCP server - 192.168.4.201; And in the case with the c9200 that I also tried, network is just 192.168.0.0/24, default-router/switch/DHCPserver is 192.168.0.201. Same issue.