Follow

Traverse: Determining adapter support and required protocol(s) for Network Configuration Management

Determining Adapter Support

You can confirm the current list of supported adapters by running the following:

Windows

  dir "<TRAVERSE_HOME>\apps\netconf\adapters"

where <TRAVERSE_HOME> is the direct path to the Traverse root directory (e.g. /usr/local/traverse)

 

Linux

 
ls -d <TRAVERSE_HOME>/apps/netconf/adapters/*

where <TRAVERSE_HOME> is the direct path to the Traverse root directory (e.g. /usr/local/traverse)

 

At this point it may take some additional research into your device and its OS. The OS may be named differently and multiple devices may use the same OS. NCM adapters are typically named according to the specific OS and not necessarily named after the device itself (e.g. Cisco IOS and Aruba OS).

 

Determining Protocol(s) Required

 To determine the required protocols for an adapter, you will need to review the adapter's metadata.

This can be found in the following path:

<TRAVERSE_HOME>/netconf/adapters/ziptie.adapters.*/scripts/ZipTie/Adapters/COMPANY/OSNAME.metadata.xml

The information above in bold will need to be updated as observed in navigating the path:

ziptie.adapters.* examples:

ziptie.adapters.generic.snmp_2008.10.0.dev

ziptie.adapters.f5.bigip_2008.10.0.dev

ziptie.adapters.hp.procurve_2008.10.0.dev

ziptie.adapters.cisco.ios_2008.10.0.dev

 

COMPANY examples for the same adapters listed previously:

Generic

F5

HP

Cisco

 

OSNAME examples for the same adapters listed previously:

SNMP.metadata.xml

BigIP.metadata.xml

ProCurve.metadata.xml

IOS.metadata.xml

 

Within the *.metadata.xml file you should be able to find the required protocols under the <operation name="backup"> tag. Please note that should both SSH and TELNET be listed, in most cases either protocol is supported. That is to say, only one is required to be enabled, but both can be enabled.

Example:

<operation name="backup">
<supportedProtocolSet>Telnet</supportedProtocolSet>
<supportedProtocolSet>SSH</supportedProtocolSet>
<supportedProtocolSet>Telnet-TFTP</supportedProtocolSet>
<supportedProtocolSet>SSH-TFTP</supportedProtocolSet>
<supportedProtocolSet>SSH-SCP</supportedProtocolSet>
</operation>

 

This requires that you have at least one of the combinations:

Telnet (assumes OS supports displaying backup configuration on screen from a CLI command)

SSH (assumes OS supports displaying backup configuration on screen from a CLI command)

Telnet + TFTP

SSH + TFTP

SSH + SCP

 

Note: Some OS/adapters support "screen scraping" a backup configuration where TFTP or SCP is not required (e.g. "show run-config" and "show startup-config").

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.