Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
ContentIndex
  
[+] Expand All
[-] Collapse All

No index entries found.

View

Logs

  • The Data Collection link is a shortcut to directories where various data collection files are stored on the server.
  • The IP/MPLSView Systems Logs link displays all the log files in /u/wandl/log.

Note there may be log files with extension .lck that are 0 bytes in size. These files are used for back-end locking and file control purposes.

File

Description

agg.err

Aggregate Error logs. This log contains only error related messages from the agg.sh program.

agg.msg

Aggregate Database Data messages. This log is generated by the agg.sh program and contains information on the database tables being processed. The agg.sh program converts database data, such as SNMP collected data and traffic, into IP/MPLSView object files.

aggutil.log

Aggregate Utility log. This log contains information on the daily database maintenance. The maintenance process moves only performance management related data, such as traffic, from live tables to archive tables in the database. During traffic collection, the collected data goes to the live tables. The archive tables stores the maximum traffic capacity in days (default 35) which is specified during installation or can be changed with the changeconfig.sh script.

aggutildb.log

Aggregate Utility Database log. This log contains detailed information supplementing the Aggregate Utility log. It logs the SQL commands executed during the database maintenance process.

appmon.msg

Application Monitor messages. The Application Monitor monitors running IP/MPLSView processes and will attempt to automatically restart them if they stop running.

appmonitor.log

Application Monitor log. This log contains detailed information on the components being monitored.

autoclear.msg

Auto Clear messages. This log contains error messages related to auto clear of events.

autoclear.log

Auto Clear log. This log contains detailed information on auto clear of events and syslog data converted events.

bulkintf.log

Bulk Stats interface log. Bulk Stats is one method for traffic data collection. This log contains information on the bulk stat process. getintftraf_wandlobj.sh appends the bulk stat traffic data to the live network interface and interfacei traffic files.

configos.log

Config/OS Management log. This log contains information on Config/OS actions, backup, restore, and process status.

dgs.log

Data Gateway Server log. DGS processes traffic data from the data collector. This log contains detailed information on the data objects and messages from the data collector. The detail level of the log is controlled by the dgs.log.properties file in /u/wandl/db/config.

dgs.msg

Data Gateway Server messages. This log contains the standard output of DGS such as initialization, exception, and connection messages.

dgsDB.log

Data Gateway Server Data Base log. This log contains detailed information on the database objects. It has SQL queries, updates, and insert statements generated by DGS. The detail level of the log is controlled by the dgs.xml file in /u/wandl/db/config.

dgsMSG.log

Data Gateway Server messages. This log has detailed data dumps of XML application data passed by JMS which is used by traffic collection manager and data collectors.

dgsTASK.log

Data Gateway Server task log. DGS creates and write traffic data to system files for use by threshold server. This log contains information on the collection threads and fail over messages of the data collector.

ejbcollect.log

Enterprise JavaBeans Collection log. This log contains error messages related to ejb data collection.

ejbserver.log

Enterprise JavaBeans server log. This log contains information on the ejb server initialization and services running.

ejbserverboot.log

Enterprise JavaBeans boot log. This log contains information on the ejb server boot up. This is the standard log from ejb server and is not created by IP/MPLSView.

eventhandler.log

Event Handler log. This log contains information related to the network model and topology on the Web. This includes the network view node list, groupings, interface status, fault management status, and application monitor.

eventhistserver.log

Event History Server log. This log contains information on event browser queries for historical events.

eventhistserver.msg

Event History Server messages. This log contains error messages related to the event history server.

eventserver.log

Event Server log. This log contains information on event browser queries, clearing, and acknowledgment of events.

eventserver.msg

Event Server messages. This log contains error messages related to the event server.

getipconf.log

Get IP Configuration log. The getipconf program parses router configuration files, router cli statements, and various input files to generate the IP/MPLSView system files for network and topology construction. This log contains information on the input files read and output files created.

hibernate.log

