<?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 To track a UDP syslog traffic 514/udp in Routing and SD-WAN</title>
    <link>https://community.cisco.com/t5/routing-and-sd-wan/to-track-a-udp-syslog-traffic-514-udp/m-p/1045913#M89880</link>
    <description>&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would like to track a UDP syslog traffic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want to do a access-list but how can I do it without applying on the serial interface?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can I just do a ip access-list 101 xx xx &lt;/P&gt;&lt;P&gt;on the config mode and track from there?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause that access-list doesn;t seems to log the traffic. I did a test on permit any any.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advanced.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;cindy&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 04 Mar 2019 06:53:43 GMT</pubDate>
    <dc:creator>cindylee27</dc:creator>
    <dc:date>2019-03-04T06:53:43Z</dc:date>
    <item>
      <title>To track a UDP syslog traffic 514/udp</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/to-track-a-udp-syslog-traffic-514-udp/m-p/1045913#M89880</link>
      <description>&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would like to track a UDP syslog traffic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want to do a access-list but how can I do it without applying on the serial interface?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can I just do a ip access-list 101 xx xx &lt;/P&gt;&lt;P&gt;on the config mode and track from there?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause that access-list doesn;t seems to log the traffic. I did a test on permit any any.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advanced.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;cindy&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 04 Mar 2019 06:53:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/to-track-a-udp-syslog-traffic-514-udp/m-p/1045913#M89880</guid>
      <dc:creator>cindylee27</dc:creator>
      <dc:date>2019-03-04T06:53:43Z</dc:date>
    </item>
    <item>
      <title>Re: To track a UDP syslog traffic 514/udp</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/to-track-a-udp-syslog-traffic-514-udp/m-p/1045914#M89881</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;don't forget&lt;/P&gt;&lt;P&gt;"Access lists that are applied to interfaces do not filter traffic that originates from that router."&lt;/P&gt;&lt;P&gt;see &lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/docs/ios/12_2/security/configuration/guide/scfacls.html" target="_blank"&gt;http://www.cisco.com/en/US/docs/ios/12_2/security/configuration/guide/scfacls.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So you can't log syslog traffic sent from a router by an ACL applied on an interface on the same router &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR,&lt;/P&gt;&lt;P&gt;Milan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Jul 2008 05:49:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/to-track-a-udp-syslog-traffic-514-udp/m-p/1045914#M89881</guid>
      <dc:creator>milan.kulik</dc:creator>
      <dc:date>2008-07-25T05:49:40Z</dc:date>
    </item>
    <item>
      <title>Re: To track a UDP syslog traffic 514/udp</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/to-track-a-udp-syslog-traffic-514-udp/m-p/1045915#M89882</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;well, you got me wrong Milan..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The syslog traffic is from another device which is passing thru this router..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so now i wan to make sure that the syslog traffic indeed pass thru to proof that there is syslog coming from the device.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Jul 2008 07:25:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/to-track-a-udp-syslog-traffic-514-udp/m-p/1045915#M89882</guid>
      <dc:creator>cindylee27</dc:creator>
      <dc:date>2008-07-25T07:25:35Z</dc:date>
    </item>
    <item>
      <title>Re: To track a UDP syslog traffic 514/udp</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/to-track-a-udp-syslog-traffic-514-udp/m-p/1045916#M89883</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A access list must be applied to a interface. You can in general apply it to either the outbound or inbound but just keying it in does nothing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A access list like&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;permit udp any any eq syslog log&lt;/P&gt;&lt;P&gt;permit ip any any &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Should get you what you need and cause no disruption to the traffic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are other ways like ip accounting or nbar that can be used to do this but all will require you to make configuration changes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Jul 2008 13:53:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/to-track-a-udp-syslog-traffic-514-udp/m-p/1045916#M89883</guid>
      <dc:creator>tdrais</dc:creator>
      <dc:date>2008-07-25T13:53:05Z</dc:date>
    </item>
  </channel>
</rss>

