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
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
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.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...