What's New:

• Released with Device Certification Deployer v4.20 release.
• Support for DCD 4.20
  • Added Certification Enhancements for the Fortinet FortiADC 100F devices.
• Prerequisites:
  • ci_defn_pack is v1.68 or later.

Important: Also, see the prerequisites in the Update Vendor Certifications topic.

What's New:

• Released with Device Certification Deployer v4.1 release.

Prerequisites:

• ci_defn_pack is v1.67 or later.

What's New:

• Updated this probe as part of addressing known vulnerabilities in DX UIM by upgrading the following third-party libraries:
  • Jettison from Json Stax implementation 1.3.3 to 1.5.4
  • Jackson-databind - 2.13.4 to 2.14.2
  • JDOM from 2.0.2 to 2.0.6.1
  • Undertow from 2.2.19 to 2.2.24
  • Xstream from 1.4.19 to 1.4.20
• Support for DCD 4.0

Fixed Cases:

• Snmpcollector probe version 4.06T2 does not start.
• Updates made to snmpcollector probe 4.06 overwrites DCD files with old level 3.40.
• Unable to import a device from the discovery server when the snmpv3 password has @ and # characters.

What's New:

• Updated the H2 Database library to 2.1.210 for remediating of CVE-2021-42392 vulnerability.
• Added H2 database migrator.

Fixed Defects:

• Fixed case 33041494 - Disappearance of the GUI on port 9715 of the SNMPCollector hub.

What's New:

• Added support for the SHA256 authentication protocol.
• Updated the Log4j library to 2.17.1 to remediate the vulnerabilities - CVE-2021-44228, CVE 2021-45046, and CVE-2021-45105.

Fixed Defects:

• Fixed an issue where snmpcollector fails to poll device with AES-256 credentials. Support case 32110381
• Fixed an issue for the Nokia Alcatel-Lucent 9500 MPR devices where there is no Interface section. Support case 32148608
• Fixed an issue with VendorCertification file (snmp-f5-bigip-global-host-cpu.xml) containing extra space. Support case 32068147
• Fixed an issue with the wrong Sample rate compared to polling value configured in template. Support case 31899010
• Fixed an issue where snmpcollector "Query Discovery Server" fails when Device Service Filter is used. Support case 32071445
• Fixed the Missing snmpcollector data issue for the devices when the device is temporarily unreachable. Support case 31846523
• Fixed an issue where snmpcollector probe uses wrong SNMPV3 credentials to connect the equipment. Support case 31825554

What's New:

• Improved the scalability and performance of the probe. Enhancements include updating the design from synchronous polling to asynchronous polling.

For more information, refer https://docops.ca.com/rest/ca/product/latest/topic?hid=snmpcollector_RN&space=UIMPGA&language=&format=rendered

What's New:

• Enhancements done to improve scalability and performance. Major design changes include changing the synchronous polling into asynchronous polling.

This is Beta build.

What's New:

• DCD is now upgraded to version 2.60.
• Added the following metric in the Availability metrics family: QOS_AVAILABILITY_SYSUPTIME
  To view the metric, you must rediscover all the devices.
• Additional details about discovery and templates is now available in the snmpcollector metrics page. You can view the summary and details of the following:
  • Discovered Devices
  • Devices Not Discovered
  • Devices with Template Not Applied
• You can now bulk configure User Defined Property 1for one or multiple devices using the callback: set_device_user_defined_property_1, which sets the property using a csv file. The csv file follows the format:
  devicename1,property_value1
  devicename2,property_value2
• Improvement in the time taken to start the polling devices after every restart of the snmpc probe or after the discovery of a large number of devices.

Fixed Defects:

