<?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: N Class Hardware path problem in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/n-class-hardware-path-problem/m-p/2805320#M82897</link>
    <description>so you interrupt the boot at the prompt... and do a search for bootable devices and find the tape drive to boot from... then when you start the boot process on the tape drive it fails with can not find vmunix?&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Thu, 12 Sep 2002 19:59:18 GMT</pubDate>
    <dc:creator>Ted Ellis_2</dc:creator>
    <dc:date>2002-09-12T19:59:18Z</dc:date>
    <item>
      <title>N Class Hardware path problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/n-class-hardware-path-problem/m-p/2805316#M82893</link>
      <description>hello!&lt;BR /&gt;&lt;BR /&gt;we are having a problem with our N Class servers... we do a migration in which we install a system exactly like they have at our customer site, then we simply switch disks... however, our N Class Server is not EXACTLY like our customers, and so when we do an ioscan on our customer's machine we get a path like: &lt;BR /&gt; 0/5/0/0/4/1.0 and by use we get:&lt;BR /&gt; 0/5/0/1.0&lt;BR /&gt;&lt;BR /&gt;when we try and and switch the disks, it doesn't work, even though they have the same scsi (c4t1d0)...&lt;BR /&gt;&lt;BR /&gt;so then we tried to restore using a make_recovery, but we got an error saying that it couldn't find the vmunix... this is strange, as we did the remapping at the beginning of the boot, and that worked fine... we've done many remapping restores and never had any problems...&lt;BR /&gt;&lt;BR /&gt;any ideas?&lt;BR /&gt;&lt;BR /&gt;thanks&lt;BR /&gt;&lt;BR /&gt;jerome</description>
      <pubDate>Thu, 12 Sep 2002 17:12:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/n-class-hardware-path-problem/m-p/2805316#M82893</guid>
      <dc:creator>Jerome Salyers</dc:creator>
      <dc:date>2002-09-12T17:12:54Z</dc:date>
    </item>
    <item>
      <title>Re: N Class Hardware path problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/n-class-hardware-path-problem/m-p/2805317#M82894</link>
      <description>so you are building the system on your machine and then taking the disks that are created (root volume) and trying to switch them out on the clients server?  Trying understand exactly what you are doing here... &lt;BR /&gt;&lt;BR /&gt;One thing you may want to try is simply using your machine to build the recovery tape.... you should be able to use that same tape on the client system.. without swapping disks... or am I missing something on what you are describing?</description>
      <pubDate>Thu, 12 Sep 2002 19:18:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/n-class-hardware-path-problem/m-p/2805317#M82894</guid>
      <dc:creator>Ted Ellis_2</dc:creator>
      <dc:date>2002-09-12T19:18:09Z</dc:date>
    </item>
    <item>
      <title>Re: N Class Hardware path problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/n-class-hardware-path-problem/m-p/2805318#M82895</link>
      <description>we are creating the entire system, root and applications, and simply putting the disks in different hardware... the paths SHOULD be correct, but are not see as such...&lt;BR /&gt;&lt;BR /&gt;we used a make_recovery made from the system we will be switching to, to try and do a reverse scenario, and the make recovery failed with the problem above... so we don't want to try the real scenaro, as it looks like it too will fail... is there some special thing i have to do to a make_recovery on an N Class server when the hardware paths are not the same?&lt;BR /&gt;&lt;BR /&gt;jerome</description>
      <pubDate>Thu, 12 Sep 2002 19:43:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/n-class-hardware-path-problem/m-p/2805318#M82895</guid>
      <dc:creator>Jerome Salyers</dc:creator>
      <dc:date>2002-09-12T19:43:40Z</dc:date>
    </item>
    <item>
      <title>Re: N Class Hardware path problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/n-class-hardware-path-problem/m-p/2805319#M82896</link>
      <description>The device Path should not get change if the architecture is same. Are you sure that you are not using rp7410 instead of Nclass? What about the other device paths? they are also changed?&lt;BR /&gt;&lt;BR /&gt;Sandip</description>
      <pubDate>Thu, 12 Sep 2002 19:56:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/n-class-hardware-path-problem/m-p/2805319#M82896</guid>
      <dc:creator>Sandip Ghosh</dc:creator>
      <dc:date>2002-09-12T19:56:35Z</dc:date>
    </item>
    <item>
      <title>Re: N Class Hardware path problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/n-class-hardware-path-problem/m-p/2805320#M82897</link>
      <description>so you interrupt the boot at the prompt... and do a search for bootable devices and find the tape drive to boot from... then when you start the boot process on the tape drive it fails with can not find vmunix?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 12 Sep 2002 19:59:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/n-class-hardware-path-problem/m-p/2805320#M82897</guid>
      <dc:creator>Ted Ellis_2</dc:creator>
      <dc:date>2002-09-12T19:59:18Z</dc:date>
    </item>
    <item>
      <title>Re: N Class Hardware path problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/n-class-hardware-path-problem/m-p/2805321#M82898</link>
      <description>I took a quick look at 2 N4000 servers we have and 1 rp7400 server and they report identical hardware paths for the root disks... so if these servers are of the same flavor, it would seem they should have the same hardware path.</description>
      <pubDate>Thu, 12 Sep 2002 20:12:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/n-class-hardware-path-problem/m-p/2805321#M82898</guid>
      <dc:creator>Ted Ellis_2</dc:creator>
      <dc:date>2002-09-12T20:12:27Z</dc:date>
    </item>
    <item>
      <title>Re: N Class Hardware path problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/n-class-hardware-path-problem/m-p/2805322#M82899</link>
      <description>Check the firmware levels.  The really old N-Class firmware did some strange things to hardware addresses.  It would have to be a really early production machine for that to happen though.   Almost certainly with 360Mhz processors in it.</description>
      <pubDate>Fri, 13 Sep 2002 02:59:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/n-class-hardware-path-problem/m-p/2805322#M82899</guid>
      <dc:creator>Angus Crome</dc:creator>
      <dc:date>2002-09-13T02:59:41Z</dc:date>
    </item>
    <item>
      <title>Re: N Class Hardware path problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/n-class-hardware-path-problem/m-p/2805323#M82900</link>
      <description>Hi Jerome,&lt;BR /&gt;Can you boot both servers, interrupt the boot at the PDC, enter the INformation menu and then execute the IO command. This should show the hardwarepaths ... and any differences between both servers.&lt;BR /&gt;&lt;BR /&gt;Hope it helps,&lt;BR /&gt;Tom</description>
      <pubDate>Fri, 13 Sep 2002 04:05:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/n-class-hardware-path-problem/m-p/2805323#M82900</guid>
      <dc:creator>Tom Geudens</dc:creator>
      <dc:date>2002-09-13T04:05:14Z</dc:date>
    </item>
  </channel>
</rss>

