Release Features 2.0 to 3.2

 



 

Changes from release 3.1 to 3.2

 

New features added to this release

 

Database support for loading MIBs has been included in this release. Applications can now load MIB files directly from any industry standard RDBMS. The loading of MIB files from database also gives good performance improvement when compared to the loading of the normal MIB file, particularly if the MIB files to be loaded are high in number. Refer Loading MIBs from Database for further details.

 

Support for saving SNMPv3 security parameters information in a database has been added in this release. Applications can now store the security information in the database and use that for accessing the devices. See Saving SNMPv3 User Information for more information.

 

The other new features and enhancements that are added in this release are as follows.

 

Low-Level API (snmp2 package)

    1. Support for broadcast of SNMP messages is added to the SnmpSession class.link to javadocs

    2. A new method getLocalAddress()link to javadocs is added in the TcpProtocolOptionsImpl class.

    3. In SnmpSession class, partialSet()link to javadocs method has been added.

    4. While using applets in SnmpSession class, deQueuing problem that occured has been fixed.

    5. The setSecLevelForTimeSync()link to javadocs method has been added to the SnmpSession class for performing v3 time Sync with security level authPriv or authNoPriv for a authPriv user.

    6. The getSecLevelForTimeSync()link to javadocs method has been added to the SnmpSession class for getting the security level that can be used for performing v3 time Sync for an authPriv user.

    7. A new class TransportUtillink to javadocs has been added to the management package. This contains methods to write the contents to an HTML file. It also contains methods to set the transport home directory.

    8. The following methods are added to the USMUtilslink to javadocs class in the com.adventnet.snmp.snmp2.usm package.

    9. A new method getEngineName()link to javadocs has been added to SnmpEngineEntry. This method can be used to get the engineName in the case of Independent Transport Provider.

MIB Support API (mibs package)

High-Level API (beans and ui package)

    1. Support for broadcast of SNMP messages is provided in SnmpRequestServer.link to javadocs

    2. In SnmpTable, the getIndices()link to javadocs method has been added.

    3. In SnmpTable, the stopPollingTable()link to javadocs method has been added.

    4. In LineGraphBean, the isTimeAvg()link to javadocs method has been added.

    5. Method isEndOfTable() is added to the SnmpTableModel.

    6. Methods setMenuFont(Font menuFont) and getMenuFont()link to javadocs methods have been added to the MibBrowserBean to customize the menu font.

    7. Added method setSecLevelForTimeSync()link to javadocs for doing v3 time Sync with security level of authPriv or authNoPriv for an authPriv user in the SnmpServer class.

    8. Added method getSecLevelForTimeSync()link to javadocs for getting the security level that is used for doing v3 time Sync for an authPriv user.

    9. Constructors added for SnmpTable class for independent protocol provider option and a new SnmpSession with local port.

    10. Methods addMouseListener() and removeMouseListener() have been added to LineGraphBeanlink to javadocs, BarGraphBeanlink to javadocs, and GraphWrapperlink to javadocsclasses.link to javadocs

    11. Methods getShowSeverityColumnColor() and setShowSeverityColumnColor()link to javadocs have been added to TrapBrowser.

    12. In the LineGraphBeanlink to javadocs methods, getLinecolors() and setLinecolors() have been deprecated because it is not fully implemented and methods getLineColors() and setLineColors() have been added.

    13. Methods getMibPath() and setMibPath()link to javadocs have been added to SnmpTrapReceiver.

    14. Constructors added for SnmpPollerlink to javadocs class for independent protocol provider option.

    15. Methods getIgnoreSpecificControlCodes() and setIgnoreSpecificControlCodes()link to javadocs have been added to SnmpTarget bean.

    16. Read Community field of MibBrowser has been changed to text field.

    17. The Mibs loaded previously is stored and updated in the File menu at startup of the MibBrowser application.

    18. In the SnmpTablePanel bean supports SNMP table columns not implemented by the agent.

    19. The SnmpTablePanel bean now displays the number of rows along with the page number.

    20. The following method is added to the SnmpTarget class.
      public void removeV3HandShakeListener(V3HandShakeResultListener l)
      link to javadocs

    21. The following method is added to the SnmpRequestServer class.
      public void removeV3HandShakeListener(V3HandShakeResultListener l)
      link to javadocs

    22. Method getTrapViewer()link to javadocs has been added to the MibBrowser that returns the last TrapViewer instance of MibBrowser.

    23. The following new methods have been added to the SnmpTarget class.link to javadocs
      void setParams(String host,String port,String community,String mib,String oid)
      void setParams(String host,String port,String community,String mib,String[] oidlist)

    24. The following new methods have been added to the SnmpTable class.
      void setTableOIDWoStart(String tableOID)
      link to javadocs
      void setParams(String host,String mib,String tableOID)
      link to javadocs
      void setCellValue(String tableOID,Object aValue, int rowIndex,int columnIndex)
      link to javadocs
      Object getCellValue(String tableOID, int rowIndex, int columnIndex)
      link to javadocs
      String[] getColumn(int columnIndex)
      link to javadocs
      String[] getColumn(String columnName)
      link to javadocs

    25. The method void setParams(String host,String mibs,String tableOID)link to javadocs has been added to the TableBean class.

    26. The following methods have been added to the SnmpTable class.
      getNotAccessibleIndex() - to get the values for the not-accessible indices
      getNotAccessibleIndexColumns() - To get the names of the not-accessible index columns

    27. The method getRow(String tableOID,String index) is added in the SnmpTable bean.

    28. A method to setSettingsTitle(String title) to set the title of MibBrowser Settings Frame has been added in MibBrowser bean.

RMI API (rmi package)

CORBA API (corba package)

    1. Two new methods stringMatrix getNotAccessibleIndex() and stringSeq getNotAccessibleIndexColumns() are added to the corba.idl file.

    2. The methods public String[][] getNotAccessibleIndex() and public String[] getNotAccessibleIndexColumns() are implemented in the com.adventnet.snmp.corba.SnmpTableImpl class.

Bug Fixes Done

 

Low Level API (snmp2 package)

MIB Support API (mibs package)

    1. When a textual convention loop exists in a MIB, StackOverflowError was thrown. Now, this is throws a ParseException.

    2. Bug with getSize(), getMax(), and getMin() methods in LeafSyntax is fixed. Now it returns appropriate value.

High-Level API (beans and ui package)

Changes from release 3.0 to 3.1

 

New Features added to this release

 

The AdventNet SNMP Release 3.1 supports Enterprise Java Beans (EJB) development of network management applications. The SNMP-enabled applications developed using AdventNet SNMP Release 3.1 can be deployed in application servers supporting EJB. This enables building and deploying scalable applications which leverage the load-balancing, fail-over, transactions, scalability of the multi-tier application server architecture that support a large number of users, and other high-end capabilities. Apart from this, the other major new features that are added in this release are as follows.

 

Low Level API (snmp2 package)

 

SNMP Transport Provider Framework

    1. A new protocol-independent transport provider framework has been provided for SNMP communication in which any transport protocol can be plugged in. This essentially means that the user can use AdventNet SNMP over any transport protocol, such as UDP/IP, TCP/IP, Serial link, and so on. This mechanism can also be used by users requiring more security to run SNMP over SSL. UDP/IP is the default protocol implementation with a reference implementation for TCP/IP also provided.

    2. The following interfaces are added for the SnmpTransport provider framework. Users wanting to use their own protocols for transport communication should implement these interfaces.

    1. A new class SnmpTransportPacket link to javadocs has been included which consists of the details of the parameters that are needed for the transport communication and the details of the message data that is to be sent or received.

    2. The following are the new TCP reference implementation classes which have been added to the snmp2 package.