• The probe published 0 as values of availability intermittently even if the device under monitoring never went down. Support Case Number 01275790
• The probe was not polling correctly as the metrics did not reflect from USM. Support Case Number 01148675
• Fixed an issue where after executing the Query Discovery Serverfrom the UI, the probe was taking 4 hours to start the first poll. Support Case Number 01195052
• Fixed an issue where the probe was polling metric page vulnerabilities, which disables the ENABLE_HTTP_WEB_SERVER metric.Support Case Number 01262269
• Fixed an issue where the device is reachable but the probe indicates that the reachability is 0% and it is not pollable.Support Case Number 01261331
• Fixed an issue where the Component User Defined Properties 1 parameter was not honored.Support Case Number 01311510
• Fixed an issue with disabling unwanted alarms in templates.Support Case Number 01304867
• Fixed an issue where using the Query Discovery server call did not add the new devices. Support Case Number 01319679
• Fixed call backs that were not working through Administration Console.

For Detailed Release Notes-Please refer

https://docops.ca.com/rest/ca/product/latest/topic?format=rendered&language=&space=UIMPGA&hid=snmpcollector_RN

Note: Support case(s) may not be viewable to all

What's New:

• Includes stability enhancements to handle multiple h2 database corruption issues.
• Added the ability to store multiple database backup files. The number of backups to be maintained is configurable through raw configuration. For more information about storing multiple database backup files, see Multiple Database backups.
• Added the ability to configure the number of polling threads. This optimizes poll intervals in scenarios where large number of devices are being monitored. For more information, see Poller Thread Multiplier.
• A new callback has been added to enable additional logging for debugging. For more information, see Additional Logging.
• The snmpc 3.44 release uses the DCD (Device Certification Deployer) tool v2.1, by default.

Fixed Defects:

• Increased occurrences of PPM-012 errors when opening the snmpcollector probe config in Admin Console. Support Case Number01134930
• Any device which reaches a sysuptime of more than 497 days becomes unreachable to the probe resulting in failure state of the profile. Support Case Number 00808412
• Snmpcollector poller.log file keeps growing until the server runs out of disk space.Support Case Number 00901811
• Component User Defined Property 1 lost on rediscovery. Support Case Number 00924133 
• snmpcollector failed initializing DB. Support Case Number 00923892
• No response when trying to update "User Defined Property 1" field, using call-back function defined in snmpcollector probe. Support Case Number 00938300
• Snmpcollector stops collecting data when polling large number of devices.Support Case Number 01064878
• Unable to open snmpcollector DB backup (zip) file. Support Case Number 00967577
• SNMP Probe Robot Stopped collecting data. Support Case Number 01135561 and 01089264 

For Detailed Release Notes-Please refer

https://docops.ca.com/rest/ca/product/latest/topic?format=rendered&language=&space=UIMPGA&hid=snmpcollector_RN  

Note: Support case(s) may not be viewable to all

What's New:

• By default, the snmpc 3.44 release uses the DCD (Device Certification Deployer) tool v2.1.
• Added the ability to store multiple database backup files, appended by date and time stamp.
  By default, the count of DB backups is 5. The count is user-configurable. Add the BACKUP_COUNT key in the config (.cfg) file, to modify the number of backups required.
• Upgraded the MVEL (MVFLEX Expression Language) third-party library from from 2.2.4.Final to 2.4.0.Final.
• A new configuration key: POLLER_THREAD_MULTIPLIER, has been added to increase the number of threads used for polling.
• A new callback (enable_extended_logs) has been added to enable extra logs. By default, the value is False. When the parameter is set to True, new log files with more information on various scenarios are created.

Fixed Defects:

• Increased occurrences of PPM-012 errors when opening the snmpcollector probe config in Admin Console. Support Case Number01134930
• Any device which reaches a sysuptime of more than 497 days becomes unreachable to the probe resulting in failure state of the profile. Support Case Number 00808412
• SNMPCollector poller.log file keeps growing until the server runs out of disk space.Support Case Number 00901811
• Component User Defined Property 1 lost on rediscovery. Support Case Number 00924133 
• snmpcollector failed initializing DB. Support Case Number 00923892
• No response when trying to update "User Defined Property 1" field, using callback function defined in snmpcollector probe. Support Case Number 00938300
• SNMPCollector stops collecting data when polling large number of devices.Support Case Number 01064878
• Unable to open SNMPCollector DB backup (zip) file. Support Case Number 00967577
• SNMP Probe Robot Stopped collecting data. Support Case Number 01135561 and 01089264

