<?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 UpIntfName DB variable for sub-interfaces in Controllers</title>
    <link>https://community.cisco.com/t5/controllers/upintfname-db-variable-for-sub-interfaces/m-p/3506052#M1402</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just a note in case anyone else stumbles upon this and gets as confused as I did: there is a discrepancy between how the UpIntfName DB variable handles sub-interfaces and how routers/switches handle them. UpIntfName selects interfaces that don't have 'shutdown' in their config. For example:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;interface gi0/0&lt;/P&gt;&lt;P&gt; description physical interface&lt;/P&gt;&lt;P&gt; shutdown&lt;/P&gt;&lt;P&gt;interface gi0/0.10&lt;/P&gt;&lt;P&gt; description sub-interface&lt;/P&gt;&lt;P&gt; no shut&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With the above configuration a 'sh int desc' on the router will show the sub-interface as being 'admin down' because it's parent physical interface is shutdown. However, UpIntfName will include the sub-interface in any templates you deploy. To correctly exclude the sub-interfaces from UpIntfName you have to enter the shutdown command on each of them (and probably re-sync the device in Prime). Was getting confused as the show commands on the router said the subs were shut and it was only when I looked at 'show run int' that I noticed they're actually not.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyway, its not a bug or problem, just thought I'd mention it, hope that helps anyone who comes across it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dave&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 29 Nov 2016 10:32:32 GMT</pubDate>
    <dc:creator>Dave Lewis</dc:creator>
    <dc:date>2016-11-29T10:32:32Z</dc:date>
    <item>
      <title>UpIntfName DB variable for sub-interfaces</title>
      <link>https://community.cisco.com/t5/controllers/upintfname-db-variable-for-sub-interfaces/m-p/3506052#M1402</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just a note in case anyone else stumbles upon this and gets as confused as I did: there is a discrepancy between how the UpIntfName DB variable handles sub-interfaces and how routers/switches handle them. UpIntfName selects interfaces that don't have 'shutdown' in their config. For example:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;interface gi0/0&lt;/P&gt;&lt;P&gt; description physical interface&lt;/P&gt;&lt;P&gt; shutdown&lt;/P&gt;&lt;P&gt;interface gi0/0.10&lt;/P&gt;&lt;P&gt; description sub-interface&lt;/P&gt;&lt;P&gt; no shut&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With the above configuration a 'sh int desc' on the router will show the sub-interface as being 'admin down' because it's parent physical interface is shutdown. However, UpIntfName will include the sub-interface in any templates you deploy. To correctly exclude the sub-interfaces from UpIntfName you have to enter the shutdown command on each of them (and probably re-sync the device in Prime). Was getting confused as the show commands on the router said the subs were shut and it was only when I looked at 'show run int' that I noticed they're actually not.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyway, its not a bug or problem, just thought I'd mention it, hope that helps anyone who comes across it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dave&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Nov 2016 10:32:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/controllers/upintfname-db-variable-for-sub-interfaces/m-p/3506052#M1402</guid>
      <dc:creator>Dave Lewis</dc:creator>
      <dc:date>2016-11-29T10:32:32Z</dc:date>
    </item>
  </channel>
</rss>

