Configuring SNMP to Send Traps (BUI)
■
Destinations - The list of destination IPv4, IPv6, and FQDN addresses to which messages
are relayed.
To configure syslog, see the following sections:
■
“Classic Syslog: RFC 3164” on page 327
■
“Updated Syslog: RFC 5424” on page 327
■
“SYSLOG Message Format” on page 327
■
“SYSLOG Alert Message Format” on page 328
■
“Example Configuring a Solaris Receiver (CLI)” on page 330
■
“Example Configuring a Linux Receiver (CLI)” on page 330
Classic Syslog: RFC 3164
The Classic Syslog protocol includes the facility and level values encoded as a single integer
priority, the timestamp, a hostname, a tag, and the message body.
The tag will be one of the tags described in “SYSLOG Message Format” on page 327.
The hostname will be the canonical name of the appliance as defined by the System Identity
configuration. For more information, see “System Identity Configuration” on page 331.
Updated Syslog: RFC 5424
The Classic Syslog protocol includes the facility and level values encoded as a single integer
priority, a version field (1), the timestamp, a hostname, a app-name, and the message body.
Syslog messages relayed by the Sun Storage systems will set the RFC 5424 procid, msgid, and
structured-data fields to the nil value (-) to indicate that these fields do not contain any data.
The app-name will be one of the tags described in “SYSLOG Message Format” on page 327.
The hostname will be the canonical name of the appliance as defined by the System Identity
configuration. For more information, see “System Identity Configuration” on page 331.
SYSLOG Message Format
The Syslog protocol itself does not define the format of the message payload, leaving it up to
the sender to include any kind of structured data or unstructured human-readable string that is
appropriate. Sun Storage appliances use the syslog subsystem tag ak to indicate a structured,
parseable message payload, described next. Other subsystem tags indicate arbitrary human-
Appliance Services 327
To Next Page
Loading...
Need help?
General
