[HPADM] Issue seeing Ignite server in search for bootable

From: Jeff Lightner (jlightner_at_water.com)
Date: 08/10/05

  • Next message: Stocker, Nick: "[HPADM] Problem with "Cur PV" not matching "Act PV"" 
    Date: Wed, 10 Aug 2005 16:21:07 -0400
To: <hpux-admin@dutchworks.nl>

    All,

     

    I'm attempting to use our Ignite/UX server to install an N class server
    via its core Ethernet card. On doing "sea lan install" from the
    firmware prompt it finds nothing. If I attempt to do the install
    anyway (since I know the IP of the boot server) it errors out relatively
    quickly (5-10 minutes). On the suggestion of a coworker I attempted to
    do the install specifying 0/0/0/0 which is the hardware path of the lan
    card (instead of just saying "lan") it takes it more than an hour but
    eventually it to errors out. (Yes I am appending the IP address to
    "lan" or HW path in the foregoing - just didn't list it there since it
    is the same.)

     

    The ignite server was last used to do installations in January. I've
    attempted stopping rbootd, bootpd and inetd and restarting. The restart
    messages in /var/adm/syslog/syslog.log show no issues. All the
    documentation I find on line just says I should be able to see this.
    I've tested tftp connection to the Ignite server (via its real IP) and
    that works. It does not work to the IPs we've assigned to Ignite itself
    and I'm not sure whether it should. (Similarly attempting to ping the
    IPs assigned to Ignite don't work either but they do to the physical
    host.)

     

    The hosts are in the same subnet.

     

    I've examined /etc/bootptab and /etc/dhcptab and see no issues. There
    is no /etc/dhcpdeny and I saw a complaint about that during the restart
    of the daemons but since I'm not denying anything it isn't clear whether
    I need an empty file or not.

     

    Can anyone suggest what I need to do to get this working?

    Is there a way short of attempting the search for bootable devices to
    verify whether the IPs assigned to Ignite are working? Should ping,
    tftp or telnet work to those IPs?

    Is it possible to Ignite by specifying the real IP of the Ignite server?

     

    TIA

     

    Jeffrey C. Lightner

    Unix Systems Administrator

    DS Waters of North America

    678-486-3516

      

    --
             ---> Please post QUESTIONS and SUMMARIES only!! <---
        To subscribe/unsubscribe to this list, contact majordomo@dutchworks.nl
       Name: hpux-admin@dutchworks.nl     Owner: owner-hpux-admin@dutchworks.nl
 
 Archives:  ftp.dutchworks.nl:/pub/digests/hpux-admin       (FTP, browse only)
            http://www.dutchworks.nl/htbin/hpsysadmin   (Web, browse & search)
  • Next message: Stocker, Nick: "[HPADM] Problem with "Cur PV" not matching "Act PV""

    Relevant Pages

    • Re: Network boot problems
      ... >> or does it need the hardware path of the LAN card? ... For that particular sort of boot, ... (However, if you boot from regular media, but choose to do the install from ... My ignite server is a J class workstation, and I've seen the "failed to ...
      (comp.sys.hp.hpux)
    • [HPADM] Ignite install issues
      ... I am attempting to install hpux 11.0 on a K460 from a newly installed ... I set up the Ignite server as described in the cookbook and attempted to ... I was logged into the ignite server from the client so when the client ... During the boot the following occurred: ...
      (HP-UX-Admin)
    • Network boot problems
      ... We are trying to do a network install ... from the pdc prompt using ... The Ignite server is on the same sub-net and lan0 works ... the machine is fully installed and will boot up normally - ...
      (comp.sys.hp.hpux)