I have core switch connected to uplink Cisco router on 1/0/48. Port 1/0/1 on the switch is connected to a server.
Now here is the configs for both ports for comparision:
interface GigabitEthernet1/0/1description Serverswitchport trunk allowed vlan 10,70,200,115,192,193switchport trunk encapsulation dot1qswitchport mode trunkspanning-tree portfast edge trunkinterface GigabitEthernet1/0/48description uplink ROUTERswitchport trunk encapsulation dot1qswitchport mode trunksrr-queue bandwidth share 1 30 35 5queue-set 2priority-queue outmls qos trust dscpauto qos trustend
CORE#show mls qos interface gigabitEthernet 1/0/1 queueingGigabitEthernet1/0/1Egress Priority Queue : disabledShaped queue weights (absolute) : 25 0 0 0Shared queue weights : 25 25 25 25The port bandwidth limit : 100 (Operational Bandwidth:100.0)The port is mapped to qset : 1
CORE#show mls qos interface gigabitEthernet 1/0/48 queueingGigabitEthernet1/0/48Egress Priority Queue : enabledShaped queue weights (absolute) : 25 0 0 0Shared queue weights : 1 30 35 5The port bandwidth limit : 100 (Operational Bandwidth:100.0)The port is mapped to qset : 2Now, queuing is applied on 1//0/48 but not on 1/0/1.
what //The port bandwidth limit : 100 (Operational Bandwidth:100.0)// means? Does it mean that the interface BW can't go higher than 100? why?
Also, how to disable any queuing on the 1/0/48 to grant full 1G bandwidth?
Go to Solution.
bandwith is "limited" to 100% (percent ) not bps!
View solution in original post
BTW, if I'm reading your posted information correctly, the first queue might also be shaped, i.e. capped.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: