Network Management
SNMP Simulation
Script reference
Try NetDecision
Buy now
About NetMechanica
Our customers
  • Register
  • Edit account
  • Forgot password?
  • Home / Archive / NetDecision 4.9 (codename: Universe) has been released print version
    NetDecision 4.9 (codename: Universe) has been released

    NetDecision 4.9 Release Notes


    • The comparator now properly handles both raw SNMP INTEGER values and MIB-resolved values (defined as enumeration). Example: for enumeration like INTEGER {up(1), down(2), testing(3)} it is possible to specify ‘up’ or just ‘1’ in trap handling configuration (comparators).
    • The values surrounded with single quotes are now properly handled by database trap handler.

    MIB Manager

    • The OBJECT-GROUP definition is now supported.
    • The NOTIFICATION-GROUP definition is now supported.
    • The MODULE-IDENTIFY definition is now properly handled.

    Network Manager

    There are three new additional parameters in SNMP trap handler:

    • Severity – the severity assigned.
    • EventDescription – the event description assigned
    • AlertElementName – the name of the network element in alert state

    The user is able to reference these new parameters using templates: [SEVERITY], [EVENT_DESCRIPTION], [ELEMENT_NAME] and {severity}, {event_description}, {element_name} for web service handler.

    Traffic Grapher

    • The path to a folder which contains RRD (Round Robin Database) files is now customizable. It is now possible to use shared folder as RRD files storage for cluster configuration.
    • For user convenience “Clone Monitor” functionality has been implemented. With the NetDecision Traffic Grapher Monitor cloning feature the user is able to get an exact duplicate of an existing monitor configuration (all monitor settings copied to a second like device monitor configuration). This feature helps save the time usually spent to set up all the settings manually.
    • There are two new additional parameters in value handler:
      • AbsoluteValue – the actual value retrieved from monitored network element.
      • VolumeValue – the volume type of value (for example: the amount of traffic in bytes) calculated on specified time interval

      The user is able to reference these new parameters using templates: [HANDLER_ABS_VALUE], [HANDLER_VOL_VALUE] and {abs_value}, {vol_value} for web service handler.

    SNMP Agent Simulator

    • SNMP tables with no columns defined are now properly handled

    Script Language

    • New plugin has been implemented to work with IBM WebSphere message queues. IBM WebSphere MQ is a family of network software products launched by IBM in March 1992. It was previously known as MQSeries, a trademark that IBM rebranded in 2002 to join the suite of WebSphere products. WebSphere MQ, which is often referred to simply as "MQ" by users, is IBM's Message Oriented Middleware offering. It allows independent and potentially non-concurrent applications on a distributed system to communicate with each other. MQ is available on a large number of platforms (both IBM and non-IBM), including z/OS (mainframe), OS/400 (IBM System i or AS/400), Transaction Processing Facility, UNIX (AIX, HP-UX, Solaris), HP NonStop, OpenVMS, Linux, OS 2200, and Microsoft Windows. WebSphere MQ is often referred to as "MQ" or "MQ Series". There are two parts to message queue (hence "MQ"):
      • Messages are collections of binary or character (for instance ASCII or EBCDIC) data that have some meaning to a participating program. As in other communications protocols, storage, routing, and delivery information is added to the message before transmission and stripped from the message prior to delivery to the receiving application.
      • Message queues are objects that store messages in an application.

      A queue Manager is a Websphere MQ prerequisite and system service that provides a logical container for the message queue and is responsible for transferring data to other queue managers via message channels. There are several advantages to this technology:

      • Messages do not depend on pure packet-based transmissions, such as TCP/IP. This allows the sending and receiving ends to be decoupled and potentially operate asynchronously.
      • Messages will be delivered once and once only, irrespective of errors and network problems.

      NetDecision acts as so called WebSphere MQ Client. A WebSphere MQ client is part of the product that can be installed on its own, on a separate machine from the base product and server. It can interact, by means of a communications protocol, with one or more WebSphere MQ servers and connect to their queue managers. IMPORTANT: The WebSphere MQ Client package is not a part of NetDecision installation package. The WebSphere MQ Client must be downloaded from IBM website, installed and configured on NetDecision host machine. To start using MQ, you must first connect to Queue Manager by using WMQConnect() function. At the end of your script the Queue Manager connection must be closed by using WMQDisconnect() function.

      • WMQConnect - Connects to a message queuing queue manager.
      • WMQDisconnect - Disconnects from a message queuing queue manager.
      • WMQOpenQueue - Opens a message queue. This function permits an application to read messages from, and write messages to, a queue.
      • WMQCloseQueue - Closes a message queue.
      • WMQPutMessage - Puts a message on a queue that was opened for output.
      • WMQGetMessages - Gets a message from a queue that was opened for input.
      • WMQGetManagerStatus - The WMQ error handling related to a message queuing queue manager.
      • WMQGetQueueStatus - The WMQ error handling related to actual queues.
      • WMQSetOptions - Sets options used for reading messages from queue using WMQGetMessages() call.
    • New functions have been added to work with USB HID (Human Interface Device) devices. Universal Serial Bus (USB) is an industry standard developed in the mid-1990s that defines the cables, connectors and communications protocols used in a bus for connection, communication and power supply between computers and electronic devices In computing, the USB human interface device class (USB HID class) is a part of the USB specification for computer peripherals: it specifies a device class (a type of computer hardware) for human interface devices such as keyboards, mice, game controllers and alphanumeric display devices. NetDecision script functions allow the user to manage USB HID connection to a compliant device, read data from ports and send data or commands (including USB HID reports).

      • USBEnumerateDevices - Enumerates USB HID devices
      • USBOpen - Opens USB HID device
      • USBClose - Closes a USB HID connection previously opened by USBOpen function.
      • USBReadData - Reads incoming data from a USB HID connection.
      • USBWriteData - Sends data via USB HID connection
      • USBWriteFeatureReport - Sends out USB HID Feature report
      • USBReadFeatureReport - Reads Feature report from USB HID device
      • USBGetFeatureReportLength - Retrieves the length of Feature Report in bytes (checks HID capabilities)

    Reporting Issues

    Found a bug? Please submit a bug to the NetDecision bug database.


    Developed by WebMechanica Copyright © 2001-2016 NetMechanica e-mail