Tech Tip NV - What to look for in a CIG Report

Document created by DavidM Employee on Dec 23, 2014
Version 1Show Document
  • View in full screen mode

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. 

ftp://ftp.ca.com/pub/netqos/supporttools/releasedtools/

SupportCIG.exe

 

If possible generate the report while NV is in the problem state.

 

It creates a zip file with three parent folders

NetQoS Logs

NetVoyant info

System info

 

See below for a listing of files.

 

These are the files most helpful in each.

 

System info

tasklist.txt

shows a list of the running processes and their memory usage.

 

systeminfo.txt

OS version

last time the system was rebooted

processors and RAM

 

MySQL51_Variables.txt

used to verify the MySql my.ini file has the recommended settings.

see this tech tip on those settings.

https://communities.ca.com/docs/DOC-231151454

Tech Tip NV - MySql Recommended Settings For My.ini

 

MySQL51_FileSize.txt

see if there is a very large error log

example:

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.

 

MySQL51_ErrorLog.txt

error examples

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.

 

 

NetVoyant info

NV_Version.txt

provides the list of all versions installed and when.

 

NV_ServiceManagers.txt

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.

 

NV_EventLog.txt

A copy of the event log as shown in the Console.

 

NV_nms2TableStatus.txt

Shows a list of all tables and their details.

examples

| 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.

| ifstats_rate             

| ifstats_rate_p1400630400  

| ifstats_rate_p1400716800

| ifstats_rate_p1400803200 

| ifstats_rate_p1400889600

 

NV_RetentionRates.txt

shows the retention rate for all the datasets

 

NV_PollinstByDatasets.txt

Shows the number of enabled and total poll instances per dataset.

Same info as shown in License Info show details

 

NV_DeviceList.txt

list of devices and their details

 

nms2.sql

a dump of certain portions of the database mostly for configuration

 

 

NetQoS Logs

contains these folders

NetVoyant Logs

contains the NV services logs which are typically of limited value

dbmaintain.log

if dbmaintain fails to repartition a dataset set of sub tables it will have an error

 

NetVoyant Portal Logs

PollerWebServiceLog<date>.txt

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.

 

SingleSignOn Logs

SingleSignOnLog<date>.log

general SSO info

 

SingleSignOnAuditLog<date>.log

will show record of login

6:56:50 5 - Single Sign-On Audit:

Message =

Sign-In Page Username = <user name>

 

 

'System info' list of files

DEP_Settings(0_or_2_is_good).txt

DetailedServices.txt

DiskSpace.txt

EnvironmentVariables.txt

EventApplicationLog.evtx < W2K8

EventSystemLog.evtx < W2K8

EventLog.txt < W2K3

FragmentationReport.txt

GathererInfo.txt

Hotfixes.htm

IISmetabase.xml

ipconfig.txt

LicenseInfo.txt

MySQL51_ErrorLog.txt

MySQL51_FileSize.txt

MySQL51_ProcessList.txt

MySQL51_Status.txt

MySQL51_Tables.txt

MySQL51_Users.txt

MySQL51_Variables.txt

netstat.txt

netstat_stats.txt

RegionalSettings.txt

registry.txt

runningservices.txt

ScheduledTasks.txt

SharedFolders.txt

systeminfo.txt

tasklist.txt

tasklistsvc.txt

TimeZone.txt

 

'NetVoyant info' list of files

nms2.sql

NV_AlarmRules.txt

NV_BinDirectory.txt

NV_datasets.txt

NV_DeviceList.txt

NV_DeviceListByGroup.txt

NV_DiscoveryScopes.txt

NV_DurationsByEnabledPollinst.txt

NV_EventLog.txt

NV_EventSeverities.txt

NV_ExpressionsByDataset.txt

NV_InterfaceTypes.txt

NV_MIBs.txt

NV_MIB_OIDs.txt

NV_nms2TableStatus.txt

NV_NotificationMessages.txt

NV_Notifications.txt

NV_PollDefs.txt

NV_PollinstByDatasets.txt

NV_ProfilesToGroups.txt

NV_RetentionRates.txt

NV_ServiceManagers.txt

NV_SSOconfig.txt

NV_TopDevicesByDiscoveredPollinst.txt

NV_TopDevicesByEnabledPollinst.txt

NV_Version.txt

1 person found this helpful

Attachments

    Outcomes