<?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: NSO - Badly formatted or nonexistent path in NSO Developer Hub Discussions</title>
    <link>https://community.cisco.com/t5/nso-developer-hub-discussions/nso-badly-formatted-or-nonexistent-path/m-p/4115539#M5441</link>
    <description>&lt;P&gt;Always good to mention that you are using NETCONF XR as may not be obvious to other users of this forum.&lt;/P&gt;</description>
    <pubDate>Wed, 08 Jul 2020 19:23:56 GMT</pubDate>
    <dc:creator>rogaglia</dc:creator>
    <dc:date>2020-07-08T19:23:56Z</dc:date>
    <item>
      <title>NSO - Badly formatted or nonexistent path</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/nso-badly-formatted-or-nonexistent-path/m-p/4115359#M5438</link>
      <description>&lt;P&gt;Hello All,&lt;/P&gt;
&lt;P&gt;I used maapi context to perform “get” operation to fetch oper data from my XR device. I get an error after “live-status” on my container level like below&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;"badly formatted or nonexistent path (8): Bad path element “show-lcmodule” after: /devices/device/live-status"&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;path = “/devices/device{netconfd}/live-status/show-lcmodule/lcmode-gl/lcmode-slots/lcmode-slot{0}/running-lcmode”&lt;BR /&gt;running = maapi.get_elem(sock_maapi, th, path)&lt;/P&gt;
&lt;P&gt;What am I doing wrong here?&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Wed, 08 Jul 2020 14:25:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/nso-badly-formatted-or-nonexistent-path/m-p/4115359#M5438</guid>
      <dc:creator>shgaiton</dc:creator>
      <dc:date>2020-07-08T14:25:53Z</dc:date>
    </item>
    <item>
      <title>Re: NSO - Badly formatted or nonexistent path</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/nso-badly-formatted-or-nonexistent-path/m-p/4115363#M5439</link>
      <description>The path looks weird, is ex1 really a valid path in the XR yang model?&lt;BR /&gt;&lt;BR /&gt;A trick is to start by doing a show in ncs_cli and tab complete to the value you want and then do | display keypath to get a valid path.&lt;BR /&gt;</description>
      <pubDate>Wed, 08 Jul 2020 14:22:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/nso-badly-formatted-or-nonexistent-path/m-p/4115363#M5439</guid>
      <dc:creator>vleijon</dc:creator>
      <dc:date>2020-07-08T14:22:41Z</dc:date>
    </item>
    <item>
      <title>Re: NSO - Badly formatted or nonexistent path</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/nso-badly-formatted-or-nonexistent-path/m-p/4115367#M5440</link>
      <description>Sorry, I wanted to just give a reference yang. The actual path has been updated.</description>
      <pubDate>Wed, 08 Jul 2020 14:26:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/nso-badly-formatted-or-nonexistent-path/m-p/4115367#M5440</guid>
      <dc:creator>shgaiton</dc:creator>
      <dc:date>2020-07-08T14:26:35Z</dc:date>
    </item>
    <item>
      <title>Re: NSO - Badly formatted or nonexistent path</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/nso-badly-formatted-or-nonexistent-path/m-p/4115539#M5441</link>
      <description>&lt;P&gt;Always good to mention that you are using NETCONF XR as may not be obvious to other users of this forum.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Jul 2020 19:23:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/nso-badly-formatted-or-nonexistent-path/m-p/4115539#M5441</guid>
      <dc:creator>rogaglia</dc:creator>
      <dc:date>2020-07-08T19:23:56Z</dc:date>
    </item>
  </channel>
</rss>

