While we are building the InteropNet I thought I’d take a bit of time to
describe what our core technologies are. What do we need to make a
network like this operational? Well over the years we’ve been able to
boil it down to a best practices network that does everything we need in
as simple a way as possible.
Whenever I explain it to someone, I usually break it down to these
components :
Data Services. This is the ISP and more. Circuits, SIP services, CO-LO
facilities and conference calling
Routing. Anything do do with layer 2 and layer 3 forwarding
Security and firewalls. This also includes IDS, Network access (802.1x)
and end client virus protection
VoIP. Soft Phones, hard phones, Skype gateways, Instant messaging, and
any other related presencing information.
Wireless. Because this network is not just for the exhibitors
Network Management. As pro-active as possible. If something is going to
break we want to know before it happens
Network analysis and forensics. These are all our Taps, repeaters and
traffic replicators. With the right design we can copy any conversation,
anywhere for analysis.
Datacenter infrastructure, Racks, UPS, power management and everything
required to hold this gear upright
Workstations and servers. These days we are virtual. But all our
services are load balanced, backed up and replicated
Out of Band Access. We build an entire parallel network that doesn’t
touch any of our routing infrastructure. on this we hang all our console
servers, PDUs and the management ports of all out equipment.
Apr 7th, 2009 |


[...] built and tested. During the build stage, project lead Geoff Horne took some time out to over the main technologies of InteropNet which come out of a KISS doctrine to build a best practices network - including the [...]