<?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: Different IP range for Controller and managed devices in Controllers</title>
    <link>https://community.cisco.com/t5/controllers/different-ip-range-for-controller-and-managed-devices/m-p/3523513#M2774</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Usually to be taken care by the routing. You can add as many routes on the controller itself, however IMO, that may not be scalable. Instead, if you can point controller to a next hop or two, which in turn has routing for managed subnets, that'd scale better. If such next hop is a physical device like Cisco ASR, you can use appropriate routing protocol (BGP/EIGRP/OSPF etc.)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 19 Dec 2016 22:12:14 GMT</pubDate>
    <dc:creator>cchitnis</dc:creator>
    <dc:date>2016-12-19T22:12:14Z</dc:date>
    <item>
      <title>Different IP range for Controller and managed devices</title>
      <link>https://community.cisco.com/t5/controllers/different-ip-range-for-controller-and-managed-devices/m-p/3523512#M2773</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Newbie question here. What I have seen so far is that APIC-EM controller uses one IP for its management and also pushing/pulling data on managed devices. In a situation where managed devices are in different subnet, what's the best approach to make them talk to the controller?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Mar 2019 12:34:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/controllers/different-ip-range-for-controller-and-managed-devices/m-p/3523512#M2773</guid>
      <dc:creator>mehdi.rashidi</dc:creator>
      <dc:date>2019-03-01T12:34:48Z</dc:date>
    </item>
    <item>
      <title>Re: Different IP range for Controller and managed devices</title>
      <link>https://community.cisco.com/t5/controllers/different-ip-range-for-controller-and-managed-devices/m-p/3523513#M2774</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Usually to be taken care by the routing. You can add as many routes on the controller itself, however IMO, that may not be scalable. Instead, if you can point controller to a next hop or two, which in turn has routing for managed subnets, that'd scale better. If such next hop is a physical device like Cisco ASR, you can use appropriate routing protocol (BGP/EIGRP/OSPF etc.)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Dec 2016 22:12:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/controllers/different-ip-range-for-controller-and-managed-devices/m-p/3523513#M2774</guid>
      <dc:creator>cchitnis</dc:creator>
      <dc:date>2016-12-19T22:12:14Z</dc:date>
    </item>
  </channel>
</rss>

