Fixed Issues

Fixed Issues
nfa2124
2
Issues Fixed in 21.2.6
The following issues were fixed in the current release:
Defect ID
Support Case
Symptom
Resolution Text
Issues Fixed in 21.2.4
The following issues were fixed in the current release:
Defect ID
Support Case
Symptom
Resolution Text
DE513467
32834440
NFA Flows Stats Page is not rendering table stats, but graphics are displaying correctly.
Reassigned to MAX integer value to droppedFlows, mapFailures properties when the summary of these data values exceed MAX integer value.
DE513273
32831308
The "Manage Monitoring" page in NetOps portal 21.2.2 is timing out.
The "Manage Monitoring" page in the NetOps portal shows the data.
DE512513
32823417
When I create a Protocol Group in NFA Console, I see the standard error page.
Added security token in all form tags which are generated dynamically to fix the error.
DE493171
32501042
Multiple SNMPv3 profiles with similar Usernames do not function correctly.
If different agents (command responders) use the same SNMPv3 username, NFA uses the
localized key
(passphrases) to identify each agent.
Issues Fixed in 21.2.2
The following issues were fixed in the current release:
Defect ID
Support Case
Symptom
Resolution Text
DE507754
32740945
SNMP refresh fails due to incorrect
mplsVpnInterfaceConfEntry
configuration.
Code changes are made to successfully refresh SNMP by fixing the
mplsVpnInterfaceConfEntry
configuration.
DE507584
32732975
threshold violations are synchronized with the wrong Router ID.
Code changes are done to send the correct Router Id in the Threshold event requests to get email notifications when threshold violation occurs.
DE504061
32707717
"Manage Monitoring" page that shows devices and their interfaces do not work.
Code changes are done to display the devices and their interfaces on the "Manage Monitoring" page.
DE503446
32684589
The Routers with Most Flow Traffic view in the
NetOps Portal
shows failed query message.
Code changes are done to display the expected data on the Routers with the Most Flow Traffic view in the
NetOps Portal
.
DE502839
32606393
Devices are being moved to reboot refresh state on receiving invalid sequence numbers.
Code changes are made to add the IP addresses to the
ignoreRebootDevices
property to skip reboot detection.
DE499207
32585974
The device from
in
NetOps Portal
(PC) is missing some Data Source groups. This is seen specifically in a case where a device is RETIRED and a new device is discovered with the same IP address as the RETIRED device.
Code changes are done to identify the new devices using other attributes even if they have the same IP address.
DE495615
32581902
Manager Service stops receiving traps.
Code changes are done to receive traps when zero bytes are sent from a socket.
DE492264
32452253
The Interface search bar ((Interface Index, Group) performs internal SOAP requests. The request was providing a series of parameters that were used to perform an SQL query to retrieve information from the backend database. The parameters were not validated prior to the SQL query, allowing a malicious user to inject arbitrary SQL queries to enumerate and retrieve information from the database.
Code changes are done to validate the parameters before running the SQL query. Hence, not allowing a malicious user to inject arbitrary SQL queries to enumerate and retrieve information from the database.
DE487278
32423225
The OData log shows an exception "Data too long for column ifAlias" on SNMP refresh.
Code changes are done to remove the exception in the OData log and SNMP refresh is successful.
DE504580
32683732
Edit Aggregations API does not push changes to the harvester.
Code changes are done to update the 'UpdatedOn' column during the edit aggregation scenario.
Issues Fixed in 21.2.1
The following issues were fixed in the current release:
Defect ID
Support Case
Symptom
Resolution Text
DE502531
32657535
DX NetOps Performance Management System Status page goes red often.
Code changes are made to clear the data source context when data source creation fails during the processing of the OData conversation API by a thread. Hence, when the same thread processes any API then we do not get any issue related to the data source.
DE504232
32695389
Odata service is not able to trust the Harvester server certificate.
Importing a Harvester certificate to console the truststore resolves the issue.