Yes, the client id server sees is "3062.302e.6332.3838.2e31.3637.312d.4661.30" instead of little more conventional "00b0.c288.1671". What's up here? This thing makes manual binding impossible, as that long number is not accepted in "client-identifier" on server.
Edit: No, I wasn't cut'n'pasting properly, that long client-id can be entered into pool configuration. So that solves the problem, and the only think that remains unanswered for me is what were Cisco thinking, when they decided that client-id is going to be this kind of crazy stuff instead of plain MAC.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...