Adding SNMP capabilities to legacy or new developments is made easy by using our SNMP Remote Proxy Daemon.

• Written in Java for maximum performance and portability.
• Configured with a single XML file.
• Can monitor events on the local host or remote hosts (hence proxy).
• Easily interfaced using:
  • socket level programming.
  • status files.
  • web interfaces.
• Supports SNMPstrings and SNMPintegers.
• Supports tables of SNMPstrings and SNMPintegers.
• Supports generation of SNMP traps.
• Ability to pass requests to another sub mib.
• Sub mib may be on local host or remote.
• Runs on Unix, Linux or Microsoft (XP,2k,98) and requires a Java Virtual Machine 1.3 or greater.

The key to any development for SNMP lays in an understanding of MIB definitions. Data defined in the management information base is held together by a series of identifiers called OID's. These OID's are predefined for many of the features to be found in a typical operating system. For custom details there is the need to acquire a custom OID that relates to your own company and products. This can be an awkward area to deal with. We can provide assistance in the definition of MIB's and gaining company specific OID's.

SNMP Remote Proxy - White Paper

For more information, please download our white paper Simple Network Monitoring - Handling New and Legacy Systems. for more details of how our SNMP-RPD concept can help.

SNMP Remote Proxy Daemon 1.5

The functionality provided by the software includes the ability to respond to SNMP queries using either the SNMP get or get next requests. The software can also be a source of traps, sending alerts to a prespecified management station.

Queries may be answered either directly by the proxy or passed to a sub mib that would be running natively on the host system. In this way the operation of an existing agent may be enhanced without changing the operation of the existing system.

The proxy daemon is an SNMP agent that can cache the status of elements within a MIB. The definition of the MIB cache and how it operates is configured using XML.

Updates can be passed to the proxy daemon in a number of ways.

An update process reads XML status from a source, the source may be a file, a web page or a socket.

Status that is marked as requiring a trap to notify change will generate a trap if a value has changed.

An alternative method exists wherein a socket can be used to indicate to the daemon that a trap generation event has occurred. Status will be read again and if appropriate a trap will be generated.

Custom Monitoring

The ability to quickly add monitoring to a new system is made possible using the proxy daemon. A simple configuration file can define those things being monitored and everything else can be passed on to the underlying native system.

In this way development focuses on supporting features of your application and not in integrating with the underlying systems existing MIB.

Legacy Monitoring

The SNMP-rpd is designed to provide support for legacy systems. If an old application or system does not natively support SNMP then we can provide a way to achieve this. Using either Perl or Java (or any method that can create simple strings and output them to a file) it is possible to measure some parameter and return it as a string or integer in XML for use by the proxy.