<?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: HP DL360 eth2 link down issue in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/hp-dl360-eth2-link-down-issue/m-p/4784582#M81326</link>
    <description>Hello. &lt;BR /&gt;&lt;BR /&gt;Check with the communications department the port settings. May be disabled. &lt;BR /&gt;</description>
    <pubDate>Mon, 16 May 2011 10:01:16 GMT</pubDate>
    <dc:creator>Noé</dc:creator>
    <dc:date>2011-05-16T10:01:16Z</dc:date>
    <item>
      <title>HP DL360 eth2 link down issue</title>
      <link>https://community.hpe.com/t5/operating-system-linux/hp-dl360-eth2-link-down-issue/m-p/4784580#M81324</link>
      <description>Hi All,&lt;BR /&gt;&lt;BR /&gt;Does anyone know about a know issue with HP DL 360 eth2 interface. The eth2 interface has been assigned with an IP address but the link never comes up. &lt;BR /&gt;We have changed the cables / swapped the eth0 and eth2 cables, but the link still shows down on eth2. &lt;BR /&gt;&lt;BR /&gt;[root@sessionmgr bin]# ethtool eth2&lt;BR /&gt;Settings for eth2:&lt;BR /&gt;        Supported ports: [ TP ]&lt;BR /&gt;        Supported link modes:   10baseT/Half 10baseT/Full&lt;BR /&gt;                                100baseT/Half 100baseT/Full&lt;BR /&gt;                                1000baseT/Full&lt;BR /&gt;        Supports auto-negotiation: Yes&lt;BR /&gt;        Advertised link modes:  10baseT/Half 10baseT/Full&lt;BR /&gt;                                100baseT/Half 100baseT/Full&lt;BR /&gt;                                1000baseT/Full&lt;BR /&gt;        Advertised auto-negotiation: Yes&lt;BR /&gt;        Speed: Unknown!&lt;BR /&gt;        Duplex: Unknown! (255)&lt;BR /&gt;        Port: Twisted Pair&lt;BR /&gt;        PHYAD: 1&lt;BR /&gt;        Transceiver: internal&lt;BR /&gt;        Auto-negotiation: on&lt;BR /&gt;        Supports Wake-on: g&lt;BR /&gt;        Wake-on: g&lt;BR /&gt;        Link detected: no&lt;BR /&gt;&lt;BR /&gt;[root@sessionmgr ~]# mii-tool eth2&lt;BR /&gt;eth2: no link&lt;BR /&gt;&lt;BR /&gt;[root@sessionmgr bin]# arp&lt;BR /&gt;Address                  HWtype  HWaddress           Flags Mask            Iface&lt;BR /&gt;10.100.220.22            ether   00:0E:7F:F1:E0:1B   C                     eth0&lt;BR /&gt;systemmgr.monsoon.co.uk  ether   00:CA:FE:89:96:46   C                     eth0&lt;BR /&gt;10.100.220.20            ether   00:0E:7F:F1:E0:1B   C                     eth0&lt;BR /&gt;10.100.220.20                    (incomplete)                              eth2&lt;BR /&gt;[root@sessionmgr bin]#&lt;BR /&gt;&lt;BR /&gt;[root@sessionmgr ~]# dmesg | grep eth2&lt;BR /&gt;eth2: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem 92000000, IRQ 177, node addr 001a64e74e48&lt;BR /&gt;bnx2: eth2: using MSIX&lt;BR /&gt;ADDRCONF(NETDEV_UP): eth2: link is not ready&lt;BR /&gt;bnx2: eth2: using MSIX&lt;BR /&gt;ADDRCONF(NETDEV_UP): eth2: link is not ready&lt;BR /&gt;bnx2: eth2: using MSIX&lt;BR /&gt;ADDRCONF(NETDEV_UP): eth2: link is not ready&lt;BR /&gt;bnx2: eth2: using MSIX&lt;BR /&gt;ADDRCONF(NETDEV_UP): eth2: link is not ready&lt;BR /&gt;bnx2: eth2: using MSIX&lt;BR /&gt;ADDRCONF(NETDEV_UP): eth2: link is not ready&lt;BR /&gt;[root@sessionmgr sysconfig]# ping -I eth2 10.100.220.250&lt;BR /&gt;PING 10.100.220.250 (10.100.220.250) from 10.100.220.39 eth2: 56(84) bytes of data.&lt;BR /&gt;From 10.100.220.39 icmp_seq=2 Destination Host Unreachable&lt;BR /&gt;From 10.100.220.39 icmp_seq=3 Destination Host Unreachable&lt;BR /&gt;From 10.100.220.39 icmp_seq=4 Destination Host Unreachable&lt;BR /&gt;From 10.100.220.39 icmp_seq=6 Destination Host Unreachable&lt;BR /&gt;From 10.100.220.39 icmp_seq=7 Destination Host Unreachable&lt;BR /&gt;From 10.100.220.39 icmp_seq=8 Destination Host Unreachable&lt;BR /&gt; &lt;BR /&gt;</description>
      <pubDate>Thu, 05 May 2011 08:39:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/hp-dl360-eth2-link-down-issue/m-p/4784580#M81324</guid>
      <dc:creator>Sabir009</dc:creator>
      <dc:date>2011-05-05T08:39:08Z</dc:date>
    </item>
    <item>
      <title>Re: HP DL360 eth2 link down issue</title>
      <link>https://community.hpe.com/t5/operating-system-linux/hp-dl360-eth2-link-down-issue/m-p/4784581#M81325</link>
      <description>What Linux OS?&lt;BR /&gt;&lt;BR /&gt;Have you run diagnostics on the port to see if has issues?&lt;BR /&gt;</description>
      <pubDate>Thu, 12 May 2011 12:36:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/hp-dl360-eth2-link-down-issue/m-p/4784581#M81325</guid>
      <dc:creator>Alzhy</dc:creator>
      <dc:date>2011-05-12T12:36:27Z</dc:date>
    </item>
    <item>
      <title>Re: HP DL360 eth2 link down issue</title>
      <link>https://community.hpe.com/t5/operating-system-linux/hp-dl360-eth2-link-down-issue/m-p/4784582#M81326</link>
      <description>Hello. &lt;BR /&gt;&lt;BR /&gt;Check with the communications department the port settings. May be disabled. &lt;BR /&gt;</description>
      <pubDate>Mon, 16 May 2011 10:01:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/hp-dl360-eth2-link-down-issue/m-p/4784582#M81326</guid>
      <dc:creator>Noé</dc:creator>
      <dc:date>2011-05-16T10:01:16Z</dc:date>
    </item>
  </channel>
</rss>

