
khilving |
You have a couple of questions here.
First, the bandwidth a user buys from an ISP is potential throughput, or clockrate. In theory, you can pumb data in and out of your site at that rate. It applies only to the connection between your site and the ISP POP.
At the ISP, there is bandwidth between it and either the Internet or one or more peering ISP. Typically, this is sized at something less than half of the total bandwidth between the ISP and all of its end customers. For home user type customers, a 10:1 ratio is fairly typical.
The difference is handled in several ways. First, it is unusual for all the customers to be transmitting or receiving at once. This bursty nature of IP traffic allows everyone to move from their access line to the shared bandwidth with little delay. Next, the traffic is buffered so that packets are not dropped when there is a slight delay. Queuing can be set up so that each access line has a shot at putting its traffic out on the share bandwidth in an orderly fashion. Essentially, all lines are checked for traffic and handled before any line puts another packet out to the shared bandwidth. This keeps any one customer from “hogging” bandwidth at the expense of other customers. This is a rapid process, so the fairness is almost a per packet approach. Over longer times, one user may be the dominant user.
There are a number of software packages that can monitor the usage, and the device IOS handles the actual control based on configuration. Capabilities will vary by hardware vendor.

redrose |
thanks for ur replies,
could u please tell me some of the softwares or any other methods from isp point of view.

astronomer |
If you are looking to monitor your gross traffic going to and coming from your end of the pipe, there are several packages available. A free one we use is MRTG. MRTG uses SNMP to interrogate your network devices. It monitors utilization of ports and displays the resulting graphs on a web server.