<?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: accessing VSX member in winscp in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/accessing-VSX-member-in-winscp/m-p/212006#M35134</link>
    <description>&lt;P&gt;I don't understand the problem. Just connect with WinSCP to the IP and browse to /var/log and copy the files. Make sure the user you use ends up in /bin/bash maybe WinSCP will give an error related to this. You might also get fingerprint pop-up the first time you connect.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 23 Apr 2024 07:15:36 GMT</pubDate>
    <dc:creator>Lesley</dc:creator>
    <dc:date>2024-04-23T07:15:36Z</dc:date>
    <item>
      <title>accessing VSX member in winscp</title>
      <link>https://community.checkpoint.com/t5/General-Topics/accessing-VSX-member-in-winscp/m-p/212002#M35133</link>
      <description>&lt;P&gt;Hi Mates,&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I'm trying to access the log files located in the &lt;/SPAN&gt;/var/log&lt;SPAN&gt; directories of the individual VSX cluster members. Could you advise on the appropriate method for accessing these logs using winscp tools?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 23 Apr 2024 06:55:22 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/accessing-VSX-member-in-winscp/m-p/212002#M35133</guid>
      <dc:creator>Ihenock1011</dc:creator>
      <dc:date>2024-04-23T06:55:22Z</dc:date>
    </item>
    <item>
      <title>Re: accessing VSX member in winscp</title>
      <link>https://community.checkpoint.com/t5/General-Topics/accessing-VSX-member-in-winscp/m-p/212006#M35134</link>
      <description>&lt;P&gt;I don't understand the problem. Just connect with WinSCP to the IP and browse to /var/log and copy the files. Make sure the user you use ends up in /bin/bash maybe WinSCP will give an error related to this. You might also get fingerprint pop-up the first time you connect.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 23 Apr 2024 07:15:36 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/accessing-VSX-member-in-winscp/m-p/212006#M35134</guid>
      <dc:creator>Lesley</dc:creator>
      <dc:date>2024-04-23T07:15:36Z</dc:date>
    </item>
    <item>
      <title>Re: accessing VSX member in winscp</title>
      <link>https://community.checkpoint.com/t5/General-Topics/accessing-VSX-member-in-winscp/m-p/212008#M35135</link>
      <description>&lt;P&gt;You need to know the number ID of your VS.&lt;/P&gt;
&lt;P&gt;Then the file structure will be something like this.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;/opt/CPsuite-R81.10/fw1/CTX/CTX00005/log/&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In expert mode, this corresponds to typing vsenv 5, then cd $FWDIR/log/ on a R81.10 VSX cluster member.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Apr 2024 07:23:16 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/accessing-VSX-member-in-winscp/m-p/212008#M35135</guid>
      <dc:creator>Alex-</dc:creator>
      <dc:date>2024-04-23T07:23:16Z</dc:date>
    </item>
    <item>
      <title>Re: accessing VSX member in winscp</title>
      <link>https://community.checkpoint.com/t5/General-Topics/accessing-VSX-member-in-winscp/m-p/212009#M35136</link>
      <description>&lt;P&gt;Dear&amp;nbsp;&lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/73547"&gt;@Lesley&lt;/a&gt;&amp;nbsp; &lt;SPAN&gt;When I connect to the VSX cluster's IP address, I can access the default VSX member (VSenv 0). However, I'd like to access a specific member, such as VSenv 1 or VSenv 2.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 23 Apr 2024 07:20:40 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/accessing-VSX-member-in-winscp/m-p/212009#M35136</guid>
      <dc:creator>Ihenock1011</dc:creator>
      <dc:date>2024-04-23T07:20:40Z</dc:date>
    </item>
    <item>
      <title>Re: accessing VSX member in winscp</title>
      <link>https://community.checkpoint.com/t5/General-Topics/accessing-VSX-member-in-winscp/m-p/212011#M35137</link>
      <description>&lt;P&gt;Ah check, VSX for me is VS0 in as stated in opening post &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;But what Alex typed is correct.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 23 Apr 2024 07:21:52 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/accessing-VSX-member-in-winscp/m-p/212011#M35137</guid>
      <dc:creator>Lesley</dc:creator>
      <dc:date>2024-04-23T07:21:52Z</dc:date>
    </item>
  </channel>
</rss>

