10-21-2022 04:49 AM
I'm trying to configure our UCS domain to send syslog messages to our syslog server but somehow I can't get it to send any logs. For testing I made two SSH connections to the FI. On the first ssh session I run:
ethanalyzer local interface mgmt capture-filter "port 514" limit-captured-frames 0 detail
On the second session I send a test message:
send-syslog alerts "This is a test message"
But the packet capture doesn't show anything.
Show syslog gives me this:
remote destinations
Name Hostname State Level Facility
-------- -------------------- -------- ------------- --------
Server 1 xxxxxxx Enabled Information Local7
Server 2 none Disabled Critical Local7
Server 3 none Disabled Critical Local7
(xxx is the IP of our syslog server)
ping xxxx works.
Telnet xxxx 514 works.
When doing the capture and telnet, the capture shows the telnet going out.
I've tried disabling and enabling the syslog remote server-1 but that doesn't help. It feels as if the services is hanging and needs a restart. I can't really pinpoint the issue. The same exercise on a different domain works as expected.
Any help is welcome.
05-11-2023 06:21 AM
05-11-2023 06:33 AM
You might want to try shifting the 'Primary' FI role to the other FI.
I've seen a few cases were SNMP, syslog, etc, just wouldn't seem to work, until after the VIP moved to the other FI.
Kirk...
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide