i have a number of examples but this one is probably the most disturbing to me as i expect xml back. this happens when i execute this via the xml subagent, im just pasting the console output as that is easiest to replicate. just for the record, this is not very useful to an xml parser.
icef5-sw1# show interface fcoe | xml
Ethernet1/1 is FCoE down
Ethernet1/2 is FCoE down
Ethernet1/3 is FCoE UP
Ethernet1/4 is FCoE UP
Ethernet1/5 is FCoE UP
Ethernet1/6 is FCoE UP
Ethernet1/7 is FCoE down
Ethernet1/8 is FCoE down
Ethernet1/9 is FCoE down
Ethernet1/10 is FCoE down
Ethernet1/11 is FCoE down
Ethernet1/12 is FCoE down
Ethernet1/13 is FCoE down
Ethernet1/14 is FCoE down
Ethernet1/15 is FCoE down
Ethernet1/16 is FCoE down
Ethernet1/17 is FCoE down
Ethernet1/18 is FCoE down
Ethernet1/19 is FCoE down
Ethernet1/20 is FCoE UP
Ethernet1/21 is FCoE down
Ethernet1/22 is FCoE down
Ethernet1/23 is FCoE down
Ethernet1/24 is FCoE down
Ethernet1/25 is FCoE UP
Ethernet1/26 is FCoE UP
Ethernet1/27 is FCoE UP
Ethernet1/28 is FCoE down
Ethernet1/29 is FCoE down
Ethernet1/30 is FCoE down
Ethernet1/31 is FCoE down
Ethernet1/32 is FCoE down
port-channel10 is FCoE down
port-channel11 is FCoE down
port-channel12 is FCoE down
port-channel13 is FCoE down
port-channel14 is FCoE down
port-channel15 is FCoE down
port-channel20 is FCoE UP
<?xml version="1.0" encoding="ISO-8859-1"?>
<nf:rpc-reply xmlns:nf="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns="http://www.cisco.com/nxos:1.0:if_manager">
<nf:data/>
</nf:rpc-reply>
]]>]]>
