<?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 VCEM deployment in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/hp-vcem-deployment/m-p/4495122#M7293</link>
    <description>Kristof&lt;BR /&gt;&lt;BR /&gt;Have a look in this community, there are some HP experts there. Vincent Berger is "the man" if he is on there.&lt;BR /&gt;HP Virtual Connect Interest Group&lt;BR /&gt;&lt;A href="https://h30340.leveragesoftware.com/default.aspx" target="_blank"&gt;https://h30340.leveragesoftware.com/default.aspx&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Basically if blade enclosures share storage then its best to put them in the same group.&lt;BR /&gt;&lt;BR /&gt;All enclosures in the same group must share identical "networks" and storage fabrics, and I think they need the same uplinks and SUS. And same for MAP/TAG Vlans.&lt;BR /&gt;&lt;BR /&gt;You can "import" an enclosure into a group and the config gets copied down. But if you are trying to join an existing enclosure with running servers to a group you need to make sure the config is exactly the same before you can import it.&lt;BR /&gt;&lt;BR /&gt;VCEM relies on SIM running, if SIM is not running you cant move profiles (without using HP secret commands). Therefore SIM and the SIM database become important points of failure.&lt;BR /&gt;So ensure SIM is ok and I'd recommend to move the SIM database from SQL Express to full SQL and get it backed up daily (if not more often)&lt;BR /&gt;&lt;BR /&gt;As long as you follow the above.... VCEM is just like having a single interface to all your VC interfaces.&lt;BR /&gt;&lt;BR /&gt;Have you also thought of using the new enclosure stacking feature in the new firmware?</description>
    <pubDate>Thu, 10 Sep 2009 18:35:04 GMT</pubDate>
    <dc:creator>Adrian Clint</dc:creator>
    <dc:date>2009-09-10T18:35:04Z</dc:date>
    <item>
      <title>HP VCEM deployment</title>
      <link>https://community.hpe.com/t5/bladesystem-general/hp-vcem-deployment/m-p/4495121#M7292</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;I've been in contact with VCM, installing it on enclosures without any prior configuration, using the profiles to manage the blades within the enclosure, ...&lt;BR /&gt;&lt;BR /&gt;The company I now work for does not yet have VCEM, but the project will start up next week with an extensive study on how the high-level design.  Basically we want to be able to use all the VCEM benefits such as managing profiles pools with multiple enclosures, as so forth.&lt;BR /&gt;&lt;BR /&gt;We have several sites throughout Europe with sites ranging from 5 to 30 C7000 enclosures.&lt;BR /&gt;Unfortunately I don't find much information on how to design an environment of this size.  What are Best Practises?  Are there any sample scenario's?  What needs to be kept in mind?&lt;BR /&gt;&lt;BR /&gt;Thanks in advance for all info.</description>
      <pubDate>Thu, 10 Sep 2009 11:58:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/hp-vcem-deployment/m-p/4495121#M7292</guid>
      <dc:creator>KristofVanweert</dc:creator>
      <dc:date>2009-09-10T11:58:38Z</dc:date>
    </item>
    <item>
      <title>Re: HP VCEM deployment</title>
      <link>https://community.hpe.com/t5/bladesystem-general/hp-vcem-deployment/m-p/4495122#M7293</link>
      <description>Kristof&lt;BR /&gt;&lt;BR /&gt;Have a look in this community, there are some HP experts there. Vincent Berger is "the man" if he is on there.&lt;BR /&gt;HP Virtual Connect Interest Group&lt;BR /&gt;&lt;A href="https://h30340.leveragesoftware.com/default.aspx" target="_blank"&gt;https://h30340.leveragesoftware.com/default.aspx&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Basically if blade enclosures share storage then its best to put them in the same group.&lt;BR /&gt;&lt;BR /&gt;All enclosures in the same group must share identical "networks" and storage fabrics, and I think they need the same uplinks and SUS. And same for MAP/TAG Vlans.&lt;BR /&gt;&lt;BR /&gt;You can "import" an enclosure into a group and the config gets copied down. But if you are trying to join an existing enclosure with running servers to a group you need to make sure the config is exactly the same before you can import it.&lt;BR /&gt;&lt;BR /&gt;VCEM relies on SIM running, if SIM is not running you cant move profiles (without using HP secret commands). Therefore SIM and the SIM database become important points of failure.&lt;BR /&gt;So ensure SIM is ok and I'd recommend to move the SIM database from SQL Express to full SQL and get it backed up daily (if not more often)&lt;BR /&gt;&lt;BR /&gt;As long as you follow the above.... VCEM is just like having a single interface to all your VC interfaces.&lt;BR /&gt;&lt;BR /&gt;Have you also thought of using the new enclosure stacking feature in the new firmware?</description>
      <pubDate>Thu, 10 Sep 2009 18:35:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/hp-vcem-deployment/m-p/4495122#M7293</guid>
      <dc:creator>Adrian Clint</dc:creator>
      <dc:date>2009-09-10T18:35:04Z</dc:date>
    </item>
  </channel>
</rss>

