Projects tagged ‘java’ and ‘snmp’

Centreon is a network, system, applicative supervision and monitoring tool, it is based upon the most effective Open Source monitoring engine: Nagios. Centreon provides a new frontend and new ... [More] functionalities to Nagios. It allows you to be more efficient in your network monitoring, but also allows you to make your supervision information readable by a largest range of users. Indeed, a non technical user can now use the Centreon/Nagios couple to easily understand your network infrastructure thanks to charts and graphical representations of the gathered information. Skilled users still have access to specific and technical information collected by Nagios though. [Less]

OpenNMS is the world's first enterprise grade network management platform developed under the open source model. It consists of a community supported open-source project as well as a commercial services, training and support organization.

joeSNMP is an open-source Java SNMP class library.

BlackRay is a relational database system designed to offer performance features commonly associated with search engines. It offers SQL support and sophisticated operational and management features. ... [More] Load-balancing and operational stability by means of N+1 redundance are included. BlackRay is called a "Data Engine" since it combines traditional, relational database features and SQL with the power and flexibility of search engines. It is a true hybrid, offering transaction support, data-versioned snapshots, and sophisticated function-based indices. Wildcards, phonetic, and fuzzy logic searches are supported, as well. Commercial support is available, and the project is released under a the GPLv2 license. [Less]

VLMa is a Java application which provides a daemon and a web interface to manage several VLC streamers. It has some nice features like: - dynamic stream assignments (incl. fallback if a server is ... [More] unavailable) - drawing of the servers stats as RRD graphs - and more... It is designed to be used in large networks such as universities or corporate networks. [Less]

IxoraRMS is an open source monitoring tool with great visualization and customization capabilities. It is well suited for use in performance labs.

