<?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: REST API for CLI &amp;quot;default interface&amp;quot; in NSO Developer Hub Discussions</title>
    <link>https://community.cisco.com/t5/nso-developer-hub-discussions/rest-api-for-cli-quot-default-interface-quot/m-p/3448350#M412</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If the command is supported by the NED, then you can do this over the REST interface. If the command is missing in the NED, then you can request it: &lt;A href="https://community.cisco.com/docs/DOC-71777"&gt;Detailed process regarding NSO and NED support&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 21 Aug 2017 10:00:49 GMT</pubDate>
    <dc:creator>KJ Rossavik</dc:creator>
    <dc:date>2017-08-21T10:00:49Z</dc:date>
    <item>
      <title>REST API for CLI "default interface"</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/rest-api-for-cli-quot-default-interface-quot/m-p/3448349#M411</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="font-size: 13.3333px;"&gt;Hi,&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;Apologies if I'm asking silly question - but there is no mechanism for REST api to send command "default interface xxx", am I right?&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;Reason I'm asking is currently I'm trying to apply rule policies, and one of the requirement from customer is REST api must not reset interface loopback config (CLI = "default interface Loopback xx").&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;So it's safe to say since REST can't issue that CLI, it should be fine?&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;I can apply rule to cover "no interface Loopback xx" scenario - just hoping that I don't have to create another policy rule for restricting &lt;SPAN style="font-size: 13.3333px;"&gt;"default interface Loopback xx"?&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;Thanks in advance!&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Mar 2019 11:58:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/rest-api-for-cli-quot-default-interface-quot/m-p/3448349#M411</guid>
      <dc:creator>smansor</dc:creator>
      <dc:date>2019-03-01T11:58:03Z</dc:date>
    </item>
    <item>
      <title>Re: REST API for CLI "default interface"</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/rest-api-for-cli-quot-default-interface-quot/m-p/3448350#M412</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If the command is supported by the NED, then you can do this over the REST interface. If the command is missing in the NED, then you can request it: &lt;A href="https://community.cisco.com/docs/DOC-71777"&gt;Detailed process regarding NSO and NED support&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Aug 2017 10:00:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/rest-api-for-cli-quot-default-interface-quot/m-p/3448350#M412</guid>
      <dc:creator>KJ Rossavik</dc:creator>
      <dc:date>2017-08-21T10:00:49Z</dc:date>
    </item>
    <item>
      <title>Re: REST API for CLI "default interface"</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/rest-api-for-cli-quot-default-interface-quot/m-p/3448351#M413</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;NSO REST can send the command by live-status feature.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;admin@ncs# conf
Entering configuration mode terminal
admin@ncs(config)# devices device csr1kv config default interface Loopback 100
result
Interface Loopback100 set to default configuration
CSR1000v(config)#
admin@ncs(config)#
&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is an action, and you can exec it from REST as well.&lt;/P&gt;&lt;PRE&gt;$ curl -X POST -u admin:admin&amp;nbsp; \
http://localhost:8080/api/operations/devices/device/csr1kv/config/ios:EXEC/default \
-H "Content-Type: application/vnd.yang.data+json" \
-d '{"input": {"args" : "interface Loopback 100"}}'
{
&amp;nbsp; "tailf-ned-cisco-ios:output": {
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "result": "\r\nInterface Loopback100 set to default configuration\r\nCSR1000v(config)#"
&amp;nbsp;&amp;nbsp;&amp;nbsp; }
 }
&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You would need to perform sync-from after the execution, otherwise the config may be out-of-sync.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Akira&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Aug 2017 03:27:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/rest-api-for-cli-quot-default-interface-quot/m-p/3448351#M413</guid>
      <dc:creator>Akira Iwamoto</dc:creator>
      <dc:date>2017-08-22T03:27:05Z</dc:date>
    </item>
    <item>
      <title>Re: REST API for CLI "default interface"</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/rest-api-for-cli-quot-default-interface-quot/m-p/3448352#M414</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ah - ok so REST will be able to send CLI command directly on top of using NED.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ok I think another way for me is to use AAA - rule list to restrict it then.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you Akira-san!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Aug 2017 03:30:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/rest-api-for-cli-quot-default-interface-quot/m-p/3448352#M414</guid>
      <dc:creator>smansor</dc:creator>
      <dc:date>2017-08-22T03:30:58Z</dc:date>
    </item>
    <item>
      <title>Re: REST API for CLI "default interface"</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/rest-api-for-cli-quot-default-interface-quot/m-p/3448353#M415</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You may also wish to review this post:&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.cisco.com/thread/84801" title="https://communities.cisco.com/thread/84801"&gt;https://communities.cisco.com/thread/84801&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;where the discussion was about restricting certain device configs using NSO tfcp:policy rules...&lt;/P&gt;&lt;P&gt;there were several nice examples provided.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Aug 2017 19:04:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/rest-api-for-cli-quot-default-interface-quot/m-p/3448353#M415</guid>
      <dc:creator>gschudel</dc:creator>
      <dc:date>2017-08-22T19:04:06Z</dc:date>
    </item>
  </channel>
</rss>

