| DSL - Which remote? With CO-ADSL, indie ISP's know which CO their customers are connected through.
With TPIA (currently), indie ISP's know which POI their customers are connected through.
Do indie ISP's know which remotes their customers are connected to?
It seems to me that IISP's should be given this info by the incumbents so they can more readily determine where network problems are, or at least be able to notify their customers served by a particular remote if there is a localized issue. |
|
|
|
| The closest you'll get is which BAS a customer is connected to, however there are generally many DSLAMs per BAS and there are often many BAS per city.
I'd say the most common outages have to do with the BAS rather than any failures with the hardware in the remotes. It does help to determine how many and which customers would be affected, but not so much for pinpointing a specific area.
Each BAS also have individual IP addresses that can be monitored to detect issues and notify affected customers accordingly. |
|
| Yes ....BUT.....when Bell has a lot of customers of their own on remotes sucking down 100 different HD channels simultaneously (ie. say 400 total customers on a remote between Bell and indies) and you add simultaneous internet use by a large number of other users, then you begin to get a recipe for either remote choking due to local cpu constraints, or due to backhaul from the remote constraints.
So the BAS further upstream is too far removed from potential localized congestion issues, and that makes is much harder for indies to better understand why customers may be having problems and taking action with the incumbent that is more productive than simply opening a ticket with Bell/Telus saying that the indie end customer is complaining about something. |
|
| said by MaynardKrebs:(ie. say 400 total customers on a remote between Bell and indies) AFAIK, the biggest VDSL2 remotes used by Bell only have 192 ports, slightly newer ISAM VDSL2 remotes maxed out at 144 ports and the current ISAM 735x remotes only have 96 ports... so 400 subscribers on a single VDSL2 remote is not going to happen. |
|
| So what - it was an example. If 50% of the SLAM users are watching 100 separate HD channels then either the SLAM will be i/o bound or cpu bound |
|
| Remote are designed to handle wire-speed traffic. They are not doing real time content encoding that eat up CPU time, so it is not like the hardware is going to melt down or anything. The overall traffic would be limited by the upstream link a remote is connected to.
Bell might have preallocated (at the expense of IP) bandwidth for those TV traffic from the links... |
|
| reply to MaynardKrebs
said by MaynardKrebs:If 50% of the SLAM users are watching 100 separate HD channels then either the SLAM will be i/o bound or cpu bound 100 HD channels at 7Mbps CBR each is only 700Mbps, only 1/3 of available uplink capacity. The likelihood of having 100 unique streams pulled to the same remote with less than 192 subscribers is very low and those are actually 7Mbps max VBR so total bandwidth would be much less than 600Mbps, particularly during peak hours where most people will be watching/recording the same 20 or so prime-time channels.
As far as being CPU-bound goes, when was the last time you have seen carrier-grade equipment advertising anything less than line-rate throughput in its intended application? Most modern hardware even boasts about line-rate performance with all features enabled. |
|
| reply to Ott_Cable
said by Ott_Cable :Remote are designed to handle wire-speed traffic. They are not doing real time content encoding that eat up CPU time, so it is not like the hardware is going to melt down or anything. The overall traffic would be limited by the upstream link a remote is connected to.
Bell might have preallocated (at the expense of IP) bandwidth for those TV traffic from the links...
And that. among other things is reason enough to know which remotes indie customers are connected to. Otherwise the incumbents will continue to pull the wool over indies (and their customers) eyes. |
|
