interface_traffic (Interface Traffic Monitoring) Release Notes

The Interface Traffic Monitoring (interface_traffic) probe monitors the network traffic on the SNMP agents using standard MIB-II queries. The probe can monitor one or more interfaces for traffic congestion and inactive interfaces. To get the interface traffic data, the probe queries the SNMP agent on the defined host, using a combination of SNMPGet requests at predefined intervals. This period is calculated as the interval * number of samples. The probe reports when the traffic breaches a predefined threshold. It also supports Quality of Service (QoS) messages for the Service Level Agreement (SLA) family. The network interface can be monitored on a Windows or UNIX systems, or router or switch.
uimpga-ga
interface_traffic_RN
 
The Interface Traffic Monitoring (interface_traffic) probe monitors the network traffic on the SNMP agents using standard MIB-II queries. The probe can monitor one or more interfaces for traffic congestion and inactive interfaces. To get the interface traffic data, the probe queries the SNMP agent on the defined host, using a combination of SNMPGet requests at predefined intervals. This period is calculated as the 
interval * number of samples
. The probe reports when the traffic breaches a predefined threshold. It also supports Quality of Service (QoS) messages for the Service Level Agreement (SLA) family. The network interface can be monitored on a Windows or UNIX systems, or router or switch.
Probes that support SNMP on Linux (interface_traffic, snmptd, and snmpget) use an SNMP library. This library can cause newer Linux systems to issue the following message on the Linux console log:
process ‘interface_traff’ is using obsolete setsockopt SO_BSDCOMPAT
The SNMP library supports older versions of glibc which require the flag for sockets to work correctly. The network portion of the glibc library sends this message. The message shows that an unsupported flag is being sent to the setsockopt function. The library ignores this flag, so you can also ignore it.
Contents
Revision History
This section describes the history of the revisions for interface_traffic probe.
Support case(s) may not be viewable to all customers.
Version
Description
State
Date
5.46
Fixed Defect:
  • On a pure IPv6 environment, the probe did not accept the IP address in bulk configuration.
GA
March 2017
5.45
Fixed Defects:
  • The probe generated false alarms for the operational state of interface.
    Support case number
    s 70000904, 70000825
  • The probe used the default values instead of the specified timeout and retry values in a profile. 
    Support case number
    00168659
  • The probe incorrectly calculated the current percentage of interface errors when monitoring errors and discarded packets. A key, 
    incerrdistototal,
     has been added in Raw Configuration to calculate this value correctly. 
    Support case number
    00159962
    Note
    : For more information about this key, see the
    interface_traffic Troubleshooting
    article.
  • Updated the documentation with information about bandwidth utilization behavior in the probe.
    Support case number 323739
GA
October 2015
5.44
Fixed Defects:
  • Incorrect utilization was displayed for some interfaces.
    Salesforce case 00152619
  • Probe crashed when editing virtual interfaces.
    Salesforce case: 00162089
  • Incorrect alarm displayed for IndexShift in USM.
    Salesforce case: 00161338
GA
July 2015
5.43
 
What's New
:
  • Added support for pure IPv6. 
Fixed Defects:
  • Fixed an issue in which the probe did not save multiple changes to an existing interface.
    Salesforce case 00157651
  • Improved the formula to remove negative values of QoS/alarm. 
    Salesforce case 00145339
  • Fixed an issue in which the probe was displaying the default name in the alarm message and not the updated one. 
    Salesforce case 00154506
GA
April 2015
5.42
Fixed Defects:
  • Fixed an issue in which, when the probe was configured to use the host address as the QoS identifier instead of profile, the metrics were generated using the profile name as the QoS identifier.
    Salesforce case 00148492
  • Incorrect percentage was calculated for the alarm messages. 
    Salesforce case 00145415
  • Enhanced the logsize upper limit to 2 GB. 
    Salesforce case 00150857
