Cisco IP Phones have a 3 ports switch inside them. One port for network uplink, one port for PC and one port to internal IP Phone ASIC.
This 3 ports switch does not run Spanning-Tree protocol, BUT it does pass the BPDUs across the ports, so when you "loop" by connecting both PC and network ports to your network, your switches will detect the loop and move one of the ports to blocking.
This exactly what you're describing.
If one of the ports becomes blocked (as it should), there should be no loop, so it is puzzling to me.
Are you sure that one of the ports connected to that IP Phone goes to blocking?
BTW, you SHOULD be using portfast feature, cause otherwise you force your users (and IP phones) into unnecessary 30 seconds delay when the port comes up...
PC Port of the IP Phone which is connected to my switch port(throu network port)gets blocked as soon as Loop has occured.
Even i have seen that the switch ports will become orange and in that switch if i see
"sh spanning-tree blockedports i will see that port is blocked.
My only problem at this stage is my Switch CPU goes to 100% and ping response to my switch will be high(More than 200 or 300 ms).At this stage my lan will be slow and my in my ip phones i do find lot of voice cracks becos this high ping response.
This sunday i my self purposefully looped by connecting PC Port of the IP Phone to the switch, then switch port went to blocking stage. One strange this was my switch CPU Utilization was fine, it didnt go above. This might be becos of it was sunday.
I will enable
Spanningtree portfast bpduguard enable
This should be fine right.
Pls let me know is there any other configs to be done.
If you use "Spanningtree portfast bpduguard enable" you can expect one of the ports to be error-disabled instead of blocked. This is a normal behavior for this feature. You would either need to issue "shut" and then "no shut" to bring it back UP or use error-disable timeout command.
Oviously, you will need to break the loop before recovering otherwise it will be error disabled again :-)
If the port is blocked there is no loop.... so you might hitting two options:
1. IOS bug that some traffic still leaks through a blocked port. Blocked ports should not transmit any traffic (this what breaks the loop), but they listen to BPDUs just in case they need to transition to forwarding.
2. This is a coincidence and dually plugging your phone to the network has nothing to do with it. If you can consistently tie this event to the network outage, then it's probably related and then maybe only option 1 exists.
Both options are difficult to identify. TAC will most likely not be of much help, but you can give them a try :-)
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...