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
    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
    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:
    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
    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 De