A CIG report is a diagnostic report created by the utility SupportCIG.exe which gathers the information on NetVoyant and the system most often needed for troubleshooting problems.
Originally it supported all the NetQoS products but now only support NV & NPC due to updates to the other products.
Copy SupportCIG to the system and via a remote desktop connection open a command window, change directories to the location of the file and then just enter 'supportcig'.
If the system is running W2K8 then open the command window via the right click 'run as administrator' option.
If needed the utility is available from this ftp location.
If possible generate the report while NV is in the problem state.
It creates a zip file with three parent folders
See below for a listing of files.
These are the files most helpful in each.
shows a list of the running processes and their memory usage.
last time the system was rebooted
processors and RAM
used to verify the MySql my.ini file has the recommended settings.
see this tech tip on those settings.
Tech Tip NV - MySql Recommended Settings For My.ini
see if there is a very large error log
Directory of D:\NetQoS\MySQL51\data
08/13/2014 07:16 AM 6,287,648,591 <Server Name>.err
see the total # of files and size of the database (nms2 folder).
having too many files can result in mysql error 22 failures.
having too many files can be the result of having retention settings too long.
It can also be the result of dbmaintain failing to maintain the correct number of dataset sub tables.
D:\NetQoS\MySql51\bin\mysqld.exe: Out of memory (Needed 2252188720 bytes)
D:\NetQoS\MySql51\bin\mysqld.exe: Incorrect key file for table '.\nms2\event_log.MYI'; try to repair it
D:\NetQoS\MySql51\bin\mysqld.exe: Table '.\nms2\avail_rate_p1416614400' is marked as crashed and should be repaired
The corresponding copy from the Windows Event Log.
MySql writes to the Application log which will sometimes contain errors not on the MySQL51_ErrorLog.txt.
provides the list of all versions installed and when.
If run at a Poller contains the name and address of the Poller.
If run at a MC contains the name and address of all NV systems.
A copy of the event log as shown in the Console.
Shows a list of all tables and their details.
| event_log | NULL | NULL | NULL | NULL |
the NULL values are an indication of corruption
| event_log | MyISAM | 10 | Dynamic | 12050157 |
this one shows the table has over 12 million rows.
too many rows will result in significant performance problems.
Another possibility is it will show too many dataset sub tables.
The number of tables will increase with an increase in retention settins.
A clear example of the problem would be if there was 100 of these tables.
shows the retention rate for all the datasets
Shows the number of enabled and total poll instances per dataset.
Same info as shown in License Info show details
list of devices and their details
a dump of certain portions of the database mostly for configuration
contains these folders
contains the NV services logs which are typically of limited value
if dbmaintain fails to repartition a dataset set of sub tables it will have an error
NetVoyant Portal Logs
one log per day.
records a lot of activity
system to system communication problems are recorded here.
also failures to connect to MySql or Topology.
general SSO info
will show record of login
6:56:50 5 - Single Sign-On Audit:
Sign-In Page Username = <user name>
'System info' list of files
EventApplicationLog.evtx < W2K8
EventSystemLog.evtx < W2K8
EventLog.txt < W2K3
'NetVoyant info' list of files