Others

    1. Support for GNU compiler for Java or the GCJ compiler is included for the low-level API.

    2. Support to re-authenticate a received SNMPv3 Trap is included.

    3. A new class SnmpBits link to javadocs has been included in the snmp2 package. This class can be used to create and set values for variables with syntax BITS.

MIB Support API (mibs package)

SAS API (sas package)

 

Protocol-independent communication framework for SAS communication

    1. A new protocol-independent communication framework is provided in which any transport protocol can be plugged in for SAS communication. The following interfaces are added. Users wishing to use any protocol provider must implement these interfaces.

    2. TCP is provided as the default protocol implementation with implementation for HTTP.

    3. Now applications can also use SAS to communicate with the server. They can use the com.adventnet.snmp.snmp2.SASAppletStub link to javadocs API.

High level API (beans and ui package)

Bug Fixes Done

 

Low-Level API (snmp2 package)

    1. The SNMPv3 message uses the value of engineID in the contextID field if the contextID parameter is not explicitly specified.

    2. In case of agent side implementations, the agent responds to a request only when the secLevel is less than the secLevel configured for that user.

    3. A null pointer exception thrown in case of wrong DNS configuration has been fixed in the SnmpSession class.

    4. In ASN1Parser, decodeOID() method now decodes OIDs starting with values other than .1.3.

MIB Support API (mibs package.)

SAS API (sas package)

    1. SAServer throws a NullPointerException if creation of custom class instance fails. This has been fixed.

High-Level API (beans and ui package)/p>

Changes from release 2.2 to 3.0

 

The mibs package uses new MibParser which offers better performance. The key enhancement is the option of loading MIB files as compiled MIB files. The loading of compiled MIB files gives good performance improvement when compared to the loading of the normal MIB file.

 

This release of AdventNet SNMPv3 API provides an elegant way of implementing the security and access controls. It includes the new security and access frameworks through which users can implement their own message-level security and access control. Users can define and implement their own security model and the access control model. The AdventNet SNMPv3 security classes provide a default implementation and registration of the User-based Security Model (USM) and the View-based Access Control Model (VACM) based on these frameworks.

 

Support for HTTP access is provided in this release. Therefore, the applets now have the choice of selecting the protocol. By default, the applet uses SAS for communication. If the protocol is set to HTTP, then the communication is through the servlet loaded in the web server.

 

Patch Manager, a utility for managing the patches is provided in this release.

 

New Features added to this release

 

Low-Level API (snmp2 package)

    1. This release includes a new security and access framework through which users can define and implement their own security model and the access control model.

    2. Support for debug link to javadocslevel in low-level API.

    3. Support for logging debug statements link to javadocs to file in low-level API.

    4. hashCode link to javadocs and equalslink to javadocs method are provided for SnmpOID link to javadocs class.

    5. In the 2.2 release support for SnmpGrouplink to javadocs, counters were provided only for those defined in RFC1213-MIB. In the 3.0 release, the additional SnmpGroup counters defined in RFC1907 are supported.

    6. The method isAuthenticationFailed()link to javadocs has been added to Snmp3Messagelink to javadocs class which returns the success or failure result of the Snmpv3 authentication module that checks the digest and timeliness.

    7. Support is provided to make SnmpEngineBoots, SnmpAPI persistent. This is useful for an agent side implementation. The following methods are provided in the SnmpAPI.
      public void setEngineBootsSerializeFileName(String name)link to javadocs

      public String GetEngineBootsSerializeFileName()link to javadocs

      public boolean serializeEngineBoots()link to javadocs

      public boolean deSerializeEngineBoots()link to javadocs

    8. The method getVersionString()link to javadocs has been added to SnmpAPI to get the release version of the SNMP library.

    9. The method getSnmpClients()link to javadocs has been added to SnmpSession which returns the clients that have registered for callbacks.

    10. Added support for sending/disable sending automatic response to the received inform request through two public API methods in SnmpSession namely, setAutoInformResponse(boolean flag)link to javadocs and isSetAutoInformResponse()link to javadocs.

