<?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: Network Status BL685 in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/network-status-bl685/m-p/5232620#M51802</link>
    <description>Has anyone any suggestions?</description>
    <pubDate>Thu, 01 Apr 2010 07:17:02 GMT</pubDate>
    <dc:creator>Post_ITS_Server_Team</dc:creator>
    <dc:date>2010-04-01T07:17:02Z</dc:date>
    <item>
      <title>Network Status BL685</title>
      <link>https://community.hpe.com/t5/server-management-systems/network-status-bl685/m-p/5232619#M51801</link>
      <description>Hello&lt;BR /&gt;&lt;BR /&gt;We have in our SIM some C7000 blade enclosures with some BL685c G6 ESXi 4 Servers connected over Virtual Connect Manager. A BL685 has 16 onboard network interfaces but we don't have everyone of them connected. Thats why we have allways the network status on Major.&lt;BR /&gt;On Windows servers we solved this by disabling the unused interfaces but how can we do this on ESXi 4 servers?&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Ville</description>
      <pubDate>Tue, 30 Mar 2010 09:58:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/network-status-bl685/m-p/5232619#M51801</guid>
      <dc:creator>Post_ITS_Server_Team</dc:creator>
      <dc:date>2010-03-30T09:58:50Z</dc:date>
    </item>
    <item>
      <title>Re: Network Status BL685</title>
      <link>https://community.hpe.com/t5/server-management-systems/network-status-bl685/m-p/5232620#M51802</link>
      <description>Has anyone any suggestions?</description>
      <pubDate>Thu, 01 Apr 2010 07:17:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/network-status-bl685/m-p/5232620#M51802</guid>
      <dc:creator>Post_ITS_Server_Team</dc:creator>
      <dc:date>2010-04-01T07:17:02Z</dc:date>
    </item>
    <item>
      <title>Re: Network Status BL685</title>
      <link>https://community.hpe.com/t5/server-management-systems/network-status-bl685/m-p/5232621#M51803</link>
      <description>The only thing that can be done due to the limitations in ESXi would be to create a dummy VC network and to have the unused interfaces be connected to that network in the profile.</description>
      <pubDate>Thu, 01 Apr 2010 09:50:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/network-status-bl685/m-p/5232621#M51803</guid>
      <dc:creator>David Claypool</dc:creator>
      <dc:date>2010-04-01T09:50:30Z</dc:date>
    </item>
    <item>
      <title>Re: Network Status BL685</title>
      <link>https://community.hpe.com/t5/server-management-systems/network-status-bl685/m-p/5232622#M51804</link>
      <description>OK I hoped that there would be something else but thanks for your reply!</description>
      <pubDate>Thu, 01 Apr 2010 12:37:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/network-status-bl685/m-p/5232622#M51804</guid>
      <dc:creator>Post_ITS_Server_Team</dc:creator>
      <dc:date>2010-04-01T12:37:22Z</dc:date>
    </item>
    <item>
      <title>Re: Network Status BL685</title>
      <link>https://community.hpe.com/t5/server-management-systems/network-status-bl685/m-p/5232623#M51805</link>
      <description>solution above</description>
      <pubDate>Thu, 01 Apr 2010 12:38:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/network-status-bl685/m-p/5232623#M51805</guid>
      <dc:creator>Post_ITS_Server_Team</dc:creator>
      <dc:date>2010-04-01T12:38:30Z</dc:date>
    </item>
  </channel>
</rss>

