<?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 High availability for VCEM in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/high-availability-for-vcem/m-p/5508913#M32061</link>
    <description>&lt;P&gt;With VCEM being a critical system that keeps track of all the MAC addresses and WWNs on the blade systems (assuming that the VCEM defined ranges are used here), I wanted to know what some of you are doing to protect it and make it highly available.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 26 Jan 2012 04:01:01 GMT</pubDate>
    <dc:creator>vash</dc:creator>
    <dc:date>2012-01-26T04:01:01Z</dc:date>
    <item>
      <title>High availability for VCEM</title>
      <link>https://community.hpe.com/t5/bladesystem-general/high-availability-for-vcem/m-p/5508913#M32061</link>
      <description>&lt;P&gt;With VCEM being a critical system that keeps track of all the MAC addresses and WWNs on the blade systems (assuming that the VCEM defined ranges are used here), I wanted to know what some of you are doing to protect it and make it highly available.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 26 Jan 2012 04:01:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/high-availability-for-vcem/m-p/5508913#M32061</guid>
      <dc:creator>vash</dc:creator>
      <dc:date>2012-01-26T04:01:01Z</dc:date>
    </item>
  </channel>
</rss>

