IntroductionTrouble Shooting Flow Analysis 1.1
ProcedureTrouble Shooting Flow Analysis 1.1
DIAGNOSTIC INFORMATION COLLECTION
When collecting data from/about Flow and NetQoS, always use the CaseInfoGatherer -?ftp://ftp.ca.com/pub/netqos/supporttools/releasedtools/SupportCIG.exe
This needs to be run as an administrator on the RA box. It will create a zip file that contains diagnostic information about the NetQoS system.
If you need to transfer an issue to the NetQoS team in STAR, Support (or the customer) can call dispatch at 800-225-5224. Only transfer an issue when the case falls outside Support?s scope.
The NetQoS Collector ReporterAnalyzer (RA) is very sensitive to intact prerequisites on the install host. Start by reviewing the install guide at http://support.nimsoft.com/downloads/flow/flow_1.10/en_US/Flow%20Analysis%20Installation_Guide.pdf. The prerequisites start at page 10 and go on for pages. It is very easy to get one wrong. There are some entries labeled optional, and that label seems accurate.
If any prerequisite was missed, it must be repaired and the RA reinstalled. The RA cannot be re-installed in place. The attached remNQsrvcs.bat must be run, and the RA installation repeated from the beginning.
2 First pass data gather
After the prerequisites are fully reviewed, get these files from the customer. Feel free to use the bracketed boilerplate below.
Please run these commands on the NetQoS Collector host:
> dir /S "C:\Program Files (x86)\Nimsoft" > C:\tmp\NimsoftDirList.txt
> dir /S "C:\NETQOS\Netflow\datafiles\HarvesterWork" > C:\tmp\HarvesterWorkDirList.txt
Then zip these files from the NetQoS Collector for analysis. Note only the most recent of each file is necessary at this time.
C:\Program Files (x86)\Nimsoft\probes\application\flow\flow.log
Use these files in the following sections.
3 Check that NetQoS is collecting data.
Review the?HarvesterWorkDirList.txt requested above. The files listed must have non-zero size. If none of these files have content, suspect 1 Prerequisites, 3 Licenses, and 4 Credentials.
4 NetQoS licenses
Some expired licenses were distributed by the Flow Analysis team early in the product?s life. Some of those licenses are still in the wild. Check:
The text of those two should read expiring in 2037. If not, get new licenses, either from GIS or from Fort Collins T3.
5 Administrator credentials
The RA requires system Administrator credentials during the install process. The RA refers to these as DSA credentials. These must be entered into a dialog during install. A non-administrator user with admin privliges is insufficient. You must enter Administrator.
After installation is complete, open the following log file for viewing, C:\tmp\ia\NimsoftFlowAnalysis.log
Look for the following text:
SUCCESS: Flow Analysis Collector credentials configured.
If the text is present, the Windows Administrator User and Password you entered during installation were successfully stored in the database.
Incorrect DSA credentials will leave this telltale log entry. View C:\NETQOS\reporter\Logs\ NetworkSharePumpLog****-**-**.log for lines like:
0:30:31 1 - RemoteFileWatcher: Could not connect to datashare to get files: Error: Unknown, 86
0:30:31 1 - RemoteFileWatcher: Restart failed, will retry in 60 seconds
0:30:31 1 - RemoteFileWatcher: Connection to datashare has been lost!
0:31:31 3 - RemoteFileWatcher: Detected the connection to the datashare has been lost, attempting reconnect
If you see the above ?86? error, use the following
The following lines in your NetworkSharePumpLog indicate you are not using correct DSA credentials on the ReporterAnalyzer host. You must use the local host administrator password.
0:28:54 1 - RemoteFileWatcher: Connection to datashare has been lost!
0:29:54 3 - RemoteFileWatcher: Detected the connection to the datashare has been lost, attempting reconnect
0:29:54 1 - RemoteFileWatcher: Could not connect to datashare to get files: Error: Unknown, 86
This can be edited in the UMP Flow Analysis interface. See page 17 of the Flow Analysis User Guide.
----------------------------------------------- Or ------------------------------------------------------------------
Access the ReporterAnalyzer console.
user name: nqadmin
Administration -> DSA -> Credentials
Domain: use Computer name from Control Panel -> System
User: Prefer Administrator, or other user must have Admin privileges.
Start -> Right-click Computer -> Manage -> Configuration -> Services -> (Restart) NetQoS DSA Loader Service
6 Runtime errors in the RA.
Observe these logs for obvious errors:
RA Console ? C:\netqos\reporter\logs\PumpLogYYYY-MM-DD.log?
Harvester ? C:\netqos\netflow\logs\nfharvestererrorsYYYY-MM-DD.log?
DSA ? C:\netqos\reporter\logs\NetworkSharePumpLogYYYY-MM-DD.log and C:\netqos\reporter\logs\DSALoaderLogYYYY-MM-DD.log?
If any are found, try restarting the following services:
RA Console ? NetQoS Reporter/Analyzer Data Pump?
Harvester ? NetQoS Harvester, NetQoS Reaper?DSA - NetQoS Reporter/Analyzer DSA Loader Service?
If that does not work, the case will be routed to CA NetQos support. Escalate ?to T3 via the normal process.
7 Flow probe must be on RA
Occasionally a customer will forget to install the flow probe on the RA robot. Check the NimsoftDirList.txt, requested above, for evidence of a C:\Program Files (x86)\Nimsoft\probes\application\flow directory.
8 Flow Analysis installation on NMS 6.5 requires an additional step.
On UMP pre-6.5, the Flow Analysis ump_flow portlet installation automatically installs the monitoring_services 1.0 portlet at the same time as the ump_flow portlet. This automatic action is broken on the 6.5 UMP environment. UMP 6.5 comes with a 1.20 version of monitoring_services. During the ump_flow installation, the script sees this higher version already installed, and actively leaves the required 1.0 behind.
In the current 6.5 architecture, both versions, 1.0 and 1.20, of monitoring_services are required for Flow Analysis installations.
The solution is fairly easy. Ensure that the 1.0 version of monitoring_services is available in your Archive. After the ump_flow portlet is installed, deploy the monitoring_services 1.0 portlet by hand. Continue with the rest of the Flow Analysis, as per the install guide.