<?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: Path Trace from DHCP interface? in Controllers</title>
    <link>https://community.cisco.com/t5/controllers/path-trace-from-dhcp-interface/m-p/3424223#M1044</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Got a response that this is on the roadmap for the August APIC-EM release.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 26 Mar 2016 04:30:34 GMT</pubDate>
    <dc:creator>Joe Clarke</dc:creator>
    <dc:date>2016-03-26T04:30:34Z</dc:date>
    <item>
      <title>Path Trace from DHCP interface?</title>
      <link>https://community.cisco.com/t5/controllers/path-trace-from-dhcp-interface/m-p/3424220#M1041</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I was exploring the Path Trace feature but can't get it to work with a interface that is set for ip address dhcp.&amp;nbsp; When I select that device, then can select the interface, the DHCP interfaces have an address of 0.0.0.0 and will error out if I select it.&amp;nbsp; Interfaces with a static ip address seem to work fine.&amp;nbsp; Is this a known limitation?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Mar 2019 12:27:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/controllers/path-trace-from-dhcp-interface/m-p/3424220#M1041</guid>
      <dc:creator>thjonson</dc:creator>
      <dc:date>2019-03-01T12:27:23Z</dc:date>
    </item>
    <item>
      <title>Re: Path Trace from DHCP interface?</title>
      <link>https://community.cisco.com/t5/controllers/path-trace-from-dhcp-interface/m-p/3424221#M1042</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ha, yes!&amp;nbsp; Glad to hear someone else is seeing this.&amp;nbsp; We ran into the same thing at CiscoLive in Europe.&amp;nbsp; APIC-EM is scraping "show run int" for operational data, and this is why DHCP interfaces do not work in Path Trace.&amp;nbsp; Engineering is aware of this, and I'm hoping the next release will have a solution for it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Mar 2016 20:38:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/controllers/path-trace-from-dhcp-interface/m-p/3424221#M1042</guid>
      <dc:creator>Joe Clarke</dc:creator>
      <dc:date>2016-03-25T20:38:53Z</dc:date>
    </item>
    <item>
      <title>Re: Path Trace from DHCP interface?</title>
      <link>https://community.cisco.com/t5/controllers/path-trace-from-dhcp-interface/m-p/3424222#M1043</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, I just wanted to make sure it wasn't user error on my part.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Mar 2016 21:16:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/controllers/path-trace-from-dhcp-interface/m-p/3424222#M1043</guid>
      <dc:creator>thjonson</dc:creator>
      <dc:date>2016-03-25T21:16:15Z</dc:date>
    </item>
    <item>
      <title>Re: Path Trace from DHCP interface?</title>
      <link>https://community.cisco.com/t5/controllers/path-trace-from-dhcp-interface/m-p/3424223#M1044</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Got a response that this is on the roadmap for the August APIC-EM release.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 26 Mar 2016 04:30:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/controllers/path-trace-from-dhcp-interface/m-p/3424223#M1044</guid>
      <dc:creator>Joe Clarke</dc:creator>
      <dc:date>2016-03-26T04:30:34Z</dc:date>
    </item>
  </channel>
</rss>