• Fixed an issue for encrypting SNMP credentials stored in the database when migrating from previous versions

• Rarely, the snmpcollector probe might lose communication with the database. Workaround is to restart the snmpcollector probe

What's New:

• Improved the internal database performance and the handling of concurrent reads and writes. The improved database performance results in faster discovery, template application, and polling configuration times.
• Added an inventory report for devices, components, and configured monitors.
• Improved support for monitoring similar processes running on the same device. Processes are now identified by a name and a number. For example, "(events/2)".
• SNMP Credentials are now encrypted when stored in the internal database.
• You can now copy and apply all default templates by checking the Enable Auto Templates box. For more information, see snmpcollector AC Configuration.
• You can now set up the Discovery Server to import devices on a recurring interval. For more information, see snmpcollector Import Devices.

Fixed Defects:

• Improved database stability and concurrency. These improvements in the database correct an issue that in past releases resulted in "JdbcSQLException" stack trace errors that indicated that the length of the database file was "-1".
• Fixed an issue in which incorrect hostnames were assigned to devices. On Windows systems, a hostname could be set to the computer name instead of a hostname that was resolved by DNS.
• Fixed an issue in which the load seed file failed for SNMPv3. The failure was caused by an incorrect setting of the SNMPv3 security level.
• Fixed an issue in which a template did not apply when you created a filter based on the “Name” attribute.
• Fixed an issue in which when you added or configured a "component user defined property 1" of any type on a specific device, the probe created components with duplicate names.
• Fixed a documentation issue in which the Theory of Operations page for the probe incorrectly stated that the probe collects alerts and traps from an SNMP agent. The probe does not collect alerts or traps from an SNMP agent.

What's new:

• Added support for monitoring LPARs on SystemEDGE- enabled devices.
• Added support for viewing data from SystemEDGE- enabled devices in the OnDemand report for SystemEDGE.

Fixed Defect:

• Fixed an issue in which, when you use a template filter with "User Defined Property 1" and the conditional "Not," the filter did not apply correctly.
• Fixed an issue in which V3 credentials failed on engine ID changes.
  Previously, if the probe failed to connect with a target after GA two seconds, the probe tried to connect three more times for a total of 16 seconds. Now the probe tries to connect only two more times for a total of eight seconds.
• Updated the documentation to emphasize that we recommend that you install the probe on a remote or secondary hub. Support case number 00646365
  In addition, we recommend that you:
  • Set up queues on the remote hub to post data to the primary hub. The remote hub requires a queue for QOS_MESSAGE, QOS_DEFINITION, QOS_BASELINE, and a queue for probe_discovery to export messages.
  • Configure NAS forwarding as "All alarm events in both directions" on the remote hub. The destination is the primary hub.

What's New

• Added support for monitoring SystemEDGE-enabled devices, including VMware hosts, using the snmpcollector probe and CA UIM 8.5 and later. (If you do not want to monitor SystemEDGE-enabled devices, the snmpcollector probe v3.3x is compatible with CA UIM 8.4 and later.) For more information, see the new how-to article, Monitor SystemEDGE-enabled Devices with the snmpcollector Probe.
  
  Note: When you create authentication profiles in Discovery for SystemEDGE-enabled devices, you must select SNMP v1.
