All connection points have default data transfer capacity values doled out to them. At the point when default data transfer capacity is a lot higher the real transmission capacity which can cause mislead traffic in the organization. Perhaps there was a superior way with 50 Mbps yet the steering convention believed that this way had 100 Mbps accessible.

The connection point data transmission values not influence the real speed or limit of the connection. Its is just for steering metric computation. Along these lines, the data transmission esteem should mirror the real speed of the connection with the goal that the steering table has exact best way data.

  • Router1 and Router2 should be set to 10 Mbps
  • Router2 and Router3 should be set to 1544 Kbps
  • R3 and R4 should be set to 100Mbps
  • R1 and R4 should be set to 128 kbps

Normally, the transmission capacity upsides of Ethernet interfaces match the connection speed, however a few different points of interaction and generally sequential connection point speed frequently not quite the same as the real speed of the connection. The default data transmission on most sequential connection points set to 1.544 Mb/s on new Cisco switches and the sequential points of interaction of more seasoned may set to 128 Kbps. The “data transfer capacity” order lets IOS know how much data transfer capacity is useable on the specific connection point. Allude to the model in Figure 1. Where I have rolled out little improvements in the past geography for better agreement. Notice the connections between:

Changing the Interface Bandwidth To change the data transfer capacity of the connection point utilize the <bandwidth kilobits> order. To reestablish the connection point default data transmission then we can utilize the <no bandwidth> order. Figure-3 delineates the transmission capacity setup. The sequential connection point on Router-3 likewise required a similar transmission capacity design.