<?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: WAAS exporting tfo logs via sftp in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/waas-exporting-tfo-logs-via-sftp/m-p/1115225#M22809</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Cameron,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Why does the export fail with a leading / in the path?  Is that not a valid path on the target server?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you perform the following debug and send the syslog.txt file:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From config mode:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;logg disk prior debug&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From enable mode:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;transaction-log force export&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Zach&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 21 Aug 2008 16:45:19 GMT</pubDate>
    <dc:creator>Zach Seils</dc:creator>
    <dc:date>2008-08-21T16:45:19Z</dc:date>
    <item>
      <title>WAAS exporting tfo logs via sftp</title>
      <link>https://community.cisco.com/t5/application-networking/waas-exporting-tfo-logs-via-sftp/m-p/1115224#M22808</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Running WAAS 4.0.19. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've stuck an issue where the CLI command on an edge WAE:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;transaction-logs export sftp-server 10.1.1.1 tst1wae01 password logs/raw&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;...is accepted but when you then try and use the Transaction Logs page of that WAE in the Central Manager's GUI and make a different change (say the interval), the GUI throws up an error:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"Directory1 must start with forward slash"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I put a forward slash in at the GUI and save it, the export will fail. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The export works when I force the WAE to use the line specified as per the CLI. If I do this the GUI shows the path as "logs/raw" which is what I want. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyway, the work around works but it is annoying because I effectively cannot use the GUI page for transaction log changes. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone else seen this? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;Cameron&lt;/P&gt;</description>
      <pubDate>Wed, 20 Aug 2008 05:11:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/waas-exporting-tfo-logs-via-sftp/m-p/1115224#M22808</guid>
      <dc:creator>cstockwe</dc:creator>
      <dc:date>2008-08-20T05:11:26Z</dc:date>
    </item>
    <item>
      <title>Re: WAAS exporting tfo logs via sftp</title>
      <link>https://community.cisco.com/t5/application-networking/waas-exporting-tfo-logs-via-sftp/m-p/1115225#M22809</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Cameron,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Why does the export fail with a leading / in the path?  Is that not a valid path on the target server?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you perform the following debug and send the syslog.txt file:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From config mode:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;logg disk prior debug&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From enable mode:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;transaction-log force export&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Zach&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Aug 2008 16:45:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/waas-exporting-tfo-logs-via-sftp/m-p/1115225#M22809</guid>
      <dc:creator>Zach Seils</dc:creator>
      <dc:date>2008-08-21T16:45:19Z</dc:date>
    </item>
    <item>
      <title>Re: WAAS exporting tfo logs via sftp</title>
      <link>https://community.cisco.com/t5/application-networking/waas-exporting-tfo-logs-via-sftp/m-p/1115226#M22810</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Zach&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It looks like that the SFTP server's directory I was supplied is not an absolute path. If I put in the absolute path "/home/tst1wae01/logs/raw" it works ok. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I suppose the strange thing that I was raising was the fact that the CLI will accept a command without the leading '/' but the central manager GUI won't. &lt;/P&gt;&lt;P&gt;&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, 22 Aug 2008 00:20:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/waas-exporting-tfo-logs-via-sftp/m-p/1115226#M22810</guid>
      <dc:creator>cstockwe</dc:creator>
      <dc:date>2008-08-22T00:20:50Z</dc:date>
    </item>
    <item>
      <title>Re: WAAS exporting tfo logs via sftp</title>
      <link>https://community.cisco.com/t5/application-networking/waas-exporting-tfo-logs-via-sftp/m-p/1115227#M22811</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It's a valid point.  I have opened defect ID CSCsu09642 to have it fixed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Zach&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Aug 2008 04:15:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/waas-exporting-tfo-logs-via-sftp/m-p/1115227#M22811</guid>
      <dc:creator>Zach Seils</dc:creator>
      <dc:date>2008-08-22T04:15:05Z</dc:date>
    </item>
  </channel>
</rss>

