<?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: Virtual connect manager in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-manager/m-p/5133836#M15028</link>
    <description>Ryadh,&lt;BR /&gt;&lt;BR /&gt;can you check what IP address the VC Ethernet module in bay 1 has got by looking at the EBIPA details in the OA GUI ?&lt;BR /&gt;&lt;BR /&gt;If that is different then the one the hyperlink in the OA GUI send you to, then try to go to that IP address directly.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;&lt;BR /&gt;Kris&lt;BR /&gt;</description>
    <pubDate>Mon, 06 Oct 2008 08:23:04 GMT</pubDate>
    <dc:creator>kris rombauts</dc:creator>
    <dc:date>2008-10-06T08:23:04Z</dc:date>
    <item>
      <title>Virtual connect manager</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-manager/m-p/5133835#M15027</link>
      <description>Hello&lt;BR /&gt;&lt;BR /&gt;I have C7K encluser with 02 VC-E in bay 1&amp;amp;2 ,&lt;BR /&gt;02 VC-FC in bay 5&amp;amp;8 and 14 BL460 ,&lt;BR /&gt;When i'm connecting to VC manager from OA i'm get the error  "Active Virtual Connect Manager not at this IP address" from VCM GUI .&lt;BR /&gt;&lt;BR /&gt;Is there another way to get access to VCM ,or how to fix that ?&lt;BR /&gt;&lt;BR /&gt;Thanks ,&lt;BR /&gt;</description>
      <pubDate>Sun, 05 Oct 2008 20:33:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-manager/m-p/5133835#M15027</guid>
      <dc:creator>salem_3</dc:creator>
      <dc:date>2008-10-05T20:33:00Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual connect manager</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-manager/m-p/5133836#M15028</link>
      <description>Ryadh,&lt;BR /&gt;&lt;BR /&gt;can you check what IP address the VC Ethernet module in bay 1 has got by looking at the EBIPA details in the OA GUI ?&lt;BR /&gt;&lt;BR /&gt;If that is different then the one the hyperlink in the OA GUI send you to, then try to go to that IP address directly.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;&lt;BR /&gt;Kris&lt;BR /&gt;</description>
      <pubDate>Mon, 06 Oct 2008 08:23:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-manager/m-p/5133836#M15028</guid>
      <dc:creator>kris rombauts</dc:creator>
      <dc:date>2008-10-06T08:23:04Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual connect manager</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-manager/m-p/5133837#M15029</link>
      <description>Have you tried going to the second VC bay? Try each VC enet module management console from the interconnect bays tab on OA. &lt;BR /&gt;&lt;BR /&gt;Assume you've not got a virtual connect domain ip configured yet?</description>
      <pubDate>Mon, 06 Oct 2008 10:52:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-manager/m-p/5133837#M15029</guid>
      <dc:creator>cjb_1</dc:creator>
      <dc:date>2008-10-06T10:52:29Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual connect manager</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-manager/m-p/5133838#M15030</link>
      <description>You are right Kris ,after checking the EBIPA details for the interconnect i found the address that i have to use to connect with .&lt;BR /&gt;&lt;BR /&gt;Thanks .</description>
      <pubDate>Tue, 07 Oct 2008 19:42:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-manager/m-p/5133838#M15030</guid>
      <dc:creator>salem_3</dc:creator>
      <dc:date>2008-10-07T19:42:25Z</dc:date>
    </item>
  </channel>
</rss>

