Fixed Issues

This release provides fixes and enhancements to pre-existing
DX NetOps Performance Management
functionality.
This release provides the following fixes and enhancements to pre-existing
DX NetOps Performance Management
functionality:
20.2.10 Fixes
  • Symptom:
    The group path selector may not correctly display path shown in the breadcrumbs if several alternative paths to the end group exists.
    Resolution:
    With this fix, the group path selector correctly correctly display path shown in the breadcrumbs when several alternative paths to the end group exists.
    (20.2.10, DE475779)
  • Symptom:
    Running
    CAPerfCenterSetup.bin -r
    to record a response file saves MySQL folders with extra '\\"' chars that do not work during later silent install.
    Resolution:
    With this fix, the
    CAPerfCenterSetup.bin -r
      command now records MYSQL_DATA_FOLDER and MYSQL_TEMP_FOLDER to the response file without the extra escaped quotes.
    (20.2.10, DE482586)
  • Symptom:
    When you enable scroll in view controls on the Time Bar Chart, page navigation control is shown. The time alignment icon is lost.
    Resolution:
    With this fix, when you scroll the Time Bar Chart, the time alignment icon is now shown. You can define the table to display more entries (rows) by selecting Max Rows, which expands the view. You can continue to use the scroll bar.
    (20.2.10, DE487489)
  • Symptom:
    SDWAN Tunnels and the SLA Paths Time Bar view does not always use the consistent time bucket resolution size with first time bucket for the selected time range.
    Resolution:
    With this fix, SDWAN tunnels and the SLA Paths Time Bar views now use the consistent time bucket resolution size for the selected time range.
    (20.2.10, DE493934)
  • Symptom:
    When generating a URL for a card view, the underlying table can have threshold icons that are too large for the results grid to display properly. Similarly, when generating a URL for an inventory view or scorecard view, the icons might display at the correct size, but they are badly mis-aligned.
    Resolution:
    With this fix, when you generate a URL for a view that contain tables (grids) with icons in them, the icons are now displayed correctly (for example, in card views, inventory views, and scorecard views).
    (20.2.10, DE496813)
  • Symptom:
    You cannot look up tunnels using only IP addresses.
    Resolution:
    With this fix, you can now look up tunnels using the dynamic hostname.
    (20.2.10, DE496939, 32600395)
  • Symptom:
    When you click a device name hyperlink on a custom Time Bar Chart, and you using component level, the wrong context page can open.
    Resolution:
    With this fix, when you click a device name hyperlink on a custom Time Bar Chart, and you are using component level, the correct context page opens.
    (20.2.10, DE497108, 32271856)
  • Symptom:
    On-Demand when using the
    Chart per metric by single item
    report type, the charts can sometimes be missing on the page.
    Resolution:
    With this fix, On-Demand when using the
    Chart per metric by single item
    report type, the page now shows the charts.
    (20.2.10, DE497160, 32595972,32556916)
  • Symptom:
    The DVS Ports ID is processed as long, which causes number format exception when processing characters.
    Resolution:
    With this fix, the PortId type is now String for DVS ports.
    (20.2.10, DE497403, 32600169)
  • Symptom:
    When the System Administrator sets up the label functionality within their Dev environment, the change does not propagate up to
    NetOps Portal
    to consolidate the items together. They still showed under the 192.168.x.x address.
    Resolution:
    With this fix, the plug-in maps the interface-label name to a number, finds that number in the interface, and replaces the system IP of devices with the IP Address of that interface.
    (20.2.10, DE497877)
  • Symptom:
    When searching locally in filter expressions, the table model does not correctly handle the asterisk (*) wildcard character.
    Resolution:
    With this fix, you can use the asterisk (*) wildcard character with table views for local filter search when querying for items (device and interfaces) that match to inventory data columns.
    (20.2.10, DE499044)
  • Symptom:
    When using the Yesterday, Previous Week, Previous Month custom time ranges, the On-Demand Report (by Component and by Device) and the revised Multi-View does not include first and last metric entries for midnight time periods.
    Resolution:
    With this fix, when using the Yesterday, Previous Week, Previous Month custom time ranges, the On-Demand Report (by Component and by Device) and the revised Multi-View now include first and last metric entries for midnight time periods.
    (20.2.10, DE499775, 32609645)
  • Symptom:
    During initial page load of As names,
    NetOps Portal
    logs errors.
    Resolution:
    With this fix,
    NetOps Portal
    does not log the errors.
    (20.2.10, DE500222)
20.2.9 Fixes
  • Symptom:
    When a
    NetOps Portal
    user with multiple permission groups creates a notification (which results in a My Assigned Groups being created),
    NetOps Portal
    adds a permission group check to make sure that the user has permission to see the item. If the cache of group paths is currently not useable (it is being updated), the check does not fall back to querying the DB. Also, the wrong validation function is called when checking the item in the creator's list of permission groups. Either cause resulted in a notification not being sent.
    Resolution:
    With this fix, the item in group logic now queries the database when the cache is currently not useable. Also, the item in permission group now uses the correct validation function.
    (20.2.9, DE473675, 32570300)
  • Symptom:
    On a system where
    NetOps Portal
    is installed as a non-root user and restrictions are made on the use of the
    rpm
    command,
    NetOps Portal
    fails to start during its check for the availability of
    wget
    .
    Resolution:
    Updated the
    NetOps Portal
    startup script that checks for
    wget
    to use the
    which
    command, which is less often restricted for non-root users.
    (20.2.9, DE484555)
  • Symptom:
    Even when an email server has not been specified/configured, a user can send or schedule a report by email (the
    Email/Schedule Report
    button is enabled) on dashboards and other pages. This results in an error telling them that an email server is not configured.
    Resolution:
    With this fix, if an email server has not been specified/configured, a user cannot send or schedule a report by email (the
    Email/Schedule Report
    button on dashboards is disabled). A tooltip now displays on the disabled menu item explaining why the user cannot send or schedule a report by email.
    (20.2.9, DE485661)
  • Symptom:
    In fault-tolerant environments, setting the data aggregator into maintenance mode causes unfriendly shutdown and
    consul-ext.log
    entries, such as
    Kill DA karaf process
    or
    daservice, which stop it by force
    .
    Resolution:
    Updated the
    stopDA.groovy
    file to use short hostname when getting status so that it succeeds and does a friendly shutdown (no "kill" in logs).
    (20.2.9, DE487120)
  • Symptom:
    The device life cycle state changes in
    NetOps Portal
    change the device's state in
    DX NetOps Spectrum
    .
    Resolution:
    With this fix, to prevent the device life cycle state changes in
    NetOps Portal
    from changing the device's state in
    DX NetOps Spectrum
    , set the
    LifeCycleStateSyncToSpectrum
    general table setting to false.
    (20.2.9, DE488398, 32428502)
  • Symptom:
    Polls do not successfully terminate when engine is stopped.
    Resolution:
    Added additional checks and all threads are now cleaned when engine is stopped.
    (20.2.9, DE489435)
  • Symptom:
    In the
    PeerPathStats
    and
    RouterStats
    , the message log keeps warn and error levels in the LOGGER. Hence, This message can flood the logs with warning messages every poll cycle.
    Resolution:
    The logs with warn level and error level have been changed into debug level in
    PeerPathStats
    and
    RouterStats
    .
    (20.2.9, DE490470)
  • Symptom:
    ActiveMQ is not logging faults on startup.
    Resolution:
    Update the configuration of ActiveMQ to have a log location.
    (20.2.9, DE491859)
  • Symptom:
    DX NetOps Virtual Network Assurance
    runs out of memory during the initial performance poll which was preventing it from getting tunnel statistics from the Viptela VManage.
    Resolution:
    Optimized the
    DX NetOps Virtual Network Assurance
    data processing to help reduce the memory footprint of the
    DX NetOps Virtual Network Assurance
    process.
    (20.2.9, DE492414, 32501295)
  • Symptom:
    The stale notification cleanup process failed to run due to a timeout. This prevented old events and cleared alarms from being removed from the database, and ultimately lead to
    DX NetOps Spectrum
    receiving stale events/alarms and
    DX NetOps Virtual Network Assurance
    having a much larger memory footprint.
    Resolution:
    With this fix, the cleanup process has a longer timeout and can run in the background without being rolled back. Additionally, the process has been optimized and now reduces the
    DX NetOps Virtual Network Assurance
    memory increase that is seen while cleaning up stale notifications.
    (20.2.9, DE492572, 32516904)
  • Symptom:
    At the time of installing
    NetOps Portal
    , the
    NetOps Portal
    installer creates an extra
    /mysql
    directory.
    Resolution:
    The
    NetOps Portal
    installer has been updated. It no longer creates this extra directory.
    (20.2.9, DE492603, 32517366)
  • Symptom:
    128T throws an unhandled exception if the value was in the wrong format.
    Resolution:
    Modified the
    Regexp
    expression so that it can handle devices without a set location, missing dot in format, or empty value in location set. In addition, added a exception to catch wrong format.
    (20.2.9, DE492842, 32497042)
  • Symptom:
    The On-Demand/Multi-Metric Trend Report intermittently has non-standard data resolution when aggregated to the group level.
    Resolution:
    With this fix, the On-Demand/Multi-Metric Trend Report no longer has an intermittent non-standard data resolution when aggregated to the group level.
    (20.2.9, DE493256, 32531719)
  • Symptom:
    Warnings are printed to the data repository installation log for files that do not exist.
    Resolution:
    With this fix, the installer now checks for presence of disaster recovery files before backing them up.
    (20.2.9, DE493519, 32533549)
  • Symptom:
    You cannot add data aggregator URLs to SSO white list.
    Resolution:
    When you add or edit a data source, the URL for the data source is saved as a possible SSO white list item.
    (20.2.9, DE494199)
  • Symptom:
    Data collector or data aggregator uninstall or upgrade might not fully stop the ActiveMQ service, and results in issues removing the existing ActiveMQ files.
    Resolution:
    With this fix, the uninstall and upgrade logic now fully stops the ActiveMQ service.
    (20.2.9, DE494220)
  • Symptom:
    If a device supports the QoS Policing metric family with the Viptela QoS Policer vendor certification, there can be many
    IllegalArgumentException
    in the data aggregator
    karaf.log
    file, and the polling data is dropped for the metric family.
    Resolution:
    Improved the expressions in the Viptela QoS Policer vendor certification so that the polled data can be processed properly.
    (20.2.9, DE494345)
  • Symptom:
    When syncing a device from the data aggregator to
    NetOps Portal
    , the device item description was being used over the Simple Network Management Protocol (SNMP) system description. For SNMP/
    DX NetOps Virtual Network Assurance
    devices, this can cause the
    DX NetOps Virtual Network Assurance
    description to be used over SNMP provided device description.
    Resolution:
    Data aggregator synchronization now uses SNMP provided system description over item description.
    (20.2.9, DE494351, 32532665)
  • Symptom:
    The data aggregator
    karaf.log
    file shows that at the data aggregator startup, the polling configuration items were calculated twice which could be a big performance impact on the data aggregator startup.
    Resolution:
    Improved the data aggregator startup process so that the polling configuration items are only be calculated once.
    (20.2.9, DE494372)
  • Symptom:
    In Firefox only, if you have configured
    NetOps Portal
    to add base tags to NetOps Portal web pages that are rendered to the browser (a web browser session security setting), some tree controls redirect to your home page when you click an element in a tree. For example, in the Create New User/Edit User wizard, clicking an element in a tree in the second or third step might misbehave.
    Resolution:
    Clicking elements in trees works correctly in Firefox.
    (20.2.9, DE494374)
  • Symptom:
    The ROS container (on disk) can contain multiple partitions.
    NetOps Portal
    attempts to drop the oldest data partition by date, if it has been merged to another data partition. With false, it does not try to break the two partitions into their own ROS container and then fails the drop.
    Resolution:
    Modified
    dropPartition
    and
    forceSplit
    from false to true.
    (20.2.9, DE494503, 32563812)
  • Symptom:
    When you set the business hour context properties at the user-session level, certain
    DX NetOps Network Flow Analysis
    views not rendering data.
    Resolution:
    With this fix, when you set the data aggregator business hour properties at the user-session level, the
    DX NetOps Network Flow Analysis
    views now render data.
    (20.2.9, DE494571)
  • Symptom:
    Due to heavy load or some other reason, the device's system clock might run slower than the data collector's system clock. If the slowness is greater than 10 seconds between two successful polls, the data collector thinks that the device had been rebooted. The polled data is then dropped, and a false reboot event is generated.
    Resolution:
    Improved the algorithm of reboot detection to better handle the drift of the device system time so that the polled data is not be dropped and false reboot events are not generated.
    (20.2.9, DE494812, 32543613)
  • Symptom:
    Certification and property file changes are not reliably detected in attached storage folders.
    Resolution:
    Updated the method for monitoring certification files and property files to use a recurring poll instead of relying on OS events, which are unreliable for attached storage and in containers.
    (20.2.9, DE494858)
  • Symptom:
    When generating URL for a view on dashboard the URL, the user token was not honoring a user proxy session.
    Resolution:
    With generating URL, the user token is now properly set and now honors a user proxy session.
    (20.2.9, DE494867, 32517350)
  • Symptom:
    The report generation service resource load grows when it is unable to get failed schedule email task messages.
    Resolution:
    Fixed the resource growth with the report generation service resource load grows when it is unable to get failed schedule email task messages.
    (20.2.9, DE495327, 32572242)
  • Symptom:
    After disabling the ActiveMQ web console in a fault-tolerant environment, you cannot start the data aggregator.
    Resolution:
    With this fix, after disabling the ActiveMQ web console in a fault-tolerant environment, you can now start the data aggregator.
    (20.2.9, DE495484, 32445089)
  • Symptom:
    When bootstrapping of Consul access control list (ACL) fails, it only showed an install error in Consul install logs, but the user was not made aware of this failure. It used to show that the data aggregator was successfully installed, but dadaemon service would not start due to this failure.
    Resolution:
    Updated the Consul installer to pass the install failure to its parent (device manager (DM) installer). Now an error is thrown during install/upgrade when the bootstrapping fails.
    (20.2.9, DE495793)
  • Symptom:
    In the usage data, Active Devices has a greater number than Consumed Licenses.
    Resolution:
    Update the Consumed Licenses number to count devices that do not have interfaces.
    (20.2.9, DE495884)
  • Symptom:
    In the usage data table on the
    System Status
    page, not all data sources displayed a value for Consumed Licenses items.
    Resolution:
    Update SQL to account for devices that do not have
    ContextType
    set.
    (20.2.9, DE495886)
  • Symptom:
    When looking at the service level agreements (SLA) Path card view results, the underlying table is missing Tunnel entry in the
    Parent Names
    column
    DX NetOps Virtual Network Assurance
    Viptela dashboard.
    Resolution:
    Addressed the missing Tunnel name in the
    Parent Names
    column looking in the SLA Path card view results table on the
    DX NetOps Virtual Network Assurance
    Viptela dashboard.
    (20.2.9, DE495907, 32564084)
  • Symptom:
    After java was upgraded to 1.8.0_275, when starting up
    NetOps Portal
    , the data aggregator, and the data collector, the APM agent could cause a deadlock before any application threads could be started. The application would appear to hang and not log anything to indicate the deadlock.
    Resolution:
    Updated the APM agent that
    NetOps Portal
    includes, the data aggregator, and the data collector to version 10.7.0.45 to resolve deadlock in new java version.
    (20.2.9, DE496095)
  • Symptom:
    When sending a notification trap,
    NetOps Portal
    sends it three times due to retry logic not stopping on any success.
    Resolution:
    Updated the notification trap retry logic to stop after successful send of trap.
    (20.2.9, Updated the notification trap retry logic to stop after successful send of trap)
20.2.8 Fixes
  • Symptom:
    The ribcache is not deleted successfully during upgrade before installing a new one. Observable in the ribcache folder by seeing files for both the previously installed version and the newly upgraded one.
    Resolution:
    Update a string check so that when an environment variable isn't set the check doesn't fail.
    (20.2.8, DE417203)
  • Symptom:
    The Event Manager might not correctly set the value of the URL environment variable when an alert is triggered on SDN types. The URL contains NULL instead of the SDN item.
    Resolution:
    With this fix, the Event Manager correctly sets value of the URL environment variable when an alert is triggered on SDN types. The URL contains the correct item type of the SDN item.
    (20.2.8, DE478189)
  • Symptom:
    Threshold processing in the data aggregatorcannot reliably keep up with 200+ threshold profiles, resulting in missing/delayed threshold alerts. A system test reveled the system falls behind and not recover at around 100 threshold profiles.
    Resolution:
    With this fix, the per metric family threshold profile processing has been optimized to split the list of profiles and process them in parallel to improve the speed at which the threshold profiles are processed. In most cases, the system should reliably process up to 400 threshold profiles.
    (20.2.8, DE479385)
  • Symptom:
    Old alarms are getting cleared after receiving updated.
    Resolution:
    With this fix, the Metadata information has been updated to PARTIAL.
    (20.2.8, DE482913)
  • Symptom:
    Alarms clearing not happening for CREATED alarms in the Viptela plug-in.
    Resolution:
    With this fix, you can clear alarms based on the
    cleared_events
    field.
    (20.2.8, DE485098)
  • Symptom:
    You cannot set default global search mode type (names or all) in
    NetOps Portal
    .
    Resolution:
    With this fix, you can set the initial global search mode type to names or all in
    NetOps Portal
    .
    (20.2.8, DE487299)
  • Symptom:
    NetOps Portal
    syncs all users. It doesn't determine if the user has
    CA Business Intelligence
    (CABI) access or not and only syncs those. The
    ResourceNotFoundException: Not Found
    exception seems to indicate it's trying to delete a user via jaspersoft rest pages and throwing a Not Found error. This issue arrives when deleting a user using
    NetOps Portal
    when the user has no Product Privileges for CABI.
    Resolution:
    With this fix, CABI ignores this exception and just logs it.
    (20.2.8, DE487569)
  • Symptom:
    When you use the
    Generate URL Preview
    option for the Dynamic Trend View or an On-Demand Report that is explicitly configured under My Assigned Groups, the generated URL might show no data with the following message:
    You no longer have access to this Permission Group
    .
    Resolution:
    With this fix, the generated URL now displays the report properly.
    (20.2.8, DE487782)
  • Symptom:
    If a user comments the old configuration in the WildFly
    standalone.conf
    file and then upgrades
    DX NetOps Virtual Network Assurance
    , the
    DX NetOps Virtual Network Assurance
    upgrade script pickets the commented value. The
    DX NetOps Virtual Network Assurance
    memory setting are reverted back to 4GB.
    Resolution:
    With this fix, the
    DX NetOps Virtual Network Assurance
    upgrade build script no longer considers the commented lines.
    (20.2.8, DE488261)
  • Symptom:
    When using the SilverPeak plug-in, users might see the following error in the Data Collector logs:
    Fail to find method null: java.lang.NoSuchMethodException: GetIpAddress.setPluginContext(com.torokina.tim.process.node.function.TimProcessPluginContext)
    .
    Resolution:
    With this fix, the "TimProcessPluginContext" library has been added to groovy files. Check Orchestrator's host before creating perspective. If it is an IP, add to property "ipAddressSet". If it is a hostname, do not add to the property.
    (20.2.8, DE489395)
  • Symptom:
    When sorting the
    Last Run Time
    column on the
    Manage Scheduled Reports
    page, the column sorted for string and not date time stamp.
    Resolution:
    With this fix, the
    Last Run Time
    column on the
    Manage Scheduled Reports
    page now sorts as date time stamp column.
    (20.2.8, DE489882)
  • Symptom:
    OpenAPI can log wrong URL for completing requests in the request log file.
    Resolution:
    With this fix, OpenAPI logs correct URL for completing requests in the request log file.
    (20.2.8, DE490246)
  • Symptom:
    DX NetOps Performance Management
    sends SNMP requests with an error-index of 50.
    Resolution:
    With this fix,
    DX NetOps Performance Management
    does not set max-repetitions when it sends SNMP requests.
    (20.2.8, DE490309)
  • Symptom:
    The "Available" and "Selected" UI labels on the Single Sign-On page in
    NetOps Portal
    are not localized.
    Resolution:
    With this fix, the "Available" and "Selected" UI labels are now localized.
    (20.2.8, DE490311)
  • Symptom:
    When a user deletes a group that includes group rules, the group rules do not populate when navigating to groups because the group rules name is no longer in the system.
    Resolution:
    With this fix, when navigating to a group rule that was added to a now-deleted group, the group rule is no longer listed.
    (20.2.8, DE490357)
  • Symptom:
    Users can delete a data aggregator using REST. This renders the system inoperable.
    Resolution:
    With this fix, users cannot delete a data aggregator using REST.
    (20.2.8, DE490622)
  • Symptom:
    The adminStatus and OperationalStatus was not available for interfaces.
    Resolution:
    With this fix, the adminStatus and OperationalStatus was added to interfaces.
    (20.2.8, DE491066)
  • Symptom:
    Error importing an On-Demand certification.
    Resolution:
    The internal buffer between REST operations has been cleared. With this fix, you can import On-Demand certifications.
    (20.2.8, DE491236)
  • Symptom:
    Silver Peak can return "Server returned HTTP response code: 401" and results in
    DX NetOps Virtual Network Assurance
    inventories being deleted from the data aggregator.
    Resolution:
    With this fix, when
    DX NetOps Virtual Network Assurance
    receives an HTTP error response,
    DX NetOps Virtual Network Assurance
    does not send OC message to the plug-in, and
    DX NetOps Virtual Network Assurance
    retains the inventory.
    (20.2.8, DE491762)
  • Symptom:
    DX NetOps Network Flow Analysis
    user-defined groups cannot not have rules created for them.
    Resolution:
    Modified the algorithm to hide rules for VNA Domain Groups so that the
    DX NetOps Network Flow Analysis
    user-defined group rules are not hidden.
    (20.2.8, DE492586, 32497562)
  • Symptom:
    activemqstats has an invalid password after upgrade.
    Resolution:
    With this fix, the installer updates activemq's
    jmx.password
    file if the default value is detected.
    (20.2.8, DE493225, 32532586)
  • Symptom:
    In the data aggregator Admin UI, when using the time range picker on the
    Events
    tab, you cannot use the mouse to use the time picker control in the time range picker (only the keyboard works in the time picker control drop-down).
    Resolution:
    With this fix, you can use the mouse and the keyboard to use the time picker control in the time range picker on the
    Events
    tab.
    (20.2.8, DE493545, 32534894)
  • Symptom:
    Exiting proxy tenant or proxy user throws a 404 Error.
    Resolution:
    The base url path has been changed to
    /pc/desktop/page
    . With this fix, the error is not thrown.
    (20.2.8, DE493959)
  • Symptom:
    (20.2.8) Dependency missing Error found in Consul logs during Consul ACL installation in fault-tolerant data aggregator environments, which results in the data aggregator not starting up.
    Resolution:
    With this fix, the Consul installer now uses the correct path to the required dependencies.
    (20.2.8, DE494252)
