<?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 Syslog Configuration. in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/syslog-configuration/m-p/4607218#M241714</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Product : C9800-L-F-K9&lt;/P&gt;&lt;P&gt;IOS Version :&amp;nbsp;17.3.3 (Amsterdam)&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;We want to configure syslog forwarding using TCP.&lt;BR /&gt;We want to enable blocking of TCP connections for syslog forwarding IF the syslog server destination is down.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Question:&lt;BR /&gt;We want to check if this command is supported in our WLC?&lt;BR /&gt;logging permit-hostdown (Command taken from Cisco ASA)&lt;/P&gt;</description>
    <pubDate>Tue, 10 May 2022 05:21:42 GMT</pubDate>
    <dc:creator>shahinmadambi585</dc:creator>
    <dc:date>2022-05-10T05:21:42Z</dc:date>
    <item>
      <title>Syslog Configuration.</title>
      <link>https://community.cisco.com/t5/wireless/syslog-configuration/m-p/4607218#M241714</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Product : C9800-L-F-K9&lt;/P&gt;&lt;P&gt;IOS Version :&amp;nbsp;17.3.3 (Amsterdam)&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;We want to configure syslog forwarding using TCP.&lt;BR /&gt;We want to enable blocking of TCP connections for syslog forwarding IF the syslog server destination is down.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Question:&lt;BR /&gt;We want to check if this command is supported in our WLC?&lt;BR /&gt;logging permit-hostdown (Command taken from Cisco ASA)&lt;/P&gt;</description>
      <pubDate>Tue, 10 May 2022 05:21:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/syslog-configuration/m-p/4607218#M241714</guid>
      <dc:creator>shahinmadambi585</dc:creator>
      <dc:date>2022-05-10T05:21:42Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog Configuration.</title>
      <link>https://community.cisco.com/t5/wireless/syslog-configuration/m-p/4607226#M241716</link>
      <description>&lt;P&gt;That command is not on 9800, but you can set a custom port for syslog (only via cli)&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;loggin host &amp;lt;IP Address&amp;gt; transport &amp;lt;TCP/UDP&amp;gt; port &amp;lt;PortNumber&amp;gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;hope this helps&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 10 May 2022 06:39:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/syslog-configuration/m-p/4607226#M241716</guid>
      <dc:creator>Ambuj M</dc:creator>
      <dc:date>2022-05-10T06:39:12Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog Configuration.</title>
      <link>https://community.cisco.com/t5/wireless/syslog-configuration/m-p/4607333#M241721</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;We know the configuration for syslog forwarding. What&amp;nbsp;&lt;/SPAN&gt;we want to know is whether we need a command to block TCP sessions if the syslog server at the destination is down and resume if the syslog server located at the destination is up online.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This will prevent the TCP sessions from being stuck at the source side (WLC) and eventually causing the WLC to hang.&lt;/P&gt;&lt;P&gt;Is there such a command for the WLC?&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;You may refer to this link:&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/asa/asa84/configuration/guide/asa_84_cli_config/monitor_syslog.html" target="_blank" rel="noopener"&gt;https://www.cisco.com/c/en/us/td/docs/security/asa/asa84/configuration/guide/asa_84_cli_config/monitor_syslog.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="reffer.JPG" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/150898i7EB6E36C49A7B579/image-size/large?v=v2&amp;amp;px=999" role="button" title="reffer.JPG" alt="reffer.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 10 May 2022 09:32:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/syslog-configuration/m-p/4607333#M241721</guid>
      <dc:creator>shahinmadambi585</dc:creator>
      <dc:date>2022-05-10T09:32:08Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog Configuration.</title>
      <link>https://community.cisco.com/t5/wireless/syslog-configuration/m-p/4607362#M241722</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;U&gt;&lt;EM&gt; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;gt;....if the syslog server at the destination is down and resume if the syslog server located at the destination is up online.&lt;/EM&gt;&lt;/U&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;Well that's the benefit of using standard &lt;STRONG&gt;&lt;FONT color="#008000"&gt;UDP&lt;/FONT&gt;&lt;/STRONG&gt; based syslog (&lt;FONT color="#0000FF"&gt;only&lt;/FONT&gt;) which is &lt;EM&gt;stateless&lt;/EM&gt; and &lt;STRONG&gt;your&lt;/STRONG&gt; device or neither&amp;nbsp; the receiver will be bothered if the destination is offline.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Tue, 10 May 2022 10:20:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/syslog-configuration/m-p/4607362#M241722</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2022-05-10T10:20:39Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog Configuration.</title>
      <link>https://community.cisco.com/t5/wireless/syslog-configuration/m-p/4607497#M241740</link>
      <description>&lt;P&gt;You can use the below&lt;/P&gt;
&lt;P&gt;ip tcp synwait-time &amp;lt;seconds&amp;gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This defines the&amp;nbsp;&lt;SPAN&gt;period of time the Cisco IOS software waits while attempting to establish a TCP connection before it times out&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 10 May 2022 13:51:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/syslog-configuration/m-p/4607497#M241740</guid>
      <dc:creator>Arshad Safrulla</dc:creator>
      <dc:date>2022-05-10T13:51:55Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog Configuration.</title>
      <link>https://community.cisco.com/t5/wireless/syslog-configuration/m-p/4608889#M241858</link>
      <description>&lt;P&gt;Thank you for your suggestion.&lt;/P&gt;&lt;P&gt;However, we do not want to use UDP because it is not reliable as TCP.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Our problem:&lt;/P&gt;&lt;P&gt;If we use TCP without the logging permit-hostdown command, in the event if the destination server is down, all TCP sessions will be stuck inside the source device and will cause the source device (ASA Firewall) to hang.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We want to avoid such kind of situation and that is why we want to use the logging permit-hostdown CLI.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, we are not sure if this command is compatible with our WLC?&lt;/P&gt;&lt;P&gt;My question is very simple. Could you confirm if the logging permit-hostdown can be used in the WLC please?&lt;/P&gt;</description>
      <pubDate>Thu, 12 May 2022 09:53:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/syslog-configuration/m-p/4608889#M241858</guid>
      <dc:creator>shahinmadambi585</dc:creator>
      <dc:date>2022-05-12T09:53:18Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog Configuration.</title>
      <link>https://community.cisco.com/t5/wireless/syslog-configuration/m-p/4608943#M241863</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;EM&gt; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;gt;...&lt;U&gt;.However, we do not want to use UDP because it is not reliable as TCP.&lt;/U&gt;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; - On pure Inr&lt;U&gt;&lt;FONT color="#0000FF"&gt;&lt;STRONG&gt;a&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/U&gt;net environments , like for instance no WAN and or VPN connections between source and destination ,&lt;EM&gt; then UDP is as much reliable as TCP.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Thu, 12 May 2022 11:33:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/syslog-configuration/m-p/4608943#M241863</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2022-05-12T11:33:53Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog Configuration.</title>
      <link>https://community.cisco.com/t5/wireless/syslog-configuration/m-p/4611708#M242023</link>
      <description>&lt;P&gt;NO!&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;That is a firewall security logging requirement feature - nothing to do with devices hanging.&lt;/P&gt;
&lt;P&gt;The WLC is NOT a firewall.&lt;/P&gt;
&lt;P&gt;If you want your connections logged with that feature they will have to be routed through an ASA firewall to do that logging.&lt;/P&gt;</description>
      <pubDate>Tue, 17 May 2022 15:08:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/syslog-configuration/m-p/4611708#M242023</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2022-05-17T15:08:54Z</dc:date>
    </item>
  </channel>
</rss>

