In that case I suggest to open a TAC. Please post the solution once you have received it. ... View more

It sounds like somebody else has/had the same problem: https://www.reddit.com/r/networking/comments/6bwupf/cisco_syslog_link_down/ Can you try the following: Conf t No logging host 172.xx.xx.xx Logging host 172.xx.xx.xx And then create a syslog message (unplug an active cable if you send trap logs) and check with show logging again if the port is now up. What software version is running on the two switches? You also might want to install Patch1 for PI and afterwards Hotfix 1 and then Device Pack 9, for maximum compatibility. Do not install Hotfix2 if you manage wireless and plan to replace APs, there is a bug with the copy&replace function. ... View more

It doesn't, but you can read about the supported devices in the device packs. In the Excel sheet are all supported devices listed. I'm still a bit confused about the "link down" part of your show logging output. Normally, at least on my Catalyst switches, it shows link up. ... View more

Interresting. And I guess a 'show int loopback10' will also correctly show it as up/up? If yes, then I have no idea why it's not working. ... View more

Ah you're using possibly more than one Loopback. Can you repeat the ping, but this time, do an extended one. For this, simply type ping and press enter. Then you should get the option to select the source interface (say y to Extended commands), enter there Loopback10. Is this also successful? If not, change the logging source interface in the configuration, to one that is Up. ... View more

I think you're right and I mixed them up. In any case, here is the theory behind those two features: https://community.cisco.com/t5/wireless-mobility-documents/load-balancing-and-band-select-on-the-cisco-wireless-lan/ta-p/3128513#toc-hId--86706536 ... View more

Can you please post the full output of show logging (until the first actual log message)? Can you 'ping 172.xx.xx.xx' successfully from the 3850? ... View more

I don't like the "link down" part of the output you have provided. On what device and with what command did you create this output? ... View more

That reminds me, you have the SSID available on both frequencies (2.4 and 5 GHz), right? Otherwise you must disable Load Balancing if I remember correctly. ... View more

I never liked load balancing, because it disrupts the client decision algorithm for roaming/attaching to an AP. In the end, it's always the client that decides when and where to roam and unless the driver of that client honors "weird" behavior of the AP, it will cause latency issues and sometimes no roamings at all. Because of this, I always left this feature disabled, together with client band select. ... View more

I don't use those profiles, never have. Only manually configured each setting. ... View more

Forgot one thing. Make sure you have Client Load Balancing disabled on the SSID, or configure it differently under Wireless -> Advanced -> Load Balancing. ... View more

Not sure, but the Traps threshold is only generating a trap and I thought it should not inform the client about it, only the SNMP receiver. In any case, increase the limit to 50, just to be sure. Also make sure it's correctly configured in the SSID under Advanced -> Maximum allowed clients. Set it to 0 to have no limit. ... View more