Hi, Have you tried in a different switch model and/or IOS? If yes, you could sniffer the traffic of the phone with Wireshark and check what messages the phone is sending and receiving. Regards. ... View more

Hi, Could you please try removing the voice VLAN setting on the port and check what happens? i.e. if you have VLAN10 for data and VLAN20 for voice, try this on the ports with 7937 phone connected: no switchport voice vlan 20 switchport access vlan 20 Cheers. ... View more

Hello Peter, Thanks for this! I actually mixed the SVI MACs with the Bridge ID. And with granularity I was refering only to the fact that the priority fields is divided in 4 bits for the bridge priority and 12 bits for the extended system-id instead of having the 16 bits dedicated to the bridge priority. Thanks again! Cheers. ... View more

Hello, The extended STP system-id is used to provide more granularity. It is used too to allow having only one MAC address per switch making it easier to troubleshoot STP issues. Please see this example to see the differences: With standard system-id we have, for instance, a priority of 32768 which is the bridge priority. With the extended system-id, we would have that priority, 32768, plus the vlan id. For example: For VLAN 100 --> 32768 + 100 = 32868 For VLAN 200 --> 32768 + 100 = 32968 And so on... In newer IOS versions the extended id is enabled by default. One situation where it is recommended is a switch with many SVIs configured (STP instances). With the standard system-id, every SVI would have one different MAC address. Since a MAC address is assigned to every SVI and hence to every VLAN, you can have the same MAC address on every SVI and differenciate them on STP instances level by adding the VLAN id to its STP priority by using the extended system-id. Hope this helps. ... View more

Hello, Maybe my question could be obvious but, do you have IPs configured on the interfaces? I cannot see them in your configuration: R1(config)#interface serial3/0 R1(config-if)#encap frame R1(config-if)#no frame-relay inverse-arp R1(config-if)#interface serial3/0 R1(config-if)#frame map ip 172.12.123.2 122 broadcast R1(config-if)#frame map ip 172.12.123.3 123 broadcast R1(config-if)#int serial3/0 R1(config-if)#no shut R1(config-if)# Cheers ... View more

Hello, Apart from duplex mismatches on the ports, the other reason why port LEDs become amber is during STP port transitions. Please check STP mode and configuration and the ports status when the cable is connected, when you disconnected and then when you connect it again. Hope this helps. ... View more

Hello, The high CPU load seems to be related to the high amount of IP flows being checked by Netflow. The more active flows Netflow is handling, the more CPU is neede to maintain the cache. You could try disabling Netflow where it is not really needed and compare the results. Regards. ... View more

Hello, I see IPv6 resources are almost no used, however IPv4 resources are. Both in FIB (64%) and Netflow TCAM resources (95%). Could you please reply these questions? - Do you have Netflow enabled in many L3 interfaces? - Do you have many IP flows? (Check with "show mls netflowmask") - Do you have Netflow Sampler enabled? (Check with "show mls sampling") Please note Neflow sampling in a SUP720 is done in software by the CPU. - Paste the output of "show mls netflow table-contention detail" and"show mls netflow aging" Regards. ... View more

Ok. Do you have Netflow Collector for IPv4 and IPv6 then, or only for IPv4 but you have IPv6 running? If possible, you can try disabling NFC for IPv6 and check if the situation improves. Cheers. ... View more

Hello, Do you have Netflow Collector enabled on the switch? If you have it, try to disable it and check if situation changes. If I remember, collection process is related to NFC. Cheers. ... View more

Hi, What I see is that when you have in CEF the entry pointing to 192.168.1.3/32 with next hop 192.168.1.3 you cannot ping it and you can ping it when the entry is the correct one: 192.168.1.0/24 with next hop 192.168.62.23. I would try clearing the adjacency table. Regards. ... View more

Hello, Have you tried the commands "clear adjacency epoch" and "clear adjacency"? It seems you have an inconsistence: RT1#sh ip cef detail -snip- 192.168.1.3/32, version 4904, epoch 0, cached adjacency 192.168.1.3 0 packets, 0 bytes   via 192.168.1.3, Vlan1, 0 dependencies     next hop 192.168.1.3, Vlan1     valid cached adjacency 192.168.1.0/24, version 18, epoch 0, cached adjacency 192.168.62.253 0 packets, 0 bytes   via 192.168.62.253, 0 dependencies, recursive     next hop 192.168.62.253, Vlan1 via 192.168.62.253/32     valid cached adjacency Hope this helps. ... View more