"TCP will also adjust its initial retransmission parameters based on the bandwidth configured on the interface."

I was unaware of this.

This is for TCP traffic sourced from the network device?

Can you provide any reference?

Joseph,

seems here Yognesh wants to say - this

bandwidth

command adjest the TCP window size in random manner.

Yognesh - is it right ????

good explanation of

bandwidth 

command !!!!!!

Hi Lucien,

From you message "You can limit BW with Qos".

Maybe you want to say something else, but

bandwidth 

in the policy-map will not limit the BW. It will

guarantee

BW during congestion.

Regards,

jerry

I want to give an example on how you can have 2 megs of bw guaranteed for specific traffic.

There is no point of making a pipe smaller than what it is, so QoS is a way to segment it into pieces as you know and guarantee traffic.

"There is no point of making a pipe smaller than what it is . . ."

To clarify for others, that although this is normally true, there are exceptions.

For instance, you might have a physical interface much faster than the end-to-end path supports. In such cases, you might want to slow a faster interface to match available

bandwidth

further along the path. (E.g. Ethernet hand-off to some WAN technology.)

Another instance, for some policy (or other special) reason, you might want to provide all or some traffic less

bandwidth

than what's actually available. (E.g. using VPN, you don't want VPN traffic sent to a remote site to fully utilize all remote's Internet

bandwidth

leaving some

bandwidth

for remote's native Internet traffic.)