Hello Root bridge will send BPDUs across all its DP ports. following links might be useful for you: http://www.cisco.com/c/en/us/support/docs/lan-switching/spanning-tree-protocol/24062-146.html https://supportforums.cisco.com/discussion/11061531/stp-root-port-vs-designated-port Hope this helps Best Regards, Zaid ... View more

the problem description is not clear, Kindly Explain more. do you mean that the router is crashing due to power-on? if yes then Please check the power source/cable etc... if after that switch is still crashing then a replacement of router is needed ... View more

Hello since this issue is happening around the same time zone I Highly doubt that this is a hardware issue. I have the following questions: 1- is there any activity being done at that specific time? 2- what is the software image being used? 3- are you sure there is enough space in the flash to save the crashinfo files? Also I would suggest to monitor the memory, buffers and CPU using the following commands: - show process mem sorted - show buffers - show process cpu sorted Also I would recommend to connect a PC with a console, enable console logging using "logging console" and once the device crashes again you will mostly have logs appearing in the console that will help troubleshooting this further. Hope this Helps :) Best Regards, Zaid ... View more

Hello, I found the following link: http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3750/software/release/12-2_44_se/release/notes/OL14630.html If the switch has interfaces with automatic QoS for voice over IP (VoIP) configured and you upgrade the switch software to Cisco IOS Release 12.2(40)SE (or later), when you enter the auto qos voip cisco-phone interface configuration command on another interface, you might see this message: AutoQoS Error: ciscophone input service policy was not properly applied policy map AutoQoS-Police-CiscoPhone not configured If this happens, enter the no auto qos voip cisco-phone interface command on all interface with this configuration to delete it. Then enter the auto qos voip cisco-phone command on each of these interfaces to reapply the configuration. Hope this Helps :) Best Regards, Zaid ... View more

Hello Tony, I can't see any problems here in the show interfaces, it seems that the interface is working fine, so you have to investigate with the PC's. Best Regards, Zaid ... View more

Hello Arunas, okay first of all as Glen said that you must be sure that the minimum requirements of the image is already there on the switch, which i can see for the latest IOS image on this supervisor is 12.2(18)SXF17b is 256M of DRAM and 64M of flash, from the "sh file systems" i can see that you have 64M of flash in disk0: but for the DRAM as Glen explained you can check the show version. second of all i want to make sure i understand correctly, are you collecting the outputs above from another switch? if yes, (and you already checked with point one above) we can take the flash or disk0 from that supervisor and try it here in this supervisor. but if this is the same supervisor and you already checked with point number one, then you need to check that you copied the IOS image correctly (verify the image using "verify /MD5 disk0:s222-adventerprisek9_wan-mz.122-18.SXF17b.bin" command) after going back to the old image to load the supervisor of course. i believe that you will see the IOS image not copied correctly, and you will have to copy it again using TFTP or FTP server. any way what ever was your answer yes or no and you already checked with the above and it is still not working, then you will have to do the following:- from rommon change the config register to 0x2142 using the command "confreg 0x2142", it will ask you to reset so type the command reset - the command above will make by pass for the configuration. the result will be on of the below:- the device will load okay with no problems, in this case this will be a bug on the software (a configuration is causing the crash) the device will not load as well, this means that the supervisor is miss-seated or there is a hardware failure on the supervisor or the chassis it self. if the image loaded will then you will have either to know what command is causing the crash by removing it one by one (very hard i know), or to try other images. but if the device doesn't load then first thing you can try to re-seat the supervisor, if it is also not working, then you will have to try it on another slot, otherwise if it is still not working, then you need to replace that supervisor, and finally the chassis if it still not working. i hope my answer was well explained have a great day, Zaid ... View more

Hello Tony, actually short link flap is caused by usual user or OS evens. For example, closing laptop lid usually putting it in standby or hibernate mode. Depending on the NIC driver the link may briefly flap and stays up while PC or laptop is in standby, hibernate or shut down mode. otherwise if that is not the case then the problem might be in one of the following;- * problem with the device connected to these interface (problem with the nic) * problem with the cable in between. * problem with the switch side. can you add the following outputs it may help more:- - show ver - show log --> if there is more logs about this flapping than the one above - show int GigabitEthernet4/39 Best Regards, Zaid ... View more

Hello Arunas, can you please add the whole logs appearing from the time you are trying to load the image untill it goes into rommon again. Best Regards, Zaid ... View more