The document explains, if we can configure transmit-rate percent 100 on physical interface and if the percent is calculated based on shaping rate value or default physical interface Bandwidth.
Noticing that 2g is provisioned on the Cos for a 2G Link.Can you please check and update.The interface which we are checking is xe-1/3/0.
CoS information:
Direction : Output
CoS transmit queue Bandwidth Buffer Priority Limit
% bps % usec
0 BE 50 1000000000 25 0 low none
1 PRI r r r 0 strict-high none
2 BC 5 100000000 35 0 low none
3 NC 5 100000000 5 0 high none
Preclassifier statistics:
Traffic Class Received Packets Transmitted Packets Dropped Packets
real-time 0 0 0
network-control 551481 551481 0
best-effort 78909358 78909358 0
Please let us know if this is configured properly or should we be seeing 2000000000 for the best effort queue.
We checked by removing the shaping rate and setting the BE transmit-rate percent at 75:
We found below output :
Destination slot: 2
0 BE 75 7500000000 25 0 low none
2 BC 5 500000000 35 0 low none
3 NC 5 500000000 5 0 high none
This shows that when no shaping rate is configured, BW is calculated on default interface BW.
Whereas, with shaping rate 2g configured, we saw the following output:
0 BE 75 1500000000 25 0 low none
When trying the make the BE transmit-rate percent at 100 and shaping rate 2g, the configuration was not allowed to commit.
[edit]
nemo-re0# set class-of-service schedulers BE transmit-rate percent 100
nemo-re0# commit
[edit class-of-service]
'scheduler-maps HERE'
Total bandwidth allocation for low priority queues exceeds 100 percent for scheduler-map HERE
error: configuration check-out failed
nemo-re0#