<?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 error in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/network-error/m-p/4039673#M29346</link>
    <description>Yes in Static mode. &lt;BR /&gt;&lt;BR /&gt;Regardless of the physical connection the software side will be set up on service restart. You can try that by yanking your network cable, restarting networking &amp;amp; ping yourself (ip, not on localhost). &lt;BR /&gt;&lt;BR /&gt;However, using DHCP will probably cause the service to restart rather slowly (initial waiting on DHCP ACK) on eth0, the dhcpcd process will then be backgrounded and networking will come up further on eth1. &lt;BR /&gt;So eth0 will be stuck without IP until connectivity is restored. &lt;BR /&gt;&lt;BR /&gt;Solution for avoiding all this is the use of "bonding". &lt;BR /&gt;See more about bonding here &lt;A href="http://docs.hp.com/en/B9903-90050/ch05s05.html" target="_blank"&gt;http://docs.hp.com/en/B9903-90050/ch05s05.html&lt;/A&gt; and here &lt;A href="http://www.linuxhorizon.ro/bonding.html" target="_blank"&gt;http://www.linuxhorizon.ro/bonding.html&lt;/A&gt;</description>
    <pubDate>Wed, 18 Jul 2007 10:21:46 GMT</pubDate>
    <dc:creator>Van den Broeck Tijl</dc:creator>
    <dc:date>2007-07-18T10:21:46Z</dc:date>
    <item>
      <title>network error</title>
      <link>https://community.hpe.com/t5/operating-system-linux/network-error/m-p/4039672#M29345</link>
      <description>Hi Friends,&lt;BR /&gt;&lt;BR /&gt;There is a query. &lt;BR /&gt;&lt;BR /&gt;I have 2 network interface, eth0 and eth1, Supposed if the network connectivity from the switch failed to eth0. In this state if I issue a service network restart command, Will it bring up both the interfaces with out error?</description>
      <pubDate>Wed, 18 Jul 2007 10:09:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/network-error/m-p/4039672#M29345</guid>
      <dc:creator>Adithyan</dc:creator>
      <dc:date>2007-07-18T10:09:41Z</dc:date>
    </item>
    <item>
      <title>Re: network error</title>
      <link>https://community.hpe.com/t5/operating-system-linux/network-error/m-p/4039673#M29346</link>
      <description>Yes in Static mode. &lt;BR /&gt;&lt;BR /&gt;Regardless of the physical connection the software side will be set up on service restart. You can try that by yanking your network cable, restarting networking &amp;amp; ping yourself (ip, not on localhost). &lt;BR /&gt;&lt;BR /&gt;However, using DHCP will probably cause the service to restart rather slowly (initial waiting on DHCP ACK) on eth0, the dhcpcd process will then be backgrounded and networking will come up further on eth1. &lt;BR /&gt;So eth0 will be stuck without IP until connectivity is restored. &lt;BR /&gt;&lt;BR /&gt;Solution for avoiding all this is the use of "bonding". &lt;BR /&gt;See more about bonding here &lt;A href="http://docs.hp.com/en/B9903-90050/ch05s05.html" target="_blank"&gt;http://docs.hp.com/en/B9903-90050/ch05s05.html&lt;/A&gt; and here &lt;A href="http://www.linuxhorizon.ro/bonding.html" target="_blank"&gt;http://www.linuxhorizon.ro/bonding.html&lt;/A&gt;</description>
      <pubDate>Wed, 18 Jul 2007 10:21:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/network-error/m-p/4039673#M29346</guid>
      <dc:creator>Van den Broeck Tijl</dc:creator>
      <dc:date>2007-07-18T10:21:46Z</dc:date>
    </item>
    <item>
      <title>Re: network error</title>
      <link>https://community.hpe.com/t5/operating-system-linux/network-error/m-p/4039674#M29347</link>
      <description>Why you need to do a network restart if that was a switch problem? You should not need to do that.&lt;BR /&gt;&lt;BR /&gt;You could also do just ifup eth0 to avoid shutting down eth1.</description>
      <pubDate>Wed, 18 Jul 2007 10:35:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/network-error/m-p/4039674#M29347</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2007-07-18T10:35:33Z</dc:date>
    </item>
    <item>
      <title>Re: network error</title>
      <link>https://community.hpe.com/t5/operating-system-linux/network-error/m-p/4039675#M29348</link>
      <description>@Ivan: It's a theoretical question: "if I issue a service network restart command, Will it bring up both the interfaces with out error"&lt;BR /&gt;&lt;BR /&gt;In the real world I agree with you, you wouldn't do that at all :-)</description>
      <pubDate>Thu, 19 Jul 2007 03:29:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/network-error/m-p/4039675#M29348</guid>
      <dc:creator>Van den Broeck Tijl</dc:creator>
      <dc:date>2007-07-19T03:29:26Z</dc:date>
    </item>
    <item>
      <title>Re: network error</title>
      <link>https://community.hpe.com/t5/operating-system-linux/network-error/m-p/4039676#M29349</link>
      <description>If you do a 'service network restart', it will drop both eth0 and eth1, break basically all network services that are currently running that's bound to either interface (sshd, httpd, nfs, etc. etc.), and then bring them up again.&lt;BR /&gt;&lt;BR /&gt;Using 'network restart' is the sledge-hammer.  It's inadvisable to do it. *EVER*. on a live system.&lt;BR /&gt;&lt;BR /&gt;As for whether it'll bring the interfaces up without error, that depends on the error, the switch fault, and far too many other variables to say conclusivly.&lt;BR /&gt;&lt;BR /&gt;Assuming it's just the switch going wonky and a 'replug' of the cable would fix it (or shutdown of interface and bring back up), then yeah.. Sure..&lt;BR /&gt;&lt;BR /&gt;If it's anything more complicated than that, then.. No, probably not.</description>
      <pubDate>Thu, 19 Jul 2007 06:00:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/network-error/m-p/4039676#M29349</guid>
      <dc:creator>Stuart Browne</dc:creator>
      <dc:date>2007-07-19T06:00:36Z</dc:date>
    </item>
    <item>
      <title>Re: network error</title>
      <link>https://community.hpe.com/t5/operating-system-linux/network-error/m-p/4039677#M29350</link>
      <description>man ip&lt;BR /&gt;&lt;BR /&gt;You can enact on a single interface without the shotgun to the face of a "service" command</description>
      <pubDate>Thu, 19 Jul 2007 07:27:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/network-error/m-p/4039677#M29350</guid>
      <dc:creator>Don Vanco - Linux Ninja</dc:creator>
      <dc:date>2007-07-19T07:27:48Z</dc:date>
    </item>
    <item>
      <title>Re: network error</title>
      <link>https://community.hpe.com/t5/operating-system-linux/network-error/m-p/4039678#M29351</link>
      <description>Post the result when you get a chance to test with ip command</description>
      <pubDate>Sat, 21 Jul 2007 17:22:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/network-error/m-p/4039678#M29351</guid>
      <dc:creator>skt_skt</dc:creator>
      <dc:date>2007-07-21T17:22:35Z</dc:date>
    </item>
  </channel>
</rss>

