ALARM MONITORING / 
NETWORK MANAGEMENT / MEDIATION
Ideal for Disaster Recovery
ALARM MONITORING /
NETWORK MANAGEMENT / MEDIATION
Ideal for Disaster Recovery
TrapServer SUMMARY:
Mediates/Monitors/Dispatches/Forwards Events --
Area Viewer: Quickly determine system health via graphic
interface
Event Viewer: See everything that affects QoS
Web Reports: Enable users to remotely see network health
Craft Access Security: Minimize windshield time by allowing
remote access
Dispatch Manager: Notify scheduled technicians without operator
assistance
The
TrapServer is an application-agile, vendor-neutral, multi-protocol network
management tool that
consolidates and
monitors ASCII/TL-1, TBOS, SNMP, MODBUS,
and proprietary protocols from
network elements relating to a
company’s internal
communications infrastructure. TrapServer
manages Area-Of-Responsibility
notification and reports. TrapServer provides users with
trouble-tracking
from notification of an event through its repair to resolution of the
detected
trouble. TrapServer provides Disaster Recovery through redundant
TrapServers and
supports multiple IP and
gateway connections to internal
infrastructure. TrapServer “future-proofs”
your monitoring network with a
specific goal
of reducing operating expenses.
Specifically, the TrapServer displays, forwards, archives, dispatches
and monitors
SNMP, ASCII,
and TL-1 based
equipment
providing a simple, low-cost
tool that will decrease the
amount of dispatches
to a problem site.
It also serves
as a platform to notify (page / email) your
technicians on
qualifying
events. For instance, the TrapServer can be
configured to
notify only when critical
and major alarms
occur. This augments the NOC
and puts the dispatch decision-making into the most
knowledgeable
resource, your regional staff.
A detailed list of features:
* Color-coded text events in Event Viewer containing a History Window and a
Standing Alarm Window.
* Manager that processes SNMP trap v1/v2, ASCII / TL1 over serial, TCP/ IP and
FIFO.
* Trap Forwarding feature to forward traps to multiple SNMP managers with any
trap version
(SNMP trap v1, v2c).
* Trap Relay feature that process traps from trap-generating SNMP devices.
* Gateway, via dual network interfaces, which provides routing capabilities and
can restrict access
to the region.
* Event Viewer contains facility to clear and acknowledge events.
* Notification (email / page) of qualifying events if system-level timeout
exhausted before event is cleared
or acknowledged and also based upon duty schedule.
* Event Reminder feature is a system-level, user-adjustable time (seconds)
setting that allows events to be
continually reported until cleared or acknowledged.
* Web-based history report.
* User security restricting usage of the TrapServer features as well as
restricting use of the operating system.
* User administration that configures all TrapServer and operating system user
security in two simple steps.
* Craft access to monitored network elements via serial interfaces. Telnet used
for TCP / IP devices.
* Simple OEM integration.
For SONET TL-1, TrapServer can manage events from the Alcatel 1603/1612 SONET
Multiplexer. For
Nortel DMS Switches, Trap Server can manage events from the
DMS-100/100/250/MTX Central
Office Switches. TrapServer can also manage equipment
involved with Harris microwave monitoring
systems.
A partial list of applications:
► 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
► Protocols supported
Modbus, TL-1, TBOS (all either Serial & TCP/IP)
and
Badger 481
► Tellabs
DACS Titan 5500, 530, 531, 523L
Modbus Serial and Modbus TCP/IP is another protocol recently added to the
TrapServer that is of interest
to utilities such as electric and pipelines.
TrapServer operates in a "Stand Alone" configuration and in an
Integrated Configuration with Badger
NetManager. All the features
currently provided with TrapServer are still available; Event Viewer;
Web
Reports; Secure Craft Access; Regionalization of IP addresses and
optional Email/Paging.
Other protocols for the TrapServer include: the Nortel Transport Node OC3/12/48,
Lucent
DDM-2000 and AFC UMC1000 Fiber multiplex interfaces. These interfaces are in
addition to the Alcatel
1603/1612/1648 Fiber Monitoring
Interfaces. Furthermore, path break (ring or link) can be detected
and the location (between fiber terminals) can be presented to the user too!
FIBER MONITORING: TrapServer will also
provide monitoring of TL-1 Fiber Multiplex Gateway from the
equipment
incorporating Python scripts to interface for each Fiber Multiplex "type". Events detected from the
Nortel equipment
will be prioritized and enabled for
paging/email based on customer-defined priority using
the Dispatch Manager.
Customer can also view these events using dial-in and/or html (WEB) browser
access for current events and for event
history.
FAULT LOCATION: Optionally, for fiber fault
location, TrapServer employs an in-bound Tstx driver equipped
with a
custom
Python Module to perform event correlation and system logging. This is used in
determining a
fiber cut (outage)
within a specific route. Once the Python Module
is implemented, the event correlation rules
would be adjustable using a
graphical interface.
TrapServer offers customers a secure migration path for future expansion of
their alarm and control systems.
Non-proprietary hardware, interfaces,
operating systems, and protocols keep the customer in control of his
system.
TrapServer supports the writing of new scripts for alarm gathering but the
customer can easily write
their own to
customize the system as the wish. As
newer equipment enters the system architecture, systems
upgrades are routinely
handled by the customer using Python, an open source language. (Additional
software modules are being written for
legacy and newer network elements on a
routine basis.)
TrapServer can poll Badger
481 RTUs (and soon Larse 1200 RTUs) over an IP Network.
Each RTU has it’s own IP Address
(because of
the terminal server) and TrapServer opens
a socket to the RTU and polls those
RTUs.
Some things you may want to consider when you make your decision:
-- How
flexible is the system in regards to interfacing to existing network elements or
network elements?
-- How flexible is the system in regards to the hardware it is operating
on?
-- Does the system offer flexibility of monitoring legacy & new network
elements over multiple IP networks?
-- Can the system accommodate MULTIPLE LAN networks?
-- Can the system be supported locally using Operations Personnel?
-- Does the system fit into your future plans regard "Open Systems" such
as non-proprietary hardware and
non-proprietary software?
-- When there is a hardware problem with the system, do you need to send
it back to the factory or can it
be supported
locally?
-- How limited in monitoring capacity is the system (i.e., what quantity and
mix of devices can be monitored)?
-- Can the system support multiple logged-on Web Browser sessions?
-- Customizable reports such as “over the weekend” report?
-- Can options be easily added (such as Trouble-Tickets)?
-- Does the system poll Badger 481 RTUs (and/or Larse 1200 RTUs) over an IP network?
-- Does the system restrict you to use a hard-to-support operating system
such as DOS?
Is this your problem?
“Every NE we purchase comes with its own EMS, so that we have many systems we need to watch and learn.”
“My company just acquired new sites/operating areas, and they have an incompatible monitoring system separate from what I use now.”
“My system is obsolete; I can’t expand it, and it is no longer supported by the original vendor, or I can’t find the original vendor so I can’t get support.”
“My monitoring system is difficult to operate and can’t easily grow with my communications system.”
“I need my technicians to have access with the same information as the NOC.”
“My current system works well, but it isn’t compatible with the latest technologies we are adding to our system."
TrapServer is the solution!
TrapServer is a registered trademark of SchoRen NMS Solutions, Inc.
Please let us know if
you'd like a TrapServer datasheet or presentation.
If you're interested in hearing about a very
cost-effective, IP-based (web-based) RTU (Remote Terminal Unit)
similar to that
from Applied Innovation
(Badger AI - OmniRemote), DPS (NetGuardian), or Dantel's WebMon,
please let us
know.
Below is a brief overview:
Enterprise 500 Remote Monitoring Unit (e500 RMU)
with expandable contact closure alarm points, analog inputs, and control relay
outputs,
as well as terminal server ports.
Functions & features:
•
One or Two
Ethernet Ports
– Router
Functionality with local access
•
Wide Range Power
Supply
- +/- 21
to 60 VDC. AC Option Available!
•
6 Terminal
Server Ports, Optional 2 additional.
Ethernet and/or
Dial-up
•
Optional 48
Contact Closure (Bi-State)
Monitoring
Points
•
Optional 48
Single Analog
Monitoring
Points
(or 24 Differential)
•
Optional 16
Control Output
Points,
3 form C
•
Built-In Web
server
for
Viewing & Configuring Alarm & Control Points
•
SNMP traps to
Integrated TrapServer
and
other SNMP managers
•
Optionally use
Dial-up
for reporting SNMP over PPP
•
Detects door openings and office summary alarms
•
Normal/Off-Normal point configuration
•
Configurable delay or debounce setting per point
•
TTL or Contact Closures to ground
•
For Temperature and Power measurements
•
Monitors fuels levels
•
20 m volt Resolution per input
•
Multiple Thresholds in Voltage Range
•
Operates devices remotely by approved Users
•
Turns on lights or auxiliary equipment
•
16 Control Relays
•
Magnetically Latched in position
•
Telnet to each Port independently
•
Enables users to access craft ports remotely
•
Remotely configure Network Elements
•
Monitor NE’s, be they applications in telephony, cellular, datacomm, etc.
IBEX Systems
150 Greenfield Drive
Bloomingdale, IL 60108-3016 USA
tel: 630 307-3634 fax: 630 307-3539
www.ibexsystems.com
Click
here to send
us an Email!
See More Exciting
Things! Return to
Cover Page 