<?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 prefix conflict when creating a NETCONF NED in NSO Developer Hub Discussions</title>
    <link>https://community.cisco.com/t5/nso-developer-hub-discussions/prefix-conflict-when-creating-a-netconf-ned/m-p/3526230#M1365</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am trying to create a NETCONF NED and several modules have prefix conflicts with NSO (such as aaa and others).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a way to deal with this in ncs-make-package? I believe ncsc has a --prefix option but I would like to check if there is a generic way&amp;nbsp; (other than manually edit the modules) such as adding something in front of all prefixes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Roque&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 01 Mar 2019 12:00:09 GMT</pubDate>
    <dc:creator>rogaglia</dc:creator>
    <dc:date>2019-03-01T12:00:09Z</dc:date>
    <item>
      <title>prefix conflict when creating a NETCONF NED</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/prefix-conflict-when-creating-a-netconf-ned/m-p/3526230#M1365</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am trying to create a NETCONF NED and several modules have prefix conflicts with NSO (such as aaa and others).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a way to deal with this in ncs-make-package? I believe ncsc has a --prefix option but I would like to check if there is a generic way&amp;nbsp; (other than manually edit the modules) such as adding something in front of all prefixes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Roque&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Mar 2019 12:00:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/prefix-conflict-when-creating-a-netconf-ned/m-p/3526230#M1365</guid>
      <dc:creator>rogaglia</dc:creator>
      <dc:date>2019-03-01T12:00:09Z</dc:date>
    </item>
    <item>
      <title>Re: prefix conflict when creating a NETCONF NED</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/prefix-conflict-when-creating-a-netconf-ned/m-p/3526231#M1366</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;With some Makefile hacking, I'm sure you could work around the issue. I edit the file(s) for now. Hopefully NSO will take care of this automatically when the Common Data Models support is released.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Sep 2017 13:12:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/prefix-conflict-when-creating-a-netconf-ned/m-p/3526231#M1366</guid>
      <dc:creator>Jan Lindblad</dc:creator>
      <dc:date>2017-09-26T13:12:43Z</dc:date>
    </item>
  </channel>
</rss>

