Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

SyslogAnalyzer not starting after changing NIC's ip address

We have a machine installed with LMS2.5.1 with dual NIC cards. We have made necessary changes to the gatekeeper.cfg. All have been working fine and we are able to receive Syslog. However, we need to change the one of the NIC card ip address. We have reboot the LMS server and the SyslogAnalyzer has failed to come out. The following message appeared when we tried to pdexec SyslogAnalyzer:

Microsoft Windows [Version 5.2.3790]

(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>pdshow SyslogAnalyzer

Process= SyslogAnalyzer

State = Never started

Pid = 0

RC = 0

Signo = 0

Start = N/A

Stop = Not applicable

Core = Not applicable

Info = Not applicable,

C:\Documents and Settings\Administrator>pdexec SyslogAnalyzer

ERROR: cmd failed. Server reason:

C:\Documents and Settings\Administrator>

Can anyone advise how to resolve this issue?

  • Network Management
8 REPLIES
Cisco Employee

Re: SyslogAnalyzer not starting after changing NIC's ip address

Assuming all you changed was the IP address, and the hostname is still the same as when LMS was installed, then there is nothing else that needs to be done from the LMS side.

The fact that the SyslogAnalyzer process state is "Never started" means that one of the processes on which SyslogAnalyzer depends did not start. SyslogAnalyzer depends on the following:

EssMonitor

RMEDbMonitor

CTMJrmServer

jrm

Find out which of those have also not started. It would be best to paste the entire contents of pdshow for diagnostic purposes.

New Member

Re: SyslogAnalyzer not starting after changing NIC's ip address

attachment show the pdshow output. Pls advise and thanks.

Cisco Employee

Re: SyslogAnalyzer not starting after changing NIC's ip address

jrm is in a waiting to initialize state. This can happen if the hostname of the server was changed, or if the System Identity User is misconfigured. Please provide the NMSROOT\log\jrm.log.

New Member

Re: SyslogAnalyzer not starting after changing NIC's ip address

Pls advise and thanks. Attached is the jrm.log.

Cisco Employee

Re: SyslogAnalyzer not starting after changing NIC's ip address

It looks like there may be a race condition at work here. What are the CPU and memory specs for this server?

New Member

Re: SyslogAnalyzer not starting after changing NIC's ip address

Pentium 4

2.4 GHz

1GB ram

The problem only happen when we change the ip address of one of the NIC card. The ip address of the other NIC card is not changed.

Cisco Employee

Re: SyslogAnalyzer not starting after changing NIC's ip address

This is the problem. You MUST have 2 GB of RAM on this server for the product to start correctly. This is even without any managed devices. You also have DFM installed, so you require a multi-CPU machine.

Given these stats, your choice is either to install another 1 GB of RAM, or uninstall DFM. If you choose to keep DFM, you will also need to add at least one more real CPU (or core) for performance purposes.

New Member

Re: SyslogAnalyzer not starting after changing NIC's ip address

I shall tried to uninstall the DFM to see if this resolve the problem. Shall post any updates.

277
Views
4
Helpful
8
Replies
This widget could not be displayed.