GA
January 2015
5.41
Added a functionality to display the interface description in the Name column and interface alias in the Description column on the probe GUI. The feature also gets the interface description as QoS target in SLM database and USM view (like version 5.32) along with SNMP_v3 support. 
Salesforce case
00129782
Note:
Refer to the Considerations section to understand the upgrade scenarios.
GA
August 2014
5.40
  • Added a functionality in the probe to avoid the issue of getting different entries in SLM and different graphs for the same interface. This issue was identified while upgrading from version 5.32 to version 5.33.
    Salesforce case 00122371
Note:
On upgrading the probe from version 5.33 to version 5.40, for backward compatibility with version 5.33 behavior which uses ifname value instead of ifdescription value on SLM, you must uncheck the Use IfDescription for CI Name check box. By default, this checkbox is enabled.
  • Fixed a defect were the clear alarm token is changed from #network.interface_traffic.in_octets_fail to #network.interface_traffic.in_octets_ok. (Salesforce Case: 00125910)
GA
June 2014
5.33
  • Fixed: An issue where $ifDescr is returning $ifName value.
  • Fixed: Wrong interface_traffic into USM 
  • Fixed: SNMP_v3 Authentication issue
GA
September 2013
5.32
  • Added issue related Network devices show up twice for cisco_monitor and interface_traffic.
  • Fixed: Major issue the alert for lower threshold value in traffic tab got disabled, for all the interfaces while upgrading. Fixed: RunTime Overflow Error "6". Fixed minor issues in SOC conguration.
GA
July 2013
5.31
  • Fixed issue in negative value of interface traffic QoS data.
  • Fixed issue in Check Data Integrity - message dropped; samplemax found in data comes while inserting QoS into database.
GA
March 2013
5.30
  • Added a feature to break non-unicast packets to multicast and broadcast packets.
  • Added a feature to add the single threshold.
  • Added a feature to send alarm only once if interface is down or unavailable.
  • Fixed: Actions that are prevented are implied by an error dialog.
  • Fixed: Issue in adding devices in bulk in interface_traffic probe.
  • Added a feature to check the interface speed periodically.
  • Added a feature to send clear alarm if the interface is removed from monitoring.
  • Ability to add the interface name, description, or user-defined name for QoS target and QoS source.
  • Added a feature to configure extreme alarm messages and severity from GUI.
  • Added a feature to add a profile even if the SNMP query fails.
  • Added a feature to specify default settings for interface name (with regexp functionality) and/or interface speed.
GA
March 2013
5.26
Fixed an issue where $ifDescr and $ifName values are not correct in Dr.Nimbus.
GA
December 2012
5.25
  • Changed from "Using Both values and % of the maximum speed" to "Using Bytes/second and % of maximum speed".
  • Unchecking Include Alarm/Qos settings still save the settings.
GA
December 2012
5.24
  • Community strings are not encrypted on selecting Encrypt community string in Setup >Advanced tab.
  • Save inactive interface definitions check box has no effect.
  • Set Default from Interface do not save for Default General
GA
September 2012
5.23
  • Fixed the problem of highlighting Send alarm option(after unchecking Enable Monitoring). The newly added profile now has all the default settings.
  • Fixed UMP configuration issues.
GA
September 2012
5.22
Fixed QOS Issue which was not shown enabled on GUI.
GA
August 2012
5.21
Added functionality to ignore alarms when interface op state is down/not present/lower layer down.
GA
July 2012
5.20
  • Fixed a defect "maxspeed(ifSpeed) cannot be determined" false alarm.
  • Added a callback get_profile_status which accepts regular expressions in profile name and returns information of all the active profiles matched and it's interfaces.
  • Added support to AIX for 64 bit.
  • Fixed "Temporarily out of resources" issue in get_system_info callback.
  • Added functionality to ignore operational state alarms when admin state of an interface is not as expected.
  • Removed autocold start of probe after 1 week in Unix like OS.
  • GUI fix: QoS Settings for Interface Traffic are not saved when Publish QoS is not active.
  • GUI fix: Cannot clear Low or High Threshold values on traffic tab.
