We are using RADIUS CoA with the new bounce-host-port support to set client VLANs on MS switches.   The client device successfully gets a new IP address in the newly assigned VLAN reliably and quickly.   The challenge I have is getting visibility of this newly assigned client IP address from the API.   Note: * we've disabled RADIUS accounting because it will either have no framed-ip-address on the initial accept, or will have the old IP address if we trigger an accounting update via a vlan change (cisco switches have aaa accounting delay-start to address this problem), so RADIUS accounting isn't useful for this scenario. * syslog for MX dhcp events isn't useful because it will only send an event on a new lease, so if I move the client to a VLAN where it's had an IP address, no dhcp event is generated.   If I change the client IP address, it can take between 60sec and 4mins for an update to Dashboard. Sometimes Dashboard doesn't update for 20+ minutes.  If I look at the API:  https://dashboard.meraki.com/api/v0/networks/{networkID}/clients    - I may get the old address. If I look at the API: https://api.meraki.com/api/v0/devices/{orgId}/clients?timespan=120  - I may get the new address (typically within 60-90 seconds).   I've opened a case with Meraki support to see if I can find out how this client-IP update process happens and try and understand why there are multiple places where this IP can be found and they're not consistently updated.   Does anyone have another way to reliably get the client IP address (local MX dhcp server so can't see this traffic via SPAN) - or has anyone else seen this issue?   Will update when I hear from support.   Thanks, Steve     ... View more