Joe Clarke Mon, 05/18/2009 - 05:49

Open a DOS prompt on the server, type the command SET, then capture the output.

Joe Clarke Mon, 05/18/2009 - 20:08

Post a screenshot of the services control panel showing all of the CiscoWorks services. Then, shutdown the Daemon Manager, run the DOS command netstat -a -n -o -b, then post the output.

sumitsept3 Mon, 05/18/2009 - 21:09

services control panel ? how can i do that ? pls help

just to go to the folder and give you the screenshot ? or something else you are asking for.

Joe Clarke Mon, 05/18/2009 - 21:13

Open the Services control panel, and take screenshots of every page of it illustrating all services.

Then shutdown the CiscoWorks Daemon Manager service, and run netstat -a -n -o -b from a DOS prompt, and post the output.

Joe Clarke Tue, 05/19/2009 - 08:25

This is what I thought. Set the CiscoWorks Tomcat, CiscoWorks VisiBroker, DFM dfmInv database engine, DFM dfmEpm database engine, and DFM dfmFh database engine services to be Manual startup, then reboot the server. It should work properly when it comes back up.

sumitsept3 Tue, 05/19/2009 - 18:33

i should keep them for manual startup ? and then start all of these services manually , right ?

Joe Clarke Tue, 05/19/2009 - 18:41

They MUST be set to Manual startup. The Daemon Manager service is the only thing allowed to start these processes.

sumitsept3 Tue, 05/19/2009 - 20:14

Hi

i have made all the changes you have asked for, but still experiencing the same issue,

out of 7 (6509E) switches configured i am getting only traps from 1 switch.

previously we used to get from all 7 switches.

( Getting trap from single switch and that too repeated trap)

EVENT ID = 0001S8Z

ALERT ID = 00000UM

TIME = Wed 20-May-2009 09:35:51 IST

STATUS = Active

SEVERITY = Critical

MANAGED OBJECT = 172.20.110.163

MANAGED OBJECT TYPE = Switches and Hubs

EVENT DESCRIPTION = Unresponsive::Component=2.2.2.9 [172.20.110.163];IPStatus=TIMEDOUT;InterfaceName=IF-172.20.110.163/238 [Vl2] [2.2.2.9];InterfaceType=PROPVIRTUAL;InterfaceOperStatus=UP;NetworkNumber=2.2.2.8;InterfaceMode=NORMAL;InterfaceAdminStatus=UP;Address=2.2.2.9;

CUSTOMER IDENTIFICATION = NSE

Joe Clarke Tue, 05/19/2009 - 20:20

The initial problem had nothing to do with traps. This is a completely different issue.

If the JRM error is resolved, then start a new thread for the DFM problem. If the JRM problem is still occurring, then post the new pdshow and jrm.log as well as exactly what you're doing which results in the JRM error.

Actions

This Discussion