<?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: efi lanboot automation in Integrity Servers</title>
    <link>https://community.hpe.com/t5/integrity-servers/efi-lanboot-automation/m-p/4779069#M7526</link>
    <description>Hi Stephan,&lt;BR /&gt;I agree with, but exist a way to assign an ip address to EFI, the problem is that there is not a sshd to connect to. I send you this(&lt;A href="http://labs.hoffmanlabs.com/node/563):" target="_blank"&gt;http://labs.hoffmanlabs.com/node/563):&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;To enable networking at EFI on Integrity (and here assuming the OpenVMS I64 EFI directory structures and organization), first summon the EFI editor:&lt;BR /&gt;&lt;BR /&gt;fs0:\efi\vms\tools&amp;gt; edit startup_net.nshEnter the following into this file:&lt;BR /&gt;&lt;BR /&gt;load \efi\vms\tools\tcpipv4.efi&lt;BR /&gt;\efi\vms\tools\ifconfig lo0 inet 127.0.0.1&lt;BR /&gt;\efi\vms\tools\ifconfig sni0 inet &lt;IP_ADDRESS&gt; netmask &lt;SUBNET_MASK&gt; &lt;BR /&gt;\efi\vms\tools\route add default &lt;GATEWAY_ADDRESS&gt;You will need to insert an IP address, netmask and gateway appropriate for this host and your network.&lt;BR /&gt;&lt;BR /&gt;And yes, thereâ  s an FTP client down there.&lt;BR /&gt;&lt;BR /&gt;...there is only an ftp client ;-(&lt;BR /&gt;&lt;BR /&gt;Regards Raffaele&lt;BR /&gt;&lt;BR /&gt;&lt;/GATEWAY_ADDRESS&gt;&lt;/SUBNET_MASK&gt;&lt;/IP_ADDRESS&gt;</description>
    <pubDate>Tue, 19 Apr 2011 09:29:27 GMT</pubDate>
    <dc:creator>RafS</dc:creator>
    <dc:date>2011-04-19T09:29:27Z</dc:date>
    <item>
      <title>efi lanboot automation</title>
      <link>https://community.hpe.com/t5/integrity-servers/efi-lanboot-automation/m-p/4779067#M7524</link>
      <description>Hello,&lt;BR /&gt;I need to automate the hp-ux os's provisioning by operation orchestration.&lt;BR /&gt;Is it possible to use ssh to connect to EFI-shell, launch a script to invoke lanboot command to restore an Ignite UX image to a ia64 client with HP-UX?&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Raffaele</description>
      <pubDate>Tue, 19 Apr 2011 08:54:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/efi-lanboot-automation/m-p/4779067#M7524</guid>
      <dc:creator>RafS</dc:creator>
      <dc:date>2011-04-19T08:54:15Z</dc:date>
    </item>
    <item>
      <title>Re: efi lanboot automation</title>
      <link>https://community.hpe.com/t5/integrity-servers/efi-lanboot-automation/m-p/4779068#M7525</link>
      <description>Hi,&lt;BR /&gt;probably not as much as you want.&lt;BR /&gt;&lt;BR /&gt;You can connect to the console via ssh, but not directly to the EFI shell - the EFI shell has no network. So you need to find a solution to enter all the needed commands on the console.&lt;BR /&gt;&lt;BR /&gt;For the lanboot commands you can use dbprofile to automate the details of lanboot but the actually starting of 'lanboot select -dn &lt;DBPROFILE name=""&gt;' has to be done by hand.&lt;BR /&gt;&lt;BR /&gt;As far as i know there is no way to get the same behavior as f.e. windows silent install.&lt;BR /&gt;&lt;BR /&gt;hth&lt;BR /&gt;Stephan&lt;/DBPROFILE&gt;</description>
      <pubDate>Tue, 19 Apr 2011 09:07:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/efi-lanboot-automation/m-p/4779068#M7525</guid>
      <dc:creator>Stephan.</dc:creator>
      <dc:date>2011-04-19T09:07:41Z</dc:date>
    </item>
    <item>
      <title>Re: efi lanboot automation</title>
      <link>https://community.hpe.com/t5/integrity-servers/efi-lanboot-automation/m-p/4779069#M7526</link>
      <description>Hi Stephan,&lt;BR /&gt;I agree with, but exist a way to assign an ip address to EFI, the problem is that there is not a sshd to connect to. I send you this(&lt;A href="http://labs.hoffmanlabs.com/node/563):" target="_blank"&gt;http://labs.hoffmanlabs.com/node/563):&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;To enable networking at EFI on Integrity (and here assuming the OpenVMS I64 EFI directory structures and organization), first summon the EFI editor:&lt;BR /&gt;&lt;BR /&gt;fs0:\efi\vms\tools&amp;gt; edit startup_net.nshEnter the following into this file:&lt;BR /&gt;&lt;BR /&gt;load \efi\vms\tools\tcpipv4.efi&lt;BR /&gt;\efi\vms\tools\ifconfig lo0 inet 127.0.0.1&lt;BR /&gt;\efi\vms\tools\ifconfig sni0 inet &lt;IP_ADDRESS&gt; netmask &lt;SUBNET_MASK&gt; &lt;BR /&gt;\efi\vms\tools\route add default &lt;GATEWAY_ADDRESS&gt;You will need to insert an IP address, netmask and gateway appropriate for this host and your network.&lt;BR /&gt;&lt;BR /&gt;And yes, thereâ  s an FTP client down there.&lt;BR /&gt;&lt;BR /&gt;...there is only an ftp client ;-(&lt;BR /&gt;&lt;BR /&gt;Regards Raffaele&lt;BR /&gt;&lt;BR /&gt;&lt;/GATEWAY_ADDRESS&gt;&lt;/SUBNET_MASK&gt;&lt;/IP_ADDRESS&gt;</description>
      <pubDate>Tue, 19 Apr 2011 09:29:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/efi-lanboot-automation/m-p/4779069#M7526</guid>
      <dc:creator>RafS</dc:creator>
      <dc:date>2011-04-19T09:29:27Z</dc:date>
    </item>
    <item>
      <title>Re: efi lanboot automation</title>
      <link>https://community.hpe.com/t5/integrity-servers/efi-lanboot-automation/m-p/4779070#M7527</link>
      <description>Hi Raffaele,&lt;BR /&gt;to be honest you know already more then me (even if you link shows access denied)... i never digged so deep into the EFI due to the fact even if you get networking - who enter the commands for it or who/how do you start the EFI on power on?&lt;BR /&gt;&lt;BR /&gt;All of my customers just let an operator use the console for installing, start EFI, start lanboot with dbprofile and rest is done by custom Ignite scripts.&lt;BR /&gt;&lt;BR /&gt;Best,&lt;BR /&gt;Stephan</description>
      <pubDate>Tue, 19 Apr 2011 09:50:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/efi-lanboot-automation/m-p/4779070#M7527</guid>
      <dc:creator>Stephan.</dc:creator>
      <dc:date>2011-04-19T09:50:03Z</dc:date>
    </item>
    <item>
      <title>Re: efi lanboot automation</title>
      <link>https://community.hpe.com/t5/integrity-servers/efi-lanboot-automation/m-p/4779071#M7528</link>
      <description>You can start a LAN stack on EFI, but there are no daemons for listening, only the telnet and ftp clients.&lt;BR /&gt;&lt;BR /&gt;Normally you create a dbprofile for use with lanboot, you may even create a boot entry for such boot. Ignite provides a procedure for forcing a running host to reboot and start a network restore.&lt;BR /&gt;&lt;BR /&gt;I'm not sure what exactly you want to do.</description>
      <pubDate>Tue, 19 Apr 2011 10:18:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/efi-lanboot-automation/m-p/4779071#M7528</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2011-04-19T10:18:52Z</dc:date>
    </item>
    <item>
      <title>Re: efi lanboot automation</title>
      <link>https://community.hpe.com/t5/integrity-servers/efi-lanboot-automation/m-p/4779072#M7529</link>
      <description>I would think that telnet'ing/ssh'ing to the MP/iLO and connecting to the console via an "expect" script or the like would be the way one could then issue the lanboot command and go from there.  &lt;BR /&gt;&lt;BR /&gt;If the system to be lanbooted already has an HP-UX OS running upon it, perhaps there is a way to use the setboot command to set-up the next boot as being via the/a LAN interface.</description>
      <pubDate>Wed, 20 Apr 2011 16:01:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/efi-lanboot-automation/m-p/4779072#M7529</guid>
      <dc:creator>rick jones</dc:creator>
      <dc:date>2011-04-20T16:01:06Z</dc:date>
    </item>
  </channel>
</rss>

