The TrapServer has many applications. Sometimes it replaces an existing management system and used as a standalone configuration. Other times, the TrapServer is used as a mediator, relaying faults from a device to another management system. Regardless of application, the TrapServer can be customized to meet the need of an organization.
The following list of general applications so you can get an idea as to how the TrapServer can be used.
Since the TrapServer supports the 481, LarScan, Larse 3000 and MCS-11 protocols, it is a direct replacement for the Badger 2000, NetManager and TSM-2500. After a database conversion, the TrapServer is a seamless upgrade to the old system.
Since the TrapServer supports many protocols, it can monitor many device types. As each different device type is added to the TrapServer management interface, the corresponding faults are reported or "concentrated" at the TrapServer. This aspect of the TrapServer allows customers to enjoy a huge cost savings, since a single TrapServer can monitor many devices.
Since the TrapServer can forward traps (v1 and v2c), and since it has protocol conversion capabilities, the TrapServer can be placed between legacy equipment that has no SNMP management capabilities and an existing SNMP manager. After the TrapServer has been installed in this configuration, an SNMP agent will exists where none existed before. Now, the legacy equipment can be monitored with SNMP.
When equipped with the TrapServerSMT application, the TrapServer becomes a powerful translating proxy that can, if necessary, manipulate the data in a trap. Please do not hesitate to contact SchoRen if you have requirements for changing the data in a trap.
The TrapServer has SNMP trap and SNMP Get facilities that convert SNMP information to events. As a result, the TrapServer is a suitable platform to be used as an SNMP manager. In reality, the TrapServer almost always is used to simultaneously monitor SNMP devices alongside non-SNMP devices, due to its strengths as a protocol converter.
The TrapServer can be deployed as a "Monitoring Server" since it has many browser-enabled features. Event status, history reports, data communication validation, scanning and controlling of remote terminal units (RTUs), and trouble ticketing are features available from the browser-based user interface. These features are served to remote users who need not be collocated with the TrapServer.
Furthermore, with a well-planned access control scheme, the Monitoring Server will provide more than just browser functionality. The Monitoring Server will ensure that only the specified resources are available to each remote user. As a result, the TrapServer administrator can restrict users to viewing event status to only events for which a user is responsible. Likewise, the user would only be able to scan and control RTUs in a certain area of responsibility.
In order to protect a TrapServer in a different geographic location, a second TrapServer can be deployed. A redundancy module allows each TrapServer to monitor the other. If secondary TrapServer cannot communicate with the primary, it will begin monitoring the network.
The TrapServer supports many device types. The following is a partial list of protocol conversion modules. New devices are constantly being added.
| Company | Products |
| AFC | UMC 1000 |
| Alcatel | SONET Multiplexer 1603/12/48 |
| Alcatel | NMS 1320, TSM-2500, TSM-3500 |
| Andrews Corp, Mikom | MR Series, Node C Series, MMR Series |
| Applied Innovation | AIBadger, AIScout, AISpy |
| Badger AC | NetManager, 481 RTU, Badger2000, e500 RMU |
| Cordell | Centurian, ISD3000, CinNAS |
| Dantel | WebMon, Point Master Eagle, Vision Master, Remote Master, MicroNOC, 460 ACS |
| DPS | AlphaMax 82A/82S, IAM5, NetGuardian (all), DPM, KDA, RAB |
| Ericsson | Switch AXE |
| Ericsson | IMC |
| Harris | Digital Telephone PBX 20/20, StarView |
| Lucent | C.O. Switch 5-ESS |
| Lucent | DDM-2000 |
| Lucent | Wireless processor ECP |
| NET | IDNX |
| Nortel | Transport Node OC3/12/48 |
| Nortel | DMS-10/100/500/MTX, SNMP Module |
| RFS | RPM 800 |
| Tellabs | DACS Titan 5500, 530, 531, 523L |
Open: SNMP, TL-1, Modbus, TBOS, TCP, UDP, Async, and ASCII
Proprietary: Badger 481, LarsScan, Larse 3000, MCS-11