GA
June 2012
5.11
  • GUI fix: Added a functionality to remove the inactive interfaces from the list.
  • Number of interfaces are now showing the actual number of interfaces displayed in the list of a particular host.
  • The help button will now display online help instead of CHM.
GA
March 27 2012
5.10
  • GUI fix: Added a functionality to save Alarm / QoS settings for inactive interfaces.
  • Added interfaces multi-edit functionality on right click.
  • Added the functionality to apply the default settings when they are saved using Set Default button in the interface definition dialog box.
GA
March 16 2012
5.01
  • Implementation of IPv6 Compatibility.
  • Snmp query related bugs fixes.
  • Updated libraries.
GA
December 2011
5.00
  • Implementation for IPv6 Compatibility.
  • Snmp query related bugs fixed.
GA
October 2011
4.95
Fixed "No traffic" threshold.
(The "No traffic" threshold was in previous versions erroneously compared to the "% of max speed" value, if other traffic alarms were specified in "% of max speed").
GA
April 2011
4.94
Fixes for Service Oriented Configuration (SOC).
GA
March 2011
4.93
Added fixes for web-based Service Oriented Configuration.
GA
January 2011
4.92
Fixed get_samples callback (The issue was that GUI was not able to fetch samples from probe on 64-bit UNIX Robots).
GA
January 2011
4.91
  • Added support for handling of extreme values in Error and Discarded Packets section.
  • Fixed minor bugs in the probe GUI.
GA
December 2010
4.90
  • Added new feature for handling of extreme values in Traffic and Processed Packets section. Added fix to make "does not exist in the MIB" alarm message configurable. 
  • Added support to specify the traffic limit required to trigger "No Traffic" alarm.
  • Added support to monitor (Alarm and QoS) Error packets and Discarded packets as percentage (%) of total processed packets.
  • Added fix to allow one threshold value (both thresholds not mandatory now) in Traffic section.
  • Added support for a callback to get total number of active and inactive interfaces..
  • Added support for all known interface operational status (total 7 as per IF-MIB).
  • Added code to remove white space from all sections.
  • Added fix in alarm threshold field to show the correct value.
  • Added fix to avoid reloading of host profiles in the tree on expanding the group.
  • Added fix to uncheck 'alarm when no traffic is detected' checkbox on unchecking 'Enable Monitoring' checkbox of 'Traffic' tab.
  • Added fix to set interface speed after every interval of timer.
  • Added support for SNMP V2 and V3 credential details to perform bulk discovery.
  • Added option in bulk configuration window to remap interfaces after an index shift.
  • Added code to allow decimal numbers in threshold fields of 'Traffic' tab.
  • Added a checkbox 'Send QoS in Kbps' in Setup tab.
  • Added button in toolbar to execute interface status callback.
GA
December 2010
4.80
  • Added support for internationalization.
  • Added support for reading alarm tokens from cfg.
  • Increased SNMPWalk limitation from 300 to 3000 entries (added key /setup/max_oids in config file).
  • Support for Web based Service Oriented Configuration (SOC).
GA
November 2010
4.70
Fixed occasional crash situation.
GA
June 2010
4.64
  • Fixed probe restart when monitoring number of interfaces.
  • Fixed potential probe restart situation.
GA
January 2010
4.62
  • Fixed memory leak. (Introduced in version 4.60).
  • Fixed probe restart when the profile has no active interfaces configured and probe tries to send clear alarm.
GA
January 2010
4.60
Added support for extended NIS database information.
GA
December 2009
4.52
  • Always send QoS of interface traffic as Bytes/second in addition to kbit/second. This is due to other Nimsoft components requiring the Bytes/second dataseries.
  • You may disable the above functionality (if you know that Bytes/sec is not needed) by adding the following configuration key using Raw Configure: /setup/only_kbits = 1.
