Initial adoptions of DOCSIS 3.1, the highly-anticipated CableLabs specification update packing 10x capacity increases over its predecessor, have already stirred up the global broadband community. Major MSOs such as Comcast, TDC-Denmark, and Cox have started initial implementations, paving the way for service providers that look to embark on a long and storied journey with the latest catalyst in broadband network innovation. In July 2016, Australia’s National Broadband Network (NBN) announced their plans to upgrade their hybrid fiber-coaxial (HFC) network with the specification. Continue Reading
You may think that there’s nothing wrong with manually managing your IP resources on spreadsheets –– after all, you’ve done it that way for years. But just because this has worked for you in the past doesn’t mean that this method will hold up when you migrate to IPv6. Even if you haven’t started thinking about IPv6 yet –– although you should –– there’s a good chance that you’re already spending too much time and money on inadequate IP management. Continue Reading
After decades of talk, the time for IPv6 has finally arrived. There are several transition options available, but whatever approach you choose, the challenge will be to make sure that your subscribers don’t experience a reduction in quality of service.
We have always taken redundancy very seriously at Incognito, and for years, we have ensured that our products have been clusterable and redundant. You can read more about our DHCP redundancy here. It definitely adds a large degree of complexity, but is well worth it in the end. Continue Reading
I’m often asked how many devices-per-second we can provision. The answer is far more complex than just saying 2,000 devices per second, for example. You can compare this to the car seller’s adage: “Your mileage may vary.” In provisioning, it definitely will vary, and it can be difficult to say by how much.
First, consider what’s involved in provisioning. We first must find the subscriber in a database. If the database is local (client class), then this lookup is very fast. If the subscriber is a member of multiple client classes, then this introduces a small increase in processing time. If the subscriber resides in LDAP, the delay is more significant. There are other factors to consider too. Where is that data hosted? What kind of hardware is being used? It’s impossible for us to predict ahead of time. Continue Reading