Do MWR2941 anf 7600 support XML-PI?

Unanswered Question
Mar 30th, 2010


I would like to know whether the MWR2942 or 7600 support the XML-PI functionality used to convert CLI show command output results into well formated/tagged XML.

Note: the exact IOS version or NE version (e.g., 7609, 7603, ...) is not relevant for now as long as it is supported by any version that I can use for having such functionality. I'm new to Cisco support and the searches I did were not conclusive, neither for the existence nor the absence of such support.

As I need to do reporting/statistics of the routing existing configuration, I would like to know whether there are restrictions on the XML-PI supported "show" commands or if the XML-PI really covers all "show" possibilities.

Thanks in advance for your help,


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Joe Clarke Tue, 03/30/2010 - 16:38

XML-PI is supported as of 12.2(33)SRE on the 7600s.  However, it is not supported on the 2941.  Documentation for XML-PI for the 7600 can be found at .  Some show commands include a built-in ODM spec, but you will need to generate your own spec files for most commands.


Please support CSC Helps Haiti

j.cazecuteiro Wed, 03/31/2010 - 05:24

Thanks Joe for the very fast support answer!

It is now confirmed that I cannot use XML-PI for retrieving information from MWR 2941.

Some questions in addition:

A) Do you know and/or recommend any other approach that would allow to retrieve the needed information from such routers?


- I assume that it would be much easier to retrieve such information via CLI than via SNMP MIB, because many of the MIBs are even proprieraty ones

- But I also know that it can be extremely difficult (and was therefore trying to avoid) to build myself a CLI output parser, especially when I do not know the formatting details and all possibilities of each CLI "show" command's output

B)  Is there any commercial or non-comercial CLI output parser that does CLI (show output) to (well formatted/tagged) XML conversion that can also be used for such routers?

C) Is the SNMP MIB retrieval really an alternative? Can I retrieve via SNMP interfaces all the information otherwise possible to be retrieved via CLI?

Note. I needed to retrieve all physical resources (i.e., slots, cards, ports) but most of the logical resources (i.e., IMA ports, PWs and PWs' ACs,...) together with some of their properties (i.e., ids, types, bandwidths, operator description, ...)



Joe Clarke Wed, 03/31/2010 - 22:18

You might want to have a look at the Cisco Enhanced Device Interface (E-DI).  All the details can be found at .  You can download the software for Windows or Linux to try it out.  I'm not sure if it will support the 2941, though.  There hasn't been any new device support packages put out for E-DI in a while.

The E-DI does provide a way to communicate using XML to devices which do not natively support NETCONF or XML-PI.  I don't know of any other industry products which do this.

While all of the data found in the CLI is not available via SNMP, much of the inventory data you talk about is.  CiscoWorks Resource Manager Essentials uses SNMP exclusively to build its inventory model of devices.  Depending on the device type, it queries MIBs such as the ENTITY-MIB, OLD-CISCO-CHASSIS-MIB, CISCO-STACK-MIB, etc.  I'm attaching a Detailed Device Report for one of my 7603s to give you an idea of the data which is available via SNMP.


Please support CSC Helps Haiti

j.cazecuteiro Thu, 04/01/2010 - 08:50

Thanks very much for the support Joe.

I will now better investigate the information retrieval via SNMP.

Once again thanks,



j.cazecuteiro Mon, 04/05/2010 - 08:56


At last reply it was confirmed that not all information present at CLI output could be retrieved via SNMP.

But is it possible to identify in general the information that can definitely not be retrieve via SNMP, although possible to be retrieved via CLI?

Concrete questions in addition (if easy to answer):

I have to represent most important properties of ATM/IMA/TDM related Attachment Circuits associated with PWs starting/ending at those nodes.

Among the properties are:

a) all ports, slots, chassis basic properties (e.g., name, description, status, interface type for ports, ...) and the timeslots making a CESoPSN cem group plus clocking information and IMA groups and the ports or channels that they are made of together with ATM related infomation like VPI/VCI, QoS, ...

b) user configurable VCID of the PW together with Cisco router own generated inbound and outbound VCIDs of the PW

c) identify the PW's snapshot path, i.e., the path a certain PW is taking over an already established LDP LSPs, which should include the crossed routers and the different segment labels of the LSP

Can the a)  b) and c) information be retrieved via SNMP?

Note: I assume that via CLI the path information is retrieved via "trace mpls pseudowire" functionality, although I have not been able to test it since I have not yet the routers to test it.

Note2: At this moment I would suspect that c) would not be possible via SNMP but a) and b) will.



Joe Clarke Mon, 04/05/2010 - 17:37

It is very difficult to determine exactly what CLI parameters are available via SNMP.  I know that attributes such as port name, description, status, and type are available via SNMP.  As for the MPLS, IMA, and PW specific parameters, I do not know off the top of my head.  I do not have access to any such configurations which which to test.

I recommend you go to , and launch the MIB Locator tool.  Pick the platform, IOS version, and feature sets you want, then look at the MIBs supported in that version of code.  From there, you can look through the MIBs to see if they provide you access to the data you require.


Please support CSC Helps Haiti


This Discussion