<?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: rhel5 nic problem in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/rhel5-nic-problem/m-p/4723969#M43012</link>
    <description>There are many ways to check if the NIC card is working or not. &lt;BR /&gt;&lt;BR /&gt;1. On the hardware level, first check if the NIC port has the link light and activity light turning on. If yes, on to step 2.&lt;BR /&gt;&lt;BR /&gt;2. Check the NIC is recognized in RHEL.&lt;BR /&gt;# dmesg&lt;BR /&gt;&lt;BR /&gt;3. Check if the NIC interface shows an IP address. To do this:&lt;BR /&gt;# ifconfig ethX&lt;BR /&gt;&lt;BR /&gt;If no IP address, consider the NIC configuration for either DHCP or static.&lt;BR /&gt;&lt;BR /&gt;4. Next check if you can ping some other known ip address (in the same network): &lt;BR /&gt;# ping -I ethX 192.168.1.1&lt;BR /&gt;&lt;BR /&gt;If you find any issues, check the driver being used for the NIC:&lt;BR /&gt;# ethtool -i ethX&lt;BR /&gt;&lt;BR /&gt;If the driver information is displayed, check if the driver is loaded:&lt;BR /&gt;# lsmod&lt;BR /&gt;&lt;BR /&gt;Note: you can pipe the output to grep for the driver name returned by ethtool. E.g.&lt;BR /&gt;# lsmod | grep &lt;DRIVERNAME&gt;&lt;BR /&gt;&lt;BR /&gt;This should give you a fair idea of how the NIC is working, and where the possible issue could be. Good luck!&lt;/DRIVERNAME&gt;</description>
    <pubDate>Sat, 11 Dec 2010 04:32:27 GMT</pubDate>
    <dc:creator>~sesh</dc:creator>
    <dc:date>2010-12-11T04:32:27Z</dc:date>
    <item>
      <title>rhel5 nic problem</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rhel5-nic-problem/m-p/4723966#M43009</link>
      <description>in rhel 5 my nic card is working for same time and some time its not shown in the modules itself. how to check the nic card is working fine or not. what r the commands are need to check it</description>
      <pubDate>Thu, 09 Dec 2010 06:37:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rhel5-nic-problem/m-p/4723966#M43009</guid>
      <dc:creator>venugopalanramraj</dc:creator>
      <dc:date>2010-12-09T06:37:47Z</dc:date>
    </item>
    <item>
      <title>Re: rhel5 nic problem</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rhel5-nic-problem/m-p/4723967#M43010</link>
      <description>Hi,&lt;BR /&gt;May be you can try these commands in Linux.&lt;BR /&gt;&lt;BR /&gt;  ifconfig $interface -- show the information for $interface (usually something like ifconfig eth0)&lt;BR /&gt;&lt;BR /&gt;  ethtool $interface&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;</description>
      <pubDate>Thu, 09 Dec 2010 07:22:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rhel5-nic-problem/m-p/4723967#M43010</guid>
      <dc:creator>Suman_1978</dc:creator>
      <dc:date>2010-12-09T07:22:34Z</dc:date>
    </item>
    <item>
      <title>Re: rhel5 nic problem</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rhel5-nic-problem/m-p/4723968#M43011</link>
      <description>lspci &lt;BR /&gt;&lt;BR /&gt;is the card still there ?  if it does not show then it is probably toast and in need of replacing.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 10 Dec 2010 20:06:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rhel5-nic-problem/m-p/4723968#M43011</guid>
      <dc:creator>Tim Nelson</dc:creator>
      <dc:date>2010-12-10T20:06:41Z</dc:date>
    </item>
    <item>
      <title>Re: rhel5 nic problem</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rhel5-nic-problem/m-p/4723969#M43012</link>
      <description>There are many ways to check if the NIC card is working or not. &lt;BR /&gt;&lt;BR /&gt;1. On the hardware level, first check if the NIC port has the link light and activity light turning on. If yes, on to step 2.&lt;BR /&gt;&lt;BR /&gt;2. Check the NIC is recognized in RHEL.&lt;BR /&gt;# dmesg&lt;BR /&gt;&lt;BR /&gt;3. Check if the NIC interface shows an IP address. To do this:&lt;BR /&gt;# ifconfig ethX&lt;BR /&gt;&lt;BR /&gt;If no IP address, consider the NIC configuration for either DHCP or static.&lt;BR /&gt;&lt;BR /&gt;4. Next check if you can ping some other known ip address (in the same network): &lt;BR /&gt;# ping -I ethX 192.168.1.1&lt;BR /&gt;&lt;BR /&gt;If you find any issues, check the driver being used for the NIC:&lt;BR /&gt;# ethtool -i ethX&lt;BR /&gt;&lt;BR /&gt;If the driver information is displayed, check if the driver is loaded:&lt;BR /&gt;# lsmod&lt;BR /&gt;&lt;BR /&gt;Note: you can pipe the output to grep for the driver name returned by ethtool. E.g.&lt;BR /&gt;# lsmod | grep &lt;DRIVERNAME&gt;&lt;BR /&gt;&lt;BR /&gt;This should give you a fair idea of how the NIC is working, and where the possible issue could be. Good luck!&lt;/DRIVERNAME&gt;</description>
      <pubDate>Sat, 11 Dec 2010 04:32:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rhel5-nic-problem/m-p/4723969#M43012</guid>
      <dc:creator>~sesh</dc:creator>
      <dc:date>2010-12-11T04:32:27Z</dc:date>
    </item>
  </channel>
</rss>

