<?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 how come the xml api is not very xmly in DevNet General Discussions</title>
    <link>https://community.cisco.com/t5/devnet-general-discussions/how-come-the-xml-api-is-not-very-xmly/m-p/3605050#M985</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;i have a number of examples but this one is probably the most disturbing to me as i expect xml back.&amp;nbsp; this happens when i execute this via the xml subagent, im just pasting the console output as that is easiest to replicate.&amp;nbsp; just for the record, this is not very useful to an xml parser.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;icef5-sw1# show interface fcoe | xml&lt;/P&gt;&lt;P&gt;Ethernet1/1 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/2 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/3 is FCoE UP &lt;/P&gt;&lt;P&gt;Ethernet1/4 is FCoE UP &lt;/P&gt;&lt;P&gt;Ethernet1/5 is FCoE UP &lt;/P&gt;&lt;P&gt;Ethernet1/6 is FCoE UP &lt;/P&gt;&lt;P&gt;Ethernet1/7 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/8 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/9 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/10 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/11 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/12 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/13 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/14 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/15 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/16 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/17 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/18 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/19 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/20 is FCoE UP &lt;/P&gt;&lt;P&gt;Ethernet1/21 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/22 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/23 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/24 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/25 is FCoE UP &lt;/P&gt;&lt;P&gt;Ethernet1/26 is FCoE UP &lt;/P&gt;&lt;P&gt;Ethernet1/27 is FCoE UP &lt;/P&gt;&lt;P&gt;Ethernet1/28 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/29 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/30 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/31 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/32 is FCoE down &lt;/P&gt;&lt;P&gt;port-channel10 is FCoE down&lt;/P&gt;&lt;P&gt;port-channel11 is FCoE down &lt;/P&gt;&lt;P&gt;port-channel12 is FCoE down &lt;/P&gt;&lt;P&gt;port-channel13 is FCoE down &lt;/P&gt;&lt;P&gt;port-channel14 is FCoE down &lt;/P&gt;&lt;P&gt;port-channel15 is FCoE down &lt;/P&gt;&lt;P&gt;port-channel20 is FCoE UP &lt;/P&gt;&lt;P&gt;&amp;lt;?xml version="1.0" encoding="ISO-8859-1"?&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;lt;nf:rpc-reply xmlns:nf="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns="&lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/nxos:1.0:if_manager" rel="nofollow" target="_blank"&gt;http://www.cisco.com/nxos:1.0:if_manager&lt;/A&gt;&lt;SPAN&gt;"&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt; &amp;lt;nf:data/&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;/nf:rpc-reply&amp;gt;&lt;/P&gt;&lt;P&gt;]]&amp;gt;]]&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 01 Mar 2019 10:49:50 GMT</pubDate>
    <dc:creator>hotlollycakes</dc:creator>
    <dc:date>2019-03-01T10:49:50Z</dc:date>
    <item>
      <title>how come the xml api is not very xmly</title>
      <link>https://community.cisco.com/t5/devnet-general-discussions/how-come-the-xml-api-is-not-very-xmly/m-p/3605050#M985</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;i have a number of examples but this one is probably the most disturbing to me as i expect xml back.&amp;nbsp; this happens when i execute this via the xml subagent, im just pasting the console output as that is easiest to replicate.&amp;nbsp; just for the record, this is not very useful to an xml parser.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;icef5-sw1# show interface fcoe | xml&lt;/P&gt;&lt;P&gt;Ethernet1/1 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/2 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/3 is FCoE UP &lt;/P&gt;&lt;P&gt;Ethernet1/4 is FCoE UP &lt;/P&gt;&lt;P&gt;Ethernet1/5 is FCoE UP &lt;/P&gt;&lt;P&gt;Ethernet1/6 is FCoE UP &lt;/P&gt;&lt;P&gt;Ethernet1/7 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/8 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/9 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/10 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/11 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/12 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/13 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/14 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/15 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/16 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/17 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/18 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/19 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/20 is FCoE UP &lt;/P&gt;&lt;P&gt;Ethernet1/21 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/22 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/23 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/24 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/25 is FCoE UP &lt;/P&gt;&lt;P&gt;Ethernet1/26 is FCoE UP &lt;/P&gt;&lt;P&gt;Ethernet1/27 is FCoE UP &lt;/P&gt;&lt;P&gt;Ethernet1/28 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/29 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/30 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/31 is FCoE down &lt;/P&gt;&lt;P&gt;Ethernet1/32 is FCoE down &lt;/P&gt;&lt;P&gt;port-channel10 is FCoE down&lt;/P&gt;&lt;P&gt;port-channel11 is FCoE down &lt;/P&gt;&lt;P&gt;port-channel12 is FCoE down &lt;/P&gt;&lt;P&gt;port-channel13 is FCoE down &lt;/P&gt;&lt;P&gt;port-channel14 is FCoE down &lt;/P&gt;&lt;P&gt;port-channel15 is FCoE down &lt;/P&gt;&lt;P&gt;port-channel20 is FCoE UP &lt;/P&gt;&lt;P&gt;&amp;lt;?xml version="1.0" encoding="ISO-8859-1"?&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;lt;nf:rpc-reply xmlns:nf="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns="&lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/nxos:1.0:if_manager" rel="nofollow" target="_blank"&gt;http://www.cisco.com/nxos:1.0:if_manager&lt;/A&gt;&lt;SPAN&gt;"&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt; &amp;lt;nf:data/&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;/nf:rpc-reply&amp;gt;&lt;/P&gt;&lt;P&gt;]]&amp;gt;]]&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Mar 2019 10:49:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/devnet-general-discussions/how-come-the-xml-api-is-not-very-xmly/m-p/3605050#M985</guid>
      <dc:creator>hotlollycakes</dc:creator>
      <dc:date>2019-03-01T10:49:50Z</dc:date>
    </item>
    <item>
      <title>Re: how come the xml api is not very xmly</title>
      <link>https://community.cisco.com/t5/devnet-general-discussions/how-come-the-xml-api-is-not-very-xmly/m-p/3605051#M986</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ashley,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; From what I understand your question is related to Cisco NX-OS XML Interface. If not please let me know. If so request to refer these two urls-&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/nx-os/xml/user/guide/nxos_xml_interface.pdf" title="http://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/nx-os/xml/user/guide/nxos_xml_interface.pdf"&gt;http://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/nx-os/xml/user/guide/nxos_xml_interface.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://opennxos.cisco.com/" title="https://opennxos.cisco.com/"&gt;https://opennxos.cisco.com/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Thanks and Regards,&lt;/P&gt;&lt;P&gt;Geevarghese&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Dec 2015 12:15:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/devnet-general-discussions/how-come-the-xml-api-is-not-very-xmly/m-p/3605051#M986</guid>
      <dc:creator>Geevarghese Cheria</dc:creator>
      <dc:date>2015-12-30T12:15:52Z</dc:date>
    </item>
  </channel>
</rss>