20.2.7 Fixes
  • Symptom:
    The Group scorecard trend view of baseline metrics shows date/.times in the column headers that do not match the requested report period. Instead of ending "now", they end at an earlier date/time.
    Resolution:
    With this fix, the Group Scorecard Trend view of baseline metrics now shows requested end time in column headers.
    (20.2.7, DE451592)
  • Symptom:
    When a data source synchronizes devices that are considered the same based on
    NetOps Portal
    reconciliation, a SQL exception can be thrown about duplicate key. Also, the same query is slow due to having to convert columns between ISO-8859-1 and UTF-8, and missing an index.
    Resolution:
    Updated the query failing to use DISTINCT to handle the duplicate keys. Added new mysql index, and encoded the temporary tables using UTF-8, to speed up queries.
    (20.2.7, DE473120)
  • Symptom:
    Multiple mac addresses were not supported for NSG. Some of the changed attributes in Nuage version 6.x were not certified.
    Resolution:
    With this fix, multi mac addresses for NSG are supported. You can now see NSG, virtual interface, tunnel, sla path in
    DX NetOps Performance Management
    , and alarm for those in
    DX NetOps Spectrum
    .
    (20.2.7, DE485371)
  • Symptom:
    In Network Protocol trend charts, if the average value for a metric for a protocol is different from the first protocol in the list, you would see wrong standard deviation values plotted in trend charts for that protocol.
    Resolution:
    With this fix, the standard deviation is not reset when the selection of the protocol changes from the first protocol in the list. The standard deviation is reset when the protocol is changed, so that the new values are picked and plot the trend chart.
    (20.2.7, DE485791
  • Symptom:
    Data Collector can run out of memory after a period of time due to high numbers of polling error messages being saved in memory.
    Resolution:
    The Data Collector now persists these polling error messages to disk. It can also now identify and remove some duplication messaging, which can cause unnecessary data usage.
    (20.2.7, DE487468)
  • Symptom:
    You could not copy and paste groups under a tenant's
    DX NetOps Virtual Network Assurance
    domains into another group that belongs to the same tenant.
    Resolution:
    SDN Domain groups belonged to multiple tenants, which did not follow the security model. The logic to add all SDN Domains to the Default Tenant's
    DX NetOps Virtual Network Assurance
    domains has been removed and a migration has been provided to cleanup these extraneous relationships to make all VNA Domains groups only belong to their tenant's
    DX NetOps Virtual Network Assurance
    domains.
    (20.2.7, DE487606)
  • Symptom:
    Selecting Previous Week, Previous Month, or a Custom Time in the Time Picker incorrectly sets to Yesterday.
    Resolution:
    Created a constant and increased the max range for time ranges which allows the selection of Previous Week, Previous Month, or a Custom Time.
    (20.2.7, DE487863, 32464285)
  • Symptom:
    Exception found in
    NetOps Portal
    console log when referencing site group when launching session level business hour on context page.
    Resolution:
    Fixed generated exception found in
    NetOps Portal
    console log when referencing site group when launching session level business hour on context page.
    (20.2.7, DE487865)
  • Symptom:
    Custom view when created on Dashboard with business hour profile and then saved at user level get stuck at default tenant level.
    Resolution:
    Prevented configured custom view when created on Dashboard with business hour profile and then saved at user level from getting stuck at default tenant level.
    (20.2.7, DE487867)
  • Symptom:
    The installer process fails to copy the install history file when upgrading a
    DX NetOps Virtual Network Assurance
    that is installed in a custom directory.
    Resolution:
    The installer has been updated to correctly update the
    DX NetOps Virtual Network Assurance
    install history file location after reading in the
    /opt/CA/VNA.cfg
    file from disk.
    (20.2.7, DE488019)
  • Symptom:
    SDN SLA Path metric family is missing in views under Site context pages.
    Resolution:
    Addressed scenario that SDN SLA Path metric family is missing in views under Site context pages.
    (20.2.7, DE488023)
  • Symptom:
    Horizontal Bar Chart contains unprocessed footer property when device is in maintenance and retired state.
    Resolution:
    Addressed the Horizontal Bar Chart containing an unprocessed footer property when device is in maintenance and retired state.
    (20.2.7, DE488139)
  • Symptom:
    When using
    DX NetOps Spectrum
    and
    DX NetOps Virtual Network Assurance
    Aggregator with
    DX NetOps Performance Management
    , SDWAN tunnel and slapath synced to
    NetOps Portal
    did not consolidate to their data aggregator equivalent tunnel and slapath. This is due to the
    Aggregator changing the SDN ID of the tunnel and slapath to be unique to
    DX NetOps Spectrum
    .
    NetOps Portal
    can no longer use it for consolidation. Inventory view for tunnel and slapath made it appear that there are duplicates.
    Resolution:
    Added a new option to
    NetOps Portal
    synchronization code to consolidate new tunnel and slapath on item name only. To enable this option, run in mysql: replace into netqosportal.general values('GlobalSync.SdnConsolidateOnItemName','true'); If you have duplicate tunnel and slapath when using
    DX NetOps Virtual Network Assurance
    Aggregator, contact support for the SQL script that clears the item id on
    DX NetOps Spectrum
    tunnel and slapath, so that they can be re-evaluated for consolidation.
    (20.2.7, DE488519)
  • Symptom:
    The On-Demand view option
    Table per Item with Multiple Metrics
    generates an error with not-managed metric family being reported by component level.
    Resolution:
    Corrected error with the On-Demand view option
    Table per Item with Multiple Metrics
    with not-managed metric family being reported by component level.
    (20.2.7, DE488755)
  • Symptom:
    On multi-node vertica systems, the not present items job isn't able to reliably insert into the not present items tables because they only exist on one node.
    Resolution:
    Update the not present items tables to be unsegmented so they are present on all vertica nodes.
    (20.2.7, DE489126)
  • Symptom:
    Global users cannot access tenant business hours on a group without administering the tenant of that group.
    Resolution:
    Update to load business hours options based on group tenancy instead of user tenancy.
    (20.2.7, DE489292)
  • Symptom:
    Collapsing the Events Panel or selecting alarms in Alarm Console can cause browser to hang.
    Resolution:
    Fixed the infinite loop in JavaScript which can occasionally occur when truncating the status bar in the Events table.
    (20.2.7, DE489718)
20.2.6 Fixes
  • Symptom:
    The One28T
    DX NetOps Virtual Network Assurance
    plugin is missing interface bps and util data.
    Resolution:
    Among other changes, requested interface metrics have been added to the plugin.
    (20.2.6, DE469162)
  • Symptom:
    When authentication is switched from external to local, the password fields do not activate and changes to the user cannot be saved without a password.
    Resolution:
    Added an event listener for changes to authentication type that updates the
    enablement/disablement
    password fields.
    (20.2.6, DE479577)
  • Symptom:
    With the On-Demand report
    Chart per Metric by Single Item
    view option, when reporting at the component level, item titles on chart can mismatched with graph data.
    Resolution:
    Addressed titles on chart mismatched with graph data with On-Demand report view option
    Chart per Metric by Single Item
    when reporting at the component level.
    (20.2.6, DE481318)
  • Symptom:
    DX NetOps Spectrum
    synchronization fails when there are too many IP domains.
    Resolution:
    With this fix, IP domain status requests to
    DX NetOps Spectrum
    are processed in groups of 50 or less.
    (20.2.6, DE483072)
  • Symptom:
    In systems setup with
    DX NetOps Mediation Manager
    on multiple data collectors that belong to different IP Domains, device components might not reconcile to a device in their IP Domain.
    Resolution:
    The list of devices that the
    DX NetOps Mediation Manager
    inventory manager uses and the IP domain filters has been updated.
    (20.2.6, DE483454)
  • Symptom:
    Some Cisco Meraki policy names are empty and the display name has a constraint to be notNull.
    Resolution:
    An empty/null check has been added for policy names. When this happens, the policy name is set to a default value.
    (20.2.6, DE483693)
  • Symptom:
    After installing
    DX NetOps Performance Management
    20.2.4, customer is still seeing unexpected values in the SilverPeak Orchestrator.
    NetOps Portal
    reports the Percent Packet Loss higher than the SilverPeak Orchestrator.
    Resolution:
    Updated existing polling code to grab performance poll data for the last minute of the polling interval due to minute granularity stats (the sum of SUM_PRE_LOSS and SUM_WRX_PKTS being less than 100, 0 is displayed). As a result, the report is more consistent between
    NetOps Portal
    and SilverPeak Orchestrator.
    (20.2.6, DE483893)
  • Symptom:
    Virtual interfaces are missing device display names in table grids when discovered as SNMP physical interface.
    Resolution:
    Addressed missing device display names with virtual interfaces in table grids when discovered as SNMP physical interface.
    (20.2.6, DE484511)
  • Symptom:
    When four or more metrics are selected from same metric family, there is a mismatch with number of charts selected versus number of rendered charts on pages with the On-Demand report
    Chart per Metric by Single Item
    option.
    Resolution:
    Addressed mismatch with number of charts selected versus number of rendered charts on page with On-Demand report
    Chart per Metric by Single Item
    option.
    (20.2.6, DE484714)
  • Symptom:
    Some of the virtual check point firewall devices are polled with the SNMPv3 context names.
    DX NetOps Performance Management
    can drop the context names if the there is a change related to the SNMPv3 profiles, and therefore the polled data is wrong.
    Resolution:
    Improved the process of the SNMP profile changes so that the context names are properly maintained on the virtual check point firewall items.
    (20.2.6, DE484875)
  • Symptom:
    An ArrayIndexOutOfBoundsException or NullPointerException can be thrown during the component reconciliation process which then causes the component discovery hanging.
    Resolution:
    DX NetOps Performance Management
    now properly handles the exception and the component discovery moves forward.
    (20.2.6, DE484975)
  • Symptom:
    Sections of the group editor tree with thousands of groups beneath it are timing out when expanding that part of the tree.
    Resolution:
    Reduce the number of calls to the database when loading the group editor tree.
    (20.2.6, DE485221)
  • Symptom:
    On the Monitored Devices page, the Details tab has an inefficient layout which makes it difficult to read long device names.
    Resolution:
    The Details tab on the Monitored Devices page now includes an improved page layout. The layout now uses screen real estate more efficiently and uses tooltips if information is truncated.
    (20.2.6, DE485346)
  • Symptom:
    Clicking the Report Name link on the Scheduled Reports page shows a 'You do not have sufficient rights to perform this action.' message.
    DX NetOps Performance Management
    is using a wrong SSO encryption/decryption key to decrypt the token.
    Resolution:
    Updated scheduled emails to use correct SSO encryption decryption key.
    (20.2.6, DE485380)
  • Symptom:
    Export of Device Inventory to comma-separated values (CSV) file fails when invalid character is found in output line that ends with double quote entry.
    Resolution:
    The export of Device Inventory to CSV file no longer fails when an invalid character is found in output line that ends with double quote entry.
    (20.2.6, DE485767)
  • Symptom:
    Silverpeak alarms are not cleared in
    DX NetOps Virtual Network Assurance
    .
    Resolution:
    Updated
    DX NetOps Virtual Network Assurance
    alarming for Silverpeak to query when alarm is closed. When closed,
    DX NetOps Virtual Network Assurance
    now creates a clear alarm.
    (20.2.6, DE486241)
  • Symptom:
    Expected behavior: Silverpeak device names should use the proper hostname. Actual behavior:
    DX NetOps Virtual Network Assurance
    uses the hostnames from the ../appliance/approved endpoint which per Silverpeak, is the default hostname of the applaince from the factory.
    DX NetOps Virtual Network Assurance
    should be using just the ../appliance endpoint VNA Integration Has Added Generic Named SilverPeak Devices.
    Resolution:
    The code now gets the hostname from the /gms/rest/appliance API instead of the /gms/rest/appliance/approved API.
    (20.2.6, DE486584)
  • Symptom:
    Error is seen when invoking
    service activemq stop
    on the data aggregator and data collector, leading to ungraceful shutdown.
    Resolution:
    Modified activemq scripts on data aggregator and data collector to not try to bind to JMX port 11099, since it is already open by the activeMQ process.
    (20.2.6, DE486750)
  • Symptom:
    Calendar heat chart incorrect renders business hour state for off hour period as blank none colored cell, similar to as No Data to Display.
    Resolution:
    Calendar heat chart correctly renders business hour cell that are Off-Hours in a shaded color.
    (20.2.6, DE486866)
  • Symptom:
    When upgrading
    DX NetOps Performance Management
    3.6.x or 3.7.x to 20.2.5 system, the upgrading could fail. After the upgrade, all the monitored items might not be polled. The problem is caused by some corrupted consolidated monitoring profile items. When a monitoring profile item is deleted, the deleted item ID could still be referenced by some of the consolidated monitoring profiles which then can cause the upgrade failure.
    Resolution:
    Enhanced the upgrade code to handle the corrupted consolidated monitoring profiles properly.
    (20.2.6, DE487180)
20.2.5 Fixes
  • Symptom:
    Under specific conditions some newly created
    NetOps Portal
    items at the end of current sync cycle like tenants, groups, domains might not be synced to the data source. Workaround is to perform a full sync.
    Resolution:
    With the fix, newly created
    NetOps Portal
    items at the end of current sync cycle would be synced to the data source on the next sync cycle.
    (20.2.5, DE348850, 01352680)
  • Symptom:
    DX NetOps Virtual Network Assurance
    can create a flood of both email and trap notifications after email service in configuration had been unreachable or down but returned to the normal operation state.
    Resolution:
    With the fix,
    DX NetOps Virtual Network Assurance
    should not create a flood of notifications as send email failures should be processed gracefully.
    (20.2.5, DE439091)
  • Symptom:
    Vulnerability tests against "https://<DAHost>:8582" show vulnerabilities for "LUCKY13" and "Secure Client Renegotiation".
    Resolution:
    "LUCKY13" and "Secure Client Renegotiation" vulnerabilities on data aggregator host when in https mode are resolved.
    (20.2.5, DE451369)
  • Symptom:
    Description and error messages for a couple of OOB groups still use old names.
    Resolution:
    Updated description and error messages for these OOB groups to use new names.
    (20.2.5, DE463889)
  • Symptom:
    The One28T
    DX NetOps Virtual Network Assurance
    plugin is slow to gather performance data.
    Resolution:
    Updated the One28T
    DX NetOps Virtual Network Assurance
    plugin to use GraphQL interface to query the data source for poll data. It allows us to limit the request to the metrics
    DX NetOps Virtual Network Assurance
    needs versus all the metrics.
    (20.2.5, DE474270)
  • Symptom:
    Wrong number of active interfaces are seen for a router.
    Resolution:
    Earlier implementation used 'Router Address' to filter the active interfaces causing some other router addresses to match the filter which led to interfaces of all the matching routers to be listed. 'Router Address' was used because
    DX NetOps Network Flow Analysis
    OData API did not support filtering on 'Router Id' for 'Active Interfaces. NFA OData API has been enhanced to support 'router id' and the corresponding changes to use 'Router Id' for filtering has been made in NetOps Portal.
    (20.2.5, DE474276, 32162682)
  • Symptom:
    DX NetOps Virtual Network Assurance
    installs on unsupported Java version.
    Resolution:
    A warning message which alerts while installing a Java version which is not openjdk or Oracle has been added.
    (20.2.5, DE478257)
  • Symptom:
    Unhanded Exceptions on the
    server.log
    file.
    Resolution:
    Handled the Exceptions gracefully.
    (20.2.5, DE478725)
  • Symptom:
    CTRL+clicking a menu item in the navigation menu did not open the page in a new browser window or tab.
    Resolution:
    CTRL+clicking a menu item in the navigation menu now opens the page in a new browser window or tab.
    (20.2.5, DE479025)
  • Symptom:
    On a
    NetOps Portal
    that has multiple IP addresses,
    NetOps Portal
    selects the first interface and first non-loopback IP for the
    NetOps Portal
    Service default Web Site Host value. This can lead to unreachable
    NetOps Portal
    IP used by Event Manger and users/services that contact the
    NetOps Portal
    service.
    Resolution:
    Update
    NetOps Portal
    to set the default Web Site Host by trying to determine the fully qualified hostname of
    NetOps Portal
    . If
    NetOps Portal
    cannot determine an FQHN, it falls back to first interface/first non-loopback IP. You can override by way of SsoConfig to set Remote Value for
    NetOps Portal
    Web Site Host.
    (20.2.5, DE479930)
  • Symptom:
    Data Collector out of memory due to excessive in-memory logging of poll errors.
    Resolution:
    Fixed maximum size calculation for polled errors log. Added options to persist all dcdebug logs to disk.
    (20.2.5, DE480361)
  • Symptom:
    In the upgrade scenario, --no-prompt was not handled that results in posting
    DX NetOps Virtual Network Assurance
    auth credentials again that leads to validation failure and results in warning message.
    Resolution:
    Upgrade scenario of
    DX NetOps Virtual Network Assurance
    with --no-prompt handled and
    DX NetOps Virtual Network Assurance
    existing credentials checked before posting new ones.
    (20.2.5, DE481089)
  • Symptom:
    Admin group UI does allow to modify locked group by adding or removing items.
    Resolution:
    With the fix, Admin group UI would not allow to modify locked group by adding or removing items.
    (20.2.5, DE481382)
  • Symptom:
    When new items come in to poll, if there is a bad polled item ID (NULL) in the request, a NullPointerException is thrown and it fails to start polling the additional item ID(s) after the NULL item ID. It does not schedule those polled item IDs.
    Resolution:
    Updated start polling code to handle if NULL is passed it, and print a WARN message and continue processing the non-NULL item IDs.
    (20.2.5, DE482423)
  • Symptom:
    Rule Editor column selector has empty checkbox fields.
    Resolution:
    Removed gear for column selection/sorting in the Rule Editor grid. Named last two columns in Rule Editor.
    (20.2.5, DE482432)
  • Symptom:
    Users that did not have permission to administrate groups can run rules on those groups.
    Resolution:
    Fixed code to grey out the
    Run Rules
    button. Users that cannot administrate groups cannot run rules on those groups.
    (20.2.5, DE482434)
  • Symptom:
    When the not present items process ran, a recurring exception was appearing in the logs for items that are marked as not present and do not have a metric table because there was never any polled data.
    Resolution:
    When putting together a set of metric tables to check for metric data on not present items, a query is run to filter out any tables that are not in the database.
    (20.2.5, DE482445)
  • Symptom:
    DX NetOps Network Flow Analysis
    admin pages are not getting loaded with
    DX NetOps Network Flow Analysis
    10.0.5.
    Resolution:
    NetOps Portal
    now looks for the new property (ODataApiUrl) to read OData URL from
    DX NetOps Network Flow Analysis
    , and uses it if available. If not, it looks for older property (ODataURL) and uses it. Falling back to older property lets
    NetOps Portal
    continue to work with older versions of
    DX NetOps Network Flow Analysis
    .
    (20.2.5, DE482726)
  • Symptom:
    Running the
    testssl.sh
    script against the (Fault Tolerant) data aggregator Proxy server while configured for HTTPS shows vulnerabilities for cipher order, SWEET32 and LUCKY13.
    Resolution:
    The data aggregator proxy's cipher suites, when configured for HTTPS, have been adjusted so that running the
    testssl.sh
    script no longer shows vulnerabilities.
    (20.2.5, DE482977)
  • Symptom:
    In fault-tolerant environments using RHEL6, the Proxy service (
    daproxy
    ) fails to start and shows "traefik error: error while building entryPoint http" in the log.
    Resolution:
    On RHEL6, the
    daproxy-init.sh
    script correctly references the
    daproxy.toml
    file.
    (20.2.5, DE483212)
  • Symptom:
    Custom Horizontal Bar chart when configured for SD-Wan metrics, metric families Tunnel or SLA Path, hyperlink for chart redirects to home page.
    Resolution:
    Addressed issue with hyperlink that redirected to home page instead of context page. The custom Horizontal Bar chart when configured for SD-Wan metrics, metric families Tunnel or SLA Path, correctly redirects user to context page.
    (20.2.5, DE483606)
20.2.4 Fixes
  • Symptom:
    Python 2 is end-of-life (EOL), and there are a few admin/debug Python 2 scripts shipped with the data aggregator/repository.
    Resolution:
    Updated the Python scripts to run against Python 3. You must now install Python 3 in Linux to run these scripts.
    (20.2.4, DE440532)
  • Symptom:
    The
    DX NetOps Virtual Network Assurance
    Viptela plugin was throwing database-related exceptions in the
    Server.log
    file.
    Resolution:
    The
    DX NetOps Virtual Network Assurance
    Viptela plugin does not throw database-related exceptions in the
    Server.log
    file anymore.
    (20.2.4, DE460271)
  • Symptom:
    The procedure for configuring the Proxy service (
    daproxy
    ) and the Consul service as HTTPS on a fault-tolerant data aggregator is incomplete and confusing. Configuring the DAProxy service from the proxy server to data aggregators yields certificate_unknown errors.
    Resolution:
    DX NetOps Performance Management
    20.2.4 now supports Træfik 2.2.8. This version resolves certificate errors between the Proxy service and the backing data aggregators. The procedures for configuring the Træfik connection as HTTPS have been rewritten and clarified.
    (20.2.4, DE460814)
  • Symptom:
    Items sent over from
    DX NetOps Virtual Network Assurance
    of type MANAGEMENT_SYSTEM are treated as groups instead of devices.
    Resolution:
    Update the NetOps mapped type for MANAGEMENT_SYSTEMs sent from
    DX NetOps Virtual Network Assurance
    .
    (20.2.4, DE463352)
  • Symptom:
    When a Data Collector upgrade that has been initiated from the UI has failed, the Data Collector remains upgrading.
    Resolution:
    Update Data Collector status to failed upgrade if a registration message is not received within 10 minutes of initiating an upgrade through the UI process.
    (20.2.4, DE470798)
  • Symptom:
    When a poll value delta is calculated to be greater than max positive 32-bit or 64-bit integer, the poll response is dropped only if it happens during a rollover. This happens when an SNMP agent returns a nearly impossible delta that could happen within the poll cycle.
    Resolution:
    Changed the SNMP delta calculation code to handle these very large deltas even when not in a rollover situation. The max delta is controlled via configuration.
    For more information about how to increase or decrease the large 32-bit or 64-bit delta value used in this check, see Configure Counter Behavior.
    (20.2.4, DE472708)
  • Symptom:
    The
    DX NetOps Virtual Network Assurance
    Viptela plugin is not closing the vManage connections properly after use.
    Resolution:
    With this fix, the
    DX NetOps Virtual Network Assurance
    Viptela plugin now closes the vManage connections properly after use.
    (20.2.4, DE472718)
  • Symptom:
    The following behaviors are seen while using the ACI Console dashboard. 1. Application profile topology incorrectly shows endpoint groups that are associated with other application profiles; 2. Application profile topology shows more endpoint groups than the application profile hierarchy; 3. When navigating between an application profile and its endpoint groups in the topology, the Health Score on the application profile item disappears; 4. The topology fails to load initially when navigating to the ACI Console from the context of an ACI leaf switch.
    Resolution:
    The following changes have been implemented to address the identified issues:
    • Endpoint Groups are now distinguished between normal and L2/L3 External. This change now allows the distinction between L2/L3 External Endpoint groups in the ACI Console topology and has resolved the issue where unrelated Endpoint Groups were being incorrectly pulled into the application profile topology.
    • The Health Scores associated with topology parents are now preserved when navigating in the ACI Console. Using the ACI Console link on the Context page of an ACI Leaf/Spine switch no longer fails to load the topology for the selected item. After upgrading from a release prior to 20.2.3, perform the following on your ACI
      DX NetOps Virtual Network Assurance
      Gateways to fully take advantage of the new features.
      These steps cause the inventory of your
      DX NetOps Virtual Network Assurance
      Gateways to be re-evaluated in the data aggregator.
      1. Navigate to Administration, Monitored Items Management,
        DX NetOps Virtual Network Assurance
        Gateways Page.
      2. For each of your ACI
        DX NetOps Virtual Network Assurance
        Gateways, select
        Edit
        , set the
        Administration Status
        to
        Down
        , and then save the changes.
    (20.2.4, DE473532)
  • Symptom:
    userName of
    DX NetOps Virtual Network Assurance
    UI accepting spaces.
    Resolution:
    Added validation to restrict spaces in userName.
    (20.2.4, DE475474)
  • Symptom:
    SNMP discovered Network Interfaces that have been reconciled with
    DX NetOps Virtual Network Assurance
    discovered interfaces are deleted when the associated
    DX NetOps Virtual Network Assurance
    -discovered item is deleted.
    Resolution:
    DX NetOps Performance Management
    has been updated to prevent SNMP discovered Network Interfaces from being removed when an associated
    DX NetOps Virtual Network Assurance
    -discovered Interface is deleted.
    (20.2.4, DE476082)
  • Symptom:
    "No data to display" after upgrading to
    DX NetOps Performance Management
    3.7.14.
    Resolution:
    Added ETL health check to the
    dr_validate.sh
    script to detect ETL issues before upgrade.
    (20.2.4, DE476111)
  • Symptom:
    Users are not able use the Type Catalog web service to import Metric Family definitions which use the
    Pollable.Indexes
    attribute instead of
    DeviceComponent.IndexList
    . It is rejected with a parsing error.
    Resolution:
    Modified the Type Catalog web service to support the
    Pollable.Indexes
    attribute.
    (20.2.4, DE476319)
  • Symptom:
    DX NetOps Virtual Network Assurance
    orgVsConnectedDevicesFile during Versa Inventory poll does not get updated.
    Resolution:
    With this fix, the file is now updated during the inventory poll.
    (20.2.4, DE476346)
  • Symptom:
    Non-application users are able to login to the
    NetOps Portal
    MySql database without providing a password.
    Resolution:
    Update
    NetOps Portal
    install script to remove anonymous user from the MySql database.
    (20.2.4, DE476790)
  • Symptom:
    OOB groups under all old tenants displayed old group names.
    Resolution:
    Added upgrade script to update OOB group names of groups that still use old group names.
    (20.2.4, DE477368)
  • Symptom:
    In alarm details panels, links are not shown as operable controls.
    Resolution:
    In alarm details panels, links are now shown as operable controls.
    (20.2.4, DE477700)
  • Symptom:
    ETL failures might occur if multiple Data Aggregators are or previously have been running simultaneously while using the same Data Repository schema instance. This results in NetOps Portal dashboards showing no data or not showing data for recently discovered items. This might occur by accidentally using the same Data Repository information when installing two data aggregators (that are not intended for Disaster Recovery) or when migrating the Data Aggregator to a new system and both the old and new data aggregator are running and the Data Repository is not blocking access to the old Data Aggregator.
    Resolution:
    To protect the Data Repository, the data aggregator now verifies that no other data aggregator is attached to the same Data Repository schema instance during the data aggregator startup process. If a data aggregator detects that another data aggregator is actively using the Data Repository, it shuts down immediately and log information to the
    shutdown.log
    file as to why it has shut down. A long-running data aggregator takes precedence over a newly started data aggregator, and the newly started data aggregator shuts down while the long-running data aggregator remains running.
    (20.2.4, DE477749)
  • Symptom:
    OC is skipping processing of few files on failure scenario.
    Resolution:
    Fixed issue in OC file processing.
    (20.2.4, DE477816)
  • Symptom:
    After customizing a view, any attempts re-edit the view does not launch view settings dialogue until after the page is refreshed.
    Resolution:
    Addressed issue that after editing a view, the user is unable make subsequent edited to view configuration until after the page is refreshed.
    (20.2.4, DE477881)
  • Symptom:
    The
    dr_validate.sh
    script requests linux user password during database connectivity testing.
    Resolution:
    Modified database connectivity check to use existing passwordless ssh.
    (20.2.4, DE477938)
  • Symptom:
    Packet loss value greater than sum of packets.
    Resolution:
    Added a condition in the
    DX NetOps Virtual Network Assurance
    plugin. If the traffic is less than 100, packet loss displays "0".
    (20.2.4, DE478053)
  • Symptom:
    Some rate records have incorrect tstamp value in the rate tables in the Data Repository (for example, 2 records for same item has the same tstamp). This incorrect tstamp value is sent in error by the Data Collector.
    Resolution:
    Made Data Collector variable that sets the cycle timestamp on poll responses volatile so it is read correctly on all threads.
    (20.2.4, DE478242)
  • Symptom:
    Ctrl+Click on chart items (for example, entries in the chart legend) that open the clicked item opens the link in the same window (replaces the page). Ctrl+Click should open the link in a new browser window (or tab).
    Resolution:
    Ctrl+Click on chart items (for example, entries in the chart legend) now opens the link in a new browser window (or tab).
    (20.2.4, DE478277)
  • Symptom:
    ArrayIndexOutOfBounds exception while processing the tunnel response.
    Resolution:
    OK Tunnel name: to_CO-GBINTX1-WOAGG03_APACBBL2-APACBBL2BAD Tunnel name: to_JPNI418BRWOBR001_APAC_WAN-APAC_WAN (the extra underscores (_) cause an issue with the parsing as
    NetOps Portal
    gets back APAC and tries to split it on dash (-).
    (20.2.4, DE478839)
  • Symptom:
    Output of some Open API queries in CSV format might include extra columns, and device information might be missing in some rows.
    Resolution:
    With this fix, output of Open API queries do not have extra empty columns, and device information is correctly repeated whenever it is needed.
    (20.2.4, DE478981)
  • Symptom:
    vEdge Interfaces that have non-unique private IP addresses are being incorrectly reconciled within
    DX NetOps Virtual Network Assurance
    . This leads to missing interface and tunnel items and also interfaces and tunnels being associated with the wrong devices.
    Resolution:
    The
    DX NetOps Virtual Network Assurance
    Viptela plugin has been updated to no longer use the private IP of an interface as a means to uniquely identify it. This allows the missing interfaces and tunnels to be created, and resolves the issue with items being associated with the wrong devices.
    (20.2.4, DE479272)
  • Symptom:
    DX NetOps Virtual Network Assurance
    sets the Unique ID to the PK ID, but this is not unique across deployments (with multiple Orchestrators) so the IP address matching is bypassed.
    Resolution:
    The serial number is appended to the instance ID.
    (20.2.4, DE479296)
  • Symptom:
    Unable to identify a user's permission group through REST to be able to set the user's default group to
    My Assigned Groups
    .
    Resolution:
    Add permission group information to user REST endpoint.
    (20.2.4, DE479547)
  • Symptom:
    Cannot add items to groups within the User Defined Groups under the
    DX NetOps Network Flow Analysis
    data source inventory in
    NetOps Portal
    .
    Resolution:
    With this fix, users can add items to groups within the User Defined Groups under the
    DX NetOps Network Flow Analysis
    data source inventory in
    NetOps Portal
    .
    (20.2.4, DE479574)
  • Symptom:
    When SSO is running on https/443 and SAML2 is being used, SSO fails to validate the SAML2 Assertion, and fail to log in. Also, if user overrides SSO Virtual Directory, some SSO URLs are made with wrong path, as they were hard coded to use /sso.
    Resolution:
    Updated the validation code to handle when the assertion is coming in with https/443 or https/no port. Both are acceptable. Also, updated the various places SSO URLs are generated to now use the SSO Virtual Directory setting in SsoConfig.
    (20.2.4, DE479656)
  • Symptom:
    Sometimes there are duplicate entries in the Help drop-down menu.
    Resolution:
    Validate that the help menu has been created. If it exists, do not re-create the Help menu and drop-down items.
    (20.2.4, DE479752)
  • Symptom:
    The ACI Console fails to load the topology when selecting certain items.
    Resolution:
    The ACI Console logic has been updated to more gracefully handle incorrectly formatted Open API responses.
    (20.2.4, DE480372)
20.2.3 Fixes
  • Symptom:
    Progress bars and loading indicators in the user interface did not have aria attributes set on them to make them visible to screen readers.
    Resolution:
    Progress bars and loading indicators in the user interface now  have aria attributes set on them to make them visible to screen readers.
    (20.2.3, DE434593)
  • Symptom:
    Disclosures (blocks of text that hide/show)  in the user interface did not  have aria attributes set on them to make them visible to screen readers.
    Resolution:
    Disclosures (blocks of text that hide/show)  in the user interface now  have aria attributes set on them to make them visible to screen readers.
    (20.2.3, DE434594)
  • Symptom:
    VNA Domains
    is not translated for non-EN users.
    Resolution:
    With this fix,
    VNA Domains
    is correctly translated into French and Japanese.
    (20.2.3, DE463156)
  • Symptom:
    When navigating to the Context Page of a Service Chain Item, the Service Chain Topology graph is left blank.
    Resolution:
    When navigating to the Context Page of a Service Chain Item, the Service Chain Topology graph has the correct diagram with all the correct images.
    (20.2.3, DE465512)
  • Symptom:
    When the user sorts on the 'Last Flow' column in 'All Interfaces' page, the sorting happens on string format of the date rather than on epoch time.
    Resolution:
    To avoid sorting on String format of date, an invisible column is created holding the epoch time in long format which is sorted when the user sorts on the last flow column.
    (20.2.3, DE470887)
  • Symptom:
    The
    DX NetOps Virtual Network Assurance
    Installer does not maintain an
    install.history
    file that can be helpful to understand when upgrades occurred, and which versions have been installed.
    Resolution:
    The installer has been updated to create and maintain a history file to track
    DX NetOps Virtual Network Assurance
    installations/upgrades. The
    install.history
    file exists in the base product directory (for example,
    /opt/CA/VNA/install.history
    ).
    (20.2.3, DE471049)
  • Symptom:
    The
    System Status
    page in
    NetOps Portal
    does not show the backend data aggregators (it only shows the Proxy service (
    daproxy
    )) in fault-tolerant environments that are HTTPS-enabled.
    Resolution:
    NetOps Portal
    was not recognizing that the Consul service is configured for HTTPS when calling Consul rest services.
    NetOps Portal
    and the data aggregator now recognize when Consul is configured for fault tolerance and HTTPS is enabled, so
    System Status
    page now shows the data aggregators.
    (20.2.3, DE471182)
  • Symptom:
    On a system configured for fault tolerance, /odataquery points to the active data aggregator instead of the Proxy service (
    daproxy
    ).
    Resolution:
    With this fix, on a system configured for fault tolerance, /odataquery now points to the Proxy service (
    daproxy
    ).
    (20.2.3, DE471203)
  • Symptom:
    Removing Proxy port field from Viptela Config is causing NPE in the
    Server.log
    file.
    Resolution:
    Added additional checks for NPE in the
    DX NetOps Virtual Network Assurance
    server.log
    file.
    (20.2.3, DE473370)
  • Symptom:
    Active access points are reported incorrectly.
    Resolution:
    Active access points filed in broker code are no longer behaving like static.
    (20.2.3, DE473478)
  • Symptom:
    End of
    DX NetOps Virtual Network Assurance
    installation, the ReadMe is still pointing to docops.ca.com.
    Resolution:
    Updated to point to the correct location of the documentation on techdocs.broadcom.com.
    (20.2.3, DE473504)
  • Symptom:
    Observed exceptions in oc logs while query for events in network where the specific deviceType does not exists.
    Resolution:
    Before query for events in network for any productType its existence is checked.
    (20.2.3, DE473799)
  • Symptom:
    When you click an item in the Cisco ACI Console topology view that does not have a topology (for example, Vswitch and Contracts), the loading symbol remains indefinitely, even though nothing is loading.
    Resolution:
    Updated ACI Console to have only a few items be clickable.
    (20.2.3, DE473842)
  • Symptom:
    When configured to use fixed context items, device or interface, with On-Demand Report or Dynamic Trend View if the items profile cannot be determined, as in retired device, configuration warning message is shown when there is no data to display.
    Resolution:
    No data to display is displayed when there is no metric data to report with with fixed context items with On-Demand Report and Dynamic Trend View. Previously when configured to use fixed context items, device or interface, if the item metric profile cannot be determined view showed configuration warning.
    (20.2.3, DE474023)
  • Symptom:
    In the data aggregator
    karaf.log
    file, there can be massive warning messages generated from the Event Manager on the CPU and Memory component items due to Syncable facet being mistakenly attached to them.
    Resolution:
    Improved the component discovery not to create Syncable facet on the CPU and Memory components.
    (20.2.3, DE474142)
  • Symptom:
    An exception is thrown for a Threshold Profile ending with a percent (ie. "95%" ) when you click on it in the Threshold Profiles tab on the  Monitored Devices page.
    Resolution:
    Fixed issue when a Threshold Profile ending with a percent (ie. "95%" ) threw an exception.
    (20.2.3, DE474143)
  • Symptom:
    While installing
    DX NetOps Virtual Network Assurance
    the end timestamp is displaying as dd_mm_yyyy_hh_mm_ss instead of actual timestamp.
    Resolution:
    Display the actual end timestamp.
    (20.2.3, DE474261)
  • Symptom:
    CARE files for the Data Aggregator and Data Collector no longer include log files and other important information after installing version 20.2.x.
    Resolution:
    Update the CARE script to look for the updated product name.
    (20.2.3, DE474321)
  • Symptom:
    An insufficiently sized thread pool leads to a WARN message to be logged for a mis-fired Poll Item or Group ETL job every hour when the DIM Item ETL is running at the same time.
    Resolution:
    The ETL scheduler's thread pool size was increased and made configurable.
    (20.2.3, DE474462)
  • Symptom:
    "No data to display" after upgrading to
    DX NetOps Performance Management
    3.7.14.
    Resolution:
    Added a new
    etlHealth.sh
    script to the upgrade process to detect ETL issues before upgrade.
    (20.2.3, DE474520)
  • Symptom:
    There is no indication of what version of CE is installed.
    Resolution:
    Update the CE installer to write the version when installing.
    (20.2.3, DE474889)
  • Symptom:
    Dynamic Trend View is not properly suppressed on Device Context Page when configured within the Dashboard Editor.
    Resolution:
    Addressed issue that the Dynamic Trend View is not properly suppressed on Device Context Page when configured within the Dashboard Editor.
    (20.2.3, DE474985)
  • Symptom:
    The Add Data Source dialog showed incorrect options when adding a CA Business Intelligence Data Source.
    Resolution:
    The Add Data Source dialog shows the correct options when adding a CA Business Intelligence Data Source.
    (20.2.3, DE475210)
  • Symptom:
    Multiple records with the same item_id and facet_id value pairs are present in the item_facet table in the Data Repository. There are internal workflows in the Data Aggregator that can result in the same facet being added to the same item in a single database request.
    Resolution:
    The item repository data base layer now removes duplicate item_facet records when inserting a single batch.
    (20.2.3, DE475453)
  • Symptom:
    After running the
    NetOps Portal
    disaster recovery script, the new Event Manager IP might not be sent to Data Aggregator due to timing between EM synchronization and event poller threads.
    Resolution:
    Updated
    NetOps Portal
    disaster recovery script to update the DB field, used for the EM URL sent to the Data Aggregator during re-registration, with the new EM IP address. This allows the event poller thread to see it on startup and send the correct EM URL to Data Aggregator.
    (20.2.3, DE475891)
  • Symptom:
    Odata count query on the metricfamilyhistory entity with a filter might return incorrect count of entities.
    Resolution:
    With this fix, odata count query on the metricfamilyhistory entity with a filter now returns correct count of entities.
    (20.2.3, DE476454)
  • Symptom:
    The "Détection rapide des unités" ("Quick Discovery") page is blank for French users.
    Resolution:
    The "Détection rapide des unités" ("Quick Discovery") page displays correctly for French users.
    (20.2.3, DE476675)
20.2.2 Fixes
  • Symptom:
    In a trend view that supports zoom, you cannot zoom in using the keyboard (you could only zoom using the mouse).
    Resolution:
    In a trend view that supports zoom, you can now zoom into the chart using the keyboard. Pressing the space bar while an element in the chart has focus marks the start of the zoom. After using the left/right arrow keys to move focus to another part of the chart, pressing the space bar again zooms into the selection.
    (20.2.2, DE406325)
  • Symptom:
    Grids with editable fields in them such as the final pane of the user definition wizard do not support keyboard access or work with screen readers.
    Resolution:
    Grids with editable fields in them such as the final pane of the user definition wizard now can be used via the keyboard and work with screen readers.
    (20.2.2, DE406328)
  • Symptom:
    The refresh icon is missing from some data aggregator Admin pages grids.
    Resolution:
    Add the code to display the missing refresh icon in all data aggregator Admin pages that require this grid refresh.
    (20.2.2, DE416639)
  • Symptom:
    The Neighbor Topology in the Alarm Console has some nodes cut off in Firefox. logy tab. The nodes drawn are over to the left and cut off.
    Resolution:
    Modified the d3 code to arrange the nodes slightly so that they are not cutoff in Firefox.
    (20.2.2, DE431384)
  • Symptom:
    Traps generated for events on Tunnel components do not contain all event properties.
    Resolution:
    Improved logging and error checking in trap sender.
    (20.2.2, DE431603)
  • Symptom:
    The Create/Edit User and Create/Edit Notification wizards are missing some aria attributes that identify them as wizards to screen readers.
    Resolution:
    The Create/Edit User and Create/Edit Notification wizards now have additional information in them to make them easier to use with screen readers.
    (20.2.2, DE434592)
  • Symptom:
    If you can capture the cookies from a
    NetOps Portal
    session, then you can use the cookies to impersonate that user even after they have logged out.
    Resolution:
    When the user logs out, the cookies are invalidated and so can't be used to impersonate that user.
    (20.2.2, DE438456)
  • Symptom:
    OData API is fetching old metric data when start time and end time equals ZERO.
    Resolution:
    OData API now returns empty data when start time and end time equals ZERO.
    (20.2.2, DE442822)
  • Symptom:
    Data aggregator failed over to the standby data aggregator with no clear indicator in the logs about why the decision was made to fail the over to the standby.
    Resolution:
    Connection and read timeouts have been added to the data aggregator ActiveMQ and REST status checks. Additionally, the Consul Extension logging has been updated to be more verbose when a system that is currently the active data aggregator goes down and a fail-over occurs.
    (20.2.2, DE448360, 31918553)
  • Symptom:
    When the browser window width is less than 1024 pixels, the user interface is clipped on the left and none of the controls (including a scroll bar) can be manipulated.
    Resolution:
    When the browser window width is less than 1024 pixels, the user interface now displays a horizontal scroll bar at the bottom of the window which allows all of the interface to be accessed. Elements within the user interface (such as dialog boxes) also now support horizontal scroll bars if elements are clipped.
    (20.2.2, DE450132)
  • Symptom:
    Old RIB document files can build up in the
    NetOps Portal
    /tmp/ribcache
    directory.
    Resolution:
    NetOps Portal
    now cleans up the old version(s) of a RIB document file when a new version is available.
    (20.2.2, DE452506)
  • Symptom:
    When TransientDBConnection logging is set to debug, SQL statements with passwords are logged.
    Resolution:
    Update logger to sift out SQL with passwords.
    (20.2.2, DE456484)
  • Symptom:
    The REST endpoint requesting the SNMPv3 EngineID every time returns a new SNMPEngineID that is one that is not much used in traps.
    Resolution:
    With this fix, the REST endpoint requesting the SNMPv3 EngineID returns the correct SNMPEngineID that is one that is much used in traps.
    (20.2.2, DE457958)
  • Symptom:
    The Group Editor's Group Description gets stuck on the invalid description if over 255 chars long.
    Resolution:
    The Group Editor allows the user to modify a description that is over 255 characters.
    (20.2.2, DE458149)
  • Symptom:
    When discovering Check Point firewall virtual systems with context support, many virtual system items are duplicated with empty context names.
    Resolution:
    Enhanced the virtual system validation process. The virtual systems that are improperly configured with empty context names are no longer discovered.
    (20.2.2, DE461334)
  • Symptom:
    8443 HTTPS is enabled by default in
    DX NetOps Virtual Network Assurance
    , though HTTPS is not supported.
    Resolution:
    Disabled HTTPS port on wildfly.
    (20.2.2, DE462717)
  • Symptom:
    On-Demand, view option
    Chart per item with multiple metrics
    when applying Metric Calculate level by Device the sort order is not being honored.
    Resolution:
    Addressed issue with On-Demand, view option
    Chart per item with multiple metrics
    when applying Metric Calculate level by Device the sort order is not being honored.
    (20.2.2, DE464964)
  • Symptom:
    Data Aggregator is unresponsive to RIB, REST, or any other request, but java memory usage/garbage collection is fine. Could be a deadlock situation between a couple tasks the data aggregator is running. There is a deadlock possibility when doing a REST/UI delete, change detection, discovery profile running, and an OData call that filters on groups.
    Resolution:
    Updated the OData filter code to negate the possibility of the deadlock situation.
    (20.2.2, DE464968)
  • Symptom:
    BST Feature update task cannot complete due to incorrect logic in BST Feature Update Task Builder (race condition). 2020-06-03 20:20:03,614 WARN (EE-ManagedThreadFactory-default-Thread-112) [OC_BROADVIEW_PLUGIN] BSTFeatureTaskBuilder$SimpleBSTFeatureUpdateTask 105 Timeout occurs for BST Feature Configuration Update thread, timeout value = 90000.
    Resolution:
    ManagedScheduledExecutorService was replaced by ScheduledThreadPoolExecutor with a fixed coreThread number. It allows to control thread pool size for scheduled tasks and can help avoid potential thread problems (unexpected growth. etc.) 1. Timeouts for tasks were changed according to plugin config variables; 2. Optimized AlarnClearTaskBuilder logic - removed supervisor thread such as plugin always used only one thread to clear all alarms; added CountDownLatch's logic to control alarm clear thread by a timeout; 3.Implemented new logic for BST Feature Update task (for example, task builder).
    (20.2.2, DE465379)
  • Symptom:
    An OData query might not return device information in expand when it starts from metric family/component, for example:
    portmfs?$expand=device
    Resolution:
    An OData query now returns device information in expand when it starts from metric family/component for example:
    portmfs?$expand=device
    (20.2.2, DE465743)
  • Symptom:
    Open API in some circumstances might not honor tenants boundaries.
    Resolution:
    With this fix, Open API now always honors tenant boundaries.
    (20.2.2, DE466422)
  • Symptom:
    When discovering Cisco switch's Environment sensors, only one of the relevent metric families is discovered; or, all of the environmental sensors metric families, but some have no components.
    Resolution:
    Improved discovery logic for Cisco Environmental Sensor vendor certs. Added new MVEL method that allows discovery expressions to scan all table entries for an OID, instead of only the first entry.
    (20.2.2, DE466858)
  • Symptom:
    On the System Health page, when you page to the next page in a table the section is collapsed each time.
    Resolution:
    Instead of setting the collapsed property to be purely based on the status of the section, we're also taking into account the current collapsed state.
    (20.2.2, DE467043)
  • Symptom:
    When proxying as a user who uses a different Locale, the Group Rule Editor shows incorrect translations in its group selector.
    Resolution:
    Modified group selector to get locale from active user.
    (20.2.2, DE467052)
  • Symptom:
     Scheduling "All Pages of multiple page views" for the On-Demand report
    Per metric by single item
    option, the PDF output combines multiple metrics the trend charts.
    Resolution:
    Fixed issue when scheduling the On-Demand report
    Per metric by single item
    option using "All Pages of multiple page views" report the PDF output combines multiple metrics the trend charts.
    (20.2.2, DE467175)
  • Symptom:
    The responsiveness of the ACI Console dashboard has been improved by updating the ACI Console to request data for multiple items at a time. This should prevent the dashboard from taking excessive time to load when a large number of switches are part of the topology.
    Resolution:
    The ACI Console can take up to a minute to respond after clicking on one of the icons in the hierarchy. The extended time that it takes to load the topology is ultimately based on number of switches that show up in the topology view on the right.
    (20.2.2, DE467188)
  • Symptom:
    The ACI console displays non-ACI User Domains in the hierarchy.
    Resolution:
    The ACI console has been updated to display only user domains that contain ACI technology group. By having the user domains in data aggregator store the information about the technology groups,
    NetOps Portal
    can directly fetch user domains that contain ACI.
    (20.2.2, DE467199)
  • Symptom:
    When installing/upgrading
    NetOps Portal
    , the data aggregator, or the Proxy service (
    daproxy
    ), and there is 1 private IP address and 1 public IP address on the machine, the installer does not prompt for which IP address to use for consul to bind and listen on. It instead just uses the private IP address.
    Resolution:
    Updated the installers to ask if there is 1 private and any number of public IP addresses.
    (20.2.2, DE467204)
  • Symptom:
    The initial state of the sections displayed in the new Administration Group Editor was confusing as some sections were initially uncollapsed and some sections were collapsed.
    Resolution:
    The initial state of the sections displayed in the new Administration Group Editor is now consistent with all sections except Properties initially collapsed. As before, excepting the Items section, as you move between groups (or pages of the UI), your configuration of what is expanded and collapsed is maintained throughout the user session.
    (20.2.2, DE467211)
  • Symptom:
    Two jre directories are created during installation of
    NetOps Portal
    .
    Resolution:
    Update the installer sub-module to no longer install the extra JRE.
    (20.2.2, DE467362)
  • Symptom:
    When selecting SD-Wan Tunnel/App Path metrics By Component level with the Scorecard Trend might be missing component items.
    Resolution:
    When selecting SD-Wan Tunnel/App Path metrics By Component level with the Scorecard Trend always render component items.
    (20.2.2, DE467610)
  • Symptom:
    SDWan Performance and Baseline charts show spikes on trend lines, chart renders with clutter when resolution is under 30 minutes.
    Resolution:
    With SDWan trend charts are forced to use 30 minute resolution when time range is two more hours to eliminate spikes on trend lines that that clutters rendered charts.
    (20.2.2, DE467612)
  • Symptom:
    DX NetOps Virtual Network Assurance
    is sending multiple IP addresses as the outofbandmanagment IP address on VM.
    Resolution:
    DX NetOps Virtual Network Assurance
    now sends the correct IP as the outofbandManagment IP address. .
    (20.2.2, DE467747)
  • Symptom:
    Zooming did not work in trend charts (when it was allowed).
    Resolution:
    Zooming now works in trend charts that support it.
    (20.2.2, DE468020, 32162368)
  • Symptom:
    When running Alarm Console against
    DX NetOps Spectrum
    10.4.x+ (20.2.x), it might time out or throw an error when not using a custom group. This is because the landscape group synchronized from
    DX NetOps Spectrum
    to
    NetOps Portal
    changed and Alarm Console did not take that into account. It uses global collection groups, and if no global collections are defined, it uses all synced
    DX NetOps Spectrum
    items.
    DX NetOps Spectrum
    also has a limit on 150 comparisons in the webservice used for Alarm Console, so if too many global collections are passed, it fails.
    Resolution:
    Updated the logic to check for the old and new
    DX NetOps Spectrum
    landscape group IDs. By using landscape group,
    DX NetOps Spectrum
    can return all events for the landscape group members quicker than specifying all items in groups. In addition, to resolve the issue with 150 comparisons, up to 150 comparisons are added to the webservice request, and a message is printed to the
    PCService.log
    file when more than 150 comparisons is hit.
    (20.2.2, DE468346)
  • Symptom:
    During installation of the data repository, the I/O scheduler is always set to the same value regardless of type of storage.
    Resolution:
    Update the data repository installation process to allow the I/O scheduler to be updated to a different value based on storage type.
    (20.2.2, DE468411)
  • Symptom:
    When device is discovered that are related to F5 metric the context tabs for F5, available on Switch Context page, are not available on the Device Context page. When preference is to not associate the device as a switch device, requires manual creating F5 Tabs on the Device Context page.
    Resolution:
    When F5 related devices are discovered as generic device and prefer to not associate the device as a switch. Provide an automated script to import context tabs for F5, available on Switch Context page, to the Device Context page.
    (20.2.2, DE468840)
  • Symptom:
    During
    NetOps Portal
    and Data Repository install, the disaster recovery scripts that might have been customized are overwritten without a backup.
    Resolution:
    Update the
    NetOps Portal
    and Data Repository installers to make backups of the disaster recovery scripts before setting down updated versions.
    (20.2.2, DE468863)
  • Symptom:
    Group Admin Item section could become non responsive after it shows "no items were added to the group" message.
    Resolution:
    Group Admin Item section continues to work as expected after it shows "no items were added to the group" message.
    (20.2.2, DE469448)
  • Symptom:
    The Group Editor's rule editor does not allow you to edit or create new rules.
    Resolution:
    Fixed missing comma in
    .jsp
    file.
    (20.2.2, DE469478)
  • Symptom:
    Manage Groups admin page is missing Device Component Items section.
    Resolution:
    With this fix, the Manage Groups admin page properly displays Device Component Items section.
    (20.2.2, DE469491)
  • Symptom:
    The
    DX NetOps Virtual Network Assurance
    SilverPeak Plugin - 401 Invalid username or password specified.
    Resolution:
    The logintype has been fixed - value 2 for TACACS authentication for Silver Peak.
    (20.2.2, DE469607)
  • Symptom:
    Card view on SD-Wan Tunnel Statistics dashboard page does not align with site count being reported with the Geo-Map View.
    Resolution:
    Addressed issue with the number of Site being reported by the Card view on SD-Wan Tunnel Statistics dashboard page, not aligning with site count in Geo-Map View.
    (20.2.2, DE469805)
  • Symptom:
    The Open API might not return all groups in expand clause for queries starting from configuration entity types (devices,interfaces,etc.) if the total number of groups is more then a hundred.
    Resolution:
    With this fix, the Open API returns all groups in expand clause for queries starting from configuration entity types (devices,interfaces,etc.) regardless of the number of groups.
    (20.2.2, DE470008)
  • Symptom:
    Multi-View Trend for Interface Utilization, Discards and Errors when configured to use bi-directional metrics, In and Out, might render with 'No Data to Display'.
    Resolution:
    Fixed the 'No Data to Display' problem with Multi-View Trend for Interface Utilization, Discards and Errors when configured to use bi-directional metrics, In and Out.
    (20.2.2, DE470045, 32099937, 32154068)
  • Symptom:
    With multiple columns trend chart views, the Y-axis title is partially hidden when metric unit is scaled to numeric values that forces axis height to 1000 units.
    Resolution:
    Addressed the partially visible Y-axis title when numeric values forces axis height on trend chart to 1000 units seen with multiple columns trend chart views.
    (20.2.2, DE470115)
  • Symptom:
    A debug logging message is shown when running the
    NetOps Portal
    installer.
    Resolution:
    The debugging message has been removed from the installer.
    (20.2.2, DE470139)
  • Symptom:
    Items cannot be manually added to the group(s) in the Admin Group Editor.
    Resolution:
    With this fix, the administrator can now manually add items to the group(s) using Admin Group Editor.
    (20.2.2, DE470634)
  • Symptom:
    Read-only checkbox in the group editor triggers a "form is dirty" state (Save button is enabled) if they were clicked on or given focus.
    Resolution:
    Read-only checkbox fields in the group editor no longer causes the Save button to be enabled (the form becoming dirty) if clicked on or given focus.
    (20.2.2, DE471045)
  • Symptom:
    In
    DX NetOps Performance Management
    20.2.1, when logging into odataquery, the login box shows a Host field. The default was changed by mistake.
    Resolution:
    Updated the sign in page to only show Host field when it should, like in
    DX NetOps Performance Management
    3.7.x.
    (20.2.2, DE471202)
  • Symptom:
    Site Context Pages rendering business hours in subtitle when business hour filter is disabled.
    Resolution:
    Fixed issue seen on Site Context Pages with business hours rendered in subtitle when business hour filter is disabled.
    (20.2.2, DE471214)
  • Symptom:
    The data aggregator proxy is unable to write to the
    daproxy.log
    file.
    Resolution:
    Update the owning group of the log directory for data aggregator proxy.
    (20.2.2, DE471368)
  • Symptom:
    After upgrading
    NetOps Portal
    to 20.2, event data appears in Chinese until the data aggregator is upgraded to 20.2.  Problem occurs after
    NetOps Portal
    upgrade, and ends after data aggregator upgrade.
    Resolution:
    Modified the Event Manager sync code to ignore translations for languages that are no longer supported.
    (20.2.2, DE471566)
  • Symptom:
    The Proxy service (
    daproxy
    ) installer fails due to missing jre folder.
    Resolution:
    Update Consul server installer to not cleanup extra
    jre
    folder on upgrade.
    (20.2.2, DE471583)
  • Symptom:
    A few icons displayed in scorecards were not drawing correctly when using the White theme.
    Resolution:
    All the icons used in scorecards draw correctly when using the White theme.
    (20.2.2, DE471739)
  • Symptom:
    When device is discovered that are related to F5 metric the context tabs for F5, available on Switch Context page, are not available on the Device Context page. When preference is to not associate the device as a switch device, requires manual creating F5 Tabs on Device Context page.
    Resolution:
    When F5 related devices are discovered as generic device and prefer to not associate the device as a switch. Provide an automated script to import context tabs for F5, available on Switch Context page, to the Device Context page. Updated to better handle view suppression within the Device Context Page.
    (20.2.2, DE471952)
  • Symptom:
    Custom Site Group are not able to reported as sub-group sites with out of the box SD-WAN Tunnel/App Path Scorecard view.
    Resolution:
    Enhanced the out of the box SD-WAN Tunnel/App Path Scorecard view to support Custom Site Group when used a sub-group sites.
    (20.2.2, DE471965)
  • Symptom:
    When a role for a user with My Custom Groups was changed via the REST API, the My Custom Groups group was deleted.
    Resolution:
    Update the role REST API call to pass down the permission group ID for the user. A mismatch for the new permission group was causing the deletion.
    (20.2.2, DE472070)
  • Symptom:
    When selecting SD-Wan Tunnel/App Path metrics with mix of core and baseline metrics at times is missing both metric types.
    Resolution:
    When selecting SD-Wan Tunnel/App Path metrics with mix of core and baseline metrics always render item to process both metric types.
    (20.2.2, DE472250)
  • Symptom:
    In the Rule Editor, you cannot add multiple values for each condition or sub-rule.
    Resolution:
    With this fix, the Rule Editor's OR condition icon (plus sign) is always displayed when it is required.
    (20.2.2, DE472271)
  • Symptom:
    Sub-Rule's "type" and "condition" columns in the Group Editor's Rule grid are not localized for French and Japanese users.
    Resolution:
    Use Culture instead of Locale so the Sub-Rule's
    type
    and
    condition
    columns in the Group Editor's Rule grid are localized for French and Japanese users.
    (20.2.2, DE472464)
  • Symptom:
    The Vsphere plugin sends all the IPs discovered as outofband Management IP address.
    Resolution:
    The Vsphere plugin now only sends the management IP only in the outofband management IP address set.
    (20.2.2, DE472565)
  • Symptom:
    When creating notification emails, the subject and body fields do not behave correctly (they take forucs from other fields, do not correctly respond to clicking the Insert button, and do not maintain changes made to their content).
    Resolution:
    When creating notification emails, the subject and body fields now behave correctly.
    (20.2.2, DE472636)
  • Symptom:
    Cisco ISPLA polling can fail with NullPointerException if component IndexList has unexpected format for a given AttributeGroup.
    Resolution:
    Cisco IPSLA poller gracefully handles the unexpected component IndexList format, log an appropriate message, and ensure data from the other valid AttributeGroups can be collected.
    (20.2.2, DE472770)
  • Symptom:
    InnoDB fails to initialize during install. A common symptom is that functions that should have installed into MySql did not. Confirmation can be found in the MySql log.
    Resolution:
    Update the installer to check the fs.aio-max-nr setting and update it to a higher recommended value.
    (20.2.2, DE472860)
  • Symptom:
    When generating CSV reports for trend chart views the CSV Export of data does not reflect Business Hour periods in both raw and scaled format.
    Resolution:
    Export of data when generating CSV reports for trend chart views data dis not reflect Business Hour periods in both raw and scaled format.
    (20.2.2, DE473237)
  • Symptom:
    ClassCastException in the
    expression.log
    file.
    Resolution:
    Improved error handling in mvel snmpProtectedDiv function, and improved expression logging.
    (20.2.2, DE473263)
  • Symptom:
    Some tooltips displayed poorly (the contents line wraps after individual characters or pairs of characters) in some browsers.
    Resolution:
    Tooltips now display correctly in all browsers.
    (20.2.2, DE473508)
  • Symptom:
    When selecting multiple groups within the On-Demand report to be aggregated at group level not all groups are included in generated report by view type 'Chart per Metric by Single Item'.
    Resolution:
    Address issue with On-Demand report for view type 'Chart per Metric by Single Item' selecting multiple groups to be aggregated at group level that not all groups are included in generated report.
    (20.2.2, DE473710)
20.2.1 Fixes
  • Symptom:
    Notification traps might show the following error in logs:  Operation not permitted
    (sendto failed).
    Resolution:
    Updated notification trap sender to retry up to two additional times, when receiving this error from the operating system. The error is relogged if retry attempts also fail.
    (20.2.1, DE384374, 01175358, 01261904)
  • Symptom:
    Availability stats were missing from the
    DX NetOps Virtual Network Assurance
    Versa plugin in some cases.
    Resolution:
    Availability stats are now available from the
    DX NetOps Virtual Network Assurance
    Versa plugin.
    (20.2.1, DE402507)
  • Symptom:
    Items appear in Excluded Items tab for a group after a rule is removed from a group. And can only be added back into the group after removing them from Excluded Items list.
    Resolution:
    Updated SQL to clear the ByRule flag on items removed from a group due to the rule being removed. Items do not appear in the Excluded Items list, and can be added back via a new rule.
    (20.2.1, DE403297, 01287437)
  • Symptom:
    A number of icons in dialog boxes and message boxes did not have the correct aria attributes set on them. As a result screen readers were unable to read the purpose of the user interface component.
    Resolution:
    All icons in dialog boxes and message boxes have the correct aria attributes assigned to them so that screen readers can read the purpose of the user interface component.
    (20.2.1, DE406123)
  • Symptom:
    User inteface components used to search and filter did not have the correct aria attributes set on them so that screen readers could provide information about how to use the control and it's components.
    Resolution:
    All user inteface components used to search and filter now have the correct aria attributes set on them so that screen readers can provide information about how to use the control and it's components.
    (20.2.1, DE406124)
  • Symptom:
    Addressed the missing SD-Wan Application Path metric family when customizing a view with context value that is an
    DX NetOps Virtual Network Assurance
    Site.
    Resolution:
    When building custom view with SD-Wan metric if the context selected is a
    DX NetOps Virtual Network Assurance
    Site the Application Path metric family is not available in the metric family selector.
    (20.2.1, DE407396)
  • Symptom:
    During install of the cabi_reports zip file from
    NetOps Portal
    on to the CABI server, if user specified HTTPS scheme, it saves with HTTP scheme.
    Resolution:
    Fixed the installer to correctly save the scheme for
    NetOps Portal
    as HTTPS when specified during install.
    (20.2.1, DE407715)
  • Symptom:
    Editing a dashboard brings up a blank page and cannot be edited. The
    PCService.log
    file shows a message like "Caused by: java.util.NoSuchElementException: Property missing: Panel/Pane".
    Resolution:
    If Pane/Row properties are missing from a view, they are now defaulted to 0 and a message is posted to the user, allowing the dashboard to be recovered.
    (20.2.1, DE408142, 01309964,01328507)
  • Symptom:
    Selecting metrics with different units does not get correctly render with when configuring custom Horizontal Bar Chart views.
    Resolution:
    Alter and validate unit type when selecting metrics when configuring custom Horizontal Bar Chart views.
    (20.2.1, DE409154)
  • Symptom:
    If the ActiveMQ process on the data aggregator or Data Collector runs out of memory, it is not restarted.
    Resolution:
    Added '-XX:OnOutOfMemoryError=/opt/IMDataAggregator/scripts/activemq stop' as JVM parameter to data aggregator and Data Collector broker processes.
    (20.2.1, DE409714, 01294980)
  • Symptom:
    IM Card View does not support Threshold values more than 10 digits long.
    Resolution:
    IM Card View now supports Threshold values up to 12 digits long.
    (20.2.1, DE410339, 01324894)
  • Symptom:
    Sync intermittently fails with high heap usage.
    Resolution:
    Improved the group path caching mechanism to reduce the memory used by the cache.
    (20.2.1, DE411395, 01331371)
  • Symptom:
    Availability Poll is not closing the session properly and throwing exception while closing the session.
    Resolution:
    Delivered a code fix to close the availability poll as expected.
    (20.2.1, DE413247)
  • Symptom:
    During install or upgrade, the installation process might fail during a check to see if MySql is running. This is particularly true when using an externalized MySql as
    DX NetOps Performance Management
    is looking for the running process.
    Resolution:
    The installation process has been improved to check if MySql is running by testing the MySql connection port instead of the mysql process. This allows for the check to validate that MySql is available regardless of whether is it running on the same machine or a different machine.
    (20.2.1, DE413399, 01340717,01337090)
  • Symptom:
    Customer is not able to integrate
    DX NetOps Virtual Network Assurance
    with one vCenter server.
    Resolution:
    Provided a code fix after adding a null check for dvsPortStatus.
    (20.2.1, DE413974, 01339886)
  • Symptom:
    Custom PE Interfaces context page suppressed CBQOS Context Tab after upgrading to
    DX NetOps Performance Management
    3.6 service pack.
    Resolution:
    Resolved the Custom PE Interfaces context page being suppressed CBQOS Context Tab after upgrading to
    DX NetOps Performance Management
    3.6 service pack.
    (20.2.1, DE414383, 01317817)
  • Symptom:
    Several combo-boxes used to select time values were missing labels which made them difficult to use with screen readers.
    Resolution:
    Combo-boxes used to select time values are now labelled with either label tags or aria-label attriibutes so that screen readers can provide context.
    (20.2.1, DE414787)
  • Symptom:
    Edit User wizard shows a password error when saving changes to a user using LDAP authentication.
    Resolution:
    Disabled password strength checking when the password fields are disabled.
    (20.2.1, DE415377, 01350459,01349270)
  • Symptom:
    At times, clicking a group in the group tree on the Manage Groups page takes a large amount of time and the group is not accessible.
    Resolution:
    With this fix, clicking a group in the group tree on the Manage Groups page now takes a reasonable amount of time.
    (20.2.1, DE415423, 01345758)
  • Symptom:
    If the
    Drilldown
    or
    DetailedLogging
    parameters are not included in a generated URL in
    DX NetOps Performance Management
    , (such as when a URL from pre-
    DX NetOps Performance Management
    3.6 is used on 3.6 and higher), the rendered view shows the gear icon and allows editing the view settings.
    Resolution:
    If the
    Drilldown
    or
    DetailedLogging
    parameters are not included in the URL,
    DX NetOps Performance Management
    defaults to
    Drilldown
    and/or
    DetailedLogging
    , and the view cannot be edited.
    (20.2.1, DE415632, 01351680)
  • Symptom:
    Customers want the option to have the system automatically discover devices contributed through
    DX NetOps Virtual Network Assurance
    as SNMP manageable.
    Resolution:
    There is now a
    DiscoverVNADeviceAsSnmpManageable
    option under the discoverydefaultconfig data aggregator REST endpoint. Setting this option to
    true
    causes the data aggregator to create a discovery profile for the IP Domain with any new
    DX NetOps Virtual Network Assurance
    IPs.
    (20.2.1, DE415805, 01349698)
  • Symptom:
    Exception on looking up IP address for Virtual machine in OC Engine for vsphere plugin.
    Resolution:
    Handled the scenario where IP address was not available for Virtual machine in vsphere plugin.
    (20.2.1, DE416260, 01354780)
  • Symptom:
    Operation status of the
    DX NetOps Virtual Network Assurance
    gateway is shown as "NoSuchMessage" on
    NetOps Portal
    when the Data Collector was not reachable.
    Resolution:
    NetOps Portal
    shows correct operation status for the
    DX NetOps Virtual Network Assurance
    gateway when the Data Collector is not reachable.
    (20.2.1, DE416277)
  • Symptom:
    Virtual Machines ,Clusters and Hosts were not discovered which were in Folders.
    Resolution:
    Fixed the issue , added logic to discover Inventory in folders.
    (20.2.1, DE416658, 01353535)
  • Symptom:
    When loading the ACI Console at larger scales, it takes the tree a significant time to load the health scores.
    Resolution:
    Updated the ACI Console to load the health scores in a more efficient manner, so the tree renders significantly faster.
    (20.2.1, DE417378, 01356232)
  • Symptom:
    SslConfig could not import key or certificate from a PKCS12 file.
    Resolution:
    With this fix, SslConfig does allow to import key and certificate from a PKCS12 file.
    (20.2.1, DE417649, 01358678)
  • Symptom:
    Access Point is shown as Other device instead of manageable device.
    Resolution:
    The Access Point is now shown as manageable device from other devices.
    (20.2.1, DE417857)
  • Symptom:
    Exceptions in the performance and inventory capture causing the inventory and performance not  to not populate for the customer.
    Resolution:
    Handled the exceptions in the code, Now the data is populated.
    (20.2.1, DE417918, 01339886)
  • Symptom:
    When discovering the
    NetOps Portal
    device via SNMP in the data aggregator, you cannot view SNMP metrics on the
    NetOps Portal
    item.
    Resolution:
    Updated the
    NetOps Portal
    item to have same default SNMP metric context tabs and ability to add a custom tab of SNMP metrics, when discovered from Data Aggregator.
    (20.2.1, DE417930, 01356609)
  • Symptom:
    On any request OData service responds with "Invalid entity collection or function name 'odata'.".
    Resolution:
    With this fix, if the issue is seen again, the OData server now logs full trace back of the exception.
    (20.2.1, DE418095)
  • Symptom:
    When the Data Collector runs as a non-root user, the user cannot re-assign the Data Collector to a different tenant and/or IP domain due to permissions to restart the Data Collector from inside the Data Collector.
    Resolution:
    Updated the restart logic to call sudo to restart the Data Collector if it's running as non-root user. Be sure to check the documentation for an additional sudo command to allow the Data Collector to run as the install user.
    (20.2.1, DE418500, 01363625)
  • Symptom:
    A new vendor set "AWS_IPSEC_TUNNEL" created for aws tunnel metrics and mapped to SDN Tunnel MF this is turned out to be a default VC for SDN Tunnel MF, which should not be the case.
    Resolution:
    Added <Vendor>Amazon</Vendor> in AWS_IPSEC_TUNNEL Vendor Cert and updated the version of the SDN Tunnel MF which was missing in earlier delivery.
    (20.2.1, DE418710)
  • Symptom:
    RIB queries that target a Data Aggregator and do not include any GROUP BY, ORDER BY, or LIMIT clause started to fail due to parsing errors on the Data Aggregator after a recent Data Aggregator upgrade.
    Resolution:
    Fixed the Data Aggregator's RIB query parsing logic for this scenario.
    (20.2.1, DE418891, 01367393)
  • Symptom:
    When the system
    NetOps Portal
    is set to have localization other than en_US.UTF-8, the caperfcenter_console service fails to start.
    Resolution:
    In the
    caperfcenter_console
    script, locally set the localization to en_US.UTF-8. This allows the expected error checking to proceed and let the process start up.
    (20.2.1, DE418968, 01366004)
  • Symptom:
    When rendering baseline and core metrics on same trend chart when resolution is less than an hour trend line for baseline metric appears as dots that are not connected due to gap data points.
    Resolution:
    Addressed issue with baseline metric appearing as dots, not connected when rendering baseline and core metrics on same trend chart when resolution being applied is less than an hour.
    (20.2.1, DE419012)
  • Symptom:
    When I select a global collection or enter a string filter value with an ampersand, for example, a global collection named "Demo & Development Systems", I get an error on the alarm console.
    Resolution:
    Modified the code that generates the built in filters, and user defined filters for the alarm console to properly escape values when generating XML requests for alarm data.
    (20.2.1, DE419546, 01368197)
  • Symptom:
    When doing an OData query that had multiple filter groups, it was incorrectly combining the checks to return the wrong items.
    Resolution:
    Updated the OData filter group handling to correctly group the checks for items to find.
    (20.2.1, DE419659, 01366295)
  • Symptom:
    DVS elements were not collected when the they are under multiple network folder structure levels.
    Resolution:
    Fixed the code to support multiple folder structure for DVS.
    (20.2.1, DE419699, 01354247)
  • Symptom:
    WildFly reload fails on initial Installation.
    Resolution:
    Using Synchronized Version of reload method for Wildfly.
    (20.2.1, DE419709)
  • Symptom:
    When running Remote Engineer on
    NetOps Portal
    , it complains that it cannot find
    em.properties
    .
    Resolution:
    Updated the
    re.sh
    script to use the correct path to
    em.properties
    .
    (20.2.1, DE419850)
  • Symptom:
    The
    commons-fileupload-1.2.2.jar
    file is present in the
    PCInstallDirectory/PerformanceCenter/PC/webapps/pc/WEB-INF/lib/
    directory. It has been highlighted as a security vulnerability by some sites.
    Resolution:
    Upgrade the
    commons-fileupload
    file to version 1.4.
    (20.2.1, DE419870, 01372590)
  • Symptom:
    NFA "Top ..." Pie Chart with Table views intermittently take a long time to render. Sometimes they are quick, other times they take minutes.
    Resolution:
    NFA "Top ..." Pie Chart with Table views now render in one pass rather than repeatedly updating the Table and Pie sections of the view.
    (20.2.1, DE419970, 01342689,20020017)
  • Symptom:
    When upgrading to
    DX NetOps Performance Management
    3.7, it might fail to run the mysql_upgrade program because the password for the account used was not being passed. Check
    /opt/CA/MySql/mysql_upgrade_results.txt
    to see if it complained about bad password or other error.
    Resolution:
    Updated
    NetOps Portal
    installer to pass the password to the mysql_upgrade program during upgrade.
    (20.2.1, DE420025)
  • Symptom:
    On a scale system Global Search could become too slow since the search criteria is applying a LIKE to every column for each view.
    Resolution:
    With this fix, the search criteria is applying to a given subset of columns for each view.
    (20.2.1, DE420103)
  • Symptom:
    On Migration from Wildfly 10 to Wildfly 13 & 17, the
    JBOSS_CONSOLE_LOG
    property changed in the wildfly initialization Script.
    Resolution:
    Added the
    JBOSS_CONSOLE_LOG
    property to
    /dev/null
    in Wildfly 13 and 17.
    (20.2.1, DE420361)
  • Symptom:
    DX NetOps Virtual Network Assurance
    gateway runs in TLSv1.0 or TLSv1.1.
    Resolution:
    Updated
    DX NetOps Virtual Network Assurance
    gateway to run using TLSv1.2 only.
    (20.2.1, DE420450)
  • Symptom:
    When discovering existing devices and an abort discovery happens before it can complete device discovery and could set the flag that the device was existing, it deleted the existing device.
    Resolution:
    Updated the discovery abort logic to not delete any existing devices.
    (20.2.1, DE420542)
  • Symptom:
    The contrast of link text
    (a shade of blue) on a selected row in a grid
    (which has a background color of a pale gray or blue), was insufficient. On certain monitors, the background color wasn't visible
    (appeared to be white). The shade of blue used for links had a contrast against the background color that was insufficient to meet Accessibility text on background contrast ratio requirements.
    Resolution:
    The background color for selected rows in grids and lists has been darkened and the color used for link text has been adjusted so that it meets accessibility contrast requirements when the link is drawn on the new background color.
    (20.2.1, DE420630)
  • Symptom:
    For Viptela environments with a large number of devices/tunnels, the performance polling results in high memory usage on the
    DX NetOps Virtual Network Assurance
    . This causes
    DX NetOps Virtual Network Assurance
    to run out of memory and/or slow down.
    Resolution:
    The
    DX NetOps Virtual Network Assurance
    Viptela plugin polling logic has been updated to more efficiently process lists of polled data.
    (20.2.1, DE420663)
  • Symptom:
    Threshold values in Group Scorecard Trend are not reversed (so that low values are Red/Critical) when only Critical and Major values are provided, and Minor is set to 0 (zero - disabled) in the view settings.
    Resolution:
    Threshold handling has been updated so that forward or reverse direction is correctly detected when any two threshold values are set, and the third is set to zero / disabled in the view settings. If only one threshold value is provided (others are zero), the direction is set to forward (High values are Red/Critical).
    (20.2.1, DE420784, 20003177)
  • Symptom:
    Geo location attributes cleared in
    NetOps Portal
    group editor for the Site groups are not cleared on the data aggregator, so the OpenAPI shows the last numerical value before they were changed to blank.
    Resolution:
    With this fix, the geo location attributes cleared in
    NetOps Portal
    group editor for the Site groups is now cleared on the data aggregator and OpenAPI-provided values now match
    NetOps Portal
    values.
    (20.2.1, DE420818)
  • Symptom:
    DX NetOps Virtual Network Assurance
    reports Virtual Machine and Host Metrics to wrong metric family in data aggregator.
    Resolution:
    Fixed and Mapped Virtual Machine and Host metrics to the correct Metric family in the data aggregator.
    (20.2.1, DE421149)
  • Symptom:
    The Data Collector can stop receiving inventory and performance data from
    DX NetOps Virtual Network Assurance
    under the following scenario: (1) In
    NetOps Portal
    , go to
    DX NetOps Virtual Network Assurance
    Gateways admin page, set the Administrative State to
    Down
    and then to
    Up
    . (2) Later on, Data Collector loses connection to
    DX NetOps Virtual Network Assurance
    because of network issue or if
    DX NetOps Virtual Network Assurance
    itself goes down.
    Resolution:
    Fixed logic in the Data Collector to ensure that is always restores the connection to
    DX NetOps Virtual Network Assurance
    when it becomes available.
    (20.2.1, DE421399)
  • Symptom:
    When group memberships in
    NetOps Portal
    are removed during global synchronization (and moved to deleted table), due to item being deleted, it does not remove the BY_RULE flag from the relationship. This causes the relationship to appear in Excluded Items.
    Resolution:
    When removing a group relationship and the relationship is moved to the deleted table, the BY_RULE flag is removed. Now, the relationship is not considered for Excluded Items list, and if the item comes back, the group rules can re-add the relationship.
    (20.2.1, DE422002, 01287437)
  • Symptom:
    When using the
    DX NetOps Virtual Network Assurance
    VMware plugin and the data aggregator is on a virtual machine managed by the plugin, removing the
    DX NetOps Virtual Network Assurance
    gateway could cause the data aggregator item to be deleted and re-created on startup.
    Resolution:
    Added check to the
    DX NetOps Virtual Network Assurance
    gateway removal code to not remove any data aggregator or Data Collector device items, and just remove the
    DX NetOps Virtual Network Assurance
    facets off them instead.
    (20.2.1, DE422039)
  • Symptom:
    During Global Synchronization, if a deadlock or cannot acquire lock issue arises, temporary tables are dropped and the connection is remade. This results when the command is re-run, it could not find the temporary table.
    Resolution:
    Updated the retry query handler to not remake the connection on deadlock or cannot acquire lock errors. So when command is re-tried, the temporary tables are still there.
    (20.2.1, DE422072)
  • Symptom:
    When a user with only access to dashboards and
    Drill into View
    role right, the menu bar disappears when drilling into an item due to NullPointerException in _topbar.jsp.
    Resolution:
    Resolved the issue causing NullPointerException, when drilling into a context page from a dashboard without
    View Inventory and Search
    role right.
    (20.2.1, DE422134, 20022262)
  • Symptom:
    A
    DX NetOps Virtual Network Assurance
    device could be mis-reconciled to an SNMP device if the
    DX NetOps Virtual Network Assurance
    device's primary is found in the SNMP device's secondary IP list.
    Resolution:
    Modified the
    DX NetOps Virtual Network Assurance
    device reconciliation algorithm to have the Unique ID have a higher precedence than the IP list match.
    (20.2.1, DE422172)
  • Symptom:
    OpenAPI does not show all paths to a group, as a result, you cannot to create a filter to get groups that belong to a path show in
    NetOps Portal
    .
    Resolution:
    With this fix, OpenAPI now shows all paths to a group separated by ";".
    (20.2.1, DE422272, 20025914,20025914)
  • Symptom:
    After a long period of operation, MySQL process eventually consumes a large percentage of overall system memory even though the process memory settings are properly sized. This is due to MySQL's performance_schema, which is an in-memory schema and not used for
    NetOps Portal
    , being enabled by default.
    Resolution:
    The MySQL performance_schema has been disabled in the
    my.cnf
    file installed with
    NetOps Portal
    .
    (20.2.1, DE422458)
  • Symptom:
    When Data Aggregator root logger is changed to ERROR, an erroneous ERROR message was printed during schema validation when there were no differences found.
    Resolution:
    Updated to check that there are differences before printing the ERROR message.
    (20.2.1, DE422638)
  • Symptom:
    Export the Global Search results to CSV produce a file that is virtually empty.
    Resolution:
    With this fix, export of the Global Search results now produces a CSV file containing the search results.
    (20.2.1, DE422647)
  • Symptom:
    After an Event Manager full synchronization is requested, EM spawns its inventory synchronization. During inventory sync, the group path cache is refreshed. If another EM synchronization is kicked off during this time, it could throw an error that group path cache is being rebuilt.
    Resolution:
    Removed the unneeded check during EM PULL to determine if group path cache was currently being rebuilt. EM synchronization should succeed.
    (20.2.1, DE422795)
  • Symptom:
    Inventory updates result in processing exceptions and ultimately fail to be processed. This results in Persistence exceptions filling up the
    DX NetOps Virtual Network Assurance
    log files and might result in missing inventory in
    DX NetOps Performance Management
    and
    DX NetOps Spectrum
    .
    Resolution:
    The
    DX NetOps Virtual Network Assurance
    datamodel has now been updated to cleanup orphan Subnetted IP Addresses when persisting NetworkInterfaces. The upgrade process now also identifies and cleans up any duplicated Subnetted IP Address objects in the database.
    (20.2.1, DE423138)
  • Symptom:
    Inventory might not update. During upgrade, an exception is thrown in log, containing the following:   "Caused by: org.hibernate.NonUniqueResultException: query did not return a unique result: 3".
    Resolution:
    Updated inventory processing logic to delete multiple instances of cache key entries with the same keystring.
    (20.2.1, DE423273)
  • Symptom:
    The Jetty server might expose its details on error pages.
    Resolution:
    With this fix, the Jetty server does not expose details on error pages.
    (20.2.1, DE423311)
  • Symptom:
    In a multiple data sources environment, any device changes from other data source could trigger the data aggregator to run the inventory discovery during the
    NetOps Portal
    and data aggregator sync process.
    Resolution:
    The sync process has been improved so that only if a new device IP is pushed down from
    NetOps Portal
    can the inventory discovery be run in the data aggregator.
    (20.2.1, DE423494)
  • Symptom:
    Devices with multiple poll rates for same metric family lose polling after data aggregator restart.
    Resolution:
    Fixed a flaw in the polling configuration recalculation logic that runs during data aggregator startup that causes a loss of polling.
    (20.2.1, DE423637, 20015980)
  • Symptom:
    When re-connecting to a
    DX NetOps Virtual Network Assurance
    Gateway, the data aggregator deletes relationships that should still exist. This ultimately leads to group memberships disappearing in the
    DX NetOps Virtual Network Assurance
    Domains hierarchy in
    NetOps Portal
    .
    Resolution:
    Updated the data aggregator logic around determining which relations should be removed when re-connecting to a
    DX NetOps Virtual Network Assurance
    Gateway. The data aggregator no longer deletes relationships that should still exist.
    (20.2.1, DE423878)
  • Symptom:
    Scheduled Reports List and Edit dialog intermittently show incorrect time for the schedule run, and are off by the number of hours between the user's time zone and the system time zone. If saved while in this state, the scheduled report now runs at the incorrectly offset time. If not saved, the scheduled email still runs at the originally defined time.
    Resolution:
    Certain dashboard views were modifying the thread's TimeZone to the user's TimeZone and not restoring it, which injected an incorrect time zone offset in the Scheduled Reports UI. This has been corrected.
    (20.2.1, DE423920)
  • Symptom:
    Tenant themes might switch back to CA-Blue after changing them to another theme. This is because the data aggregator tenant entry in
    NetOps Portal
    data source tenant table still had CA-Blue.
    Resolution:
    Updated Data Aggregator pull sync code to send up tenant and ip domain changes sent during previous push sync, so data aggregator data source table entries are updated with new theme.
    (20.2.1, DE424092)
  • Symptom:
    NetOps Portal
    takes a very long time possibly to consolidate SDWAN tunnels and application paths at large scale.
    Resolution:
    Rewrote SQL queries to consolidate SDWAN tunnels and application paths in an acceptable time frame.
    (20.2.1, DE424244)
  • Symptom:
    User's default group is not accessible via REST.
    Resolution:
    Added defaultGroupId tag to user REST service. Added new REST endpoint to set default group: http://{PC}:8181/pc/center/webservice/users/userId/{User ID}/defaultGroup/{group ID}.
    (20.2.1, DE424967, 20028161,20030925)
  • Symptom:
    When device's Reachability is not backed by the ICMP vendor cert and the device is down, the device's status in the context page are shown as Unknown, instead of Down.
    Resolution:
    Improved the polling process to better handle the SNMP rechability so that the device status can be shown correctly.
    (20.2.1, DE425145)
  • Symptom:
    When doing a Data Aggregator synchronization, it might take a long time during PUSH group stage, when there are many site groups using business hours at very large pollable item scale. Checking kill -3 on the data aggregator process during PUSH shows getBusinessHoursID in one of the stacks and repeating after 5 mins and seeing the same stack on the same thread confirms.
    Resolution:
    Sped up the getBusinessHoursID search greatly by just looking at items with business hour tag on it, and not also checking all items with polllable tag.
    (20.2.1, DE425157)
  • Symptom:
    When using the
    NetOps Portal
    REST service to clone a user who uses external
    (LDAP) authentication, the new user cannot log in.
    Resolution:
    For users with external authentication, modified the clone operation to set the correct authentication flags. For users with internal authentication, modified the clone operation to expire the password immediately; new users must change their password on login.
    (20.2.1, DE425283)
  • Symptom:
    The
    parseSyncTimes.pl
    script provided with
    NetOps Portal
    does not include sync stage timings for data sources that use the HTTPS protocol.
    Resolution:
    The
    parseSyncTimes.pl
    script has been modified to report sync stage timings for data sources that use the HTTPS protocol.
    (20.2.1, DE425408)
  • Symptom:
    Inventory discovery hangs when the Data Collector does not return a response to the Data Aggregator. This is due to the Data Collector throwing an ArrayIndexOutOfBoundsException when it receives invalid SNMP GetNext response, causing it to stop processing instead of returning a response.
    Resolution:
    Fixed the logic to ensure an SNMP Get next response contains the appropriate number of var binds based on the request. If this not the case, the Data Collector sends a failure response to the data aggregator.
    (20.2.1, DE425425)
  • Symptom:
    Parsing the SSO token could result in retrieving wrong field for version.
    Resolution:
    Updated the SSO token parsing code to correctly retrieve version from the token.
    (20.2.1, DE425577)
  • Symptom:
    If a sync push or pull phase for a data source fails due to an exception, there is no END PULL or END PUSH message logged for the sync cycle for that data source. This can make it difficult to understand when each sync phase completes when reviewing the logs.
    Resolution:
    The END PULL and END PUSH messages are logged even if there is a failure during the cycle. The error that caused the failure is logged shortly after then END PULL or END PUSH log.
    (20.2.1, DE425597)
  • Symptom:
    DX NetOps Virtual Network Assurance
    and
    DX NetOps Mediation Manager
    metrics for devices and their components are dropped after using the Stop and then Start Polling actions. .
    Resolution:
    The SDN and EMS Polling Configurations are now correctly recreated when the Start Polling action is sent to a device.
    (20.2.1, DE426041)
  • Symptom:
    A small number of  UI elements that need labels in order for screen readers to successfully explain the purpose of the element were missing associated label tags or were missing aria-label attributes.
    Resolution:
    All UI elements that need labels in order for screen readers to successfully explain the purpose of the element now have either explicit label tags associated with them or have aria-label attributes associated with them.
    (20.2.1, DE426089)
  • Symptom:
    Disabled buttons are present in the keyboard tab order even though they cannot be operated and the focus indicator is barely visible.
    Resolution:
    Disabled buttons are no longer in the keyboard tab order.
    (20.2.1, DE426090)
  • Symptom:
    Labels in some types of charts are drawn in a color that does not have sufficient contrast against the background color.
    Resolution:
    Labels in some types of charts are now drawn in a color that has sufficient contrast against the background color.
    (20.2.1, DE426091)
  • Symptom:
    Open API does not allow to filter on null values, so it is not possible to create a filter expression  find all for example device that have Description property value as null  .
    Resolution:
    With this fix, OpenAPI now allows filtering on null value for String property types. Filtering on other property type values, such as Double and Integer, is not possible due to OData2 framework limitation. The issue is fixed in Odata4 framework.
    (20.2.1, DE426201)
  • Symptom:
    The Data Collector does not send a poll request if it is determined to be "late". This can happen if the Data Collector system time moves ahead by at least 90 seconds (if Data Collector is polling items at 1 minute) or by at least 450 seconds (if Data Collector is polling items at 5 minutes).
    Resolution:
    The Data Aggregator generates events indicating that a Data Collector is having this issue, and also generate events on devices for which poll requests are dropped.
    (20.2.1, DE426204)
  • Symptom:
    The Edit Metric Expression dialog did not display its contents correctly.
    Resolution:
    The Edit Metric Expression dialog now displays correctly.
    (20.2.1, DE426590)
  • Symptom:
    Time-selection combo-boxes did not work correctly with screen readers.
    Resolution:
    Time-selection combo-boxes work correctly with screen readers.
    (20.2.1, DE426904)
  • Symptom:
    Fields  associated with picking dates or times do not all have either label tags associated with them or aria-label attributes associated with them so that screen readers can identify the purpose of the field.
    Resolution:
    Fields  associated with picking dates or times now have either label tags associated with them or aria-label attributes associated with them so that screen readers can identify the purpose of the field.
    (20.2.1, DE426917)
  • Symptom:
    Description Field for Notifications in MySql is only 255 Char , So when the String to be added is more than 255 char it is throwing an persistence Exception.
    Resolution:
    Increased the Description Field for Notifications to 1024 Char.
    (20.2.1, DE427528, 20030542)
  • Symptom:
    DX NetOps Spectrum
    is not detecting inventory in the Aggregator scenario.
    Resolution:
    The logging has been improved to stop these issues.
    (20.2.1, DE427652)
  • Symptom:
    After a
    DX NetOps Virtual Network Assurance
    gateway has been removed from the Data Aggregator, temporary
    DX NetOps Virtual Network Assurance
    items and relationships are not cleaned up.
    Resolution:
    Update the delete
    DX NetOps Virtual Network Assurance
    Gateway logic to also clean up temporary SDN items.
    (20.2.1, DE427863)
  • Symptom:
    When the
    NetOps Portal
    MySQL instance is installed on a host that is remote to the
    NetOps Portal
    services, firewall rules might close idle DB connections which leads the SSO process to exhaust its connection pool, and eventually hang while processing login requests. This problem should not be present if MySQL is co-located with the
    NetOps Portal
    services.
    Resolution:
    Fixed a defect related to persistent DB connections that "leaked" connections if the connection was closed by an external agent, such as firewalls do with idle connections. Reconfigured DB connection pools used by all
    NetOps Portal
    services to periodically validate idle connections to keep them from being closed by firewalls.
    (20.2.1, DE427880)
  • Symptom:
    DX NetOps Virtual Network Assurance
    Notifications are dropped if the value of the string is more than the mysql database char size.
    Resolution:
    The Description field and the cause field are auto -truncated if the size of the chars is more than 1024 and 255 chars respectively.
    (20.2.1, DE428342)
  • Symptom:
    The data sources with host name length greater than 50 fail in data source registration.
    Resolution:
    The max length of data source host name has been increased to 255.
    (20.2.1, DE428397)
  • Symptom:
    The
    NetOps Portal
    Console service is unable to start on a system that does not have wget installed.
    Resolution:
    In the
    NetOps Portal
    console start-up script, check if wget is installed and report an error to the user if it isn't.
    (20.2.1, DE428440)
  • Symptom:
    The IP adress from vCenter is sent with invalid spaces at the end of the IP address, which causes an error on adding the device to the database.
    Resolution:
    The Ipaddress from vCenter is trimmed before adding to the database.
    (20.2.1, DE428464)
  • Symptom:
    Component name aliases in data aggregator were being synced to
    NetOps Portal
    , and if longer than 255 characters, throws SQL error about data truncation. This causes data aggregator PULL phase of synchronization to fail.
    Resolution:
    Updated data aggregator synchronization code to no longer send component name aliases to
    NetOps Portal
    . The data aggregator should never have been synced to
    NetOps Portal
    .
    NetOps Portal
    should only be pushing the name alias to data aggregator.
    (20.2.1, DE428603)
  • Symptom:
    Some separators (horizontal rules) in pages and in drop-down lists were in the tab order of the page (and had nothing associated with the that a screen reader could use). This issue manifested itself only in Firefox.
    Resolution:
    Separators in pages and drop-down lists are no longer tab stops at any time or in any browser.
    (20.2.1, DE428706)
  • Symptom:
    Our enhanced keyboard navigation didn't have protection from overloading the tab contents loading queue. So, when "zipping" through the tabs with the keyboard, a user might see a dialog pop up with a
    500 Server Error
    . Hitting refresh in the browser cleared this error, but it was annoying.
    Resolution:
    Protection has been added to navigating with the keyboard, like navigating with the mouse.
    (20.2.1, DE429272)
  • Symptom:
    Trend/Table views with Business Hours applied shows no shading in Trend for time ranges longer than 14 days.
    Resolution:
    The Trend in Trend/Table view has been corrected to request hourly data instead of daily for longer time ranges when Business Hours filtering is applied. This allows the shading to be rendered correctly.
    (20.2.1, DE429361)
  • Symptom:
    After proxying to a user and loading user's default dashboard, if the user then brings up the group selection dialog, it hangs when trying to close the dialog.
    Resolution:
    Proxying takes you to the user's default dashboard. The url contains a "pg" parameter with no value. That was causing a problem when bringing up the group context selector dialog. Protective code has been added to handle this case properly.
    (20.2.1, DE429375, 20044304)
  • Symptom:
    Global synchronization for devices could throw error about "Data too long for column 'IPs'" if there were too many devices with same common IP.
    Resolution:
    Removed the function that contained the offending SQL, as it was no longer needed.
    (20.2.1, DE429382)
  • Symptom:
    When a Data Collector goes down and back up during a discovery, the discovery could get into a state of trying to be aborted by the hang detector and not fully get aborted and cleaned up. Resulting in the number of running discoveries to be clogged up by discoveries not running.
    Resolution:
    Added additional info/debug to discovery code around aborting discovery to help track these what is happening.
    (20.2.1, DE430011)
  • Symptom:
    Items are missing from
    DX NetOps Virtual Network Assurance
    due to persistence failures while processing messages. .
    Resolution:
    Updated the
    DX NetOps Virtual Network Assurance
    persistence error handling to prevent failures from rolling back message processing. Additionally, updated the persistence logic to correctly persist objects that were previously leading to persistence failures.
    (20.2.1, DE430044)
  • Symptom:
    Upgrading
    NetOps Portal
    after previously upgrading to a recent monthly update appears to be successful, but the
    dbmigrate
    log file in the
    InstallLogs
    directory shows errors similar to the following:
    Sep 04, 2019 11:20:11 AM com.ca.im.installanywhere.util.DbMigrateApp main SEVERE: java.lang.IllegalArgumentException: Expected scheme name at index 0: :mysql\\://localhost\\:3306/netqosportal?characterEncoding\\=UTF-8&useSSL\\=true&verifyServerCertificate\\=false at java.net.URI.create(URI.java:852) at com.ca.im.installanywhere.util.DbMigrateApp.runMigrateMode(DbMigrateApp.java:286) at com.ca.im.installanywhere.util.DbMigrateApp.run(DbMigrateApp.java:164) at com.ca.im.installanywhere.util.DbMigrateApp.main(DbMigrateApp.java:54)
    This problem requires two
    NetOps Portal
    upgrades to be exhibited.
    Resolution:
    The
    NetOps Portal
    installer adds escape characters to the database URLs in the various properties files, which were not expected by the DB migration utilities, and were causing errors in parsing such URLs. The DB migration utilities have been updated to properly handle URLs if they have escape characters.
    (20.2.1, DE430601)
  • Symptom:
    The overall performance of
    NetOps Portal
    becomes very slow in a high scale environment when telemetry data is being collected.
    Resolution:
    Update the telemetry database queries to optimize performance.
    (20.2.1, DE430708)
  • Symptom:
    Inventory discovery could hang and then abort when discovering a device that has class D or E IP addresses.
    Resolution:
    Enhanced the device discovery to properly handle IP class D and E IP addresses.
    (20.2.1, DE430883)
  • Symptom:
    DX NetOps Virtual Network Assurance
    device items were not showing up within the
    DX NetOps Virtual Network Assurance
    group hierarchy.
    Resolution:
    Updated the Data Collector to correctly handle situations where
    DX NetOps Virtual Network Assurance
    sends more than one type of relation for an entity.
    (20.2.1, DE430894)
  • Symptom:
    When threshold events are forwarded to
    DX NetOps Spectrum
    , the quotes around the item are not displayed correctly.
    Resolution:
    Updated threshold event message to use ASCII single quote and double-quotes instead which are displayed correctly.
    (20.2.1, DE431054)
  • Symptom:
    Certain special characters within a custom database password were causing database setup to fail for
    NetOps Portal
    .
    Resolution:
    Updated the installer logic to better handle when special characters are included in the database password.
    (20.2.1, DE431277)
  • Symptom:
    Reconciliation of entities between
    NetOps Portal
    and
    DX NetOps Spectrum
    is not happening in aggregator scenario of
    DX NetOps Virtual Network Assurance
    , due to mismatch in Entity IDs.
    Resolution:
    Introduced Sub Entity ID which is sent in aggregator scenario which
    DX NetOps Spectrum
    uses for reconciliation in case of aggregator scenario.
    (20.2.1, DE431335)
  • Symptom:
    When trying to override the device type for a Meraki device, discovered via SNMP, it shows Other.
    Resolution:
    Updated the CiscoMerakiManagementMib vendor certification to pass the SysObjectID read from the device to the device type MVEL function. Now it can use the custom
    DeviceTypes.xml
    to override the type.
    (20.2.1, DE431612)
  • Symptom:
    Inventory view for "Virtual Interfaces" was incorrectly labeled as an Event List view. The incorrectly label view confused user when configuring dashboard page.
    Resolution:
    Correct the name used for a Virtual Interfaces inventory view that was labeled as an Event List view. .
    (20.2.1, DE431708)
  • Symptom:
    Fips is unable to be configured with an encrypted password in the
    sso.properties
    configuration file.
    Resolution:
    Update Fips configuration to be able to handle encrypted passwords.
    (20.2.1, DE431709)
  • Symptom:
    Emails could not be sent securely if email server supported STARTTLS.
    Resolution:
    Updated
    NetOps Portal
    email properties to enable STARTTLS on all emails being sent. Removed Use SSL button, as
    NetOps Portal
    tries and sends all emails securely if email server supports STARTTLS.
    This now requires the email server certificate and any intermediate/root certificates to be imported into the
    /opt/CA/jre/lib/security/cacerts
    directory, so the email server certificate is trusted on connection.
    For more information, see Configure the Email Server.
    (20.2.1, DE432418)
  • Symptom:
    Configuring custom Trend Chart to generate comma-separated, CSV, report non-baseline metrics were missing when combined with baseline metrics as primary sort column.
    Resolution:
    Addressed issue when generating a comma-separated, CSV, report was missing non-baseline metrics when combined with baseline metric as primary sort column on custom Trend Chart views. .
    (20.2.1, DE432700)
  • Symptom:
    DX NetOps Performance Management
    did not capture the adminStatus and operationalStatus of the OpenDayLight controller in
    DX NetOps Virtual Network Assurance
    correctly.
    Resolution:
    With this fix,
    DX NetOps Performance Management
    now captures the adminStatus and operationalStatus correctly.
    (20.2.1, DE432780)
  • Symptom:
    The time displayed in the time picker
    (upper right corner of dashboard) shows incorrect/next year for the last week of the year. December 30, 2019 Displays as December 30, 2020.
    Resolution:
    Modified the date formatter to use yyyy instead of YYYY which formats the last week of the year correctly. The time displayed in the time picker now shows the correct year for the last week of the year, for example, December 30, 2019.
    (20.2.1, DE433614, 20197781)
  • Symptom:
    Vendor cert "Cisco IPSLA Ethernet DMM and IP Statistics" and "Cisco IPSLA Ethernet SLM
    (Synthetic Loss Measurement) Statistics" were coupled with vendor cert "Cisco IPSLA Ethernet Jitter Precision Statistics". If "Cisco IPSLA Ethernet Jitter Precision Statistics" is not supported, the other two vendor certs are not discovered as supported even though they were configured on the devices.
    Resolution:
    Decoupled the three vendor certs so that they can be discovered properly and independently. .
    (20.2.1, DE433784)
  • Symptom:
    Metric family "Response Path Test Ethernet Jitter" missed two metrics: FrameLossRatioSrcDest and FrameLossRatioDestSrc.
    Resolution:
    Added two metrics FrameLossRatioSrcDest and FrameLossRatioDestSrc to metric family "Response Path Test Ethernet Jitter".
    (20.2.1, DE433788)
  • Symptom:
    When installing the consul service for Fault Tolerance in the proxy and Data Aggregator, the installer isn't asking which IP address to bind to, if there are multiple IPs on the machine.
    Resolution:
    Updated the proxy and data aggregator installers to prompt for which IP address to bind consul service to, if there are multiple IPs on the machine.
    (20.2.1, DE434128)
  • Symptom:
    A recurring message of dropped relations appears in the data aggregator whenever it receives an inventory update from the
    DX NetOps Virtual Network Assurance
    .
    Resolution:
    Change the logging level of the message to debug so that you do not continually see the message, just for debugging.
    (20.2.1, DE434146)
  • Symptom:
    When
    DX NetOps Spectrum
    pulls events from Event Manager, you could see duplicate events. This is due to the item being contributed by multiple data sources, and not using DISTINCT in EM DB queries.
    Resolution:
    Updated the EM DB query to use DISTINCT when getting events to send to
    DX NetOps Spectrum
    .
    (20.2.1, DE434444)
  • Symptom:
    The data aggregator might fail to start due to an ArrayIndexOutOfBoundsException when initializing the RelationshipImporter. This is due to inconsistent values in the attributes used to persist previously imported relationships. The inconsistency could have been caused by a bug in the item repository persistence layer where attribute writes that should have been committed in a single transaction were committed individually.
    Resolution:
    Fixed a bug in the item repository persistence layer's transaction management. Fixed the relationship importer's initialization process to re-initialize the history of previously imported relationships if the history attributes are inconsistent. If the attributes are found to be inconsistent, an error is logged and any automatically generated relationships that had previously been removed are returned and must be removed again via the UI.
    (20.2.1, DE434597)
  • Symptom:
    Items are missing from
    DX NetOps Virtual Network Assurance
    due to persistence failures while processing messages. .
    Resolution:
    Updated the
    DX NetOps Virtual Network Assurance
    persistence error handling to prevent failures from rolling back message processing. Additionally, updated the persistence logic to correctly persist additional objects that were previously leading to persistence failures.
    (20.2.1, DE435483, 20099081,20093248)
  • Symptom:
    Percentage of Actively Memory used was not calculated for ESX hosts.
    Resolution:
    Updated the vendor cert to support the percentage of Active memory used.
    (20.2.1, DE435721)
  • Symptom:
    After upgrade to
    DX NetOps Performance Management
    3.7.5, the Dashboards menu might contain duplicate entries. Upgrade was calling create_dashboards, when it should only be calling create_new_dashboards.
    Resolution:
    Updated installer to not call create_dashboards on upgrade.
    (20.2.1, DE435768)
  • Symptom:
    Users are unable to access
    NetOps Portal
    from the DX SaaS tile page.
    Resolution:
    Users can now access
    NetOps Portal
    after successfully logging into DX SaaS.
    (20.2.1, DE435872)
  • Symptom:
    Group Scorecards when combining total rate and percentiles metrics throws query processing error.
    Resolution:
    Addressed error when combining total rate and percentile metrics on the Group Scorecards view.
    (20.2.1, DE435901)
  • Symptom:
    When setting the
    NetOps Portal
    group context to be a
    DX NetOps Spectrum
    global collection, you only see device level alarms, and not interface level alarms. OneClick shows both.
    Resolution:
    Modified the way that the global collection filter is sent to
    DX NetOps Spectrum
    , so that the alarm view now shows device and interface level alarms when the alarm view context is set to a synchronized
    DX NetOps Spectrum
    global collection.
    (20.2.1, DE436170)
  • Symptom:
    If you select an Interface in Inventory, and then select the IP Performance Tab, and then zoom into one of the charts. After clicking Apply To Dashboard for that chart, the time does not change in the Time Display for the dashboard.
    Resolution:
    The dashboard's time range field was updated to reflect the "Apply to Zoom" feature.
    (20.2.1, DE436188)
  • Symptom:
    Dateparser was not handling few cases of date format during alarm processing in Versa.
    Resolution:
    Added the possible date formats.
    (20.2.1, DE436625)
  • Symptom:
    Performance poll was running sequentially for various device types , which is consuming time thereby missing every other poll.
    Resolution:
    Added Multi Threading for processing performance poll.
    (20.2.1, DE436698)
  • Symptom:
    There is a spike while calculating Delta for
    DX NetOps Virtual Network Assurance
    metrics on the reports when the engine or
    DX NetOps Virtual Network Assurance
    is down for a particular time.
    Resolution:
    Data Collector now discards first poll after the
    DX NetOps Virtual Network Assurance
    or Engine is down, if the value is more than 2 polls.
    (20.2.1, DE436702)
  • Symptom:
    NetOps user interface experiencing performance issue when attempting to render Trend Chart with Events reporting when greater than monthly period.
    Resolution:
    Added safeguard to limit the time range to 31 days when attempting to render Trend Chart with Events reporting to address performance impact./ .
    (20.2.1, DE436873)
  • Symptom:
    Unable to Print "SDN/NFV vSwitch Performance Overview" page to PDF, yields "Property missing: Title" exception in log.
    Resolution:
    This could occur on systems that were upgraded from a pre-3.0.0 release due to a view removed from this page in 3.0.0. The properties of the deprecated view are now restored and the page can now be printed or edited without "Property Missing" exception.
    (20.2.1, DE436879)
  • Symptom:
    When an error happens in the middle of a Full Pull data source stage, it can result in all items not sent by the data source to be removed from the
    NetOps Portal
    inventory. This could result in new item ids being assigned to them if they only come from a single data source like
    DX NetOps Spectrum
    global collections.
    Resolution:
    Updated the
    NetOps Portal
    Full Pull synchronization logic to only mark items, not sent by the data source, after the stage is complete. For example, this should stop
    DX NetOps Spectrum
    global collections from getting assigned a new
    NetOps Portal
    item id, if there is an error during Full pull for groups.
    (20.2.1, DE437034, 01142425)
  • Symptom:
    After upgrade of a very high scale system,
    NetOps Portal
    user REST services are significantly slower.
    Resolution:
    Optimized telemetry queries.
    (20.2.1, DE437335, 20103983)
  • Symptom:
    OK and Cancel buttons on On Demand's Add/Remove Item/Groups dialogs were missing the text
    (OK, Cancel). They were blank buttons. Also, Add/Remove Group for the On Demand from Search Results emitted a 500 Server error.
    Resolution:
    Modified the properties files to reflect new page (18 for nested dialog). Also changed add/remove groups to nested dialog.
    (20.2.1, DE437351)
  • Symptom:
    Engine which is deleted an not cleaned up properly is remaining in the collector folder. On Wildfly restart,
    DX NetOps Virtual Network Assurance
    is considering it a running engine and trying to start the same.
    Resolution:
    On Restart of
    DX NetOps Virtual Network Assurance
    , now it checks if the engines exist in the DB. All engines which don't exist are deleted.
    (20.2.1, DE437603)
  • Symptom:
    When data aggregator thought Data Collectors were disconnected, it aborts all currently running discoveries. Due to a un-handled exception in the aborting process, the counter of the running discoveries was not decreased. When the number of running discoveries reached to the maximum number of concurrent discoveries, all discoveries are stuck on
    NetOps Portal
    .
    Resolution:
    Improved the discovery abort process and handled all the exceptions so that the discovery counter can work properly.
    (20.2.1, DE437748)
  • Symptom:
    With On-Demand report view option Chart per Item with Multiple Metrics when reporting at the component level item titles on chart can mismatched with graph data.
    Resolution:
    Addressed titles on chart mismatched with graph data with On-Demand report view option Chart per Item with Multiple Metrics when reporting at the component level.
    (20.2.1, DE437961, 20108850)
  • Symptom:
    Data Collector could fail to start due to a NULL pointer exception when it tries to sync items from the Data Aggregator.
    Resolution:
    Improved the sync process between data aggregator and Data Collector to handle all possible exceptions properly.
    (20.2.1, DE438315)
  • Symptom:
    Some fields in
    NetOps Portal
    were not adequate protection against HTML/JavaScript injection.
    Resolution:
    Injection protection has been added to all the identified fields.
    (20.2.1, DE438451)
  • Symptom:
    One of the services displays a stack trace to the client when an exception was thrown. This potentially gives and attacker information about the underlying code.
    Resolution:
    The stacktrace is now logged and sent back a standard server error code.
    (20.2.1, DE438461)
  • Symptom:
    When
    DX NetOps Virtual Network Assurance
    receives a time filter larger than 24hrs, it throws an error, which results in client not able to get further updates.
    Resolution:
    DX NetOps Virtual Network Assurance
    now sends a FULL update on receiving a time filter larger than 24hrs, which helps auto renew connections with the client.
    (20.2.1, DE438556)
  • Symptom:
    In a system with
    DX NetOps Virtual Network Assurance
    installed, the data aggregator/
    NetOps Portal
    sync process can be very expensive. It checks the item creation time on all items in the system to find out the newly created
    DX NetOps Virtual Network Assurance
    domain group items.
    Resolution:
    Improved performance of data aggregator/
    NetOps Portal
    sync process by dramatically narrowing down the search scope.
    (20.2.1, DE438808)
  • Symptom:
    Tunnels from the router(customer gateay) which was discovered through snmp are missing./Its not the issue of snmp reconciliation.
    Resolution:
    There was an aws technology specific code written in data aggregator based on the vendor attribute, due to which further code that builds tunnels getting restricted. Upon discussion with Abe/Li this code cleaned-up, that fixed the issue.
    (20.2.1, DE438825)
  • Symptom:
    If any ec2 is in terminated state in AWS console and its IPs are deleted and empty/null ip not handled, due to which entire inventory failed.
    Resolution:
    Terminated ec2's are handled so that upon null/empty ip, the entire inventory poll shall not fail.
    (20.2.1, DE439129)
  • Symptom:
    When rendering shade area on trend chart related to standard deviation the processing performance impacted memory resource usage.
    Resolution:
    Address the processing performance impact when rendering shade area on trend chart related to standard deviation.
    (20.2.1, DE439284)
  • Symptom:
    1. The data aggregator falls behind in processing
    DX NetOps Virtual Network Assurance
    changes. This results in models missing from existing
    DX NetOps Virtual Network Assurance
    Domains or else
    DX NetOps Virtual Network Assurance
    Domains not being created after configuring an additional SDN Gateway.2. All of the Groups under a
    DX NetOps Virtual Network Assurance
    Domain disappear after toggling the Administration Status of the applicable SDN Gateway.
    Resolution:
    Enhancements were made to the
    DX NetOps Virtual Network Assurance
    integration to allow inventory updates to be processed much faster. These enhancements also added more robust logic to avoid exceptions previously seen during response processing and also to prevent Items and Relationships from incorrectly being deleted when toggling the Administration Status of a
    DX NetOps Virtual Network Assurance
    .
    (20.2.1, DE439424)
  • Symptom:
    Distributed Item Repository communication between Data Aggregator and all Data Collectors can be disrupted if one Data Collector gets into a bad state. An example is seen when a Data Collector broker stops consuming messages from the DA, causing a back up in its DIM.request queue. Once the data aggregator broker detects this queue is 100% full, all other data aggregator/Data Collector communication is disrupted.
    Resolution:
    Reworked data aggregator side Distributed Item Repository processing to isolate workloads per Data Collector so that when one Data Collector gets into a bad state, communication is not disrupted for all Data Collectors.
    (20.2.1, DE439788)
  • Symptom:
    Time bar view does not sort as expected when initially rendered on the page, required column selection to sort correctly.
    Resolution:
    Addressed issue where time bar view does not sort as expected when initially rendered on the page, required column selection to sort correctly.
    (20.2.1, DE440194)
  • Symptom:
    Running the
    testssl.sh
    script against
    NetOps Portal
    shows vulnerabilities for "Secure Client-Initiated Renegotiation", "LOGJAM
    (CVE-2015-4000)", and "LUCKY13
    (CVE-2013-0169)".
    Resolution:
    Vulnerabilities for "Secure Client-Initiated Renegotiation", "LOGJAM
    (CVE-2015-4000)", and "LUCKY13
    (CVE-2013-0169)" have been resolved in
    NetOps Portal
    , and are no longer flagged by the
    testssl.sh
    script.
    (20.2.1, DE440319)
  • Symptom:
    The Data Aggregator misinterprets an exception from the database as an outage and shuts down.
    Resolution:
    Updated the regular expression for expected exceptions from the database that should not be interpreted as an outage.
    (20.2.1, DE440348)
  • Symptom:
    Report Analyzer view, Interfaces over Threshold, renders missing image icon on interface name column with Firefox.
    Resolution:
    Addressed the missing image icon with Firefox appearing on interface name column when rendering Report Analyzer view, Interfaces over Threshold.
    (20.2.1, DE440550)
  • Symptom:
    Cannot delete group using
    NetOps Portal
    REST service, when the user has "My Assigned Groups".
    Resolution:
    Fixed permission checking code in
    NetOps Portal
    REST API.
    (20.2.1, DE440557)
  • Symptom:
    When upgrading
    NetOps Portal
    , the service (
    NetOps Portal
    , DM, EM, sso) properties files, that store settings, loses any user added entries.
    Resolution:
    Modified install to preserve any user added settings in the service properties files.
    (20.2.1, DE440676)
  • Symptom:
    Some of the metrics were missing and for those, broker code throwing Null Pointer exception.
    Resolution:
    Null check added for the metrics, so that it avoids the null pointer exceptions.
    (20.2.1, DE441345)
  • Symptom:
    CSV report export only includes first page for legacy systems that upgraded to
    DX NetOps Performance Management
    Service Pack 3.7.4 or higher.
    Resolution:
    Addressed upgrade to
    DX NetOps Performance Management
    Service Pack 3.7.4 or higher issue that CSV report export only includes first page.
    (20.2.1, DE441538)
  • Symptom:
    When Domain is a selected inventory column rendering No Data when applying filter to table view search.
    Resolution:
    Addressed issue when applying filtered search to table with Domain inventory column that sometimes renders No Data to Display.
    (20.2.1, DE441661)
  • Symptom:
    After configuring a Scorecard table that contains percentile metric; when removing percentile metric from list metrics with hierarchy option still renders percentile entry.
    Resolution:
    Addressed issue when removing percentile metric from Scorecard Table with hierarchy option still renders percentile entry in view.
    (20.2.1, DE441793)
  • Symptom:
    Certain
    DX NetOps Virtual Network Assurance
    entities are deleted and recreated every poll cycle even though there are no changes occurring in the environment.
    Resolution:
    The Persistence logic in
    DX NetOps Virtual Network Assurance
    has been updated. With the new implementation, if keys are to be removed from the ID service, the key is checked to make sure it associated with the entity's ID. If it is associated with a different ID, a warning is printed and it is no longer removed from the ID service.
    (20.2.1, DE442571)
  • Symptom:
    The global search can hang on a search string that contains '=' character.
    Resolution:
    With this fix, the global search works, however if the search string contains '=' character, add a new '=' character to the beginning of the search string.
    (20.2.1, DE442778, 20140853)
  • Symptom:
    SslConfig on
    NetOps Portal
    and in the
    sslConfig.sh
    script on the data aggregator uses SHA1WithRSA when generating private key for HTTPS use.
    Resolution:
    Updated both tools to use SHA256WithRSA when generating private key for HTTPS.
    (20.2.1, DE442855)
  • Symptom:
    When
    DX NetOps Spectrum
    system time is behind Event Manager system time, events might not be getting created in
    DX NetOps Spectrum
    when pulled from Event Manager.
    Resolution:
    Updated Event Manager to only handle when current time on Event Manager is older than the end timestamp being requested by
    DX NetOps Spectrum
    . It time shifts the start/end request timestamps to Event Manager local timestamp. Event Manager no longer time shifts forward
    DX NetOps Spectrum
    start/end request timestamps, if older than Event Manager local timestamp.
    (20.2.1, DE443851)
  • Symptom:
    When business hour filter is applied to context page incorrectly shown on view subtitle for data source not related to Data Aggregator.
    Resolution:
    Addressed view subtitle showing business hour filter on context page for data sources that are not related to Data Aggregator.
    (20.2.1, DE444080)
  • Symptom:
    Generate URL not always initially rendering correctly when when view container is enabled on URL Generate dialog.
    Resolution:
    Addressed problem when generate URL that view is collapsed if view container is enabled on URL Generate dialog.
    (20.2.1, DE444200)
  • Symptom:
    If the user's time zone causes "last 8 hours" to shift into the prior day, then the dashboard's time display incorrectly says Today instead of yesterday's date.
    Resolution:
    With this fix, the timezone is now included when checking to see if the date is today's date.
    (20.2.1, DE444215)
  • Symptom:
    Calendar Heat charts were not accessible.
    Resolution:
    Calendar Heat charts are now fully accessible and meet Section 508 accessibility requirements.
    (20.2.1, DE444413)
  • Symptom:
    Reports using custom group of SDWAN tunnels shows no data. Custom groups of devices shows data for SDWAN tunnels they are a participant in.
    Resolution:
    Updated Data Aggregator SQL view to check if the SDWAN tunnel is in the group, in addition to either device of the tunnel.
    (20.2.1, DE444464)
  • Symptom:
    Vulnerable version of jQuery.
    Resolution:
    Updated to latest version of jQuery.
    (20.2.1, DE444735)
  • Symptom:
    When
    NetOps Portal
    restarts, if MySql does not start in 6 seconds, then the
    NetOps Portal
    services fails to start.
    Resolution:
    Fixed comparison in MySql check script to do integer comparison, not string compare that resulted in the check exiting earlier than expected. Also increased check to 120 seconds.
    (20.2.1, DE445174)
  • Symptom:
    NFA Hierarchy sub-table for By Host and By Protocol intermittently does not display the interface data, as items are selected in top table the lower table is still blank.
    Resolution:
    Addressed intermittent issue when selecting item in top table the lower table does not render interface data with NFA Hierarchy sub-table for By Host and By Protocol view.
    (20.2.1, DE446176)
  • Symptom:
    vCenter is sending IP address in invalid format, which is causing persistence failures.
    Resolution:
    Added check for invalid IP addresses coming from vCenter. The plugin lookups for IP address for the VM, if the IP address is invalid.
    (20.2.1, DE446231)
  • Symptom:
    During global synchronization stage on
    NetOps Portal
    , a SQL exception might be thrown during tenant or IP domain stage about truncating LocalID in ds_items table. Large model handles from
    DX NetOps Spectrum
    were causing the SQL exception.
    Resolution:
    Updated the SQL call to do string comparison instead of numeric. The LocalID column is a string and should've been comparing as a string but was using numeric comparison that could result in truncation issues.
    (20.2.1, DE447006)
  • Symptom:
    After configuring Scorecard Trend view with baseline metric renders 'No Data to Display'.
    Resolution:
    Addressed issue when selecting baseline metric with Scorecard Trend view renders 'No Data to Display'.
    (20.2.1, DE447990)
  • Symptom:
    When selecting SD-Wan Tunnel/App Path metrics By Component level with the Scorecard Trend might be missing component items.
    Resolution:
    When selecting SD-Wan Tunnel/App Path metrics By Component level with the Scorecard Trend always render component items.
    (20.2.1, DE448032)
  • Symptom:
    NFA Stacked Protocol Trend views rendered No Data to Display when time range is greater than 2 hours.
    Resolution:
    Addressed No Data to Display rendered on NFA Stacked Protocol Trend views when time range is greater than 2 hours.
    (20.2.1, DE448349, 31842884,31828116)
  • Symptom:
    New NFA views on interface context page has default row value of 1000 that creates long running view processing.
    Resolution:
    New NFA views on interface context page modified row items in view selection and default row value to avoid long running view processing, altered views include;  IP Performance Protocol- Protocol List, IP Performance ToS - ToS List, IP Performance Host - Hosts List, IP Performance Conversation - Conversation List.
    (20.2.1, DE449080)
  • Symptom:
    Installers complain about SLES 12 SP4+ not passing kernel check.
    Resolution:
    Updated installers to pass kernel check with SLES 12 SP4, and SP5.
    (20.2.1, DE449181, 20310176)
  • Symptom:
    When doing a new data aggregator fault tolerant silent install, the data aggregator data directory uses default instead of the
    DA_DATA_HOME
    value in properties file provided.
    Resolution:
    Updated silent installer logic to not set the
    DA_DATA_HOME
    to a default if already set via properties file.
    (20.2.1, DE449615)
  • Symptom:
    DX NetOps Virtual Network Assurance
    was not sending the correct out of band management IP address for some Versa devices.
    Resolution:
    A new configuration has been added to
    DX NetOps Virtual Network Assurance
    that enables finding and sending the correct out of band management IP address for Versa devices.
    (20.2.1, DE450038)
  • Symptom:
    When a device has more than 150 interfaces the Alarms View on Alarms tab of device context page fails with error,
    An unexpected error has occurred
    .
    Resolution:
    Addressed issue that Alarms View on Alarms tab of device context page fails with error when a device has more than 150 interfaces.
    (20.2.1, DE450059)
  • Symptom:
    A cross-site scripting vulnerability exists for a url passing javascript to the
    pg=
    parameter, like this example which raises an alert dialog:
    https://your_pc_host:8182/pc/desktop/page?timeRange=0&endTime=2020-01-28+14%3A25&startTime=2020-01-28+13%3A25&mn=5&pg='%2Balert(15)%2B'&parentid=13
    .
    Resolution:
    The vulnerability for the
    pg=
    parameter has been resolved - the alert in the example URL no longer executes.
    (20.2.1, DE451032)
  • Symptom:
    Plugin logger exposing passwords in plaintext when category OC_ACQUISITION is set to level DEBUG.  Sample message: oc.log:2020-03-11 13:53:43,328 DEBUG
    (EE-ManagedThreadFactory-default-Thread-3) Viptela_17664d4c-c80b-44b1-8722-aa768696e4e9=Inventory Poll [OC_ACQUISITION] TimReflectionHelper 213  inject vman#2837 to method setPassword.
    Resolution:
    Added logic to the OC_ACQUISITION plugin logger to suppress debugging of password values.
    (20.2.1, DE451580)
  • Symptom:
    When SNMP MIB table read encountered PARTIAL_FAILURE error during a metric family change detection process, it could create some incomplete component items. Next time when the MIB table is read successfully, the incomplete items are marked as Not Present. If a device's SNMP agent frequently returns PARTIAL_FAILURE for its MIB table reads, a lot of Not Present components is created.
    Resolution:
    Improved the metric family discovery not to create any component items when a SNMP PARTIAL_FAILURE is encountered. .
    (20.2.1, DE451685)
  • Symptom:
    When sending email via STARTTLS,
    NetOps Portal
    only allows TLSv1.0. If email server is TLSv1.1 or TLSv1.2, the email server rejects the email connection.
    Resolution:
    Updated
    NetOps Portal
    to support TLSv1.2, TLSv1.1 and TLSv1.0 when email server supports STARTTLS.
    (20.2.1, DE451724)
  • Symptom:
    When LogoutService is called during SAML logout, it throws the
    net.shibboleth.utilities.java.support.component.UninitializedComponentException: Component has not yet been initialized and cannot be used.
    exception while trying to decode the HTTP request.
    Resolution:
    Resolved the exception by initializing the decoder code before using it. This exception was hit due to admins trying to not have
    NetOps Portal
    logout of SAML server when logging out of
    NetOps Portal
    . So this fix also includes code to allow admins to not provide a SingleLogoutService in the metadata XML from the IDP. When
    NetOps Portal
    /sso sees there is no SingleLogoutService, it logs the user out of
    NetOps Portal
    . The user can still remain logged into SAML.
    (20.2.1, DE452302)
  • Symptom:
    ACI filter Configuration is reset to default after the upgrade and all customer  has to re-configure the same .
    Resolution:
    It is a code fix to take backup of existing filter configurations and retain the same after upgrading
    DX NetOps Virtual Network Assurance
    .
    (20.2.1, DE452507)
  • Symptom:
    Daily scheduled email jobs are sent multiple times during Spring DST transition when email TZ is UTC and scheduled time is between 00:00 - 01:00.
    Resolution:
    Some combinations of
    NetOps Portal
    host TZ (a DST TZ, like ESTEDT) and scheduled email TZ (non-DST TZ like UTC), when scheduled time is between midnight and 1AM were leading to incorrect calculation of next run time, causing run time to be repeated until after 1AM. The date math has been corrected to better account for the email timezone when calculating next run time.
    (20.2.1, DE453071)
  • Symptom:
    The
    DX NetOps Virtual Network Assurance
    Meraki plugin was fetching the client performance data for only a few of the access points.
    Resolution:
    The
    DX NetOps Virtual Network Assurance
    Meraki plugin now fetches the client performance data for all the access points.
    (20.2.1, DE453478)
  • Symptom:
    The
    DX NetOps Virtual Network Assurance
    Meraki plugin was not discovering any access point without a lan ip address.
    Resolution:
    The
    DX NetOps Virtual Network Assurance
    Meraki plugin now discovers access points without a lan ip address.
    (20.2.1, DE453486)
  • Symptom:
    If other (1) and softwareLoopback (24) are re-enabled in Interface or High Speed Interface vendor certifications, users cannot select them in monitoring profile filters for Interface metric family under Type.
    Resolution:
    Updated monitoring profiles Interface metric family filter support for Type to show other and softwareLoopback values, and treat them as supported.
    (20.2.1, DE453520)
  • Symptom:
    Custom Gauge View automatically scales the gauge needle when using the fixed end point combined with percent option.
    Resolution:
    Custom Gauge View allows for option whether to scale the gauge needle when using the fixed end point combined with percent option.
    (20.2.1, DE453522)
  • Symptom:
    Interfaces were not processed when an HTTP Request fails ,which is creating a null or empty file.
    Resolution:
    Added null check for content in the files when HttpRequestFailure occurs.
    (20.2.1, DE454311)
  • Symptom:
    Suborgs were not processed earlier in versa plugin.
    Resolution:
    Added support for processing SubOrgs.
    (20.2.1, DE454336, 31812847)
  • Symptom:
    DX NetOps Virtual Network Assurance
    installer is allowing duplicate domain names across multiple
    DX NetOps Virtual Network Assurance
    s.
    Resolution:
    Updated installer banner text and
    DX NetOps Virtual Network Assurance
    Swagger update domain with a caution message "Domain name should be unique across VNAs".
    (20.2.1, DE455141)
  • Symptom:
    After upgrading to
    DX NetOps Performance Management
    3.7.10, the following symptoms were seen on certain data aggregators that were monitoring SDWAN environments with
    DX NetOps Virtual Network Assurance
    : 1. High CPU Usage after upgrade caused
    NetOps Portal
    to lose contact with the data aggregator (see: \u003Ca class="cke-link-popover-active" href="https://knowledge.broadcom.com/external/article?articleId=188059"https://knowledge.broadcom.com/external/article?articleId=188059\u003C/a );  2. Changes in the monitored
    DX NetOps Virtual Network Assurance
    environment were not being reflected in
    NetOps Portal
    . These include, but might not be limited to: Sites, Tunnels and SLAPaths; 3. Prior to and after upgrading to
    DX NetOps Performance Management
    3.7.10 "duplicate" / "stale" items and SDN Domains were seen in
    NetOps Portal
    under the SDN Domains group.
    Resolution:
    The data aggregator's processing of
    DX NetOps Virtual Network Assurance
    data has been updated to be more efficient during the processing of data from SDWAN environments. The changes include: 1. A reduction in the upper limit of the number threads available for SDN processing to 1/3 of the CPUs on the Data Aggregator; 2. General improvements to the
    DX NetOps Virtual Network Assurance
    processing to improve the efficiency of processing
    DX NetOps Virtual Network Assurance
    updates from SDWAN environments; 3. Additional protections have been added to the
    DX NetOps Virtual Network Assurance
    processing to resolve missing items seen after upgrading; 4. SDN processing in the data aggregator has been updated to prevent Items from being created for SDN Gateways that had already been deleted from the DA.
    (20.2.1, DE455285)
  • Symptom:
    In the CSV output, OpenAPI might not correctly match expand metric family data with its corresponding configuration entity for example a query like the following
    devices?$expand=interfaces,portmfs
    might return metric data in the line for a different interface.
    Resolution:
    With this fix, OpenAPI now matches all expand data correctly.
    (20.2.1, DE455825)
  • Symptom:
    When using
    DX NetOps Virtual Network Assurance
    as an aggregator inventory items/keys are removed after upgrade. This is especially applicable to
    DX NetOps Spectrum
    . After upgrade, it was unable to reconcile the changes which has the effect of the system creating duplicate items.
    Resolution:
    Migration script modified to only modify ID cache if
    DX NetOps Virtual Network Assurance
    is not operating in "aggregator" mode.
    (20.2.1, DE456076)
  • Symptom:
    For consolidated devices,
    NetOps Portal
    maintained IP address of the device that was synched up first (the data aggregator device IP was not given priority over
    DX NetOps Spectrum
    ).
    Resolution:
    Updated Global sync to give data aggregator device IP priority over
    DX NetOps Spectrum
    device IP during device consolidation based on primary-secondary IP matching.
    (20.2.1, DE456272)
  • Symptom:
    Reporting views using business hours, that have multiple timezones to consider, can take minutes to run the query in the database. This is partly due to the amount of memory the database reserves to run the query, which is based on 65k characters for timezone values.
    Resolution:
    Updated the sql view, for comparing timezone, to select only 255 characters from the timezone attribute. This results in far less memory being needed to run the query. It could result in steps of the query now being multi-threaded, where before it couldn't due to memory requirements. This could result in some business hour queries running much faster than before.
    (20.2.1, DE456460)
  • Symptom:
    When TransientDBConnection logging is set to debug, SQL statements with passwords are logged.
    Resolution:
    Update logger to sift out SQL with passwords.
    (20.2.1, DE456484)
  • Symptom:
    Web service calls to
    DX NetOps Spectrum
    for Alarm Console or the subscription alarm service might timeout after 100 seconds. This usually is due to
    DX NetOps Spectrum
    's response time to the request being made.
    Resolution:
    Updated the timeout to 120 secs, but also made it configurable via the netqosportal.general table or
    NetOps Portal
    admin debug global attributes page. To increase the Alarm Console timeout, run:
    REPLACE INTO netqosportal.general VALUES('AlarmView_WebService_Timeout', '<timeout in seconds>');
    To increase the
    DX NetOps Spectrum
    alarm status subscription timeout, run:
    REPLACE INTO netqosportal.general VALUES('SpectrumStatus_WebService_Timeout', '<timeout in seconds>');
    (20.2.1, DE456697, 20294595)
  • Symptom:
    NetOps Portal
    global synchronization fails if duplicate tunnels and/or SLA paths are synchronized from any data source. Error similar to the following is found in the
    DMService.log
    file upon failure:
    MySQLIntegrityConstraintViolationException: Duplicate entry '5868174-14' for key 'PRIMARY
    .
    Resolution:
    Updated the global sync SQL calls to not error when duplicate tunnels/SLA paths are sent from data source(s).
    (20.2.1, DE456711)
  • Symptom:
    Data aggregator operations that require internal attribute reads such as data aggregator REST calls,
    DX NetOps Virtual Network Assurance
    inventory processing, etc are subject to slowness at high concurrency due to excessive use of java locking objects.
    Resolution:
    Refactored Item Repository read functionality to more efficiently use java locking objects.
    (20.2.1, DE456931)
  • Symptom:
    On deletion of engine, a few entities are not deleted.
    Resolution:
    The issue is caused due to inconsistent hashcode on the properties. Updated the hashcode.
    (20.2.1, DE458021)
  • Symptom:
    After applying edit changes context page with F5 device there is an error when attempting to save context tab, requiring name entry. Workaround required add entry to context tab prior to being able to save modifications.
    Resolution:
    Address error that required F5 context tab manually add title entry to context tab prior to being to save modifications on context page.
    (20.2.1, DE458272)
  • Symptom:
    Various security CVEs reported against the version of Consul that
    DX NetOps Performance Management
    uses.
    Resolution:
    Upgraded the version of Consul to 1.7.2. For the new version of Consul to be enabled after
    NetOps Portal
    is upgraded, the user must run the following commands. If these commands are skipped, the old version of Consul remains running after the install.
    Issue the following commands:
    1. service capc-consul stop
    2. rm -rf <CA_Performance_Center_Directory>/consul/data/*
      Example:
      rm -rf /opt/CA/PerformanceCenter/consul/data/* )
    3. service capc-consul start
    (20.2.1, DE458789)
  • Symptom:
    The
    DX NetOps Virtual Network Assurance
    Viptela plugin is sending data with many disparate sample time values, resulting in many timestamps with few items in the sdn_tunnel_rate table in the DR. This is inefficient for threshold evaluation because each timestamp results in a threshold evaluation query in the DR. This causes long running threshold evaluation times for the NormalizedSDNTunnelInfo metric family and causes the System Health to indicate a degraded state for Data Aggregator Threshold evaluation.
    Resolution:
    Provided an option in the Data Collector to modify sample times for each incoming
    DX NetOps Virtual Network Assurance
    metric so that they appear on a boundary (for example, samples collection at 1:00, 1:02, 1:03, et al) has a sample time of 1:00. This greatly reduces the number of timestamps that need to be evaluated for threshold evaluation, thus keeping the evaluation time for the NormalizedSDNTunnelInfo metric family to comparable values as other metric families.
    (20.2.1, DE459147)
  • Symptom:
    After an upgrade of
    NetOps Portal
    , entries for service properties files add backslash before colons and equals, causing some of the scripts to not run successfully.
    Resolution:
    Updated the upgrade custom code to not add backslashs before colon and equals characters in service properties files.
    (20.2.1, DE459183)
  • Symptom:
    The ACI Console is very unresponsive to mouse clicks in environments that contain a large number of groups.
    Resolution:
    The ACI Console was updated to use more efficient OpenAPI queries for the performance metrics displayed in the dashboard.
    (20.2.1, DE459510)
  • Symptom:
    If a Calix chassis has multiple blades that shares the same IP address of the chassis, only one of them can be discovered properly.
    Resolution:
    Improved the Calix blade discovery to properly handle the shared IP on the blades.
    (20.2.1, DE459921)
  • Symptom:
    When not providing a SsoProductCode to the
    sign-out.jsp
    file, a NullPointerException is shown.
    Resolution:
    Updated the logout code to return an informative error message, if no SsoProduceCode is provided.
    (20.2.1, DE460006)
  • Symptom:
    Alarms are generated with unknown severity.
    Resolution:
    Made changes in AlarmNotifications to not change the severity to unknown when the alarms are cleared.
    (20.2.1, DE460254)
  • Symptom:
    When using a combo-box, the pop-up menu associated with the control always "opens downwards". If the menu is positioned near the bottom of the browser window, it is clipped such that some or all of the menu is not available.
    Resolution:
    When using a combo-box, the pop-up menu associated with the control now opens "upward" if it is clipped by the bottom of the browser window.
    (20.2.1, DE460315)
  • Symptom:
    When global synchronization runs, it might throw a SQL exception like:  com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for the column 'SourceIds' at row 672.
    Resolution:
    Fixed the SQL statement so it does not throw a data truncation error causing global sync to fail.
    (20.2.1, DE460948)
  • Symptom:
    VM and Host metrics were polled on the wrong values on the vsphere client.
    Resolution:
    VM and Host Metrics are polled now on the correct values from the Vsphere client.
    (20.2.1, DE461311)
  • Symptom:
    The value of Added By column of group items created by a rule could be overwritten if a new item is added to the group manually.
    Resolution:
    With this fix, a new item added to a group manually does not override Added By column value of the items created by a rule.
    (20.2.1, DE463375)
  • Symptom:
    Some telemetry SQL queries in
    NetOps Portal
    could still run a long time at scale, due to not using available indexes. They could interfere with queries run for UI tasks, making the UI unresponsive.
    Resolution:
    Updated the remaining telemetry SQL queries that needed additional comparisons to cause them to use indexes to speed up queries.
    (20.2.1, DE464384)
  • Symptom:
    The product key used for on-prem telemetry is invalid.
    Resolution:
    Update the product key for on-prem telemetry to the correct value.
    (20.2.1, DE464806)
  • Symptom:
    OData query might not return device information in expand when it starts from metric family/component, for example portmfs?$expand=device.
    Resolution:
    With this fix, OData query now returns device information in expand when it starts from metric family/component, for example portmfs?$expand=device.
    (20.2.1, DE465743)
  • Symptom:
    The Data Collector might not start polling all components if many calls are made to data aggregator REST webservice to start/stop polling on an individual component.
    Resolution:
    Fixed NullPointerException in the Data Collector so that
    DX NetOps Performance Management
    can better handle polling change requests from the data aggregator.
    (20.2.1, DE466104)
  • Symptom:
    Running a Discovery Profile for ranges that were discovered by a
    DX NetOps Virtual Network Assurance
    Gateway can lead to items being deleted if the IP addresses are pingable but not SNMP contactable.
    Resolution:
    Updates were made to the discovery process which now prevents items from being deleted when they have been previously discovered by a
    DX NetOps Virtual Network Assurance
    Gateway.
    (20.2.1, DE466358)
  • Symptom:
    Open API in some circumstances might not honor tenants boundaries.
    Resolution:
    With this fix, Open API should honor tenant boundaries all the tine.
    (20.2.1, DE466422)
  • Symptom:
    On the System Health page, when you page to the next page in a table, the section is collapsed each time.
    Resolution:
    Instead of setting the collapsed property to be purely based on the status of the section,
    NetOps Portal
    also takes into account the current collapsed state.
    (20.2.1, DE467043)