User's Manual

Configuring GRE, NAT, RIPSO, and BFE Services
2-26
308625-14.00 Rev 00
Logging NAT Messages
By default, the router does not log NAT messages. You can enable the logging of
messages by specifying the types of messages that the router should log. Table 2-1
lists the message types that can be logged by NAT software. If you enable logging,
the change is effective immediately (if there are any messages to be logged).
Using the BCC
To specify the types of log messages that are reported by NAT software, navigate
to the global NAT prompt (for example,
box; ip; nat
) and enter:
log-mask
<mask_keyword>
mask_keyword
can be one or more keywords representing the log type (see
Table 2-1
). If you enter more than one keyword, you must enclose them in braces
or in quotation marks. The default is none. To select all log messages, enter:
log-mask all
For example, the following command enables the logging of NAT event messages
with the logging levels NAT_DBG_MIB_LOG and NAT_DBG_IP_LOG:
nat#
log-mask {mib ip}
nat#
Table 2-1. NAT Log Message Types
Message Type Definition Bit Position Hex Value BCC Keyword
NAT_DBG_MIB_LOG MIB-related events 0 0x00000001 mib
NAT_DBG_IP_LOG Debug events at IP level 1 0x00000002 ip
NAT_DBG_FWD_LOG Forwarding events 2 0x00000004 forwarding
NAT_DBG_MAPPING_LOG Translation table events 3 0x00000008 mapping
NAT_DBG_AGING_LOG Aging level events 4 0x00000010 aging
NAT_DBG_SYNCH_LOG Synchronization events 5 0x00000020 synchronization