GA
July 2009
4.51
Fix potential program failure when using "Monitor" interface.
GA
June 2009
4.50
  • Added Alarm/QoS options on interface administrative status.
  • Added option of sending QoS messages on interface traffic in kbit/sec.
  • Fixed use of alarm severity other than 'major' on "Processed Packets" alarms.
  • Added support for x64 Windows platform.
  • Added support for 64bit platforms on SOLARIS, LINUX.
  • Added support for LINUX on 64bit PowerPC (glibc = 2.3).
  • Discontinued support for Solaris 2.5, 2.6 and 7.
GA
April 2009
4.40
Added support for "Virtual Interfaces".
GA
April 2009
4.36
  • Changed interface checksums to MD5.
  • Added utility "Generate Checksums" (update checksums on multiple profiles).
GA
November 2008
4.35
  • Fixed "No Traffic" alarm when ifSpeed is unknown.
  • Added alarm when ifSpeed is unknown and probe is configured to alarm on Traffic in % of ifSpeed
  • Fixed remapping of interfaces where ifName is used instead of ifDescr.
GA
May 2008
4.34
  • Fixed 'Rediscover Interfaces' and 'Query Agent' for SNMPv3 AuthPriv agents.
  • Fixed fetching of operstate on inactive (in probe config) interfaces for SNMPv3 AuthPriv agents.
  • Fixed 'Monitor' window for SNMPv3 AuthPriv agents. Added logging of thread id's.
GA
April 2008
4.32
  • Added critical sections around SNMPQueryCreate if SNMPv3
  • Added terminating -1 to SNMPQueryCreate.
  • Added platforms (missing in v4.30) LINUX and SOLARIS 8,9,10 (sparc).
  • Added support for privacy (SNMPv3).
  • Added SNMPv3 support in "bulk-configure".
  • Added SNMPv3 support in "add-range".
  • Fixed saving of default interface definitions.
  • Updated libraries.
GA
March 2008
4.25
  • Fixed saving of Defaults.
  • Updated libraries.
GA
October 2007
4.23
Fix: Do not save alarm and QoS settings of inactive interfaces (when inactive interfaces are set to be saved) Fixed fetching of operstate on inactive interfaces when using SNMPv3.
GA
September 2007
4.22
  • Fixed fetching of High Performance counters when using SNMPv1 (bug introduced in version 4.20)
  • Added support for SNMPv2c and SNMPv3.
  • Added retries setting for SNMP Get requests.
  • Added timeout setting for SNMP Get requests.
  • Fixed community string issue when longer than 20 characters.
  • Improved Message Pool Manager to handle SubsystemIds.
  • Added possibility to send Traffic QoS messages as % of max interface speed.
  • Added possibility to send Packet QoS messages as total packets counted.
  • Added possibility to set default interface settings per interface type.
  • Added possibility to override outbound and inbound speeds.
  • Added possibility to hide community strings from GUI.
  • Added NoTraffic on 'Any interface' alarm option.
  • Rediscover/Merge has been enhanced with UI feedback when interfaces has different names than configured.
  • Fixed samplemax on Traffic QoS messages when no traffic was detected on interface.
  • Fixed bulk-configurator.
  • Fixed alarm not being sent when configured to alarm in UP state.
  • Fixed dashboard filter settings.
  • Dashboard discovery template enhanced to use 'friendly' names of devices and interfaces.
GA
September 2007
4.12
  • Fixed update problems with the uptime variable in 'get_samples' command.
  • Fixed default interface settings to keep the 'unit' variable.
  • Added $group as a variable to be used in the message pool.
  • Added support for a user defined text per interface ($user1).
GA
March 2006
4.02
  • Added NULL QoS values for traffic metrics when interface was reported 'down'.
  • Added support for more operational states.
  • Fixed problem when configuring probe through a NimBUS tunnel.