MIBs Package

    1. Performance improvement in the MibParser is achieved by providing the option of loading MIB files as the compiled MIB files.

    2. The MibParser now supports loading of Multiple Mib Modules from the same MIB file.

    3. Cyclic imports are supported by the MibParser.

    4. Forward reference of MibNode is supported in the current MibParser.

    5. Multiple rootslink to javadocs are supported with the current parser (cross iso ccitt mibs).

    6. Support for dateAndTime TC is provided in mibs package.

High-Level API (beans and ui packages)

MibBrowser Application

    1. The Find option is added in the MibBrowser application to search a MIB node from the MibTree.

    2. SNMPDecoder utility for decoding v1 and v2c PDU HEX dumps is provided in the Debug window of the MibBrowser.

    3. Logging feature is provided, which can log MibBrowser result display, Debug messages and SNMPDecoder messages.

    4. The Print option is provided to print the SNMP operations results, debug messages, and SNMP Decoder messages.

    5. TrapParserCustomizer is added to the MibBrowser to edit the trap parser file.

    6. Delete option is provided to delete the trap messages from the TrapBrowser.

    7. TrapBrowser bean's status is shown with a LED panel and status panel.

Applet Support API

Bug fixes done

 

Low-Level API (snmp2 package)

    1. For SNMPv3 manager applications, some of the report PDUs are not generated. This bug has been fixed.

    2. For agent side implementations, if the value of requestID/messageID in the request message is zero, the agent generates the response message with a non-zero requestID/messageID value. Therefore, the manager drops the response message. This has been fixed.

    3. SnmpSession gives a null pointer exception if an Snmp Entity returns a PDU with an ASN.1 serialization error. This has been fixed.

    4. The Snmp callback client is not called in case of timeout. This has been fixed.

    5. Bugs in the snmpv3trap and snmpv3trapd examples, which are available in the snmpapps and mibapps directories, have been fixed.

    6. SnmpCounter64 data type is implemented using long data type to handle up to 2^63-1. Now, it can handle up to 2^64 by using java.math.BigInteger data type.

    7. Bug in encoding and decoding SnmpCounter64 data has been fixed.

    8. When setRemoteHost() method in the SnmpPDU class is invoked second time on an already constructed PDU, the remote host is still set to the first remote host and the PDU was sent again to the first host. This has been fixed.

    9. The getIncrement() method in the SnmpCounter64 returns proper difference (including counter rollover).

    10. Bug in re-using the PDU is fixed.

    11. If the received SNMP packet resulted in an ASN.1 error or decryption error (in case of SNMPv3), subsequent packets received may not have the correct data. This bug has been fixed.

    12. SNMP_ERR_NOSUCHNAME and NOSUCHOBJECTEXP are mapped to the same error string "There is no such variable name in this MIB". Now, NOSUCHOBJECTEXP is mapped to "There is no such object in this MIB."

    13. While using privacy features, the decryption module was using PKCS#5 padding scheme. Now, it has been modified so that padding is ignored.

MIBs Package

