1.51. Release Notes 0.94

1.51.1. New features and improvements in this release

  • added support for discovery and monitoring of protocol counters. Currently monitoring ospfSpfRuns (“Counter of intra-area route table calculations”) and bgpPeerInUpdates (“Number of BGP UPDATE messages received on this connection”). These counters are converted to rate and stored as monitoring variables ospfSpfRunsRate and bgpPeerInUpdatesRate.

  • Many sections and parameters of the configuration file nw2.conf which user does not usually need to modify to start using application have been made the defaults and commented out in the prototype config. Unless you have made changes to the following sections of the nw2.conf file, we recommend you delete or comment them out:


    Contents of these sections in the file nw2.conf.prototype reflect the defaults. To change some of the values, we recommend overriding them with specific configuration statements that change the value of only one parameetr, for example:

    monitor.display.colors.0 = "#eeeeee"
    monitor.display.thresholds.minorChassisAlarm = [
                { value = "0", colorLevel = 0},
                { value = "1", colorLevel = 1},
                { value = "2", colorLevel = 2}
  • New interface role tag “Physical Port” has been introduced. This tag is opposite of “Virtual interface”. You can match this tag in the device details panel to limit the view of interfaces to only physical ports. For example on Juniper routers and switches interface ge-0/0/0 gets this tag, but ge-0/0/0.1 does not. On Cisco devices interfaces TenGigabitEthernet 1/1 or GigabitEthernet 8/9 get this tag, but Vlan201 does not.
  • UI, map view: icon [X] located under the zoom control performs “fit to screen” function for the map. It resets zoom factor to 1.0 (the default) and recalculates coordinates of all network nodes to make sure they fit in the view port. Recalculated coordinates are saved to the database, therefore this operation is permanent and is going to be visible to other users.

1.51.2. Known issues in this release

  • Zoom control still does not work in the map view. You can zoom in and out using mouse wheel.

  • Data processing functions should be applied to the time series data in correct order. Some of the functions operate on the time series and return new time series, while others operate only on the last data point and return single data point. For example, rate() operates on the time series and returns new time series that is one data point shorter. smm() takes time series as an input and returns new time seties as well. Functions mul() and div() operate only on the last value and return single data point. This means, sequence

    mul(smm(rate( ... )))

    will compute rate, smooth it and then multiple the last value, which leads to the correct result. However,:

    smm(mul(rate( ... )))

    does not, because mul() returns only single data point so smm() does not have enough time series data to smooth.

    This is going to be fixed in one of the subsequent releases.