<?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: Spurrious Ignite Errors in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/spurrious-ignite-errors/m-p/2685264#M518985</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I see all of your warning messages in all my successfully ignited systems. There are readly nothing to worry about.&lt;BR /&gt;&lt;BR /&gt;In order to disable DHCP, at the main menu, choose advance options first, instead of Install HPUX, then there is a option to disable DHCP. Or alternatively, you could add the line disable_dhcp=true in your INSTALLFS.&lt;BR /&gt;&lt;BR /&gt;/opt/ignite/bin/instl_adm -d &amp;gt; tmpfile&lt;BR /&gt;echo "disable_dhcp=true" &amp;gt;&amp;gt; tmpfile&lt;BR /&gt;/opt/ignite/bin/instl_adm -f tmpfile&lt;BR /&gt;&lt;BR /&gt;You might want to check what is the hardware at 0/0/0/4 and see whether you have a driver installed for it.&lt;BR /&gt;&lt;BR /&gt;cheers&lt;BR /&gt;Siewhoong</description>
    <pubDate>Wed, 20 Mar 2002 01:29:42 GMT</pubDate>
    <dc:creator>Hooi Siew Hoong_1</dc:creator>
    <dc:date>2002-03-20T01:29:42Z</dc:date>
    <item>
      <title>Spurrious Ignite Errors</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/spurrious-ignite-errors/m-p/2685261#M518982</link>
      <description>I have an Ignite/UX server configured with a golden for installations. It all works, it is just that I never get a green icon at the end :-(  &lt;BR /&gt;&lt;BR /&gt;I think that the errors can be ignored, but I would like to get things nice and neat and with a green icon at the end :-)&lt;BR /&gt;&lt;BR /&gt;I am using HPUX 11i with Ignite B.3.6 to install (And re-install) HPUX 11i clients on rp7400 servers. The errors I get during the installs are -  &lt;BR /&gt;&lt;BR /&gt;1.        * Could not get DHCP information.  No host specific network defaults &lt;BR /&gt;         will be supplied.  (dhcpclient returned: 5)&lt;BR /&gt;ERROR:   Hostname and/or IP address was not set with instl_adm(1M), and not &lt;BR /&gt;         obtainable via DHCP.&lt;BR /&gt;ERROR:   Failed to Start networking.&lt;BR /&gt;         Failed to startup networking, user interaction required&lt;BR /&gt;&lt;BR /&gt;Now, all my clients are known to the Ignite server and the networking details are all permanent so how do I get around this without setting up a DHCP server ?&lt;BR /&gt;&lt;BR /&gt;2. WARNING: The instance number request for 0/0/4/0 cannot be assigned due to lack&lt;BR /&gt;         of driver name information.  You may need to update your config files &lt;BR /&gt;         by using the latest save_config command - or by specifying the driver &lt;BR /&gt;         name on the hw_instance_num keyword (see instl_adm(4)).&lt;BR /&gt;&lt;BR /&gt;I have tried redoing the save_config but with no effect .... and I don't really get where or what I do with hw_instance_num ?&lt;BR /&gt;&lt;BR /&gt;3. WARNING: No such device, tunable, or cdio pbc.&lt;BR /&gt; Ignoring the following line.&lt;BR /&gt; pbc&lt;BR /&gt;&lt;BR /&gt;Now I have been told that this is a 'non-issue' but I don't have pbc in the kernel on the 'donor' system so why do I get it when installing from the golden image ?&lt;BR /&gt;&lt;BR /&gt;Any help gratefully received, &lt;BR /&gt;&lt;BR /&gt;Cheers&lt;BR /&gt;&lt;BR /&gt;Niall&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 18 Mar 2002 15:45:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/spurrious-ignite-errors/m-p/2685261#M518982</guid>
      <dc:creator>Niall K Watts</dc:creator>
      <dc:date>2002-03-18T15:45:08Z</dc:date>
    </item>
    <item>
      <title>Re: Spurrious Ignite Errors</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/spurrious-ignite-errors/m-p/2685262#M518983</link>
      <description>&lt;BR /&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;I've used golden images quite a lot, mainly for installing 11.0 and 11i, on L/N-Class type machines.&lt;BR /&gt;&lt;BR /&gt;I have had several problems but not the one you are experiencing. If I have a system I'm going to Ignite, then I boot it off the Ignite Server ^C when it starts looking for DHCP.  Then I setup system parameters like hostname and the networking details - I set this as permanent.  I then install from the Ignite GUI and it picks up these previous settings.  I then have no problems getting a successful 'green' install.&lt;BR /&gt;&lt;BR /&gt;Dunno whether this will be any help - but I can't see why you're getting the problem you are.&lt;BR /&gt;&lt;BR /&gt;Rgds, Paul</description>
      <pubDate>Tue, 19 Mar 2002 09:22:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/spurrious-ignite-errors/m-p/2685262#M518983</guid>
      <dc:creator>Paul McCleary</dc:creator>
      <dc:date>2002-03-19T09:22:14Z</dc:date>
    </item>
    <item>
      <title>Re: Spurrious Ignite Errors</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/spurrious-ignite-errors/m-p/2685263#M518984</link>
      <description>The instance number comes from ioscan.&lt;BR /&gt;&lt;BR /&gt;ioscan -fnkClan&lt;BR /&gt;&lt;BR /&gt;for example:&lt;BR /&gt;Class     I  H/W Path     Driver   S/W State   H/W Type     Description&lt;BR /&gt;========================================================================&lt;BR /&gt;lan       0  0/0/0/0      btlan3   CLAIMED     INTERFACE    HP PCI 10/100Base-TX&lt;BR /&gt; Core&lt;BR /&gt;                         /dev/diag/lan0  /dev/ether0&lt;BR /&gt;lan       1  0/2/0/0/4/0  btlan    CLAIMED     INTERFACE    HP A5506B PCI 10/100&lt;BR /&gt;Base-TX 4 port&lt;BR /&gt;                         /dev/diag/lan1  /dev/ether1     /dev/lan1&lt;BR /&gt;lan       2  0/2/0/0/5/0  btlan    CLAIMED     INTERFACE    HP A5506B PCI 10/100&lt;BR /&gt;Base-TX 4 port&lt;BR /&gt;                         /dev/diag/lan2  /dev/ether2     /dev/lan2&lt;BR /&gt;lan       3  0/2/0/0/6/0  btlan    CLAIMED     INTERFACE    HP A5506B PCI 10/100&lt;BR /&gt;Base-TX 4 port&lt;BR /&gt;                         /dev/diag/lan3  /dev/ether3     /dev/lan3&lt;BR /&gt;lan       4  0/2/0/0/7/0  btlan    CLAIMED     INTERFACE    HP A5506B PCI 10/100&lt;BR /&gt;Base-TX 4 port&lt;BR /&gt;                         /dev/diag/lan4  /dev/ether4     /dev/lan4&lt;BR /&gt;&lt;BR /&gt;Instances 0, 1, 2, 3, 4&lt;BR /&gt;&lt;BR /&gt;the instance number relates to the device file: lan0...&lt;BR /&gt;ifconfig lan0 etc...&lt;BR /&gt;&lt;BR /&gt;The hardware path corresponds to the physical location of the io interface.&lt;BR /&gt;&lt;BR /&gt;Hope that helps some, never saw this error, but assume that your /etc/rc.config.d/netconf or lan settings are incorrect because hardware is not identical on backed up and restored system, and that you have more than one lan i/f on your system.&lt;BR /&gt;&lt;BR /&gt;Later,&lt;BR /&gt;Bill</description>
      <pubDate>Tue, 19 Mar 2002 10:43:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/spurrious-ignite-errors/m-p/2685263#M518984</guid>
      <dc:creator>Bill McNAMARA_1</dc:creator>
      <dc:date>2002-03-19T10:43:41Z</dc:date>
    </item>
    <item>
      <title>Re: Spurrious Ignite Errors</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/spurrious-ignite-errors/m-p/2685264#M518985</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I see all of your warning messages in all my successfully ignited systems. There are readly nothing to worry about.&lt;BR /&gt;&lt;BR /&gt;In order to disable DHCP, at the main menu, choose advance options first, instead of Install HPUX, then there is a option to disable DHCP. Or alternatively, you could add the line disable_dhcp=true in your INSTALLFS.&lt;BR /&gt;&lt;BR /&gt;/opt/ignite/bin/instl_adm -d &amp;gt; tmpfile&lt;BR /&gt;echo "disable_dhcp=true" &amp;gt;&amp;gt; tmpfile&lt;BR /&gt;/opt/ignite/bin/instl_adm -f tmpfile&lt;BR /&gt;&lt;BR /&gt;You might want to check what is the hardware at 0/0/0/4 and see whether you have a driver installed for it.&lt;BR /&gt;&lt;BR /&gt;cheers&lt;BR /&gt;Siewhoong</description>
      <pubDate>Wed, 20 Mar 2002 01:29:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/spurrious-ignite-errors/m-p/2685264#M518985</guid>
      <dc:creator>Hooi Siew Hoong_1</dc:creator>
      <dc:date>2002-03-20T01:29:42Z</dc:date>
    </item>
    <item>
      <title>Re: Spurrious Ignite Errors</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/spurrious-ignite-errors/m-p/2685265#M518986</link>
      <description>Apologies for not posting this sooner, I've been somewhat sidetracked, anyway here's the solutions .....&lt;BR /&gt;&lt;BR /&gt;1. As detailed by Siewhoong I needed to turn off DHCP (Thanks for your help Seiwhoong) and the ignite clients booted quite happily picking up there ip addresses. &lt;BR /&gt;&lt;BR /&gt;2. This took my ages to sort but now I understand it :-)  The problem was with a device at 0/0/4/0 which infact was the console, UPS &amp;amp; remote ports on the coreIO. The fix was to add the required kernel driver next to the h/w path in the save_config output such as - hw_instance_num += 0/0/4/0 "tty" "func0" 1 - The messages about h/w instances were somewhat misleading.&lt;BR /&gt;&lt;BR /&gt;3. I never got a fix to this as such but since resolving the other problems this one didn't cause the icon to change from green. From what I have been lead to believe "pbc" was a 'fix' HP used to differentiate between 32bit and 64bit versions of HP-UX that is no longer required ....  &lt;BR /&gt;&lt;BR /&gt;I hope someone finds this info of use, laters Niall&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 01 May 2002 12:10:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/spurrious-ignite-errors/m-p/2685265#M518986</guid>
      <dc:creator>Niall K Watts</dc:creator>
      <dc:date>2002-05-01T12:10:09Z</dc:date>
    </item>
  </channel>
</rss>

