Troubleshooting IP-centric technologies can be a new challenge for engineers. Often it becomes a case of “You don’t know—what you don’t know,” until it is too late. In addition, once the engineer knows there is a problem, it is important to know what tools are needed to solve it.
Step one in the maintenance of an IP-centric facility is knowledge of T&M and the proper gear. The old oscilloscope and voltmeter are probably not the best tools for the job. Today’s test gear is as sophisticated as the media equipment.
Step two in calming the often “Hair on fire,” panic scenario is documentation. Without a map, the engineer is hopelessly lost.
But, IP facilities require a new type of documentation. With the familiar SDI infrastructure, a traditional system block diagram is often sufficient for troubleshooting. With a modern IP-centric facility, block diagrams are of little use because of the software involved.
These two articles will help you both document and effectively troubleshoot your IP-centric facility and gear.
Troubleshooting IP systems requires both system knowledge and the proper tools. If either is missing, the odds for a winning game plan are small.
As production and playout centers and broadcasters adopt computer-based technology, the technical staffs needs to expand their knowledge of IP and the tools needed to troubleshoot these systems. Part of the process can be training supplied by the equipment vendors.
However, the bottom line responsibility is on the technical staff to understand their facility’s intricacies and have the documentation and tools required to keep it running smoothly.
In the article, “Maintenance and Troubleshooting in the World of IP,” the author suggests some steps to take through real-world scenarios. What he discovers on the job, proves to often be an eye-opening exercise.
The transition to IP is having an impact on all aspects of broadcast from business to technical operations, workflow engineering and maintenance. One key component of this change is how a production or broadcast system needs to be documented. Gone are the good old days when an engineering drawing and wire run list and some service manuals were all the engineer needed to maintain, diagnose and troubleshoot issues.
In this article, readers learn about documenting IP addresses, port configuration, VLANs and subnets. They will review the importance of documenting applications running, Firewall rules and services being used.
The article concludes with a real-life story of what happened when something failed and a facility’s IP documentation was insufficient. All this and more in the article, “How IP is Redefining System Engineering Documentation.”
Visit The Broadcast Bridge NAB coverage spectacular to see products, technology and news from this year’s convention.
While there, sign up for a free subscription to receive a daily, weekly or monthly custom email filled with content and technology that you select. Don’t wait for an out-of-date, month’s-old print version of “breaking events,” get your free membership to The Broadcast Bridge today.
You might also like...
Many broadcasters and television networks consider the provision of linear content Over The Top (OTT) for on-demand streaming a necessity. The process, however, is far more complex than preparing a file and sending it to an OTT provider. Several factors…
In the last article on Cloud Broadcasting we looked at integration and how we communicate with SaaS and cloud services in the absence of GPI’s and serial connections. In this article, we introduce secure server access and issues around s…
Rohde & Schwarz, like many companies in this sector, were once known as hardware manufacturers but are now evolving to offer new solutions. In a future where IP connectivity reigns and resolution increases to 4K and beyond it is vital…
The broadcast equipment industry is in the process of making the transition to IP based transport for video, audio and data. This has led to development of a suite of standards including SMPTE ST 2022-6 for encapsulation of uncompressed SDI…
Some engineers can maintain their current SDI systems armed with little more than a foggy memory of how things are interconnected. But with IP networks, such a philosophy guarantees panic if something fails. When it comes to properly documenting an…