After upgrading from 9.0 to 9.1/9.2 you may notice that your Enterprise Overivew views timeout when loading.
Description:
When loading the Enterprise Overview Page in NFA 9.1.x or 9.2 the "Top Interfaces - In" and/or the "Top Interfaces - Out" one or both of these views may timeout.
You will see an error like below:
An error occurred!
Control(32002): Top Interfaces - In
A Timeout expired. The timeout period elapsed prior to completion of the
operation or the server is not responding. error was returned: at
MySql.Data.MySqlClient.MySqlConnection.HandleTimeoutOrThreadAbort(Exception
ex) at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior
behavior) at
MySql.Data.MySqlClient.MySqlCommand.ExecuteDbDataReader(CommandBehavior
behavior) at
System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehav
ior behavior) at System.Data.Common.DbDataAdapter.FillInternal(DataSet
dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String
srcTable, IDbCommand command, CommandBehavior behavior) at
System.Data.Common.DbDataAdapter.Fill(DataTable[] dataTables, Int32
startRecord, Int32 maxRecords, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable) at
NetQoS.Data.MySqlDataComponentBase.ExecuteDataTable(MySqlConnection
connection, String sql, DataTable table, DataParameter[] dataParameters) at
NetQoS.Data.MySqlDataComponentBase.ExecuteDataTable(String sql, DataTable
table, DataParameter[] dataParameters) at
NetQoS.ReporterAnalyzer.Data.ReporterAnalyzer.EnterpriseTopInterfacesReportDc.
GetReport(DateTime utcStartTime, DateTime utcEndTime, DataDirection
dataDirection, Nullable`1 limit, SqlFilter sqlFilter, ReportFilters`1
interfaceFilters, InterfaceConstraint constraintType, Nullable`1
constraintValue) at
NetQoS.ReporterAnalyzer.Business.Reporting.EnterpriseOverviewData.EnterpriseTo
pInterfaces(DateTime utcStartTime, DateTime utcEndTime, DataDirection
dataDirection, Nullable`1 limit, String filter, AgentIdCache cache, UInt32
groupId, RAItemType itemType, Nullable`1 itemId) at
NetQoS.ReporterAnalyzer.WebService.ReporterAnalyzer.GetEnterpriseTopInterfaces
Report(UInt32 groupId, RAItemType itemType, Nullable`1 itemId, DateTime
utcStartTime, DateTime utcEndTime, RADataDirection dataDirection, Nullable`1
limit, String filter, Nullable`1& error) Unknown
nqPortal
at
nqPortal.Views.DataSources.ReporterViewDataSource.HandleRAError(RAErrorType
errorType, Nullable`1 error) at
nqPortal.Views.DataSources.ReporterViewDataSource.EndGetData() at
nqPortal.Views.ViewBase.RetrieveAsyncData() at
NetQoS.Ajax.AjaxUserControl.OnPreRender(EventArgs e)
This is due to the default retention of this data being set to 30 days in NFA to allow for this data to be available in CAPC. NFA will only display 24 hours worth of data on the Enterprise Overview page.
Solution:
To correct this you can delete rows from the database to cut this data down to the last week's worth of data by following the steps below.
- Make a backup of the reporter.interfaceflows table on the NFA console server:
mysqldump -P3308 reporter interfaceflows > interfaceflows.sql
- Login to the 'reporter' database on the NFA console server with:
mysql -P3308 reporter
- Then you can delete anything older than 1 week with the query below:
delete from interfaceflows where endtime < (unix_timestamp() -604800);
**Note** you can adjust the time frame you are deleting from by replacing 604800 with the number of seconds you want to delete older than. For example you can use 86400 to delete everything older than 24 hours.**
- Then to prevent this problem from coming back we can update the settings so that it will prune once a week instead of once a month.
update parameter_descriptions set DefaultValue='1w' where Parameter='flowInfoLimit';
**Note** The default is '1n' which is equal to 1 month. You can also use '1d' for one day, or any other time frame that will work in your enviornment.
- Once these are set, try loading that same Enterprise Overview page again and see if it works without timing out. If it still times out, you may need to cut the data retained to a shorter time period in steps 3 and 4.