An appender to send formatted logging event strings to a specified managment host (typically, a MLM of some sort, but could also be an SNMP management console) in the form of an SNMP trap. This ... [More] appender does not attempt to provide full access to the SNMP API. In particular, use of this appender does not make an SNMP agent out of the calling application. You cannot use this appender as an interface to do SNMP GET or SET calls -- all it does is pass on your logging event as a TRAP. This appender uses a helper class which serves as the interface to the SNMP sub-system. This class must implement the SnmpTrapSenderFacade interface. The concrete implementation class you want to use must be specified in your properties file -- see the examples below. The implementation class must provide a parameterless constructor -- this is the constructor that Log4J will use to instantiate the class using the class name in the properties file. There are three implementation classes provided with this appender; the JoeSNMPTrapSender, the WengsoftSNMPTrapSender and the NetSnmpCommandLineTrapSender classes. If you fail to specify an implementation in your properties file, or if there is a problem finding, loading or instantiating the implementation that you do specify, the appender will fall back to using the JoeSNMPTrapSender implementation as a default. You can and should, as your needs dictate, write your own implementation of SnmpTrapSenderFacade, using the underlying SNMP library of your choice. In this case, the implementations provided with the appender should serve as adequate examples for how this might be done. Here's a sample of what you would need in an XML configuration file to configure this appender: To configure an otherwise identical appender that uses a different implementation class, you would simply change the value of the "ImplementationClassName", as in the following example: To configure the appender to use a delimited conversion pattern, to allow multiple VarBinds, you would drop the parameter from the configuration, and change the Layout class to SnmpDelimitedConversionPatternLayout. You would then need to set the appropriate parameters of the Layout class. See SnmpDelimitedConversionPatternLayout for an explanation of using multiple VarBinds. Here's a sample of what you would need in a properties configuration file to configure this appender: log4j.appender.TRAP_LOG=org.apache.log4j.ext.SNMPTrapAppender log4j.appender.TRAP_LOG.ImplementationClassName=org.apache.log4j.ext.JoeSNMPTrapSender log4j.appender.TRAP_LOG.ManagementHost=127.0.0.1 log4j.appender.TRAP_LOG.ManagementHostTrapListenPort=162 log4j.appender.TRAP_LOG.EnterpriseOID=1.3.6.1.4.1.24.0 log4j.appender.TRAP_LOG.LocalIPAddress=127.0.0.1 log4j.appender.TRAP_LOG.LocalTrapSendPort=161 log4j.appender.TRAP_LOG.GenericTrapType=6 log4j.appender.TRAP_LOG.SpecificTrapType=12345678 log4j.appender.TRAP_LOG.ApplicationTrapOID=1.3.6.1.4.1.24.12.10.22.64 log4j.appender.TRAP_LOG.CommunityString=public log4j.appender.TRAP_LOG.ForwardStackTraceWithTrap=true log4j.appender.TRAP_LOG.Threshold=DEBUG log4j.appender.TRAP_LOG.layout=org.apache.log4j.PatternLayout log4j.appender.TRAP_LOG.layout.ConversionPattern=%d,%p,[%t],[%c],%m%n Here's an example using the properties file format the uses the delimited conversion pattern technique to allow multiple VarBinds: log4j.appender.TRAP_LOG=org.apache.log4j.ext.SNMPTrapAppender log4j.appender.TRAP_LOG.ImplementationClassName=org.apache.log4j.ext.JoeSNMPTrapSender log4j.appender.TRAP_LOG.ManagementHost=127.0.0.1 log4j.appender.TRAP_LOG.ManagementHostTrapListenPort=162 log4j.appender.TRAP_LOG.EnterpriseOID=1.3.6.1.4.1.24.0 log4j.appender.TRAP_LOG.LocalIPAddress=127.0.0.1 log4j.appender.TRAP_LOG.LocalTrapSendPort=161 log4j.appender.TRAP_LOG.GenericTrapType=6 log4j.appender.TRAP_LOG.SpecificTrapType=12345678 log4j.appender.TRAP_LOG.CommunityString=public log4j.appender.TRAP_LOG.ForwardStackTraceWithTrap=true log4j.appender.TRAP_LOG.Threshold=DEBUG log4j.appender.TRAP_LOG.layout=org.apache.log4j.ext.SnmpDelimitedConversionPatternLayout log4j.appender.TRAP_LOG.layout.ValuePairDelim=/ log4j.appender.TRAP_LOG.layout.VarDelim=; log4j.appender.TRAP_LOG.layout.ConversionPattern= %p;1.3.6.1.4.1.24.100.1/%m;1.3.6.1.4.1.24.100.2/%C{1};1.3.6.1.4.1.24.100.3 This software is based on the log4j software provided by the Apache Jakrta log4j project. This software is released under a version of the Apache license version 1.1 -- please see the LICENSE.TXT file included with this distribution for details. Version 1.2.9.1 2001-09-29 changes --- 2001-10-03: mwm : made changes needed to support v.1.1.1 of the SNMPTrapSenderFacade 2002-09-02: mwm : changed to be compatible with Log4J v. 1.2.x 2002-10-03: mwm : Made changes, mainly in #append, to deal with the new SnmpTrapSenderFacade interface architecture. 2002-10-15: mwm: Included the SysUpTimeResolver contributed by Thomas Muller. 2002-10-15: mwm : changed the sysUpTime value to a long, to cope with the SysUpTimeResolver mechanism. 2002-12-10: mwm : minor tweaks and prettying up of code. 2003-03-21: mwm : incorporated the first cut of Matt Monks's code to use a delimited conversion pattern string to allow mutliple VarBinds to be attached to the trap PDU. 2003-03-22: mwm : after reading Ceki's fine new book on Log4J, made several changes (for example, to the implementation of #close) to correct deficiencies in this class as an implementation of AppenderSkeleton. Also improved/added handling of the stack trace of the Throwable associated with the LoggingEvent, again inspired by Ceki's example in the new book. 2003-03-23: mwm : building on Matt Monks's ideas, added the SnmpDelimitedConversionPatternLayout, and used it to refactor the handling of the delimited conversion pattern case. 2003-05-24: mwm : minor changes to accomodate the change in the SnmpTrapSenderFacade interface, and added two new properties. 2003-07-05: mwm : some improvement in the exception handling of #loadImplementationClass Author: Mark Masterson (m.masterson@computer.org), Thomas Muller (ttm@online.no), Matt Monks (Matthew.Monks@netdecisions.com) [Less]

JaXAs is a command-pattern framework used as middleware in many projects at SoftMethod.

The software parses text file MIBs(scalars and tables) into Java MIB objects for SNMP network communication, these MIB objects are markable for query/persist optimization, only marked fields are ... [More] applicable for operations. A session based persist manager is reponsible for converting MIB objects into SNMP operations sent to the network element. Traps from the network elements are also in Java objects form. [Less]

