<?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: Prime Infrastructure 3.2.0 Problem in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/prime-infrastructure-3-2-0-problem/m-p/4570553#M239615</link>
    <description>&lt;P&gt;I wonder if this symptom is a bug that can be fixed with an upgrade.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your help.&lt;/P&gt;</description>
    <pubDate>Tue, 15 Mar 2022 04:16:34 GMT</pubDate>
    <dc:creator>kanghoon</dc:creator>
    <dc:date>2022-03-15T04:16:34Z</dc:date>
    <item>
      <title>Prime Infrastructure 3.2.0 Problem</title>
      <link>https://community.cisco.com/t5/wireless/prime-infrastructure-3-2-0-problem/m-p/4569650#M239557</link>
      <description>&lt;P&gt;After Prime Infrastructure reboot at Feb/28 , all functions are fine, but the update function with increasing or decreasing "Associated Wireless Count" quantity does not work.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="KakaoTalk_20220302_151310276_01.jpg" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/146031iB557B714FC9F641D/image-size/large?v=v2&amp;amp;px=999" role="button" title="KakaoTalk_20220302_151310276_01.jpg" alt="KakaoTalk_20220302_151310276_01.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are currently unable to proceed with the TAC, so we tried to find a related bug, but could not find it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can anyone help with this phenomenon?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Prime Infrastructure Model : PI-UCS-APL-K9&lt;BR /&gt;Build Version : 3.2.0.0.258&lt;/P&gt;</description>
      <pubDate>Mon, 14 Mar 2022 01:11:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/prime-infrastructure-3-2-0-problem/m-p/4569650#M239557</guid>
      <dc:creator>kanghoon</dc:creator>
      <dc:date>2022-03-14T01:11:52Z</dc:date>
    </item>
    <item>
      <title>Re: Prime Infrastructure 3.2.0 Problem</title>
      <link>https://community.cisco.com/t5/wireless/prime-infrastructure-3-2-0-problem/m-p/4569696#M239561</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1215741"&gt;@kanghoon&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P&gt;&lt;SPAN&gt;We are currently unable to proceed with the TAC&lt;/SPAN&gt;&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Because PI 3.2 has already past end-of-support date.&lt;/P&gt;</description>
      <pubDate>Mon, 14 Mar 2022 03:06:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/prime-infrastructure-3-2-0-problem/m-p/4569696#M239561</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2022-03-14T03:06:29Z</dc:date>
    </item>
    <item>
      <title>Re: Prime Infrastructure 3.2.0 Problem</title>
      <link>https://community.cisco.com/t5/wireless/prime-infrastructure-3-2-0-problem/m-p/4569761#M239566</link>
      <description>&lt;P&gt;Its time to uplift your PI to 3.7 at lease, if you have the option to go 3.9 or 3.10&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 14 Mar 2022 07:52:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/prime-infrastructure-3-2-0-problem/m-p/4569761#M239566</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2022-03-14T07:52:11Z</dc:date>
    </item>
    <item>
      <title>Re: Prime Infrastructure 3.2.0 Problem</title>
      <link>https://community.cisco.com/t5/wireless/prime-infrastructure-3-2-0-problem/m-p/4570553#M239615</link>
      <description>&lt;P&gt;I wonder if this symptom is a bug that can be fixed with an upgrade.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your help.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Mar 2022 04:16:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/prime-infrastructure-3-2-0-problem/m-p/4570553#M239615</guid>
      <dc:creator>kanghoon</dc:creator>
      <dc:date>2022-03-15T04:16:34Z</dc:date>
    </item>
    <item>
      <title>Re: Prime Infrastructure 3.2.0 Problem</title>
      <link>https://community.cisco.com/t5/wireless/prime-infrastructure-3-2-0-problem/m-p/4570855#M239634</link>
      <description>&lt;P&gt;May be, if you have concern raise an TAC case to clarify.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Mar 2022 13:26:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/prime-infrastructure-3-2-0-problem/m-p/4570855#M239634</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2022-03-15T13:26:57Z</dc:date>
    </item>
    <item>
      <title>Re: Prime Infrastructure 3.2.0 Problem</title>
      <link>https://community.cisco.com/t5/wireless/prime-infrastructure-3-2-0-problem/m-p/4570917#M239636</link>
      <description>&lt;P&gt;Prime is tricky especially if the database gets corrupted in some way or form. &amp;nbsp;Why not try to spin up a virtual machine with a later version of Prime Infrastructure? &amp;nbsp;This way you can test and determine what your nexts steps should be. We have a PI 3.2 VM with no issues but I also have a PI 3.9 and 3.10 running in parallel. &amp;nbsp;I don’t know if an upgrade will help or not, but you need to look at the hardware you have and what versions are supported on the hardware.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Mar 2022 14:43:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/prime-infrastructure-3-2-0-problem/m-p/4570917#M239636</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2022-03-15T14:43:42Z</dc:date>
    </item>
  </channel>
</rss>