GA
May 2005
Probe Specific Hardware Requirements
The interface_traffic probe should be installed on systems with the following minimum resources:
  • Memory: 2-4GB of RAM. The OOB configuration of the probe requires 256MB of RAM
  • CPU: 3GHz dual-core processor, 32-bit or 64-bit
Probe Specific Software Requirements
The interface_traffic probe requires the following software environment:
  • Nimsoft Monitor Server 7.6 or 
    CA Unified Infrastructure Management
    8.0 or later.
  • Robot 7.6 or later (recommended)
  • The target SNMP agent must support the MIB-II ifTable.
    • For SOC functionality, server 5.6 or later and UMP 2.5.2 or later is required.
    • SNMP v3 requires that your network community strings are at least 8 characters long.
Upgrade Considerations
This section contains the upgrade considerations for this probe. 
  • The probe supports IPv6 from version 5.43. The probe must be deployed in pure IPv6 environment to monitor IPv6 interfaces.
  • The
    Setup
    window in version 5.41 or later version of the probe has the 
    Use IfDescription for CI Name
    and
    Use Alias
    check boxes. You must consider the following scenarios for these check boxes:
Use IfDescription for CI Name
Use Alias
Functionality
Not Selected
Not Selected
The probe GUI displays the interface name in the
Name
column and interface description in the
Description
column. The interface name is visible as the QoS target in
USM
view and
SLM
database. The current version of the probe will function as version 5.33 of the probe.
Selected
Not Selected
If you have upgraded from a previous version, the settings of the previous version remain intact until you rediscover the interfaces. After you rediscover the interfaces, the default settings of version 5.41 or later are applied.
The probe GUI displays the interface name in the
Name
column and interface description in the
Description
column. However, the interface description is visible as the QoS target in
USM
view and
SLM
database. This is the default configuration in version 5.41 or later.
Not Selected
Selected
The probe GUI displays the interface description in the
Name
column and interface alias in the
Description
column (like version 5.32). The interface name is visible as the QoS target in
USM
view and
SLM
database (like version 5.33) along with SNMPV3 support. Hence, it is not recommended to select only the
Use Alias
option.
Selected
Selected
The probe GUI displays the interface description in the
Name
column and interface alias in the
Description
column. The interface description is visible as the QoS target in
USM
view and
SLM
database (like version 5.32) along with SNMP_v3 support.
Known Issues and Workarounds
Before configuring a template on UMP, please ensure that probe is deployed on the robot.
  • The probe was displaying the default name of the interface in the alarm message, even after the the name has been manually updated. 
    The
    ifName
    (default name) of the interface cannot be altered. In order to view the updated name in the alarm message, use
    '$name'
     variable . 
  • Issues with the profiles (devices) added to interface_traffic
    before
    v4.35. 
    A problem regarding automatic re-mapping of indexes after an index shift has been detected on devices that use
    ifName
    (from ifXTable) instead of
    ifDescr
    as interface name(s). 
    In order for the probe to operate properly (if an index shift occurs), a "Rediscover Interfaces" (available in the probe GUI) should be issued to generate new checksums of interface names.If
    ifDescr
    is not unique on the device and ifName contains only 1 character (i.e. "1") as the name for an interface, it could lead to false "interface index change" alarms. The workaround is to set
    ifName
    on the affected interface(s) to a string with at least 2 characters, and then do a "Rediscover Interfaces" from the probe GUI.
  • (probe version 5.32) The probe GUI displayed the interface description in the Name column and interface alias in the Description column.
    This issue is resolved in version 5.33 where the interface name is displayed in the
    Name
    column and interface description is displayed in the
    Description
    column.
  • (probe version 5.33) For the same interface, there were different entries in the SLM database and different USM graphs.
    The workaround is that a check box
    Use IfDescription for CI Name
    is added in the
    General Setup
    tab in version 5.40.