<?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: Configure LAN interfaces ...... [FAIL] in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/configure-lan-interfaces-fail/m-p/4643889#M379663</link>
    <description>I suppose lan card itself id not coming up properly.&lt;BR /&gt;Can you check with &lt;BR /&gt;ioscan -fnC lan&lt;BR /&gt;&lt;BR /&gt;BR,&lt;BR /&gt;Kapil+</description>
    <pubDate>Tue, 08 Jun 2010 02:11:07 GMT</pubDate>
    <dc:creator>Kapil Jha</dc:creator>
    <dc:date>2010-06-08T02:11:07Z</dc:date>
    <item>
      <title>Configure LAN interfaces ...... [FAIL]</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/configure-lan-interfaces-fail/m-p/4643888#M379662</link>
      <description>&lt;!--!*#--&gt;I am a computer hobbyist and have some experience running DEC unix many years ago. I bought this old workstation b/c I wanted to stay up on unix, it is running the latest os, and it was only $250 with a 22" monitor. So it's home next to my G4, Ubuntu, Multia and NeXT machines.&lt;BR /&gt;&lt;BR /&gt;It is running HP-UX B.11.00 on an HP Model 9000/712/60.&lt;BR /&gt;&lt;BR /&gt;The footnote to this error says:&lt;BR /&gt;&lt;BR /&gt;[quote]&lt;BR /&gt;Failed to enter route entry because its interface is not yet initialized."&lt;BR /&gt;[/quote]&lt;BR /&gt;&lt;BR /&gt;And it continues:&lt;BR /&gt;&lt;BR /&gt;[quote]&lt;BR /&gt;May need to add this route entry with a route command after the interface is up:&lt;BR /&gt;add net default: gateway ....1: Network is unreachable&lt;BR /&gt;"/sbin/rc2.d/S340net start" FAILED&lt;BR /&gt;[/unquote]&lt;BR /&gt;&lt;BR /&gt;So...&lt;BR /&gt;&lt;BR /&gt;1) how do I initialize the interface?&lt;BR /&gt;&lt;BR /&gt;2) I tried 'route add default &lt;IP&gt; 1' but the result was "Network is unreachable."&lt;BR /&gt;&lt;BR /&gt;BTW, the text "HP-UX 11.x" does explain the network commands well, but it, and the internet, do not explain how to initialize the nic.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance for any help you may give me.&lt;/IP&gt;</description>
      <pubDate>Tue, 08 Jun 2010 01:24:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/configure-lan-interfaces-fail/m-p/4643888#M379662</guid>
      <dc:creator>joe comunale</dc:creator>
      <dc:date>2010-06-08T01:24:24Z</dc:date>
    </item>
    <item>
      <title>Re: Configure LAN interfaces ...... [FAIL]</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/configure-lan-interfaces-fail/m-p/4643889#M379663</link>
      <description>I suppose lan card itself id not coming up properly.&lt;BR /&gt;Can you check with &lt;BR /&gt;ioscan -fnC lan&lt;BR /&gt;&lt;BR /&gt;BR,&lt;BR /&gt;Kapil+</description>
      <pubDate>Tue, 08 Jun 2010 02:11:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/configure-lan-interfaces-fail/m-p/4643889#M379663</guid>
      <dc:creator>Kapil Jha</dc:creator>
      <dc:date>2010-06-08T02:11:07Z</dc:date>
    </item>
    <item>
      <title>Re: Configure LAN interfaces ...... [FAIL]</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/configure-lan-interfaces-fail/m-p/4643890#M379664</link>
      <description>There are many reasons for the NIC to not start. The first is to see if it exists:&lt;BR /&gt; &lt;BR /&gt;ioscan -knfC lan&lt;BR /&gt;lanscan&lt;BR /&gt;netstat -in&lt;BR /&gt;lanadmin -g 0&lt;BR /&gt; &lt;BR /&gt;The important item is whether the LAN card shows S/W state = CLAIMED and not UNKNOWN or NO_HW. If CLAIMED, then you can use sam to configure the LAN card. Another way is to run:&lt;BR /&gt; &lt;BR /&gt;/etc/set_parms initial&lt;BR /&gt; &lt;BR /&gt;Manually, it is done with the /etc/rc.config.d/netconf file but there are several related files such as /etc/hosts, /etc/nsswitch.conf, /etc/resolv.conf. But sam or set_parms is much simpler than reading very lengthy manuals.</description>
      <pubDate>Tue, 08 Jun 2010 02:20:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/configure-lan-interfaces-fail/m-p/4643890#M379664</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2010-06-08T02:20:53Z</dc:date>
    </item>
    <item>
      <title>Re: Configure LAN interfaces ...... [FAIL]</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/configure-lan-interfaces-fail/m-p/4643891#M379665</link>
      <description>&lt;!--!*#--&gt;Here is the result of ioscan and a few other network commands: (NOTE: "&lt;IP&gt;" is the first three numbers of the actual IP, and &lt;NAME&gt; is the hostname for the machine.)&lt;BR /&gt;&lt;BR /&gt;= ioscan =&lt;BR /&gt;Class = 0&lt;BR /&gt;I = 0&lt;BR /&gt;H/W Path = 2/0/2&lt;BR /&gt;Driver = lan2&lt;BR /&gt;S/W State = CLAIMED&lt;BR /&gt;H/W Type = INTERFACE&lt;BR /&gt;Description = Built-in Ether&lt;BR /&gt;&lt;BR /&gt;= lanscan =&lt;BR /&gt;(has the same info above and PPA = snap0)&lt;BR /&gt;&lt;BR /&gt;= ifconfig lan0 =&lt;BR /&gt;inet &lt;IP&gt;.104 netmask ffffff00 broadcast &lt;IP&gt;.255&lt;BR /&gt;&lt;BR /&gt;= netstat -r =&lt;BR /&gt;localhost localhost UH 0  23 lo0  4136&lt;BR /&gt;&lt;NAME&gt;    &lt;NAME&gt;    UH 0 128 lan0 4136&lt;BR /&gt;&lt;IP&gt;.0    &lt;NAME&gt;    U  2   0 lan0 1500&lt;BR /&gt;127.0.0.0 localhost U  0   0 lo0  4136&lt;BR /&gt;&lt;BR /&gt;=========================================&lt;/NAME&gt;&lt;/IP&gt;&lt;/NAME&gt;&lt;/NAME&gt;&lt;/IP&gt;&lt;/IP&gt;&lt;/NAME&gt;&lt;/IP&gt;</description>
      <pubDate>Tue, 08 Jun 2010 02:45:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/configure-lan-interfaces-fail/m-p/4643891#M379665</guid>
      <dc:creator>joe comunale</dc:creator>
      <dc:date>2010-06-08T02:45:52Z</dc:date>
    </item>
    <item>
      <title>Re: Configure LAN interfaces ...... [FAIL]</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/configure-lan-interfaces-fail/m-p/4643892#M379666</link>
      <description>Sorry Bill, there is no option "-g" for the lanadmin command... did you mena "-b"?&lt;BR /&gt;&lt;BR /&gt;I am at the end of running set_parms and am stuck on the NIS domain name as well as its server name (or IP).&lt;BR /&gt;&lt;BR /&gt;How do I find them out?&lt;BR /&gt;&lt;BR /&gt;Thanks for your help.</description>
      <pubDate>Tue, 08 Jun 2010 03:30:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/configure-lan-interfaces-fail/m-p/4643892#M379666</guid>
      <dc:creator>joe comunale</dc:creator>
      <dc:date>2010-06-08T03:30:18Z</dc:date>
    </item>
    <item>
      <title>Re: Configure LAN interfaces ...... [FAIL]</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/configure-lan-interfaces-fail/m-p/4643893#M379667</link>
      <description>I didn't know what to give as an answer to the NIS Domain Name or NIS Server Name, so I did some research using google and I read that the NIS Domain name is decided by me, and the (I think) Server Name can be the same. So I chose something, set them both to that name, and rebooted.&lt;BR /&gt;&lt;BR /&gt;I can now ping google.com, bfgtech.com (they make the PhysX card for my Win XP machine), but not microsoft.com. So I think things are working... of a sort. B/c I have a new problem. While both my hostname and domainname are different, on boot up I get message about how the os is going to use the "short name" ...&lt;BR /&gt;&lt;BR /&gt;I am going to leave it alone for now and play with what I got. I want to install gcc, compile the BOINC source code and run their client on this machine.&lt;BR /&gt;&lt;BR /&gt;If want any more information reply here as I will leave this thread open.&lt;BR /&gt;&lt;BR /&gt;Thanks to you both for your help.&lt;BR /&gt;&lt;BR /&gt;-joe</description>
      <pubDate>Tue, 08 Jun 2010 04:03:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/configure-lan-interfaces-fail/m-p/4643893#M379667</guid>
      <dc:creator>joe comunale</dc:creator>
      <dc:date>2010-06-08T04:03:20Z</dc:date>
    </item>
    <item>
      <title>Re: Configure LAN interfaces ...... [FAIL]</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/configure-lan-interfaces-fail/m-p/4643894#M379668</link>
      <description>&amp;gt; Sorry Bill, there is no option "-g" for the lanadmin command...&lt;BR /&gt; &lt;BR /&gt;For 11.00, lanadmin does have a -g option. It was added with patch PHNE_22331, but the current cumulative patch is PHNE_32643. Sounds like your system is in need of major patching. Go to this location to get the last patch bundle (Mar 2004) and download the HWE and QPK bundles.&lt;BR /&gt;  &lt;BR /&gt;&amp;gt; m stuck on the NIS domain name&lt;BR /&gt; &lt;BR /&gt;If you don't know about NIS, then you are definitely not using it. This was called Yellow Pages in the old days and was a way to centralize login IDs and passwords. You can disable NIS.&lt;BR /&gt; &lt;BR /&gt;&amp;gt; I can now ping google.com...but not microsoft.com&lt;BR /&gt; &lt;BR /&gt;Absolutely normal -- nobody can ping microsoft.com because ping is blocked due to network security. ping is a primitive method to verify networking and most large companies have a policy to block ping from routers to avoid discovery.&lt;BR /&gt; &lt;BR /&gt;&amp;gt; While both my hostname and domainname are different...&lt;BR /&gt; &lt;BR /&gt;I am assuming you are referring to the hostname command and the domain you set in /etc/resolv.conf. The OS doesn't "use" a hostname -- it translates the name to an IP address using the resolver. The order of name resolution is defoined by the file /etc/nsswitch.conf. Setup yours like this:&lt;BR /&gt; &lt;BR /&gt;passwd:       files&lt;BR /&gt;group:        files&lt;BR /&gt;hosts:        files [NOTFOUND=continue UNAVAIL=continue] dns&lt;BR /&gt;ipnodes:      files [NOTFOUND=continue] dns&lt;BR /&gt;services:     files&lt;BR /&gt;networks:     files&lt;BR /&gt;protocols:    files&lt;BR /&gt;rpc:          files&lt;BR /&gt;publickey:    files&lt;BR /&gt;netgroup:     files&lt;BR /&gt;automount:    files&lt;BR /&gt;aliases:      files&lt;BR /&gt; &lt;BR /&gt;Now you can add entries top /etc/hosts and they will be discovered before consulting with your DNS provider. Note that your host can have several network names. These can be listed in /etc/hosts.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 08 Jun 2010 12:23:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/configure-lan-interfaces-fail/m-p/4643894#M379668</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2010-06-08T12:23:40Z</dc:date>
    </item>
    <item>
      <title>Re: Configure LAN interfaces ...... [FAIL]</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/configure-lan-interfaces-fail/m-p/4643895#M379669</link>
      <description>&lt;!--!*#--&gt;&amp;gt;&amp;gt; For 11.00, lanadmin does have a -g option.&lt;BR /&gt;&amp;gt;&amp;gt; It was added with patch PHNE_22331, but&lt;BR /&gt;&amp;gt;&amp;gt; the current cumulative patch is&lt;BR /&gt;&amp;gt;&amp;gt; PHNE_32643. Sounds like your system is&lt;BR /&gt;&amp;gt;&amp;gt; in need of major patching. Go to this&lt;BR /&gt;&amp;gt;&amp;gt; location to get the last patch bundle&lt;BR /&gt;&amp;gt;&amp;gt; (Mar 2004) and download the HWE and QPK&lt;BR /&gt;&amp;gt;&amp;gt; bundles.&lt;BR /&gt;&lt;BR /&gt;Well, now that it's working I will definitely do that. So that's another question - what is the ftp for this site?? &lt;A href="ftp://hp.com??" target="_blank"&gt;ftp://hp.com??&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&amp;gt; I am stuck on the NIS domain name&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt; If you don't know about NIS, then you are&lt;BR /&gt;&amp;gt;&amp;gt; definitely not using it. This was called&lt;BR /&gt;&amp;gt;&amp;gt; Yellow Pages in the old days and was a&lt;BR /&gt;&amp;gt;&amp;gt; way to centralize login IDs and&lt;BR /&gt;&amp;gt;&amp;gt; passwords. You can disable NIS.&lt;BR /&gt;&lt;BR /&gt;I managed to mess this up last time I played with the machine. In the nsswitch file some of the entries had "nis".&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt; Absolutely normal -- nobody can ping&lt;BR /&gt;&amp;gt;&amp;gt; microsoft.com because ping is blocked&lt;BR /&gt;&amp;gt;&amp;gt; due to network security. ping is a&lt;BR /&gt;&amp;gt;&amp;gt; primitive method to verify networking&lt;BR /&gt;&amp;gt;&amp;gt; and most large companies have a policy&lt;BR /&gt;&amp;gt;&amp;gt; to block ping from routers to avoid&lt;BR /&gt;&amp;gt;&amp;gt; discovery.&lt;BR /&gt;&lt;BR /&gt;Yeah, I can imagine hackers would probably bombard MS with as many pings as possible.&lt;BR /&gt;&lt;BR /&gt;&amp;gt; While both my hostname and domainname are different...&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt; I am assuming you are referring to the&lt;BR /&gt;&amp;gt;&amp;gt; hostname command and the domain you set&lt;BR /&gt;&amp;gt;&amp;gt; in /etc/resolv.conf. The OS doesn't "use"&lt;BR /&gt;&amp;gt;&amp;gt; a hostname -- it translates the name to&lt;BR /&gt;&amp;gt;&amp;gt; an IP address using the resolver. The&lt;BR /&gt;&amp;gt;&amp;gt; order of name resolution is defoined by&lt;BR /&gt;&amp;gt;&amp;gt; the file /etc/nsswitch.conf. Setup yours&lt;BR /&gt;&amp;gt;&amp;gt; like this:&lt;BR /&gt;&amp;gt;&amp;gt; &lt;BR /&gt;&amp;gt;&amp;gt; passwd: files&lt;BR /&gt;&amp;gt;&amp;gt; group: files&lt;BR /&gt;&amp;gt;&amp;gt; hosts: files [NOTFOUND=continue UNAVAIL=continue] dns&lt;BR /&gt;&amp;gt;&amp;gt; ipnodes: files [NOTFOUND=continue] dns&lt;BR /&gt;&amp;gt;&amp;gt; services: files&lt;BR /&gt;&amp;gt;&amp;gt; networks: files&lt;BR /&gt;&amp;gt;&amp;gt; protocols: files&lt;BR /&gt;&amp;gt;&amp;gt; rpc: files&lt;BR /&gt;&amp;gt;&amp;gt; publickey: files&lt;BR /&gt;&amp;gt;&amp;gt; netgroup: files&lt;BR /&gt;&amp;gt;&amp;gt; automount: files&lt;BR /&gt;&amp;gt;&amp;gt; aliases: files&lt;BR /&gt;&lt;BR /&gt;As I mentioned above, I removed the 'nis' entries, but also added the ipnodes line. I am still able to ping outside.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt; Now you can add entries top /etc/hosts&lt;BR /&gt;&amp;gt;&amp;gt; and they will be discovered before&lt;BR /&gt;&amp;gt;&amp;gt; consulting with your DNS provider.&lt;BR /&gt;&amp;gt;&amp;gt; Note that your host can have several&lt;BR /&gt;&amp;gt;&amp;gt; network names. These can be listed in&lt;BR /&gt;&amp;gt;&amp;gt; /etc/hosts.&lt;BR /&gt;&lt;BR /&gt;Currently I have 5 working machines. I would like for them to see each other. I have names for them:&lt;BR /&gt;1) sweet (WinXP),&lt;BR /&gt;2) macBaby (G4),&lt;BR /&gt;3) dog (Ubuntu PC ...needs a cpu fan :( ),&lt;BR /&gt;4) hpux1 (HP-UX), and&lt;BR /&gt;5) a loaner laptop from the school where I teach physics as an adjunct.&lt;BR /&gt;&lt;BR /&gt;So if I know the IP for each machine, then should I edit /etc/hosts this way?&lt;BR /&gt;&lt;BR /&gt;&lt;IP&gt;.101    sweet&lt;BR /&gt;&lt;IP&gt;.102    macBaby&lt;BR /&gt;&lt;IP&gt;.103    dog&lt;BR /&gt;&lt;IP&gt;.104    hpux1&lt;BR /&gt;&lt;IP&gt;.105    "laptop"&lt;BR /&gt;&lt;BR /&gt;BTW, thanks! If I ever bump into you in a bar, just TRY and pay for your own drinks... :)&lt;/IP&gt;&lt;/IP&gt;&lt;/IP&gt;&lt;/IP&gt;&lt;/IP&gt;</description>
      <pubDate>Tue, 08 Jun 2010 13:27:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/configure-lan-interfaces-fail/m-p/4643895#M379669</guid>
      <dc:creator>joe comunale</dc:creator>
      <dc:date>2010-06-08T13:27:33Z</dc:date>
    </item>
  </channel>
</rss>

