How Cingular Unified NEC 21SV Legacy Remotes and New NetGuardian RTUs in One T/Mon System

When NEC discontinued the 21SV remote and the 21GTX Fault Management System, Cingular engineer Chuck Wood needed a path to expand monitoring without replacing hundreds of legacy remotes.

Industry	Wireless telecom (cell site operations)
Company Type	Wireless carrier
Geography / Coverage	Massachusetts and southern New Hampshire
Operational Scope	350 cell sites at the time of the project (later over 400)
Primary Challenge	Discontinued NEC 21SV remotes and 21GTX master system created expansion, reliability, and database-management risk
Solution Deployed	T/MonXM WorkStation with a custom 21SV Interrogator Software Module, plus NetGuardian RTUs at new sites
Key Result	Legacy NEC 21SV sites and new SNMP sites monitored from one T/Mon alarm display; NEC master and hard masters were removed from service
Products Used	T/MonXM WorkStation (T/Mon platform), NetGuardian RTUs, 21SV Interrogator Software Module

---

Client Overview

Chuck Wood supported remote alarming for a large group of Cingular cell sites in Massachusetts and southern New Hampshire. At each site, NEC 21SV remotes were used to monitor microwave radios, MUXs, and environmental conditions.

When NEC discontinued the 21SV remote and the 21GTX Fault Management System, the existing monitoring architecture became difficult to maintain and even harder to expand as new sites came online.

---

The Challenge

Wood faced a practical problem that many telecom operators recognize immediately: new sites were being built, but the discontinued RTU could not be purchased anymore. At the same time, the legacy master and its supporting components were becoming a single point of failure.

Problem 1: Wood Could Not Buy New NEC 21SV Remotes

With the 21SV and 21GTX discontinued, Wood had to keep his existing system running without normal vendor support.

• No new remotes: "We had more cell sites that needed remote alarm capabilities, and we couldn't buy 21SV remotes from NEC any longer," said Wood.
• Equipment failures: "I was having problems with breakdowns. I only had one spare hard master [a polling unit that mediates between the 21SV remote and the 21GTX master]. Then a hard master died, and I didn't have any more. If I lost another hard master, I'd be out of luck," said Wood.
• No one could use the software: "The one guy who knew how to change the database left the company. The master software ran on Unix, and I didn't have the Unix expertise to manipulate the database. I was getting backlogged with database changes I couldn't make," said Wood.

Two Bad Choices: Replace Everything or Run Two Systems

Wood needed a remote monitoring solution for new cell sites. From an operational standpoint, the obvious paths both carried major drawbacks:

• A forklift swapout of legacy NEC 21SV remotes: "We never seriously considered getting rid of the 21SVs, because we didn't have the money to replace them. We had 350 sites - buying a new remote for each of them would have been cost-prohibitive. We thought we might have to get rid of the 21SVs, but we wanted to avoid it," said Wood.
• Run two separate monitoring systems: "It would be bad enough that our system operators would have to learn a new interface. We didn't want them to have to log into two different systems and maintain two databases as well," Wood said.

New System Dilemma: Limited Alarm Detail or Complex SNMP Management

Even if the legacy NEC platform could be kept alive, the new sites still needed a modern alarming approach. Wood evaluated options that would either reduce visibility or increase complexity:

• Embedded scan points and poor network visibility: Wood could bring in alarms through a radio's embedded alarm system, but that meant summary alarms and limited detail. "There's 24 scan points on the Nokia system, and there's 26 alarms per radio. That's not enough points for a multiple radio site. You just get summary alarms that tell you there's a problem and you've got to go. The more information a tech has, the better he knows what he's up against," said Wood.
• SNMP manager with difficult configuration: "We were looking at using SNMP remotes reporting OpenView, but OpenView is complicated. In OpenView it's very hard to set up screens and alarms, and OpenView doesn't do paging by itself. It's very user-unfriendly," Wood said.

---

The Solution

Wood consulted with DPS Telecom to evaluate the NetGuardian RTU product family as an SNMP remote for new sites. As he became more familiar with DPS capabilities, he identified a bigger opportunity: unify both old and new sites under one monitoring system, without replacing working NEC 21SV remotes.

Why T/Mon Instead of a Generic SNMP Manager

Wood determined that a DPS Telecom T/Mon Remote Alarm Monitoring System would be a better fit than a general-purpose SNMP manager for day-to-day telecom operations and alarm response.

"At first we were looking at NetGuardians reporting to OpenView, but when we saw the capability and simplicity of T/Mon, we realized T/Mon would be easier to implement and we'd get better performance," said Wood.

In practical terms, a T/Mon system is purpose-built for alarm collection, event processing, and operator workflows. When you are consolidating alarms from many sites and device types, T/Mon is designed to keep alarm presentation clear and actionable, while supporting multiple protocols and integration methods.

Legacy Protocol Support for NEC 21SV Remotes

During the evaluation, DPS Telecom offered a legacy support path that addressed Wood's core concern: keep the 21SV remotes in place and still monitor everything from a single screen.