• Added new options to the drop down menu for the Polling Interval field in the probe configuration UI and templates: 10, 30, and 60 minutes.
• Changed the default Router-Switch template so that it does not include the CBQoS metric families. Added a new default Router-Switch With CBQoS that does include the CBQoS metric families:
  • CBQoS Red
  • CBQoS ClassMap
  • CBQoS Match Statement
  • CBQoS Policer
  • CBQoS Queueing
  • CBQoS Traffic Shaping
  Note: The above CBQoS metric families are known to cause increased discovery time and to slow probe performance because they can result in the discovery of hundreds of even thousands of components for each device.Unless you require CBQoS monitoring, we suggest that you use the new Router-Switch template that does not contain the CBQoS metric families.
• Added the option to enable the discovery of and monitoring of only the most commonly monitored metric families, and the new SystemEDGE metric families. The optimized list of 35 metric families also includes those that are monitored by the default templates. It excludes those metric families that are monitored by the Router-Switch With CBQoS template. For more information, see snmpcollector Configure Monitoring with templates.
  
  Users who take advantage of monitoring only this optimized list of 35 metric families, and who can begin with a clean snmpcollector directory, could see the following performance improvements:
  • Faster polling from startup
  • Reduced Discovery times
  • Reduced polling configuration times
  • Reduced template application times
  • Smaller database size
  • Elimination of GUI load time outs
  • Faster GUI load times
  For more information, see Upgrade snmpcollector.

Fixed Defects

• Fixed an issue in which existing monitor settings were deleted when you added a metric family to a device profile and then forced component rediscovery.
• Fixed an issue in which the vendor certifications for Fujitsu Primergy devices returned an incorrect value for the device status. Previously, these vendor certifications normalized status values to either 0 or 100. Users who created alarm definitions based on these vaules, will need to modify the alarm definitions to check for the actual status value.
  
  For example, the Primergy sc2 fan now has the actual status values: unknown (1), disabled (2), ok (3), failed (4), prefailure-predicted (5), redundant-fan-failed (6), not-manageable (7), not-present (8).
• Updated the documentation for the snmpcollector Memory and Disk Requirements:
  • Increased the memory requirements in the probe documentation. Support case number 532713
  • Added a note to Memory and Disk Requirements : If your instance of snmpcollector is installed on a virtual machine, the probe requires dedicated memory.
• Updated the documentation for how to Upgrade snmpcollector:
  • Added a note: Version 3.x of the probe requires less memory and has different startup options than version 2.x. Because of this, when you upgrade from 2.x to 3.x, the probe startup options are overwritten. After you upgrade from 2.x to 3.x, review the startup options to determine if you want to restore any of your custom changes.

What's New

• Revised the documentation to explain how snmpcollector interacts with three optional utilities that can help you set up and manage your monitoring of supported SNMP devices: the Device Support Tool, the SelfCert portlet, and the Device_Certification_Deployer package. For more information, see snmpcollector Theory of Operations.

Fixed Defects

• Fixed a defect in which dynamic template generation incorrectly processed filters for "not", such as "does not contain".
• Fixed a defect in which, when a user upgraded to 3.2, the snmpcollector.cfg file settings were overwritten.
• Fixed a defect in which, when a user upgraded to 3.21 from 2.26, the topology graph published only one component for a given non-interface metric family.
• Fixed a defect in which rediscovery alternately deletes and re-adds components when the applied template specifies non-default values for Polling Interval or Speed Override.
• Fixed a defect in which template attributions were not deleted when the template was deleted or deactivated.
• Fixed a defect in which, when a user upgraded to 3.21 from 2.26 or later, a null pointer exception occurred if a metric family had no components, which caused the upgrade to fail. Support case number 482763
• Fixed a defect in which, when a user upgraded to 3.21 from 2.26 or later, the upgrade did not remove invalid components.
• Fixed a defect in which a null pointer exception occurred during CTD GUI graph creation.
• Fixed a defect in which the snmpcollector UI would not open in a Java 8 environment.

What's New

• Improved template application performance.

Fixed Defects