High-Level API (beans and ui package)

    1. Methods setObjectID() and SetSnmpOID() of SnmpTarget bean do not update the OID list properly. If an array of OIDs are set using setObjectIDList() or setSnmpOIDList() method and an OID is set using setObjectID() or setSnmpOID() method, only the first element of the oidList is replaced instead of removing all other OIDs from the OID list. This bug has been fixed.

    2. Using SnmpTarget bean for multiple polling sessions or prolonged polling leads to out of memory error. This bug has been fixed.

    3. The traps received by the trap parser bean are delayed due to DNS lookup issues. This bug has been fixed.

    4. In the SnmpTarget bean, if a v2c GetResponse PDU is received with a noSuchObject or noSuchInstance error values, SNMP error was being returned instead of returning the response PDU with partial results. This bug has been fixed.

    5. In SnmpRequestServer bean, the request ID is added to a list to identify the response PDU. If an early response is received before adding the request to the request list, the response is dropped. When a response arrives, it checks for the request ID and waits for 100 milliseconds. If it is not available again, it checks for the request ID causing a delay when multiple SnmpRequestServer instances are used. This bug has been fixed.

    6. UI problems in the Trap Details screen of the TrapBrowser bean have been fixed.

    7. Bug in the handling the nonprintable characters in the trap message of TrapBrowser bean has been fixed.

    8. TrapParserBean used to create a default parser file if the file was not available sometimes causing problem. Now, the default file is not created and the user has to set the file properly. Otherwise an error message is displayed and all traps are accepted.

    9. The poll interval value is not set properly if the restart button was clicked in BarGraph and LineGraph bean of MibBrowser. It has been fixed.

    10. Error messages are not displayed if the graphs are plotted for columns with non-numeric values. This has been fixed.

    11. Exception is thrown while changing the table OID in the tableSettingsDemo example present in uiapplications directory. It has been fixed.

    12. The Bar Chart gives a NumberFormatException for large values involving the exponent sign "E". This has been fixed now.

    13. SnmpTrapReceiver does not release resources unless cleanup() method was invoked from an application. The cleanup() may also release shared resources. This has been fixed and made deprecated. An alternative method stop() is provided to stop receiving traps. An application should remove all the TrapListeners registered with an SnmpTrapListener to release the resources, which are no longer used, by garbage collector.

    14. SnmpRequestServer resources are never garbage collected when no RequestListeners is registered and removed. This bug has been fixed.

    15. In the TrapEvent.getAgentAddress() method, there is a delay involved when a DNS look-up is performed. This has been fixed.

    16. Creating multiple instances of Java bean components (SnmpTarget, SnmpRequestServer, etc.) and using multi-threading had problem with reusing the low-level resources. It is fixed by synchronizing the creation of the low-level resources.

    17. Invalid OID format error occurs when the value of the table is set from the combo box. This has been fixed.

Applet Support API (sas package)

Changes from release 2.1 to 2.2

 

Features added in this release

Bug Fixes done

    1. While running applications with the SnmpAPI debug mode active, there is a possibility of delay due to DNS calls. This has been fixed.

    2. SAServer should not create a socket on the system assigned port if the specified local port is less than zero. This bug has been fixed.

    3. Bug with the modify routine in USMUserTable has been fixed.

    4. Bug in storing IMPLIED index names has been fixed.

    5. Bugs while setting foreGround color, backGround color, font, and size of LineGraphBean have been fixed.

    6. Bug in the example sendv2trap in applications directory has been fixed.

    7. Bugs in the node list while loading some of the MIB files have been fixed.

    8. The method setRequestID(int) in RequestEvent does not work. It has been fixed now.

    9. The SnmpTrapReceiver bean throws NullPointerException when MIB is loaded without setting the port. This has been fixed.

    10. The method getSelectedMibNode() in MibTree returns null. It has been fixed.

    11. Exception is thrown while parsing the access value of not-implemented in AGENT-CAPABILITIES. This has been fixed

    12. If the Augmented node is present in the current module, the index is not set properly. It has been fixed.

    13. If non SNMP messages are received, decode failure occurs and the null PDU is returned. It is added to the response list and NullPointerException is thrown while checking the reqid for the next request. This has been fixed.

    14. AdventNet SNMPv3 API supported only the standard discovery process. Now, the implementation is modified so that if the msgAuthoritativeEngineID field is of zero-length, regardless of the other security parameters, the API returns a report PDU containing the authoritative snmpEngineID.

    15. An encrypted timeSync message is sent for the user who had a securityLevel of authPriv. Now the timeSync Message is sent with a securityLevel of authNoPriv.

    16. AdventNet SNMPv3 drops the PDU if the authentication fails. This has been fixed so that the registered callBack method receives the PDU.

