found this on CCO, not sure how your management VLAN is configured:
- One performance-related issue that results from misconfiguration is when the inband channel, which is used for any control traffic terminating on the switch, such as ping, Telnet, VTP, STP, or CDP is not put in a seperate VLAN from user data.
It is always recommended to keep the managment or sc0 interface of the switch in a separate VLAN from user data. Otherwise, any broadcast or multicast storm can flood the inband channel to the Network Management Processor (NMP) which needs to be free to hande the protocols just mentioned.
You can test the the com with the mod with the following:
test scp 2 1464 10
Pinging Module 2, Length 1464, Count 10
The reason why they say make sure your managment VLAN does not carry data is that for inband comms they are tagged with the sc0 vlan. If you do some debugging one can see this, but please do not do this on a live network it can literally kill the switch.. :))
Did you have any STP loops/High CPU at the time message is printed? The above messages are printed when the Supervisor's CPU gets pegged high. Also does the Supervisor in slot 2 reset? There was a bug file for this kind of crash saying the switch should not crash under these circumstances and is fixed now.
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...