<?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: Multiple OA (iLo) c7000 in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/multiple-oa-ilo-c7000/m-p/4794962#M13734</link>
    <description>&lt;!--!*#--&gt;HP best practice is for the VC and OA modules to be on the same subnet. This is also important if you are stacking enclosures for the purpose of configuring a single VC Domain IP. We typically square those away on their own VLAN using static IP for OA and EIBPA for the VC on a management network. IPs are sequential. For example:&lt;BR /&gt;&lt;BR /&gt;.2 OA 1&lt;BR /&gt;.3 OA 2&lt;BR /&gt;.4 VC 1&lt;BR /&gt;.4 VC 2&lt;BR /&gt;&lt;BR /&gt;Also - avoid Enclosure IP mode at all cost.&lt;BR /&gt;&lt;BR /&gt;Then, you can easily VLAN iLO on a per server basis - you do that in the OA: Enclosure Information -&amp;gt; Enclosure Settings -&amp;gt; VLAN Configuration. You decide whether EIBPA, iLO static or VLAN specific DHCP is used for the iLO IP addressing. &lt;BR /&gt;&lt;BR /&gt;You will just need to remember to tag up the interface that connect your OA modules to your network. For example:&lt;BR /&gt;&lt;BR /&gt;VLAN 10: OA/VC&lt;BR /&gt;VLAN 20: Environment A ILO&lt;BR /&gt;VLAN 30: Environment B ILO&lt;BR /&gt;&lt;BR /&gt;Lastly, when you design you access credentials - ensure you have have two users (or groups) that have typically Operator access to the OA and you define which device bays they can access. So:&lt;BR /&gt;&lt;BR /&gt;Operator A:&lt;BR /&gt;    Power management&lt;BR /&gt;    Remote Console&lt;BR /&gt;    Virtual Media&lt;BR /&gt;&lt;BR /&gt;    Access to Environment A Device Bays Only&lt;BR /&gt;&lt;BR /&gt;Operator B:&lt;BR /&gt;    Power management&lt;BR /&gt;    Remote Console&lt;BR /&gt;    Virtual Media&lt;BR /&gt;&lt;BR /&gt;    Access to Environment B Device Bays Only&lt;BR /&gt;&lt;BR /&gt;We never permit anything but administrator access to virtual connect.&lt;BR /&gt;&lt;BR /&gt;Hope that helps.</description>
    <pubDate>Thu, 16 Jun 2011 19:58:13 GMT</pubDate>
    <dc:creator>H4nd0</dc:creator>
    <dc:date>2011-06-16T19:58:13Z</dc:date>
    <item>
      <title>Multiple OA (iLo) c7000</title>
      <link>https://community.hpe.com/t5/bladesystem-general/multiple-oa-ilo-c7000/m-p/4794959#M13731</link>
      <description>I have a chassis that we are using for two different environments.  I will give an example, let’s say A environments servers are 10.12x and B servers are on 10.22x.  The OA has 10.12x.  The B environment servers are on 10.22x.  We really don’t want to have a B environment server with a A environment ilo address.  I was hoping there was a way for the ilo’s to be setup on two different networks but it sounds like that is not possible.   Is that the case?</description>
      <pubDate>Thu, 02 Jun 2011 16:11:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/multiple-oa-ilo-c7000/m-p/4794959#M13731</guid>
      <dc:creator>sdf2sjk</dc:creator>
      <dc:date>2011-06-02T16:11:06Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple OA (iLo) c7000</title>
      <link>https://community.hpe.com/t5/bladesystem-general/multiple-oa-ilo-c7000/m-p/4794960#M13732</link>
      <description>You are correct. Is the prospect of having all the ilos on one subnet so bad?</description>
      <pubDate>Fri, 03 Jun 2011 07:28:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/multiple-oa-ilo-c7000/m-p/4794960#M13732</guid>
      <dc:creator>cjb_1</dc:creator>
      <dc:date>2011-06-03T07:28:30Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple OA (iLo) c7000</title>
      <link>https://community.hpe.com/t5/bladesystem-general/multiple-oa-ilo-c7000/m-p/4794961#M13733</link>
      <description>Well we have two different iLo networks in this computer room.  One is our airline servers the other is for the servers that run the sort.  Differnt names spaces... so the guys that handle DNS don't like us having a server within one name space and the ilo being in the other.  We are trying to keep both server IP and iLo IP within the same name space.</description>
      <pubDate>Fri, 03 Jun 2011 09:56:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/multiple-oa-ilo-c7000/m-p/4794961#M13733</guid>
      <dc:creator>sdf2sjk</dc:creator>
      <dc:date>2011-06-03T09:56:05Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple OA (iLo) c7000</title>
      <link>https://community.hpe.com/t5/bladesystem-general/multiple-oa-ilo-c7000/m-p/4794962#M13734</link>
      <description>&lt;!--!*#--&gt;HP best practice is for the VC and OA modules to be on the same subnet. This is also important if you are stacking enclosures for the purpose of configuring a single VC Domain IP. We typically square those away on their own VLAN using static IP for OA and EIBPA for the VC on a management network. IPs are sequential. For example:&lt;BR /&gt;&lt;BR /&gt;.2 OA 1&lt;BR /&gt;.3 OA 2&lt;BR /&gt;.4 VC 1&lt;BR /&gt;.4 VC 2&lt;BR /&gt;&lt;BR /&gt;Also - avoid Enclosure IP mode at all cost.&lt;BR /&gt;&lt;BR /&gt;Then, you can easily VLAN iLO on a per server basis - you do that in the OA: Enclosure Information -&amp;gt; Enclosure Settings -&amp;gt; VLAN Configuration. You decide whether EIBPA, iLO static or VLAN specific DHCP is used for the iLO IP addressing. &lt;BR /&gt;&lt;BR /&gt;You will just need to remember to tag up the interface that connect your OA modules to your network. For example:&lt;BR /&gt;&lt;BR /&gt;VLAN 10: OA/VC&lt;BR /&gt;VLAN 20: Environment A ILO&lt;BR /&gt;VLAN 30: Environment B ILO&lt;BR /&gt;&lt;BR /&gt;Lastly, when you design you access credentials - ensure you have have two users (or groups) that have typically Operator access to the OA and you define which device bays they can access. So:&lt;BR /&gt;&lt;BR /&gt;Operator A:&lt;BR /&gt;    Power management&lt;BR /&gt;    Remote Console&lt;BR /&gt;    Virtual Media&lt;BR /&gt;&lt;BR /&gt;    Access to Environment A Device Bays Only&lt;BR /&gt;&lt;BR /&gt;Operator B:&lt;BR /&gt;    Power management&lt;BR /&gt;    Remote Console&lt;BR /&gt;    Virtual Media&lt;BR /&gt;&lt;BR /&gt;    Access to Environment B Device Bays Only&lt;BR /&gt;&lt;BR /&gt;We never permit anything but administrator access to virtual connect.&lt;BR /&gt;&lt;BR /&gt;Hope that helps.</description>
      <pubDate>Thu, 16 Jun 2011 19:58:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/multiple-oa-ilo-c7000/m-p/4794962#M13734</guid>
      <dc:creator>H4nd0</dc:creator>
      <dc:date>2011-06-16T19:58:13Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple OA (iLo) c7000</title>
      <link>https://community.hpe.com/t5/bladesystem-general/multiple-oa-ilo-c7000/m-p/4794963#M13735</link>
      <description>Thanks for the info.</description>
      <pubDate>Fri, 17 Jun 2011 11:21:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/multiple-oa-ilo-c7000/m-p/4794963#M13735</guid>
      <dc:creator>sdf2sjk</dc:creator>
      <dc:date>2011-06-17T11:21:13Z</dc:date>
    </item>
  </channel>
</rss>