Migration to 2.2

 

The API compared to the earlier releases. The API users hae tov make some changes to their applications so that the existing code compiles with AdventNetSnmpv3 2.2 API. This document guides the API user on the changes to be made to upgrade to the 2.2 release.

 

Changes in the snmp2 package

  1. In the 2.1 release and earlier, the SnmpEngineTable class provided methods which could be used to retrieve the respective SnmpEngineEntry objects for a particular agent host and port as well as add entries to the table. These methods were static. Now they are made non-static. Similarly, the USMUserTable class in the 2.1 release and earlier had methods which could be used to retrieve the respective USMUserEntry objects. The methods in this class which were static are now non-static. The SnmpAPI instantiates these two classes in its constructor and has a reference to them. Methods are provided in the SnmpAPI to retrieve these classes. These methods are getSnmpEngine() to retrieve the SnmpEngineTable reference and getUSMTable() to retrieve the USMUserTable reference. There is no need for the API user to separately instantiate these classes. Therefore, the API user writes the code similar to the following.

SnmpAPI api = new SnmpAPI();
.
.
SnmpSession session = new SnmpSession(api);
.
.
SnmpEngineTable engineTable  =  session.API.getSnmpEngine();
SnmpEngineEntry engineEntry  =  engineTable.getEntry(host, port);
.
.
.
USMUserEntry userEntry = new USMUserEntry(userName.getBytes(), engineEntry.getEngineID());
.
.
.
USMUserTable USMTable = session.API.getUSMTable();

USMTable.addEntry(userEntry);

 

The API user need not instantiate these classes. Instead, the instance of these classes provided in the SnmpAPI should be operated.

 

Moreover, the method init_v3_params in USMUtils class is a comprehensive initialization routine to perform discovery and time synchronization. When this method is used, the user need not create/maintain the Engine and USM tables. If this method is already been used (this method was is present in the 2.1 release and earlier), the existing applications works with the 2.2 release. Therefere, no changes are required. The snmpget.java in low_level_api_examples/snmpapps provides a good source of example to understand the changes.

  1. In the release 2.1 and earlier, the get and set methods for SnmpEngineID, SnmpEngineBoots, SnmpEngineTime, and TimeWindow were static. These methods are now non-static and the API user needs to perform get and set on the SnmpAPI instance.

  2. In the release 2.1 and earlier, the Snmp3Message had a method setMsgFlags. The msgFlags field of the PDU is calculated internally based on the securityLevel while encoding and therefore the setMsgFlags method is removed in release 2.2.

  3. In the release 2.1 and earlier, the SnmpEngineTable had methods which were static. These are non-static now. Moreover, the constructor is no longer public and there is no need to instantiate this class. SnmpAPI instantiates this class in its constructor and provides methods to retrieve this SnmpEngineTable reference.

  4. In the USMUserEntry, public access to setEngineID, setUserName, and setSecurityName is removed. In earlier versions of AdventNet SNMPv3, while using the lowlevel API, the userName on USMUserEntry reference needs to be set in theSnmp3Message with the following code.

((Snmp3Message)(pdu.getMsg())).getSecurity().setUserName(userName.getBytes());
or
((Snmp3Message)(pdu.getMsg())).getSecurity().setSecurityName(userName.getBytes());

 

This can no longer be used as public and now the user needs to set the userName on the SnmpPDU. Therefore, the following code can be used instead.

 

pdu.setUserName(userName.getBytes())

Refer the examples present in the low_level_api_examples/snmpapps directory for more details. Also the methods get/set KeyStatus and get/set Status are removed from the API.

  1. In the release 2.1 and earlier, the USMUserTable had methods which were static. These are non-static now. Moreover, the constructor is no longer public and there is no need to instantiate this class. The SnmpAPI instantiates this class in its constructor and provides methods to retrieve this USMUserTable reference.

  2. In USMUtils, the method auth_password_to_key is renamed as password_to_key. The methods signPdu and checkDigest are no longer public.