• Fixed an issue in which the probe would apply templates on all devices, even when no new devices had been discovered, which caused unnecessary polling configuration.
• Fixed an issue in which speed override configurations did not apply to speed in or speed out metrics.
• Fixed an issue in which template application and polling were delayed by devices in pending or failed state.
• Fixed an issue in which templates were applied at startup even when no changes had been made since the last startup. Templates are now applied only if changes have been made since the last startup.
• Fixed an issue in which a run time exception caused polling to stop.
• Fixed an issue in which speed override configurations did not apply to speed in or speed out metrics.
• Fixed an issue in which discovery of large devices, such as router tables, took more than two minutes.
• Fixed an issue in which changing the configuration for global retries and timeouts has no effect on previously discovered devices.
• Fixed an issue in which discovery failed for devices that did not report SysUpTime.
• Revised the Software Requirements documentation to state that snmpcollector 3.2x requires CA Unified Infrastructure Management 8.4 or later.

What's New

• Incorporated the functions of the pollagent probe into the snmpcollector probe.
  • Beginning with v3.2, the snmpcollector probe no longer uses or is installed with the pollagent probe.
  • When you upgrade from v2.26 to v3.2, the pollagent probe is automatically deactivated and uninstalled.The polling interval is then set to the default in snmpcollector.
• Metric family, vendor certification, and vendor priority files remain. However, device configuration files are replaced with an internal database, which stores the results of template applications so that polling begins more quickly on probe startup.
• Added the following read-only fields to the probe configuration GUI snmpcollector Node: Poll Config Status, Device Discovery Status.
• The probe now allows you to configure the number of timeouts and retries per device.
• The template editor now identifies deprecated metric families. If a metric family is marked as deprecated, reconfigure your monitoring settings.
• Device filter IDs are now in the Template Editor .tplt files located GA in \probes\network\snmpcollector\bulk_config\templates. This simplifies the process of copying templates to another system. Only the desired .tplt file is required.
• The Template Editor .tplt file names now include a human readable fragment based on the template name. The .tlpt file name fragment retains the numbers, letters, and underscores in the template name. All spaces and special characters are removed when the probe creates the .tlpt file. For example, a template with the name My Template $_1 would have the corresponding .tplt file with the name MyTemplate_1.12e433.tlpt
• The template .gzip file in no longer required for Template Editor templates.
• Scheduled rediscovery is now off (0) by default. To change this setting:
  1. Go to the probe configuration GUI and click the snmpcollector node.
  2. Change the Hours between rediscovery value in the Probe Configuration section of the details pane.
• Added the following metric families:
  • Normalized Application Services
  • Normalized Cluster Node
  • Normalized Environmental Sensor Door Switch
  • Normalized Environmental Sensor Dry Contact
  • Normalized Mobile WLAN Station
  • Normalized Node Client Information Daemon
  • Normalized Node Lock Manager
  • Normalized Node Network
  • Normalized OSPF Neighbor o Normalized UPS Line
  • Normalized UPS
• Deleted the CBQos Queueing, CBQos Queueing 1, CBQos Queueing 2, and CBQos Queueing 3 metric families. The Interface Queues metric family now contains the following changes:
  • The CurrentQueueSize, MaximumQueueSize, and MessagesDiscarded metrics are now located in the Interface Queues metric family
  • The DiscardedPacket metric was deleted and is now mapped to MessagesDiscarded

Fixed Defects

• Corrected an issue in which the graph for line status appeared incorrectly in UMP. The graph now shows up in UMP with a label of State and the values are integers.
• Corrected an issue in which the metric type for free licenses was appearing as 11.396:3. The metric type now correctly appears as FreeLicenses.
• Corrected an issue in which some metrics display pct instead of the percent (%) symbol.
• Corrected issues with firewall metrics.
• Corrected metric for QOS_RESPONSEPATHTESTDNS_AVGRESPONSETIME so it no longer returns 0.