<?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: nabox 4.x adding systems in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/nabox-4-x-adding-systems/m-p/455053#M43953</link>
    <description>&lt;P&gt;Thread can be set as resolved. We have installed 3.x, there you have the option to select insecure ssl. That made it work.&amp;nbsp;&lt;a href="https://community.netapp.com/t5/user/viewprofilepage/user-id/65619"&gt;@TMACMD&lt;/a&gt; thank you, I think this option should be also added to the 4.x ova appliance&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 13 Sep 2024 13:09:14 GMT</pubDate>
    <dc:creator>thor1887</dc:creator>
    <dc:date>2024-09-13T13:09:14Z</dc:date>
    <item>
      <title>nabox 4.x adding systems</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/nabox-4-x-adding-systems/m-p/455046#M43950</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;we have installed. NABOX 4.0.7 ova.&lt;/P&gt;&lt;P&gt;Now we are not able to connect systems.&lt;/P&gt;&lt;P&gt;Error:&amp;nbsp; Error while updating system poller does not exists&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;{"message":"Get \"&lt;A class="" title="https://10.1.70.235/api/cluster/%22:" href="https://10.1.70.235/api/cluster\%22:" target="_blank" rel="noreferrer noopener"&gt;https://10.1.70.235/api/cluster\":&lt;/A&gt; tls: failed to verify certificate: x509: certificate signed by unknown authority"} {"message":"invalid poller name"}&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks a lot,&lt;/P&gt;&lt;P&gt;Thorsten&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2024 11:58:13 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/nabox-4-x-adding-systems/m-p/455046#M43950</guid>
      <dc:creator>thor1887</dc:creator>
      <dc:date>2024-09-13T11:58:13Z</dc:date>
    </item>
    <item>
      <title>Re: nabox 4.x adding systems</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/nabox-4-x-adding-systems/m-p/455047#M43951</link>
      <description>&lt;P&gt;Any ideas?&lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2024 11:59:23 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/nabox-4-x-adding-systems/m-p/455047#M43951</guid>
      <dc:creator>thor1887</dc:creator>
      <dc:date>2024-09-13T11:59:23Z</dc:date>
    </item>
    <item>
      <title>Re: nabox 4.x adding systems</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/nabox-4-x-adding-systems/m-p/455051#M43952</link>
      <description>&lt;P&gt;Check the certificates on ONTAP&lt;/P&gt;&lt;P&gt;&amp;nbsp;set diag&lt;/P&gt;&lt;P&gt;&amp;nbsp;security certificate show -type server -fields exp -sort-by exp&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;set admin&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2024 12:13:13 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/nabox-4-x-adding-systems/m-p/455051#M43952</guid>
      <dc:creator>TMACMD</dc:creator>
      <dc:date>2024-09-13T12:13:13Z</dc:date>
    </item>
    <item>
      <title>Re: nabox 4.x adding systems</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/nabox-4-x-adding-systems/m-p/455053#M43953</link>
      <description>&lt;P&gt;Thread can be set as resolved. We have installed 3.x, there you have the option to select insecure ssl. That made it work.&amp;nbsp;&lt;a href="https://community.netapp.com/t5/user/viewprofilepage/user-id/65619"&gt;@TMACMD&lt;/a&gt; thank you, I think this option should be also added to the 4.x ova appliance&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2024 13:09:14 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/nabox-4-x-adding-systems/m-p/455053#M43953</guid>
      <dc:creator>thor1887</dc:creator>
      <dc:date>2024-09-13T13:09:14Z</dc:date>
    </item>
    <item>
      <title>Re: nabox 4.x adding systems</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/nabox-4-x-adding-systems/m-p/455054#M43954</link>
      <description>&lt;P&gt;You could also just create a new server certificate for the cluster. If you are not using signed certificates, I just create a 10 year self signed cert. problem solved. When creating the cert be sure to tab out the expiration which defaults to 365 then just tack a zero on the end and make it 3650.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;if you have expired certs it my bite you in other ways. You should really correct them&lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2024 13:30:40 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/nabox-4-x-adding-systems/m-p/455054#M43954</guid>
      <dc:creator>TMACMD</dc:creator>
      <dc:date>2024-09-13T13:30:40Z</dc:date>
    </item>
  </channel>
</rss>

