Dell OS10 Syslog and Logging: Configure and Verify - 夜莺博客

Dell OS10 Syslog and Logging: Configure and Verify

Dell SmartFabric OS10 keeps two distinct log streams: a syslog file that carries system events and alarms, and an event/alarm database that drives the severity-profile logic and the counter-based health checks. Engineers who only look at one of them spend hours chasing an issue the other stream already described. This article walks through OS10 logging configuration, the commands that show what the switch actually recorded, and the verification steps that prove a syslog server is receiving events.

OS10 logging architecture in one paragraph

OS10 writes local events into the system log file, forwards them to a remote syslog server if one is configured, and separately records state-change events and alarms that can be filtered against a severity profile. The local log file can be large, so the first diagnostic step on any OS10 issue is usually to read it rather than to start a debug.

Viewing system logs

show logging

show logging is the main entry point and accepts several parameters:

OS10# show logging
OS10# show logging log-file
OS10# show logging log-file | more
OS10# show logging process-ospf
OS10# show logging reverse
OS10# clear logging
  • log-file provides a detailed log including both software and hardware events saved to a file.
  • process-<name> narrows the output to a single daemon, which is the fastest way to isolate one protocol's complaints.
  • clear logging resets the local buffer — do this at the start of a maintenance window so old noise does not hide new events.

show trace

The current syslog file itself is read with show trace, which prints the raw stream including anything the parsed view filters out:

OS10# show trace
OS10# show trace log-file
OS10# show trace jenkins

Configuring remote syslog

Enable global logging first, then point the switch at the collector. OS10 requires logging to be enabled before the server statement has any effect:

OS10# configure terminal
OS10(config)# logging enable
OS10(config)# logging server 10.20.30.40
OS10(config)# logging server 10.20.30.41 6
OS10(config)# logging console
OS10(config)# end
OS10# write memory

The optional severity level after the server address sets the lowest severity that is forwarded; leaving it out sends everything at the default level. OS10 also supports system logging over TLS when the collector requires an encrypted transport, which is worth enabling for switches that leave the management network.

Events, alarms and severity profiles

OS10 separates alarms from logs. Alarms have state (active or acknowledged) and can be inspected as a set:

OS10# show alarms
OS10# show alarms summary
OS10# show alarms details
OS10# show alarms sequence
OS10# show event history
OS10# alarm acknowledge

A custom severity profile lets you keep noisy informational events out of the alarm list while promoting anything that touches links or power to a higher severity. Review show event severity-profile after any profile change to confirm the mapping you intended is the mapping that is active.

Verifying that logs are actually leaving the switch

  1. Confirm logging is enabled with show running-configuration logging — an OS10 switch will happily accept a server statement while global logging is off.
  2. Generate a known event on purpose: shut and un-shut an unused access port and watch for the interface state change in the collector.
  3. If nothing arrives, test reachability to the collector on the syslog UDP port from the switch's management VRF before blaming the switch configuration.
  4. On the collector, filter by the switch hostname or source address; duplicate hostnames across a fleet is a classic reason logs appear to be missing.

Collecting a support bundle

When the log alone is not enough, OS10 can package logs, alarms, configuration and hardware state into a single archive for Dell support:

OS10# generate support-bundle
OS10# show support-bundle status

See also: Dell OS10 basic switch management CLI, OS10 hardware health and optics diagnostics, and building a central rsyslog server.

原文链接:https://www.dell.com/support/manuals/en-us/dell-emc-smartfabric-os10/smartfabric-os-user-guide-10-5-1/view-system-logs