<?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: Dynamic nPartitions in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/dynamic-npartitions/m-p/5101656#M444271</link>
    <description>What exactly are you wondering about it? (Because you aren't being clear here... Mr. Burnard already pretty much summed it up -- and the white paper page 4 goes into what it means (restrictions, etc.) to have a Base vs. Floating cell [so I also don't understand why you say the white paper "states nothing about it"]). Page 7 (minimum base vs. floating ratios) is important as well.</description>
    <pubDate>Sun, 06 Apr 2008 17:06:35 GMT</pubDate>
    <dc:creator>Don Morris_1</dc:creator>
    <dc:date>2008-04-06T17:06:35Z</dc:date>
    <item>
      <title>Dynamic nPartitions</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dynamic-npartitions/m-p/5101653#M444268</link>
      <description>Could someone please explain to me what does the "float" failure usage in the parcreate/parmodify command(s) do? Thank you. &lt;BR /&gt;example:&lt;BR /&gt;parcreate -p 0 -a 0:floating:y:float:100%&lt;BR /&gt;</description>
      <pubDate>Sun, 06 Apr 2008 13:16:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dynamic-npartitions/m-p/5101653#M444268</guid>
      <dc:creator>Sherif A. Louis</dc:creator>
      <dc:date>2008-04-06T13:16:56Z</dc:date>
    </item>
    <item>
      <title>Re: Dynamic nPartitions</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dynamic-npartitions/m-p/5101654#M444269</link>
      <description>This sets up a cell board to "floating", or able to be removed from one partition and added to another WITHOUT bring down the partitions.&lt;BR /&gt;Take a read of:&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/10907/dynamic_nPars_WP.pdf" target="_blank"&gt;http://docs.hp.com/en/10907/dynamic_nPars_WP.pdf&lt;/A&gt;&lt;BR /&gt;</description>
      <pubDate>Sun, 06 Apr 2008 13:57:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dynamic-npartitions/m-p/5101654#M444269</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2008-04-06T13:57:25Z</dc:date>
    </item>
    <item>
      <title>Re: Dynamic nPartitions</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dynamic-npartitions/m-p/5101655#M444270</link>
      <description>yes i know that. when i read the man page of the commands it stated only on failure usage option which is "ri" which means during POST if any failures occur to memory or CPU it should reboot and reactivating memory interleave. but the float option what does it exactly do? i read the white paper and it states nothing about it neither the HP-UX manpages!! how come?</description>
      <pubDate>Sun, 06 Apr 2008 16:11:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dynamic-npartitions/m-p/5101655#M444270</guid>
      <dc:creator>Sherif A. Louis</dc:creator>
      <dc:date>2008-04-06T16:11:33Z</dc:date>
    </item>
    <item>
      <title>Re: Dynamic nPartitions</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dynamic-npartitions/m-p/5101656#M444271</link>
      <description>What exactly are you wondering about it? (Because you aren't being clear here... Mr. Burnard already pretty much summed it up -- and the white paper page 4 goes into what it means (restrictions, etc.) to have a Base vs. Floating cell [so I also don't understand why you say the white paper "states nothing about it"]). Page 7 (minimum base vs. floating ratios) is important as well.</description>
      <pubDate>Sun, 06 Apr 2008 17:06:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dynamic-npartitions/m-p/5101656#M444271</guid>
      <dc:creator>Don Morris_1</dc:creator>
      <dc:date>2008-04-06T17:06:35Z</dc:date>
    </item>
    <item>
      <title>Re: Dynamic nPartitions</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dynamic-npartitions/m-p/5101657#M444272</link>
      <description>failure usage: float&lt;BR /&gt;&lt;BR /&gt;i understand the floating concept cell.&lt;BR /&gt;i'm talking about this specific option!!</description>
      <pubDate>Sun, 06 Apr 2008 17:23:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dynamic-npartitions/m-p/5101657#M444272</guid>
      <dc:creator>Sherif A. Louis</dc:creator>
      <dc:date>2008-04-06T17:23:28Z</dc:date>
    </item>
    <item>
      <title>Re: Dynamic nPartitions</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dynamic-npartitions/m-p/5101658#M444273</link>
      <description>Ah, now I see what you're asking.&lt;BR /&gt;&lt;BR /&gt;From parmodify(1m) [latest version, which I would have expected to have gone out with Dynamic nPartitions, but I don't find a patch which corresponds to it... so I'll check with some folks tomorrow and see what's going on here -- I may just not be seeing the delivery mechanism, mind you]:&lt;BR /&gt;&lt;BR /&gt;failure_usage field is used by system firmware when a partition is booted.  &lt;BR /&gt;If a CPU selftest failure or a DIMM de-allocation occurs during the         power-on self-test process then this flag is used by the system firmware to determine whether or not and how the cell should be integrated into the partition at boot time.  &lt;BR /&gt;&lt;BR /&gt;The valid failure_usage                          value for cells is:&lt;BR /&gt;&lt;BR /&gt;    ri          reactivate with memory interleave.&lt;BR /&gt;                                      Specifies to integrate the cell as it                                       would normally be integrated.  This is                                       the default for base cells.&lt;BR /&gt;                          &lt;BR /&gt;float       this is the default value for floating                                      cells.  If the user specifies ri for a                                      floating cell, the command outputs an                                      error and exits.                  &lt;BR /&gt;&lt;BR /&gt;deconf      deconfigure.&lt;BR /&gt;&lt;BR /&gt;ni          no interleave.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;So the short version is -- "float" just tells the firmware to not only add the cell to the parition "ni" on hardware error, but be sure to keep in Floating. (You can't be "ri" since Floating can't be interleaved, obviously...) "deconf" could be used to keep suspect Floating cells out of the parition for checking/replacement after which they could be OLA'd.</description>
      <pubDate>Sun, 06 Apr 2008 18:48:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dynamic-npartitions/m-p/5101658#M444273</guid>
      <dc:creator>Don Morris_1</dc:creator>
      <dc:date>2008-04-06T18:48:48Z</dc:date>
    </item>
    <item>
      <title>Re: Dynamic nPartitions</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dynamic-npartitions/m-p/5101659#M444274</link>
      <description>perfect, thanks :o)</description>
      <pubDate>Sun, 06 Apr 2008 20:33:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dynamic-npartitions/m-p/5101659#M444274</guid>
      <dc:creator>Sherif A. Louis</dc:creator>
      <dc:date>2008-04-06T20:33:49Z</dc:date>
    </item>
    <item>
      <title>Re: Dynamic nPartitions</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dynamic-npartitions/m-p/5101660#M444275</link>
      <description>give it a '10'</description>
      <pubDate>Sun, 06 Apr 2008 20:43:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dynamic-npartitions/m-p/5101660#M444275</guid>
      <dc:creator>Sherif A. Louis</dc:creator>
      <dc:date>2008-04-06T20:43:49Z</dc:date>
    </item>
  </channel>
</rss>

