Customizing MapVendor.xml

The MapVendor.xml file is used by Auto-Discovery to map a unique string obtained from the CLI to that vendor name of that device.

Before you begin

Before editing the MapVendor.xml file, you must be familiar with XML.

About this task

This task assumes that you are familiar with the XML tags described in the following table:

XML tag Description

<vendorlist>

The file contains <vendorlist> tags. Embedded inside are <vendor> and <output> tags. The name attribute in each <vendor> tag indicates that everything enclosed within these tags apply to the specified vendor, which in this example are CISCO and Juniper devices only.

Procedure

  1. Open the file for editing.
  2. Edit the XML tags according to your needs. Use the Example section as a guide.
  3. When you are satisfied with your edits, save and exit the file.

Example

Consider the following XML tags in a sample file:

<vendorlist>
<vendor name="CISCO">  1 
<output>Cisco</output>  2 
</vendor>
</vendorlist>

Now consider the following return from the Auto-Discovery tool when it uses a RegexList.xml file to parse the CISCO CLI:

vendor=CISCO  1 
model=2651  2 
os=12.4(5A)

The Auto-Discovery tool:

  1. Compares the value CISCO returned to vendor with the value specified in the name attribute of the <vendor> tag. The values match.
  2. Returns the value specified in the <output> tag, if the values in vendor and <vendor> match. In this example, returns the device vendor as Cisco.

Consider the following XML tags for Juniper in a sample file:

<vendor name="JUNOS">  1 
<output>Juniper</output>  2 
</vendor>
</vendorlist>

Now consider the following return from the Auto-Discovery tool when it uses a RegexList.xml file to parse the Juniper CLI:

vendor=JUNOS  1 
model=M5  2 
os=6.2R2.4

The Auto-Discovery tool:

  1. Compares the value JUNOS returned to vendor with the value specified in the name attribute of the <vendor> tag. The values match.
  2. Returns the value specified in the <output> tag, if the values in vendor and <vendor> match. In this example, returns the device vendor as Juniper.

What to do next

You can now configure the MapModel.xml file.

For instructions on how to configure the MapModel.xml file, see Customizing MapModel.xml.

To study a complete working example of a file, see MapVendor.xml example.