The configuration works (the switch automatically executes smartport_intel.sh when it detects a MAC address starting with 000423) but it's too slow. For example, if a DHCP client runs on the connecting node, it will already have received an IP address by the time the macro executes. If my macro were to switch VLANs, the node would lose connectivity as the VLAN it's going to uses different IP addresses, while the DHCP client has already done its business. Can this be fixed somehow?
The only work around I could come up with was to assign static IPs to the phones that I was auto-detecting, forcing them onto the correct VLAN that the macro would (eventually) assign to the port. Additionally, if I attempted to set the phones for VLAN tagging the switch wouldn't even recognize them to start with. It was less than ideal, but since the phones don't auto register we had to touch each one anyway (Panasonic has some catching up to do with the rest of the market), and we only had a couple dozen, it wasn't too bad, and now all the moves-adds-changes will be fully automated. I attempted to contact TAC to see if there is some better work around, but gave up after spending hours on the phone getting nowhere. I have the impression that MAC detection is only there as a last resort, and we should all be using cisco end nodes that can be auto-detected with CDP if we really expect things to work.
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...