<?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: dead network port: Server or switch? in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/dead-network-port-server-or-switch/m-p/4772390#M13193</link>
    <description>Cisco 3020</description>
    <pubDate>Thu, 31 Mar 2011 17:00:30 GMT</pubDate>
    <dc:creator>Albator</dc:creator>
    <dc:date>2011-03-31T17:00:30Z</dc:date>
    <item>
      <title>dead network port: Server or switch?</title>
      <link>https://community.hpe.com/t5/bladesystem-general/dead-network-port-server-or-switch/m-p/4772388#M13191</link>
      <description>Hello everyone!&lt;BR /&gt;&lt;BR /&gt;one of our half-height BL460c G1 server lost connection on one network port. How can I tell if it is the NIC port or the switch port? I have no slots left to move the server to another slot. The switch shows the port as down/down.&lt;BR /&gt;&lt;BR /&gt;Thank you!</description>
      <pubDate>Thu, 31 Mar 2011 12:45:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/dead-network-port-server-or-switch/m-p/4772388#M13191</guid>
      <dc:creator>Albator</dc:creator>
      <dc:date>2011-03-31T12:45:03Z</dc:date>
    </item>
    <item>
      <title>Re: dead network port: Server or switch?</title>
      <link>https://community.hpe.com/t5/bladesystem-general/dead-network-port-server-or-switch/m-p/4772389#M13192</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;What Interconnect are you using in the back of your enclosure?&lt;BR /&gt;i.e. Cisco 3020, SAS switch, ProCurve switch, GbE2c switch?&lt;BR /&gt;Or is it a Pass-Thru module going to an external switch?</description>
      <pubDate>Thu, 31 Mar 2011 14:02:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/dead-network-port-server-or-switch/m-p/4772389#M13192</guid>
      <dc:creator>BrianDoyle</dc:creator>
      <dc:date>2011-03-31T14:02:08Z</dc:date>
    </item>
    <item>
      <title>Re: dead network port: Server or switch?</title>
      <link>https://community.hpe.com/t5/bladesystem-general/dead-network-port-server-or-switch/m-p/4772390#M13193</link>
      <description>Cisco 3020</description>
      <pubDate>Thu, 31 Mar 2011 17:00:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/dead-network-port-server-or-switch/m-p/4772390#M13193</guid>
      <dc:creator>Albator</dc:creator>
      <dc:date>2011-03-31T17:00:30Z</dc:date>
    </item>
    <item>
      <title>Re: dead network port: Server or switch?</title>
      <link>https://community.hpe.com/t5/bladesystem-general/dead-network-port-server-or-switch/m-p/4772391#M13194</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;because, as you likely know, the connections between the blades I/O and the interconnects (like the Cisco switches i.e.) in the back are hardwired by design, the only way i see that you can determine 100% if this is a server LAN port issue or a LAN switch issue is swap 2 blade servers from position....&lt;BR /&gt;This impacts both servers but if you already removed/reseated the blade itself and this issue stays then the next step with the least impact is changing this blade to another slot.&lt;BR /&gt;&lt;BR /&gt;I don't know if the Cisco switch allows to disable/re-enable a port, to see if this 'wakes' up the connection....&lt;BR /&gt;&lt;BR /&gt;Kris&lt;BR /&gt;</description>
      <pubDate>Fri, 01 Apr 2011 08:26:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/dead-network-port-server-or-switch/m-p/4772391#M13194</guid>
      <dc:creator>kris rombauts</dc:creator>
      <dc:date>2011-04-01T08:26:23Z</dc:date>
    </item>
  </channel>
</rss>

