9638
Previous Page: What if LAN connections are not available to remote sites (like a transmitter site on top of a mountain)?
PDFDownload White Paper

Chapter 2: Making SNMP-Legacy Integration Work - Without Sacrificing Functionality

Let's tackle the top question most network managers have about SNMP-legacy integration - can you really integrate to SNMP and still retain all the useful features and functions of your legacy equipment?

That's a smart question to ask. There's no point to an "upgrade" that gives you less functionality than before.

A truly successful integration means mediating all your alarms to SNMP - from every type of equipment and every protocol you use -without losing any essential information in the process.

It sounds like a pretty tall order ... and in fact, it is. But you can do it, and I'll show you how.

As I will throughout this course, I'm going to talk about this subject by fielding some actual questions and problems submitted by network managers.

Legacy Migration
T/Mon converts alarms from all equipment to a common format for both local visibility and SNMP mediation.

QUESTION #1: "If I integrate my systems, can I still keep all the advantages of both?"

The whole purpose of integration is to enable you to monitor with SNMP without being limited to just SNMP-native equipment.

Being locked into one telemetry protocol is just as dangerous as being locked into one equipment vendor - you're stuck with what's available, not what will really meet your needs.

SNMP has a lot of advantages: it's open, extensible, and widely supported. But other common telemetry protocols such as TL1, TABS, TBOS and ASCII can often provide more detailed and more robust alarm visibility than SNMP.

And aside from protocol considerations, your existing legacy equipment may have features that can't easily be duplicated by new SNMP equipment.

You can retain those functions and features by choosing protocol mediation equipment that 1) fully supports all the protocols you use and 2) can fully convert data from legacy and proprietary protocols to SNMP.

The T/Mon Remote Alarm Monitoring System performs these functions by converting all incoming alarms - no matter what their source protocol - to a common T/Mon format. This format retains all the information contained in the alarm, and all alarms in this format can be forwarded as traps to your SNMP manager.

If the protocol you work with is supported by T/Mon - and T/Mon supports over 25 different protocols - you can monitor it with your SNMP manager. You can select the equipment you want, confident that it will work with your SNMP monitoring.

Next Page: Watch out for this potential obstacle to successful integration
PDFDownload White Paper

Get a Custom Application Diagram of Your Perfect-Fit Monitoring System

There is no other network on the planet that is exactly like yours. For that reason, you need to build a monitoring system that's the right fit for you.

"Buying more than you need" and "buying less than you need" are real risks. You also have to think about training, tech support, and upgrade availability.

Send me a quick online message about what you're trying to accomplish. I'll work with you to build a custom PDF application diagram that's a perfect fit for your network.


Make an Informed Decision


Your network isn't off-the-shelf.

Your monitoring system shouldn't be, either.

Customized monitoring application drawing

We'll walk you through this with a customized monitoring diagram.

Just tell us what you're trying to accomplish with remote monitoring.

Get a Custom Diagram