"They told me they could develop a solution for polling NEC remotes for T/Mon. I wasn't really confident that it could be done, so I said, 'Prove to me that it works, and I'll buy it,'" said Wood.

---

Implementation

Wood deployed a T/Mon alarm monitoring workstation with a custom-designed software module that polls NEC 21SV remotes in their native protocol. This became Wood's central platform for alarms across both legacy and new sites.

To reduce administrative overhead, DPS also developed software to convert Wood's 21SV alarm database to T/Mon format, eliminating the need for new database work during the transition.

As new sites were added, Wood installed DPS Telecom RTUs (NetGuardians) to provide SNMP-based alarming and site I/O expansion where needed, while keeping the monitoring and operator interface consistent at the center.

---

Results

Wood received his custom-developed solution, the 21SV Interrogator Software Module for T/Mon. With legacy polling integrated and new sites using NetGuardian RTUs, Wood could manage alarm monitoring from a single T/Mon system.

Wood summarized the operational outcomes of the integrated approach:

• Full support for NEC 21SV remotes: "I've got support to run the 21SV remotes until they die. I'm continuing to use the 21SVs, but as they fail, I'm replacing them with NetGuardian," Wood said.
• New NetGuardians for new sites: "As far as the NetGuardians go, I don't have any complaints with that system at all," said Wood.
• Eliminated unreliable legacy hardware: "I've shut off my master NEC unit and the hard masters, and now I do everything with T/Mon," said Wood.
• Easier database work: "I can easily manipulate the T/Mon database. It's dramatically easier than the NEC was," said Wood.
• Simplified network and more reliable polling: "The polling from T/Mon is actually more reliable than it was from the NEC master, and it's much simpler. I used to need the NEC master, and then three separate hard masters for each leg. Now I just have the T/Mon, with three separate ports for each leg on the same box," said Wood.
• Easy access to alarm information: "It's a big improvement that we can Web directly into the T/Mon. You couldn't Web into the NEC. From the technicians' perspective, a Web interface simplifies the job. They can get diagnostic information without having to worry about the alarm system. They can be at the site, look directly at the alarms. There's no delay. Everything's instantaneous," said Wood.

---

Key Takeaways

• Legacy RTUs do not always require replacement: With the right protocol support, existing remotes can remain in service while you modernize the monitoring center.
• Unifying alarms reduces operational friction: One interface and one database helps operators and technicians work faster than maintaining separate systems.
• Modern expansion can be staged: New sites can use NetGuardian RTUs while legacy sites remain online, then migrate over time as equipment reaches end of life.

---

Products Used in This Solution

• T/Mon Alarm Monitoring System (Alarm Master platform) - Central alarm monitoring, event handling, and operator interface.
• NetGuardian RTU product family - SNMP alarming and site monitoring for new deployments.
• 21SV Interrogator Software Module for T/Mon - Custom module used to poll NEC 21SV remotes in native protocol (available to DPS clients).

---

Want More Information About T/Mon Legacy Support Solutions?

Chuck Wood's custom solution, the 21SV Interrogator Software Module, is available to DPS clients. NEC 21SV support is one of many integration options available for T/Mon, which supports over 30 standard, legacy, and proprietary protocols.

T/Mon can consolidate alarms from remote sites to one screen, reducing the need for multiple specialized consoles and helping operators focus on actionable alarm detail.

---

Industry and Challenge FAQ

Can T/Mon monitor both legacy protocols and SNMP devices?

Yes. This project combined legacy NEC 21SV polling (via a T/Mon software module) with new SNMP-based alarming from NetGuardian RTUs, all presented through one T/Mon operator view.

What is the operational risk of relying on discontinued master hardware?

When key master components become unavailable, failures can create gaps in alarm visibility. In this case, Wood described limited spares for hard masters and the risk of losing monitoring capability if another unit failed.

Why not just use an off-the-shelf SNMP manager?

Many SNMP managers are general-purpose tools that can be complex to configure for telecom alarm workflows. Wood preferred T/Mon because it was easier to implement for alarm presentation and day-to-day operations.

How do NetGuardian RTUs fit into a migration plan?

NetGuardian RTUs are commonly deployed at new sites to collect discrete alarms, environmental inputs, and equipment status, then forward alarms upstream via SNMP. Wood used NetGuardians for new sites while keeping NEC 21SV remotes in service at existing sites.

Can legacy alarm databases be transitioned into T/Mon?

In this case, DPS developed software to convert the NEC 21SV alarm database into T/Mon format, reducing manual re-entry and accelerating cutover.

---

Secure Your Network with the New IAM-6

If you want to protect your network against the dangers of service outages and equipment loss, check out the new IAM-6. It's 2-6 times faster than the IAM-5 and fully compatible with your existing IAM/T/MonXM software and database.

---

Next Step

If you are expanding into new sites while supporting discontinued RTUs or legacy protocols, DPS Telecom can help you consolidate alarming into one operational view with T/Mon and NetGuardian RTUs.

Get a Free Consultation