<?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 Managing Support Packs in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/managing-support-packs/m-p/7023092#M62363</link>
    <description>&lt;P&gt;&lt;A title="bp003135.xml" href="https://vmslcsim01:2381/cgi-bin/vcrepository/cgi?legacyuri=/vcrepository/catalog&amp;amp;bundle=bp003135.xml" target="_blank"&gt;Service Pack for ProLiant Version 2018.06.0 (English (US),Chinese (Simplified),Japanese)&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I have a Service Pack for ProLiant Version 2018.06. It keeps reporting the same 9 componets as not in the catalog&lt;/P&gt;&lt;P&gt;Example:&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;hp-i40e-kmp-default-2.4.6.1_k4.4.21_69-4.sles12sp2.x86_64.rpm -&amp;nbsp;&lt;/SPAN&gt;&lt;FONT color="#aa0000"&gt;The referenced component is not in the catalog.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#aa0000"&gt;The compsig file is there, the component i in the repository directory and it is listed in the catalog.&amp;nbsp; There is no mnf file. Is there a way to force recreation of the MNF file.&amp;nbsp; I have tried removing etc...&amp;nbsp; &lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#aa0000"&gt;&amp;nbsp;I just started using SIM and have tried rebuilding the catalog removing the files from the catalog.&amp;nbsp; I don't need the components so I just&amp;nbsp; want to remove them from the catalog.&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#aa0000"&gt;&lt;BR /&gt;Also I see if I automatically download the files, I can exclude various types of patchs that are for OS's we do not use.&amp;nbsp; Is there a way to add just the files I want and exclude the others?&amp;nbsp;&amp;nbsp;&lt;BR /&gt;I am looking for documentation, on the net, but I am in a hurry and if it is simple It would speed up the process.&lt;/FONT&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 24 Oct 2018 15:22:54 GMT</pubDate>
    <dc:creator>echeadle2</dc:creator>
    <dc:date>2018-10-24T15:22:54Z</dc:date>
    <item>
      <title>Managing Support Packs</title>
      <link>https://community.hpe.com/t5/server-management-systems/managing-support-packs/m-p/7023092#M62363</link>
      <description>&lt;P&gt;&lt;A title="bp003135.xml" href="https://vmslcsim01:2381/cgi-bin/vcrepository/cgi?legacyuri=/vcrepository/catalog&amp;amp;bundle=bp003135.xml" target="_blank"&gt;Service Pack for ProLiant Version 2018.06.0 (English (US),Chinese (Simplified),Japanese)&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I have a Service Pack for ProLiant Version 2018.06. It keeps reporting the same 9 componets as not in the catalog&lt;/P&gt;&lt;P&gt;Example:&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;hp-i40e-kmp-default-2.4.6.1_k4.4.21_69-4.sles12sp2.x86_64.rpm -&amp;nbsp;&lt;/SPAN&gt;&lt;FONT color="#aa0000"&gt;The referenced component is not in the catalog.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#aa0000"&gt;The compsig file is there, the component i in the repository directory and it is listed in the catalog.&amp;nbsp; There is no mnf file. Is there a way to force recreation of the MNF file.&amp;nbsp; I have tried removing etc...&amp;nbsp; &lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#aa0000"&gt;&amp;nbsp;I just started using SIM and have tried rebuilding the catalog removing the files from the catalog.&amp;nbsp; I don't need the components so I just&amp;nbsp; want to remove them from the catalog.&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#aa0000"&gt;&lt;BR /&gt;Also I see if I automatically download the files, I can exclude various types of patchs that are for OS's we do not use.&amp;nbsp; Is there a way to add just the files I want and exclude the others?&amp;nbsp;&amp;nbsp;&lt;BR /&gt;I am looking for documentation, on the net, but I am in a hurry and if it is simple It would speed up the process.&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 24 Oct 2018 15:22:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/managing-support-packs/m-p/7023092#M62363</guid>
      <dc:creator>echeadle2</dc:creator>
      <dc:date>2018-10-24T15:22:54Z</dc:date>
    </item>
    <item>
      <title>Re: Managing Support Packs</title>
      <link>https://community.hpe.com/t5/server-management-systems/managing-support-packs/m-p/7023263#M62364</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;It seems that VCRM is used in the environment.&lt;/P&gt;&lt;P&gt;Please try rebuliding catalogue from VCRM first. VCRM can be accessed through the SMH.&lt;/P&gt;&lt;P&gt;If fails, clear the repository and try importing the support pack from VCRM either through SPP or copy the SPP components to the repository.&lt;/P&gt;&lt;P&gt;If it still fails, log a support case with HPE with valid contract on the ProLiant server and support team would help to resolve the issue.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Fri, 26 Oct 2018 03:05:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/managing-support-packs/m-p/7023263#M62364</guid>
      <dc:creator>KK</dc:creator>
      <dc:date>2018-10-26T03:05:36Z</dc:date>
    </item>
  </channel>
</rss>

