<?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 Ignite client boot problems in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ignite-client-boot-problems/m-p/3746114#M256932</link>
    <description>Hi!&lt;BR /&gt;I'm trying to use Ignite-server for installing OS, like 11.23 or 11.11.&lt;BR /&gt;For regret Ignite use bootpd for booting&lt;BR /&gt;the Client mashine for installation and for&lt;BR /&gt;this reason the both mashines must be in &lt;BR /&gt;the same VLAN. But I have a systems in &lt;BR /&gt;different lans: 192.168.24.x; 192.168.1.x &lt;BR /&gt;and so on... So is there any experiance in "trunking", where the same port  of&lt;BR /&gt;switch for Ignite-server become part of&lt;BR /&gt;2-3 VLANs. &lt;BR /&gt;&lt;BR /&gt;How I could organize that?</description>
    <pubDate>Tue, 07 Mar 2006 09:45:48 GMT</pubDate>
    <dc:creator>Inesa Clinko</dc:creator>
    <dc:date>2006-03-07T09:45:48Z</dc:date>
    <item>
      <title>Ignite client boot problems</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ignite-client-boot-problems/m-p/3746114#M256932</link>
      <description>Hi!&lt;BR /&gt;I'm trying to use Ignite-server for installing OS, like 11.23 or 11.11.&lt;BR /&gt;For regret Ignite use bootpd for booting&lt;BR /&gt;the Client mashine for installation and for&lt;BR /&gt;this reason the both mashines must be in &lt;BR /&gt;the same VLAN. But I have a systems in &lt;BR /&gt;different lans: 192.168.24.x; 192.168.1.x &lt;BR /&gt;and so on... So is there any experiance in "trunking", where the same port  of&lt;BR /&gt;switch for Ignite-server become part of&lt;BR /&gt;2-3 VLANs. &lt;BR /&gt;&lt;BR /&gt;How I could organize that?</description>
      <pubDate>Tue, 07 Mar 2006 09:45:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ignite-client-boot-problems/m-p/3746114#M256932</guid>
      <dc:creator>Inesa Clinko</dc:creator>
      <dc:date>2006-03-07T09:45:48Z</dc:date>
    </item>
    <item>
      <title>Re: Ignite client boot problems</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ignite-client-boot-problems/m-p/3746115#M256933</link>
      <description>I know some Cisco switches will allow multiple VLANs to be assigned to a port. I'm sure this is a pretty common feature. However, just because you configure the switch to show the server on all the VLANs doesn't necessarily mean you'll be able to boot all of the clients from the server without a boot helper. They still need to be on the same IP subnet to do the bootp stuff. If they are on different IP subnets, requiring a router to communicate, then you still need the boot helper even if they are on the same VLAN.</description>
      <pubDate>Tue, 07 Mar 2006 09:58:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ignite-client-boot-problems/m-p/3746115#M256933</guid>
      <dc:creator>Jeff_Traigle</dc:creator>
      <dc:date>2006-03-07T09:58:27Z</dc:date>
    </item>
    <item>
      <title>Re: Ignite client boot problems</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ignite-client-boot-problems/m-p/3746116#M256934</link>
      <description>Shalom Inesa,&lt;BR /&gt;&lt;BR /&gt;Some vlan situations require a boot helper machine to get the needed traffic from client to server.&lt;BR /&gt;&lt;BR /&gt;Last I checked Ignite boots had to also be on the built in NIC, not any add in cards. When possible, I set up a cisco switch and private lan for boots to get around VLAN problems.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Tue, 07 Mar 2006 10:02:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ignite-client-boot-problems/m-p/3746116#M256934</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-03-07T10:02:17Z</dc:date>
    </item>
  </channel>
</rss>