Changes from release 2.0.1 to 2.1

 

Features added in this release

    1. Support for swing1.0 has been removed.

    2. SnmpTrapReceiver has been modified to work with the SNMP Applet Server.

    3. A new method decodeDefval has been incorporated in the MibNode. It returns the SnmpVar corresponding to the defval for the node.

    4. Option for unloading mibs is provided. The method unloadMibModule has been added to MibOperations.

    5. The loadMibs method in all the beans has been modified to load only a single MIB at a time.

    6. The addLabel() method in MibOperations to add label which need not be treated as reserved word. Therefore, in case if a particular reserved word in MIBs is used in a different manner, the conflict can be resolved using this method.

    7. Support for OIDs of the form ModuleName.NodeName has been included.

    8. APIs are provided to make USMUserTable and SnmpEngineTable persistent. The User and Engine Tables are serialized into the files UserEntry.ser and EngineEntry.ser.

    9. A beta version of TrapBrowser and TrapParser bean are provided.

    10. The SnmpTablePanel has the following features added.

    11. The jars have been renamed. AdvSnmpAllBeans.jar is now called AdventNetSnmp.jar, AdvSnmp.jar is called AdventNetSnmpLLAPI.jar, and AdvSnmpBeans.jar is now AdventNetSnmpHLAPI.jar.

    12. More number of MIBs have been packaged in this release. They are present in the mibs directory.

Bug Fixes done

    1. The packet size restriction has been removed in this release.

    2. Memory issues have been fixed with the beans. The poller and requestserver resources do not get de-allocated because of the underlying thread-based resources. his has been resolved by inserting checks for listeners and explicit release of resources when all listeners are removed.

    3. Call to MibOperations.createVariableBinding() with some of the mnemonics returned wrong VarBind value. This has been fixed.

    4. The OID should translated from .iso as far as loaded MIBs allow. This has been is fixed.

    5. Exception while parsing AGENT-CAPABILITIES macro has been fixed.

    6. The SnmpIpAddress.toString() routine gives a StringIndexOutOfBoundsException in case of UnKnownHost. It has been fixed and null is returned.

    7. ArrayIndexOutOfBoundsException is thrown while using MibOperations.getSnmpOID(). This has been fixed now.

    8. Bug in MODULE-COMPLIANCE in storing the value of OBJECT clause. This has been fixed.

Changes from release 2.0 to 2.0.1

  1. A separate AdvSnmpAllBeans.jar has been provided for working with swing1.1. This is located in AdventNetSNMP v3 /classes/swing1.1 directory.

  2. The PropertySettings bean has been added. This is a GUI component, which allows easy entry and modification of PDU settings.

  3. SnmpTrapReceiver has been modified to listen for traps only when the trap port property for the bean has been set.

  4. SnmpSession now includes methods to enable trap authentication for SNMPv3. The default setting accepts all v3 traps even if an authentication failure occurs.

  5. Bug in large table, which throws ArrayIndexOutOfBounds exception under specific conditions, has been fixed.

  6. LineGraph can be viewed for selected table columns in SnmpTablePanel bean.

  7. SnmpTarget has been updated to send notifications.

  8. There is a change in SnmpTarget related to traps. If the target SNMP version is v2c or v3, the v1 trap parameters passed on invoking snmpSendTrap are converted to v2 notification parameters.

  9. SnmpPDU has been modified to disallow sending a v1 trap PDU when the SNMP version for the PDU is v2c or v3. Sending a v2 version PDU with command type of v1 trap (TRP_REQ_MSG) is not a valid behavior and is no longer permitted.

 



Copyright © 1996-2006, AdventNet Inc. All Rights Reserved.