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.

Related Documentation

    Event Administration


    Starting and Stopping the Event Server


    Below are the commands to stop and start the event server:

    /u/wandl/bin/.eventserver stop
    /u/wandl/bin/.eventserver start /u/wandl/db/config/eventserver.xml

    Starting and Stopping the SNMP Trap Server


    Below are the commands to stop and start the SNMP trap server:

    /u/wandl/bin/.snmptrap stop
    /u/wandl/bin/.snmptrap start

    Resetting Port Values


    Ensure that the proper ports required for the Event Browser are opened through the firewall.

    You prompted for the port value the first time the Event Browser is opened. Once the settings are saved, you are not prompted for them anymore. To get the prompt for these options again, delete the file: C:\Documents and Settings\<user_name>\Application Data\wandl\EventBrowser.<server_ip>.xml (Windows XP) or C:\Users\<user_name>\AppData\Roaming\wandl\EventBrowser.<server_ip>.xml and then reopen the Event Browser.


    Data Archival and Cleanup


    The raw trap data is stored under the directory /u/wandl/data/trap.

    The raw event data is stored under the directory /u/wandl/data/event/[date], where [date] is the date of the collection using the format yymmdd, with yy as the two character year, mm the two character month, and dd the two character day. In each date directory, one file is created per device using the device hostname as the filename, and all raw event data for that device is saved to that device file. For example, to see all raw events for a device with hostname NewYorkPOP on the date July 4, 2008, you would look at the file /u/wandl/data/event/080704/NewYorkPOP.evt.

    • By default events data older than 30 days are purged. This number can be modified in the XML file /u/wandl/db/config/eventserver.xml. Edit the parameter maxStore for id=”eventStore”.
    • By default historical events data older than 100 days are purged. This number can be modified in the XML file /u/wandl/db/config/eventserver.xml. Edit the parameter maxStore for id=”aggStore”.

    Troubleshooting the Event Server


    1. If the traps are not being received, check that the router can reach the IP/MPLSView server’s SNMP Trap Daemon IP, configured in /u/wandl/bin/mplsenvsetup.sh (MPLS_TRAP_IP), and that the router has been configured to send traps to this IP address.
    2. If /u/wandl/bin/status_mplsview shows that the event server is not started but the ./.eventserver command says that it is, check that the EVENTSERVER entry is properly cleared from the /u/wandl/tmp/.pids file. Use the ‘ps’ command to confirm that the process Id is not being used for the event server.
    3. If you see the message: ‘device ID’ not mapped correctly, note that the SNMP trap server relies on the /u/wandl/data/.network/intfmap.x file to resolve device ID’s. This error message will appear if this file is missing or if the relevant device has not been collected. If necessary, add the missing device to the live network collection task.
    4. Recreate Aggregate Events: If for some reason, the old events (all events prior to software upgrade) are not shown in the event browser. To fix this issue, force the eventserver to recreate the aggregate events.
      • Stop the event server: cd /u/wandl/bin; .eventserver stop
      • Rename the old aggregate events: cd /u/wandl/data/event/aggregate; mv AggregateEvent.store AggregateEvent.store.orig
      • Touch AggregateEvent.store with an old timestamp – less than the historical data’s oldest timestamp: touch –m –t 0801010000 AggregateEvent.store
      • Restart the event server: cd /u/wandl/bin; .eventserver start
    5. Event server log files are located in the /u/wandl/log directory:
      • eventhandler.log.n (Change log levels in the /u/wandl/db/config/eventhandler.log.properties, a rotating log with max size 500KB)
      • eventserver.msg: All exceptions, stdout, and stderr output from the Event Server are included here
    6. SNMP Trap Server log files are located in the /u/wandl/log directory as well:
      • snmptrap.log.n: (Change log levels in the /u/wandl/db/config/snmptrap.log.properties, a rotating log with max size 500KB)

    Modified: 2015-12-29