更新情報0.3.0betaをリリースしました。MIB検索機能が強化されています。ただし、制限事項としてSNMP電文の送受信はできません。0.3.0正式リリースでは ... [More] SNMP電文の送受信も可能にします。 次期バージョンのベータ版ダウンロードはここからお願いします： http://mibible.googlecode.com/files/mibible-0.3.0beta.zip 最新正式版ダウンロードはここからお願いします： http://mibible.googlecode.com/files/mibible-0.2.0.zip 年内には、0.3.0正式版をリリースしたいな… 概要このプロジェクトではSNMPに関するツール群を開発していきます。基本的には、「SNMPに関して、あると助かるツール群を提供する」をコンセプトとして開発していきたいと考えています。 mibbleを中心に据えているため、現在はGPLライセンスとなっていますが、将来の目標としてはApache Licenseのような自由さのあるライセンスにしたいと考えています。 このツールの具体的な利用方法については、http://code.google.com/p/mibible/w/listを参照してください。 mibible browser(ver0.3.0beta)の画面イメージ mibible printer(ver0.2.0)の実行例 > mibprinter "%type:%Num %text" ..\mib\ietf\IF-MIB OBJECT IDENTIFIER:1 iso OBJECT IDENTIFIER:1.3 org OBJECT IDENTIFIER:1.3.6 dod OBJECT IDENTIFIER:1.3.6.1 internet OBJECT IDENTIFIER:1.3.6.1.1 directory OBJECT IDENTIFIER:1.3.6.1.2 mgmt OBJECT IDENTIFIER:1.3.6.1.2.1 mib-2 (中略) OBJECT-TYPE:1.3.6.1.2.1.2.2.1 ifEntry OBJECT-TYPE:1.3.6.1.2.1.2.2.1.1 ifIndex OBJECT-TYPE:1.3.6.1.2.1.2.2.1.2 ifDescr OBJECT-TYPE:1.3.6.1.2.1.2.2.1.3 ifType OBJECT-TYPE:1.3.6.1.2.1.2.2.1.4 ifMtu OBJECT-TYPE:1.3.6.1.2.1.2.2.1.5 ifSpeed OBJECT-TYPE:1.3.6.1.2.1.2.2.1.6 ifPhysAddress OBJECT-TYPE:1.3.6.1.2.1.2.2.1.7 ifAdminStatus OBJECT-TYPE:1.3.6.1.2.1.2.2.1.8 ifOperStatus (中略) NOTIFICATION-TYPE:1.3.6.1.6.3.1.1.5.3 linkDown NOTIFICATION-TYPE:1.3.6.1.6.3.1.1.5.4 linkUp (後略)名前の由来名前の由来は「mib + bible」です。SNMPの世界で聖書のように多くの方々に利用されるプロダクトを目指した、大それた名前です^^;　また、mibbleをリスペクトしつつも、ユーザや開発者に対する愛(i)を中心に据えたい、との想いもあります。「ミバイブル」ではなく、ネイティブっぽく「ミバイボ」と発音してください。 目標以下のようなものを開発していきたいと考えています(2008年10月現在)。 変わる可能性は大いにあります。 素敵なMIBブラウザ(mibible browser) 素敵なMIB加工ツール(mibible printer) 素敵なSNMP Agent net-snmpのようなコマンド群 メンバ募集中このプロダクトを一緒に成長させて頂けるメンバを募集中です。実際にソースを書くだけでなく、動作させて貴重な意見を頂けたり、ドキュメントを書いて頂けたり、HPをメンテナンスして頂けたり、その人なりの様々な関わり方ができると考えています。 mibbleがJavaであるため基本的にはJavaで開発しています。その他言語を利用したい場合はご相談ください。Javaに固執するつもりはありませんが、様々な環境に配布しやすいプロダクトにしたいと考えています。 ご興味がある方はまでご連絡ください。また、Googleグループのmibibleページもありますので、必要に応じて利用しようと考えています。 バグや要望の提出先バグや要望については、是非までご連絡をお願いします。 沿革 2008/10/18 mibibleプロジェクト発足。メンバ1名(tknstyk) 2008/10/20 mibible-0.1.0 リリース(mibible browserリリース) 2008/10/22 メンバ新規加入(bluemoonredsky) 2008/10/23 メンバ新規加入(markon.0827) 2008/10/23 mibible-0.1.1 暫定リリース 2008/10/25 mibible-0.2.0 リリース(mibible printerリリース) 2008/11/25 mibible-0.3.0beta リリース [Less]