|
|
|
If the slump logon was successful and you still do not see new events, turn on logging and check the files for an indication that an event has come through CA NSM. You can create an event simply by changing the status on a managed object on the 2D/3D map.
To turn on logging, modify the file NX.env file located in $NX_ROOT (UNIX) or installation-directory (Windows) to include the following line:
@NX_LOG_LEVEL_BSTRAP=VERBOSE
You can then monitor the tngcnv.n files (located in installation-directory\log) to determine if events are being passed to CA SDM. You should see something similar to the following:
09/17 16:35:58:01 tngcnv 477 MILESTONE convrtr.c 399 Sending 1:::dogwood:::9994011e-2f7e-11d1-a435-00c04fd478c9:::09/17/1997 :::16:35:41:::Object_Status_Updated minor:::BV:141.202.211.0:Segment.1 IP:141.202.211.14 MAC: CNT: LOC: DSC::::3:::tngcnv:1:::tng:::WindowsNT: ::CNV:::CRT:::1:::
In this example, the message indicates that the status on a managed object has been updated to Minor.
If you find that events are being passed to CA SDM and they appear in the log, double check to make sure that you are using the default filter and writer rules. If not, restore the original default filter and writer files, recycle the server, and create an event.
If you find that events are not being passed to CA SDM, make sure that two CA NSM processes responsible for passing event information (canotify.exe and caoprdmn.exe) are executing. If they are not running, start them as described in the CA NSM documentation. If they are running, contact CA NSM Support.
| Copyright © 2012 CA. All rights reserved. |
|