<?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: Interconnect problem in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/interconnect-problem/m-p/4611514#M9873</link>
    <description>Hi Nick,&lt;BR /&gt;     This may be off track, but when you communicate with a module installed in an interconnect bay (or an iLO/Remote Console), the traffic passes in and out of the enclosure through the OA management port.&lt;BR /&gt;&lt;BR /&gt;This is why the iLO's and interconnect modules must be assign IP addresses on the Management subnet.&lt;BR /&gt;&lt;BR /&gt;You may be creating a conflict by assigning a different IP address via the console cable.&lt;BR /&gt;&lt;BR /&gt;Note:: you should be able to connect to your cisco switch, from the external network, using the EBIPA address.&lt;BR /&gt;&lt;BR /&gt;Hope this helps (Im not a network guy, so if it is a naive answer, I apologise.)&lt;BR /&gt;&lt;BR /&gt;Dave.</description>
    <pubDate>Fri, 02 Apr 2010 10:43:22 GMT</pubDate>
    <dc:creator>The Brit</dc:creator>
    <dc:date>2010-04-02T10:43:22Z</dc:date>
    <item>
      <title>Interconnect problem</title>
      <link>https://community.hpe.com/t5/bladesystem-general/interconnect-problem/m-p/4611513#M9872</link>
      <description>I have c3000 blade system and cisco 3020 inserted in interconnect bay 1. I setup IP address for my HP OA - 192.168.212.160 via Web interface and setup ip address for interface FastEthernet0 for my cisco switch via console cable. I can see switch status in HP OA, all is fine(model, ip, version), but can not ping it over network. When I turn on debig icmp packets on the switch I see that packet going from 169.254.0.1. This is APIPA addres. Why it going from this address ?&lt;BR /&gt;&lt;BR /&gt;Thanks.</description>
      <pubDate>Fri, 02 Apr 2010 09:09:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/interconnect-problem/m-p/4611513#M9872</guid>
      <dc:creator>vbox.nick</dc:creator>
      <dc:date>2010-04-02T09:09:49Z</dc:date>
    </item>
    <item>
      <title>Re: Interconnect problem</title>
      <link>https://community.hpe.com/t5/bladesystem-general/interconnect-problem/m-p/4611514#M9873</link>
      <description>Hi Nick,&lt;BR /&gt;     This may be off track, but when you communicate with a module installed in an interconnect bay (or an iLO/Remote Console), the traffic passes in and out of the enclosure through the OA management port.&lt;BR /&gt;&lt;BR /&gt;This is why the iLO's and interconnect modules must be assign IP addresses on the Management subnet.&lt;BR /&gt;&lt;BR /&gt;You may be creating a conflict by assigning a different IP address via the console cable.&lt;BR /&gt;&lt;BR /&gt;Note:: you should be able to connect to your cisco switch, from the external network, using the EBIPA address.&lt;BR /&gt;&lt;BR /&gt;Hope this helps (Im not a network guy, so if it is a naive answer, I apologise.)&lt;BR /&gt;&lt;BR /&gt;Dave.</description>
      <pubDate>Fri, 02 Apr 2010 10:43:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/interconnect-problem/m-p/4611514#M9873</guid>
      <dc:creator>The Brit</dc:creator>
      <dc:date>2010-04-02T10:43:22Z</dc:date>
    </item>
  </channel>
</rss>