Hibernate log. Hibernate is a database data retrieval program that does not use SQL commands to gather the data. This log contains detailed information on the program.

hornetq.log

Hornet Q log. This log contains information on Hornet Q. This is the standard log from Hornet Q and is not created by IP/MPLSView.

instmysql.log

MySQL installation log. This log contains information on MySQL processes initialized, running, and shutdown.

mergeEventTypes.log

Merge Event Types log. This log is created only during installation. Merge event types is a process to make custom event types from previous versions compatible with the current version.

migrateWRouter.log

Migrate WRouter log. This log is created only during installation. This process migrates the old format of the wrouter table from previous versions to be compatible with the current database version.

mysql.log

MySQL log. This log contains information on MySQL. This is the standard log from MySQL and is not created by IP/MPLSView.

mysql.msg

MySQL messages. This log contains start and stop messages of MySQL processes.

npatlogfile

NPAT log. This log contains information on the user id starting clients and establishing connection with the Filemanager.

provision.log

Provision Manager log. This log contains information related to the provision manager.

selectiveIntf.log

Selective Interface log. This log contains detailed information on the routers processed for selective interface traffic data collection. It has information on the index, rules, and interfaces to poll for traffic.

selectiveIntf.msg

Event Summary log. This log contains fault management summary of event counts and counters.

summary.log

Threshold Server log. The threshold server is involved in processing traffic data to the interface, interfacei, and tunnel system files. This log contains information on the collection status of the threshold server and data processed.

threshold.msg

Threshold Server messages. This log contains error messages related to the threshold server.

tmng.log

Task Manager log. This log contains detailed information on task server resources, components, and tasks. Any task related to task server or wtalk are logged.

tmng.msg

Task Manager messages. Logging starts at the launch of the task server and ends after logging in to the client. These messages are for troubleshooting startup issues. Once task server is running, further logging is done in the tmng.log file.

updateWRouterTable55_AFTERINSTALL.log

Update WRouter Table After Install log. This log is created only during installation. It is related to the migrate wrouter table process and shows the table rows affected by the migration. This process primarily affects IP/MPLSView version 5.5 and earlier.

updateWRouterTable55_BEFOREINSTALL.log

Update WRouter Table Before Install log. This log is created only during installation. It is related to the migrate wrouter table process and shows the table rows that need to be updated. This process primarily affects IP/MPLSView version 5.5 and earlier.

wDriverTask.log

IP/MPLSView Talk Driver log. Lists the jobs executed on each router along with its collection status.

webserver.log

Web Server log. This log contains detailed information on web server resources, components, and connections. This is the standard log from web server.

webserverboot.log

Web Server Boot log. This log contains detailed information on the intialization and boot up of the web server.


Login History


Records the time and web user ID for each access to the Web interface. A user named “fromgui” indicates that the web interface was accessed from IP/MPLSView client using the File > Launch Web action.


Login Statistics


Reports the number of times the Web interface was accessed yearly, monthly, or weekly. Click on a month name to view weekly statistics.


User Activity Log


This log displays the records of user activity, and can serve as a useful audit trail of the actions performed by IP/MPLSView users. Activities recorded include:

  • Client login attempts
  • Client subscriptions
  • Web login attempts
  • Web logout attempts
  • Device Profile sync to Traffic Collection Manager
  • Task Manager operations
  • Traffic Collection Manager operations

Note: To record and display Web logout attempts in the User Activity Log, you must click the logout button on the right side of the window when you log out of the IP/MPLSView Web interface. Simply closing your Web browser or closing the browser window tab does not record this action as a Web logout in the User Activity Log.

Figure 219: User Activity Log with Web Logout Recorded

User Activity Log with Web Logout Recorded

System Monitor


This allows the administrator to monitor the status of IP/MPLSView processes, including the Disk Utilization and CPU and Memory usage of related processes.


Release Information


This function displays the IP/MPLSView version and build number installed.


Modified: 2016-01-05