Quantcast
Channel: THWACK: Message List - Security Event Manager (SEM) - Formerly Log & Event Manager
Viewing all articles
Browse latest Browse all 5385

Re: New syslog node

$
0
0
Check which connectors you have configured on your appliance.  Click on gear next to appliance and see if an HP Procurve is already connected

 

Only the one HP switch that's working and logging correctly is present.

 

Check the logs to see if it is actually coming in on one of the local log files

 

Check what logs?  The log on the HP switch?

 

Configure the connector by hand without the Scan for new nodes and point the HP Procurve connector to the local logfile.  Create a new connector through Tool config

 

This is already how I'm doing it.  Scan for New Nodes doesn't work.  I tried it a couple weeks ago.  I let it run for 7 hours before finally just rebooting the LEM server.  Since it had been stuck in discovery, it refused to let me add any more nodes.  At the time, I had some agent nodes I needed to add, so I had to bounce the server first since there appears to be no way to cancel a running discovery.  After that I was able to add the new agent nodes no problem.

 

It is possible that the log format has changed and it is not being caught by anything

 

The format has not changed.  Verified manually just to be certain.

 

(Mostly applies to something that is not covered) It is possible it is not a covered connector

If this were the case, then the one HP switch I was able to add wouldn't be logging correctly.


Viewing all articles
Browse latest Browse all 5385

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>