<?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: css support log in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/css-support-log/m-p/853532#M16680</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes you can. With CSS you can enable/disable syslog for different Subsystems.Service transitions are logged by "netman subsystem".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you use the default netman (level 4) you will  see the service failures. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You need to increase the logging on the "netman" subsystem" to at least level 5. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;logging subsystem netman level notice-5&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Level 5 will show the services coming back up as well. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;More Details at&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/css11500series/v7.50/configuration/administration/guide/Logging.html" target="_blank"&gt;http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/css11500series/v7.50/configuration/administration/guide/Logging.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Syed&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 18 Oct 2007 01:14:09 GMT</pubDate>
    <dc:creator>Syed Iftekhar Ahmed</dc:creator>
    <dc:date>2007-10-18T01:14:09Z</dc:date>
    <item>
      <title>css support log</title>
      <link>https://community.cisco.com/t5/application-networking/css-support-log/m-p/853531#M16679</link>
      <description>&lt;P&gt;in a css support file log, i mean logging and sent to syslog server?&lt;/P&gt;&lt;P&gt;if the real server down, css can capture this event via log ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;</description>
      <pubDate>Thu, 18 Oct 2007 00:49:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-support-log/m-p/853531#M16679</guid>
      <dc:creator>giordano234</dc:creator>
      <dc:date>2007-10-18T00:49:16Z</dc:date>
    </item>
    <item>
      <title>Re: css support log</title>
      <link>https://community.cisco.com/t5/application-networking/css-support-log/m-p/853532#M16680</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes you can. With CSS you can enable/disable syslog for different Subsystems.Service transitions are logged by "netman subsystem".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you use the default netman (level 4) you will  see the service failures. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You need to increase the logging on the "netman" subsystem" to at least level 5. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;logging subsystem netman level notice-5&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Level 5 will show the services coming back up as well. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;More Details at&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/css11500series/v7.50/configuration/administration/guide/Logging.html" target="_blank"&gt;http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/css11500series/v7.50/configuration/administration/guide/Logging.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Syed&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Oct 2007 01:14:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-support-log/m-p/853532#M16680</guid>
      <dc:creator>Syed Iftekhar Ahmed</dc:creator>
      <dc:date>2007-10-18T01:14:09Z</dc:date>
    </item>
  </channel>
</rss>

