<?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: Device Archives in Inventory Manager fail with a Device Busy error in ExtremeCloud IQ- Site Engine Management Center</title>
    <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/device-archives-in-inventory-manager-fail-with-a-device-busy/m-p/96167#M9879</link>
    <description>&lt;P&gt;I would suggest confirming or posting what the Inventory Settings are for this device. They may be improperly set to use the&amp;nbsp;&lt;SPAN&gt;etsysConfigMgmtChangeTable MIB vs a script.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Otherwise please consider opening a support case to further investigate this issue.&lt;/P&gt;&lt;P&gt;If you can SSH to the appliance via WebShell and manually issue a SCP command to offload the config towards XIQ-SE using XIQ-SE's 'root' or 'netsight' credentials I see no reason why the scripts would fail.&lt;/P&gt;</description>
    <pubDate>Mon, 19 Jun 2023 12:33:05 GMT</pubDate>
    <dc:creator>Robert_Haynes</dc:creator>
    <dc:date>2023-06-19T12:33:05Z</dc:date>
    <item>
      <title>Device Archives in Inventory Manager fail with a Device Busy error</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/device-archives-in-inventory-manager-fail-with-a-device-busy/m-p/96162#M9877</link>
      <description>&lt;P&gt;I have one switch that fails on archive and compiance checks in Site Engine.&amp;nbsp;&lt;/P&gt;&lt;P&gt;The switch in question still works fine, management access, ssh, snmp etc works as it should.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Switch model :&amp;nbsp;VSP4900-12MXU-12XE&lt;BR /&gt;Ver:&amp;nbsp;8.9.0.0&lt;/P&gt;&lt;P&gt;Site engine ver:&amp;nbsp;&lt;SPAN&gt;22.9.13.5&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Errormessage in Site Engine:&amp;nbsp;Site Engine Archive - Device Busy - Waiting...&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I found this article:&amp;nbsp;&lt;A href="https://extremeportal.force.com/ExtrArticleDetail?an=000061637" target="_blank"&gt;https://extremeportal.force.com/ExtrArticleDetail?an=000061637&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;But it's a bit different product line, and that solution doesn't fit this switch model. Any ideas other tnan just reboot the switch in question?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jun 2023 10:43:05 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/device-archives-in-inventory-manager-fail-with-a-device-busy/m-p/96162#M9877</guid>
      <dc:creator>AyuCon</dc:creator>
      <dc:date>2023-06-19T10:43:05Z</dc:date>
    </item>
    <item>
      <title>Re: Device Archives in Inventory Manager fail with a Device Busy error</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/device-archives-in-inventory-manager-fail-with-a-device-busy/m-p/96167#M9879</link>
      <description>&lt;P&gt;I would suggest confirming or posting what the Inventory Settings are for this device. They may be improperly set to use the&amp;nbsp;&lt;SPAN&gt;etsysConfigMgmtChangeTable MIB vs a script.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Otherwise please consider opening a support case to further investigate this issue.&lt;/P&gt;&lt;P&gt;If you can SSH to the appliance via WebShell and manually issue a SCP command to offload the config towards XIQ-SE using XIQ-SE's 'root' or 'netsight' credentials I see no reason why the scripts would fail.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jun 2023 12:33:05 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/device-archives-in-inventory-manager-fail-with-a-device-busy/m-p/96167#M9879</guid>
      <dc:creator>Robert_Haynes</dc:creator>
      <dc:date>2023-06-19T12:33:05Z</dc:date>
    </item>
  </channel>
</rss>

