LMS31 RME Analyzer not talking to Collector on same server
Environment: LMS 3.1, Windows 2003, Syslog Analyzer and Collector processes running on the same server
All of my RME syslog reports are empty, but the syslog.log file has about 9MB of good syslogs in it.
I only have the default filters available, and all are set to disabled.
In the SyslogAnalyzer.log:
I'm getting the following message "Server certificate chain does not end with trusted root cert!" The Analyzer and Collector are on the same server, but we have ssl enabled with the certificate issued to the fully qualified name of the lms31 server. Initially, the collector status page listed only the hostname of the LMS server, so I deleted it and created a new one with the fully qualified name of the server, and rebooted. I'm still getting the "Server certificate chain does not end with trusted root cert!".
In the SyslogAnalyzerUI.log:
I'm getting "Unable to initialize logging infrastructure for localization".
says "Unable to resurrect connection to a subscriber.
I'm also receiving the Server certificate chain does not end with trusted root cert!" message in this log.
This log also contains a warning saying it can't find the collector properties file in the c:\Progra~1\CSCOpx\MDC\Tomcat\webapps\rme\WEB-INF\classes\C:\c:Progra~1\....\collector.properties. I checked and the collector.properties file is in the correct place and I didn't see anything unusual with the file.
I assume my problem is related to certificates, but I'm not sure what to try. When I connect from a browser on an other computer to the LMS server, I receive the SSL connection with no problem.
1. I was wondering if anyone could please suggest some troubleshooting steps.
2. I'm not sure if and how to trigger the Analyzer to get data from the collector after I make a change. This makes it a bit hard to troubleshoot since I don't know how long to wait to see the effect of my change. Once they synch up properly, does the Analyzer suck up all the old data from the collector, or does it only get the new messsages since they last synched up properly.
3. I'd like to perform direct SQL queries to the database to see if the database has any syslog information in it, but I'm not sure how to do this.
Re: LMS31 RME Analyzer not talking to Collector on same server
Direct database access is not supported. You could get a procedure for getting troubleshooting access by opening a TAC service request. You can also check the AnalyzerDebug.log for SyslogAnalyzer errors. The Collector is working fine, but perhaps there is a problem with the Analyzer not being able to insert messages into the RME database.
[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...