The following config was applied to 3750 switch ports and appeared to have a detrimental effect on the LAN. It seems that the config put all user traffic into native Vlans, which then left the traffic floating around in the core with nowhere to go. Ooops - not clever!! Each floor has it's own Vlan and voice is the same for all floors.
The STP, queueing and mls entries are the defaults created by the "auto qos voip trust" cmd
description *** Phones or PC's ***
switchport trunk encapsulation dot1q
switchport trunk native vlan 110
switchport trunk allowed vlan 300,110
switchport mode trunk
switchport voice vlan 300
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
mls qos trust cos
auto qos voip trust
spanning-tree bpduguard enable
Currently the phones have not been deployed, therefore only host PC's are in use, so when the config was ripped out and replaced with just access port commands all settled down and the LAN runs sweetly.
So the question is, and it's a bit of a grey area for me, what should the port config look like in order to support the Nortel phones when they are rolled out? They don't support CDP as the new Mitel SW version does so Im a bit stuck and would appreciate some input.
If i understand your issue correctly, then you should remove the, switchport trunk native vlan 110, and replace it with switchport trunk vlan (FloorVlan). Also allow this vlan over the trunk instead of 110.
Because you designated 300 as the voice vlan it will assume that the user traffic should ride on vlan 110 which seems to be the native vlan.
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...