1-17
Cisco ASA Series CLI Configuration Guide
Chapter 1 Configuring Logging
Configuring Logging
Including the Device ID in Non-EMBLEM Format Syslog Messages
To include the device ID in non-EMBLEM format syslog messages, enter the following command:
Command
Purpose
logging device-id
{
cluster-id
|
context-name
|
hostname
|
ipaddress
interface_name
[
system
]
|
string
text
}
Example:
hostname(config)# logging device-id hostname
hostname(config)# logging device-id context-name
Configures the ASA or ASASM to include a device ID in
non-EMBLEM-format syslog messages. You can specify only
one type of device ID for syslog messages.The
context-name
keyword indicates that the name of the current context should
be used as the device ID (applies to multiple context mode
only). If you enable the logging device ID for the admin
context in multiple context mode, messages that originate in
the system execution space use a device ID of
system
, and
messages that originate in the admin context use the name of
the admin context as the device ID.
Note
In an ASA cluster, always use the master unit IP
address for the selected interface.
The
cluster-id
keyword specifies the unique name in the boot
configuration of an individual ASA unit in the cluster as the
device ID. The
hostname
keyword specifies that the hostname
of the ASA should be used as the device ID. The
ipaddress
interface_name
keyword-argument pair specifies that the
interface IP address specified as
interface_name
should be
used as the device ID. If you use the
ipaddress
keyword, the
device ID becomes the specified ASA interface IP address,
regardless of the interface from which the syslog message is
sent. In the cluster environment, the
system
keyword dictates
that the device ID becomes the system IP address on the
interface. This keyword provides a single, consistent device
ID for all syslog messages that are sent from the device. The
string
text
keyword-argument pair specifies that the text string
should be used as the device ID. The string can include as
many as 16 characters.
You cannot use blank spaces or any of the following
characters:
•
& (ampersand)
•
‘ (single quote)
•
“ (double quote)
•
< (less than)
•
> (greater than)
•
? (question mark)
Note
If enabled, the device ID does not appear in
EMBLEM-formatted syslog messages nor in SNMP
traps.
Summary of Contents for 5505 - ASA Firewall Edition Bundle
Page 28: ...Glossary GL 24 Cisco ASA Series CLI Configuration Guide ...
Page 61: ...P A R T 1 Getting Started with the ASA ...
Page 62: ......
Page 219: ...P A R T 2 Configuring High Availability and Scalability ...
Page 220: ......
Page 403: ...P A R T 2 Configuring Interfaces ...
Page 404: ......
Page 499: ...P A R T 2 Configuring Basic Settings ...
Page 500: ......
Page 533: ...P A R T 2 Configuring Objects and Access Lists ...
Page 534: ......
Page 601: ...P A R T 2 Configuring IP Routing ...
Page 602: ......
Page 745: ...P A R T 2 Configuring Network Address Translation ...
Page 746: ......
Page 845: ...P A R T 2 Configuring AAA Servers and the Local Database ...
Page 846: ......
Page 981: ...P A R T 2 Configuring Access Control ...
Page 982: ......
Page 1061: ...P A R T 2 Configuring Service Policies Using the Modular Policy Framework ...
Page 1062: ......
Page 1093: ...P A R T 2 Configuring Application Inspection ...
Page 1094: ......
Page 1191: ...P A R T 2 Configuring Unified Communications ...
Page 1192: ......
Page 1333: ...P A R T 2 Configuring Connection Settings and QoS ...
Page 1334: ......
Page 1379: ...P A R T 2 Configuring Advanced Network Protection ...
Page 1380: ......
Page 1475: ...P A R T 2 Configuring Modules ...
Page 1476: ......
Page 1549: ...P A R T 2 Configuring VPN ...
Page 1550: ......
Page 1965: ...P A R T 2 Configuring Logging SNMP and Smart Call Home ...
Page 1966: ......
Page 2059: ...P A R T 2 System Administration ...
Page 2060: ......
Page 2098: ...1 8 Cisco ASA Series CLI Configuration Guide Chapter 1 Troubleshooting Viewing the Coredump ...
Page 2099: ...P A R T 2 Reference ...
Page 2100: ......