<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: PIX log timestamp in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-log-timestamp/m-p/79125#M641702</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That number is the message severity number (ie number that identifies what the message is in order for to look it up on the website).  When you enable timestamp logging, it only applies to messages being sent to the syslog.  I don't believe you can add the timestamp on there, only syslog, as cisco says"PIX Firewall provides more information in messages sent to a syslog server than at the console, but the console provides enough information to permit effective troubleshooting." &lt;/P&gt;&lt;P&gt;Steve&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 07 Oct 2002 17:50:48 GMT</pubDate>
    <dc:creator>steve.barlow</dc:creator>
    <dc:date>2002-10-07T17:50:48Z</dc:date>
    <item>
      <title>PIX log timestamp</title>
      <link>https://community.cisco.com/t5/network-security/pix-log-timestamp/m-p/79124#M641666</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;How can I get the PIX log to show a timestamp that shows the time and date.&lt;/P&gt;&lt;P&gt;I get a strange #. Below is my show clock and show log output.&lt;/P&gt;&lt;P&gt;thanks,&lt;/P&gt;&lt;P&gt;rrc&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; PIX(config)# sh logg&lt;/P&gt;&lt;P&gt;&amp;gt; Syslog logging: enabled&lt;/P&gt;&lt;P&gt;&amp;gt;     Facility: 20&lt;/P&gt;&lt;P&gt;&amp;gt;     Timestamp logging: enabled&lt;/P&gt;&lt;P&gt;&amp;gt;     Standby logging: disabled&lt;/P&gt;&lt;P&gt;&amp;gt;     Console logging: disabled&lt;/P&gt;&lt;P&gt;&amp;gt;     Monitor logging: disabled&lt;/P&gt;&lt;P&gt;&amp;gt;     Buffer logging: level debugging, 29 messages&lt;/P&gt;&lt;P&gt;&amp;gt; logged&lt;/P&gt;&lt;P&gt;&amp;gt;     Trap logging: disabled&lt;/P&gt;&lt;P&gt;&amp;gt;     History logging: level informational, 25&lt;/P&gt;&lt;P&gt;&amp;gt; messages logged&lt;/P&gt;&lt;P&gt;&amp;gt; 199002: PIX startup completed.  Beginning operation.&lt;/P&gt;&lt;P&gt;&amp;gt; 609001: Built local-host inside:10.1.1.10&lt;/P&gt;&lt;P&gt;&amp;gt; 305011: Built dynamic ICMP translation from&lt;/P&gt;&lt;P&gt;&amp;gt; inside:10.1.1.10/51204 to&lt;/P&gt;&lt;P&gt;&amp;gt; outside:172.17.63.210/0&lt;/P&gt;&lt;P&gt;&amp;gt; 305011: Built dynamic UDP translation from&lt;/P&gt;&lt;P&gt;&amp;gt; inside:10.1.1.10/1028 to&lt;/P&gt;&lt;P&gt;&amp;gt; outside:172.17.63.210/1024&lt;/P&gt;&lt;P&gt;&amp;gt; 302015: Built outbound UDP connection 0 for&lt;/P&gt;&lt;P&gt;&amp;gt; outside:172.17.63.209/3006&lt;/P&gt;&lt;P&gt;&amp;gt; (172.17.63.209/3006) to inside:10.1.1.10/1028&lt;/P&gt;&lt;P&gt;&amp;gt; (172.17.63.210/1024)&lt;/P&gt;&lt;P&gt;&amp;gt; 101003: (Secondary) Failover cable not connected&lt;/P&gt;&lt;P&gt;&amp;gt; (this unit)&lt;/P&gt;&lt;P&gt;&amp;gt; 302015: Built outbound UDP connection 1 for&lt;/P&gt;&lt;P&gt;&amp;gt; outside:10.0.0.2/3006&lt;/P&gt;&lt;P&gt;&amp;gt; (10.0.0.2/3006) to inside:10.1.1.10/1028&lt;/P&gt;&lt;P&gt;&amp;gt; (172.17.63.210/1024)&lt;/P&gt;&lt;P&gt;&amp;gt; 302015: Built outbound UDP connection 2 for&lt;/P&gt;&lt;P&gt;&amp;gt; outside:10.0.0.1/3006&lt;/P&gt;&lt;P&gt;&amp;gt; (10.0.0.1/3006) to inside:10.1.1.10/1028&lt;/P&gt;&lt;P&gt;&amp;gt; (172.17.63.210/1024)&lt;/P&gt;&lt;P&gt;&amp;gt; 302010: 3 in use, 3 most used&lt;/P&gt;&lt;P&gt;&amp;gt; 502103: User priv level changed: Uname: enable_1&lt;/P&gt;&lt;P&gt;&amp;gt; From: 1 To: 15&lt;/P&gt;&lt;P&gt;&amp;gt; 111008: User 'enable_1' executed the 'enable'&lt;/P&gt;&lt;P&gt;&amp;gt; command.&lt;/P&gt;&lt;P&gt;&amp;gt; 111009: User 'enable_15' executed cmd: show version&lt;/P&gt;&lt;P&gt;&amp;gt; 111007: Begin configuration: console reading from&lt;/P&gt;&lt;P&gt;&amp;gt; terminal&lt;/P&gt;&lt;P&gt;&amp;gt; 111008: User 'enable_15' executed the 'configure t'&lt;/P&gt;&lt;P&gt;&amp;gt; command.&lt;/P&gt;&lt;P&gt;&amp;gt; 111008: User 'enable_15' executed the 'http 10.1.1.0&lt;/P&gt;&lt;P&gt;&amp;gt; 255.255.255.0 inside'&lt;/P&gt;&lt;P&gt;&amp;gt; command.&lt;/P&gt;&lt;P&gt;&amp;gt; PIX(config)#  &lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; PIX(config)# sh clock&lt;/P&gt;&lt;P&gt;&amp;gt; 11:22:53.865 UTC Fri Oct 4 2002&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 06:17:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-log-timestamp/m-p/79124#M641666</guid>
      <dc:creator>rcrumm_2</dc:creator>
      <dc:date>2020-02-21T06:17:20Z</dc:date>
    </item>
    <item>
      <title>Re: PIX log timestamp</title>
      <link>https://community.cisco.com/t5/network-security/pix-log-timestamp/m-p/79125#M641702</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That number is the message severity number (ie number that identifies what the message is in order for to look it up on the website).  When you enable timestamp logging, it only applies to messages being sent to the syslog.  I don't believe you can add the timestamp on there, only syslog, as cisco says"PIX Firewall provides more information in messages sent to a syslog server than at the console, but the console provides enough information to permit effective troubleshooting." &lt;/P&gt;&lt;P&gt;Steve&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Oct 2002 17:50:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-log-timestamp/m-p/79125#M641702</guid>
      <dc:creator>steve.barlow</dc:creator>
      <dc:date>2002-10-07T17:50:48Z</dc:date>
    </item>
  </channel>
</rss>

