Putting it all together
Jan 1, 2009 12:00 PM, By Brad Gilmer
Follow these steps to build a solid IT infrastructure.
Broadcasters should ensure that patch panels, patch cords and other basic network infrastructure components are rated for the appropriate network speeds. Frequently, older components may cause errors on a network and loss of performance.
Broadcasters are becoming more dependent on their IT-based infrastructures every day. It is increasingly important to have a solid network to support professional applications.
Given that this is a January column, it seems appropriate to look back at topics covered over the course of the previous year, but from the perspective of building an overall infrastructure to support your professional broadcast applications.
When evaluating a network for professional applications, it is critical to consider the overall network design. For most broadcasters, this means evaluating a network that is already in place. That said, the following points apply even if you are building a new facility.
Cable, wall jacks, patch panels and jumpers
In a facility that evolves over time, it is not uncommon to find a mix of cabling technologies. Given that network speeds have increased tremendously over the last five years, it is entirely possible to have a mix of media types and terminations in your facility. If there is Cat 6 rated cable throughout the facility, but there is an old Cat 3 patch panel somewhere in the critical path, the overall network performance will suffer. If you have not done so recently, conduct a survey of wiring, wall jacks, patch panels and jumpers, and other network cabling infrastructure to get the maximum performance out of your networks.
Rogue switches and unauthorized components
In facilities that have been in use for some time, it is not uncommon to find a switch or some other network component has been added without consideration of its effect on network performance. If the switch is old, or does not have capabilities needed in the network, you can experience significant performance issues. Look for equipment that is added haphazardly after the initial network design. On critical broadcast networks, create and enforce a policy that reduces the likelihood of the introduction of rogue network components.
Of course, sometimes in the rush to get a new facility on the air, broadcasters may grab whatever equipment they can get their hands on. They intend to replace that equipment as soon as things calm down, but frequently the initial equipment may stay in place for years, even if it was a temporary fix.
Level of redundancy
Everyone is under cost pressure these days. Furthermore, not every element in your networks is critical. Evaluate the design of your network, and employ appropriate redundancy plans for the business value being supported by the network. Network design allows you a great deal of flexibility in deploying redundancy only where it is needed. Just because you have a critical application on a network does not mean that every connection on the network should be protected from failure to the same extent.
Consideration for key network services
Most networks require certain services in order to function. In a typical broadcast facility, these might include Domain Name System (DNS) servers, Network Time Protocol (NTP) servers and Dynamic Host Configuration Protocol (DHCP) servers. If you are responsible for a core broadcast network, know where each of these servers is located and what impact, if any, there would be if they quit.
Current software revisions
Committing to a regular plan of preventative maintenance is critical to maintaining performance. You should view the overall network in the same way you view a news camera or broadcast switcher. Network components require maintenance as well.
While networks do not require much physical maintenance, it is critical to maintain a plan for the upgrade of routers, switches and computers on the network. In many cases, this means committing to testing and rolling out software or firmware revisions as they become available. But this must be a conscious decision that also takes into account the impact of deploying upgrades in mission-critical applications.
For example, I know some plants where the engineering managers refuse to deploy any new software until the first major maintenance release is available because they think at that point the manufacturer has identified the critical issues that need to be addressed. I am not advocating this position, but it does make the point that while in many cases it is important to maintain your systems at the most recent upgrade level, you may decide to temper that decision based on your own experience and level of expertise.
My personal experience has been that you should not wait too long to upgrade systems, because the work involved in moving from old software to the current version may be huge. In many cases, it is easier to do it in smaller increments.
| Want to use this article? Click here for options! |  |
