mhammett

and actually, Cisco isn't overly prevalent in the IX market. It is usually Jennifer, brocade or extreme. Extreme seems to be picking up market share as there switches have a good time pls stack and the large exchanges use a lot of MPLS for scalability. Brought to you by voice to text, so hopefully it makes sense.

I was following a guide (that didn't seem to work perfectly) to import the FCC's daily transaction log, dump it into SQL, parse it for the links, then dump out a KML. Getting the system together has been pretty manual, but the end result would be fairly easy to run again and again for anywhere. I have exported 1' versions for 18 GHz and 23 GHz. I don't believe 1' antennas would be allowed in 11 GHz. These are just samples of one vendor's implementation. There are a variety of factors that go into what you use. I picked... the easiest thing to generate pretty reports for you guys. ;-) Keep in mind that the sample link I used is 4.1666 miles. Something half of that length would perform much better at 23 GHz. Also, if throughput demands for a site are smaller (as such is the case for NV1.0 and Clear towers), the smaller dishes may provide the required throughput at acceptable reliabilities. The max throughput on even an NV2.0 tower (with one channel per band) is around 500 megabit. Now factor in how much you're likely to see with the varying modulations for the active users and you may never see anything close to that. They're probably okay with less. Microwave ping times are going to be nearly indistinguishable from fiber ping times. Modern licensed microwave gear is going to have fractions of a millisecond per hop. The load on the management interfaces of the testing devices would play more of an impact. No clue on the stability of mobile LTE latencies. There is going to be a layer 2 tunnel from the eNodeB all the way to the core. Traceroutes wouldn't help (unless maybe it was an MPLS transport and the gear was configured to respond with MPLS information... unlikely.

Typically an IX is completely open and very basic. An IX may have increased measures on its management or operations networks, but the business end is not much more advanced than basic switching. Measures are typically in place to protect the IX operation, such as a single MAC per port. Route servers usually have route filtering of some kind in place to protect the Internet in general from operator (mess) ups.

Where? o.0 ;-) I'm guessing something government or financial given the degree of diversity and the carriers chosen. Then again, generic enterprise makes similarly odd decisions. ;-)

Well, there are a variety of platforms to choose from, depending on how firm the throughput requirements are. The increases in frequency (and corresponding increases in rain fade) would dictate an increase of antenna size or switch to a platform with high enough Tx (transit) power or increase in Rx (receive) sensitivity to compensate for the losses. There are formulas for rain fade by frequency, rain rate and distance. There are also formulas for dish size and frequency giving you it's gain, so you could make one formula to do all of that... or just use the tools that are available and just choose a bigger dish and see what it gets you. Here's an example of some links done at different frequencies and dish sizes. I haven't done much work at 23 Ghz, so I may simply be seeing a limitation of the product\tool. 23 GHz also appears to only be slated for 50 MHz channels as opposed to 80 MHz channels in 11 GHz and 18 GHz. I haven't verified if that's an FCC thing or a product thing. 2048QAM only seemed to be available on the 23 GHz radio and not the 11 or 18, so it made up a little bit for the smaller channel with increased modulation complexity. https://www.dropbox.com/sh/3smdt2g1ih0jg0b/AADie--OZ7vQNmTOHQSXLu3pa?dl=0 Having multiple links that go in different directions is good. For example, having a N-S link and an E-W link. Storms are typically lines and traveling along lines. A storm that went from West to East on an E-W link would experience a less intense fade for a longer period of time, while a N-S link in that same area would experience a more intense fade for a shorter period of time. If you have both and a layer 2 system that effectively measures available capacity dynamically and uses it in aggregate (such as Accedian or OpenFlow), then you are the least mitigated. Such fancy boxes are fairly new. Building these into a complete ring maximizes availability. Nice maps! I wanted to generate that for all Clear\Sprint nation-wide, but I only got part way through setting up that system. I've been crazy busy the last year or two, so that hasn't been done. When Clear built their network, Fiber To The Tower wasn't a term yet, so they made do with what they had available. It was obviously being done, but it wasn't embraced like it is now. Many of those sites may have fiber available now. Many of those sites may be existing Sprint sites. Many of those sites may be close enough to build a backhaul to an existing Sprint site. I would be using microwave a lot more if I were these guys. Every tower that is microwave-only would have at least two paths to fiber. Fiber drops would be to completely diverse fiber routes and providers. Fiber fed sites would still have a microwave path out to another fiber provider.

As a broadband provider who submitted his own network coverage data.... ;-) PS: I didn't know they have the population counts on the ISP pages. I guess I never got that far on their site.

Where are these pop counts that you are talking about coming from this website? I have never seen any pop counts on the website. They are pretty easy to calculate, however. You load in the census shapefiles as well as the National Broadband map shapefiles. You select by attributes on the National Broadband map files and search for the company of interest and the technology of interest. You save that as a separate layer. Using clip the census shapefiles to the company and technology coverage layer, which will give you call census blocks that provider covers. You then simply add up All of the population count fields.

I don't believe so. They keep coverage areas and said coverage areas are available for people to download as shapefiles and come up with their own statistics.