<?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: Network Boot in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/network-boot/m-p/5000983#M508979</link>
    <description>Issue confirmed... Thanks</description>
    <pubDate>Fri, 01 Sep 2006 12:34:40 GMT</pubDate>
    <dc:creator>placitasmd</dc:creator>
    <dc:date>2006-09-01T12:34:40Z</dc:date>
    <item>
      <title>Network Boot</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/network-boot/m-p/5000979#M508975</link>
      <description>I have an L3000 with my only active LAN port being a 1000Base SX card installed in slot 12. When I issue the "boot lan install" command to reload the server from my network ignite server it fails with a bunch of zeros. It never sees the ignite server as a potential boot device. Is this because i can only use the core LAN port to boot over the network? I issues a "search' from the main menu and the LAN never shows up as a potential boot path.</description>
      <pubDate>Fri, 01 Sep 2006 11:50:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/network-boot/m-p/5000979#M508975</guid>
      <dc:creator>placitasmd</dc:creator>
      <dc:date>2006-09-01T11:50:56Z</dc:date>
    </item>
    <item>
      <title>Re: Network Boot</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/network-boot/m-p/5000980#M508976</link>
      <description>&lt;BR /&gt;&lt;BR /&gt;You are correct - you need to use the core LAN card for the LAN boot</description>
      <pubDate>Fri, 01 Sep 2006 11:56:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/network-boot/m-p/5000980#M508976</guid>
      <dc:creator>DCE</dc:creator>
      <dc:date>2006-09-01T11:56:09Z</dc:date>
    </item>
    <item>
      <title>Re: Network Boot</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/network-boot/m-p/5000981#M508977</link>
      <description>Also ignite server should be on same subnet where client is available.&lt;BR /&gt;&lt;BR /&gt;change lan connection to Core Lan on client and you would see Ignite server images.</description>
      <pubDate>Fri, 01 Sep 2006 12:04:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/network-boot/m-p/5000981#M508977</guid>
      <dc:creator>IT_2007</dc:creator>
      <dc:date>2006-09-01T12:04:48Z</dc:date>
    </item>
    <item>
      <title>Re: Network Boot</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/network-boot/m-p/5000982#M508978</link>
      <description>Yes, this is one of those things that you plan for when doing network Ignites. HP had to choose the lowest common denominator or produce custom firmware to allow a box to boot off the network using a non built-in NIC. They chose the wiser and safer course. It's documented behavior so you shouldn't complain. You should dedicate a VLAN for Ignites because many of the built-in's on the older boxes are 10-Base-T only.&lt;BR /&gt;</description>
      <pubDate>Fri, 01 Sep 2006 12:07:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/network-boot/m-p/5000982#M508978</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2006-09-01T12:07:44Z</dc:date>
    </item>
    <item>
      <title>Re: Network Boot</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/network-boot/m-p/5000983#M508979</link>
      <description>Issue confirmed... Thanks</description>
      <pubDate>Fri, 01 Sep 2006 12:34:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/network-boot/m-p/5000983#M508979</guid>
      <dc:creator>placitasmd</dc:creator>
      <dc:date>2006-09-01T12:34:40Z</dc:date>
    </item>
  </channel>
</rss>

