guides:reference:vendors:supported_transfer_protocols_per_device
Differences
This shows you the differences between two versions of the page.
guides:reference:vendors:supported_transfer_protocols_per_device [2022/07/18 17:32] – jbosch | guides:reference:vendors:supported_transfer_protocols_per_device [2024/07/03 12:31] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | <WRAP widths 100% box> | ||
+ | ===== Supported transfer protocols per vendor ===== | ||
+ | </ | ||
+ | |||
+ | ^ Vendor | ||
+ | ^ ^^ plain ^ vrf ^ plain ^ vrf ^ plain ^ vrf ^ plain ^ vrf ^ FTP ^^ cli show ^^ | ||
+ | | Alcatel OmniSwitch || <color green> | ||
+ | | Alcatel/ | ||
+ | | Arista/EOS || <color green> | ||
+ | | Aruba/CX || n/a || <color green> | ||
+ | | Aruba/MC || n/a || <color green> | ||
+ | | Aruba/MM || n/a || <color green> | ||
+ | | Avaya/ERS || <color green> | ||
+ | | Avaya/VSP || n/a || n/a || n/a || n/a || <color green> | ||
+ | | Checkpoint/ | ||
+ | | Ciena/CI6 || <color green> | ||
+ | | Ciena/CI8 || <color green> | ||
+ | | Cisco/ACI || <color green> | ||
+ | | Cisco/IOS || n/a || <color green> | ||
+ | | Cisco/Nexus || <color green> | ||
+ | | Cisco/WLC || <color green> | ||
+ | | Cisco/XE || n/a || <color green> | ||
+ | | Cisco/XR || <color green> | ||
+ | | Corvil/CNE || n/a || <color green> | ||
+ | | Falcon/ | ||
+ | | F5/ | ||
+ | | Fortinet/ | ||
+ | | HP/Comware5 || <color green> | ||
+ | | HP/Comware7 || <color green> | ||
+ | | Huawei/S || <color green> | ||
+ | | Huawei/CE || <color green> | ||
+ | | Juniper/ | ||
+ | | PaloAlto/ | ||
+ | | Perle IOLAN || n/a | n/a | <color green> | ||
+ | |||
+ | * not supported on each model within vendor family | ||
+ | |||
+ | Bold text indicates the default protocol used for vendor in question. \\ | ||
+ | The " | ||
+ | |||
+ | ==== Using a non default transfer protocol ==== | ||
+ | |||
+ | Click the // | ||
+ | |||
+ | {{: | ||
+ | |||
+ | ===== Configure a VRF to be used for file transfers, manual ===== | ||
+ | |||
+ | To create a new VRF, click the //Mpls vrfs// item from the Build menu, click the new button and select the desired // | ||
+ | |||
+ | {{: | ||
+ | |||
+ | Click //OK// to create this VRF. | ||
+ | |||
+ | Now to configure a node to actually use this newly created VRF go back to the main Build form and find the node you would like to configure this VRF, doubleclick the node to enter the //Edit Node// form, click the //VRFs// button to enter the VRF part of this node, click the new button and select the VRF you created earlier: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | make sure to set the value of // | ||
+ | |||
+ | ===== Configure a VRF to be used for file transfers, using service-type ===== | ||
+ | |||
+ | To update the VRF on multiple nodes is possible using the service-types and the CSV api or using XML. An example is given below. | ||
+ | |||
+ | CSV_API.ini addition: | ||
+ | < | ||
+ | [VrfMgmt] | ||
+ | brief = Enable VRF management for a VRF on a node | ||
+ | Hostname | ||
+ | Vrf_id | ||
+ | </ | ||
+ | |||
+ | A service-type needs to be added with the following contents. (click the image for a larger view) | ||
+ | {{: | ||
+ | |||
+ | The following sheet can be used to automate the nodes and the attached VRF to enable the Vrf_management flag. Make sure to match the values of the Client_type, | ||
+ | |||
+ | {{ : |